Can high end android phones handle... - Android Q&A, Help & Troubleshooting

A Nintendo gamecube emulator? There are ngc emulators out there for Mac & pc, butI was wondering if it can be possible for high end android. Now That would be awesome.
Sent from my ADR6400L using Tapatalk

Do you by chance know the clock speed of a nintendo gamecube? Emulators usaully use 100x the processing power. I don't think its possible unless the processing speed is lower than 13 mhz

ragul40 said:
I don't think its possible unless the processing speed is lower than 13 mhz
Click to expand...
Click to collapse
The PS1 has a clock speed of 33.8688MHz and 1GHz+ devices can easily play it's games (even lower-end devices can play some at full speed). Specs of the Nintendo Gamecube:
485MHz custom CPU with 162MHz custom graphics processor
Click to expand...
Click to collapse

Related

[Q] Hows this thing on gaming?

Hows the gaming on Tbolt?. Way better than older snapdragons like evo or inc? Comparable to galaxy s? Choppy? Smooth? Im just curious.
It is a lot better than the Evo but not on the same level of SGS phones, Samsung is always ahead in the graphics department.
So maybe droid x level?
Depends on what you are playing, of course. N64oid doesn't run all games smoothly yet.
The new Snapdragon processor that is in the thunderbolt is pretty much the same as the first hummingbird, so the graphic capabilities should also be about the same. I came from a Captivate and all the games I played on it play just as well. I do miss that SAMOLED screen though...
emulators are available right? like gameboid etc? You dont need root do you?
Familyguy1 said:
emulators are available right? like gameboid etc? You dont need root do you?
Click to expand...
Click to collapse
Dont see whynot
I play this stupid little game called The Elements which is VERY processor intensive.
It ran pretty good on my Incredible. Ran pretty choppy on my Droid X, but on the Thunderbolt, it's smooth as heck. Way better than the previous two phones.
I bought the let's golf game accidentally but its a lot of fun and runs great for whatever kind of processor usage it takes...I still have to get raging thunder off my Droid but that should be good too..
Sent from my Thunderbolt using XDA App
SeenNotScene said:
Depends on what you are playing, of course. N64oid doesn't run all games smoothly yet.
The new Snapdragon processor that is in the thunderbolt is pretty much the same as the first hummingbird, so the graphic capabilities should also be about the same. I came from a Captivate and all the games I played on it play just as well. I do miss that SAMOLED screen though...
Click to expand...
Click to collapse
It is not anywhere close to the Hummingbird when it comes to graphics. Go look at some of the Quadrant tests and look at how smooth the graphics are. Thunderbolt stutters a bit but way way way better than the Evo ever was or could be.
If you run a Smartbench 2010 test, it will show the results for a SGS phone, graphics score way higher.
engagedtosmile said:
It is not anywhere close to the Hummingbird when it comes to graphics. Go look at some of the Quadrant tests and look at how smooth the graphics are. Thunderbolt stutters a bit but way way way better than the Evo ever was or could be.
If you run a Smartbench 2010 test, it will show the results for a SGS phone, graphics score way higher.
Click to expand...
Click to collapse
Yea because not the humming bird CPU but the sgs gpu (graphics processing unit) the snapdragon is was superior but Samsung gpu is better
Sent from my ADR6300 using XDA Premium App
superchilpil said:
Yea because not the humming bird CPU but the sgs gpu (graphics processing unit) the snapdragon is was superior but Samsung gpu is better
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
Hummingbird is both the CPU + GPU. CPU wise, they are based on ARM Cortex A8. Info:
http://en.wikipedia.org/wiki/Samsung_Hummingbird
http://en.wikipedia.org/wiki/ARM_Cortex_A8
So in the end, Hummingbird is superior when it comes to graphic capabilities. Thunderbolt is faster when it comes to data crunching and processing.
"The current generation Snapdragon uses Adreno 205 GPUs. This GPU is just as fast as the Hummingbird, if not faster."
http://www.tested.com/news/hummingbird-vs-snapdragon-vs-omap-vs-tegra-2-arm-chips-explained/1704/
SeenNotScene said:
"The current generation Snapdragon uses Adreno 205 GPUs. This GPU is just as fast as the Hummingbird, if not faster."
http://www.tested.com/news/hummingbird-vs-snapdragon-vs-omap-vs-tegra-2-arm-chips-explained/1704/
Click to expand...
Click to collapse
That is not what the benchmarks are saying. Run one yourself.
Benchmarks are Benchmarks, Real Life performance is Real life performace.
My TB has been beastly on Words with Friends.

