Post Reply Subscribe to Thread Email Thread

[ROM] [NIGHTLY] [KitKat] [4.4] CyanogenMod 11.0 nightlies

21st February 2015, 12:15 AM |#581  
Member
Thanks Meter: 4
 
80 posts
Join Date:Joined: Nov 2008
Edit: sorry I saw in other post an answer to my question. Thanks

Enviado desde mi SM-N9005 usando Tapatalk 2
Last edited by Neodreamer24; 21st February 2015 at 12:18 AM.
26th February 2015, 06:51 PM |#582  
Junior Member
Thanks Meter: 5
 
23 posts
Join Date:Joined: Dec 2007
CM 12?
milaq,

Any chance you're working on CM 12 for the Ouya?
13th March 2015, 01:41 PM |#583  
Junior Member
Thanks Meter: 0
 
12 posts
Join Date:Joined: Oct 2014
720p
What does
setprop persist.tegra.hdmi.resolution 720p
*really* do?

I have the property set, but my monitor and various 'system info' type apps still report 1080. I edited the entry in build.props as well just to test, and still 1080. My monitor definitely supports both 1080 and 720 resolutions. I've tried various builds from early October, through current.

If I open a terminal and use 'wm size' it reports back physical size 1080. I can issue a 'wm size 720p' and apps will start reporting 720p, but 'wm size' then reports physical size 1080 and override size of 720.

I've triple checked my spelling and I am setting the correct persist property. I know things are working because I can alter overscan using setprop and the changes are as expected.

If the persist.tegra.hdmi.resolution property is set to 720p does the internal framebuffer actually get reduced in size, or are graphics still rendered at 1080 internally, then scaled to a 720p output?

Can someone with a working 720p configuration tell me what is reported by 'wm size' in a terminal?

TIA
Jerry
19th March 2015, 08:06 AM |#584  
XirXes's Avatar
Senior Member
Flag Salt Lake City
Thanks Meter: 184
 
208 posts
Join Date:Joined: Jan 2009
Donate to Me
More
Quote:
Originally Posted by jerryfath

What does
setprop persist.tegra.hdmi.resolution 720p
*really* do?

I have the property set, but my monitor and various 'system info' type apps still report 1080. I edited the entry in build.props as well just to test, and still 1080. My monitor definitely supports both 1080 and 720 resolutions. I've tried various builds from early October, through current.

If I open a terminal and use 'wm size' it reports back physical size 1080. I can issue a 'wm size 720p' and apps will start reporting 720p, but 'wm size' then reports physical size 1080 and override size of 720.

I've triple checked my spelling and I am setting the correct persist property. I know things are working because I can alter overscan using setprop and the changes are as expected.

If the persist.tegra.hdmi.resolution property is set to 720p does the internal framebuffer actually get reduced in size, or are graphics still rendered at 1080 internally, then scaled to a 720p output?

Can someone with a working 720p configuration tell me what is reported by 'wm size' in a terminal?

TIA
Jerry

Quote:
Originally Posted by XirXes

I actually ended up modifying this script to also include setting the Ouya's rendering resolution to 720p. Videos outside of xbmc now play properly without pausing.
Attachment 2763784

Setting persist.tegra.hdmi.resolution only changes the output resolution. You need to set the framebuffer resolution with wm size. The script in my old post includes that.

Code:
wm size 1280x720 &
wm density 150 &
Post Reply Subscribe to Thread

Tags
cm-11, custom, cyanogenmod, kitkat, ouya
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes