I tried the following: In the sample's onCreate() method, i created the mentioned file in the cache-dir (0 size, readable, writable, executable). This got rid of the original error-message. But instead, it complained about the cache-file being too small and the sample still crashes.
Then I put a megabyte of 0-values into that cache-file (no longer a 0 size). This got rid of the 'being too small' error, but it started complaining about an incorrect magic cookie value in the cache-file. The sample still crashes. The cache-file can be created (there are no permission issues here). And when the cache-file is there, the sample actually use it as-is. It seems there is some sort of bug that opens the cache-file willy-nilly without properly checking for its existence (and failing to create one when necessary). *Is there some (renderscript) call we need to do to make sure a proper cache-file is initially created for the given project?* Thanks! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
