Develop Bugs

changed dpi, have some questions

I changed the screen dpi to 200 but now miui launcher looks weird.
So I'm using adw launcher with 1 extra row and looks nice, however I like the way miui launcher functions, like when I install a app it immediately puts it on desktop, just like the iphone.
Is there any launcher that acts like this and also allows to change number of rows and columns?
this is miui default, folders and other widgets look even weirder
{
"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"
}
adw is perfect

out of interest, how did you change it?

with lcd density, app from market

Naffets said:
out of interest, how did you change it?
Click to expand...
Click to collapse
You change the LCD density string in build.prop to set it permanently, or use lcd density changer from the market to do a temp change.
You can use a tool called "Absolute System" to edit the build.prop easily.
Sent from my GT-I9100 using Tapatalk

you can use launcherpro which allows to change number of rows and columns

and what would exactly be the point in changing it?

may be engwee wants to see more apps at the same time without moving the screen up and down

Jiniko77 said:
and what would exactly be the point in changing it?
Click to expand...
Click to collapse
changing the lcd density has the same same effect as changing the resolution on your pc monitor. the phone will fit more on the display, so smaller icons and text etc...

any of this apps are changing the phone dialer too ?.....???

None of the sammy aps like dialer change with DPI changes, everything looks smaller and a bit crap, you will either need to find a ROM with DPI changes built in for that or there might be a theme you can use maybe.

My theme is built for changed DPI (shameless plug)
Sent from my GT-I9100 using xda premium

da.trute said:
None of the sammy aps like dialer change with DPI changes, everything looks smaller and a bit crap, you will either need to find a ROM with DPI changes built in for that or there might be a theme you can use maybe.
Click to expand...
Click to collapse
Yes, TouchWiz doesn't play nice with DPI changes. Use Go Contacts (includes dialer) for dialer - I haven't found a MULTI-DPI camera replacement yet tho.
Sent from my GT-I9100 using xda premium

Changing LCD Density
Changing the density changes the whole phone - if you set density to a lower number everything will be smaller on the screen and then you can fit more items on the screen. A higher number will make things bigger and fit less.
An unfortunate side effect of changing DPI however is that quite a lot of apps don't like it and will force close when you try and open them. For example, I just set mine to 200dpi and Angry Birds FC's.
The Market is another app that seems to be fairly DPI sensitive, however in my case right now running CM7 nightly the Market is working fine at 200dpi.
Another effect can also be black bands around apps that are not written to scale to screen DPI but rather with hard coded sizes for LDPI/MDPI/HDPI.
Cheers!

ecips said:
Changing the density changes the whole phone - if you set density to a lower number everything will be smaller on the screen and then you can fit more items on the screen. A higher number will make things bigger and fit less.
Click to expand...
Click to collapse
Gotcha!
You've got PM!!!
Big sorry for polluting the thread, but i can't seem to get a hold of ecips

ayk33 said:
you can use launcherpro which allows to change number of rows and columns
Click to expand...
Click to collapse
like I said in my first post, I'm using ADW and it works fine with it, I was looking for a miui like launcher, with all the apps on desk and no app drawer, probably doesn't exist.
While I was on miui rom I didn't encounter problems with the apps I used, this goes from games to standard apps, like the market.
Now I'm on stock and I saw the dialer is small, but no problem otherwise, when I get called the slider works fine.
the advantage is it makes the screen seem like higher res, browser fits a lot more content, holding it next to a sensation it looks the same, one difference I encountered on sensation is a game megajump, doesn't fill out the screen while on sgs2 with dpi change it still does.
it probably looks so good because of the samoled + subpixel density stuff

It makes it look extremely hi-res. I can't, no, WON'T have my phone at stock DPI, ever.
Sent from my GT-I9100 using xda premium

'Nough said...I switched to 200 and i'm in love baby. Only problem...dialler misplaced and camera screwed up. Any ideas?

my ideea is to live with them, my camera app is fine though
restarted phone today.. and it looks so ugly with the initial dpi

engwee said:
my ideea is to live with them, my camera app is fine though
restarted phone today.. and it looks so ugly with the initial dpi
Click to expand...
Click to collapse
yes camera it's fine at 200 dpi in kg5

