NanoToolkit Blog

The Way to Keep in Touch.

Quick Follow-up on Google Cloud Messaging Power Consumption

This is a quick follow-up on previous post on whether Apple Push Notification is more efficient than Android and Windows Push Notification . I did a quick test. I let my HTC Amaze run over night with Android’s “Restrict background data” enabled. I let my phone be on for eight hours. It had 77% battery charge at night and eight hours later it still had 77% battery Charge. But Then I decided to have equal intervals where My Android ICS would be once on “restrict Background Data” and once with Android Background Notification be enabled.

After a 100 minutes with “Restrict background data” Turned on setting, my Phone Battery remained at 55%. There was only 3,988 bytes (approximately 3.9 Kilobytes) sent out of that android phone in a period of 100 minutes.

After a 100 minutes with “Restrict background data” turned off setting, my Phone Battery dropped from 55% to 52%. There was 143,800 bytes (approximately 140 Kilobytes) sent from that Android Phone in a 100 minutes.

You Android’s behavior is very similar to Windows Desktop and Linux. That is if you have a socket open on to some end-point, The OS is gone send “heart-beats” or so called keep-alive packets to the other end of the socket. For Instance on Windows when a Socket is open and Keep-alive is gone be configured this way. Linux sockets also have a similar keep-alive option.