MobileRead Forums - View Single Post - Adding shortcuts to home screen doesn't work

chaley · 12-25-2019, 07:33 AM

Well, file URIs didn't work in CC when I tried changing the target release, using the Android emulator(s) in Android Studio and on my OnePlus phone. It could be that Huawei took out the restriction.

Another complication is that when using the SAF (Storage Access Framework), it is *very hard* to get a real file path. I used a hack that requires reaching into the kernel to get the mount names. I found on some devices the hack doesn't work. I don't know whether my hack will work if targeting V9 or V10. Unfortunately one must use the SAF when accessing SD card. The Android 10 "Scoped Access" documents imply (strongly) that the SAF will be needed for all storage, not just SD cards. If the hack for getting a file path doesn't work then the app must use Android's SAF content provider. The resulting URI can be handed unchanged to other apps.

At this point the problem belongs to Sam & Co. I don't know what they plan to do. I do know that I am (happily) not in the loop.

12-25-2019, 07:33 AM	#14
chaley Grand Sorcerer Posts: 12,476 Karma: 8025702 Join Date: Jan 2010 Location: Notts, England Device: Kobo Libra 2	Well, file URIs didn't work in CC when I tried changing the target release, using the Android emulator(s) in Android Studio and on my OnePlus phone. It could be that Huawei took out the restriction. Another complication is that when using the SAF (Storage Access Framework), it is very hard to get a real file path. I used a hack that requires reaching into the kernel to get the mount names. I found on some devices the hack doesn't work. I don't know whether my hack will work if targeting V9 or V10. Unfortunately one must use the SAF when accessing SD card. The Android 10 "Scoped Access" documents imply (strongly) that the SAF will be needed for all storage, not just SD cards. If the hack for getting a file path doesn't work then the app must use Android's SAF content provider. The resulting URI can be handed unchanged to other apps. At this point the problem belongs to Sam & Co. I don't know what they plan to do. I do know that I am (happily) not in the loop.