Tegra 3 games on sgs3

Can someone help me? Why tegra 3 games doesn't launch on the s3 ? And the s3 has better processor!
Sent from my GT-I9300 using xda premium
Maybe because they're made for the tegra 3 not exynos.
Sent from my GT-I9300 using xda premium
louayjoumaa said:
Can someone help me? Why tegra 3 games doesn't launch on the s3 ? And the s3 has better processor!
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Mate tegra 3 has a different or addition Gpu instructions Set proprietary from Nvidia that others gpu doesn't have and make games on tegra look a little bit better.
And this is not about who has the fastest Cpu but about GPU so tegra 3 will never launch as far as I know on others cpu as the exynos for example on Samsung because Mali Gpu doesnt not simple have the requirement in orther to run Tegra Games
Hope it helps
Cheeers
Sent from my GT-I9300 using xda premium
so what ur telling me basicly is, the samsungs are better for raw processing power. But for games and video things the HTC's are better?
Kinda like xbox, the xbox has a better gpu.
games like dead trigger just require a file edit to enable all tegra specific ****s as they call, its just a software trick which can by bypassed by some well known dev. atleast for some of the tegra based games
soulzero said:
so what ur telling me basicly is, the samsungs are better for raw processing power. But for games and video things the HTC's are better?
Kinda like xbox, the xbox has a better gpu.
Click to expand...
Click to collapse
No exactly... but yes Samsung has a pretty decent raw processing power and in some case like HTc one x vs S3 exynos dominate the Htc in cpu power..but Tegra Gpu is not really better than let say others Gpu for example mali400 or adreno 320 as far as gaming benchmark is concern but as I said it has just some extra instructions set or api that make the game look better...like more intensive smoke effect, better lightning , better water reproduction etc. And yes I believe that game will be better for hardcore gamer (lol) on tegra devices like HTC one X for example ( with only supported Tegra Games)
Sent from my GT-I9300 using xda premium
but as I said it has just some extra instructions set or api that make the game look better...like more intensive smoke effect, better lightning
Click to expand...
Click to collapse
Regardless of what movies suggest, a processor does not have commands for "make that game look awesome" or "add lightning here". All they are capable of doing is trigonometric manipulation with dots, lines, triangles and squares.
Here's a short and somewhat technical description on how e.g. illumination is calculated. As you can see, nothing but lots of math - not a prepared and ready-for-use command
http://http.developer.nvidia.com/GPUGems2/gpugems2_chapter38.html
The difference between Exynos and Tegra is that Nvidia actually cares a lot about getting developers on their platform. (Well it is their last straw in mobile computing and they are pretty much f*** if that fails since they only sell parts, not entire platforms)
As a result they help with development, costs and give lots of promises to have the games exclusively appear for their platform. But as others said, usually there is not really a reason for the limitation and in some case a small manipulation of textfiles is sufficient to trick the games into believing they are running on Tegra platforms and thus use their full capacity.
To some extend you can compare it with the exclusive games on Xbox360 and PS3. There is obviously no technical reason why it could not be ported to the other platform, but often the studios still do not. Some stuff may look better on Xbox, some on PS3. However that usually boils down to how well the developers know the platform and especially the completelty different CPU architectures (Cell vs PowerPC)
d4fseeker said:
Regardless of what movies suggest, a processor does not have commands for "make that game look awesome" or "add lightning here". All they are capable of doing is trigonometric manipulation with dots, lines, triangles and squares.
Here's a short and somewhat technical description on how e.g. illumination is calculated. As you can see, nothing but lots of math - not a prepared and ready-for-use command
http://http.developer.nvidia.com/GPUGems2/gpugems2_chapter38.html
The difference between Exynos and Tegra is that Nvidia actually cares a lot about getting developers on their platform. (Well it is their last straw in mobile computing and they are pretty much f*** if that fails since they only sell parts, not entire platforms)
As a result they help with development, costs and give lots of promises to have the games exclusively appear for their platform. But as others said, usually there is not really a reason for the limitation and in some case a small manipulation of textfiles is sufficient to trick the games into believing they are running on Tegra platforms and thus use their full capacity.
To some extend you can compare it with the exclusive games on Xbox360 and PS3. There is obviously no technical reason why it could not be ported to the other platform, but often the studios still do not. Some stuff may look better on Xbox, some on PS3. However that usually boils down to how well the developers know the platform and especially the completelty different CPU architectures (Cell vs PowerPC)
Click to expand...
Click to collapse
You dont know what your talking about and...no offense Since the graphic processor is all about calculating polygon etc can you for example on Pc run a Dx11 Game in Dx10 or Dx9 GPU Cards??? so that your Dx10 graphic CARD will render the game with same details , tessellation as a Dx11 graphic card?? WELL NO and im repeating again there is some Hardware tweak on Tegra device so the software (Games) could look better yeah its all about polygon yes but how or the way you get those polygon matters and for that gpu architecture matters also
You might tweak some tegra games by modifying some file in order to run it on other devices but I believe you wont have the same experience as on tegra device at least for the must uptimized tegra game
Get your fact straight
Sent from my GT-I9300 using xda premium

