Database Users

[wip] htc/vanilla dialer [UPDATED 05/12/10]

I AM NOT A DEVELOPER
I AM NOT A GRAPHIC ARTIST
I DON'T KNOW IF I DID THIS RIGHT
Version 0.2 -Added CAPS alphebet and improved graphics.
{
"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"
}
Ok, now that that is out of the way, we can proceed. I've been using hoban_eris's Tainted Vanilla rom ( http://forum.xda-developers.com/showthread.php?t=674134 ) and I really like it. One of the pushes over there is to get away from the HTC dialer, I think just because it's ugly. But because I heavily rely on the smart dial feature, I don't want the Vanilla dialer.
This is the standard HTC dialer from the Tainted_Vanilla rom (and I think the Eris_V3 rom) with some minor graphic changes, to make it resemble the Vanilla dialer. All I did was copy the HTCDialer.apk and Phone.apk out, renamed them to .zip, unzipped the files, found and edited the .pngs, pasted the .png's back to the zipped files (I tried re-zipping the extracted files, but couldn't make it work), then renamed the .zip to .apk, then deleted the apk's under system/apps and copied the new ones over (using Android Commander).
THIS IS A WORK IN PROGRESS! I would like to work on it more, but I'm at my real job and need to do my 'real' work. I'm posting it here to see if anyone finds it useful or has suggestions to make it better. Thanks for looking.
To install- MAKE A NANDROID BACKUP OR BACKUP YOUR APK'S -delete these apk's under system/app and copy the new ones over - NO REBOOT NECESSARY
I'm sure there are other ways of doing this, but I don't know the commands.

Testing out!

Hmm didnt work for me.... force close and then the apps dont show up...

andrew8806 said:
Hmm didnt work for me.... force close and then the apps dont show up...
Click to expand...
Click to collapse
Hmm..... I did a Nand restore to try to duplicate your problem. I'm using Android Commander and when I delete the system files, I get FC's, but after I copy the apks over, they work fine.
Sorry about the trouble, I'm still learning.

yeah even when copy and paste... still FC phone...

Re: [wip] htc/vanilla dialer
We'll just have to see if the other devs will weigh in on this.
-------------------------------------
Sent via the XDA Tapatalk App

btw the remove the dot unerneath the 1, just photoshop and color over the dot with the same color as the dialer. dot gone...

New apk's in the first post!

When u delete files do you get an automatic FC?
When I tried copying and pasting them in the /system/app overwriting the original ones I still get FC

Awesome work!
haha, this is awesome work. I love it. I'll include it in my next tainted vanilla release if you don't mind.
By the way, I had no issues getting it installed with your latest apk's using the following method:
$ adb remount
$ adb shell cp /system/app/Phone.apk /system/app/Phone.apk.bak
$ adb push Phone.apk /system/app/Phone.apk
$ adb shell chmod 644 /system/app/Phone.apk
$ adb shell cp /system/app/HtcDialer.apk /system/app/HtcDialer.apk.bak
$ adb push HtcDialer.apk /system/app/HtcDialer.apk
$ adb shell chmod 644 /system/app/HtcDialer.apk

Nice work jadesdan! Works fine for me. I did the following:
1) sudo ./adb remount
2) sudo ./adb push HtcDialer.apk /system/app
3) sudo ./adb push Phone.apk /system/app

Okay, silly question, as I'm still quite the noob here...
Does this work for Froyo?
I've been reading a lot and recently rooted my Eris, installed several different roms. I'm backed up with Ivan's ROM right now and running KaosFroyo... Customized it pretty well. Dialer One however doesn't have access to my Facebook Photos and it's getting annoying! I think it's got an ugly dialer too... If this works with Froyo, it would be a godsend!
EDIT:
also...
How do you do these command lines... I downloaded the SDK stuff and I haven't figured out which program i'm supposed to use to run the commands... I'm lost on the command running side of things.

avantgarde2 said:
Okay, silly question, as I'm still quite the noob here...
Does this work for Froyo?
I've been reading a lot and recently rooted my Eris, installed several different roms. I'm backed up with Ivan's ROM right now and running KaosFroyo... Customized it pretty well. Dialer One however doesn't have access to my Facebook Photos and it's getting annoying! I think it's got an ugly dialer too... If this works with Froyo, it would be a godsend!
EDIT:
also...
How do you do these command lines... I downloaded the SDK stuff and I haven't figured out which program i'm supposed to use to run the commands... I'm lost on the command running side of things.
Click to expand...
Click to collapse
This won't work with KaosFroyo because it requires the HTC Sense overlay. So far, there aren't any froyo ROMS with sense in them.
To run the commands, open a command window (in windows) and then go to where ever you installed the android sdk. You'll need to be in the tools folder. For my setup, I am in c:\android\tools. Once you are in there, you can run your adb commands. Make sure your phone has USB Debugging turned on in the settings.

magnethart said:
This won't work with KaosFroyo because it requires the HTC Sense overlay. So far, there aren't any froyo ROMS with sense in them.
To run the commands, open a command window (in windows) and then go to where ever you installed the android sdk. You'll need to be in the tools folder. For my setup, I am in c:\android\tools. Once you are in there, you can run your adb commands. Make sure your phone has USB Debugging turned on in the settings.
Click to expand...
Click to collapse
Thanks a lot for the information.
the adb command input stuff kept me from trying the Evil Eris rom. Apparently, in order to fix a few things, I had to run a few commands. I didn't have the ability to do that at the time so I passed on trying it out.
I may go back and give it a try now, thanks!

