Develop Bugs

[Q!]Bootloop after changing framework-res.apk

Ok, so i modded about 6 png's that are for the notification bar.
However, when i add them to my used framework-res (no problems at all) my phone get's stuck in a bootloop.
After a quick question in the ROM threat, brady1uk mentioned the file size.
so i checked them, and before i modded them they were a total of 43kb, but now they are 143kb!
Could this be the problem of my bootloop, and if yes, how do i reduce the file size?
*added the status_bar png's*

I don't think it's the file size. Let me ask, when you "add them to your used framework-res" how do you do it? Did you extract the .apk then re-archive?

ephumuris said:
I don't think it's the file size. Let me ask, when you "add them to your used framework-res" how do you do it? Did you extract the .apk then re-archive?
Click to expand...
Click to collapse
I open the framework-res whit winrar, and i just drag and drop my custom files in there with out extracting it.

ok, so i replaced my new png's whit the old ones in the hope my phone would work again, but it didn't
Now i'm totaly clueless...
If someone could take a look at what i have combined and why it doesn't work it would love it (using lee droid 1.9A)
*sleeping*

dragonithe said:
ok, so i replaced my new png's whit the old ones in the hope my phone would work again, but it didn't
Now i'm totaly clueless...
If someone could take a look at what i have combined and why it doesn't work it would love it (using lee droid 1.9A)
*sleeping*
Click to expand...
Click to collapse
as all is failing i would suggest getting the original framework-res.apk - before u ever touched it (download leedroid rom again if you didnt back it up). And then use either APK Manager or Theme Pro to decompile the apk, then mod away and change everything you want then use APK Manager or Theme Pro to compile it back up. Thats how I do it. I think there is a chance using Winrar to just pull out the files and add them back in has currupted it somehow

brady1uk said:
as all is failing i would suggest getting the original framework-res.apk - before u ever touched it (download leedroid rom again if you didnt back it up). And then use either APK Manager or Theme Pro to decompile the apk, then mod away and change everything you want then use APK Manager or Theme Pro to compile it back up. Thats how I do it. I think there is a chance using Winrar to just pull out the files and add them back in has currupted it somehow
Click to expand...
Click to collapse
ok, so i did this, but now when i flash the .zip i get a error [ E:Failure at line 9: run_program PACKAGE:check_data_app instalation aborted.]

Ok, so after failing to create my own apk file i pulled it from my desire and added the 6 files to it.
adb push, reboot.
And it gets stuck in a bootloop...
So ok, that failed, but i had the pulled framework still on my computer, so i decided to push this file back to make it work again.
But now it's still stuck in a bootloop....
seems like my adb corupts the .apk or what could be the problem?

You shouldnt need to decompile it if your only making a few changes to the framework.
I use 7-zip to open the rom, navigate to the required apk, and open that archive then swap the images over, no need to delete the original, they will just get over written. Then press up or back within 7-zip. when you navigate out of the apk you were in 7-zip will say it has been changed, carry on, pressing back untill you are all the way out of the rom. Then resign the rom and flash it.
Ive never used apk tool to change images in the htc resources or the framework res and never had a problem.

dragonithe said:
ok, so i replaced my new png's whit the old ones in the hope my phone would work again, but it didn't
Now i'm totaly clueless...
If someone could take a look at what i have combined and why it doesn't work it would love it (using lee droid 1.9A)
*sleeping*
Click to expand...
Click to collapse
I pretty sure the framework in the zip you posted is not from Leedroid so theres your 1st problem. Unless you made more than just 6 png changes.

djmace said:
You shouldnt need to decompile it if your only making a few changes to the framework.
I use 7-zip to open the rom, navigate to the required apk, and open that archive then swap the images over, no need to delete the original, they will just get over written. Then press up or back within 7-zip. when you navigate out of the apk you were in 7-zip will say it has been changed, carry on, pressing back untill you are all the way out of the rom. Then resign the rom and flash it.
Ive never used apk tool to change images in the htc resources or the framework res and never had a problem.
Click to expand...
Click to collapse
I also sort of use your described methode, but istead of using 7-zip, i use winzip.
djmace said:
I pretty sure the framework in the zip you posted is not from Leedroid so theres your 1st problem. Unless you made more than just 6 png changes.
Click to expand...
Click to collapse
It could be that the base of the framework is from leedroid, but i added a theme to it (think it is NexTang-DJDroid).
used it for about a month w/o problems, then i changed 6 files in the framework. And nothing works anymore ._.

can you try flashing the stock leedroid fw-res.apk to see if you get out of the bootloop? if you can do that, then at least you have a fallback plan.
and instead of flashing it, try using:
Code:
adb mount
adb push framework-res.apk /system/framework/framework-res.apk
I have never had any problems doing it that way.

I had the same problems. But i tried to make a flashable zip file and this work very fine..
And remeber you can not just replace a 9.png file maybe this is your fault?

mista1982 said:
I had the same problems. But i tried to make a flashable zip file and this work very fine..
And remeber you can not just replace a 9.png file maybe this is your fault?
Click to expand...
Click to collapse
hmm,
could you tell me a bit more about that?

[GUIDE] how to make a flashable package (update.zip)
How to edit .9.pngs

nzdcoy said:
can you try flashing the stock leedroid fw-res.apk to see if you get out of the bootloop? if you can do that, then at least you have a fallback plan.
and instead of flashing it, try using:
Code:
adb mount
adb push framework-res.apk /system/framework/framework-res.apk
I have never had any problems doing it that way.
Click to expand...
Click to collapse
I have the same problem, could you tell me how to push the framework-res.apk step by step ( just press the power button --> ) . Sorry ....

dragonithe said:
Ok, so i modded about 6 png's that are for the notification bar.
However, when i add them to my used framework-res (no problems at all) my phone get's stuck in a bootloop.
After a quick question in the ROM threat, brady1uk mentioned the file size.
so i checked them, and before i modded them they were a total of 43kb, but now they are 143kb!
Could this be the problem of my bootloop, and if yes, how do i reduce the file size?
*added the status_bar png's*
Click to expand...
Click to collapse
Same thing happened to me!
I Wiped Cache, Dalvik Cache, but nothing happened!
I had to flash 2.3.6 Stock ROM via Odin, to make my phone work!

[Q] Compiling 9-patch in framework-res

