Develop Bugs

[Q] Problems recompiling cm9 (themed) framework-res.apk

Attempting to toggle on the soft buttons in Nashdogg's CM9 b1 Blue Mist theme.
No problems decompiling and editing the appropriate xmls.
But I keep getting errors when I go to recompile the changes to the theme's framework.framework-res.apk. (apkmultitool and aapt).
Any suggestions?
Thx!

make sure you have the ics apktool.jar
Sent from a phone with kNOw CiQ k0nane...

Okay but that's not nashdoggs theme that's gooch's theme. Also try using apkmanager... let me get a link with my apk manager.
http://db.tt/EKvaxWIc
Once you unzip everything is in the folder in the other folder run the framework-if batch file then place the framework.apk in the place for modding. Open the script batch file choose the framework-res as your 0project [22] then decompile [9] edit it recompile [11] and it should work. Oh and the folder for editing appears in the project folder and the recompiled will appear in the modding folder name "unsignedFramework.apk". Oh and if it asks if its a system app hit n its not.
Sent from my SPH-D700 using xda premium

You can't recompile a themed framework. You need a clean framework
Sent from my Nexus S 4G using Tapatalk

GituSum said:
You can't recompile a themed framework. You need a clean framework
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
you can compile themed frameworks with apktool, I didnt think so at first either.
Sent from a phone with kNOw CiQ k0nane...

Big Goron said:
Okay but that's not nashdoggs theme that's gooch's theme.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Totally meant gooch. Knew there was a g and an o in the name ;-)
Ton of fires today. Hope to test this out tomorrow.
Thanks alla yous for your suggestions!
sent from my fully armed and operational space phone

I can decompile/recompile the soft buttons modded apk, but get compile error (specified file is missing) when I decompile/recompile gooch's theme. (Not altering anything - just getting a control test)
Tomorrow, time permitting, ill take the apk from the rom and move each of the two modded apks' changes over.
Thanks for the download, Big G
sent from my fully armed and operational space phone

Is the error in red? What is the file its saying is missing? If its signedframework or unsignedframework.. ignore that its nothing.
Sent from my SPH-D700 using xda premium

Big Goron said:
Is the error in red? What is the file its saying is missing? If its signedframework or unsignedframework.. ignore that its nothing.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Heh -- wrote my message whilst walking the dog -- didn't want to misquote myself without specific examples.
But, yep -- all red
c:\android\apkmanager\other\..\projects\sb_framework-res.apk\res\values\public.xml:4536: error: Public symbol drawable/zoom_plate declared here is not defined.
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutException: could not exec command: [aapt, p, -F, C:\Users\ASCHIL~1\AppData\Local\Temp\APKTOOL8847823845691568917.tmp, -x, -S, c:\android\apkmanager\other\..\projects\sb_framework-res.apk\res, -M, c:\android\apkmanager\other\..\projects\sb_framework-res.apk\AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java: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:182)
at brut.apktool.Main.main(Main.java:67)
Caused by: brut.common.BrutException: could not exec command: [aapt, p, -F, C:\Users\ASCHIL~1\AppData\Local\Temp\APKTOOL8847823845691568917.tmp, -x, -S, c:\android\apkmanager\other\..\projects\sb_framework-res.apk\res, -M, c:\android\apkmanager\other\..\projects\sb_framework-res.apk\AndroidManifest.xml]
at brut.util.OS.exec(OS.java:83)
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:191)
... 6 more
Click to expand...
Click to collapse
Looks to be the pngs in the themed app. I ran #2 to optimize images, but that didn't do diddly.
Gonna look at Draw-9 patch later.

Unable to recompile SystemUI.apk using apktool

I have been using apktool 1.4.3 to decompile and recompile framework-res.apk without any problem.
However while I can decompile SystemUI.apk without problem, I cannot recompile it. The error is shown below.
I have done searching in this forum but still can't find the solution.
Please kindly help thanks.
Code:
C:\apktool>apktool b systemui.apk
Exception in thread "main" brut.androlib.AndrolibException: brut.directory.PathN
otExist: apktool.yml
at brut.androlib.Androlib.readMetaFile(Androlib.java:142)
at brut.androlib.Androlib.build(Androlib.java:159)
at brut.androlib.Androlib.build(Androlib.java:154)
at brut.apktool.Main.cmdBuild(Main.java:182)
at brut.apktool.Main.main(Main.java:67)
Caused by: brut.directory.PathNotExist: apktool.yml
at brut.directory.AbstractDirectory.getFileInput(AbstractDirectory.java:
103)
at brut.androlib.Androlib.readMetaFile(Androlib.java:138)
... 4 more
C:\apktool>

