Thursday, 2023-05-04

rinigus@bouic: thank you for documenting it!04:11
piggzanyone know how to override DEFAULT_RNDIS_CTRL_ETHADDR in usb_moded? it defauls to ethaddr at but doesnt look like its configurable08:33
malpiggz: what would that be on your device?09:58
malif you need to configure it then it shouldn't be too difficult09:59
piggzmal: im just not sure what the config option is10:03
piggzdevice has dev_addr and host_addr files10:03
T42<bouic> That is the least I can do as a noob crash-tester for g7's ideas! Now I really hope I can fix the issues listed at the top of the guide. Re-enabling encryption in both OSes would really be best, and fixing WLAN in Sailfish is a must. (re @SailfishFreenodeIRCBridgeBot: <rinigus>@bouic: tha...)11:59
T42<adampigg> @bouic and wlan worked in a "regular" flash ?12:00
T42<bouic> I can't be 100% positive because what I wanted to test when you asked me to flash it without customization, was encryption and that black screen issue12:01
T42<bouic> However I'm almost certain I could connect to my home WiFi at the initial start up config, yes.12:01
T42<bouic> However I'm almost certain I could connect to my home WiFi at the initial start up configuration, yes. (edited)12:02
T42<bouic> I might go back and reflash it alone to test that when I have some time @adampigg12:02
T42<bouic> Well, interesting. I reflashed stock Android to start clean, which prompted me to reset the device, I did so and it rebooted in Android just fine.17:19
T42<bouic> 17:19
T42<bouic> From there, reboot to bootloader, flash SFOS, and now I'm in a boot loop. Same SFOS image as before. This is new. (re @adampigg: @bouic and wlan work...)17:19
T42<adampigg> did you flash the correct android version?17:35
T42<edp_17> Have you reformatted /data? If you boot into android that tends to encrypt and format is necessary.18:54
T42<edp_17> Also, format can remove some old sfos residue too.18:55
T42<bouic> As discussed in the other channel, but stating it here for others, this was all due `fastboot set_active b` persisting after a stock reflash, while I thought it would not. (re @adampigg: did you flash the co...)19:10
T42<bouic> The boot loop issue was unrelated. However, now that you say that, I did try `fastboot format:ext4 userdata` before flashing Droidian when I was this issue whereby the Droidian encryption passphrase would stop working after resizing the Volume Group (hence breaking the OS), and this didn't help. (re @edp_17: Have you reformatted...)19:14
T42<bouic> What seems to have helped is flashing stock Android and *not* enabling any encryption or any form of locking, like answering "Not now" when prompted to set a key or pin code at the initial start up on first boot.19:14
T42<bouic> So maybe those methods are not 100% overlapping?19:15
T42<b100dian> does official encryption work on non-lvm ports?20:00
T42<adampigg> no20:12
T42<bouic> What tools do we have to investigate non-working wlan on a port? I have no internet connection on the phone, and nor `ip` nor `ifconfig` are available.20:13
T42<bouic> I'll try putting my SIM card in it maybe20:13
T42<adampigg> connmanctl ... but you need network to install it20:15
T42<bouic> The SIM slots are detected, so there's hope my SIM card can help. Brb.20:17
T42<b100dian> @adampigg just tried it. At least it doesn't lose it, just says "cannot"20:20
T42<bouic> Well nope. The SIM is detected, but no WLAN, no Modem (can't select the network in the Settings/Cellular Network menu), and most apps (but Settings, Terminal, Tutorial and Jolla store) fail to open due to "The name org.sailfishos.sailjaild1 was not provided by any .service files". (re @bouic: The SIM slots are de...)21:51
T42<bouic> Do we have an equivalent to android_bootctl in Sailfish? I'd love to be able to switch slot without a computer since there's now an OS on each slot.21:52
T42<bouic> sailjaild1 might not actually be the cause of apps failing to open, since journalctl shows similar logs for those few apps that do open.21:53
T42<elros34> don't you have already bootctrl in /usr/libexec/droid-hybris/system/bin/?21:56
T42<edp_17> Have you tried run apps from terminal?21:56
T42<elros34> you should start with getting full journal after reboot, apps/wlan do not work then for sure something must fail at boot time22:01
T42<bouic> Running them from CLI works indeed (re @edp_17: Have you tried run a...)22:02
T42<bouic> Even the camera works22:03
T42<bouic> Indeed it's there, but since it is not in $PATH, I couldn't find the binary (re @elros34: don't you have alrea...)22:04
T42<bouic> However it gives me "Error setting active boot slot: Operation not permitted" even with devel-su, devel-su -p, or when already as root. (re @elros34: don't you have alrea...)22:06
T42<bouic> `set-active-boot-slot` simply doesn't seem to be a supported command, as opposed to android_bootctl in Droidian22:06
T42<bouic> Hum. yes it should22:07
T42<elros34> then try android one, there should be one in /system or somewhere22:07
T42<bouic> No I was wrong, this is a supported option, it just says "NOPE" when I try22:09
T42<FakeShell> Hi have you had a chance to test the things i mentioned yet? (re @Mister_Magister: Weird)22:09
T42<Mister_Magister> nope22:09
T42<Mister_Magister> @MattRoot get on it22:10
T42<FakeShell> Thanks22:10
T42<bouic> Does that include boot logs? (re @elros34: you should start wit...)22:17
T42<elros34> not really but there is something: Timed out waiting for device dev-disk-by\x2duuid-8b776eab\x2dffc0\x2d46ed\x2d8a7f\x2dfb082c9763aa.device. and then Dependency failed for /home.22:21
T42<elros34> phone waits 20s for some device then home, connman, sailjail fails. You need to figure out that ^22:27
T42<bouic> Thanks Elros!22:35

Generated by 2.17.1 by Marius Gedminas - find it at!