In attempts to do a bit of my own theming, I've begun looking around for info on how to create 9 patch images (.9.png). I've successfully created them and understand the whole stretching and content thing, but I can't figure out how to compile the images so that the 1 pixel border isn't part of the image.
For now, I am working off of Manup's INCredibile rEVOlution theme and just replacing some stuff that I'd like to start out with. I've tried a couple of things which may sound retarded to those that know what they're doing with this stuff, including manually adding the new 9-patch to the framework-res.apk with aapt.exe, along with extracting the apk, replacing the old image with my new 9-patch then building a whole new apk using apkbuilder.bat. Each time the image gets added to the archive successfully, but neither of these compile it and the 1 pixel border is still visible on the image.
I've read about decompiling the framework somehow and rebuilding it but A) I'm not sure if that's really necessary and B) am not quite sure how to do it anyway. I've tried creating a new android project in eclipse using the source of the extracted framework-res.apk, but I can't create the project because it can't parse the AndroidManifest.xml file.
Is there some sort of tool available that can simply be executed on a newly created .9.png to compile it into an image that is can be easily inserted into framework-res.apk? Any insight would be greatly appreciated!

Ok, so I got all excited thinking I figured this out and was good to go with all my future .9.png editing, but I'm still getting a boot loop when I push framework-res.apk back onto my phone. I have already replaced regular .png files and pushed successfully, so I know it's gotta be something with the .9.png file I am trying to edit and not the signing/pushing process.
The steps I used to edit and get the file back on the phone are:
1. Create new png file in Photoshop with the same dimensions as the existing .9.png to be replaced (478x46).
2. Save the file as .png (tried both regular save and Save for Web/Devices as PNG-8 which I read somewhere)
3. Open with draw9patch
4. Add one pixel on the left side and one pixel on the top for stretchable areas (I have tried with and without lines for content on the right and bottom)
5. File -> Save 9-patch (Creates new .9.png, dimensions 480x48)
6. Create new eclipse project from sample project source
7. Insert new .9.png into res/drawable (also tried res/drawable-hdpi)
8. Right click root project folder -> Android Tools -> Export Unsigned Application Package
9. Open sample apk with winRAR, extract my new .9.png (dimensions are once again 478x46)
10. Open framework-res.apk and replace current .9.png with mine
11. Resign framework-res.apk
12. Push framework-res.apk to /system/framework in recovery
Could anyone tell me what I am doing wrong in this process? I figured originally since the image wasn't compiled it was causing a boot loop. But now that I've figured out how to compile them, it still happens!

