In other answer INSTALL_FAILED_SHARED_USER_INCOMPATIBLE while using shared user id they describe to do: I got the solution for. 14 Android Studio解决unspecified on project app resolves to an APK archive which is not supported. May 30, 2012. INSTALL_FAILED_SHARED_USER_INCOMPATIBLE The shared user administration is kept in /data/system. [SOLVED] install failed shared user incompatible by tweakradje.

==================================================================== system 쪽과 signature mis-match 가 나서 이 어플을 loading 할 수 없다는 의미이다. 해결방법은 해당 어플도 똑같이 platform signing 을 해주는 방법밖에 없다. 그래야 system 권한을 얻을 수 있다는 의미이다. 하기와 같이 platform key 를 어디선가 구해와서 signing 해주면 된다.

(당연히 아래 platform key 가 당신의 device 에 flashing 되어 있는 image 의 signed platform key 와 동일해야 한다.) Platform key 는 어디서 구할까??? 해당 모델의 Vendor 만이 알 수 있다. Java -jar signapk.jar platform.x509.pem platform.pk8 Unsigned.apk Signed.apk 위 명령어로 생성된 Signed.apk 를 설치해주면 System 권한으로 internal api 사용이 가능하며 원하는 모든 기능이 정상 동작 될 것이다.

This paper turns from: Android to each APK process to allocate a separate user space, the userid in the manifest is the corresponding to a Linux user User ID Shared With User ID Shared, multiple APK with the same ID User can be configured to run in the same process. You can access any data from each other, and you can configure it to run into different processes, and you can access other APK's data directory.

Databases and files are the same as the access to the program. If you compile Settings or manifest ID XML user shared Android, including android.uid.shared and other system permissions, it will be reported the following error. Error: INSTALL_FAILED_UPDATE_INCOMPATIBLE Installation Error: INSTALL_FAILED_SHARED_USER_INCOMPATIBLE Installation INSTALL_FAILED_UPDATE_INCOMPATIBLE 1, because the uninstall is not complete, you can use the settings in the application, or uninstall com.android.*** ADB INSTALL_FAILED_SHARED_USER_INCOMPATIBLE Mainly due to the use of the problem caused by android.uid.shared. Solutions are as follows The first method is simple, but it needs to be compiled with make in the Android system source code: 1 modify the Android.mk file, add LOCAL_CERTIFICATE: = platform this line 2 view Android.mk file, add LOCAL_CERTIFICATE: = this line, according to the contents of this line, select the corresponding signature.

Platform----->platform.pk8 and platform.x509.pem ----->shared.pk8 shared and shared.x509.pem 3 use the platform key to re sign the APK file for the target system. This step is more troublesome, First find the key file, in the location of my Android source directory Is 'build target product security', the following platform.pk8 and platform.x509.pem Two files. Then use Signapk to provide the Android tool to signature, signapk source code is Under 'build tools signapk', Usage as '-jar signapk.jar platform.x509.pem platform.pk8 input.apk output.apk java', File name is best to use the absolute path to prevent can not find, you can modify the source code directly.

Finally, explain the principle, first of all to join android:sharedUserId= 'android.uid.system' attribute. With User ID Shared, multiple APK with the same ID User can be configured to run in the same process. So the program UID with android.uid.system, it is to make the program running in the system process, so that the right to change the system time. Just to join the UID is not enough, if this time to install APK, then found unable to install, the signature does not match, the reason is the program wants to run in the system process but also to have the target system key platform, is the above second methods mentioned platform.pk8 and platform.x509.pem two file.

With these two key signature after APK can really put into the system process. The first method to add LOCAL_CERTIFICATE: = platform is actually used these two key to sign. This also has a problem, that is, the only way to generate the program is only in the original Android system or its own system can be used to compile, because such a system can get platform. Acer Aspire Sa90 Usb Media Card Reader Driver here. pk8 and platform.x509.pem two files. If you don't even have a Android installed on the company's company. Try Android key in the original to OK, G3 has no signatures that match shared user android.uid.system in those Package, which is also the protection of the system's security. Finally, the android:sharedUserId attribute is not only the APK system can be put into the system, it can be configured to run multiple APK in a process, so that you can share data, it should be very useful In android:sharedUserId= we can see android.uid.system 'AndroidMenifest.xml' But after this sentence, you can not read and write SD card operations, such as creating a new folder in the SD card, is not successful. However, if the android:sharedUserId= 'android.uid. Big Book Disco Funk Pdf Writer. system' notes, you can use the SD card for IO operation.