Ok, second time is the charm
I switched USB cable (it was probably bad), ordered wiping user data and used 24.04-stable for flashing...

Flashing worked the second time and now I'm on UT on my FP5

So... Bought myself a new shiny FP5

1. I unlocked the boot loader with FP code
2. I downgraded the Android to v13 as I was instructed via UBPorts Installer
   Yes, Android 13 booted successfully
3. Flashed the Ubuntu 24.04-daily
4. Device is refusing to boot UT

Hello fellow Ubuntistas,
I'm thinking about migrating myself to a "proper" UT device for a change,,,,,

...and I have some questions reg. FP5:

• Does it need to be unlocked in any way?
• What Android is required to be flashed in order to work properly with UT ?
  • Are there any specific Android images? Where to get those?
• Can this device be re-flashed between Adnroid and UT without a hassle? (I plan to use the device for both OSes kindof interchangeably...)
• Are there any caveats for using UT on FP5 as a daily driver? (I saw bad photo quality on some devices, hanging camera/ media recording/media playback, troubles with WiFi hotspots not working, ring tones disappearing after a period of time without reboots, etc etc...)

Thanks a lot for your comments

This applies for my Miatoll device (Redmi Note 9 Pro):

• Sometimes it takes minutes (sometimes up to 10min) for the mobile to re-connect the mobile data again after a phone call. [New after migration to 24.04]
• The keyboard sometimes still crashes when typing quickly. [New after migration to 24.04]
• Ringing sound gets "almost muted" (not hearable when receiving a call) after some time (usually around a week and several received calls) [This was always there]
• Camera app basically never initiates correctly on first time use after reboot [This was always there]
• Audio apps (all of them, i.e. sound Recording app) stop working/start freezing after the first phone call (sound subsystem config is messed-up?) [This was always there]

Hmmm... Not sure if this is related or different bug, but I bought new BT headset last week (Xiaomi Redmi Buds 6) and I can crash Lomiri while paring the headset to the phone with approx 50/50 chance

Notes:

• The isue was present before current OTA7 RC update
• This is on Xiaomi Redmi Note 9 with update from RC 2024-W47

Can anybody please point out, where to create a bug report for Xiaomi X3 POCO NFC? Or where I can check open bug reports?

Thanks.

@MrT10001 said in sdm845: Device not supported:

B ) Make sure the correct version of Android is installed

Hmmmmm This might not be fulfilled currently (I do have installed PostmarketOS on the phone).

Can I please ask you for a confirmation exactly which Android image needs to be used for this? (I'm asking since there are lots of Oneplus Android 9 image version flying around...)

(The rest of the prerequisites are satisfied, including my patience )

And thank you for the reply and time you are spending helping me

@Lakotaubp Yes, I tried. Unfortunately that does not work: UBPorts installer flashes something small onto the device, then asks user to manually switch the phone to Recovery mode, and then nothing happens (Installer starts adb waiting for the device.... indefinitely)

The big problem here is that the device is stated as - basically - fully supported in the device DB, which is obviously not true...

It is quote save, but not sure, if I recommended it in it's current state:

• the GUI has lags during starting of apps and between switching apps
• the power/thumb reader button is "always on", so any touch activates it.
  Also, the phone reboots from time to time (not frequently - once in a week or so).

Otherwise, the phone is pretty ok to use with 22.04 20.04.

OnePlus 6/6T cannot be imaged with UBports. For months.
Can anybody please look at this?

Thanks a lot.

@StephPTi Well, I did not use Android extensively, only for some minor looking around (it is awful :smiling_face_with_smiling_eyes: ), but I did not notice anything wrong with the button or the system...

The device came with Android 11, I downgraded to Android 10 using the image:
surya_global_images_V12.0.9.0.QJGMIXM_20210508.0000.00_10.0_global
...and using the attached script 'flash_all.sh'.

I'm thinking if there is a way to re-image it back to Android now? To check, if the button worked ok? (I never re-imaged UBports phone back to Android before, so not sure about the implications...)

@StephPTi Yes, correct, 16.04 stable.
The device model is M2007J20CG.

Hi there,
I have a freshly flashed device POCO X3 NFC. It seems to be working just fine, except one thing:

The fingerprint reader, which is also a power button, stays always on. Meaning it reacts on every touch of the skin. Even if there are no finger prints registered and the device is not set to use FP to unlock the screen.

It is getting super annoying, because the button emits certain "behaviours" under different circumstances: Mostly it acts as "enter" (new line) when typing messages in various applications; in app switch view it selects/switches to the first app etc.

Can I please ask for help, if this FP reader can be disabled? (so that the button really works as just an ordinary power button).

Thanks a lot

Hi there,
I need a new Ubuntu phone, since my current Meizu PRO 5 is dying slowly.

I have access to a Redmi Note 9 PRO device, and (as usual) prior to installing Ubuntu Touch the device needs to be unlocked.

Looking over the internet, I'm actually quite confused about what "unlockig this device" actually means, which steps to take, because:

• Activating developer mode and Enabling OEM unlock is fine...
• But then some of the HowTos suggest creating Xiaomi account? And a need to wait 160h for "something somewhere" to activate?
• Also, lots of online HowTo require to download a Windows-based "Mi Unlock" tool to further unlock the bootloader? (I do not have a windows machine anywehere...)

I do not have such a big understanding of the Android internals, so I do not want to e.g. brick the device by my own incompetence.

Can please anybody here please help and put down a clear list of actions, how to fully unlock the Xiaomi device using Linux?

Thank you a lot in advance.

@tricky Hello everyone. This still does not seem to work here (T-Mobile Czech Rep.).
Was there anything done to resolve this, please?