Related
I've seen it asked quite a few times now, so I thought I would share how I've been creating my own themes for the Nook. This is a quick and dirty guide as I've almost got it down to a science for quick, keyboard shortcut, theming.
Things you'll need
Photoshop or The Gimp for editing files
Android SDK so you can push and pull files to/from the Nook.
draw9patch app in the Android SDK /tools folder for creating 9.png files
APK Manager (http://forum.xda-developers.com/showpost.php?p=6703735&postcount=1)
Notepad++ or some other text editor for editing XML files. After using Notepad++ on this, I'd highly recommend it though
An attention span
Some restraint
This is a rather good guide that helped me get started. My only complaint is that it is almost to complicated and includes more information than what is needed for a basic theme.
http://forum.xda-developers.com/showthread.php?t=916814
Getting Started:
Download the Android SDK and get it installed.
Download APK Manager
ADB pull /system/framework/framework-res.apk
Make a copy of the framework-res.apk files as a back-up in case you need to revert
Copy the framework-res.apk file to the /place-apk-here-for-modding folder under the APK Manager folder
Launch the APK Manager Script.bat file
Type in 22 to select the default project
Type in the number next to framework-res.apk in the list to select it as your project
Select 1 to extract the files
Select 9 to decompile (this is what makes the XML files readable)
Go to the /projects/framework-res/res folder under the APK Manager folder to view all the files from the theme
Images are located in the /drawable-mdpi folder. XML files are located throughout, but the files specific to layout are under the /layout folder. To change global settings, such as color codes and strings, edit the XML files under the /values folder.
Creating custom PNG files: If you are using Photoshop, use the Save For Web feature when saving. Save the image as PNG-24. Select None under the Matte option. Select None under Metadata.
A word on 9.png files: 9.png files are files that can be stretched by the OS. There is a 1 pixel border all the way around the image. In that 1 pixel border, you'll notice solid black lines here and there. The black pixels indicate which portions of the image are to be stretched. You can add this border and the black pixels in Gimp or Photoshop, or you can open the file the draw9patch app under the Android SDK /tools folder. The draw9patch app will actually display how the image will look when stretched as you add the black pixels around the border, so it can come in handy and it's what I prefer to use. You can open and edit .9.png files in draw9patch and edit the border even after you save the file.
Once you have all your files edited, recompile the APK package with APK Manager
Option 11
y
y
It will tell you to delete the files under the /keep folder that you have edited. Delete any images and XML files, from the /keep folder, you edited under the /projects folder. If you edited XML files, delete the /keep/res/resources.arsc file as well
Press any key to continue and let the script finish
In a separate command line window, mount your Nook's /system folder (adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system)
back in APK Manager, select 8
/system/framework/framework-res.apk
Reboot your Nook
Boot Loop: If you messed something up and are stuck in a boot loop, most of the time you can still mount your Nook, push the original framework-res.apk to it and reboot. Or, you can use an unedited version of the CWM flashable zip file from the link below.
NOTE: it is not smart to push your framework-res.apk file to the Nook. I've learned the hard way that you can only do this about 10 times before you run out of memory and can no longer boot your Nook until you reflash Froyo again.
I'd recommend only a few flashes on a bare bones copy of Froyo until you feel comfortable with working on the framework theme. After that, I'm attaching a base, flashable zip for you to use in CWM so you can flash the theme instead of pushing. This will prevent you from getting stuck in a boot loop (unless you do something wrong yourself).
To add your framework-res.apk file to the zip, just open the zip and replace the /system/framework/framework-res.apk file (I'd recommend 7zip).
A Few Goodies
I'm including all of the PSD files I use to edit and create themes. If you want to create your own, custom theme, these will get you started. The only downside to these PSD files is that they are at the MDPI scale. If you want to create an HDPI theme, you'll need to increase the sizes.
Link to PSD files for creating your own theme, plus the flashable CWM zip file:
http://jjis.me/android-theme-templates
Hey man, I know you theme the froyo roms, but Im attempting a theme for the Phiremod CM7 and I cant seem to get anything but splash hangs and bootloops. I theme CM7 for the hero so I know my way around that, but Im wondering if theres something about the Nook that I have to do differently. For instance what is the mount.sh file you have in the tools folder on your themes? Is that only for froyo? Any help you could give me would be appreciated.
PMDColeslaw said:
Hey man, I know you theme the froyo roms, but Im attempting a theme for the Phiremod CM7 and I cant seem to get anything but splash hangs and bootloops. I theme CM7 for the hero so I know my way around that, but Im wondering if theres something about the Nook that I have to do differently. For instance what is the mount.sh file you have in the tools folder on your themes? Is that only for froyo? Any help you could give me would be appreciated.
Click to expand...
Click to collapse
CM7 is a little different than the stock builds of Froyo and others. They use the theme manager for it. If you are looking to theme for CM7, I'd suggest learning what it is needed to package it for the theme manager. I spent about an hour one day trying to find documentation, but couldn't. If can, or have it, please let me know where to find it so I can link to it and use it myself.
With that said, it appears that CWM does not flash, or at least mount, the same on the Nook. I'm assuming it's because it's on the external SD card and not internal. The mount.sh file was borrowed from samuelhaff's flashable ROMs. It actually tells CWM to mount the internal memory and flash to it.
If you are flashing without the mount.sh, it could be why you're getting the boot loops.
CWM uses edify language instead of amend. Again, it took me forever to find little to no documentation on it.
If you are using the mount.sh file and you are still getting stuck in a boot loop, I did discover a little issue with it yesterday. I was trying to use it to flash my new theme without the Vending.apk mod and I kept getting stuck in a black screen during start up. I forgot my edify code deletes the Vending.apk file so that was causing my problem. If you know how to edit the file, go for it. If not, I'm planning on updating it to correct this. If you need to, for now, just copy the Vending.apk to your flashable zip file.
It deletes the services.jar file as well. This was a requirement on Froyo since the status bar text is black by default. The services.jar file has to be edited to change the status bar text to white. Since CM7 does not need that change, try pushing just the framework-res.apk file, reboot and see if you boot successfully. If so, that is more than likely your problem.
wretchedlocket said:
CM7 is a little different than the stock builds of Froyo and others. They use the theme manager for it. If you are looking to theme for CM7, I'd suggest learning what it is needed to package it for the theme manager. I spent about an hour one day trying to find documentation, but couldn't. If can, or have it, please let me know where to find it so I can link to it and use it myself.
With that said, it appears that CWM does not flash, or at least mount, the same on the Nook. I'm assuming it's because it's on the external SD card and not internal. The mount.sh file was borrowed from samuelhaff's flashable ROMs. It actually tells CWM to mount the internal memory and flash to it.
If you are flashing without the mount.sh, it could be why you're getting the boot loops.
CWM uses edify language instead of amend. Again, it took me forever to find little to no documentation on it.
If you are using the mount.sh file and you are still getting stuck in a boot loop, I did discover a little issue with it yesterday. I was trying to use it to flash my new theme without the Vending.apk mod and I kept getting stuck in a black screen during start up. I forgot my edify code deletes the Vending.apk file so that was causing my problem. If you know how to edit the file, go for it. If not, I'm planning on updating it to correct this. If you need to, for now, just copy the Vending.apk to your flashable zip file.
It deletes the services.jar file as well. This was a requirement on Froyo since the status bar text is black by default. The services.jar file has to be edited to change the status bar text to white. Since CM7 does not need that change, try pushing just the framework-res.apk file, reboot and see if you boot successfully. If so, that is more than likely your problem.
Click to expand...
Click to collapse
Thanks for the reply! I actually took yours apart and was able to correct my script and I noticed that the delete services.jar line was causing issues as well. If you can I'd like you to take a look at the updater script after I edited it and see if you see any errors. It's attached below. I have gotten the framework and other themed apps to flash fine, but for some reason the themed market will not install. After flash it is in the /system/app folder as vending.apk. but it doesn't actually replace the stock market anywhere else. I actually spent several hours today trying to get the market back because I got frustrated and went all delete happy in root explorer, lol.
As far as Theme Chooser goes, here is a decent tutorial, but I haven't taken the time to really try and change my whole MO to use it. I theme the aospCMod for the heroc without using the chooser app. You can also get some good tips on building themes for the chooser in the #aospbot irc channel. A few of the guys in there build themes for it.
View attachment updater-script.zip
PMDColeslaw said:
Thanks for the reply! I actually took yours apart and was able to correct my script and I noticed that the delete services.jar line was causing issues as well. If you can I'd like you to take a look at the updater script after I edited it and see if you see any errors. It's attached below. I have gotten the framework and other themed apps to flash fine, but for some reason the themed market will not install. After flash it is in the /system/app folder as vending.apk. but it doesn't actually replace the stock market anywhere else. I actually spent several hours today trying to get the market back because I got frustrated and went all delete happy in root explorer, lol.
As far as Theme Chooser goes, here is a decent tutorial, but I haven't taken the time to really try and change my whole MO to use it. I theme the aospCMod for the heroc without using the chooser app. You can also get some good tips on building themes for the chooser in the #aospbot irc channel. A few of the guys in there build themes for it.
View attachment 546902
Click to expand...
Click to collapse
Stupid question, but you are copying the vending file as Vending.apk and not vending.apk, correct?
Also, if you're using my themed market, there are only two icons that are customized. The rest looks stock.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
wretchedlocket said:
Stupid question, but you are copying the vending file as Vending.apk and not vending.apk, correct?
Also, if you're using my themed market, there are only two icons that are customized. The rest looks stock.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Click to expand...
Click to collapse
Yeah the file is Vending.apk but its my themed market.
Sent from my NookColor using Tapatalk
PMDColeslaw said:
Yeah the file is Vending.apk but its my themed market.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Sorry for the delay in response. I had too many things to do with the family yesterday.
If you haven't got this working yet, I'd suggest trying to start with removing just the /system/app/Vendind.apk file via the updater-script. If it works, then go back in and add each additional line until you run into problems again. At that point, you'll know what your problem is.
Since everything else (framework-res.apk, services.jar, etc.) gets replaced successfully, leave those lines alone. I'd just start with the basics of replacing the Vending.apk first and then work your way back up from there.
I dusted off a script I had been working on to allow easy customization on my original EVO.
It all still works on my rooted Evo 3D without many changes!
The script automates the use of adb. Downloads and decompiles the frameworks from your evo/evo 3d. Then you can make any desired changes (examples provided). Recompiles and uploads back to device.
Offering it for people to play with. I also included precompiled framework-res.apk and SystemUI.apk for those that like my choices. Otherwise use the script and create your own.
Enjoy
NEW! 1.1 Beta. Now creates flashable update zips
Beta update posted for new OTA
After recompiling your frameworks select option 5 from the Main Menu. An update.zip will be created in a directory called "flash" Try it out and please give feedback.
1 - Extract GingerScript to a folder on your desktop.
2 - Connect your phone via USB cable to your computer.
3 - Open the GingerScript folder you created and doubleclick on GingerScript.bat.
4 - Select item 1. (Process Framework-res.apk) This will download your framework-res.apk as well as create a back up in the /tools folder. When prompted, select yes to decompile this framework. This will create a folder called extracted-framework.res.
5 - This is where it gets tricky. Inside the extracted-framework.res folder, there is a folder called res. Inside THAT folder are multiple directories. The two you are concerned with are marked drawable and drawable-hdpi. *NOTE* In some builds the "drawable-hdpi" folder is named "drawable-hdpi-v4" Thats why it's best to modify your own framework.
6 - In the GingerScript folder, we will work with the Example.Icon.Framework-res.Circle.Battery folder. In this folder, you will find two directories: drawable and drawable-hdpi. Copy and paste the contents of the two directories from the Example folde into the corresponding folders in the extracted-framework.res/res directory. This may overwrite some of the files in each directory. This is okay!
7 - Go back to the script; it should still be on the gray screen. Select option 3 - recompile framework. This will take a minute or two so go grab a drink while it does its magic. It will seem to be hung; I don't have a progress bar created in the script so just hold tight while it finishes.
8 - Next, select option 4 - Upload new framework to phone. This will prompt you to put the phone in recovery mode; I'm not going to explain that part. Once the phone is in recovery mode Mount the /system partition using the recovery mount feature then press any key in the script window to push the file to your phone.
9 - At this point, clear the Dalvik Cache at a minimum and press a key once finished. the phone will reboot. Now, this provides the battery mod. To modify the other status bar icons, return to the main Menu and select option 3 to modify the systemUI.apk. The process is EXACTLY the same as the framework-res.apk but it uses the contents of the Example.Icons.SystemUI.mod directory. If problems occur, recover the backups from the /tools directory and push them to your phone.
I hope this helps. If you are still running into issues, please post what step you having issues with and remember, black and white goes with everything! *grin*
Do you install the apps or push them with abd, a little more clarity on how to install
Sent from my PG86100 using XDA App
dog44 said:
Do you install the apps or push them with abd, a little more clarity on how to install
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Extract the Gingerscript.zip on your Windows PC with your phone connected via USB.
Inside the folder double click on Gingerscript.bat. It's fairly easy to figure out from there, It creates a backup of the files before modification as a safety precaution. This just makes all of the framework compiliing/decompiling less of a hassle
Everything needed is in the zip file so you will need nothing except a text editor and a program to manipulate the png images. There are example folders in the zip that contain my modified png images and edited xml files
Note: The script references the use of Clockwork Mod Recovery, but TWRP works just as well. Just clear the Dalvik cache after uploading the framework. Then Reboot. I'll clean up the scripts wording at a later date
I will give it a shot here in a minute, and I will let you know how well it works.
I like your icons. Which APK does what?
The framework-res.apk contains the battery mod and a few minor icons. The rest of the status bar icons are in the SystemUI.apk.
The com-htc.resource.apk wasn't modified in my example, but it does contain images.
I wish there was a easy way to determine what resources are used but there isn't. Some status icons are located in the individual applications resource file as well (My script can't handle those)
I'm going to give this a go in a little bit when I can. Can anyone else confirm their success and any additional steps required (eg - clearing cache and dalvik). Thanks.
Can you please make a clear taskbar...thanxs
Can you make it simple zip file? so I can just flash it.
Thx
one up on this i like your blue battery ya got there, can ya make a zip for us
to flash please?
justwonder said:
Can you make it simple zip file? so I can just flash it.
Thx
Click to expand...
Click to collapse
That didnt work
Can you make a stock % battery?
Send from my Rooted HTC Evo 3D
nabbed said:
That didnt work
Click to expand...
Click to collapse
What part of "That" didn't work?
townsenk said:
What part of "That" didn't work?
Click to expand...
Click to collapse
After pushing the files, wiping dalvik cache, and rebooting, there was no status bar at all.
This is viper rom rc1.1, netarchy test3 kernel.
jayjay7411 said:
one up on this i like your blue battery ya got there, can ya make a zip for us
to flash please?
Click to expand...
Click to collapse
I've never been successfull creating a update.zip. I can never seem to get the syntax correct on the update-script.
If someone more experienced wants to create one, I'd love to take a look at it and see what I'm doing wrong.
nabbed said:
After pushing the files, wiping dalvik cache, and rebooting, there was no status bar at all.
This is viper rom rc1.1, netarchy test3 kernel.
Click to expand...
Click to collapse
Did you modify *Your* framework files or use the ones provided? The ones I used as examples are from a stock rom that is still odexed
I recommend you modify a copy of your own framework files since there may have been changes in the viper rom. It should still work. If you want you can send me a copy of your unaltered framework files and I can take a look.
mexiking713 said:
Can you make a stock % battery?
Send from my Rooted HTC Evo 3D
Click to expand...
Click to collapse
That requires the creation of about 60 new icons.
Easier method. Find me the icons..or even a Original Evo mod package and I can extract the icons from that.
townsenk said:
Did you modify *Your* framework files or use the ones provided? The ones I used as examples are from a stock rom that is still odexed
I recommend you modify a copy of your own framework files since there may have been changes in the viper rom. It should still work. If you want you can send me a copy of your unaltered framework files and I can take a look.
Click to expand...
Click to collapse
Ah! Viper is deodexed, so there's the problem right there.
Ill try to modify...
I have stock rom, if I do Push command and restart it should work right?
adb push new_SystemUI.apk /system/app/SystemUI.apk
adb push new_framework-res.apk /system/framework/framework-res.apk
justwonder said:
I have stock rom, if I do Push command and restart it should work right?
adb push new_SystemUI.apk /system/app/SystemUI.apk
adb push new_framework-res.apk /system/framework/framework-res.apk
Click to expand...
Click to collapse
That is correct - You'll still have to wipe the Dalvik and let it rebuild on boot
Let me know if it works for you
i installed the transparent statusbar mod in my xperia mini st15i.. i just want the original one back. i don't have a nand backup. can someone post the related apks here and tell me how to install them if a specific procedure is to be followed.
gandhar said:
i installed the transparent statusbar mod in my xperia mini st15i.. i just want the original one back. i don't have a nand backup. can someone post the related apks here and tell me how to install them if a specific procedure is to be followed.
Click to expand...
Click to collapse
Someone with mini have to help you. But since no one replying, and to save your time from searching all over the web;
To know which apk that has been modified, open the mod that you have applied using archive apps (winrar should do if you are in windows) and see what apk is inside (generally it should be framework-res.apk and/or SystemUI.apk)
To revert back, one of the way is to extract that apk from stock fw file, copy to your /system/ then change permission rw-r--r-- (if you dont know what it means, just refer to any apk inside /system/app/ permission's, they are all the same generally for /system/app/ and /system/framework/ ). Then, move it to appropiate folder replacing the current file (SystemUI.apk into /system/app/ for example. Better to replace systemui.apk first before framework-res.apk to avoid unexpected fc in the process)
Once done, reboot.
Other ways, ask anyone to make cwm compatible zip file for you to revert back to original or wait for someone to post the apk's here for you.
Thats a very good lessons actually, do a backup first before doing/modifying anything. Dont just simply flash any zip file, see first whats inside, backup whatever files that is affected by that zip to your sdcard is the fastest way (but not 100% reliable compare to make a backup in cwm.
Anyhow, good luck. cheers fren.
Sent from my SK17i using XDA App
feed3 said:
Someone with mini have to help you. But since no one replying, and to save your time from searching all over the web;
To know which apk that has been modified, open the mod that you have applied using archive apps (winrar should do if you are in windows) and see what apk is inside (generally it should be framework-res.apk and/or SystemUI.apk)
To revert back, one of the way is to extract that apk from stock fw file, copy to your /system/ then change permission rw-r--r-- (if you dont know what it means, just refer to any apk inside /system/app/ permission's, they are all the same generally for /system/app/ and /system/framework/ ). Then, move it to appropiate folder replacing the current file (SystemUI.apk into /system/app/ for example. Better to replace systemui.apk first before framework-res.apk to avoid unexpected fc in the process)
Once done, reboot.
Other ways, ask anyone to make cwm compatible zip file for you to revert back to original or wait for someone to post the apk's here for you.
Thats a very good lessons actually, do a backup first before doing/modifying anything. Dont just simply flash any zip file, see first whats inside, backup whatever files that is affected by that zip to your sdcard is the fastest way (but not 100% reliable compare to make a backup in cwm.
Anyhow, good luck. cheers fren.
Sent from my SK17i using XDA App
Click to expand...
Click to collapse
i got it from a friend, thanks anyway.
Can anyone tell me if its possible to add the 1% battery mod to a stock odex ics rom? I have a moto razr maxx. Is there a way i can mod this myself? I tried uot kitchen but it only shows increments of 10% on my phone.
Thanks!
Yes, it can be done. My phone's ROM is the stock odexed ROM and I have 1% battery increments. You need to edit framework-res.apk, you can use apktool or APK Multi Tool or whatever to unpack the APK, and rebuild it afterwards. To get 1% battery, you need to edit/replace some XMLs.
I'll try find a link to show how the XMLs should be and some commonly used icons.
EDIT: Here: http://forum.xda-developers.com/showthread.php?t=724778
Find a style you like, download it and copy the two folders from inside into the "res" folder in your unpacked APK, overwriting any existing files (you may need to rename the drawable-hdpi-v4 folder depending on your phones resolution)
But UOT should work. Make sure in the "battery" section you changed at the top from "Custom battery" to "SCB with %" and then selected the style you want.
SifJar said:
Yes, it can be done. My phone's ROM is the stock odexed ROM and I have 1% battery increments. You need to edit framework-res.apk, you can use apktool or APK Multi Tool or whatever to unpack the APK, and rebuild it afterwards. To get 1% battery, you need to edit/replace some XMLs.
I'll try find a link to show how the XMLs should be and some commonly used icons.
EDIT: Here: http://forum.xda-developers.com/showthread.php?t=724778
Find a style you like, download it and copy the two folders from inside into the "res" folder in your unpacked APK, overwriting any existing files (you may need to rename the drawable-hdpi-v4 folder depending on your phones resolution)
But UOT should work. Make sure in the "battery" section you changed at the top from "Custom battery" to "SCB with %" and then selected the style you want.
Click to expand...
Click to collapse
what phone do you have? i already tried the uot and it will not work. from what im understanding you would need to edit the systemUI.odex file to allow for battery % but i have no clue how to do it.
fix-this! said:
what phone do you have? i already tried the uot and it will not work. from what im understanding you would need to edit the systemUI.odex file to allow for battery % but i have no clue how to do it.
Click to expand...
Click to collapse
I have an HTC Explorer. But I believe the battery icon is stored in framework-res.apk, and not SystemUI.apk, so SystemUI.odex shouldn't be a problem (SystemUI.odex is the odex file of SystemUI.apk - you can't edit odexed apps, you would have to deodex SystemUI.apk first; this means combining the SystemUI.odex and SystemUI.apk files into one, deodexed SystemUI.apk, which can then be edited).
Although UOT may require you to upload a deodexed SystemUI.apk along with framework-res.apk, because some theme mods required SystemUI.apk. So you might need to get a deodexed SystemUI.apk. There's a guide to deodexing here: http://forum.xda-developers.com/showthread.php?t=1208320
It is a slightly complicated process, but it's not impossible to figure out I don't know for sure if this is what you need to do to make it work though. Make sure you have a nandroid backup before you flash the theme
i guess ill wait for a dev to deodex the stock rom then. the uot kitchen states it can work on odex roms but in my case it does not.
fix-this! said:
Can anyone tell me if its possible to add the 1% battery mod to a stock odex ics rom? I have a moto razr maxx. Is there a way i can mod this myself? I tried uot kitchen but it only shows increments of 10% on my phone.
Thanks!
Click to expand...
Click to collapse
Anything's possible... See HERE, HERE, and a mini re-odex tutorial HERE.
And, I believe there were some major framework/system changes in the transition from GB to ICS - so, the battery files may have moved to SystemUI from framework-res..
alteredlikeness said:
Anything's possible... See HERE, HERE, and a mini re-odex tutorial HERE.
And, I believe there were some major framework/system changes in the transition from GB to ICS - so, the battery files may have moved to SystemUI from framework-res..
Click to expand...
Click to collapse
thanks for that but it's a bit too over my head to attempt myself. if i uploaded my systemUI & systemUI.odex do you think you could help me out?
fix-this! said:
thanks for that but it's a bit too over my head to attempt myself. if i uploaded my systemUI & systemUI.odex do you think you could help me out?
Click to expand...
Click to collapse
You'd also need to upload all the .jar and .odex files from /system/framework I think to make it possible to deodex systemUI.apk.
EDIT: If you do that, I should probably be able to deodex it for you. (Assuming that process hasn't changed for ICS, which I don't think it has). Once you have this file deodexed, you should be able to use UOT, it supports ICS battery mods.
EDIT: If you need an easy way to copy those files off the phone, you can try this: http://androidcommander.com/
fix-this! said:
thanks for that but it's a bit too over my head to attempt myself. if i uploaded my systemUI & systemUI.odex do you think you could help me out?
Click to expand...
Click to collapse
Sorry, but I'm not too familiar with ICS yet... eagerly waiting Q3 for my phone.
Plus, I ported the battery from a deodexed set so I don't know all of the smali/xml edits involved if I were to do it from scratch...
You could still upload a whole system dump or cwm backup for me to look at ...if you wanted to. It'll let me get familiar with Moto's ICS..
SifJar said:
You'd also need to upload all the .jar and .odex files from /system/framework I think to make it possible to deodex systemUI.apk.
EDIT: If you do that, I should probably be able to deodex it for you. (Assuming that process hasn't changed for ICS, which I don't think it has). Once you have this file deodexed, you should be able to use UOT, it supports ICS battery mods.
EDIT: If you need an easy way to copy those files off the phone, you can try this: http://androidcommander.com/
Click to expand...
Click to collapse
im uploading now if someone can do this for me, i cannot figure it out. the razr devs do not seem interested in doing this on a ics leak.
http://www.mediafire.com/?m1i08symjcalvy4
uploaded system/framework & app
fix-this! said:
http://www.mediafire.com/?m1i08symjcalvy4
uploaded system/framework & app
Click to expand...
Click to collapse
Downloading now, provided it works I should have it up in 15 - 20 mins
EDIT: Appears it's a bit different, trying another approach now which will take a bit longer, but seems to be working for now at least (doing it this way means deodexing all the files).
EDIT: I'll try and get SystemUI.apk uploaded tonight, the rest will have to wait to tomorrow if you want them.
EDIT: There is a possibility I will need "init.rc" from the root of your device (i.e. not inside any folders like "system" or "data") to properly deodex all the files. A few seem to be giving errors and stuff.
Here's the (hopefully) deodexed SystemUI.apk [well, it IS deodexed, the "hopefully" refers to hopefully it's done right]. Try this with UOT (along with framework-res.apk, which isn't odexed in the first place), and as I said before, be sure to make a nandroid backup before hand.
You may also need to delete the SystemUI.odex file from your phone after applying the theme, I am not completely sure. If after applying the theme it has not worked, try doing so - worst case scenario you should be able to restore your nandroid backup if deleting the .odex file breaks something.
SifJar said:
Downloading now, provided it works I should have it up in 15 - 20 mins
EDIT: Appears it's a bit different, trying another approach now which will take a bit longer, but seems to be working for now at least (doing it this way means deodexing all the files).
EDIT: I'll try and get SystemUI.apk uploaded tonight, the rest will have to wait to tomorrow if you want them.
EDIT: There is a possibility I will need "init.rc" from the root of your device (i.e. not inside any folders like "system" or "data") to properly deodex all the files. A few seem to be giving errors and stuff.
Click to expand...
Click to collapse
heres the file you need to deodex.
fix-this! said:
heres the file you need to deodex.
Click to expand...
Click to collapse
Thanks. I can try deodex all the jars and apks with that tomorrow if you want. For now, SystemUI.apk seems to have deodexed fine without it, so you can grab it above and try UOT with it (that's the only file UOT needs other than framework-res.apk which isn't odexed anyway). Let me know if it works
SifJar said:
Thanks. I can try deodex all the jars and apks with that tomorrow if you want. For now, SystemUI.apk seems to have deodexed fine without it, so you can grab it above and try UOT with it (that's the only file UOT needs other than framework-res.apk which isn't odexed anyway). Let me know if it works
Click to expand...
Click to collapse
ill try it but if you think you could deodex everything that would be great.
used uot with the modded systemUI and it didn't work, still only getting 10% increments. i think the entire system/app & framework needs to be deodexed.
fix-this! said:
used uot with the modded systemUI and it didn't work, still only getting 10% increments. i think the entire system/app & framework needs to be deodexed.
Click to expand...
Click to collapse
Just found this HERE - looks like a good 1% battery tutorial...
But, from the look of your system, you have battery files (images/xmls) in BOTH the SystemUI.apk and framework-res.apk - how's that?
I don't think I'll be able to upload the deodexed files. It'd be a large file, and I don't really want to waste the bandwidth I'm afraid.
It's not a hard process for you to do though. There are two main options. Either buy Titanium Backup Pro for your phone, and then load it up and press menu, then "more" and then "Undo sys Dalvik integration..." which will deodex everything in /system/app (but not /system/framework), or else download this: http://forum.xda-developers.com/attachment.php?attachmentid=972719&d=1333088601 (I'd strongly recommend this second method)
Extract the ZIP, and place everything from /system/app in "_app" and everything from /system/framework in "_framework". Run AutoDEOToolMain.bat. Select option 2, then paste in this as the custom BootClassPath:
Code:
core.jar:core-junit.jar:bouncycastle.jar:ext.jar:framework.jar:framework-ext.jar:android.policy.jar:services.jar:apache-xml.jar:filterfw.jar:com.motorola.android.frameworks.jar:com.motorola.android.widget.jar:com.motorola.frameworks.core.addon.jar
Let it run, and all the deodexed files will be in the deodexed folders. Any files that weren't deodexed will be in the original folders.
This is really quite an easy process, so I'm sure you could achieve it yourself.
EDIT: There still seem to be a couple of errors with the above BootClassPath, the following two JARs seem to be missing: /system/framework/kafdex.jar and /system/framework/com.motorola.orange.simauth.jar (I removed them from the BootClassPath because the JARs were missing, if you can find these two JARs add :kafdex.jar:com.motorola.orange.simauth.jar to the end of the above BootClassPath and put the two JARs in "_framework". Then I think you will be able to deodex every JAR and APK. Without them, most still seem to work though. (A number of the APKs in /system/app do not deodex properly. A little googling has shown me that motorola often neglect to include com.motorola.orange.simauth.jar on their phones [probably to try and stop deodexing] and this is the main problem)
EDIT: Try using this tool to mod your battery: http://forum.xda-developers.com/showthread.php?t=1434061
Use the deodexed SystemUI.apk along with the standard framework-res.apk, and download one of the 1% battery mods from that thread. I really don't think the rest of the system apps being odexed should cause an issue.
Based on process for galaxy nexus http://forum.xda-developers.com/showthread.php?t=1413582
See also; http://forum.xda-developers.com/showthread.php?t=1724112
Required;
Root
PNGs of desired icons (get them at galaxy nexus post, link above)
Root Browser (or other decent file manager)
Custom ROM (maybe, not tested on stock)
The usual anti-warranty applies; use at your own risk, use common sense, back up your files, back up your System partition
Decompress your systemUI.apk file from /system/app and replace the system icon PNGs in the /res/drawable-sw600dp-mdpi directory with the PNGs downloadable from the above link, giving them the same name as those in the prexisting .apk, then re-zip rename it as "systemUI.apk", and replace the original systemUI.apk in /system/app. Then set permissions to rw-r-r, and reboot. Confirmed working only on custom Roms.
Edit: note when you decompress, you'll get a folder called systemUI. When you go to re-zip, you want to multi-select the contents of that folder and then make a zip of them to normal compression. Then rename the product .zip file as systemUI.apk. its probably a good idea to backup your original systemUI.apk... You should modify the systemUI.apk from your ROM, or be running the same ROM as myself, just to be safe- i have not tested mixing and matching ROMs and systemUI's and it could be potentially dangerous, as I cannot guarantee that they will be compatable.
Attatched- my screenshot (im using a subtle reflection theme) and a modified systemUI.apk (from the screenshot) - only tested on the ROM I'm using - a cm10 euroskank nightly
*don't try to install sysuemUI.apk like an app, it will do nothing.
Known bugs- no downward ^ when keyboard is up (probably an easy fix)- this is because the galaxy nexus files do not include one...
I take no credit for this process, only for writing this post. All credit goes to the author of the original galaxy nexus post
Feel free to post your screenshots and modified systemUI.apk's This is my first how-to, so let me know what you think, and how I can improve it. I'm an official noob, so I'm sure I've left something out. Let me know anything I could mention regarding other custom and stock ROMs as well. Don't forget to hit Thanks