Is anybody working, or is there anything that can be done to enable hardware rendering of h264 videos. As discovered the first week, you have to reencode all of your movies and shows as h264 baseline which is a royal pain in the @ss. Is there anything that can be done, dev-wise?
Haven't really encoded anything in H.264 yet, but according to the motorola support forums it supports:
Listed below is the H.264 profiles supported
Baseline Profile up to 1080P, 20Mbps
Main Profile :
Progressive, CAVLC, no WP up to 1080P, 20Mbps
Progressive, CABAC, no WP up to 720P, 4-6Mbps
Progressive, CABAC, WP up to 480P, 2Mbps
Progressive, CAVLC, WP up to 480P, 2Mbps
Interlaced, CABAC,no WP up to D1, 3 mbps
High Profile
Progressive, CABAC, no WP up to 720P, 2 Mbps
Progressive, CAVLC, no WP up to 720P, 2 Mbps
Progressive, CABAC, WP up to 480P, 2Mbps
Progressive, CAVLC, WP up to 480P, 2Mbps
Whether this is true or not, I have no idea. I haven't tested any of this.
Here is the thread on the moto forums.
Hypothetically speaking, what would a normal encode look like of a tv show downloaded off the net? I know it's profile is high, but I don't understand the rest of the acronyms. I just know they won't play without a reencode. I'm not condoning or suggesting I've done that, i'm just wondering.
scottrleo1 said:
Hypothetically speaking, what would a normal encode look like of a tv show downloaded off the net? I know it's profile is high, but I don't understand the rest of the acronyms. I just know they won't play without a reencode. I'm not condoning or suggesting I've done that, i'm just wondering.
Click to expand...
Click to collapse
Define "normal"
The quality of the picture and sound on a video you download is completely dependent on who encoded it in the first place. Having said that, if you re-encode it to make it work on your device the settings that you use can make it look/sound the same or horribly worse. Download something, transcode it using your favorite suite and find a setting that works for you.
Looks like they've more or less sorted this one out, so this conversation can move over here:
http://forum.xda-developers.com/showthread.php?t=963569
Related
Ok, so we have been told the Atrix and ALL Tegra 2 devices cannot playback High Profile MKV. Most people believe it.
It's not true whatsoever. Single core 800mhz CPU's can do it, this one can too. We are looking at codec's or drivers here. I know it's almost entirely GPU related, so CPU speed doesn't matter much. I am SURE the Atrix can play 720p MKV decoded using the CPU.
My 1.6ghz Atom can do that. For the most part. Cortex A9 smashes Atom N450 though, shouldnt be an issue. From what I've seen we cannot even access our other core yet, I have seen NO apps that benefit from it yet. Looks like its time. If this can be fixed, Tegra 2 will be much better off. At this point, I am not proud of my phone anymore, inferior, older phones can play videos my Atrix cannot. Umm, wat?
We need to fix this now, it's pathetic. Can anyone shed some light on this?
*edit*
Nvidia is such trash for doing this. Last Nvidia product I buy. After the GTX 400 series GPU's and then this, lost ALL faith in them.
i agree, its pathetic...
to be fair, on a small screen baseline profile is perfectly fine in terms of quality, but its more the convenience of being able to drag and drop a x264 rip without having to encode.
I'm new to the Thunderbolt, and trying to decide if I am going to stay with it or try something else (like Inc2 or DX2). I took some sample videos, and the framerates are reported at a paltry
6fps at 8000 kbps encoding for 720p, and
11fps at 3000kbps encoding for 800x480.
The audio bitrate is at 64kbps for both
This is with a stock unrooted phone on Froyo (2.2.1)
Can I increase these sampling and encoding rates by rooting, upgrading to GB, overclocking, etc?? I just have no idea if this is a hardware limitation (not having a separate GPU) or a software limitation. What kind of rates is everyone else getting?? Thanks
Epicardium said:
I'm new to the Thunderbolt, and trying to decide if I am going to stay with it or try something else (like Inc2 or DX2). I took some sample videos, and the framerates are reported at a paltry
6fps at 8000 kbps encoding for 720p, and
11fps at 3000kbps encoding for 800x480.
The audio bitrate is at 64kbps for both
This is with a stock unrooted phone on Froyo (2.2.1)
Can I increase these sampling and encoding rates by rooting, upgrading to GB, overclocking, etc?? I just have no idea if this is a hardware limitation (not having a separate GPU) or a software limitation. What kind of rates is everyone else getting?? Thanks
Click to expand...
Click to collapse
I've never had frame rates that low. 6fps is something that's GLARINGLY obvious. The Snapdragon does have it's own GPU, the Adreno 205. I can't speak to stock because I've never really used a stock Tbolt, but the custom ROMs have got to be pushing more frames than that because I've pulled some fairly crisp stills from the frames before.
why cant our dual core 1.5ghz phones even play 1080 flash videos smoothly
hyphydragon said:
why cant our dual core 1.5ghz phones even play 1080 flash videos smoothly
Click to expand...
Click to collapse
Technically, Gingerbread does not fully support dual core processors...
hyphydragon said:
why cant our dual core 1.5ghz phones even play 1080 flash videos smoothly
Click to expand...
Click to collapse
you mean youtube 1080p or something like that??? good question, guessing our phones don't have the decoders to do that and do not take full advantage of the gpu and cpu. But in any case our screens are not 1080p its not even 720p, it's qhd meaning 1/4 of actual 1080p. so there would be no point anyways..
---------- Post added at 10:39 PM ---------- Previous post was at 10:35 PM ----------
hasoon2000 said:
Technically, Gingerbread does not fully support dual core processors...
Click to expand...
Click to collapse
hmm, I didn't know that, so technically we have a phone that's not using its full potential at the moment, its kinda like when all these dual core computers came out with windows xp, when it wasn't even supported...The players also have to support hardware encoding and there's a lot of other factors..
seansk said:
you mean youtube 1080p or something like that??? good question, guessing our phones don't have the decoders to do that and do not take full advantage of the gpu and cpu. But in any case our screens are not 1080p its not even 720p, it's qhd meaning 1/4 of actual 1080p. so there would be no point anyways..
---------- Post added at 10:39 PM ---------- Previous post was at 10:35 PM ----------
hmm, I didn't know that, so technically we have a phone that's not using its full potential at the moment, its kinda like when all these dual core computers came out with windows xp, when it wasn't even supported...The players also have to support hardware encoding and there's a lot of other factors..
Click to expand...
Click to collapse
Pretty much. lol. You can see that multi-core support was added to Honeycomb.
http://en.wikipedia.org/wiki/Android_version_history
hasoon2000 said:
Pretty much. lol. You can see that multi-core support was added to Honeycomb.
http://en.wikipedia.org/wiki/Android_version_history
Click to expand...
Click to collapse
Hah whats funny is that I have a galaxy tab 10.1 and my phone runs videos that the tab can't and a better smoother performance too...lol...it has a lot to do with the player and the decoders as well and how they use the system. samsung is the master of that, they include a lot of good support for video and audio play on their phones...but unfortunately I refuse to upgrade to touchwiz on my tab and rather stay stock honeycomb and just convert videos on my desktop and watch them later on my tab.
i had the sensation before the amaze and it played 1080 perfect with the exact same cpu/soc and less ram and lower clock 1.2ghz, and ill respectfully disagree that playing videos in 1080 doesnt make a difference as it clearly does
720p cant read small text on streams and in 1080 i can read it perfect just its going at 2 fps >,<
btw i had faux kernel on my sensation and i also have it in my amaze
hyphydragon said:
i had the sensation before the amaze and it played 1080 perfect with the exact same cpu/soc and less ram and lower clock 1.2ghz, and ill respectfully disagree that playing videos in 1080 doesnt make a difference as it clearly does
720p cant read small text on streams and in 1080 i can read it perfect just its going at 2 fps >,<
btw i had faux kernel on my sensation and i also have it in my amaze
Click to expand...
Click to collapse
I don't know, maybe its not true 1080p or true 720p, they might have been encoded with loss of quality to save space...ask others see what they think. If you think that's the case download this program it converts all files to other files...and convert the flash videos to mp4 1080p files
http://www.freemake.com/
seansk said:
I don't know, maybe its not true 1080p or true 720p, they might have been encoded with loss of quality to save space...ask others see what they think. If you think that's the case download this program it converts all files to other files...and convert the flash videos to mp4 1080p files
http://www.freemake.com/
Click to expand...
Click to collapse
thank you for being so helpful but the video i m referring to is on live streams like on twitch.tv justin.tv or own3d.tv
hyphydragon said:
thank you for being so helpful but the video i m referring to is on live streams like on twitch.tv justin.tv or own3d.tv
Click to expand...
Click to collapse
make sure to have adobe flashplayer installed
Felinos11 said:
make sure to have adobe flashplayer installed
Click to expand...
Click to collapse
also make sure you're getting decent reception wifi preferably, so the data can come in clearly and not choppy. what is it that you're trying to watch I'll try it on my phone and see if I have the same problem then try my gf sensation and see if I see a difference... unless its something inappropriate lol
I imagine ics has dual core support right? I mean, its built on honeycomb, hopefully well have hd on YouTube lol
Sent from my HTC Amaze 4G using xda premium
Hi! Happy new year! I've jus bought a brand new xperia neo on amazon and i'm waiting for being delivered soon (i'm in Venezuela). looking for more information about the smartphone i've seen that it has a 8.1mpx camera but only record at 720p, the question is ¿It's possible to enable 1080p recording with this camera? it has a very good hardware so i think it's very possible.
What do you know about it?
Thanks a lot!
douglasroos said:
Hi! Happy new year! I've jus bought a brand new xperia neo on amazon and i'm waiting for being delivered soon (i'm in Venezuela). looking for more information about the smartphone i've seen that it has a 8.1mpx camera but only record at 720p, the question is ¿It's possible to enable 1080p recording with this camera? it has a very good hardware so i think it's very possible.
What do you know about it?
Thanks a lot!
Click to expand...
Click to collapse
It is hardware limitated.... only 720p
silasje1 said:
It is hardware limitated.... only 720p
Click to expand...
Click to collapse
Don't think so:
The X10 also didn't have multi-touch and 720p recording when it was launched, but after an update it was capable of that.
But maybe the quality is better on 720p than on 1080p, less noise, better light conditions, more fps.
For x10
Yes, [email protected] ([email protected] with cont. autofocus via Android 2.1 Eclair update)
---
For HD video is required Single core 1GHz which x10 have.
But for FULL HD is required minimal 1.0 Dual core processor which x10 dont have, arc dont have and neo dont have.
Phone with 1.0ghz single core dosent have power enough to record that resolution or even playback it.
sdk16420 said:
Don't think so:
The X10 also didn't have multi-touch and 720p recording when it was launched, but after an update it was capable of that.
But maybe the quality is better on 720p than on 1080p, less noise, better light conditions, more fps.
Click to expand...
Click to collapse
My bad.... lets hope it can do 1080p... but i think it will be problematic with buffers
silasje1 said:
My bad.... lets hope it can do 1080p... but i think it will be problematic with buffers
Click to expand...
Click to collapse
Check Desire HD/s threads... It have same hardware. This MSM chips are not capable of 1080p recording or playback. Nothing will change that.
i can't see diference betwen 720p to 1080p on 3.7 screen
Ok now i Get it, thanks for the replys, maybe the developers in the future can do something about it. Dont loose the hopes!!
Kinhooow said:
i can't see diference betwen 720p to 1080p on 3.7 screen
Click to expand...
Click to collapse
yes but if you gonna see videos on LCD TV 42" you can note the difference between resolutions. That's why i'm asking in the first place.
It is possible to do. But i can only tell it is hard and takes alot of time. The Canon EOS 500D has also only 1080p (20fps) and it took a **** time before someone could make it 24 fps (still not usuable enough though) But im comparing DLSR with smartphone just my words
Its processor limitation not camera sensor limitation...
Sent from my MT15i using xda premium
Actually the 1.2GHz Hummingbird single-core processor is capable of FULL-HD recording and playing,so i think 1080p is not a problem even for a single-core.
Phone with 1.0ghz single core dosent have power enough to record that resolution or even playback it.[/QUOTE]
I can playback 1080p video without problems on my single core GTab!
testadeferro said:
Phone with 1.0ghz single core dosent have power enough to record that resolution or even playback it.
Click to expand...
Click to collapse
I can playback 1080p video without problems on my single core GTab![/QUOTE]
i tried 1080p on my neo and it was choppy....
---------- Post added at 10:33 PM ---------- Previous post was at 10:32 PM ----------
insitex said:
Actually the 1.2GHz Hummingbird single-core processor is capable of FULL-HD recording and playing,so i think 1080p is not a problem even for a single-core.
Click to expand...
Click to collapse
where is your source on that ?! thanks
So what about over clocking the cpu to around 1.4-1.6 Ghz ? with custom kernels we even can go for around 2Ghz mark.
cpu msm8255 not support Full HD 1080p recoder. Sorry for my english
Specifications
CPU Single-core Scorpion CPU up to 1.4GHz
GPU AdrenoTM 205 Graphics with dedicated 2D/3D engines and support for Flash 10 and WebGL
Modem Options include 1x, DO, HSPA+
Memory 2x 333MHz LPDDR2
Video HD 720p video playback and streaming at 30fps
Camera 12-megapixel
Camcorder Up to 720p (MPEG-4) record and playback at 30fps
LCD Support Up to WXGA (1280x720)
Audio Up to 128-voice polyphony, surround sound, enhanced echo and noise cancellation
USB USB 2.0 High Speed Peripheral or Host
Security and DRM Secure MSM v4 with TrustZone
Wi-Fi/BT/FM Support for Wi-Fi, Bluetooth and FM connectivity2
After reading this tread i actually searched the market and found Lgcamera (free)
After installing it i changed to cam mode and selected 1080p and tried to record...
And actually it starterd ---RECORDING 1080p--- After that i tried it again but it wasnt able to record a video, even after setting it to 720p it still wasnt able to record.
So i installed it again and it worked again. So i looks like neo can record
1920x1080p - h.264 - mp4 - up to 30 bitrate and max of 30 fps
--> Looks like cleraring cache & data of Lgcamera fixes the "cannot record video bug" so u dont have to install it every time again.
To record properly i OC to 1800 Ondemand with 40 cpu treshhold, using lower settings resolved for me not to be able to record video in 1080 (even after reinstalling)
I see quite a improvement on a bigger screen.
Pät said:
After reading this tread i actually searched the market and found Lgcamera (free)
After installing it i changed to cam mode and selected 1080p and tried to record...
And actually it starterd ---RECORDING 1080p--- After that i tried it again but it wasnt able to record a video, even after setting it to 720p it still wasnt able to record.
So i installed it again and it worked again. So i looks like neo can record
1920x1080p - h.264 - mp4 - up to 30 bitrate and max of 30 fps
--> Looks like cleraring cache & data of Lgcamera fixes the "cannot record video bug" so u dont have to install it every time again.
To record properly i OC to 1800 Ondemand with 40 cpu treshhold, using lower settings resolved for me not to be able to record video in 1080 (even after reinstalling)
I see quite a improvement on a bigger screen.
Click to expand...
Click to collapse
can you post that 1080p video on youtube or something i highly doubt that this is right....
skyboyextreme said:
can you post that 1080p video on youtube or something i highly doubt that this is right....
Click to expand...
Click to collapse
Yes, you were right i uploaded it and youtube doesnt even reckognize 720p on the 1080p so its just a bug
Here if u wanna see.
http://www.youtube.com/watch?v=xryZFicOR8Y&feature=youtu.be 1080p and 720p is in my account (just made a youtube acc for that ;D)
Still its a good app since we can choose focus mode and chance bitrates
Pät said:
Yes, you were right i uploaded it and youtube doesnt even reckognize 720p on the 1080p so its just a bug
Here if u wanna see.
http://www.youtube.com/watch?v=xryZFicOR8Y&feature=youtu.be 1080p and 720p is in my account (just made a youtube acc for that ;D)
Still its a good app since we can choose focus mode and chance bitrates
Click to expand...
Click to collapse
m&m mmm schmeckt gut !
Last summer, I decided to buy a Nexus 7 for using it mainly as an ebook reader. It's perfect for that with its very sharp 1280x800 screen. It was my first Android device and I love this little tablet.
I'm a fan of retro gaming and I installed emulators on every device I have: Pocket PC, Xbox, PSP Go, iPhone, iPad3, PS3. So I discovered that the Android platform was one of the most active community for emulation fans like me and I bought many of them, and all those made by Robert Broglia (.EMU series). They were running great on the N7 but I found that 16GB was too small, as was the screen.
I waited and waited until the 32 GB Nexus 10 became available here in Canada and bought it soon after (10 days ago). With its A15 cores, I was expecting the N10 to be a great device for emulation but I am now a little disapointed. When buying the N10, I expected everything to run faster than on the N7 by a noticeable margin.
Many emulators run slower on the N10 than on the N7. MAME4Ddroid and MAME4Droid reloaded are no longer completely smooth with more demanding ROMs, Omega 500, Colleen, UAE4droid and SToid are slower and some others needed much more tweaking than on the N7. I'm a little extreme on accuracy of emulation and I like everything to be as close to the real thing as possible. A solid 60 fps for me is a must (or 50 fps for PAL machines).
On the other side, there are other emus that ran very well: the .EMU series and RetroArch for example. These emulators are much more polished than the average quick port and they run without a flaw. They're great on the 10-inch screen and I enjoy them very much. The CPU intensive emulators (Mupen64Plus AE and FPSE) gained some speed but less that I anticipated.
So is this because of the monster Nexus 10's 2560x1600 resolution? Or is it because of limited memory bandwith? Maybe some emulators are not tweaked for the N10 yet. I wish some emulators had the option to set a lower resolution for rendering and then upscale the output. I think that many Android apps just try to push the frames to the native resolution without checking first if there is a faster way.
The N7 has a lower clocked 4 core CPU but has only 1/4 the resolution. I think that it's a more balanced device that the N10 which may have a faster dual core CPU but too much pixels to push. It's much like the iPad3 who was twice as fast as the iPad2 but had a 4x increase in resolution.
I am now considering going for a custom ROM on the N10 but I wonder if I will see an increase in emulation speed. Maybe those of you who did the jump can tell me. I'm thinking about AOKP maybe.
Any suggestion on that would be appreciated, thanks!
The emulators just need to be tweaked a bit to better perform on the completely different processor architecture. Really our processor is far more powerful than the Nexus 7 so the emulators should run faster. I too am a fan of the old games, and I play Super Nintendo and Game Boy Advance (and some Color) games quite often. I find performance to be perfect with no issues at all, but then again those arent exactly "demanding" emulators.
We do not have any sort of memory bandwidth limitation on the Nexus 10. The tablet has been designed to give the full needed 12.8 GB/s of memory bandwidth that is required for 2560x1600 resolution.
EniGmA1987 said:
The emulators just need to be tweaked a bit to better perform on the completely different processor architecture. Really our processor is far more powerful than the Nexus 7 so the emulators should run faster. I too am a fan of the old games, and I play Super Nintendo and Game Boy Advance (and some Color) games quite often. I find performance to be perfect with no issues at all, but then again those arent exactly "demanding" emulators.
We do not have any sort of memory bandwidth limitation on the Nexus 10. The tablet has been designed to give the full needed 12.8 GB/s of memory bandwidth that is required for 2560x1600 resolution.
Click to expand...
Click to collapse
Hmm, if no memory bandwidth limitation exists on the N10, wouldn't I be able to run GTA 3 at 100% screen resolution and not have significantly lower FPS, as compared to 50% resolution?
Even Beat Hazard Ultra seems to be a bit laggy on the N10. When I inquired about it to the developer, he said:
Having to render to that size of screen [2560x1600] will slow the game down. It’s called being ‘fill rate bound’. Even for a good processor it's a lot of work as the game uses quite a lot of overdraw.
The solution is to draw everything to a smaller screen (say half at 1280x800) and then stretch the final image to fill the screen.
Click to expand...
Click to collapse
A sad true my nexus 10 get dam hot and i have to play games at 1.4 or 1.2 that sux
Sent from my XT925 using xda app-developers app
espionage724 said:
Hmm, if no memory bandwidth limitation exists on the N10, wouldn't I be able to run GTA 3 at 100% screen resolution and not have significantly lower FPS, as compared to 50% resolution?
Even Beat Hazard Ultra seems to be a bit laggy on the N10. When I inquired about it to the developer, he said:
Click to expand...
Click to collapse
But fillrate isnt memory bandwidth. We need both more MHz and more raster operations to get higher fill rate of pixels per second. We can overclock the GPU to get the MHz, and that will help, but we have to find a way to solve the higher heat output too from that. More ROP's are impossible as it is a hardware design for how many we have. If we ever get to overclock up to around 750 MHz then we should see a 30-40% improvement in fill rate. At that point we may have memory bandwidth problems, but we wont know for sure until we get there. But the 12.8GB/s of bandwidth that we currently have is enough to support 2560x1600 resolution at our current GPU power. Our Nexus 10 also has the highest fillrate of any Android phone or tablet to date, about 1.4 Mtexel/s. And if we have memory bandwidth limitations, then we would see no improvement at all from the current overclock we do have up to 612-620MHz because the speed wouldnt be where the bottleneck is. Yet we can clearly see in benchmarks and real gaming that we get FPS increases with higher MHz, thus our current problem is the fillrate and not the memory bandwidth.
Also, the solution is not to render the game at half the resolution as that is a band-aid on the real problem. If the developer of a game would code the game properly we wouldnt have this problem, or if they dont feel like doing that then they should at least stop trying to put more into the game than their un-optimized, lazy project is capable of running nicely.
espionage724 said:
Hmm, if no memory bandwidth limitation exists on the N10, wouldn't I be able to run GTA 3 at 100% screen resolution and not have significantly lower FPS, as compared to 50% resolution?
Even Beat Hazard Ultra seems to be a bit laggy on the N10. When I inquired about it to the developer, he said:
Click to expand...
Click to collapse
With that logic you could buy any video card for a PC and it would run any game at the resolution the video card supports. That isn't the case because rendering involves more than just memory fill rate. There are textures, polygons, multiple rendering passes, filtering, it goes on and on. As EniGmA1987 mentioned nothing has been optimized to take advantage of this hardware yet, developers were literally crossing their fingers hoping their games would run 'as is'. thankfully the A15 cpu cores in the exynos will be used in the tegra 4 as well so we can look forward to the CPU optimizations soon which will definitely help.
Emulators are more cpu intensive than anything else, give it a little time and you won't have any problems with your old school games. Run the new 3DMark bench to see what this tablet can do, it runs native resolution and its not even fully optimized for this architecture yet.
2560*1600*4*60/1024/1024 = 937,3 MB/s for a 60 fps game at 32-bit depth. Most emulators don't use 3D functions so fillrate, rendering, overdraw won't be a factor. Most emulators are single-threaded (correct me if I'm wrong) and the A15 should shine in this particular situation and even more so in multi-threaded scenarios. With its out-of-order pipeline and greatly enhanced efficiency it should be perfectly suited for the job.
We have the fillrate, we have enough CPU power and I'm still wondering why simple app like emulators aren't much faster than that. Is it Android? Is it the Dalvik VM? Or is it because some emulators need to be written in native code instead of using Java VM? I'm not a developer and I have only minimal knowledge in this department. I can only speculate but I'm curious enough about it that I started googling around to find why.
Lodovik said:
2560*1600*4*60/1024/1024 = 937,3 MB/s for a 60 fps game at 32-bit depth
Click to expand...
Click to collapse
Just curious but what is that calculation supposed to be? total bandwidth needed? Cause I don't see your bit depth in there, unless the 4 is supposed to be that? If that is true than you are calculating on 4-bit color depth?
And then the result would just be bandwidth required for pixel data to memory wouldnt it? It wouldnt include texture data in and out of memory and other special functions like post processing.
2560*1600 = number of pixels on the screen
4 = bytes / pixels for 32-bits depth
60 = frames / second
/1024/1024 = divide twice to get the result in MB
Actually, I made a typo the result is 937,5 MB/s or 0.92 GB/s. This is just a rough estimate to get an idea of what is needed at this resolution just to push the all pixels on the screen in flat 2D at 60 fps, assuming that emulators don't use accelerated functions.
My point was that with 12.8 GB/s of memory bandwith, we should have more than enough even if this estimate isn't very accurate.
Thanks for the explanation
If there really were a memory bandwidth limitation the newer Trinity kernels and newest KTManta should help. In addition to the higher GPU speed they both allow (KTManta up to 720MHz) both ROM's have increased memory speeds which increase memory bandwidth to 13.8GB/s, up from 12.8 on stock.
Thanks for the info. There's so many configuration options available for the Nexus 10. I really enjoy having all those possibilities.
EniGmA1987 said:
If there really were a memory bandwidth limitation the newer Trinity kernels and newest KTManta should help. In addition to the higher GPU speed they both allow (KTManta up to 720MHz) both ROM's have increased memory speeds which increase memory bandwidth to 13.8GB/s, up from 12.8 on stock.
Click to expand...
Click to collapse
=Lodovik;40030*1600*4*60/1024/1024 = 937,3 MB/s for a 60 fps game at 32-bit depth. Most emulators don't use 3D functions so fillrate, rendering, overdraw won't be a factor. Most emulators are single-threaded (correct me if I'm wrong) and the A15 should shine in this particular situation and even more so in multi-threaded scenarios. With its out-of-order pipeline and greatly enhanced efficiency it should be perfectly suited for the job.
We have the fillrate, we have enough CPU power and I'm still wondering why simple app like emulators aren't much faster than that. Is it Android? Is it the Dalvik VM? Or is it because some emulators need to be written in native code instead of using Java VM? I'm not a developer and I have only minimal knowledge in this department. I can only speculate but I'm curious enough about it that I started googling around to find why.
Click to expand...
Click to collapse
You are taking what I said out of context. I was responding to someone else, thus the "quote" above my post.
Since you posted I loaded up some Super Nintendo, N64, and PlayStation games on my n10 without any issues. It may just be your setup. There are a lot of tweaks out there that could easily increase performance. One great and very simple one is enabling 2D GPU rendering which is in developer options. Just do some searching. GPU Overclocking won't help much, as you said above your games are only 2D. I am sure you can get them running just fine.