Develop Bugs

Circular Battery on Status Bar

Use adb from Android SDK, the tools directory
(http://developer.android.com/sdk/index.html)
1) Pull framework-res.apk from /system/framework/ by command:
> adb pull /system/framework/framework-res.apk .
2) Make a copy of the original framework-res.apk to framework-res-original.apk in your tools folder (in case you screw things up )
3) Rename framework-res.apk in your tools folder to framework-res.zip
4) Open framework-res.zip
5) Replace the "circular battery" files I have attached to res/drawable-mdpi directory in the zip file
6) Use normal compression when replacing the files
7) Rename the zip file back to apk extension
8) Push framework-res.apk back to /system/framework by commands:
> adb remount
> adb push framework-res.apk /system/framework/
> adb shell reboot
Credit to giant_rider, I pulled the files out from his SuperEclair ROM
If anyone wants to create an signed apk for easy update, be my guest

awesome, will definitely use!

Need Help
I have tried this twice & it always reverts back to the standard battery icons. I push the new file with the circular battery files you uploaded. However, when I pull the framework file again to check the icons(after I reboot my phone & see that it hasn't changed) it its back to normal with the standard ones. I can't imagine why Any ideas ? ? ?

( M3GA ) said:
I have tried this twice & it always reverts back to the standard battery icons. I push the new file with the circular battery files you uploaded. However, when I pull the framework file again to check the icons(after I reboot my phone & see that it hasn't changed) it its back to normal with the standard ones. I can't imagine why Any ideas ? ? ?
Click to expand...
Click to collapse
Ready for Stericson's Metamorph apk
http://www.ansemreport.com/Kspec/KspecBattery.zip

raspdeep said:
5) Replace the "circular battery" files I have attached to res/drawable-mdpi directory in the zip file
Click to expand...
Click to collapse
i am confuse with this step, my original file only has "drawable" & "drawable-land" folders, so do i add a new folder containing your circular battery png called "drawable-mdpi"
my Magic just stay on the splash screen when i do this
----------------------
so i restore and try replace the circular battery png to the original battery png in my "drawable" (copy n paste)
my Magic still stay on the splash screen.
pls help

I have tried this twice & it always reverts back to the standard battery icons. I push the new file with the circular battery files you uploaded. Howe
Click to expand...
Click to collapse
Ready for Stericson's Metamorph apk
http://www.ansemreport.com/Kspec/KspecBattery.zip
Click to expand...
Click to collapse
Thanks. Can it be applyed to any rom?
-------------------------------------
Sent via the XDA Tapatalk App

Evil-Monkey said:
Thanks. Can it be applyed to any rom?
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
it worked for me on CM4.x.x.x donut and CM5
its actually very simple, just follow step (1) and pull the file, look for your original battery png files and replace it with the circular battery files, both original and circular battery status should have the same png file names

kakyoin said:
it worked for me on CM4.x.x.x donut and CM5
its actually very simple, just follow step (1) and pull the file, look for your original battery png files and replace it with the circular battery files, both original and circular battery status should have the same png file names
Click to expand...
Click to collapse
sweet. Im currently running pays 1.6 and i want to try to run an eclair but theyre all ugly as hell and i dont want a fully themed rom, i just want specific icons ect.
ive been looking into this for a while So i have some noob questions if you will.
1: do i need to "re-sign" the apk?
2: can i apply this method to all the icons on a rom.
for example, i like the "dowloading" icon from my current rom but would like it on an the eclair.
same goes for the text icon on the notifications bar, i like the green one but clair normally uses a black one
could i switch them out?

rgawenda said:
Ready for Stericson's Metamorph apk
http://www.ansemreport.com/Kspec/KspecBattery.zip
Click to expand...
Click to collapse
i tried this and metamorph wouldnt do it.

issues with cm6
i am consistantly getting an error message when trying to push the file onto the device stating that the device does not have room has this been addressed?
C:\androidSDK\tools>adb push framework-res.apk /system/framework
failed to copy 'framework-res.apk' to '/system/framework/framework-res.apk': No
space left on device
Click to expand...
Click to collapse

Keep on pushing it? I did that until it finally got transferred ..
Alternatively, you can delete the previous framework apk and push the updated one.
Sent from my HTC Magic using XDA App

Tried the original method on Fresh 1.0.1, Pulled file, edited, re-pushed, got stuck at white boot screen, the one that says HTC EVO 4G or something like that.

just get metamorph from market and dr.cloverdale black bar metamorph. replace necessary battery images in black bar zip and no need to sign or push via adb.

This battery is awsome, I'm busy with my own notification bar so I can really use this!

What really is Missing is an step right before remounting the ADB.
Try the Following Steps:
1) Pull framework-res.apk from /system/framework/ by command:
> adb pull /system/framework/framework-res.apk .
2) Make a copy of the original framework-res.apk to framework-res-original.apk in your tools folder (in case you screw things up )
3) Rename framework-res.apk in your tools folder to framework-res.zip
4) Open framework-res.zip
5) Replace the "circular battery" files I have attached to res/drawable-mdpi directory in the zip file
6) Use normal compression when replacing the files
7) Rename the zip file back to apk extension
8) Restart the phone till you get to the End of the "Boot Loop" and be able to reconnect to phone again with using ADB and Entering Following command:
> adb shell reboot
9) Then push framework-res.apk back to /system/framework by commands:
> adb remount
> adb push framework-res.apk /system/framework/
> adb shell reboot
Have Fun...
Amir.

