Database Develop

Launcher Tab, unlimited shortcuts, based on ATT tab

Ok, here's the files. I started on att manila(which is where tab comes from) and now have it running on non att manila(. This has been tested with ONYX theme which is using the latest htc manila version(1.2.35845.1_1813.6), which is where pics came from. I had up to 48 shortcuts made up, so I don't think it has a limit. It can be an odd number of shortcuts, doesn't have to have 3 on last row.
Its made from the ATT tab that was used for ATT specific links. I removed the ATT links and images. I added the tab icon links for tab bar back into the icons.mode9 file, 61f866ab_manila. Included lua scripts and ATT tab icons (1a5a121d_manila and 2e35e5f2_manila) which you can change to match your theme. The heart of it is the att_tabitems.xml which is where you have to edit your links for the shortcuts. All of files in zip need to be placed into \Windows folder on your phone. I can't make a cab, because you will have to edit the xml file to use this first. You can make shortcuts to open web links, files, folders, or apps. IconPath can point anywhere? or left blank. The softkeys are also set in the xml, so make them what you want. They currently connect to home and programs tabs of tf3d.
Here's some examples of xml, in these I was linking to icons folder I made in root of device named Realize(from the realize icon set).
App Link
Code:
<ATTtabItem
Name="Total Commander"
Path="\Program Files\Total Commander\cecmd.exe"
Arguments=""
IconPath="\Realize\TotalCommander.png"/>
Web Links
Code:
<ATTtabItem
Name="Opera"
Path="\Windows\OperaL.exe"
Arguments="http://m.google.com"
IconPath="\Realize\Opera95.png"/>
<ATTtabItem
Name="Google"
Path=":DEFBROWSER"
Arguments="http://forum.xda-developers.com"
IconPath="\Realize\GoogleNew.png"/>
<ATTtabItem
Name="Ebay"
Path="\Windows\iexplore.exe"
Arguments="http://ebay.com"
IconPath="\Realize\ebay.png"/>
Folder/file links
Code:
<ATTtabItem
Name="Games"
Path="\Windows\fexplore.exe"
Arguments="\Windows\Start Menu\Programs\Games"
IconPath="\Realize\Poker.png"/>
Soft Keys
Code:
<Softkey>
<LSK Path="\Windows\manila.exe" Arguments="--switchtopage Manila://home.page" Text="Home"/>
<RSK Path="\Windows\manila.exe" Arguments="--switchtopage Manila://programs.page" Text="Programs"/>
</Softkey>
To Install:
1. Disable tf3d in today settings.
2. Take the xml file and edit on your pc using Notepad to setup all your links
3. Edit your 26948339_manila file using Notepad as well, add lines from Post #2 below.
4. Copy all files in zip and your 26948339_manila to somewhere on phone.
5. Copy all files into \Windows folder on your phone using Total Commander(or equivalent).
6. Restart tf3d.

Almost forgot, you will have to add tab to your tab xml for tf3d.
Edit your 26948339_manila file using notepad on your pc.
Add the following lines, just change the page number to match your xml file.
Code:
<Page Order="10" Name="atttab.page" PackageName="HTC" Title="Launcher">
<ComponentReference Name="page" Mode9Path="HTC\ATTtab.mode9" Component="GizmoRoot" SmartComponent="true" />
<ComponentReference Name="icon_normal" Mode9Path="HTC\icons.mode9" Component="ATTAtt_Off" />
<ComponentReference Name="icon_selected" Mode9Path="HTC\icons.mode9" Component="ATTAtt_On" />
<ComponentReference Name="icon_preview" Mode9Path="HTC\icons.mode9" Component="ATTAtt_Preview" />
</Page>

WOW nice work I know lots of people have been asking for something like this. Ill wait for it to be a bit easier to install and edit which I"m sure will happen once everyone catch's wind of this lol
Thanks for the hard work

Is it possible to get this tab working with the rhodium manila? I'm currently using Energy Rom series 2.

[HOW TO] Make your own bootscreen and create signed zip

