I've had several instances where the battery drain quickly. Using the System Activity app I can confirm that there is some application that is running the CPU and 100% constantly when this is happening. I checked several times over a 10 min period with the System Activity app and it was always at 100 % about 60% User and 40% Kernal. Additionally, as expected, the case remained warm. The only solution was to reboot.
I got the email from Apple about the battery life. I posted a couple times on their forum because I noticed that battery life was not as good with 3.1 as it was before the update. Mine was not as bad as others who posted but it was apparent. After a coupld power cycles everything seemed to smooth out.
I have noticed problems with the wifi. It will just drop, even when I'm standing next to the router. I have to turn off the wifi on the phone and back on then it's fine. Very unpredictable.
have you tried to turn off the locking? could be that it's trying to put the phone to "sleep" to save battery
Has Apple ever done anything like this in the past? I like it.
Yeah.
Apple engineers contacted me a few times for an issue with iTunes importing CDs very slowly (like less than 1.0 x). Ran a few tests and sent them the results back.
Thousands of people have noticed after updating to 3.1 they have no WiFi whatsoever, they simply cannot connect. Most times when I turn on wifi my network doesn't appear, and the few times when it does I try connect I get the message "unable to connect....". It's a widespread problem with no solution yet.
However I wish Apple would solve your problem and thousands of others (if that number is legitimate) as soon as possible, how come it is a widespread problem when they sell millions of iPhone and iPod touch?
Wish Apple would address the battery issues with 15" MacBook Pros that have been "upgraded" to Snow Leopard.
Guess the Snow Leopard adopters with battery problems have been officially marginalized...I truly hope Apple puts some effort into helping us as much as they are doing for their Iphone Cash cow.
I am/was an apple advocate for over 20 years but this frustrating battery issue is not helping to perpetuate that.
With various reports of poor iPhone battery life following the 3.1 OS update, Apple has reportedly begun asking users about its experiences and usage habits in an attempt to address the issue..
Ever since I got my iPhone 3gs the battery life is horrible. This morning my battery was 100% . in 2 hours it's now 53%. I have made 2 phone calls and have went to this site.
(of course, we're straying from the battery life issue.)
Quote:
Originally Posted by Ireland
I'm an not going to even talk about my network or router anymore, as I said I find it insulting.
Which is a shame, because the only way to work out why it works for some and not others (and thereby help establish where the problem lies within the iPhone OS) is to try and narrow down the variables...
My LAN set-up is:
- iPhone 3G, with 3.1.
- 802.11g, with WPA/AES authentication (the SSID is different from default, and hidden, and the password is 15 characters.)
(it's an older Belkin access point: I did recently update firmware, because I switched from WPA/TKIP to WPA/AES and it then kept locking up. I found that there was more recent firmware that what I was running with, and that seems to have helped a lot.)
- DHCP (running on a separate server, not the access point.)
my phone is set to auto-join my home network, but I have the "Ask to join other networks" set to Off.
I do observe a delay sometimes, in the iPhone acquiring my network after unlock, but I've only had problems when the WiFi network itself had locked up (see above) or when other nearby networks have crowded out the channel I was using.
OK, fine. I was just asking a few questions. I'm sure there is something in the OS that is doing this. But I don't think it is as cut and dried as you suggest.
Oh but it is. I looking into this for about 3 hours the other night. It's very cut and dried. In 3.0 and 3.1 this is a bug, it's that bloody simple.
(of course, we're straying from the battery life issue.)
Which is a shame, because the only way to work out why it works for some and not others (and thereby help establish where the problem lies within the iPhone OS) is to try and narrow down the variables.
It's a bug in the OS. It's like buying new tires, you drive down the road and they blow up and someone suggest you check your oil. Fuck the router. As I said the issue is the OS, the OS, the OS, the OS.
Battery performance on my iPhone 3G (purchased in February '09) post 3.1 update is the same as 3.0 which was a slight improvement over the previous version. I can't complain. I have BlueTooth and WiFi always on but location services off (that really sucks the battery down). I do a fair amount of browsing, calls, SMS and some Apps. Like another poster said, for what the iPhone does, the battery performance is pretty good. Prior to my iPhone, I had a Crackberry Curve and it typically lasted only a little longer than the iPhone. But then the iPhone does a lot more.
As to the WiFi issue, I have not had any issues with 3.1. It connects just the same as it did with 3.0 and everything before that. It occasionally takes an extra second or two to find my network, but no different than previous software versions. My LAN setup is:
Linksys WRT-350N (802.11N)
Network mode is mixed
WPA-2 security
Phone is set to auto-join and "ask to join other networks" is on.
I posted on this battery issue the same day the OS 3.0 software became available but was pooh poohed by a few clever arsed techno boffins who also post here. Update's still haven't improved on it.
Indeed they almost convinced me it was something i was doing wrong or over looking. On saying that i've now got used to the slight reduction in battery life, so if the outcome of this is a fix then it's a bonus. Still a great phone though.
[QUOTE=Douglas Bailey;1485847]I can't think what the problem is with the battery life. I charge my phone for about 8 hrs at night an then it will last all the way from from 7am till 11pm as Since OS 2.2, my iPhone always last at least two days and often three days (and even then it is still at around 20%) UNLESS I use it really heavily. Normal usage for me is maybe 2 hours of audio per day, hourly e-mail check, and maybe a handfull of other interactive usages (weather, wikipedia, train schedule) and one or two (short) telephone calls. Wifi and Bluetooth are naturally off (I switch them on when I need them.) And during the night the phone is in Airplane mode (if somebody really wants to call me during the night, there is always my landline).
Sure, if I have an app track me via GPS and listen to music, it might be dead in six hours.
If you have the time, you can test things in stages:
0) How long does it last in Airplane mode (or how long does take to get down by one third)?
1) How long does it last in non-3G mode?
2) 3G mode?
3) Wifi on?
4) playing music?
5) making a call?
Another thing I have noticed, is that when travelling the battery empties much faster (I put this down to constantly having to switch to a different tower and to being in low-signal areas).
Wish Apple would address the battery issues with 15" MacBook Pros that have been "upgraded" to Snow Leopard.
Oddly my new 15 inch Macbook Pro's battery life has improved since upgrading to SL. Prior to SL the battery life was way behind my wife's White 13-inch Macbook which is two year old and seemed more like my old G4 iBook. Certainly acceptable now.
It's a bug in the OS. It's like buying new tires, you drive down the road and they blow up and someone suggest you check your oil. Fuck the router. As I said the issue is the OS, the OS, the OS, the OS.
Remember when (I think it was) Mac OS X 10.4 was released and suddenly hundreds of Mac owners started getting memory errors? They, like you, blamed the OS but the fact was 10.4 had more exacting memory checking and was actually finding RAM that had been substandard and out of spec.
To correct your analogy, it would be like buying new tires, they blow up, but the actual culprit is your rims that were out of spec and incompatible with your new tires that were rigidly specced unlike your old ones.
Sometimes the suspect you're sure you've implicated isn't necessarily the culprit.
Oddly my new 15 inch Macbook Pro's battery life has improved since upgrading to SL. Prior to SL the battery life was way behind my wife's White 13-inch Macbook which is two year old and seemed more like my old G4 iBook. Certainly acceptable now.
Are you talking about a Unibody 15" or a C2D (core 2 duo) ?
The Snow Leopard battery problems are correlating to the C2D 15" Macbook Pros
Please post your wife's battery specs and model number
How much has it improved in mAh? Minutes? Hours?
I think the department/division in "charge" of the battery software / management really dropped the ball here.
Remember when (I think it was) Mac OS X 10.4 was released and suddenly hundreds of Mac owners started getting memory errors? They, like you, blamed the OS but the fact was 10.4 had more exacting memory checking and was actually finding RAM that had been substandard and out of spec.
To correct your analogy, it would be like buying new tires, they blow up, but the actual culprit is your rims that were out of spec and incompatible with your new tires that were rigidly specced unlike your old ones.
Sometimes the suspect you're sure you've implicated isn't necessarily the culprit.
Hmm, I see what you are saying but you are incorrect.
What is going on here is a closed system -
1) apple batteries
2) apple software
3) apple computer
The tire analogy
1) brand x tires
2) brand y rims
3) unknown road
a better analogy -
1) you pay a car dealer for a "performance upgrade" to your car
2) your car cuts out on you when the gas gauge says half full
3) you can now only fill the tank half way
4) car dealer says - you need to buy a new gas tank / fuel gauge
Are you talking about a Unibody 15" or a C2D (core 2 duo) ?
The Snow Leopard battery problems are correlating to the C2D 15" Macbook Pros
Though I'm not the one you directed the question at, I figured I'd chime in. I have a late '08 Unibody 15" MBP 2.4 GHz Core2Duo that seems to have improved slightly with Snow Leopard as well. Though, I have to say that the battery performance has never been all that great to begin with. My battery is the A1281 @ 50Wh
Hmm, I see what you are saying but you are incorrect.
What is going on here is a closed system -
1) apple batteries
2) apple software
3) apple computer
The tire analogy
1) brand x tires
2) brand y rims
3) unknown road
a better analogy -
1) you pay a car dealer for a "performance upgrade" to your car
2) your car cuts out on you when the gas gauge says half full
3) you can now only fill the tank half way
4) car dealer says - you need to buy a new gas tank / fuel gauge
I think in ktappe's analogy, the rims were analogous to the RAM. So, everyone doesn't necessarily have Apple memory (though I assume most do). I personally have OWC memory in my MBP.
Remember when (I think it was) Mac OS X 10.4 was released and suddenly hundreds of Mac owners started getting memory errors? They, like you, blamed the OS but the fact was 10.4 had more exacting memory checking and was actually finding RAM that had been substandard and out of spec.
To correct your analogy, it would be like buying new tires, they blow up, but the actual culprit is your rims that were out of spec and incompatible with your new tires that were rigidly specced unlike your old ones.
Sometimes the suspect you're sure you've implicated isn't necessarily the culprit.
Good call. Open-mindedness is an absolute necessity in debugging complex
I don't have battery issues in 3.1, but I do have freezes while asleep (about every other day) that could seem like a dead battery--until you reboot, anyway. Not sure if the culprit is 3.1, or a dud phone. (I just got it as a warranty swap when 3.0 permanently killed my WiFi and 3.1 didn't bring it back.)
Comments
I got the email from Apple about the battery life. I posted a couple times on their forum because I noticed that battery life was not as good with 3.1 as it was before the update. Mine was not as bad as others who posted but it was apparent. After a coupld power cycles everything seemed to smooth out.
I have noticed problems with the wifi. It will just drop, even when I'm standing next to the router. I have to turn off the wifi on the phone and back on then it's fine. Very unpredictable.
have you tried to turn off the locking? could be that it's trying to put the phone to "sleep" to save battery
Has Apple ever done anything like this in the past? I like it.
Yeah.
Apple engineers contacted me a few times for an issue with iTunes importing CDs very slowly (like less than 1.0 x). Ran a few tests and sent them the results back.
Thousands of people have noticed after updating to 3.1 they have no WiFi whatsoever, they simply cannot connect. Most times when I turn on wifi my network doesn't appear, and the few times when it does I try connect I get the message "unable to connect....". It's a widespread problem with no solution yet.
However I wish Apple would solve your problem and thousands of others (if that number is legitimate) as soon as possible, how come it is a widespread problem when they sell millions of iPhone and iPod touch?
Guess the Snow Leopard adopters with battery problems have been officially marginalized...I truly hope Apple puts some effort into helping us as much as they are doing for their Iphone Cash cow.
I am/was an apple advocate for over 20 years but this frustrating battery issue is not helping to perpetuate that.
HELLO? Apple?
See these posts on the Apple forums:
http://discussions.apple.com/thread....t=165&tstart=0
With various reports of poor iPhone battery life following the 3.1 OS update, Apple has reportedly begun asking users about its experiences and usage habits in an attempt to address the issue..
I'm an not going to even talk about my network or router anymore, as I said I find it insulting.
Which is a shame, because the only way to work out why it works for some and not others (and thereby help establish where the problem lies within the iPhone OS) is to try and narrow down the variables...
My LAN set-up is:
- iPhone 3G, with 3.1.
- 802.11g, with WPA/AES authentication (the SSID is different from default, and hidden, and the password is 15 characters.)
(it's an older Belkin access point: I did recently update firmware, because I switched from WPA/TKIP to WPA/AES and it then kept locking up. I found that there was more recent firmware that what I was running with, and that seems to have helped a lot.)
- DHCP (running on a separate server, not the access point.)
my phone is set to auto-join my home network, but I have the "Ask to join other networks" set to Off.
I do observe a delay sometimes, in the iPhone acquiring my network after unlock, but I've only had problems when the WiFi network itself had locked up (see above) or when other nearby networks have crowded out the channel I was using.
OK, fine. I was just asking a few questions. I'm sure there is something in the OS that is doing this. But I don't think it is as cut and dried as you suggest.
Oh but it is. I looking into this for about 3 hours the other night. It's very cut and dried. In 3.0 and 3.1 this is a bug, it's that bloody simple.
(of course, we're straying from the battery life issue.)
Which is a shame, because the only way to work out why it works for some and not others (and thereby help establish where the problem lies within the iPhone OS) is to try and narrow down the variables.
It's a bug in the OS. It's like buying new tires, you drive down the road and they blow up and someone suggest you check your oil. Fuck the router. As I said the issue is the OS, the OS, the OS, the OS.
Battery performance on my iPhone 3G (purchased in February '09) post 3.1 update is the same as 3.0 which was a slight improvement over the previous version. I can't complain. I have BlueTooth and WiFi always on but location services off (that really sucks the battery down). I do a fair amount of browsing, calls, SMS and some Apps. Like another poster said, for what the iPhone does, the battery performance is pretty good. Prior to my iPhone, I had a Crackberry Curve and it typically lasted only a little longer than the iPhone. But then the iPhone does a lot more.
As to the WiFi issue, I have not had any issues with 3.1. It connects just the same as it did with 3.0 and everything before that. It occasionally takes an extra second or two to find my network, but no different than previous software versions. My LAN setup is:
Linksys WRT-350N (802.11N)
Network mode is mixed
WPA-2 security
Phone is set to auto-join and "ask to join other networks" is on.
Indeed they almost convinced me it was something i was doing wrong or over looking. On saying that i've now got used to the slight reduction in battery life, so if the outcome of this is a fix then it's a bonus. Still a great phone though.
Sure, if I have an app track me via GPS and listen to music, it might be dead in six hours.
If you have the time, you can test things in stages:
0) How long does it last in Airplane mode (or how long does take to get down by one third)?
1) How long does it last in non-3G mode?
2) 3G mode?
3) Wifi on?
4) playing music?
5) making a call?
Another thing I have noticed, is that when travelling the battery empties much faster (I put this down to constantly having to switch to a different tower and to being in low-signal areas).
Wish Apple would address the battery issues with 15" MacBook Pros that have been "upgraded" to Snow Leopard.
Oddly my new 15 inch Macbook Pro's battery life has improved since upgrading to SL. Prior to SL the battery life was way behind my wife's White 13-inch Macbook which is two year old and seemed more like my old G4 iBook. Certainly acceptable now.
It's a bug in the OS. It's like buying new tires, you drive down the road and they blow up and someone suggest you check your oil. Fuck the router. As I said the issue is the OS, the OS, the OS, the OS.
Remember when (I think it was) Mac OS X 10.4 was released and suddenly hundreds of Mac owners started getting memory errors? They, like you, blamed the OS but the fact was 10.4 had more exacting memory checking and was actually finding RAM that had been substandard and out of spec.
To correct your analogy, it would be like buying new tires, they blow up, but the actual culprit is your rims that were out of spec and incompatible with your new tires that were rigidly specced unlike your old ones.
Sometimes the suspect you're sure you've implicated isn't necessarily the culprit.
Oddly my new 15 inch Macbook Pro's battery life has improved since upgrading to SL. Prior to SL the battery life was way behind my wife's White 13-inch Macbook which is two year old and seemed more like my old G4 iBook. Certainly acceptable now.
Are you talking about a Unibody 15" or a C2D (core 2 duo) ?
The Snow Leopard battery problems are correlating to the C2D 15" Macbook Pros
Please post your wife's battery specs and model number
How much has it improved in mAh? Minutes? Hours?
I think the department/division in "charge" of the battery software / management really dropped the ball here.
Thanks-
Remember when (I think it was) Mac OS X 10.4 was released and suddenly hundreds of Mac owners started getting memory errors? They, like you, blamed the OS but the fact was 10.4 had more exacting memory checking and was actually finding RAM that had been substandard and out of spec.
To correct your analogy, it would be like buying new tires, they blow up, but the actual culprit is your rims that were out of spec and incompatible with your new tires that were rigidly specced unlike your old ones.
Sometimes the suspect you're sure you've implicated isn't necessarily the culprit.
Hmm, I see what you are saying but you are incorrect.
What is going on here is a closed system -
1) apple batteries
2) apple software
3) apple computer
The tire analogy
1) brand x tires
2) brand y rims
3) unknown road
a better analogy -
1) you pay a car dealer for a "performance upgrade" to your car
2) your car cuts out on you when the gas gauge says half full
3) you can now only fill the tank half way
4) car dealer says - you need to buy a new gas tank / fuel gauge
Are you talking about a Unibody 15" or a C2D (core 2 duo) ?
The Snow Leopard battery problems are correlating to the C2D 15" Macbook Pros
Though I'm not the one you directed the question at, I figured I'd chime in. I have a late '08 Unibody 15" MBP 2.4 GHz Core2Duo that seems to have improved slightly with Snow Leopard as well. Though, I have to say that the battery performance has never been all that great to begin with. My battery is the A1281 @ 50Wh
Hmm, I see what you are saying but you are incorrect.
What is going on here is a closed system -
1) apple batteries
2) apple software
3) apple computer
The tire analogy
1) brand x tires
2) brand y rims
3) unknown road
a better analogy -
1) you pay a car dealer for a "performance upgrade" to your car
2) your car cuts out on you when the gas gauge says half full
3) you can now only fill the tank half way
4) car dealer says - you need to buy a new gas tank / fuel gauge
I think in ktappe's analogy, the rims were analogous to the RAM. So, everyone doesn't necessarily have Apple memory (though I assume most do). I personally have OWC memory in my MBP.
Remember when (I think it was) Mac OS X 10.4 was released and suddenly hundreds of Mac owners started getting memory errors? They, like you, blamed the OS but the fact was 10.4 had more exacting memory checking and was actually finding RAM that had been substandard and out of spec.
To correct your analogy, it would be like buying new tires, they blow up, but the actual culprit is your rims that were out of spec and incompatible with your new tires that were rigidly specced unlike your old ones.
Sometimes the suspect you're sure you've implicated isn't necessarily the culprit.
Good call. Open-mindedness is an absolute necessity in debugging complex
systems.