I tried using the usual programs like LCD Density Changer but no matter what value I choose, nothing happens after the device restarts. Any ideeas?
albireox said:
I tried using the usual programs like LCD Density Changer but no matter what value I choose, nothing happens after the device restarts. Any ideeas?
Click to expand...
Click to collapse
this could help you http://forum.xda-developers.com/showthread.php?t=1063739
albireox said:
I tried using the usual programs like LCD Density Changer but no matter what value I choose, nothing happens after the device restarts. Any ideeas?
Click to expand...
Click to collapse
maybe font changer can help?
http://forum.xda-developers.com/showthread.php?t=744363
it has a section for you to change the density. However I have not tried this myself....
Just edit the density in the build.prop manually. It does work but i don't really like it.
Related
Anyone know why the screen density you set (either using LCD Density or modifying build.prop directly) doesn't keep when rebooting? TIA
What do you think the optimal density is and does it make a noticeable difference?
I like 140 - makes the screen look very nice and smooth. All apps seem to run fine, with the "stretch apps" fix.
ethanwinkley said:
I like 140 - makes the screen look very nice and smooth. All apps seem to run fine, with the "stretch apps" fix.
Click to expand...
Click to collapse
what "stretch apps" fix do you mean? are you talking about messing with the manifest file the .apk file?
post pics please!
Sorry, I couldn't remember before... spare parts is the name of the app you need to install. Then, go in there and set Compatibility Mode disabled - reboot. This stretches apps that run in less than full screen.
ethanwinkley said:
Sorry, I couldn't remember before... spare parts is the name of the app you need to install. Then, go in there and set Compatibility Mode disabled - reboot. This stretches apps that run in less than full screen.
Click to expand...
Click to collapse
Have had that running. Does not work on all apps though. I thought maybe I missed something new. Thanks though.
Sent from my HTC HD2 using XDA Premium App
Well..i need to learn something from the devs..!
i like to have my lcd density at 180-190 instead of original 240!
so the question is that if can someone make some fixes about this beacuse when you change the lcd density some games are not fitted well on screen also the dialpad too..and the keyboard become so small...!
its a little request if that can be fixed..or teach me how to make it work!
HD2 at lcd density 167 had original size keyboard,right oriented dialpad on screen..and all games was fitted well on screen!
thank you all guys!
P.S if the thread is not in the right place please moderators remove this elsewhere!!
(Example...try playing FAST AND FURIOUS 5 with 180 lcd density and see the screen size)
Hi, what you do mean by density? Do you mean resolution? Or the threshold when you press the screen???
Sent from my LG-P990 using XDA Premium App
xxdoggyxx said:
Hi, what you do mean by density? Do you mean resolution? Or the threshold when you press the screen???
Sent from my LG-P990 using XDA Premium App
Click to expand...
Click to collapse
hi there..i mean resolution!
you can change it on system/build.prop and change the line where it says lcd density:240 and set on 240 whatever you want and reboot device..!mine is 190!if you dont like it just change again the line to 240 which is the stock resolution...its simple!
Oh, haha.
Anyway, off-topic: where to download fast five for android?
Mine is on 161, the reason of 161 instead of 160 is the notification bar, with setting of 160 it will not go fullscreen, but 161 would.
About small keyboard button issue, I compile my own keyboard from 2.3 gingerbread source a 2.3 stock keyboard, with a larger define on the keys, works well now on my 2X.
About some games are not "resize" to take the different LCD density issue, try install Spare Parts from market, Un-tick "Run in compatibility mode", reboot it "should" help, this is needed on many older/not multiple resolution ready apps.
when changing the density to 161 or 180 the notification bar gets all corrupted, am i the only one having this? i'm on CM7 19
[EDIT] typo, was on 170, but is this normal?
svceon said:
when changing the density to 161 or 180 the notification bar gets all corrupted, am i the only one having this? i'm on CM7 19
[EDIT] typo, was on 170, but is this normal?
Click to expand...
Click to collapse
I am stock ROM 10a, no such problem (corrupted).
I am sure 160, 161, 180, 200, 220, 240 works, the catch on non 161 and 240(default) is the notification do not extent to full width, which is actually common and known issue of mdpi/sdpi/hdpi issues.
can u plz post an image to show how it corrupted?
I've just updated to Gingerbread, rooted using ZergRush and none of the existing LCD resolution changers seem to work, including Bladebuddy. All I get is a blank screen with the button lights on until I reboot when it then goes back to standard settings. Has anyone else seen this problem or have a fix?
TK
tadkingston said:
I've just updated to Gingerbread, rooted using ZergRush and none of the existing LCD resolution changers seem to work, including Bladebuddy. All I get is a blank screen with the button lights on until I reboot when it then goes back to standard settings. Has anyone else seen this problem or have a fix?
TK
Click to expand...
Click to collapse
Have you tried LCD Density Changer. It isn't free however.
Sent from my PG86100 using XDA App
LCD Density changer worked fine under Froyo but it also fails under Gingerbread.
tadkingston said:
LCD Density changer worked fine under Froyo but it also fails under Gingerbread.
Click to expand...
Click to collapse
I have Gingerbread 2.3.3 (my SGT-P1000 came with it) but I have since installed Overcome 7 Series v4.0.0 ROM (GB 2.3.3). I installed LCDDensity for Root by Elviss Kustans and it works just fine for me; however, it doesn't persist after a reset. If I didn't prefer the stock 240 density anyway, I'd use LCDDensity for Root to find my optimum density setting then change build.prop so my desired density would persist. (I wouldn't suggest just changing build.prop without using LCDDensity because if you modified it to an incompatible setting it would be more difficult to recover from.)
aznmode said:
Have you tried LCD Density Changer. It isn't free however.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Try an app from the market called LCD Resolution it also has an option for persistence after a reboot. I used it for some time and it was fine but the resolution change made market insist that my tab was incompatible with half of the apps in market, so I didn't need the hassle and went back to 240
I've been applying assorted mods and V6 Supercharging lately just to see what all I can do before I break stuff. Well, I broke Active Display and I wasn't sure what did it. I restored back to stock 4.4 and noticed that Active Display breaks when I change the LCD density lower than 320 (I'm using 280). After the phone goes to sleep a few times, it wacks out and won't let me unlock it. Shortly after it soft reboots and Active Display no longer works.
Has anyone else noticed this problem and were you able to make Active Display work with the lower density?
d3athsd00r said:
I've been applying assorted mods and V6 Supercharging lately just to see what all I can do before I break stuff. Well, I broke Active Display and I wasn't sure what did it. I restored back to stock 4.4 and noticed that Active Display breaks when I change the LCD density lower than 320 (I'm using 280). After the phone goes to sleep a few times, it wacks out and won't let me unlock it. Shortly after it soft reboots and Active Display no longer works.
Has anyone else noticed this problem and were you able to make Active Display work with the lower density?
Click to expand...
Click to collapse
The thing with changing DPI is it makes the active display go off center, and thus crash sometimes. Change back the DPI of Active Display only to stock 320 while keeping the rest of the system on 280.
anirudh412 said:
The thing with changing DPI is it makes the active display go off center, and thus crash sometimes. Change back the DPI of Active Display only to stock 320 while keeping the rest of the system on 280.
Click to expand...
Click to collapse
I didn't know you could do that. I'm on AT&T 4.4, how would I change just AD to 320? I only know how to change system through build.prop.
I found that if you change certain apps that you have set up to show notifications in active display, if you adjust the DPI you'll lose the pictures for the notification. For example, change the Messaging app to something other than 320. Poof, No more pictures.
---------- Post added at 01:02 AM ---------- Previous post was at 01:01 AM ----------
d3athsd00r said:
I didn't know you could do that. I'm on AT&T 4.4, how would I change just AD to 320? I only know how to change system through build.prop.
Click to expand...
Click to collapse
Used Xposed module. App Settings.
natezire71 said:
I found that if you change certain apps that you have set up to show notifications in active display, if you adjust the DPI you'll lose the pictures for the notification. For example, change the Messaging app to something other than 320. Poof, No more pictures.
---------- Post added at 01:02 AM ---------- Previous post was at 01:01 AM ----------
Used Xposed module. App Settings.
Click to expand...
Click to collapse
Thanks. I must have missed that one.
d3athsd00r said:
Thanks. I must have missed that one.
Click to expand...
Click to collapse
Let me know if that works. I've been wanting to change the stem DPI also
natezire71 said:
Let me know if that works. I've been wanting to change the stem DPI also
Click to expand...
Click to collapse
Will do. I might have to take a break from work to run out to my car and try this.
d3athsd00r said:
Will do. I might have to take a break from work to run out to my car and try this.
Click to expand...
Click to collapse
Man, it's late for work. You should take a break
natezire71 said:
Man, it's late for work. You should take a break
Click to expand...
Click to collapse
I work night shift, and we can't have our phones in the building. :sad:
natezire71 said:
Man, it's late for work. You should take a break
Click to expand...
Click to collapse
So something is up with my settings. When I click on "security", settings crashes. Looks like I'm going to have to wipe
natezire71 said:
Let me know if that works. I've been wanting to change the stem DPI also
Click to expand...
Click to collapse
d3athsd00r said:
Will do. I might have to take a break from work to run out to my car and try this.
Click to expand...
Click to collapse
Download the newest version from here
http://forum.xda-developers.com/showthread.php?t=2554049
While in recovery, change Active Display to 320 in App Settings module, build.prop to 280 (or whatever number you desire). Reboot, profit
Also, if anyone wants tablet mode for certain apps (I use mine on GMail, go to App Settings module, select the particular app, change DPI to around 220, and DP to 800X1280)
So I finally got around to refreshing my phone. 280 in build.prop with 320 set for active display makes the phone right where I want it with resolution and size
My new favorite phone of all time. And I don't even have AOKP, and never will
Sent from my XT1058 using XDA Premium 4 mobile app
d3athsd00r said:
So I finally got around to refreshing my phone. 280 in build.prop with 320 set for active display makes the phone right where I want it with resolution and size
My new favorite phone of all time. And I don't even have AOKP, and never will
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can you please explain how u did it? I'm lost.. Thanks!
varun.gid said:
Can you please explain how u did it? I'm lost.. Thanks!
Click to expand...
Click to collapse
You have to install Xposed and the module App Settings. Once you've rebooted and Xposed is active, go into App Settings and set the DPI on Active Display to 320. Then set your DPI in build.prop to whatever you want. Reboot and enjoy.
Sent from my XT1058 using XDA Premium 4 mobile app
Hi all,
I've just replaced my screen on my Nexus 6, boots fine but when Android starts to load the resolutions/screen is all messed up.
Same issue here https://www.reddit.com/r/nexus6/comments/3grwqv/lcd_screen_replacement_update/
I've re-imaged as well.
Screenshots here
http://imgur.com/a/1jyFy
Any help would be much appreciated
Stu
I would return it and ask for a replacement. Where did you purchase the replacement screen?
blkcliostu said:
I've just replaced my screen on my Nexus 6, boots fine but when Android starts to load the resolutions/screen is all messed up.
Click to expand...
Click to collapse
Just guessing
1. The refresh rate is wrong, or the display is too slow.
2. Resolution issue.
You could reflash the current factory image to make sure the system defaults are set.
When that does not solve the problem you could try to root the phone and change the value of the LCD-density to the value equal to the native reslution. The idiot Google default is 560 dpi, but the native resolution of the N6 AMOLED display is 493 dpi. The value is listed in the text file build.prop.
There is also an app called Build.prop editor.
You need to be rooted.
If your new screen have a different native resolution you need to use that value first.
Of course you may experiment with other values.
NLBeev said:
Just guessing
1. The refresh rate is wrong, or the display is too slow.
2. Resolution issue.
You could reflash the current factory image to make sure the system defaults are set.
When that does not solve the problem you could try to root the phone and change the value of the LCD-density to the value equal to the native reslution. The idiot Google default is 560 dpi, but the native resolution of the N6 AMOLED display is 493 dpi. The value is listed in the text file build.prop.
There is also an app called Build.prop editor.
You need to be rooted.
If your new screen have a different native resolution you need to use that value first.
Of course you may experiment with other values.
Click to expand...
Click to collapse
This sounds promising, will give it a go.
blkcliostu said:
This sounds promising, will give it a go.
Click to expand...
Click to collapse
And . . . don't forget it could be a hardware issue,
The connector display to phone.
Dirt, oxidised or touched. Connection not exactly fitted.
Just a quick update on this,
So I rooted and amended the DPI but still no good. It looks like its a faulty display.
Thanks for the pointers.