Jadesdan,
Perhaps you can help me. I would like to create my own dialer # buttons and I see you have experience in this area. Can you tell me which png I need to replace and which apk it is in? I don't have an HtcDialer.apk but I do have a Phone.apk. I know how to unzip and zip the apks and I know how to adb push & pull. Just don't know which png to modify. Any help would be greatly appreciated.
I'm running NonSensikal 16.1 ROM

nagahtom said:
Jadesdan,
Perhaps you can help me. I would like to create my own dialer # buttons and I see you have experience in this area. Can you tell me which png I need to replace and which apk it is in? I don't have an HtcDialer.apk but I do have a Phone.apk. I know how to unzip and zip the apks and I know how to adb push & pull. Just don't know which png to modify. Any help would be greatly appreciated.
I'm running NonSensikal 16.1 ROM
Click to expand...
Click to collapse
You could just keep looking at the pics till you see the right one. If your OS allows large thumbnail previews in file browsing that will probably help.

nagahtom said:
Jadesdan,
Perhaps you can help me. I would like to create my own dialer # buttons and I see you have experience in this area. Can you tell me which png I need to replace and which apk it is in? I don't have an HtcDialer.apk but I do have a Phone.apk. I know how to unzip and zip the apks and I know how to adb push & pull. Just don't know which png to modify. Any help would be greatly appreciated.
I'm running NonSensikal 16.1 ROM
Click to expand...
Click to collapse
I think they are dial_num_1, 2, etc located in Phone.apk\res\drawable-mdpi-finger

Thanks for your responses guys! Appreciate your help!

nagahtom said:
Jadesdan,
Perhaps you can help me. I would like to create my own dialer # buttons and I see you have experience in this area. Can you tell me which png I need to replace and which apk it is in? I don't have an HtcDialer.apk but I do have a Phone.apk. I know how to unzip and zip the apks and I know how to adb push & pull. Just don't know which png to modify. Any help would be greatly appreciated.
I'm running NonSensikal 16.1 ROM
Click to expand...
Click to collapse
Dialer will be in Contacts.apk res/drawable-mdpi-finger
Phone.apk has the images you see when you are on a phone call. Contacts.apk has the dialer images.

Just so you all know, I've updated this to a Metamorph that does the same thing. It also contains all the pngs and the file pates. You can find it here -> http://forum.xda-developers.com/showthread.php?t=742609

GPS fixed on Captivate. Combination of 2 methods + detailed steps

This is how I fixed my GPS issue on Captivate. It would not lock on, not even after 5 minutes of me standing still.
Found this thread - http://forum.xda-developers.com/showthread.php?t=786486
Was trying to follow the steps and realized I wished it was spelled out more. So this is what I am doing in this thread, to make it easier for everyone else, if they decide to try. After an hour of googling commands and trial and error - its done, and my phone's GPS locks on under 10 seconds.
I downloaded that zip file. Then installed Droid Explorer on my PC. I already had USB drivers installed for the Galaxy S, so during install I unchecked it. When I opened Droid Explorer I realized I cant write to the /system/bin and the other two. The Write permissions for the system folder were not set, so when I dragged files over - they wouldnt copy over to my phone. It would kinda "refresh" but files wouldnt show up in there.
Easy way seemed to be to buy and install Root Explorer on my phone from the market. And click on Mount R/W for the system folder. However I am waiting for credit card replacement in the mail and was so fed up with GPS that I wanted to do it NOW, and was not gonna stop until its done. Today.
So the other way to make /system/bin , /system/etc and /system/lib folders writable was thru command prompt.
First off my phone has Cog 5.5 on it so it is rooted.
1. set phone in usb debugging mode and connect to pc
2. navigated to my sdk/tools directory on my hard drive. In my case it looked like this
Code:
cd c:\sdk\tools
<hit enter> but it depends on where you downloaded and unzipped your android SDK folder
3. typed
Code:
adb shell
<hit enter> then
Code:
su
<hit enter> to give me root access to the phone.
{
"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"
}
The phone will ask if you want to grant permissions to unknown, hit Yes.
4. Now we need to set system as writable. While googling commands it seemed that the command should be
Code:
mount -o rw,remount /system
But in my case that didnt work, telling me location was invalid. I obviously was missing something. Duh! correct location! So -
type
Code:
mount
<hit enter> It will list the root directory. We need t locate exactly where system is on the phone. In my case it was /dev/block/st19 /system
So the command should be then
Code:
mount -o rw,remount /dev/block/st19 /system
<enter>
then
Code:
chmod 777 /system
<enter>
Code:
chmod 777 /system/bin
<enter>
Code:
chmod 777 /system/etc
<enter>
Code:
chmod 777 /system/lib
<enter>
Code:
exit
<enter>
and one more time
Code:
exit
<enter>
The folders are now writable.
5. Opened Droid Explorer, copied files over, lbstestmode launch app was already installed on my phone. So it didnt have to do that step, as it was in j101399j's thread
6. Rebooted the phone, opened lbstestmode, deleted GPS data.
Started testing. It wouldnt lock. Went to Get Position Test in lbstestmode app. It would see the sattellites, 8 of them but wouldnt give me my lat/long! So I remembered this post - http://forum.xda-developers.com/showpost.php?p=9150551&postcount=7862 by cnewsgrp
and changed
3. In the LBSTestMode menu change “Operation Mode” to MS Based
4. In the LBSTestMode menu, find “SUPL/CP Settings” and change the SERVER & PORT to supl.google.com and port 7276 (DO NOT use www. in front of supl)
Click to expand...
Click to collapse
Didnt even have to reboot. Went to Get Position Test again and it saw like 8 or 9 satellites and had * next to 4 of them in 10 seconds. Give me my lat/long with precision. Wanted to mention that I tried cnewsgrp 's method a week ago, just by itself, and it gave me no results.
So to summarize. Combination of those 2 fixes worked wonders for me. And the Captivates GPS issue is definitely not hardware based.
I do have a question however,lol, how do I revoke write settings for my system folder, and go back to how it was? Would that be
Code:
chmod 755
?
I hope these detailed instructions help someone.

