View Single Post
Old 11-10-2014, 05:15 AM   #8
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,458
Karma: 8012886
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by HarryT View Post
chaley - I see that one of the improvements in Android 5 is to allow setting permissions on folders not owned by the app. Is this likely to solve the problems with SD cards that Android 4.4 introduced, do you think?
Unknown. From what I understand, Google added a new layer of permissions based on new API. One must use "Content Providers" to access the SD card, and then use something called DocumentFile and DocumentsContract to access the files on the card. The existing File interfaces don't work with this new stuff, which means that CC would need to support two separate and different APIs to access storage.

I am not looking forward to this. Supporting new and legacy APIs is a bug-laden pain. We don't have any devices with SD cards that will run Lollipop. The emulator does not support SD cards. And so on. I am considering not trying to support it unless the existing mechanisms are now broken.
chaley is offline   Reply With Quote