06:12 <arno11> Wizzup: ok, ty. btw i pushed drnoksnes in extras (need to check jobs for it too)

10:03 <kiva> It was nice suprise that yellow update notfication blinked with Pinephone..it was jib and update works, but keeping finger on link and choosing open link to new window does not work.

10:05 <Wizzup> yes, I think I also reported this, I think dsc was not aware of the fact that qt auto adds a context menu

10:05 <Wizzup> so that needs to be hooked up still

10:11 <kiva> btw..is there any plans for next supported phones Pinephone Pro, Gemini PDA 4G, Cosmo Communicator, fxtech pro/prox1?

10:16 <dsc_> im working on adblock for jib

10:17 <kiva> I do not ask because that it should, to me is more important that one supported device is fully supported. That reminds me question has anybody tried compile fcam drivers from fremantle to Leste N900?

10:22 <Wizzup> kiva: we won't stop people from supporting other deivces, pinephone pro I would like to support soon. I do have a fxtec device but I don't know what mainline for it looks like

10:25 <kiva> ok

10:27 <Wizzup> If we want to support a lot more devices to a degree we could ggo the libhybris way (if that is still a thing) that many other projects did to support old kernels, but we haven't seriously explored it)

10:51 <kiva> ok, now I understand reason why some devices support Debian with kernel version 3 or 4, but not any newer kernel.

10:56 <Wizzup> right

10:59 <kiva> So text "support Debian Linux" on Gemini and Cosmo does not have real meaning in long run. So Pinephone Keyboard with Maemo Leste is the best linux phone with keyboard in summer 2024!

11:05 <Wizzup> pinephone pro might be better once we get there, it's a shame that folks who did get it to work didn't report back here.

11:05 <Wizzup> then we could have taken their work and put it in our future images

11:23 <kiva> Pinephone Pro might need lot of work with power management and overheating protection for modem...but I dont mind if OS reminds "take little break" :)

11:27 <kiva> Does Maemo Leste have overheating shutdown protection with Pinephone? I forget it in small bag and it run very hot.

15:21 <Wizzup> I will be moving the phoenix.maemo.org / leste.maemo.org and build servers in the next few days

15:22 <Wizzup> but I will be moving them from DSL to ... fiber 1Gbit/s :)

15:23 <branon_> gotta go fast

15:58 <Wizzup> well it'll be nice if I don't have to pay for a dedi

21:15 <Macario> Hello, I have just acquired a second d4 device, and while following the same steps as I did with the 1st one somehow I cannot get kexecboot to work. These are the logs of the steps: https://pastebin.com/Wm8gUtBr. I downloaded utags from the symlink in the repo's root (https://github.com/tmlind/droid4-kexecboot/blob/master/utags-mmcblk1p13.bin) and

21:15 <Macario> the latest kexecboot image (https://github.com/tmlind/droid4-kexecboot/blob/master/2023-12-26/droid4-kexecboot.img). Is there any know issue? Thanks!

21:15 <Macario> *known issue

21:17 <Macario> The device was already on the latest firmware and thus I didn't reflash android, just cleared cache and userdata. Currently the kexecboot menu does not show and it loads android directly (there is some flashing of the screen but nothing displays)

21:21 <Wizzup> I would reflash android just to be sure

21:22 <Wizzup> uvos: could you try to restore regs on 6.6 and see if that works for you?

21:23 <uvos> Wizzup: yes

21:23 <uvos> Wizzup: currently occupied with mr covid so later

21:24 <Wizzup> oops, sorry to hear, get well soon

21:28 <Macario> Wizzup: thank you. I will do so. Is it also necessary to "lock the utags and bpsw partitions later on after

21:28 <Macario> things are working again with:

21:28 <Macario> $ fastboot flash mbm mbm.bin' after flashing utags (from kexecboot installation guide)

21:28 <Macario> ?

21:29 <Macario> uvos: whising you a quick recovery

22:08 <Wizzup> mdz: I don't think you need to lock them

22:08 <Wizzup> oops, sorry, that was for Macario

22:17 <Macario> unfortunately even after reflashing android kexecboot is still missing. I will do some more investigation over the weekend and report back, should be able to mount the boot partitiion with adb shell and compare it with my working d4.

22:30 <Macario> oh gosh, I found out why. This is going to be one of the most embarrasing things ever: I was flashing a text file as utags. It turns out that when you download a symlink from github using the web ui, it does not download the symlinked file, but a text file with the name of the target.

22:31 <Macario> I was lucky I didn't brick the device for good

22:34 <uvos> i dont thing you can brick the device by falshing utags

22:34 <uvos> if mbm cant parse it it it should either ignore it or fail at which point mbm-backup will boot you into fastboot where you can simply erase utags

22:34 <Macario> luckily!

22:35 <uvos> the link must be some git + windows thing

22:35 <uvos> on linux it results in a correct symbolic link

22:36 <Macario> yes, it is a git + linux thing, I have seen it before but somehow I missed it today

22:37 <Macario> sorry, git + windows, it defintely works as intended in Linux

22:39 <Macario> ntfs supports symlinks, but I guess the windows implementation of git does not care to use them as it would need to special case for different filesystems

22:52 <Wizzup> the symlink problem I think is just one of github web ui

22:57 <Macario> In any case, sorry for the false alarm, I hope it had at least some comedy value