Unpacking and copying app contents causes app to appear hung

[kollivier]

We have an app that has a lot of data files, and we support preloading our app on devices without internet access, so the Play restrictions do not apply and furthermore we cannot rely on downloadable asset packs. When the app is first loaded, the unpack and copy of all the app's data files to the /data partition causes the app to appear hung for upwards of 1 minute because the unpack happens in onCreate. Having an app display a blank screen for any real length of time, much less a minute or more, gives a pretty bad first impression.

My understanding is that the technical reason for this process is that fopen and co. will not directly open files on Android because of the need to use AssetManager, so this is worked around by moving all the files to a place where files are directly accessible. I've found another cross-platform app developer who addressed this by devising a drop-in replacement for the fopen series of functions that use the asset manager under the hood.

http://www.50ply.com/blog/2013/01/19/loading-compressed-android-assets-with-file-pointer/#comment-1850768990

Would something like this be an option? Or perhaps a slightly more advanced version that tries the asset manager only for certain paths, or falls back to fopen when that fails? I've spoken with @inclement and others on kivy-dev about this, but I wanted to open a ticket to track this issue as we will really need to get this fixed to continue using p4a.

[inclement]

As far as I know, something like that could work but needs some hacking to test it out.

[kollivier]

Cool, I'll probably start playing with adding an experimental --nozip option for p4a that just puts all the files in the assets folder. Once I get to the point where it's giving file access errors, I'll start playing around with  this and seeing what might work. For patched software like Python 2, do you have a repo where you maintain the patches or do you basically just download the tarball, apply the patches, and then just make new ones each time there's a change like this? From: Alexander Taylor <notifications@github.com> Reply-To: kivy/python-for-android <reply@reply.github.com> Date: Monday, January 16, 2017 at 3:21 PM To: kivy/python-for-android <python-for-android@noreply.github.com> Cc: kollivier <kevino@theolliviers.com>, Author <author@noreply.github.com> Subject: Re: [kivy/python-for-android] Unpacking and copying app contents causes app to appear hung (#983) As far as I know, something like that could work but needs some hacking to test it out. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[inclement]

For patched software like Python 2, do you have a repo where you maintain the patches or do you basically just download the tarball, apply the patches, and then just make new ones each time there's a change like this?

Just the latter one, so you can make new patches by downloading the tarball, adding the relevant files to a repo, committing any changes and getting the patch with git diff.

[inclement]

Closing as resolved by #990