Here's a tutorial for those wanting to make their own (animated) bootscreen for the HTC Hero. Decided to write it after I'd seen a couple of posts from people asking about this, and some encouragement from yet another. I've tried to write this in greatest detail possible, so everyone can have a go at doing this.
Tools
It's really quite simple, if you have the proper tools for the job:
SignAPK.jar + testkey.pk8 + testkey.x509.pem
SignAPK.cmd (batch file written by me to facilitate signapk.jar use)
Graphics editor that can work with animated GIF files (Adobe Photoshop or Fireworks recommended)
a plain text editor capable of editing UNIX files (if you're unsure about this, use the free, and open source Notepad++. You can get the Installer.exe here.)
These aren't required, but make things easier:
Android SDK Tools installed (working adb.exe at the very least)
Hero's stock bootscreen to start from)
I have attached two stock Hero bootscreens (one with and one without the HTC startup sound), as well a zip file with the signapk files.
Setting up SignAPK
First, make sure you have Java installed. If not go to www.java.com to install it.
Second, I recommend to unzip the SignAPK_xda.zip file to C:\SignAPK.
Lastly, add the signapk folder to your PATH environment variable:
[*]Go to Control Panel, System
[*]Click on "Advanced" (or "Advanced System Settings")
[*]Click the button "Environment Variables..."
[*]Locate the PATH variable under "User Variables" (or "System variables" if you want to use SignAPK under other user accounts) and double-click it to edit
[*]In the "Variable Value" field, at the end of the line, type a semi-colon and the path to the signapk files ;C:\SignAPK
[*]You could also add the path to your java.exe file here if you have troubles with running signapk.​
A note on signapk.CMD
I wrote this batch file so it's possible to sign a zip file from a command line with the least amount of typing (saves time and less chance of a typo). It will check for java.exe and if it doesn't find it in your %PATH% it will let you know and try anyway. It will also prompt you to overwrite or not, if it finds the signed destination file already exists. Open in notepad to find out more.
Contents of bootscreen_stock.zip
You can delete the following three files, as they are created by the signing process:
META-INF\CERT.RSA
META-INF\CERT.SF
META-INF\MANIFEST.MF
This file contains the command to copy the files to the SYSTEM: volume on your device - you never need to edit this:
META-INF\com\google\android\update-script
This file tells Android how and which files to display - open in Notepad++:
system\media\bootscreen\boot_animation.xml
Then we have the actual bootscreen files:
system\media\bootscreen\boot1.gif - shown first, and plays only once
system\media\bootscreen\boot2.gif - shown after first ends, and loops forever (i.e. until end of boot sequence)
system\media\bootscreen\boot_bg.gif - optional file, this file is used as background during entire boot sequence if the 2 aforementioned files are smaller than Hero's screen
system\media\bootscreen\boot.mp3 - optional sound file, played once during boot
boot_animation.xml file contents
Code:
<?xml version="1.0" encoding="utf-8"?>
<!--
* Copyright (C) 2008 HTC Inc.
*
-->
[COLOR="Red"]<!-- For new bootup animation
<BootConfiguration>
<BootAnimation
image="/system/media/bootscreen/boot.gif"
audio="/system/media/bootscreen/boot.mp3"
image2="/system/media/bootscreen/boot2.gif" (optional)
image3="/system/media/bootscreen/boot3.gif" (optional)
screenX="100" (optional)
screenY="130" (optional)
image_bg = "/system/media/bootscreen/boot_bg.gif" (optional)
useAudio="1" // 1: true ; 0:false (optional)
/>
</BootConfiguration>
-->
[/COLOR]
[COLOR="Green"]<!-- For cropped version -->
<BootConfiguration>
<BootAnimation
image="/system/media/bootscreen/boot.gif"
image2="/system/media/bootscreen/boot2.gif"
image3="/system/media/bootscreen/boot2.gif"
loopimage="/system/media/bootscreen/boot2.gif"
image_bg="/system/media/bootscreen/boot_bg.gif"
audio="/system/media/bootscreen/boot.mp3"
screenX="10"
screenY="180"
useAudio="1"
/>
</BootConfiguration>
[/COLOR]
[COLOR="Red"]<!-- For full screen version -->
<!--BootConfiguration>
<BootAnimation
image="/system/media/bootscreen/boot.gif"
audio="/system/media/bootscreen/boot.mp3"
useAudio="1"
/>
</BootConfiguration-->[/COLOR]
This is the file included with the stock bootscreen. This file actually contains 3(!) configurations, however the first and third (red-colored) have been commented out. In short, edit the middle (green-colored) "BootConfiguration" section.
Delete the line that begins with image3= as you won't need it.
If you do not wish to include a startup sound, delete lines starting with:
audio=
useaudio=
Alternatively, simply set useAudio=0
If you boot1.gif and boot2.gif files are both 320x480 pixels, delete lines starting with:
image_bg=
screenX=
screenY=
Alternatively, simply set screenX=0 and screenY=0
If you delete the audio= and image_bg= lines, you can ofcourse delete the files audio.mp3 and image_bg.gif to keep the update.zip as small as possible.
ScreenX and ScreenY are coordinates in pixels, that tell Android where to place the GIF files on the screen. Top-left of the screen would be ScreenX=0 and ScreenY=0; bottom-right would be ScreenX=320 and ScreenY=480. This means that if you make a GIF file that is 200 px wide and 180px high and you wish to center this on the screen, you'd use ScreenX=60 and ScreenY=150 (i.e. ScreenX=320-200=120/2=60 and ScreenY=480-180=300/2=150). If your GIF files are exactly 320x480 pixels, you can set ScreenX and ScreenY both to 0, or leave those two lines out entirely.
Creating a GIF animation from scratch
(boot1.gif and boot2.gif)
Using Adobe Photoshop CS4 (cannot speak for older versions, I think you'd need the now discontinued Adobe ImageReady instead):
Create a layer for each frame of your animation (yes, I didn't say creating an animation from scratch wouldn't be a lot of work)
Click Window -> Animation to show the Animation panel
Click the panel menu (top right icon in panel) and choose "Make Frames from Layers"
If the frames are loaded in reverse from what you intended, choose "Reverse Frames" from the Animation panel menu
From the panel menu, choose "Optimize Animation" and UNtick both "Bounding Box" and "Redundant Pixel Removal"
Finally, go to File -> Save for Web & Devices, UNtick "Transparency" and play with some of the options to reduce file size.
To (re-)open an animated GIF file in Photoshop CS4, go to File -> Import -> Video Frames to Layers and type in the file name box *.gif then hit the Enter key so you can see GIF files, browse to it, select and click Load.
Using Adobe Fireworks CS4:
Make sure the "States" panel is visible, via Window -> States
Create a new "State" for each frame of your animation
To set frame delays, or basically set how long each frame will be shown for, in 100ths of a second, select one or more states and right-click, choose "Properties"
Make sure you do not use transparency (this gave me problems)
To save, go to File -> Save As, set "Save as Type" to "Animated GIF (*.gif)" and "click Options"
Do check "Dither" for better looking gradients and transitions
Play with the options on the first tab to reduce file size
On the "Animation" tab, UNcheck "Crop each state" (don't do this and get some crazy glitchy results in your bootscreen)
Creating a GIF animation by converting a G1 bootscreen animation to Hero format
(boot1.gif and boot2.gif)
You can also import a bunch of PNG files as layers (and subsequently frames) from, for example, a G1 bootscreen.
The fastest way in my experience is simply using Fireworks' File -> Open dialog, make sure all files are in one directory, select them all, do check the "Open as Animation" checkbox and click "Open". This will open each file into its own state in one big file. Then use instructions above to set frame delays and proceed to save as animated GIF.
You can also do it in Photoshop, but this method is very slow, via File -> Scripts -> Load Files into Stack (UNtick "Create Smart Object after loading layers"). Then follow the steps above to create an animated GIF file.
Compiling your bootscreen
If you have the files you want, it's time to zip them and then sign the zip file.
Make a folder "mybootscreen" and unzip the stock bootscreen into that, so it looks like this:
META-INF\CERT.RSA
META-INF\CERT.SF
META-INF\MANIFEST.MF
META-INF\com\google\android\update-script
system\media\bootscreen\boot_animation.xml
system\media\bootscreen\boot1.gif
system\media\bootscreen\boot2.gif
system\media\bootscreen\boot_bg.gif
system\media\bootscreen\boot.mp3
Delete those first 3 files, edit the XML file as needed and replace the GIF files with your own (see my explanations above).
Use for example 7-zip to select the 2 folders META-INF and system and click "Add" (to create new archive)
Make sure you set "Archive Format" to ZIP
Open a Command Prompt window (click Start, Run, type cmd and click OK, or if you have Vista or Windows 7, click Start, type cmd and hit Enter key)
Use this command to go to the directory with your zip file: CD /D C:\path\to\your\file
Type signapk mybootscreen.zip and hit Enter key
Barring any typo's you should now have a file named mybootscreen_signed.zip. You can copy that to the root of your SDCARD and flash it via your recovery image, or use DroidExplorer's flash function.
If this tutorial was of any use to you, or you have ideas to make it better, please reply and let me know. Thanks for reading!
EDIT (2010-04-11): updated SignApk_xda_v20100411.zip. Fixed a couple of forgotten quotes in signapk.cmd that made signing files with spaces in their filenames impossible. New zipfile attached.

wooooo THANKS!
THANKS A LOT! I have made the animated gifs and the sound, but I was insure how to sign and create the signed zip. I'll be trying this ASAP when Ive finished work. Ill keep you posted....
Thanks again m8.

Great guide, I have made my own bootscreen for the Villain rom, but for some reason, when i flash it to my hero, on boot, it plays less than a second of it, ad then messes up completely and displays random static like on an old tv, and then just a black screen for the remainder of the boot time
Help!! my gifs are not that big, i made sure of that (only slightly more than the stock) and i made them in photoshop CS4 with the animations panel, and followed your instructions to the letter.
Gifs are bellow, please help, as i would really like to release these, as i think they are really nice.
Boot1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Boot2

Hey, very nice work! Try the zip I've attached. I think it came out great.
It boils down to a few small problems. Here are some steps I took to correct them:
Imported your files into PS as I described in the tutorial using "Video frames to Layers"
Edit -> Convert to Profile -> sRGB IEC61966-2.1 (UNcheck "Flatten Image")
For just boot1.gif in Animation Panel, bottom left, set looping to "Once"
For just boot1.gif via Image -> Image Size... -> Width:320px, Height:480px, Resolution:72dpi, Check Resample Image and set to "Bicubic"
File -> Save for Web & Devices, with these settings: Selective, Diffusion, UNcheck transparency, UNcheck interlaced, Colors:64 (as this is a grayscale animation, it looks fine), Dither:100%, Matte:none, Web snap:0%, Lossy:0, Metadata:none.
The end result is bigger files, but they work. The XML was fine.

Great! thanks a lot for your help, and your original guide, I might do a few more boot screens now as it looks really good (in my opinion)

mattyyey said:
THANKS A LOT! I have made the animated gifs and the sound, but I was insure how to sign and create the signed zip. I'll be trying this ASAP when Ive finished work. Ill keep you posted....
Thanks again m8.
Click to expand...
Click to collapse
How'd it come out? Would love to see your results!

Really interessant, this is exactly what I was looking for! Thanks for this How-To!
For the signing process I haven't use your "signapk.cmd" (since I'm a linux user)But I have a question: testkey.x509.pem & testkey.pk8 you provied are only to sign app for the Hero? or is it a standard Android singning process? I mean... where are those key from?
For now i've just "resign" the stockbootscreen for "educational purpose", soon I'll try to create something, I hope
EDIT: Okay I was able to resign the original one correctly since I was able to flash it, BUT my bootscreen is still this nexus one animated. So maybe I don't understand wich bootscreen we actually modifing. I know this is not the really first one (this one is fine: spend one day to find that we need a custom SPL to change my ex horrible T-mobile first bootscreen to a Hero one) So why can't I remove the nexus one coming with aHero ROM?
EDIT2: using
Code:
./adb pull /system/media/bootscreen/boot.gif ./Desktop
I get the right image... that mean the files are correctly flashed on my ROM but nothing change so that mean aHero is using a different path for the 2nd bootscreen ???
Thanks for any hint

carbonyle said:
Really interessant, this is exactly what I was looking for! Thanks for this How-To!
Click to expand...
Click to collapse
You're most welcome!
carbonyle said:
For the signing process I haven't use your "signapk.cmd" (since I'm a linux user)But I have a question: testkey.x509.pem & testkey.pk8 you provied are only to sign app for the Hero? or is it a standard Android singning process? I mean... where are those key from?
Click to expand...
Click to collapse
The signapk files (except signapk.cmd) came from a 5MB file named "AndroidMod.zip" that floats around the internet, so to speak. It also contains 3 img files, part of a tutorial I guess, which are not needed for signing. The testkey certificates were created by whomever made that zipfile. The credentials for those files are quite anonymous ("Android" and "[email protected]", etc), so they should be fine to use. You could use openssl to generate your own key files. I tried, and they generated okay, but zips signed with my own certificate wouldn't flash. Recovery (Amon RA) kept saying the files weren't signed. So if you figure out how to properly generate your own certificates, I'd love to hear it.
carbonyle said:
For now i've just "resign" the stockbootscreen for "educational purpose", soon I'll try to create something, I hope
EDIT: Okay I was able to resign the original one correctly since I was able to flash it, BUT my bootscreen is still this nexus one animated. So maybe I don't understand wich bootscreen we actually modifing. I know this is not the really first one (this one is fine: spend one day to find that we need a custom SPL to change my ex horrible T-mobile first bootscreen to a Hero one) So why can't I remove the nexus one coming with aHero ROM?
EDIT2: using
Code:
./adb pull /system/media/bootscreen/boot.gif ./Desktop
I get the right image... that mean the files are correctly flashed on my ROM but nothing change so that mean aHero is using a different path for the 2nd bootscreen ???
Thanks for any hint
Click to expand...
Click to collapse
I don't know I'll download aHero and have a look.
EDIT: Okay, just had a quick look in "aHero07-signed.zip" and it appears Android 2.1 uses a different bootscreen format. Do this:
adb shell
cd /system/media
ls
Instead of a bootscreen directory you'll see a file "bootanimation.zip". Instead of 2 animated GIFs, it contains 2 directories. Each directory is an animation, with a bunch of PNG files for frames. A text file describes which dir is what animation (order of playback) and the delay between frames. If you want to convert a 1.5/1.6 bootscreen from GIFs to seperate PNGs for use in this new format, just open the GIF file in Photoshop (or GIMP I guess) as described and save each frame as a seperate file (Photoshop has a function or script for that, maybe GIMP does too).
Maybe you'll find more information in this thread. I got the Supernova bootscreen graphics (see my sig) from there, which I converted into a bootscreen for Cupcake.

Well, my experience from running 2.1, you can use the bootanimation.zip, or if you delete it and create the bootscreen folder, it also works.
I have the same problem though, when I load up my gif, using the old method, it looks like hells just got unleashed on the gif. Nothing in place, static, etc... I followed your tutorial, tried a couple things, nothing has been working so far...
EDIT: Nvm, found another program to remove the transparency, works now! Got bored, haven't seen any terminal style logins - this works great for my phone, the timing might be different for others though.
To get it working, just delete your bootanimation.zip and flash the zip as usual.
Boot1
Boot2
http://groups.google.com/group/admin-panel-dev/web/terminal_signed.zip

Great tutorial! And nice work that one is Warhawk
I have a problem. I made one by screen capturing some video. Converted it to .gif fine. I can play it in windows fine, but when flashing to android the image just gives a black screen (its only the gif area of the screen cos the animation is only 300x120.
I have provided the .gif above, if anyone can help.
Thanks

I went ahead and removed the transparency from the gif, it showed up on my Hero just fine when I zip/signed it.

Aaah Thanks so much buddy. I swear i tried that though (maybe i made a mistake)
Cheers so much!

I am getting an error after flashing. My installation aborts.
...
Verifying update package...
Installing update...
E:Can't find update script
Installation aborted.
...
Can you help??

quan_one said:
I am getting an error after flashing. My installation aborts.
...
Verifying update package...
Installing update...
E:Can't find update script
Installation aborted.
...
Can you help??
Click to expand...
Click to collapse
Upload your update.zip. Some-one should be able to help.

Did you include the update-script to: \META-INF\com\google\android

Hey guys I created my own boot screen but I am failing to see why my gif will not display on my hero. I have created it from scratch being careful not to include any transparent images or layers but it still displays as a black screen. I am not sure what would cause my gif not to play on my phone other than a transparency issue.
Any help would be more than welcome.
(I am able to sign my zip and flash it no problem)
(edit: The image was my actual .gif but after upload it turn into a jpeg. I will host the file and upload from there.)
My stuff can be found here at mediafire : http://www.mediafire.com/?sharekey=43b651ad9cd91774e7c82ed4b8f0c380e53d1e35008d24d5d8c7c6998cb4ca21
.psd
signed zip
Thanks again!

rejectedkid said:
Hey guys I created my own boot screen but I am failing to see why my gif will not display on my hero. ...
Click to expand...
Click to collapse
You need to go into mybootanimation_signed.zip\system\media\bootscreen and edit your boot_animation.xml.
phaelox said:
...ScreenX and ScreenY are coordinates in pixels, that tell Android where to place the GIF files on the screen. Top-left of the screen would be ScreenX=0 and ScreenY=0; bottom-right would be ScreenX=320 and ScreenY=480. This means that if you make a GIF file that is 200 px wide and 180px high and you wish to center this on the screen, you'd use ScreenX=60 and ScreenY=150 (i.e. ScreenX=320-200=120/2=60 and ScreenY=480-180=300/2=150). If your GIF files are exactly 320x480 pixels, you can set ScreenX and ScreenY both to 0, or leave those two lines out entirely...
Click to expand...
Click to collapse
The difficult thing is that you have two .gifs that are diff sizes so not too sure what to do.
On the one I made, my .gifs are both the same resolution so the value I set for ScreenX and ScreenY work for both.
Look at some other people's .xml files and hope you find someone elses that also uses two different resolution .gifs.

ah. thanks for your input
Sent from my HERO200 using the XDA mobile application powered by Tapatalk

And just because there are no transparent images that you can see or know you put in, doesn't mean that they aren't in there. For some reason, even if I untick Transparent layers in PS, I still get them. I went and got Animation Shop 3, optimized the gif after making it in PS, then re-wrote the file, and everything works fine.
Hope everything is working

Hi !
I have 2 questions :
First one :
To ddotpatel : Your bootscreen is really nice ! Is it working on any 2.1 rom or do I have to change it ? On which rom did you create it ?
And the second one, that tuto is working on 1.5 and 2.1 roms ? Because I heard that it was different to make an 1.5 bootscreen and an 2.1 one...
Thanks for your answers

[FIX] Show status bar item press (10/28/10)

One very annoying thing about the vibrant status bar (in ALL eclair ROMs) is the lack of visual feedback from selecting a notification item. Usually when you click a notification on stock, the item will turn orange. With the vibrant, this does not happen. The "pressed" state uses the same drawable as normal for notification icons. The same is true for the clear notifications button. I find this extremely annoying.
So, I went poking around in the framework-res.apk and found a typo in a status bar layout file. I fixed it so now it works!
EDIT: Oops! I posted the wrong file. It is actually "status_bar_latest_event.xml"
Sorry about that.
Here is the typo:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<LinearLayout android:orientation="vertical" android:layout_width="fill_parent" android:layout_height="66.0sp"
xmlns:android="http://schemas.android.com/apk/res/android">
<View android:background="@drawable/quick_panel_list_stroke_01" android:layout_width="fill_parent" android:layout_height="1.0sp" />
<com.android.server.status.LatestItemView android:id="@id/content" android:background=[COLOR="Red"]"@drawable/status_bar_item_background_normal"[/COLOR] android:focusable="true" android:clickable="true" android:layout_width="fill_parent" android:layout_height="65.0sp" />
</LinearLayout>
That's the whole file. The "typo" is in red. "@drawable/status_bar_item_background_normal" points to a .9.png file which is why the drawable simply stayed the same ("normal") even when you clicked it.
What the file SHOULD say is this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<LinearLayout android:orientation="vertical" android:layout_width="fill_parent" android:layout_height="66.0sp"
xmlns:android="http://schemas.android.com/apk/res/android">
<View android:background="@drawable/quick_panel_list_stroke_01" android:layout_width="fill_parent" android:layout_height="1.0sp" />
<com.android.server.status.LatestItemView android:id="@id/content" android:background=[COLOR="Red"]"@drawable/status_bar_item_background"[/COLOR] android:focusable="true" android:clickable="true" android:layout_width="fill_parent" android:layout_height="65.0sp" />
</LinearLayout>
"@drawable/status_bar_item_background" points to an xml file which is a selector that tells the drawable to switch according to the view's state (pressed, selected, normal)
I've looked at several frameworks and they all have the same typo in them. After I found this, I looked at a nexus one framework and that confirmed that this is indeed the way the file should read. Whether this was intentionally done by Samsung or not, I do not know. Although I'm assuming it was a mistake.
To use:
1. Download attachment "status_bar_latest_event.xml.zip" and remove ".zip" (don't unzip)
2. MAKE A BACKUP OF YOUR FRAMEWORK-RES.APK
3. Open framework-res.apk with 7-zip or winrar or whatever (DO NOT unzip it)
4. Copy status_bar_expanded.xml to /res/layout/ and overwrite.
5. Do this:
Code:
adb shell stop
adb push /path/to/framework-res.apk /system/framework/
adb reboot
Enjoy!

I just wanted to say 1up on this... I
'd love to have this figured out.

I've noticed this as well. I'm not sure why out isn't doing it either, but I know it definitely works correctly in froyo.

I think I found it. Testing now.
EDIT: See first post.

Awesome find, adding to the directory now!

matt_stang said:
One very annoying thing about the vibrant status bar (in ALL ROMs) is the lack of visual feedback from selecting a notification item. Usually when you click a notification on stock, the item will turn orange. With the vibrant, this does not happen. The "pressed" state uses the same drawable as normal for notification icons. The same is true for the clear notifications button. I find this extremely annoying.
So, I went poking around in the framework-res.apk and found a typo in a status bar layout file. I fixed it so now it works!
To use:
1. Download attachment "status_bar_expanded.xml.zip" and remove ".zip" (don't unzip)
2. MAKE A BACKUP OF YOUR FRAMEWORK-RES.APK
3. Open framework-res.apk with 7-zip or winrar or whatever (DO NOT unzip it)
4. Copy status_bar_expanded.xml to /res/layout/ and overwrite.
5. Do this:
Code:
adb shell stop
adb push /path/to/framework-res.apk /system/framework/
adb reboot
Enjoy!
Click to expand...
Click to collapse
Hi,
Thanks for figuring this out.
Any chance of posting the typo fix in the OP?
It would make it easier for those of us running our own customized frameworks.
Mostly I'm just lazy and don't want to drop your xml into a file, decompile, diff against stock, diff against my customizations, etc., etc.
Cheers, =)

Did you ever try my ROM? You can't really say that it is missing in ALL ROMS if you haven't tried them all.
It defiantly wasn't missing in my Axura, it was just blue instead of orange

s0niqu3 said:
Hi,
Thanks for figuring this out.
Any chance of posting the typo fix in the OP?
It would make it easier for those of us running our own customized frameworks.
Mostly I'm just lazy and don't want to drop your xml into a file, decompile, diff against stock, diff against my customizations, etc., etc.
Cheers, =)
Click to expand...
Click to collapse
Yeah I'll update the first post in a second. I'm not sure if it was a typo or not but it seems like Samsung would have fixed it in the latest releases and leaks.
Master™ said:
Did you ever try my ROM? You can't really say that it is missing in ALL ROMS if you haven't tried them all.
It defiantly wasn't missing in my Axura, it was just blue instead of orange
Click to expand...
Click to collapse
Sorry! It's only the Eclair ROMs. As mentioned earlier, Froyo ROMs already have this fixed.

Thanks a lot....nice observation to find AND fix the typo

Hey good work! Will be including this in an update.

Hi again,
Quick FYI, if you want the "clear-all" button to show the pressed state, decompile twframework-res.apk and edit /res/layout/status_bar_expanded.xml
change the red highlighted text in the following to:
@drawable/quickpanel_btn_default
Code:
<Button android:textSize="14.0sp" android:textColor="#ffffffff" android:layout_gravity="center_vertical" android:id="@id/clear_all_button" android:background="[COLOR="Red"]@drawable/quick_panel_btn_default_normal[/COLOR]" android:layout_width="75.0dip" android:layout_height="wrap_content" android:layout_marginRight="6.0dip" android:text="@string/status_bar_clear_all_button" />
Then save and recompile.
Cheers everyone, =)

s0niqu3 said:
Hi again,
Quick FYI, if you want the "clear-all" button to show the pressed state, decompile twframework-res.apk and edit /res/layout/status_bar_expanded.xml
change the red highlighted text in the following to:
@drawable/quickpanel_btn_default
Code:
<Button android:textSize="14.0sp" android:textColor="#ffffffff" android:layout_gravity="center_vertical" android:id="@id/clear_all_button" android:background="[COLOR="Red"]@drawable/quick_panel_btn_default_normal[/COLOR]" android:layout_width="75.0dip" android:layout_height="wrap_content" android:layout_marginRight="6.0dip" android:text="@string/status_bar_clear_all_button" />
Then save and recompile.
Cheers everyone, =)
Click to expand...
Click to collapse
Thanks! I looked for that but didn't think to check the twframework again because the other fix was in the regular framework. I noticed in the regular framework the button code was fine but it didn't occur to me it might be in tw.

