You Are Here:

Energy saving tips

Register Today

Register with Forum Nokia now and you'll enjoy the full benefits of the Forum Nokia membership.

Register Login
Community Highlights

Wiki article of the week

Zoom and Rotate Gestures in FlashLite for touch-enabled devices

Champion of the month

Jackson Feijó Jackson Feijó
Read more about Jackson on the Champions website.


Forum Nokia Events

Nokia Developer Days in South Africa
December 01, 2009
Johannesburg, South Africa

Forum Nokia Developer Conference ’09, India
December 07, 2009
Bangalore, India

LeWeb
December 09, 2009
Paris

Web Runtime Coding With Aptana WRT Plug-in
December 09, 2009
9am New York | 2pm London | 4pm Helsinki

Web Runtime Coding With Aptana WRT Plug-in
December 09, 2009
9:30am New Delhi, noon Beijing


View all
Avoid long-running frequent timers
Frequently triggering timers may prevent the processor from entering the low-power sleep mode and increase power consumption significantly. In Symbian programming paradigms, asynchronous notification-based services are embraced instead of polling.
Lazy construction and use of resources only when needed
Construct/load/open/initialize services just before they are needed and close/destruct objects right after use. In this way, unnecessary memory is not allocated and possible specific hardware components (like Bluetooth chip, cellular radio, HW accelerators) can be turned off by power management.
Screen saver and backlight
Do not override backlight and screen saver settings because they work automatically according to user-set preferences. Monitor the screen saver status, key locks, and foreground/background events to detect whether the device is in active use.

In special cases, overriding the settings is understandable (for example, in a navigation application). However, monitor the device status to check whether the prerequisites are still valid. For example:
  • Is the device connected to a power supply (charger or car kit)?
  • Does the application require lights on the foreground?
  • Is the battery level sufficient?
Implement idle time-outs for resources
Close hardware resources automatically after a period of user inactivity so that resources are not left open if the user forgets to close them explicitly.
Consider carefully when to use fancy UI effects
Animations and other similar user interface effects can be turned off when the device is locked or application is on the background. Various bells and whistles, like animations and UI transitions, look nice but they also consume energy, so at least provide an option for end users to turn them off if they do not add any value and are not necessary to perform a given task.

Back to top



Rate This

Bookmark this page: DeliciousDiggFacebookGoogleYahooStumbleUponRedditDiigoTechnocratiTwitter  Share this page Share this page Print this Page Print this page Invite a friend Invite a friend
RDF Facets: qdcZidentifierQSxhttpE3aE2fE2fwwwE2eforumE2enokiaE2ecomE2fTechnologyE5fTopicsE2fE44esignE5fandE5fUserE5fE45E78perienceE2fUserE5fE45E78perienceE2fUsabilityE5fTipsE2fE45nergyE5fsavingE5ftipsE2eE78htmlX qfnZupdatedQDx2009E2d10E2d05X qdcZtypeQUqfnZE45E78cludedFromGeneralE4CistingsQ qdcZtypeQUqwebZE52esourceQ qdcZtypeQUqwebZInformationE52esourceQ qdcZtypeQUqwebZPageQ qdcZtypeQUqfnTypeZE52esourceQ qdcZtypeQUqfnTypeZWebpageQ qdcZtypeQUqmarsZManagedE52esourceQ qdcZtypeQUqrdfsZE52esourceQ qfnZdistributionQUxhttpE3AE2FE2FforumE2EnokiaE2EcomE2FX qfnZtypeQUqfnTypeZE52esourceQ qfnZtypeQUqfnTypeZWebpageQ qmarsZlanguageQUxhttpE3AE2FE2FswE2EnokiaE2EcomE2FlanguageE2D1E2FenX qrdfZtypeQUqwebZInformationE52esourceQ qrdfZtypeQUqwebZE52esourceQ qrdfZtypeQUqwebZPageQ qrdfZtypeQUqfnTypeZE52esourceQ qrdfZtypeQUqmarsZManagedE52esourceQ qrdfZtypeQUqfnTypeZWebpageQ qrdfZtypeQUqrdfsZE52esourceQ qrdfZtypeQUqfnZE45E78cludedFromGeneralE4CistingsQ