Change resolution from real 720p to real 1080p on the fly useing just 1 kernel (POC)

[leolas]

trying wont hurt;p

And it is a very good try.

[Adainair]

Very good lewy this is many times better than stock 720p, and if is stock 720p real 720p then is this fix real 1080p, because you did not hack system you are just send commands for 1080p, what in display option does not work.
I have file which change resolution in Android 4.1 for odroid board .
Files for 1080p in odroid maybe helps someone ih tweaks

UPDATE
It's shame to this thread is without attention maybe is reason for that Lewy finding.
Lewy you need to change forum this is not place for US.
Sorry

[Pluto]

Terminal for 1080p kernel

su
am display-size 1280x720

Terminal for 720p kernel

su
am display-size 1920x1080

i came around those commands as well, in the 1080p kernel for Strauzos Nexus Rom, the am display-size 1920x1080 makes the screen box shaped and worthless, i use am display-size reset to revert the changes, and then i used am display-size 1920x840, and it seems to produce the same effect and it is the only resolution that fills the screen (of course except 720p)

[lewy20041]

i implemented this into my roms and everything is fine:"

[neomode]

Very good lewy this is many times better than stock 720p, and if is stock 720p real 720p then is this fix real 1080p, because you did not hack system you are just send commands for 1080p, what in display option does not work.
I have file which change resolution in Android 4.1 for odroid board .
Files for 1080p in odroid maybe helps someone ih tweaks

UPDATE
It's shame to this thread is without attention maybe is reason for that Lewy finding.
Lewy you need to change forum this is not place for US.
Sorry

Hello,

Sorry that you are thinking, this is not the right Forum for you.
The Thread has become attenion.
But our People here want Rom´s and not all Technical Intressted.

Ray

[opengl1971]

Well , i tested this thoroughly with more than 6 different roms , i have a theory of what is going on:

The android renders first to an internal frame buffer then scales this frame buffer to the fixed
resolution of the kernel then sends the resulting image out to HDMI connection which may or may not
Scale the image again (depending on the HDMI resolution used)

So what happens when we use this commands to switch to 1080p from a 720p kernel?

First the image will be rendered to a 1080p frame buffer then get scaled once to the 720p kernel resolution Then scaled again from 720p to the tv's resolution of 1080p. ,
the second scaling is what causes this Extreme pixilation as it is up scaling resulting
in obvious blurring.

To test this you can change the HDMI resolution to 720p , you will notice that the result is obviously
Better because the scaling in this case is done only once (from 1080p to 720p kernel resolution)
So in this case although the "am display-size" is 1080p but the result is better with 720p HDMI resolution Which gets along with the theory above.

So what is the use of such an option if it will finally get scaled to the kernel resolution ?
The answer is to enable application developpers to simulate different resolutions so they can
Test their apps performance on different resolutions (reads different devices).

So it is not a real resolution switching as this option only changes the internal drawing area.
(Frame buffer resolution) which previously is set is set to kernel resolution by default.
(Only my 2 cents worth)

[lewy20041]

i came around those commands as well, in the 1080p kernel for Strauzos Nexus Rom, the am display-size 1920x1080 makes the screen box shaped and worthless, i use am display-size reset to revert the changes, and then i used am display-size 1920x840, and it seems to produce the same effect and it is the only resolution that fills the screen (of course except 720p)

on tv boxes/sticks you need to swich this to 1080x1920 then it will work as it should.
have fun

[lewy20041]

Well , i tested this thoroughly with more than 6 different roms , i have a theory of what is going on:

The android renders first to an internal frame buffer then scales this frame buffer to the fixed
resolution of the kernel then sends the resulting image out to HDMI connection which may or may not
Scale the image again (depending on the HDMI resolution used)

So what happens when we use this commands to switch to 1080p from a 720p kernel?

First the image will be rendered to a 1080p frame buffer then get scaled once to the 720p kernel resolution
Then scaled again from 720p to the tv's resolution of 1080p. , the second scaling is what causes this
Extreme pixilation as it is up scaling resulting in obvious blurring.

To test this you can change the HDMI resolution to 720p , you will notice that the result is obviously
Better because the scaling in this case is done only once (from 1080p to 720p kernel resolution)
So in this case although the "am display-size" is 1080p but the result is better with 720p HDMI resolution
Which gets along with the theory above.

So what is the use of such an option if it will finally get scaled to the kernel resolution ?
The answer is to enable application developpers to simulate different resolutions so they can
Test their apps performance on different resolutions (reads different devices).

So it is not a real resolution switching as this option only changes the internal drawing area.
(Frame buffer resolution) which previously is set is set to kernel resolution by default.
(Only my 2 cents worth)

i get to this to;p
but if you use this on 1080p kernel to scale down apps launcher etc. to 720p its gave nice performance boost.

[opengl1971]

i get to this to;p
but if you use this on 1080p kernel to scale down apps launcher etc. to 720p its gave nice performance boost.

Yes because it renders everything to 720p resolution , then upscale the result
To kernel's 1080p.

[Pluto]

on tv boxes/sticks you need to swich this to 1080x1920 then it will work as it should.
have fun

i did, theres no resolution i havent tried. 1080x1920 made a portrait box in the middle of the TV.

i get to this to;p
but if you use this on 1080p kernel to scale down apps launcher etc. to 720p its gave nice performance boost.

well, this might be the reason why this is happening: http://www.freaktab.com/showthread.p...g-a-42-quot-TV

whether 1080p or 720p, browsing on it is a pain-in-the-arse

[lewy20041]

you need to change "am display-density" or build .prop ro.sf.display.density to get normall fonts:"

[Pluto]

now forgive me for being the PITA now but whats the best mixture of density/resolution then when your screen is at 1920x1080?

[neomode]

Try it with 240.

Neomode

[lewy20041]

yap.
neo is right
240 for 1080p and 160 for 720p

[Pluto]

I guess it might work, some apps showed i had a 160 DPI, will try it as soon as i get home.

Also, as i said before, ScreenInfo app, why does it say that height is 840? Again, im on Nexus 1.2 which i flashed directly with the 1080p Kernel.