And this is why people who don't know what they are doing shouldn't be poking around with root. chmod'ing everything 777 is only one step removed from just running rm -rf * and deleting everything.
There has to be a much easier way of doing things.
And you can "revoke" the settings by remembering what each and every file in those directories had their permissions set to and setting them back with chmod. I guarantee they were not all 755.

chmod 777???
NO THANK YOU!!

zerojay said:
And this is why people who don't know what they are doing shouldn't be poking around with root. chmod'ing everything 777 is only one step removed from just running rm -rf * and deleting everything.
There has to be a much easier way of doing things.
And you can "revoke" the settings by remembering what each and every file in those directories had their permissions set to and setting them back with chmod. I guarantee they were not all 755.
Click to expand...
Click to collapse
it didnt change file settings inside folders, just folder setting

also this is where I got chmod 777 from - http://android-tricks.blogspot.com/2009/01/mount-filesystem-read-write.html and http://karuppuswamy.com/wordpress/2009/04/25/mounting-system-partition-in-read-write-mode-in-android/
was obviously for android.

There's a reason why 777 permissions weren't there to begin with
also I love how there are currently 7 views and 6 replies. which means almost everyone is going - Aaah!!!!! NOOO!!! Must post and warn her!!!

my phone's GPS locks on under 10 seconds
Click to expand...
Click to collapse
This is meaningless. A quick lock does not mean the GPS is "fixed", I wish people would stop making misleading threads

sinoth said:
This is meaningless. A quick lock does not mean the GPS is "fixed", I wish people would stop making misleading threads
Click to expand...
Click to collapse
ok, misleading threads? it was combination of two threads that I linked to, with explanation. Obviously it works for me, and stuff in other threads worked for other people. Enough already with GPS thread policing, hate and trolling.
Yes there is a
"a reason why 777 permissions weren't there to begin with"
Click to expand...
Click to collapse
It is a system folder after all. Same as Windows warns you not to modify windows folder contents. People wrote to and modified android system folder for years. Your point is non existent.
And regarding chmod 777 - look at my screenshot, file permissions arent changed. what was changed was ability to write to those folders. Also Root Explorer function to mount system as R/W obviously does the same thing. Why is it there, if it is soooo dangerous
Went and did chmod 755 on the folders I 777'd. Everything is back to the way it was and works fine.

bmvik said:
ok, misleading threads? it was combination of two threads that I linked to, with explanation. Obviously it works for me, and stuff in other threads worked for other people. Enough already with GPS thread policing, hate and trolling.
And regarding chmod 777 - look at my screenshot, file permissions arent changed. what was changed was ability to write to those folders. Also Root Explorer function to mount system as R/W obviously does the same thing. Why is it there, if it is soooo dangerous
Went and did chmod 755 on the folders I 777'd. Everything is back to the way it was and works fine.
Click to expand...
Click to collapse
I do agree that it takes a while to get a lock...but the BIG concern here is tracking. Hows the accuracy, the tracking? Does it stay locked while driving? That is the REAL problem here...

kletiz said:
I do agree that it takes a while to get a lock...but the BIG concern here is tracking. Hows the accuracy, the tracking? Does it stay locked while driving? That is the REAL problem here...
Click to expand...
Click to collapse
I agree. I'll let you know regarding tracking as I test. Before however, not only it would take 5 min to lock on, but would lose me while I was driving, constantly. Accuracy was jumping to 200 meters or so. So instant lock was a good sign to me.

bmvik said:
Yes there is a It is a system folder after all. Same as Windows warns you not to modify windows folder contents. People wrote to and modified android system folder for years. Your point is non existent.
Click to expand...
Click to collapse
Wow, the cluelessness.

