Having the dpi set at 160 is driving me crazy, because it breaks some of the apps I use most often. I can reset it to 161, then restart again, but that's a pain, plus it reverts to 160 on every startup.
I'd like to just go back to an older nightly, but the oldest I can find on the changelog is 176. I don't remember where the change took place but I believe it was before that point. So where can I find older nightlies, along with their changelogs?
not so sure about the older nightlies, but you can change the dpi to 161 with blade buddy and the change will not revert back with each reboot.
blade buddy:
https://market.android.com/details?id=com.droidgram.bladebuddy&feature=search_result
Change was 200 if I remember.
---------------------------------
Sent from my LG Optimus V using Tapatalk
If this post helped you don't forget to say thanks!
Dalgrin posted about changing the default DPI to 160 on September 19th. (http://forum.xda-developers.com/showpost.php?p=17683346&postcount=5053)
The next "nightly" was #197 (this was the same time that kernel.org was down). That was the first nightly with the DPI changed by default.
Nightly #177 is still listed on the download page. It is the most recent one with the DPI set to the old, market breaking setting.
If you want to go back, I'd recommend using that one.
Right now, 209 and below no longer appear to be on the server.
200 was the first with the LCD density change. Dal said he was going to do in in his 9/19 post but it did not make it into a nightly until 200. I know because I waited for it before I updated further.
http://forum.xda-developers.com/showpost.php?p=17798039&postcount=5104
Thanks everyone, unfortunately although there is a link to 177, there's no file there. So I'm going to try the blade buddy thing and just have to live with it.
I use the "LCD Density" app to reset mine. I hand-edited /system/build.prop until somebody told me about that app.
Sent from my NookColor using xda premium
Related
I used to run on android 2.2.1 on my hd2.
Yesterday i decieded to give it a go for a 2.3.3 version.
After some problems with CWM i finaly had a few running.
Only thing is, it seems that on every ROM i try the screenlayout has changed. the icons are smaller and de layout is totally diffrent.
I wanted to post a picture of it, but havent got 8 posts yet
As you can see there is mutch space between the icons. i got this problem everywere.
What to do?
Thanks!
p.s. now running on HD2_NDT_ginger_v.4.0
its quite possible that the dpi has been changed from 240 to something else, you will need to edit build.prop to see what the lcd density is or download an app fro mthe market
Richy99 said:
its quite possible that the dpi has been changed from 240 to something else, you will need to edit build.prop to see what the lcd density is or download an app fro mthe market
Click to expand...
Click to collapse
yup. in hyperdroid it set to 167. u can edit icon layout via adw setting
Sent from my HTC HD 2 powered by HYPERDROID
I dont think im running on hyperdroid but on cyonogenmod?
ADW is a app i need to download in market?
I saw a post recently about changing lcd density higher will revert the launcher to Gingerbread looking launcher. I prefer to still have the HC launcher, but thought that a higher lcd density might make the fonts and widgets bigger. I've done this on my Nook Color running CM7, and I just love how it looks at 200. I'm just scared to mess around with the A500 right now without nandroid backup possible. Anybody brave enough to try to change their lcd density yet? Please post some screen shots if you did and at what lcd density you have set it. Thanks!
I changed it to 300 and I changed to 100.
At 100 it looked really great when going through browsers since it gave you a full view though the text was a bit small.
at 300 it looked like a phone with big icons and text
Keep in mind that the settings revert after you reboot
Shigster said:
I changed it to 300 and I changed to 100.
At 100 it looked really great when going through browsers since it gave you a full view though the text was a bit small.
at 300 it looked like a phone with big icons and text
Keep in mind that the settings revert after you reboot
Click to expand...
Click to collapse
How can we change the LCD Density? Is is possible on unrooted device?
modify build.prop... changing the ro.sf.lcd_density value
Sent from my A500 using Tapatalk
minotauri said:
modify build.prop... changing the ro.sf.lcd_density value
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
or you can use this app though it needs SU access
https://market.android.com/details?i...=search_result
tried 170 and 180 but no luck getting the gingerbread ui......
eliteone said:
tried 170 and 180 but no luck getting the gingerbread ui......
Click to expand...
Click to collapse
try 220, should be work
Shigster said:
Keep in mind that the settings revert after you reboot
Click to expand...
Click to collapse
Any idea why the change in settings won't stick after a reboot? It's not convenient to keep on changing the setting since every change also needs a reboot to take effect.
Shigster said:
or you can use this app though it needs SU access
https://market.android.com/details?i...=search_result
Click to expand...
Click to collapse
Can anybody else not click that link? Takes me to exactly the link shown, '...' and all.
Build.prop is overwritten on startup by those pesky iconia devs. Not sure if this can fixed or not, gotta find where it happens.
akkidy said:
Any idea why the change in settings won't stick after a reboot? It's not convenient to keep on changing the setting since every change also needs a reboot to take effect.
Click to expand...
Click to collapse
Changing to anything >200 caused it to fail on boot before it was rewritten. It just hung at the boot logo.
I managed to get in with adb and reset it, but I'd highly recommend against trying this.
_motley said:
Build.prop is overwritten on startup by those pesky iconia devs. Not sure if this can fixed or not, gotta find where it happens.
Click to expand...
Click to collapse
Ugh! I wouldn't bother changing it then, if that's the case. Just too much work rearranging widgets every reboot. Thanks for the information.
bricked 2 iconias this way before cwm was possible.
cant recommend lcd changing.
Whats the best solution or whats recommended?
Greetz
Hiarni
I ran at 120 for a while with very good success until i noticed that 90% of what was on the market wasn't compatible with my device. I had to change it back.
I used "LCD Resolution" which can set at boot and works pretty well.
Anyone know a way past the incompatible market stuff?
Well, from the looks of things, I set mine to "leave it the heck alone"
hiarni said:
Whats the best solution or whats recommended?
Greetz
Hiarni
Click to expand...
Click to collapse
ro.sf.lcd_density=200. This is the best
i think this is the simple way..instead messing with the non working 3rd party app
larrylong said:
ro.sf.lcd_density=200. This is the best
Click to expand...
Click to collapse
just copy the build.prop from your system folder to ur computer..open it in notepad 2
next press crtl+F and type density..
you will find to rows with density written in it..i guess its 75 and 76 row..
on the right side of the density it is showing 240 change it to 200...and 200 is very good...
make it 200 in both the rows..
save it..
copy it in ur sd card...open root explorer in ur device...copy that build.prop file from the sd card folder..
now on the right corner..mount it as R/W...and paste it in the system folder...overwrite and reboot...
ta da...
I have the HD2/Leo and I am running the AmeriCan Andriod's 01/19/2012 release. It's a fresh install, haven't changed any the LCD density before this. It started at 167 but after seeing other threads with similar issues but different devices, I changed it to 160 with no avail. Any Ideas what the LCD density is supposed to be or what I need to do to fix this?
Pulsem70 said:
I have the HD2/Leo and I am running the AmeriCan Andriod's 01/19/2012 release. It's a fresh install, haven't changed any the LCD density before this. It started at 167 but after seeing other threads with similar issues but different devices, I changed it to 160 with no avail. Any Ideas what the LCD density is supposed to be or what I need to do to fix this?
Click to expand...
Click to collapse
It seems for me using both IceCreamToasti 0.6 and Tytungs ICS CM 1.3 that a density of 200 works. But I don't know how this will affect the look of your ROM.
Cheers,
Evil.
theres a hacked market for all densities.(never tried it)
u can also change density to 240 and try(try this first)
here is the hacked market
http://www.sendspace.com/file/mibkww
here is the source
http://forum.xda-developers.com/showpost.php?p=21887239&postcount=18445
Pulsem70 said:
I have the HD2/Leo and I am running the AmeriCan Andriod's 01/19/2012 release. It's a fresh install, haven't changed any the LCD density before this. It started at 167 but after seeing other threads with similar issues but different devices, I changed it to 160 with no avail. Any Ideas what the LCD density is supposed to be or what I need to do to fix this?
Click to expand...
Click to collapse
I would set to 160 and clear market data under settings applications all . Then reboot . Also use a non hacked market with either 160 or 240 dpi . Also changing your build.prop file will help to m
Sent from my HTC HD2 using Tapatalk
Got everything working, the hacked market worked (I think) it wouldn't let me copy it to my system/apps folder and on top of that when I try to install vending.pka it would fail. I'll post my lcd density for other that have this problem in a later post.
For those changing lcd density you have to re-apply your edits after each rom/nightly flash. This method prevents that by overriding lcd density by using a local.prop file in /data.
1) Restore stock lcd density in build.prop: either undo the manual edits you did, or reflash your rom .zip to restore the build.prop to stock
2) Get one of these files based on the density you liked to use: lcd-density-120 or lcd-density-132
3) Rename it to "local.prop" and save it in /data (the root of the /data folder) - if you're on your touchpad then use any file manager to do this, or download to pc and adb push to /data
4) Reboot
This should override the 160 lcd density in /system/build.prop and it will survive rom flashes and incremental updates with goo manager for my nightlies (until you wipe /data obviously). Of course you can reverse the changes by simply deleting the file and rebooting.
You are welcome to try to add other mods using this method but not all will work, and for some reason not all apps/games read local.prop.
The files I posted just contain
"qemu.sf.lcd_density=132" which overrides "ro.sf.lcd_density=132" in /system/build.prop.
You can reply to this thread with other mods that you found to be working.
nice! THanks!
thanks!
has anyone gotten the latest chrome to work work on non-standard dpi's though? Considering it is my most used app, it kinda stopped me from using a dpi other than 160.
hockey4life0099 said:
thanks!
has anyone gotten the latest chrome to work work on non-standard dpi's though? Considering it is my most used app, it kinda stopped me from using a dpi other than 160.
Click to expand...
Click to collapse
Didn't even know that's what the problem was. Dissapointing since 160 dpi make me feel like I'm holding a large phone
Sent from my DROID3 using Tapatalk 2
This is a nice mod, thanks.
murso74 said:
Didn't even know that's what the problem was. Dissapointing since 160 dpi make me feel like I'm holding a large phone
Sent from my DROID3 using Tapatalk 2
Click to expand...
Click to collapse
the iPad2 has actually the same resolution but noone ever mentioned it.
it's awesome how the resolution actually changes but causes a lot of different problems with i.e. folders.
murso74 said:
Didn't even know that's what the problem was. Dissapointing since 160 dpi make me feel like I'm holding a large phone
Sent from my DROID3 using Tapatalk 2
Click to expand...
Click to collapse
yeah, so ive been stuck on 160 for a week now and it's not as bad as i thought it would be. If there is ever a fix id be happy to try it though. Not sure why one version it would work great but on the next it would force close. Maybe the next official update will solve our problems.
Thanks, this definitely saves some time and comes in handy!
Works as it should. I just wish 132 and 120 didn't distort much of the cm9 interface.
Does this work for any build prop entry? I would like to override a ro.ril setting....would I just use qemu.ril, and how can I verify it's working?
Hi,
so after using Android N for about a week, I certainly love the dpi setting the most! I was able to make everything look smaller with a single touch! (well done google). Anyways, truth is, N is still in beta stages, so using it as a daily driver is a NO-NO for now... I went back to Marshallow and now I want to set my phone at the same DPI as that 'small screen size' setting did, the problem is that i cant find the exact value .. tried many different values and it just doesnt feel the same.... so it is simple, would any of you great people happen to know the exact DPI value for the 'small screen size' setting for N so i can change it with an app on marshmallow ? THANKS!
I think it is 484 dpi
Cheers.
MrUnknown said:
I think it is 484 dpi
Cheers.
Click to expand...
Click to collapse
OMG it is thanks a lot mate!