I'm testing the resolution to 4k and it seems that it looks better than the default 2k. That if the battery goes down something faster.
If you want to try is easy. With adb shell (pc) or console (mobile) put this:
Adb shell wm size 2160x3840
Adb shell wm density 640
The first line is for resolution and the second for density. Never lower the density below 600 with 4k resolution, if you do already know .......... launcher loop and format the mobile.
For mobile by console (app terminal) ....
First enter as root with "su" without quotes and commands:
Wm size 2160x3840
Wm density 640
If you want to return to the default resolution and density
Size wm 1440x2560
Wm density 560
Note that if you do not change the two lines of the dpi option of the build.prop file, some options of the launcher (lock clock and something else) will be seen with the default dpi of the rom (560).
If we change the resolution will not work the screenshots, but by third party app's if (google play). The screenshots are output to 4k and not to 2k.
P.d: The normal or reasonable dpi for 4k is 800-840.
P.d2: Do it under your responsibility (if you do not know, do not touch)
P.d3: The youtube app the maximum that it offers are 2k.
Edit:Really is a 4k screen? Could you implement 4k in the kernel as in xperia z5 premium?
Le max 2 screen is a 2k not 4k
So is it possible to set resolution to 720 or 1080p to improve performance and battery life?
I Issued those command with no error/success and couldn't find option for 4K in video settings. Did I miss anything?
Shished said:
So is it possible to set resolution to 720 or 1080p to improve performance and battery life?
Click to expand...
Click to collapse
Good question. 720p would be ideal as 2K (quad HD) is a direct multiple of 720p (HD), so scaling would be no problem.
Hello,
I change the resolution to Full HD
Adb shell wm size 1080x1920
Adb shell wm density 420
I use the Pixel Launcher and I haven't problems, but I test with default launcher and was deformed.
I don't see how you changed it to 4K when display does not have that amount of pixels... can't you smell this smell?
bdsr said:
Hello,
I change the resolution to Full HD
Adb shell wm size 1080x1920
Adb shell wm density 420
I use the Pixel Launcher and I haven't problems, but I test with default launcher and was deformed.
Click to expand...
Click to collapse
could you watch something about the running time?
xterminater07 said:
Le max 2 screen is a 2k not 4k
Click to expand...
Click to collapse
voolandis said:
I don't see how you changed it to 4K when display does not have that amount of pixels... can't you smell this smell?
Click to expand...
Click to collapse
Heyyo, err... It's called downsampling. It's a technique used generally on PC gaming to improve texture quality and lower aliasing compared to using post processing like FXAA or SMAA as those can have a smear or blurred effect to them sometimes.
Nvidia have Dynamic Super Resolution which is a driver software based solution
https://www.geforce.com/hardware/technology/dsr
AMD went the hardware route so there's less performance hit but more limitations on resolution. Virtual Super Resolution
https://www.amd.com/en/technologies/vsr
With that said? I think the gains on the Le Max 2 downsampling 4K UHD to QHD (2K resolution is technically 2048x1080 also known as 2K DCI... QHD = quadruple HD and HD is 1280x720) would be quite minimal since the pixel per inch of this 5.7" QHD acreen is already so ridiculously high compared to a TV or computer monitor.
Related
Check it out , from minute 1:51 http://www.youtube.com/watch?v=bxeFQ6U4uRM&feature=player_embedded
The iPhone 4 does the same,i wonder what is the reason for that...
darksaber73 said:
The iPhone 4 does the same,i wonder what is the reason for that...
Click to expand...
Click to collapse
i read about the iphone doing the same but i have no clue
ya read that too on gsmarena.. hope they fix it by release time.
It isn't a really terrible issue,but i can't help but keep wondering what's the reason for that zoom.
It wasn't solved on iphone 4 so i guess there's a "deep and technical" reason beyond that.
Maybe the 1080p doesn't divide well into the 8 megapixel camera for easy conversion, so they make the viewable area slightly smaller so it is a nice multiple of the 1080p, because the processor can't handle the load otherwise. Shot in the dark.
Could it be that you can't display a full 1920x1080 video in a 800x480 screen?
Sent from my Captivate.
MikeyMike01 said:
Could it be that you can't display a full 1920x1080 video in a 800x480 screen?
Sent from my Captivate.
Click to expand...
Click to collapse
i doubt it because you cannot display full 720p either ie 1280x720 but it doesnt crop/zoom that image when you video record..
darksaber73 said:
The iPhone 4 does the same,i wonder what is the reason for that...
Click to expand...
Click to collapse
No it doesnt. Double tap your screen and it zooms out.
MikeyMike01 said:
Could it be that you can't display a full 1920x1080 video in a 800x480 screen?
Sent from my Captivate.
Click to expand...
Click to collapse
Naturally it is so and also logical !
How should a 800 x 480 pixel screen show full resolution of 1080 p ? It is not possible physically. Only via HML on the TV-screen You will have full HD res.
troed said:
Naturally it is so and also logical !
How should a 800 x 480 pixel screen show full resolution of 1080 p ? It is not possible physically. Only via HML on the TV-screen You will have full HD res.
Click to expand...
Click to collapse
but how can it display 1280x720?
Chad_Petree said:
but how can it display 1280x720?
Click to expand...
Click to collapse
1) Scale 1280x720 to 800x480, in which case you get an aspect ratio error of 1% which is more than acceptable.
2) Scale 1280x720 to 800x450 and pad the rest with black bars.
Is that what was asked?
For comparison purposes, my Captivate does this also. 720x480 is zoomed; 1280x720 is zoomed further.
martino2k6 said:
1) Scale 1280x720 to 800x480, in which case you get an aspect ratio error of 1% which is more than acceptable.
2) Scale 1280x720 to 800x450 and pad the rest with black bars.
Is that what was asked?
Click to expand...
Click to collapse
450? did you watch the video? the problem seems to be only in 1080p and as far i know 720p and 1080p have the same aspect ratio
Chad_Petree said:
450? did you watch the video? the problem seems to be only in 1080p and as far i know 720p and 1080p have the same aspect ratio
Click to expand...
Click to collapse
450 because it will be the same AR. Anyway, apologies. I should have read further back to see what the actual problem behind the discussion was.
Do we know the reason for this? All of the retail units are doing it.
Its simply a lower viewing angle at higher resolutions, its not that uncommon on video recording devices.
not sure I understand?
The youtube video in the OP shows RECORDING, not playback, right?
When it records in 1080p, the screen shows a zoomed in picture.
This is because the phone cannot take raw 1920x1080 video stream from the camera, and at the same time be encoding it as 1080p and saving it to memory, and downscaling that raw 1920x1080 stream to 800x480 to display on screen. This phone is powerful, but not that powerful. Or maybe that youtube video was of not final software.
Yes it's zoomed, and that's a hack to make it possible to record 1080p.
They've basically just cut off the pixels on the side, and are using 1920x1080 pixels from the centre of the camera's sensor.
This way, it doesn't have to process the "extra" pixels on the side, do pixel binning etc. The sensor is decent enough that 1080p still looks crisp at native res.
Rawat said:
Yes it's zoomed, and that's a hack to make it possible to record 1080p.
They've basically just cut off the pixels on the side, and are using 1920x1080 pixels from the centre of the camera's sensor.
This way, it doesn't have to process the "extra" pixels on the side, do pixel binning etc. The sensor is decent enough that 1080p still looks crisp at native res.
Click to expand...
Click to collapse
Ahh that is what they were showing Makes sense, just like the iP4 then - thanks for the explanation.
Since it's 1920x1080 say I want to go lower like 1680x1050 or 1366x768 or even 1280x720 or other such type of resolutions?? I think that might be a way to save a bit of battery since I don't think I'd notice a slightly lower resolution.
Just curious if such a thing is possible.
Try Resolution Changer from the playstore.
Coming from the S7 edge which ran smoothly with 2k res, the new s8 on the same res is much slower.
Has anyone experienced the same problem?
By running, simple animations, or heavy 3d games?
You have to be more specific
The UI animations, closing / opening apps animations etc...
ssking said:
The UI animations, closing / opening apps animations etc...
Click to expand...
Click to collapse
It's the Touchwiz Launcher that's having the issue. Samsung built this incredible phone but they can't optimize the one app you interact with more than anything! The dropped animations when closing some apps (especially closing any browser) are maddening! I promise you if you install Nova Launcher you will see a pretty dramatic difference.
But it doesn't happen with fhd+...
Try nova launcher, btw 2k resolution is 1080p.
peachpuff said:
Try nova launcher, btw 2k resolution is 1080p.
Click to expand...
Click to collapse
2k is 1440, 1080 is Full HD, 720 is HD. 4K is 3840 if im not wrong.
ryanchua0202 said:
2k is 1440, 1080 is Full HD, 720 is HD. 4K is 3840 if im not wrong.
Click to expand...
Click to collapse
3840 is called 4k because it has 4000 pixels, so tell me why 1920x1080 isn't called 2k? Its exactly half of 4k and has almost 2000 pixels width wise.
2560x1440 is technically 2.5k but no one calls it that, the 2k and 4k names normally are used for tv/movie resolutions.
peachpuff said:
3840 is called 4k because it has 4000 pixels, so tell me why 1920x1080 isn't called 2k? Its exactly half of 4k and has almost 2000 pixels width wise.
2560x1440 is technically 2.5k but no one calls it that, the 2k and 4k names normally are used for tv/movie resolutions.
Click to expand...
Click to collapse
That's just how it's called. I have no idea why, but a quick google gave this: https://forums.evga.com/m/tm.aspx?m=1874357&p=1
---------- Post added at 12:03 PM ---------- Previous post was at 12:01 PM ----------
BTW, to OP: If you're talking about opening/closing apps, it has to do with the launcher, as Touchwiz launcher has its own set of animations which isn't very optimised for 2K resolution yet. Nova launcher helps change the animations. If you're talking about switch off/on the display, I get that some times too, on 2K.
ryanchua0202 said:
That's just how it's called. I have no idea why, but a quick google gave this: https://forums.evga.com/m/tm.aspx?m=1874357&p=1
Click to expand...
Click to collapse
I don't see anything that supports your argument in that link, it supports mine more than yours.
The problem has been solved with QG5 (July 2017) update.
nwver used touch wiz launcher on s8, only Nova launcher installed as system app, there is never any lag at all, not once.
Sent from my SM-G955F using Tapatalk
peachpuff said:
I don't see anything that supports your argument in that link, it supports mine more than yours.
Click to expand...
Click to collapse
yeah, 2k is 1440 1080 is FHD...
wulvz said:
yeah, 2k is 1440 1080 is FHD...
Click to expand...
Click to collapse
Right because 2560x1440 is around 2000 pixels wide
peachpuff said:
3840 is called 4k because it has 4000 pixels, so tell me why 1920x1080 isn't called 2k? Its exactly half of 4k and has almost 2000 pixels width wise.
2560x1440 is technically 2.5k but no one calls it that, the 2k and 4k names normally are used for tv/movie resolutions.
Click to expand...
Click to collapse
I agree with you. 2560x1440, is 3k. It seems they seem to round up so that I don't get how they keep referring to 3840 to 4k and just half assing the others.
I mean, 720p works just fine and all, but when it's docked it basically looks like you're taking a magnifying glass to the screen, as there's like a line between each pixel that's noticeably visible. You don't notice it in handheld obviously due to the size and resolution of that screen, but it can be annoying when it's hooked up into a 22' monitor that's right in front of muh face.
This build of Android is 1080p on the 720p screen & outputs 1080p unless you flash the 720p image.
Mechaghostman2 said:
I mean, 720p works just fine and all, but when it's docked it basically looks like you're taking a magnifying glass to the screen, as there's like a line between each pixel that's noticeably visible. You don't notice it in handheld obviously due to the size and resolution of that screen, but it can be annoying when it's hooked up into a 22' monitor that's right in front of muh face.
Click to expand...
Click to collapse
Those spaces between each pixel are an effect of your display, not of the signal. The screen can't render natively in 720p unless it's a 720p screen, it can only render at its native resolution, which means the space between the pixels is the same no matter what.
Jdbye said:
Those spaces between each pixel are an effect of your display, not of the signal. The screen can't render natively in 720p unless it's a 720p screen, it can only render at its native resolution, which means the space between the pixels is the same no matter what.
Click to expand...
Click to collapse
My monitor is 1920x1080p. I don't get that effect with my PC or when I have my Switch running normally and hooked into it. Only when in Android mode does it do that.
Jdbye said:
Those spaces between each pixel are an effect of your display, not of the signal. The screen can't render natively in 720p unless it's a 720p screen, it can only render at its native resolution, which means the space between the pixels is the same no matter what.
Click to expand...
Click to collapse
You are 100% clueless. This build of Android is 1080p only unless you manually change the resolution with an app or flash the 720p image.
techjunky90 said:
You are 100% clueless. This build of Android is 1080p only unless you manually change the resolution with an app or flash the 720p image.
Click to expand...
Click to collapse
That is completely besides the point. I wasn't talking about the ROM at all because it's irrelevant; it's simply not possible for a lower resolution to cause the effect they're describing.
Yeah LCD have fixed resolution. the space between pixel won't become easier to see when it's taking low resolution feed
The version of android I'm using seems to be 720p regardless of if it's docked or not and 60fps portable but only 30fps docked... I use the app screen resize to force 1080p when docked.
Where can I find the build that auto switches to 1080p when docked?
Hi. Just got a new HD10 specifically because I need the 1920x1200 resolution. But it is not currently functioning in that resolution, which is quite obvious by the fact that my stuff doesn't fit on the screen. Went to www.whatismyandroidversion.com and it shows the resolution is 1280x800. Checked wm size in ADB and it says 1920x1200. I have tried googling for a solution, but all I ever get is thousands of useless blogs listing the specifications. So hoping someone here knows what's going on.
How can I actually get the 1920x1200 resolution? Thx.
MCL1981 said:
Hi. Just got a new HD10 specifically because I need the 1920x1200 resolution. But it is not currently functioning in that resolution, which is quite obvious by the fact that my stuff doesn't fit on the screen. Went to www.whatismyandroidversion.com and it shows the resolution is 1280x800. Checked wm size in ADB and it says 1920x1200. I have tried googling for a solution, but all I ever get is thousands of useless blogs listing the specifications. So hoping someone here knows what's going on.
How can I actually get the 1920x1200 resolution? Thx.
Click to expand...
Click to collapse
Do you want to see a native resolution of your Fire tablet?
You can use AIDA64 to view it:
Google Play: https://play.google.com/store/apps/details?id=com.finalwire.aida64
AIDA64 website: https://www.aida64.com/downloads/latesta64droid
know what the native resolution is, it is 1920x1200. But the browsers are only using 1280x800.
So I think this is happening because the device pixel ratio is 1.5. But I cannot figure out how to change this. There is no display scaling in settings, and it doesn't appear to be an ADB command either.
Got it. The pixel density in ADB was 240. 240 / 1.4 = 160. So wm density 160 brought the scale back to 1:1 and the browser is using the full resolution now.