4G icon - G2 and Desire Z Themes and Apps

is there any themes that can put the "4G" icon instead of the "H". but can be applied thru theme chooser? im not good at editing the filesystem.
HTC Vision (G2)
Android 2.3.5
CM7 Nightly #182

http://forum.xda-developers.com/showthread.php?t=993824&highlight=4g+icon

thats not helping, ive commented on it and i want the system theme. not cyanbread, etc. im the last comment on it!
HTC Vision (G2)
Android 2.3.5
CM7 Nightly #179

the 4G icons are already in the file system of CM7.
The easiest (I guess) way to do it is to just explore into the ROM, and rename the 4G icons to the proper names of the H icons, so instead of showing H, they show 4G.
For example. All i did was copy out all of the "4G" icons, and rename them the same as the "H" icons, then copy them back, and hit ok to replace the current files. (All icons follow the same naming convention (in, out, inandout, connected, etc.), just replace 4G with H and you're good).
for reference, the icons are found in SystemUI.apk > res > drawable-hdpi
You don't even have to unzip/zip or worry about signing .apk's, just browse with something like 7zip and go find them.
I've done this and it works just fine. I'm sure you could easily write a script that would do this too, but whatever. I'm not good at any of that. I found a way that works and went with it. FWIW I was under the impression that flashing nightlies doesn't overwrite the themes, but from my experiences it did. Possibly had something to do with me running a mod to flash the stock 2.3 launcher and remove ADW though, that seemed to mess with the themes before.
If not, you should theoretically only have to do this change to the systemui theme once, and then you'd be good to go for later nightlies. Correct me if I'm wrong here.

ok so i found what your talking about, but how do i edit these and then apply. do i reflash?
HTC Vision (G2)
Android 2.3.5
CM7 Nightly #179

PooN_HeaD said:
ok so i found what your talking about, but how do i edit these and then apply. do i reflash?
HTC Vision (G2)
Android 2.3.5
CM7 Nightly #179
Click to expand...
Click to collapse
Download a nightly.
Using 7zip, just go into the ROM.zip (don't unzip, just explore) and replace the icons, back out all the way. 7zip will ask if you would like to update the folder with changes, select "yes".
Then flash that ROM.

ok i have a mac
HTC Vision (G2)
Android 2.3.5
CM7 Nightly #179

PooN_HeaD said:
ok i have a mac
HTC Vision (G2)
Android 2.3.5
CM7 Nightly #179
Click to expand...
Click to collapse
mm well unless you have bootcamp or a virtual machine, you're kinda SOL. I use bootcamp windows 7 to do this stuff.
The problem in OSX is that you can't explore without unzipping (AFAIK). So you're stuck unzipping the ROM and having to re-zip and sign and all that (otherwise the ROM won't flash). At that point you're better off spending your time doing a more intricate mod.

Related

Splash screen

I have a custom splash screen and the .txt file needed to flash a new splash screen using adb but my question is I do not have access to a working computer right now is their any way to flash it from the phone?
Evo 4g running CM7 nightly 99
All you need to do is get that file, the desc file, ect, place it in a PC36IMG, place it on the sdcard, then reboot into the bootloader and apply the update.
It needs a desc file I thought it needed a file called android-info.txt and the image I thought description files were for the boot animation
Edit: I zipped the files as PC36IMG and placed on sdcard went into hboot and it searched and found it went to parsing then just stopped and went backyard to, regular screen no install please help
Evo 4g running CM7 nightly 99
Like is their anyway to flash this with amon or clockwork or something cus I really hate Tue bright white splash screen especially in the dark in the middle of the night
Evo 4g running CM7 nightly 99
Dumb question was the pic 480x800 and was it turned into .img
brought to you by the voices in my head
I know it is 480x800 and pretty sure .img
Evo 4g running CM7 nightly 99
Ok it was PNG I changed to img and tried again getting the same result
Evo 4g running CM7 nightly 99
spcking said:
It needs a desc file I thought it needed a file called android-info.txt and the image I thought description files were for the boot animation
Edit: I zipped the files as PC36IMG and placed on sdcard went into hboot and it searched and found it went to parsing then just stopped and went backyard to, regular screen no install please help
Evo 4g running CM7 nightly 99
Click to expand...
Click to collapse
Yes, the android file, my bad. Hold on; I'll link my PC36IMG splash zip, then all you have to do is add you .img file, and remove the old one.
Now just rename the file to PC36IMG, and do what ya did before. Also you can keep that splash if you want, good way to syke people out.
Trying now
Evo 4g running CM7 nightly 99
Alrighty cappy.
Finally no more bright ass splash screen thank you very much for that
Evo 4g running CM7 nightly 99
spcking said:
Finally no more bright ass splash screen thank you very much for that
Evo 4g running CM7 nightly 99
Click to expand...
Click to collapse
Never a problem man.

[Q] Boot Animation Puzzle

First post, but I believe I have done due diligence in reading up on this issue.
I really love reading the posts and have found several of them useful, but I just haven't done a lot of posting... until now.
Does anyone else hate that stupid Sprint 4G animation????
I recently flashed MikG and the only thing that I don't love about this rom is the boot animation. It has the standard Sprint animation. I see there are plenty of other cool animations, so I wanted to update this.
I went and renamed the sprint spc_bootanimation.zip and have placed several different boot animation zips in the system/customize/resource folder (one after the other). Sprint animation goes away, but no matter which version of the bootanimation.zip I put in it's place, I get the same results. My boot animation is always a black screen with small light letters on it spelling "android". There is kind of a cloud animation scrolling behind the letters. Always the same no matter which bootanimation.zip I put in place.
I've tried the adb push method, the boot replacer program, and just copying the file to the proper location (several different files in fact) (using explorer v1.0 folder is mounted r/o) with the same results. I found a cool one on the collection page that was flashable, but it ended up having an error in the code and aborted.
Gotta get rid of that Sprint sales advertisement and get some cool looking animation that you guys have cooked up!
Any thoughts would be much appreciated!
ROM: MikG 1.03 Sense 2.1+3.0
Android 2.3.3
Kernel:HTC-Kernel 18-2 #1
Rooted with Unrevoked 2
S-off
Hardware version 0003
Amon-RA 2.3
hell dude i ripped into that rom and i cant find a 2nd bootanimation only the one in the syscustomize folder, and you have already said you replaced that one. have you tried posting on mik's site. sorry couldnt be more help.
I'm having the same problem, im currently trying to fix it. If I figure it out I'll post what I did.
Sent from my PC36100 using XDA Premium App
That's the default ANDROID animation. Aosp. Find a boot that flashes or Google uot theme kitchen and make your own file to flash; just choose the boot animstion
Gimme a couple a days to come up with a new sig that is cool.
I am running that same rom. No problems changing the boot animation. I push rom> reboot> power down > push boot animation located on sd card in recovery>
here is the honeycomb boot animation I am using:
Okay have it figured out now.....
Had the file going in the correct location. Needed to modify the permissions of the file to match the other files in that folder & renamed the file "spc_bootanimation.zip" in lieu of "bootanimation.zip". Working great now.
Thanks for all of your assistance!
Loving this ROM!
I found out you just need to have it named spc_bootanimation.zip
Sent from my PC36100 using XDA Premium App

[Q] Need Help...

This is actually kinda ridiculous, so sorry for the fuss, but:
Am on CM7 RC1v2, deblurred Nordic Froyo base, everything worked fine until...
Decided to prep up my lockscreen font so went into system/fonts and friggin idiotically deleted the clocktopia.ttf forgetting to rename the new font to this. Now I'm stuck in a bootloop. All I need is root access from my desktop, but somehow can't get into recovery either. Anybody out there who can help? Trying to avoid a complete wipe, forgot to naindroid and to do a decent titanium backup since I've been in "discovery mode" since 10 days (my first CyanogenMod ). Can't post in the developement section either for obvious reasons...
Thx for any help!
You can run again the update via recover y
Sent from my MB525 using XDA App
uff, thx, worked. Got confused and first booted into the standard system recovery instead of 2nd-init. Followed the steps from the CM7 FAQ for a system update, now everything back to normal...
Still curious though, how do I change the clock font in the lockscreen? Should I just go ahead and rename the new font to clocktopia?

Gingerbread on Droid Pro with Unlocked Froyo Radio

So, as people know, the newest builds of CM7 or CM9 by JackpotClavin require it to be placed on top of a fully updated Gingerbread Droid Pro. However, those of us with a US Band unlocked radio can't do that without losing our unlocked radio since there is no unlocker for the gingerbread radio. Based on what Axl did for the Droid 2 Global, I've created a gingerbread kernel based on the Droid Pro to allow us to install gingerbread roms while maintaining our unlocked radios. I've also created a clockworkmod backup that can be used as is, or as a base for installing another gingerbread rom such as CM7. Thanks to JohnS and dettofatto, the kernels and clockworkmod backups were updated to 4.7.3. Below are the Resources and the Process.
Resources:
1) RDS Lite (http://forum.xda-developers.com/showpost.php?p=19390783&postcount=1)
2) SBF 2.26 (http://db.tt/5gKwCQwF)
3) TBH Radio Unlocker (http://goo.gl/6NuuG - http://www.mediafire.com/?9pfbk846tjb5a36)
4) Root (http://www.psouza4.com/Droid3/)
5) Droid 2 bootstrap (http://www.mediafire.com/?g8l7vy0futbc4g5)
6) Kernel (US http://www.mediafire.com/?swv4bl7wa47mpxg or EU http://www.mediafire.com/?w6963rmkvdqmro1)
7) ClockworkMod Backup (Verizon US http://www.mediafire.com/?yhr4b768qbnyote or European http://www.mediafire.com/?wn3pyy5fw3i1nr2)
8) Optional Roms - CM7 for Droid Pro (http://goo.gl/M6e4s) or Apex for Droid Pro (http://goo.gl/sTwSp)
Process:
1) Boot to Recovery & Wipe Data (R+M+Power)
2) Boot to Bootloader (Up+Down+Power) & SBF to 2.26 (Using RSD Lite & SBF file) - Usually I have to copy SBF File to root of Hard Drive & name it 2026.sbf or it may fail (ymmv)
3) Skip Activation (http://goo.gl/n2Zhw)
4) Settings->Applications, Set Unknown Sources and USB Debugging (in development)
5) Root
6) Install Bootstrap apk, open, press 'bootstrap recover'. then 'reboot recovery' to boot to recovery mode.
7) While in recovery mode, and without rebooting at all:
...a) Wipe Data
...b) Install Radio Unlock
...c) Install Kernel
...d) Restore Clockworkmod backup (you should have extracted the clockworkmod zip so the folder is located on your sdcard at [ie clockworkmod\backup\...] folder (with the system.img and other images under that folder))
8) Optional - Install cm7, apex or other rom you download
9) Reboot
Notes:
1) You can build your own Clockworkmod recovery file by following the JackpotClavin link below and then just backing up your build. It won't have signal while you're doing it (because of the locked radio), but after you restore it later using the above steps, it'll be fine.
2) Your SIM needs to be unlocked from verizon (i used sim-unlock.net) to work.
3) Info on an Argentinian 2.3.6 rom here
Credits:
JackpotClavin - CM7 for Droid Pro (http://goo.gl/M6e4s)
Axl - Created the Droid2 Kernel which allowed me to use the same method for the Droid Pro (http://goo.gl/ErLAR)
dettofatto - Clockworkmod backup and kernel for European 4.7.3
JohnS - Clockworkmod backup and kernel for Verizon US 4.7.3
Good Luck!
hey im from argentina, here we have Motorola Pro which is the same as droid pro but it doesnt use cdma, it uses gsm and hsdpa. Can i install this on my phone or will it turn to a nice brick?
now i have ANDROID 2.2.2 and it says that the phone is the xt610 same as the droid pro.
thanks
edit: i just followed your source (jackpotcalvin) and it says it should work with gsm but there are still issues
bveditz, thanks for your work.
i have a droid pro (unlocked, verizon branded).
right now i'm using android v2.2 because the TBH radio hack only works with this version. i didn't dare doing any updates because of that. lol. i have one questions.
my phone is already sim unlocked.
so with this new CM7 build, can i just flash and use it without doing the TBH radio hack all over again?
chagla said:
bveditz, thanks for your work.
i have a droid pro (unlocked, verizon branded).
right now i'm using android v2.2 because the TBH radio hack only works with this version. i didn't dare doing any updates because of that. lol. i have one questions.
my phone is already sim unlocked.
so with this new CM7 build, can i just flash and use it without doing the TBH radio hack all over again?
Click to expand...
Click to collapse
Yes, you don't need to unlock the radio, you can start from step 5 (or 6 if its already rooted) and just skip the part about running the radio unlock. Running the radio unlock again doesn't hurt anything either.
Just a word of note, I don't know how the froyo build is by default (i didn't use it), but the current CM7 build still has the issue with switching between mobile data and wifi data, and mobile data can also cut out at times. All that info is in the CM7 discussion, but it's worth noting that the Droid Pro CM7 Build isn't a final build and might not function with the same stability as the Froyo build did. This has nothing to do with this process, it's just the current state of the CM7 rom at the moment. Flashing APEX might produce better results with the radio, but you lose features of CM7, although it has a number of its own features.
installed it. i just started with step 7C. so far so good.
radio is working. sim is still unlocked.
so far i've found one thing, maybe i didn't see the setting yet. the keyboard back lights aren't working?
chagla said:
installed it. i just started with step 7C. so far so good.
radio is working. sim is still unlocked.
so far i've found one thing, maybe i didn't see the setting yet. the keyboard back lights aren't working?
Click to expand...
Click to collapse
No, with that issue and the wifi/radio issues (loosing connection and not being able to switch between the two) , I switched over to the APEX ROM, it's more stable. You don't get the features of CM7, but it has less bugs. Might want to try that. You don't need to do anything different, just put the apex file on your SD, reboot to clockwork mod and wipe data and reflash.
is it possible to use this in some way to have band unlock and normal ginerbread without cm7
Yes. You need to basically upgrade Gingerbread to the full release, root it and do a nandroid backup. Then, you follow the steps in the first post but instead of restoring the nandroid backup of CM7, you install the nandroid backup of regular gingerbread that you made yourself.
bveditz, thanks, that is along the lines of what i was thinking might work after reading the directions... Im already running tbh rooted gingerbread... Do i need to sbf and upgrade to a clean gingerbread, or can i nandroid backup what i already have and then retain all my settings and apps so i dont have to start over. Has anyone noticed any disadvantage to useing the older radio besides the obvious advantage of being able to use the band unlock?
Excellent tutorial!!
EXCELLENT TUTORIAL GUYS. Also, you should make sure to mention after installing bootstrap, press 'bootstrap recover'. then 'reboot recovery' option. I did that, installed the kernal and restored backup fine.
Only issue so far was a -20% battery decrease randomly. I had 100% with a brand new battery fully charged for the first time and when I finished installing cm7 I was already on 80%, then dropped to 70% on a reboot or two, its weird. Anyone else had this happen? I heard the apex 2.0 rom did it to someone else as well on another forum
Also, do you guys know how to get back the blur social network apps such as friendfeed, or whichever app it was that adds your friends social network updates to their contact numbers on your contacts? Most people don't like it, but I think its a pretty awesome built in feature
jxs714 said:
EXCELLENT TUTORIAL GUYS. Also, you should make sure to mention after installing bootstrap, press 'bootstrap recover'. then 'reboot recovery' option. I did that, installed the kernal and restored backup fine.
Only issue so far was a -20% battery decrease randomly. I had 100% with a brand new battery fully charged for the first time and when I finished installing cm7 I was already on 80%, then dropped to 70% on a reboot or two, its weird. Anyone else had this happen? I heard the apex 2.0 rom did it to someone else as well on another forum
Also, do you guys know how to get back the blur social network apps such as friendfeed, or whichever app it was that adds your friends social network updates to their contact numbers on your contacts? Most people don't like it, but I think its a pretty awesome built in feature
Click to expand...
Click to collapse
Thanks, made the note to the tutorial. I haven't noticed the issue with the battery, but I do know that this is one of those roms that seems to jump in increments of 10 for the battery which is kinda weird. That said, i only used it about a week on CM7 before switching over to the Apex rom (and haven't noticed that issue on the apex rom).
Don't know about blur, I didn't use the original OS at all. That said, you can do what the guy above did and wipe the phone, upgrade all the way to gingerbread, do a nandroid backup then follow the original instructions but use that backup to restore to, which should have the full motoblur functionality. Thats just a guess though, haven't tried it myself.
------------------
Could you re-up just the Kernel file? I've followed your instructions to the T and every time it seems that I have a problem at that step.
I've gotten to Flashing the Kernel VIA CWM, and when I try to restore the backup of CM7 via \clockworkmod\restore\ folder - it will say MD5 mismatch.
Also, if I skip the restore portion of CM7 and just try to reboot the phone after flashing the Kernel, I will be stuck at the red M.
I've tried rebooting the phone right after applying the band unlock (all after SBF + Wipe data), and the phone will boot up just fine if I skip flashing the Kernel (again I leave it in zip form and install it via CWM).
I’ve already unlock my SIM via code provided by VZW (I am a VZW customer in good standing)
While stuck at the red M, I’ve done a battery pull and tried to enter Recovery mode by pressing M+R+Power, and the recovery screen that is booted up doesn’t look like it’s compatible with the phone. I can almost describe it as a bunch of white horizontal lines of what the menu should be, and all the menus and the green android are skewed diagonally to the right/and also looks like it’s double or triple vision.
I know a very similar process works for the D2G, because I have successfully performed and tested it on the D2G on one of my other lines.
Any help is greatly appreciated. I can stick with Froyo, but I’d like to have GB.
Try redownloading the CM7 backup, it might be a corrupted download. If that doesn't work, try the APEX file. But, yes, you cannot reboot without restoring a gingerbread backup or you'll have to start over again (there's ways to get back to the cwm but i'm not sure how, I did it accidently a few times).
Thanks I am a complete noob
So it turns out the problem is when I unzipped the Backup that it created sub folders "\nandroid\restore\xxxx\xxx\backup\restore\"
Just to save everyone headaches, make sure the when you unzip the file into your backup folder that the name of the next folder down is the series of numbers that represent the name & number i.e.
Should NOT be
\clockworkmod\backup\clockworkmod\clockworkmod\backup\2011-11-27.09.52.03\
but instead SHOULD BE
\clockworkmod\backup\2011-11-27.09.52.03\
My 7zip by default created all those sub directories, which caused the CWM restore not to find the back up files.
On another note, I am having issues with GSM Wifi and 3G.
With a fresh flash & WiFI on - if I connect WIFI first I cannot later add the APN and access Cellular Data
Inversely, If I add the APN first (again after a fresh SBF flash, kernel update, and Backup restore), and connect to cellular data, none of the WIFI connects I make can access WIFI Data
I am going to try WIFI fixer in one of the older threads to see if this resolves the problem.
DROID PRO
Please upload the file in other downloads bc megaupload is temp down
agni said:
Please upload the file in other downloads bc megaupload is temp down
Click to expand...
Click to collapse
If you're talking about the two multiupload files I put up, use one of the other links below megaupload. I just tried the bottom one (wupload) and it worked. If you're talking about RSD Lite and SBF files, I'll see if I can find another link to them, but you can easily find them by searching the forums or google.
**Edit** Edited first post with non-megaupload links.
jraskal said:
On another note, I am having issues with GSM Wifi and 3G.
With a fresh flash & WiFI on - if I connect WIFI first I cannot later add the APN and access Cellular Data
Inversely, If I add the APN first (again after a fresh SBF flash, kernel update, and Backup restore), and connect to cellular data, none of the WIFI connects I make can access WIFI Data
I am going to try WIFI fixer in one of the older threads to see if this resolves the problem.
Click to expand...
Click to collapse
Let me know how that worked out. I stopped using CM7 and switched to Apex because of the Wifi/Cellular switching issues of the november cm7 rom.
bveditz said:
Let me know how that worked out. I stopped using CM7 and switched to Apex because of the Wifi/Cellular switching issues of the november cm7 rom.
Click to expand...
Click to collapse
Can you provide a link to the Apex rom you're using?
aaevann said:
Can you provide a link to the Apex rom you're using?
Click to expand...
Click to collapse
Theres an apex thread on xda that links to the rom http://forum.xda-developers.com/showthread.php?t=1292506