kletiz said:
I do agree that it takes a while to get a lock...but the BIG concern here is tracking. Hows the accuracy, the tracking? Does it stay locked while driving? That is the REAL problem here...
Click to expand...
Click to collapse
For me it does. I have been using GPS with any issues for past few days. And to give credit what ever steps I have posted have been around for a long time just search for "Vibrant GPS fix". The only reason I needed to do that was my GPS stopped working after applying Cog 2.4 ROM with is Vibrant ROM. I applied Vibrant GPS fix and voila GPS now works!!
I must stress here that I have had no GPS issues with any of the Captivate ROMS or Stock ROMS. I usually get lock in 10 - 30 seconds and it tracks well for me. I used GPS test and I an see around 8-9 satellites with S/N ratio of 35 and accuracy of 16.5 regularly.

Oh the boogeyman
I also would like to add, had anything went wrong during these steps - I would've just reflashed my phone to another Cognition ROM and started from scratch. Voila!

bmvik said:
Same as Windows warns you not to modify windows folder contents. People wrote to and modified android system folder for years. Your point is non existent.
Click to expand...
Click to collapse
bmvik said:
Also Root Explorer function to mount system as R/W obviously does the same thing. Why is it there, if it is soooo dangerous
Click to expand...
Click to collapse
It's clear you don't understand the issue. It's not about editing the file system. Heck we all do that if we are in the dev section . It's about having /system permanently open to editing by anything. It's just problematic from a security point of view.
If I run an unverified app not from the android market, I sleep soundly knowing that it stays within its borders (unless I give it superuser permissions). I like to have the choice of saying, root explorer I trust you, you have SU permissions. Okay I trust who made this framework-res.apk, I can add this to /system/framework. I don't want /system permanently open.

installing unverified app and installing fishy framework on phone that is the problem .. not the permissions , I ran my (previous) android phone for a long time with random folders / files at 777 absolutely no damage can nor did happen from doing this alone
thishread is being filled wit los of misinformation while its sole purpose was to 'help the community with a ( well needed it seems ) gps fix
I dont know why everyone is bashing the OP I dont need the fix but its nice to know there is one ..
bashing is all I saw in here nbody told the OP something like ' why wouldnt it work with 644 nor any other suggestions no everybody started bashing .. I m like wow .
/end rant

DAGr8 said:
installing unverified app and installing fishy framework on phone that is the problem .. not the permissions , I ran my (previous) android phone for a long time with random folders / files at 777 absolutely no damage can nor did happen from doing this alone
thishread is being filled wit los of misinformation while its sole purpose was to 'help the community with a ( well needed it seems ) gps fix
I dont know why everyone is bashing the OP I dont need the fix but its nice to know there is one ..
bashing is all I saw in here nbody told the OP something like ' why wouldnt it work with 644 nor any other suggestions no everybody started bashing .. I m like wow .
/end rant
Click to expand...
Click to collapse
It would help if OP can take a snapshot of before and after to list what files had changed. That would help pinpoint what is being used by the GPS that needs more permissions.

DAGr8 said:
installing unverified app and installing fishy framework on phone that is the problem .. not the permissions , I ran my (previous) android phone for a long time with random folders / files at 777 absolutely no damage can nor did happen from doing this alone
thishread is being filled wit los of misinformation while its sole purpose was to 'help the community with a ( well needed it seems ) gps fix
I dont know why everyone is bashing the OP I dont need the fix but its nice to know there is one ..
bashing is all I saw in here nbody told the OP something like ' why wouldnt it work with 644 nor any other suggestions no everybody started bashing .. I m like wow .
/end rant
Click to expand...
Click to collapse
Thank you. I mean, really.
fatttire said:
It's clear you don't understand the issue. It's not about editing the file system. Heck we all do that if we are in the dev section . It's about having /system permanently open to editing by anything. It's just problematic from a security point of view.
If I run an unverified app not from the android market, I sleep soundly knowing that it stays within its borders (unless I give it superuser permissions). I like to have the choice of saying, root explorer I trust you, you have SU permissions. Okay I trust who made this framework-res.apk, I can add this to /system/framework. I don't want /system permanently open.
Click to expand...
Click to collapse
Let me spell it out for you. In this thread http://forum.xda-developers.com/showthread.php?t=786486 OP suggests
2. Using root explorer or droid explorer, copy the files from each folder.
Click to expand...
Click to collapse
For root explorer to be able to write to system folder it would HAVE to change that folders permissions. I didnt have the app, so changed them manually, then used droid explorer. Then changed permissions right back to 755.
cnewsgrp said:
It would help if OP can take a snapshot of before and after to list what files had changed. That would help pinpoint what is being used by the GPS that needs more permissions.
Click to expand...
Click to collapse
Well I just copied the files from the zip file I linked to in the OP, over to the system/bin, /etc and /lib I dont know how screenshot would help

aaaand uhhhhhh can you non-haters vote the thread up, plz? some 5 haters hit 1 star

OP is trying to help. Geez, cut some.slack.
Sent from my SAMSUNG-SGH-I897 using XDA App

skinien said:
OP is trying to help. Geez, cut some.slack.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Lol stop using the samsung keyboard the period is in the wrong spot.
btw op can you plz post some tracking results with mytracks or something. Locking on is not the problem, tracking is.
If you do ill vote this thread up

[Q] Changing the "Verizon Wireless" text

Can anyone please help? I have been going through multiple threads across many forums and still can not find out how to change the color of the "Verizon Wireless" message in the notification bar. I have read the one for Droid but no info for Droid X. I know how to change what it says but just want to change it to a blue or white. Any help will be greatly appreciated. Thank you.