s0niqu3 said:
Hi again,
Quick FYI, if you want the "clear-all" button to show the pressed state, decompile twframework-res.apk and edit /res/layout/status_bar_expanded.xml
change the red highlighted text in the following to:
@drawable/quickpanel_btn_default
Code:
<Button android:textSize="14.0sp" android:textColor="#ffffffff" android:layout_gravity="center_vertical" android:id="@id/clear_all_button" android:background="[COLOR="Red"]@drawable/quick_panel_btn_default_normal[/COLOR]" android:layout_width="75.0dip" android:layout_height="wrap_content" android:layout_marginRight="6.0dip" android:text="@string/status_bar_clear_all_button" />
Then save and recompile.
Cheers everyone, =)
Click to expand...
Click to collapse
------------------------------
I don't get why when I make changes to the twframework-res.apk file it always breaks the system with force closes.
phone - media - email all force close
I am using bionix 1.1
APK Manager 4.9
If I make any change to twframework-res.apk it ends in FCs.
When I tried to recreate from this tutorial its a no go.
I thought originally it might be a problem when recompiling, so I copied the modified files into the apk (I use winrar) but it still FCs.
The only way for me to have this work on my phone is to install it as it.
Any ideas?

Muffin-Factory said:
------------------------------
I don't get why when I make changes to the twframework-res.apk file it always breaks the system with force closes.
phone - media - email all force close
I am using bionix 1.1
APK Manager 4.9
If I make any change to twframework-res.apk it ends in FCs.
When I tried to recreate from this tutorial its a no go.
I thought originally it might be a problem when recompiling, so I copied the modified files into the apk (I use winrar) but it still FCs.
The only way for me to have this work on my phone is to install it as it.
Any ideas?
Click to expand...
Click to collapse
Hi,
Are your wiping your cache,
Dalvik-cache and fixing permissions before rebooting?
I'd say 95% of the time that solves fc issues for me when modifying system files.
Else I have no clue, I modify twframework-res all the time without issue.
Good luck though, cheers, =)

