hyperPad drains battery when on USB to Mac

  • hyperPad is so heavily flogging the system that an iPad is not able to sustain full charge when connected to the humble USB of a Mac.

    I've never seen any other app do this. Nor ever felt my iPad get this hot.

    Please do something about this.

  • This happens to me too...
    Some apps take over memory and use up more battery than the rate of charging.

    • I would check the settings and turn off ALL background app refresh as it uses 20% of total battery.

    • Turn off Bluetooth if necessary.

    • Turn off your WiFi (from your device.) if unneeded. Note that HyperPad doesn't need internet to edit games, but only to view games on the hub or to upload/update projects.

    • Close all unneeded running background apps, as they take about 30% of memory.

    This seems a lot, but you don't have to do all of these... :3

  • @RobinsonX I'm all this except for turning off wifi. Still seeing that drain.

    This is something wrong in hyperPad. Not even the most exhaustive DAWs and synths do this.

  • @Deeeds I think what it comes down to is hyperPad is unstable as a mother of god due to the size of the project compared to the size of the team running it.

  • Admin

    This is an issue we're aware of and actively dealing with (it was much worse in the early days) and there is definitely room for improvement.

    The major issue with this is the way we handle I/O and file saving. Every modification you make is saved. We did this because the iPad has (especially early on) very limited memory and saving actions to 'disk' allowed us to free up memory for other heavy lifting.
    Additionally in the case of crashes, your projects are more likely to be recovered.

    However, ever I think it's time to look at this again since iPads have become much more powerful.

    The other issue is that we're running the graphics engine in the editors as well. Think of this as running a game the entire time. There are definitely improvements to be made here. @Deeeds has even done some researched and gave a few suggestions. There are also other spots that we can improve on.

    Due to the nature of what hyperPad is, it will never be as battery efficient as other apps. But there is room for improvement :).

  • @Murtaza Here is the area to focus on:

    0_1512250683182_Screen Shot 2017-11-21 at 6.40.37 PM.png

  • @Hamed @Murtaza

    As it turns out, I don't have to pain myself trying to explain this, the guru of this bug has been kind enough to stay on top of it:

    CACurrentMediaTime is a friendlier converted version of mach time that's slightly slower and less ideal. Read more here:

    At any rate (oh, puns!) here's the goodies, the most important bit, but he does some other clever stuff in the above file that's well worth taking a look at and learning from.

    -(void) mainLoop:(id)sender
         * Experimental game loop.
         * To stop the game becoming unresponsive after heavy load.
         * See : http://www.ananseproductions.com/game-loops-on-ios/
        static double bank = 0;
        double frameTime;
        frameTime = _displayLink.duration * _displayLink.frameInterval;
        bank -= frameTime;
        if (bank > 0) {
        bank = 0;
        CFTimeInterval now = CACurrentMediaTime();
        [self drawScene];
        CFTimeInterval elapsed = CACurrentMediaTime() - now;
        bank = elapsed;
        if (elapsed > frameTime) {
            bank = frameTime + fmod( elapsed, frameTime );

  • @Hamed @Murtaza

    And here's the most obvious thing I'm going to say today.

    When users aren't touching the screen in the Scene Editor or the Behaviour editor, deactivate this call:

    [self drawScene];

    Do this and make the above changes (use mach time, though) and we'll all be able to charge our iPads from our computers, AND use hyperPad at the same time.

Log in to reply