Database Users

LCD Density Changer on Liberated

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

Anyone changed lcd density yet on their A500?

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...

[MOD] [local.prop] [CM9/AOSP ROMS] Persistent lcd density change

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?

Who has changed DPI?

Who has changed their DPI?
What have you changed it to?
Have you encountered any issues?

vinokirk said:
Who has changed their DPI?
What have you changed it to?
Have you encountered any issues?
Click to expand...
Click to collapse
If you change DPI even without rooting Android Pay won't work

what's the stock DPI? 240 I hope

Changed mine as soon as I got it. Everything is too big with the default DPI so using 400 atm, I tried 360 but it changed into tablet mode.

Born<ICs;4924608 said:
what's the stock DPI? 240 I hope
Click to expand...
Click to collapse
Good luck reading the display at 240 dpi. The lowest I used on my Nexus 6 was 400 and that's on a bigger screen

Pilz said:
Good luck reading the display at 240 dpi. The lowest I used on my Nexus 6 was 400 and that's on a bigger screen
Click to expand...
Click to collapse
Oh sorry, don't have phone. 240 is stock font on my tablet so I don't know

Born<ICs;4924608 said:
Oh sorry, don't have phone. 240 is stock font on my tablet so I don't know
Click to expand...
Click to collapse
Well yeah on a tablet its a different story because the screen is a lot bigger. It's the DPI bkt a font which is how everything is scaled

I know nothing about changing dpi, but can it be done without root?
Sent from my Nexus 6P using Tapatalk

Davidinks said:
I know nothing about changing dpi, but can it be done without root?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Yes if you did a little research you would have found that answer.
You need to have ADB on your computer then run these commands:
adb devices (make sure it finds your phone and you allow it to connect by hitting ok on your phone when prompted)
adb shell
wm density xxx && reboot (the xxx refers to the new density you want. The 6P stock is probably at 560DPI)

Pilz said:
Yes if you did a little research you would have found that answer.
You need to have ADB on your computer then run these commands:
adb devices (make sure it finds your phone and you allow it to connect by hitting ok on your phone when prompted)
adb shell
wm density xxx && reboot (the xxx refers to the new density you want. The 6P stock is probably at 560DPI)
Click to expand...
Click to collapse
I found that by doing this, it caused some issues. Mainly, on my Nexus 6, it caused some image problems throughout the Play Store. But if I changed the DPI in the build.prop, those issue did not exist.

Stock is 560. I changed mine to 400 with no adverse affects. Although I immediately change the DPI on any device I use.

388 is the lowest you can go before tablet mode change.
And I changed mine without root with a simple adb command:
Adb shell wm density 388

Is there a tool that can change the DPI rather than us having to do the script?
I have my Nexus 6P connected to my PC with the short cable it came with and when I do ADB Devices it comes up with nothing at all. In Windows Devices it registers that it knows it is a Nexus 6P but i cannot browse to the files on the phone or anything So i am not certain why the phone is not showing up on the PC.
**Update**
Figured out why it was not showing up on my PC and I was able to get it working via the PC rather than using an app. Thanks folks

littleneutrino said:
Is there a tool that can change the DPI rather than us having to do the script?
I have my Nexus 6P connected to my PC with the short cable it came with and when I do ADB Devices it comes up with nothing at all. In Windows Devices it registers that it knows it is a Nexus 6P but i cannot browse to the files on the phone or anything So i am not certain why the phone is not showing up on the PC.
Click to expand...
Click to collapse
use https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi&hl=en

Thanks for the quick link but is there a tool that does not require root?

stuff said:
I found that by doing this, it caused some issues. Mainly, on my Nexus 6, it caused some image problems throughout the Play Store. But if I changed the DPI in the build.prop, those issue did not exist.
Click to expand...
Click to collapse
it does change it system wide and if I'm not mistaken that include the build prop as well. I used this on and the build prop edit on different occasions and never had any issues other than Android Pay not working with a custom DPI.

I have changed the DPI though build.prop and Google search is gone from the recents menu. I've tried flashing the factory image and a new rom and still can't get the bar to appear. I've used 380,400,420, 480 and I'm at 500 now.

osi13 said:
I have changed the DPI though build.prop and Google search is gone from the recents menu. I've tried flashing the factory image and a new rom and still can't get the bar to appear. I've used 380,400,420, 480 and I'm at 500 now.
Click to expand...
Click to collapse
Does it come back when you say the DPI to stock?

@Pilz will changing to other "stock" dpi, for example 480, allow android pa pay continue to function?