Nexus 10 PSX Emulators

Hey guys! Just got my Nexus 10 an am thrilled with it.
Has anyone set up FPSE on it? I downloaded it and installed a bios etc. but when I try to play a game (I ripped an old copy of Star Wars Jedi power battles I found in a box in my room) the graphics do not load properly. I have tried with and without the Opengl plugin. Does anyone have any insight? I have played with the settings for video as well but am not really sure what to change to fix this. I'm running paranoid android if that has any effect...
Edit:
OK Turned off OPENGL and now the graphics load perfectly! Theyre not as smoothed as they would have been I guess, but at least I can play now!! The only thing is that the game seems to be moving is fast motion! I'll try the frame limiter and report back
Twisted metal
Can Twisted Metal be played on Google Nexus 10? I think that game will be awesome to play in touch screen mode.
lidzhet said:
Can Twisted Metal be played on Google Nexus 10? I think that game will be awesome to play in touch screen mode.
Click to expand...
Click to collapse
I'm sure it can. I got a couple of my old games working flawlessly now. The framerate limiter stops the games from being payed in fast forward. Doesn't look like the Nexus 10 is playing nice with opengl though, will have to see if there is an update to allow this to work.
I doubt nexus 10 will ever work with opengl. It uses the frame rate of the nexus 10 to upscale. Don't think the tablet can handle that kind of processing demand.
Sent from my SCH-I535 using xda app-developers app
duarian said:
I doubt nexus 10 will ever work with opengl. It uses the frame rate of the nexus 10 to upscale. Don't think the tablet can handle that kind of processing demand.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
And why do you think that?
Sent from my Nexus 10 using xda app-developers app
ady_seray said:
And why do you think that?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Because upscaling a ps1 game to 2560x1600 resolution is going to take more than a dual core processor and onboard GPU. Its on a resolution basis...the higher the resolution the more demanding.
Sent from my SCH-I535 using xda app-developers app
duarian said:
Because upscaling a ps1 game to 2560x1600 resolution is going to take more than a dual core processor and onboard GPU. Its on a resolution basis...the higher the resolution the more demanding.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
True but then why do games like dead trigger and vice city work in 2560x1600 with very good fps, and a 14 year old ps1 game would not.
Personally I think it can handle it easily (if a tegra 3 can do it then the exynos 5 can do it blindfolded, hands tied to the back, one foot chopped off and thrown into the sea with a boulder tied to its neck)
Sent from my Nexus 10 using xda app-developers app
Because game emulation =/= PC games.
Emulating games take much more CPU power than modern PC games mainly because those PS1 games were made for a PS1 and not a PC. That would be why you can't just stick in your PS1 disc and play the game. The emulator makes the game readable by the PC and that takes tons of power.
Emulating games take about 100x the power of the original system. So while the CPU frequency won't translate directly to 100x, the architecture of the CPU also is taken into account.
EDIT: I consider Android games PC games since the gap between PCs and mobile devices are starting to close.
404 ERROR said:
Because game emulation =/= PC games.
Emulating games take much more CPU power than modern PC games mainly because those PS1 games were made for a PS1 and not a PC. That would be why you can't just stick in your PS1 disc and play the game. The emulator makes the game readable by the PC and that takes tons of power.
Emulating games take about 100x the power of the original system. So while the CPU frequency won't translate directly to 100x, the architecture of the CPU also is taken into account.
EDIT: I consider Android games PC games since the gap between PCs and mobile devices are starting to close.
Click to expand...
Click to collapse
Well then, don't want to sound ignorant, if a PC cpu that has approximately the same performance as the cpu in the N10 ( the means of comparison being geekbench), is able to emulate PS2 games then it would easily emulate PS1 games.
Through deduction the N10 having a similar performance to that PC CPU should be able to easily emulate PS1 games. Hence why gentlemen I do believe that the n10 can breeze through PS1 games.
Sent from my Nexus 10 using xda app-developers app
ady_seray said:
Well then, don't want to sound ignorant, if a PC cpu that has approximately the same performance as the cpu in the N10 ( the means of comparison being geekbench), is able to emulate PS2 games then it would easily emulate PS1 games.
Through deduction the N10 having a similar performance to that PC CPU should be able to easily emulate PS1 games. Hence why gentlemen I do believe that the n10 can breeze through PS1 games.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
While I don't understand all the basics -- I can see the point though if it's trying to upscale the resolution.
2560x1600 = 4096000 pixels
320x240 = 76800 pixels (most common ps1 resolution)
So if you figure that you're running about 60fps...
That's information for 241152000 more pixels in a second that it needs to create information for.
Depending on the efficiency of the algorithm in the emulator/openGL code -- it's very possible it can tax the system. Remember also the heat throttle on the N10 which will reduce its performance below what you might expect it to max out at. I also think you're overestimating the power of an N10 to a PC. Think more maybe along the lines of a netbook or older laptop if trying to find a power comparable just because of all the differences in the architecture (for example you don't have the entire system in a single chip... there will be bottlenecks in the N10).
ady_seray said:
Well then, don't want to sound ignorant, if a PC cpu that has approximately the same performance as the cpu in the N10 ( the means of comparison being geekbench), is able to emulate PS2 games then it would easily emulate PS1 games.
Through deduction the N10 having a similar performance to that PC CPU should be able to easily emulate PS1 games. Hence why gentlemen I do believe that the n10 can breeze through PS1 games.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
I never said it wouldn't work on the N10. Your reasoning behind emulation was just wrong so I felt the need to correct it. This way, you will probably now understand why you can't emulate PS3 and xbox360 games on your computer. It won't happen anytime soon.
Emulation also depends on the emulator. If it's well-coded, then it'll emulate things well. If it's not, well then you'll get slow downs. I never used FPse so I don't know how great it is, but I'm assuming it's good.
Anyway, most likely than not, the N10 can probably emulate PS1 games. It probably can't emulate PS2 games at that resolution though.
The N10 emulates ps1 games fine. Its when you use openGL that it really has a performance hit. Which attempts to upscale everything to the resolution of the tablet...which is very high
Sent from my SCH-I535 using xda app-developers app
ceribaen said:
I also think you're overestimating the power of an N10 to a PC. Think more maybe along the lines of a netbook or older laptop if trying to find a power comparable just because of all the differences in the architecture (for example you don't have the entire system in a single chip... there will be bottlenecks in the N10).
Click to expand...
Click to collapse
I guess I might be overestimating a bit, but my core2duo laptop had the same geekbench score as my (at the time) 2.0 GHz OC'ed N10, which was around 3000. My core2duo laptop can emulate ps2 games ok-ish that's why I believed the N10 can emulate PS1 games fine, because it's on par with my PC CPU.
The thermal throttle issue, while being a pressing and annoying one, can be reduced or eliminated entirely by upping the thermal limits with ktoonsez kernel.
Although I do agree that proper software is as important, or more important, than hardware, and that if the emulator is not coded properly it's useless to have all this horse power.
Sent from my Nexus 10 using xda app-developers app
I use ePSXe and it works very well. Open gl plugin is no good though as the device seems to process faster than the plugin is coded. Using hardware gpu works well enough but you will have original ps1 graphics.
Sent from my SAMSUNG-SGH-I317 using xda premium
The Nexus 10 can easily emulate a PS1. The fact that the OP has been forced to use the frame limiter proves that the emulation was much faster than needed. Also, even without the OpenGL plugin, you are already pushing the game at the native N10 resolution if you play full screen, so it's not a question of bandwidth or GPU because you're using the same number of pixels, accelerated or not.
What the OpenGL plugin brings is nicer graphics with less jaggies and the GPU of the N10 can easily handle the very low polygon count of the PS1 games. The benefit of that is to play PS1 games with even better graphics that on the original console. But, remanipulating the textures to fit an higher resolution is a difficult task and you end up with artifacts that were not originally there. The N10 GPU can handle the output but the problem is feeding it fast enough to keep the original framerate.
If you want to see some videos of emulation on the N10, you can watch this one and some others on the same Youtube channel:
http://www.youtube.com/watch?v=9leFKGewvsM
As you will see, the N64 and PS1 emulator only take a fraction of the CPU power of the N10. Thermal throttling may be a factor on the N10 but not with those older consoles.
My N7 handles quite nicely the OpenGL plugin of FPSE. The Tegra3 chip isn't the most powerful out there but it has better support than the Exynos. That will change when N10s will finally be in the hands of all those that (like me!) are waiting for more stock to buy one. I live in Canada and, about 10 times a day, I check to see if the N10 is available on the Google Store. It's a very looooong wait...
I don't think it is possible to run fpse OpenGL currently on the Nexus 10. OpenGL is upscaling the graphics to 2560 x 1660 native, which is causing tremendous slowdown when you consider this + hardware comsumption of Console emulation. Is there any way we can recommend a "Resolution downscale" option for fpse? At LEAST bring the game down to 1920 x 1080p which is still a great resolution. It would be nice to NOT have an "MAX" or "MIN" setting, but an "In Between" regarding screen resolution.
Speed isn't the issue because if the OP had OpenGL disabled he was running in software mode which means it was only running off the CPU.
Nexus 10 isn't the issue because the GPU supports OpenGL 3.0 standard, so any OpenGL issues will be software related which means they can be fixed quite easily.
Only question is who needs to fix it, the emulator dev or Samsung driver team?
brees75 said:
Only question is who needs to fix it, the emulator dev or Samsung driver team?
Click to expand...
Click to collapse
At this point in the development of an entirely new architecture it could be either one. We do know that the Mali GPU driver does have at least one issue already. Most likely though I would guess it would need to be fixed in the emulator software, because the people who create those while good, are not as good as the people working with those who design the hardware itself. And again, the software would need to be written to take advantage of an entirely new architecture. And Im not talking about the CPU only here. That is a pretty large architectural step for ARM too, but the GPU is a huge step in design. This is ARM's first unified shader architecture and both drivers and software need to be written differently to take advantage of such. The CPU is a large evolution of previous designs, the GPU has a lot of complete rework from the ground up.

