@_Joao_ said in PIN Code needed after a few hours:

@Eric-H
Hi Eric, I'd like to thank you and the developers because the previous operations solved the problem; the phone no longer restarts by itself and I've gained +/- 6 hours of autonomy, which is really cool.

Thanks again and best wishes for 2024.

Note: if I can help with other tests to further the community, I'd be delighted to do so.

Please, may I ask your help with the flickering issue ?

Could you do a simple test ?

Wait for flickering

Remove ~/.cache/UBports/lomiri/qmlcache directoryrm -r /home/phablet/.cache/UBports/lomiri/qmlcache See if there is still flickering (probably yes)

(if still flickering)

go to sleep mode (by quick power button pressure, for example) resume (by quick button pressure) see if there is still flickering

(if still flickering)

Close all open apps (morph, telegraph…) see if there is still flickering (probably not)

If flickering is still here, redo the previous test but deleting ~/.cache/mesa_shader_cache directory this time

Thanks

@Boldos said in Poco X3 NFC:

Also, the phone reboots from time to time (not frequently - once in a week or so).

There is now a solution for this issue.
In a terminal, type

setprop persist.vendor.ssr.enable_ramdumps 0 setprop persist.vendor.ssr.restart_level ALL_ENABLE

For more details see at :
https://forums.ubports.com/post/77507

Before posting my question, videos in MP4 format did not work.
Later, I re-installed UT with the graphic installer (without erasing the user data).
So I tested an MKV video, and it worked !
So I re-tried MP4 videos and all them worked !

Use issues on GitLab :
https://gitlab.com/ubports/porting/community-ports/android10/xiaomi-poco-x3/xiaomi-surya/-/issues

@DPITTI said in Xiaomi Poco F3 compatibility:

Look on Ubports Devices

https://devices.ubuntu-touch.io/

@Moem yes true

@mito77
Still halium 9 on device page.
https://devices.ubuntu-touch.io/device/laurel-sprout

@messayisto said in Xiaomi x3 pro:

@Steinmoshe Have a look here:
https://devices.ubuntu-touch.io/device/surya

The Poco X3 Pro codename is Vayu, not Surya. This is for X3 NFC and X3 model, not for X3 Pro.

@reeered start by restoring your device with Xiaomi's tool: https://forum.xda-developers.com/t/miflash-guide-use-xiaomi-flash-tool.4262425/

@Moem said in Xiaomi Redmi 9T lemon:

@s10ley said in Xiaomi Redmi 9T lemon:

I'm fix that when install oldest version UT 16

You can't. It's not a supported device.

I'm using 16 UT now and all right (i mean booting), but i have many issue with physical keyboard, im now searching somethin driver for that china device)

@MrT10001 I think it don't. Didin't check that.

@gabo29 you can see the supported devices at https://devices.ubuntu-touch.io/ although not all of them are at the same level of usability.

As this forum is in English if you need help in Spanish maybe the Spanish telegram group can help you https://t.me/UBPorts_ES

puedes ver los dispositivos compatibles en https://devices.ubuntu-touch.io/ aunque no todos están en el mismo nivel de usabilidad.

Como este foro es inglés si necesitas ayuda en español quizás te puedan ayudar en el grupo de telegram en español https://t.me/UBPorts_ES

@nop said in Xiaomi Redmi 9C - Need to downgrade to Android 10 MIUI FW?:

Maybe the README could be clarified by mentioning that Android 11 and later is not OK?

I'd think that "the latest Android 10 MIUI FW" means that, and no other. If a recipe says to use apple juice, would you want it to add that pineapple juice or apple sauce are not suitable?

@moem ok thanks anyway

@hannescam i can use it while in the waiting period
and i i wonder if it would be possible to unlock it without waiting

@mrt10001 Hello in airplane mode it does not restart thank you for this idea. It's not the wifi so it's the mobile network that bugs the phone. I tested the sim on my nexus 5 no worries it works. I redid an install without any additional application it does not change anything with or without the RC update. Waydroy restat the phone from time to time if I raise several times. Thanks to you

@katesfb Apologies for the late answer and you may have gotten this resolved by now. However, I'll respond just in case someone else might have the same question in the future.

From looking into this a bit further, they should be the same device, so yes, technically it should work. Just to be sure though, I recommend confirming this with the contributor of the Mi A2 to ensure compatibility.

@lepotototor said in Installation on poco m3 failed:

@nitanmarcel The poco m3 is build with halium 10 so I flash the recommended rom with android 10 and I use the latest recovery image of miui or the latest of TWRP ?

I cannot see what you are trying to achieve. If you use the installer and follow the instructions, you should get a good install. If you don't, it is best to install TWRP, wipe DATA, CACHE and SYSTEM, then reinstall stock (using the MiFlash tool, ensuring you DO NOT relock the bootloader) and then try again with the UT installer.

If UT won't install, you have to make sure (using TWRP) that the DATA partition is erased and formatted to EXT4 and NOT F2FS - this will decrypt the DATA partition and allow UT to see it when installing.

If UT still fails to install then the device may have had a revision upgrade and might have (annoyingly and unknown) changed hardware like a different manufactured eMMC, Screen, Camera etc, that may stop UT installing.

These are some observations where I have had installation issues across a lot of devices. I have avoided flashing devices in the list using the CLI if there is the Installer available for it as without the installer it generally has failed down to my lack of CLI and coding Fu. I have had moderate success with devices not on the installer using the CLI without bricking the device to the point of unusability, an example is the Moto E 2nd gen EXT1524 which seems to be OK(ish) with UT.

@audrew ADB is like a higher level of Fastboot. Basically ( please feel to correct me anyone) fastboot installs a boot image and a recovery image. The boot image allows UT to boot, but you usually have to manually boot to recovery. Once in recovery ADB is then working and the UT install will continue by pushing the UT files over it from the PC to the device.
A bad or incompatible USB cable will stop ADB from functioning so no UT install.
An encrypted data partition will stop an install and can be flagged as an ADB error, that is why you have to format the data partition to EXT4 and wipe it so it is decrypted.
If the partitions have been resized, usually by installing a non stock ROM such as Lineage OS, UT won't install and may give an ADB error.
A bad or USB 3 port may cause an ADB error.
A PC/laptop may cause an issue for various reasons, if UT won't install on Windows, try a Linux based machine or a MacOS based machine.
Try an older installer, the latest Ubports installer may be a bit buggy.
Also follow the installation instructions to the letter or the install usually fails. Try a different channel if the stable channel fails to install.