Yea, I plan on keeping FD enabled after this test. I like knowing the watch is helping to provide extra safety. Noise detection is another battery drainer. I have that turned off, as I don't have a constant need to analyze questionable sound.
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.
Terrible battery life
- Thread starter Cold_Beaver
- Start date
- Sort by reaction score
Yes I have Noise disabled, Hey Siri disabled, Start Workout Reminder disabled. Nothing really worked.
Couldn’t make the watch stop draining less than 3.5% per hour. Then finally I just gave in and addressed the elephant in the room, the one everyone is trying to not recognize as the major battery drain culprit, AOD.
With that disabled I could finally see that there isn’t anything wrong with my watch and it performs just as great or better (due to the bigger battery) than a Series 4.
Couldn’t make the watch stop draining less than 3.5% per hour. Then finally I just gave in and addressed the elephant in the room, the one everyone is trying to not recognize as the major battery drain culprit, AOD.
With that disabled I could finally see that there isn’t anything wrong with my watch and it performs just as great or better (due to the bigger battery) than a Series 4.
This is the thing though people shouldn't need to be switching features off. Sadly it's come to that for some. Those still having issues I think just getting series 4 might be a better idea if you have to switch off AOD
mine I think drops about 3-3.5% an hour but for me that's fine as it will get me through all day easily. If I can take my watch off the charger at 7am and it still have 20-30% by the time I go to bed at 23.00-23:30 then it's done it's job for me.
Yes I agree. I am certainly disappointed in Series 5 because I got it for the AOD. But I went it with the expectation that I would get the same battery life as Series 4 because that is how Apple sold it. Which isn’t the case, you will end up with half of the battery life when compared to a Series 4 if you have AOD enabled. Now, Apple does says 18hours battery life and Series 5 definitely does more than 18 hours so they aren’t lying about that.
But just saying that if you prefer more battery life. Just disabling AOD will get it performing just as great as a Series 4.
This is likely why no sleep tracking was added this year as there's no way this would happen. Maybe next years we will see a big jump in battery life as it will need to for that to work. That said I like to watch my phone and watch at night no matter what the battery % is. I know not everybody likes to do this but for me that's my normal routine.
I just put my s5 on the charger at 20%. With Fall Detection temporarily turned off, and noise detection already off, I got 4:58 mixed usage and 1 day standby with my cellular version. That is the most I have seen thus far and don't think I will do better, unless I were to turn off cellular and a few other features. I don't think that is practical or prudent to do. While the s5 doesn't have the great battery life of my s3, I am happy with the results thus far.
Last edited:
This makes the most sense to me. I'd like to see someone do a detailed comparison of battery life with AOD on and off. It's a shame as that is the selling point of the 5 over the 4.
I tried with and without AOD and for me it was about 1% difference from 3% to 2% or closer to it. Not enough to turn it off.
~2% from having
-AOD off
-Cellular off
-RTW off
-Siri off
-Lowest display intensity
-Almost no background app refresh
With this setup I reached >36 hours easily.
~3%
- AOD on
- RTW off
- Cellular on
- Siri off
- Display mid intensity
- Almost no background app refresh
Anyone have any other suggestions to turn on/off please let me know so I can try it out as well.
Coming from a S2 I am ok to have just 24h of active use. I can always turn everything except the clock off if I want to extend it but defeats the purpose of the clock, in my view....
I hope Apple will continue to reduce battery use in future 6.x.x releases.
~2% from having
-AOD off
-Cellular off
-RTW off
-Siri off
-Lowest display intensity
-Almost no background app refresh
With this setup I reached >36 hours easily.
~3%
- AOD on
- RTW off
- Cellular on
- Siri off
- Display mid intensity
- Almost no background app refresh
Anyone have any other suggestions to turn on/off please let me know so I can try it out as well.
Coming from a S2 I am ok to have just 24h of active use. I can always turn everything except the clock off if I want to extend it but defeats the purpose of the clock, in my view....
I hope Apple will continue to reduce battery use in future 6.x.x releases.
Watch finishes day on 16% with 16 hours standby and 8 hours usage. Least it lasts me all day now
I have background app refresh enabled for almost all apps. Display low intensity. Siri is on only raise to speak. Cellular is on. Raise to Wake is on.
Disabling AOD made a huge difference for me. At this point of the day I got 20% more battery and the gap only gets bigger as the day goes on. I think in the end it is about 40% more battery life when you let the watch run out of battery.
[automerge]1573515686[/automerge]
For the curious. I am at 10 hours standby. And it is at 75% at the moment.
Check the diagnostic logs or contact Apple support for them to check them for you. It might be a process taking a lot of cpu usage.
As an example. My watch was draining battery a lot after pairing. I checked the diagnostic logs and found that Reminders was taking a lot of CPU. I went ahead and opened the reminders app and in fact it wasn’t syncing but after waiting for it to download all my tasks everything got fixed.
Last edited:
My biggest issue with AOD seems to come from the display brightness. For some reason when it goes into standby the watch gets brighter than when I wake it up. If I use my palm to put the watch in standby then the brightness lowers like it should. Seems to be a bug which hopefully they fix in the future.
After unpairing/repairing the watch on Friday, as of yesterday my watch was back to its normal 12-15% drain per hour.
Looking at my logs, I received a trustedpeershelper.cup_resource file this morning where my CPU had run for 92s at 98% average cpu usage.
I can't for the life of me figure out what app is causing the issue. Anyone have an idea of how to read these errors? I took a snippet of the code and posted below:
Command: TrustedPeersHelper
Path: /System/Library/Frameworks/Security.framework/XPCServices/TrustedPeersHelper.xpc/TrustedPeersHelper
Identifier: com.apple.TrustedPeersHelper
Version: 1.0 (1)
PID: 317
Event: cpu usage
Action taken: none
CPU: 90 seconds cpu time over 92 seconds (98% cpu average), exceeding limit of 50% cpu over 180 seconds
CPU limit: 90s
Limit duration: 180s
CPU used: 90s
CPU duration: 92s
Duration: 91.94s
Duration Sampled: 10.21s
Steps: 13
Hardware model: Watch4,2
Active cpus: 2
Heaviest stack for the target process:
13 ??? (libdispatch.dylib + 91600) [0x204c45d0]
13 ??? (libdispatch.dylib + 53472) [0x204bb0e0]
13 ??? (libdispatch.dylib + 50468) [0x204ba524]
13 ??? (libdispatch.dylib + 121344) [0x204cba00]
13 ??? (libdispatch.dylib + 50468) [0x204ba524]
13 ??? (libdispatch.dylib + 118384) [0x204cae70]
13 ??? (libdispatch.dylib + 26216) [0x204b4668]
13 ??? (libxpc.dylib + 61244) [0x2072cf3c]
13 ??? (libxpc.dylib + 60384) [0x2072cbe0]
13 ??? (Foundation + 2331552) [0x216253a0]
13 ??? (Foundation + 353372) [0x2144245c]
13 ??? (Foundation + 2331212) [0x2162524c]
13 ??? (CoreFoundation + 17712) [0x209be530]
13 ??? (CoreFoundation + 1247792) [0x20aeaa30]
13 ??? (TrustedPeersHelper + 1048032) [0x2aa7de0]
13 ??? (TrustedPeersHelper + 1046384) [0x2aa7770]
13 ??? (libswiftDispatch.dylib + 49032) [0x4613df88]
13 ??? (libswiftDispatch.dylib + 47416) [0x4613d938]
13 ??? (libswiftDispatch.dylib + 74184) [0x461441c8]
13 ??? (libswiftDispatch.dylib + 49228) [0x4613e04c]
13 ??? (libdispatch.dylib + 77496) [0x204c0eb8]
13 ??? (libdispatch.dylib + 26024) [0x204b45a8]
13 ??? (libswiftDispatch.dylib + 23312) [0x46137b10]
13 ??? (libswiftDispatch.dylib + 86456) [0x461471b8]
13 ??? (libswiftDispatch.dylib + 85488) [0x46146df0]
13 ??? (libswiftDispatch.dylib + 86068) [0x46147034]
13 ??? (libswiftDispatch.dylib + 47788) [0x4613daac]
13 ??? (libswiftDispatch.dylib + 86028) [0x4614700c]
13 ??? (TrustedPeersHelper + 1087164) [0x2ab16bc]
13 ??? (TrustedPeersHelper + 1073860) [0x2aae2c4]
13 ??? (TrustedPeersHelper + 1086284) [0x2ab134c]
13 ??? (TrustedPeersHelper + 1073828) [0x2aae2a4]
13 ??? (TrustedPeersHelper + 112728) [0x29c3858]
13 ??? (TrustedPeersHelper + 588744) [0x2a37bc8]
13 ??? (CoreData + 38036) [0x245fc494]
13 ??? (libdispatch.dylib + 77496) [0x204c0eb8]
13 ??? (libdispatch.dylib + 26024) [0x204b45a8]
13 ??? (CoreData + 1169944) [0x24710a18]
13 ??? (TrustedPeersHelper + 591816) [0x2a387c8]
13 ??? (TrustedPeersHelper + 948172) [0x2a8f7cc]
13 ??? (TrustedPeersHelper + 591248) [0x2a38590]
13 ??? (TrustedPeersHelper + 962876) [0x2a9313c]
13 ??? (TrustedPeersHelper + 959400) [0x2a923a8]
13 ??? (TrustedPeersHelper + 596524) [0x2a39a2c]
13 ??? (TrustedPeers + 35356) [0x44161a1c]
13 ??? (TrustedPeers + 36096) [0x44161d00]
13 ??? (TrustedPeers + 104552) [0x44172868]
13 ??? (TrustedPeers + 106540) [0x4417302c]
13 ??? (TrustedPeers + 100488) [0x44171888]
13 ??? (SecurityFoundation + 15728) [0x360dcd70]
13 ??? (Security + 660796) [0x2174653c]
13 ??? (Security + 660308) [0x21746354]
13 ??? (Security + 659496) [0x21746028]
13 ??? (Security + 606976) [0x21739300]
13 ??? (libcorecrypto.dylib + 145416) [0x20461808]
13 ??? (libcorecrypto.dylib + 288288) [0x20484620]
8 ??? (libcorecrypto.dylib + 143612) [0x204610fc]
2 ??? (libcorecrypto.dylib + 120156) [0x2045b55c]
2 ??? (libcorecrypto.dylib + 118316) [0x2045ae2c]
2 ??? (libcorecrypto.dylib + 177296) [0x20469490]
1 ??? (libcorecrypto.dylib + 158716) [0x20464bfc]
Powerstats for: TrustedPeersHelper (TrustedPeersHelper) [317]
UUID: A9C692DD-727D-390D-A5B5-7C0495F15B51
Path: /System/Library/Frameworks/Security.framework/XPCServices/TrustedPeersHelper.xpc/TrustedPeersHelper
Architecture: arm
Footprint: 46.45 MB
Start time: 2019-11-12 08:28:38 -0500
End time: 2019-11-12 08:28:49 -0500
Num samples: 13 (100%)
CPU Time: 10.064s
Primary state: 13 samples Non-Frontmost App, Non-Suppressed, User mode, Effective Thread QoS User Initiated, Requested Thread QoS User Initiated, Override Thread QoS Unspecified
User Activity: 0 samples Idle, 0 samples Active, 13 samples Unknown
Power Source: 0 samples on Battery, 0 samples on AC, 13 samples Unknown
Looking at my logs, I received a trustedpeershelper.cup_resource file this morning where my CPU had run for 92s at 98% average cpu usage.
I can't for the life of me figure out what app is causing the issue. Anyone have an idea of how to read these errors? I took a snippet of the code and posted below:
Command: TrustedPeersHelper
Path: /System/Library/Frameworks/Security.framework/XPCServices/TrustedPeersHelper.xpc/TrustedPeersHelper
Identifier: com.apple.TrustedPeersHelper
Version: 1.0 (1)
PID: 317
Event: cpu usage
Action taken: none
CPU: 90 seconds cpu time over 92 seconds (98% cpu average), exceeding limit of 50% cpu over 180 seconds
CPU limit: 90s
Limit duration: 180s
CPU used: 90s
CPU duration: 92s
Duration: 91.94s
Duration Sampled: 10.21s
Steps: 13
Hardware model: Watch4,2
Active cpus: 2
Heaviest stack for the target process:
13 ??? (libdispatch.dylib + 91600) [0x204c45d0]
13 ??? (libdispatch.dylib + 53472) [0x204bb0e0]
13 ??? (libdispatch.dylib + 50468) [0x204ba524]
13 ??? (libdispatch.dylib + 121344) [0x204cba00]
13 ??? (libdispatch.dylib + 50468) [0x204ba524]
13 ??? (libdispatch.dylib + 118384) [0x204cae70]
13 ??? (libdispatch.dylib + 26216) [0x204b4668]
13 ??? (libxpc.dylib + 61244) [0x2072cf3c]
13 ??? (libxpc.dylib + 60384) [0x2072cbe0]
13 ??? (Foundation + 2331552) [0x216253a0]
13 ??? (Foundation + 353372) [0x2144245c]
13 ??? (Foundation + 2331212) [0x2162524c]
13 ??? (CoreFoundation + 17712) [0x209be530]
13 ??? (CoreFoundation + 1247792) [0x20aeaa30]
13 ??? (TrustedPeersHelper + 1048032) [0x2aa7de0]
13 ??? (TrustedPeersHelper + 1046384) [0x2aa7770]
13 ??? (libswiftDispatch.dylib + 49032) [0x4613df88]
13 ??? (libswiftDispatch.dylib + 47416) [0x4613d938]
13 ??? (libswiftDispatch.dylib + 74184) [0x461441c8]
13 ??? (libswiftDispatch.dylib + 49228) [0x4613e04c]
13 ??? (libdispatch.dylib + 77496) [0x204c0eb8]
13 ??? (libdispatch.dylib + 26024) [0x204b45a8]
13 ??? (libswiftDispatch.dylib + 23312) [0x46137b10]
13 ??? (libswiftDispatch.dylib + 86456) [0x461471b8]
13 ??? (libswiftDispatch.dylib + 85488) [0x46146df0]
13 ??? (libswiftDispatch.dylib + 86068) [0x46147034]
13 ??? (libswiftDispatch.dylib + 47788) [0x4613daac]
13 ??? (libswiftDispatch.dylib + 86028) [0x4614700c]
13 ??? (TrustedPeersHelper + 1087164) [0x2ab16bc]
13 ??? (TrustedPeersHelper + 1073860) [0x2aae2c4]
13 ??? (TrustedPeersHelper + 1086284) [0x2ab134c]
13 ??? (TrustedPeersHelper + 1073828) [0x2aae2a4]
13 ??? (TrustedPeersHelper + 112728) [0x29c3858]
13 ??? (TrustedPeersHelper + 588744) [0x2a37bc8]
13 ??? (CoreData + 38036) [0x245fc494]
13 ??? (libdispatch.dylib + 77496) [0x204c0eb8]
13 ??? (libdispatch.dylib + 26024) [0x204b45a8]
13 ??? (CoreData + 1169944) [0x24710a18]
13 ??? (TrustedPeersHelper + 591816) [0x2a387c8]
13 ??? (TrustedPeersHelper + 948172) [0x2a8f7cc]
13 ??? (TrustedPeersHelper + 591248) [0x2a38590]
13 ??? (TrustedPeersHelper + 962876) [0x2a9313c]
13 ??? (TrustedPeersHelper + 959400) [0x2a923a8]
13 ??? (TrustedPeersHelper + 596524) [0x2a39a2c]
13 ??? (TrustedPeers + 35356) [0x44161a1c]
13 ??? (TrustedPeers + 36096) [0x44161d00]
13 ??? (TrustedPeers + 104552) [0x44172868]
13 ??? (TrustedPeers + 106540) [0x4417302c]
13 ??? (TrustedPeers + 100488) [0x44171888]
13 ??? (SecurityFoundation + 15728) [0x360dcd70]
13 ??? (Security + 660796) [0x2174653c]
13 ??? (Security + 660308) [0x21746354]
13 ??? (Security + 659496) [0x21746028]
13 ??? (Security + 606976) [0x21739300]
13 ??? (libcorecrypto.dylib + 145416) [0x20461808]
13 ??? (libcorecrypto.dylib + 288288) [0x20484620]
8 ??? (libcorecrypto.dylib + 143612) [0x204610fc]
2 ??? (libcorecrypto.dylib + 120156) [0x2045b55c]
2 ??? (libcorecrypto.dylib + 118316) [0x2045ae2c]
2 ??? (libcorecrypto.dylib + 177296) [0x20469490]
1 ??? (libcorecrypto.dylib + 158716) [0x20464bfc]
Powerstats for: TrustedPeersHelper (TrustedPeersHelper) [317]
UUID: A9C692DD-727D-390D-A5B5-7C0495F15B51
Path: /System/Library/Frameworks/Security.framework/XPCServices/TrustedPeersHelper.xpc/TrustedPeersHelper
Architecture: arm
Footprint: 46.45 MB
Start time: 2019-11-12 08:28:38 -0500
End time: 2019-11-12 08:28:49 -0500
Num samples: 13 (100%)
CPU Time: 10.064s
Primary state: 13 samples Non-Frontmost App, Non-Suppressed, User mode, Effective Thread QoS User Initiated, Requested Thread QoS User Initiated, Override Thread QoS Unspecified
User Activity: 0 samples Idle, 0 samples Active, 13 samples Unknown
Power Source: 0 samples on Battery, 0 samples on AC, 13 samples Unknown
I know when I had drain it was down to apple podcast app. reinstalled and it'd fine but I got a replacement watch. seems to be your best bet?
That seems to be related to an issue with your iCloud Keychain. Try using a different AppleID and see if you still have the issue. That is just only to isolate the issue of course. I know it isn’t viable to permanently change your AppleID.
Thanks for the input. I don't use the podcast app, so I know it can't be the issue.
I tried to shut off my iCloud Keychain on my iPhone and after putting in my appleid password, the toggle switch turned back to on. This is odd in itself. Maybe this is part of the issue. . .
My series 2 (38mm) which is almost 3 years old now has the same battery life as always on 6.1. I end the day with 55-65% depending on if I do any workouts.
My October 2017 42mm LTE Series 3 is also doing very well on 6.1 - virtually no difference to prior watchOS versions and still up to 1,5 days, depending on usage.