Sorry if I posted on wrong sub-forum

Have you tried recompiling with version 1.4.2?

who_mike_d said:
Have you tried recompiling with version 1.4.2?
Click to expand...
Click to collapse
The error still exists thanks

nighos said:
The error still exists thanks
Click to expand...
Click to collapse
Check if you set the right path for java
Its sometimes in program files or programs x86
Check the portal news. There was an article of an modded apktool version specially for ics
I had the same errors like you
Had these path settings wrong

Leave off the .apk. To compile the SystemUI folder type 'apktool b SystemUI'. Its also case sensitive
Sent from my Galaxy Nexus using xda premium

nbeebe24 said:
Leave off the .apk. To compile the SystemUI folder type 'apktool b SystemUI'. Its also case sensitive
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You are right! Such a stupid mistake
Thanks

nbeebe24 said:
Leave off the .apk. To compile the SystemUI folder type 'apktool b SystemUI'. Its also case sensitive
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I didn't even notice he did that, that should fix the problem
Sent from my Galaxy Nexus using XDA

nighos said:
You are right! Such a stupid mistake
Thanks
Click to expand...
Click to collapse
No problem
Sent from my Galaxy Nexus using xda premium

i got the same error however i did not write ".apk" at the end of line.
Code:
C:\Users\x\Desktop\Apktool>apktool b SystemUI
I: Checking whether sources has changed...
I: Smaling...
Exception in thread "main" java.lang.NullPointerException
at org.jf.util.PathUtil.getRelativeFile(PathUtil.java:44)
at org.jf.smali.smaliFlexLexer.getSourceName(smaliFlexLexer.java:2922)
at org.antlr.runtime.CommonTokenStream.getSourceName(CommonTokenStream.j
ava:345)
at org.antlr.runtime.tree.CommonTreeNodeStream.getSourceName(CommonTreeN
odeStream.java:106)
at org.antlr.runtime.tree.TreeParser.getSourceName(TreeParser.java:78)
at org.jf.smali.smaliTreeWalker.getErrorHeader(smaliTreeWalker.java:372)
at org.antlr.runtime.BaseRecognizer.displayRecognitionError(BaseRecogniz
er.java:192)
at org.antlr.runtime.BaseRecognizer.reportError(BaseRecognizer.java:186)
at org.jf.smali.smaliTreeWalker.smali_file(smaliTreeWalker.java:451)
at brut.androlib.mod.SmaliMod.assembleSmaliFile(SmaliMod.java:85)
at brut.androlib.src.DexFileBuilder.addSmaliFile(DexFileBuilder.java:43)
at brut.androlib.src.DexFileBuilder.addSmaliFile(DexFileBuilder.java:33)
at brut.androlib.src.SmaliBuilder.buildFile(SmaliBuilder.java:64)
at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:48)
at brut.androlib.src.SmaliBuilder.build(SmaliBuilder.java:35)
at brut.androlib.Androlib.buildSourcesSmali(Androlib.java:222)
at brut.androlib.Androlib.buildSources(Androlib.java:179)
at brut.androlib.Androlib.build(Androlib.java:170)
at brut.androlib.Androlib.build(Androlib.java:154)
at brut.apktool.Main.cmdBuild(Main.java:182)
at brut.apktool.Main.main(Main.java:67)
C:\Users\x\Desktop\Apktool>
just changed an icon inside drawable-hdpi

try using this set of apk tools. this works great for me with ICS & Jelly Bean. And also make sure your SDK's are up to date. extract the folder from the zip file and use normally.

jase33 said:
try using this set of apk tools. this works great for me with ICS & Jelly Bean. And also make sure your SDK's are up to date. extract the folder from the zip file and use normally.
Click to expand...
Click to collapse
same problem
i uploaded apk,
i decompile, change an icon from drawable, but cannot recompile.

