@Linus67 said: add separators or spacing between apps in the drawer I believe such a thing may be in the works!

@hunter_tor That sounds like you installed it? Good news! By the way, please use the attachment button to upload images. And resize them a bit before uploading. Thanks!

@projectmoon HEY! I run my own gitea server too! I host all my public repos on github tho. more eyeballs. I'm actually writing my own git system called giteam basically a google docs like version control with git on top. about ready to start testing. thanks for the link ill check it out.

@gpatel-fr would not upgrade it. Just test notifications. It is indeed 16.04 and turns on. Haven't tested yet though.

@Zer0 I would assume so, yes.

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

readyblue said: (edit) after restart wi-fi start to work normally (both normal wi-fi and the hidden one) default browser still stuck in the loading after restart Bluetooth keyboard connects

@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.

@Linus67 said: I've found the cause of the increased battery drain on Wi-Fi. Clear the list of saved Wi-Fi connections: Go to Wi-Fi -> Wi-Fi Settings -> Saved Networks and tap “Forget” next to all the networks. Then reconnect to your home Wi-Fi network. After that, battery drain in standby mode will return to a minimum of < 2% per hour. Did that and it seems to work. Battery drain is in normal levels again. Weird quirk, though...

@MrT10001 Getting stock Android 11 onto the Lenovo Tab was a real challenge yesterday. Problems: SPflashtool failed due to chip permissions. Attempts using MTK bypass tools also failed How it filaly worked (after ~3 houres) Download Lenovo Software Fix Tool (thanks for the tip) Create a Lenovo account (using a disposable email address) Start the recovery workaround (but you can only flash up to Android 10 !!!!) OK, perform a recovery with Android 10 The recovery tool downloads the ROM (A 11) to your PC Before starting the recovery, you must replace the downloaded Android 10 files with the Android 11 files witch you downloaded from the UBports link bevor. Then start the recovery process and the Lenovo Software Fix Tool will flash the tablet with Android 11, which you’ve placed in its nest, just like a cuckoo’s egg. Translated with DeepL.com (free version)