[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

Screen dp

So let's talk about the biggest turn off on this phone , not the lack of NFC but the screen resolution , it's not the best and you can learn to adapt to it but here and there the scaling is just bad. Especially for others like my self coming from old flagships with a higher resolution (had an S8 and 720p is quite the downgrade from 1440p).
fortunately enough in developer options there is the option to change how the phone scale by changing the smallest width , mine is set at 480 dp and I like the phone way more than the day I got it ,
share your experience regarding the best settings for the screen scaling !

sounds good, how to do it?
---------- Post added at 01:24 AM ---------- Previous post was at 01:23 AM ----------
... develepor options, didnt read carefully

psycø lucïfer said:
fortunately enough in developer options there is the option to change how the phone scale by changing the smallest width , mine is set at 480 dp and I like the phone way more than the day I got it ,
share your experience regarding the best settings for the screen scaling !
Click to expand...
Click to collapse
Thanks for the sharing man! Love it with 480dp.
It's in Developer Options > Drawing Section > Smallest width

I'm digging 390.

What was the default value ??

360 is default

dragganta said:
360 is default
Click to expand...
Click to collapse
360 seems way to big, makes the phone look like toy, default was 400 something, anyway mine is at 413 and it looks fine

Simran62 said:
360 seems way to big, makes the phone look like toy, default was 400 something, anyway mine is at 413 and it looks fine
Click to expand...
Click to collapse
360 is actually the stock value, it also seems huge to me after setting it at 420

GoelPlz said:
360 is actually the stock value, it also seems huge to me after setting it at 420
Click to expand...
Click to collapse
Ya it was looking huge when i reverted back to 360, so maybe it happened after seeing it at 400+

390 is great.

You can use settings -> display -> GUI size (or interface size, not sure about English term). Values used by system are 320, 360 and 423dp.

now on android 10 increasing the screen's dpi causes the notification bar to cut the battery icon and the clock

Ergeles said:
now on android 10 increasing the screen's dpi causes the notification bar to cut the battery icon and the clock
Click to expand...
Click to collapse
Do you have a screenshot? Maybe it could be solved by increase of the padding.
adb shell settings put secure sysui_rounded_content_padding x

_mysiak_ said:
Do you have a screenshot? Maybe it could be solved by increase of the padding.
adb shell settings put secure sysui_rounded_content_padding x
Click to expand...
Click to collapse
I don't have another phone to show how it looks on the screen, but I've already tried this ADB command, but it looks like it doesn't work on the Mi A3

Ergeles said:
I don't have another phone to show how it looks on the screen, but I've already tried this ADB command, but it looks like it doesn't work on the Mi A3
Click to expand...
Click to collapse
Not sure about Android 10, but it works fine in Android 9.
Return to default value:
Code:
laurel_sprout:/ # settings delete secure sysui_rounded_content_padding
Deleted 1 rows
laurel_sprout:/ # settings get secure sysui_rounded_content_padding
null
Move towards center (experiment with the last number, default is about 8):
Code:
laurel_sprout:/ # settings put secure sysui_rounded_content_padding 10

_mysiak_ said:
Not sure about Android 10, but it works fine in Android 9.
Return to default value:
Code:
laurel_sprout:/ # settings delete secure sysui_rounded_content_padding
Deleted 1 rows
laurel_sprout:/ # settings get secure sysui_rounded_content_padding
null
Move towards center (experiment with the last number, default is about 8):
Code:
laurel_sprout:/ # settings put secure sysui_rounded_content_padding 10
Click to expand...
Click to collapse
{
"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"
}
https://imgur.com/s0IUO6C
https://imgur.com/u5w0v8M
(I just realized that I don't know how to add a photo: p)
any number above 423 starts cutting the battery and the clock
and the commands didn't work here

Thanks for this! Screen looks much sharper because of this! Could be placebo lol

480 works fine, my bigger turn off is the pixels you can view on the screen, you can note it when you see brighter shades on screen. add to that I'm using a matte screen protector ...and I feel this screen guard only enhances the pixel problem.

Galaxy Tab A 10.1
Min - 320dp
Default - 901dp
Max - 1600dp

393 dpi is best

Question Is there a way to change the screen resolution?

I have a Poco F3. I upgraded from a LG V30. On my V30 it allowed you to lower the screen resolution to save battery life among other things. Can you change the screen resolution on the F3? I have not been able to find anything.
Thanks

Alright so you have to understand some basic things first before proceeding:
1.You don't lower the resolution, you merge the pixels or their RGBs.
2.You need an AMOLED display, I hope you do.
3.Any system change requires root permissions and an app / terminal
4.To get into / (root partition) you need both root and a working app to do your job, both are dangerous.
5.Any 3rd party app must support root permissions
After all this, you will need:
A) Software with root permission supported, that can do that job
B) A rooted phone and sudo installed probably
I'm not gonna get deeper, these are just the basics.To lower a resolution you will need to merge pixels, which is a VERY HARD process that will consume time for no reason.

AndroGR said:
Alright so you have to understand some basic things first before proceeding:
1.You don't lower the resolution, you merge the pixels or their RGBs.
2.You need an AMOLED display, I hope you do.
3.Any system change requires root permissions and an app / terminal
4.To get into / (root partition) you need both root and a working app to do your job, both are dangerous.
5.Any 3rd party app must support root permissions
After all this, you will need:
A) Software with root permission supported, that can do that job
B) A rooted phone and sudo installed probably
I'm not gonna get deeper, these are just the basics.To lower a resolution you will need to merge pixels, which is a VERY HARD process that will consume time for no reason.
Click to expand...
Click to collapse
{
"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"
}
Screen shots from my V30 and it's ability to change resolution. Now granted I know little of phone screens but it seems like something that can be done. I was just looking to see if a app or hidden setting existed. Was LG able to do it because of different screen tech?

