| Mister_Magister | oh great torch doesn't work on 4 of my devices out of 7 | 00:51 |
|---|---|---|
| Mister_Magister | because of the change to droidmedia-flashlight | 00:52 |
| T42 | <damnbruh2004> hello hello, reminding all of you that im trying to port onto fortuna3g with a hybris 18.1 base | 01:12 |
| T42 | <damnbruh2004> i am currently investigating a droid-hal-init failure | 01:12 |
| T42 | <damnbruh2004> it turns out the device is running system-as-root and i edited fstab to mount into / instead of /system | 01:12 |
| T42 | <damnbruh2004> droid-hal-init started giving signs of life, but i had to also create a symlink for /vendor -> /system/vendor | 01:12 |
| T42 | <damnbruh2004> and a symlink from /apex into /system/apex | 01:12 |
| T42 | <damnbruh2004> ~ # ls -l /system/bin/linker* | 01:12 |
| T42 | <damnbruh2004> lrwxr-xr-x 1 root shell 36 Jan 1 2009 */system/bin/linker* -> */apex/com.android.runtime/bin/linker* | 01:12 |
| T42 | <damnbruh2004> lrwxr-xr-x 1 root shell 36 Jan 1 2009 */system/bin/linker_asan* -> */apex/com.android.runtime/bin/linker* | 01:12 |
| T42 | <damnbruh2004> -rwxr-xr-x 1 root shell 694032 Jan 1 2009 */system/bin/linkerconfig* | 01:12 |
| T42 | <damnbruh2004> it then complained about boringssl self test failing and rebooting, so as irc logs suggested, if commented out reboot on failure defs in the rc files. and now it passes the boringssl checks but reboots with a message `bpfloader-failed` | 01:14 |
| Mister_Magister | system as root simply means you have /system in that partition no? so you mount it as system_root like very other sane person | 01:15 |
| Mister_Magister | dont' try to reinvent the wheel xd | 01:16 |
| T42 | <damnbruh2004> i did this to the fstab. before that there was nothing besides data mounting in early init | 01:18 |
| T42 | <damnbruh2004> https://github.com/fortuna-for-smoothie/android_device_samsung_msm8916-common/commit/505337a990947ded3fc79180defea64cef09cd39 | 01:18 |
| T42 | <damnbruh2004> this is so the hybris-hal scripts can create appropriate .mount files, as per hadk hot | 01:19 |
| Mister_Magister | mal: pages/about/components/MemInfoItem.qml adds up free space from two lists, PartitionModel.User and PartitionModel.System. miami has everything on one partition (/dev/sde26), and that gets classed as Mass (type 4), so it's in neither list. | 01:33 |
| Mister_Magister | so it is because it's not LVM setup | 01:33 |
| Mister_Magister | and on g2/op6 there's no dm-0 because it doesn't have the dmsetup so Storage comes up at 0GB | 01:38 |
| Mister_Magister | and 0GB available for same reason as miami | 01:38 |
| Mister_Magister | feels like jolla could give it bit more thought | 01:38 |
| Mister_Magister | it won't work anywhere but official ports and ports with LVM | 01:39 |
| Mister_Magister | fix for droidmedia-flashlight is supposed to be "update droidmedia dumbass" | 01:41 |
| Mister_Magister | my droidmedia on g2 is from 2024 xddd | 01:41 |
| Mister_Magister | ah droidmedia-flashlight won't work on 5.1 android | 02:08 |
| Mister_Magister | the interface is just not there | 02:08 |
| Mister_Magister | i wonder if i can fall back to the old one | 02:08 |
| Mister_Magister | now why would patterns-sailfish-device-configuration-titan contain it | 02:09 |
| Mister_Magister | Correct me if i'm wrong but droidmedia-flashlight is absolutely required and you cannot go back to sysfs way and on 5.2 flashlight is broken on at least 4 devices | 02:15 |
| Mister_Magister | let me repeat myself | 02:17 |
| Mister_Magister | [02:38] <Mister_Magister> feels like jolla could give it bit more thought | 02:17 |
| Mister_Magister | like at least provide old provider | 02:18 |
| Mister_Magister | wait does that mean on mainline you can't have flashlight? epic! | 02:18 |
| Mister_Magister | I won't repeat myself third time xd | 02:19 |
| Mister_Magister | I'm not upset i'm just disappointed | 02:24 |
| *** n2klb_ is now known as n2klb | 02:45 | |
| abr | The droidmedia flashlight implementation just provides a d-bus service implementing org.sailfish.flashlight.provider. You can write your own alternative doing that however you need to. It's more flexible than the old way, which was awful and needs to stay dead. | 05:43 |
| T42 | <elros34> @bruhforreal don't you have flattened apexes (don't make /apex symlink) error when droid-hal-ini-starts? | 09:30 |
| T42 | <damnbruh2004> Initially i have nothing in /apex and folders like com.android.* in /system/apex | 09:38 |
| T42 | <elros34> so what is output from droid-hal-init without symlink? | 09:51 |
| T42 | <damnbruh2004> First it complianed about missing selinux policies files in vendor. I crsted the /vendor -> /system_root/vendor symlink. Then it complained about boringssl test failing. I tried running the boringssl_self_test32 file manually and it complained about missing linker. I checked and turnns out /system/bin/linker (or smth like that) is linked to /apex/com.android.something/linker. /apex is empty so linked /apex -> /system/apex. Now boringssl | 09:57 |
| T42 | <damnbruh2004> And now i get further in init and it says somehting about the bpf loader failing | 09:58 |
| T42 | <code_bht> /apex | 10:00 |
| T42 | <damnbruh2004> Got em | 10:02 |
| T42 | <elros34> just show whole log if you can't find it | 10:02 |
| T42 | <elros34> but I bet its common non updatable apexes issue | 10:03 |
| T42 | <damnbruh2004> I'll send later today. Do I capture logs with / without the symlinks I already made? | 10:05 |
| T42 | <elros34> I think without /apex symlink it should be good but maybe I am wrong. I guess apex-bootstrap starts with error | 10:06 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!