Now available: 20.04 devel channel (Focal Fossa) for the FP3 - Feedback thread
-
Hi @all FP3/+ users,
There is now a new OTA-channel available for your devices, called
20.04 development
.
You should be able to see and select it in you system-settings update-settings.For those, who are already using a Focal-prebuild on the FP3, you can update your device, using the ubports-installer (without wipe option, of course).
Now, if you are willing to test this, it would be great, if you would share your experiences here afterwards, regarding update process and general migration behavior.
Please keep in mind: For now we have the devel-channel of 20.04 only, where daily updates happen and the system may break because of an update. So if you are a user, who prefers using a stable device you should not install this version yet.
-
@Luksus
Hello Luksus,great thanks I will test it.
-
@Luksus
My short Feedback:
It's simillar stable like FP4 and Vollaphone. I have both.So great work thank for your support.
my wife will be happy to have FP3 back again with running ubports 20.04.So waiting for FP2....smile
-
BTW. I have already implemented the lte-battery-saver script/service in the Focal port (see script variant 2 in https://forums.ubports.com/topic/6211/howto-alternate-way-of-saving-battery-when-using-4g-lte).
It is optional, so, if you want to try it out, you need to activate it first:- start:
systemctl --user start lte-battery-saver
- activate autostart:
systemctl --user enable lte-battery-saver
Use
systemctl --user stop ...
if you just want to stop it for now orsystemctl --user disable ...
if you don't want the service to start at all.For me, it makes a huge difference in battery-lifetime.
- start:
-
@Luksus Hello, while updating it broke my phone. When checking for the update, it first downloaded some update 999 from the 16.04 channel. I paused that. Then I switched to the focal channel, downloaded the update. After reboot the phone was super slow, it said no space on device. I rebooted, and then only black screen.
Re-installing did not work. I the end I had to wipe the system and re-install. Luckily I had backed up the most important stuff.Everything works well now, only this I recognized:
- small fonts like in a desktop app (Cinny, Nymea, Sfxr)
- wifi is sometimes lost and needs to be clicked again (was the same on 16.04)
Thanks for your great work and energy you put into this!
-
@Homer3 Thanks for your report.
I wonder what was going on. Maybe I need to test that again.I remember some similar behaviour with the wrong (16.04) downloaded update at the first try.
Maybe I can workout some workaround on how to carry out the upgrade from a 16.04 device to 20.04. -
@Luksus it would be nice to have the option in the OS to rease all downloaded updates.
The mobile data script woeks well, I have the feeling the battery lasts longer with the script enabled. -
@Luksus another thing I reconized is loss of wifi network connection. At random times the phone loses the cinnectiin to our home wifi, you have to select the stored network connection to re-connect. This behaviour was also in 16.04. Is it possible to write a script, that checks:
- is wifi enabled
- is wifi network connected
- if not, can I reconnect to the saved network within reach?
-
@Homer3 about WiFi:
I cannot confirm the loss, of the connection.
But I sometimes see, that the WiFi-indicator is displayed as "empty" after some time, like no or week signal. But the connection is still there and I can browse the network/internet still.Besides that, I re-testet the upgrade process myself.
It seems that it generally downloads the latest Xenial-devel-build first. After selecting 20.04-devel in the OTA-channel settings.
After that, I opened the OTA-channel-settings again and selected the 20.04 devel again and then it downloaded the latest Focal-devel-build.
As a result, now two updates were displayed, which I could "install". I selected the second one (Focal, with the lower build number) and the update went well, without any freezes or other issues.Though, one must know that, to not accidentally install the first downloaded xenial-devel-build...
I wonder if maybe some migration-processes slowed down your phone, maybe lots of music or similar, which needed to be indexed.