I've set the DPI to 440 using the ADB method and nothing seems to be broken so far.
Looks so much better than the default.
Not able to test Android Pay as it's not available in my country yet.

Lowest DPI for G4

Hi all.
What is the minimum DPI for the G4 using stock LG software?
For the G3 it was 528. I see 540 mentioned here a bit so wondering if on G4 the lowest DPI is 540 or 528?
TIA

I'm using 538 at the moment. I read that it was the lowest possible.

530 was the lowest for me.
I use App Setting Xposed module to set non LG apps to lower values.

theKramer said:
Hi all.
What is the minimum DPI for the G4?
For the G3 it was 528. I see 540 mentioned here a bit so wondering if on G4 the lowest DPI is 540 or 528?
TIA
Click to expand...
Click to collapse
I use 520 since a while. See screenshot.
.

steadfasterX said:
I use 520 since a while. See screenshot. .
Click to expand...
Click to collapse
Hi.
I forgot to specify on stock LG software. I'm gonna wait a little while before unlocking the bootloader. Make sure everything is working as it should before destroying my warranty

WMaddler said:
530 was the lowest for me.
I use App Setting Xposed module to set non LG apps to lower values.
Click to expand...
Click to collapse
If I get issues with apps crashing, I can still change the DPI via ADB, can't I ? There's nothing that prevents that right?

theKramer said:
If I get issues with apps crashing, I can still change the DPI via ADB, can't I ? There's nothing that prevents that right?
Click to expand...
Click to collapse
Yes, you should able to.
What I usually do is setting LG apps DPI to default (640) or anything => 530 using App Settings xposed module, that would put you on the safe side.
---------- Post added at 11:40 AM ---------- Previous post was at 11:39 AM ----------
steadfasterX said:
I use 520 since a while. See screenshot.
.
Click to expand...
Click to collapse
Which app is that?

maddler said:
Yes, you should able to.
What I usually do is setting LG apps DPI to default (640) or anything => 530 using App Settings xposed module, that would put you on the safe side.
Click to expand...
Click to collapse
Not a bad idea that

maddler said:
Which app is that?
Click to expand...
Click to collapse
Screen Shift. Requires root of course. Can use per app profiles and let you choose the resolution as well..
.

theKramer said:
Not a bad idea that
Click to expand...
Click to collapse
I know
Been doing that on various devices/ROMS when I had issues with custom DPI

I have never tried Dpi changer like apps. I want to know that does it take phone to bootloop if there is something gone wrong?

xdaorxan said:
I have never tried Dpi changer like apps. I want to know that does it take phone to bootloop if there is something gone wrong?
Click to expand...
Click to collapse
So just as an FYI, the G4 goes down to 528 without issue.
I didnt go any lower since lower than 527 would cause SystemUI errors on the G3 on stock, so G4 is probably the same...

Why would you want to lower the DPI? To safe battery? Does it make any difference?

BrotherZero said:
Why would you want to lower the DPI? To safe battery? Does it make any difference?
Click to expand...
Click to collapse
It makes all elements in the screen smaller, so you can "fit" more into your screen.
Personally I find the text too big with the standard DPI, so I reduce the DPI to make everything smaller.
Its easy to change and only requires a restart to enable. One just needs to be sure to not go below 527, as that will give continuous errors related to SystemUI.
You need adb installed and then you run the following command from a command prompt, where ADB is located:
adb shell wm density 528 && adb reboot
You can change 528 to whatever you want (between 528 and 640) ...

theKramer said:
It makes all elements in the screen smaller, so you can "fit" more into your screen.
Personally I find the text too big with the standard DPI, so I reduce the DPI to make everything smaller.
Its easy to change and only requires a restart to enable. One just needs to be sure to not go below 527, as that will give continuous errors related to SystemUI.
You need adb installed and then you run the following command from a command prompt, where ADB is located:
adb shell wm density 528 && adb reboot
You can change 528 to whatever you want (between 528 and 640) ...
Click to expand...
Click to collapse
My only problem is the faulty app drawer button of the stock launcher, on custom dpi's...

steadfasterX said:
I use 520 since a while. See screenshot.
Click to expand...
Click to collapse
do you use that on custom ROM? or stock ? cuz stock will have all LG apps crashing ..

iiD4x said:
do you use that on custom room ? or stock ? cuz stock will have all LG apps crashing ..
Click to expand...
Click to collapse
Custom. RR

polfrank said:
My only problem is the faulty app drawer button of the stock launcher, on custom dpi's...
Click to expand...
Click to collapse
I use Nova launcher, so don't have that issue..