I get a few random reboots that usually don’t happen on LineageOS; but not as many as other UT users report (but then, I don’t use it as daily driver…)
Thanks, @Guillauume but I’m actually not really contributing to Ubuntu Touch, I just happen to test their progress from time to time and let people know in this topic
Now that Lineage 15.1 is officially supported I’m testing Ubuntu Touch again. Updated to 16.04/devel version 2018-08-11. No time for a full feature test, but things I noticed
The Samsung BD-J5500 Blu-Ray player is now found via WiFi direct but connecting fails
The libertine desktop app scope now shows the installed apps
Then I also tried the vivid version of cutespotify, but it fails to login. Tried to build it myself for xenial but I already failed at download a required library from spotify because the linked download page no longer exists.
uMastonauts (for Mastodon) seems to work somewhat, i.e. I was able to login and it showed my timeline a couple of days ago but today the app screen stays blank.
The phone was switched on for 26 hours now and the battery is down 59%. But then I’m not using it much as my main use cases don’t work (yet). I had GPS and bluetooth enabled for roughly half of the time (which I usually switch off on my main phone).
Thanks for your regulär reports!
Do you have any knowledge about the state oft anbox? Last thing I heard was that it is being worked at but there are problems for certain devices due to kernels.
Has the camera improved for the new models? Last time I tried it was working so far that the picture had the right orientation, but taking photos was incredibly slow and flash was not working. (I wonder whether they could benefit from @mal’s work, as the camera is perfectly working with SFOS.)
As far as I understood, there is no work being done at the moment to bring anbox to new devices as everyone concentrates on getting 16.04 done. And IIRC anbox has some challenges with qualcomm devices, so I wouldn’t expect anything soon for the FP2.
Also, I don’t think anyone works at the FP2 new camera module problems (no flash, front camera picture is upside down).
Edit: at the moment, there is no fully working email client, but a first alpha of dekko2 is out since yesterday. Setting up an IMAP account worked fine, but that alpha version doesn’t display multipart emails yet.
The issues in Anbox are not so much with Qualcomm but wayland in general. Upstream Anbox doesn’t yet work well with wayland backend of SDL. There is work being done to fix it but might need some changes to Anbox. In theory the alternative approach we have used in Sailfish might also work in other mobile platforms such as Ubuntu Touch. Not sure what backend Ubuntu Touch actually uses though.
Can’t say. Whenever there is talk about anbox in the UT telegram groups there are references about trouble with Qualcomm devices. But maybe this is just coincidence.
And as far as I understood, UT uses Mir, not Wayland.
Thank you.
At least for me, camera isn’t upside down anymore (when I tried last time). It has correct orientation, but is incredibly laggy when you shoot a photo. So, as there seems to be progress in this issue, I thought that some progress might have happened to the flash in the mean time, too.
It still has a few problems, so the automatic update for existing installations on the stable channel will switch to 16.04 with OTA-5 which is expected to arrive early October.
I’m on OTA-4. With some issues that need to be solved on OTA-5 (for example, Web Browser-next is not yet ready), but it runs really well. Very good OS. Dekko 2 Beta runs well, although needs to be “finished”. But I can see new mails, answer them… Flash is yet useless. But Camera runs very well (front camera is upside-down, but I think this is a “Stranger Things” reference, Isn’t it? Ho, ho…).
I hope OTA 5 will arrive with amazing changes too. And I heard that OTA 7 will bring Unity 8 and probably New MIR, in January. Great!
Just installed UT again on my device for testing and restored the contents of my home directory.
Wanted to try out anbox next, but the system.img only has 2GB which are almost full. I found some instructions how to enlarge that, but I’ll postpone that for later.
Edit: there is also some hint to clear the apt cache and set the reserved blocks in the image to 0. Then the space is sufficient.
First impression: anbox enabled (not actually running) already drains the battery a lot (phone is unresponsive and gets extremely hot).
So the most important command to learn was anbox-tool disable.
