NeoChapay | In my device logcat show only error messages how enable verbose debugging of logcat ? | 08:05 |
---|---|---|
Yardanico | ugh, 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 |
Yardanico | and then "[ 11.231879] EXT4-fs (mmcblk0p49): Remounting filesystem read-only" | 09:43 |
mal | have you run fsck to that partition? | 09:43 |
Yardanico | mal, the bad thing is that happens for some other people testing my builds, not only me | 09:44 |
Yardanico | *it happens | 09:44 |
Yardanico | so yeah, it remounts / and /data as ro | 09:45 |
Yardanico | and that's why boot doesn't continue | 09:45 |
r0kk3rz | Yardanico: could be a shutdown issue? | 09:46 |
Yardanico | r0kk3rz, hmm, yeah, probably | 09:46 |
Yardanico | maybe there were other errors for other people, I need to experiment | 09:47 |
Yardanico | but the most weirdest thing about this ext4 issue - it works after some reboots | 09:52 |
Yardanico | ext4 still says an error but doesn't remount / and /data as ro | 09:53 |
Yardanico | oh wait wtf no | 09:56 |
Yardanico | it still mounted / and /data as ro but GUI loaded | 09:56 |
Yardanico | I'll try to format /data on my device | 09:58 |
Yardanico | ok, nvm, it's not a fs issue because it doesn't boot with "rw" mounted partitions | 10:23 |
Yardanico | oh, so "wait-session-to-start[2980]: In wait loop (410) - state: activating" in journalctl | 10:29 |
Yardanico | and 410 keeps going up to 411, 412, 413, etc | 10:29 |
Yardanico | so 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 |
Yardanico | ah nvm it finds it in /system/lib | 13:00 |
r0kk3rz | yeah typically theres lots of things that scan directories for files | 13:05 |
r0kk3rz | ome of them are needed, some of them are optional | 13:05 |
tmp64 | Hey! I'm porting to ASUS Z00ED (ZE500KL) and I've got an error with build_packages.sh: Unknown option '--allow-unsigned-rpm' | 13:10 |
r0kk3rz | post the full output | 13:11 |
tmp64 | https://pastebin.com/EBmNBfLn | 13:12 |
tmp64 | Wait | 13:13 |
tmp64 | I ran it with --droid-hal and it worked | 13:13 |
r0kk3rz | yeah that only runs a subset of the whole thing | 13:15 |
tmp64 | Ok | 13:20 |
tmp64 | Well, 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 |
r0kk3rz | you must have missed a step | 13:24 |
r0kk3rz | theres some repos you need to create that live in folders like that | 13:25 |
Yardanico | which libs (except gstreamer) are usually loaded when playing a video? I'm interested in libs on android hal side mostly | 13:25 |
Yardanico | well, doesn't matter, I'll try to flash sfos-patched kernel and run it on LOS 14.1 and check if video still plays | 13:27 |
Yardanico | or not, hmm | 13:27 |
r0kk3rz | yeah thats pointless, dont do that | 13:27 |
tmp64 | I 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 |
Yardanico | r0kk3rz, well, I don't know what to do :D | 13:27 |
abranson | tmp64: 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 now | 13:28 |
tmp64 | Ok, thanks everyone! | 13:29 |
r0kk3rz | abranson: ah you brokez it! | 13:29 |
abranson | r0kk3rz: well this package management upgrade is proving a bit too disruptive to avoid that :D | 13:49 |
r0kk3rz | abranson: i'm sure | 14:00 |
taixzo | mal: any luck with the matissewifi port? | 14:26 |
tmp64 | Where should I see the flashable ZIP? All I got is a tar.bz2 of rootfs. | 14:31 |
tmp64 | I also see a lot of floating point exceptions in the log | 14:32 |
r0kk3rz | you probably didnt install zip | 14:35 |
tmp64 | Yeah, that's the problem, there is no zip file. Here's the log: https://pastebin.com/V02Vahj5 | 14:38 |
tmp64 | Looks like I'm gonna have to manually unpack rootfs and 'fastboot boot' the boot image | 14:48 |
r0kk3rz | or install zip | 14:48 |
r0kk3rz | like 'zypper in zip' | 14:49 |
tmp64 | No, I don't have a ZIP file that I can flash in TWRP, not the zip utility | 14:52 |
tmp64 | Anyway, I should be able to boot into Sailfish with fastboot | 14:55 |
r0kk3rz | do you or do you not have the zip utility installed in the platform sdk chroot | 14:56 |
r0kk3rz | is that clear enough? | 14:56 |
r0kk3rz | in order to pack the rootfs into a zip file that needs to be installed | 14:56 |
tmp64 | I thought it would pack it autmagically. The manual says I should get a ZIP to flash in recovery. | 14:59 |
r0kk3rz | yes, it does | 14:59 |
tmp64 | Not in my case | 14:59 |
r0kk3rz | but its not that magic, it still needs the program | 14:59 |
tmp64 | I do have zip installed | 15:00 |
Yardanico | tmp64, in ubuntu chroot? | 15:01 |
r0kk3rz | you dont run mic in the ubuchroot | 15:02 |
Yardanico | ah yeah sorry | 15:02 |
tmp64 | In platform sdk, yeah | 15:02 |
tmp64 | I'm untaring the rootfs now | 15:02 |
mal | taixzo: sorry, I haven't yet looked into that | 15: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 8 | 15:30 |
T4 | <adampigg> 👍 | 15:31 |
mal | I think it's almost ready for pull request | 15:31 |
T4 | <adampigg> mal, what is the repo for that, interested to see how it works | 15:31 |
mal | @adampigg https://github.com/mlehtima/geoclue-providers-hybris/tree/libgbinder | 15:32 |
mal | I haven't been able to test everything yet, not sure how to make some callbacks trigger | 15: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 code | 15:38 |
tmp64 | I 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 |
tmp64 | I 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 |
mal | tmp64: some devices have has issues unpacking the tar in recovery and some people have managed to fix it by changing the recovery version | 16:11 |
mal | *have had | 16:12 |
tmp64 | I 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 |
mal | tmp64: which device are you using? | 16:13 |
tmp64 | ASUS ZE500KL (Z00ED) with TWRP recovery and LOS 14.1 by audahadi | 16:15 |
tmp64 | (dmesg) Out of memory: Kill process 274 (tar) | 16:15 |
mal | how much memory does that have? | 16:16 |
tmp64 | I'll try an older recovery | 16:16 |
tmp64 | 2 GB | 16:16 |
mal | very odd, seems like some bug somewhere | 16:16 |
Yardanico | mal, I had this too on two TWRP recovery versions and found one which didn't crash | 16:20 |
Yardanico | somehow tar takes all memory even on my 3gb device | 16:20 |
Yardanico | (but with this working twrp it keeps running with 10mb free) | 16:20 |
tmp64 | I tried older versions, but they don't recognize adopdable storage microSD. Gonna copy to /data | 16:21 |
Yardanico | tmp64, you can also compile your own TWRP but it will take some time :) | 16:22 |
tmp64 | Yardanico, there are some older TWRPs for MM. Currently I'm on 2.8.7.7. | 16:24 |
tmp64 | I think it's done | 16:24 |
tmp64 | I can ping it over USB, but no telnet (Connection refused) | 16:29 |
tmp64 | Wait | 16:29 |
tmp64 | The port is default | 16:29 |
mal | tmp64: port 23 or 2323 | 16:30 |
tmp64 | Yeah, I'm in | 16:30 |
mal | which one worked? | 16:30 |
tmp64 | 23 | 16:32 |
mal | tmp64: 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#L5 | 16:32 |
mal | ok, if you are in 23 then the stuff I said are not relevant yet but still needed later | 16:32 |
tmp64 | Kernel panic | 16:33 |
mal | tmp64: check /init.log for mount issues | 16:33 |
tmp64 | After continue | 16:33 |
tmp64 | I'll check last dmesg | 16:33 |
mal | tmp64: if it stops in 23 then something is wrong and no point in continuing before yo have fixed the issue | 16:34 |
tmp64 | Ok | 16:34 |
tmp64 | I also forgot to enable ramoops | 16:34 |
tmp64 | I found the error | 16:37 |
tmp64 | I made mistakes in fixup-mountpoints | 16:38 |
*** phlixi is now known as phlixi_ | 16:48 | |
tmp64 | I got past switch_root but I'll finish it tomorrow. Thanks for help, everyone | 16:57 |
Yardanico | well, my problem with video is even worse - I can't play any videos EVEN with omx and libav installed :( | 18:01 |
r0kk3rz | sounds bad | 18:05 |
wiktorek140 | is there a magick about sensorfwd? some logs (https://pastebin.com/ib5W6V9W), symptoms: accelerometr, rotation, and proximity (auto brightness) doesn't work | 18:46 |
Yardanico | wiktorek140, what does "test_sensors" say? | 18:48 |
wiktorek140 | Yardanico: it work a little moment and then crash, and after restart sensorfwd service it work a liitle again | 18:49 |
wiktorek140 | Yardanico: https://pastebin.com/32j7rKFq | 18:49 |
Yardanico | oh, 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 |
wiktorek140 | Yardanico: there is super easy, my device has olny 32bit libs | 18:52 |
Yardanico | lol :) | 18:52 |
wiktorek140 | only* | 18:52 |
mal | wiktorek140: something like this https://github.com/mer-hybris/droid-config-sony-nile/blob/master/sparse/usr/share/csd/settings.d/hw-settings.ini | 18:55 |
mal | wiktorek140: oh, you had some lower level issue | 18:55 |
wiktorek140 | mal: its there | 18:55 |
wiktorek140 | mal: i think i fond a some kind of solution but dont know its configured correctly | 18:56 |
mal | wiktorek140: at least test_sensors looks reasonable | 18:57 |
wiktorek140 | mal: the true is if i configure /etc/sensorfwd/sensord.conf.d/* accelerometer and als sensors work correctly | 18:59 |
wiktorek140 | but still no autorotation | 18:59 |
Yardanico | what about hw-settings.ini? | 19:01 |
Yardanico | try 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#L18 | 19:02 |
wiktorek140 | Yardanico: i dont have gyroscope | 19:03 |
mal | wiktorek140: can you show what you have in that file, are you sure you added that hw-settings.ini to correct place with correct name | 19:03 |
wiktorek140 | mal: https://pastebin.com/qyXg1d4w | 19:05 |
wiktorek140 | file is extacly there where should be | 19:05 |
mal | wiktorek140: does journalctl output tell anything about sensors? | 19:07 |
mal | from sensorfw | 19:08 |
wiktorek140 | mal: yea, thats what i put up | 19:08 |
mal | fp2 needed a delay service to make sure android side is ready when sensorfw starts | 19:08 |
mal | https://github.com/mlehtima/droid-config-fp2-sibon/blob/master/sparse/lib/systemd/system/sensors-delay-hack.service | 19:09 |
Yardanico | mal, can gui fail to boot if bluetooth service fails to start? | 19:09 |
mal | Yardanico: not sure if something depends on it | 19:10 |
wiktorek140 | mal: i will try | 19:11 |
wiktorek140 | it help for accelerometer and als sensor | 19:12 |
wiktorek140 | but rotation stil doent work | 19:12 |
mal | wiktorek140: dynamic rotation only works if sensors were working before UI started | 19:13 |
wiktorek140 | mal: so i will try again, maybe litte more time | 19:13 |
mal | wiktorek140: just curious, how do you test dynamic rotation? | 19:14 |
wiktorek140 | by rotating the phone? | 19:15 |
wiktorek140 | mal: and app messerwerk or something similiar written | 19:17 |
wiktorek140 | mal: little more time help. i will test it more on 5 sec as it was | 19:18 |
mal | wiktorek140: you have to have some app open that actually supports dynamic rotation, like messages app | 19:26 |
wiktorek140 | mal: yea, i know it. i test it on messages app | 19:27 |
T4 | <adampigg> Yardanico, for omx, you created the device specific config? | 19:35 |
Yardanico | @adampigg you mean gstomx.conf? | 19:37 |
wiktorek140 | mal: so stay best oponent, buletooth dont remeber state after reboot | 19:43 |
wiktorek140 | connman file exist and filled correctly | 19:43 |
mal | wiktorek140: not sure why it doesn't work, is bt address correct? | 20:05 |
wiktorek140 | mal: what mean it is correct? its other than 00:00:00:00:00:00 | 20:07 |
wiktorek140 | but it start with 00: | 20:07 |
mal | could you give the first 3 parts of it i.e. the vendor code | 20:09 |
wiktorek140 | mal: 00:a0:c6 | 20:17 |
mal | ok, that says Qualcomm as vendor | 20:18 |
wiktorek140 | mal: i will check init scripts, but i dont think i can find something there | 20:19 |
mal | for me it gives the actual device vendor i.e. Fairphone | 20:19 |
mal | so maybe you have issue with bluetooth init | 20:19 |
mal | which script do you use for initializing it? | 20:19 |
wiktorek140 | mal: droid-hcismd-up | 20:20 |
wiktorek140 | mal: this one extacly https://github.com/wiktorek140/droid-config-surnia/blob/hybris-12.1/sparse/usr/bin/droid/droid-hcismd-up.sh | 20:20 |
mal | wiktorek140: 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.sh | 20:23 |
wiktorek140 | mal: i can test your version | 20:23 |
wiktorek140 | mal: i get it when i fix bt on hybris-14, and there it work | 20:26 |
wiktorek140 | mal: and yes, i think it should be this version because my bt address is now pure text ;) | 20:27 |
wiktorek140 | mal: your script can't parse output from hci_qcom_init | 20:30 |
wiktorek140 | and bt now its random after reboot ;) | 20:31 |
mal | so my version doesn't work for you | 20:39 |
wiktorek140 | mal: i check init files but i dont find any clues there | 20:47 |
mal | wiktorek140: in 14.1 it worked better? | 20:50 |
wiktorek140 | yes. on this same script if i remeber correct | 20:50 |
mal | do you have some other issues in 14.1? | 20:51 |
wiktorek140 | mal: yes. cannot reboot | 20:51 |
wiktorek140 | mal: in 14.1 i have only reboot issue. on 12.1 only bluetooth issue | 20:53 |
mal | powering off works though? | 20:57 |
wiktorek140 | mal: nope. reboot, poweroff halt dont work | 20:57 |
wiktorek140 | only hard power off(via keys) or kernel trigger(via commandline) | 20:58 |
mal | ok | 20:58 |
mal | so some kernel issue probably, it gets stuck | 20:59 |
wiktorek140 | yes, but its inherited from 13.0 branch somewhere | 20:59 |
mal | not sure if that is worse than fp2 not shutting down at all, it always reboots | 20:59 |
wiktorek140 | mal: i think my issue is less troublesome for end user but it still bad | 21:00 |
mal | ot sure if some key combination would make fp2 shutdown, some device have special keys for that | 21:02 |
mal | in fp2 the issue is even in android | 21:02 |
mal | with certain camera module, only if that module is present | 21:02 |
wiktorek140 | in surnia is the same, sometime freeze and dont reboot | 21:03 |
wiktorek140 | mal: and without this module it work normal? | 21:03 |
mal | wiktorek140: yes, also with older camera module it works fine | 21:03 |
mal | I have been trying to debug the issue by checking the kernel changes related to the new module but no luck yet | 21:04 |
wiktorek140 | mal: so why dont left older module? | 21:04 |
wiktorek140 | and if i understand corectly module is prebuilded? | 21:05 |
mal | wiktorek140: the module is user changeable, the new module has more megapixels than the old one | 21:06 |
mal | wiktorek140: fp2 is modular and user can change some parts (mostly with same spare parts but camera modules were upgraded) | 21:07 |
wiktorek140 | oh, now i understand | 21:08 |
wiktorek140 | but is strange that camera trigger reboot somehow | 21:09 |
mal | wiktorek140: 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 themselves | 21:09 |
wiktorek140 | mal: its very practical, and if it have source code its even more practical | 21:10 |
wiktorek140 | its get official update to android 7? | 21:11 |
mal | yes, it should get android 7 soon, community already got official lineage 15.1 support for it also | 21:12 |
wiktorek140 | and new module work corectly on android 7? | 21:13 |
mal | nope | 21:13 |
wiktorek140 | maybe 15.1? | 21:13 |
mal | shutdown issue is in all os versions | 21:14 |
mal | it's a kernel bug | 21:14 |
wiktorek140 | mal: maybe its a stupid question, and probably u try this, but did u strace poweroff? | 21:15 |
mal | no, not sure what that would help if the issue is in kernel | 21:16 |
wiktorek140 | sometime u can find solution in place where u will never look because of something ;) | 21:18 |
wiktorek140 | mal: are u still there? | 21:28 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!