Friday, 2026-11-06

Mister_Magisteroh great torch doesn't work on 4 of my devices out of 700:51
Mister_Magisterbecause of the change to droidmedia-flashlight00:52
T42<damnbruh2004> hello hello, reminding all of you that im trying to port onto fortuna3g with a hybris 18.1 base01:12
T42<damnbruh2004> i am currently investigating a droid-hal-init failure01:12
T42<damnbruh2004> it turns out the device is running system-as-root and i edited fstab to mount into / instead of /system01:12
T42<damnbruh2004> droid-hal-init started giving signs of life, but i had to also create a symlink for /vendor -> /system/vendor01:12
T42<damnbruh2004> and a symlink from /apex into /system/apex01: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_Magistersystem as root simply means you have /system in that partition no? so you mount it as system_root like very other sane person01:15
Mister_Magisterdont' try to reinvent the wheel xd01:16
T42<damnbruh2004> i did this to the fstab. before that there was nothing besides data mounting in early init01:18
T42<damnbruh2004> https://github.com/fortuna-for-smoothie/android_device_samsung_msm8916-common/commit/505337a990947ded3fc79180defea64cef09cd3901:18
T42<damnbruh2004> this is so the hybris-hal scripts can create appropriate .mount files, as per hadk hot01:19
Mister_Magistermal: 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_Magisterso it is because it's not LVM setup01:33
Mister_Magisterand on g2/op6 there's no dm-0 because it doesn't have the dmsetup so Storage comes up at 0GB01:38
Mister_Magisterand 0GB available for same reason as miami01:38
Mister_Magisterfeels like jolla could give it bit more thought01:38
Mister_Magisterit won't work anywhere but official ports and ports with LVM01:39
Mister_Magisterfix for droidmedia-flashlight is supposed to be "update droidmedia dumbass"01:41
Mister_Magistermy droidmedia on g2 is from 2024 xddd01:41
Mister_Magisterah droidmedia-flashlight won't work on 5.1 android02:08
Mister_Magisterthe interface is just not there02:08
Mister_Magisteri wonder if i can fall back to the old one02:08
Mister_Magisternow why would patterns-sailfish-device-configuration-titan contain it02:09
Mister_MagisterCorrect 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 devices02:15
Mister_Magisterlet me repeat myself02:17
Mister_Magister[02:38] <Mister_Magister> feels like jolla could give it bit more thought02:17
Mister_Magisterlike at least provide old provider02:18
Mister_Magisterwait does that mean on mainline you can't have flashlight? epic!02:18
Mister_MagisterI won't repeat myself third time xd02:19
Mister_MagisterI'm not upset i'm just disappointed02:24

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