Yup, those 9-patches can be realllllyyy annoying. You have to be careful.
This is what works for me:
1. Get APKManager. (google it. It's here on xda somewhere)
2. Follow directions to install it.
3. Decompile apk.
4. Go to 'out' and find the image you want to edit.
5. (Assuming it's a 9-patch) Edit with GIMP or PS, but DO NOT TOUCH THE 1px BORDER. You can delete it or whatever, but make sure it's the same after you save it. (Pure black 1px)
6. Recompile apk.
7. Done!
One more warning, do NOT open any 9-patch images. (unless decompiled) It will mess up the metadata.
Hope that helps!

I had downloaded APKManager previously and messed with it a bit, but didn't think it could ultimately help me. That being said, I'm having some issues trying to do what you suggested:
1. Place unmodified framework-res.apk into "place-apk-here-for-modifying"
2. Decompile apk (Success)
*I don't have an 'out' directory, but everything is extraced into 'projects\framework-res.apk' so I'm guessing that's where you mean.
3. Edit status_bar_close_on.9.png in Photoshop, retaining the existing 1px border
4. Recompile apk (Here's the big issue)
APKManager says "Building Apk" and then gives me this message: "An Error Occured, Please Check The Log (option 21)" Press any key to continue
I press a key and it then asks, "Is this a system apk? (y/n)"
If I enter 'y', it is followed by: "Aside from the signatures, would you like to copy over any additional files that you didn't modify from the original apk in order to ensure least # of errors (y/n)"
The best combination of answering these questions I've seen is yes it's a system file and yes to copy files from the original. This creates a folder called 'keep' and instructs to delete anything I've modified. I assumed that was so that it would take any missing files from 'keep' and replace them with the modified file of the same name in 'projects\framework-res.apk', but when I delete from 'keep' the file is just missing from the new apk that is created.
When I answer no it is not a system apk, I don't see a new apk created and the original one is still unchanged containing the original image.
Answering yes it's a system file and no to copy files from original, I just get an apk with 'META-INF'.
I tried replacing the image during the whole "keep" process instead of deleting the old one, and that put it in the new apk but it still has the 1px border.
I also noticed that inside 'projects\framework-res.apk' there is a 'build\apk' folder which is empty. Not sure if I need to put something in there or what.
When I check the log, it starts with:
java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b07)
Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode, sharing)
Could Not Find C:\Users\Zach\Desktop\DroidStuff\APKManager\place-apk-here-for-modding\../place-apk-here-for-modding/signedframework-res.apk
Could Not Find C:\Users\Zach\Desktop\DroidStuff\APKManager\place-apk-here-for-modding\../place-apk-here-for-modding/unsignedframework-res.apk
I: Loading resource table...
I: Decoding resources...
W: Cant find 9patch chunk in file: "drawable-hdpi-v4/status_bar_item_app_background_normal.9.png". Renaming it to *.png.
W: Cant find 9patch chunk in file: "drawable-hdpi-v4/status_bar_item_background_normal.9.png". Renaming it to *.png.
W: Cant find 9patch chunk in file: "drawable-hdpi-v4/status_bar_header_background.9.png". Renaming it to *.png.
I: Copying assets and libs...
W: Could not find sources
I: Checking whether resources has changed...
I: Building resources...
libpng error: Read Error
ERROR: Failure processing PNG image C:\Users\Zach\Desktop\DroidStuff\APKManager\other\..\projects\framework-res.apk\res\drawable-hdpi\status_bar_header_background.9.png
libpng error: Read Error
ERROR: Failure processing PNG image C:\Users\Zach\Desktop\DroidStuff\APKManager\other\..\projects\framework-res.apk\res\drawable-hdpi\status_bar_item_app_background_normal.9.png
libpng error: Read Error
ERROR: Failure processing PNG image C:\Users\Zach\Desktop\DroidStuff\APKManager\other\..\projects\framework-res.apk\res\drawable-hdpi\status_bar_item_background_normal.9.png
Then there's a ton of entries that look like this for every single png:
C:\Users\Zach\Desktop\DroidStuff\APKManager\other\..\projects\framework-res.apk\res\values\public.xml:2690: error: Public symbol drawable/activity_title_bar declared here is not defined.
And ends with:
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutException: could not exec command: [aapt, p, -F, C:\Users\Zach\AppData\Local\Temp\APKTOOL1864619025913287067.tmp, -x, -S, C:\Users\Zach\Desktop\DroidStuff\APKManager\other\..\projects\framework-res.apk\res, -M, C:\Users\Zach\Desktop\DroidStuff\APKManager\other\..\projects\framework-res.apk\AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(Unknown Source)
at brut.androlib.Androlib.buildResourcesFull(Unknown Source)
at brut.androlib.Androlib.buildResources(Unknown Source)
at brut.androlib.Androlib.build(Unknown Source)
at brut.androlib.Androlib.build(Unknown Source)
at brut.apktool.Main.cmdBuild(Unknown Source)
at brut.apktool.Main.main(Unknown Source)
Caused by: brut.common.BrutException: could not exec command: [aapt, p, -F, C:\Users\Zach\AppData\Local\Temp\APKTOOL1864619025913287067.tmp, -x, -S, C:\Users\Zach\Desktop\DroidStuff\APKManager\other\..\projects\framework-res.apk\res, -M, C:\Users\Zach\Desktop\DroidStuff\APKManager\other\..\projects\framework-res.apk\AndroidManifest.xml]
at brut.util.OS.exec(Unknown Source)
... 7 more

Hmm... it sounds like quite a few of the 9-patch files are corrupted. Looking at the error log, it seems as if you have some 9-patch files that "aren't 9-patch"ed. That is, you opened the compiled 9-patch, or somehow corrupted it.
Are you sure it's an unmodified framework-res.apk? Try pulling the one from your phone (assuming it's running), or download your ROM again.
PS Don't worry about all the errors. I know it looks scary, but the rest of the errors are caused by the failed compilation of those 9-patches.

It has been modified from the standpoint that it is Manup's INCredible rEVOlution theme and not stock, but it runs on my phone. However, I think I may have just discovered something really stupid on my part.
Instead of restoring my nandroid when it didn't work, I decided "hey, why don't I repush this unmodified backup framework I have and save 15 minutes!" I pushed that and it still boot looped, so I think somewhere along the line I overwrote my backup/file I was using as a base, with something that doesn't work. Ugh! I must have at some point a while ago opened those png's that are corrupted, because I see they are all related to the status bar, which is what I'm trying to modify, I haven't touched them recently though.
I'm now in the middle of a long txt conversation with someone so it'll have to wait, but I think I should be good to go using my previous method and a freshly pulled framework-res.apk, possibly using the decompiled 9-patch from APKManager in place of mine created from scratch.
I'll let you know how it goes when I get around to it!
Edit: I pulled the current working framework off my phone and got the same errors on those png's with APKManager. I tried making the edit and pushing again anyway, didn't work. Re-pushing the unmodified one (which I'm sure was unmodified, as far as since I pulled it just now) boot looped still. Something obviously got messed up somewhere, but I'm confused why it runs on my phone, but when I re-push it, it stops working. So I guess I'll try a fresh download again later and see how it goes. If that doesn't work, then I'm just completely lost =/

Yeah, so I'm pretty lost on this. I downloaded a fresh copy of the framework-res.apk from the INCredible rEVOlution theme and I still can't get it to work.
I've tried making a status_bar_close_on.9.png from scratch with draw9patch as well as overwriting the decompiled status_bar_close_on.9.png from the apk, thinking maybe there was a conflict with something in xml when I changed the stretchable areas by making my own (I don't know much about the xml so I'm trying to avoid touching it for now).
Since APKManager is still giving me re-compiling errors, I used my previous method of compiling the image (both mine and the original decompiled one) by putting it in a res/drawable folder within an eclipse project and exporting, which appears to work since the dimensions shrink from 480x48 to 478x46 after it's done. This is the original dimensions of the .9.apk I pulled.
The only thing I can think of is maybe the file size? My png is 13k before I compile it, and then becomes 31k. The original status_bar_close_on.9.png is around 4k.

Seems like we need to do some debugging.
Try (in this order):
1. Flashing the umodified framework-res.apk. If it's good, then go on. If not, then it's the theme's fault.
2. Decompile the umodified framework-res.apk. Recompile it. Are there errors? If yes, then it's APKManager's fault and you should try APKtool. If no errors, then it's something about your editing.
Try those two steps, then report back! =]

The unmodified theme works fine, so I tried decompiling and recompiling it and gave the same errors. apktool gives me the same errors as APKManager, so it's not the fault of APKManager but rather the SDK tools it uses to do its job, or rather the theme itself.
However, I decided to try replacing the framework-res.apk inside of the original .zip file for the theme and flashing that instead of pushing it through adb. For whatever reason, that worked! Now that I think of it, the standard .png images I replaced previously were in com.htc.resources.apk and not the framework-res.apk. So I guess the phone doesn't like the framework being pushed through adb.

Thanks for the tip re: APKManager. I'm going to give that a shot. Seems less cumbersome than the 9Patch tool/Eclipse/Unzip approach I'm currently using.

I have been extremly unsuccessful with 9patch images until I found the attached
1) Extract the contents to any folder
2) Look in the \Originals\res\drawable-hdpi folder and you will see a sample I left in there.
3) After edits (I use Gimp) just run the xUltimate-d9pc.exe
4) Look in the done\Originals\res\drawable-hdpi and you will see the new output patched image.
5) Copy your outputs images to the appropriate folder in the apk. either by:
a. dragging the images to the folder within the archive (I use 7Zip) or
b. first extract the res folder to the PC and make your edits there then
drag the whole folder back into the archive.
EDITING NOTES:
1) The image that you use as input has to be 2x2 pixels bigger than the final 9patch image you want for the "stretch marks" along the sides and top.
2) Look at the sample I provided and basically the solid black marks on the right, bottom, left and top will work for most images but you can experiment.
3) The marks (patches) MUST be solid black
Enjoy

