@magnargj Success!!! Wow, finally...

Ok, assuming that the necessary tools like adb and fastboot are installed on the PC. The phone is in developer mode, bootloader is unlocked and usb debugging enabled.

1. Download the latest twrp for the device, it is sufficient with the img file. Here: https://eu.dl.twrp.me/jasmine_sprout/
2. Download the zip file with Android 9 as indicated by the ubports installer
3. Turn on the phone in Fastboot mode (volume down + power).
4. Boot the phone with the twrp img file: fastboot boot filename.img (No point in flashing twrp to the device, it worked fine just by booting with it)
5. Just use the file manager (nautilus or whatever) and copy the zip file in point 2 above to the phone
6. In twrp press the big install button in the main menu and browse to the zip file and flash
7. Go to the big reboot button in the main menu and change slot to the other and repeat point 6.
8. Reboot the phone into Android 9. Enable developer mode and usb debugging.
9. Run the UBports installer and follow its instructions.

It worked!!! Finally.

BUT: USE A GOOD USB CABLE!!!!!!! Half of my problems were because the zip file was corrupted when transferred over to the phone. The first cable (which was the one that came with my pinephone) just didn't do the job. This caused error messages when attempting to flash.

I definitively understand that this is a resource question, and the development of UT is low on resources... It might even be so that the amount of bug reports currently received, is more than enough, and the current way of doing it actually ensures that the amount doesn't become overwhelming.

@unisuperbox said in OTA-20 Is Now Rolling Out:

software is available to everyone at no charge.

Which, of course, is appreciated every day by yours truly. I'm so happy that I don't need to use android and ios.

I don't think it's that much of an ask to have people go to a central place to report issues that they have with Ubuntu Touch. Especially when someone getting a GitHub or GitLab account opens them up to many, many opportunities with Open Source software.

This is not the user perspective, but rather the developer/coder/IT-person perspective. Personally, Github scares me away, I think it is counter intuitive and clearly made by and for coders and developers. I've thought about how handy it could be many times, but every time I'm in there I'm filled with a sense of frustration and feel alienated. Even though this may be hard to relate to among those that are daily github users, I think many "lay-men" are in the same boat as myself.

Maybe you have an idea on how we could make the current bug reporting process easier for people? We can probably find a way to make sure that we get all the information that we need from everyone, without taking a lot of your time.

I have no ready solutions for making the bug-reporting process easier, but I was envisaging something similar to Questback (I know, it is not a bug reporting software) where the user fills in feedback on different topics and where there are field where problems could be elaborated. I'm sure it would be possible to make some sort of link to have it all end up in github.
The whole reporting could be integrated into the phone user interface, somewhere in the settings, so that bots didn't find it and create a spam issue.

When I woke up there was a notification about OTA-22 on my phone. How nice! a feature arrived with ota-21?

A nice feature I think, would be automatic toggling between silent mode and sound at specified times. Typically, it would be great if the phone went into silent mode when I start putting the kids to bed in the evening, and stayed silent until I got up in the morning, without having to remember to flip that switch every day!

@totalrando oh, right! I did downgrade to Android 9 before installing UT, so it is Halium 9 then thanks!

@magnargj Ok, so the phone is back alive. Had to use the MI flash tool on a windows PC and short circuit the test pins hidden under the battery connector. Important lesson: Start the flashing immediately, less than a minute after the phone was connected. I ended up flashing Android 8 on it.

But now I am at a loss at how to proceed. The UBports installer states: "You can use either use stock recovery or TWRP recovery to flash it. Flash it to both slots to be safe." The android 9 build it links to, doesn't contain any scripts for flashing. It also contains a .bin file which presumably contains .img files? Does this mean I need to flash these at a specific sequence using fastboot flash recovery etc?

Anyone know any good tutorials or want to share their experiences in this?

@applee I struggled really bad (steep learning curve), but this isn't really my comfort zone. I bricked it and had to open the phone to get it back alive, but with patience I managed. There is a thread about it on the forum: https://forums.ubports.com/topic/6187/ut-installation-failure
It was worth it, though

