Moving system apk from stock 4.0 to CM 11 - Android Q&A, Help & Troubleshooting

Hi,
I got CM 11 running on my devices (Nexus Q) and want to add some system apk from the stock factory images and need some help. I mounted the factory image and copied TungstenLEDService.apk from /system/app to my computer and tried to install it over adb. This is what I have done so far.
Code:
adb install TungstenLEDService.apk
but it fails with INSTALL_FAILED_SHARED_USER_INCOMPATIBLE error. Ok fine, its a system apk, so I did the following.
I enabled root over adb on developer settings on the device and from the terminal I did
Code:
adb push TungstenLEDService.apk /sdcard/
adb shell
su
mount -o rw,remount -t ext4 /system
cp /sdcard/TungstenLEDService.apk /system/app/
And then I set the permission with Solid Explorer filemanager to -rw-r--r-- on TungstenLEDService.apk and rebooted. From logcat I got this error
Code:
Package com.google.tungsten.ledservice has no signatures that match those in shared user android.uid.system; ignoring!
What to do next? Do I need to resign the apk? How do I do that? I have not modified the apk in any way and the CM 11 build is from this xda thread: http://forum.xda-developers.com/showthread.php?t=2596910

---

mannberg said:
Hi,
I got CM 11 running on my devices (Nexus Q) and want to add some system apk from the stock factory images and need some help. I mounted the factory image and copied TungstenLEDService.apk from /system/app to my computer and tried to install it over adb. This is what I have done so far.
Code:
adb install TungstenLEDService.apk
but it fails with INSTALL_FAILED_SHARED_USER_INCOMPATIBLE error. Ok fine, its a system apk, so I did the following.
I enabled root over adb on developer settings on the device and from the terminal I did
Code:
adb push TungstenLEDService.apk /sdcard/
adb shell
su
mount -o rw,remount -t ext4 /system
cp /sdcard/TungstenLEDService.apk /system/app/
And then I set the permission with Solid Explorer filemanager to -rw-r--r-- on TungstenLEDService.apk and rebooted. From logcat I got this error
Code:
Package com.google.tungsten.ledservice has no signatures that match those in shared user android.uid.system; ignoring!
What to do next? Do I need to resign the apk? How do I do that? I have not modified the apk in any way and the CM 11 build is from this xda thread: http://forum.xda-developers.com/showthread.php?t=2596910
Click to expand...
Click to collapse
3 things that are probably causing issues.
1) it's a signed factory apk, and is looking for a factory rom to work on. You can try re-signing it using basic "test" signature. Also, make sure the apk is "deodexed".
2) Just incompatible with version 4.4 KitKat. In this case, you would probably have to re-write a lot of code.
3) Decompile and check the Android Manifest for anything unusual. Also, while decompiled, check all the folders for the last error message you posted. Might be a clue in there.

---

Moscow Desire said:
1) it's a signed factory apk, and is looking for a factory rom to work on. You can try re-signing it using basic "test" signature. Also, make sure the apk is "deodexed".
Click to expand...
Click to collapse
How do I deodex the apk / odex files? Any good and easy guides out there? Im a neewbie. Tell me like I'm 4 years old The apk / odex files is from android version 4.0.4
Signing with test signature, do you mean something like this
Code:
jarsigner -keystore ~/.android/debug.keystore -storepass android -keypass android TungstenLEDService.apk androiddebugkey
after the apk is deodoxed?
Moscow Desire said:
2) Just incompatible with version 4.4 KitKat. In this case, you would probably have to re-write a lot of code.
Click to expand...
Click to collapse
I hope not.
Moscow Desire said:
3) Decompile and check the Android Manifest for anything unusual. Also, while decompiled, check all the folders for the last error message you posted. Might be a clue in there.
Click to expand...
Click to collapse
I didnt see anything special in the Manifest, it looks like the one I posted below. Do I need to change android:versionCode and android:versionName?
Code:
<?xml version="1.0" encoding="utf-8"?>
<manifest android:sharedUserId="android.uid.system" android:versionCode="15" android:versionName="4.0.4-403218" package="com.google.tungsten.ledservice"
xmlns:android="http://schemas.android.com/apk/res/android">
<uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" />
<uses-permission android:name="android.permission.BROADCAST_STICKY" />
<application android:label="Tungsten LED Service">
<service android:name=".LEDService" android:exported="true">
<intent-filter>
<action android:name="com.google.tungsten.LedService" />
</intent-filter>
</service>
<receiver android:name="BootReceiver">
<intent-filter>
<action android:name="android.intent.action.BOOT_COMPLETED" />
</intent-filter>
</receiver>
<service android:name="com.google.tungsten.ledservice.TungstenLedContainer" android:enabled="true" android:exported="true">
<intent-filter>
<action android:name="com.android.athome.START_SERVICE" />
</intent-filter>
<meta-data android:name="com.android.athome.service" android:resource="@xml/connector_info" />
</service>
</application>
</manifest>