NilsP's xUltimate headache cure
@NilsP
Thank you very much for the xUltimate-9Patch.zip, it worked perfectly.
I have tried a couple of other xUltimate downloads but ended up with either bad .9.png's after compiling with APKmanager or simply just errors when running the .exe inside the xUltimate folder.
I am going to be flashing a new Desire HD rom onto my Desire very soon and can not wait to edit some fresh, uncorrupted .9.png's knowing I will not get errors from APKmanager.

Hi, I wonder if you´re still there! I would like to make my phone dialer transparent, understand that therefor I have to work on .9.pngs in drawable-sw320dp-hdpi of secphone.apk. But I run into various problems. First there are lots of .9.pngs, then I thought I´d begin with *bg.9.pngs and there came my first surprise. xUltimate-9Patch says even when compiling the original ones that there are errors ... So how could I proceed? If you could answer I´d really appreciate it!!! Thanks!

NilsP said:
I have been extremly unsuccessful with 9patch images until I found the attached... xUltimate-d9pc.exe ...
Click to expand...
Click to collapse
FYI, many AVs have started tagging xUltimate-d9pc.exe as a trojan. I'm not smart enough to know if it's a false positive though:
https://www.virustotal.com/en/file/...2db2aef519e3a80cd991fab1a513438a638/analysis/

[TUT] Custom frameworks for Gen 8

So, it seems that more people are taking an interest in making custom frameworks. This isn't really a full tutorial, but I thought it would be helpful to just post some tips on how to go about making your own framework-res.apk, save others a bit of time retreading old ground, since the methods are scattered around the site a bit!
Thanks to wdl1908 for prompting me to do this - should really have done this sooner!
Okay, so basic requirements:
Rooted Gen 8 (Uruk or chulri method)
Original Archos framework-res.apk
zip editor
image editing software
.png's to replace the stock ones with
That's about it! I've been using GIMP on Ubuntu for the image editing, and Phatch for batch resizing, but Photoshop will work just as well on Windows.
Edit: Thanks to wdl1908, have found that Gwenview gives much better results when resizing, compared to Phatch or GIMP. Works on both Ubuntu and KDE.
Use your preferred zip editor to unzip the contents of framework-res.apk to your chosen folder. The main folder of interest is "drawable-mdpi".
The Gen 8's use MDPI resolution images (well, A70 and A101 to at any rate. I think someone mentioned the A32 or A43 used HDPI images). Depending on your .png source, you may need to resize the images. I took my images from themes made for the Desire, which is an HDPI device, so I used GIMP/Phatch to resize them.
In terms of resizing, I compared the size of each new png with the original one, and resized. I know p0rkburn just resizes the images to 66%, but I've had problems with some images not coming out the right size that way. The other thing to watch out for is that not all the images need resizing. Also, some of the textfield and tab_select images are different proportions to their phone equivalents, so again watch out for that.
Once you've replaced the images you want to, they need to be put back into the .apk. I used to copy and paste into the framework-res.apk, but that doesn't work for 9patch files. Also, wdl1908's FrameWorkBuilder makes the compile process so ridiculously easy, there is no reason not to use that instead.
To put the new framework-res.apk on the device, I use this method via ADB wireless, which works fine.
Happy theming!
EDIT: 9patch files
These can be a PITA, until you understand how they work. I used the following two sources to finally crack it :
http://developer.android.com/guide/developing/tools/draw9patch.html
http://forum.xda-developers.com/showthread.php?t=580351
If you are changing 9patch files, you have to decompile and recompile using the FrameWorkBuilder.
I prefer using the draw9patch tool, as it lets you check that the 9patch works as expected.
Spent enough time bashing my head against a brick wall trying to sort out 9patch files, so if I can spare anyone else that, feel free to post/PM..

I'll leave this post here for my recommendations that will be more complex when you need to modify xml files.
In short the procedure is a follows (this needs to be expanded)
unpack the apk to framework-res-UNPACKED dir
decompile the apk to framework-res-DECOMPILED (with apktools)
copy framework-res-MOD to framework-res-DECOMPILED
compile framework-res-COMPILED (with apktools)
unpack the compiled apk to framework-res-COMPILED (with 7za)
remove all the files that are present in framework-res-MOD from the framework-res-UNPACKED dir
remove the file resources.arsc from framework-res-UNPACKED
copy all files from framework-res-UNPACKED to framework-res-COMPILED
zip all files in framework-res-COMPILED to the new framework-res.apk
remove the resources.arsc from that apk file
readd the resources.arsc file without compression to the new apk file
Done
The reason this is so complex is that their are bugs in apktools and the signature needs to be preserved.
FrameWorkBuilder v0.3
README.txt
-------------------------------------------------------------------------------------------------------
Place the script FrameWorkBuilder.sh in a directory and execute.
The script will download all the needed tools.
Place framework-res.apk in the dir framework-res-STOCK
Place mods in framework-res-MOD follow the usual directory structure.
Example:
framework-res-MOD
framework-res-MOD/res
framework-res-MOD/res/drawable-hdpi
framework-res-MOD/res/drawable-mdpi
framework-res-MOD/res/drawable
Execute FrameWorkBuilder.sh to apply the mod.
Modded framework-res.apk will be stored in the directory framework-res-MODDED.
-------------------------------------------------------------------------------------------------------
Changelog
-------------------------------------------------------------------------------------------------------
v0.3 Added xml png duplication check to avoid that animations don't work. .9.png support
v0.2 Added mod checks Added compile failure test
v0.1a BUGFIX cp dirs
v0.1 Initial version
-------------------------------------------------------------------------------------------------------
Have fun modding.

wdl1908 said:
I'll leave this post here for my recommendations that will be more complex when you need to modify xml files.
If you don't mind we'll make it a joined tutorial. I have no time now it's time I got some sleep.
Click to expand...
Click to collapse
I have no idea about editing XML files, but that was the next thing on my "To learn" list. I would be very happy for you to add your knowledge to this thread.
Also, if anyone has info to add/corrections to make, please feel free.

Good stuff, guys. At the very least we can make this a three man party.

The more the merrier!
Guys, can I ask what device you're both using?

fisha21 said:
Guys, can I ask what device you're both using?
Click to expand...
Click to collapse
A101IT with archangel root
A70IT with chulri's root

