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

[Q] Old Eyes, need help fixing

Hi all,
I love my Tab S 8.4, it's light, elegant, fast with the replacement ROM Definitive ROM NF9. But my old eyes don't like the tiny fonts under icons, as well as in a variety of applications. I've changed the font size in the settings to Extra Large, but that doesn't really help in most apps. One of the reasons I switched to tablets and ereaders was to not have to put on readers every time I want to look at anything.
I've tried using Textdroider to increase the size of things, but it just created a SystemUI bootloop.
Has anyone figured out a way to make everything larger? Without crashing the system? I've also tried using Xposed module App Settings but nothing seems to happen when I use it.
Would love to solve this, otherwise a lower resolution tablet might be in my future. Wish there was something simple like the scaling option in Windows 7.
Thanks for the help.

android94301 said:
Hi all,
I love my Tab S 8.4, it's light, elegant, fast with the replacement ROM Definitive ROM NF9. But my old eyes don't like the tiny fonts under icons, as well as in a variety of applications. I've changed the font size in the settings to Extra Large, but that doesn't really help in most apps. One of the reasons I switched to tablets and ereaders was to not have to put on readers every time I want to look at anything.
I've tried using Textdroider to increase the size of things, but it just created a SystemUI bootloop.
Has anyone figured out a way to make everything larger? Without crashing the system? I've also tried using Xposed module App Settings but nothing seems to happen when I use it.
Would love to solve this, otherwise a lower resolution tablet might be in my future. Wish there was something simple like the scaling option in Windows 7.
Thanks for the help.
Click to expand...
Click to collapse
You can try to change the DPI..
Basically, by setting a higher value everything will be bigger. (But too much and it will become ugly/unresponsive)
There are 2 ways to do this:
1) Change the DPI for the whole device:
This can be done by changing it in the file build.prop.
Afterwards reboot and you're set.
2) Change the DPI per app
Download + install Xposed Framework.
Then open XPosed, go to download and look for the module "App Settings".
Install it, activate it & reboot the device.
Afterwards you can change the DPI settings for each app individually with the App Settings app.
I would advice that you try option 2, as this gives you more options aswel as the changes are immediatly, and you don't have to worry about editing or messing up build.prop.

shifter7 said:
You can try to change the DPI..
Basically, by setting a higher value everything will be bigger. (But too much and it will become ugly/unresponsive)
There are 2 ways to do this:
1) Change the DPI for the whole device:
This can be done by changing it in the file build.prop.
Afterwards reboot and you're set.
2) Change the DPI per app
Download + install Xposed Framework.
Then open XPosed, go to download and look for the module "App Settings".
Install it, activate it & reboot the device.
Afterwards you can change the DPI settings for each app individually with the App Settings app.
I would advice that you try option 2, as this gives you more options as well as the changes are immediately, and you don't have to worry about editing or messing up build.prop.
Click to expand...
Click to collapse
I tried both, as Textdroider changes build.prop. Also, App Settings doesn't seem to change anything. Even after I reboot apps like Opera, or Feedly, still have small fonts. What numbers should I use with it? I tried 400 for dpi and 150 for font scaling.
Thanks for any help with this.

As you found out, changing dpi will give you boot loop. Not a lot you can do.
Feedly is hopeless. The font size is tiny. Try using Amber or gReader.
As for the web, you are at the mercy of web coders. If they use relative font size, you can increase with text scale. If they use absolute font size, which so many of them do, you are stuck. You can try another browser like Firefox to see if its text scaling works any better.

Hi if you are still interested I have a solution. It's not so simple though.
Install the CM12 build (lollipop)
http://forum.xda-developers.com/showthread.php?p=57853197
It's very smooth and stable. Some hardware stuff are missing, because CM12 is new and also Samsung is not helping out the devs any with their lack of driver code release.
Anyway, changing the DPI on this Rom will work. Here's a screen shot of my tapatalk. You can see how big the fonts are at 400 dpi
{
"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"
}
I tried it with DPI changer but it did not take. I just ended up changing /system/build.prop myself. Change permission to 666, open in any text editor, look for
ro.sf.lcd_density=320
and change 320 to 400. Save and reopen file to verify that the change you made sticks. Then change file permission back to 644.
There's another file /system/media/lcd_density.txt. It just contains the text 320. I changed it to 400. I don't know if that is necessary or not but did it anyway. Same procedure above applies.
Reboot and cross your fingers.
If that works, you can experiment and change to something other than 400 if you want. You'll want to do a full nandroid back up before doing this.

Thanks for a solution that isn't "wear readers"
barth2 said:
Hi if you are still interested I have a solution. It's not so simple though.
Install the CM12 build (lollipop)
http://forum.xda-developers.com/showthread.php?p=57853197
It's very smooth and stable. Some hardware stuff are missing, because CM12 is new and also Samsung is not helping out the devs any with their lack of driver code release.
Anyway, changing the DPI on this Rom will work. Here's a screen shot of my tapatalk. You can see how big the fonts are at 400 dpi
I tried it with DPI changer but it did not take. I just ended up changing /system/build.prop myself. Change permission to 666, open in any text editor, look for
ro.sf.lcd_density=320
and change 320 to 400. Save and reopen file to verify that the change you made sticks. Then change file permission back to 644.
There's another file /system/media/lcd_density.txt. It just contains the text 320. I changed it to 400. I don't know if that is necessary or not but did it anyway. Same procedure above applies.
Reboot and cross your fingers.
If that works, you can experiment and change to something other than 400 if you want. You'll want to do a full nandroid back up before doing this.
Click to expand...
Click to collapse
Thanks, that is very helpful...I'm not clear on the hardware limitations of the lollipop build though. I don't care about the fingerprint reader, probably don't even care about the camera, but would want the sound system to work well. Wifi of course too, but bluetooth not so much. What are the limitations of the CM12 lolli build you are running to get the dpi to 400?

