@Vlad-Nirky Worth keep testing.

In the Settings section of satStat, in the section that says something like "Updating from AGPS", do you have anything marked? There is: WIFI, BLUETOOTH, ETHERNET, VPN

@Vlad-Nirky Thanks, very informative.

But waydroid does not have any WIFI access or mobile data. There is something that fakes WIFI, the LineageOS thinks that the network is being accessed through WIFI and not through the bridge with the UT host, but it doesn't seem to be working for me in the waydroid/LineageOS being used currently in the FP5 ( I think 13). And I doubt that even with the fake WIFI working, this will help Agps to get anything.

@Vlad-Nirky I press on "Recharger ..."

But I have to amend very much my first tests. I tested this several times after my first tests and the results were worse and more in line with the usual lag of getting a position.

This morning I went out jogging and after following the above sequence I couldn't get any position at all. I went through places with tall buildings on both sides but also through open spaces.

I doubt very much that waydroid can get any Agps result in these devices. As far as I understand, Agps gets information from cell towers, and waydroid does not see any cell signal to do that.

Having said this, I have to say that I have also a Volla Phone 22, and that one gets position immediately in waydroid, even under a ceiling. I don't know what is going on there, but it looks very different from what I see in the FP5.

Answering @Vlad-Nirky in a new topic, this was out of topic in the request for FP5 features:

@wgarcia
If you are using waydroid, could you make this test. (as you report very long >time to fix gps postion)
Disable GPS (and move somewhere else).
Launch waydroid.
Run (after install) satStat.Settings reload AGPS.
Enable GPS.
Look at the connection time in waydroid and in UT.

I did some experiments with my FP5. This is what I tried:

I installed satStat from Fdroid in Waydroid. I opened and checked settings. There is an option for Agps, but only to choose Wifi, Ethernet, VPN, ... , I left that all unchosen. I saw another menu entry, not in Settings but at the top level, side by side with Settings, which says something like "Get location from Agps" but could not find anything about reload. So the experiments I did was clicking on that menu entry. I tried this:

1. Restart phone
2. Disable location in UT
3. Open Waydroid.
4. Open satStat and click on "Get location from Agps"
5. Reenable location in UT
6. Open an app in Waydroid requiring location (in my case "Mapmyrun").

It got position in approximately 1 minute.

The I repeated this but with an app in UT:

1. Restart phone
2. Disable location in UT
3. Open Waydroid.
4. Open satStat and click on "Get location from Agps"
5. Reenable location in UT
6. Open Unav in UT

Unav got location in about 5 to 6 minutes.

These experiments were done both in the same open space (within the city, with some high buildings around).

@Futura I'm located in Spain. I think Volte is working as expected, but I haven't run any explicit test to try it.

@O.o. The camera in waydroid, as far as I know, works in all UT devices where waydroid works.

I use it in a FP5 with the Pleko app (Chinese) for OCR on Chinese characters, and I have used it to scan QR codes to login into streaming services. So I think it should work in the FP4.

But if the app has controls against rooting or any other of those filters, then the app will not work in waydroid. If you say that it works in your desktop, it should work, unless those filters jump in when you try to validate with your camera.

@guybrush3pwood said in FP5 bugs - SD card and Fairbuds XL headphones not working:

Lastly... is there a way to set an 'edge' to the top status bar? The clock ends up being cut off by the curved edge of the screen

There is an "apply_notch" hack but there is no specific patch for the FP5. Nevertheless, the FP4 patch works quite well for me, but use it on your own risk. To install it, open the UT terminal and issue the following commands:

wget -O apply-notch-hax.sh https://git.io/JtIpG
chmod +x apply-notch-hax.sh
./apply-notch-hax.sh FP4

The only problem I see is that in landscape mode the farthest indicator on the left is shown partially. I tried to fork the repository and adjust the parameters to solve this but haven't been able to make my fork patch work.

You have to run the last command above each time you upgrade UT.

@sub078 Stupid suggestion: have you checked if the boot was paused? There is a text that says "click start to pause boot" and I think "click start to continue boot".

Hi @Benoit-NL and welcome to this forum.

I don't know Mailo, but if it is a web-based email platform, you have to take into account that the web browser in Ubuntu Touch, Morph, has a quite outdated web engine due to library dependencies in the system.

It is hoped that when UT moves to the next version, from 20.04 which is now to 24.04, the web browser will be updated and it will be able to deal with more modern web pages where it now fails.

There are some other alternative web browsers in UT but they are very experimental and incomplete, not ready for daily use.