fisha21 said:
The more the merrier!
Click to expand...
Click to collapse
well, if i can do something, i'm here ;-)

wdl1908 said:
A101IT with archangel root
A70IT with chulri's root
Click to expand...
Click to collapse
Cool, thanks. Also, can I ask how you're viewing the XML files? Every program I've tried won't open them - keep getting error messages about invalid character content.
woti23 said:
well, if i can do something, i'm here ;-)
Click to expand...
Click to collapse
Welcome...

fisha21 said:
Cool, thanks. Also, can I ask how you're viewing the XML files? Every program I've tried won't open them - keep getting error messages about invalid character content.
Click to expand...
Click to collapse
You have to decompile the framework-res.apk with the apktools then all is revealed.

I have an A43it, and I find it to use a mixture of the hdpi and mdpi drawables, it is quite odd how they have it. I am drawing this conclusion because I only changed the hdpi drawables, and some things (status bar pull down for one) stayed original. I am going to work some more on it later today and will update here. My method for pushing to the device uses adb like such:
Code:
adb push framework-res.apk /sdcard/framework-res.apk
adb shell
su
stop
cp /sdcard/framework-res.apk /system/framework/framework-res.apk
chmod 644 /system/framework/framework-res.apk (only needs to be done the first time, as the permissions will adopt those when replacing in the future)
start
This causes the device to do a little soft-reboot (does not perform a proper full shutdown/reboot) that is pretty quick, and avoids any f/c situations you may encounter replacing the file while the system is live.
Edit 2 - ok, I just plain old missed the drawables earlier, they are all in hdpi for the A43. Posting screenshots of what I have put together shortly.

daveid said:
My method for pushing to the device uses adb like such:
Code:
adb push framework-res.apk /sdcard/framework-res.apk
adb shell
su
stop
cp /sdcard/framework-res.apk /system/framework/framework-res.apk
chmod 644 /system/framework/framework-res.apk (only needs to be done the first time, as the permissions will adopt those when replacing in the future)
start
This causes the device to do a little soft-reboot (does not perform a proper full shutdown/reboot) that is pretty quick, and avoids any f/c situations you may encounter replacing the file while the system is live.
Click to expand...
Click to collapse
Great I was looking for that.

wdl1908 said:
[*]compile framework-res-COMPILED (with apktools)
Click to expand...
Click to collapse
Getting stuck on the above step. Have got a folder called framework-res-DECOMPILED. When I try to compile it, the first message I get is:
Code:
w:Could not find sources.
It then runs through the process throwing up multiple error messages, and at the end I am left with an empty Build folder. Any ideas? I read on the Apktool thread that you need to add a classes.dex file to apk that don't already have one?
Thought I'd try your method as my primitive version keeps resulting in faulty apk's the last day or two!

fisha21 said:
Getting stuck on the above step. Have got a folder called framework-res-DECOMPILED. When I try to compile it, the first message I get is:
Code:
w:Could not find sources.
Click to expand...
Click to collapse
No problem there thats only a warning.
fisha21 said:
It then runs through the process throwing up multiple error messages, and at the end I am left with an empty Build folder.
Click to expand...
Click to collapse
What error messages?
fisha21 said:
Any ideas? I read on the Apktool thread that you need to add a classes.dex file to apk that don't already have one?
Click to expand...
Click to collapse
What version of apktools do you have?
never needed any classes.dex in framework-res.apk
fisha21 said:
Thought I'd try your method as my primitive version keeps resulting in faulty apk's the last day or two!
Click to expand...
Click to collapse
I'll try to cleanup my script and post it soon.

I just found out we can have custom boot animations on our gen 8 devices.
search for some bootanimation.zip on the web or go to UOT Kitchen and download one from the kitchen. place it in the directory /data/customization/ and reboot. This works even for the stock firmwares with archangel root.
Enjoy

I've added the first version of my FramWorkBuilder script in the second post.

