Probably there are other users with the same problem. The attempt to install 24.01 via the installer lead to a blocked device. It was possible to return to the former release 20.04/rc by using the installer. From there you can try to update again to 24.01 - unfortunately with the earlier result: the device boots and stucks displaying the white "Sony"-screen. So I installed the 20.04-release again.
Posts
-
RE: Error on installing - software binarie
-
RE: Error on installing - software binarie
I followed the link from DJac and applied the TWRP install, however, w/o success. Thats sad - I liked the Xperia-device. So any recommendation that solves the issue is welcome!
-
SIM card inactive
I have two Xperia X phones, one running on Android 8, the other on UT 20.04 (2025-W09). The first one accepts my SIM card and makes calls. When I try to move the SIM to the 2nd phone, it will ask for the PIN, when powered on. However, it will not show a service provider, nor a net. Furthermore, flight-modus is indicated and cannot be disabled in settings. Any recommendations?
I was able to use the phone for calls 2 years ago.
-
Install
Hi there,
my name is Stefan. In 2016 I bought an BQ Aquaris M10 tablet - which worked well with Ubuntu Touch (given my use case). However, it has reached end of life. During the last two years I played around with Pinetab2, but the result was somehow cumbersome, and low performant.
Recently I bought a used Lenovo TB-X306FA. I followed the installation instructions, but with my computer (Asus / Ubuntu 24.04) the SP_Flashtool was not capable to update Android. Hence I followed thecosmix UT_Install_ReadMe.md instructions to flash via fastboot, resulting in a device with Android 11. Then I utilized the UBports-Installer. The Lenovo-device works perfectly so far. Thanks to everybody who contributed!
Regards, Stefan
-
RE: ut-sysbench-qt-gui: Compare CPU performance of different devices
I used the test for 3 devices, here are the results:
- Device BQ Aquaris M10 FHD, Ubuntu 16.04
sysbench --test=cpu --num-threads=2 --Cpu-max-prime=20000 run 59 events per second
sysbench --test=cpu --num-threads=8 --Cpu-max-prime=20000 run 113 events per second
sysbench --test=memory --num-threads=4 run Operations performed: 0 ( 0.00 ops/sec) 0.00 MB transferred (0.00 MB/sec)
sysbench --test=mutex --num-threads=64 run total time: 0.9229s
- Device xperia X ubuntu-sdk-20.04
sysbench --test=cpu --num-threads=2 --cpu-max-prime=20000 run 1385 events per second
sysbench --test=cpu --num-threads=8 --cpu-max-prime=20000 run 2465 events per second
sysbench --test=memory --num-threads=4 run Total operations: 25487419 (2546616.80 per second) 24890.06 MiB transferred (2486.93 MiB/sec)
sysbench --test=mutex --num-threads=64 run total time: 9.2790s
- Device: pinetab2, ubuntu-sdk-20.04
sysbench -test=cpu -num-threads=2 -cpu-max-prime=20000 run 678 events per second
sysbench -test=cpu -num-threads=8 -cpu-max-prime=20000 run 1263 events per second
sysbench -testzmemory -num-threads=4 run Total operations: 50881276 (5086734.72 per second) 4968.75 MIB transferred (4967.51 MiB/sec)
sysbench -test=mutex -num-threads=64 run total time: 15.9498s
This result is quite in line with my observations when using these devices: Xperia X performance is quite good after the update to the new release.
Kind regards, Stefan
-
RE: Call for testing: Ubuntu Touch Focal OTA-4
Hello everybody,
I use an Xperia X Suzu, which was running fine with UT 20.04 (2023-W44), i.e. Release-Channel. I switched to Development-Channel, downloaded, and pressed "Install". Which ended in a message "Installation failed. Please reboot." Which I did, resulting in a system start. Surprisingly the "System"-section shows, that UT 20.04 (r852) is the current OS, under details the device image is shown as 20240111-31815. It seems that the update was done, despite the error message.
As far as I can see, all apps work, in particular the Morph browser. Camera, ADB and change of PIN works, too, as well as WLAN and BT. Currently I do not use phone calls in this device, so no testing in that respect.
I returned to the release-channel, installed the previous version, which worked and showed the earlier entries under system information. Then I started the update a second time with the a.m. result.
Hope this helps. Thanks for your ongoing work!
Stefan -
RE: Smooth 20.04/rc on Xperia X F5121
I moved my Xperia to 20.04 recently, and everything went well. I am pleased with the outcome, thanks to everybody, who contributed to that!
I wonder if anybody has tried to upgrade to OTA-2 manually, and with what results? (Obviously there is no upgrade offered under the System/update section.)
Kind regards,
Stefan -
Problem to flash Aquaris E5
Hello,
I use 2 BQ devices, Aquaris E5HD and Aquaris M10FHD. I bought them in 2016, and flashed both to the Android version, when Ubuntu stopped the support. Lately I realized, that UBports provides an updated version of UT, and tested it. I was very satisfied to find an alternative for Android, and use both devices day-today. Thank you for your work! However, last week the E5 handy got some problems with the display: the screen began to shutter and greyed out, no entries are possible anymore. Thus I decided to start a new installation. The UBports installer 0.4.18-beta did not work, so I began with the SP_flashtool and the Vegeta01A-image. Which worked and provided me with the old UT-version, including scopes etc., all displayed as usual. After that, I launched the UBports installer, started the process which ran through to the success-message. Unfortunately, when power on is used at the device, the display problem is back again: a shuttering b&w screen "powered by ubuntu" comes up and no further action is possible. Any suggestions that might help?
-
RE: Can't update Aquaris M10 FHD Frieza
I flashed the same device a few days ago. Before you run the tool from UBports, you will start the SP_flashtool. In my case that did not start, and I looked into the guidance https://wiki.ubuntuusers.de/Ubuntu_Touch/flash_tool/. They mention a BROM-error - as recommended there I disabled the modemmanager, and started the SP_flashtool again. This time it ran through, and after the UBports-tool is successful.