Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
10 hours of battery life...really?
- Thread starter samywamy10
- Start date
- Sort by reaction score
The iPad can certainly hit 10 hours with it left on. The big battery drains are the screen, heavy OpenGL (games), and GPS for the units that have it.
Yeah, I leave my wifi on and get right around 10 hours.
I lose about 10% for hour of active use, lose 1-2% overnight.
WiFi doesn't use that much battery.
Another example is the wifi only Kindle 3. It gets 3 weeks battery life with the wifi on, 4 weeks with it off per Amazon's description, and I'd say that's about right based on my experience with that device.
3G, on the otherhand, does eat battery life if left on. The 3G Kindle 3 is rated at at 10 days with the the wireless turned on (wifi and 3g antennas are both on or off at the same time, no independent option to turn one off and leave the other on).
I lose about 10% for hour of active use, lose 1-2% overnight.
WiFi doesn't use that much battery.
Another example is the wifi only Kindle 3. It gets 3 weeks battery life with the wifi on, 4 weeks with it off per Amazon's description, and I'd say that's about right based on my experience with that device.
3G, on the otherhand, does eat battery life if left on. The 3G Kindle 3 is rated at at 10 days with the the wireless turned on (wifi and 3g antennas are both on or off at the same time, no independent option to turn one off and leave the other on).
The brightness setting is by far the biggest determination of battery life. Other important factors include 3G being on, GPS, and high GPU processing like when playing demanding games. Everything else is pretty small potatoes when it comes to battery life.
You should always check your brightness setting if you're not getting the advertised rates. Apple does not use 100% brightness when determining battery life under "normal usage".
The OP had his set on 100% which likely entirely explains why he wasn't getting 10 hours.
You should always check your brightness setting if you're not getting the advertised rates. Apple does not use 100% brightness when determining battery life under "normal usage".
The OP had his set on 100% which likely entirely explains why he wasn't getting 10 hours.
This! I've had no issues with my original iPad until I updated to 4.3.1. After updating the battery drained 10% at night, before it was just 1%.
Recalibrating the battery did fix it.
My iPad is on all day, everyday. I I took it off the charger at around 2 today and now it's 12:35 and I'm only at 44%
I've listened to music, watched a movie, browsed the web for at least a few hours, played angry birds, and all my notifications are on, also, email push every hour. My brightness is almost all the way up, I'd say about 85-90%. Personally, I'm very satisfied with my iPad's battery life. It doesn't even compare to my iPhone that can barely last me a day if I do half of those activities on it.
I've listened to music, watched a movie, browsed the web for at least a few hours, played angry birds, and all my notifications are on, also, email push every hour. My brightness is almost all the way up, I'd say about 85-90%. Personally, I'm very satisfied with my iPad's battery life. It doesn't even compare to my iPhone that can barely last me a day if I do half of those activities on it.
I dunno if it's the iPad 2 or the 3G but compared to my old iPad 1 the standby times stink. I charged it to 100% yesterday and didn't use it at all til this morning at 7am and it's down to 80% the iPad 1 would still be at 100% or very close to it like 98%
Sure, but that's far too simplistic a view.
The mail response can happen just as long as that connection is still open. Unfortunately, connections timeout after 5-45 minutes.
That's why ActiveSync and all other so-called mobile "push" clients (RIM excepted, with PINs and UDP) have to send a quicker-than-the-timeout heartbeat to the server to keep a connection open. If the connection stays the whole time, the heartbeat timeout is extended. If not, its delay gets smaller.
Relying on a constant heartbeat == not real push, just a long timed pull.
There is no pull, let alone a timed pull. The rest is accurate.
The heartbeat doesn't do anything other than keep the socket open (phone is behind a NAT, usually). The packet saying there is new data is pushed from the server. Since the client isn't polling on any schedule, it is considered push.