wdl1908 said:
I've added the first version of my FramWorkBuilder script in the second post.
Click to expand...
Click to collapse
Thanks for the hard work!
Gave it a run through but get the following error messages:
Code:
Applying MOD...cp: cannot stat `/home/sarju/FWB/framework-res-MOD/*': No such file or directory
and
Code:
Copy files from UNPACKED to COMPILED that are not modified...cp: cannot stat `/home/sarju/FWB/WorkSpace/framework-res-UNPACKED/*': No such file or directory
The script is located in the "FWB" folder.

fisha21 said:
Code:
Copy files from UNPACKED to COMPILED that are not modified...cp: cannot stat `/home/sarju/FWB/WorkSpace/framework-res-UNPACKED/*': No such file or directory
The script is located in the "FWB" folder.
Click to expand...
Click to collapse
yeah download the 0.1a version and try again.

wdl1908 said:
yeah download the 0.1a version and try again.
Click to expand...
Click to collapse
Ok, think I'm just being stoopid here. Ran the v0.1a, no error messages BUT
If I use the folder structure "framework-res-MOD>drawable-mdpi", the resulting apk just has the original contents of drawable-mdpi. If I use "framework-res-MOD>res>drawable-mdpi", the resulting pak has an empty drawable-mdpi folder.

fisha21 said:
Ok, think I'm just being stoopid here. Ran the v0.1a, no error messages BUT
If I use the folder structure "framework-res-MOD>drawable-mdpi", the resulting apk just has the original contents of drawable-mdpi. If I use "framework-res-MOD>res>drawable-mdpi", the resulting pak has an empty drawable-mdpi folder.
Click to expand...
Click to collapse
the structure should look like this.
Code:
framework-res-MOD
framework-res-MOD/res
framework-res-MOD/res/drawable-hdpi
framework-res-MOD/res/drawable-ldpi
framework-res-MOD/res/drawable-mdpi
framework-res-MOD/res/drawable
but make sure you remove empty dirs.
I suspect it has to do with empty dirs I'll check that....

Nope tthats not it.
can you zip up the files files-to-remove.txt and log.txt in the WorkSpace dir and post them or via pm if thats possible.

[GUIDE] Change Nav Bar D.P.I. on Android Jelly Bean 4.1.1 (Galaxy Nexus)

Guide – Change Navbar D.P.I. in Android Jelly Bean (4.1.1)
•Thanks to Vomer for helping me learn this and answering my questions when I had them… Also for persuading me to write this guide for others users to hopefully use to learn a small bit of Android modding, which will hopefully create more publically used mods for the benefit and growth of the community. Let’s get it…
First thing is first… This guide is created with the Galaxy Nexus in mind. Even though other phone brands (Samsung, H.T.C., LG, Sony, etc.) are now upgrading their handsets to Android Jelly Bean, this guide is created with my experience with the pure Google experience in mind and pure Google O.S. *If you are using a rom with Samsung Touch Wiz, H.T.C. Sense or anything else produced/provided by another company, this isn’t for you, although it may answer some questions and get you started in the right direction…
THE TOOLS:
I’m using an ApkTool package, which were obtained from a thread created by monstaX < Credit to him!
First off, go to this webpage http://www.mediafire.com/?acrgcd0w850q0gj and download the file. File name should be “apktoolsJB.zip”. Once you have the tools downloaded, unzip them to your desktop.
Inside the unzipped file, you will locate the following files; aapt.exe; apktool.bat; apktool149.jar; apktool142.jar; apktool144.jar and baksmali.jar.
After confirming that the above listed files are present, rename “apktool149.jar” to “apktool.jar”.
That’s it for the tools, leave the file on your desktop, as this will ultimately be your workspace along with a command prompt.
I would also download 7-Zip and Notepad++ from the internet. You can Google those two programs and download them if you don’t already have them….
GETTING WINDOWS READY:
The next thing we need to do is remove the “Environmental Values”. If you have attempted to edit/mod any apks in the past, you probably set up “Environmental Values” in “Path” under “System Variables”. If you have done this, simply navigate back to “System Variables>Path” and delete the added non-sense that you added before. An example would be something like “Android\SDK\platform-tools\;” Make sure that after you’re done deleting, you leave a “;” at the end of the “Path Variable” line of text.
Now for the fun part:
DECOMPILE/COMPILE
Once you have done the above steps, you’re now ready to have some fun.
First off, you need to download a copy of the .zip file of the ROM you’re using onto your computer OR transfer a copy of the framework-res.apk and SystemUI.apk to your computer from your G-Nex. Once you have located these files, you need to place both files into the JBapktool folder that we unzipped onto the desktop earlier.
Once you have placed both files into the JBapktool folder, open the folder and shift+right-click somewhere inside the folder (NOT ON A FILE). Once you have done that and a menu has popped up, select “Open Command Window Here”.
Once the command window has opened; you need to install the framework-res.apk… Now there is a bunch of technical jargon for this but simply and easily type the following command;
java –jar apktool.jar if framework-res.apk
You will see a line that reads “ Framework installed to: C:\Users\yournamehere\apktool\framework\1.apk”
After the above line appears, you will now decompile the framework-res.apk file. To do this, type the following command;
java –jar apktool.jar d framework-res.apk
You will now see something like:
I: Loading resource table…
I: Loaded
I: Decoding file-resources…
I: Decoding values*/* XMLs…
I: Done
I: Copying assets and libs…
*DON’T CLOSE THE COMMAND PROMPT*
After you see that, you should notice that a new file has been added to the JBapktool folder, which should be named “framework-res”. Inside that folder, you will observe the following folders/files; assets; build; dist; res; AndroidManifest.xml; apktool.yml. The file that we are worried about is the “res” file. Open the “res” folder and then navigate to the “values” folder and look for a file named “dimens.xml”. The “dimens.xml” is where the magic happens. Right click on this file and open as “Edit with Notepad++”.
Once Notepad++ is open with the “dimens.xml” file open, you want to focus on three strings in the file. The strings are: 36.0dip
36.0dip
32.0dip
*For a 32 DPI nav bar, I personally use 32 for the height and 28 for the width.*
Now here, the parts of the string that we want to change are highlighted in yellow and represent the “DPI” of the nav bar. The above lines are from a “dimens.xml” file that I changed to make a “36 DPI” nav bar. Once you have made the changes to the above dimensions, just click file and save in Notepad++ and close the program.
Now to compile the “framework-res” folder back into an .apk.
Simply go back to the command prompt that we opened earlier (you shouldn’t have closed it, but if you did follow steps above to open a new one, reinstall the framework-res.apk (STEPS ABOVE) and then continue).
Type the following command;
Java –jar apktool.jar b framework-res
You will see the following (hopefully);
W:Could not find sources
I:Checking wheter resources has changed…
I:Building resources…
I:Building apk file…
After this, you should revert back to the “JBapktool” folder and navigate to “framework-res” folder>”build”>”apk”… Look for the “resources.arsc” file. THAT’S THE MONEY SHOT…
Using 7-zip, you want to open the “framework-res.apk” file that we originally began with (I would make a copy of it and put it on my desktop). Right-click on the “framework-res.apk” file, click 7-Zip and then open archive. A new window will open, showing the visible files inside the framework-res.apk. Look for the file “resources.arsc”. Delete it, locate the “resources.arsc” from the framework-res folder (framework-res>build>apk) in the JBapktool folder. Click and drag it to the unzipped original framework-res.apk file and drop it. WE’RE DONE WITH THE FRAMEWORK-RES.APK FILE.
Now simply place that file in a CWM flashable .zip file and hold tight.
Now we need to decompile the SystemUI.apk that we placed in the JBapktool folder earlier. Follow the above listed instructions to complete this, same as we did with the framework-res.apk.
Once you have the SystemUI.apk file decompiled, look for a folder in JBapktools named “SystemUI”. Inside the “SystemUI” folder, navigate to res>layout>navigation_bar.xml. We now want to open the navigation_bar.xml file with Notepadd++, so that we can delete two lines in it that would cause a larger back button on the nav bar if left intact.
Inside the navigation_bar.xml file look for the following two lines:
"@drawable/ic_sysbar_back" android:scaleType="center"
"@drawable/ic_sysbar_back_land" android:scaleType="center"
Now, we want to delete the following from both lines:
android:scaleType="center"
After deleting that line from both lines, save the file by clicking file>save and close Notepad++. Now back go back to JBapktools and to the already opened command prompt window (it should still be open).
We are now going to compile the SystemUI. To do this type the following command;
java –jar apktool.jar b SystemUI
You will see some text in the command prompt and will ultimately see I:Building APK file…
Once this is complete, navigate back to the JBapktool folder and to the SystemUI file. Once you have the SystemUI folder open, we need to navigate to build>apk and look for the following file; AndroidManifest.xml. Now this is important, we need to replace this file with the AndroidManifest.xml file from the original unzipped SystemUI.apk. So open the original SystemUI.apk with 7-zip, and copy “META-INF” and “AndroidManifest.xml”. Once you have those copied from the original unzipped SystemUI.apk, relocate back to the JBapktool folder>SystemUI>build>apk and paste both of them. If asked to replace, CLICK YES OR REPLACE ON ALL WARNINGS THAT POP UP!!!!
Now we need to back out to the SystemUI folder in JBapktool and click on the folder that is named “dist” (the “dist” folder is where the freshly compiled SystemUI.apk is located once we type in the compile command in the command prompt). Once inside the “dist” folder, you will see a SystemUI.apk file. DELETE IT… We never use the first SystemUI.apk that we compile, because we needed to added the META-INF and AndroidManifest.xml files for signing purposes. Once you have the 1st compiled SystemUI.apk deleted, return to the command prompt and enter the compile command again and compile a 2nd SystemUI.apk.
The 2nd SystemUI.apk will appear in the “dist” folder and is the usable SystemUI.apk.
Now that you have your new SystemUI.apk compiled, place it in the same CWM flashable .zip file, boot into recovery, wipe cache and dalvik cache and VOILA, you have just pimped your nav bar’s DPI.
•Remember when placing the SystemUI.apk file into your CWM .zip file to place it under /system/App. And when placing your framework-res.apk into your CWM .zip file it goes under /system/framework…
The mods and this guide take time for us to put together for your enjoyment/the improvement of the community. If I or anyone else has helped you, please hit the “Thank You” button. Thanks.

