Friday, 2019-05-31

*** birdzhang_pc is now known as birdzhang02:31
T4<adampigg> @mal [@adampigg maybe you could also try https://git …], oh, what is that doing?05:50
T4<Harsh18262> is there anyway to check which defconfig is being used in the making of hybris-boot.img i dont think the correct one is being used06:22
T4<DylanVanAssche> @adampigg [oh, what is that doing?], I think you can set the pixels of the screen for Lipstick with that config. In case Lipstick sees the screen as too wide or too small in comparison to the hardware.06:23
T4<birdzhang> @Harsh18262 grep TARGET_KERNEL_CONFIG under you device tree06:26
T4<Harsh18262> is there anyway to check after building ? because the defconfig specified by target kernel config does not match the .config or defconfig files in the out/target/... path06:44
*** OhYash1 is now known as ohyash06:54
*** Neo is now known as Guest1619107:09
T4<adampigg> @DylanVanAssche [I think you can set the pixels of the screen f …], well its 2more thing to try07:28
Mister_Magistermonich: what is required to get sim working without rild from android?07:34
Mister_Magisterpiggz: your mido builds are not even extracting lol08:27
Mister_Magisterand .ks isn't even building08:27
r0kk3rz3.0.2.8 worked08:40
Mister_Magisternot really08:40
Mister_Magisterunpacking throws error08:40
r0kk3rzfrom gitlab?08:42
T4<adampigg> Odd08:42
Mister_Magisternot really08:42
Mister_Magisterboth and from gitlab cannot unpack08:42
r0kk3rztheres a common element here08:43
Mister_Magisternot me08:44
Mister_Magisteri'm doing that for a friend08:44
Mister_Magisterwho has mido08:44
Mister_Magisterr0kk3rz: why you have to start from insulting me lel08:44
r0kk3rzdont be so sensitive :p08:45
Mister_Magister lel i even built one image myself and it again does not unpack08:46
Mister_Magistersooo it doesn't work08:53
T4<birdzhang> are you sure the file is fully downloaded, gitlab download  does not support "Range & Content-Range"08:54
Mister_Magister@adampigg 6GB of swap and it still fails to unpack (on the phone)09:12
vknechtbad twrp maybe ?09:13
Mister_Magistervknecht: it doesn't even unpack on pc but he tried 2 different twrp's and still nothing09:13
T4<adampigg> does it unpack on a pc?09:15
T4<adampigg> i heard of probelms with some recoveries unablle to unpack09:16
Mister_Magister@adampigg like i said no it doesn't09:16
Mister_Magistereven i built one image and it didn't unpack09:16
T4<adampigg> so, you are saying someone broke tar?09:16
T4<adampigg> :D09:16
T4<adampigg> well, im sure i havnt modified the packaging procedure, so, im gonna say 'not my fault'09:19
Mister_Magisterbut it's not working lel09:21
Mister_Magister12GB swap eaten09:22
Mister_MagisterLOL 15GB swap did the job09:56
T4<adampigg> that doesnt make sense, its only untarring09:57
Mister_Magisterwell i didn't make that tar09:58
malMister_Magister: can you give a link to what file you are trying to use09:58
T4<adampigg> is the problem between the keyboard and chair?09:59
Mister_Magistermal: this and this
Mister_Magister@adampigg nope09:59
Mister_Magisterwhy everyone says i'm the problem09:59
T4<adampigg> im sure ive flashed that/image before09:59
Mister_Magisterimagine uset grabbed zip and wanted to install it09:59
T4<adampigg> and others have09:59
Mister_Magisterand it failed09:59
T4<adampigg> i blame r0kk3rz10:00
* Mister_Magister blames r0kk3rz too10:00
vknechthad no problem of that kind with CI builds from few days ago...10:03
* vknecht thanks r0kk3rz :-)10:03
Mister_Magistervknecht: with 15GB it works xd10:05
vknechtif anyone wants to check video support in piggz-o-vision camera, binaries for 3.0.3 and 3.0.2 here... any insight about how to fix MediaPlayer bug...10:09
vknechtfed up with this for now, gotta go out :-)10:10
vknechtsee may 28 commit comment for how to get it to actually play the vid...10:11
malMister_Magister: that worked fine for me, I downloaded it from gitlab10:11
Mister_Magistermal: didn't unpack for me10:11
Mister_Magisterand in twrp only with 15GB swap10:11
T4<adampigg> twrp version as per xda thread?10:19
T4<birdzhang> what's the md5 ?10:21
malMister_Magister: I only tried on my laptop but that just mean the file is valid10:43
T4<jamesisaweeb> is telling me this, what am I missing here?13:25
maltoo new config submodule, check faq (linked in channel topic) and search for
T4<jamesisaweeb> ah, thank you!13:28
T4<jamesisaweeb> git reset rerturns ```fatal: Could not parse object '5758d400b50a4d391af268376d716f2456c1690d'.```13:32
malare you in correct folder13:34
T4<jamesisaweeb> $ANDROID_ROOT/hybris/droid-configs right?13:36
vknechtcd $ANDROID_ROOT/hybris/droid-configs/droid-configs-device/13:37
vknechtFAQ is a bit incorrect, missing a subdir13:37
malseems like it13:37
malfixed faq13:38
T4<jamesisaweeb> can confirm13:38
T4<jamesisaweeb> thanks13:38
T4<jamesisaweeb> ```Warning[05/31 13:50:34] : repo problem: nothing provides droid-hal-version-scale needed by pattern:jolla-hw-adaptation-scale-1-1.noarch,``` … Should I just do the Dealing with a Missing Package bit?13:51
maldid you run completely13:53
T4<jamesisaweeb> I think so13:54
T4<jamesisaweeb> I'll run it again just to be safe13:54
T4<jamesisaweeb> apparently I didn't13:56
T4<jamesisaweeb> I build libhybris right?13:56
T4<jamesisaweeb> 👍13:59
T4<jamesisaweeb> ok so I've got into telnet but i have no gui and it's still only on the huawei boot screen14:55
T4<jamesisaweeb> (Photo, 719x1280)
malnow you check if you can connect via telnet as instructed in hadk pdf15:06
malip port either 23 or 232315:07
T4<jamesisaweeb> yeah i can connect to telnet15:09
malwhich port15:13
T4<jamesisaweeb> 2315:14
malok so then you need to check /init.log and see what failed15:18
T4<jamesisaweeb> ok there's a bit here which i suspect is why it doesn't want to boot seeing as it says "Refusing to boot"15:22
T4<jamesisaweeb> here's the full logs if you want to take a look15:23
T4<jamesisaweeb> nevermind15:23
T4<jamesisaweeb> ```~ # cat /diagnosis.log  … CONFIG_AUTOFS4_FS=y not found in /proc/config.gz```15:24
malso incorrect kernel config, fix the defconfig and rebuild hybris-hal, then you can either just fastboot flash the hybris-boot.img from out/ to boot partition or run -d and then rebuild the sfos zip15:26
T4<elros34> looks like problem with wrong fixup-mountpoints15:26
malthat also15:29
mal@jamesisaweeb can you show your fixup-mountpoints changes15:29
T4<jamesisaweeb> here it is15:29
malwhich device?15:30
T4<jamesisaweeb> here's just the changes15:30
T4<jamesisaweeb> mal: scale15:30
malthe changes are wrong15:30
T4<jamesisaweeb> ah15:31
malthose should have "block/bootdevice/by-name" not "block/platform/msm_sdcc.1/by-name"15:31
malyou can see that the init.log says "DATA_PARTITION=/dev/block/bootdevice/by-name/userdata" which means the fixup didn't work15:31
T4<jamesisaweeb> alright, i've fixed it15:32
mal@jamesisaweeb so now you need to rebuild hybris-hal and then run -d and then rebuild the sfos zip15:33
malwhich android base? 15.1?15:33
T4<jamesisaweeb> alright15:33
mal@jamesisaweeb which android base? hybris-15.1?15:34
T4<jamesisaweeb> hybris-14.115:34
malok, then check the faq for 14.1 porting notes15:34
malit has some things you need in config repo15:35
T4<jamesisaweeb> will do15:35
T4<jamesisaweeb> the link to the script on the faq is broken D:15:36
malfixed it15:37
T4<jamesisaweeb> thanks!15:38
T4<jamesisaweeb> ok so now telnet is running on 232316:22
T4<jamesisaweeb> but i still have no gui16:22
T4<jamesisaweeb> but a purple light turns on now16:22
T4<elros34> progress, time to grab journalctl —no-page and dmesg16:26
T4<jamesisaweeb> here's a long journal
T4<jamesisaweeb> here's just the errors16:31
T4<jamesisaweeb> lipstick doesn't start16:31
maldroid-hal-init fails, which is bad16:32
mal@jamesisaweeb did you need straggler files define in droid-hal spec?16:32
T4<elros34> are you sure you disabled selinux?16:32
T4<jamesisaweeb> mal: nope16:32
T4<jamesisaweeb> @elros34 i'm not too sure16:33
T4<jamesisaweeb> maybe?16:33
T4<jamesisaweeb> i'll look at my defconfig16:33
T4<jamesisaweeb> i have not16:34
T4<elros34> mer-kernel-checker explains how to do it16:35
malyou need to disable it in a specific way16:35
T4<BusterBg_18> So, I know that building for 16.0 devices isn't available yet, but I have a bigger concern, does sailfish knows if a device has a notch?16:36
T4<jamesisaweeb> i think i've disabled it ok16:37
mal@jamesisaweeb so you have AUDIT=y bootparam=y and in kernel commandline selinux=016:38
T4<jamesisaweeb> no16:39
T4<jamesisaweeb> i've got audit=n bootparam=unset and selinux=??16:40
malselinux=0 is not in defconfig, it's in device repo16:40
malshow your defconfig16:41
T4<jamesisaweeb> here you go16:41
malset CONFIG_AUDIT=y and CONFIG_SECURITY_SELINUX_BOOTPARAM=y in defconfig, then find the kernel command line option part in device repo, usually in and add selinux=0 to that16:45
T4<jamesisaweeb> ```# SELinux … BOARD_SEPOLICY_DIRS += \ …     $(VENDOR_PATH)/sepolicy``` … is this the right bit?16:48
T4<jamesisaweeb> It's not anywhere in boardconfig.mk16:56
T4<jamesisaweeb> should i add it?16:56
vknechtgit grep BOARD_KERNEL_CMDLINE17:02
vknechtmight help to find it if it's in different file17:02
T4<jamesisaweeb> found it17:03
T4<jamesisaweeb> kernel.mk17:03
T4<jamesisaweeb> should i remove androidboot.selinux=permissive?17:04
malprobably no need to remove, but doesn't hurt either17:12
T4<jamesisaweeb> all done17:15
T4<jamesisaweeb> now to rebuild17:15
T4<jamesisaweeb> do i just need the kernel or do i need to rebuild the whole zip17:16
malfor this kernel is enough, assuming you already rebuilt after the fixup-mountpoint fixes17:17
T4<jamesisaweeb> 👍17:18
T4<jamesisaweeb> still no gui :(17:59
malnew logs18:00
T4<jamesisaweeb> one sec18:01
malcheck what journal log says about droid-hal-init18:01
T4<jamesisaweeb> ```Failed to start droid-hal-init.```18:02
malsame error about property area?18:04
T4<jamesisaweeb> yeah18:04
T4<jamesisaweeb> here's all the errors again18:07
malcheck that kernel commandline looks ok with "cat /proc/cmdline"18:07
malalso "zcat /proc/config.gz | grep SELINUX"18:08
malshow dmesg18:08
malyou can see your changes are not there18:09
malare you sure you correctly installed the newly built kernel?18:09
T4<jamesisaweeb> i'll reinstall it but i'm pretty sure i did it right18:09
mal@jamesisaweeb what exactly did you do after building the kernel?18:10
T4<jamesisaweeb> flashed boot.img via twrp18:10
malyou mean hybris-boot.img?18:10
T4<jamesisaweeb> out/product/scale/boot.img18:11
T4<jamesisaweeb> is that the wrong thing?18:11
malno, it should be hybris-boot.img18:11
T4<jamesisaweeb> ah18:12
malnot sure how those are flashed from twrp, I use fastboot to flash kernel if I need to manually do it18:12
T4<jamesisaweeb> hmm18:13
T4<jamesisaweeb> maybe the kernel didn't build or something18:13
T4<jamesisaweeb> i'm rebuilding now18:14
malyou can recheck the .config in out/ for the kernel config changes18:17
mal@jamesisaweeb just to be sure, you are building the kernel in HABUILD_SKD by running make hybris-hal, or make hybris-boot18:18
T4<jamesisaweeb> yes18:18
T4<jamesisaweeb> and i can't see a .config file in /out18:18
malit's somewhere under it, "find out/ -name .config"18:19
T4<jamesisaweeb> yeah all the changes are there18:20
malok, then try to flash the hybris-boot.img to boot partition18:23
T4<jamesisaweeb> droid hal still doesn't work18:26
malmake sure the kernel is now correct18:37
T4<jamesisaweeb> they're still not there18:38
malhow did you install the kernel?18:38
T4<jamesisaweeb> i flashed it in twrp18:38
malI have no idea how that is done in twrp18:38
maland if it's even supposed to work18:38
T4<jamesisaweeb> i could try fastboot18:38
maltry with fastboot18:39
T4<jamesisaweeb> oh hey it worked18:41
T4<jamesisaweeb> selinux=018:41
malgood, any change in dmesg18:42
T4<jamesisaweeb> not sure18:43
malis droid-hal-init still failing18:43
T4<jamesisaweeb> yeah :(18:43
T4<jamesisaweeb> so uhh19:54
T4<jamesisaweeb> how hard is this to fix?19:54
T4<jamesisaweeb> i can't find much on google19:55
vknechtbetter than google in most cases:
vknechtalso can try adding to your G searches19:57
malthere are some possible ways, we just need to figure out which is the correct way19:58
T4<jamesisaweeb> vlnecht: thanks20:05
vknecht@jamesisaweeb: could try disabling qseecomd service by inserting "disabled" here:
vknecht(faq line 668, iirc it helped for my msm8916/8939 device)20:31
T4<jamesisaweeb> thanks! i guess i rebuild the zip now, right?20:35
vknechthmm, if I'm correct only make hybris-boot and flash should be ok20:37
vknechtbut when in doubt, you can do the whole thing :)20:37
T4<jamesisaweeb> i'll do the whole thing, just to be safe20:37
mal@jamesisaweeb you can test the change on device20:39
mal@jamesisaweeb also that won't be in kernel20:39
mal@jamesisaweeb so hybris-hal build is needed and new image, but maybe try first manually by editing the file on device20:40
T4<jamesisaweeb> ah, ok20:40
malthat file is probably in device root but could be named differenty, you'll find it20:41
Nokiusgood evening is there a way to tell in the ks file from which source the pkg should be installed? :-/20:43
malNokius: what package is the issue20:43
malNokius: the easy way is to just bump the version in that package20:43
Nokiusmal: it's qt-core20:45
malNokius: hmm, why do you need custom package for that20:45
Nokiusfor the custom Eviorment20:46
malassuming the version of that package is bigger than the one in official repo then it will be installed if you add the repos to .ks20:46
Nokiusmal: let's see =)20:47
Nokiusmal: many thanks20:47
malNokius: you can check in the packages file after image build20:48
Nokiusmal: thy, I will do so20:55
Nokiusr0kk3rz[m]: sorry for the ci spam20:58
T4<jamesisaweeb> vknecht: still doesn't work D:21:13
Nokiusmal: looks like it worked :D21:20
Nokiusmal: sometimes it's just easy :))21:20
Nokiusmal: have a great weekend o/21:20
vknecht@jamesisaweeb: too bad... maybe post fresh logs (dmesg, logcat...)21:22
T4<jamesisaweeb> Will do on a sec21:25
T4<jamesisaweeb> here's dmesg21:29
T4<jamesisaweeb> and here's journalctl
T4<jamesisaweeb> annnd here's just the errors
T4<DSstill01> How can i tell ofono not to hi21:39
T4<DSstill01> [Edit] How can i tell ofono not to hide the phone that is calling me? In ofono log number: blank during a call21:40
T4<DSstill01> On UI it says "private number" instead of telling me the number which is calling me21:41
vknecht@jamesisaweeb: did you try running test_hwcomposer yet ?21:54
malvknecht: no point in that because droid-hal-init fails22:13

Generated by 2.17.1 by Marius Gedminas - find it at!