OK I'm decompiling SystemUI.apk (using framework-res.apk for same ROM), once decompiled without any changes (just testing) I compile it again (opt. 11 - system - yes) and sign it and the file is 209kb instead of the original 257kb.
Problem is when I adb push it it won't install, when booting no statusbar is visible...for the life of mine I can't figure out whats wrong.
Is there a special way to compile/decompile SystemUI.apk?
Phones:
Iphone 1gen = SOLD
HTC Wildfire = SOLD
Dell Streak = BROKEN
HTC DESIRE HD = SOLD
SAMSUNG GALAXY TAB 7" = SOLD SAMSUNG GALAXY S2 = Rooted, VillainRom 1.4 - KF2 Kernel - KF2 Modem.
Replaced SGS2, 3 times already! First was scratched, second was flickering, third seems perfect *fingers crossed*
OK I'm decompiling SystemUI.apk (using framework-res.apk for same ROM), once decompiled without any changes (just testing) I compile it again (opt. 11 - system - yes) and sign it and the file is 209kb instead of the original 257kb.
Problem is when I adb push it it won't install, when booting no statusbar is visible...for the life of mine I can't figure out whats wrong.
Is there a special way to compile/decompile SystemUI.apk?
Ok are you using a sense rom? In any case you need the meta-inf and Android manifest from the original apk.
Hey guys, I'm having trouble working with Rosie.apk from an evo3d port. I have no problem decompiling or recompiling any other apks from this rom or any other, including other Rosies. For some reason, this one apk is the only one giving me problems. Here's the errors when compiling:
Code:
c:\>apktool b Rosie Rosie1.apk
I: Checking whether sources has changed...
I: Smaling...
I: Checking whether resources has changed...
I: Building resources...
libpng error: Read Error
ERROR: Failure processing PNG image c:\\Rosie\res\drawable\all_apps_divider.9.pn
g
libpng error: Read Error
ERROR: Failure processing PNG image c:\\Rosie\res\drawable-hdpi\all_apps_divider
.9.png
c:\\Rosie\res\values\public.xml:87: error: Public symbol drawable/activity_title
_bar declared here is not defined.
c:\\Rosie\res\values\public.xml:88: error: Public symbol drawable/alarm declared
here is not defined.
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutExce
ption: could not exec command: [aapt, p, -F, C:\Users\MIKEYB~1\AppData\Local\Tem
p\APKTOOL2559603846819444637.tmp, -I, C:\Users\Mikey B\apktool\framework\1.apk,
-I, C:\Users\Mikey B\apktool\framework\2.apk, -S, c:\\Rosie\res, -M, c:\\Rosie\A
ndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.jav
a:193)
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:301)
at brut.androlib.Androlib.buildResources(Androlib.java:248)
at brut.androlib.Androlib.build(Androlib.java:171)
at brut.androlib.Androlib.build(Androlib.java:154)
at brut.apktool.Main.cmdBuild(Main.java:174)
at brut.apktool.Main.main(Main.java:59)
Caused by: brut.common.BrutException: could not exec command: [aapt, p, -F, C:\U
sers\MIKEYB~1\AppData\Local\Temp\APKTOOL2559603846819444637.tmp, -I, C:\Users\Mi
key B\apktool\framework\1.apk, -I, C:\Users\Mikey B\apktool\framework\2.apk, -S,
c:\\Rosie\res, -M, c:\\Rosie\AndroidManifest.xml]
at brut.util.OS.exec(OS.java:83)
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.jav
a:191)
... 6 more
There were MANY more instances of "Public symbol drawable/* not defined" for res/values/public.xml, cut them out to size down the error log. Basically every drawable defined in the xml threw this error, but the thing is all of the drawables exist and are where they are supposed to be. Also, this is from a straight decompile and compile, no edits made. I have my sdk in PATH as well as apktool 1.4.1 in my windows dir so aapt shouldn't be a problem. Anybody have any ideas??
after build apk , does it need to signe apk or no?
Data app (third party, market app) = signed. Test sign usually works for most apks.
System app (apps that go in system/app) = not signed. Look at a couple posts above. You need to transfer original meta inf and AndroidManifest.xml from ORIGINAL apk to new one, the one in "dist" folder.
When writing an app with performance in mind, you most likely want to write it native code using the … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?