Hi,
I'm trying to install a stock Contacts.apk (from donut), in a Cyanogenmod 4 ROM (speed issues).
It fails with this message from LogCat:
Code:
D/PackageParser( 112): Scanning package: /system/app/Contacts.apk
I/PackageManager( 112): /system/app/Contacts.apk changed; collecting certs
D/PackageManager( 112): Scanning package com.android.contacts
D/PackageManager( 112): Shared UserID android.uid.shared (uid=10009): packages=[PackageSetting{43b213b8 com.android.launcher/10009}, PackageSetting{43b27250 com.android.globalsearch/10009}, PackageSetting{43b27bf8 com.android.providers.applications/10009}, PackageSetting{43b216e0 com.google.android.providers.enhancedgooglesearch/10009}, PackageSetting{43b264c0 com.android.providers.userdictionary/10009}, PackageSetting{43b21d40 com.android.contacts/10009}, PackageSetting{43b258d0 com.android.inputmethod.latin/10009}, PackageSetting{43b278d0 com.android.providers.contacts/10009}]
E/PackageManager( 112): Package com.android.contacts signatures do not match the previously installed version; ignoring!
How can I re-sign that apk, so that it can be installed?
I've googled this issue but couldn't find a fix... I just need something to get started
Thanks
Julian.
Related
working on getting the IM app instaleld..thought it might be as simple as pulling the apk and doing adb install IM.apk..it fails with a DEXOPT error, here's the logcat. Thoughts?
D/dalvikvm( 338): GC freed 8171 objects / 572600 bytes in 158ms
D/dalvikvm( 338): threadid=17 wakeup: interrupted
D/AndroidRuntime( 793):
D/AndroidRuntime( 793): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 793): CheckJNI is OFF
D/AndroidRuntime( 793): --- registering native functions ---
D/PackageParser( 58): Scanning package: /data/app/vmdl29166.tmp
I/PackageManager( 58): /data/app/vmdl29166.tmp changed; unpacking
D/installd( 36): DexInv: --- BEGIN '/data/app/vmdl29166.tmp' ---
W/dalvikvm( 800): DexOptZ: zip archive '/data/app/vmdl29166.tmp' does not inclu
de classes.dex
W/installd( 36): DexInv: --- END '/data/app/vmdl29166.tmp' --- status=0xff00,
process failed
E/installd( 36): dexopt failed on '/data/dalvik-cache/[email protected]@[email protected]
lasses.dex' res = 65280
W/PackageManager( 58): Package couldn't be installed in /data/app/com.android.
im.apk
Okay scrap that..found that classes.dex had to be there in the apk file - I grabbed the .odex from the IM app and put it in the apk as classes.dex -- right thing to do? wrong thing? now i'm getting this:
E:\>adb install E:\IM.apk
927 KB/s (0 bytes in 326585.000s)
pkg: /data/local/tmp/IM.apk
Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
adb logcat shows:
D/AndroidRuntime( 827):
D/AndroidRuntime( 827): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 827): CheckJNI is OFF
D/AndroidRuntime( 827): --- registering native functions ---
D/PackageParser( 58): Scanning package: /data/app/vmdl29167.tmp
E/PackageParser( 58): Package com.android.im has no certificates at entry clas
ses.dex; ignoring!
D/AndroidRuntime( 827): Shutting down VM
D/dalvikvm( 827): DestroyJavaVM waiting for non-daemon threads to exit
D/dalvikvm( 827): DestroyJavaVM shutting VM down
D/dalvikvm( 827): HeapWorker thread shutting down
D/dalvikvm( 827): HeapWorker thread has shut down
D/jdwp ( 827): JDWP shutting down net...
D/dalvikvm( 827): VM cleaning up
!
Does anyone have any ideas?
I've been working on getting the IM from CRB34 into 6.0r1. I really want it. But I get stuck, just like you.
Anyone wanna help us?
fwiw the IM app is definitely new. The IM app no longer includes gtalk as the gtalk app is used for that (from the HTC builds)
I'm convincing myself that someone who is online today will know more about package manager than yesterday..gogo!
You can't just rename the odex to dex and dump it into the apk file. Odex is the optimized dex file that is generated specifically for that build of a device. You'd essentially need to get a virgined dex file, or somehow fool the device into thinking its already installed and push the files.
afflaq said:
Okay scrap that..found that classes.dex had to be there in the apk file - I grabbed the .odex from the IM app and put it in the apk as classes.dex -- right thing to do? wrong thing? now i'm getting this:
E:\>adb install E:\IM.apk
927 KB/s (0 bytes in 326585.000s)
pkg: /data/local/tmp/IM.apk
Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
adb logcat shows:
D/AndroidRuntime( 827):
D/AndroidRuntime( 827): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 827): CheckJNI is OFF
D/AndroidRuntime( 827): --- registering native functions ---
D/PackageParser( 58): Scanning package: /data/app/vmdl29167.tmp
E/PackageParser( 58): Package com.android.im has no certificates at entry clas
ses.dex; ignoring!
D/AndroidRuntime( 827): Shutting down VM
D/dalvikvm( 827): DestroyJavaVM waiting for non-daemon threads to exit
D/dalvikvm( 827): DestroyJavaVM shutting VM down
D/dalvikvm( 827): HeapWorker thread shutting down
D/dalvikvm( 827): HeapWorker thread has shut down
D/jdwp ( 827): JDWP shutting down net...
D/dalvikvm( 827): VM cleaning up
Click to expand...
Click to collapse
strazzere said:
You can't just rename the odex to dex and dump it into the apk file. Odex is the optimized dex file that is generated specifically for that build of a device. You'd essentially need to get a virgined dex file, or somehow fool the device into thinking its already installed and push the files.
Click to expand...
Click to collapse
that was my fear -- any ideas on doing either of those things? dexdumping it perhaps?
afflaq said:
that was my fear -- any ideas on doing either of those things? dexdumping it perhaps?
Click to expand...
Click to collapse
I am not sure, but does it require you to install? Could you try pushing the apk and odex to apps directory and see if it shows up after reboot?
Hello,
I have found why I couldn't change HTCLaucher.apk or why the Dude's beta4 has install issue: we MUST resign all apk INCLUDE those in framework! I did it and now I have an auto rotate HTCLaucher.apk because I can use testsign.jar to resign it.
I hope it will help.
hello,
just to keep thread up.
You can just replace the apk's without resigning.
nono2lozere said:
Hello,
I have found why I couldn't change HTCLaucher.apk or why the Dude's beta4 has install issue: we MUST resign all apk INCLUDE those in framework! I did it and now I have an auto rotate HTCLaucher.apk because I can use testsign.jar to resign it.
I hope it will help.
Click to expand...
Click to collapse
Because of framework ?
I use Soulife Roger, and it's ok.
I have a little problem with all rogers rom: I can't replace HTCLauncher.apk by other Launcher.apk from TheDude 1.3RC1 or from hero theme. I have done this on haykuro 6.0H and it has worked. I tried to remove HTCLauncher.apk from /system/app and push the new Launcher.apk in it but I have this errors on logcat:
before resigning:
Code:
D/PackageParser( 79): Scanning package: /system/app/Launcher.apk
I/PackageManager( 79): /system/app/Launcher.apk changed; collecting certs
W/PackageParser( 79): Exception reading /system/app/Launcher.apk
W/PackageParser( 79): java.lang.SecurityException: META-INF/MANIFEST.MF has invalid digest for AndroidManifest.xml in /system/app/Launcher.apk
W/PackageParser( 79): at java.util.jar.JarVerifier.verifySignatures(JarVerifier.java:398)
W/PackageParser( 79): at java.util.jar.JarFile$JarFileInputStream.read(JarFile.java:124)
W/PackageParser( 79): at android.content.pm.PackageParser.loadCertificates(PackageParser.java:213)
W/PackageParser( 79): at android.content.pm.PackageParser.collectCertificates(PackageParser.java:346)
W/PackageParser( 79): at com.android.server.PackageManagerService.collectCertificatesLI(PackageManagerService.java:1734)
W/PackageParser( 79): at com.android.server.PackageManagerService.scanPackageLI(PackageManagerService.java:1783)
W/PackageParser( 79): at com.android.server.PackageManagerService.access$1200(PackageManagerService.java:104)
W/PackageParser( 79): at com.android.server.PackageManagerService$AppDirObserver.onEvent(PackageManagerService.java:3187)
W/PackageParser( 79): at android.os.FileObserver$ObserverThread.onEvent(FileObserver.java:91)
W/PackageParser( 79): at android.os.FileObserver$ObserverThread.observe(Native Method)
W/PackageParser( 79): at android.os.FileObserver$ObserverThread.run(FileObserver.java:56)
I/PackageManager( 79): Failed verifying certificates for package:com.android.launcher
after resigning:
Code:
D/PackageParser( 79): Scanning package: /system/app/Launcher.apk
I/PackageManager( 79): /system/app/Launcher.apk changed; collecting certs
D/dalvikvm( 79): GC freed 8212 objects / 532656 bytes in 203ms
D/PackageManager( 79): Scanning package com.android.launcher
D/PackageManager( 79): Shared UserID android.uid.shared (uid=10026): packages=[PackageSetting{437583a0 com.htc.CustomizationSetup/10026}, PackageSetting{4379da08 com.android.providers.im/10026}, PackageSetting{437466b8 com.android.contacts/10026}, PackageSetting{4372c9f8 com.htc.provider.CustomizationSettings/10026}, PackageSetting{437571a8 com.android.googlesearch/10026}, PackageSetting{437568c8 com.android.launcher/10026}, PackageSetting{43755d98 com.android.providers.contacts/10026}]
W/PackageManager( 79): Package com.android.launcher codePath changed from /system/app/HTCLauncher.apk to /system/app/Launcher.apk; replacing with new
E/PackageManager( 79): Package com.android.launcher has no signatures that match those in shared user android.uid.shared; ignoring!
after resigning apks in framework I can install the resigned one!
I think it's because when system boots the package installer scan framework directory before app directory and register the framework signature for android.uid.shared before scaning app. If framework has been signed with other key (release key I think) that one was used for Launcher.apk the system won't install it!
sorry for my bad english!
excuse me, but ... if i m to swap some files in / out of a signed rom,
do i have to resign everything? is resigning the update.zip good enoguh
side question: how do i specify a wallpaper for a rom?
kiddyfurby said:
excuse me, but ... if i m to swap some files in / out of a signed rom,
do i have to resign everything? is resigning the update.zip good enoguh
side question: how do i specify a wallpaper for a rom?
Click to expand...
Click to collapse
Update.zip is good enough.
For the wallpaper question, check the themes forum and search....you will find
Happy hunting
nono2lozere said:
I have a little problem with all rogers rom: I can't replace HTCLauncher.apk by other Launcher.apk from TheDude 1.3RC1 or from hero theme. I have done this on haykuro 6.0H and it has worked. I tried to remove HTCLauncher.apk from /system/app and push the new Launcher.apk in it but I have this errors on logcat:
Click to expand...
Click to collapse
Hi,
Have you find a solution for that ? I have the same problem...
If i'm not resign the apk, i get an error like "no signatures that match those in shared user android.uid.shared" for those packages i'm trying to install, and if i'm resign all the apk, i have the same error but for all..
I'm want to find/replace the root certificate, and replace it if possible, but i don't know how..
plus, i've found some apks and jars dont like to be signed with test-keys (all framework jars/apks and launcher.apk). It usually breaks things. Like mikey said, usually just the update zip is fine
I was curious if anyone has found a solution to re-signing all the apk's on the Rogers builds. Soulife, Enomther & I have been looking at this so we could include irrenhaus' Advanced Launcher v17 as a replacement for the stock HTCLauncher. If you have your phone setup & running, and flash the launcher as an update afterwards, it'll run fine. But as soon as you wipe or try to start clean, the phone will go into boot loops. If you resign all the apk's in /system/app & /system/framework, you can included the Launcher as a replacement for HTCLauncher and it will flash/boot w/ no problems until you want to sign into google or access the market. You can't. Same thing happens when you try to update the stock HTCLauncher when editing the AndroidManifest.xml file to enable auto-rotation. Re-sign the apk & it'll work fine till you wipe. Any suggestions would be appreciated. Thanks & take care.
Hello !!
I installed Link2SD on my Acer liquid E (running LiquidNext 1.9.2).
linked 5 apps.
But after rebooting, Titanium autmoatically crashes, as well as other apps!!
I could not understand what the problem is !
could you please help me ?
Logcat attached
Firstly, I would actually like to thank you on taking the efforts on getting a logcat...
Loads of members nowadays think that their problem is our problem, and hence don't put in efforts in even explaining...
On the other hand, you actually did a good thing :thumbup::good:
Even though I'm not too knowledgeable on such technical stuff, I did go through your logcat (for the simple reason that you took efforts in attaching it in the first place)...
I've (hopefully) identified the problem areas:
Code:
I/Vold ( 284): Vold 2.1 (the revenge) firing up
D/Vold ( 284): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 284): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 284): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
W/Vold ( 284): Ignoring unknown switch 'MSM72K_UDC'
.
.
.
.
I/Installer( 347): connecting...
E/PackageManager( 347): Package com.keramidas.TitaniumBackup has mismatched uid: 0 on disk, 10042 in settings
I/PackageManager( 347): Linking native library dir for /data/app/com.keramidas.TitaniumBackup-1.apk
I/PackageManager( 347): Time to scan packages: 7.069 seconds
W/PackageManager( 347): Unknown permission com.android.vending.permission.UPDATE_MARKET_FAILURE in package com.android.vending.updater
W/PackageManager( 347): Unknown permission android.permission.ADD_SYSTEM_SERVICE in package com.android.phone
W/PackageManager( 347): Unknown permission android.permission.READ_EXTERNAL_STORAGE in package com.cyanogenmod.cmparts
W/PackageManager( 347): Not granting permission android.permission.SEND_DOWNLOAD_COMPLETED_INTENTS to package com.android.browser (protectionLevel=2 flags=0x9be45)
W/PackageManager( 347): Unknown permission com.google.android.gm.permission.READ_GMAIL in package com.google.android.talk
W/PackageManager( 347): Unknown permission android.permission.READ_OWNER_DATA in package com.android.setupwizard
W/PackageManager( 347): Unknown permission android.permission.WRITE_OWNER_DATA in package com.android.setupwizard
W/PackageManager( 347): Unknown permission com.google.android.gm.permission.WRITE_GMAIL in package com.android.settings
W/PackageManager( 347): Unknown permission com.google.android.gm.permission.READ_GMAIL in package com.android.settings
W/PackageManager( 347): Unknown permission com.google.android.gm.permission.READ_GMAIL in package com.google.android.apps.uploader
W/PackageManager( 347): Unknown permission com.google.android.voicesearch.SHORTCUTS_ACCESS in package com.google.android.googlequicksearchbox
W/PackageManager( 347): Unknown permission android.permission.READ_EXTERNAL_STORAGE in package com.android.vending
W/PackageManager( 347): Not granting permission android.permission.SEND_DOWNLOAD_COMPLETED_INTENTS to package com.android.vending (protectionLevel=2 flags=0xabec5)
W/PackageManager( 347): Unknown permission android.permission.SEND_SMS_NO_CONFIRMATION in package com.android.vending
W/PackageManager( 347): Not granting permission android.permission.STATUS_BAR to package com.android.vending (protectionLevel=3 flags=0xabec5)
W/PackageManager( 347): Not granting permission android.permission.PACKAGE_USAGE_STATS to package com.android.vending (protectionLevel=2 flags=0xabec5)
W/PackageManager( 347): Unknown permission android.permission.PACKAGE_VERIFICATION_AGENT in package com.android.vending
W/PackageManager( 347): Unknown permission com.google.android.verifier.permission.UPDATE_VERIFIER in package com.android.vending
W/PackageManager( 347): Not granting permission android.permission.INSTALL_PACKAGES to package com.chelpus.lackypatch (protectionLevel=3 flags=0xbe46)
W/PackageManager( 347): Not granting permission android.permission.DELETE_PACKAGES to package com.chelpus.lackypatch (protectionLevel=3 flags=0xbe46)
W/PackageManager( 347): Not granting permission android.permission.CLEAR_APP_USER_DATA to package com.chelpus.lackypatch (protectionLevel=2 flags=0xbe46)
W/PackageManager( 347): Unknown permission android.permission.READ_OWNER_DATA in package com.android.email
W/PackageManager( 347): Not granting permission android.permission.DEVICE_POWER to package com.android.deskclock (protectionLevel=2 flags=0x8be45)
(I've put in dots .... to just state that there isn't any error there)
From what I've seen, I believe that your partition (since you are using link2sd) isn't formatted properly (or mounted)...and titanium was linked to your partition (am I right?)
Do your system apps also force close?
There's an error with the status bar...
And ya, because of that logcat, I hope we see more of such members in the future :beer:
I agree. I am thinking that your partitions are not set up correctly. IIRC from when I used Link2Sd, you had to have 1-Fat32 for normal stuff and 1-Fat32 for the apps to link too. In older versions it was Fat32, Ext2/3 and the Swap.
When you installed Link2Sd, and it checked for partitions, did it throw any errors? Does your ROM support Link2SD? I'll look around at it some more but A.cid asked for some help.
Thank you both guys for replying in such a kind way: i appreciate!
I am running this MOD: LiquidNext (latest version 1.9.2)
forum thread about the rom here
It seems to be possible to run link2SD on the above ROM.
Other apps crash as well, but I honestly can't recall whether they were system apps or not.
I have now resetted everything:
I have wiped everything, both internal and external memories (8GB SDcard).
I have formatted the sd card from the CWM Recovery (touch): EXT3 1024 MB, Swap: 0 MB, FAT32 remaining space.
I have flashed the same rom again, and haven't yet installed link2sd and Titanium.
so far everything is running smoothly, but I want to understand what's wrong when I install link2sd!
I have been running it smoothly in the past on the same ROM => then something mysterious happened
hope you guys are better than me and can find the culprit !!
Corrupt partition. Removing the link2sd script from init.d will be a temporary fix. You need to reformat your ext partition!
___________XDA Premium__________
Don't be a noob. Be a newbie..!!
Details here.
____________________________________
shaaan said:
Corrupt partition. Removing the link2sd script from init.d will be a temporary fix. You need to reformat your ext partition!
Click to expand...
Click to collapse
already done !!
thanks though
Hey, I know that this isn't your device but there may be somethings in this trhead that will help you troubleshoot, like kernel modules and proper partition setup. This was my first Android device so you might see a post or two in there from me way back when.
[GUIDE] Link2SD on milestone XT 720
Woodrube said:
Hey, I know that this isn't your device but there may be somethings in this trhead that will help you troubleshoot, like kernel modules and proper partition setup. This was my first Android device so you might see a post or two in there from me way back when.
[GUIDE] Link2SD on milestone XT 720
Click to expand...
Click to collapse
Thank you but that was not of much help !!
I still haven't managed to get Link2SD to work correctly!!
help me please
Hello, I am trying to install certain apps on my phone. I have the apk but when I try to install it says "app not installed".
So I tried installing through adb.
but it says
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
Logcat says
D/AndroidRuntime( 5674): Calling main entry com.android.commands.pm.Pm
W/ActivityManager( 568): No content provider found for permission revoke: file:///data/local/tmp/SamsungCamera.apk
W/ActivityManager( 568): No content provider found for permission revoke: file:///data/local/tmp/SamsungCamera.apk
D/dalvikvm( 568): GC_CONCURRENT freed 2684K, 38% free 14829K/23555K, paused 3ms+8ms, total 86ms
D/dalvikvm( 568): GC_CONCURRENT freed 3013K, 37% free 14985K/23555K, paused 3ms+5ms, total 78ms
D/dalvikvm( 568): WAIT_FOR_CONCURRENT_GC blocked 55ms
E/PackageManager( 568): Package com.sec.android.app.camera requires unavailable shared library seccamera; failing!
W/PackageManager( 568): Package couldn't be installed in /data/app/com.sec.android.app.camera-1.apk
I tried to uninstall the com.sec.android.app.camera-1.apk it mentioned
but it says
D/AndroidRuntime( 5703): Calling main entry com.android.commands.pm.Pm
W/PackageManager( 568): Package named 'com.sec.android.app.camera-1.apk' doesn't exist.
This is the samsung camera app, its better than the default camera app (well I like it better) and want to install it on an android rom (so not the samsung rom)
Any help or ideas would be appreciated.
Thanks
Certain Touchwiz apps (including camera) won't work on AOSP or AOKP or any non touchwiz ROM. It doesn't have the proprietary framework I believe
Sent from my MB508 using xda premium
Would you know any way to pinpoint what files it depends on?
It would require a touchwiz ROM, framework of AOSP and touchwiz/sense/motowhatever cannot coexist
Sent from my DROID2 using xda premium
I have the same problem. But wow, I found a topic from 2012. But, I have a completely different device and a different version of android)
Hi,
I'm trying to modify the AOSP ICS launcher. I've downloaded the ICS source tree and built Launcher2 as is. However, when I try to install it in an Android device(a stock Samsung Galaxy S3 running stock ICS, and a HTC Desire Z running Andromadus mimicry 1.5.0 based on ICS) using "adb install", I get a INSTALL_FAILED_DEXOPT installation error. Logcat output from the Galaxy S3 is as follows:
Code:
D/AndroidRuntime( 5431):
D/AndroidRuntime( 5431): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
D/AndroidRuntime( 5431): CheckJNI is OFF
D/AndroidRuntime( 5431): setted country_code = France
D/AndroidRuntime( 5431): setted countryiso_code = FR
D/AndroidRuntime( 5431): setted sales_code = XEF
D/AndroidRuntime( 5431): readGMSProperty: start
D/AndroidRuntime( 5431): readGMSProperty: already setted!!
D/AndroidRuntime( 5431): readGMSProperty: end
D/LibQmg_native( 5431): register_android_app_LibQmg
D/AndroidRuntime( 5431): Calling main entry com.android.commands.pm.Pm
W/PackageManager( 2093): verifying app can be installed or not
I/ApplicationPolicy( 2093): isApplicationInstallationEnabled
D/dalvikvm( 2093): GC_CONCURRENT freed 7885K, 31% free 32346K/46791K, paused 2ms+6ms
D/dalvikvm( 2093): GC_CONCURRENT freed 1834K, 31% free 32555K/46791K, paused 3ms+5ms
E/PackageManager( 2093): Package XXX.XXXXXXX.XXXXXXXX has mismatched uid: 10130 on disk, 10131 in settings
I/PackageManager( 2093): Running dexopt on: XXX.XXXXXXX.XXXXXXXX
I/PackageManager( 2093): Linking native library dir for |XXXX|XXX|XXXXXXXXXXXXXXXXXXXXXX.XXX
W/dalvikvm( 5442): DexOptZ: zip archive '/data/app/com.android.launcher-1.apk' does not include classes.dex
W/installd( 1907): DexInv: --- END '/data/app/com.android.launcher-1.apk' --- status=0xff00, process failed
E/installd( 1907): dexopt failed on '/data/dalvik-cache/[email protected]@[email protected]' res = 65280
W/PackageManager( 2093): Package couldn't be installed in /data/app/com.android.launcher-1.apk
Does anyone know how to build and install the AOSP launcher on non Nexus devices?
Thanks.
It looks like the apk you built was deodexed but was missing a classes.dex file. And when the installer tried to create an odex file it couldn't because the apk didn't contain instructions on how to.
That's my interpretation of the log for you, although I can't answer you question. Sorry.
Wouldn't this be better in q&a section? Also regarding the launcher I'm pretty sure you can just install the unmodified apk as is by enabling install from unknown sources and placing the apk on your memory card, or just use one of the plethora of stock based home launchers like apex, trebuchet, nova, adw or holo launcher just to name a few.
Sent from my LT30p using xda app-developers app
razz, there's actually a .apk file and a .odex file in the out directory after I build the app. Is the .odex file what it's trying to look for? Is there any way I can include it in the apk, or direct the installer to its location so that it doesn't throw the error? I'm guessing the apk is currently odexed since there's an .odex file, and I need to deodex it? If so, how can I do this?
Galcactus, I'm trying to modify the stock AOSP launcher, hence getting it to install on an Android device unmodified is my first step.
I thought I could install it as is as well, however I keep getting this error. I've tried pushing the apk to my memory card and using a file manager/app installer app to install it but no go as well.
Anyone? Thanks.