Hey guys, this is gonna be kind of long so bear with me:
I'm running a Le Pan TC970 and we currently have root access, but no CWM or custom ROMS. It runs on Froyo 2.2 OS and as we all know, it's ugly as sin. I've successfully managed to use this framework-res replacement script (found here: http://forum.xda-developers.com/showthread.php?t=889963) to swap out icons galore and change the status bar and notification area to blacked-out colors. I'm trying to make a theme for our community, because I know I can't be the only one looking at this ugly OS and screaming.
Well the problem I'm having is really frustrating, the black notification bar looks great, however the notifications & clock are in black font. Therefore you can't see them with the new notif/status areas. I did some research and figured out you can change some color codes in the /layout/status_bar.xml file. But when I try to open it, it's all encrypted. I used APKTool to decompile and recompile it and it wasn't encrypted. I changed the #000000 to #FFFFFF. Then, flashed it using the script. This caused a massive boot loop and I couldn't power down the tab at all. Being impatient, with the help of a friend I figured out how to rip open the tab and pull the battery, allowing me to access the proprietary recovery & I reflashed the firmware and got back to stock.
I've tried pulling that file from other themes and just replacing it, I've tried decompiling & recompiling and editing the original file, I've tried everything I can think of and every solution I've searched for has lead me to endless boot loops when I try to screw with anything besides the icons & images in hdpi folder. This is the only stopping me from having a custom theme is the damn color code. Does ANYONE have any suggestions I can try?
I don't want to continue getting boot loops because each time I have to reflash the stock firmware, re-root, tiba restore to get my root tools back and it's a big fat pain in the A$$. We have no CWM or NANDROID capabilities, so this is really my only option. Before I throw this stupid thing, I thought I'd ask around XDA and see if someone knew the solution to my problem.
Thanks for any help
you should enable usb debugging and from then you can use adb
i you make backups of the file you might try pushing it back if the edit fails
however, you might want to take a look at this topic: [TUTORIAL] Where to find the colors for making a theme
hope this topic helps you
picard666 said:
you should enable usb debugging and from then you can use adb
i you make backups of the file you might try pushing it back if the edit fails
however, you might want to take a look at this topic: [TUTORIAL] Where to find the colors for making a theme
hope this topic helps you
Click to expand...
Click to collapse
I've read this thread a few times, I could be doing something completely wrong I'm not sure. But I've used APKTool to decompile and edit the font colors as that guide suggests and then recompile and it always ends in a bootloop. I have tried pushing the individual files with adb & that was a flop also. It's just this one stinkin' XML file giving me issues. I'll try re-reading that again and see if I did something wrong, thanks for the help
dbaybay said:
I've read this thread a few times, I could be doing something completely wrong I'm not sure. But I've used APKTool to decompile and edit the font colors as that guide suggests and then recompile and it always ends in a bootloop. I have tried pushing the individual files with adb & that was a flop also. It's just this one stinkin' XML file giving me issues. I'll try re-reading that again and see if I did something wrong, thanks for the help
Click to expand...
Click to collapse
color is 8-digit number: AAEEGGBB, where AA is alpha value (or transparency, where FF is the least transparent and 00 is fully transparent), and RRGGBB is the color code in RGB hex (in the OP you wrote 6digit colors, so i'm not sure if you used those in the xml or the proper format, because using 6digit colors might be a cause of bootloop)
picard666 said:
color is 8-digit number: AAEEGGBB, where AA is alpha value (or transparency, where FF is the least transparent and 00 is fully transparent), and RRGGBB is the color code in RGB hex (in the OP you wrote 6digit colors, so i'm not sure if you used those in the xml or the proper format, because using 6digit colors might be a cause of bootloop)
Click to expand...
Click to collapse
Yeah, I meant it that way, sorry. Once the XML file was viewable in Notepad++ (it was encrypted until I used APKTool) I noticed it said "FF000000" and I wanted it white, so I replaced only the "000000" with white, leaving it exactly "FFFFFFFF".
I also tried swapping out that file with files from other themes that already had white text. Every time results in a boot loop. I'm not sure if the files for my tab are proprietary but when I edited it myself and recompiled I just don't get why it wouldn't work.
In some of the research I've been doing, I stumbled across this thread - http://forum.xda-developers.com/archive/index.php/t-1060199.html - which states that if you edit and XML file you must delete the resources.arsc so it knows to create a new one reflecting the changes.
I'm using APKTool to decompile the framework.res.apk file and once it's decompiled "resources.arsc" isn't there. It only shows back up once I recompile the framework-res.apk.
Can someone give me a lead as to if this is true and if so, how to do it properly?
try apkmanager
picard666 said:
try apkmanager
Click to expand...
Click to collapse
Tried this out, decompiled, edited, compiled, signed, flashed. Still got the bootloop and fried my 16GB microSD card. Flashed the same file several times now with no problems besides the bootloop, so this is the only thing I can accuse of frying my SD card.
Sigh. I give up at this point.
Related
Hi Guys,
is it possible to change android (magic) taskbar color/theme for the device without root access?
I don't like the boring white, I want black taskbar with white font.
any suggestion will be appreciated .
thanks
I would like the same my device is rooted though
Draxter said:
I would like the same my device is rooted though
Click to expand...
Click to collapse
dont think it is possible if you aren't rooted. If you are rooted open up the update.zip file you are using as your rom using 7-zip, go to where framework drawable folder is. Open status bar and change its colour, drop it back in and resign app. There are instructions how to do this in themes section of Dream.
http://forum.xda-developers.com/showthread.php?t=473580
http://forum.xda-developers.com/showthread.php?t=471586 I use post number 6 the way i do it.
I'm using the Vodafone rom... I don't think I can get my update.zip from that? I rooted my device with haykuro's stuff in this tutorial.
http://android-dls.com/wiki/index.php?title=Magic_Rooting
I want to keep my Dutch XT9 so I can't flash anything else but smartphone france or my stock vodafone...
all the drawables should be in the root-me rom. open it and have a look for them.
But if they aren't I will brick my device by flashing a wrong framework...
no you wont. All you do is open it and drop in the .pngs you want, then resign it. they will be there in the rom- if not look at one of the other roms- Rogers, or daldroid will have them.
If it does go in to boot loop reboot into recovery and flash the last working rom you have until you figure out what went wrong. The only thing you are changing is the pngs. you shouldnt go intoa bootloop doing this- i have done a heap of theming for myself for the G1 and each time i got a boot loop it was cos i was playing around with services.jar and xml files. each time i just rebooted into recovery and reflashed previous working rom.
The thing is, I don't know which ROM I have... I have rooted my magic by using the android-dls tutorial with haykuro's stuff. There are still some vodafone relics left. I still have the vodafone shortcut, and i still have support for Dutch XT9.
http://android-dls.com/wiki/index.php?title=Magic_Rooting
I haven't made a Nandroid backup and I don't know how to make a backup either so... There is only one alternative, flashing Smartphone France firmware, it has Dutch support. I wouldn't mind trying out that one but that'll be the first time that I flash firmware onto my Magic so I'd like some guidance on MSN with that
Drawer
Im looking for the application drawer button in the res folder that is inside framework... found the status/notification bar and all icons but can't seem to find the app drawer button... i want to change it to a darker grey and make the notification bar black...
the app drawers are in launcher.apk
Easiest/safest way of changing the graphics I have found was to:
1. Connect your phone via USB and make sure you have the drivers installed
2. do adb remount
3. Do a adb pull on /system/framework/framework-res.apk for example
4. Open the apk with something like winrar etc
5. Locate the png files you want to change and extract them
6. make modifications to the files
7. pop back to the apk
8. do an adb push of the file back to the device
I've done this with fairly few apk's such as the launcher.apk and framework-res.apk and never had to resign the file =o)
The advantage is that you are using the file from your phone that you know works =o)) certain apk's don't even need a restart such as the Launcher.apk, I did alot of modding with the app drawer without ever needing to restart the phone.
This is good for changing the images but things like changing the clock color is ALOT harder, it requires you to edit the services.jar file with a hex editor =o(
Hope this helps.
Draxter said:
the app drawers are in launcher.apk
Click to expand...
Click to collapse
Ok, i did find the file in the launcher.apk, i edited it and all the other files and now need to resign in linux... was looking for the SignApk.jar in the SDK and didn't find it... also tried JF's testsign.jar and didnt work... can anyone point me in the right direction so i can resign the file using test keys in linux.
Thanks,
If you just changed the png's you shouldn't have to resign it
fxn said:
If you just changed the png's you shouldn't have to resign it
Click to expand...
Click to collapse
What about the hour and date font in the status bar... if i change the notification area to black it wont automatically switch to white text... do you know where i can find the parameters to change it?
Some of the text like notification texts etc are held in framework-res.apk xml files in the drawable folder if I remember correctly.
The clock is the difficult one as it is inside services.jar file, its a serious pain in the back side, the dream forum has more info about it but it involves opening up files in hex editor and changing the hex code directly there
I'll be having a look at this and see if I can make step by step guide of this but it is seriously a pain!
Any idea which XML's in framework-re.apk (or other location) hold the various notification font colour(s)?? I can't seem to find it.
Please read this whole thing before you reply!
I am trying to edit the battery icon XML files in framework-res.apk. Awhile ago I found a tool that would convert from binary XML to human-readable XML and back again, but for the life of me I cannot find it again.
Anyway, I opened stat_sys_battery_charge.xml with it and all was good, except it mentioned weird names for filenames. Eg instead of 'res/drawable-hdpi/stat_sys_battery_0.png' it was '89845b4jrqyuq34gy34q89tyq34' (or some gibberish like that).
I understand everything up to this point. I understand why those names are encoded like that. What I don't understand is how people figure out these codes. I have been using someone elses framework-res.apk as my base, and they use "v4" folders. Eg 'drawable-hdpi-v4' instead of 'drawable-hdpi'. These filename codes in the XML value were generated for this V4 folder, correct? How did they do that?
I do not want to use a V4 folder in my theme if I can avoid it. If I have to, I still have a problem as to how to correctly point to my battery icons. And no I cannot just replace the PNGs because my changing icons have more frames than the stock XML allows.
Any help would be extremely appreciated. Thank you.
TheLynxy said:
Please read this whole thing before you reply!
I am trying to edit the battery icon XML files in framework-res.apk. Awhile ago I found a tool that would convert from binary XML to human-readable XML and back again, but for the life of me I cannot find it again.
Anyway, I opened stat_sys_battery_charge.xml with it and all was good, except it mentioned weird names for filenames. Eg instead of 'res/drawable-hdpi/stat_sys_battery_0.png' it was '89845b4jrqyuq34gy34q89tyq34' (or some gibberish like that).
I understand everything up to this point. I understand why those names are encoded like that. What I don't understand is how people figure out these codes. I have been using someone elses framework-res.apk as my base, and they use "v4" folders. Eg 'drawable-hdpi-v4' instead of 'drawable-hdpi'. These filename codes in the XML value were generated for this V4 folder, correct? How did they do that?
I do not want to use a V4 folder in my theme if I can avoid it. If I have to, I still have a problem as to how to correctly point to my battery icons. And no I cannot just replace the PNGs because my changing icons have more frames than the stock XML allows.
Any help would be extremely appreciated. Thank you.
Click to expand...
Click to collapse
Well I'm using apktool for decompiling and I'm also trying to add some icons so maybe the help Daneshm90 has given me can help you Apkmanager
EDIT: Lol you didn't even write you were trying to add icons It is seriously stuck to my brain xD
Does apktool let you change the paths for the filenames in XML files, and correctly re-encodes it when you compile it back? I have been trying desperately to get apktool to work for me, but it just refuses. I'll have to try it on another computer or perhaps a VM then.
If apktool does not correctly handle paths, is there any tool that can? From what I've read, its impossible, but there must be a way!
TheLynxy said:
Does apktool let you change the paths for the filenames in XML files, and correctly re-encodes it when you compile it back? I have been trying desperately to get apktool to work for me, but it just refuses. I'll have to try it on another computer or perhaps a VM then.
If apktool does not correctly handle paths, is there any tool that can? From what I've read, its impossible, but there must be a way!
Click to expand...
Click to collapse
What do you mean by "paths in XML files"? Apktool decompiles XMLs fully, so you could do everything that you could do with your own app/sources.
Like the title says, this is how to modify your Notification title drawer on the Captivate with Froyo like Tatuyama's theme's drawer(notification slide) for the i9000. This will tell you how to make it transparent and add a graphic or change the colors. This has been tested on Cog B7, dont think it works on i9000 roms like Shep's. I can help you though on this if you absolutely are dieing to do it. It will just take a little fandanglin and searching but can be done. I ripped apart Shep's rom and found all of Tat's mods, I jsut dont remember them off the top of my head..
I have also attached the drop bars from Tat's theme and another black AOSP bar should you want to use it. I have also included a PSD file to modify to your liking, my APK's for the frameworks I edited below (these include the tat icons already inside), a blank black background bar to use should you want, and other goodies for your modding needs. I have also slapped some screenies below to get an idea of wtf I am even talking about. Also if you use my Frameworks be aware that I am using the battery mod version "I" from that one thread, injected Tat's icons and goodies, and other MISC things.
I will try to do this as simple as possible. I dont linger in the themes area so you are pretty much on your own. I am going to write this tutorial based on Windows O/S and Adobe Photoshop. Attempt this at your own risk. If you biff it up its not my fault. I wrote the directions as I did it, and I am working great with awesome sauce dripping from my phone. I cannot be held responsible if you are below par of the preqs listed. I assume if you are going to attempt it you are competent and comfortable with all things required. However, should you somehow mess up, I do provide some SYA (save your ass) directions below. That being said, Good luck and Mod On!
Prerequisites:
1) ADB Dev Kit and experience using it (push, pull, shell)
2) Photoshop or other photo editing software & experience
3) Basic Windows experience: cut/copy/paste/rename/zipping/moving files. (if you use linux you shouldnt worry as you more than likely are a power user already and can cross apply).
Step 1: We need to download the APK's off the phone and get them ready for editing (or yank them out of the ROM package you download).
1) open a CMD (command prompt) window type:
adb pull /system/framework/twframework-res.apk C:\
adb pull /system/framework/framework-res.apk C:\This will save the files to your root of C:. Should you want to do it elsewhere you can specify or else leave it blank and it will stick the files in your developer kit folder.
2) (OPTIONAL BUT RECOMMENDED! STEP) Navigate to where you saved the files, right click and copy/paste to make a set of backups of these files.
3) Rename the .apk to .zip files. You can also associate your .apk to a program like WinRAR or WinZIP instead. This will open APK Files by default or optional secondary(open with). This makes the whole thing a lot easier as you can open the file(APK) and leave it up, make the edits and drop them directly back into the APK. KEEP FILE STRUCTURE PROPER!
4) Extract the APK files to seperate folders or dig out the below files for editing.
Step 2: Editing the proper files.
1) Navigate to twframework.apk's extracted folder from above or these files you extracted.
2) Find and open sub folder /res/
3) Once in /res/ find and open /drawable-hdpi/
4) Once in /drawable-hdpi/ locate the following files:
- status_bar_background.9.png (actual background of the drawer)
- status_bar_header_background.png (this is the 5 icons across the top of drawer)
- status_bar_close_on.png (this is the dropdown bar at the bottom of drawer)
- quick_panel_list_bg_01.9 (seperator between carrier and application info)
5) Open these files in Photoshop(or another editor)
6) Verify these are set to RGB not Index color mode so you can edit them.
7) Edit the layers to make them transparent. If there are not layers, right click and "create layer from background". You can then edit your layer settings. I set mine to 75% transparency in Photoshop, the actual background to 85% to darken it up a little. This will take some tweaking to get it just perfect for you. Make sure you save them in .png format with the same name they started with and not the PSD or "copy". Also you want non interlaced if it prompts you.
8) Do the same steps for the framework-res.apk.
- status_bar_item_app_background_normal.9.png (not sure if this one is necessary)
- status_bar_item_background_normal.9.png (this is teh notifications)
Step 3: Put it together and upload.
After you update the files, you will need to inject them back ito the APK's where you got them (/res/drawable-hdpi/). You can do this by opening the APK with Winzip/WinRAR/7zip and put them in there or if you extracted the entire contents just zip it all back up. You will need to remove the .zip extension if you went that route. Also, make sure you open it after zipping and verify it maintains the correct structure or you will be doing the recovery shuffle after you reboot. If you see only 1 folder in your zip this is WRONG! You need to see assets, RES, META-INF, and 2 other files in there(manifests and resources). If you see all these then you are ready to rock and roll.
After you get them back together upload them to your device using:
adb push <location of apk you edited>\framework-res.apk /sdcard/
adb push <location of apk you edited>\twframework-res.apk /sdcard/
then in teh same command prompt window (or another, whatever)
adb shell
su
cd sdcard
cp twframework-res.apk /system/framework/twframework-res.apk
cp framework-res.apk /system/framework/framework-res.apk
reboot
It shouldnt take but a second to come back up. You are done.
It may take a little bit of editing of the files to get them to look OK. I spent most of my day today getting mine together. You can use them if you like the "hootie edition" or just edit your own.
SEE POST #6 IF SOMETHING GOES HORRIBLY WRONG!!!!!
Screenies:
http://www.wtfokc.com/sef****/snapshot-1.pnghttp://www.wtfokc.com/sef****/snapshot-2.pnghttp://www.wtfokc.com/sef****/snapshot-3.png
That looks fantastic. I want your notification drop down and all minus the owl of course and text, but can this be done by using metamorph instead of having to adb everything?
awsome write up. Looks pretty simple and I will attempt this when I get home today.
This is an absolutely EXCELLENT tutorial. Props to you. I will be doing this shortly to all my Captivates in the house, 3 in use, plus the 4th one I'm using as a Dev phone.
Hi,
I've followed your instructions. After the files have been pushed up, my phone goes through the usual errors due to the framework change. The problem I'm having is that after I restart my phone, the phone gets past the galaxy s screen, but then it goes black and does not respond. Any suggestions?
smeltn said:
That looks fantastic. I want your notification drop down and all minus the owl of course and text, but can this be done by using metamorph instead of having to adb everything?
Click to expand...
Click to collapse
To be honest I have never used metamorph on the Captivate. On my G1 yes you could acheive that. I googled the metamorph tutorial Junkdruggler did and it looks rather lengthy and involved editing XML files. You can find that info here. Also, the files you would need to do my way with just a blank one are above. Just download the closebars zip and the "blank" zip. Then mod/inject your APK - or hell mine from above- and push it to your device. This is a rather quick ordeal.
thehavock18 said:
awsome write up. Looks pretty simple and I will attempt this when I get home today.
Click to expand...
Click to collapse
miztaken1312 said:
This is an absolutely EXCELLENT tutorial. Props to you. I will be doing this shortly to all my Captivates in the house, 3 in use, plus the 4th one I'm using as a Dev phone.
Click to expand...
Click to collapse
Thanks guys, took me a little while to figure it all out and a lot of framework pushing to get it just right Let me know how it turns out for you! Hell post some screenshots when you are done. I want to see them
gangpe said:
Hi,
I've followed your instructions. After the files have been pushed up, my phone goes through the usual errors due to the framework change. The problem I'm having is that after I restart my phone, the phone gets past the galaxy s screen, but then it goes black and does not respond. Any suggestions?
Click to expand...
Click to collapse
THIS IS HOW TO SAVE YOURSELF
Well, not sure what you mean "usual errors" with framework change? I havent ever had any issues with the framework replacements. I occasionally have then crash if I replace them while phone is on and not in recovery. A reboot fixes this though. Are you using a Cap rom or an I9000? This doesnt work on I9000 roms as thier APK's are slightly different- teh HDPI folder has a v4 at the end (IIRC). I can help you through this though if that's the case..
If it truly is a cap rom, I did experience a similar problem on my phone one time when I pushed the framework.apk. What had happened is I right-clicked the ROOT directory I had placed all the files in and said to zip it. This caused the folder to be INSIDE the zip. So the file structure went like this:
>>ZIP FILE I CREATED>>
--------->>FOLDER ALL FILES WERE IN>>
------------------>>FILE STRUCTURE OF THE ORIGINAL APK>>
Which should have been
>>ZIP FILE I CREATED>>
--------->>FILE STRUCTURE OF ORIGINAL APK>>
To better explain it- If you open the zip you created, do you see the RES folder, META-INF folder, assets folder, and then there will be 2 other files? Or do you see 1 single folder? If you see 1 single folder you zipped it up incorrectly. You will need to go into the folder and select all-> right click-> zip (send to-> compressed folder). This should fix it. If this isnt the case something else went horribly wrong. To fix it we will need to restore the original files you hopefully backed up. If you didnt back up you still arent totally hosed- just redownload the ROM you are running, open it up and navigate to the /system/framework folder and pull out the original frameworks. Then follow these instructions to get them back on the device.
Step 1:
A quick way to get out of this situation is to take the copies rename them back to twframework-res.apk and framework-res.apk (or pull from the original rom package as mentioned above).
Hopefully you have the 2e recovery kernel, as you need it to get back to where you started. If you cant do clockwork, well you may as well odin cause you are a few flashes behind anyway.
K, so first you will need to download the update.zip I have included with this post. This is the clockwork recovery file. You will next need to put your phone in reocvery mode. to do this do:
adb reboot recovery
Step 2:
Next you will need push that file you downloaded to your SD. to do that you need to:
adb push <location of downloaded>\update.zip /sdcard/
Now, once in recovery- tell it to reinstall packages. This may reboot the phone. If it does, tell it to reinstall packages again. This should get you to clockwork recovery.
Step 3:
once you have a green clockwork recovery screen, you will get the chance to SU via ADB SHELL. You can then repeat the pushing of your ORIGINAL fles back to your phone and retry the process.
You could also pull the files you pushed to see what went wrong- but do that first as if you push before they will be overwritten with the original files.
Looking into doing a little custom work but before I do. Like Tat's theme do you need to edit XML files for specific things like the pop ups being black. Or do I just get the naming right and put the proper PNG in the apk.
thehavock18 said:
Looking into doing a little custom work but before I do. Like Tat's theme do you need to edit XML files for specific things like the pop ups being black. Or do I just get the naming right and put the proper PNG in the apk.
Click to expand...
Click to collapse
This is only for the notification drawer and not the actual pop ups. If you want to edit the popups you will need to edit the XML files.
Thanks for the quick response. I might have to dive into all the XML edits.
thehavock18 said:
Thanks for the quick response. I might have to dive into all the XML edits.
Click to expand...
Click to collapse
If you do post a how to thread cause I would like to know how myself
status_bar_background.9.png (actual background of the drawer)
If I ONLY wanted to make the pull-down menu background transparent the above file would be the only one that I need to mod... correct??
jslee1020 said:
status_bar_background.9.png (actual background of the drawer)
If I ONLY wanted to make the pull-down menu background transparent the above file would be the only one that I need to mod... correct??
Click to expand...
Click to collapse
That is correct.
The one problem though is the AT&T (carrier part) at the top is also transparent and you quickly notice it looks a little strange with your items not transparent. I tried to live with it for a little bit but ended up modding the rest too.
malfuncion said:
That is correct.
The one problem though is the AT&T (carrier part) at the top is also transparent and you quickly notice it looks a little strange with your items not transparent. I tried to live with it for a little bit but ended up modding the rest too.
Click to expand...
Click to collapse
quick_panel_list_bg_01.9 (seperator between carrier and application info)
is this the file for the AT&T carrier part??
The quick panel is actually the part that says "Notifications" or "On Going" below the AT&T part. THe AT&T and clear button is part of the actual background peice. So what happens is the AT&T part becomes transparent, while the notification peices are solid. It may not bother you but it bugged the crap out of me. It's personal preference really..
malfuncion said:
The quick panel is actually the part that says "Notifications" or "On Going" below the AT&T part. THe AT&T and clear button is part of the actual background peice. So what happens is the AT&T part becomes transparent, while the notification peices are solid. It may not bother you but it bugged the crap out of me. It's personal preference really..
Click to expand...
Click to collapse
I get it. Well I'll try it out and see... I guess no better way to learn then to experience it first hand Thanks!
I was able to take the Cog Beta 7 framwork and Tat's framwork. I pulled out all the changes from his theme and put them in cog beta 7. I actually did not have to edit any files and was able to apply it.
I had to change a few file names around so all the backgrounds / pop ups applied to the theme. I left DG's background.
I don't want to post it since it is not my own work but if you want to take a look at the framwork and twframwork I can send them PM.
notification bar??
What file is the actual notification bar with the battery/clock/etc... would it be inside twframework-res.apk or framework-res.apk?
EDIT: Just set background transparency to 80% in photoshop and changed the color to black. The transparency seems ok, but it resembles minimalistic theme too much... gonna fiddle with it some more today.
jslee1020 said:
What file is the actual notification bar with the battery/clock/etc... would it be inside twframework-res.apk or framework-res.apk?
Click to expand...
Click to collapse
it is in the framework.apk. The notification bar's file is:
statusbar_background.9.png
This is confirmed. I j ust set mine to a gradient and it actually looks kind of good.
screenie:
http://wtfokc.com/sef****/snapshot-4.png
Hey Malfunction,
Finally got it working past the galaxy S screen, thanks for the info. One last question, then I should be out of your hair. Where can I change the settings for the media scanning icons? Currently, the white default icons are showing, but I'm trying to change that to the black SD card. I'm going to look into it myself too; figured I'd ask though.
Thanks,
gangpe said:
Hey Malfunction,
Finally got it working past the galaxy S screen, thanks for the info. One last question, then I should be out of your hair. Where can I change the settings for the media scanning icons? Currently, the white default icons are showing, but I'm trying to change that to the black SD card. I'm going to look into it myself too; figured I'd ask though.
Thanks,
Click to expand...
Click to collapse
Good deal, glad you got it working. What was the problem?
As for the SDCard- depends which you need. In framework-res there are these 3:
stat_notify_sdcard.png
stat_notify_sdcard_prepare.png
stat_notify_sdcard_usb.png
I had to do some hunting to find out which program was the running process for the Media Scanner. It is "MediaProvider.apk" on your /system/app folder. I edited mine and it now works and has all the Tat icons loaded. Thanks for that heads up I hadnt noticed that little piece before you mentioned it.
I looked at Tat's ROM section and also saw that he has edited these, may consider if you are wanting to mimick his:
DownloadProvider (Market)
MediaProvider (Media Scanner)
Vending (Market)
PackageProvider.apk (Uninstallation Screen)
GoogleQuickSearchBox.apk (Google Search)
ok... status_bar_close_on_cust.9.png
i believe i have followed all the guides i have seen correctly. sorry. i've been stuck on this for almost 4 hours.
i opened the apk in 7zip, exported the image.
removed the 9 from the file name
edited the png in PS
opened draw9patch,
added the full bottom and right side lines.
added the 2 dots i need on top and made the leftside work after eclipse failure
did the eclipse project thing
pulled new status_bar_close_on_cust.9.png from the eclipse created apk
opened framework-res.apk in 7zip again
i tried both..
- deleting the original image and then adding the new to the archive
- drag-drop the new image thus replacing the original
resign the rom's zip
when i install on system i get the bootloop with each loop getting shorter.
i have tried converting framework-res.apk to a zip, resigning it, and then back to an apk
i know this is a much descussed subject on this forum and all the other's i googled looking for the missing step or something i'm doing wrong
i have tried apkmanager, apktools, shorter suggested methods i've seen, and full drawn out methods.
i dont know if i'm messing something up in the png edit, the draw9patch, eclipse, signing or not the apk, or somewhere else.
i've tried pulling a logcat/boot.log from the device but i get some sort of error. i dont know if it's not creating one or i'm trying to pull it from the wrong place.
i'm sure a ton of you guys have had this happen to you. please offer some advice
Do you get an error when importing into eclipse? If so what does it say?
im sorry shoulda clarified that. originally i failed to put the patches on the left side. it failed when trying to make the apk. put thos there and the apk was created. my proplem is with the framework-res.apk i guess.
i put it back in the rom, sign it, and boot-loops.
i guess it has something to do with adding the image to the framework-res.apk. apparently it doesnt like the new image, so to speak. i have tried finding out how to re-build the framework-res.apk, to no avail. hell, i may be using the wrong terminology when searching. at this point, i have no idea.
If i change any images i use metamorph, free from the market. You dont need to sign and flash full apk's, just the files that need changing, a lot quicker and easier.
You could create your ***.9.png as a full size png and remove the 9 patch data, eg. instead of having a 5x32.9png make it 320x32.png(depending on your resolution).
In fact come to think of it ive never seen the "status_bar_close_on_cust.9.png" on my screen, just "status_bar_close_on.9.png".
EDIT: If you've used apktool or other to decompile, crop the the edges by 1 pixel each side, this will remove the 9 patch data, edit your image, then use your draw9 tool, and recompile with eclipse.
You may have been adding another 1 pixel 9patch border to the already existing 9patch border, hope that makes sense.
this is the custom pull down notification bar in gingerfly-1.7.0 based on cm6.1 i believe with some gingerbread looks.
This is how I do it:
1. Extract image from framework-res.akp. You can right click on the framework > 7-zip > open archive and extract the image this way or just extract the whole apk.
2. Edit the image. Open the image in Photoshop and do what you want. Don't worry if you don't have the border. Save the image as a .png file.
3.Add the border. Open draw9patch and add the image. A border for the dots should be created automatically so just do what you need to do and save it as the same file name. It should automatically change the file type to .9.png.
4. Compile the image.9.png. Download the file attached. In the zip, you should see a file called 'xUltimate-d9pc' and a folder called 'Original'. Put the image into the folder 'drawable inside 'res' inside 'Original'. Then open the file named 'xUltimate-d9pc' and wait. When it has finished, there should be a new folder and inside should be the compiled image.
5. Replace the image in framework. Right click framework-res.apk > 7-zip > open archive. Drag the new image into the framework, make sure you have the same file name. You shouldn't need to sign it.
Now you should have a framework-res.apk working with no problem.
I'm not sure if it will work for a custom rom as I use the framework-res.apk from my X10
Hope this helps.
that worked! thanks much!!! the one step i did add to this is to re-sign the rom. i have had nothing but problems anytime i have not signed it after making any changes. it may be an un-needed step, but it worked. thanks again!!!
Can I bump this real quick?
This is my first post here and I'm sorry if I shouldn't bump this thread but my problem is closely related and I hope someone out there knows what I'm doing wrong.
First things first, I'm using the EVO, that's probably important information.
I just flashed Warm Z TwoPointTwo and I love it, except... I really want the vanilla lockscreen. No problem, right? Just rename or delete HtcLockScreen.apk and you're good to go.
That works, and the vanilla lock screen appears upon hot reboot, but the images aren't right; they are all transparent in Warm Z. I have been trying basically all day to get the stock images back into framework-res.apk and nothing has worked; I bootloop every time.
The images are jog_tab_* except that the images in MY framework-res.apk have for example jog_tab_bar_left_end_confirm_gray.png (for all of the left and right end confirm images), whereas the AOSP framework-res.apk has 9patches for all of those.
I've tried deleting the jog_tab_* images in mine and placing in the ones from AOSP, I've tried placing the AOSP images in alongside the ones already in my copy, but nothing works.
I've tried apktool, apk manager, xultimate... I've read about 25 xda threads on this and tried every new suggestion. It bootloops no matter what I do. I think I'm missing something.
I've done the 7zip replacement without re-signing, I've re-signed, I've done xultimate with compression 0, and I've tried creating my own metamorphs. Something about Warm Z is conflicting with the vanilla images, but I'm too inexperienced in themes and the Android OS to know what's up.
Perhaps Warm Z changes definitions elsewhere as to which images are used, or perhaps something else isn't lining up properly with the vanilla lockscreen code. I hope someone out there knows what on earth I'm talking about.
Can someone tell me where I can change the font of the notifications. They come out in black and don't go with my theme, I'd like to change them to white. Thanks
Also if someone can teach me how to get the words under the icons to show up (wifi, bluetooth, gps ... )
You'll be wanting to read how to theme, there are a few threads if you search. twframework-res.apk and framework-res.apk is what you'll be modifying.
Caution swyping! Read at your own risk.
cappysw10 said:
You'll be wanting to read how to theme, there are a few threads if you search. twframework-res.apk and framework-res.apk is what you'll be modifying.
Caution swyping! Read at your own risk.
Click to expand...
Click to collapse
Thanks, I've modified both those files with all the images I need in those two folders. I just need someone to point me to the right xml file that needs editing for these two questions (and if you'd be so kind to point me to where in the xml file even better), thanks
Can anybody help me out... Pleeaase?
Sent from my SAMSUNG-SGH-I897 using XDA App
I think this is what you're looking for
http://forum.xda-developers.com/showthread.php?t=1007221
CuriousTech said:
I think this is what you're looking for
http://forum.xda-developers.com/showthread.php?t=1007221
Click to expand...
Click to collapse
Ok that somewhat helped. I'm looking at the status_bar_expanded.xml file and the last three are already at #ffffffff for white (which is what I want) but my notifications are still coming up in black
I think that's in framework-res.apk/res/layout/status_bar_latest_event_content.xml
It looks like you're trying to change a heavily modified theme back to original. It would be easiest to look at a stock framework and use those values.
CuriousTech said:
I think that's in framework-res.apk/res/layout/status_bar_latest_event_content.xml
It looks like you're trying to change a heavily modified theme back to original. It would be easiest to look at a stock framework and use those values.
Click to expand...
Click to collapse
That should do it!
CuriousTech said:
I think that's in framework-res.apk/res/layout/status_bar_latest_event_content.xml
It looks like you're trying to change a heavily modified theme back to original. It would be easiest to look at a stock framework and use those values.
Click to expand...
Click to collapse
It's actually status_bar_expanded.xml. I need to change the color from ff000000 to ffffffff, that will change it from black to white. So I decompiled framework-res.apk using apk manager. I edited the file, then when I try to compile, I get an error, even if I answer Yes Yes to the two questions and delete the resources.arsc file plust the xml file I edited. It creates an unsigned package but it's much smaller than the original. What am I doing wrong?
I'd prefer to learn how to change the font color to white, however if anybody knows which is the image file for the background I can also just change that to a white or light color that is not transparent like the current one is
What errors are you getting when you compile it? Are you trying to mod a already moded theme? It is most likely .9.png errors that you are getting and they will need to be fixed before it will recompile. Also make sure you are using apktool 1.3.1 as the newer version is known to cause recompiling issues.
The backgrounds are in framework-res
status_bar_item_background_normal.9.png
status_bar_item_app_background_normal.9.png
One is the title "Ongoing..." I think. The associated "pressed" or for when pressed.
The most significant error is the first one. Usually the ones below that are caused by it. Because of the .9.png errors, I always make xml changes to the original unthemed APK, compile it, then pull the compiled xml files out and drop them into the themed one or keep a copy of the drawable-hdpi folder with all the modified .9s (compiled) and drop them into the new APK each time. It's a pain but works.
Thanks guys. framework was previously themed, I'm trying to add my own flavor into the mix. I'll check into the .9.png files when I get home and report back.
A better explanation is that .9.png files that have an opacity set won't decompile so they're corrupt. They'll show up in the error log or show as default (cone, box, sphere) thumbnails when viewing the folder. So when you recompile, those corrupt files will throw errors.
There are a lot of other ways to get around it like keep a copy of all the problem files, and drop the stock images in the apk before decompiling, then after compiling drop the modified ones back in.
If you need to edit them it can get confusing though. They need to remain the same image size. If they're compiled, take the .9 off before modifying in draw9patch so it will add the 1px border back before compiling. Then it's back to the correct size. And since those aren't corrupt, they'll compile fine.