| typeof | Hey r0kk3rz | 00:30 |
|---|---|---|
| r0kk3rz | typeof: hello | 01:07 |
| typeof | Sup? | 01:09 |
| osum4est | stil 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: https://pastebin.com/kGMLW5Hq looks like rild might not be able to find/register the modem? | 01:43 |
| r0kk3rz | yeah rild doesnt look that happy | 01:46 |
| r0kk3rz | check for modem firmware? | 01:46 |
| osum4est | where would it be? | 01:47 |
| r0kk3rz | depends on the device, normally you dont have to worry about it | 01:50 |
| osum4est | i have a /dev/block/platform/soc/624000.ufshc/by-name/modem_a/b folder if that means anything to you | 01:53 |
| r0kk3rz | ok, so the modem has its own firmware partition | 01:54 |
| r0kk3rz | thats mounted? | 01:54 |
| osum4est | it is not mounted | 01:55 |
| osum4est | where should it be mounted? | 01:56 |
| r0kk3rz | /modem at a guess | 01:57 |
| osum4est | guess i should look in android | 01:59 |
| T4 | <StillJustGerd> so apparently the 15.1 tree should be working, but instead i'm getting this error: https://hastebin.com/okituqihuy | 02:34 |
| T4 | <StillJustGerd> ninja: error: 'libsf_compat_layer', needed by 'hybris-hal', missing and no known rule to make it | 02:35 |
| T4 | <StillJustGerd> am i doing something wrong? | 02:35 |
| osum4est | hm 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 ahah | 02:44 |
| osum4est | also when it was working, vibration was working as well. not sure if thats related | 02:46 |
| r0kk3rz | possibly | 02:46 |
| T4 | <StillJustGerd> oh actually I see what I was doing wrong I forgot to do the whole "clone libhybris to external" thing | 02:46 |
| r0kk3rz | android can be a bit of a house of cards sometimes | 02:46 |
| osum4est | how do i even debug that? the logcat is the same as it was before i mounted the modem partition | 02:52 |
| osum4est | also ~1/10 boots i get a green flashing light and no ui | 02:59 |
| osum4est | also 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 differs | 03: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`? … https://photos.app.goo.gl/Q2NKnCPRaFxnekCe9 | 03:50 |
| T4 | <birdzhang> https://github.com/mer-hybris/hybris-boot/blob/master/fixup-mountpoints | 03:57 |
| T4 | <birdzhang> examples | 03:57 |
| r0kk3rz | osum4est: what was the issue with rild? | 04:08 |
| osum4est | https://pastebin.com/kGMLW5Hq "failed to register for modem"? | 04:09 |
| r0kk3rz | so you fixed that? | 04:10 |
| osum4est | kind 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 boots | 04:11 |
| r0kk3rz | ok so its some kind of timing issue at boot | 04:13 |
| T4 | <linusdan> I found what I wanted. Thanks for the light @birdzhang :) | 04:16 |
| osum4est | r0kk3rz, thats what i'm thinking, but i have no idea how to solve that | 04:16 |
| r0kk3rz | it can be a bit tricky yeah | 04:17 |
| r0kk3rz | my guess is check when the firmware gets mounted | 04:17 |
| osum4est | its in the fstab, so shouldnt that happen before anything else? or is there an earlier way of mounting it? | 04:18 |
| r0kk3rz | you can also do a `systemd-analyze plot >boot.svg` to make a chart of the boot process | 04:18 |
| osum4est | woah, thats pretty cool. do you know what i'm looking for? want me to upload it somewhere? | 04:26 |
| r0kk3rz | well, if you can get the one where it detects a simcard, and one without | 04:27 |
| r0kk3rz | it might be obvious | 04:27 |
| r0kk3rz | or it might not | 04:27 |
| osum4est | ah, good idea. i'll try that out tomorrow. gotta go to bed for now. thanks for your help! | 04:27 |
| r0kk3rz | sometimes the mount operation can take noticably longer | 04:27 |
| kimmoli | rinigus: merged and tagged | 04:48 |
| rinigus | kimmoli: thanks! It looks like devel build is triggered. Let's see if testing will join as well | 04:53 |
| kimmoli | i triggered it manually | 04:53 |
| kimmoli | changed that service url to mer | 04:54 |
| kimmoli | i 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 |
| rinigus | mal: script is needed for faq example. If fp2 is fine for it, we can refer to it | 04:54 |
| rinigus | kimmoli: strange. I guess we'll need then to trigger testing manually as well... | 04:57 |
| kimmoli | yep. soon. | 04:58 |
| T4 | <StillJustGerd> seems like something else broke and i have no idea what or how | 06:02 |
| T4 | <StillJustGerd> https://hastebin.com/nuquravaze | 06:02 |
| T4 | <StillJustGerd> i "fixed" it for now by creating that dir and giving my user permissions for it | 06:58 |
| T4 | <StillJustGerd> is this a known issue? | 06:58 |
| mal | rinigus: not sure which version is used more often, my version or the other | 08:44 |
| mal | rinigus: only difference is some additional extra program calls in onyx and some other ones | 08: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 bootlogo | 08:57 |
| mal | less than a minute usually | 09:15 |
| mal | which device? | 09:15 |
| r0kk3rz | sounds normal for early stage port, you never get a full boot the first time | 09:16 |
| r0kk3rz | get on the telnet | 09:16 |
| T4 | <StillJustGerd> can't, not getting anything on USB either | 09:20 |
| T4 | <StillJustGerd> it's a known issue that on android a lot of stuff related to USB, notably tethering is broken | 09:20 |
| T4 | <StillJustGerd> (device is montana, using LOS 15.1 as base) | 09:21 |
| mal | did you copy the files as mentioned in faq? notes on 15.1 porting | 09:22 |
| r0kk3rz | so 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 libhybris | 09:25 |
| T4 | <StillJustGerd> if I forgot anything, I'm officially to stupid to read | 09: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 android | 09:27 |
| mal | that is also possible | 09:28 |
| T4 | <StillJustGerd> nope, i forgot to copy those files. didn't realized that that point was still part of 15.1 | 09:28 |
| T4 | <StillJustGerd> i'll fix it dangit | 09: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.1 | 09:30 |
| r0kk3rz | so no treble a/b shenannigans? | 09:31 |
| T4 | <StillJustGerd> luckily no | 09:31 |
| T4 | <StillJustGerd> there is no official, or community implementation of treble at all | 09:32 |
| T4 | <StillJustGerd> i'll try doing the fix from the etherpad later | 09: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 quirk | 10:25 |
| mal | 14.1 has different quirk which won't work in 15.1 | 10:26 |
| T4 | <StillJustGerd> okay makes sense | 10:29 |
| T4 | <StillJustGerd> rebuilding no | 10:29 |
| T4 | <StillJustGerd> [Edit] rebuilding now | 10:29 |
| T4 | <StillJustGerd> so just doing a `build_packages.sh -c` and then rebuilding the image with mic is enough or is there anything else i have to do? | 10:31 |
| mal | for that part that is enough | 10:32 |
| T4 | <StillJustGerd> do i have to do a regular build_packages.sh afterwards or just mic right away? | 10:32 |
| mal | like I said, that what said is enough | 10:33 |
| mal | +you | 10:33 |
| T4 | <StillJustGerd> okay, building now | 10:34 |
| T4 | <StillJustGerd> okay flashed and now attempting to boot | 11:16 |
| T4 | <StillJustGerd> network device did show up this time, but went away after a few seconds | 11:16 |
| T4 | <StillJustGerd> lsusb is blank again | 11:18 |
| T4 | <StillJustGerd> yeah i got nothing once again | 11:23 |
| T4 | <StillJustGerd> oops my bad i forgot to flash recovery | 11:31 |
| T4 | <StillJustGerd> okay no change after flashing hybris-recovery.img | 11: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 |
| mal | assuming you used correct values, PORT_ARCH is armv7hl and you should have "%define droid_target_aarch64 1" in droid-hal spec | 11:42 |
| T4 | <StillJustGerd> yes, and yes | 11:45 |
| T4 | <StillJustGerd> let me double-check | 11:45 |
| T4 | <StillJustGerd> oh hey i somehow managed to get into telnet | 11:46 |
| T4 | <StillJustGerd> what now | 11: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 frames | 11:50 |
| T4 | <StillJustGerd> devel-su wants a password. is that password static? | 11:51 |
| T4 | <StillJustGerd> actually nvm i'm stupid i'm already root | 11: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 device | 11:57 |
| T4 | <austenite> @mal https://del.dog/sfos-garlic.diff ls -l /system/etc/ https://del.dog/sfos-garlic01.diff | 12:37 |
| mal | those seem normal | 13:06 |
| ghosalmartin | hmm device reboots to bootloader and not recovery, possibly selinux issue? | 18:52 |
| piggz | evening guys | 19:04 |
| *** typeof is now known as type0f | 19:36 | |
| T4 | <linusdan> evening :) … I see that version 3.0.3.8 is available in the repository. … Is it a pre-release or can it already be used? | 19:54 |
| mal | 3.0.3 is early-access release | 19:55 |
| mal | also you shouldn't try to update to it without rebuilding middleware, it will break otherwise | 19:55 |
| piggz | mal: how you fancy working on p-o-v ? :P | 19:56 |
| T4 | <linusdan> mal: I was going to update the SDK, but I'll wait a little bit :) | 19:57 |
| mal | piggz: not today | 19:58 |
| osum4est | still can't seem to get cellular to work regularly, only works about 1/10 boots. heres a journal when it doesnt work: https://pastebin.com/1iTG71rH and a journal when it does: https://pastebin.com/XAF54JwA 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 the | 20:03 |
| osum4est | logcat says that it failed to register for modem: https://pastebin.com/wU6X9JPG | 20:03 |
| mal | you should also show normal logcat, not only logcat -b radio like you did now | 20:16 |
| osum4est | mal, https://pastebin.com/cyDXPxRi | 20:23 |
| 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/modme | 20:25 |
| osum4est | */firmware/radio | 20:25 |
| mal | that has quite bad looking backtrace from qcom PeripheralManager | 20:27 |
| mal | which is asked by ril so there is the problem | 20:27 |
| mal | but why is that not running is another question | 20:27 |
| mal | osum4est: where did you mount the modem partition? | 20:28 |
| mal | did you need any symlinks, often those are needed | 20:28 |
| mal | osum4est: can you show the original fstab for your device i.e. give a link to your device repo | 20:28 |
| osum4est | mounted 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: https://github.com/LineageOS/android_device_google_marlin/blob/lineage-16.0/fstab.common | 20:30 |
| osum4est | i 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 |
| mal | I don't quite understand your problem, are you saying that mountpoint is wrong or what? | 20:32 |
| mal | it's fixup-mountpoint that selects which (a/b) you are mounting | 20:33 |
| mal | because you manually device the actual partition matching the mount | 20:34 |
| osum4est | my problem is that my sim card is only detected for ~1/10 boots | 20:34 |
| mal | am I misunderstanding your problem completely? | 20:34 |
| mal | first I want to understand that mount issue | 20:34 |
| mal | because I see no problem | 20:35 |
| osum4est | i don't have a mount issue. i'm able to successfully mount the radio partition 100% of the time | 20:35 |
| osum4est | was 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 fine | 20:36 |
| mal | 23: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/modme | 20:36 |
| mal | then what was that | 20:36 |
| mal | am I missing something | 20:36 |
| mal | that looks like a problem to me | 20:37 |
| mal | osum4est: are all of the options really needed? | 20:37 |
| osum4est | by 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 |
| mal | yes | 20:37 |
| mal | we do not use fstab in sfos | 20:37 |
| mal | everything is done in systemd | 20:38 |
| osum4est | but doesnt systemd use the fstab? | 20:38 |
| mal | no | 20:38 |
| mal | looks at /lib/systemd/system/ and you see some .mount files there | 20:38 |
| mal | those are what define what is mounted | 20:39 |
| osum4est | but i have a firmware-radio.mount service that was generated by the fstab systemd generator | 20:39 |
| mal | so how does that looks like | 20:39 |
| mal | osum4est: that is created at build time | 20:39 |
| osum4est | just 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 contents | 20:40 |
| mal | that is not used in normal sfos like I said already | 20:40 |
| mal | at least it shouldn't have anything like modem partition mount | 20:41 |
| mal | firmware-radio.mount should be from build time, pastebin the file | 20:42 |
| osum4est | adding the modem to /etc/fstab cause /run/systemd/generator/local-fs.target.requires/firmware-radio.mount to be created. here's the file: https://pastebin.com/xAFZfuUG | 20:42 |
| osum4est | how do i get it to mount properly, since sfos doesnt use the fstab? | 20:42 |
| mal | I said those should have been created by build, not during runtime, so we need figure out why it was not created it it was missing | 20:43 |
| mal | adding or editing fstab is not the way | 20:43 |
| osum4est | got it. so the build process needs to make it's own firmware-radio.mount service? | 20:44 |
| mal | it should have made it unless something went wrong | 20:46 |
| osum4est | i'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 |
| mal | no need to reflash, check the rpms | 20:50 |
| mal | in droid-local-repo | 20:50 |
| mal | in some droid-hal rpm | 20:51 |
| mal | https://github.com/mer-hybris/droid-hal-device/blob/master/helpers/makefstab | 20:52 |
| mal | called from https://github.com/mer-hybris/droid-hal-device/blob/master/droid-hal-device.inc#L411 | 20:52 |
| osum4est | so it looks like that common.fstab that i linked is not included in FSTAB_FILES in the .inc file. o dpmt | 20:59 |
| osum4est | ... sorry didn't mean to send yet | 21:00 |
| osum4est | the 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 folders | 21:01 |
| osum4est | and just double checked. neither the rpm's or a new install of the zip contain mount files for mounting /firmware/radio | 21:07 |
| mal | osum4est: 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 ueventd | 21:56 |
| osum4est | don't see anything: https://pastebin.com/0cQmvPFf | 22:00 |
| osum4est | mal, 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 work | 22:12 |
| mal | osum4est: so maybe then copy the fstab.common to vendor/etc in out, similarly as you did for the ueventd.rc | 22:59 |
| mal | osum4est: in normal android build that is copied to fstab.marlin | 23:01 |
| osum4est | mal, alright, got that working. how do i integrate that into the build process though? becuase the out folder isn't on git. | 23:54 |
| r0kk3rz | it would be in the make files somewhere | 23:58 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!