Develop Bugs

[Q] What would it take to upgrade to a 720p screen with our GS2?

I posted a video showing how to increase display resolution on the Galaxy S II. I'm running at 1200 x 720 and looks great.
http://www.youtube.com/watch?v=pPPuEbXwOF4
There are a issues with a few stock apps, so make sure to watch the whole thing if you can, as I demonstrate everything I've run into so far.
p.s. For rooted phones only and even though process is ultra simple, don't hold me responsible if you mess up your phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

doesn't the screen only support up to 480 x 800
ah... nvm.. it becomes smaller.

It works the same way as it does on your computer... higher resolution means everything will be smaller, but you will see a lot more on display. It would look the same on phones that were designed with higher resolution (such as Galaxy Nexus).

goonx said:
doesn't the screen only support up to 480 x 800
ah... nvm.. it becomes smaller.
Click to expand...
Click to collapse
Yes, its pretty much fake 1280x720. Just lower the number using lcd density app for smaller looking screen.
Sent from my SGH-T989 using xda premium

im loving it!!! Thanks

the problem with this is, a lot of apps and stock apps such as the dialer, and sms, and maybe the keyboard (not sure) doesnt scale correctly, so the display looks bad, not worth the "fake" resolution, IMO.

Enzopreme said:
the problem with this is, a lot of apps and stock apps such as the dialer, and sms, and maybe the keyboard (not sure) doesnt scale correctly, so the display looks bad, not worth the "fake" resolution, IMO.
Click to expand...
Click to collapse
It really depends on the user... to many, fake resolution may be worth replacing every single app they use, especially if 99% of the people wouldn't be able to tell fake from a true HD display. It really does look great, so replacing a couple of apps for me was a no-brainer.
This wouldn't be that much of a big deal for any other phone that has a resolution better matched to its size, but T-mobile's (and Sprint's) SGS2 with its Herculesque proportions could really use it.

Enzopreme said:
the problem with this is, a lot of apps and stock apps such as the dialer, and sms, and maybe the keyboard (not sure) doesnt scale correctly, so the display looks bad, not worth the "fake" resolution, IMO.
Click to expand...
Click to collapse
Takes like 4 seconds to change it back.
Sent from my SGH-T989 using xda premium

Enzopreme said:
the problem with this is, a lot of apps and stock apps such as the dialer, and sms, and maybe the keyboard (not sure) doesnt scale correctly, so the display looks bad, not worth the "fake" resolution, IMO.
Click to expand...
Click to collapse
There plenty of free apps to replace those though. Go Contacts is free, has some great themes, and has a dialer that scales properly. And there are multiple SMS replacement apps that are free too. The calendar doesn't scale right either, I barely use the calendar so I haven't bothered with replacing it but I'm sure there's an app for that too.

It felt very pointless, it just made everything small.
Sent from my SGH-T989 using Tapatalk

Can't you show how the cameras, youtube, etc. work in the higher resolution? What a drag watching people scrolling around home screen and facebook. such a waste of time. Do something useful! But thanks anyway it looks really good. Does it have 16/9 modes? show that too.

All your doing is changing the DPI on screen. The screen size is still the same.
Your essentially doing what Windows and many other operating systems has been doing for people for years.
Can't see well increase the dpi.. too big decrease the dpi.
The resolution doesn't change just the font and icons.

firebane said:
All your doing is changing the DPI on screen. The screen size is still the same.
Your essentially doing what Windows and many other operating systems has been doing for people for years.
Can't see well increase the dpi.. too big decrease the dpi.
The resolution doesn't change just the font and icons.
Click to expand...
Click to collapse
Exactly. Like for me my native 17" display should be 1280 x 1024, but everything is so small, so I need to change it to at least 1152 x 864. Just the opposite on my phone. 800 x 480 seems a bit too big, so making things smaller helps. Actually I "tricked" my eyes to the point. I haven't changed the dpi, but instead choose a font that was 15% smaller than the default. Now everything looks smaller, and I fit much more on the screen before I have to scroll.

i have a hunch about the new 720 "HD" display of the Galaxy Nexus/Korean SGS2 HD
i'm almost certain the screen is the same screen, it's just default to higher DPI, very similar to our PCs/Laptops when Windows or Linux boots up, reads the screen model, then it automatically select X resolution for that model
so, we can basically get the same results by setting our phones to run in that configuration as well.
I'm quite sure once ICS is out, we'll know more the innards of it and Galaxy Nexus
then we can just add SGS2 into the same list of screens as the Galaxy Nexus to get the same 720p resolution

What are the SamSung stock apps and how are they affected? (Keyboards, and Camera mostly, what else?)
thanks it looks great.

Thanks! Great stuff

very nice....

If some of the stock Samsung apps don't scale properly, wouldn't it be feasible to use the same apps designed for the 720p display like from the Note?

The only affected apps I have noticed so far: stock touchwiz launcher (home screens and app tray are at the top half of the display), smaller dialer, lower portion of calendar is covered up by a box, and music player doesn't open. Camera has not been affected at all. Market is much better. I will try to make another video showing different apps.

Allen K said:
The only affected apps I have noticed so far: stock touchwiz launcher (home screens and app tray are at the top half of the display), smaller dialer, lower portion of calendar is covered up by a box, and music player doesn't open. Camera has not been affected at all. Market is much better. I will try to make another video showing different apps.
Click to expand...
Click to collapse
the only problem with this is that most applications on the market checks the screen resolutionor dpi and wont let you install.
i've tried this method before to use the qHD resolution and apps like tango in the market say "your device is not supported" and the install button is greyed out.
yet, after side loading the apk, app worked fine.
so it works but it's a little too much inconvenience when you nee to download and app quick./

[need help] [Z00A] Change resolution to 720x1280 and still use the physical nav keys.

I have been flashing ROMS since it was cool to do so (no, not before).
But I am a complete n00b when it comes to dev stuff and this whole post is written at that point of view; this post MAY contain incorrent information and n00bish mistakes.
Why change to 720px1280?
Frame rate doubles when using games or other graphics intensive applications.
Increased batter life due to lower resolution.
Even more snappier!
Since it's a 5.5" screen, not much difference between 1080x1920 and 720x1280. Of course, it's a compromise but barely noticable.
(Don't actually do anything, just read!)
How to change the resolution?
Make sure you enable "USB Debugging"
Make sure you installed adb and fastboot in your computer.
Connect your phone to your computer (usb cable... etc).
In the terminal type : adb shell wm size 720x1280
Wait, everything is so big! We need to change the DPI.
The original DPI is 480, but at 720x1280, 350 seems to restore the previous size and feel. Feel free to experiment with the DPI
How to change the DPI?
Make sure you enable "USB Debugging"
Make sure you installed adb and fastboot in your computer.
Connect your phone to your computer (usb cable... etc).
In the terminal type : adb shell wm density 350
OK, now you notice the (Virtual) Navigation Keys at the bottom don't work anymore.
Well that is because the Virtual Keys Mapping is out of range.
To understand why, consider this question : How will the system know which button you are pressing?
System uses the "display coordinate system" to identify where the buttons are located on the screen.
This info in located in this file: /sys/board_properties/virtualkeys.ftxxxx_ts
virtualkeys.ftxxxx_ts:
Code:
0x01:158:215:2045:260:250
0x01:102:540:2045:260:250
0x01:139:865:2045:260:250
Syntax:
Code:
0x01: A version code. Must always be 0x01. (ok google)
<Linux key code>: The Linux key code of the virtual key.
<centerX>: The X pixel coordinate of the center of the virtual key.
<centerY>: The Y pixel coordinate of the center of the virtual key.
<width>: The width of the virtual key in pixels.
<height>: The height of the virtual key in pixels.
Linux key code says what the button is: return, home, recent...
The last four parameters (centerX, centerY, width_of_virtual_key, height_of_virtual_key) are our concern, because they say where the buttons are located on the screen using "display coordinate system".
In "virtualkeys.ftxxxx_ts", the location of buttons is defined for 1080x1920.
So when we changed the resolution to 720x1280, the mapping for the virtual buttons became out of range and thus unusable.
So what should those parameters be for 720x1280?
Code:
0x01:158:143:1363:173:166
0x01:102:360:1363:173:166
0x01:139:576:1363:173:166
Stop lying!
Well I don't know for sure.
Method 1:
The original resolution is 1080x1920 and we changed it to 720x1280.
a -> 1080x1920
b -> 720x1280
w -> width
h -> height
wb/wa = 1280/1920 = hb/ha = 1280/1920 = 0.666666667
Both the resolutions have same aspect ratio. So we need not bother about width and height seperately, because they are both changed at the same proportion.
So, multiply the last four parameter values (centerX, centerY, width_of_virtual_key, height_of_virtual_key) by 0.666666667 and you should get the location of the buttons when resolution is changed to to 720p.
Method 2:
Enable "Show pointer location" in "Developer Settings".
The co-ordinates of where you touched the screen are displayed at the top.
Change the resolution to 720x1280.
The Navigation Buttons don't work but drag your fingers onto them.
You will see X and Y are near to the values we calculated in METHOD 1.
So lets modify the file already! (/sys/board_properties/virtualkeys.ftxxxx_ts)
Well you see, the file (virtualkeys.ftxxxx_ts) is located in the directory "/sys".
It turns out, it is not an actually directory. It is a "view" of the KERNEL as a filesystem.
So, every time the system boots, the kernel creates (magics?) those files in "/sys" which the system uses.
We do not have permission to change that directory's contents, not even with a slip from our parents.
Unless we have a way of overriding the kernel created file (virtualkeys.ftxxxx_ts), we have to patch the kernel itself.
I don't know how to patch kernels and stuff, this escalated quickly for me. So if you are interested check it out!
Please check the validity of anything said in this post. Positive criticism is welcome!
Sources : https://source.android.com/devices/input/touch-devices.html#virtual-key-map-files, @aziz07 (started all this after reading their posts in : http://forum.xda-developers.com/zenfone2/general/downgrade-resolution-ze551ml-t3163797)

This is the file on ze550ml. Your results appears to correct.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Im using second monitor from play store to change resolution and density on the fly.
Sky on demand not work if detect 1080 device. So i change to 720p to connect tv.
Facing with virtual Keys not working, hwvr i use iswipe to manage it.
Solution can be virtual nav bar, exposed mondule, anyway resulution is not 1080 or 720 but is scaled so open zenui.apk to see how it work, what now? You need mod zenui or just flash custom rom, 'cuz will afect call screan, setting screen, app drawer and so on.
Some aps will not work changing density and zenui sometime crash, so need reboot.
Forget to say that: changing resolution will impact batery life in whorste way (you will run ever biggest res then the normal use). Only wallpaper, immersive mode (photo and video) and of course user apps are the only run in full resolution, set black screen wallpaper and use appsetting module to change per app resolution if you tink will save batery life.

Ah, the much easier method. Thank you for posting.

I think, 540x960 will be better for lowres because it will use whole 2x2 pixels and won't create blur.
I've just got idea to mix such tweak with second user. So, when you switch the user, resolution will be switched as well.

UP, it work with Cyanogenmod 13, much better battery life, but we need kernel patch for modify virtualkeys.ftxxxx_ts

tikilou said:
UP, it work with Cyanogenmod 13, much better battery life, but we need kernel patch for modify virtualkeys.ftxxxx_ts
Click to expand...
Click to collapse
why?

@blazzer12 I would like to correct something :
the correct parameters for 720x1280 are
0x01:158:140:1341:180:100
0x01:102:360:1341:170:100
0x01:139:580:1341:180:100
these values are the one metioned in our kernel source.

blazzer12 said:
Well you see, the file (virtualkeys.ftxxxx_ts) is located in the directory "/sys".
It turns out, it is not an actually directory. It is a "view" of the KERNEL as a filesystem.
So, every time the system boots, the kernel creates (magics?) those files in "/sys" which the system uses.
We do not have permission to change that directory's contents, not even with a slip from our parents.
Unless we have a way of overriding the kernel created file (virtualkeys.ftxxxx_ts), we have to patch the kernel itself.
Click to expand...
Click to collapse
Better you can try a ROM from Z008/720p Model. Because I've flashed a full ROM of Z008 to my Z00A for recovering it from HardBrick (In that case I had only 720p model RAW Firmware file). That ROM was working very fine but the icons was smaller due to DPI of the ROM. My Idea is, if I flash 720p ROM and change resolution to 720p using your methid, everything will be normal. right? (Or, you can use a kernel alone from Z008 instead of searching for a kernel patch).... Am I right?

say99 said:
@blazzer12 I would like to correct something :
the correct parameters for 720x1280 are
0x01:158:140:1341:180:100
0x01:102:360:1341:170:100
0x01:139:580:1341:180:100
these values are the one metioned in our kernel source.
Click to expand...
Click to collapse
would be nice if you can add this patch in your kernel

xCalibur15 said:
would be nice if you can add this patch in your kernel
Click to expand...
Click to collapse
ok, I did this today in the morning, but I must tell you this method didn't work
https://github.com/Zenfone2-Dev/kernel-FlareM/commit/ba444d0616457c283cd257a363d427c915efbf7b
I was able to change the content of the file, but as soon as that happened, I was only able to access 3/4th of my screen, touch didn't work. I must also tell you guys that, even though we change the DPI to 720P, sweep2sleep still works that just means that the location of the hardware keys is still the same. I am trying to figure out the correct coordinate that we should use. Cause according to our boot animation, we get a increase of about 1.45x in X coordinate.
help me with the codes if you want to
Sent from my ASUS_Z00A using Tapatalk

i calculated the values for 540x960px (easier to calculate):
0x01:158:107:1023:130:125
0x01:102:270:1023:130:125
0x01:139:433:1023:130:125
dpi 240
if i got it right, I can make the values for 720p also

i found this very cool, and wish to change the button positions... but sorry i dont get it, there is a way to do it?

Asus Zenfone 2 Laser ZE500KL
Asus Zenfone 2 Laser ZE500KL
Resolution 720 x 1280 pixels (~294 ppi pixel density)
android marsmallow
0x01:158:140:1328:160:80
0x01:102:360:1328:180:80
0x01:139:580:1328:160:80
---------- Post added at 07:02 AM ---------- Previous post was at 06:51 AM ----------
Asus Zenfone 2 ZE551ML
1080 x 1920 pixels (480 ppi pixel density)
android marsmallow
0x01:158:140:1328:160:80
0x01:102:360:1328:180:80
0x01:139:580:1328:160:80

https://goo.gl/UKaif3 here's how to change resolution with root

say99 said:
ok, I did this today in the morning, but I must tell you this method didn't work
Click to expand...
Click to collapse
And if you include the next code but with correct touch screen coordinates for 720p?
https://github.com/BORETS24/Kernel-...0c/drivers/input/touchscreen/ftxxxx_ts.c#L926
https://github.com/BORETS24/Kernel-...0c/drivers/input/touchscreen/ftxxxx_ts.c#L986

How to change density from 480 to 420 (same as Pixel) without root

If you're like me, you probably find the XZ's default density of 480 makes items far too large and cuts out text. The Googl Pixel, which is also a 5.0" 1080p screen uses a 420dpi. To make your XZ the same:
* Enable developer settings
* Enable ADB over USB
* From a computer, with adb, type:
adb shell wm density 420
The change will be instant, though a reboot is recommended.

CLShortFuse said:
If you're like me, you probably find the XZ's default density of 480 makes items far too large and cuts out text. The Googl Pixel, which is also a 5.0" 1080p screen uses a 420dpi. To make your XZ the same:
* Enable developer settings
* Enable ADB over USB
* From a computer, with adb, type:
adb shell wm density 420
The change will be instant, though a reboot is recommended.
Click to expand...
Click to collapse
Can you add a screenshot comparing both the densities ?
Thank you

chawlasrijan said:
Can you add a screenshot comparing both the densities ?
Thank you
Click to expand...
Click to collapse
i did it !! you can't actually feel the differences. i only understood it through the keyboard and the little gaps on the sides of the dock

CLShortFuse said:
If you're like me, you probably find the XZ's default density of 480 makes items far too large and cuts out text. The Googl Pixel, which is also a 5.0" 1080p screen uses a 420dpi. To make your XZ the same:
* Enable developer settings
* Enable ADB over USB
* From a computer, with adb, type:
adb shell wm density 420
The change will be instant, though a reboot is recommended.
Click to expand...
Click to collapse
This is the greatest thing ever. Thanks heaps!
Any way to shrink the notification text to match? Cheers, mate!
Edit: a restart fixed it - all good! I found 400 to be perfect for me. Thanks again.

I GOT SCREENSHOTS!
The change takes effect immediately so watch your screen closely before pressing enter on terminal.
Reboot after change is still advised.
460 dpi (27% battery)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
420 dpi (29% battery)
440 dpi
Bonus:
The "recognized developer" badge on play store screwed up after a reboot... Just thought it is interesting

How does reducing the density make icons and text appear smaller? Shouldn't it do the opposite? How does this change affect the picture quality of the display (same, worse, better)?

Window Manager density isn't the same as device density in build.prop. There are awkward effects when developers don't use the WM density. Also, you rely on nodpi packages now.
Still, the side effects are rare and IMO the pros greatly outweigh the cons.

CLShortFuse said:
If you're like me, you probably find the XZ's default density of 480 makes items far too large and cuts out text. The Googl Pixel, which is also a 5.0" 1080p screen uses a 420dpi. To make your XZ the same:
* Enable developer settings
* Enable ADB over USB
* From a computer, with adb, type:
adb shell wm density 420
The change will be instant, though a reboot is recommended.
Click to expand...
Click to collapse
Thanks for this. However i noticed noughat has this functionality built in but it seems to only have 3 (Small to Large) settings, whereas the pixels phone have 5 (small to Largest).
Have sony been stupid and just reduced functionality?

There is actually a simpler way. .You can find the same in "Developer Options" on your device with Android 7.0 Nougat, just below the Animation Settings

Mazellat said:
There is actually a simpler way. .You can find the same in "Developer Options" on your device with Android 7.0 Nougat, just below the Animation Settings
Click to expand...
Click to collapse
Thanks but i cant seem to find it in developer options. do yoiu mind sending a screen grab

coleburns said:
Thanks but i cant seem to find it in developer options. do yoiu mind sending a screen grab
Click to expand...
Click to collapse
Settings> Display >view >display size >small, default, big ?

Zewarxx said:
Settings> Display >view >display size >small, default, big ?
Click to expand...
Click to collapse
I am aware of this setting as per my original question. i was referring to the setting under developer options

coleburns said:
Thanks but i cant seem to find it in developer options. do yoiu mind sending a screen grab
Click to expand...
Click to collapse
Sent from my F8332 using Tapatalk

paphonb said:
Sent from my F8332 using Tapatalk
Click to expand...
Click to collapse
Apparently I don't have this option ..
It's 7.0 specific?

lnxcat said:
Apparently I don't have this option ..
It's 7.0 specific?
Click to expand...
Click to collapse
Yes.
Sent from my F8332 using Tapatalk

460 is good 5 icon in Pixel launcher and looks good

I've set mine to 420dp and can have 5 icons per row on stock home launcher , looks loads better

You can alsow change the resolution without root
adb shell wm size 720x1280
adb shell wm density 320
now icon not small but some effects on battery usage

ClementNg23 said:
I GOT SCREENSHOTS!
The change takes effect immediately so watch your screen closely before pressing enter on terminal.
Reboot after change is still advised.
460 dpi (27% battery)
420 dpi (29% battery)
440 dpi
Bonus:
The "recognized developer" badge on play store screwed up after a reboot... Just thought it is interesting
Click to expand...
Click to collapse
What's the theme you using?

pw1nce said:
What's the theme you using?
Click to expand...
Click to collapse
Nova Launcher with Polycon icon pack. Stock ROM when the screenshots were taken.
https://play.google.com/store/apps/details?id=com.teslacoilsw.launcher&hl=en
https://play.google.com/store/apps/details?id=com.thearclabs.polycon&hl=en

Question Change screen resolution

Anyone knows if is possible change resolution in adb? Or someting

Pretty sure you used to be able to use the following command
For resolution:
adb shell wm size 1080x1920
For screen density:
adb shell wm density 390
Obviously adjust numbers to suit your needs.
I accept no responsibility for any issues which may occur if you use these commands
Edit:
Did a quick bit of googling and found this which echos the above:
https://www.reddit.com/r/pokemongodev/comments/6554k1/_/dgfpesr

I know this is quite an old post, but couldn't find a newer one mentioning if changing screen res works. Did these commands worked fine with the 6 pro? And is there any noticable difference in battery life/performance if it does work?

I'm interested too. Give it a shot and report back on the results? I'm in the car all day, otherwise I would

There is also the "smallest width" setting under the developers options menu. I set mine to 720 for higher resolution.

B from C said:
There is also the "smallest width" setting under the developers options menu. I set mine to 720 for higher resolution.
Click to expand...
Click to collapse
I just tried that and needed to pull out my magnifying glass lol. Everything was so small!!

I've got mine at 474 with font set to large... happy medium for me

Gave it a try just now and it does work, however definitely not what I expected. Basically adds 2 huge top/bottomn notches and brings your rendered screen in the middle. Bottom gestures are almost impossible, as you have to start somewhere middle in the screen. And for unlocking the device - now you need 2 fingers - one to trigger the FP scanner because it ends up in the bottom right and one on the actual Scanner. Also you end up with a weirdly placed camera cutout that you cant remove.
I might try to run my phone like this for a day, as I wanted to experiment how the battery behaves. Menus seems really fast and smooth, but can be because the animations have less space and are shorter . If anyone has an idea for a command to stretch the screen over the whole display, I'd love to try.
Edit: Never mind, dumb me didnt adjust for screen ratio not being what I'm used to. After taking that into account 1080x2340 works. Fingerprint and camera cutout issues still persist though.

While this may be a little small/sharp for some people, I've been running "Smallest Width" at 720, which seems to yield a "Display Size" of 320dpi, along with default font size for awhile and have had no issues with the camera cutout or the fingerprint reader. I also use the AOD Notify app to put a glowing ring around the camera and didnt need to make any offsets so I'm pretty sure my camera cutout is where it's supposed to be.
I ran 320dpi/720width for years on a few Samsung Note devices prior to my P6P so that's what I'm used to (I'm one of those people who run a 4k tv as a monitor with no scaling). You may need to play with different dpi and font combinations until you find something you are comfortable with. In rare situations I have needed to restart the device or clear the cache for all UI elements to resize correctly after a change.

After a couple days of testing (it did indeed took me 2 days to kill my phone) I figured that for whatever reason, on the Pixel (maybe exynos) lowering the render res does indeed save some battery. On 1080p I managed to get around 1%/h - 2%/h less consumption on Screen on Time, which for people like me who manage to get 5+ hours of screen on time can result in quite of a difference. I regularly end days with something between 30-40% battery, which is still really good but I won't go to a second day as the 2 hours charge time is really annoying me .
With the lower resolution I ended the first day with 57% and I ended up with 37.5 hours of standby and 8 hours and 40 min of SoT in a full charge. I even went further by reducing the resolution to 720p, but it is really obvious that Google never made a 720p phone - almost all UI's broke and even changing the brightness was a hassle. I also believe that it might have triggered some rouge process as my phone lost 10% battery in less than an hour, so I switched back to my original 1440p.
To conclude this - is changing your resolution to 1080p worth the broken finger print - depends. In my example, I would probably do it if I know I am going on a trip where lots of pics/videos will be taken and heavy navigation use, as my phone is more of a tool in cases like that and I always try to squeeze every bit of battery I can. If google does implement the ability to change the res though - I would definitely switch.
I just wonder, why does it made such a big difference on this phone, but it didnt for S10(the only battery test I found on a video). Is Android 12 harder to drive? Or are these LTPO panels more intense on the GPU? Or is it even exynos/mali GPU not as efficient as SD on rendering UIs? If anyone wants to chime in - Id' be glad to hear some opinions. ( Or maybe I just used my phone less.. that would be the worst )
P.S. Just to say this was done on 60hz and that your milage might vary, if you decide to try. Everyone's usage is different and in my case I work from home - so WiFi connection (although router is far) but horrible signal, as I am a top flat in the UK (worst case scenario). The setting I used for the adb command is 1080x2340 and denstity was 400, although density is preference I guess and I believe wont affect battery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yessss... I changed it... All. Works
Download app easy dpi changer from playstore
Easy DPI Changer [Root] - Apps on Google Play
Make your screen yours
play.google.com
And set this value
Need root
If want to stock values only tap to reset and all come back to stock value

liver20 said:
Yessss... I changed it... All. Works
Download app easy dpi changer from playstore
Easy DPI Changer [Root] - Apps on Google Play
Make your screen yours
play.google.com
And set this value
Need root
If want to stock values only tap to reset and all come back to stock value
Click to expand...
Click to collapse
For what it's worth, with Android 13 Stable and the Kirisakura custom kernel, you can now change to 1080p from Android settings.
XDA Article: Google Pixel 6 Pro gains 1080p support thanks to Android 13 and a custom kernel

roirraW edor ehT said:
For what it's worth, with Android 13 Stable and the Kirisakura custom kernel, you can now change to 1080p from Android settings.
XDA Article: Google Pixel 6 Pro gains 1080p support thanks to Android 13 and a custom kernel
Click to expand...
Click to collapse
And doesn't break the fingerprint scanner like Easy DPI changer does

There must be a way of doing it without opening the bootloader, right? Or do you guys think it's impossible without breaking stuff like the fp scanner? I'd love to lower my resolution but I really didn't want to lose all my stuff and have to reinstall everything at this moment.

Another method to adjust screen resolution/size/dpi: I noticed the "AOSP Mods" module for LSposed/Magisk has an option in the "Miscellaneous" section for "Display resolution". The slider does work and changes the resolution on my P6P without modifying the smallest width developer setting. YMMV
forum link

B from C said:
Another method to adjust screen resolution/size/dpi: I noticed the "AOSP Mods" module for LSposed/Magisk has an option in the "Miscellaneous" section for "Display resolution". The slider does work and changes the resolution on my P6P without modifying the smallest width developer setting. YMMV
forum link
Click to expand...
Click to collapse
Thanks a million for this. The module fixed my screen flickering - couldn't go over approx 50% without flicker . I set the screen brightness from within Miscellaneous. Only problem is that I can't access Miscellaneous again without module force closing (other options are fine) - looking into the reason for it.

Question How to change resolution of inner screen?

I searched on reddit a guy recommended via ADB to change but not sure how it works and need more insight. He recommended "adb shell wm size 1080x1920".
How will this work and will it make content viewing experience better?
thanks

mentalpositivity said:
I searched on reddit a guy recommended via ADB to change but not sure how it works and need more insight. He recommended "adb shell wm size 1080x1920".
How will this work and will it make content viewing experience better?
thanks
Click to expand...
Click to collapse
It will make it significantly worse, as its not the native resolution, that's a 16x9 res, the screen is 4x3. If it fits the whole screen everything will be stretched to heck

the_ape said:
It will make it significantly worse, as its not the native resolution, that's a 16x9 res, the screen is 4x3. If it fits the whole screen everything will be stretched to heck
Click to expand...
Click to collapse
But is it possible to do? How would I do it only for inner screen? And if it's bad how to revert? I want to try for experiment purpose

Wouldn't really know off the top of my head but the inside screen is native 2176x1812 so at 1080p it would look terrible
Why would you possibly want to change the resolution to a non-native one? No non-native resolution will look good on it, as the pixel grid is just not setup for it.
It would be something like
adb shell wm density DPI (where DPI is a DPI)
adb shell wm size 1920x1080 (where 1920x1080 is resolution)
Not 100% sure how to target a specific display though, so you may need to fiddle about
But to run that command your going to need to root the device anyhow
Could have a fiddle in dev options to see if it helps too
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

the_ape said:
Wouldn't really know off the top of my head but the inside screen is native 2176x1812 so at 1080p it would look terrible
Why would you possibly want to change the resolution to a non-native one? No non-native resolution will look good on it, as the pixel grid is just not setup for it.
It would be something like
adb shell wm density DPI (where DPI is a DPI)
adb shell wm size 1920x1080 (where 1920x1080 is resolution)
Not 100% sure how to target a specific display though, so you may need to fiddle about
But to run that command your going to need to root the device anyhow
Could have a fiddle in dev options to see if it helps too
View attachment 5702087
Click to expand...
Click to collapse
The dev options min width changed the phone width but not the content.
My intention is to get better video size as sometimes black bars are too big, 50% of the video are black bars

Do you guys know if the inner screen's resolution as good as the outer screen? the icons and fonts look much bigger on the inner screen compared to the outer screen and outer screen is looking much better compared to inner. I would want to see same level of clarity on the inner screen as outer one.

Inside screen is 374ppi and outside is 402ppi, so technically the outside is higher "HD Ness"
But on mine seems pretty consistent size wise etc, but I've set the zoom to zero

the_ape said:
Inside screen is 374ppi and outside is 402ppi, so technically the outside is higher "HD Ness"
But on mine seems pretty consistent size wise etc, but I've set the zoom to zero
View attachment 5702151
Click to expand...
Click to collapse
If I want to have videos bigger and less black bars would changing resolution help? Yes would be stretched

mentalpositivity said:
The dev options min width changed the phone width but not the content.
My intention is to get better video size as sometimes black bars are too big, 50% of the video are black bars
Click to expand...
Click to collapse
You won't, and cannot get rid of the bars? Your watching 16x9 formatted content, on a 4x3 screen? There is literally nothing you can do about it.
If you want it filli g, then you need some playback software that will do pan-and-scan lime the old tv's used to do (but the other way around, putting old 4x3 content onto 16x9 screens without the side black bars)
Just deal with it, it is what it is. Wide-screen content will always have black bars on square screens.
After all its still a bigger 'virtual' screen than an s22! Even a s22 Pro, it's only 7mm smaller than the ultra at the end of the day (height of screen so viewing Co tent on its side)

the_ape said:
Wouldn't really know off the top of my head but the inside screen is native 2176x1812 so at 1080p it would look terrible
Why would you possibly want to change the resolution to a non-native one? No non-native resolution will look good on it, as the pixel grid is just not setup for it.
It would be something like
adb shell wm density DPI (where DPI is a DPI)
adb shell wm size 1920x1080 (where 1920x1080 is resolution)
Not 100% sure how to target a specific display though, so you may need to fiddle about
But to run that command your going to need to root the device anyhow
Could have a fiddle in dev options to see if it helps too
View attachment 5702087
Click to expand...
Click to collapse
Don't have to be rooted to run adb commands on any android. I have 2 rooted apps I'm using on my Fold 4 that I always use by simply running
a couple of adb commands. You can Uninstalle bloat on the F4 too but if you don't know what you're doing you may end up with a brick.

Here's example of different fitting
https://imgur.com/a/Ci0i1Lz
Best you can do.. But honestly, just live with it, at least the screen is oled so the black bars aren't using energy

ggrant3876 said:
Don't have to be rooted to run adb commands on any android. I have 2 rooted apps I'm using on my Fold 4 that I always use by simply running
a couple of adb commands. You can Uninstalle bloat on the F4 too but if you don't know what you're doing you may end up with a brick.
Click to expand...
Click to collapse
True you don't need root for a lot of stuff (I've debloared etc) but AFAIK or remember screen res is root only, I may be wrong, but I've not had need to do it since the s3 days..