Never mind about the pm I sent you, I figured it out. I would like to know how to change the color too though.
EDIT:
I found this, it may be useful
http://www.droidforums.net/forum/thebowers/27622-text-color-change-complete-how-do.html

I did read this but does it apply to Droid only or can the same be done for Droid X?

I'm not sure. I haven't tried it. I guess the only way to find out is to make a nandroid of your phone and start experimenting

MAKE A BACKUP
Here is the guide:
1. Go into root explorer navigate to system/framework
2. Hit mount r/w on top then hold and copy framework-res.apk
3. Paste framework-res.apk on root of sdcard
4. Mount the phone to your pc AND move framework-res.apk to desktop
5. Right click framework-res.apk on desktop hit 7zip then hit open archive
6. Navigate to res/xml/ find eri.xml and drag it to your desktop
KEEP ARCHIVE OPEN YOU WILL BE BACK
7. Right click eri.xml on desktop open with HxD
8. Now look to the right side of the screen and find "Verizon Wireless"
9. Highlight the whole word "Verizon wireless"
10. While highlighted type your new name..16 LETTERS MAX
(if any "Verizon wireless" is left just keep hitting space bar after new name)
11. Now save your new eri.xml and drag it back into archive
12. Close the archive
13. Put framework-res.apk back on root of sdcard
14. Now on your phone open Android Terminal Emulator on phone and type
Su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/framework-res.apk /system/framework
reboot
15. Your done.

spaciorek said:
MAKE A BACKUP
Here is the guide:
1. Go into root explorer navigate to system/framework
2. Hit mount r/w on top then hold and copy framework-res.apk
3. Paste framework-res.apk on root of sdcard
4. Mount the phone to your pc AND move framework-res.apk to desktop
5. Right click framework-res.apk on desktop hit 7zip then hit open archive
6. Navigate to res/xml/ find eri.xml and drag it to your desktop
KEEP ARCHIVE OPEN YOU WILL BE BACK
7. Right click eri.xml on desktop open with HxD
8. Now look to the right side of the screen and find "Verizon Wireless"
9. Highlight the whole word "Verizon wireless"
10. While highlighted type your new name..16 LETTERS MAX
(if any "Verizon wireless" is left just keep hitting space bar after new name)
11. Now save your new eri.xml and drag it back into archive
12. Close the archive
13. Put framework-res.apk back on root of sdcard
14. Now on your phone open Android Terminal Emulator on phone and type
Su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/framework-res.apk /system/framework
reboot
15. Your done.
Click to expand...
Click to collapse
He wants to know (as do I) how to change the color of the text, not how to change what the text displays, he stated he already knows how to change the displayed text.
I know you have to modify an .xml file, I just don't know which one and what part to modify to change the color.

Thanks for the assist but bouchigo is correct I am looking to change the text color. Already changed words.
Sent from my DROIDX using XDA App

I finally figured it out:
{
"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"
}
Just follow this link.....read it a few times and you will get it:
http://androidforums.com/droid-all-things-root/49813-guide-change-notification-clock-pull-down-text-colors.html

Thanks I did read this one. Can you pull the 3 files from and do it direct without adb by just using a copy of original files then replacing with 7zip? Not to proficient with adb.
Thank you by the way good job and you work is much appreciated.
Sent from my DROIDX using XDA App
Sent from my DROIDX using XDA App

scott021467 said:
Thanks I did read this one. Can you pull the 3 files from and do it direct without adb by just using a copy of original files then replacing with 7zip? Not to proficient with adb.
Thank you by the way good job and you work is much appreciated.
Sent from my DROIDX using XDA App
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
The three .xml files modify the drop down menu on the status bar and other status bar elements.
If you want to modify the network tag, clock or date, you have to modify services.jar
Do this:
1 Make a folder called "framework" on your desktop because you will put services.jar inside there.
2. Take your services.jar file from inside your framework folder from the ROM you have installed on your phone (if you are using a theme, take the services.jar from your theme, or you can pull it from your phone as the guide in the link i posted earlier states to do).
3. Now right click on that folder and "Add to Archive" with winzip.....make sure you select Archive format to ZIP not RAR......you can name the zip file to be "theme" or whatever you want to call it.
4. Now put the newly zipped file in the root of C:\ drive. Make sure colorChagev3.jar is in C:\ too.
5. Now, using PowerCmd cd yourself to C:\ since that's where all your files are at and type this to change the "Verizon Wireless" color (it will be blue in this case; blue = 0000FF, but entered reversed FF0000 the last FF is just the degree of transparency):
java -Xmx512M -jar colorChangev3.jar theme.zip network=FF0000FF
6. If you want to change the date color, then enter this:
java -Xmx512M -jar colorChangev3.jar theme.zip date=FF0000FF
7. If you want to change the clock color, then enter this:
java -Xmx512M -jar colorChangev3.jar theme.zip clock=FF0000FF
8. Or you can do it all at once:
java -Xmx512M -jar colorChangev3.jar theme.zip network=FF0000FF date=FF0000FF clock=FF0000FF
9. After the color change is complete message, there will be a new zip created in C:\ called theme-new.zip. You will take services.jar from there and adb push it back to your phone OR do step 10:
Code:
adb remount
adb push services.jar /system/framework/
adb shell reboot
10. Or you can simply replace the services.jar in the theme you are using with the new services.jar and re-flash the theme to your phone.
If you want to change the .xml files then you will need to extract the framework-res.apk and make changes to it according to the guide then just replace it in the same manner as the services.jar.
Mine looks like this right now....I will be removing the clock from the status bar, I don't like it there since it's redundant in my case because I have BW to show me the time:

Thank you very much, I will try this as soon as I get home tonight and let you know how it turns out.

Cool, hopefully it all works out for you.

Unable to access jarfile colorChangev3.jar....grrrr....just do not understand this.

scott021467 said:
Unable to access jarfile colorChangev3.jar....grrrr....just do not understand this.
Click to expand...
Click to collapse
Are you using PowerCmd or windows command prompt? Try using PowerCmd.
You put all the files in C root and renamed colorChangev3 correctly?
EDIT:
I think you don't have java installed. Go here and get it, then try again:
http://www.java.com/en/download/inc/windows_upgrade_xpi.jsp

YES......Completed and now I am the proud owner of a properly colored notification screen.......I owe it all to the helpful guidance of bouchiga...thank you sooo very much...since I cannot post pics here for some reason I will pm you a link.

bouchigo said:
I finally figured it out:
Just follow this link.....read it a few times and you will get it:
http://androidforums.com/droid-all-things-root/49813-guide-change-notification-clock-pull-down-text-colors.html
Click to expand...
Click to collapse
this is sick!

scott021467 said:
YES......Completed and now I am the proud owner of a properly colored notification screen.......I owe it all to the helpful guidance of bouchigo...thank you sooo very much...since I cannot post pics here for some reason I will pm you a link.
Click to expand...
Click to collapse
Sweet, you finally got it working.....it looks real nice too!
Persistence pays off in the end
Sent from my DROIDX using XDA App

Thanks to you and happy you like the finished product. Thanks for all the help, Happy Thanksgiving.
Sent from my DROIDX using XDA App

scott021467 said:
YES......Completed and now I am the proud owner of a properly colored notification screen.......I owe it all to the helpful guidance of bouchiga...thank you sooo very much...since I cannot post pics here for some reason I will pm you a link.
Click to expand...
Click to collapse
hello, how did you fix "Unable to access jarfile colorChangev3.jar" error? i get it too and dont know what to do ..
i have java instaled and using PowerCmd still the same
thanks!
i fix that

I was not renaming the .jar.zip file correctly. Once changed it's icon should change to a java icon from there you are good to go.
Sent from my DROIDX using XDA App

Editing build.prop tutorial

I haven't seen a guide for this yet...but if there is mods please delete this.
Your build.prop is what tells android what your phone is. A Nexus S a Motorola Droid, or a Samsung Epic. Knowing how to change it can be EXTREMELY useful from tweaking your phone to faking it to run netflix.
There's 3 ways to modify your build.prop. You must have root (and busybox) for all of them, but I beleive if you want to you can unroot and it will stick.
ADB
Adb is a part of the android sdk, and is more for advanced users then novices. You can modify your build.prop by using adb and pulling it, editing it on your computer, and putting it back. Not the simplest way.
Type in adb:
Code:
adb pull /system/build.prop C:\Users\user\Desktop
Always replace "user" with your windows username
You should see a file named "build.prop" on your desktop. Open it with WORDPAD, not notepad. Change what you want. When your done, type this:
Code:
adb push C:\Users\user\Desktop\build.prop /sdcard/build.prop
This will put the build.prop on your sd card, since we cannot directly push to /system
Code:
adb shell
This should give you a shell. A shell is where you can run commands. After you have a shell, type:
Code:
su
mount -o remount,rw none /system
busybox cp /sdcard/build.prop /system/build.prop
mount -o remount,ro none /system
You have successfully changed your build.prop!
File Expert (or other free file managers) and text edit
This involves two apps, File Expert (or similar) and Text Edit. They can be found on the market here: File Expert and Text Edit
After you install these two apps, open File Expert. Click the menu button (the one on the phone), more, and Settings. Click on File Explorer Settings and click Root Explorer. It should request root, allow it. Press back twice to go back to your sd card. Then press back twice again. Click on /system. Press the menu button, more, and click mount. Select "Mount as Read Write". Now long click on build.prop and select File Operations. Click permission. A menu should pop-up, check the boxes so it looks like this
Code:
X X []
X X []
X X []
and click apply. Now, click on build.prop and it should say open as. Click text, then Text Edit.
Feel free to edit as you please! Once your done, click menu, then save. Then close the application. Don't forget to go to file expert and unmount system as rw, do this by going to the system folder and clicking menu, more, Mount, Mount as Read Only. Your done!
The easy way
Go buy an app. Really, some are worth the trouble. Two apps that will help edit your build.prop are Absolute System and Root Explorer
Thats about it. Any suggestions on how to edit, I'll add in this op. So be sure to leave them!

thanks for this! I have it bookmarked but where can i find common build prop edits?

You can also use ROM Toolbox to edit some items on the build.prop

