Thursday, 2022-01-06

T42<Herrie1982> Does anyone know of a way to debug when the modem doesn't get provided via binder to oFono? I'm getting the following on Android side, but not really sure how to debug further. 01-05 20:50:55.576     0     0 E init    : Could not find service hosting interface android.hardware.radio@1.0::IRadio/slot107:44
T42<Herrie1982> I can see the files are available on the phone, so not sure what's the issue07:45
T42<TheVancedGamer> Maybe include that in your manifest.xml?07:45
T42<TheVancedGamer> Or build the impl07:45
T42<Herrie1982> Well they are it seems07:49
T42<Herrie1982> https://github.com/Tofee/android_device_lge_hammerhead/blob/halium-9.0/manifest.xml#L147-L16607:49
T42<Herrie1982> I added the required bits to device.mk as well, so they end up in the file system: https://github.com/Herrie82/android_device_lge_hammerhead/blob/halium-9.0/device.mk#L284-L29207:50
T42<Herrie1982> I've got android.hardware.radio@1.1.so, android.hardware.radio@1.0.so and android.hardware.radio.deprecated@1.0.so on the device07:51
T42<Herrie1982> So not really sure how to further debug this07:53
T42<foxclore> Hey, any ideas why 'rpm/dhd/helpers/build_packages.sh --droid-hal'09:18
T42<foxclore> just freezes doing nothing? Here is the build log after Ctrl + c (always freezes on +echo int): https://pastebin.com/dBDndneK09:18
T42<foxclore> After Ctrl + C it inputs this: https://pastebin.com/5Y81Ktgg09:18
T42<elros34> @foxclore grep for PARANOID in droid-hal-device.inc then you have echo and 2 x if checks, so your cat hang could be here probably: kernel_release=$(cat out/target/product/%{device}/*/*/include/config/kernel.release)11:27
T42<foxclore> @elros34 you mean this? : https://irc.thaodan.de/.imgstore/e983b241/file_3190.jpg12:11
T42<foxclore> also, in that line kernel_release line (843), had to modify to the following: https://gitlab.com/FishFactoryHQ/apollon/hybris/droid-hal-device/-/commit/3ecaff4d1d96dd3a29e02b912ace38116413feb912:12
T42<elros34> so you have the answer, your modification is wrong12:13
T42<foxclore> Hmm, but it was due to the previous issue (re @elros34: so you have the answ...)12:16
T42<foxclore> Here. (re @rodrisola: i solve with edit ht...)12:16
T42<elros34> so maybe it's time to make proper PR to fix these DTBO_OBJ issues?12:16
T42<elros34> I do not see */*/* in his workaround, just: kernel_release=$(cat out/target/product/%{device}/*/KERNEL_OBJ/include/config/kernel.release)12:18
T42<foxclore> hmm, still hangs on the same echo inet12:26
T42<elros34> so do you have that file  out/target/product/%{device}/obj/KERNEL_OBJ/include/config/kernel.release? it hang at cat previously12:28
T42<foxclore> that PARANOID thing points to correct place tho12:28
T42<foxclore> yep (re @elros34: so do you have that ...)12:28
T42<foxclore> https://irc.thaodan.de/.imgstore/85b7285a/file_3191.jpg12:29
T42<elros34> so obviously try to run that workaround cat command manually12:30
T42<foxclore> @elros34 which workaround command??12:31
T42<elros34> this one: https://irclogs.sailfishos.org/logs/%23sailfishos-porters/latest.log.html#t2022-01-06T12:18:0212:31
T42<foxclore> here is the output of that command, but when I put it in droid-hal-device.inc it still freezes on that echo inet (re @foxclore: )12:34
T42<elros34> so show everything again: changes, log because it did not freeze at echo previously12:42
T42<foxclore> @elros34 here you go: https://gitlab.com/FishFactoryHQ/apollon/droid/droid-hal-apollon/-/snippets/223135313:02
T42<elros34> so again change is wrong, how about you copy paste correct line13:07
T42<foxclore> @elros3413:17
T42<foxclore> My bad, corrected to: " kernel_release=$(cat out/target/product/%{device}/*/KERNEL_OBJ/include/config/kernel.release)"13:17
T42<foxclore> Still, freezes here: https://pastebin.com/a54c1B0E13:17
T42<elros34> so still same run: kernel_release=$(cat out/target/product/apollon/*/KERNEL_OBJ/include/config/kernel.release) to confirm this finish correctly13:22
T42<elros34> if yes then it's strange and you should put some debug echo to droid-hal-device.inc to figure out his13:23
T42<foxclore> funny, but changing to that line helped!13:31
T42<foxclore> Any ideas why?13:31
T42<elros34> I only changed %{device} to apollon so check whether %{device} really prints correct name13:32
T42<elros34> but it must be so I can assume you again did not copy paste correct line13:35
T42<foxclore> Hey uhm, so i successfully built .zip, but again, have troubles installing it, because when sideloading or installing via recovery error "updater process terminated with error 7" pops. On russian forum I was advised to use https://github.com/SailfishOS-sagit/hybris-installer16:47
T42<foxclore> Is that really good idea or something else should be fixed to install os ?16:47
T42<zinstack625> @foxclore I use (or better used) it with river. It seemed easy to hack and did the job. There’re still headaches with A/B devices though, like TWRP can’t guarantee proper system mounts between versions and let someone save your soul should you try to use system toybox from it17:59
T42<zinstack625> I did a dirty myself and am packaging statically linked custom made toybox with the installer archive, which is super uncanny but it works18:00
T42<zinstack625> BTW, am doing a hybris-17.1 again, there is firmware in both /vendor/firmware and /vendor/firmware_mnt/images, (maybe elsewhere too, nevermind) and drivers in kernel search for binaries in /lib/firmware, I guess I can bind-mount (or even symlink) one of the directories there, but since request_firmware in kernel expects mostly flat filesystem structure on that path, I’m pretty much missing every directory except one. Is there any better18:05
T42<zinstack625> E.G. adreno calls to request_firmware for a530_pm4.fw and a506_zap.mdt, and those lay in aforementioned /vendor/firmware and /vendor/firmware_mnt/image respectively. There are much more, but that’s the point18:08
T42<zinstack625> Sry for long texts irc folk18:09
T42<zinstack625> Also, strange, because on hybris-16 it kinda just worked given the vendor mounts structure was restored18:10
T42<foxclore> whats river? (re @zinstack625: @foxclore I use (or ...)18:10
T42<zinstack625> @foxclore codename for motorola moto g718:10
T42<foxclore> oh okay sorry xd18:11
T42<foxclore> anyone got to boot on hybris-18.1?18:11
T42<zinstack625> I saw our lord and saviour mal describing it being unfinished, so better wait18:12
T42<foxclore> very unfortunately, my device has only lineage-18.1 available18:13
T42<foxclore> so am kind of18:13
T42<foxclore> https://irc.thaodan.de/.imgstore/394cdc09/file_3193.jpg18:13
T42<TheVancedGamer> Suffering from success18:14
T42<TheVancedGamer> The pic didn't even load and I can already tell18:14
T42<zinstack625> But it you’re really curious, I tried it with river yesterday and literally everything was broken, not even droid side going anywhere18:14
T42<Mister_Magister> port lineage17 then (re @foxclore: very unfortunately, ...)18:14
T42<Mister_Magister> shouldn't be too hard18:14
T42<foxclore> yee (re @TheVancedGamer: Suffering from succe...)18:14
T42<foxclore> mmm (re @Mister_Magister: port lineage17 then)18:14
T42<TheVancedGamer> Meticulous, my friend and a Huawei dev ported android KitKat to a phone launched with marshmallow/nougat18:15
T42<foxclore> mhm18:15
T42<foxclore> so you are saying that hybris-18.1 is so broken I better port lineage 17.1 to my device and then build hybris-17.1?18:16
T42<TheVancedGamer> What was your device launched with?18:16
T42<TheVancedGamer> Android 10 or 11?18:16
T42<foxclore> well I have apollo, afaik it was on android 1018:17
T42<foxclore> but people who built lineage 17 vanished with sources leaving me with pre-built kernel18:17
T42<TheVancedGamer> Apollo is?18:17
T42<TheVancedGamer> It's a xiaomeme for certain18:17
T42<foxclore> yeeee18:18
T42<foxclore> xiaomeme Mi  10T18:18
T42<TheVancedGamer> Ah18:19
T42<TheVancedGamer> downgrading android 11 trees is fairly easy18:19
T42<foxclore> if you have any worth reading guides pm please18:20
T42<TheVancedGamer> you pm me18:21
T42<TheVancedGamer> I won't18:21
malthere is just one bug in 18.1 which causes boot issues18:27
malI have booted my device to UI but it needs a manual hack on every boot to get it working properly18:28
T42<zinstack625> Where from should droid-load-firmware.sh be launched from again?19:00
T42<TheVancedGamer> Uh oops19:00
T42<TheVancedGamer> I did not consider that19:01
T42<zinstack625> Where from should droid-load-firmware . sh be launched from again?19:01
T42<zinstack625> Well, tg considers it a link, so be it19:01
T42<zinstack625> Also, how are we supposed to use pastebin then?19:04
T42<TheVancedGamer> This person linked github (re @foxclore: Hey uhm, so i succes...)19:05
T42<TheVancedGamer> ah I know19:05
T42<TheVancedGamer> It only deletes forwarded messages and links if the user joined <24h ago19:05
T42<zinstack625> Oh, smart19:07
T42<fakelog> phone19:07
T42<elros34> @zinstack625  udev triggers it. Make sure you have all these CONFIG_FW_LOADER* enabled19:07
T42<zinstack625> But then a lot of bots actually sit like half a year in a channel and then start acting19:08
T42<zinstack625> @elros34 yeah, just remembered. For some reason it was disabled in kernel, but I can’t recall why..19:08
T42<elros34> maybe because you have followed mer-kernel-check19:09
T42<TheVancedGamer> @zinstack625 we've never had a bot sit for half a year19:09
T42<TheVancedGamer> I usually skim through the user list and ban sketchy people and bots19:09
T42<TheVancedGamer> And sometimes I come across bots that I've seen and know are bots before19:09
T42<zinstack625> Cool moderating =^319:10

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