Tuesday, 2023-05-02

T42<FakeShell> i have reinstalled sailfish on my lavender and it worked fine03:00
T42<FakeShell> all you have to do is mask bluebinder and usb-moded and it should boot fine03:00
T42<FakeShell> i just setup my system and connected to the internet it works without any issues (re @Mister_Magister: ill leave it to you ...)03:00
T42<FakeShell> after flashing03:02
T42<FakeShell> `chroot /data/.stowaways/sailfishos/ /bin/bash -c "export PATH=/bin:/sbin:/usr/bin:/usr/sbin && systemctl mask bluebinder && systemctl mask usb-moded"`03:02
T42<FakeShell> also the getprop reports the firmware as03:06
T42<FakeShell> lavender-user 9 PKQ1.180904.001 V10.3.6.0.PFGMIXM release-keys03:06
T42<FakeShell> so i guess sailfish is much more picky compared to droidian manjaro and alpine03:06
T42<FakeShell> try downgrading to that firmware before installing03:06
T42<FakeShell> report back if you were successful so that i can add it to the docs03:07
rinigus@bouic: If it's official one, it should be set to your pin. As you haven't set pin then no idea what it would be04:10
rinigusPlease share dual boot setup, would be interesting to look at it04:10
T42<Mister_Magister> Weird (re @FakeShell: i have reinstalled s...)07:12
T42<bouic> That's the plan yes, just trying to sort it out first and then I will try to find the motivation to write a summary (re @SailfishFreenodeIRCBridgeBot: <rinigus>Please shar...)07:33
T42<bouic> And yeah I didn't set a pin code. What happened is, upon booting into SFOS the first time, I was prompted to select the language, then accept the user agreement, and then immediately afterwards there was a screen saying "Encrypting user data" with the spinning animation, without asking for a password first, and then I just got a blackscreen.07:36
T42<bouic> 07:36
T42<bouic> I can still boot into Droidian after switching slots.07:36
T42<bouic> 07:36
T42<bouic> On next boots on SFOS, I am just stuck on the Android logo ("F(x)tec Pro1, Powered by Android"). Surprisingly, when I forced rebooted into bootloader from that state, I could see the unlock keypad (the one on the black background). I could not reproduce this though.07:36
*** rdr_ is now known as rdr10:06
rinigusThat's piggz port. I wonder whether official or community encryption used there12:22
piggzits official on that device, already discussed :)12:24
T42<bouic> And yeah I didn't set a pin code. What happened is, upon booting into SFOS the first time, I was prompted to select the language, then accept the user agreement, and then immediately afterwards there was a screen saying "Encrypting user data" with the spinning animation, without asking for a password first, and then I just got a blackscreen.12:53
T42<bouic> 12:53
T42<bouic> I can still boot into Droidian after switching slots.12:53
T42<bouic> 12:53
T42<bouic> On next boots on SFOS, I am just stuck on the Android logo ("F(x)tec Pro1, Powered by Android"). Surprisingly, when I forced rebooted into bootloader from that state, I could see the unlock keypad (the one on the black background) briefly. I could not reproduce this though. (edited)12:53
T42<bouic> Is there any way to disable encryption? Eugenio mentioned a file in /var/lib to remove (if I can mount the img before flashing it).14:57
T42<bouic> I'd rather keep encryption on both OSes, but this could be a step forward anyway.14:57
T42<adampigg> @bouic how do you install both OS? sailfish overwrites the entire userdata with lvm partitions, wondering where droidian is20:31
T42<bouic> See that @adampigg (with some changes after we tried it yesterday, and still that SFOS encryption issue that needs to be figured out).20:48
T42<bouic> Forwarded from unknown: 1) flash droidian using the fastboot-flashable images20:48
T42<bouic> 2) enable encryption if you want20:48
T42<bouic> 3) boot droidian recovery20:48
T42<bouic> 4) add the two android system partitions to the VG if you want a couple of GB more of space (useful for the sailfish's root partition)20:48
T42<bouic> 5) resize the droidian rootfs partition LV+partition20:48
T42<bouic> 6) create sailfish-root and sailfish-home partitions (on top of my mind, I don't remember if they're called that way)20:48
T42<bouic> 7) reboot to droidian20:48
T42<bouic> 8) download sailfish image, unsparse the userdata image, loopmount it, dd the root and home partitions to their respective lvm LVs20:48
T42<bouic> 9) resize the new sailfish-root and sailfish-home20:49
T42<bouic> 10) Rename the droidian vg to `sailfish`20:49
T42<bouic> 11) Change the flash-bootimage configuration to avoid switching slots on kernel upgrades, and to always install the kernel to the same slotted partition20:49
T42<bouic> 12) flash the sailfish bootimage to the other slot20:49
T42<bouic> 20:49
T42<bouic> should work, you can then switch with `sudo bootctl set-active-boot-slot 0` (or 1 depending on the slot you want), I don't know if bootctl is shipped in the sfos' android system, I think so though as they should have a way to mark the boot as successful20:49
T42<bouic> Forwarded from unknown: 1) flash droidian using the fastboot-flashable images20:49
T42<bouic> 2) enable encryption if you want20:49
T42<bouic> 3) boot droidian recovery20:49
T42<bouic> 4) add the two android system partitions to the VG if you want a couple of GB more of space (useful for the sailfish's root partition)20:49
T42<bouic> 5) resize the droidian rootfs partition LV+partition20:49
T42<bouic> 6) create sailfish-root and sailfish-home partitions (on top of my mind, I don't remember if they're called that way)20:49
T42<bouic> 7) reboot to droidian20:49
T42<bouic> 8) download sailfish image, unsparse the userdata image, loopmount it, dd the root and home partitions to their respective lvm LVs20:49
T42<bouic> 9) resize the new sailfish-root and sailfish-home20:49
T42<bouic> 10) Rename the droidian vg to `sailfish`20:49
T42<bouic> 11) Change the flash-bootimage configuration to avoid switching slots on kernel upgrades, and to always install the kernel to the same slotted partition20:49
T42<bouic> 12) flash the sailfish bootimage to the other slot20:49
T42<bouic> 20:49
T42<bouic> should work, you can then switch with `sudo bootctl set-active-boot-slot 0` (or 1 depending on the slot you want), I don't know if bootctl is shipped in the sfos' android system, I think so though as they should have a way to mark the boot as successful20:49
T42<bouic> Hum, I cannot forward messages here apparently. Wait.20:49
T42<bouic> From Eugenio/g7:20:51
T42<bouic> 20:51
T42<bouic> 1) flash droidian using the fastboot-flashable images20:51
T42<bouic> 2) enable encryption if you want20:51
T42<bouic> 3) boot droidian recovery20:51
T42<bouic> 4) add the two android system partitions to the VG if you want a couple of GB more of space (useful for the sailfish's root partition)20:51
T42<bouic> 5) resize the droidian rootfs partition LV+partition20:51
T42<bouic> 6) create sailfish-root and sailfish-home partitions (on top of my mind, I don't remember if they're called that way)20:51
T42<bouic> 7) reboot to droidian20:51
T42<bouic> 8) download sailfish image, unsparse the userdata image, loopmount it, dd the root and home partitions to their respective lvm LVs20:51
T42<bouic> 9) resize the new sailfish-root and sailfish-home20:51
T42<bouic> 10) Rename the droidian vg to `sailfish20:51
T42<bouic> `11) Change the flash-bootimage configuration to avoid switching slots on kernel upgrades, and to always install the kernel to the same slotted partition20:51
T42<bouic> 12) flash the sailfish bootimage to the other slot20:51
T42<bouic> 20:51
T42<bouic> should work, you can then switch with `sudo bootctl set-active-boot-slot 0` (or 1 depending on the slot you want), I don't know if bootctl is shipped in the sfos' android system, I think so though as they should have a way to mark the boot as successful20:51
T42<adampigg> @bouic and have you ever tried just flashing sailfish without droidian to confirm if the image works?20:56
T42<bouic> Nope, not yet. You are right, maybe that would be worth a shot before spending too much time on that. Problem is I kind of started setting up Droidin in bed last night ._.20:57
T42<bouic> Nope, not yet. You are right, maybe that would be worth a shot before spending too much time on that. Problem is I kind of started setting up Droidian in bed last night ._. (edited)20:57
T42<bouic> I cn try another image first, will search in the history in this channel if someone asked guidance to flash one and reported success.20:58
T42<bouic> I can try another image first, will search in the history in this channel if someone asked guidance to flash one and reported success. (edited)20:58
T42<bouic> I can try another image first, will search in the history in this channel if someone asked for guidance to flash one and reported success. (edited)20:58
T42<adampigg> id like to know the state of the latest, without "customisations" ;)20:59
T42<leha155> After this patch RIL working! And i have /linkerconfig/ld.config.txt (No any subfloader) . But GUI do not start( (re @elros34: @leha155 have you tr...)22:41
T42<bouic> The image seems to work Adam. I do get this "Encrypting user data" screen *before* typing a keycode, but then I'm prompted for a keycode instead of staying on a black screen. (re @adampigg: id like to know the ...)22:42
T42<leha155> / # EGL_PLATFORM=hwcomposer test_hwcomposer22:43
T42<leha155> library "libbinder.so" not found22:43
T42<leha155> test_hwcomposer: test_common.cpp:370: HWComposer* create_hwcomposer_window(): Assertion `err == 0' failed.22:43
T42<leha155> Aborted (core dumped) (edited) (re @elros34: @leha155 have you tr...)22:43
T42<bouic> Just did a clean flash @adampigg. The image seems to work. I do get this "Encrypting user data" screen *before* typing a keycode, but then I'm prompted for a keycode instead of staying on a black screen. (edited) (re @adampigg: id like to know the ...)22:43
T42<leha155> After this patch RIL working! And i have /linkerconfig/ld.config.txt But GUI do not start(22:45
T42<leha155> / # EGL_PLATFORM=hwcomposer test_hwcomposer22:45
T42<leha155> library "libbinder.so" not found22:45
T42<leha155> test_hwcomposer: test_common.cpp:370: HWComposer* create_hwcomposer_window(): Assertion `err == 0' failed.22:45
T42<leha155> Aborted (core dumped) (edited) (re @elros34: @leha155 have you tr...)22:45
T42<bouic> Just did a clean flash @adampigg. The image seems to work perfectly. I do get this "Encrypting user data" screen *before* typing a keycode, but then I'm prompted for a keycode instead of staying on a black screen. (edited) (re @adampigg: id like to know the ...)22:45
T42<elros34> @leha155 gui worked before applying that patch? Use minimer instead test_hwcomposer22:51
T42<elros34> can you answer also the question about /linkerconfig/bootstrap -> /linkerconfig, did you had it or disabled somehow?22:52
T42<leha155> Gui worked before patch. Now i have only one file in /linkerconfig, no any subfloader22:57
T42<elros34> but did you had mount unit  before, you should22:58
T42<elros34> what you have in /usr/lib/systemd/system/*.mount?23:00
T42<leha155> Yes i have linkerconfig.mount23:02
T42<elros34> so it worked before or not? Do you see it journal?23:04
T42<elros34> about hwcomposer: do you see some new errors in logcat/journal?23:07
T42<leha155> I dont see, but i think that it worked before last patch, because i have two subfloader in /linkerconfig23:11
T42<leha155> /linkerconfig/bootstrap23:11
T42<leha155> /linkerconfig/default23:11
T42<leha155> Now only23:11
T42<leha155> / # ls /linkerconfig23:11
T42<leha155> ld.config.txt23:12
T42<leha155> / #23:12
T42<leha155> Yes i see new errors:23:15
T42<leha155> "03-14 19:23:31.433 26699 26699 I ServiceManager: Waiting for service 'display.qservice' on '/dev/vndbinder'...23:15
T42<leha155> 03-14 19:23:31.469 26643 26643 W ServiceManager: Service display.qservice didn't start. Returning NULL23:15
T42<leha155> 03-14 19:23:31.469 26643 26643 E SDM     : HWCSession::Init: Failed to acquire display.qservice23:15
T42<leha155> 03-14 19:23:31.469 26643 26643 D RefBase : RefBase: Explicit destruction, weak count = 0 (in 0x7d09bca278)23:15
T42<leha155> 03-14 19:23:31.469 26643 26643 W RefBase : CallStack::getCurrentInternal not linked, returning null23:15
T42<leha155> 03-14 19:23:31.469 26643 26643 W RefBase : CallStack::logStackInternal not linked23:15
T42<leha155> 03-14 19:23:31.469 26643 26643 E android.hardware.graphics.composer@2.3-service: failed to open hwcomposer device: Invalid argument23:15
T42<leha155> 03-14 19:23:31.528 26781 26781 I chatty  : uid=1000(system) /vendor/bin/mm-pp-dpps expire 4 lines23:15
T42<leha155> 03-14 19:23:31.532  3410 26784 I chatty  : uid=1000(system) hwservicemanage expire 1 line23:15
T42<leha155> 03-14 19:23:31.532  3410 26786 I chatty  : uid=1000(system) hwservicemanage expire 1 line"23:15
T42<elros34> clearly something didn't or your /linkerconfig/bootstrap/* was empty23:16
T42<elros34> can you show whole logcat after reboot? I wonder how gui worked previosly without /linkerconfig/ld.config.txt23:31

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