Wi-Fi works, it would not be useable otherwise It only seems to connect to my router on 2.4ghz and not 5ghz, but speed is good. Audio works fine. Camera works. When you take a selfie it says cannot connect to camera but it actually does work anyway. I haven't tried Skype. Blue tooth works but I don't have any device to test it with at the moment. I think things like IR and NFC don't work and may never do. No big loss as fat as I'm concerned.
Main issue right now is you need to disable hardware overlay for video to work. This means that you take a performance hit when it comes to graphics, and probably more battery drain than otherwise. Practically speaking, I notice a little bit more blurring with video. 3Dmark is like 5% lower than average score with hardware overlay disabled. Not a huge deal. Netflix, YouTube, Amazon video, MX player, BS player are all working for me.
Overall, the OS is smoother and less laggy than stock. You get all the lollipop goodness, too, of course. CM12 is in early beta and there's not even official CM support for this tablet yet so things can only get better.
If your eyes don't glaze over when you hear things like nandroid backup, recovery, etc, definitely give it a shot.

[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

Question Horizontal split screen in Portrait orientation

My question is, is there a way to have a split screen mode in portrait orientation where the apps are above/below each other, instead of left and right? Just like how a phone would handle this.
What i have right now
What i want
Each window has a handle, but you can only swap they position, instead of changing the alignment.
Thanks!

If you turn off miui optimizations you'd get the normal split screen but I noticed the 3 fingers screenshot won't work also.

Half Alive said:
If you turn off miui optimizations you'd get the normal split screen but I noticed the 3 fingers screenshot won't work also.
Click to expand...
Click to collapse
This is weird, i can't find it in the dev options, but it shows up in the search. If i click on the search result it only brings me into Dev options, since the checkbox is missing.
https://imgur.com/Ixgj8WX
EDIT:
Imagine googling stuff first...
https://piunikaweb.com/2021/04/19/m...ing-in-developer-options-try-this-workaround/
Worked, thanks!
*EDIT2:*
If someone arriving to this thread later on, i'm on version 12.5.8.
Also as i seems, disabling the optimization, you have to give up on floating windows too.
EDIT3:
since MIUI 13, disabling the optimization, won't disable floating windows.

Unfortunately this wasn't fixed in MIUI 13, which is pretty disappointing.

S0und_ said:
Unfortunately this wasn't fixed in MIUI 13, which is pretty disappointing.
Click to expand...
Click to collapse
In the latest version of miui 13 by disabling the optimization does it still allow you to do the horizontal split screen?
Im thinking of buying this tablet but horizontal split screen in portrait mode is essential for me
Also can you move the split bar making one app bigger?

RaFePt said:
In the latest version of miui 13 by disabling the optimization does it still allow you to do the horizontal split screen?
Im thinking of buying this tablet but horizontal split screen in portrait mode is essential for me
Also can you move the split bar making one app bigger?
Click to expand...
Click to collapse
It still does but somehow it looks broken when you open recent app, probably using GSI rom would be better.. also split screening setting will crash the system ui, idk why..

RaFePt said:
In the latest version of miui 13 by disabling the optimization does it still allow you to do the horizontal split screen?
Im thinking of buying this tablet but horizontal split screen in portrait mode is essential for me
Also can you move the split bar making one app bigger?
Click to expand...
Click to collapse
Interesting, it's still MI UI 13 but turning off optimization split screen works in portrait. Previously you've lost the floating window feature because of that, so it's not really worth it. Although it's still broken a bit. So in landscape you can resize the apps in a 33/66 or 50% or 66/33 ratio. In portrait you only have 50% 33/66 doesn't work its snaps back to 50.
{
"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"
}

Sorry if I'm bothering you but I'm really conflicted between this Xiaomi pad 5 and the Lenovo tab p11 pro, their the same price over here
I love the xiaomi but I'm scared of the software, do videos (YouTube in full screen, netflix, chrome) still play in the split screen (portrait) while using other apps?
Also what do you mean by broken?
S0und_ said:
Interesting, it's still MI UI 13 but turning off optimization split screen works in portrait. Previously you've lost the floating window feature because of that, so it's not really worth it. Although it's still broken a bit. So in landscape you can resize the apps in a 33/66 or 50% or 66/33 ratio. In portrait you only have 50% 33/66 doesn't work its snaps back to 50.
Click to expand...
Click to collapse

RaFePt said:
Sorry if I'm bothering you but I'm really conflicted between this Xiaomi pad 5 and the Lenovo tab p11 pro, their the same price over here
I love the xiaomi but I'm scared of the software, do videos (YouTube in full screen, netflix, chrome) still play in the split screen (portrait) while using other apps?
Also what do you mean by broken?
Click to expand...
Click to collapse
Sorry, forgot to answer your question.
I'm not sure about the performance difference between to two tablets, but Lenovo tab p11 pro has a OLED screen, that's a big plus. Although Xiaomi's LCD is good enough for general content consumption, but it's not good enough for HDR movies. In my country the P11 pro was 30% more expensive then the Tab5, and although i would prefer an OLED screen, i was not willing to pay that much.
You can playback two videos in two different apps in portrait split screen. I've tested this with Youtube and Twitch. What you have to keep in mind, that portrait split screen is stuck in 50-50% app ratio. You have no option to change it to 33/66% which you can do in horizontal.

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