Tuesday, 2018-08-14

NeoChapayIn my device logcat show only error messages how enable verbose debugging of logcat ?08:05
Yardanicough, about my issue when sometimes gui doesn't load: "EXT4-fs error (device mmcblk0p49): ext4_mb_generate_buddy:757: group 171, block bitmap and bg descriptor inconsistent: 438 vs 387 free clusters"09:43
Yardanicoand then "[   11.231879] EXT4-fs (mmcblk0p49): Remounting filesystem read-only"09:43
malhave you run fsck to that partition?09:43
Yardanicomal, the bad thing is that happens for some other people testing my builds, not only me09:44
Yardanico*it happens09:44
Yardanicoso yeah, it remounts / and /data as ro09:45
Yardanicoand that's why boot doesn't continue09:45
r0kk3rzYardanico: could be a shutdown issue?09:46
Yardanicor0kk3rz, hmm, yeah, probably09:46
Yardanicomaybe there were other errors for other people, I need to experiment09:47
Yardanicobut the most weirdest thing about this ext4 issue - it works after some reboots09:52
Yardanicoext4 still says an error but doesn't remount / and /data as ro09:53
Yardanicooh wait wtf no09:56
Yardanicoit still mounted / and /data as ro but GUI loaded09:56
YardanicoI'll try to format /data on my device09:58
Yardanicook, nvm, it's not a fs issue because it doesn't boot with "rw" mounted partitions10:23
Yardanicooh, so "wait-session-to-start[2980]: In wait loop (410) - state: activating" in journalctl10:29
Yardanicoand 410 keeps going up to 411, 412, 413, etc10:29
Yardanicoso I'm stracing jolla-gallery when trying to play a video, and it shows a lot of "open("/usr/libexec/droid-hybris/system/lib/libstagefright_enc_common.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)" for different .so libraries in "/usr/libexec/droid-hybris/system/lib/", is that ok?13:00
Yardanicoah nvm it finds it in /system/lib13:00
r0kk3rzyeah typically theres lots of things that scan directories for files13:05
r0kk3rzome of them are needed, some of them are optional13:05
tmp64Hey! I'm porting to ASUS Z00ED (ZE500KL) and I've got an error with build_packages.sh: Unknown option '--allow-unsigned-rpm'13:10
r0kk3rzpost the full output13:11
tmp64I ran it with --droid-hal and it worked13:13
r0kk3rzyeah that only runs a subset of the whole thing13:15
tmp64Well, the whole thing doesn't work. The same error and I don't have 'hybris/droid-configs/installroot/' dir. What do I do?13:24
r0kk3rzyou must have missed a step13:24
r0kk3rztheres some repos you need to create that live in folders like that13:25
Yardanicowhich libs (except gstreamer) are usually loaded when playing a video? I'm interested in libs on android hal side mostly13:25
Yardanicowell, doesn't matter, I'll try to flash sfos-patched kernel and run it on LOS 14.1 and check if video still plays13:27
Yardanicoor not, hmm13:27
r0kk3rzyeah thats pointless, dont do that13:27
tmp64I don't think so. I created the repos (page 21-22), ran build_packages.sh, fixed "Installed (but unpackaged)" (page 23) and ran build_packages.sh again. Ended up with 'Unknown option' error.13:27
Yardanicor0kk3rz, well, I don't know what to do :D13:27
abransontmp64: that new --allow-unsigned-rpm is required for the new libzypp that's in the next release. you should remove it from that line in the script for now13:28
tmp64Ok, thanks everyone!13:29
r0kk3rzabranson: ah you brokez it!13:29
abransonr0kk3rz: well this package management upgrade is proving a bit too disruptive to avoid that :D13:49
r0kk3rzabranson: i'm sure14:00
taixzomal: any luck with the matissewifi port?14:26
tmp64Where should I see the flashable ZIP? All I got is a tar.bz2 of rootfs.14:31
tmp64I also see a lot of floating point exceptions in the log14:32
r0kk3rzyou probably didnt install zip14:35
tmp64Yeah, that's the problem, there is no zip file. Here's the log: https://pastebin.com/V02Vahj514:38
tmp64Looks like I'm gonna have to manually unpack rootfs and 'fastboot boot' the boot image14:48
r0kk3rzor install zip14:48
r0kk3rzlike 'zypper in zip'14:49
tmp64No, I don't have a ZIP file that I can flash in TWRP, not the zip utility14:52
tmp64Anyway, I should be able to boot into Sailfish with fastboot14:55
r0kk3rzdo you or do you not have the zip utility installed in the platform sdk chroot14:56
r0kk3rzis that clear enough?14:56
r0kk3rzin order to pack the rootfs into a zip file that needs to be installed14:56
tmp64I thought it would pack it autmagically. The manual says I should get a ZIP to flash in recovery.14:59
r0kk3rzyes, it does14:59
tmp64Not in my case14:59
r0kk3rzbut its not that magic, it still needs the program14:59
tmp64I do have zip installed15:00
Yardanicotmp64, in ubuntu chroot?15:01
r0kk3rzyou dont run mic in the ubuchroot15:02
Yardanicoah yeah sorry15:02
tmp64In platform sdk, yeah15:02
tmp64I'm untaring the rootfs now15:02
maltaixzo: sorry, I haven't yet looked into that15:19
T4<adampigg> mal: anbox mounting patches worked on yet?15:29
mal@adampigg nope, I have been doing too much gps support for android 815:30
T4<adampigg> 👍15:31
malI think it's almost ready for pull request15:31
T4<adampigg> mal, what is the repo for that, interested to see how it works15:31
mal@adampigg https://github.com/mlehtima/geoclue-providers-hybris/tree/libgbinder15:32
malI haven't been able to test everything yet, not sure how to make some callbacks trigger15:32
T4<adampigg> were you able to reverse enginner the types etc fromt he android docs?15:36
mal@adampigg those are easily obtainable from automatically generated code15:38
tmp64I couldn't unpack rootfs tar. It's uses too much memory and crashes. And I don't have a ZIP file I can flash in the recovery and I have no idea how to create one or why MIC doesn't make it for me.15:55
tmp64I looked through some files and found out that ZIP would just run 'tar' command. Is there something wrong with my device that tar uses all RAM available and crashes the system?16:09
maltmp64: some devices have has issues unpacking the tar in recovery and some people have managed to fix it by changing the recovery version16:11
mal*have had16:12
tmp64I think that is a kernel issue. I'll try to "disable" low memory killer: https://together.jolla.com/question/98797/how-to-disable-lowmemorykiller/16:12
maltmp64: which device are you using?16:13
tmp64ASUS ZE500KL (Z00ED) with TWRP recovery and LOS 14.1 by audahadi16:15
tmp64(dmesg) Out of memory: Kill process 274 (tar)16:15
malhow much memory does that have?16:16
tmp64I'll try an older recovery16:16
tmp642 GB16:16
malvery odd, seems like some bug somewhere16:16
Yardanicomal, I had this too on two TWRP recovery versions and found one which didn't crash16:20
Yardanicosomehow tar takes all memory even on my 3gb device16:20
Yardanico(but with this working twrp it keeps running with 10mb free)16:20
tmp64I tried older versions, but they don't recognize adopdable storage microSD. Gonna copy to /data16:21
Yardanicotmp64, you can also compile your own TWRP but it will take some time :)16:22
tmp64Yardanico, there are some older TWRPs for MM. Currently I'm on
tmp64I think it's done16:24
tmp64I can ping it over USB, but no telnet (Connection refused)16:29
tmp64The port is default16:29
maltmp64: port 23 or 232316:30
tmp64Yeah, I'm in16:30
malwhich one worked?16:30
maltmp64: did you run the symlink script mentioned in 14.1 porting section of faq (linked in channel topic), also did you add detritus package to patterns like this https://github.com/mlehtima/droid-config-fp2-sibon/blob/master/patterns/jolla-hw-adaptation-fp2-sibon.yaml#L516:32
malok, if you are in 23 then the stuff I said are not relevant yet but still needed later16:32
tmp64Kernel panic16:33
maltmp64: check /init.log for mount issues16:33
tmp64After continue16:33
tmp64I'll check last dmesg16:33
maltmp64: if it stops in 23 then something is wrong and no point in continuing before yo have fixed the issue16:34
tmp64I also forgot to enable ramoops16:34
tmp64I found the error16:37
tmp64I made mistakes in fixup-mountpoints16:38
*** phlixi is now known as phlixi_16:48
tmp64I got past switch_root but I'll finish it tomorrow. Thanks for help, everyone16:57
Yardanicowell, my problem with video is even worse - I can't play any videos EVEN with omx and libav installed :(18:01
r0kk3rzsounds bad18:05
wiktorek140is there a magick about sensorfwd? some logs (https://pastebin.com/ib5W6V9W), symptoms: accelerometr, rotation, and proximity (auto brightness) doesn't work18:46
Yardanicowiktorek140, what does "test_sensors" say?18:48
wiktorek140Yardanico: it work a little moment and then crash, and after restart sensorfwd service it work a liitle again18:49
wiktorek140Yardanico: https://pastebin.com/32j7rKFq18:49
Yardanicooh, I don't know then, just wanted to ask because when I was porting it didn't find any sensors (because there were no 32-bit libs available)18:51
wiktorek140Yardanico: there is super easy, my device has olny 32bit libs18:52
Yardanicolol :)18:52
malwiktorek140: something like this https://github.com/mer-hybris/droid-config-sony-nile/blob/master/sparse/usr/share/csd/settings.d/hw-settings.ini18:55
malwiktorek140: oh, you had some lower level issue18:55
wiktorek140mal: its there18:55
wiktorek140mal:  i think i fond a some kind of solution but dont know its configured correctly18:56
malwiktorek140: at least test_sensors looks reasonable18:57
wiktorek140mal: the true is if i configure /etc/sensorfwd/sensord.conf.d/* accelerometer and als sensors work correctly18:59
wiktorek140but still no autorotation18:59
Yardanicowhat about hw-settings.ini?19:01
Yardanicotry to add Gyro maybe (and some other ones) https://github.com/SailfishMarkw/droid-config-markw/blob/master/sparse/usr/share/csd/settings.d/hw-settings.ini#L1819:02
wiktorek140Yardanico: i dont have gyroscope19:03
malwiktorek140: can you show what you have in that file, are you sure you added that hw-settings.ini to correct place with correct name19:03
wiktorek140mal: https://pastebin.com/qyXg1d4w19:05
wiktorek140file is extacly there where should be19:05
malwiktorek140: does journalctl output tell anything about sensors?19:07
malfrom sensorfw19:08
wiktorek140mal: yea, thats what i put up19:08
malfp2 needed a delay service to make sure android side is ready when sensorfw starts19:08
Yardanicomal, can gui fail to boot if bluetooth service fails to start?19:09
malYardanico: not sure if something depends on it19:10
wiktorek140mal: i will try19:11
wiktorek140it help for accelerometer and als sensor19:12
wiktorek140but rotation stil doent work19:12
malwiktorek140: dynamic rotation only works if sensors were working before UI started19:13
wiktorek140mal:  so i will try again, maybe litte more time19:13
malwiktorek140: just curious, how do you test dynamic rotation?19:14
wiktorek140by rotating the phone?19:15
wiktorek140mal: and app messerwerk or something similiar written19:17
wiktorek140mal: little more time help. i will test it more on 5 sec as it was19:18
malwiktorek140: you have to have some app open that actually supports dynamic rotation, like messages app19:26
wiktorek140mal: yea, i know it. i test it on messages app19:27
T4<adampigg> Yardanico, for omx, you created the device specific config?19:35
Yardanico@adampigg you mean gstomx.conf?19:37
wiktorek140mal:  so stay best oponent, buletooth dont remeber state after reboot19:43
wiktorek140connman file exist and filled correctly19:43
malwiktorek140: not sure why it doesn't work, is bt address correct?20:05
wiktorek140mal: what mean it is correct? its other than 00:00:00:00:00:0020:07
wiktorek140but it start with 00:20:07
malcould you give the first 3 parts of it i.e. the vendor code20:09
wiktorek140mal:  00:a0:c620:17
malok, that says Qualcomm as vendor20:18
wiktorek140mal: i will check init scripts, but i dont think i can find something there20:19
malfor me it gives the actual device vendor i.e. Fairphone20:19
malso maybe you have issue with bluetooth init20:19
malwhich script do you use for initializing it?20:19
wiktorek140mal: droid-hcismd-up20:20
wiktorek140mal: this one extacly https://github.com/wiktorek140/droid-config-surnia/blob/hybris-12.1/sparse/usr/bin/droid/droid-hcismd-up.sh20:20
malwiktorek140: was that version needed and my version was not enough? https://github.com/mlehtima/droid-config-fp2-sibon/blob/master/sparse/usr/bin/droid/droid-hcismd-up.sh20:23
wiktorek140mal:  i can test your version20:23
wiktorek140mal: i get it when i fix bt on hybris-14, and there it work20:26
wiktorek140mal: and yes, i think it should be this version because my bt address is now pure text ;)20:27
wiktorek140mal:  your script can't parse output from hci_qcom_init20:30
wiktorek140and bt now its random after reboot ;)20:31
malso my version doesn't work for you20:39
wiktorek140mal: i check init files but i dont find any clues there20:47
malwiktorek140: in 14.1 it worked better?20:50
wiktorek140yes. on this same script if i remeber correct20:50
maldo you have some other issues in 14.1?20:51
wiktorek140mal: yes. cannot reboot20:51
wiktorek140mal: in 14.1 i have only reboot issue. on 12.1 only bluetooth issue20:53
malpowering off works though?20:57
wiktorek140mal: nope. reboot, poweroff halt dont work20:57
wiktorek140only hard power off(via keys) or kernel trigger(via commandline)20:58
malso some kernel issue probably, it gets stuck20:59
wiktorek140yes, but its inherited from 13.0 branch somewhere20:59
malnot sure if that is worse than fp2 not shutting down at all, it always reboots20:59
wiktorek140mal: i think my issue is less troublesome for end user but it still bad21:00
malot sure if some key combination would make fp2 shutdown, some device have special keys for that21:02
malin fp2 the issue is even in android21:02
malwith certain camera module, only if that module is present21:02
wiktorek140in surnia is the same, sometime freeze and dont reboot21:03
wiktorek140mal: and without this module it work normal?21:03
malwiktorek140: yes, also with older camera module it works fine21:03
malI have been trying to debug the issue by checking the kernel changes related to the new module but no luck yet21:04
wiktorek140mal: so why dont left older module?21:04
wiktorek140and if i understand corectly module is prebuilded?21:05
malwiktorek140: the module is user changeable, the new module has more megapixels than the old one21:06
malwiktorek140: fp2 is modular and user can change some parts (mostly with same spare parts but camera modules were upgraded)21:07
wiktorek140oh, now i understand21:08
wiktorek140but is strange that camera trigger reboot somehow21:09
malwiktorek140: quite practical that if user breaks the display and then orders a new from fairphone store they can replace it in less than a minute by themselves21:09
wiktorek140mal: its very practical, and if it have source code its even more practical21:10
wiktorek140its get official update to android 7?21:11
malyes, it should get android 7 soon, community already got official lineage 15.1 support for it also21:12
wiktorek140and new module work corectly on android 7?21:13
wiktorek140maybe 15.1?21:13
malshutdown issue is in all os versions21:14
malit's a kernel bug21:14
wiktorek140mal: maybe its a stupid question, and probably u try this, but did u strace poweroff?21:15
malno, not sure what that would help if the issue is in kernel21:16
wiktorek140sometime u can find solution in place where u will never look because of something ;)21:18
wiktorek140mal: are u still there?21:28

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!