@gpatel-fr Oh, noooo, not at all, I'm not that deep or intense I just don't trust myself. I am quite tired and confused these days. I mean I tested it with Dekko, I tested with bubbles and with notifications but maybe I missed something. Who knows?... That is why I would feel better if someone else would confirm it for 16.04 - so that it would not be my experience only.

@Zer0 Nice iniciative, to me there is some nice ideas in your effort, will try in a spare phone in the near future. Its always good to have options, design choices should evolve and enable users to use their device as they wish. I would suggest having your work as an unconfined click app, so you can reach more users. There are other launchers and apps that modify Lomiri so should be doable. Thanks for your work

Maybe check out the core apps. They're probably the most organized UT app repos. Maybe check Dekko too, I believe it also has or had a snap package.

@mariogrip i was able to install 26.04-1.x daily in POCO X3(surya) ,Redmi note 9 pro(curtana) through switching channel through adb shell and using adb shell.but now it is supported and unable to install.Also i have installed in Redmi note 9 (merlin) version 28,29 and updated to version 30.Now I have stopped updating through switching channel and installer. It is still running in 26.04-1.x daily.Why this devices were disabled ?

Confirming. Before the update, these things worked fine. Is there a way to roll back?

For info, just installed it on OP3... Made sure the device was on Oxygen OS 9.0.6. unlocked the bootloader Booted to fastboot - then booted TWRP 3.7.0_9 Formatted DATA Wiped Cache, Dalvik/Cache, Storage and System Rebooted to Bootloader (fastboot mode) Used Installer 0.11.2 to test and started the install - device got picked up, no need to select Left "wipe data" unticked Followed instructions and UT installed as expected (Xenial).

Looks like this is probably the fix? https://github.com/mer-hybris/ofono-binder-plugin/pull/53

@Linus67 Take a look here, maybe you can share your thoughts. https://forums.ubports.com/topic/12319/release-homespike-v1.0-a-real-home-screen-for-ubuntu-touch-multi-page-dock-drag-to-reorder-three-placement-modes-true-multitasking

I had to install back a second time Android on my Fairphone 4, this time I've took some notes shared below. TLDR: LineageOS developer options pane allows you to enable Rooted debugging. This allows you to use the adb root command which start a rooted debugging session. Then you can use adb shell to open a console on the device and run restorecon -FR /mnt/vendor/persist to restore the SELinux permissions. From Ubuntu Touch, the easiest way to go to the fastboot mode, is to open the terminal application and run: sudo reboot -f bootloader Then, I used the Android 11 factory reset image provided by Fairphone (but don't do like me, see below). Then, I wanted to install LineageOS and they require to have Android 13/15. So, I opened Android 11, go to phone information in the settings application, repeatedly touch the build number until the developer mode is enabled. Go, to the system panel in the settings application, open the developer mode and enable the ADB debugging. On my computer, I go back to the fastboot mode with: adb reboot bootloader I've installed Android 13 factory reset image provided by Fairphone as I already have downloaded it for another experiment. Then I boot Android 13 and enabled usb debugging with same steps than Android 11 (see above). Then I've followed LineageOS instructions to install it step by step: https://wiki.lineageos.org/devices/FP4/install/ Then, with LineageOS, you can enable developer options with same procedure. The LineageOS developer options have two options: USB debugging and Rooted debugging, you need the last one to be able to run commands to reset correctly permissions on the hardware drivers. Then, on my computer I was able to run, adb root to start rooted debugging, open a shell on the phone with adb shell and run in this shell restorecon -FR /mnt/vendor/persist: $ adb root restarting adbd as root $ adb shell FP4:/ # restorecon -FR /mnt/vendor/persist SELinux: Loaded file context from: /system/etc/selinux/plat_file_contexts /system_ext/etc/selinux/system_ext_file_contexts /product/etc/selinux/product_file_contexts /vendor/etc/selinux/vendor_file_contexts /odm/etc/selinux/odm_file_contexts FP4:/ # Then you need to reboot and you can check this worked by enabling the automatic rotation feature: open an application and rotate your phone, the application should follow the movement

@domubpkm The app itself would be doable but the packages aren't doable since they ust replace system files so translations can't be processed. I mean it's doable but it'll take for someone to modify each file manually and create separate packages per language

I made just this, and its an actual home screen. Not an app. https://forums.ubports.com/topic/12319/release-homespike-v1.0-a-real-home-screen-for-ubuntu-touch-multi-page-dock-drag-to-reorder-three-placement-modes-true-multitasking

@gpatel-fr Weirdly that does work somewhat, but the process seems to be rather convoluted. Rebooting to the bootloader/fastboot from the adb shell allows the installer to detect the device, but while installing it eventually reboots to recovery and shows a 'failed installation message (error 256)', and then it auto-reboots into the 'System Updater' screen you'd expect from an OTA update. So something about the installer 'unblocked' my previous update attempts (?).

@MrT10001 I reran the installer three times. It didn't work. So the third time I used this guide. And it worked! You're awesome man! Thanks!

@DJac Both of these issues only started occurring for me after upgrading to version 24.04-1. But I'm sure the developers will find a solution. Otherwise, I’m satisfied with UT on my Xperia. The only long-standing bug that hasn’t been—or can’t be—fixed is the streak in the main camera’s image when you zoom in too much. It isn’t visible in the photos in the gallery, but you can see it in the video. But as mentioned, this bug has been known for a long time.

@fischer.poco said: zBsp.: Xiaomi Poco X3 NFC / X3 da fehlt im Netz dann das "/ X3" Damit wird gemeint: Xiaomi Poco X3 NFC oder Xiaomi Poco X3. Oneplus Nord n10 5g ist aber eine gute Wahl!

@rocket2nfinity if someone can donate the hardware I am willing to give it a go.

Your BE2015 install path was useful prior art for cracking the BE2012 (T-Mobile US, not Metro) variant — same chipset, slightly different blockers. Sharing in the spirit of reciprocity. Full BE2012 installer up at https://github.com/dcherrera/n100-be2012-crossflash. macOS-native EDL flash (no MSMDownloadTool needed), plus a small binary patch to /usr/sbin/ofonod that fixes a SIM-init blocker which leaves Modem.Features stuck at ['sim'] on first boot — same modem firmware family, may be relevant to BE2015 users on certain SIMs too. README has the offset table if anyone wants to verify against their build. Also confirms your "T-Mobile SIM works, Verizon SIM doesn't" observation on the BE82CB modem firmware — same outcome on our end, since the modem firmware is T-Mobile-band tuned.

I successfully flashed ubuntu touch on it. I bought this model not knowing it wouldn't work. So I spent a few day putting together a work around because honestly it just sounded like a fun challenge. You can look through my findings here. https://github.com/dcherrera/n100-be2012-crossflash. Just a heads up, you should be able to clone this and claude code should be able to orient itself and help you get it done. i tried very hard to make sure the documentation was complete.