when I use some softwares to check the screen resolution, it shows as 320*533. why? it should be 480*800.
Because the software is wrong, lol.
Maybe it assumes the width is 320, then applies the 5:3 screen ratio to it to arrive at 533. But yes, the software is wrong.
If an application hasn't been updated to support large screens, Android will tell the app that it's running on 320x... and scale it up so it displays properly. The app you're using needs to be updated to support multiple screen resolutions.
finally, i got a screenshot, the picture is 480*800.
Related
So I've discovered that a simple terminal command fixes the black bars on the left and right when outputting through HDMI. It's caused by the tablet outputting a 1280x800 display to a 1280x720 signal. This is easily fixed by changing the device's resolution with the following command:
wm size 720x1280
To revert to the tablet's original resolution, use:
wm size reset
You may need to run the "su" command first for these commands to work, and you do need to be rooted in order for it to work. This will cause some things to get wonky, like the nav buttons disappearing in landscape orientation or the status bar being hard to pull down (perhaps solvable with a change to the DPI), but if you're planning to use this trick for gaming (which was my reason), using something like Smart Launcher 2 with a controller makes this a non-issue. If you want a quick and easy way to switch back and forth, try QuickTerminal on the Play Store and set up both terminal commands as "Quick Commands", or at least that's how I've done it. Now, the picture on your TV will fill the screen. This is as close to Console Mode as we'll probably ever see on this device, so I thought this might help a few people out!
rchrdcrg said:
So I've discovered that a simple terminal command fixes the black bars on the left and right when outputting through HDMI. It's caused by the tablet outputting a 1280x800 display to a 1280x720 signal. This is easily fixed by changing the device's resolution with the following command:
wm size 720x1280
To revert to the tablet's original resolution, use:
wm size reset
You may need to run the "su" command first for these commands to work, and you do need to be rooted in order for it to work. This will cause some things to get wonky, like the nav buttons disappearing in landscape orientation or the status bar being hard to pull down (perhaps solvable with a change to the DPI), but if you're planning to use this trick for gaming (which was my reason), using something like Smart Launcher 2 with a controller makes this a non-issue. If you want a quick and easy way to switch back and forth, try QuickTerminal on the Play Store and set up both terminal commands as "Quick Commands", or at least that's how I've done it. Now, the picture on your TV will fill the screen. This is as close to Console Mode as we'll probably ever see on this device, so I thought this might help a few people out!
Click to expand...
Click to collapse
I've been doing something similar with the NOM Resolution Changer app but I can't get the DPI settings right to match the 720x1280 res. It gets a bit tricky getting back into settings etc after changing the res as my app drawer is inaccessible after doing so. I always just resort back to default with the fail safe timer, I really don't want to get stuck in a resolution which i can't get back out of.
Andy4Shurr said:
I've been doing something similar with the NOM Resolution Changer app but I can't get the DPI settings right to match the 720x1280 res. It gets a bit tricky getting back into settings etc after changing the res as my app drawer is inaccessible after doing so. I always just resort back to default with the fail safe timer, I really don't want to get stuck in a resolution which i can't get back out of.
Click to expand...
Click to collapse
I haven't had that probably making the change manually, and I do believe I tried the app you mention and had the same issue, so you might wanna try testing the terminal command out; if it messes up, you can always reboot the tablet and everything will properly reformat for the lower resolution and then you should be able to change it back with "wm size reset".
rchrdcrg said:
I haven't had that probably making the change manually, and I do believe I tried the app you mention and had the same issue, so you might wanna try testing the terminal command out; if it messes up, you can always reboot the tablet and everything will properly reformat for the lower resolution and then you should be able to change it back with "wm size reset".
Click to expand...
Click to collapse
Thanks rchrdcrg, yeah I'll give it a whirl that way. It is really annoying having those black end sections on the output!!
I've got a chromecast and been trying to get the 'cast screen' option to work using r3pwn's method here http://forum.xda-developers.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193/page167#post55119152
I thought that might be worth a shot to see if the output res remains at 1200 x 800 for the mirror but I can't get a picture to display, only sound, when it connects and tries to cast screen. I'm thinking it probably won't make a difference though as I have just bought a miracast ezcast m2 dongle too and that still displays at the 1200 x 800 resolution when miracast is used. It probably is just a rom limitation at the moment.
Andy4Shurr said:
Thanks rchrdcrg, yeah I'll give it a whirl that way. It is really annoying having those black end sections on the output!!
I've got a chromecast and been trying to get the 'cast screen' option to work using r3pwn's method here http://forum.xda-developers.com/hardware-hacking/chromecast/experimental-enable-mirroring-device-t2812193/page167#post55119152
I thought that might be worth a shot to see if the output res remains at 1200 x 800 for the mirror but I can't get a picture to display, only sound, when it connects and tries to cast screen. I'm thinking it probably won't make a difference though as I have just bought a miracast ezcast m2 dongle too and that still displays at the 1200 x 800 resolution when miracast is used. It probably is just a rom limitation at the moment.
Click to expand...
Click to collapse
Yeah, I "borrowed" a Chromecast from Best Buy and could never get screen casting to work. You might want to see if changing the resolution fixes this issue with Miracast as well... I have a suspicion it will, and that might be useful to some folks. I sure wish I knew how to force the HDMI output to 1080p; it switches over when playing a 1080p video, so I know it's possible, but I don't know enough about development stuff to know how it's doing that, and forcing the resolution to 1080x1920 with the "wm size" command just displays a 1080p picture downscaled to 720p.
try vlc beta off the play store
here's a sort of rant and with a video playback only solution. Not sure how to hide the rant part. I don't forum anything much.
I bought a Belkin miracast adapter off amazon, and have had trouble getting videos playing properly in full screen. It would mirror the 1280x800 with videos played with regular video apps ( MX player, Archos player, stock) which would be 16:10, and would have those bars on either side on both my 1080p insignia tv and our pseudo 720p panasonic (actual res was 1024x768, but at 16:9, which should be illegal to market as a hdtv). I know from previous experience with my galaxy s4, which the samsung video app would mirror only the video at the correct tv resolution, leaving the phone as the remote. You could also use other apps while any video was playing through the samsung watchon (video) app. So randomly downloaded the vlc beta off the play store. It works for the tegra note 7 the same way samsung set up theirs, minus the multitasking(so far). It took me weeks on and off being frustrated with apps that wouldn't recognise that mirroring was enabled to take advantage of the external display. It's kinda whatever now seeing how much time I spent trying to get the video to play properly by itself, for my s4 I tried mhl cables, chromecast, dlna. this works a lot better
So if you just want videos to play, use the vlc player beta. you can use miracast or hdmi. works the same with both. Only if I could miracast surround sound. that would be nice.
I've just started using my tablet and a HDMI cable to run XBMC. This tip has saved me much frustration.
I already use Tasker which can send terminal commands as an action to make it easier. Tasker does have a HDMI plugged state which should allow this to be automated but for some reason tasker doesn't seem to detect it, not sure why yet.
So I've been fiddling a bit more to optimiser the HDMI experience. I've discovered an app called second screen that let's you sert display profiles and launch then the HDMI is plugged in. Thee app sets the size, resolution, dims the screen and force closes the UI to make sure the new settings actually come into effect. It will also revert the changes when the cable is removed. Does need to run on a rooted device but mine is already.
Alright, I'm reaching out to the community for help on this one. With the recent sale on Daydream VR (they're $50 from Google and Verizon right now), I have been trying to optimize my 6P with the VR set. I have tried some of the suggestions on the form, but I'm still having stuttering issues. So I had the idea about lowering the resolution. So I used the "wm size 1080x1920" trick and successfully dropped by resolution down, and adjusted the DPI accordingly. It runs well, however, when I put it in the VR set, the viewing angles are messed up. When I put the headset on, both eyes are not lined up with each other. I fiddled around with all the wm settings I could find (overscan, scaling, etc), and I can confirm that the viewing angle is messed up in the opposite direction when I set the size over 4k.
I used a Display Settings app to look at my settings, and it seems as though the device thinks the actual screen size is changing when I change the resolution, which may be why Daydream is maligning the eye points.
Is there a way to change the resolution while making the device think the screen size has stayed the same? Or is there a way to change this info just for Daydream?
If it's any encouragement, the Daydream apps ran very smoothly with one eye closed at 1080p. The Google Photos app stuttered at 4k but had no problem at 1080. So if we can figure this out, we could have a smoothly running Daydream setup.
razgriz8426 said:
Alright, I'm reaching out to the community for help on this one. With the recent sale on Daydream VR (they're $50 from Google and Verizon right now), I have been trying to optimize my 6P with the VR set. I have tried some of the suggestions on the form, but I'm still having stuttering issues. So I had the idea about lowering the resolution. So I used the "wm size 1080x1920" trick and successfully dropped by resolution down, and adjusted the DPI accordingly. It runs well, however, when I put it in the VR set, the viewing angles are messed up. When I put the headset on, both eyes are not lined up with each other. I fiddled around with all the wm settings I could find (overscan, scaling, etc), and I can confirm that the viewing angle is messed up in the opposite direction when I set the size over 4k.
I used a Display Settings app to look at my settings, and it seems as though the device thinks the actual screen size is changing when I change the resolution, which may be why Daydream is maligning the eye points.
Is there a way to change the resolution while making the device think the screen size has stayed the same? Or is there a way to change this info just for Daydream?
If it's any encouragement, the Daydream apps ran very smoothly with one eye closed at 1080p. The Google Photos app stuttered at 4k but had no problem at 1080. So if we can figure this out, we could have a smoothly running Daydream setup.
Click to expand...
Click to collapse
It's just a guess, but have you tried to edit the build.prop file in order to "mess around" with declared display density over there?
chk27 said:
It's just a guess, but have you tried to edit the build.prop file in order to "mess around" with declared display density over there?
Click to expand...
Click to collapse
Yes, I messed with any of the build.prop settings that dealt with display. I long ago gave up and now have an Axon 7. Good luck to anyone else trying it!
Hi,
after the oreo update my display resolution is set to 4K. Can everyone confirm this?
I have never touched this setting.
Mr.MSB said:
Hi,
after the oreo update my display resolution is set to 4K. Can everyone confirm this?
I have never touched this setting.
Click to expand...
Click to collapse
Aida64 shows the same for me but other apps like cpu-z do not. That shows a random resolution close to 1080p due to the status and navbars so its still only 1080p really when theyre included according to cpu-z just seems that Aida64 can see that its actually a 4K panel though almost as if Aida64 reads the hardware and cpu-z and other apps read the software.
This might explain it. Seems like Aida64 was coded to request the screen to be upgraded to 4k, while still rendering the UI at 1080.
Mr.MSB said:
Hi,
after the oreo update my display resolution is set to 4K. Can everyone confirm this?
I have never touched this setting.
Click to expand...
Click to collapse
No, it's just correctly naming the display physical attributes. the resolution is still 400dpi though, as displayed below it.
Was wondering if this display shows native 4K all the time or has user selectable option for it?
Was super pissed with my XZ Premium being forced to render at 1080p in all but a few apps.
4K is only useful on this size screen for VR, so won't make the same mistake again.
gaijin1% said:
Was wondering if this display shows native 4K all the time or has user selectable option for it?
Was super pissed with my XZ Premium being forced to render at 1080p in all but a few apps.
4K is only useful on this size screen for VR, so won't make the same mistake again.
Click to expand...
Click to collapse
Forced 1080p but you could make the xz 4k all the time through adb look it up
ariy11 said:
Forced 1080p but you could make the xz 4k all the time through adb look it up
Click to expand...
Click to collapse
Thanks for the reply. You answered my question.
Actually, the adb method was only emulated 4K, not native. Still selected the resources from xxhdpi folders and blew them up. Doesn't even select the xxxhdpi higher resolution images for 2K. For the best I guess. then it would scale it down to 1080p before enlarging to 4K adding extra blur.
ariy11 said:
Forced 1080p but you could make the xz 4k all the time through adb look it up
Click to expand...
Click to collapse
What command in adb can force this screen resolution?
For the XZ Premium apparently the following would have worked:
In an ADB shell:
wm size 2160×3840
wm density 820
In my case the wb size command gives me:
Error: bad size 2160×3840
Probably we need another resolution
After change it to 4K, the screenshot have an issue ( not capturing the whole screen as 4k but the screen at a corner with other space in black. How do you guys solve this issue?
wm size 2160×3840
wm density 820
In my case the wb size command gives me:
Error: bad size 2160×3840
Try....2160x3840
Not ....2160*3840
I just placed my xz2p into native 4k mode with the dpi set at 640/xxxhdpi. I really like the increase in real estate and the integer scaling makes everything look crisp.
That said, I've currently got two hiccups (not already mentioned, I also have the screenshoting issue hereto described) related to dpi change:
(1) The monochrome viewfinder is behaving strangely, but still serviceable (wrong aspect ratio & tap to focus doesn't move the focus indicator)
(2) The rotation animation is really broken and is either firing twice or has some other timing related issue.
#1 I can live with, but #2 is a real drag. I've turned the transition animations off in the dev setting, but it still looks really weird when i rotate.
Any ideas? It seems like sony has made some additional changes to deal with the 4k/1080p pop in and out. Simply setting the WM mode doesn't appear to manipulate those hidden settings. Perhaps one of the on phone apps needs to be disabled?
Edit: https://forum.xda-developers.com/xz...20hz-quest-t3852052/post78603665#post78603665
...according to the xzp forums, its not actually 4k? how can one verify this?
Edit2: Saying things that will have me eating crow in no time!
I'm at least somewhat convinced the xzp peps are wrong. I have been swapping the phone from [email protected] dpi to [email protected] dpi. If they are correct either both would look exactly the same or the 4k version would look worse (because of the double scaling). It clearly looks better. A good test to try; make the icons and text as large as you can in nova launcher and switch between the two. If you look at the top and bottom of the dark ring inside the camera icon you'll see clear aliasing at 1080p and smooth curves at 4k. Just a reminder anything that is not a perfect multiple of 160 will always cause scaling on android. same with dpi values over 640.
I've got a pretty decent canon camera(xc10) with 10x optical zoom, once I find the charger for it I'm going to try to get some clean photos of the screen in the two mode and post 100% crops here.
blinksilver said:
I've got a pretty decent canon camera(xc10) with 10x optical zoom, once I find the charger for it I'm going to try to get some clean photos of the screen in the two mode and post 100% crops here.
Click to expand...
Click to collapse
Can you do that? Also a comparison of Instagram, or VSCO high quality photos?
I've been taking some 3840x2160 screenshots on my PC and transferring them to my phone uncompressed. They look really good when i look at them on screen through the gallery: Nice detail, sharp lines etc.
The images are taken in portrait so that when I download them onto my phone, I can rotate them 90 degrees so they fit the screen properly.
The problem is when I go to set the image as a wallpaper, the image becomes compressed ever so slightly. The once smooth lines are now noticeably jagged, even though there seems to be no stretching or scaling of the image. I am able to zoom in to the image to the exact same scale in the gallery and everything seems fine.
To me, there must some kind of process that is converting the image to a lower resolution or compressing the image in some way. My question is how do I stop it so the wallpaper looks nice and sharp.
Anyone know what is going on here who can tell me how I can prevent this?
+1
You've answered this yourself.
Your image is 2160p
The screen is 1440p
Or 1080p if like me you've realised that's m that it's virtually impossible to tell the difference and it's a negligible visual benefit for a significant battery hit.
So resize the image based on the screen you want to use or the phone will do it for you.
Depending on the launcher you're using you it may actually have a size limit and resolution so there should be they to take into account too.
Start by finding out what resolution you're using then get an image for it off the same resolution
dladz said:
You've answered this yourself.
Your image is 2160p
The screen is 1440p
Or 1080p if like me you've realised that's m that it's virtually impossible to tell the difference and it's a negligible visual benefit for a significant battery hit.
So resize the image based on the screen you want to use or the phone will do it for you.
Depending on the launcher you're using you it may actually have a size limit and resolution so there should be they to take into account too.
Start by finding out what resolution you're using then get an image for it off the same resolution
Click to expand...
Click to collapse
I did some additional research into the issue.
The oneplus 8 pro is 3168x1440. It is perfectly capable of displaying a 3840x2160 image with no significant loss of quality. I was able to zoom the image in the photo gallery to cover the entire display (as a wallpaper would) and found the image still looked crisp as it should, yet setting it as a wallpaper caused quality loss despite scaling the same. Clearly the issue was to do with the wallpaper scaling process in android (what the exact issue is i am not sure).
Nevertheless, i downloaded an app from the playstore that was able to fix the issue. The app is called Image 2 Wallpaper on the playstore.