system ui

I was wondering what the systemui.apk does?
mdo41 said:
I was wondering what the systemui.apk does?
Click to expand...
Click to collapse
It provides the status bar that you see at the top of the screen and the notification pulldown curtain.. among other things.
will it affect the framework or any tweaks that are in a rom if i change it?
If you are just wanting to change the hue of images (pngs).. then the answer is no.. you can do that all you want.
strongsteve said:
If you are just wanting to change the hue of images (pngs).. then the answer is no.. you can do that all you want.
Click to expand...
Click to collapse
I pulled the system ui from another rom that i liked more. if i were to replace the one that is being used with the one i like would it effect like the battery tweaks? os is that completely seperate? thanks.... noob questions
It is very common for ROM devs to tweak that file for their respective projects. I have done basic changes like swapping out images and such without harm. (changing battery images usually)
On the other hand I have also tried mixing the systemui.apk from one ROM to another and many times it breaks the status bar. Whenever I am going to play with modding that file I keep a flashable zip containing the original ready to go to put it back in case something goes wrong.
Thanks
Sent from my A200 using XDA
Also, systemui depends on framework-res.apk to run correctly. Framework editing will also make changes to the notification bar. You may have to change them as a pair. Like the other user stated, either keep a stock flashable of what you're replacing on SD or a nandroid backup prior to changing any system files because the phone may not boot after you make changes.
Well, it's always a good idea to have a current backup anyway.
OK I changed it after I backed up and it seems to be running fine
Sent from my A200 using XDA

Categories

Resources