Help
s0niqu3 said:
Hi again,
Quick FYI, if you want the "clear-all" button to show the pressed state, decompile twframework-res.apk and edit /res/layout/status_bar_expanded.xml
change the red highlighted text in the following to:
@drawable/quickpanel_btn_default
Click to expand...
Click to collapse
Do you think you could post that xml file for us who are not so good at decompiling and using adb.

s0niqu3 said:
Hi,
Are your wiping your cache,
Dalvik-cache and fixing permissions before rebooting?
I'd say 95% of the time that solves fc issues for me when modifying system files.
Else I have no clue, I modify twframework-res all the time without issue.
Good luck though, cheers, =)
Click to expand...
Click to collapse
Ok, I don't quite understand how to edit twframework-res.apk.
If you would, please, a quick run down of options I should be selecting when decompiling and recompiling.
As of right now i have found out that my recompiling is not reencoding the xml files

Muffin-Factory said:
Ok, I don't quite understand how to edit twframework-res.apk.
If you would, please, a quick run down of options I should be selecting when decompiling and recompiling.
As of right now i have found out that my recompiling is not reencoding the xml files
Click to expand...
Click to collapse
Hi,
Do you use apk manager 4.9 to decompile?
If so, a straight decompile (option 9) is all I ever do for twframework-res.apk and it works fine. Now, when recompiling, if you start from something like bionix/hybrid/etc. base, its likely that they "cheated" when they replaced .9.png files for their theme, so you'll get errors when you recompile the framework.
So, here's my process if modding an already themed framework-res/twframework-res apk:
1) decompile apk
2) make my edits, try to recompile, if it errors, then:
3) Check the log, if its an error about a .9.png then:
4) decompile stock, non-themed apk from the rom version I use (JFD or JI6)
5) copy over the entire contents of the drawable-hdpi(-v4) folder to the apk I'm editing.
6) try to re-compile, 99% of the time, this works, since it seems most rom cooks like to cheat with their .9.png edits.
optional - 7) open the newly compiled apk and the original apk with 7zip and copy over the contents of the drawable-hspi(-v4) folder from the original/themed apk to my new compiled apk
8) zipalign apk
9) push apk to /system/framework
10) adb reboot recovery
11) reinstall packages to get into clockwork recovery
12) wipe cache, advanced wipe dalvik-cache and fix permissions
13) reboot
Hope this helps, cheers, =)

Dugorf said:
Do you think you could post that xml file for us who are not so good at decompiling and using adb.
Click to expand...
Click to collapse
Hi,
I don't really want to post my xml file for 2 reasons, (mostly for reason number 1 though.)
1) I made extra edits to it for my own personalized theme, and it might cause display issues for people using anything other than my own specific theme.
2) I'm kind of tired of people using somebody else's work and not giving credit. I see a lot of my battery icons used all over the place, and very rarely do people link back to the thread, or even say thanks in their OP.
I do this purely for fun (well, and to kill boredom time since I'm unemployed currently), but I also don't like people not giving credit to original content authors.
Anyway, sorry about that, cheers, =)

s0niqu3 said:
Hi,
I don't really want to post my xml file for 2 reasons, (mostly for reason number 1 though.)
1) I made extra edits to it for my own personalized theme, and it might cause display issues for people using anything other than my own specific theme.
2) I'm kind of tired of people using somebody else's work and not giving credit. I see a lot of my battery icons used all over the place, and very rarely do people link back to the thread, or even say thanks in their OP.
I do this purely for fun (well, and to kill boredom time since I'm unemployed currently), but I also don't like people not giving credit to original content authors.
Anyway, sorry about that, cheers, =)
Click to expand...
Click to collapse
That is totally understandable. Thank you for the detailed instructions. I am just getting into making my own themes (starting just for me). I have used your battery mod for awhile and love it. I'm looking forwards to learning how to make that kind of thing myself.
Thanks again.

Can you make a MM zip or flashable zip? I don't know exactly how to do this in Fusion 1.2 I don't want to mess anything up, last time I tried it was a fail. I kept getting FCs.

[TUTORIAL]Boot Animation Sound

MAKE A BACKUP!!! I am in no way responsible for anything you do to your phone!
I thought I'd do a write up on how you can add, remove, or change your ROOTED Thunderbolt animation sound. You have to do some of your own poking around to locate the files needed for your specific rom. There are many people that don't want to do this cause they are afraid they will screw something up. You can safely do this on your PC. Create a folder and extract your rom into that folder. Navigate to system/customize/cid where you extracted your rom. Locate the default.xml file and right click and to open with notepad. Now, scroll to the bottom and look for something that resembles the following.
<BootAnimation animation="/system/customize/resource/VZW_bootanimation.zip" audio="/system/customize/resource/Verizon_Thunderbolt_3sec.mp3" audiostart="VZW" />
Click to expand...
Click to collapse
OR this...
-
<BootAnimation animation="/system/media/bootanimation.zip" audio="/system/media/FinalThunder.mp3" audiostart="VZW" />
Click to expand...
Click to collapse
OR maybe even this...
-
<BootAnimation animation="/system/customize/resource/bootanimation.zip" audio="/data/local/bootsound.wav" />
Click to expand...
Click to collapse
You are looking for the name of the boot animation and sound. Write down the location and exact spelling paying attention to capitalization. Now go back to your extracted rom and look for your boot animation in the path that you wrote down. Open the zip and look at the folders contained inside. This will vary. Some animations have part0 and part1, while others might have just android. This will be needed for the start up boot animation and/or the down boot animation sounds.
***If you're running Synergy Rom yours will most likely look like the last one above.*** I've always edited the "audio="/data/local/bootsound.wav" />" string to match that of the boot animation. Just makes it easier in the long run. Modifying the xml file is easy to do on your phone with a web editing app from the market and never have to touch a PC. However, I prefer to do it with the PC because it is much easier to read, and edit.
To simplify things a bit I’m going to post some pics with the corrected strings so that you can copy and paste to your own XML file.
Synergy’s Stock XML
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Notice there is no string for the down boot animation audio. We will be adding that next as well as changing the location and identity of the boot sounds. Overwrite by copying and pasting the following into your XML starting directly below <BootConfiguration> and stopping after </ShutdownConfiguration>
<BootAnimation animation="/system/customize/resource/bootanimation.zip" audio="/system/customize/resource/FinalThunder.mp3" audiostart="android" />
</BootConfiguration>
<ShutdownConfiguration>
<ShutdownAnimation image_png="/system/customize/resource/downanimation.zip" audio="/system/customize/resource/DownSound.mp3" audiostart="android" image="" fps="15" />
</ShutdownConfiguration>
Click to expand...
Click to collapse
Synergy’s Stock XML should now look like this.
Once your XML file matches the above, you are now ready to save and close out of notepad. Transfer the edited default.xml file to your phones sd card. Using Root Explorer (mount R/W) copy the transfered file to system/customize/cid. Before you paste the edited XML file, rename your existing file by putting .old on the end for a backup. Paste the edited file. Give the default.xml proper permissions and ownership. Long press on the XML file and select "Permissions". Make it look like below and select ok.
X X
X
X
Now long press on the file again and select "Change Owner". Make it look like below.
Owner - Root
Group - Root
Time for your mp3 file! Your start up mp3 can be as long as you want but keep in mind that it will keep playing (mine are around 30 seconds). In contrast, your shutdown mp3 should be no longer than 4 to 5 seconds. Name your start up mp3 FinalThunder.mp3. Name your shutdown mp3 DownSound.mp3. Place your properly named mp3’s on the sd card and with root explorer (mounted R/W). Copy and paste the two mp3 files to system/customize/resources. Give them proper permissions and ownership as shown above.
Reboot and enjoy!
See Post 2 for Th3ory V6.02 and Bamf. The directions are exactly the same.
I'd like to give THANKS to McLabia for testing things out for me and also giving me some "constructive" criticism!
If this helped you at all, hit the Thanks!
hinds73

