Title says it all. Anyone else experiencing this? Searched all over and no mention of it thus far so maybe it's only me...
Thanks for any help.
Try the free LCD Density for root app in the Market. Change density to to 260, reboot, then change it back to 240 then reboot again. That may help you
This happens on my X also when I change the density in JRummy's over clock app. So I just leave it alone.
Sent from my DROIDX using XDA App
I think I read somewhere on either here or Droid Forums that the Blur dialer does not like any other LCD densities. Maybe someone could confirm this.
Jiggity Janx said:
Title says it all. Anyone else experiencing this? Searched all over and no mention of it thus far so maybe it's only me...
Thanks for any help.
Click to expand...
Click to collapse
I can confirm - the blur dialer absolutely does not accommodate any LCD density changes. I havent heard of any fixes yet.
thepolishguy said:
I can confirm - the blur dialer absolutely does not accommodate any LCD density changes. I havent heard of any fixes yet.
Click to expand...
Click to collapse
Did this start with .320-.340? I was using 210, 217, and/or 220 density on .15 blur without issue. My first thought is the addition of the last called strip on the dialer forced the issue.
Thanks for all the responses/help thus far.
Related
Anyone here try the lcd density changer app it? Are there any flaws to it? It really helps with a big phone loke evo. It can make everything smaller like list so u can see a lot more and also makes the icons smaller so u can fit more. Love it bc with the evo everything is huge
I just use rootexplorer to change my lcd density its permanant and doesnt need an app
I never used any lcd density app but i've heard you have to set it every boot but as i said im not sure
Intresting i dont know i just bought it
With the paid version you dont need to run it again after a reboot. I tried it, I didn't like it cause it made the Widgets all funky.
Can you explain how to do it using root explorer
Also can someone tell me the default for evo. Its either 230 or 240 i think...
jc8081 said:
Also can someone tell me the default for evo. Its either 230 or 240 i think...
Click to expand...
Click to collapse
240
Sent from my blah blah blah blah
jc8081 said:
Also can someone tell me the default for evo. Its either 230 or 240 i think...
Click to expand...
Click to collapse
The default is 240.
Ok thanks now one more question, i changed it back to 240 but my games are still off evrything is still small and some are so off they cant be played. Does anyone know how to fix this? I cleared all data uninstalled reinstalled turned off phone and they r still like this.
And i know its not deleting evrrything bc once i reinstalled it it saved the levals i beat in robo defense. Thanks
jc8081 said:
Ok thanks now one more question, i changed it back to 240 but my games are still off evrything is still small and some are so off they cant be played. Does anyone know how to fix this? I cleared all data uninstalled reinstalled turned off phone and they r still like this.
And i know its not deleting evrrything bc once i reinstalled it it saved the levals i beat in robo defense. Thanks
Click to expand...
Click to collapse
I know there is something funny about using the density changing app, but not sure what. Read the help section about uninstalling.
To change the density with root explorer, go into /system and find the build.prop. Open it in text editor, find where it says default density value, and change it to what you want. Hit menu, save and exit, then reboot and ur good to go. I set mine to 161 for maximum content. Don't try 160, it will screw with ur notification pull down, it will think ur phone is smaller and shrink to half size.
Hey... This thing makes phone calls too!
Thanks but whenever i try to edit it it says rrsd only and i cant save. Anuone know a solution?
phatmanxxl said:
With the paid version you dont need to run it again after a reboot. I tried it, I didn't like it cause it made the Widgets all funky.
Click to expand...
Click to collapse
You need LauncherPro+ or ADW to resize the widgets properly.
jc8081 said:
Thanks but whenever i try to edit it it says rrsd only and i cant save. Anuone know a solution?
Click to expand...
Click to collapse
At the top of the screen, to the right is a button that says "Mount R/W." Press it.
On my Hero, I always used LCD Density Changer, I loved the look, but it doesnt quite work as expected on my Aria. It works fine on CM, but on the Liberated Froyo ROM, no matter what I change the density to, even 159 from 160, my messaging app force closes when I select a message thread. Upping the density doesnt have this problem. Its not a must have thing, rather just a nice little mod in my opinion. Has anyone else had this problem or know of something I could do to try and fix it?
lstat said:
On my Hero, I always used LCD Density Changer, I loved the look, but it doesnt quite work as expected on my Aria. It works fine on CM, but on the Liberated Froyo ROM, no matter what I change the density to, even 159 from 160, my messaging app force closes when I select a message thread. Upping the density doesnt have this problem. Its not a must have thing, rather just a nice little mod in my opinion. Has anyone else had this problem or know of something I could do to try and fix it?
Click to expand...
Click to collapse
whoa I dunno what this is or what it's supposed to do but it definitely fuxed ish up on my aria...dunno how you would go about fixing that.
The application allows you to change the density of the phones screen, much like changing the resolution on a computer. Im just looking for a fix for the force close on messages. A work around is a third party sms app, but I am not a real big fan of the ones on the market. I like the stock app because it looks uniform and goes with the rest of the phone.
lstat said:
The application allows you to change the density of the phones screen, much like changing the resolution on a computer. Im just looking for a fix for the force close on messages. A work around is a third party sms app, but I am not a real big fan of the ones on the market. I like the stock app because it looks uniform and goes with the rest of the phone.
Click to expand...
Click to collapse
Well this has nothing to do with the messages. How is it supposed to fix it?
Sent from my HTC Liberty using XDA App
You dont seem to understand, this application, when active, is what is causing the messages app to force close. That is what im looking for a fix for. When the app isnt active everything is fine, when I use it to change the density I get the force close. I need a fix for the force close *Caused by the app*
Aren't the aria and the hero the same resolution? If they are, the messaging app should work.
kevina90 said:
Aren't the aria and the hero the same resolution? If they are, the messaging app should work.
Click to expand...
Click to collapse
The problem isn't the messing app. Its the pixel density app that is causing the message app to FC due to some incompatability issues. When the density app isn't working he said the messaging app works fine, the stock messaging app on top of that.
Try searching the general android development forums under apps and games for various sms apps, theres a few over there.
Sent from my cm6.1 Aria using XDA App
I will try that. I have not been a hug fan of any on the market. It looks like I wont have the phone much longer though, I am trading up to a Desire. I would still love to figure out this problem though..Thanks for pointing me in the right direction Callmearia
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?