For version 2 above, I use ES File Explorer and its built in ES Text Editor. One app instead of two. Same effect.
Sent from my Samsung Legendary 4G, a Universe UTES Phone, running "two. two"

tq, nice info
Sent from my SCH-I500 using XDA App

awesome post. comes in handy

Is it not just possible to take the zip from a custom rom and modify it with Notepad++?

zanderman112 said:
For version 2 above, I use ES File Explorer and its built in ES Text Editor. One app instead of two. Same effect.
Sent from my Samsung Legendary 4G, a Universe UTES Phone, running "two. two"
Click to expand...
Click to collapse
I came to say the exact same thing.
Sent from my SPH-D700 using Tapatalk

You may want to add quotes for the desktop directory in case their user name is "John Smith"
Sent from my SPH-D700 using Tapatalk

ugothakd said:
File Expert (or other free file managers) and text edit
This involves two apps, File Expert (or similar) and Text Edit. They can be found on the market here: File Expert and Text Edit
After you install these two apps, open File Expert. Click the menu button (the one on the phone), more, and Settings. Click on File Explorer Settings and click Root Explorer. It should request root, allow it. Press back twice to go back to your sd card. Then press back twice again. Click on /system. Press the menu button, more, and click mount. Select "Mount as Read Write". Now long click on build.prop and select File Operations. Click permission. A menu should pop-up, check the boxes so it looks like this
Code:
X X []
X X []
X X []
and click apply. Now, click on build.prop and it should say open as. Click text, then Text Edit.
Click to expand...
Click to collapse
If anyone has any problems, MAKE SURE you're using TEXT EDIT. That solved my problem! =D

Actually Z, root explorer will let you edit the text.
Sent from a phone with kNOw CIQ

So I got the editing part down, how about potential options. Like what identifies the device to the market? I wanna be able to increase my app compatibility and I'm wondering if changing from an ei22 fingerprint to something else may help?
sent from the other woman

bryanfritz1 said:
So I got the editing part down, how about potential options. Like what identifies the device to the market? I wanna be able to increase my app compatibility and I'm wondering if changing from an ei22 fingerprint to something else may help?
sent from the other woman
Click to expand...
Click to collapse
I'm not sure but I think it's your build I.d. Just woke up and still learning.
Via OG Epic 4g Cm9 & NYGiants 2012 Champions!!!!!

So here is my build.prop
{
"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"
}
. The part about ei22 and test keys can that be updated to something different (newer) and would that play a part in the market apps not being compatible? Thx guys just trying to understand how it all works together.
sent from the other woman

Hi!I have xperia mini with ICS.My device wake up if I push the volume button(unlock).I edit the build.prop.I writing this line:ro.config.hwfeature_wakeupkey = 0.
But this not working just with radio.Its not good with Proplayer.
Any solution?

My huawei 8650 sonic freeze after i do your steps because i forgot to install the busybox any idea what i can do ?
sry for my english...

Thank you so much!!!!!!:victory::victory::victory: o/

Nice OP!

Pure Awesomeness
Thanks a million! :good:

hey guys i need a big help whit that i was tweaking the build.prop of my pantech flex is already rooted but it get stock into the logo of att i mean it got brick so i decide to modifited the build.prop to the original i mean just erasing the lines i added to it but i was just fine doing the abd pull and the push to the sdcard build.prop but i get failed doing (su
mount -o remount,rw none /system
busybox cp /sdcard/build.prop /system/build.prop
mount -o remount,ro none /system) in the cmd it stay doing anything

[Boot Animation]Droid Prime