---

mannberg said:
How do I deodex the apk / odex files? Any good and easy guides out there? Im a neewbie. Tell me like I'm 4 years old The apk / odex files is from android version 4.0.4
Click to expand...
Click to collapse
Ha! Can't do that mate. Have to work!
Now, here is what I use for pretty much all my needs when it comes to working with apks and other things.
http://forum.xda-developers.com/showthread.php?t=1619473
They have a pretty good support here at XDA, and also their own website. This saves you having to find all these apktools and such for decompiling, deodexing and stuff, which is a real pain. I use it under Win 7. Might have to install the latest version of Microsoft.net though.
First thing, is make sure your apk is deodexed or not. If it's not, you will see an odex file with the same name in your system folder of your old 4.0.4 files. If it's not, you'll need to deodex it before decompiling. If there's not an odex file, then you can go straight to decompiling. Then, you can look in all the folders and such. Then recompile it back, using the test keys for signing.
As with the manifest, it's possible you need to change the android versions. But the message you had, seems to be looking for something signed specifically for that 4.0.4. Probably a factory signed framework or systemUI.
CM uses unsigned files, or files signed using random testkeys.
You can also check XDA University about porting apps to KitKat. Lots of these folks do this, and port to other devices, so hopefully somebody there can tell you more. Or check the General Android Application Development forums.
MD

---

I dedoxed the apk and odex files. Changed the manifest and removed the sharedUserId and rebuilt the apk, signed with a test key. Then I copied the the apk to /system/app. So far everything is fine.
I tried to launch the service (tungsten.ledservice) with
Code:
adb shell am startservice -n com.google.tungsten.ledservice/.TungstenLedContainer
and when I check ps in adb shell I see a process called com.google.tungsten.ledservice. But nothing happens when I change the volyme. It should change the leds on the Nexus Q. I checked adb logcat and found this in the log.
Code:
D/AndroidRuntime( 2626):
D/AndroidRuntime( 2626): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
D/AndroidRuntime( 2626): CheckJNI is OFF
D/dalvikvm( 2626): Trying to load lib libjavacore.so 0x0
D/dalvikvm( 2626): Added shared lib libjavacore.so 0x0
D/dalvikvm( 2626): Trying to load lib libnativehelper.so 0x0
D/dalvikvm( 2626): Added shared lib libnativehelper.so 0x0
D/dalvikvm( 2626): No JNI_OnLoad found in libnativehelper.so 0x0, skipping init
E/cutils-trace( 2626): Error opening trace file: No such file or directory (2)
D/dalvikvm( 2626): Note: class Landroid/app/ActivityManagerNative; has 180 unimplemented (abstract) methods
E/memtrack( 2626): Couldn't load memtrack module (No such file or directory)
E/android.os.Debug( 2626): failed to load memtrack module: -2
D/AndroidRuntime( 2626): Calling main entry com.android.commands.am.Am
D/AndroidRuntime( 2626): Shutting down VM
This service use some library from /system/lib/, libled_service_jni.so and libtungsten_led.so. I guess some changes were made to the jni stuff between android 4.0.4 and 4.4. Is this fixable? Is it the java code that fails or the compiled c librarys?