@chris_bavaria I have the same problem. I think it might be bluetooth le which is not supported. I tried to bring it up in the volla telegram group, but noone responded...

@matteo thanks for the update. And don't worry, translated from a Norwegian saying: "those who wait for somthing good, waits not in vain" Good luck with the new PC and enjoy the Summer. The latter applies to the whole community

@mrt10001 said in Stuck early in the setup process: am I missing a key piece of the puzzle?:

@phandersson You do not need to root the phone. You need to be on Android 9 and not 8 to flash Ubuntu Touch. You have to follow the steps precisely with Xiaomi phones to unlock the bootloader, which involves:
1)having a working SIM card inserted
2)creating a MI account and linking the phone to it
3) setting up developer mode
4) in developer mode setting OEM unlock to on and enabling USB debugging
5)unlock the phone using the Mi unlock tool and not fastboot OEM unlock.

Then be patient and go back into Android and re-enable USB debugging and power the phone off. Then power back on and enter flashboot mode by holding the power on and volume down button. In flashboot mode, flash the latest version of TWRP for that phone and wipe and format the partitions to EXT 4. Reboot to fastboot mode and Ubuntu Touch should install.

This was not necessary for me (I suppose there might be country specific differences, or versions of the phone ?). I never had the sim card nor was the phone connected to internet via wifi. After managing to get android 9 (image suggested by the installer), the install was staight forward. The challenge here seems to be getting the phone to boot the twrp image, which is puzzling...

Thanks for this! I also sent an e-mail to Volla support half a week ago, but they haven't gotten back to me yet.

I noticed that the Ubports-installer has two options for Volla 22, one just "Volla 22" and one "Volla 22 with new screen". This makes me believe/hope that the firmware problem has been solved.

I've been using my Volla 22 as a daily driver for almost a year, and been fairly happy about it. Then came the upgrade to OTA-5. Now the phone claims to be connected to the mobile service provider while it simultanously claims not to recognize the sim card and refusing to make calls, send sms and mms.
I went from having a nice phone one day to not being able to use it the next. The only thing I did with the phone around the same time was to attempt to solve the notch issue, which has beend described elswhere on the forum. After doing that I reverted back using the same script...

I've looked and it seems that noone else has experienced this after OTA-5? I tried to ask around on the telegram channel for volla 22, but it is a quiet place.

So, I wonder if anyone would be so kind to aid me in debugging the problem? I would so much appreciate to be aided back to the safe spot of UT, rather than my current android emergency solution.

Bonus frustration: While I was working to reflash the phone (which did not help), it slid off the table and the screen broke. Anyone know where I can get hold of a new screen?

Where exactly can I get hold of a new screen for my Volla 22? Doesn't seem to be in the volla shop?

@domubpkm thanks!

@domubpkm thanks for this, but how do I get rid of it again?

It is my impression that this is the case on my Volla 22 as well. Stable release.

My experience with the Volla 22 is that it struggles with too many webapps and browsing. Things slow down and it becomes less responsive. Helps to close apps. It works well as a daily driver, but I do experience this quite often. I wonder if it was a purchase for the future and if it is only downhill from here. Of course the design philosophy for webpages is much to blame. I miss html4

There are no phone batteries that are able to provide enough power for such a solution...

I've used Volla22 with focal for a few months (5?) now. There are two issues that is bothering. First one is that the phone struggles to switch between wifi and mobile data. Coming home I expect it to switch automatically to my wifi network, but that can in reality take hours. Leaving home it often gets stuck on 2G and I have to turn on and off flight mode to get it into 3G.
The other thing is that it doesn't see bluetooth le devices, ex pinetime and Amazfit GTR2.
In the beginning I was thinking that these would probably be rectified over a few OTAs, but now I am not so sure anymore. I am wondering how to get news on the progress with this device and where to interact?

Only thing I miss from xenial is hutspot https://github.com/wdehoog/hutspot-ut/releases
Or rather a way of channeling spotify to my livingroom hifi system. Also that focal doesn't have the tweak tool in order to keep apps awake, I miss.
But it is a patience game, isn't it? Not complaining, and really happy that I can live without android and ios.