Does it use more CPU if you're not running any code? I mean a higher frame rate updates the display in the case of 30 fps to 60 fps 30 more times than normal but if the view doesn't change and no code needs to execute how much is really being used? Because, Flex has a invalidation for specific regions that triggers a redraw for certain areas only when they change and the Flash Player uses the display list to indicate to the GPU or software renderer to indicate what areas need to be redrawn.
It would be a good test to see how much battery is drained in a blank or simple app running at 30 FPS where there are no visual updates and then again at 60FPS. Then another test where there is a visual change, say a ball animating around the screen and measure the battery drain again in both 30/ 60 FPS. On Wed, Apr 2, 2014 at 1:09 PM, Alex Harui <[email protected]> wrote: > Using a higher frame rate can increase your cpu utilization and > potentially burn battery faster. You can change it at runtime for when you > really need it > Sent via the PANTECH Discover, an AT&T 4G LTE smartphone. > > Javier Guerrero García <[email protected]> wrote: > > > Exactly the way I felt the first time :) > > I mean, it's not THE silver bullet, and your > opaqueBackground/cacheAsBitmap/etc... optimizations of course counts > (hugely on low end devices), BUT ... you really can notice the difference > :) > > Cheers :) > > > On Wed, Apr 2, 2014 at 7:03 PM, After24 <[email protected]> wrote: > > > Hi Javier, > > > > To be honest I never tried to change the framerate of the application... > > I'm > > feeling a bit stupid now :-) > > Will try with an app on a Nexus S and a nexus 4. > > > > Thanks. > > > > > > > > -- > > View this message in context: > > > http://apache-flex-users.2333346.n4.nabble.com/Coding-a-better-flex-mobile-app-tp5888p5925.html > > Sent from the Apache Flex Users mailing list archive at Nabble.com. > > >
