@UBportsNews Please don't apologise for this issue. it happens. This is done by volunteers in their own time and is way above what myself and others can do, for which myself personally am very grateful for. Please keep up the good work it's greatly appreciated.
Best posts made by MrT10001
RE: Few thoughts regarding coming back after several years
I have held off on this thread, but I thought I would put my bit in now!
Bought 2 x BQ Aquaris e4.5 when Canonical and BQ put them on the market that day. One was mine and the other was mine too, but I handed it out for people to play with.
As a phone, text, MMS, camera and web browsing, most used and thought it was adequate. For social media, it was no and a resounding no at that.
Ok so come to 2022/2023. Canonical has devolved Ubuntu Touch to the community when the phones and tablets did not take off as planned - you have to try these things! So now Ubuntu Touch is run as a charitable foundation (UBports) by volunteers. There is some commercial working from what I can see, but most is run by enthusiasts and volunteers. This means your data is not going to be scraped and sold to the online bidders so you can get spammed with ads (thanks Amazon, Google, Apple, Xiaomi......). It also means that some things work, some things don't and it is not for everyone as they want a device that just well works for what they they want.
Some things won't work as UT is open source, i.e. Internet banking apps (encryption), Social Media, such as SnapChat and Whatsapp and so on. (BTW this is my opinion from what I have observed and read).
The Browser issues has been strongly covered with reasons why Morph is used and not Chromium or Firefox, but I find Morph overall very usable and suitable for me.
The Apps issues has also been extensively covered and again a lot are coded by volunteers and enthusiasts who spend their own free time and money running and maintaining them (kudos given for that). If you want an app that is not in the store, create it yourself, or use the browser, or heaven forbid, use your Android or Apple phone. It is that simple. What I cannot use on UT, I will use on my computers, or Android phone (my Iphone is out of Action, but was needed for one app).
I don't use Waydroid as I don't see the point personally (using UT is to avoid some Android apps), as I said if I need to use an app that is not in the store, I will use it on another device. But for some Waydroid is convergence with Android apps and I see why people are enthusiastic about it and again Kudos to the people setting it up and running with it.
Options, options and options, there are so many to do what you want. There is always a way and work around.
Thank you all for your hard work on UT and also the criticism as criticism makes things better in most cases.
Kind regards to all,
Mr T10001 (I pity the fool).
Breeze to install
Got hold of a Oneplus 6. Running Android 11, so downgraded using OB25 build from here.
Unlock the device (open developer options by tapping build in about device until it states "you are now a developer", back to System, Developer options, enable OEM unlock and USB debugging). In a command prompt use ADB to reboot to bootloader and then use the fastboot command "fastboot oem unlock", then when done reboot the device and set Android up again. Set up developer options and USB debugging, set it file transfer and copy the OB25 file to the root of the device (i.e. not in a folder). Go to system update and check local update and tap the zip file. Allow it to do its thing and tap reboot when done. The set android up again and hey you are on Android 9!
Then just follow the UT installer.
Installed so easily, I thought it was a Nexus 4 (apart from the Halium splash). Less than an hour and it is up and running. Good device so far!
RE: Have you tried other alternative OS systems ?
@UTdroid Hi. I have tried e/OS and also Sailfish OS. Sailfish is similar in the way the touch screen works to UT and has a reasonably good app store. It is also known as Jolla. I have also tried Plasma Mobile, which is very rough around the edges and looks a lot more like a Linux system.
e/OS is based on Lineage, so is Android stripped out and more privacy oriented.
e/OS is my fallback. UT is by far the better for me for a community driven phone os.
They all have their quirks and issues.
Hacking is another issue. I have never had an issue with it.
RE: About the criteria for developing new models.
@daemonicvs It is more than that, it is about Lineage support and getting hold of Vendor Blobs ( a lot of vendor blobs are proprietary so they have to be reverse engineered - think of a blob as a driver in PC terms). It is the ability to unlock the boot loader so vendors like Huawei are out. It is also the ability to get the right Android on the device, some devices the Android version needs rolling back and it cannot be done without bricking the device.
And one of the main restrictions is having an enthusiastic person who has the ability and time to a) create the UT port and b) to maintain it.
RE: Installing Ubuntu Touch to a Xiaomi Mi A2 with Android 10
@embeddedmz - I thought you didn't have access to a windows machine. This makes life easier, however upgrade to window 10 at least, windows 8.1 will have woefully inadequate support for drivers and items such as fastboot and ADB (USB device drivers). As the phone is unlocked, use the Mi Flash tool to downgrade the ROM to Android 9, it is by far the easiest method. There is an US English version, ignore the pop up box in Chinese, it is pretty much no use. However try installing UT with Android 10 first, it may just work. As I said, I download and use Android Studio as it installs the correct and latest Fastboot and ADB drivers and has always worked for me.
This is my MiFlash tool in windows:
- note the phone ROM is for kenzo - Redmi Note 3(not a Mi A2) as I was downgrading a different phone, use the select to browse to your ROM and DO NOT relock the bootloader.
Installation and perseverence
I have managed to install Ubuntu Touch onto my Redmi note 7. It requires you to be patient and persevere, so I will give a few points from my experience.
Kudos to the installer, it makes life so easy, but being in beta it has its flaws. The main flaw across the phones and tablets I have installed to, is the phone or tablet always reboots during the download phase of Ubuntu Touch which causes the install to fail. When it does this, persevere and start again - it will work, especially on this phone.
I have now flashed this phone a few times, to make it work (on both phones in my possession) make sure a working SIM is installed - don't know why, but it worked for me, without it it always hung at waiting for adb device.
I flashed the phones with Android 10 installed and it worked. I did follow the advice and down graded to Android 9, but without the working SIM, it failed.
The other thing I found I had to do, apart from when unlocking is to register it with my Xiaomi account. I don't know again if this had much bearing, but when not registered it failed to install Ubuntu Touch.
Be patient. It seems to hang a lot, but will get there. The initial firmware flash, sits there for about five minutes with the progress bar 75% across the computer screen (all you get on the phone is the fastboot logo). It will then reboot and you don't see it get to 100%.
You know you are going to have success with the flash when it sits at the Halium-9 recovery and the installer is pushing the files to the phone.
I am very pleased to get this working and would like to thank all for porting this and the advice and notices given in this forum, especially Stanwood who linked to a very useful instruction on Github. So a big thanks from me, now I have a "premium" phone to run as a daily driver with Ubuntu touch.
I asked this question in Q&A, but probably due to time constraints it wouldn't be answered. Being into the device repair, I see a lot of issues so:
Would it be possible to add hardware issues to the devices information to assist users in the choice of hardware that they are going to purchase?
Nexus 5 irreparable boot loop unless you have a re-flow machine, even then not guaranteed to work.
Nexus 7 (2013) both versions - screen issues usually motherboard. USB port charging issues.
Nexus 4 - very common to have the lower touchscreen not working which requires replacement
SONY phones may not be able to unlock the bootloader - very common
Xiaomi phones - difficult to unlock the bootloader as you have to do it through their Mi Unlock program. If you are unlocking more than one you may have a long wait (up to a month per phone) and there is no work round (that I have found that works).
Also as a side note a lot of devices have battery life issues which is usually down to the age and previous usage of that device, not always Ubuntu Touch (Nexus 4 and 5 with batteries dating back to 2013 are OK, must have been well made!)
I know things are changing now so devices will be left behind, but it would be helpful for some of the potential pitfalls on devices. Main things could be:
- Battery life
- Battery replacement
- Screen issues
- Ease of unlocking
and so on. The older the device, the more difficult the parts to get are, and also the cost may rise so their is a lot of making a working device from four or five broken ones. I also understand that being a UT forum a big emphasis is on the porting side, but if you want to encourage new blood, and that person may have an unused phone that they want to mess things, this information would be helpful.
RE: upgrade android version and UB-Touch
@beyolf Ah, I forgot about fastbootD, I haven't used it in a long while (dm-verity ). When I have downgraded a Pixel 3A ROM, I used the Android recovery tool in Chrome which allows it to be disabled.
(On a side note Xiaomi phone hardware is good, but being forced to wait to unlock the bootloader of a device that you have bought and paid for is wrong, not withstanding the hoops you have too jump through to do it.)
Latest posts made by MrT10001
RE: Redmi Note 9 Pro bricked when trying to return to Android
@noob-gamr You should return to the stock ROM version that was installed before you installed UT. Follow the link here - it is the same one on the UT devices page, the version is the last version of Android 10 - V22.214.171.124.QJZMIXM - this being the Global fastboot version or you can use the recovery version (which requires the MiFlash tool and Windows PC).
Make sure you get the correct version for your phone - you have stated Redmi Note 9 pro so I am assuming you have that device which is codename "joyeuse" and I have pointed you to the Global version - yours may be different depending which part of the Globe you reside in.
DO NOT relock the bootloader as you have a really high chance of hard bricking the device, i.e no fastboot, no recovery.
To install UT to this device, the partitions required resizing. Reverting to stock may and I say MAY resolve this and allow you to install a ROM (UT is not a ROM) such as LineageOS.
RE: Ubuntu Touch Q&A 134 Saturday 17th Feb 19:00 UTC
As we move forward, UT consumers seem to want more out of the OS than the physical development can allow (people have lives doing other stuff etc.). Would it be better to concentrate on getting core processes and apps streamlined so they "just work" on every device rather than what appears to be a "shotgun effect" were some devices work but have no sound in calls, or the camera doesn't work, battery life etc., etc...(EDIT: this is for the devices that use the installer)?
RE: Trying to switch back from UT to Android but facing a problem
@UTdroid Your device is not being seen by the pc. You need to make sure you have the latest fastboot drivers installed. You need to make sure the cable you are using is suitable - some are not and won't work. The phone needs to be in fastboot mode - ADB can be a bit flakey on that device.
As I said relocking the bootloader may brick your device, and I say may. It may not as well, but read round the forum s here and elsewhere and you will find out why.
RE: Ubuntu Touch Q&A 134 Saturday 17th Feb 19:00 UTC
There still seems to be confusion and some conflicting advice about devices that are on Xenial on the devices list, but running Focal, be it stable or development. Is this going to rectified with the list update?
On the devices list (I know the developers want to push focal, but after a forum thread discussion, some are still staying with Xenial) would it be possible to leave the list for Xenial and add the Focal list above or below it for the time being, rather than removing the Xenial list for that device?
Some people are trying UT and going back to Android for their reasons. Would it it a) be possible to make really clear the stability of Ubuntu Touch on a device (this information may be lost in the busyness of the device screen and people may miss something)and b) give a link to our make it really clear how to go back to Android with advice of do's and dont's?
I would like to thank everyone for their time and contribution to this project.
RE: Trying to switch back from UT to Android but facing a problem
@UTdroid My advice would be to not lock the bootloader. You have a high chance of bricking the device. I would also revert back to the Android version: factory image PQ3B.190801.002 first then upgrade the device through OTA upgrades.
Also boot the device to fastboot, not Ubuntu Touch and set the flash tool going from there.
Update dropped in for Focal, r7, today so I allowed it to update. Rebooted and hung at the Lenovo screen.
Turned off, waited a few seconds and turned on again. No boot.
Held Volume Up, Volume down and power together. When the tablet vibrated, released the power button but kept the Volume buttons pressed. Went to a black screen and then booted as normal.
Battery was at 99%, now at 94%.