GPS location data not available in Sailjailed app

REPRODUCIBILITY (% or how often): 100%
BUILD ID = OS VERSION (Settings > About product):
HARDWARE (XA2, X10, X10 II, …): Vollaphone, GS290
REGRESSION: (compared to previous public release: Yes, No, ?): YES


When adapting an application to use Sailjail, specifying (in this particular case Location and Internet) doesn’t appear to grant the app location (import QtPositioning 5.2) in QML.


Modify app to use Sailjail.


  1. Build (on 4.3 phone) (or install from chum)
  2. Start from grid,
  3. accept privs,
  4. on first screen choose Pulldown GPS Locations
  5. Sigh
  6. Build (on 4.3 phone) (or use an old store install)
  7. Start app from grid
  8. on first screen choose Pulldown GPS Locations
  9. Choose something near to you. Sigh.


Location data. A fix. I just want a fix.


Seems to be blocked. File reading and writing to localstorage and internet are not a problem.


I’ve tried running trace but that’s not verbose enough:

[defaultuser@VollaPhone ~]$ /usr/bin/sailjail --trace /usr/share/applications/harbour-dwd.desktop /usr/bin/harbour-dwd
…/daemon/sailjailclient.c:455: client_set_trace_dir(): W: /usr/share/applications/harbour-dwd.desktop: is not already existing writable directory
constructing /run/firejail/mnt/privileged: …
mounting /run/firejail/mnt/privileged @ /home/defaultuser/.local/share/system/privileged
hiding /run/firejail/mnt/privileged …

But this is probably wrong?

I’ve also tested now, just removing the Jail settings from the desktop. Then GPS works.

It is strange, gps is working for OSM Scout in Sailjail (2.19). I am using QML Location as source too…

I will try to look on it at Monday.

I’ll have a look at your code. I was there looking at your migration code which was really nice. I was thinking of making that into a generic local storage migration app :open_mouth:


An attentive user just pointed out that I’m probably doing ApplicationName incorrectly. I don’t understand why it would work at all :slight_smile: But, in testing, I’m obviously installing from the SDK.

I had harbour-dwd as name, which I should presumably change to DWD or some such.

EDIT: I haven’t tested it yet, but the symptoms they experience are not the same for me. So, I don’t think it’s naming. I can also start sailjail with the name from the desktop file without problems.

EDIT: I checked and name is not the issue: Using the same setup as Karry (for the desktop file) makes no difference.

Can someone with a Sony/Licensed device test this?

It seems that “activating” PositionSource is just enough. It works for me even in Sailjail.

1 Like

I had to do a bit extra, but THIS was the sauce! Thank you!

It does work, however, something is still odd.

It was built F&D (fast and dirty), so I cleaned up a bit and noticed while testing with QML live, I got immediate results, like I had in the previous version. In that version I hadn’t set PositionSource active but had button to allow it. In any case, even without the button, if you had GPS on, you immediately got a list. Now, if you exit and start the app from the tray, agree to the Sailjail, (all the time, GPS is on, for instance), the view first needs to start (with NaNs) and you have to exit the view or hit the button and wait before you get results.

Something is broken. If I remove the Sailjail, it just works. The crappier code was snappy in 3.4. Now you actually see the Locate & Update button and wait for seemingly for ever. I mean. It does work. But it was better. More fun. Fluffy.

It’s pretty crappy code (well, a bit better now :slight_smile: so I don’t expect help but maybe someone could confirm my observations? Maybe it’s a ports issue? Maybe it’s only Volla? Version 0.8.0 in the repo.