No SD card write access for Android Apps [answered]

Question

2

No SD card write access for Android Apps [answered]

asked 2020-05-01 12:29:31 +0300

VincentB

433 ●11 ●14 ●22

updated 2020-05-04 09:57:55 +0300

jovirkku

23703 ●213 ●311 ●247

moderator

Hi all

everything was OK in 3.3.0.14, but nor in 3.3.0.16.
Android apps have only read access to sdcard.

I can say that because :
* with AlienDalvik Control, I can browse gallery (my picture are on the sdcard), but camera app can't take picture, saying that a issue occured during saving picture,
* in whatsapp, I can't download image or video,
* Android Store (from jolla Store) can't install or update apps, saying that it can't write in SD card.

Native apps can read and write on sdcard.

It mounted in /run/media/nemo/7397-7B02/, and this directory is owned by nemo user.

I saw this TJC question but I don't know if it is still available in Rokua.

EDIT :
Rokua release note says :

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 music to the card. Apps like WhatsApp can attach pictures from the SD card to messages now. The card name must not contain spaces.

"the card name", what does it mean? the mounted folder? something else?

Is there a way to give write access to sdcard to android apps?

Vincent

EDIT2 : I tested with my old Jolla 1, with the same sdcard and android OpenCamera app, and it works. My Jolla 1 is also in 3.3.0.16.

So, this is not related to 3.3.0.16, and the SDCard is not faulty.

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by jovirkku
close date 2020-05-04 10:04:11.793993

Comments

For me, i remark that with 3.3.0.16 :

1/ OSMand can write on µSD card but it was very unstable. I need to re-launch the app after each tiles download

2/ The Android app OpenCamera crash when you want to change parameters.

Note that i have not the openrepos on my XA2-H3113 (monosim)

mips_tux ( 2020-05-01 12:45:52 +0300 )edit

Have you updated AlienDalvik Control to latest version like it's stated in SFOS release notes and on OpenRepos page of AlienDalvik Control?

Pohli ( 2020-05-01 12:46:49 +0300 )edit

@Pohli. After 3.3.0.14, I installed and reinstalled AlienDalvik. But not after 3.3.016 update. I will try...

Done : without any effect, as I was already in 9.2.0 version.

VincentB ( 2020-05-01 12:51:45 +0300 )edit

@mips_tux : I tried OpenCamera, and with my J1, it's ok

VincentB ( 2020-05-01 20:09:14 +0300 )edit

It could still be related to 3.3.0.16 IMO cause SailfishX and SFOS are not the same thing under the hood.

Pohli ( 2020-05-02 01:06:44 +0300 )edit

For me, i remark that with 3.3.0.16 :
1/ OSMand can write on µSD card but it was very unstable. I need to re-launch the app after each tiles download
2/ The Android app OpenCamera crash when you want to change parameters.
Note that i have not the openrepos on my XA2-H3113 (monosim)
mips_tux ( 2020-05-01 12:45:52 +0300 )edit
Have you updated AlienDalvik Control to latest version like it's stated in SFOS release notes and on OpenRepos page of AlienDalvik Control?
Pohli ( 2020-05-01 12:46:49 +0300 )edit
@Pohli. After 3.3.0.14, I installed and reinstalled AlienDalvik. But not after 3.3.016 update. I will try...
Done : without any effect, as I was already in 9.2.0 version.
VincentB ( 2020-05-01 12:51:45 +0300 )edit
@mips_tux : I tried OpenCamera, and with my J1, it's ok
VincentB ( 2020-05-01 20:09:14 +0300 )edit
It could still be related to 3.3.0.16 IMO cause SailfishX and SFOS are not the same thing under the hood.
Pohli ( 2020-05-02 01:06:44 +0300 )edit

Accepted Answer

1

answered 2020-05-02 19:57:52 +0300

VincentB

433 ●11 ●14 ●22