Disclaimer:I am not responsible if you break,brick,hump,throw against wall or any other action you do to your phone. By using this bootanimation you agree anything that happens is your own noobtastic fault. Any attempts at blaming me for anything other than this being fantastic will result in you being pointed and laughed at.
If you are using BACKSIDE/IHO or have already installed the script dont I REPEAT DONT run the script again. Doing so makes multiple instances of the commands and will stop the bootsound from playing. If you run the script more than once you will have to delete somethings to get it to work. SO be warned DO NOT RUN THE SCRIPT IF YOU HAVE ALREADY OR ARE USING BACKSIDEIHO ROM
Ran across this the other day and have been waiting patiently ever since. I posted about it already now its ready for the wild.
I did not create this. I have only edited the desc.txt so it will run on our phones. All credit goes to BootAnimator on RootzWiki. Again I did not create this so please thank the creator BootAnimator on RootzWiki
.
{
"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"
}
Unzip the file then follow the instructions below.
http://www.mediafire.com/?7tmnb3u7axbu2u0
Root Explorer method:
1. Rename your bootanimation to bootanimation (if not already named this)
2. Put it on your SD card
3. Open Root Explorer and copy bootanimation.zip to /system/media. This will replace the existing boot animation
4. Reboot your phone
ADB method:
1. Make sure you have downloaded android sdk
2. Put android sdk in C:\
3. Set the directory of command prompt to C:\android-sdk-windows\platform-tools. Click here for a video tutorial.
4. Rename your boot animation to bootanimation and put it in C:\android-sdk-windows\platform-tools
5. Open cmd
6. Type in order:
-adb remount
-adb push bootanimation.zip /system/media/bootanimation.zip
-adb reboot
Click to expand...
Click to collapse
You can also preview your bootanimation before rebooting.
In adb type adb shell bootanimation.
To add the sound.
If you are running BACKSIDE or have already installed the script all you have to do is using root explorer copy the file "android_audio.mp3" from the zip you downloaded to /system/media.
Then reboot and you should have awesome bootsound.
If you have never run the script and are not using BACKSIDE then follow the instructions below.
Originally Posted by hockeyfamily737
0. It's recommended to do a nandroid backup first!
1. Download the "bootsnd.sh" file and put it on the root of your sd card.
2. Using root explorer copy the file "android_audio.mp3" from the zip you downloaded to /system/media
3. Open Terminal Emulator and type the following commands using the stock keyboard. Press enter after each line:
su
cd /sdcard
sh
sh bootsnd.sh
reboot
4. As the device boots up you will hear the transformers sound bite sound. You are now free to replace the android_audio.mp3 file in /system/media with any .mp3 file you like as long as you rename it to "android_audio.mp3"
5. DO NOT ATTEMPT TO OUTSMART THESE DIRECTIONS OR YOU WILL BE RESTORING YOUR NANDROID BACKUP!
6. Enjoy
Click to expand...
Click to collapse
http://dl.dropbox.com/u/10373328/bootsnd.sh
If for some ungodly reason you ignored the above warning and installed the script again..read below.
Here is how to fix it.
Make sure you are mounting in r/w mode on each of these steps.
Using a app like root explorer, goto /system/bin and delete the file bootsound.
Back out to /system now open build.prop in text editor mode, look for this text.
Code:
ro.config.play.bootsound=1
Delete it from the build.prop and save and exit.
This is optional but recommened.
Reboot phone.
Verify no sound is playing.
Now run the script again and reboot.
You should have a boot sound again.
Click to expand...
Click to collapse

Sent from LGE XDA phone

eollie said:
Disclaimer:I am not responsible if you break,brick,hump,throw against wall or any other action you do to your phone. By using this bootanimation you agree anything that happens is your own noobtastic fault. Any attempts at blaming me for anything other than this being fantastic will result in you being pointed and laughed at.
If you are using BACKSIDE/IHO or have already installed the script dont I REPEAT DONT run the script again. Doing so makes multiple instances of the commands and will stop the bootsound from playing. If you run the script more than once you will have to delete somethings to get it to work. SO be warned DO NOT RUN THE SCRIPT IF YOU HAVE ALREADY OR ARE USING BACKSIDEIHO ROM
Ran across this the other day and have been waiting patiently ever since. I posted about it already now its ready for the wild.
I did not create this. I have only edited the desc.txt so it will run on our phones. All credit goes to BootAnimator on RootzWikiAgain I did not create this so please thank the creator BootAnimator on RootzWiki
Unzip the file then follow the instructions below.
http://www.mediafire.com/?7tmnb3u7axbu2u0
You can also preview your bootanimation before rebooting.
In adb type adb shell bootanimation.
To add the sound.
If you are running BACKSIDE or have already installed the script all you have to do is using root explorer copy the file "android_audio.mp3" from the zip you downloaded to /system/media.
Then reboot and you should have awesome bootsound.
If you have never run the script and are not using BACKSIDE then follow the instructions below.
http://dl.dropbox.com/u/10373328/bootsnd.sh
If for some ungodly reason you ignored the above warning and installed the script again..read below.
Click to expand...
Click to collapse
Umm... It never work... I tried this for 7 times...
Sent from LGE XDA phone

Do this plug your phone in via the usb and open adb window.
Type "adb shell bootanimation".
It will say "mmap failed:errno 19 no such device" and play the animation on your phone screen.
If it says anything else post it here and I can figure out what the problem is.

Boot animation works. But sound doesn't. Used root explorer and changed the permissions also.
Sent from my LG-P500 using Tapatalk

lekhwani said:
Boot animation works. But sound doesn't. Used root explorer and changed the permissions also.
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
+1 Same... 40 times I tried ur method...
Sent from LGE XDA phone

lekhwani said:
Boot animation works. But sound doesn't. Used root explorer and changed the permissions also.
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
dax4182 said:
+1 Same... 40 times I tried ur method...
Sent from LGE XDA phone
Click to expand...
Click to collapse
Im sorry its probably your phone. I see dax is using a P500. Some phones just wont play the boot sound.Ive seen it happen on the V no reason just refuses to play.

eollie said:
Im sorry its probably your phone. I see dax is using a P500. Some phones just wont play the boot sound.Ive seen it happen on the V no reason just refuses to play.
Click to expand...
Click to collapse
But on the official ginger is able to play the bootsound as is original manfacturered...
Sent from LGE XDA phone

DaxElectro said:
But on the official ginger is able to play the bootsound as is original manfacturered...
Sent from LGE XDA phone
Click to expand...
Click to collapse
Where is the bootsound located on the official gingerbread release?
I only say some phone just wont play it because Ive tried to help several people on android central get it working and their phone just wont play it no matter what we did. Im sure somebody with more knowledge than I have on this would be able to figure it out, however Im not sure why it wont work. I was told that on CM rom the kernel was trimmed and bootsound was removed that is why you have to run the script I link to.