I need to change my LCD density on my phone (NAND / Warm Donut), but I do not want to reinstall the whole system...is there a way to change the LCD density without formatting/reinstalling Android?
Also what is the best NBH resolution and density combination to use?...I tried 120 density on 240x320 NBH file, but it is 'too big'...I have to scroll down to see stuff. 110 was perfect it seemed for 240x320 except that it left some black space on the edges at times.
Thanks,
-C
su
mount /system -o rw,remount
edit ro.sf.lcd_density in /system/build.prop
mount /system -o ro,remount
then reboot
I am a Windows user. How do I do it in Windows or in the phone. Also my phone is not "rooted" (whatever that means)
crobs808 said:
I am a Windows user. How do I do it in Windows or in the phone. Also my phone is not "rooted" (whatever that means)
Click to expand...
Click to collapse
Our phones are rooted, period.
You have to use adb to do it from windows or linux, or be comfy using vi on the phone (ha.)
so you'd do the remount stuff mentioned above, then
Code:
adb pull /system/build.prop/ro.sf.lcd_density c:\mydata\ro.sf.lcd_density
*edit the pulled file*
adb push c:\mydata\ro.sf.lcd_density /system/build.prop/
mrkite38 said:
Our phones are rooted, period.
You have to use adb to do it from windows or linux, or be comfy using vi on the phone (ha.)
so you'd do the remount stuff mentioned above, then
Code:
adb pull /system/build.prop/ro.sf.lcd_density c:\mydata\ro.sf.lcd_density
*edit the pulled file*
adb push c:\mydata\ro.sf.lcd_density /system/build.prop/
Click to expand...
Click to collapse
Ok thanks...now, what is the best NBH resolution and density value combination to use for the Vogue?
open a terminal "better terminal emulator" on your phone
type
su
mount /system -o rw,remount
Click to expand...
Click to collapse
use astro to browse and edit /system/build.prop
look for the line ro.sf.lcd_density=120
change it to whatever you like save changes.
makes filesystem read only
Code:
mount /system -o ro,remount
restart phone
seriously read Tatnai's FAQ (apparently yours isn't the easiest if it didn't work on your own Vogue) and stop making these useless threads.
berardi said:
seriously read Tatnai's FAQ (apparently yours isn't the easiest if it didn't work on your own Vogue) and stop making these useless threads.
Click to expand...
Click to collapse
Huh? I didn't incorporate anything about LCD density into my tutorial on purpose...my tutorial is about how to install Android via the NAND method...has nothing to do with density tweaking, and I never intended it to.
Also "stop making threads"...? What is this forum for then, because I only post a thread when the search or FAQs do not cover something. Isn't that the point of a forum?
myn said:
Change LCD Density to 110
Change LCD Density to 160
Click to expand...
Click to collapse
If you want any other density edit the build.prop within these files - look for lcd density and change it to what you want. Go into your boot up menu and do "install update"
Do a little reading like everyone else does, studies show it is good for your brain.
if using 320x480, you should use lcd.density of 160.
if using 240x320, most people use something between 110 and 120. I like 110, things are a little smaller, easier to see in messaging, and the eclair dialer and wysie's dialer fit the screen. others like 120, because supposedly it is a little "crisper"; try for yourself. I've played around with 113, 115, -> basically everything between 120 and 110.
if using 320x428 (does anyone use this anymore???) use 160 (I think, I can't even remember anymore).
there is a full discussion of other benefits of different resolutions in the FAQ thread. also, you might want to take a look at the market FAQ post, as it applies.
berardi said:
If you want any other density edit the build.prop within these files - look for lcd density and change it to what you want. Go into your boot up menu and do "install update"
Do a little reading like everyone else does, studies show it is good for your brain.
Click to expand...
Click to collapse
ha...you like following me around the board and insulting me. you have done this now on three threads where i simply ask a question on how to do something, then you state that my post is 'useless'. that really lends itself to good discussion. please re-evaluate why you post things because you are definitely not doing it to help me or answer the original question.
p.s. - i did read the forum and search before i posted. all the instructions so far were how to do it on Linux or how to do it using ADB, neither of which I have at my disposal. The other posters in this thread helped, which I had already stated (post #5 on pg.1) before you even posted, so there was no reason for you to post all all, except to get your insult in I guess. Stop following me around the forum. Now.
crobs808 said:
ha...you like following me around the board and insulting me. you have done this now on three threads where i simply ask a question on how to do something, then you state that my post is 'useless'. that really lends itself to good discussion. please re-evaluate why you post things because you are definitely not doing it to help me or answer the original question.
p.s. - i did read the forum and search before i posted. all the instructions so far were how to do it on Linux or how to do it using ADB, neither of which I have at my disposal. The other posters in this thread helped, which I had already stated (post #5 on pg.1) before you even posted, so there was no reason for you to post all all, except to get your insult in I guess. Stop following me around the forum. Now.
Click to expand...
Click to collapse
It is my opinion man, can't we all post our own opinions wherever we want? these were your words afterall..
As for you reading the forum and not finding the answers, well apparently you can't read very well. Trust me I am FAR from a coder / developer / hacker - I learned how to do it simply by reading other posts. If you do a little reading you can get far.
Hoping someone can point out the error of my ways ... I am running kaiser-eclair via nand on my Polaris and trying to edit build.prop in order to adjust density using the "su" and "mount" commands above. Astro is unable to save changes as I do not appear to be getting write access to either /system or build.prop. When I open terminal, I am greeted by $. I entered "su" and got a new line with #. Here I typed "mount /system -o rw,remount". I changed ro.sf.lcd_density from 160 to 110 in build.prop using Astro but could not save changes - I checked the build.prop permissions (-r-) and /system permissions (dr-). Please pardon my lack of Linux savvy-ness, but what have I missed? Thanks!
tmcfarland said:
Hoping someone can point out the error of my ways ... I am running kaiser-eclair via nand on my Polaris and trying to edit build.prop in order to adjust density using the "su" and "mount" commands above. Astro is unable to save changes as I do not appear to be getting write access to either /system or build.prop. When I open terminal, I am greeted by $. I entered "su" and got a new line with #. Here I typed "mount /system -o rw,remount". I changed ro.sf.lcd_density from 160 to 110 in build.prop using Astro but could not save changes - I checked the build.prop permissions (-r-) and /system permissions (dr-). Please pardon my lack of Linux savvy-ness, but what have I missed? Thanks!
Click to expand...
Click to collapse
Are you using one of those files I linked to? I found it easiest to do it in windows on a pc. If so, open up the .tar file and look for build.prop - open that and make the change. Close the file and it should allow you to save changes. Put that on an sd card in your phone reboot and install update and you should be good.
berardi said:
Are you using one of those files I linked to? I found it easiest to do it in windows on a pc. If so, open up the .tar file and look for build.prop - open that and make the change. Close the file and it should allow you to save changes. Put that on an sd card in your phone reboot and install update and you should be good.
Click to expand...
Click to collapse
That did the trick ... many thanks!
crobs808 said:
I need to change my LCD density on my phone (NAND / Warm Donut), but I do not want to reinstall the whole system...is there a way to change the LCD density without formatting/reinstalling Android?
Also what is the best NBH resolution and density combination to use?...I tried 120 density on 240x320 NBH file, but it is 'too big'...I have to scroll down to see stuff. 110 was perfect it seemed for 240x320 except that it left some black space on the edges at times.
Thanks,
-C
Click to expand...
Click to collapse
Either use an androidupdate.tar, or, if you need to do it on your phone:
Open BetterTerminal.
1. Type 'su', enter.
2. Type 'mount -o remount,rw /system', enter.
3. Type 'vi /system/build.prop'.
4. Scroll down to the build.prop section. Put the cursor where you want to modify.
5. Hit 'i' to go into edit/insert mode.
6. Hit backspace to delete the comment "#" of the line you want..
7. Add a # to the old density line. You can safely use the dpad to move in edit mode.
8. Hit escape (Hold Center Button and type '1'), to leave edit/insert mode.
9. Type ':wq', then enter, to write and quit.
10. Power down (the proper way, hold red button, hit power off....).
You can always hit escape (Center-1), then ':q<enter>' to quit without saving if you mess up. Then start over.
I just did this, so it works.
Vi has two modes, edit mode, and command mode. If you don't know what mode you're in, always just hit ESC (Hold center button, type the number '1') to return you to command mode.
BetterTerminal is kinda screwy, the cursor covers the letter before it, so you have to keep that in mind.
Personally, I prefer 120, it's nice and clear. It originally was changed from 120 to 110 because Google Maps would freeze on the 3.4.0? update and a density of 120, however 4.0.0+ seems to fix that. I don't know why Myn doesn't go back.... Google maps works perfectly fine for me now on 120.
jnadke said:
Either use an androidupdate.tar, or, if you need to do it on your phone:
Open BetterTerminal.
1. Type 'su', enter.
2. Type 'remount -o remount,rw /system', enter.
3. Type 'vi /system/build.prop'.
4. Scroll down to the build.prop section. Put the cursor where you want to modify.
5. Hit 'i' to go into edit/insert mode.
6. Hit backspace to delete the comment "#" of the line you want..
7. Add a # to the old density line. You can safely use the dpad to move in edit mode.
8. Hit escape (Hold Center Button and type '1'), to leave edit/insert mode.
9. Type ':wq', then enter, to write and quit.
You can always hit escape (Center-1), then ':q<enter>' to quit without saving if you mess up. Then start over.
I just did this, so it works.
Vi has two modes, edit mode, and command mode. If you don't know what mode you're in, always just hit ESC (Hold center button, type the number '1') to return you to command mode.
BetterTerminal is kinda screwy, the cursor covers the letter before it, so you have to keep that in mind.
Personally, I prefer 120, it's nice and clear. It originally was changed from 120 to 110 because Google Maps would freeze on the 3.4.0 update and a density of 120, however 3.4.1+ seems to fix that. I don't know why Myn doesn't go back....
Click to expand...
Click to collapse
Man you are a vi hacker!!
The only reason I am using 110 (soon to be 113) is because the eclair dialers cut off the top of the numbers with 120. Some themes however don't have the eclair dialer so 120 is completely perfect for it.
This process of changing density will become inherently easier come the next release of Warm Donut . More to come as I make more progress.. I will leave it at that.
myn said:
Man you are a vi hacker!!
The only reason I am using 110 (soon to be 113) is because the eclair dialers cut off the top of the numbers with 120. Some themes however don't have the eclair dialer so 120 is completely perfect for it.
This process of changing density will become inherently easier come the next release of Warm Donut . More to come as I make more progress.. I will leave it at that.
Click to expand...
Click to collapse
Astro wouldn't save the changes to build.prop Even after su/remount (That's because only BetterTerminal gets su privileges, not Astro)
Yeah, I've learned to love vi, mainly because searching is similar to sed, unlike that stupid emacs.
I actually use 123, I'm greedy
the 1, 2, 3 don't bother me in the least, you can still press them and I rarely dial numbers manually
tmcfarland said:
Hoping someone can point out the error of my ways ... I am running kaiser-eclair via nand on my Polaris and trying to edit build.prop in order to adjust density using the "su" and "mount" commands above. Astro is unable to save changes as I do not appear to be getting write access to either /system or build.prop. When I open terminal, I am greeted by $. I entered "su" and got a new line with #. Here I typed "mount /system -o rw,remount". I changed ro.sf.lcd_density from 160 to 110 in build.prop using Astro but could not save changes - I checked the build.prop permissions (-r-) and /system permissions (dr-). Please pardon my lack of Linux savvy-ness, but what have I missed? Thanks!
Click to expand...
Click to collapse
Ditto - I tried doing it this way after reading a post on page like 153 (or there abouts) on the main Myn Warm Donut thread to no avail. Definitely doesn't work.
Related
ive done a search already and found nothing...is there a way or a file i unmount in terminal emulator to reduce the # of home screens because i only need the 3 that the stock firmware includes but i get 5..can any1 help?
ps..ive done a search already and found nothing..
search the forums for advanced launcher. it lets you configure the # of screens (and much more!)
Also, totally should go in the Q&A section, dude. For future reference.
boimarc89 said:
ive done a search already and found nothing...is there a way or a file i unmount in terminal emulator to reduce the # of home screens because i only need the 3 that the stock firmware includes but i get 5..can any1 help?
ps..ive done a search already and found nothing..
Click to expand...
Click to collapse
It's not as easy as that.
You'd need to build the Launcher.apk from source (i think) and manually edit the number of home screens.
Or you can do what biosehnsucht said, which is what i'd recommend
Very old mod. Probably no longer works. Use at own risk. No longer supported by me.
ROOT REQUIRED
ONLY works on ROMS that include HtcLockScreen.odex.
So it wont work if you've flashed lwp patches, Sprint ROMS or anything that removes the .odex file.
-------
Originally created by JsChiSurf over in the Hero forums via my encouragement This version is made for the Eris, it is not the same as the Hero version (which doesn't work properly for us).
This is a modification of the STOCK HTC Sense lockscreen that removes the background so you can see your homescreen behind it.
*Users need to already be comfortable with using 'adb' I won't be providing support on that since there are numerous threads with instructions all around.*
**Before** pushing the apk into that folder, you'll need to FIRST perform the following steps to remove the stock lock wallpapers from loading, as well as any cached custom wallpaper you have applied. You can perform these via adb as listed, or if you have Root Explorer (on the marketplace), you can navigate to the folders listed and delete the items that way.
Code:
adb remount
adb shell
cd /data/misc/lockscreen
rm *
cd /system/customize/resource
rm htc_wallpaper*
exit
Note: You may or may not have anything to delete in /system/customize/resource, so if you get an error message while using adb, don't worry.
HtcLockScreen.zip MD5: 9423D8C3D6CBBF3E084CD185130F9649
*APK NOTE: APKs are case sensitive, be sure you install this without renaming it, or it wont overwrite your original APK*
After you extract the zip to your sdk/tools directory perform the following (case sensitive):
Code:
adb push HtcLockScreen.apk /system/app
adb reboot
If you get "read-only" errors, try "adb remount" OR "adb shell", then, "su", then "mount -o rw,remount /dev/block/mtdblock3 /system" and then the other commands.
EDIT: Clock-less version now available for download! Same instructions apply.
Clock-less Info: **Since some users may have performed the 'experienced users' steps below, an Android image has been added to 'lockscreen_topedge.png' so that it isn't 100% transparent.
If you want to remove this image: First, download the ZIP below with the PNGs, take any one of those and rename it to 'lockscreen_topedge.png, open the lock apk in your favorite zip file manager (winzip, winrar, 7-zip), navigate to "res\drawable-normal-mdpi" and drag your newly-renamed PNG in there. If a dialog pops up, be sure you select the option that has NO compression, this is usually called "Store."**
Make a post if you have any problems NOT related to 'adb.' Again, support is not provided for that.
Clockless Lock.zip MD5: B604B530E02C47DA81AD8B4563BE71D2
__________________
Now some optional additional steps for **experienced users only** (I suck at tech support so if you ask something, I'll try to answer, but no guarantees):
If you put the PNGs included in the zip below into 'com.htc.resources.apk\res\drawable-mdpi', it will remove the HTC "Arc" on the lockscreen. Now, to create your own Arc replacement, all you'll need to do is go into 'HtcLockScreen.apk\res\drawable-normal-mdpi' and change the lockscreen_topedge.png to your liking A much easier change than fiddling with your resources apk everytime and its only 1 image to change, instead of trying to line up three. Of course, if you remove the Arc and do not change your lockscreen_topedge.png, you will have a completely invisible lockscreen, so don't freak yourself out, just make something for that PNG.
*Does not seem to work with Hero or Legend ROMs*
I've used adb push (to change my boot animation) but I can't say I know how to use it.
Can you specify which commands to use?
EDIT: do you have to have root for this?
Yes you have to have root. You would do 'adb install HtcLockScreen.apk'.
wshuman3 said:
You would do 'adb install HtcLockScreen.apk'.
Click to expand...
Click to collapse
waahhh no X_X this isn't an app to be installed. you are overwritting the old one (after youve backed up!) the "install" command installs to data/app, which isn't what we want (but thanks for keepin an eye on the thread for me wshuman3 )
if you put the apk in your sdk\tools directory, then the command would be
Code:
adb push HtcLockScreen.apk system/app
you were correct about needing root tho
oh sweet!
one question though, what if your phone is locked? will it still show the homescreen?
Lemcott said:
oh sweet!
one question though, what if your phone is locked? will it still show the homescreen?
Click to expand...
Click to collapse
please read the first post again before you post. your question is answered in both the thread title as well as the second line.
thanks!
no no no... okay I admit, i worded that question wrong.
if you phone is password protected, as in locked down, with the graphical password and all that. will it still show the homescreen?
Lemcott said:
no no no... okay I admit, i worded that question wrong.
if you phone is password protected, as in locked down, with the graphical password and all that. will it still show the homescreen?
Click to expand...
Click to collapse
i believe it should still show you the home screen, considering with the normal lock app by htc in order to unlock it with the dot pattern, you have to pull the slider down, then it shows you the pattern. so going off of that, then it should still do the same thing, but instead of showing a pic on the lock screen, it shows the home screen, then you slide it down to unlock, which i would assume that it would then pop up the dot pattern.
ECLIPS3's explanation is entirely correct. locking will not hide your homescreen. but then, if someone wanted to see your homescreen with the normal lockscreen, they would just have to slide down the Arc most of the way and they'd see most of it. not secure either way.
but i dont think thats what you were even worried about Lemcott. but explained it anyway
yep, you got it I'm not really worried about them seeing the homescreen (oh no! they saw my poor organizational skills! I'm ruined! haha) I just have my phone locked done mainly because my friends and I have a pretty long running epic war to change each other's facebook status'/tweets to very embarrassing things, nosey family members, and just in case i ever forgot it somewhere.
cant wait till i get my new phone in tomorrow and patch this sucker on. speaking of which, if i were to patch this after flashing on Jamezelle's sense-abloe 2.0, would it look just like the normal htc lock screen just transparent? or will it look like sense-able's lock screen but transparent?
Lemcott said:
yep, you got it I'm not really worried about them seeing the homescreen (oh no! they saw my poor organizational skills! I'm ruined! haha) I just have my phone locked done mainly because my friends and I have a pretty long running epic war to change each other's facebook status'/tweets to very embarrassing things, nosey family members, and just in case i ever forgot it somewhere.
cant wait till i get my new phone in tomorrow and patch this sucker on. speaking of which, if i were to patch this after flashing on Jamezelle's sense-abloe 2.0, would it look just like the normal htc lock screen just transparent? or will it look like sense-able's lock screen but transparent?
Click to expand...
Click to collapse
it will look like the normal lock screen, just transparent. but you could edit the transparent lock screen to look like jameselles, just transparent. im sure someone would be willing to do that for you. i might, just dont have time right now.
I'll give it a whirl, but if anyone wants to race me be my guest, I'm pretty noobish when it comes to android/linux, but I'll give it my best.
Lemcott said:
if i were to patch this after flashing on Jamezelle's sense-abloe 2.0, would it look just like the normal htc lock screen just transparent? or will it look like sense-able's lock screen but transparent?
Click to expand...
Click to collapse
99.9% sure your senseable lock would be in-tact, just transparent. since your senseable lock's graphics are stored in com.htc.resources.apk and this is only a change to your HtcLockScreen.apk
Running Ivan's 0.8T2, works like a charm. Thanks!
For all of those confused on how to install this, you simply unzip HtcLockscreen.zip on your computer, follow the instructions in the first post, then you:
Code:
adb remount
adb push HtcLockScreen.apk /system/app
adb reboot
and when your phone boots back up, you'll be looking at a shiny new transparent lockscreen.
Arcalyth said:
Running Ivan's 0.8T2, works like a charm. Thanks!
For all of those confused on how to install this, you simply unzip HtcLockscreen.zip on your computer, follow the instructions in the first post, then you:
Click to expand...
Click to collapse
NOTE!: the code is case sensitive, make sure you capitalize as follows:
Code:
adb remount
adb push HtcLockScreen.apk /system/app
adb reboot
When I try this I always get the nexus 1 lock screen. I'm running Ivan's latest build.
I will try again on a fresh flash since I have been messing with stuff.
Edit: OK, fresh flash without wiping allowed me to change to the Transparent Lock Screen. Thanks gohamstergo.
btw, I have no idea what I changed to not allow this mod.
@silver: not sure but youre not the only one with the issue. no idea what causes it. seems rare tho
AWW, I thought I was special.
But, If anyone ever needs any "rare issues or bugs" found....
Thanks for posting this!
Would anyone consider making a "lockscreen" that is nothing BUT a photo/walpaper?
No clock, no arc, nothing?
Maybe just a "walpaper" or photo?
Or even better- Truly Transparent!
That would be cool!
TheAtheistReverend said:
Thanks for posting this!
Would anyone consider making a "lockscreen" that is nothing BUT a photo/walpaper?
No clock, no arc, nothing?
Maybe just a "walpaper" or photo?
Or even better- Truly Transparent!
That would be cool!
Click to expand...
Click to collapse
If read the "advanced" directions in the OP, it basically explains how to do this, even though he was trying to tell you how to AVOID doing that. but I agree, I'd like it too. It would almost be like a security feature cuz only you would know where to swipe to unlock
is it possible to change the resolution of htc legend..........i tried lcd density but no use ...i am using azure cyanogen mod 6.....
i tried to edit the build pro..but no use
some one help me.......
Change Your Screen Resolution on HTC Evo 4g
I have successfully done this now. Remember that we don't have root in the same way that the EVO 4G does.
So:
Using any file manager that can read the / partition of your phone find and copy "/system/build.prop" onto your SD card.
Now copy the file to your desktop, and take a backup of that file too.
Open notepad and make sure word wrap is on, then open build.prop in notepad
Edit the required value (I chose 120), save and copy the file to your ADB/tools directory
Reboot your phone into clockworkMOD recovery, and connect your phone to the PC. Also go into the partitions menu of ClockworkMOD and click "mount system"
Open up ADB, and run "adb devices" to make sure the phone is connected and everything is working
Run these commands in this order:
adb push build.prop /sdcard/build.prop
adb shell
mount -o remount,rw /dev/block/system /system
cp /sdcard/build.prop /system/build.prop
Then reboot your phone.
Let me know if this helps
Also, for other readers:
Make sure you read the post that is linked to in the above post, otherwise my instructions might not make sense... I might edit it later when I have time
@TheGrammarFreak
What is the resoultion of your screen now?
qzem said:
@TheGrammarFreak
What is the resoultion of your screen now?
Click to expand...
Click to collapse
I dunno how I'd work it out, sorry.
Ah...
I think I've found the first of many flaws with this, and it was mentioned in the EVO 4G post. Some apps ignore this and use the old resolution, and thus don't fill the screen (see attachment)
As you can the the status bar goes a lot wider than the app. The status bar is the full width of the screen.
Other problems arise too, a reinstall of the app doesn't help, and some apps just end up completely screwed...
qzem said:
@TheGrammarFreak
What is the resoultion of your screen now?
Click to expand...
Click to collapse
The resolution is the same - HVGA (pixels are hardware). You only change the dpi value which means that more things will fit to your screen but it will appear coarser than before.
grandioso said:
The resolution is the same - HVGA (pixels are hardware). You only change the dpi value which means that more things will fit to your screen but it will appear coarser than before.
Click to expand...
Click to collapse
Cool, thanks grandioso
On a slightly different note I've found that changing the value to 130, and using the 5 icon rows feature of launcher pro, is quite nice.
grandioso said:
The resolution is the same - HVGA (pixels are hardware). You only change the dpi value which means that more things will fit to your screen but it will appear coarser than before.
Click to expand...
Click to collapse
Thanks for clearing that .
There are some problems, but if you want to try it out, you can flash the update.zip I've just made.
160lcd.zip takes you back to default and 120lcd.zip makes your screen resolution higher.
@Briix
Can you make update for 130, like TheGrammarFreak suggested
I'd make one but I'm currently struggling to sign my .zip
EDIT:
Done it, just testing then I'll upload. I also notice that ROM Manager is one of the apps that ends up being screwed by this mod...
EDIT 2:
Wow, lots of edits. Anyhoo, 130lcd right here:
really nice
TheGrammarFreak said:
I have successfully done this now. Remember that we don't have root in the same way that the EVO 4G does.
So:
Using any file manager that can read the / partition of your phone find and copy "/system/build.prop" onto your SD card.
Now copy the file to your desktop, and take a backup of that file too.
Open notepad and make sure word wrap is on, then open build.prop in notepad
Edit the required value (I chose 120), save and copy the file to your ADB/tools directory
Reboot your phone into clockworkMOD recovery, and connect your phone to the PC. Also go into the partitions menu of ClockworkMOD and click "mount system"
Open up ADB, and run "adb devices" to make sure the phone is connected and everything is working
Run these commands in this order:
adb push build.prop /sdcard/build.prop
adb shell
mount -o remount,rw /dev/block/system /system
cp /sdcard/build.prop /system/build.prop
Then reboot your phone.
Let me know if this helps
Also, for other readers:
Make sure you read the post that is linked to in the above post, otherwise my instructions might not make sense... I might edit it later when I have time
Click to expand...
Click to collapse
thanks man its working...........
Has anyone tried GrammarFreak's zip ?
Are there any problems with it ? Is it worth the effort ?
Do I have to wipe for this to work ?
Explicitly my zip? Or any of the zip's in this thread?
No wipe is needed.
Also, this method is inherently flawed. Some apps just don't use the edited resolution. Unless a way can be found to force these apps to scale up then there will always be ugly moments.
One of the things that I've found to not work is the HTC-IME mod. So is it worth it? That for you to decide... Lol
Sent from my Legend using XDA App
I mean yours or Briix' - are there any others ?
I don't want to edit the file manually if I don't have to
grandioso said:
Has anyone tried GrammarFreak's zip ?
Are there any problems with it ? Is it worth the effort ?
Do I have to wipe for this to work ?
Click to expand...
Click to collapse
Yup.. Tried.. working like a charm..
-------------------------------------------------------------------
Could you make a 140 and a 110 .. Just to try and see the result!?
I'll gladly test them both..
whitetigerdk said:
Yup.. Tried.. working like a charm..
-------------------------------------------------------------------
Could you make a 140 and a 110 .. Just to try and see the result!?
I'll gladly test them both..
Click to expand...
Click to collapse
I'd love to, but I can't at the moment, I'm at school and didn't bring my laptop. Unless someone beats me to it I'll make one in about an hour and a half; when I'm home.
I did try 140 myself but I didn't think it was worth it. I use 5 icon rows in launcher pro and the widgets started overlapping again. Like they did in the default resolution.
Sent from my Legend using XDA App
I'll wait..
Would be great though if WF & Clock Widget (The Sense look Clock) would adapt to new screen and fill it out..
Totally sweet indeed..
Yeah, if I knew more about android I'd look into forcing apps to scale up. I'm not sure if it's even possible, but hey.
Sent from my Legend using XDA App
I shall take no credit for any of this. Smartsreenath first put me onto the idea, and pretty much anyone if this forum could've managed it. I just had the time to do it all.
Woo! Snakehult, being a genius, has made a clever little zip that uses proper scripts to just change the required value, instead of the whole file. So! Instead of me making an insane number of zips every time ROMs are updated use these instead. Cheers Snakehult!
Attached is a zip file with a whole lot of flashable zips in it. Don't flash the zip you download, extract that one somewhere and look inside
How to use:
Download the attached zip file, and extract it to somewhere on your computer. Inside the zip are a bunch of folders, each folder named after a ROM for the HTC Legend. Navigate into the folder that shares the name of whatever ROM you are using and inside you will find 6 zip files. These zips are flashable. The the zips are names thus: xxx.zip, where xxx is a number. The lower the number, the higher the apparent resolution. Choose a zip, copy it to your SD card and flash it like any other zip. To revert back to how it was simply flash the "160.zip". This just flashes a completely un-modified version of build.prop for your ROM. Make sure you only use the zips form the correct folder for your ROM, or funny things *might* happen.
More info:
By editing the build.prop file it is possible to increase the dpi of an Android device. This essentially scales everything down, so you can fit more on the screen. This is especially nice for browsing the market and the internet; as well as improving, in my opinion, the overall Android experience. The lower the number in the name of the zip, the higher the apparent resolution. It's worth noting that this does *not* change the actual resolution of the Legend; it's still a HVGA device. So you still can't install apps designed for bigger, more powerful phones, like the HTC Desire or Nexus One. This is a somewhat flawed way of achieving this effect, and can have some ugly side effects:
Some apps simply don't scale
HTC-IME mod ends up screwed
Games *can* be rendered unplayable, but not always. Often the menu is the worst affected part.
A work around to fix a number of issues is to disable the built in compatibility mode of Android, and if I knew a way to do this through a zip, rest assured that I would. It'd save me having to explain how to do it. Alas, I don't know how, so here's how:
In your ROM look for an app called "Spare parts". If it's not there look for it in the market. If you open that app and scroll down to the bottom you will find a checkbox option for "Compatibility mode". Ensure that this is *un-checked*, then reboot. Most issues will be resolved. As I learn more about Android I shall keep an eye out for a way to force apps to scale correctly, and if I ever find one I'll update these.
I have also tried values higher than usual, just for kicks. I don't expect them to be useful, nor will I make actual zip files for them, but I went all the way up to 200; and it felt like I was using an HTC wildfire: everything was really quite cramped.
My personal favourite setup is as follows:
CM 6.1, with a 768MHz overclock
My "lcd-density" (this MOD) set to 130
Launcher Pro Plus with 5 icon rows
Below is a paste of what was the first post (when I was just trying to fix a ****-up on my part), and is now here for reference. It has all of the original build.prop files attached.
Attached is a .zip file, which you will need to extract somewhere. It's not for flashing. Within this zip are several folders, each containing a "build.prop". You'll notice that each folder is named after a ROM: Azure, NeonMOD etc. The "Based-on-stock" folder should cover these ROMs:
[ROM] Based on Official WWE_2.03.405.3 ROM + A2SD [Rev 03 - released]
[ROM] UPDATED Almost Stock Legend HTC WWE 2.03.405.3 Radio 7. 08.35.21
You'll need to use ADB to push these files, as I haven't had time to make flash-able zip's for them yet
Instructions:
1. Extract the zip to a suitable directory, and locate the appropriate build.prop
2. Copy the build.prop to your AndroroidSDK/tools folder
3. Reboot your phone into ClockworkMOD recovery and navigate the the "Partitions menu", then click "mount /system"
4. Connect your phone to the PC and start CMD/a terminal window in your AndroidSDK/tools folder
5. Run the command "adb devices" to ensure that the ADB server is running, and that the PC has detected your device correctly
6. Run these commands in this order:
adb push build.prop /sdcard/build.prop
adb shell
mount -o remount,rw /dev/block/system /system
cp /sdcard/build.prop /system/build.prop
This will put your resolution back to default, but should fix everything else too. If you still want a higher resolution then follow the guides in posts 1 and 2 of the other thread. This one.
If you can't use ADB for whatever reason you'll just have to wait it out until myself or someone else create proper, flash-able, fixes. I have done this to try and quickly rectify the issue; assuming, of course, that most people in this forum can use ADB
I will make proper zips, but it's getting late for me...
Click to expand...
Click to collapse
hi
here is a zip for neonmod 0.21 with 135lcd, flashed it on my legend today with rom manager
Wow do we have a lot of ROMs...
Anyhoo, I am currently working on appropriate flashable zips for each ROM, and each ROM will have the following versions:
110
120
130
140
150
160 (original)
I'm doin' 'em as fast as I can..
EDIT:
Current thoughts:
All build by Ali Ba have nice, short build.prop files. The current record for the longest one it held by MyTouch Legend...
TheGrammarFreak said:
Wow do we have a lot of ROMs...
Anyhoo, I am currently working an appropriate flashable zips for each ROM
Click to expand...
Click to collapse
Awesome!
All our lovely ROMs are actively being used, and its great.
Thx for all hard work!
No worries, I hope I haven't missed one
Now to sign 50 60 zip files...
EDIT:
DONE! All finished. I really hope they work. I can't test them all, but there is no reason why they won't work. Lemme know either way.
nice job
thanks bro
nice
spare parts is also in neonmod
xennr3 said:
nice
spare parts is also in neonmod
Click to expand...
Click to collapse
Cool, and you can turn compatibility mode off?
TheGrammarFreak said:
Cool, and you can turn compatibility mode off?
Click to expand...
Click to collapse
sure
1234
TheGrammarFreak said:
Cool, and you can turn compatibility mode off?
Click to expand...
Click to collapse
thanks for your work! i just tried 130 dpi and it seems really good.. i'll try also others zip asap!
yes with compatibility mode off all softwares i tried work really well!
xennr3 said:
sure
1234
Click to expand...
Click to collapse
Cool, thanks for the info. I'll update the OP when I'm home
Sent from my Legend using XDA App
Wow, really cool mod Love it!
Good job!
Cool, glad you like it
Just flashed 130 for SpeedLegend and it worked like a charm
HTC_IME works here (this isnt the mod)
images dont look so good anymore and stuff, but alright
works fine
edit; TBH I find the 140 to be 'more' compatible overall, and show a better picture (ive tried all the flashables)
thats besides the orgnal setting btw, it gives the best picture by far.
Im on the same DPI and rom as you TheGrammarFreak. works great. Too bad there is no function for more icons on the homescreens with LauncherPro...
SimDroid said:
Im on the same DPI and rom as you TheGrammarFreak. works great. Too bad there is no function for more icons on the homescreens with LauncherPro...
Click to expand...
Click to collapse
Yeah it does. On your homescreen press menu, then preferences. In advanced options there is something for it.
Sent from my Legend using XDA App
i glad to hear that someone like you got the idea from my thread........good work ...........and nice job.....you will get all help from me and from my friends
FOLLOW ME http://smartsreenath.blogspot.com/
TheGrammarFreak said:
Yeah it does. On your homescreen press menu, then preferences. In advanced options there is something for it.
Sent from my Legend using XDA App
Click to expand...
Click to collapse
yeah, that is for 5 rows on a screen, but you still can't have 5 icons on a row... That's what I want. I tried ADWLauncher again, but it feels so god damn slow.
Ummm, I have 5x5 icons on my desktop with the stock ADW launcher. Just check out "Settings > ADW > Screen prefs > Desktop cols/Desktop rows"
Is it possible to get bootsounds working on my
Cm7 hero. I have tried a few zips I have found.
I get errors every time
Any help would be appreciated
Too busy to post it. It works. I have the files. Pm me and ill help later.
I would actually like to know how to do that as well.
OK here it is. I don't know if this works on sense, but it does work on AOSP based ROMs. Take the mp3 below and put it in /system/media, it's the THX movie bootup sound (I think). You can change it to whatever you want later. Take the sh file and put it on the root of your sd. Once both of those things are done, do this EXACTLY:
-open terminal emulator
-type "su" press enter
-type "cd /sdcard" press enter
-type "sh bootsnd.sh" press enter ONLY ONE TIME !!!
-type "reboot"
EDIT: no quotes obviously...
If you follow this, it will work. If you get smart and change it, or press enter twice where it says once, it will hose your /system. Oh, you should probably NANDROID FIRST.
Peace.
http://dl.dropbox.com/u/5669105/bootsnd.sh
http://db.tt/Jpn5NZ1 - thx sound
OMG! Yes! I love messing with terminal emulator. It makes me feel smarter than I actually am, lol. Thanks for the quick response.
Quick question - You said we should be able to change it afterwards so does that mean after we follow the steps you so graciously provided we should then be able to find an .mp3 somewhere in /system that can simply be replaced with another .mp3? for example maybe in /system/media/audio......?
You can use any mp3 you want.
il Duce said:
OK here it is. I don't know if this works on sense, but it does work on AOSP based ROMs. Take the mp3 below and put it in /system/media, it's the THX movie bootup sound (I think). You can change it to whatever you want later. Take the sh file and put it on the root of your sd. Once both of those things are done, do this EXACTLY:
-open terminal emulator
-type "su" press enter
-type "cd /sdcard" press enter
-type "sh bootsnd.sh" press enter ONLY ONE TIME !!!
-type "reboot"
EDIT: no quotes obviously...
If you follow this, it will work. If you get smart and change it, or press enter twice where it says once, it will hose your /system. Oh, you should probably NANDROID FIRST.
Peace.
http://dl.dropbox.com/u/5669105/bootsnd.sh
http://dl.dropbox.com/u/5669105/bootsnd.sh
Click to expand...
Click to collapse
I was gonna try this tonight, because I really want to grab the boot sound from the old Red Dawn Rom......but both of the dropbox links are the bootsnd.sh. If it's not to much trouble could you repost the THX mp3?
Thank you!
Oops. Fixed the mp3 link. I have the sense boot sound if you want. Not sure if it's the same as red dawn but let me know if you want that.
il Duce said:
Oops. Fixed the mp3 link. I have the sense boot sound if you want. Not sure if it's the same as red dawn but let me know if you want that.
Click to expand...
Click to collapse
Thanks for fixing that, and honestly with the 3D about to hit the shelves I'm downloading everything I can, before all these links start coming up 404...... So i'll take whatever's offered.
You know I think that link might be the sense 2.1 sound. I dont know where the thx one went. You could google sounds, change the name to android_audio.mp3 and your good.
il Duce said:
You know I think that link might be the sense 2.1 sound. I dont know where the thx one went. You could google sounds, change the name to android_audio.mp3 and your good.
Click to expand...
Click to collapse
Right you are, that was not the THX sound....Thanks for the guidance though, I now have it working. Off to try and make it work on my Nook. For anyone else trying to do this, the THX sound file you need is here........http://dl.dropbox.com/u/30200380/android_audio.mp3
hockeyfamily737 said:
Right you are, that was not the THX sound....Thanks for the guidance though, I now have it working. Off to try and make it work on my Nook. For anyone else trying to do this, the THX sound file you need is here........http://dl.dropbox.com/u/30200380/android_audio.mp3
Click to expand...
Click to collapse
Awesome, now just need a THX bootscreen
il Duce said:
OK here it is. I don't know if this works on sense, but it does work on AOSP based ROMs. Take the mp3 below and put it in /system/media, it's the THX movie bootup sound (I think). You can change it to whatever you want later. Take the sh file and put it on the root of your sd. Once both of those things are done, do this EXACTLY:
-open terminal emulator
-type "su" press enter
-type "cd /sdcard" press enter
-type "sh bootsnd.sh" press enter ONLY ONE TIME !!!
-type "reboot"
EDIT: no quotes obviously...
If you follow this, it will work. If you get smart and change it, or press enter twice where it says once, it will hose your /system. Oh, you should probably NANDROID FIRST.
Peace.
http://dl.dropbox.com/u/5669105/bootsnd.sh
http://db.tt/Jpn5NZ1 - thx sound
Click to expand...
Click to collapse
i followed these steps exactly and it worked perfectly scared the crap out of my wife with it she didnt know i added sound to the bootup she came running bringing it to me saying its making noises i think something is wrong.
question about changing the sound file does it matter the size or whether its an mp3 or a wma file. just overwrite the one i placed during setup? do i have to rerun the TE commands if i change the sound file? thanks for any answers to this
edit:crap shouldve just edidted my post above with this question sorry
Lol at your wife. You have to use mp3 only, memory size doesn't matter, but I think length does I think you want one that isn't too long, though I never tried a long one. < TWSS lmao. You dont need to redo the commands, unless you flash a new rom. Then you have to redo the whole thing.
sent from a series of tubes.
spleef said:
question about changing the sound file does it matter the size or whether its an mp3 or a wma file. just overwrite the one i placed during setup? do i have to rerun the TE commands if i change the sound file? thanks for any answers to this
edit:crap shouldve just edidted my post above with this question sorry
Click to expand...
Click to collapse
Any mp3 file will work as long as its renamed to android_audio.mp3 and placed in /system/media. I recommended an mp3 file no longer than 20-30 seconds at the most. I'm not sure if wma files will work as that's a windows file.
You do not need to run the commands in TE again unless you nandroid back or possibly wipe everything.
Note: This is just from my own personal experience. I'm not a developer or anything and I take no responsiblilty if you screw up your phone. I hope this helps and don't forget to nandroid first
EDIT: lol sorry Duce, you posted sometime in the middle of me typing on my phone
Sent from my pimped out HERO200 using XDA App
kewl going to play around with it thanks a bunch for the speedy responses
Sent from my HERO200 using XDA App
spleef said:
i followed these steps exactly and it worked perfectly scared the crap out of my wife with it she didnt know i added sound to the bootup she came running bringing it to me saying its making noises i think something is wrong.
Click to expand...
Click to collapse
Thats hilarious! I love it
Incase you get a permission denied error, just do chmod -x bootsnd.sh