Thanks.
Followed Amir's steps and now I have circular battery .
ROM: CursorSence

Hi guys
made this small app might help, no need to root / install new ROM / Alter framework-res.apk
it gives you circular battery indicator with percentages (up to 1% if your device supports it)
just download and install the app to your device
it works with Desire and Droid X perfectly, not sure about other devices
http://forum.xda-developers.com/showthread.php?t=809553
let me know if it worked for you
cheers

Irkan, love the app. Works perfect on my MT3g 32b with CM6, and I really like the temp stats in notification bar too. Nice work

I am on the CM nightlies and trying to replace files in the framework-res.apk and putting it back messes with my phone for some odd reason. Is there anyway someone who knows their stuff make it flashable?

root?
Hello.
Must I have root-rights to do it?
Cause, when I adb Shell it and use the first command from step 1, it says:
adb pull: permission denied.
Thx

[REF] Choosing between GlassLock and Android's stock lock screen

Hi guys,
Since there seems to be some demand for this kind of thing, I decided to post instructions on a mod I made a while back. This gives you the option of choosing between Samsung's GlassLock (i.e. the default TW lockscreen) or the stock keyguard of Android 2.1.
The method involves de- and re-compiling /system/framework/android.policy.odex, and you should have some basic knowledge of the tools involved (i'm not gonna spell out every step). Before beginning, take a backup of android.policy.jar and android.policy.odex (or preferably the whole framework folder). You should issue the commands in recovery mode.
Required tools: rooted SGS (I've done this only with JM2, and the code *might* need modifying for other roms, though I doubt it), adb, smali/baksmali, dexopt-wrapper, text & hex editor, winrar (or any jar editor).
Here we go:
1. Use adb to pull out /system/framework/android.policy.odex and other framework .odexes (required for de-odexing). Might be wise to backup the whole /system/framework/ directory at this point.
2. Use baksmali to deodex the file (java -jar baksmali.jar -x android.policy.odex -o android.policy). Baksmali will let you know if you are missing any of the framework .odexes.
3. Open LockPatternKeyguardView.smali and find the method getLockScreenMode()Lcom/android/internal/policy/impl/LockPatternKeyguardView$LockScreenMode;
4. Replace the contents of this method with the attached file getLockScreenMode.txt.
5. Save LockPatternKeyguardView.smali.
6. Use smali to compile the files back to classes.dex (java -jar smali.jar android.policy -o classes.dex)
7. Pull /system/framework/android.policy.jar, add the newly created classes.dex to it, and push it back to the device.
8. On your phone, do:
# cd /system/framework
# dexopt-wrapper android.policy.jar patched.odex /system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar
Ouput should be:
--- BEGIN 'android.policy.jar' (bootstrap=0) ---
--- would reduce privs here
--- waiting for verify+opt, pid=3105
--- END 'android.policy.jar' (success) ---
9. You now have odexed the file into patched.odex. However, the signature of the file is not compatible with the other framework files, so you need to fix it. I think the proper way should be to re-odex all the framework files, but I haven't encountered any issues with just patching the signature.
10. Open the original android.policy.odex in a hex editor, and copy signature bytes from offsets 0x34-0x47 to the new patched.odex, and save it. Optionally, you can also do this on your device by issuing the command:
# dd if=original.android.policy.odex of=patched.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
Where if="..." is the original file, and of="..." is the file you want to patch.
11. Push the patched and hex-edited file to /system/framework/android.policy.odex and restore the original /system/framework/android.policy.jar.
12. Reboot and enjoy your good ol' keyguard
Some notes:
- If you want to revert back to Samsung's lock screen, just create a file called /data/local/enable_glass_lock ("adb touch /data/local/enable_glass_lock").
- By default, the menu button will also unlock the screen. To disable this behavior, you have to modify /res/values-hdpi-v4/bools.xml in /system/framework/framework-res.apk, and change the value of <bool name="config_disableMenuKeyInLockScreen">false</bool> to true. Can also be done by modifying code.
On a side note, the code for Smart Unlock (present in some Samsung phones) seems to be in there... it would be an interesting project to get that working

Great stuff, i've been waiting for someone to find out how to get rid of the glass screeen since first day.
Sadly i'm a real noob so it is useless for me.
Maybe someone can create an apk or a win program out of this.

thank you !
but could you explain it better ?

toca79 said:
Maybe someone can create an apk or a win program out of this.
Click to expand...
Click to collapse
+1 for an automated solution, provided method seems too hard for me.

Excellent post Ateisti! We need more of these advanced mods for SGS.

Ateisti said:
adb, smali/baksmali, dexopt-wrapper,
Click to expand...
Click to collapse
Could you provide links to this?
Or are those sw included in the Android SDK?

I want to do 6-step but I see:
Code:
C:\Users\Konrad>"C:\Program Files (x86)\Java\jre6\bin\java.exe" -jar "C
:\Users\Konrad\Desktop\smali.jar" android.policy -o classes.dex
android.policy\com\android\internal\policy\impl\LockPatternKeyguardView$LockScre
enMode.smali[0,-1] The file must contain a .class directive
What's wrong?
EDIT:
I've changed a wrong smali.

In step 10, how do i copy the signature bytes with my hex editor? I dont understand what offsets 0x34-0x57 is...
10. Open the original android.policy.odex and copy signature bytes from offsets 0x34-0x47 to the new patched.odex, and save it.
Click to expand...
Click to collapse

Can anyone who successfully coped with getting this done following the instructions above please do a video showing us how to do it, I think that might help us a lot... thanks a lot on behalf of us noobs

Stefanauss said:
Could you provide links to this?
Or are those sw included in the Android SDK?
Click to expand...
Click to collapse
ADB is included in the SDK, Smali and Baksmali can be downloaded here and dexopt-wrapper for example here.
qwas00 said:
In step 10, how do i copy the signature bytes with my hex editor? I dont understand what offsets 0x34-0x57 is...
Click to expand...
Click to collapse
It means to seek to the 52nd byte (or 0x34 in hex) of the file, and then copy and replace the following 20 bytes to the second file. But you can also do it on the device by issuing this command (I think busybox is required):
dd if=original.android.policy.odex of=patched.android.policy.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
...where "if=..." is the original file and "of=..." is the file you want to patch.

Ateisti said:
Hi guys,
Since there seems to be some demand for this kind of thing, I decided to post instructions on a mod I made a while back. This gives you the option of choosing between Samsung's GlassLock (i.e. the default TW lockscreen) or the stock keyguard of Android 2.1.
The method involves de- and re-compiling /system/framework/android.policy.odex, and you should have some basic knowledge of the tools involved (i'm not gonna spell out every step). Before beginning, take a backup of android.policy.jar and android.policy.odex (or preferably the whole framework folder). You should issue the commands in recovery mode.
Required tools: rooted SGS (I've done this only with JM2, and the code *might* need modifying for other roms, though I doubt it), adb, smali/baksmali, dexopt-wrapper, text & hex editor, winrar (or any jar editor).
Here we go:
1. Use adb to pull out /system/framework/android.policy.odex and other framework .odexes (required for de-odexing). Might be wise to backup the whole /system/framework/ directory at this point.
2. Use baksmali to deodex the file (java -jar baksmali.jar -x android.policy.odex -o android.policy). Baksmali will let you know if you are missing any of the framework .odexes.
3. Open LockPatternKeyguardView.smali and find the method getLockScreenMode()Lcom/android/internal/policy/impl/LockPatternKeyguardView$LockScreenMode;
4. Replace the contents of this method with the attached file getLockScreenMode.txt.
5. Save LockPatternKeyguardView.smali.
6. Use smali to compile the files back to classes.dex (java -jar smali.jar android.policy -o classes.dex)
7. Pull /system/framework/android.policy.jar, add the newly created classes.dex to it, and push it back to the device.
8. On your phone, do:
# cd /system/framework
# dexopt-wrapper android.policy.jar patched.odex /system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar
Ouput should be:
--- BEGIN 'android.policy.jar' (bootstrap=0) ---
--- would reduce privs here
--- waiting for verify+opt, pid=3105
--- END 'android.policy.jar' (success) ---
9. You now have odexed the file into patched.odex. However, the signature of the file is not compatible with the other framework files, so you need to fix it. I think the proper way should be to re-odex all the framework files, but I haven't encountered any issues with just patching the signature.
10. Open the original android.policy.odex and copy signature bytes from offsets 0x34-0x47 to the new patched.odex, and save it.
11. Push the patched and hex-edited file to /system/framework/android.policy.odex and restore the original /system/framework/android.policy.jar.
12. Reboot and enjoy your good ol' keyguard
Some notes:
- If you want to revert back to Samsung's lock screen, just create a file called /data/local/enable_glass_lock ("adb touch /data/local/enable_glass_lock").
- By default, the menu button will also unlock the screen. To disable this behavior, you have to modify /res/values-hdpi-v4/bools.xml in /system/framework/framework-res.apk, and change the value of <bool name="config_disableMenuKeyInLockScreen">false</bool> to true. Can also be done by modifying code.
On a side note, the code for Smart Unlock (present in some Samsung phones) seems to be in there... it would be an interesting project to get that working
Click to expand...
Click to collapse
THANX TO ALL YOUR EFFORTS........ can you please attach a screen shot of the lock what you are talking about.. and does it work flawlessly without any sort of a lag.. and is it 100% bugs free?????

Could you also choose any other lockscreen, like WidgetLocker or SimplyLockscreen?
That would be great

Ateisti said:
It means to seek to the 52nd byte (or 0x34 in hex) of the file, and then copy and replace the following 20 bytes to the second file. But you can also do it on the device by issuing this command (I think busybox is required):
dd if=original.android.policy.odex of=patched.android.policy.odex bs=1 count=20 skip=52 seek=52 conv=notrunc
...where "if=..." is the original file and "of=..." is the file you want to patch.
Click to expand...
Click to collapse
Thanks, that worked fine

Thanks! This method worked like a charm. I hated that glass unlock thingy.
However my /system/framework/framework-res.apk doesn't have a value folder, so I can't remove the possibility to unlock with the menu button.
Couldn't find any bools.xml in there at all.

This is replacing the music player controls when the screen is locked, right? It's a nice functionality and would be a pity to loose it.
Otherwise its a great mod and it would be cool if someone can make the One Click LockScreen Changer ;-)
Sent from my GT-I9000 using Tapatalk

thE_29 said:
Could you also choose any other lockscreen, like WidgetLocker or SimplyLockscreen?
That would be great
Click to expand...
Click to collapse
Not as such, but technically it should be possible with some additional coding. I however don't have the time to undertake such a task.
Tharfrin said:
Thanks! This method worked like a charm. I hated that glass unlock thingy.
However my /system/framework/framework-res.apk doesn't have a value folder, so I can't remove the possibility to unlock with the menu button.
Couldn't find any bools.xml in there at all.
Click to expand...
Click to collapse
This might be a ROM version thingy. On my system there are actually two XML files with that same setting, but only one of them works (the one I mentioned in my original post). Just search all your framework-res xml files for "config_disableMenuKeyInLockScreen", and change every instance to true. Should do the trick.
Or if all else fails, just edit the file LockScreen.smali, method "shouldEnableMenuKey()", and make it always return 0 ("return v4" -> "return v6").
mobilx said:
This is replacing the music player controls when the screen is locked, right? It's a nice functionality and would be a pity to loose it.
Otherwise its a great mod and it would be cool if someone can make the One Click LockScreen Changer ;-)
Click to expand...
Click to collapse
That is unfortunately the case. The music controls (as well as the puzzle pieces) are coded into the GlassLock class, so it would required some additional reverse engineering to implement those in the stock keyguard.

4 hours working and it works (jm2).
I'm going to test on the jpc.
EDIT:
I put it on the jpc and it doesn't work.

Did not work with JPC I really want to use the stock lockscreen!
Sent from my GT-I9000 using XDA App

hi guy thanks for your instruction. However I'm using samset's 1.9f which has the ROM deodexed and i found no .odex files but .jar files. Is there a way to workaround this? I'd really love to revert back to stock eclair lockscreen~!

billytcf said:
hi guy thanks for your instruction. However I'm using samset's 1.9f which has the ROM deodexed and i found no .odex files but .jar files. Is there a way to workaround this? I'd really love to revert back to stock eclair lockscreen~!
Click to expand...
Click to collapse
same here no odex files...

ICS blue notification icons

I did a search but could not find a theme that changes all the notification icons in the notification bar (i.e. for talk/ gmail/ whatsapp etc etc) + the alarm clock & vibrate icon to ICS blue.
Is there a theme out there that does exactly that?

I already made a few of these for a widget, I can make a set and upload them. You would have to adb pull SystemUI.apk, replace the png's, and then push it back to system/app.

Thank you very much!
But before you go any length, let me please read up on what you just said

What rom are you using? I can throw them in for you.

Without doing it for me- that just deserves another thank you
At this moment I'm on AOKP b27 but that varies quite a bit
So instead of you doing all the work for me (may be it is best to learn it myself since I change ROMS fairly often), would you care to help me a bit?
This is what I've found:
1. Root is prerequisite. If you're using stock rom, you can obtain cf-root from here.
2. Install android sdk from here. Eclipse is optional. The essential stuff we need is the adb from the sdk.
3. Please make a backup using cwm in case you end up deleting or corrupting your phone.
4. Connect your phone to the pc.
5. Open cmd and type cd C:\android\tools . (Depends on where is your sdk tools folder)
6. type adb pull /system/app/SystemUI.apk (Status Bar Modding)
7. Alright, now edit the .apk to .zip in your tools folder.
8. Open up the zip and replace the mdpi files inside with the one you prepared.
9. After all the changes, change the .zip back to .apk
10. Open cmd and type cd C:\android\tools . (Depends on where is your sdk tools folder)
11. type adb push SystemUI.apk /system/app/SystemUI.apk
12. Reboot your phone.
Courtesy of terrymcnuggets in this topic.
My questions; regarding
7. Alright, now edit the .apk to .zip in your tools folder; and
9. After all the changes, change the .zip back to .apk
Do i rename the .apk to .zip or do I create a .zip?
AND
8. Open up the zip and replace the mdpi files inside with the one you prepared.
the files you would be prepared to share are mdpi files? not .png?
The icons I want in ICS blue (#FF33B5E5 - or same color as the time etc in te notifcation (top) bar) are: Bluetooth icon, Vibrate icon, Alarm icon, and all of the notication icons (talk/ gmail/ whatsapp etc)
If you'd rather point me out in the directio on how to change them myself that would be great too (Photoshop?)
Many many thanks for your time

Ti2 said:
Without doing it for me- that just deserves another thank you
At this moment I'm on AOKP b27 but that varies quite a bit
So instead of you doing all the work for me (may be it is best to learn it myself since I change ROMS fairly often), would you care to help me a bit?
This is what I've found:
1. Root is prerequisite. If you're using stock rom, you can obtain cf-root from here.
2. Install android sdk from here. Eclipse is optional. The essential stuff we need is the adb from the sdk.
3. Please make a backup using cwm in case you end up deleting or corrupting your phone.
4. Connect your phone to the pc.
5. Open cmd and type cd C:\android\tools . (Depends on where is your sdk tools folder)
6. type adb pull /system/app/SystemUI.apk (Status Bar Modding)
7. Alright, now edit the .apk to .zip in your tools folder.
8. Open up the zip and replace the mdpi files inside with the one you prepared.
9. After all the changes, change the .zip back to .apk
10. Open cmd and type cd C:\android\tools . (Depends on where is your sdk tools folder)
11. type adb push SystemUI.apk /system/app/SystemUI.apk
12. Reboot your phone.
Courtesy of terrymcnuggets in this topic.
My questions; regarding
7. Alright, now edit the .apk to .zip in your tools folder; and
9. After all the changes, change the .zip back to .apk
Do i rename the .apk to .zip or do I create a .zip?
AND
8. Open up the zip and replace the mdpi files inside with the one you prepared.
the files you would be prepared to share are mdpi files? not .png?
The icons I want in ICS blue (#FF33B5E5 - or same color as the time etc in te notifcation (top) bar) are: Bluetooth icon, Vibrate icon, Alarm icon, and all of the notication icons (talk/ gmail/ whatsapp etc)
If you'd rather point me out in the directio on how to change them myself that would be great too (Photoshop?)
Many many thanks for your time
Click to expand...
Click to collapse
7. Yes, change the extension to zip. Alternatively simply open it with 7zip/winrar or another archiver.
8. mdpi is the name of the folder. when you open the apk with the archiver you will see a folder called /res/ and inside a couple of drawable[xxx] folders. in theory you should only have to modify files in the drawable xhdpi folder (since the gnex is a xhdpi device). I would suggest extracting the whole /res/ folder and looking in it.
9. if you changed the extension to .zip, change it back to apk. otherwise simply drag and drop the modified files in the correct folders.
PS: make sure you save the original SystemUI.apk somewhere, in case the modifications don't work as expected and you want to revert to the original one
Good luck!

Ok, just to be safe.
1. I connect my phone with usb and type adb pull /system/app/SystemUI.apk in cmd
2. I copy that file to 2 different locations (1 to be sure I have the original in case I screw up , 1 to try and modify)
3. I type adb push /system/app/SystemUI.apk so that my phone is still in good state
Then I go to 1 of the saved SystemUI.apk and rename it to SystemUI.zip
I search for the folder /res/ and look for the notification icons etc which I would like to change the color
Change the color of the .png files with the ICS color in photoshop and replace them
Rename SystemUI.zip back to SystemUI.apk
In cmd I type adb push /system/app/SystemUI.apk and reboot
Did I understand it all correctly? Thanks

Ti2 said:
Without doing it for me- that just deserves another thank you
At this moment I'm on AOKP b27 but that varies quite a bit
So instead of you doing all the work for me (may be it is best to learn it myself since I change ROMS fairly often), would you care to help me a bit?
This is what I've found:
1. Root is prerequisite. If you're using stock rom, you can obtain cf-root from here.
2. Install android sdk from here. Eclipse is optional. The essential stuff we need is the adb from the sdk.
3. Please make a backup using cwm in case you end up deleting or corrupting your phone.
4. Connect your phone to the pc.
5. Open cmd and type cd C:\android\tools . (Depends on where is your sdk tools folder)
6. type adb pull /system/app/SystemUI.apk (Status Bar Modding)
7. Alright, now edit the .apk to .zip in your tools folder.
8. Open up the zip and replace the mdpi files inside with the one you prepared.
9. After all the changes, change the .zip back to .apk
10. Open cmd and type cd C:\android\tools . (Depends on where is your sdk tools folder)
11. type adb push SystemUI.apk /system/app/SystemUI.apk
12. Reboot your phone.
Courtesy of terrymcnuggets in this topic.
My questions; regarding
7. Alright, now edit the .apk to .zip in your tools folder; and
9. After all the changes, change the .zip back to .apk
Do i rename the .apk to .zip or do I create a .zip?
AND
8. Open up the zip and replace the mdpi files inside with the one you prepared.
the files you would be prepared to share are mdpi files? not .png?
The icons I want in ICS blue (#FF33B5E5 - or same color as the time etc in te notifcation (top) bar) are: Bluetooth icon, Vibrate icon, Alarm icon, and all of the notication icons (talk/ gmail/ whatsapp etc)
If you'd rather point me out in the directio on how to change them myself that would be great too (Photoshop?)
Many many thanks for your time
Click to expand...
Click to collapse
That's a great attitude!!! Good for you for taking it in your own hands!!!
Sent from my Galaxy Nexus using Tapatalk

Ti2 said:
Ok, just to be safe.
1. I connect my phone with usb and type adb pull /system/app/SystemUI.apk in cmd
2. I copy that file to 2 different locations (1 to be sure I have the original in case I screw up , 1 to try and modify)
3. I type adb push /system/app/SystemUI.apk so that my phone is still in good state
Then I go to 1 of the saved SystemUI.apk and rename it to SystemUI.zip
I search for the folder /res/ and look for the notification icons etc which I would like to change the color
Change the color of the .png files with the ICS color in photoshop and replace them
Rename SystemUI.zip back to SystemUI.apk
In cmd I type adb push /system/app/SystemUI.apk and reboot
Did I understand it all correctly? Thanks
Click to expand...
Click to collapse
1. the command is: adb pull /system/app/SystemUI.apk <location>
<location> would then be, for example, c:\temp
so, adb pull /system/app/SystemUI.apk c:\temp
2. then you create a copy of the SystemUI.apk from you c:\Temp folder
3. no need to push it back. adb pull simply copies a file from the filesystem
Then you go about and do all the other stuff (extract, edit, etc.)
Finally, when all is done you must do this:
In cmd type:
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push <location/SystemUI.apk> /system/app
where <location> is the place where you have the file. so the command would be, for example:
adb push c:\temp\SystemUI.apk /system/app

can you provide the zip with the png images. I would like it so i can install via root explorer. thanks in advance!

Hey guys, I finished the set, the download link is in my icon thread since that's where the rest of my holo themed/ics blue work is.
http://forum.xda-developers.com/showthread.php?p=22296313

mrfenyx said:
1. the command is: adb pull /system/app/SystemUI.apk <location>
<location> would then be, for example, c:\temp
so, adb pull /system/app/SystemUI.apk c:\temp
2. then you create a copy of the SystemUI.apk from you c:\Temp folder
3. no need to push it back. adb pull simply copies a file from the filesystem
Then you go about and do all the other stuff (extract, edit, etc.)
Finally, when all is done you must do this:
In cmd type:
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push <location/SystemUI.apk> /system/app
where <location> is the place where you have the file. so the command would be, for example:
adb push c:\temp\SystemUI.apk /system/app
Click to expand...
Click to collapse
I'll start from here (when I can find some time), when I have further questions I'll post them here. Thanks for your help mate

Ti2 said:
I'll start from here (when I can find some time), when I have further questions I'll post them here. Thanks for your help mate
Click to expand...
Click to collapse
No problem, good luck. Shoot me a pm if you get stuck somewhere, don't forget to make a nandroid, etc.

Zer0_Cool said:
Hey guys, I finished the set, the download link is in my icon thread since that's where the rest of my holo themed/ics blue work is.
http://forum.xda-developers.com/showthread.php?p=22296313
Click to expand...
Click to collapse
And also a thanks to you for your help!
So, besides pulling them from systemUI.apk and putting thenm back, what more can I do? You told me you could "put them in my ROM" of choice. Since I regularly flas a diff rom, could you please explain to me how to do this before I flash the new rom?

Ti2 said:
And also a thanks to you for your help!
So, besides pulling them from systemUI.apk and putting thenm back, what more can I do? You told me you could "put them in my ROM" of choice. Since I regularly flas a diff rom, could you please explain to me how to do this before I flash the new rom?
Click to expand...
Click to collapse
What I meant was that I could take the SystemUI.apk file from whatever rom you are currently running. Different roms have different tweaks done here and there, and that's one of the larger areas of change, so I wanted to give you the correct one to avoid any potential complications.

Ok so I managed to pull the systemUI.apk an rename it to zip.
I found the following .png I ould like to change to ICS blue:
C:\noticons\SystemUI.zip\res\drawable-sw600dp-xhdpi
stat_sys_alarm.png
stat_sys_data_bluetooth.png
C:\noticons\SystemUI.zip\res\drawable-xhdpi
stat_notify_image.png
stat_notify_image_error.png
stat_notify_more.png
stat_sys_alarm.png
stat_sys_ringer_silent.png
stat_sys_ringer_vibrate.png
Now what I couldn't find the notification icons for Gmail/ Gtal/ Whatsapp etc etc; where can I find these? As well as bluetooth connected/ usb debugging icon etc

Ti2 said:
Ok so I managed to pull the systemUI.apk an rename it to zip.
I found the following .png I ould like to change to ICS blue:
C:\noticons\SystemUI.zip\res\drawable-sw600dp-xhdpi
stat_sys_alarm.png
stat_sys_data_bluetooth.png
C:\noticons\SystemUI.zip\res\drawable-xhdpi
stat_notify_image.png
stat_notify_image_error.png
stat_notify_more.png
stat_sys_alarm.png
stat_sys_ringer_silent.png
stat_sys_ringer_vibrate.png
Now what I couldn't find the notification icons for Gmail/ Gtal/ Whatsapp etc etc; where can I find these? As well as bluetooth connected/ usb debugging icon etc
Click to expand...
Click to collapse
wild guess: in the gmail, gtalk, whatsapp apks...
good luck
PS: editing non-system apps (also called market apps) is a bit tricky

Why is that tricky please?
So how do I change those icons?
adb pull /system/app/Gmail.apk c:\temp
rename to .zip
search for the icon, change
rename to .apk
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push C:/temp/SystemUI.apk/system/app
like that? Or should I really leave that alone as a n00b?

Ti2 said:
Why is that tricky please?
So how do I change those icons?
adb pull /system/app/Gmail.apk c:\temp
rename to .zip
search for the icon, change
rename to .apk
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push C:/temp/SystemUI.apk/system/app
like that? Or should I really leave that alone as a n00b?
Click to expand...
Click to collapse
Those app's weren't included in the set provided by google. What I (or you) will have to do is download the application you want to modify, extract it and find the png that is going to be changed, edit it, name it the same thing as it was before. Then, double click and open the original apk with the archive manager (to avoid re-signing), navigate to the folder the image was in (probably /res/drawable_something) and then drag the new file over. It will overwrite the old image without needing to extract/re-sign/etc. then you adb push theapp.apk /data/app/ and see if it works.
*do you really need to rename it to a .zip to extract on windows?

Zer0_Cool said:
Those app's weren't included in the set provided by google. What I (or you) will have to do is download the application you want to modify, extract it and find the png that is going to be changed, edit it, name it the same thing as it was before. Then, double click and open the original apk with the archive manager (to avoid re-signing), navigate to the folder the image was in (probably /res/drawable_something) and then drag the new file over. It will overwrite the old image without needing to extract/re-sign/etc. then you adb push theapp.apk /data/app/ and see if it works.
Click to expand...
Click to collapse
can this be actually done without having to resign the apk? I remember trying to change the icon for facebook once. I simply copied the new icon inside the apk and overwrote the existing one (same name but obviously, different size). It seemed to work at first but then the app disappeared from the app drawer (it was still in /data/app/ but I could not use it anymore). had to manually delete it and download and install again from market...
In order to get it to work I had to resign it but we know that is not the optimal way to work...

How to add on screen button at framework for ICS

I'm using Xperia arc s at stock rom 4.1.B.0.587 and locked bootloader.
I'm using few mods, and also custom systemui *Colored icons systemui
Few days ago I am starting curious how to add on screen button at my own, and I still cannot do it successfully (got bootloop after xperia title).
After trial and error I found the solution, I don't add original META-INF framework.apk to my modified framework.apk.
Now I'm only curious how to add crt off animation. *I found out that original framework.apk already has the setting to show crt animation. Anyone has an idea what to do??
How I successfully add on screen button:
What I do: (following the tutorial from http://forum.xda-developers.com/showthread.php?t=1364757, and http://forum.xda-developers.com/showpost.php?p=9126643#post9126643 to mod the apk)
1. extract framework-res.apk from my system [framework-res.apk]
2. decompile it with 1.4.10 apktool by this command: java -jar apktool.jar d framework-res.apk framework-res
3. edit bools.xml to change show navigation bar to true
4. edit dimens.xml to change navigation bar height to (21.0dip)
5. rebuild the apk with this command: java -jar apktool.jar b framework-res out\framework-res.apk
6. <from this part I dont really understand> From the output apk [The name is outframework-res.apk] from apktool 1.4.10 (At first I use 1.4.3 and it always failed to compile, but It compiled successfully with 1.4.10), I add the extension to 7z [outframework-res.apk.7z], and unpack it. (i.e: it become outframework-res folder)
7. With 7zip app (actually I use total commander, with zero compression), I replace all files from outframework folder back to outframework.apk.7z
8. I also add resources.arsc from the outframework-res folder and also add it to the outframework-res.apk.7z. *The file size is the same before and after I put the resources.arsc.
9. I downloaded ics_sysbar.zip, then with total commander (7zip like program), I add those files to SystemUI.apk (/res/drawable-hdpi/) using 7-zip or other program. (replace original PNGs to these files).
10. I rename the outframework-res.apk.7z to framework-res.apk then push it to my device along with the SystemUI.apk.
Click to expand...
Click to collapse

Adding "qemu.hw.mainkeys=0" to build.prop enables soft-keys in AOSP/CM10.. I don't use stock ICS so can't confirm this. Wait for few more replies from other users.

soumya_digi said:
Adding "qemu.hw.mainkeys=0" to build.prop enables soft-keys in AOSP/CM10.. I don't use stock ICS so can't confirm this. Wait for few more replies from other users.
Click to expand...
Click to collapse
Thanks for your reply.
By the way, I actually found what is my problem, from analyze other working on screen button.
It turns out the compiled framework don't add META-INF.
After I add that folder to my compiled framework, *with total commander, It works.
And editing the SystemUI turns out unnecessary.
What I still wonder is how to add menu button (the right key, beside back and home button), and also make holding home button show the ics style recent app (the one that you can swipe to remove it from recent app).

MODS for Stock Tmobile UVDLJA Odex (oem 4.1.1 rom)

Some of us prefer the stock rom, rooted with some minor tweaks.
I made some small changes to the SystemUI.apk, Framework-res.apk, and some csc xmls and wanted to share.
Hopefully its not a dumb idea to post this for people to use.
This is for TMOBILE stock UVDLJA ODEX 4.1.1 rom, and will use your EXISTING *.odex files, you're only changing the apks.
I personally renamed the original files with a .oem extension to have in case i wanted to revert back to later.
When renaming the SystemUI.apk in /system/app/ and Framework-res.apk in /system/framework/ with file explorer - you will get some errors.
This is because the system was still running on the apk file you just renamed. The errors won't happen when you reboot.
List of changes:
Changed status bar background to pure black
Removed clock from status bar
Removed screen wake when unplugged from charger
Enabled lock screen rotation
Removed brightness slider from expanded status bar
Removed all but 5 toggles from expanded status bar
Enabled text message reminders
Removed oem browser bookmarks
Changed homepage to Google
Removed keyboard notification in status bar + expanded status bar
Download the zip with MODS from here ----> CLICK HERE!
Since you are on rooted stock rom with stock recovery, you have 2 ways to install. ADB or file explorer.
Method using file explorer: (which is how i did it)
Extract contents of the downloaded zip and put them on your sdcard.
Navigate to the /system/app directory and rename SystemUI.apk to SystemUI.apk.oem. (expect errors)
Just click ok a couple times on the error popups and continue.
**DON'T** rename SystemUI.odex - we are keeping this file the same.
Move the new SystemUI.apk from the zip file to /system/app and set correct file permissions on the new apk.
Breathe!
Navigate to the /system/framework directory and rename Framework-res.apk to Framework-res.apk.oem. (expect errors)
Just click ok a couple times on the error popups and continue.
**DON'T** rename Framework.odex - we are keeping this file the same.
Move the new Framework-res.apk from the zip file to /system/framework and set correct file permissions on the new apk.
Breath!
Navigate to the /system/csc directory and rename customer.xml + feature.xml + others.xml with a .oem extension. (no errors)
Move the new customer.xml + feature.xml + others.xml from the zip to /system/csc and set correct file permissions on each.
Navigate to the /data/dalvik-cache/ directory and select all the *classes.dex files and delete them. (this is clearing the dalvik cache manually)
Now you can reboot and you will have to sign in to your Google account again.
Enjoy.
--> Don't forget to set proper permissions for each file you use from the zip BEFORE you reboot or you may have a bootloop <---
--> You probably will have problems if you don't clear the dalvik cache - don't skip this <--
You can push these files with ADB - but i'm not getting in to that. If you know what ADB is then you probably know how to use it.
Download the zip with MODS from here ----> CLICK HERE!
Thanks to mrRobinson for providing a root injected system image. Found here --> OEM FACTORY UVDLJA IMAGE
Factory ROM - provided by DocHoliday77 - can also be found here --> [Firmware/OTAs] T999(V) Official, Leaked & Root66 FW and OTA Updates!

Interested in trying this but just want to verify it should not be attempted with wildchld's stock release, which is deodexed? Is the OTA version odexed?

Sincitybronze said:
Interested in trying this but just want to verify it should not be attempted with wildchld's stock release, which is deodexed? Is the OTA version odexed?
Click to expand...
Click to collapse
Correct, do not use this on wildchlds rom.
This is for the factory 4.1.1 odex version only.