Openening a video is done in a "strange" mode

[brunetton]

Sorry for this strange bug title! Feel free to rectify it.

For each video found thanks to Disk Usage, I'm using Simple Gallery to open videos in order to delete it or backup it with Google photo (using Simple Gallery's open with option).

But Simple Gallery doesn't seems to "have write access to the file". It doesn't shows delete button, and if I open the file with Google photo, I'm unable to backup it (nor deleting it).

Is this intended? I'm guessing that this is maybe to keep Storage Analyser display consistent: delete can only be done from the app so files listed are existing files.

But I don't care about having an outdated list of files. I don't care having error messages when I click on a file I just deleted from another app. This is totally fine.

If this is intended, I think that an option to disable this could be very useful! Thanks a lot

[IvanVolosyuk]

I believe you are talking about diskusage version 5.0-alpha1.
Looks like in recent versions of android I cannot expose a writable URL to another app - system blocks this attempts, thus the URL I provide is kinda scoped URL which is very limited in nature. This is kinda sad as from diskusage it would be nice to be able to delete big files. I just don't know how to do that with the new locked down APIs.

[brunetton]

Thanks for your answer. Yes I'm talking about 5.0-alpha1, sorry for not mentioning that. I'm not an Android dev so I can't really help here. Maybe looking to how other open-source apps does? Like Simple Gallery typically? Or I won't be disturbed seeing an option to use "old" Android API. This is quite common, I've already seen this kind of option. Anyway, thank you! Le lun. 18 déc. 2023 à 03:34, Ivan Volosyuk ***@***.***> a écrit :

…

I believe you are talking about diskusage version 5.0-alpha1. Looks like in recent versions of android I cannot expose a writable URL to another app - system blocks this attempts, thus the URL I provide is kinda scoped URL which is very limited in nature. This is kinda sad as from diskusage it would be nice to be able to delete big files. I just don't know how to do that with the new locked down APIs. — Reply to this email directly, view it on GitHub <#88 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAVCMSYRBIX3YYQNRLUWATYJ6TUDAVCNFSM6AAAAABAYZOV5WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJZGQ2TAMRRGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[IvanVolosyuk]

I can have a look at Simple Gallery, is it this one: https://github.com/SimpleMobileTools/Simple-Gallery I can guess that the difference is being kinda a file manager and delegating permissions to other apps. This is specifically prohibited in the new android versions and the old API doesn't work anymore. I don't develop much on android these days, so I don't have much knowledge about this very specific mode the file managers are forced to operate in.

…

On Mon, Dec 18, 2023 at 8:10 PM Bruno Duyé ***@***.***> wrote: Thanks for your answer. Yes I'm talking about 5.0-alpha1, sorry for not mentioning that. I'm not an Android dev so I can't really help here. Maybe looking to how other open-source apps does? Like Simple Gallery typically? Or I won't be disturbed seeing an option to use "old" Android API. This is quite common, I've already seen this kind of option. Anyway, thank you! Le lun. 18 déc. 2023 à 03:34, Ivan Volosyuk ***@***.***> a écrit : > I believe you are talking about diskusage version 5.0-alpha1. > Looks like in recent versions of android I cannot expose a writable URL to > another app - system blocks this attempts, thus the URL I provide is kinda > scoped URL which is very limited in nature. This is kinda sad as from > diskusage it would be nice to be able to delete big files. I just don't > know how to do that with the new locked down APIs. > > — > Reply to this email directly, view it on GitHub > < #88 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AAAVCMSYRBIX3YYQNRLUWATYJ6TUDAVCNFSM6AAAAABAYZOV5WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJZGQ2TAMRRGE> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> > — Reply to this email directly, view it on GitHub <#88 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABXQ6HNY4GNALNSP2YYC55LYKACATAVCNFSM6AAAAABAYZOV5WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJZHA2TONRQGY> . You are receiving this because you commented.Message ID: ***@***.***>

[brunetton]

Yes it's this one (the link was in my first message 😜)