Th3ory 6.02 AND Bamf Stock XML (Previous versions differ)
Overwrite by copying and pasting the following into your XML starting directly below <BootConfiguration> and stopping after </ShutdownConfiguration>
<BootAnimation animation="/system/media/bootanimation.zip" audio="/system/media/FinalThunder.mp3" audiostart="part0" />
</BootConfiguration>
<ShutdownConfiguration>
<ShutdownAnimation image_png="/system/media/downanimation.zip"audio="/system/customize/resource/DownSound.mp3" audiostart="android" image="" fps="15" />
</ShutdownConfiguration>
Th3ory 6.02 AND Bamf Stock XML should now look like this.
Follow the bottom of post 1.
Th3oryRom INFUS3TH3ORY V1.0B (Open like above and copy/paste)
<BootAnimation animation="/system/customize/resource/VZW_bootanimation.zip" audio="/system/customize/resource/FinalThunder.mp3" audiostart="part0" />
</BootConfiguration>
<ShutdownConfiguration>
<ShutdownAnimation image_png="/system/customize/resource/downanimation.zip" audio="/system/customize/resource/DownSound.mp3" audiostart="android" image="" fps="15" />
Click to expand...
Click to collapse
I have attached what I am currently using for Th3ory Rom. Enjoy!
Edit:Added Th3oryRom INFUS3TH3ORY New build V1.08

Reserved for issues and resolutions...

HA! I didnt expect this to be this long. It didnt read like it was this long. Hopefully people do this though, cause I know I dig the hell outta mine. Thanks again for the help and for writing this dude.

McLabia said:
HA! I didnt expect this to be this long. It didnt read like it was this long. Hopefully people do this though, cause I know I dig the hell outta mine. Thanks again for the help and for writing this dude.
Click to expand...
Click to collapse
I know right!!! Geez, now that it's up I'm like damn!
Not a problem! Thanks for your help too!

hinds73 said:
MAKE A BACKUP!!! I am in no way responsible for anything you do to your phone!
I thought I'd do a write up on how you can add, remove, or change your ROOTED Thunderbolt animation sound. You have to do some of your own poking around to locate the files needed for your specific rom. There are many people that don't want to do this cause they are afraid they will screw something up. You can safely do this on your PC. Create a folder and extract your rom into that folder. Navigate to system/customize/cid where you extracted your rom. Locate the default.xml file and right click and to open with notepad. Now, scroll to the bottom and look for something that resembles the following.
OR this...
OR maybe even this...
You are looking for the name of the boot animation and sound. Write down the location and exact spelling paying attention to capitalization. Now go back to your extracted rom and look for your boot animation in the path that you wrote down. Open the zip and look at the folders contained inside. This will vary. Some animations have part0 and part1, while others might have just android. This will be needed for the start up boot animation and/or the down boot animation sounds.
***If you're running Synergy Rom yours will most likely look like the last one above.*** I've always edited the "audio="/data/local/bootsound.wav" />" string to match that of the boot animation. Just makes it easier in the long run. Modifying the xml file is easy to do on your phone with a web editing app from the market and never have to touch a PC. However, I prefer to do it with the PC because it is much easier to read, and edit.
To simplify things a bit I’m going to post some pics with the corrected strings so that you can copy and paste to your own XML file.
Synergy’s Stock XML
Notice there is no string for the down boot animation audio. We will be adding that next as well as changing the location and identity of the boot sounds. Overwrite by copying and pasting the following into your XML starting directly below <BootConfiguration> and stopping after </ShutdownConfiguration>
Synergy’s Stock XML should now look like this.
Once your XML file matches the above, you are now ready to save and close out of notepad. Transfer the edited default.xml file to your phones sd card. Using Root Explorer (mount R/W) copy the transfered file to system/customize/cid. Before you paste the edited XML file, rename your existing file by putting .old on the end for a backup. Paste the edited file. Give the default.xml proper permissions and ownership. Long press on the XML file and select "Permissions". Make it look like below and select ok.
X X
X
X
Now long press on the file again and select "Change Owner". Make it look like below.
Owner - Root
Group - Root
Time for your mp3 file! Your start up mp3 can be as long as you want but keep in mind that it will keep playing (mine are around 30 seconds). In contrast, your shutdown mp3 should be no longer than 4 to 5 seconds. Name your start up mp3 FinalThunder.mp3. Name your shutdown mp3 DownSound.mp3. Place your properly named mp3’s on the sd card and with root explorer (mounted R/W). Copy and paste the two mp3 files to system/customize/resources. Give them proper permissions and ownership as shown above.
Reboot and enjoy!
See Post 2 for Th3ory V6.02 and Bamf. The directions are exactly the same.
I'd like to give THANKS to McLabia for testing things out for me and also giving me some "constructive" criticism!
If this helped you at all, hit the Thanks!
hinds73
Click to expand...
Click to collapse
Thanx for this...