[INFO] Nexus 10 vs Nexus 7 and emulators

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.

[Q] Current Android phones?

I saw Android phones today with cpu like 2.2 ghz quadcore or something.
As I can remember I was able to play PCSX2 smoothly with a 2.9 ghz dual core PC before, as well as a laptop something like 2.4 ghz.
I'm planning to buy one, are current smartphones capable of running emulated consoles smoothly? (PS1, PSP, DS, maybe PS2)
If yes, can you suggest what phone?
If no, are the hardwares not good enough or is it the emulators not perfected yet? (will current hardwares run them well in the future)
Thank you~
weirdopunkd said:
I saw Android phones today with cpu like 2.2 ghz quadcore or something.
As I can remember I was able to play PCSX2 smoothly with a 2.9 ghz dual core PC before, as well as a laptop something like 2.4 ghz.
I'm planning to buy one, are current smartphones capable of running emulated consoles smoothly? (PS1, PSP, DS, maybe PS2)
If yes, can you suggest what phone?
If no, are the hardwares not good enough or is it the emulators not perfected yet? (will current hardwares run them well in the future)
Thank you~
Click to expand...
Click to collapse
PC's and Phones use different architecture that is not directly comparable or compatible.
PS1 Games are playable with an app called FPse here:
Other games are playable if they have a specific app with a GPL port like Doom 3 or Jedi knight. Other older games can be played using other emulator apps like Dosbox Turbo but performance is limited.
ps2 emulator
so is there ANY ps2 emulator for android|?
You can use FPse for PS game, PPSSPP for the PSP game. As to DS, their are different DS emulator, among which Drastic is the fastest, most game can run with full speed.
Awesome. I think PS1, PSP and DS emu are more than enough
I'm picking between Note 3, Nexus 5 and Xperia Z1. What do you think is the best for gaming especially for console emulation?

Categories

Resources