Thursday, 2019-05-02

typeofHey r0kk3rz00:30
r0kk3rztypeof: hello01:07
osum4eststil trying to get cellular working. i tried disabling ofono, start rild manually, then starting ofono but that didn't seem to help. here's the log cat when doing that: looks like rild might not be able to find/register the modem?01:43
r0kk3rzyeah rild doesnt look that happy01:46
r0kk3rzcheck for modem firmware?01:46
osum4estwhere would it be?01:47
r0kk3rzdepends on the device, normally you dont have to worry about it01:50
osum4esti have a /dev/block/platform/soc/624000.ufshc/by-name/modem_a/b folder if that means anything to you01:53
r0kk3rzok, so the modem has its own firmware partition01:54
r0kk3rzthats mounted?01:54
osum4estit is not mounted01:55
osum4estwhere should it be mounted?01:56
r0kk3rz /modem at a guess01:57
osum4estguess i should look in android01:59
T4<StillJustGerd> so apparently the 15.1 tree should be working, but instead i'm getting this error:
T4<StillJustGerd> ninja: error: 'libsf_compat_layer', needed by 'hybris-hal', missing and no known rule to make it02:35
T4<StillJustGerd> am i doing something wrong?02:35
osum4esthm well it worked once, somehow. i needed to mount the model partition to /firmware/radio. then i rebooted and now i can't seem to get it to work again ahah02:44
osum4estalso when it was working, vibration was working as well. not sure if thats related02:46
T4<StillJustGerd> oh actually I see what I was doing wrong I forgot to do the whole "clone libhybris to external" thing02:46
r0kk3rzandroid can be a bit of a house of cards sometimes02:46
osum4esthow do i even debug that? the logcat is the same as it was before i mounted the modem partition02:52
osum4estalso ~1/10 boots i get a green flashing light and no ui02:59
osum4estalso looks like when it does detect the sim card it gets stuck connecting to mobile data in ui. systemctl status ofono says it's unable to read mailbox and that file structure differs03:50
T4<linusdan> Can someone give me a light with the mount point? … I am in doubt about how to insert: … For being exynos 4 series I have to put as … `/ block / /`, `/block/platform/*/by-name/{partition}` or how is it in the image but removing `/dev`? …
T4<birdzhang> examples03:57
r0kk3rzosum4est: what was the issue with rild?04:08
osum4est "failed to register for modem"?04:09
r0kk3rzso you fixed that?04:10
osum4estkind of? i added a mount for modem to /firmware/radio to my fstab, and rild runs successfully and detects that there's a sim card about 1/10 boots04:11
r0kk3rzok so its some kind of timing issue at boot04:13
T4<linusdan> I found what I wanted. Thanks for the light @birdzhang :)04:16
osum4estr0kk3rz, thats what i'm thinking, but i have no idea how to solve that04:16
r0kk3rzit can be a bit tricky yeah04:17
r0kk3rzmy guess is check when the firmware gets mounted04:17
osum4estits in the fstab, so shouldnt that happen before anything else? or is there an earlier way of mounting it?04:18
r0kk3rzyou can also do a `systemd-analyze plot >boot.svg` to make a chart of the boot process04:18
osum4estwoah, thats pretty cool. do you know what i'm looking for? want me to upload it somewhere?04:26
r0kk3rzwell, if you can get the one where it detects a simcard, and one without04:27
r0kk3rzit might be obvious04:27
r0kk3rzor it might not04:27
osum4estah, good idea. i'll try that out tomorrow. gotta go to bed for now. thanks for your help!04:27
r0kk3rzsometimes the mount operation can take noticably longer04:27
kimmolirinigus: merged and tagged04:48
riniguskimmoli: thanks! It looks like devel build is triggered. Let's see if testing will join as well04:53
kimmolii triggered it manually04:53
kimmolichanged that service url to mer04:54
kimmolii tried to get droid-hal-version-onyx to change version per tag, but it wanted to fetch 0.9.0 (deleted the 0.10.0 already)04:54
rinigusmal: script is needed for faq example. If fp2 is fine for it, we can refer to it04:54
riniguskimmoli: strange. I guess we'll need then to trigger testing manually as well...04:57
kimmoliyep. soon.04:58
T4<StillJustGerd> seems like something else broke and i have no idea what or how06:02
T4<StillJustGerd> i "fixed" it for now by creating that dir and giving my user permissions for it06:58
T4<StillJustGerd> is this a known issue?06:58
malrinigus: not sure which version is used more often, my version or the other08:44
malrinigus: only difference is some additional extra program calls in onyx and some other ones08:45
T4<StillJustGerd> stupid question, but how long can an initial sfos boot take? I'm not getting anything back from the phone at all, only the bootlogo08:57
malless than a minute usually09:15
malwhich device?09:15
r0kk3rzsounds normal for early stage port, you never get a full boot the first time09:16
r0kk3rzget on the telnet09:16
T4<StillJustGerd> can't, not getting anything on USB either09:20
T4<StillJustGerd> it's a known issue that on android a lot of stuff related to USB, notably tethering is broken09:20
T4<StillJustGerd> (device is montana, using LOS 15.1 as base)09:21
maldid you copy the files as mentioned in faq? notes on 15.1 porting09:22
r0kk3rzso nothing coming up in dmesg / lsusb?09:22
T4<StillJustGerd> waaait what files did i have to copy?09:25
T4<StillJustGerd> i saw the thing about cloning libhybris09:25
T4<StillJustGerd> if I forgot anything, I'm officially to stupid to read09:26
T4<elros34> 15.1 base? I bet it's skip_initramfs, check if there is something like that in boot arguments when you boot android09:27
malthat is also possible09:28
T4<StillJustGerd> nope, i forgot to copy those files. didn't realized that that point was still part of 15.109:28
T4<StillJustGerd> i'll fix it dangit09:28
mal@StillJustGerd as r0kk3rz said, it's also possibel your device might be skipping the ramdisk, did that device originally have android 8?09:29
T4<StillJustGerd> no, it originally had 7.109:30
r0kk3rzso no treble a/b shenannigans?09:31
T4<StillJustGerd> luckily no09:31
T4<StillJustGerd> there is no official, or community implementation of treble at all09:32
T4<StillJustGerd> i'll try doing the fix from the etherpad later09:34
T4<StillJustGerd> do i still symlink all of the initfiles from /system/init to /usr/libexec/droid-hybris/system/etc/init or is that a 14.1 specific quirk10:25
mal14.1 has different quirk which won't work in 15.110:26
T4<StillJustGerd> okay makes sense10:29
T4<StillJustGerd> rebuilding no10:29
T4<StillJustGerd> [Edit] rebuilding now10:29
T4<StillJustGerd> so just doing a ` -c` and then rebuilding the image with mic is enough or is there anything else i have to do?10:31
malfor that part that is enough10:32
T4<StillJustGerd> do i have to do a regular afterwards or just mic right away?10:32
mallike I said, that what said is enough10:33
T4<StillJustGerd> okay, building now10:34
T4<StillJustGerd> okay flashed and now attempting to boot11:16
T4<StillJustGerd> network device did show up this time, but went away after a few seconds11:16
T4<StillJustGerd> lsusb is blank again11:18
T4<StillJustGerd> yeah i got nothing once again11:23
T4<StillJustGerd> oops my bad i forgot to flash recovery11:31
T4<StillJustGerd> okay no change after flashing hybris-recovery.img11:33
T4<StillJustGerd> just hypothetically: the device (and android base) is arm64, but sfos is armv7hl. that should not be a problem, since arm is backwards compatible to some extent, right?11:39
malassuming you used correct values, PORT_ARCH is armv7hl and you should have "%define droid_target_aarch64 1" in droid-hal spec11:42
T4<StillJustGerd> yes, and yes11:45
T4<StillJustGerd> let me double-check11:45
T4<StillJustGerd> oh hey i somehow managed to get into telnet11:46
T4<StillJustGerd> what now11:46
T4<austenite> I get resource allocation error when playing video above 720p in 3rd video apps and browser. Is this because of 32bit?11:46
mal@austenite which apps? do all videos fail in sfos browser?11:48
T4<austenite> No , in ytplayer , LLS video player , webcat and native browser - can't play 1080p , inbuilt video player manages to work with slow frames11:50
T4<StillJustGerd> devel-su wants a password. is that password static?11:51
T4<StillJustGerd> actually nvm i'm stupid i'm already root11:51
T4<austenite> Not even 720p works if the video is large (movie)11:52
mal@austenite pastebin output of "ls -l /etc/" and "ls -l /system/etc/" from device11:57
T4<austenite> @mal ls -l /system/etc/
malthose seem normal13:06
ghosalmartinhmm device reboots to bootloader and not recovery, possibly selinux issue?18:52
piggzevening guys19:04
*** typeof is now known as type0f19:36
T4<linusdan> evening :) … I see that version is available in the repository. … Is it a pre-release or can it already be used?19:54
mal3.0.3 is early-access release19:55
malalso you shouldn't try to update to it without rebuilding middleware, it will break otherwise19:55
piggzmal: how you fancy working on p-o-v ? :P19:56
T4<linusdan> mal: I was going to update the SDK, but I'll wait a little bit :)19:57
malpiggz: not today19:58
osum4eststill can't seem to get cellular to work regularly, only works about 1/10 boots. heres a journal when it doesnt work: and a journal when it does: i looked at the svg's made by systemd-analyze but nothing stood out. my firmware-radio.mount always happens before ofono starts. when sim card isn't detected, rild isn't running, and if i run it manually then the20:03
osum4estlogcat says that it failed to register for modem:
malyou should also show normal logcat, not only logcat -b radio like you did now20:16
osum4estand just so you know, i had to manually add the modem firmware mount to my fstab. i have a modem_a/b partition and needed to mount it to /firmware/modme20:25
malthat has quite bad looking backtrace from qcom PeripheralManager20:27
malwhich is asked by ril so there is the problem20:27
malbut why is that not running is another question20:27
malosum4est: where did you mount the modem partition?20:28
maldid you need any symlinks, often those are needed20:28
malosum4est: can you show the original fstab for your device i.e. give a link to your device repo20:28
osum4estmounted it to /firmware/radio thats where android had it. haven't checked for symlinks, is there some way to search for symlinks that point to a certain location? original fstab:
osum4esti added the same options, but systemd didin't seemt o like the context one, wait, or slotselect (just hardcoding in a for now)20:31
malI don't quite understand your problem, are you saying that mountpoint is wrong or what?20:32
malit's fixup-mountpoint that selects which (a/b) you are mounting20:33
malbecause you manually device the actual partition matching the mount20:34
osum4estmy problem is that my sim card is only detected for ~1/10 boots20:34
malam I misunderstanding your problem completely?20:34
malfirst I want to understand that mount issue20:34
malbecause I see no problem20:35
osum4esti don't have a mount issue. i'm able to successfully mount the radio partition 100% of the time20:35
osum4estwas just letting you know that i couldn't get all of the mount options to work, in case some of them are important. leaving out context and wait still lets the modem partition to mount just fine20:36
mal23:25 < osum4est> and just so you know, i had to manually add the modem firmware mount to my fstab. i have a modem_a/b partition and needed to mount it to /firmware/modme20:36
malthen what was that20:36
malam I missing something20:36
malthat looks like a problem to me20:37
malosum4est: are all of the options really needed?20:37
osum4estby default my modem firmware partition isn't mounted, i just had to add it to my fstab myself. stock sailfish didn't mount it. is that a problem?20:37
malwe do not use fstab in sfos20:37
maleverything is done in systemd20:38
osum4estbut doesnt systemd use the fstab?20:38
mallooks at /lib/systemd/system/ and you see some .mount files there20:38
malthose are what define what is mounted20:39
osum4estbut i have a firmware-radio.mount service that was generated by the fstab systemd generator20:39
malso how does that looks like20:39
malosum4est: that is created at build time20:39
osum4estjust so we're on the same page, i'm talking about /etc/fstab in the .stowaways/sailfish folder. not the android one. hold on i'll check the contents20:40
malthat is not used in normal sfos like I said already20:40
malat least it shouldn't have anything like modem partition mount20:41
malfirmware-radio.mount should be from build time, pastebin the file20:42
osum4estadding the modem to /etc/fstab cause /run/systemd/generator/ to be created. here's the file:
osum4esthow do i get it to mount properly, since sfos doesnt use the fstab?20:42
malI said those should have been created by build, not during runtime, so we need figure out why it was not created it it was missing20:43
maladding or editing fstab is not the way20:43
osum4estgot it. so the build process needs to make it's own firmware-radio.mount service?20:44
malit should have made it unless something went wrong20:46
osum4esti'll try reflashing and double checking that there isn't a .mount file already. what file in the build process creates that mount file? since it will be different for each device right?20:47
malno need to reflash, check the rpms20:50
malin droid-local-repo20:50
malin some droid-hal rpm20:51
malcalled from
osum4estso it looks like that common.fstab that i linked is not included in FSTAB_FILES in the .inc file. o dpmt20:59
osum4est... sorry didn't mean to send yet21:00
osum4estthe only android fstab file i have in my out/ folder is a recovery.fstab at target/product/marlin/recovery/root/etc/ i don't have fstab files in the /vendor or /root folders21:01
osum4estand just double checked. neither the rpm's or a new install of the zip contain mount files for mounting /firmware/radio21:07
malosum4est: hmm, maybe you have the same issue I had on one device, check output of make modules (in HABUILD_SDK) for anything related to fstab and also ueventd21:56
osum4estdon't see anything:
osum4estmal, this might be related to the ueventd.rc file problem we found the other day. that was also not being included and i had to copy it over to out/target/product/marlin/root to get ui to work22:12
malosum4est: so maybe then copy the fstab.common to vendor/etc in out, similarly as you did for the ueventd.rc22:59
malosum4est: in normal android build that is copied to fstab.marlin23:01
osum4estmal, alright, got that working. how do i integrate that into the build process though? becuase the out folder isn't on git.23:54
r0kk3rzit would be in the make files somewhere23:58

Generated by 2.17.1 by Marius Gedminas - find it at!