answered
2019-05-26 16:36:07 +0200
I had similar problem with data synchronization between native Syncthing and Android application. I'm posting here my solution because it could be interesting for your use-case. I achieve that by using:
bindfs --map=100000/1023:1023/100000:@100000/@1023:@1023/@100000 ~/syncthing ~/android_storage/syncthing
For the explanation bindfs mount will map users and groups. So user and group nemo (1023) will be mounted as user and group media_rw (100000) on the ~/android_storage/syncthing folder side. The media_rw is android storage user and this mapping will work even for written file. So this way you are able to make nemo folder accessible for write for android applications.
The only drawback is that I wasn't able to create a working systemd service for this solution. Do not know why, probably because of bad mounting order. Could someone here help me with this? It is annoying to run the script manually every time I reboot my phone.
Thanks!
Sorry if I'm missing something - why can't you copy to Android storage, (file manager, /home/nemo/android_storage)?
Levone1 ( 2019-02-23 02:58:00 +0200 )editSame problem, when I copy the whatsapp history to android storage, AD crashed
TMavica ( 2019-02-23 15:36:32 +0200 )editSame problem here, I tried using three methods to copy data to android_storage on Xperia XA2 Sailfish beta -- all failed:
Don't think I can use this version of the OS until I can copy files to android_storage... :(
caa ( 2019-02-23 21:59:05 +0200 )editWhen I tried to copy a file I usually got message: "Cannot create /home/nemo/android_storage/file_name.xml" Or when I want to switch android storage in file manager I got: "Android Storage not found" :(
Jolla fan 007 ( 2019-02-23 22:22:20 +0200 )editsame here, it seems any attempt to write to android_storage triggers an error resultng in unmounting of the android_storage...only reappears after a restart of android system
pelupes ( 2019-02-28 14:00:50 +0200 )edit