Database Users

how to select 1080p resolution in xbmc, android stick mx2 imito?

is this possible? in my android version of xbmc the video output shows as 1280p x760 i think and i can't change it. the setting in my main android settings page is set to 1080p 60
how can i make sure i am getting these settings?

wakkaday said:
is this possible? in my android version of xbmc the video output shows as 1280p x760 i think and i can't change it. the setting in my main android settings page is set to 1080p 60
how can i make sure i am getting these settings?
Click to expand...
Click to collapse
what ROM are you using ?

On Finless ROM 1.5 you can choose to install either a 720p or 1080p kernel and boot screen, but I think once you choose you're stuck with it unless you reinstall. I originally tried 1080p, but things on screen were too small for my liking (even on my 73" DLP). So I reinstalled and selected 720p. Very happy with this setup even though it's only 720p.
Perhaps other ROMs will let you change this on the fly, but I couldn't find an easy way on Finless 1.5.

rickwood said:
On Finless ROM 1.5 you can choose to install either a 720p or 1080p kernel and boot screen, but I think once you choose you're stuck with it unless you reinstall. I originally tried 1080p, but things on screen were too small for my liking (even on my 73" DLP). So I reinstalled and selected 720p. Very happy with this setup even though it's only 720p.
Perhaps other ROMs will let you change this on the fly, but I couldn't find an easy way on Finless 1.5.
Click to expand...
Click to collapse
yes once you choose you are stuck with it. I think 1.7 is out btw.

Bagbug said:
yes once you choose you are stuck with it. I think 1.7 is out btw.
Click to expand...
Click to collapse
managed to do it
is it worth installing finless 1.7?

I haven't tried it yet - - thought I'd wait and see what people think first. I have read some comments that auto-hiding the bottom bar doesn't work for XBMC, and the button to do it manually was removed in 1.7. This would be kind of a deal breaker for me, so I think I'll wait until that gets resolved before I upgrade.

1080p isn't worth it because the RK3066 can't handle it. I've tried it and the performance difference between 720p and 1080p is crazy. And just to note, I'm talking about 1080p device resolution (if you check device info using various apps, it'll show something like 1920 x 1032 (48 pixels for the status bar) as opposed to 1280 x 688 or something.
Some kernels "output" 1080p but are still 720p in terms of device resolution. I think this is pointless as it is just upscaling the signal. Like some have said, it is also too small to see anything from the couch.

I installed finless 1.5 1080p and yes the icons are too small but it was an easy task to adjust the icon size following the instructions in the PDF for rom install. Its just a matter of moving a # symbol in a text file. Once done all the text and icons are per normal. Very happy with results.

davphi338 said:
I installed finless 1.5 1080p and yes the icons are too small but it was an easy task to adjust the icon size following the instructions in the PDF for rom install. Its just a matter of moving a # symbol in a text file. Once done all the text and icons are per normal. Very happy with results.
Click to expand...
Click to collapse
i havent tried any 1080p files, thats a shame as the item is being sold as 1080p

Changing HDMI Resolution

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.

Remove Black Bars on HDMI Output

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.

Lower Resolution issues with Daydream VR

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!

4K option or forced 1080p?

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?