Actually, You don't need to decompile/recompile to change the images, brother. Just change SystemUI.apk to SystemUI.zip. Extract it. Edit the images you want to change. Drag the edit images into the .zip and in compression level select store. It will replace the files in .zip. Change .zip back to .apk. Try it now, it should work.
PS: Selecting store means it doesn't compress the images, Dragging the edited images into the .zip, selecting store and stuff isn't necessary, but it helps sometimes is it makes mimimal changes to the apk.

Your also going to want to get the sources from your framework-res.apk, by this command.
apktool if framework-res.apk
This should/might clear up your recompiling errors.
Sent from my Galaxy Nexus using xda premium

[Tutorial] Doing simple mods on framework-res.apk when apktool doesn't work properly

Hi again!
Some people asked how I did the mod I posted on the thread http://forum.xda-developers.com/showthread.php?t=1738094 and I promised I would say it.
First off, this method will require you to go deep inside binary files, so please don't try to do it if you didn't completely understand every step and know the basics about the hexadecimal, binary diffs, etc.
Before start
I will start saying what was supposed to work. You should use apktool to decode the apk, modify what you want, and then use apktool build it again. But, as of the latest version of apktool I tried (1.4.3), decode and build doesn't work for for Xperia S' framework-res.apk. (Maybe bug http://code.google.com/p/android-apktool/issues/detail?id=313 and http://code.google.com/p/android-apktool/issues/detail?id=256 are related?)
The closest I could get is using apktool 1.4.1, but the generated file was so smaller than the original and I wasn't brave enough to test on my phone.
Anyway, you will need to do this "normal" process (decode and build) for this method too. You can use any version of apktool that decode and build without errors. I used 1.4.1, but I believe a newer version could get a closer output, thus a easy file to do a binary diff. Don't worry, we won't flash these malformed apk's!
So, lets start.
PLEASE, read all the steps before start to understand the whole thing. The main idea is to find some bytes that precedes the value we want to change, then find these bytes on the original resources file and change the value we want.
1. Make sure you have adb, apktool, and everything needed on your path. I will give you the commands assuming all of them are in your path.
2. Get the necessary apk's from your phone:
Code:
[email protected]:~/Android/LT26i$ adb pull /system/framework/framework-res.apk
3972 KB/s (22227101 bytes in 5.463s)
[email protected]:~/Android/LT26i$ adb pull /system/framework/SemcGenericUxpRes.apk
4970 KB/s (2095961 bytes in 0.411s)
3. Install the apk's on apktool
Code:
[email protected]:~/Android/LT26i$ apktool if framework-res.apk nozomi
I: Framework installed to: /home/brunojcm/apktool/framework/1-nozomi.apk
[email protected]:~/Android/LT26i$ apktool if SemcGenericUxpRes.apk nozomi
I: Framework installed to: /home/brunojcm/apktool/framework/2-nozomi.apk
4. decode and build the framework-res.apk WITHOUT changing anything:
Code:
[email protected]:~/Android/LT26i$ apktool d -f -t nozomi framework-res.apk framework-res
(some lines, with warnings)
I: Done.
I: Copying assets and libs...
Code:
[email protected]:~/Android/LT26i$ apktool b framework-res unchanged/framework-res.apk
(few lines)
I: Building apk file...
5. Do the same of the step above, but CHANGING what you want before build. Pay attention to the output folder of the build, it's different from the previous step.
Code:
[email protected]:~/Android/LT26i$ apktool d -f -t nozomi framework-res.apk framework-res
(some lines, with warnings)
I: Done.
I: Copying assets and libs...
(CHANGE WHAT YOU WANT)
Code:
[email protected]:~/Android/LT26i$ apktool b framework-res changed/framework-res.apk
(few lines)
I: Building apk file...
I changed the config_showNavigationBar, inside framework-res/res/values/bools.xml, but you can try changing what you want. I recommend you to start changing one single boolean value, then you can try to do more advanced things.
6. Here starts the fun! Since we have almost the same apk file, because we built both using the same apktool version, the only different bytes must be the boolean we changed. So we can unpack both apk's and run a binary diff of the resources.arsc. I'm using the vbindiff (apt-get install vbindiff) on ubuntu, but there should be other binary diffs or hexadecimal editors. So unpack and run the following:
Code:
vbindiff unchanged/framework-res.apk_FILES/resources.arsc changed/framework-res.apk_FILES/resources.arsc
It will show you the binary representation of the two files, the changed and the unchanged. Press enter once and you will see some chars in red (if you don't see, you did something worng). These represent the changed value. It was 00 00 00 00 (false) and is FF FF FF FF (true) on the modified file. Now we can observe what we have around the value we want to changed. We need to observe because we're going to edit the original file. Note that there is a column containing a hexa sequence (27, 28, 29, 2A, 2B). Our changed value is in the same line of the 29. This is the line that starts with '0077 F500'.
Copy the text of the vbindiff, containing the changed value and everything around it, to a draft file for further reference. I've attached a print of this screen, se below.
7. Now we need to do the final ninja hit: Change the original apk. Actually, the original resources.arsc. But things are no so easy, because the value we need to change is not on the same position it was is the file we changed. If we go to the position 0077 F500, something completely diferent will be there. So we need to search for something near the value we want to change. I will search for the sequence '29 1D', which is 8 bytes before the value we want to change. Yes, it's a short sequence and will occours a lot of times, but it is the best we can use. Maybe '00 29 1D', but no more than that. Let's go, unpack the original framework-res.apk and run:
Code:
vbindiff framework-res.apk_FILES/resources.arsc
Now hit F to find the sequence, and H to Hexa sequence, and type the sequence you choose (here, '00 29 1D'). To find the next occourrence, press F, then N. Do it until you find this sequence in a similiar way of the original file, having one line below with 2A, and below 2B etc. It should be near '007D C5CF'. Now you need to press E, go to the column where you have '00 00 00 00' and change to 'FF FF FF FF'. Pay attention to the other lines to change the right columns. The edited values will be in yellow. You can see the second attached print screen.
8. This is the easiest step, just copy the modified resources.arsc to the original apk. It should not be the apktool-built one, it should be the file you modified on the vbindiff editor.
I did it using the Gnome archive manager, just drag and drop the resources.arsc inside the archiver window after open the framework-res.apk.
And voilà! Your modded apk is ready!
------
Hope someone can understand this and make some mods. I did my best to explain what I did, but it's a really hard procedure thus not easy to explain.
If you have any doubts, just post and I will try to answer!
And if you like, click thanks to me!

as far as i know SemcGenericUxpRes.apk is odexed, this doesn't affect the process?

iBotPeaches has taken over development of apktool. The development thread is here:
http://forum.xda-developers.com/showthread.php?t=1755243
The latest version seems a lot better than 1.4.3
---------- Post added at 10:36 AM ---------- Previous post was at 10:35 AM ----------
Yakandu said:
as far as i know SemcGenericUxpRes.apk is odexed, this doesn't affect the process?
Click to expand...
Click to collapse
i believe only the code is odexed so you can make changes to the resources without breaking the odex file.

Frist thanks to brunojcm for share this tutorial
finally with this tutorial i could make smaller on screen buttons .
Install via CWM : Smaller On Screen Buttons.zip
Tested on .58 stock rom

Some mods by me SHOULD come tomorrow after school. Nothing big, just a few things.
Sent from my LT26i with Tapatalk 2

Soheil_rf said:
Frist thanks to brunojcm for share this tutorial
finally with this tutorial i could make smaller on screen buttons.
Install via CWM : Smaller On Screen Buttons.zip
Tested on .58 stock rom
Click to expand...
Click to collapse
Cool you understood it!
What did you change to accomplish that? just booleans or integers too? were they easy to find?

brunojcm said:
Cool you understood it!
What did you change to accomplish that? just booleans or integers too? were they easy to find?
Click to expand...
Click to collapse
after enable navigation bar in bools.xml you can change size of bar in dimens.xml ( navigation_bar_height and navigation_bar_width )

Soheil_rf said:
Frist thanks to brunojcm for share this tutorial
finally with this tutorial i could make smaller on screen buttons .
http://img818.imageshack.us/img818/1254/screenshot2012080916234.png
http://img195.imageshack.us/img195/8084/screenshot2012080916240.png
http://img402.imageshack.us/img402/2717/screenshot2012080916242.png
Install via CWM : Smaller On Screen Buttons.zip
Tested on .58 stock rom
Click to expand...
Click to collapse
How you made that? I get confused on the file comparing thing... Or you just have to decompile, change the DPI and compile back?
Your file works fine on .452 firmware. However, it has some icon bugs on status bar (the USB connnection and debugging ones) and the carrier name stays a little over where it should be.

Felimenta97 said:
How you made that? I get confused on the file comparing thing... Or you just have to decompile, change the DPI and compile back?
Your file works fine on .452 firmware. However, it has some icon bugs on status bar (the USB connnection and debugging ones) and the carrier name stays a little over where it should be.
Click to expand...
Click to collapse
Try to reading Tutorial again , its simple but gets some time
maybe you are using moded SystemUI.apk or .58 FW had some difference
here its normal

Soheil_rf said:
Try to reading Tutorial again , its simple but gets some time
...
Click to expand...
Click to collapse
Could make your mod, Felimenta97?

brunojcm said:
Could make your mod, Felimenta97?
Click to expand...
Click to collapse
Nope. Always something Ib my way. Was replacing the resources.arsc after I rebuild the app. But I read I have to replace the Meta-Inf and Manifest.xml. But now no time.
Sent from my LT26i with Tapatalk 2

You wont be able to recompile and use the same apk that's the entire point to this article and getting around this limitaion.
Simply put hex edit the resources.arsc after binary dif finds the changes integers and replace with the original in the framework-res.apk.
-smc

somemadcaaant said:
You wont be able to recompile and use the same apk that's the entire point to this article and getting around this limitaion.
Simply put hex edit the resources.arsc after binary dif finds the changes integers and replace with the original in the framework-res.apk.
-smc
Click to expand...
Click to collapse
Well, I see. I'm just trying to see what would be the effect of setting True to the Animate Screen Lights line on bools.xml I'm no developer, just a simple user trying to do some mods by myself
Sent from my LT26i with Tapatalk 2

Felimenta97 said:
Well, I see. I'm just trying to see what would be the effect of setting True to the Animate Screen Lights line on bools.xml I'm no developer, just a simple user trying to do some mods by myself
Sent from my LT26i with Tapatalk 2
Click to expand...
Click to collapse
What was it supposed to do?

brunojcm said:
What was it supposed to do?
Click to expand...
Click to collapse
As far as I know, it's the responsible for the screen off animation, at least on GB.
Sent from my LT26i with Tapatalk 2

Don't get discouraged, i've never tried to play with the screen animations but maybe there's something else you need to find/edit? Seems like a fairly small change you tried to make.
If it's not a small change not being able to recompile the framework-res file makes doing more advanced mods frustratingly impossible, i've got several mods waiting to go for our phone when we're able to.
-smc

I want to try myself some mods too. 30 volume step, Sense multitasking, etc. And it compiles perfectly (except when it says that there it's something that it's missing a translation, a file I didn't even touched). One day, when I have more time, I will try to do such things, slowly.
Sent from my LT26i with Tapatalk 2

Why to use apktool instead of 7zip?
I tried replacing a .png in framework.res and get errors.

Erachter said:
Why to use apktool instead of 7zip?
I tried replacing a .png in framework.res and get errors.
Click to expand...
Click to collapse
Because it involves a lot more than just removing files
Sent from my LT26i with Tapatalk 2

Thanks to iBotPeaches the latest custom build of apktool is now out:
[UTIL][Sept 2 2012] Apktool v1.5.0 - a tool for reverse engineering apk files
A new version has been released!
v1.5.0 (Released September 2 - 2012 ) Codename : Pikmin
Fix for colours being decompiled with improper hex colours
Fix for <string-array> being treated as array on occasion
Support for Mac OS X user:home, instead of dumping frames into /home
Updated internal framework.jar to API16
Added <user-sdk> reading to insert into apktool.yml to help with aapt building
Supported -d mode
Added --verbose mode to output contents of AAPT (note this is a HUGE output). Only used for debugging.
Ignore bootclasspath on debug mode. (Causes some classes in smali to be fail decompile)
New AAPT (Linux only) - http://miui.connortumbleson.com/othe...apt/linux/aapt
Get the patched aapt.
@Felimenta97 if your getting the language error it should be normal depending on what framework you are using, single language is never set for a multilanguage firmware.
-smc

Center/reverse clock on CM 9.1.0

Was just wondering if there was a way to center the clock or perhaps reverse the location of the clock on 9.1.0? All the tutorials I've seen involve AOKP or CM10. Neither of which I use. I don't mind decompiling anything I'm just not sure how to do it or what to edit once it's done. Anything helps
Thanks XDA :laugh:

ian577416 said:
Was just wondering if there was a way to center the clock or perhaps reverse the location of the clock on 9.1.0? All the tutorials I've seen involve AOKP or CM10. Neither of which I use. I don't mind decompiling anything I'm just not sure how to do it or what to edit once it's done. Anything helps
Thanks XDA :laugh:
Click to expand...
Click to collapse
Edit systemui.apk
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

elesbb said:
Edit systemui.apk
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
How should I go about doing this? Any tools or what not you suggest and what do I edit once its decompiled?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

ian577416 said:
How should I go about doing this? Any tools or what not you suggest and what do I edit once its decompiled?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I figured you knew based off your first post stating you don't mind decompiling anything lol.. but you need to use apktool.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

elesbb said:
I figured you knew based off your first post stating you don't mind decompiling anything lol.. but you need to use apktool.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
[email protected]:/home/ian/workspace# apktool.jar b -f SystemUI SystemUI2.apk
I: Smaling...
I: Building resources...
invalid resource directory name: /home/ian/workspace/SystemUI/res/layout-sw600dp
invalid resource directory name: /home/ian/workspace/SystemUI/res/values-sw720dp
invalid resource directory name: /home/ian/workspace/SystemUI/res/values-sw600dp
invalid resource directory name: /home/ian/workspace/SystemUI/res/values-sw720dp-port
invalid resource directory name: /home/ian/workspace/SystemUI/res/drawable-sw600dp-hdpi
invalid resource directory name: /home/ian/workspace/SystemUI/res/values-sw600dp-port
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutException: could not exec command: [aapt, p, -F, /tmp/APKTOOL6862800640251751969.tmp, -I, /root/apktool/framework/1.apk, -S, /home/ian/workspace/SystemUI/res, -M, /home/ian/workspace/SystemUI/AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java: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:182)
at brut.apktool.Main.main(Main.java:67)
Caused by: brut.common.BrutException: could not exec command: [aapt, p, -F, /tmp/APKTOOL6862800640251751969.tmp, -I, /root/apktool/framework/1.apk, -S, /home/ian/workspace/SystemUI/res, -M, /home/ian/workspace/SystemUI/AndroidManifest.xml]
at brut.util.OS.exec(OS.java:83)
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:191)
... 6 more
[email protected]:/home/ian/workspace#
Any ideas chief?

I had to download apk auto tool or whatever its called, and an apk tool for the one s that had an updated aapt file
Sent from my SGH-T989 using xda premium

ian577416 said:
[email protected]:/home/ian/workspace# apktool.jar b -f SystemUI SystemUI2.apk
I: Smaling...
I: Building resources...
invalid resource directory name: /home/ian/workspace/SystemUI/res/layout-sw600dp
invalid resource directory name: /home/ian/workspace/SystemUI/res/values-sw720dp
invalid resource directory name: /home/ian/workspace/SystemUI/res/values-sw600dp
invalid resource directory name: /home/ian/workspace/SystemUI/res/values-sw720dp-port
invalid resource directory name: /home/ian/workspace/SystemUI/res/drawable-sw600dp-hdpi
invalid resource directory name: /home/ian/workspace/SystemUI/res/values-sw600dp-port
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutException: could not exec command: [aapt, p, -F, /tmp/APKTOOL6862800640251751969.tmp, -I, /root/apktool/framework/1.apk, -S, /home/ian/workspace/SystemUI/res, -M, /home/ian/workspace/SystemUI/AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java: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:182)
at brut.apktool.Main.main(Main.java:67)
Caused by: brut.common.BrutException: could not exec command: [aapt, p, -F, /tmp/APKTOOL6862800640251751969.tmp, -I, /root/apktool/framework/1.apk, -S, /home/ian/workspace/SystemUI/res, -M, /home/ian/workspace/SystemUI/AndroidManifest.xml]
at brut.util.OS.exec(OS.java:83)
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.java:191)
... 6 more
[email protected]:/home/ian/workspace#
Any ideas chief?
Click to expand...
Click to collapse
Did you decompile first?? lol..... also, what the heck did you edit? xD
the only thing needing editing is the SystemUI.apk/res/layout/status_bar.xml
---------- Post added at 04:10 AM ---------- Previous post was at 04:08 AM ----------
born2gethard said:
I had to download apk auto tool or whatever its called, and an apk tool for the one s that had an updated aapt file
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Thats usually only for CM10. but i think his errors are in something else, as when one needs the things you mentioned, its usually getting errors at decompiling step.

elesbb said:
Did you decompile first?? lol..... also, what the heck did you edit? xD
the only thing needing editing is the SystemUI.apk/res/layout/status_bar.xml
---------- Post added at 04:10 AM ---------- Previous post was at 04:08 AM ----------
Thats usually only for CM10. but i think his errors are in something else, as when one needs the things you mentioned, its usually getting errors at decompiling step.
Click to expand...
Click to collapse
No it decompiles fine. I'm using apktool 1.4.3 and everything I do just gets all fubard. I was using this tutorial if it helps http://forum.xda-developers.com/showthread.php?t=1773930 This is bugging me alot. I want to center the clock but I don't really just want the easy way out. And going back to AOKP just for this isn't really an option. Thanks for all the help by the way.

ian577416 said:
No it decompiles fine. I'm using apktool 1.4.3 and everything I do just gets all fubard. I was using this tutorial if it helps http://forum.xda-developers.com/showthread.php?t=1773930 This is bugging me alot. I want to center the clock but I don't really just want the easy way out. And going back to AOKP just for this isn't really an option. Thanks for all the help by the way.
Click to expand...
Click to collapse
That guide has the right stuff to edit. You scrolled down to the bottom where it says "Center clock" and applied what they stated? Also, ive never done it on ubuntu before. so maybe you wanna look up a tut for doing it on ubuntu.

Mind if I PM you?

ian577416 said:
Mind if I PM you?
Click to expand...
Click to collapse
Be my guest lol don't bother me any.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

Here you are good sir!

elesbb said:
Here you are good sir!
Click to expand...
Click to collapse
You rock man!
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

[Q] Transparent status bar

Is it possible to make the status bar transparent, but not the drop down menu?
I've been looking for that on google for two days now, but no good results. I only saw paranoid android rom has this option, but I use CM10.
I don't know how to edit .apk's, so I'm basically looking for a mod that can be flashed or an already made SystemUI.apk for this phone.

slim bean able.
Sent from my One V using xda app-developers app

Like MIUI?
I'm sure I can use edits found on XDA. I don't think they'll work to good. APKtool barely works for me anymore
Sent from my HTC One V using Tapatalk 2

thestory101 said:
slim bean able.
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
I almost just finished customizing the cm10 rom for myself, so I don't want to have to erase it and re-do it all over again :/
Curiousn00b said:
Like MIUI?
I'm sure I can use edits found on XDA. I don't think they'll work to good. APKtool barely works for me anymore
Sent from my HTC One V using Tapatalk 2
Click to expand...
Click to collapse
I think MIUI has this feature, but I'm not quite sure. I did try to install MIUI last week, but it kept crashing, so I'm staying away from it. I do hope you can find something useful on xda

miui crashed? u mostly didn't do full wipe that's why..
Sent from my One V

paarthdesai said:
miui crashed? u mostly didn't do full wipe that's why..
Sent from my One V
Click to expand...
Click to collapse
I did a full wipe 3 times :/
But I also restored my apps and contacts/messages with titanium backup. I guess that's why it started crashing, since cm10 and miui data's are different.
Also, MIUI is a really nice rom
I'm actually using it's white/orange theme on cm10, even though it's a bit buggy
Only the transparent status bar is missing

Changing the status bar color would also help, if it can't be made transparent. If anybody has any tips on that :cyclops:

To in system/app/systemUI.apk decompile and in the files find all the XML files. U will need a good code reader (windows..notepad++,Linux green fish I think could be wrong. On android the BEST I found is Axel and droidcode). Find the super_stat file and in there is background="************" change to "#00000000" android. That is transparent. There is I a guide here on xda search it and read cause u need to edit a few more.
Sent from my PK7630000 using xda app-developers app

sbkjuggalo said:
To in system/app/systemUI.apk decompile and in the files find all the XML files. U will need a good code reader (windows..notepad++,Linux green fish I think could be wrong. On android the BEST I found is Axel and droidcode). Find the super_stat file and in there is background="************" change to "#00000000" android. That is transparent. There is I a guide here on xda search it and read cause u need to edit a few more.
Sent from my PK7630000 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the suggestion. I tried it, but failed :/
When I decompiled the systemUI.apk it only gave me the "smali" file and no "res" as this guide says. And with Axel it told me that it fails to read XML input, the file may be malformed. I have no experience with decompiling whatsoever, so I have no idea what I'm doing wrong.
View attachment SystemUI.apk
I uploaded my systemUI.apk if you can take a look at it, and tell me what's wrong

OK XML files r located at systemui.apk/res/drawable

Just use pa man...cm and pa almost alike
Sent from my One V using xda premium

sbkjuggalo said:
OK XML files r located at systemui.apk/res/drawable
Click to expand...
Click to collapse
I've tried using the apktool and console, but it won't recompile the apk. Even if I change nothing it gives this error:
Code:
I: Checking whether sources has changed...
I: Smaling...
I: Checking whether resources has changed...
I: Building resources...
invalid resource directory name: C:\Users\Jaka\Downloads\apktool\SystemUI\res/dr
awable-sw600dp
invalid resource directory name: C:\Users\Jaka\Downloads\apktool\SystemUI\res/dr
awable-sw600dp-hdpi
invalid resource directory name: C:\Users\Jaka\Downloads\apktool\SystemUI\res/dr
awable-sw720dp-hdpi
invalid resource directory name: C:\Users\Jaka\Downloads\apktool\SystemUI\res/la
yout-sw600dp
invalid resource directory name: C:\Users\Jaka\Downloads\apktool\SystemUI\res/la
yout-sw720dp
invalid resource directory name: C:\Users\Jaka\Downloads\apktool\SystemUI\res/la
yout-sw720dp-land
invalid resource directory name: C:\Users\Jaka\Downloads\apktool\SystemUI\res/la
yout-sw720dp-port
invalid resource directory name: C:\Users\Jaka\Downloads\apktool\SystemUI\res/va
lues-sw600dp
invalid resource directory name: C:\Users\Jaka\Downloads\apktool\SystemUI\res/va
lues-sw600dp-land
invalid resource directory name: C:\Users\Jaka\Downloads\apktool\SystemUI\res/va
lues-sw600dp-port
invalid resource directory name: C:\Users\Jaka\Downloads\apktool\SystemUI\res/va
lues-sw720dp
invalid resource directory name: C:\Users\Jaka\Downloads\apktool\SystemUI\res/va
lues-sw720dp-port
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutExce
ption: could not exec command: [aapt, p, -F, C:\Users\Jaka\AppData\Local\Temp\AP
KTOOL408005964997419481.tmp, -I, C:\Users\Jaka\apktool\framework\1.apk, -S, C:\U
sers\Jaka\Downloads\apktool\SystemUI\res, -M, C:\Users\Jaka\Downloads\apktool\Sy
stemUI\AndroidManifest.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:182)
at brut.apktool.Main.main(Main.java:67)
Caused by: brut.common.BrutException: could not exec command: [aapt, p, -F, C:\U
sers\Jaka\AppData\Local\Temp\APKTOOL408005964997419481.tmp, -I, C:\Users\Jaka\ap
ktool\framework\1.apk, -S, C:\Users\Jaka\Downloads\apktool\SystemUI\res, -M, C:\
Users\Jaka\Downloads\apktool\SystemUI\AndroidManifest.xml]
at brut.util.OS.exec(OS.java:83)
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.jav
a:191)
... 6 more