next »

[PompiPompi]

I haven't researched into this subject too much, except that my previous game (Sumerian Blood) was impossible to play during summer because the AI would make the device boil.
It was cool on a multiplayer game though.

My next game is going to be a turn based RPG, so I think I won't use the CPU side too much, but the GPU side or generally SoC might over heat from rendering 3D graphics?

Please share your experience with Android devices profiling...

[Muz]

Lol, really hard to profile 'Android devices'. It's like trying to profile 'Windows computers'.

There's a huge variety of phones out there, from dodgy hacked China phones to budget models to high end ones like the Samsung S3 and Note 2 which have close to the power of a computer half a decade ago. But maybe not the heat sinking capability. IMO not even really worth trying to profile it because you get a whole generation in half a year at this rate.

Games like The Sims actually do intensive 3D rendering and they seem to play fine. I find that a lot of games that are ported tend to overload and crash the system, so I've stopped playing most non-native games. Maybe lack of optimization or how it deals with the hardware.

[PompiPompi]

Err, you can profile "windows computers", you have tools that run across all windows systems that can run them. So I don't see your point.
Of course different devices have different capabilities but the basics are true for most of them, unless there are major hardware changes between them.

On the PC I can profile the CPU, how much time is spent on each function and etc. GPU profiling is a bit more limited, NSight gives you GPU duration for every frame if I am not mistaken. I don't recall if it gives time per draw call.
But this works on many NVIDIA GPUs, you don't need a different program for different NVIDIA GPUs.

On an Android device you can probably measure time spent in each thread, maybe each function. I am not sure about the GPU stuff, as some Androids have SoC.
Also, I am not sure how this translates to heat and battery life.
I am sure there is something that can be said except for "it's impossible to do much because there are many different devices"

So this is why I ask.

[rivon]

I googled this: http://developer.android.com/tools/debugging/debugging-tracing.html

[Muz]

My point is that if you're going to profile them, you've got to be a lot more specific with the kind of device it is or the O/S. Farmville used to overheat my old laptop to the point where it shut down, but I can't say that it's too heavy duty for most PCs.

I'd be really surprised if you could overload a Samsung S3. My target market is usually something along the lines of a Nexus, probably the Android 2.1 phones for stuff like apps.