Apr 25, 2014
I already searched in the Internet an answer to my problem, but unfortunately I have not found a solution for my issue. I even wrote in this case on the official forum (groups.google.com/forum/#!forum/android-developers), Unfortunately, the moderators could not cope with this problem. Below I describe the problem:
View 4 Replies
I made an application that works fine on Android 4.1, which is why I reject the problems associated with the lack of "something". For now, it seems that in newer versions of android is a bug, because after updating to Android 4.3+ (API 18+) my app shows the message:
Quote:/cache/recovery/command: open failed: EACCESS (permission denied)
My application is an system application, so the file '*.apk' was put in directory '/system/app/' together with a suitable file access permissions (chmod), so that the 'context.getApplicationInfo().flags & ApplicationInfo.FLAG_SYSTEM' is equal 1.
Because the application uses the method 'RecoverySystem.installPackage(...)' I added permissions:
<uses-permission android:name="android.permission.ACCESS_CACHE_FILE SYSTEM" />
<uses-permission android:name="android.permission.REBOOT" />
<uses-permission android:name="android.permission.DELETE_CACHE_FILE S" />
<uses-permission android:name="android.permission.RECEIVE_BOOT_COMP LETED" />
More than the required minimum, because among others my application uses the method 'RecoverySystem.verifyPackage(...)'
Also, this method had problems after updating to Android 4.3+, but these problems have been solved after adding one of (or all) permissions:
<uses-permission android:name="android.permission.WRITE_MEDIA_STORA GE"/>
<uses-permission android:name="android.permission.READ_EXTERNAL_STO RAGE" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_ST ORAGE" />
<uses-permission android:name="android.permission.MOUNT_UNMOUNT_FIL ESYSTEMS" />
I think that one of the possible reasons may be bug in the 'bootable/recovery/recovery.c', but I can not find any confirmation.