REPRODUCIBILITY: 75%
OS VERSION:5_2
HARDWARE:Jolla Phone (2026)
UI LANGUAGE: German
REGRESSION: I don’t know
DESCRIPTION:
Out of 4 tests, 3 times there were no usable satellites
First try: spent 55 minutes searching for satellites, then rebooted and repeated the process for 1 hour. Comparison image from the XA2+, which acquired a fix with usable satellites after 2 minutes. CSD images from the J2 and XA2+ are attached.
PRECONDITIONS:
Flight mode is out and GPS is active/on - after that i have started the App GPSinfo. Location setting → Custom: GPS position and both A-GPS. For a new trial i reboot the device.
STEPS TO REPRODUCE:
see preconditions.
EXPECTED RESULT:
That, after a reasonable waiting period (depending on how long the device has been left unused), it detects usable satellites when i am outdoor.
ACTUAL RESULT:
No usable satellite…
MODIFICATIONS:
no modification, but I use the App patchmanager (grater Icons on Appgrid)
ADDITIONAL INFORMATION:
The next 4 Image are from Jolla Phone 2026 (second image is from the second try - after i had reboot the device. I stopped the second try after an hour by saving the image.
Next 2 image are from the XA2-Plus - Device. It was right next to the Jolla Phone (2026). After 2 minutes, it had a workable and usable synchronisation, and it wasn’t used for 2 months. Otherwise, the same settings as the Jolla Phone
You might just have a faulty device and have to send it for repair/replacement, on J2 getting consistently 40-50 satellites and lock in gpsinfo within 4-6 seconds
I think beaconDB would not help here. GPSInfo gives a position and 19 satellites. That means it got some info from A-GPS (beaconDB would do the same, just maybe faster). The problem is it captures signal from 0 satellites out of the 19 it should be seeing. I would personally send it in warranty.
I ran another test today (rebooted the device). No improvement.
What’s the procedure for repairs or replacements? Should I just wait until Jolla gets in touch here, or should I send an email to their overflowing inbox (shop@jolla.com)?
It don’t seems a hardware failure because the Phone sees 19 or 20 satellites. Maybe it didn’t download the full Almanac. Did you try with mobile data with clear sky for 10 minutes or so?
I’d be very grateful for any tips, as nobody wants to have to exchange the device and set it up all over again.
I’ll give the mobile data option a go (I hadn’t switched it on – just 4G), but even so, after a 1.5-hour attempt, the GPS receiver should be able to establish contact with the satellites by then, even without any additional assistance.
I’ve now tried out the two suggestions that were made. Here’s the result:
First image: Started at 5.00 pm with mobile data on. At 5.38 pm, it appears to have received some data (on the XA2, the clock runs continuously from that point onwards, as it naturally maintains the connection). At 6.00 pm, I stopped the test – no further updates – apart from the one at 5.38 pm.
Second image: GPS switched off for half an hour, then switched back on – mobile data is on. Start at 6.30 pm, finish at 7.30 pm
I’ll carry out a factory reset if the rain here allows it (tomorrow or the day after tomorrow)
The “0/50” kind of display is what happens inside a house.
The location inferred through A-GPS or beaconDB means the satellites should be there, but the phone cannot see them.
The second value is the actual number of satellites seen by the device. The first value is how many are used in location lock and that value becomes something other than 0 only once there is location obtained by the device. I think A-GPS might only work if mobile data is on (at least at the moment) and main benefit of it is to more quickly download the almanac data. If A-GPS is not possible due to no suitable network being found and there is no pre-existing new enough almanac data then the data is gathered from information sent by GNSS satellites which is a rather slow method. If there are a lot of satellites seen but none are in use it can being either because bad signal quality (like indoors) or missing almanac data. But if you had mobile data on then it should have obtained the almanac quite quickly.
BeaconDB is only used for obtaining rough initial location based on cell phone tower information so the hardware has some idea where the device is and can use it as help when obtaining location if not a lot of data is available like only some good satellites in view. It does not help getting the almanac data.
I’ve no idea either, but if “The second value is the actual number of satellites seen by the device” is correct, then my device here in the room should surely be displaying a zero in the second position (mobile data:on, GPS:on) – but it isn’t. It counts up straight away: 0/18, 0/32…
To me, it looks as though these are the old almanac data that it has loaded from the cache, and it stops at 32 for the time being because it’s reloading new almanac data (for the current time). After all, the device can’t see any satellites here in the room, but only the Amanach data.
After some further checking it might be that the value could contain satellites it should be seeing. The documentation is not very accurate in that part. Do you ever see signal strength for satellites it lists in CSD app especially when testing outside?
