https://medium.com/androiddevelopers/android-11-storage-faq-78cefea52b7c
On 1/7/21 4:00 PM, Troy A. Griffitts wrote:
>
> Thanks Tobias, Timmy, and everyone contributing to this discussion. I
> did a quick search and this page has been helpful. It recommends
> opting out by using the requestLegac
Thanks Tobias, Timmy, and everyone contributing to this discussion. I
did a quick search and this page has been helpful. It recommends opting
out by using the requestLegacyExternalStorage options you've also
suggested, but if I understand things correctly, it says this will
basically make Android
Regarding the /sdcard issues I reported with Bishop I think it is
actually due to the changes Google introduced in API level 29 / Android
10 (see Timmy's earlier post).
I was previously compiling my Ezra Project debug app for API level 26
and there I didn't have issues reading/writing /sdcard.
Hi Troy,
Thanks for your help! This is how it looks after wiping the
/sdcard/sword directory and freshly starting up Bishop:
01-02 21:10:58.863 9973 10061 D libsword.so: libsword: init() begin
01-02 21:10:58.863 9973 10061 D libsword.so: libsword: init() sword
config not found, attempting t
It's not used for anything in particular, just as a write test. We used to
store (I guess we still do) stuff in a [globals] section like a directory to
scan for new module when SWORD first starts up and then it would install those,
letting an external program or user just dump stuff to a folder,
I just created an empty file /sdcard/sword/mods.d/globals.conf, but I
still get the same error message as below.
It seems like the method FileMgr::existsFile is not detecting the file
/sdcard/sword/mods.d/globals.conf on my tablet.
Best regards,
Tobias
On 1/2/21 10:49 AM, Tobias Klein wrote:
Ok!
Below is a full dump of adb logcat | grep libsword.
Seems like this is the key section, though:
01-02 10:35:25.259 5450 5538 D libsword.so: libsword: init() sword
config not found, attempting to create parent of:
/sdcard/sword/mods.d/globals.conf
01-02 10:35:25.260 5450 5538 D libswor
Aside:
I suppose there’s no chance that Bishop for iOS/iPadOS could share modules
installed by PocketSword?
Correct me if I’m wrong.
David
Sent from ProtonMail Mobile
On Fri, Jan 1, 2021 at 20:07, Tobias Klein wrote:
> Hi Troy!
>
> Happy new year!
>
> Where does Bishop store the SWORD data
FYI all, Android has made some storage changes in Android 10, and even more
restricted in 11. I have not gotten to the bottom of it myself but you can
read about the changes here:
https://developer.android.com/about/versions/10/privacy/changes#scoped-storage
https://developer.android.com/about/vers
Hmmm. That's odd. If you can adb logcat your tablet while it is plugged into
your laptop and have a look at the output when Bishop starts up, it might give
us a clue. Bishop is pretty noisy to the logs. The detection logic is located
in init(), here:
https://crosswire.org/svn/sword/trunk/bindin
Thanks Troy!
I see this working with Bishop on my phone (Android 8.1.0). There Bishop
reads from and writes to /sdcard/sword.
However, it is not working on my Tablet (Android 10). I do have SWORD
directories there with this structure:
/sdcard/sword
/sdcard/sword/installMgr
/sdcard/sword/mod
Yes, that's exactly right. Upon install, Bishop asks for permissions to read
and right files to /sdcard/sword/. If it is able, it does, if not, it writes to
its app’s private data area.
I don't believe there is anything like this available on iOS, but I am no
expert. I would be interested to le
Hi Troy!
Happy new year!
Where does Bishop store the SWORD data files on Android? I was browsing the
filesystem but could not find the respective directory.
I am asking because I am working on Android support for
node-sword-interface and I wanted to align this and use a common place for
the
13 matches
Mail list logo
