Iphone5 DEVICE overheat issue

I just noticed that my game running in the iphone5 device starts overheating the device. The game starts running really slow.

Done some research and found out that the issue is that the processor of the phone is running 100% all the time. And thats whats causes a overheat.


My game is very dynamic, the concept is waves of enemies thats vary with bosses.

Someone have some tips to make that overheating stop? Like reduce object creations, my app does have a lot of it, blood weapon swipes enemies creating frequently.

**Ipad is good so far.

Are you sure it is running at 100% all the time? What is your frame rate?

in xCode you can monitor the CPU usage when you compile to run on your iPhone 5. you can also examine the frame rate and other important factors with the GPU as well as network usage, disk usage. this will allow you to make adjustments and test them. This just helped me a great deal with a game i'm about to release. For me, i had to reduce the number of active objects (it was ok, the style of game made it an acceptable compromise).

I just tested...and no is not all the time with 100%....

The frame rate is set to 60. What do you sugest?

Well, again, for me, I reduced the number of active objects. 60 FPS should be fine.

I'd run the game while attached to xcode and see where the CPU spikes are happening try to determine what's heating up the phone that way.

Yeah...i just reduced the object creations frequency and gave it a smaller heat....maintained the app running normally.


But in a long run the device gets hot... =/

With your device connected to your mac, try run the profiler:
http://www.andersriggelsen.dk/clickt...rofilemenu.png

Select the time profiler:
http://www.andersriggelsen.dk/clickt...meprofiler.png

Make sure these checkboxes are checked as in the image:
http://www.andersriggelsen.dk/clickt...rtcalltree.png

Then press the record button in the profiler to play your game for a while (in the frame that makes it overheat).
Take a screenshot of the statistics screen and post it here.

That will make it possible for me to tell you what makes your game go slow.

Here is the print Anders,

Attachment 15276

http://postimg.org/image/fd9mlvfeb/
http://postimg.org/image/n2ctbey8d/

From 40 seconds forward is that frame.

thanks

It seems it spends a lot of time unpacking compressed data from the .cci file.
Any chance you can expand the top item on that list "NSData(NSDataExtension) zlibinflate" to reveal where it does this the most? Expanding it down a few levels into the hierarchy would be helpful.

There can be a number of causes for this but the most likely one is that your app constantly load some image resource from disk - and that can again be caused by a number of things:
- You manually do it in your events
- Your app consumes too much memory and is given memory warnings from the iOS operating system.

When the app receives a memory warning it attempts to free as much image data from memory it can.
When the image resource is needed again (for drawing on screen) it will be reloaded from disk.

If you app in general consumes too much memory it goes into this bad cycle where it loads a lot of resources, gets a memory warning, unloads all resources - only to reload them again almost immediately.
As you can see this is very power consuming but it is necessary or the app will be force-closed by iOS and will look like a crash.

Your only way to fix this is reduce how much memory you are using.

If you want I can profile your game more in-depth to figure out exactly where the problem lies.

Well... thats seems about whats happening.

It is a survivor mode fight game...so the enemies keep showing up until you die.
So when a enemy gets killed it unloads (i am assuming that) and it might be the next one since is a random value that generates the enemy.
The frame does not end until you die...is eternal you can say.

And we have also the hit sprites, fire atacks, ground hits and other small objects that are created along the game.

If i kil that, ill be killing the game actually... so...

I could send you the file to take a look at it in profiling. How can i do that? Cant do it here, its the hole game.

(This issue does not happened in ipad)

Here is the print of the item you asked...

http://postimg.org/image/atz4uvjqr/

I believe my images are too big... i made a size mistake in the beginning, and that's what's consuming too much memory.

Actually that doesn't look like it reloads the images all the time. It just shows that the initial time spent loading the frame is skewing the statistics a lot. Playing the frame for a longer period of time without changing frames will make more accurate statistics.

I see in the graph that there is a place where it spends a lot of CPU time. What frame is that? Any chance I can profile this game myself?

Yes... I am traveling now, but come back next week. I ll make a file so you can download.

One question, the app is in review again. Is this a release blocker?

Anders, i am sending you the mmf file now by message.