second screenshot could not get it to attach to my response.

nate600 said:
View attachment 5375195second screenshot could not get it to attach to my response.
Click to expand...
Click to collapse
is that stretched?

In windows on a desktop if you go to System, Display, Display Resolution, you can adjust the resolution to fit your connected display. On my Old LG V30 you could do the same thing to improve performance / save battery. With the principle being the lower the resolution the easier it is for the GPU to draw. Like dropping a First person shooter from 4K to 1440p to get higher frame rate.
But instead of being one app on the LG V30 it was the whole phone, all apps and video's, etc.. would run at the adjusted resolution. Why cant it be done on the Poco F3?

nate600 said:
In windows on a desktop if you go to System, Display, Display Resolution, you can adjust the resolution to fit your connected display. On my Old LG V30 you could do the same thing to improve performance / save battery. With the principle being the lower the resolution the easier it is for the GPU to draw. Like dropping a First person shooter from 4K to 1440p to get higher frame rate.
But instead of being one app on the LG V30 it was the whole phone, all apps and video's, etc.. would run at the adjusted resolution. Why cant it be done on the Poco F3?
Click to expand...
Click to collapse
Xiaomi​

AndroGR said:
Alright so you have to understand some basic things first before proceeding:
1.You don't lower the resolution, you merge the pixels or their RGBs.
2.You need an AMOLED display, I hope you do.
3.Any system change requires root permissions and an app / terminal
4.To get into / (root partition) you need both root and a working app to do your job, both are dangerous.
5.Any 3rd party app must support root permissions
After all this, you will need:
A) Software with root permission supported, that can do that job
B) A rooted phone and sudo installed probably
I'm not gonna get deeper, these are just the basics.To lower a resolution you will need to merge pixels, which is a VERY HARD process that will consume time for no reason.
Click to expand...
Click to collapse
Btw this si wrong you can use Adb

Arealhooman said:
Btw this si wrong you can use Adb
Click to expand...
Click to collapse
Thanks . I thought it should be easy.

if you changed resolution even with adb the notch becomes weirdly stretched, the statusbar becomes weirdly big, letters get weirdly cut

3zozHashim said:
if you changed resolution even with adb the notch becomes weirdly stretched, the statusbar becomes weirdly big, letters get weirdly cut
Click to expand...
Click to collapse
can it be stretched like pc

predict9 said:
can it be stretched like pc
Click to expand...
Click to collapse
what do you mean? fill the screen instead of a small screen in the middle?

3zozHashim said:
what do you mean? fill the screen instead of a small screen in the middle?
Click to expand...
Click to collapse
yes instead of black bars filled

predict9 said:
yes instead of black bars filled
Click to expand...
Click to collapse
yeah fullscreen
for adb:
adb shell
wm size 720x1600
wm density 294
Click to expand...
Click to collapse
for terminal:
wm size 720x1600
wm density 294
Click to expand...
Click to collapse
to reset to normal:
wm size reset
wm density reset
Click to expand...
Click to collapse

3zozHashim said:
yeah fullscreen
for adb:
for terminal:
to reset to normal:
Click to expand...
Click to collapse
no i get black bars on the bottom and top of screen pocof3 i have root btw

predict9 said:
no i get black bars on the bottom and top of screen pocof3 i have root btw
Click to expand...
Click to collapse
are you sure about that? because im not getting any...

3zozHashim said:
are you sure about that? because im not getting any...
Click to expand...
Click to collapse
yes if i put for example 1150x1950 i get black bars on top and bottom i would like it to be stretched do you have a poco f3 or?

predict9 said:
yes if i put for example 1150x1950 i get black bars on top and bottom i would like it to be stretched do you have a poco f3 or?
Click to expand...
Click to collapse
you cant just change resolution and be done with it. you need to change density as well
use wm density and wm resolution to know the stock values then use ratio to set resolution and density

3zozHashim said:
you cant just change resolution and be done with it. you need to change density as well
use wm density and wm resolution to know the stock values then use ratio to set resolution and density
Click to expand...
Click to collapse
bro you know that density doenst change scaling of your screen right it changes only the size of letters apps etc i want basically fill to fit screen and make it like pc

predict9 said:
bro you know that density doenst change scaling of your screen right it changes only the size of letters apps etc i want basically fill to fit screen and make it like pc
Click to expand...
Click to collapse
oh... you are trying to change the aspect ratio...
and why are you using a higher resolution than the one that came with the phone? 1150... 1080...

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