I have a Volla 22, and the time it gets a GPS fix in Waydroid is very short. I haven't seen anything comparable in any of the other devices where I've seen UT running (and I have seen Nexus 5, OnePlusOne in the 16.04 times, and original Volla (crazy), Pixel 3a XL and Fairphone 5 in the 20.04 era.)

I've seen it getting a fix even indoors and getting the correct fix even if changing completely location, so I doubt it is using a cache.

One would suspect it is using a-gps in Waydroid, but if I understand correctly, a-gps uses the cell towers and so needs an active SIM card, which Waydroid does not have.

I've seen this only happening in Waydroid, if I use GPS from a native UT app the time to get a fix is the "normal" one for UT, that is, quite slow.

I don't know if anybody else has this same experience.

My experience with Fairphone 5:

1. Bluetooth:

Working in my car for receiving and sending calls. Works also connected to a Pebble watch.

2. GPS:

Works for me, it takes 10 to 20 minutes to get a fix, in the open air or at the balcony of my place (1st floor of a building 9 floors high). Sometimes it takes longer, if I don't see a fix in 20 minutes I restart the phone.

3. IDLE:

Using the current development image the battery lasts for the whole day, unless using Waydroid for too long. I haven't seen the background apps draining battery so far.

4. NFC

I use it with Waydroid in the transport system of my city, no issues.

Calls: No issues, 5G or Volte are working.

SMS/MMS: SMS fine, I don't use MMS.

Waydroid: Very fluid, but it hangs often when put in the background. Not a big deal because it starts in seconds.

Connection to PC: No issues to mount the device in Linux, or connect with adb.

Wifi/network: Disconnects if moving between WIFI antenna, but otherwise no issues.

Fairphone 5 with Orange in Spain works well with Volte.

With the 28 May update and a Volla 22

Emojis: OK
Waydroid: OK

I dont' have a SIM in this phone so I can't test related things.

Sorry for the late report. For the things I can test:

Vola 22

Emojis: working OK
Waydroid: working OK

@MrT10001 There is currently a note saying that due to a bug the ISO is oversized:

https://cdimage.ubuntu.com/daily-live/current/

@delijati I used waydroid in the original Volla (until July 2023), the Volla 22 (from July 2023) and the Pixel 3a XL (since some days ago).

Waydroid in general has improved a lot, it used to crash much more often. But among these phones, by far where I find it smoother and more stable is in the Pixel 3a XL.

I finally managed to downgrade, quite unexpectedly.

I tried to install twrp recovery, to see if you could install the Android 9 image with it. I tried to flash it in fastboot mode with:

sudo fastboot flash boot twrp...img

(without sudo it wouldnt install)

and it got stuck in fastboot. I would not boot, or go to recovery, or anything.

Then I changed boot partition

fastboot set_active other

not that I had any idea on what I was doing, just as a result of desperation, since I saw this command somewhere. It moved from partition "a" to "b" but nothing changed.

Then out of boredom I went back to Google Chrome and Android Flash Tool and voilà, this time it downloaded and installed Android 9.

What a pain, it was a similar experience with an OP5 recently. It is a breeze to install UT, but downgrading Android can take you a full morning.

@MrT10001 said in Installation to Google Pixel 3a XL:

@wgarcia

You need to install the latest fastboot and ADB drivers.

I have the latest I think.

Once that is done you need to download the fastboot flash version which will have the flash all.sh file in it.

I've downloaded several, didn't see any "flash-all.sh" utility. Do you have a link to the one that has it?

I'm trying to install UT to a Gogle Pixel 3a XL.

I already unlocked the bootloader. It currently has Android 12, and so I'm trying to downgrade to Android 9, to the image that says in the devices page.

I downloaded the zip file corresponding to that image, but I don't know what to do with it. I've seen a "flash-all.sh" utility mentioned in other posts, but I can't find it to download from anywhere, I downloaded "platform-tools_r35.0.0-linux.zip " but this file is not here.

I tried to downgrade with Android Flash Tool in Chrome (from a linux machine). Chrome sees the device and connects to it, it starts the installation of the image. I puts the phone in fastboot mode, and then it aborts all the time (different cables, with "wipe data" and without, trying other options as "wipe al partitions" or similar.) The message is "Error connection", and "Error connecting to your device. Try disconnecting and reconnecting it. Failed to execute 'open' on 'USBDevice': Access denied. (open)".

So stuck here.

In the UT Telegram client Teleport, I cannot send images right now on the Volla Phone 22.

I see the attached image in Teleports, but the other party does not receive it. I cannot see it either in my own account if I open a client in the computer desktop or an Android device. I can send images from these two clients.

I opened an issue one month ago:

https://gitlab.com/ubports/development/apps/teleports/-/issues

Anybody else seeing this issue?