Posts made by stefan_hdb

I used the test for 3 devices, here are the results:

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

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

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

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

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

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?

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.