Database Develop

LCD DENSITY screen size

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?

Edits and Tweaks: Build prop, bools.xml

build.prop edits are very easy and useful, they can be applied on stock rom/kernel, i have compiled this from various sources!
For ICS, most of these will be useless
Locate build.prop
got to system/ and find build.prop
Edit with notepad++. Save and overwrite previous file, then change permissions to rw,r,r!
Change the tweaks already present and add new at the end of file!
Change android name and version
ro.build.display.id=Your ROM name
ro.build.version.release=2.3.6 (Android version number)
Decrease boot time
debug.sf.nobootanimation=1 (Disables bootanimation)
ro.config.hw_quickpoweron=true
persist.sys.shutdown.mode=hibernate
dev.bootcomplete=0
Power saving
ro.ril.power_collapse=1
pm.sleep_mode=1
wifi.supplicant_scan_interval=120 (sets wifi scanning interval, can be increased or decreased)
ro.mot.eri.losalert.delay=1000 (might break tethering)
3G Tweaks
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hsdpa.category=10
ro.ril.hsupa.category=5
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.rill.enable.a53=1
Telephony/ring Tweaks
ro.telephony.call_ring.delay=0
ring.delay=0
Proximity (Disable blackscreen issue after call)
mot.proximity.delay=0
ro.lge.proximity.delay=25
Smooth Scrolling
windowsmgr.max_events_per_sec=84(This value is experimental)
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
Disables error reports
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
Force home launcher into memory(use light launchers only)
ro.HOME_APP_ADJ = 1
Render UI with GPU
debug.sf.hw = 1
Disable logcat
logcat.live=disable
dalvik.vm.heapsize = 64m
Note: This value is different for different phones, the value can larger(128m) with larger RAM device, use accordingly!
Phone will not wake up from hitting volume rocker
ro.config.hwfeature_wakeupkey=0
Change LCD density
ro.sf.lcd_density=160
Allows purging of assets to free up RAM
persist.sys.purgeable_assets=1

Locate bools.xml
1. Decompile framework-res.apk
2. Go to res/values and find bools.xml
The file generally contains true and false values for various things, change true->false and false->true to see the magic!
config_sf_slowBlur
Blurred background when power menu comes up
config_automatic_brightness_available
Enable/disable automatic brightness
config_unplugTurnsOnScreen
Screen turns on after unplugging usb
config_animateScreenLights
Keep "true" for CRT OFF animation
config_disableMenuKeyInLockScreen
Disable hard key in lockscreen
lockscreen_isPortrait
Lockscreen in potrait/landscape mode(experimental)
config_batterySdCardAccessibility
Indicate whether the SD card is accessible without removing the battery.
config_carDockEnablesAccelerometer
Control whether being in the car dock should enable accelerometer based screen orientation.
config_deskDockEnablesAccelerometer
Control whether being in the desk dock should enable accelerometer based screen orientation.
skip_restoring_network_selection
If restoring network selection should be skipped The restoring is handled by modem if it is true.

Thanks for this. I have seen these tweaks before but its really nice to have an explanation.
Sent from my SGH-T989D using Tapatalk 2

cwillison94 said:
Thanks for this. I have seen these tweaks before but its really nice to have an explanation.
Click to expand...
Click to collapse
There are a lot of threads on the subject, but would Google any before using them as some work better on other devices or they don't do anything at all.

XperienceD said:
There are a lot of threads on the subject, but would Google any before using them as some work better on other devices or they don't do anything at all.
Click to expand...
Click to collapse
Yes, scrolling speed, vm heapsize, lcd density etc are different for devices!
Sent from mass relay

No point of putting CRT off animation there....

js2892 said:
Allows purging of assets to free up RAM
persist.sys.purgeable_assets=1
Click to expand...
Click to collapse
can u please explain this in details..
thanks
Sent from my GT-S5830i using xda app-developers app

srt99 said:
can u please explain this in details..
thanks
Sent from my GT-S5830i using xda app-developers app
Click to expand...
Click to collapse
allows system to free ram by klling unused assets(programs) !

I once tried to change my phones model via build prop using the same method you wrote up and my phone bootlooped.
Im on n2 sgh-i317.
I fixed it but was wondering what I could have done wrong. Im slowly inching towords getting my feet wet in learning aboutvrom making. Nice thread btw.