Just a little tip for those that are wondering how to trim the boot sound, if you download Ringdroid( https://market.android.com/details?id=com.ringdroid&hl=en ), you can chop and rename the files as needed. Just a shortcut for anyone that doesnt want or know how to use audio editing software.

my question to you, how do you use more then 1 mp3 at a time? For example it plays 1 first, and then goes to the other?
so for example
<BootAnimation animation="/system/media/bootanimation.zip" audio="/system/media/scream.mp3" audiostart="part1" audio="/system/media/android_audio.mp3" audiostart="part2" />
I tried this and only android_audio.mp3 started - it skipped/did not play scream.mp3
edit: also how do you make a song loop until animation is finished, or play a song a second time?

Wicked123 said:
my question to you, how do you use more then 1 mp3 at a time? For example it plays 1 first, and then goes to the other?
so for example
<BootAnimation animation="/system/media/bootanimation.zip" audio="/system/media/scream.mp3" audiostart="part1" audio="/system/media/android_audio.mp3" audiostart="part2" />
I tried this and only android_audio.mp3 started - it skipped/did not play scream.mp3
edit: also how do you make a song loop until animation is finished, or play a song a second time?
Click to expand...
Click to collapse
Hey Wicked, I use audacity for all my mp3 trimming. Especially if I want to merge 2, 3, 4 or more clips into one. You can do all kind of things with it. To answer your question, I'm not so sure that can be done. The easiest way would be to time your boot animation from start to finish and then make your clip to suit. If you want, you can upload your mp3s that you want and give me the order you want them in and exactly how long. Also let me know which "part" you want to have them start.
hinds73

PMGRANDS said:
Thanx for this...
Click to expand...
Click to collapse
Welcome, let me know if you hit any snags? With as many updates that come out, zips and xmls seem to get changed regularly.
hinds73

This helped me fix my boot sound
hinds73 said:
Th3ory 6.02 AND Bamf Stock XML (Previous versions differ)
Overwrite by copying and pasting the following into your XML starting directly below <BootConfiguration> and stopping after </ShutdownConfiguration>
<BootAnimation animation="/system/media/bootanimation.zip" audio="/system/media/FinalThunder.mp3" audiostart="part0" />
</BootConfiguration>
<ShutdownConfiguration>
<ShutdownAnimation image_png="/system/media/downanimation.zip"audio="/system/customize/resource/DownSound.mp3" audiostart="android" image="" fps="15" />
</ShutdownConfiguration>
Th3ory 6.02 AND Bamf Stock XML should now look like this.
Follow the bottom of post 1.
Th3oryRom INFUS3TH3ORY V1.0B (Open like above and copy/paste)
I have attached what I am currently using for Th3ory Rom. Enjoy!
Edit:Added Th3oryRom INFUS3TH3ORY New build V1.08
Click to expand...
Click to collapse
Your tutorial on the XML was great, helped me figure out how to fix boot sound on my EVO with Synergy. +1 Thanks button hit

Bumping cause I recommended it to someone... Lol.
Sent from my rooted, Dark Horse INFECTED Synergy bolt running Ziggys latest.

is the default.xml not in an aosp rom? I have searched everywhere in shiftao5p v1.2 but cannot find one.

bigd5783 said:
is the default.xml not in an aosp rom? I have searched everywhere in shiftao5p v1.2 but cannot find one.
Click to expand...
Click to collapse
You may be looking for something like this to make it work.
http://forum.xda-developers.com/showthread.php?t=1048231
Let me know if it works for you?
hinds73

[Advice/Reference/Guide] The Definitive APK Modding & Theming Thread... {06/07/13}

[Advice/Reference/Guide] The Definitive APK Modding & Theming Thread... {06/07/13}
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
XperienceD said:
This is why I love Virtuous Ten, as you can install multiple resources.
Click to expand...
Click to collapse
jacknb1ack said:
wow, i didnt know there is tools like that
Click to expand...
Click to collapse
After reading jacknb1ack's comment I felt compelled to re-write this whole thread to accommodate for the various PC Programs that you use to do all of your apk modding which can and do make things a hell of a lot quicker. I've wrote this as something I would have liked to have come across when I first joined because I know there is a lot to take in, and hearing you need to decompile, edit this or that xml, recompile, sign etc etc etc can be off putting for some especially if you struggle to get a program or apktool setup to begin with.
Knowing how to use command prompts will be beneficial in the long run so I've wrote a detailed guide below which covers it from start to finish along with how to Sign and Zipalign your apks, pulling them from the computer and so on. I've also covered some Theming basics with links to everything you're ever going to need, which will be extra handy if you're just getting started.
Minimum Requirements:
A Rooted Phone.
Java SE Runtime Environment
Java SE Development Kit
Any of the apk modifying methods below.
7-Zip or WinRar
Theming Requirements:
Notepad++
Photoshop, GIMP or any other image editing software.
Patience. :silly:
To avoid any java not found issues you need to set up the PATH for it in Environment Variables, you can find a short Guide on how to HERE. This is how mine looks...
Code:
[B]C:\Program Files (x86)\Java\jre6\bin;[/B]
I would advise that you also install the Android SDK but if you don't want to you can download this APK_Mod.zip that you can extract to a folder and place it anywhere you want on your Computer (I recommend C:\APK_Mod) and run any adb, apktool, zipalign or signing command prompts from it. You can find a more detailed guide for this method below.
But first off all here are some of the most common Programs that you can use to modify and theme your apks, and I'll start with one of the best...
Virtuous Ten Studio (VTS)
Virtuous Ten Studio (VTS) is the ultimate solution for the modification of android applications.
This program allows you to manage entire Android projects within an easy to use and familiar environment.
The intended group of users covers anyone from a themer over ROM devs up to the smali gods known for their awesome mods of existing apks.
The modifcation of smali code is one of the biggest features in VTS. You can easily decompile, edit and recompile any apk or jar file.
However, the application is not limited to smali files. You can edit almost any file found inside an apk or jar.
Virtuous Ten Studio is also the official successor to the highly important M10Tools released last year by the Virtuous Team.
You can easily edit any m10 file from Sense apps in order to resize or change them.
Additionally VTS brings support for un- and repacking of boot images (boot.img), a job that previously required a cygwin installation with the dsixda kitchen.
Since VTS' own implementation is a native windows solution, which means you don't need dsixda or cygwin anymore.
VTS has been designed to run on Windows, has been in development for nearly two years and has gone through many stages of testing.
Today VTS is a highly respected full blown Android IDE (Integrated Develoment Environment) suited for all your reverse engineering tasks.
Click to expand...
Click to collapse
- www.virtuous-ten-studio.com
AndroidSuite 2013
AndroidSuite 2013 what it does
Decodes and encodes Dex files
Decodes and encodes APK files (Previously bugged in APKManager)
Gives a console output
Flash boot.img (fastboot)
Flash update.zip (fastboot)
reboot/reboot fastboot mode
Sign unsigned apks
Click to expand...
Click to collapse
- (App) Androidsuite 2013 v117 (01/04/2013) Jelly Bean Support!
Tickle My Android 5.4
Tickle My Android, or TMA for short, is a command line tool for Windows that uses apktool to help you pull and decompile files from your Android phone or tablet.
But it can also:
change the battery icon,
change the WiFi icon,
change the signal icon,
change the emoticons,
change the notification toggles,
change the transparency of the statusbar (if the rom allows it),
add Ice-Cream Sandwich-style transitions
zipalign apk files,
sign new apk files,
sign recompiled apk files in the same way as the original,
deodex apk and jar files,
backup personal data and transfer to a brand new device,
resize and change boot animations,
change fonts,
add sounds from other devices,
create backup-generating flashable zip files
..and now comes in Portuguese and French!!
Click to expand...
Click to collapse
- [TOOL]Tickle My Android 5.4 - DE/RECOMPILE APPS, CHANGE ICONS...AND MORE!!!!
ApkManager V6.1
1. Based on ApkManager 4.9 by Daneshm90 (Big thanks to him)
2. Updated Apktool V1.5.2 by iBotPeaches & Brut.Alll
3. Updated Aapt v0.2
4. Default compression level set to “0?
5. 512Mo as default allowed heap size
6. 3 ready for use fake frameworks : “other\wanam1.apk”… (for Lidroid framework editing)
7. Add a “Decompile all files” feature (option 25)
Click to expand...
Click to collapse
- wanamlite.com
Command Prompt Editing​
Basically this is just manually doing what all of the programs above need to do in order to decompile, recompile, sign and zipalign apks so it's worth knowing how to modify apks this way for occasions when the above programs for whatever reason gives you issues.
Use Linux or a Mac?
See the following threads for more information on using apktool on other Operating Systems...
APK Manager for Mac OS X
[Linux][UTILITY][TOOL] APK Multi-Tool
[tutorial] decompiling,recompiling and signing in linux (27-01-2013)
How to install and use Apktool with Ubuntu
Getting APKs To Your PC​
You have two options here...
1. Use a file manager on your Phone to copy and paste files to your SD, then connect to your PC and use Windows Explorer to copy and paste to your desired location.
2. ADB. Open a command prompt window in the ADB folder (see below) and type/copy the following command...
Code:
adb pull /system/app/ Original_apps
...which will pull the whole app folder to your computer and create a new folder called Original_apps, which you can then simply copy apps to the main folder ready to be modified (keep the Original_apps folder as a backup). Then do the same for your framework folder...
Code:
adb pull /system/framework/ Original_framework
...want to pull your Phones whole system...
Code:
adb pull /system/ Xperia_Z_System
...you can rename "Xperia_Z_System" to whatever you want.
Further Information: [WINDOWS][TUT]ADB tutorial, setting up ADB, usefull commands, collecting debug info.
This is a zip of the apktool folder I currently use - APK_Mod.zip - which as said above also contains the ADB files needed to pull and push apps from your Phone, or you can check out the following links...
[Tool] ADB Fileexplorer
[TOOL][WINDOWS] Android Apktool
Installing Resources​
For apktool to work you need to install the resources needed by your apks for de and recompiling, and those resources are other apks, the first apk regardless of your Phones manufacturer is going to be your framework-res.apk. The second apk you need is dependent on the manufacturer so you need to check your framework folder for another apk such as twframework.apk or SemcGenericUXpres.apk, in some cases it might even be the SystemUI.apk but you would need to check if you have issues with the other two. Put those two apks in the APK_Mod folder to begin with then open a command prompt window. The easiest way for me is holding the shift key then right clicking the mouse and selecting Open command window here, but if you're not able to do that then click your Start button and search for Command Prompt, then open it. You then need to point it to the relevant folder, so type cd then copy and paste the location of the folder (cd C:\APK_Mod) and hit enter.
The install commands are...
Code:
[B]apktool if[/B] framework-res.apk
...and for the second...
Code:
[B]apktool if[/B] SemcGenericUXpres.apk
Decompiling​
The command for decompiling is...
Code:
[B]apktool d[/B] framework-res.apk
...and so on for each individual apk you want to modify. A new folder will be created that is named after the apk you are modding, then you can edit xmls, smali files and .9png images. You'll notice that there are a lot more folders when you decompile an apk, that's normal as those folders are from the resources.arsc and where you'll find the xml files you may need to edit to make the changes you want.
Recompiling​
When you've done editing it's time to recompile, using the command...
Code:
[B]apktool b[/B] -insert folder name-
...and if you've edited your files correctly then it should compile with no errors and create a folder named dist in the decompiled folder along with a new apk.
Signing​
Before using the new apk you will need to sign it, to do this you need to extract (open the apk and simply drag and drop them to the dist folder) from the original apk the resources.arsc (only if you haven't changed anything in the values folder, the AndroidManifest.xml and META-INF folder (if it exists), then copy them into the new apk. In WinRar it will give you the option to choose the compression method, and it's vital that you choose Store as the compression method because if you don't then you WILL BOOT LOOP after restarting your Phone!
NOTE: If you have edited anything in the values folder then extract the resources.arsc from the new apk and copy (drag and drop) it back in the same manner described above.
Alternatively you can use the following command...
Code:
[B]java -jar signapk.jar testkey.x509.pem testkey.pk8[/B] framework-res.apk.apk framework-resS.apk
...notice the extra "S", the output name has to differ from the input name otherwise it will give an error, if done right it will create a new apk called framework-resS.apk, just remember to rename it back to the original before using it on your Phone.
Zipaligning​
DISADVANTAGES OF UNALIGNED APKs
Quite understandably, situation would be reserved for unaligned application packages. Resource reading would be slow and memory usage would be on the higher end of the spectrum. It would also depend on how many unaligned applications are present. For example, if less number of applications with an unaligned home application, you’d see slower application launch times. This is the best case scenario. For a worst case scenario, having a number of unaligned applications will result in the system repeatedly starting and killing processes, struggling with lags and huge battery drain.
Click to expand...
Click to collapse
- SOURCE
The command for zipaligning is...
Code:
[B]zipalign -v 4[/B] framework-res.apk ZAframework-res.apk
...notice the "ZA", again that can be anything you want so long as it differs from the original name, I use ZA for an obvious reason, and again don't forget to rename it before using on your Phone.
Getting apks back to your Phone​
It's just a reversal of how you got them off your Phone to begin with, use a file explorer and put your apk on your SD Card, then move it to the Phones System folder and change it's permissions to rw-rw-r, then move and replace it with the original. Most apps should continue to work but if you change your framework-res or SystemUI you will most likely need to reboot. Or you can use adb to push and install them. Check the previous link for the commands.
If all the above has worked correctly you should now have your modified apk installed with the changes you've made displayed on your Phone.
Theming & Modifying​
This is where the fun begins, once you've got setup to decompile your apks then obviously you're going to want to mod them, so here's a few pointers to clear up what seems like a daunting process to new comers...
To start with you'll probably just want to start with replacing images, so if that's all you want to do for now then here's a quick tip, you DON'T need to decompile or sign your apks!, simply edit and rename your replacment images on you computer, preferably using the same or similar dimensions then drag and drop them back into the right folders in the apk, always using Store as the compression method, but PLEASE NOTE; .9 pngs can be replaced in the same way, but if you want to edit them in Photoshop for example then you need DO need to decompile them.
A few things to note...
Smali code is real Developer territory, it's Matrix code to me , thankfully there's usually a guide to follow so you can simply copy and paste code without having to fully understand how it works, so don't fret about this.
.9pngs are simply png images with a 1 pixel border. You can edit anything within that border but anything on or over will give errors when building. Unless you're creating an image from scratch then you can leave the border as it is, it's that simple! Sure there's a bit more to .9png editing but you can find a few links below that go into more detail about .9s and how they work.
xmls are relatively simple and edited with Notepad++, much simpler to understand than smali and again, there's usually a guide to be found for most mods you may want to make yourself, but if you're feeling brave you can experiment with it when you have a basic understanding of how it works.
Restoring modified files if you mess up is easier and quicker with a CWM.zip, especially if you're modifying any framework apks! Just because an apk might build with no errors doesn't mean it won't give you any when installed to the Phone.
.9png Editing​
I hope after reading this explanation you're left wondering what all the fuss is about, as it really is quite simple. I'll use the following two images, btn_default_pressed_holo.9 & status_bar_close_off.9 to illustrate the basic point of the borders...
Decompiled .9pngs:
Recompiled .9pngs:
Those borders control which part of the image is stretched, and we'll use Draw 9-patch which is for editing the borders of decompiled .9pngs and lets you see how the image, when stretched, will be displayed on the Phone. Notice that the borders are different sizes, well that's because I only want/need a certain part of the image to stretch to get the desired look on the Phone.
...in the image below the left side shows the stretched image and desired effect should look on the Phone and the right side shows how it would look if I had edited the borders incorrectly or used none at all...
You can get away by not using a border but you would need to edit your image to specific dimensions to accommodate for the stretching, for example it might look fine for a simple OK button but it might not look right if you used the same .9png for a screen press which stretches the whole length of the screen, so you're better off just using them to begin with, plus you'll more than likely get errors down the line while decompiling or recompiling your apk.
The use of the border is made even more clear when you add text to an image. For my status_bar_close_off.9 I've filled all four sides of the image (except for an empty pixel in all four corners as that is the max amount of border you can use) as I need it to stretch the image just how I've edited it...
...but if I used the same sized left side border as the btn_default_pressed_holo.9 then this is how it would look on the Phone...
...which is obviously not the look I'm trying to achieve, as the left side border is causing the image to stretch incorrectly.
So that's basically it, depending on the image you're editing you can usually leave the borders alone but if you create one from scratch then you might need to play about with them if your images doesn't look quite right when used on the Phone. Here's a few links that will assist you further, especially the batch editing...
How to edit .9.pngs
[TUTO] Create your 9.png !
[UTILITY][TOOL] 9patchPngSuite [Windows&Linux]
How to draw NinePatch images with Photoshop - .9.PNG
[TOOL][Multi-Platform][.9.png][ALL DPIs] Android Resizer Tool
[Tutorial][Commentary] How To Batch Edit .9PNG/PNG Images
Xposed Framework​
rovo89 said:
In this thread, I'm presenting a framework which gives you the possibility to modify your ROM - without modifying any APK (developers) or flashing (users)!
...
Advantages:
No need to modify any APKs. This means:
No need to decompile, change things in smali, compile, sign, ...
It will work for odexed and deodexed ROMs.
Your mod is not bound to a specific version of the ROM. Unless there is a major change in the methods called for a certain functionality, your mod will continue to work even when you upgrade your ROM. Hell, it will probably even work with different ROMs.
Multiple mods can be installed at the same time, even if they change the same package. So you can use these battery icons and those quick toggles. Even hooking the same method twice is possible. Of course, this only works properly if the mods are not trying to do incompatible things.
It does its magic at runtime. That means you can implement options to let the user decide if they prefer the bikeshed to be painted in red or blue. Or you can have some extra logic for certain ROMs without building different mod versions.
It can be disabled easily without having to reflash.
It's open source.
Click to expand...
Click to collapse
- [FRAMEWORK ONLY!] Xposed - ROM modding without modifying APKs
[Guide] Porting XTheme themes
[Guide] Xposed Framework/TabletUI (Noob-Friendly)
[INDEX][WiP] List of APPs & MODs that use XPOSED Module
[MOD][XPOSED][4.0+] XThemeEngine beta5 - Theme engine for any rooted phone
And that's pretty much it, the only way you're really going to learn is by reading then putting into practice what you've read and picking stuff up along the way, fortunately this far into the history of Android there are numerous guides for numerous mods and tools to help with a variety of tasks and the following links are going to be a big help...
U.I Modding
Text Color Guide
Tutorial :- Changing App Icons
[TUTORIAL]How to Theme Your MMS
[How-to] Edit the "About Phone" display
[GUIDE][REF]Changing System Text Settings
[TUTORIAL] How to add various framework/Settings mods
[TUTORIAL] Where to find the colors for making a theme
Some Extra Theming and Moving the Power Widget Down
[HOWTO] Integrating/Adding applications to the settings menu
[TUT][JB] HOW TO THEME SystemUI.apk for TOTALLY newbie!
[GUIDE][MOD][SYSTEMUI] How to add 0.0K/s meter on statusbar ICS/JB
[GUIDE] How to get Transparent App Drawer [Launcher2.apk or Trebuchet.apk]
[TUT] How To Center The Clock On The Statusbar..And Move Other Icons As Well!
[How-To]Removing Battery Percentage, Adding Toggles,Battery Circles to Statusbar
[GUIDE][Mods][All Devices]How to add/ Change Clocks to Analog/ Digital with Seconds
Various Tools...
[TOOL][BETA]Miui Theme Converter/Convert apk Themes!!!
[TOOL][JAVA]"The Rom Fumbler" aka "The Battery Icon Creator"[V29.0]
[TOOL]Boot Animation Factory-Create,Preview and Manage Boot Animations
Useful Links
findicons.com
colorschemer.com
[GUIDE] Tips for themers
Ultimate Online Theme Kitchen
[GUIDE] Want to learn how to theme?
General Questions about Themes GO HERE!!!!!
[Guide] How to port themes to T-Mobile Theme Chooser
[Collection] ICON SETS | Over *750* different Icon Packs
[DEV/GUIDE]Creating APKs for use with TMobile Theme engine
[GUIDE] T-mobile theme engine for the faint at heart (non-linux users)
[TEMPLATE] Icon Packs/Themes for Apex, Nova, Holo, ADW, and more!!
[INFO] Custom framework-res.apk resources.arsc using vendor overlays
If you feel something more should be added to this thread please feel free to suggest it.
Credits & Thanks:
@_calum_
@Diamondback
@ebs512
@Rizal Lovins
@Ticklefish
@wanam
@rovo89
And not forgetting @iBotPeaches and @Brut.all for making it possible with - [UTIL][Feb 02 2013] Apktool v1.5.2 - a tool for reverse engineering apk files

ClockworkMod Recovery...
Flashable Clockwork Mod (CWM) zip​
ClockworkMod Recovery zips are used for flashing individual files to whole ROMS and can be a life saver if you push a badly edited apk to your Phone that results in a bootloop. There's also a few programs that can assist you with that too, but if all you're doing is replacing a few files all you really need is a template, then it's just a matter of creating the Phones folder setup in the zip which is simply creating folders: system\app - system\media\audio etc then dragging and dropping your files into it. A basic understanding of the updater script is essential, a ROM.zip will more than likely wipe your Phone whereas a Theme.zip may just replace files but it might delete some also.
See below for a CWM.zip Template but first some helpful links...
[Tool]easy flasher v4 (ur own update.zip)
[TUT] [for NOOB] editing updater-script for noobs!
[TUTORIAL] Making Flashable ZIPs, EDIFY Script, ZIP Signing & Key Creation
[Utility-Tool][DEVandThemers]CWMflashpack.zipCreatorV1{TheCollective}w/EdifyScripting
This is my Theme_CMW_Template.zip which is set up so you can add your own files to the framework and apps folders in the main system location, but you can easily add other folders to it if you want to add things like fonts, tones or anything else, just remember to add folders within folders if that's where the files you want to include are such as tones, media\audio\alarms for example.
If you navigate to META-INF\com\google\android you will find the updater-script which controls how the zip works and the text you see when you run it in CWM. As this zip is just for basically over writing files you don't need to edit anything except for a few lines...
...this is how I've edited it for my Ice Green ResMods theme...
...so just edit it using Notepad++ to your liking.
When adding files to your zip add them using Normal as the Compression Method...
...and that's pretty much it. Remember to remove the text files I've added otherwise they will be flashed to your folders too.

[How To] AOSP Lockscreen...
[MOD][4.2.2][Z] AOSP Lockscreen
1. Decompile your framework-res.apk.
2. Go to your layout folder and open keyguard_screen_tab_unlock.xml then find and change the following lines...
Code:
<com.android.internal.widget.DigitalClock android:layout_gravity="right" android:id="@id/time" android:layout_marginTop="@dimen/keyguard_lockscreen_status_line_clockfont_top_margin" android:layout_marginRight="@dimen/keyguard_lockscreen_status_line_font_right_margin" android:layout_marginBottom="12.0dip">
...to...
Code:
<com.android.internal.widget.DigitalClock android:id="@id/time" android:layout_gravity="center_horizontal" android:layout_marginTop="100.dip" android:layout_marginBottom="3.0dip">
...then change this...
Code:
<LinearLayout android:layout_gravity="right" android:orientation="horizontal" android:layout_marginRight="@dimen/keyguard_lockscreen_status_line_font_right_margin">
...to this...
Code:
<LinearLayout android:layout_gravity="center_horizontal" android:orientation="horizontal" android:layout_width="wrap_content" android:layout_height="wrap_content" android:layout_marginBottom="6.0dip">
...also change this...
Code:
<Button android:layout_gravity="right" android:id="@id/emergencyCallButton" android:visibility="gone" android:layout_width="wrap_content" android:layout_height="wrap_content" android:layout_marginTop="4.0dip" android:layout_marginRight="16.0dip" android:text="@string/lockscreen_emergency_call" android:drawableLeft="@drawable/lockscreen_emergency_button" android:drawablePadding="4.0dip" style="?android:attr/buttonBarButtonStyle" />
...to this...
Code:
<Button android:layout_gravity="center_horizontal" android:id="@id/emergencyCallButton" android:visibility="gone" android:layout_width="wrap_content" android:layout_height="wrap_content" android:layout_marginTop="4.0dip" android:text="@string/lockscreen_emergency_call" android:drawableLeft="@drawable/lockscreen_emergency_button" android:drawablePadding="4.0dip" style="?android:attr/buttonBarButtonStyle" />
...then change this...
Code:
<LinearLayout android:gravity="center" android:orientation="horizontal" android:layout_width="fill_parent" android:weightSum="2.0" style="?android:attr/buttonBarStyle">
...to this...
Code:
<LinearLayout android:gravity="center" android:visibility="gone" android:orientation="horizontal" android:layout_width="fill_parent" android:weightSum="2.0" style="?android:attr/buttonBarStyle">
3. Recompile and sign your framework-res.apk
4. Go to system/app and either delete, rename or remove all permissions for UxpNxtLockScreen.apk.
5. Replace your framework-res.apk on your Phone with the new one, reboot, done....
To also remove the operator logo as I have change this line...
Code:
<TextView android:textAppearance="?textAppearanceMedium" android:textSize="@dimen/keyguard_lockscreen_status_line_font_size" android:textColor="?textColorSecondary" android:ellipsize="marquee" android:gravity="center_horizontal" android:id="@id/carrier" android:layout_width="fill_parent" android:layout_height="wrap_content" android:layout_marginBottom="12.0dip" android:singleLine="true" android:layout_alignParentBottom="true" />
...to...
Code:
<TextView android:textAppearance="?textAppearanceMedium" [B][COLOR="Red"]android:visibility="gone"[/COLOR][/B] android:textSize="@dimen/keyguard_lockscreen_status_line_font_size" android:textColor="?textColorSecondary" android:ellipsize="marquee" android:gravity="center_horizontal" android:id="@id/carrier" android:layout_width="fill_parent" android:layout_height="wrap_content" android:layout_marginBottom="12.0dip" android:singleLine="true" android:layout_alignParentBottom="true" />

Deodexing...
philos64 said:
The differences between Odex and Deodex Files...
In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space The odexed file structure works well as an optimization tool. Since these .odex files contain preliminary load information about each system app, the OS knows what to expect when it’s booting up, and consequently, loads all these apps faster.
On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
For instance, on a non-rooted device you’ll find
system/app/Phone.apk ===> as well as ===> system/app/Phone.odex
Click to expand...
Click to collapse
- [GUIDE] - The differences between Odex and Deodex Files
[TOOL][WINDOWS]Universal Deodexer[ALL DEVICES!!]​
abcdjdj said:
Hi everyone,
Alokbina and I have created a tool which allows users to very easily deodex apks from a rom. This tool is very useful for Rom developers too. For now only windows is supported but we will try our best to make the same tool for linux too and make the tool as user friendly as possible. And, please don't forget to thank alokbina too.
Requirements:-
--->Java installed on your PC
--->system/framework folder from your rom
--->apks from that SAME ROM with the respective .odex file
--->Patience and a calm head (common sense included)
You can watch this video for setting up and using the tool -
- [FIXED][UPDATE - V3][TOOL][WINDOWS]Universal Deodexer[ALL DEVICES!!]
Click to expand...
Click to collapse
[GUIDE] How to DEODEX stock ODEXED ROM using dsixda's kitchen

Random Stuff...
edangel said:
Solution For 70 limit stock SMS Characters...
Well...for people who can't sent 160 sms characters on stock sms messaging app and they are limited to sent 70 characters here is the solution...
Simple...root needed!
with root explorer etc...
go to: /data/data/com.sonyericsson.conversations/shared_prefs
and open the file com.sonyericsson.conversations_preferences.xml.
find the line which says "semc_pref_key_character_conversion"value=false
and set it true..!
save the file and reboot your phone...and happy texting!
if i helped press thanks button!
:laugh:
Click to expand...
Click to collapse
XperienceD said:
cickii said:
can someone please tell me which xml is responsible for the blue / gray colors in the picture below.
Click to expand...
Click to collapse
Finally sussed it. It's LinearColorBar.smali found at Settings\smali\com\android\settings\applications, search for 0x99cc and -0xff6634 and change them for your own colours...
Click to expand...
Click to collapse
XperienceD said:
Hi all.
Just a short write up as a follow on from THIS thread as this is relatively quite simple.
So you want to change your notification background from the plain dark color to something a bit more your style...
...well all you need to do is decompile your SystemUI.apk and navigate to the values folder and open up your drawables.xml and you should see something like this...
Code:
<resources>
<item type="drawable" name="notification_number_text_color">#ffffffff</item>
<item type="drawable" name="notification_item_background_color">#ff111111</item>
<item type="drawable" name="notification_item_background_color_pressed">#ff257390</item>
<item type="drawable" name="ticker_background_color">#ff1d1d1d</item>
<item type="drawable" name="status_bar_background">#ff000000</item>
<item type="drawable" name="status_bar_recents_background_solid">#e5000000</item>
<item type="drawable" name="status_bar_recents_app_thumbnail_background">#88000000</item>
<item type="drawable" name="status_bar_notification_row_background_color">#ff090909</item>
<item type="drawable" name="notification_header_bg">#ff000000</item>
<item type="drawable" name="notification_tracking_bg">#e5000000</item>
<item type="drawable" name="recents_callout_line">#99ffffff</item>
<item type="drawable" name="notification_item_background_legacy_color">#ffaaaaaa</item>
</resources>
Simply change these two lines...
Code:
[B]<item type="drawable" name="notification_item_background_color">#ff111111</item>
<item type="drawable" name="notification_item_background_color_pressed">#ff257390</item>[/B]
to...
Code:
[B]<item type="drawable" name="notification_item_background_color">[COLOR="Red"]@drawable/status_bar_item_background_normal[/COLOR]</item>
<item type="drawable" name="notification_item_background_color_pressed">[COLOR="Red"]@drawable/status_bar_item_background_pressed[/COLOR]</item>[/B]
...then add two .9 png images of the same name, status_bar_item_background_normal and status_bar_item_background_pressed to your drawable-hdpi folder, recompile, zipalign, push to your Phone, done.
Quick Tip: If you can't create a .9 from scratch just edit the first two in drawable_hdpi which in my folder is alert_bar_background_normal.9 and alert_bar_background_pressed.9, just remember not edit over the .9 borders.
Click to expand...
Click to collapse

Hell man no posts from anyone??
Excellent excellent thread man.

dhirend_6d said:
Hell man no posts from anyone??
Click to expand...
Click to collapse
With 1500+ views hopefully it's because it's written that well People don't need to ask anything. :silly:
dhirend_6d said:
Excellent excellent thread man.
Click to expand...
Click to collapse
Thanks.

Thanks for this!
Sent from my SGH-I747 using xda premium

Can you make a tutorial
1. How to port magnify glass to ics devices/mdpi
2.how to port small app to ics devices/mdpi
3. How to add internet speedo meter In pull down menu not in status bar for ics
A million thanks if you make it ......
Sent from my ST21i2 using xda app-developers app