Great tutorial
Sent from my Galaxy Nexus using Tapatalk 2

Thank's man.....................

APatte111: could you upload your 32 height 28 landscape framework-res for v4 rom ?
Great guide.
If you dont want to waste time uploading....its all good anyway mate :good:

bs android said:
APatte111: could you upload your 32 height 28 landscape framework-res for v4 rom ?
Great guide.
If you dont want to waste time uploading....its all good anyway mate :good:
Click to expand...
Click to collapse
This is not the mods thread
Great job bud!
Also, remember guys - if you make a MiNCO Mod - share with other's in the MiNCO Plus+ Thread. Chances are someone else would want it too

bs android said:
APatte111: could you upload your 32 height 28 landscape framework-res for v4 rom ?
Great guide.
If you dont want to waste time uploading....its all good anyway mate :good:
Click to expand...
Click to collapse
This framework-res.apk is in place in several of the mods in the MiNCO Plus+ mods and enhancements thread that vomer began... Just download one of the mods and extract the framework-res.apk from one of the .zip files... Probably the easiest way to get it...
Sent from my Galaxy Nexus using xda premium

vomer said:
This is not the mods thread
Great job bud!
Click to expand...
Click to collapse
OK sorry for asking OP if that annoys you
APatte111 said:
This framework-res.apk is in place in several of the mods in the MiNCO Plus+ mods and enhancements thread that vomer began... Just download one of the mods and extract the framework-res.apk from on of the .zip files... Probably the easiest way to get it...
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Nice APatte, I saw it now, downloaded and tried your framework with vomers standard white for minco rom. Got the failure in back button so guess I have to wait till I get home to a computer to fix it. Thanks for the guide anyway, love different and smaller navbars.

bs android said:
Got the failure in back button so guess I have to wait till I get home to a computer to fix it. Thanks for the guide anyway, love different and smaller navbars.
Click to expand...
Click to collapse
Yeah, if by "failure" you mean the larger back key then that is being caused by the un-edited navigation_bar.xml file which is located in SystemUI.apk>res>layout... You need to delete the two lines mentioned above, re-compile the SystemUI.apk and everything should be golden. Let me know if it doesn't work and I will help ya... Good Luck

Good guide!

Great job man!! Great tutorial!
:good::good::good::good::good:

MAN CHANGE THIS IS WRONG!! Java –jar apktool.jar b frame-work
IT IS java -jar apktool.jar b framework-res

masterchif92 said:
MAN CHANGE THIS IS WRONG!! Java –jar apktool.jar b frame-work
IT IS java -jar apktool.jar b framework-res
Click to expand...
Click to collapse
Thanks, you found a typo and the one mistake in the whole guide... Appreciate that...
Sent from my Galaxy Nexus using xda premium

After looking at 5 or 6 other guides. This one is BY FAR the easiest to understand & includes everything you need to get the job done.
Thanks a ton OP!

i cant seem to find the "@drawable/ic_sysbar_back" & "@drawable/ic_sysbar_back_land" in the navigation_bar.xml file. Any help please? I must mention that i am on AndroidME CM10 1.7.0 and took both files from the cwm zip.
Only repeating line i can find is "@drawable/ic_sysbar_lights_out_dot_large" . Dont know if it is the same.
I ve done some android developing in the past. every linear_layout represents a button, right?

angelossssss said:
i cant seem to find the "@drawable/ic_sysbar_back" & "@drawable/ic_sysbar_back_land" in the navigation_bar.xml file. Any help please? I must mention that i am on AndroidME CM10 1.7.0 and took both files from the cwm zip.
Only repeating line i can find is "@drawable/ic_sysbar_lights_out_dot_large" . Dont know if it is the same.
I ve done some android developing in the past. every linear_layout represents a button, right?
Click to expand...
Click to collapse
Can you upload the navigation_bar.xml file for me so I could have a look...
*** Nice signature by the way *** LOL
Sent from my Galaxy Nexus using xda premium

APatte111 said:
Can you upload the navigation_bar.xml file for me so I could have a look...
*** Nice signature by the way *** LOL
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
here. i uploaded in my dropbox.
https://www.dropbox.com/s/7331l8fqs7a99yg/navigation_bar.xml
Thanks for the signature
---------- Post added at 08:25 PM ---------- Previous post was at 08:17 PM ----------
angelossssss said:
here. i uploaded in my dropbox.
https://www.dropbox.com/s/7331l8fqs7a99yg/navigation_bar.xml
Thanks for the signature
Click to expand...
Click to collapse
actually nevermind that... i just flashed the cwm without the systemui.apk and it seems to be working fine. lol