I gave up. I made a fresh install of 3.3.0.16, and everything is ok.

edit flag offensive delete publish link

Answer 2

1

answered 2020-05-03 19:51:38 +0300

Jari K
61 ●2 ●3 ●7

Probably a different issue, but I had problems because my card is ext4 formatted and the permissions were so that nemo group had permissions to write to /run/media/nemo/XXXX-YYYY/ but not nemo user. According to the logs *), the system was trying to create application specific folders under /run/media/nemo/XXXX-YYYY/Android/data but that failed. I created Android/data and gave all a write access there => app folders started appearing as nemo:media_rw.

The apps mentioned in 3.3.0 release notes work now. Unfortunately c:geo is totally broken, probably because some additional permission problems.

*) https://jolla.zendesk.com/hc/en-us/articles/204110913-Collecting-logs-from-Android-Support-with-Logcat-Debugging-Android-apps-

edit flag offensive delete publish link

Comments

If a card is formatted with Sailfish the permissions should go right.

jovirkku ( 2020-05-04 10:03:08 +0300 )edit

Indeed, c:geo doesn't work for me either on 3.3.0.16, just quietly shuts down. Are there logs that could be used to determine what the problem is? I tested that if I updated c:geo to the latest build it will be able to show the release notes, but will again get confused when trying to switch from that to the main application.

ExTechOp ( 2020-05-04 17:28:33 +0300 )edit

JariK, have you been able to figure out what is wrong because I really could use c:geo?

ExTechOp ( 2020-06-06 14:43:52 +0300 )edit

@ExTechOp / @jovirkku Nope, I went back to using cgeo with my old J1. What I've tried is formatting XA2 sd card from Sailfish (it is FAT based now) and removing and reinstalling cgeo. Usually cgeo startup gets stuck when trying to add account information. The last lifesign in the log seems to be something like:

06-07 12:00:53.744    73   337 D VoldConnector: SND -> {24 volume mkdirs /storage/sailfishos_storage/Android/data/cgeo.geocaching/files/}
06-07 12:00:53.731    18   759 D audio_hw_alien: out_get_latency(): 133
06-07 12:00:53.746     5    11 E cutils  : Failed to mkdirat(/storage/sailfishos_storage/Android): Read-only file system
06-07 12:00:53.746    73   155 D VoldConnector: RCV <- {400 24 Command failed}
06-07 12:00:53.748   920   920 W ContextImpl: Failed to ensure /storage/sailfishos_storage/Android/data/cgeo.geocaching/files: 400
06-07 12:00:53.750   920   920 W cgeo    : [main] 'null' is NOT available as external dir
06-07 12:00:53.754    18   759 D audio_hw_alien: out_get_latency(): 133
06-07 12:00:53.756    18   759 D audio_hw_alien: out_get_latency(): 133
06-07 12:00:53.760   920   920 W cgeo    : [main] Couldn't get active Locus version
06-07 12:00:53.973    73   116 I ActivityManager: Displayed cgeo.geocaching/.settings.SettingsActivity: +383ms

Jari K ( 2020-06-07 12:08:43 +0300 )edit

@jari-k I just installed Sailfish 3.4.0.22 Pallas-Yllästunturi, but unfortunately c:geo did not start working. Are there instructions somewhere on how to enable debugging for c:geo?

ExTechOp ( 2020-09-30 20:32:26 +0300 )edit

No SD card write access for Android Apps [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by jovirkku
close date 2020-05-04 10:04:11.793993

Comments

2 Answers

Comments

Question tools

Stats

Related questions

No SD card write access for Android Apps [answered]

The question has been closed for the following reason "the question is answered, an answer was accepted" by jovirkku close date 2020-05-04 10:04:11.793993

Comments

2 Answers

Comments

Question tools

Public thread

Stats

Related questions

The question has been closed for the following reason "the question is answered, an answer was accepted" by jovirkku
close date 2020-05-04 10:04:11.793993