asked 2019-07-03 11:04:23 +0300
(probably already asked just kick this off then)
I am not able to set a path to sdcard for osmand because of permission problems. With the older dalvik versions it was quite easy: Create the directory in the sdcard, set the owner of osmand to this directory and set this path in osmand setting. But that does not really work and: I cannot find the application itself and therefor cannot get the real permissions for the path...
answered 2019-07-03 12:37:40 +0300
Two things :
The applications (like any other android app) should be visible under /home/.android/data/data/net.osmand.
You should be able to check the for the correct UID/GID there.
According to the Jolla devs, the way the SD card appears to Android apps is in the process of being changed and by the next version 3.1.0 it should have reached target (hopefully ?) That means that the way it worked in the past, the way it works in 3.0.3 and the way it will work in a couple of weeks are all different. Expect to have some hiccups when trying to share storage.
This is mostly due that now, with XA2 and 8.1 Oreo, AOSP is running inside a container (Instead of a Java-like VM like up to 4.4 Kitkat) and doesn't necessarily see the same paths as the main Linux host.
In order to explore inside the container, you need to get a shell inside with (as root, so devel-su) :
lxc-attach -n aliendalvik /system/bin/sh
By typing mount on the shell inside theLXC aliendalvik container, I (sometime) see this entry popping up :
/run/media/nemo on /data/media/0/sd type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other)
So the Sailfish-side directory where the removeable media are mounted (/run/media/nemo), should show up in /data/media/0/sd
Again, according to what the Jolla official devs have said in chats and blog posts, this is subject to change and we should revisit this in a couple of weeks once 3.1.0 is released.
I would actually advise to completely skip the Android problem and go straight for Sailfish Native apps.
Multiple other apps can also use that local server (e.g. sport tracker Laufhelden).
It's much easier to configure to use SD cards (being a native app).
[https://openrepos.net/content/rinigus/osm-scout-server] and [https://openrepos.net/content/rinigus/pure-maps] are very nice, but they are not up to Osmand's standards, which offers contour lines, intermediate stops, public transport itineraries, rerouting from deviations, and some more cool stuff.
danfin ( 2019-08-18 14:06:47 +0300 )editI would suggest to check issues filed for Pure Maps and see if any of missing functionality has been requested already. If not, file an issue per functionality. As for rerouting and public transport, both are supported. If osmand has better public transport, I will have to look where do they get data from maybe we can use the same data source. Intermediate stops (waypoints) are planned; contour lines as well.
rinigus ( 2019-08-19 13:55:42 +0300 )editanswered 2020-04-04 13:20:37 +0300
Citing the release notes for 3.3.0:
Many Android apps can access the SD card, now. For instance, OsmAnd and HERE WeGo map apps can save the offline map tiles to the card. Likewise, Spotify can save the music to the card. Apps like WhatsApp can attach pictures from the SD card to messages now. The card name must not contain spaces.
Asked: 2019-07-03 11:04:23 +0300
Seen: 1,164 times
Last updated: Apr 04 '20