freakboy13 said:
I once tried to change my phones model via build prop using the same method you wrote up and my phone bootlooped.
Im on n2 sgh-i317.
I fixed it but was wondering what I could have done wrong. Im slowly inching towords getting my feet wet in learning aboutvrom making. Nice thread btw.
Click to expand...
Click to collapse
u mean the android version or the phone name...
well, irrespective of that, it's quite weird that build.prop edit lead to bootloop...I've edited these things many times and worked normally for me..
if you know how to read logcat etc, u can get a logcat try that to point out the reason for the same!

Thank you, It would be usefull for me.

Thank
Thank u for this post. I will test on my devices.

Before posting things like this, I highly recommend reading this and this just so you know what works and what does nothing (hint: a lot of the tweaks don't work)

pandaball said:
Before posting things like this, I highly recommend reading this and this just so you know what works and what does nothing (hint: a lot of the tweaks don't work)
Click to expand...
Click to collapse
Well, i've read this earlier but forgot to mention about this in OP (i'm still on a GB phone)
Thanks for pointing out, i've edited the OP.
For GB, i've tested them and they work like a charm( with exceptions for some phones).

Thanks for this!

Good Job
Okay

Thanks a lot

Hlpful to me and will be for noobs like me
Really helpful. Should have pressed thanks twice if that was possible

Thanks you
Shadman0 If I help U Pls Give Thanks
My Work http://forum.xda-developers.com/showthread.php?t=2521867

Yea great thread I also am learning android development thanks to you guys. It's cool to know how to modify my devices to my liking.
Sent from my GT-N7105 using Tapatalk

Scaling issues with custom DPI

since I changed the stock DPI to 520(via ADB) , I'm having a couple apps acting out, SwiftKey being the main offender to the point is rendered useless
I tried clearing data/uninstall but it didn't solve the issue. I'm stock rooted. Anyone knows how to fix this?

Change your DPI back. You can't modify system appearance and expect everything to cooperate!

Donjuanal said:
Change your DPI back. You can't modify system appearance and expect everything to cooperate!
Click to expand...
Click to collapse
^^^ This.
I am using 380 dpi and it works great on everything though. 380 puts the phone into tablet mode, but using dpi numbers that are not necessarily tied to anything can cause issues.

EniGmA1987 said:
^^^ This.
I am using 380 dpi and it works great on everything though. 380 puts the phone into tablet mode, but using dpi numbers that are not necessarily tied to anything can cause issues.
Click to expand...
Click to collapse
Dang. That would make everything tiny.

sgloki77 said:
since I changed the stock DPI to 520(via ADB) , I'm having a couple apps acting out, SwiftKey being the main offender to the point is rendered useless
I tried clearing data/uninstall but it didn't solve the issue. I'm stock rooted. Anyone knows how to fix this?
Click to expand...
Click to collapse
Change it to a DPI that Google recognizes ... Multiples of 80 .... Nexus 6 is 560 g3 is 640 etc .... So go back to note 3 which is 480... This also keeps your apps from breaking because some apps won't install when you have a non Google play store DPI
Sent from my Nexus 6 using Xparent BlueTapatalk 2

Skripka said:
Dang. That would make everything tiny.
Click to expand...
Click to collapse
Na, it's perfect size. You get to see so much on screen without everything being so small you cant read it.
nexus6R3plicant said:
Change it to a DPI that Google recognizes ... Multiples of 80 .... Nexus 6 is 560 g3 is 640 etc .... So go back to note 3 which is 480... This also keeps your apps from breaking because some apps won't install when you have a non Google play store DPI
Click to expand...
Click to collapse
Really? I never knew that. Odd that 380 works perfect since that is not a multiple of 80 and it puts the Nexus 6 into tablet mode. Ill try 400 later and see how it is.

EniGmA1987 said:
Na, it's perfect size. You get to see so much on screen without everything being so small you cant read it.
Really? I never knew that. Odd that 380 works perfect since that is not a multiple of 80 and it puts the Nexus 6 into tablet mode. Ill try 400 later and see how it is.
Click to expand...
Click to collapse
The first ones had DPI of 160 then the s2 etc was 240 etc and so forth
Sent from my Nexus 6 using Xparent BlueTapatalk 2

finally got it to work
I used BuildProp Editor and changed the line ro.sf.lcd_density 520 for a 520 DPI
all apps are scaling correctly now no need to go back to those gigantic icons on stock DPI

sgloki77 said:
finally got it to work
I used BuildProp Editor and changed the line ro.sf.lcd_density 520 for a 520 DPI
all apps are scaling correctly now no need to go back to those gigantic icons on stock DPI
Click to expand...
Click to collapse
I was able to change my density using the following ADB shell commands, but it caused a few glitches with apps as others mentioned (Play Store, KeePass2Android keyboard, DSub, etc):
Code:
adb shell
wm density 480
exit
Perhaps those glitches are due to the build.prop still having the default density after applying ADB shell commands:
Code:
ro.sf.lcd_density 560
Next, I tried using a couple of different build prop editing apps, but none actually change the file even though I'm granting root access. Can anyone advise why this might be? Which app specifically did you use (play store link)?
Another method I tried was editing a copy of build.prop using a text editor, then used TWRP to replace the original and set permissions to 644. This caused my phone to get stuck at the colored dots boot screen, and forced me to do a nandroid restore in TWRP.
Seems like this should be easier...any advice?

acc3d said:
I was able to change my density using the following ADB shell commands, but it caused a few glitches with apps as others mentioned (Play Store, KeePass2Android keyboard, DSub, etc):
Code:
adb shell
wm density 480
exit
Perhaps those glitches are due to the build.prop still having the default density after applying ADB shell commands:
Code:
ro.sf.lcd_density 560
Next, I tried using a couple of different build prop editing apps, but none actually change the file even though I'm granting root access. Can anyone advise why this might be? Which app specifically did you use (play store link)?
Another method I tried was editing a copy of build.prop using a text editor, then used TWRP to replace the original and set permissions to 644. This caused my phone to get stuck at the colored dots boot screen, and forced me to do a nandroid restore in TWRP.
Seems like this should be easier...any advice?
Click to expand...
Click to collapse
use https://play.google.com/store/apps/details?id=com.texdroider.texdroider_dpi its so simple.

Wait 380 put's the phone in Tablet mode?
Do apps think it's a tablet then? I'm missing Xposed and Tablet Metrics for making Spotify think I've got a tablet so I can use the skip song feature for free.
---------- Post added at 08:33 AM ---------- Previous post was at 08:02 AM ----------
Oh wow multiples of 80 actually do fix things that break! I had changed my DPI from 560 to 490 and it looked GREAT but various icons inside of apps were broken in the sense that they did not display correctly. I changed my DPI to 480, a multiple of 80 and everything displays correctly now.
I did not know Google used multiples of 80, you would think some of the quick change apps would reflect that or let you know that!
Thanks everyone!

I just tried the adb shell wm density trick to change it to 480
Looks soo much better, but i had the visual problems.
I used custom DPI on my nexus 5 with XPOSED reporting stock DPI to play store to install apps.
I want to use 480 for the nexus 6 , but i have to be rooted to edit.
Using CF autorrot is just as easy as it was for the nexus 5?
I know i need to oem unlock, i havent done that. After unlocking, using CF auto root gives me SU. Will sideloading OTA-s stiil work with root or not?
I read that since lollipop , OTAs dont work if you have any modification. It was working fine with my rooted nexus 5 on Kitkat, but since lollipop something changed.

How do I change the DPI?
---------- Post added at 08:08 AM ---------- Previous post was at 08:08 AM ----------
konaman said:
How do I change the DPI?
Click to expand...
Click to collapse
Never mind I see the app above

I'm having some difficulties with keyboard after changing the dpi to 480 so i am going back to stock dpi.

nexus6R3plicant said:
Change it to a DPI that Google recognizes ... Multiples of 80 .... Nexus 6 is 560 g3 is 640 etc .... So go back to note 3 which is 480... This also keeps your apps from breaking because some apps won't install when you have a non Google play store DPI
Sent from my Nexus 6 using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Where did you get that info? Why multiples of 80? Supposedly the native DPI of the Nexus 6 should be 493 and that's not a multiple of 80
Here's some info I found on reddit
"
The old "decide layout based on DPI" method has been deprecated since Honeycomb. Android guidelines since 3.2 indicate apps should specify a tablet layout based on the minimum resolution-independent "space" it needs to look comfortable -- the system will tell the app if that is actually the case.
Also, 480 dpi is in fact one of the "native" resolutions (XXHDPI) Google advises devs to include alternate resources in. So at 480, the system would not have to scale graphic resources for most apps, possibly making them look better. And no, 480 should not force common apps into tablet layout (source: Note 3 at native 480 dpi).
I do agree that scaling to even numbers is better; the best is to shoot for a multiple of 4 or 8, just because of how resizing algorithms work in general. So if 480 doesn't float your boat, 492 would be a very good alternative."
https://www.reddit.com/r/nexus6/comments/2mwtl9/psa_while_rooted_set_your_n6_to_its_native_493_dpi/

Chad_Petree said:
Where did you get that info? Why multiples of 80? Supposedly the native DPI of the Nexus 6 should be 493 and that's not a multiple of 80
Here's some info I found on reddit
"
The old "decide layout based on DPI" method has been deprecated since Honeycomb. Android guidelines since 3.2 indicate apps should specify a tablet layout based on the minimum resolution-independent "space" it needs to look comfortable -- the system will tell the app if that is actually the case.
Also, 480 dpi is in fact one of the "native" resolutions (XXHDPI) Google advises devs to include alternate resources in. So at 480, the system would not have to scale graphic resources for most apps, possibly making them look better. And no, 480 should not force common apps into tablet layout (source: Note 3 at native 480 dpi).
I do agree that scaling to even numbers is better; the best is to shoot for a multiple of 4 or 8, just because of how resizing algorithms work in general. So if 480 doesn't float your boat, 492 would be a very good alternative."
https://www.reddit.com/r/nexus6/comments/2mwtl9/psa_while_rooted_set_your_n6_to_its_native_493_dpi/
Click to expand...
Click to collapse
That thread is BS. The native PPI (pixels per inch).is 493. DPI is *nothing* to do with PPI. It's something entirely different. DPI is a Scaling method to make things bigger or smaller and has no direct relationship to pixels.
If you have a 5" screen with a 1080p resolution and a 10" screen with a 1080p resolution, they both have the same amount of pixels. So the pixels are much bigger on 10" screen, so all the buttons, icons etc would also be much bigger. This is not making good use of a bigger screens. So android implemented DPI to allow these assets to be scaled. What they are scaled to is completely subjective. There's no hard and fast rule. And they're Scaling within a set resolution so there is no loss of quality either.
Tablet mode comes in at under 300 DPI in later versions I believe.

danarama said:
That thread is BS. The native PPI (pixels per inch).is 493. DPI is *nothing* to do with PPI. It's something entirely different. DPI is a Scaling method to make things bigger or smaller and has no direct relationship to pixels.
If you have a 5" screen with a 1080p resolution and a 10" screen with a 1080p resolution, they both have the same amount of pixels. So the pixels are much bigger on 10" screen, so all the buttons, icons etc would also be much bigger. This is not making good use of a bigger screens. So android implemented DPI to allow these assets to be scaled. What they are scaled to is completely subjective. There's no hard and fast rule. And they're Scaling within a set resolution so there is no loss of quality either.
Tablet mode comes in at under 300 DPI in later versions I believe.
Click to expand...
Click to collapse
Now I'm confused, I didn't know the nexus 6 had a 493 PPI , I used a website to calculate the DPI and went it , and it said 493 and then I read that post, and I even found another web which says the nexus a 493 dpi :/
http://dpi.lv/

Chad_Petree said:
Now I'm confused, I didn't know the nexus 6 had a 493 PPI , I used a website to calculate the DPI and went it , and it said 493 and then I read that post, and I even found another web which says the nexus a 493 dpi :/
http://dpi.lv/
Click to expand...
Click to collapse
I believe its 493 for stock but 560 for aosp. regardless, I enjoy using 532 DPI.

simms22 said:
I believe its 493 for stock but 560 for aosp. regardless, I enjoy using 532 DPI.
Click to expand...
Click to collapse
560 is stock stock stock. Which makes for some funny big icons

Chad_Petree said:
Now I'm confused, I didn't know the nexus 6 had a 493 PPI , I used a website to calculate the DPI and went it , and it said 493 and then I read that post, and I even found another web which says the nexus a 493 dpi :/
http://dpi.lv/
Click to expand...
Click to collapse
That's because those sites are sort of wrong.
Forgetting android for a moment, in the printing industry and by extension, IT, DPI means Dots Per Inch. Literally how many dots in an Inch can be printed on a page. Dots and pixels seem very interchangeable at this point, but even there they are not. When a print designer mocks up a product for review, the pixels in electronic format do not translate to how many dots a printer can print. But because these two ideas are (somewhat incorrectly) seen as synonymous, and essentially a pixel on a screen is technically a "dot", the incorrect terms are used when it comes to screen technology.
All those sites that say the DPI is 493 are wrong. They mean PPI. The link you posted even uses PPI and then interchanges it with DPI. For screen hardware though, it certainly should be PPI.
Where we get even muddier here is that even the android developer documentation uses DPI to reflect the screen density as dots per inch. But android is using this in the software and not in the hardware. DPI is used to tell the OS what screen it has and from that the OS and Apps can decide how they should be displayed. Where as it seems right that the DPI should be set the same as the PPI, this rarely is the case. As we see with the nexus 5 and 6, Google set the DPI in android higher than the PPI because it looks better. So when Google are setting the DPI different to the PPI, we must be careful how we use these terms. The native PPI of the N6 i 493 but the native DPI is 560.
Edit > Further clarifying statement..PPI is a physical characteristic of a screen. DPI is a virtual representation of a screen.

DPI changes

So I am hoping I am not the only one that thanks the stock navigation bar is way too big. On my Oneplus One I had it set pretty small, but it made the phone look better, just didn't make everything look so big.
My question is has anyone changed the DPI on the G4, and if so, what did you use to do that?
I am rooted and have flashed xTreme v1.0.
Thanks.

vng10 said:
So I am hoping I am not the only one that thanks the stock navigation bar is way too big. On my Oneplus One I had it set pretty small, but it made the phone look better, just didn't make everything look so big.
My question is has anyone changed the DPI on the G4, and if so, what did you use to do that?
I am rooted and have flashed xTreme v1.0.
Thanks.
Click to expand...
Click to collapse
You just need an app like build.prop editor, ES File Explorer,or Root Explorer to find and edit text within the build.prop file. It is in the "system" folder. Once you've accessed the build.prop look for ro.sf.lcd_density and change the value from 640 to whatever you like and restart the phone. I've heard that if you go below 540 the camera app and some other apps will not work properly. I set mine to 560. Also, if you have a quickcircle case, that quickcircle app will no longer be aligned correctly as it's set for 640 dpi. Once we get xposed running or if you have a rom that allow for per-app dpi settings, you would be able to easily fix this issue.
Hopefully this helps.

willmayah said:
You just need an app like build.prop editor, ES File Explorer,or Root Explorer to find and edit text within the build.prop file. It is in the "system" folder. Once you've accessed the build.prop look for ro.sf.lcd_density and change the value from 640 to whatever you like and restart the phone. I've heard that if you go below 540 the camera app and some other apps will not work properly. I set mine to 560. Also, if you have a quickcircle case, that quickcircle app will no longer be aligned correctly as it's set for 640 dpi. Once we get xposed running or if you have a rom that allow for per-app dpi settings, you would be able to easily fix this issue.
Hopefully this helps.
Click to expand...
Click to collapse
Did you have any bootloop issues?

vng10 said:
Did you have any bootloop issues?
Click to expand...
Click to collapse
I didn't. Never had any boot loop issues throughout the whole rooting process. I have an ATT H810 model however. Just lurking on the T-Mobile page to see what development comes out now that you all have unlocked bootloader.

willmayah said:
I didn't. Never had any boot loop issues throughout the whole rooting process. I have an ATT H810 model however. Just lurking on the T-Mobile page to see what development comes out now that you all have unlocked bootloader.
Click to expand...
Click to collapse
Okay. THanks. Yeah I tried editing the build.prop and when it rebooted, it was optimizing 32 apps and when it was finishing up, it would reboot. So I am on my backup. Ill see if there are any other options or fixes to this. I just hate how big everything looks at the default.

I used an app someone in one of the G4 threads mentioned called DPI Density changer. I lowered it to 550 seems pretty good to me.

If you're unhappy with the NavBar, you can give Swipe Navigation [Root] a try. It's GREAT on the G4, the Nexus 6 and other onScreen Nav based devices. I have it set with the NavBar completely hidden and it has an outstanding swipe gesture setup to replace the NavBar buttons. It's made every app take full advantage of the display without any loss due to the NavBar sucking up some space.

Build Prop Editor on the play store works flawlessly. The DPI option is conveniently located in the side menu too. Running 540 with no issues, though the circle case will still be misaligned.

vng10 said:
Okay. THanks. Yeah I tried editing the build.prop and when it rebooted, it was optimizing 32 apps and when it was finishing up, it would reboot. So I am on my backup. Ill see if there are any other options or fixes to this. I just hate how big everything looks at the default.
Click to expand...
Click to collapse
Build prop created boot loop for me too I switched to kernel audiutor from play store and no more boot loops. Changed dpi to 530 with no issues.
Sent from my LG-H811 using Tapatalk

Dpi density changer worked for me. Nav bar is still a little big for me at 540 but its manageable. Thanks for all the help!
Sent from my LG-H811 using Tapatalk

Strange issue after screen replacement (See screenshots)

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.