zenfone 2 dpi display issues - ZenFone 2 Q&A, Help & Troubleshooting

Hi guys, I have the zenfone 2 ww version (ZE550ML) rooted.
Short version: received the system update notification and tried running it OTA but that failed, most likely due to root. So I decided to download the entire firmware build and manually flash. That seemed to go okay but it immediately caused some weird display driver issue. After doing google and threads on xda it seems like my DPI settings got screwed up. So by default my resolution or dpi results in very very small icons and text on screen.
I tried using the adb shell wm density command and editing build.prop (rebooting) to fix this but based on the output below the system isn't truly accepting the changes. This discrepancy is leading to some applications rendering badly. E.g) changing my display picture in whatsapp results in the app zooming the image to a humungous size and I can only crop a small section of the picture.
Output from adb shell wm density shows that no matter what I change the dpi to the phone registers the actual dpi as 320 instead of the normal 480. I did the command on a friend who has the exact same phone to get the different outputs. Does anyone know how to get the native dpi to register at 480 (3.0)?
I've tried re-flashing the firmware and using older versions..same issue.
Key differences evident:
Working zenfone 2
Display Devices: size=1
DisplayDeviceInfo{"Built-in Screen": 1080 x 1920, 60.000004 fps, supportedRefreshRates [60.000004], density 480, 403.0 x 403.0 dpi, appVsyncOff 7500000, presDeadline 12666666, touch INTERNAL, rotation 0, type BUILT_IN, state OFF, FLAG_DEFAULT_DISPLAY, FLAG_ROTATES_WITH_CONTENT, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
mAdapter=LocalDisplayAdapter
mPhys=PhysicalDisplayInfo{1080 x 1920, 60.000004 fps, density 3.0, 403.0 x 403.0 dpi, secure true, appVsyncOffset 7500000, bufferDeadline 12666666}
my zenfone 2
Display Devices: size=1
DisplayDeviceInfo{"Built-in Screen": 1080 x 1920, 60.000004 fps, supportedRefreshRates [60.000004], density 320, 403.0 x 403.0 dpi, appVsyncOff 7500000, presDeadline 12666666, touch INTERNAL, rotation 0, type BUILT_IN, state OFF, FLAG_DEFAULT_DISPLAY, FLAG_ROTATES_WITH_CONTENT, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}
mAdapter=LocalDisplayAdapter
mPhys=PhysicalDisplayInfo{1080 x 1920, 60.000004 fps, density 2.0, 403.0 x 403.0 dpi, secure true, appVsyncOffset 7500000, bufferDeadline 12666666}
So it's clear his dpi settings are at 480 (density 3.0) and mine are locked to 320 (density 2.0) and this result is the same no matter what I change my display density to via build.prop or shell wm density.

Hi!
How are you getting those details?
BTW, based on your data, your friend has a density of 480 which i think belongs to ZE551 and not on ZE550. Correct me if I'm wrong.

And as you stated in "My Zenfone"
You are getting 1920x1080 resolution. So, i think you flashed wrong firmware.
551ML firmware on 550ML??

xgneilx said:
Hi!
How are you getting those details?
BTW, based on your data, your friend has a density of 480 which i think belongs to ZE551 and not on ZE550. Correct me if I'm wrong.
Click to expand...
Click to collapse
You are correct, after confirming the models etc.. it was a firmware mis-match on my part that started the entire mess. Realised that when my accelerometer was not working either.
adb shell dumpsys display

[email protected] said:
And as you stated in "My Zenfone"
You are getting 1920x1080 resolution. So, i think you flashed wrong firmware.
551ML firmware on 550ML??
Click to expand...
Click to collapse
Yes I did. I believe my errors started when I did the incorrect firmware build after the failed OTA. So that first build possibly changed my fastboot, boot, recovery images and I was under the wrong impression my model was the 550ML. It didn't help that the Regulatory Info in Settings|About reflected the model as the Z008D.
So once I restored the correct fastboot, boot and recovery images for the Z00AD and factory reset I was able to re-flash the correct firmware.
Everything works fine now. Thanks very much for chiming in.:good:

Related

[Q] Turning off widescreen mode on the G2

considering every other camera phone you can change to aspect ratio (4:3) ie 640x 480 instead of 640x960 it is for work in reo propertys where every thing has to be documented and sent some where.
need to be able to for my work
and other phones can see below just not a tmobile version ?
http://sites.pruvan.com/certified-hardware/smartphones

[XS] Change device screen resolution, The Correct way?

I owned a Sony Xperia S lt26i.
it will lags constantly while playing some games, i think it is because of its high screen resolution. (correct me if i'm wrong)
If i want to change whole device screen resolution from 1280x720 to 960x540
I just need to change the lcd density/screen resolution at build.prop and change all apps to 960x540 compatible (included launcher/dialer) , then change the details of my model to Xperia P (which is a 960x540 resolution)
Is it this way will work?
any help is appreciate
seems not easy to get an answer ~.~
bump~
bump ~.~
dotamaple said:
I owned a Sony Xperia S lt26i.
it will lags constantly while playing some games, i think it is because of its high screen resolution. (correct me if i'm wrong)
If i want to change whole device screen resolution from 1280x720 to 960x540
I just need to change the lcd density/screen resolution at build.prop and change all apps to 960x540 compatible (included launcher/dialer) , then change the details of my model to Xperia P (which is a 960x540 resolution)
Is it this way will work?
any help is appreciate
Click to expand...
Click to collapse
You cant change the resolution of the screen. The density is another story though.
Sent from my LT26i using xda app-developers app
He wants to change the screen of the application.
No need to be an asshole, you know what he means.
Verstuurd van mijn Xperia S met Tapatalk
dotamaple said:
I owned a Sony Xperia S lt26i.
it will lags constantly while playing some games, i think it is because of its high screen resolution. (correct me if i'm wrong)
If i want to change whole device screen resolution from 1280x720 to 960x540
I just need to change the lcd density/screen resolution at build.prop and change all apps to 960x540 compatible (included launcher/dialer) , then change the details of my model to Xperia P (which is a 960x540 resolution)
Is it this way will work?
any help is appreciate
Click to expand...
Click to collapse
If you have CWM installed then make a backup. Then apply the changes you think will work. If it works then good if not restore the backup.
Sent from my LT28
ToledoJab said:
If you have CWM installed then make a backup. Then apply the changes you think will work. If it works then good if not restore the backup.
Sent from my LT28
Click to expand...
Click to collapse
Q1:
CWM with locked bl will work as well? (i mean backup)
Q2:
changing density = changing resolution?
if 1280x720 change to 960x540, then
341.54 PPI (my PPI i think 340 if didn't rmb wrong) need to change to what value?
Edit: Checked, LCD density is 320, so what value i gonna to change to suit the 960x540?
Q3:
i tried to change before, but seems Launcher is not suitable for this resolution and those apps like subway surfers still is 1280x720 (define by the watching the FPS (2x~4x) ), so means i need details of my XS to XP then the apps need to re-download?
Thanks for reply
For unlocked bootloader, CWM backup works on latest version. I think version 4 is newest
I have no knowledge about resolution. Maybe check white paper, on Sony site, for the P for its specs.
After build.prop changes reinstall apps. Market should see changes.
Good luck
sent from my ION
ToledoJab said:
For unlocked bootloader, CWM backup works on latest version. I think version 4 is newest
I have no knowledge about resolution. Maybe check white paper, on Sony site, for the P for its specs.
After build.prop changes reinstall apps. Market should see changes.
Good luck
sent from my ION
Click to expand...
Click to collapse
i see.
Extra:
LCD density increase = Screen resolution decrease = Performance increase = Visual quality decrease?
is it this statement correct?
You can't decrease or increase screen resolution. The number of pixels are a hardware thing. You can change DPI, but that won't have an effect on the performance, but on how big or small everything will be rendered on the screen.
Felimenta97 said:
You can't decrease or increase screen resolution. The number of pixels are a hardware thing. You can change DPI, but that won't have an effect on the performance, but on how big or small everything will be rendered on the screen.
Click to expand...
Click to collapse
Oh ya.. This is the answer i want :crying:
It won't increase performance then no point to change it
that means we can't play subway surfers with full fps.. (even lose a samsung galaxy s)
Question Solved.
Thanks everyone!
dotamaple said:
Oh ya.. This is the answer i want :crying:
It won't increase performance then no point to change it
that means we can't play subway surfers with full fps.. (even lose a samsung galaxy s)
Question Solved.
Thanks everyone!
Click to expand...
Click to collapse
I hope you weren't using subway surfers as your lag test. I just went to the store to download it and every comment about it said that the app made the phone lag/laggy.
My kids play temple run, looks similar, and no lagging here
Edit: I just played both and I have no lag. Game played smoothly. Only played a couple minutes though
sent from my ION
ToledoJab said:
I hope you weren't using subway surfers as your lag test. I just went to the store to download it and every comment about it said that the app made the phone lag/laggy.
My kids play temple run, looks similar, and no lagging here
Edit: I just played both and I have no lag. Game played smoothly. Only played a couple minutes though
sent from my ION
Click to expand...
Click to collapse
yeah, temple run is constant 60fps and never drop, asphalt 7 still ok, but not constantly smooth also
max temp for cpu is how much? i would like to set it higher to prevent cpu decrease while gaming :silly:

Resolution to 1080 or 1224?

I tried changing resolution to
1224 x 2176 520 dpi
1080 1920 480dpi
But I want two apps to work
LG Keyboard ( I really like it. Its better than all others)
LG Launcher (good but I can live without it)
I can make the other apps work fine but above two. Has any one successful in running any of the above apps on 1080 ?
I am on lollipop btw
I was finally able to change resolution to 1224 with LG Home, Swiftkey and LG keyboard and all apps working perfectly fine.
Here's what I did.
Changed resolution to 1224 x 2176 DPI 540 using Nomone resolution changer.
Then I used Rom Toolbox Lite to edit build.prop and changed LCD density to 540 as well.
Reboot.
Everything is working great.
Why I changed to 1224 x 2176.
LG G3 original resolution
1440 x 2560 = 3686400 pixels.
and
1224 x 2176 = 2663424 pixel (72% of 1440 x 2560) Huge performance boost.
You can also try
1920 x 1080 = 2073600 (56% of 1440 x 2560) Even better performance boost.
I couldnt find the right DPI settings for 1080. LG Home, Keyboard doesnt work fine. Other apps can work fine by appsettings(xposed module) though.

How's the state of resolution changes?

Hi guys,
I pretty much got the G3 despite its QHD screen, but would actually prefer FullHD for performance reasons.
Can someone please tell me if there is a current and proven way to change the resolution across reboots without UI crashes? Can it be done with Fulmics?
I've tried doing it with Nomone resolution changer, 1920*1080 @ 485DPI. I tried raising the DPI to 530 for LG apps. Unfortunately, I get constant "com.android.phone has crashed" errors.

Switching Display Res from WQHD - FHD

Hey guys,
So just wondering has anyone noticed and pros / cons when switching the display resolution from WQHD ( 2560 x 1440) to HHD (1920 x 1080)?
Ive switched to it back and forth several times, and so far I really cant see any difference. The screen quality / crispness seems to be the same. Also I noticed that when i have FHD selected the device obviously seems to run a little faster / snappier.
Incase you don't know what I'm referring to its in Settings>Display>Screen Resolution.
Hmm the only place I can change that is by turning on a power saving mode, I don't see any screen resolution in the settings otherwise (on Canadian N930W8).
stevierayvaughan said:
Hmm the only place I can change that is by turning on a power saving mode, I don't see any screen resolution in the settings otherwise (on Canadian N930W8).
Click to expand...
Click to collapse
Thats strange I have it as a stock option in settings...
I tried it once and didnt like how the LCD density increases significantly. It also doesnt play nice when setting a custom LCD density via a root app or through adb.
I've noticed no improvements with quality, performance, and even battery life. Setting the res to anything but WQHD actually somehow drains more battery and causes performance issues.
To ellaborate on the tricky LCD density issues, I thought I could set the res to 720p and the LCD density to my usual (420 down from stock 560), but having the density to 420 on WQHD and then changing it to 720p essentially erases the set density, and then things get a little funky when trying to re-change the density. Doing so causes some weird glitches since the density of 420 on 720p is based on the resolution, so it actually makes the density much bigger compared to stock density on 720p, and then setting the density to the proportionate number based on calculating the difference causes the entire Ui to seize up and crash. The same effect you would get where if you set the density below 300.
imatts said:
I tried it once and didnt like how the LCD density increases significantly. It also doesnt play nice when setting a custom LCD density via a root app or through adb.
I've noticed no improvements with quality, performance, and even battery life. Setting the res to anything but WQHD actually somehow drains more battery and causes performance issues.
To ellaborate on the tricky LCD density issues, I thought I could set the res to 720p and the LCD density to my usual (420 down from stock 560), but having the density to 420 on WQHD and then changing it to 720p essentially erases the set density, and then things get a little funky when trying to re-change the density. Doing so causes some weird glitches since the density of 420 on 720p is based on the resolution, so it actually makes the density much bigger compared to stock density on 720p, and then setting the density to the proportionate number based on calculating the difference causes the entire Ui to seize up and crash. The same effect you would get where if you set the density below 300.
Click to expand...
Click to collapse
Ok thanks for the great answer! Guess ill stick to WQHD! Just thought it might offer some benefits.
been testing this and found that it does not get warm when switched down
and to the eye same amazing screen
imatts said:
I tried it once and didnt like how the LCD density increases significantly. It also doesnt play nice when setting a custom LCD density via a root app or through adb.
I've noticed no improvements with quality, performance, and even battery life. Setting the res to anything but WQHD actually somehow drains more battery and causes performance issues.
To ellaborate on the tricky LCD density issues, I thought I could set the res to 720p and the LCD density to my usual (420 down from stock 560), but having the density to 420 on WQHD and then changing it to 720p essentially erases the set density, and then things get a little funky when trying to re-change the density. Doing so causes some weird glitches since the density of 420 on 720p is based on the resolution, so it actually makes the density much bigger compared to stock density on 720p, and then setting the density to the proportionate number based on calculating the difference causes the entire Ui to seize up and crash. The same effect you would get where if you set the density below 300.
Click to expand...
Click to collapse
phame said:
Ok thanks for the great answer! Guess ill stick to WQHD! Just thought it might offer some benefits.
Click to expand...
Click to collapse
Sorry, but my findings are almost the opposite, I even made a thread in discussion forum to regard the change to FHD to other users.
FOR ME, switching to FHD has improved the responsiveness of the UI (graceui) considerably, and I do not see the "LCD density increase" (btw.: what should that be? i guess DPI?? then switching to FHD would be a DEcrease...)
Also, I'm almost sure that this must lead to battery improvement too. simple because cpu und gpu have less work to do calculating the lesser amount of screen-pixels to draw! This might be slight, but should be there!
The other problems you mention are because you are playing around with density mods, are you using xposed? I use the lower FHD resolution now for a week, and I do not have ANY problem with it!!! And trust me, I use this phone the whole day long and have many programs and communication tools installed.
everything works as it should!
TML1504 said:
Sorry, but my findings are almost the opposite, I even made a thread in discussion forum to regard the change to FHD to other users.
FOR ME, switching to FHD has improved the responsiveness of the UI (graceui) considerably, and I do not see the "LCD density increase" (btw.: what should that be? i guess DPI?? then switching to FHD would be a DEcrease...)
Also, I'm almost sure that this must lead to battery improvement too. simple because cpu und gpu have less work to do calculating the lesser amount of screen-pixels to draw! This might be slight, but should be there!
The other problems you mention are because you are playing around with density mods, are you using xposed? I use the lower FHD resolution now for a week, and I do not have ANY problem with it!!! And trust me, I use this phone the whole day long and have many programs and communication tools installed.
everything works as it should!
Click to expand...
Click to collapse
This was the case both on root/unroot using standard adb shell wm debsity xxx and in-settings res.

Categories

Resources