Re: pilbox file sharing
Hi Shaughan, > Yes, I set the storage permission. This is odd, since it works for you. Termux > still works for me, but not pilbox. I'm using a Samsung Galaxy Tab S5e. > Samsung > always locks everything down—maybe that's it. Strange. So for a first fix, I will set the requestLegacyExternalStorage flag in AndroidManifest.xml, as suggested by Wilhelm, and releaes a new PilBox. In the long range, we must find out how to support Scoped Storage. I have the same problem in PentiKeyboard btw. ☺/ A!ex -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Subscribe
picolisp@software-lab.de?subject=Subscribe
Re: pilbox file sharing
Yes, I set the storage permission. This is odd, since it works for you. Termux still works for me, but not pilbox. I'm using a Samsung Galaxy Tab S5e. Samsung always locks everything down—maybe that's it. Sent from ProtonMail mobile Original Message On Jan 18, 2021, 11:21 PM, Alexander Burger wrote: > Hi Shaughan, Wilhelm, > > Hi On Tue, Jan 19, 2021 at 03:49:45AM +, Shaughan Lavine wrote: >> Yes: Android 10 vs 9. So, how do I get files out of pilbox on Android 10? > > Hmm, I do have Android 10 here, and I can access files on external storage > with > PilBox Version 20201231 without problems. (Perhaps a stupid question, but you > did enable the permission in Settings/Apps/PilBox, right?) > > On Mon, Jan 18, 2021 at 08:22:13PM -0800, Wilhelm Fitzpatrick wrote: >> If you are using the Play Store version, that >> we might have to lobby Alex to make an update >> that sets this flag, which he should be able > > This would not be a problem. > >> to do as long as he has not already set the >> the target API version of the published app to >> 30. If a version with target API 30 has >> already been published then we are past the >> point of no return. > > In the long range, I will not be able te avoid API 30. I cannot bring my > customers to install from F-Droid, sadly. > >> To cooperate with the storage access framework >> past API 29 is very tricky. Termux recently >> abandoned their Play Store distributed version > > I have not looked at the Scoped Storage API yet. Is it really a problem? The > PilBox core runtime does not depend on external storage, so the API should be > accessible from Lisp (with perhaps a slight modification of > AndroidManifest.xml), no? > > ☺/ A!ex > > -- > UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
Re: pilbox file sharing
On 1/18/21 11:21 PM, Alexander Burger wrote: I have not looked at the Scoped Storage API yet. Is it really a problem? The PilBox core runtime does not depend on external storage, so the API should be accessible from Lisp (with perhaps a slight modification of AndroidManifest.xml), no? ☺/ A!ex I confess I've not dug into it myself either, as I've not had the need to do external file access in any of my apps. As you say, since Pilbox allows calls to be made to the Android framework, it should be possible to cobble something together. The general approach as I understand it is that the app makes a request that causes a system UI to appear that allows the user to select a file to operate on, or (I believe) a directory tree. There is definitely some approach that the various file manager apps are using to adapt to this new world. What I'm not clear on myself is if this is a permission grant that then allows normal file IO operations to be done, or if the access has to take place through a new API path. -wilhelm -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