angelossssss said:
here. i uploaded in my dropbox.
https://www.dropbox.com/s/7331l8fqs7a99yg/navigation_bar.xml
Thanks for the signature
---------- Post added at 08:25 PM ---------- Previous post was at 08:17 PM ----------
actually nevermind that... i just flashed the cwm without the systemui.apk and it seems to be working fine. lol
Click to expand...
Click to collapse
I was going to say, it looks like they have already removed that from the navigation_bar.xml file... The description of the ROM shows that Nav Bar Options are included... You could change the DPI size, compile and see if the back button is larger (which is what deleting those two lines fix)... If it's not (which you stated it's working) then skip that step....

APatte111 said:
I was going to say, it looks like they have already removed that from the navigation_bar.xml file... The description of the ROM shows that Nav Bar Options are included... You could change the DPI size, compile and see if the back button is larger (which is what deleting those two lines fix)... If it's not (which you stated it's working) then skip that step....
Click to expand...
Click to collapse
y i only compiled the framework-res.apk but i thing now my phone became a little laggy. especially when swipping between screens and opening apps.
i'll check it out if i did anything wrong.

angelossssss said:
y i only compiled the framework-res.apk but i thing now my phone became a little laggy. especially when swipping between screens and opening apps.
i'll check it out if i did anything wrong.
Click to expand...
Click to collapse
Check in the ROM and see if there is already a built in option to change the nav bar DPI size... if not, make the changes to the dimens.XML file and then recompile/replace the .apk and re-flash... that should work and everything should be normal...
Sent from my Galaxy Nexus using xda premium

APatte111 said:
Check in the ROM and see if there is already a built in option to change the nav bar DPI size... if not, make the changes to the dimens.XML file and then recompile/replace the .apk and re-flash... that should work and everything should be normal...
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
unfortunately there is not. it only has options to change the buttons order.

[FAQ] Frequently asked question concerning VTS

How to properly install framework apks and use tags
ApkTool (and therefore VTS) needs framework apks to properly de- & recompile Android resources.
Framework tags are used to differentiate between multiple sets of framework apks.
You are usually going to have one set (ie. multiple apks) per device and base/rom version.
When installing frameworks it's very important to install all frameworks from the same device/rom with the same tag.
Have a look at this tutorial to learn more about installing frameworks with VTS.
Click to expand...
Click to collapse
How to completely reset the VTS layout
VTS has a "Reset layout" button, but sometimes this can't repair all problems with a broken window layout.
To fix such persistent problems, open the settings and untick the "Save dock layout" checkbox.
Now restart VTS, the layout should be reset to the default layout.
You can enable layout saving again.
Click to expand...
Click to collapse
How to manually edit VTS settings
Since VTS 2.6.12 you can easily change these settings with the "Advanced settings" window inside VTS.
Open the settings window and click on the "Advanced" button at the bottom.
VTS stores its settings easily accessible in XML files. They are stored in a folder (normally) located here:
C:\Users\<your user>\Documents\Virtuous Ten Studio\Settings\
You can easily open and edit these settings files, just make sure VTS is closed before doing so.
Note: Some settings only exist after VTS used them for the first time.
Click to expand...
Click to collapse
VTS can't find the Java binary
Make sure to add the location of your Java.exe to your PATH variable and reboot after doing so.
VTS should be able to find your java binary now.
If it still doesn't work, you can manually specify the java path in the VTS settings.
Click to expand...
Click to collapse
Something else went wrong and I need help
Editing apks and other Android related files can be a highly complex task.
There are many possible error sources. If something goes wrong nobody can help you unless you provide some important things: (if applicable)
The VTS logs. Without these it's pretty impossible to troubleshoot problems that occured while using VTS.
Have a look at this tutorial, it explains you how to use the Log Viewer.
Make sure all checkboxes on top are checked and copy all the log text from the textbox.
When asking for help, make sure to include all the text in [CODE]<log text>[/CODE] tags.
A logcat of your device, the packagename (if applicable) and filename of the file you are working on.
If something goes wrong or doesn't work on the device you are working with, it's absolutely required to get a logcat before asking for help.
You can use the Logcat viewer of VTS to get a copy of the so called Logcat. It's the internal log of your device and usually helps revealing and solving all kinds of problems occuring on the device.
As with the VTS logs, please include the Logcat in [CODE]<logcat text>[/CODE] tags.
Your Operating System version (eg. Windows 8, Windows Vista etc)
General information:
Can you reproduce the issue?
Did you try to restart your computer/your device first?
Click to expand...
Click to collapse
Feel free to propose me any new entries for this post

Something is badly messed up..
I used VTS v2.6.12 .. Until then everything was alright.. I used to decompile framework-res.apk, framework.jar, systemui.apk..
I never got any boot loop..
I downloaded and installed the latest version and ..
Whatever projects I made in v2.6.12 .. Were not recompiling.. May be because there was an update to apktool..
I had to make all new projects.. .
SystemUI.apk of my stock ROM is ~2.5mb.. After I decompile and recompile its size is like 5mb .. Why so??
I have to do everything manually ..
It never shows any error while decompiling or compiling..
How can i figure out where the problem is??

rkharat98 said:
Something is badly messed up..
I used VTS v2.6.12 .. Until then everything was alright.. I used to decompile framework-res.apk, framework.jar, systemui.apk..
I never got any boot loop..
I downloaded and installed the latest version and ..
Whatever projects I made in v2.6.12 .. Were not recompiling.. May be because there was an update to apktool..
I had to make all new projects.. .
SystemUI.apk of my stock ROM is ~2.5mb.. After I decompile and recompile its size is like 5mb .. Why so??
I have to do everything manually ..
It never shows any error while decompiling or compiling..
How can i figure out where the problem is??
Click to expand...
Click to collapse
You made a pretty big jump in versions there, I suspect the changes in the file formats prevented a proper loading of your old files.
Sorry for that, I never expected such large version jumps.
As for the size, in its default configuration VTS builds all binaries with no compression, whereas most binaries come with some compression. You can set the compression level in the settings of the zip module yourself. In any case, the size difference does no harm, you can leave it either way.

@Diamondback, great work.
Can I compile Apk via VTS? Example: I have sources and want to compile it with my drawables,XML,values. Thanks in Advance