Nope, New screen failed to stop the loop at the UT splash screen unless on 16.04 Development.

Would like to know why........

@arubislander I upvoted you on this as you explained it better than I could. The Mi A2 if I remember correctly require flashing to both A and B partitions. I haven't flashed this device for a while.

Hi @naizena

That's good news.
It's probably a combination of USB port, USB cable and maybe software.

Try to keep track of those to better understand what the problem was.

@CiberSheep Thanks

@josevidal I don't have this device but my Lenovo tablet have a similar issue. Its port is dead though 😅
I recommend checking the syslog too (/var/log/syslog). In my tablet's case, if the issue persists for a long time, that log file can fill the whole device storage 😅

At first I tried by terminal the dépendency but it was the os. Even Gearboy color cant use of the controller option it has. Or it can be possible somehow?

Finally, I made a reset factory.
Miracle, all work !!!

@Ian said in restart unity8 on ubuntu tweak:

@kanab2 Are you on 16.04? It used to work for me, the fonts are way too small for my aged eyes. Still waiting for the tweak tool on 20.04.

Thete was an option to restart Unity 8 in the tweak tool, or you could use the undocumented feature. Open more than 4 apss and leave them running then do a long press on the power button and select 'restart'. If you had closed all your apps the phone would restart, but with several apps open you just get a restary of Unity8/Lomiri.

Thank You. I will try to restart unity by the 4 apps...

@josevidal said in UBports "quick" and "simple" install on Xiaomi Mi A2:

Since I installed Android9 I get a warning when starting the mobile,
'the boot loader is unlocked and software integrity cannot be saved. Any data stored on the device may be available to attackers. Do not store any sensitive data on the device.'

That is completely normal.

Hello,
try in terminal the following:
sudo systemctl stop bluebinder
"hit Enter"
sudo systemctl start bluebinder
"hit Enter"

this on already turned-on WiFi.
For me it is working

@arubislander yes i did

Final summary:

So, my experience counters some of what I have been told by the fellow Linuxheads.

You actually do not need the MiFlash tool to succesfully flash Android back.

No matter whether I used the MiFlash tool or manual fastboot commands in Linux terminal/Windows cmd, the result was frustratingly samey: Going back from Linux, Android 9 made the Wi-Fi unaccessible.

The good news is, Android 10 -- again, no matter how I flashed it -- didn't bring around the same trouble. Alas, Android 10 was the reason Mi A2 got significantly slower in early 2020, so I still wanted to go back to Pie.

If you struggle with the same set of circumstances, there is a hope! I flashed Oreo (which, just like A10, caused not troubles) and updated to Pie from there.

Hopefully this may help someone some day!

@MrT10001 Yes. I rebooted many times. Two Ubuntu Desktops, three USB cables, toggled Developer Mode, dmesg registers nothing with my UT phone, unless in Recovery Mode. That's the only situation where the USB cable and ADB works. It seems something in the UT OS has disabled MTP.

Later today I found this posting:
https://forums.ubports.com/topic/8849/mtp-not-working-on-pixel-3a-xl-after-ota-25-update

It appears to be a recent issue with UT OTA-25.

Thank you for any assistance you can offer.

@messayisto Sorry for reactivating this old thread.
Now on focal with the same device, on devel. Battery consumption is very high again and "top" finds out its the ominous bluebinder process again. So I tried to kill it, but it failed. Next thing I have tried is to change channel, I am now on RC - and voila, this works. Bluebinder is not running anymore, battery drain is normal again. Just in case someone on devel is wondering about the high energy consumption of the device...

Using focal OTA1, fingerprint is working on my Mi A2 with a Goodix fingerprint sensor. It also worked flawlessly with different versions of xenial UT.

If I recall correctly from lineageOS forums in XDA, Mi A2 can include two different fingerprint sensors: Goodix and FPC. This may be related to some devices having problems with fingerprint under UT. To check the type of sensor, in my phone there is a folder /sys/class/goodix_fp.

@keneda

I did nothing but this morning I received and send mms.
Best regards,
Frédéric

@cesar-herrera Can you staate which update channel and if 16.04 or 20.04. Now both are being used it makes it harder to sort issues if OS version is not mentioned. Thanks.

When a Xiaomi Mi A2 I used did not charge anymore or only very slowly, the problem was fixed by using a different USB cable and a stronger charger.
The old USB cable and charger still worked perfectly fine with other mobile phones, so this was clearly an issue with the Xiaomi Mi A2.
This was under Android, so I think this is a hardware problem, that can appear after some time.