Related
It turns out that the recently circulating hulu-capable hacked version can and does play back at full 30fps in 720p on the Transformer. Success!
This lead me to question why it would work though. I downloaded this hacked version (Google search it, I won't link it here) and also downloaded the original 10.3.185.22 version it is based on (it's about 2 months old). Testing the hacked version and I do indeed get hardware accelerated 720p. I disassembled them to figure out what was changed between the hacked and the official version and the only change is one line in the Flash Player library that reports to the browser what version of flash is running (Sort of like a UA string hack for Flash). This isn't enough to disable hardware acceleration though, and guess what: strangely enough, I also get hardware acceleration on the non-hacked version as well. Crazy that!
So, the tl;dnr version: For some reason, the latest Flash Player does not accelerate 720p video. I still don't know why. An older version (10.3.185.22) DOES accelerate Flash and can be used to fix this nagging problem. Download it here:
http://www.filesonic.com/file/1037676654
OR HERE:
http://dl.dropbox.com/u/10724980/Flash.Player.10.3.185.22.Android.apk
To install:
First remove any installed version of flash (go to market -> my apps -> Flash Player -> uninstall)
Copy the downloaded .APK to your device and run. No root required, but you will need to turn on non-market app installs.
Before testing, reboot into recovery and wipe cache. (The whole point is to wipe the browser cache - People report that this helps. If you like, you can just go to settings -> applications -> manage applications -> All -> Browser -> Wipe Cache)
Test playback on 720p stream or use http://www.youtube.com/my_speed and look at what the 'video fps' tells you
EDIT: You may have to run this in the STOCK BROWSER. Opera calls the Froyo version of the library which does not allow for hardware accelerated playback.
Some other notes:
The youtube test video still reports software decoding - this is normal, it's looking for the PC HW accel module, which Android does not have.
Some people are still have trouble making this work. I'll admit, it's sort of like voodoo - I've torn through the files in the .APK and the only file that is changed in the old version is a compiled library that I can't (legally) decode. Without source code, I still can't tell you why it works for some but not for others.
Apparently some people never had problems in the first place. Congratulations - we don't need to hear about it here. Unless you know why it works for you and not for others, don't add to the length of this thread.
It's not the latest version, but nothing significant has been added since this one, and at least it works right!
sassafras
It Works!
Here is the link where I got my flash: forum.xda-developers.com/showthread.php?t=1076612
About damn time!
xTRICKYxx said:
Here is the link where I got my flash: forum.xda-developers.com/showthread.php?t=1076612
About damn time!
Click to expand...
Click to collapse
This version is the modified 10.3.185.22 version that is NO DIFFERENT than the official .22 version except for the modification one line that tells the browser it is a Windows based version of flash instead of Android.
If you install this version of Flash, hardware acceleration works but you cannot update via the Market (even though it tell you that you have an update) because it will fail every time.
The official version I linked will not play Hulu but does update via the market and at least for now, seems to retain hardware acceleration.
sassafras
xTRICKYxx said:
Here is the link where I got my flash: forum.xda-developers.com/showthread.php?t=1076612
About damn time!
Click to expand...
Click to collapse
Installed this, still getting ****ty framerate on youtube test.
Gary13579 said:
Installed this, still getting ****ty framerate on youtube test.
Click to expand...
Click to collapse
Strange.
Gary, can you ADB to your device?
If so, can you
Code:
adb uninstall com.adobe.flashplayer
And then try installing this. Note that it does take a few seconds for the video framerates to stabilize due to some inherent WiFi flakiness in the ASUS drivers.
sassafras
I don't have access to adb atm, but I figured uninstalling Flash through the GUI rather than adb would have the same effect (and I did uninstall Flash before installing that version). I also tried restarting the browser, cycling opengl on/off, and rebooting the entire device.
After the intro, it still falls to 3-5 FPS on youtube.com/my_speed on 720p.
just uninstall the hacked version then install market version and the ability to play 720p at 30 fps seems to persist.
Sent from my Transformer TF101 using Tapatalk
Gary13579 said:
I don't have access to adb atm, but I figured uninstalling Flash through the GUI rather than adb would have the same effect (and I did uninstall Flash before installing that version). I also tried restarting the browser, cycling opengl on/off, and rebooting the entire device.
After the intro, it still falls to 3-5 FPS on youtube.com/my_speed on 720p.
Click to expand...
Click to collapse
To be honest, it really makes little sense why it works. The old version works and the new version works when updated via the market (though it shouldn't because it overwrites everything) so honestly, I can't really troubleshoot to any degree.
My advice would be to just nuke anything in the /data/data/com.adobe.flashplayer location, then install my linked version. Install that, update via the market (You might have to reboot or use Titanium Backup to get it to attach to the market) and see if it works. There is no good reason why it didn't work in the first place, and there is even less why it works now. It's like a ghost in the machine.
sassafras
sassafras_ said:
It turns out that the recently circulating hulu-capable hacked version can and does play back at full 30fps in 720p on the Transformer. Success!
This lead me to question why it would work though. I downloaded this hacked version (Google search it, I won't link it here) and also downloaded the original 10.3.185.22 version it is based on (it's about 2 months old). Testing the hacked version and I do indeed get hardware accelerated 720p. I disassembled them to figure out what was changed between the hacked and the official version and the only change is one line in the Flash Player library that reports to the browser what version of flash is running (Sort of like a UA string hack for Flash). This isn't enough to disable hardware acceleration though, and guess what: strangely enough, I also get hardware acceleration on the non-hacked version as well. Crazy that!
So, the tl;dnr version: For some reason, the latest Flash Player does not accelerate 720p video. I still don't know why. An older version (10.3.185.22) DOES accelerate Flash and can be used to fix this nagging problem. Download it here:
http://www.filesonic.com/file/1037676654
OR HERE:
http://dl.dropbox.com/u/10724980/Fla...22.Android.apk
To install, first remove any installed version of flash (go to market -> my apps -> Flash Player -> uninstall) then copy to your device and run. No root required, but you will need to turn on non-market app installs.
It's not the latest version, but nothing significant has been added since this one, and at least it works right!
sassafras
Click to expand...
Click to collapse
Works great! Haven't tried updating to the lastest verson through market though. Yet, it's still not as smooth as my GS2, don't know if it's the limitation of Terga2.
Sent from my GT-I9100 using XDA App
hongkongtom said:
Works great! Haven't tried updating to the lastest verson through market though. Yet, it's still not as smooth as my GS2, don't know if it's the limitation of Terga2.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
It's not a limitation of the Tegra as much as it is a limitation of the screen size. With a larger screen you have more pixels to push and that strains the hardware when it's not designed for it. Unfortunately, the Tegra GPU wasn't ever really designed for tablet resolutions - but it works and they use it - it's just not going to match the only 480x800 display (in the SGS2) in terms of fluidness.
sassafras
Gary13579 said:
I don't have access to adb atm, but I figured uninstalling Flash through the GUI rather than adb would have the same effect (and I did uninstall Flash before installing that version). I also tried restarting the browser, cycling opengl on/off, and rebooting the entire device.
After the intro, it still falls to 3-5 FPS on youtube.com/my_speed on 720p.
Click to expand...
Click to collapse
I have a similar issue. I uninstalled via settings/applications and then used terminal to verify that /data/data/com.adobe.flashplayer did not exist.
I get about 6 fps. I even tethered to my phone to get a faster download because my DSL speed was too slow to keep up.
I have stock 3.1 rooted.
Yeah, it's becoming clear to me that this is not an exact science. There isn't actually any reason why it shouldn't hardware accelerate on the market version when it does on the hacked (or just plain old) version.
Note that the youtube.com/my_speed video does report two frame rates, one titled "stage fps" and one "video fps" - it's that second one that is reporting the true decode speed. Also, if you're seeing spinning dots in the middle, that's your internet too slow to keep up, not your device.
If you're having no luck with the official .22 point release I linked, try using the hacked version linked in the second post and see if that changes anything.
sassafras
okay installed this flash (hulu verison) and now opera 11 shows that flash is not install...anyone else having this issue?
I tried the linked version as well- not sure what is different but it does have a different checksum.
Perhaps I have to actually watch a hulu video first?
--- I poked around at some of the methods and the ones that flash via clockwork mod also install some libs- perhaps that this the other piece of the puzzle? It's bedtime here, so 30 fps will have to wait until later...
After uninstalling the newest version and installing the .22 modified one I am getting 30fps and little dropped frames in the speed test on the stock browser. Unfortunately Opera is still showing around 10fps.
gee one said:
I tried the linked version as well- not sure what is different but it does have a different checksum.
Perhaps I have to actually watch a hulu video first?
--- I poked around at some of the methods and the ones that flash via clockwork mod also install some libs- perhaps that this the other piece of the puzzle? It's bedtime here, so 30 fps will have to wait until later...
Click to expand...
Click to collapse
I've explained this in detail in the OP but basically the .apk just installs the libraries to it's personal /data/data/ directory and the browser is able to dynamically load them from there. There is no need to install additional libraries because all four of the shared libraries flash requires are installed by installing the .apk.
Adkinson said:
After uninstalling the newest version and installing the .22 modified one I am getting 30fps and little dropped frames in the speed test on the stock browser. Unfortunately Opera is still showing around 10fps.
Click to expand...
Click to collapse
Yes, unfortunately, Opera loads the libstagefright_froyo.so instead of the libstagefright_honeycomb.so which is the required library for hardware accelerated playback. I'll mention this in the OP.
sassafras
Could you fix the OP to include a proper dropbox link? It isn't possible to use fileserve on the TF.
http://imgur.com/5BujJ
Fastest I've managed. And that's a rlatively static image. Even slower when not overclocking. Please post what ROM, kernel, CPU speed etc you guys are using.
Gary13579 said:
Could you fix the OP to include a proper dropbox link? It isn't possible to use fileserve on the TF.
Click to expand...
Click to collapse
All better.
Are you by chance using a non-stock browser?
sassafras
God no, they're all worses than stock browser in my opinion. At least unil OnLive releases theirs!
Think I figured it out, the link in post #2 is bad. After using the APK posted in the other thread, it works great. Fired up Big Buck Bunny on YouTube and i was as smooth as could be. Thanks .
I don't know about you guys, but my Ouya stays on 1080p all of the time. This would normally be great for most uses, but Mupen64plus is a tad laggy at 1080p. I'd rather play at 720p so things might be smoother.
I googled a bunch, but couldn't find much on how to force a manual resolution change (short of buying a 720p-only TV…not an option).
I did some digging of my own. Here's what I found:
In /sys/class/graphics/fb0 are several files I believe are related to HDMI output:
"cat mode" displays:
D:1920x1080p-60
Click to expand...
Click to collapse
"cat modes" displays:
D:1360x768p-60
D:1280x720p-60
D:640x480p-60
D:640x480p-72
D:640x480p-74
D:800x600p-59
D:800x600p-72
D:800x600p-74
D:1024x768p-60
D:1024x768p-70
D:1024x768p-74
D:720x480p-59
D:1920x1080p-60
D:1920x1080p-24
D:1920x1080p-30
Click to expand...
Click to collapse
I figured I would take a shot at changing the resolution to 720p. I performed the following as root:
echo "D:1280x720p-60" > mode
Click to expand...
Click to collapse
When I ran the command, the screen went blank (at least it did something, lol).
I then tried to change back to D:1920x1080p60 with the following
echo "D:1920x1080p-60" > mode
Click to expand...
Click to collapse
The screen remained blank. I tried several other modes in the list 600p, 480p, 768p, but none worked. I set mode to D:1280x720p-60 and rebooted the Ouya. The console booted back up, but it was still in 1080p. I checked the mode file. It had reverted back to D:1920x1080p-60.
Hopefully this helps us get somewhere
I need this on my TV, I haven't checked what it's outputting thru adb(it's connected to comp atm) but it's oversizing when I first got the console. My guess is it's forcing 1080p on the TV.
Sent from my GT-P1000 using Tapatalk HD
I've got the same issue, there's really no reason to not have settings for this, it's really stupid :/
GizmoTheGreen said:
I've got the same issue, there's really no reason to not have settings for this, it's really stupid :/
Click to expand...
Click to collapse
If it's just leaking a bit off the screen you need to go into your TV settings and adjust overscan. I've plug it into 2 1080 and 2 720 tvs and have had no issue besides that.
I have a cheap insignia tv with no overscan settings, only zoom, and even the best one doesn't show everything...
For years I didn't know my tv had it. Mine calls it "hd size" hidden 3 menus deep.
Size 2 is what I set it to
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
FrostyWolf said:
If it's just leaking a bit off the screen you need to go into your TV settings and adjust overscan. I've plug it into 2 1080 and 2 720 tvs and have had no issue besides that.
Click to expand...
Click to collapse
it's quite alot missing and my tv has no overscan settings. there was 16:9, 4:3, zoom 1 and zoom 2. neither helped any (zoom just made it worse)
it's a 1366x768 resolution tv but it obviously takes 1080p and scales it down (my ps3 works fine in 1080p!)
I'm hoping 720p output from the ouya would solve it.
GizmoTheGreen said:
it's quite alot missing and my tv has no overscan settings. there was 16:9, 4:3, zoom 1 and zoom 2. neither helped any (zoom just made it worse)
it's a 1366x768 resolution tv but it obviously takes 1080p and scales it down (my ps3 works fine in 1080p!)
I'm hoping 720p output from the ouya would solve it.
Click to expand...
Click to collapse
Strange! I've tried in on a couple of monitors of various resolutions and sizes since my last post, but same on all of them, so I can't even replicate this to test options to fix it :/
FrostyWolf said:
Strange! I've tried in on a couple of monitors of various resolutions and sizes since my last post, but same on all of them, so I can't even replicate this to test options to fix it :/
Click to expand...
Click to collapse
I seem to have slight more luck doing this:
1. echo 0 > /sys/class/graphics/fb0/device/enable
2. echo (videomodefrommodesfile) > /sys/class/graphics/fb0/mode
3 echo 1 > /sys/class/graphics/fb0/device/enable
atleast I get picture after doing this but it's the top half center of the screen only... :/
I don't have my ouya yet but try an app like anycut that allows you to make activity shortcuts. I used it on my htc evo 4g lte to make a shortcut that would change the screen resolution to 480p. Also maybe a build.prop edit would work.
Nope tested out anycut it's a no go
I intend to use this primarily on a 4:3 display, through a VGA adapter.
What sucks is that no matter what /sys/class/graphics/fb0/mode is set to (1280x1024 in my case), the Ouya insists on only using a 16:9 viewable area... restricting games like Towerfall and retro emulators to a little box in the middle of the screen.
Also, if 1080p or 720p modes are not read in the monitor EDID, it defaults to a letterboxed 640x480 which is even worse.
Heck the 360 supports 4:3 displays appropriately, even if the game doesn't. At least if the game has a 4:3 mode it can use it, and isn't forced into letterbox.
You can change resolutions using the activity manager command.
'am display-size'
eg.
am display-size 1920x1080
am display-size 1080x720
am display-size 720x480
That only changes the virtual size, not the actual displayed resolutions. So far nothing works to actually display at 1280x720 on ouya, whereas some android stick I have lets you just choose that resolution and works fine at the same monitor. With the ouya I'm stuck to 640x480, so I can't use with the screen I intended and have to buy a new screen now :/
GizmoTheGreen said:
1. echo 0 > /sys/class/graphics/fb0/device/enable
2. echo (videomodefrommodesfile) > /sys/class/graphics/fb0/mode
3 echo 1 > /sys/class/graphics/fb0/device/enable
Click to expand...
Click to collapse
That works to some extent for me, through my VGA adapter.
For example, if I echo D:1280x1024p-74 > /sys/class/graphics/fb0/mode
then I'll get a 1280x1024 screen on my 4:3 LCD, but with only a 16:9 play area.
Using am display-size 1280x1024 will crop it down to a 4:3 720p instead of filling out the rest of the screen.
At this point I'm not sure if I'm running into limitations on the ouya, or fighting the VGA adapter. Eventually this all does have to go through the VGA adapter as the display I'll be using has no DVI or HDMI input.
E: While connected directly to my LCD via HDMI->DVI, it's actually quite curious, if I set the resolution to 1024x768, and confirm on the monitor that it is receiving that res, I have a letterboxed 640x480 play area in the corner.
When I am display-size 1024x768, the play area SHRINKS further. I think this does not quite what we expect.
muriani said:
E: While connected directly to my LCD via HDMI->DVI, it's actually quite curious, if I set the resolution to 1024x768, and confirm on the monitor that it is receiving that res, I have a letterboxed 640x480 play area in the corner.
When I am display-size 1024x768, the play area SHRINKS further. I think this does not quite what we expect.
Click to expand...
Click to collapse
Same thing happens to me with HDMI-DVI into a widescreen monitor. Curious part is that none of the widescreen resolutions actually show up in the modes file. On the off chance, I tried echo D:1280x720p-60 > /sys/class/graphics/fb0/modes, but it didn't work.
TopherBarnett said:
Same thing happens to me with HDMI-DVI into a widescreen monitor. Curious part is that none of the widescreen resolutions actually show up in the modes file. On the off chance, I tried echo D:1280x720p-60 > /sys/class/graphics/fb0/modes, but it didn't work.
Click to expand...
Click to collapse
You have to use one of the modes listed in /sys/class/graphics/fb0/modes.
Also, echo it to /sys/class/graphics/fb0/mode, not modes.
Before you do, echo 0 > /sys/class/graphics/fb0/device/enable, echo your mode, and then echo 1 > /sys/class/graphics/fb0/device/enable
If your screen is still blank, try hitting a button on the controller.
muriani said:
You have to use one of the modes listed in /sys/class/graphics/fb0/modes.
Also, echo it to /sys/class/graphics/fb0/mode, not modes.
Before you do, echo 0 > /sys/class/graphics/fb0/device/enable, echo your mode, and then echo 1 > /sys/class/graphics/fb0/device/enable
If your screen is still blank, try hitting a button on the controller.
Click to expand...
Click to collapse
Sorry, should have been more clear. I did all that, I was just trying to see if I could add an extra resolution into the 'modes' with "echo D:1280x720p-60 > /sys/class/graphics/fb0/modes", then activate it in the 'mode' with "echo D:1280x720p-60 > /sys/class/graphics/fb0/mode". No luck.
Ah, no.
I may be way off, but from what I can tell the entries in modes are more like aliases to the stored monitor EDID settings.
Oddly enough, the -60 modes almost never worked for me. I tended to use -74 modes if they were available and those worked better.
Out of curiosity, what are the contents of your modes file?
muriani said:
Ah, no.
I may be way off, but from what I can tell the entries in modes are more like aliases to the stored monitor EDID settings.
Oddly enough, the -60 modes almost never worked for me. I tended to use -74 modes if they were available and those worked better.
Out of curiosity, what are the contents of your modes file?
Click to expand...
Click to collapse
D:640x480p-60
D:640x480p-74
D:800x600p-59
D:800x600p-74
D:1024x768p-60
D:1024x768p-74
D:1280x1024p-74
D:1280x1024p-59
D:1152x864p-74
...huh. And this is a widescreen monitor? Those are all 4:3/5:4 aspects.
Try D:1280x1024p-74 if you don't mind, and let me know what happens.
That's worked best for me, but with a 4:3 monitor. Not sure how it'll act on yours.
The only other option I can think of is one from the other thread - the HDMI switch with the EDID spoofer.
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.
Is there any way to resize the screen very annoying that most apps stretch out of the screen..Not real Impressed with Google TV.Lacking a ton of features.Lack of Apps is total Garbage..
It sounds like you are asking if there are any options to compensate for the overscan your TV is applying.
You should have an option on your display to ensure the image is 1:1.
I will have to check..I noticed a lot of apps everything is stretched out past the screen very annoying..
your tv is doing that.
Had the same issues. LG TV by chance?
Go in and change the HDMI profile for your Shield on the TV. I had mine set for 16x9, but there was an option called "variable" or "fit" or something like that. Once I changed to that? Shield TV displays perfectly.
It's called overscan. This should allow you to fix the overscan issues of your TV, and the DPI issues to show more.
http://forum.xda-developers.com/android/apps-games/app-screen-shift-change-screen-t3138718
While we are talking about display issues does anyone know how to change the Shield TV to 3440*1440. I have a 34" LG 21:9 monitor wall mounted in my office but it will only output 1080p on it.
Pilz said:
While we are talking about display issues does anyone know how to change the Shield TV to 3440*1440. I have a 34" LG 21:9 monitor wall mounted in my office but it will only output 1080p on it.
Click to expand...
Click to collapse
http://www.addictivetips.com/android/resolution-changer-for-android/
Android doesn't support 21:9, but that should get you a few more options.
kdb424 said:
http://www.addictivetips.com/android/resolution-changer-for-android/
Android doesn't support 21:9, but that should get you a few more options.
Click to expand...
Click to collapse
I though about that but I wasn't sure what dpi I should use plus my Shield TV won't flash SuperSU when I try in TWRP. Once I root it I'll give it a go
First you have to unlock the device with fastboot. It may erase all of your userdata when you do that. I suggest backing it up with TWRP before you unlock to an external SD or USB drive. I personally run anywhere between 160 and 200 depending on the application and screen size. I use an xposed module for per app dpi, though my global is 180 right now (the build.prop edit method). You can expariment with them depending on your screen. It's all up to you what you want.
I mean you are asking how you can resize your screen .plz clear your demand.
mohinipollob said:
I mean you are asking how you can resize your screen .plz clear your demand.
Click to expand...
Click to collapse
If you mean to make things display larger or smaller, like bigger or smaller text and icons, that's DPI settings.
If you mean things are shown off the screen, that's called overscan. Both were discussed here.
kdb424 said:
http://www.addictivetips.com/android/resolution-changer-for-android/
Android doesn't support 21:9, but that should get you a few more options.
Click to expand...
Click to collapse
How do we install that from Play since Play only shows Android TV apps?
For the sake of completeness (most of you will have noticed this app already): For a change, Samsung have done a fantastic job and released a great app called "Game Tuner". It's simple to use, doesn't even need root, and renders all of the stuff I wrote below obsolete!
What it does is, it renders each game at an individual screen resolution, frame rate, and texture quality (texture quality only working for me since MM upgrade).
All you have to do is install Game Tuner from Google Play (above link), start it, follow the instructions to install GameMode through Galaxy Apps, and you're good to go. Create a custom profile, set default values (e.g. 75% resolution=1080p), activate the profile. Set different resolutions for other games. And if you want to control apps other than games, tap top left menu, and chose "Apps".
I've done the same benchmarks as with the method below, and the results were exactly the same, so it's really working, but without messing up the UI or impairing system apps like the camera.
Hey folks,
I've decided to put together a little wrap-up of the stuff I found regarding the sometimes rather poor 3D performance of the Note 4. This is only for experienced users who are familiar with things as rooting, backups, adb, in general: unbricking their phone if bad things happen. As usual, I don't take any responsibilty if you brick your phone or destroy it in any other way. Just make sure to activate USB debugging, and if anything goes wrong, either follow this guide, or simply reflash your ROM.
Just make sure you make a Nandroid or at least Titanium backup before you try this. Better safe than sorry...
It comes as no surprise that running a cpu at almost 3GHz takes its toll. Demanding games such as Real Racing 3 or XCOM:EW, or emulators such as PPSSPP cause the cpu to heat up rapidly, until it reaches ~80°C, before it gets mercilessly downclocked to cool down. At this point, you start noticing more or less pronounced performance drops. There isn't really much you can do, except using a custom kernel to downclock cpu & gpu, before your phone does.
But apart from that, there is another, even greater performance hog, which is also one of the main reasons for the overheating issue: the QHD resolution of our Note 4's screen. We're talking about a 3.69 megapixel resolution, that's almost twice as much as Full HD (2.07 MP), and exactly four times as much as HD (0.92 MP). Gorgeous and brilliant, beautiful to look at during everyday use, but pushing the Adreno gpu to its limits when it comes to gaming.
So, an ingenious guy called NOMone has created a nifty little tool called "NOMone Resolution Changer", already some time ago. It's available for free at Google Play. It's been widely discussed here on xda and on other forums, but I want to share my experience specifically on the Note 4.
Btw, it seems he only posted here two times, so he's most likely not active anymore, but you should head over and thank him anyway.
Now, if you're thinking "no way, why should I deliberately sacrifice my QHD resolution?", read on nonetheless. Because this tool is extremely easy to use, and if you only switch the resolution before playing a game, and revert afterwards (it's only one click), you won't have to sacrifice any visual quality. The settings stick after a reboot, so make sure to really restore defaults if you want to go back to QHD.
The trick is to use the appropriate resolution and dpi values, so your screen doesn't get mixed up.
The results are impressive, sometimes even staggering. Has anyone ever wondered why PPSSPP doesn't perform better on a Note 4 than it does on a Note 2? Here's the reason. PPSSPP gains so much performance , it's almost unbelievable.
I've also done some benchmark runs to measure the improvements (yeah, I know, benchmarks are bad, but still :angel: ). The improvement is clearly visible and, even more important, reproducable:
GFXBench GL Benchmark 3.1 (Manhattan):
1. 1440p: 449,4 frames, 7.2 fps
2. 1080p: 800,6 frames, 13 fps (+78%)
3. 720p: 1621 frames, 26 fps (+261%)
4. 480p: 2728 frames, 44 fps (+507%)
This is plain awesome. The Note 4 is listed even lower, with 434 frames, in the device list, while the 1080p Galaxy S5 reaches 775 frames.
AnTuTu (gpu score only):
1. 1440p: 16210
2. 1080p: 21253 (+31%)
3. 720p: 22524 (+40%)
4. 480p: 22523 (+40%)
Obviously, by comparing scores 3 and 4, the Note 4 hits the fps limit at HD resolution, so there's no more room for improvement in AnTuTu.
Seascape Benchmark (detail setting: Very High):
1440p: 26.9 fps
1080p: 46.6 fps (+73%)
720p: 53.4 fps (+99%, sometimes hits the frame limit of 59.0 fps)
480p: 59.0 fps (+119%, hits the frame limit constantly).
This is a beautiful OpenGL ES 2.0 test, so no cpu scores interfering with the result. Again the fps limit prevents a higher score, but nonetheless, this is pretty amazing.
Other benefits: if you're using a custom kernel, you can run gpu-intensive games at lower cpu speeds to keep the cpu temperature in check. In my case, XCOM:EW runs smoothly @ 30% (!!) cpu speed. This way, the cpu doesn't heat up to more than 60°C, which means it doesn't get downclocked while playing. If you like, you can also automate the process of setting the cpu speed with the aptly named app "Automate" . Which is fantastic, btw.
Now what about visual quality?
Seriously: it's hard to tell the difference. If you look very closely, you can see the display isn't as sharp in FHD as in QHD. But if you look that closely, you're in constant danger of triggering some random app with the tip of your nose. At normal viewing distance, especially while gaming, it's impossible to tell the difference.
So, are there any drawbacks?
Yes, there are: the UI gets messed up a bit (e.g. bigger status bar, some Samsung apps don't fit on screen anymore), and NOMone Resolution Changer doesn't seem to work with CM12.1. Well, at least for me, and other users reported so as well. I tested it some time ago, while I was on CM12.1, and even thought it was a fake app, which it isn't! Seems that the resolution is somehow hard coded into CM12, and you can only switch dpi. There's probably nothing you can do when you're running CM, except try your luck.
But if you are running a Touchwiz ROM, stock or custom, it should work as intended (Emotion Revolution ROM r10.1 in my case). And you can simply ignore the UI issues, as long as you only switch the resolution for gaming. It's not a real issue then, because the status bar is hidden anyway while the game is running.
If you want to keep your device running at FullHD permanently, it's a bit more complicated: first, you'll need Xposed, so you can use the App Settings module to set Android System and SystemUI to 480 dpi. This'll fix the UI (Not needed. Just reboot)
Some apps like phone, contacts, S-Note scale down to the lower dpi setting, whereas Samsung keyboard and the camera won't (camera works, see post #10 below).
So you'll have to install another keyboard like SwiftKey (if you don't have it already), find a working camera app (3rd party or hacked Note 4 camera), and clear your Google Play data (at least I had to, it wouldn't install any apps after the changes), and you're good to go. There might also be other issues I'm not aware of yet. But apart from the ones I described, everything's working fine so far.
Have fun!
you don't need root to change the dpi and the resolution.
enable usb debugging and adb the following:
adb shell wm density 480
adb shell wm size 1080x1920
adb reboot
if you want to revert back:
adb shell wm size reset
adb shell wm density reset
adb reboot
the changes persist after reboot.
I am using it like that for some time. Everything is much faster. Even the browsing..
the only 2 bugs I noticed is the Samsung keyboard (i switched to swiftkey) and the action memo (c'mon Samsung devs, code properly..)
mitko76 said:
you don't need root to change the dpi and the resolution.
enable usb debugging and adb the following:
adb shell wm density 480
adb shell wm size 1080x1920
adb reboot
if you want to revert back:
adb shell wm size reset
adb shell wm density reset
adb reboot
the changes persist after reboot.
I am using it like that for some time. Everything is much faster. Even the browsing..
the only 2 bugs I noticed is the Samsung keyboard (i switched to swiftkey) and the action memo (c'mon Samsung devs, code properly..)
Click to expand...
Click to collapse
You're right, you don't necessarily need this tool. All it does is simplify the process. And you should really be able to use adb commands to fix your phone when you mess it up. But NOMone's tool comes in very handy when you're away from your pc and need to switch resolutions quickly. In my case, it's when I want to use the camera: the UI is messed up at 1080p and I haven't found a way to fix it yet, except switch back to QHD. Or the other way round: if you want to play a demanding game on the train at lower resolution, but go back to QHD again.
I'm using 1080p resolution permanently now, because I get a smoother UI, a cooler phone, better battery life, and much better performance. I hope they don't give us 5" UHD screens next...
Could you please explain what is wrong with the camera on 1080p 480dpi? I am using these settings and have 0 problems with the camera. Just curious.. If possible please attach a screen shot. Cheers
The UI is messed. I can't see most of the buttons, and can't take a photo, see attached screenshot.
Xelasarg said:
The UI is messed. I can't see most of the buttons, and can't take a photo, see attached screenshot.
Click to expand...
Click to collapse
Using my method and my values, it is absolutely fine for me. Do you restart after changing the resolution and the dpi?
I am on UK BTU 5.1.1
mitko76 said:
Using my method and my values, it is absolutely fine for me. Do you restart after changing the resolution and the dpi?
I am on UK BTU 5.1.1
Click to expand...
Click to collapse
I even wiped /cache and /dalvik. Strange. My device is a Snapdragon N910F. Is yours an Exynos N910C perhaps? If not, would you mind sending me your camera apk for testing?
Thanks!
Xelasarg said:
I even wiped /cache and /dalvik. Strange. My device is a Snapdragon N910F. Is yours an Exynos N910C perhaps? If not, would you mind sending me your camera apk for testing?
Thanks!
Click to expand...
Click to collapse
very strange indeed. My device is n910f as well. Not rooted and fully stock. I used the Debloater app to disable all unused apps (works via adb) and the method descried in my other post to change the resolution and dpi. The camera is working absolutely fine i.e. no visual changes or glitches. As I am not rooted I am not sure if I can give you the camera apk. It is basically the same apk as in the stock 5.1.1 BTU rom. Try my method on the stock rom with my values and I am sure it will work.
Cool
mitko76 said:
very strange indeed. My device is n910f as well. Not rooted and fully stock. I used the Debloater app to disable all unused apps (works via adb) and the method descried in my other post to change the resolution and dpi. The camera is working absolutely fine i.e. no visual changes or glitches. As I am not rooted I am not sure if I can give you the camera apk. It is basically the same apk as in the stock 5.1.1 BTU rom. Try my method on the stock rom with my values and I am sure it will work.
Click to expand...
Click to collapse
Well, I went ahead and downloaded _alexndr's COI3 stock debloated rom base (Deodexed), extracted SamsungCamera3.apk, replaced the one in my /system/app dir, set permissions, rebooted, and everything's working fine now. :good:
No idea what the Emotroid guys did to the camera app.
I've attached the apk to this post in case anyone else is having this issue.
Man, I've been playing XCOM:EW at 720p, and my phone didn't get warmer than 59°C, even after 2+ hours. And the performance boost is just so incredible... Turns out I don't even mind the 720p resolution in 3D games, it didn't bother me at all.
Just a warning:
I just managed to render my phone useless with this. After changing resolution and DPI, the phone did a soft reboot (as it should), startet booting, then, after the initialisation of systemUI reboots. Has been Bootlooping the past hour. ADB doesn't work, as reboot it's unauthorised and boot loop doesn't allow for any authorisation. Tried resetting via build.prop and userinit.sh. Even Direct Script Injection into init.rc didn't work.
Cache wipe -> no chance
System wipe and reflash -> Nope
In the End i ended up factory resetting and reflashing complete rom. This did work. Not to rant or anything, just a little story for those that are not capable to troubleshoot problems: This might screw your Installation!
domsch1988 said:
Just a warning:
I just managed to render my phone useless with this. After changing resolution and DPI, the phone did a soft reboot (as it should), startet booting, then, after the initialisation of systemUI reboots. Has been Bootlooping the past hour. ADB doesn't work, as reboot it's unauthorised and boot loop doesn't allow for any authorisation. Tried resetting via build.prop and userinit.sh. Even Direct Script Injection into init.rc didn't work.
Cache wipe -> no chance
System wipe and reflash -> Nope
In the End i ended up factory resetting and reflashing complete rom. This did work. Not to rant or anything, just a little story for those that are not capable to troubleshoot problems: This might screw your Installation!
Click to expand...
Click to collapse
Hence the warning at the beginning of the thread.
But seriously: which method did you use? The NOMone app or the adb commands? Because only the adb command needs a reboot to take effect, NOMone does not reboot: it changes the resolution on the fly, then waits 10 seconds for confirmation and switches back to default resolution otherwise.
It's impossible to tell what went wrong in your case, might have been anything from a bad adb command to a malfunction of the app or your rom. I guess if you enter bad values, both methods might break your SystemUI. I managed to do so by using Automate to activate the shell commands on app launch (no bootloop, though, only permanent FC of SystemUI), but I was able to fix it with adb easily.
It's a shame it didn't work for you, most people who are using this method are very happy with it.
THANKS !
dooes this improve battery as well /
gonna try this
Boody hegan said:
THANKS !
dooes this improve battery as well
Click to expand...
Click to collapse
Yes, it does, at least a bit. The screen does still burn a lot of juice because it's so big and bright, but the cpu stays much cooler. Less heat=less power consumption.
Thanks alot , i'm on simplrom v5c and googy max kernel v2
can this still work ..
Xelasarg said:
Hence the warning at the beginning of the thread.
But seriously: which method did you use? The NOMone app or the adb commands? Because only the adb command needs a reboot to take effect, NOMone does not reboot: it changes the resolution on the fly, then waits 10 seconds for confirmation and switches back to default resolution otherwise.
It's impossible to tell what went wrong in your case, might have been anything from a bad adb command to a malfunction of the app or your rom. I guess if you enter bad values, both methods might break your SystemUI. I managed to do so by using Automate to activate the shell commands on app launch (no bootloop, though, only permanent FC of SystemUI), but I was able to fix it with adb easily.
It's a shame it didn't work for you, most people who are using this method are very happy with it.
Click to expand...
Click to collapse
It was completely my fault. I knew what i was getting into, so no problem. It's just that, the "mistakes" i did could easily be done by accident by some less experienced users.
First off, i'm on CM12. NOMones Sollution doesn't seem to work there. CM does a "Hot Reboot" to reload the system UI. No matter what you set in NOMones app, the resolution doesn't change. DPI does though. This seems to be a CM related issue. Maybe they hardcode the resolution at build time...
After that i tried another app, which had the Orientation labeled backwards. So it set 1920x1080 landscape instead of portrait. After that the Phone Bootlooped the System UI. It would always boot up to the PIN Enter Screen and then reboot.
As said, no big Problem. I knew what to do and was able to bring my phone back to working state. Just make sure that you are 100% sure about the numbers you put into such apps and keep in mind that even with such "small" changes you should always have a up to date Backup of everything.
Boody hegan said:
Thanks alot , i'm on simplrom v5c and googy max kernel v2
can this still work ..
Click to expand...
Click to collapse
It should, unless SimplROM is CM12-based. NOMone Resolution Changer, as well as similar apps and the adb method, aren't limited to specific devices. In theory, they may all work on all Android phones. You'll have to try it out yourself, just make a backup before you do so!
domsch1988 said:
It was completely my fault. I knew what i was getting into, so no problem. It's just that, the "mistakes" i did could easily be done by accident by some less experienced users.
First off, i'm on CM12. NOMones Sollution doesn't seem to work there. CM does a "Hot Reboot" to reload the system UI. No matter what you set in NOMones app, the resolution doesn't change. DPI does though. This seems to be a CM related issue. Maybe they hardcode the resolution at build time...
After that i tried another app, which had the Orientation labeled backwards. So it set 1920x1080 landscape instead of portrait. After that the Phone Bootlooped the System UI. It would always boot up to the PIN Enter Screen and then reboot.
As said, no big Problem. I knew what to do and was able to bring my phone back to working state. Just make sure that you are 100% sure about the numbers you put into such apps and keep in mind that even with such "small" changes you should always have a up to date Backup of everything.
Click to expand...
Click to collapse
Right, thanks for clarification. I don't remember the hot reboot in CM12, but I know the resolution switch didn't work when I tried it on my Note 2 some time ago. Funny that for once Touchwiz is more customizable than CM.
If you're still interested, but hate the Samsung colour scheme (like me), you can try out Emotion Revolution ROM r10.1. It's based on the latest COI3 TW firmware, but they themed the notifcation/status bar and toggles to somewhat more like stock Android, see attached screenshot. Looks pretty sleek, performance is easily on par with CM12, and the Emotion kernel has tons of great tweaking options. Or you can go for their Port Note 5 r2.1 ROM, also based on COI3, which should offer full Theme Store support. That's the one I'll flash next. :good:
Xelasarg said:
Right, thanks for clarification. I don't remember the hot reboot in CM12, but I know the resolution switch didn't work when I tried it on my Note 2 some time ago. Funny that for once Touchwiz is more customizable than CM.
If you're still interested, but hate the Samsung colour scheme (like me), you can try out Emotion Revolution ROM r10.1. It's based on the latest COI3 TW firmware, but they themed the notifcation/status bar and toggles to somewhat more like stock Android, see attached screenshot. Looks pretty sleek, performance is easily on par with CM12, and the Emotion kernel has tons of great tweaking options. Or you can go for their Port Note 5 r2.1 ROM, also based on COI3, which should offer full Theme Store support. That's the one I'll flash next. :good:
Click to expand...
Click to collapse
Nah, TW is no option... I choose CM because of the straight forward no bllsht Apps approach. Plus Nightly builds via OTA... In no possible way am i going back to TW
AnTuTu Benchmark @ 1080p, performance governor, stock cpu frequency (2.65 GHz): :highfive:
(OK, cpu was also very cool when benchmark started, 28°C).