Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

honglong1976

macrumors 68000
Original poster
Jul 12, 2008
1,680
1,135
UK
I had a space grey series 0 on 3.1.1. I part ex for a SS series 0 but the latest firmware is 3.1

Anyone else notice the battery life is better with 3.1.1?

I used to charge and wake up with 97-99% battery life. Now I have 90%.

Has anyone used 3.1.3? Is the battery even better than 3.1.1?

Thanks
 
You might just need to reset it (turn off and then back on). The percent meter might not be calibrated. I have zero issues with 3.1.1 on my Series 0. Its possible you need to unpair and repair too.
 
38mm series 2 here. I only installed 3.1.3 last night is it is too early to draw definite conclusions, but for me battery life for an overnight use seems similar to 3.1 in the use case you describe. That is slightly above 90% battery when I wake up. Never used 3.1.1 though as it has already been removed by Apple when I got the watch.
 
still no native sleep tracking though :( thankfully there is autosleep

Yep that's a shame but I am not holding my breath for Apple to implement it on the current hardware.

I'll have to wait another few days to see if it was a once-of issue, but based on last night's data Autosleep actually got messed-up for me after upgrading to 3.1.3.

With the same "sensitivity level" which was working for me before it says I only slept 2h56m last night whereas I am sure I slept at least 6-7 hours. If I move the sensitivity slider to the right I can get figures which seems more reasonable for last night, but then for all the previous nights it is clearly over-reporting my sleep-time and ignoring occurrences where I woke-up or even got up during the night.
 
Yep that's a shame but I am not holding my breath for Apple to implement it on the current hardware.

I'll have to wait another few days to see if it was a once-of issue, but based on last night's data Autosleep actually got messed-up for me after upgrading to 3.1.3.

With the same "sensitivity level" which was working for me before it says I only slept 2h56m last night whereas I am sure I slept at least 6-7 hours. If I move the sensitivity slider to the right I can get figures which seems more reasonable for last night, but then for all the previous nights it is clearly over-reporting my sleep-time and ignoring occurrences where I woke-up or even got up during the night.
have you reported to the dev?

If anything autosleep shows that sleep tracking is possible with any of the Apple Watch models and all the data is in healthkit!
 
have you reported to the dev?

If anything autosleep shows that sleep tracking is possible with any of the Apple Watch models and all the data is in healthkit!

I'm thinking I'll wait to have a second night worth of data before contacting the dev - it would be a strange coincidence but could be that my sleep was unusually agitated last night.

And yes it is technically possible (though to make it mainstream battery life is a bit short - it would be better if the watch could last a few more days). But between being technically possible and being the best marketing decision there can be a gap and I am afraid Phil Schiller has is own opinion on this and will be the one making the call.
 
With the same "sensitivity level" which was working for me before it says I only slept 2h56m last night whereas I am sure I slept at least 6-7 hours. If I move the sensitivity slider to the right I can get figures which seems more reasonable for last night, but then for all the previous nights it is clearly over-reporting my sleep-time and ignoring occurrences where I woke-up or even got up during the night.

Did you try to change this setting (picture). There was a extra setting for 3.1.1. Maybe this setting should be off with 3.1.3?

http://autosleep.tantsissa.com/tips#TOC-Watch-OS-3.1.1

600335-7a659157ed14dcc8512e47acd292fba9.jpg
 

Attachments

  • AlternateSensivitity.jpg
    AlternateSensivitity.jpg
    21.8 KB · Views: 186
I can not say my watch used more or less, about the same.

I was somewhat shocked at the amount of time for the update to be downloaded to my phone and installed in the watch. Why so slow when a iPhone updates so quickly. Just the download time was really slow.
 
You can do it from Wizard. No need to re install.

Sorry I might be missing something obvious, but how do you kick-off the wizzard without reinstalling the app?

All the options I can find are in the Tweak tab but this does not cover the setting above.
 
Do you have Autosleep 2.0? It's there on the front page. Down, left, above text "recharge".

600357-6d661ac91e49d703ff72f1215d1fb132.jpg
 

Attachments

  • 24HourHome.jpg
    24HourHome.jpg
    17.2 KB · Views: 150
  • Like
Reactions: bob24
I can not say my watch used more or less, about the same.

I was somewhat shocked at the amount of time for the update to be downloaded to my phone and installed in the watch. Why so slow when a iPhone updates so quickly. Just the download time was really slow.

Well considering the speed and size of the CPU, GPU, storage device and RAM are much less then that in an iPhone, and that its downloading the update to the iPhone then transferring it to the Watch are all major contributors.
 
Do you have Autosleep 2.0? It's there on the front page. Down, left, above text "recharge".

600357-6d661ac91e49d703ff72f1215d1fb132.jpg

So I feel stupid but I was indeed being blind! For some reason I didn't see the button but it is there.

Unfortunately doesn't seem to fix my problem though. It changes the sensitivity range, bit for I still can't find one sensitivity level which gives correct results both for last night (first night on watchOS 3.1.3) and for the previous ones.
I'll see tomorrow whether it was a once off issue and contact the developer if it is recurring.
 
Well considering the speed and size of the CPU, GPU, storage device and RAM are much less then that in an iPhone, and that its downloading the update to the iPhone then transferring it to the Watch are all major contributors.

I understand that but when it takes like 30 minutes for the update to just download to my iPhone on my high speed WiFi, seems slow to me. I do understand that it will be slow to actually do the update.
 
  • Like
Reactions: bob24
This is only preliminary feedback but on battery life after one day of use 3.1.3 did slightly better than 3.1.

My usage pattern is to charge the watch before going to bed, wear it at night and during the day, and charge it again the next evening.

With 3.1 I was usually somewhere between 45-55% before charging the watch again. Today with 3.1.3 I am at 59%.

It it just one day and as part the update the watch was restarted, so I wouldn't draw any definite conclusion out of this.
 
Last edited:
  • Like
Reactions: 44267547
The is only preliminary feedback on battery life after one day of use is that 3.1.3 did slightly better than 3.1.

My usage pattern is to charge the watch before going to bed, wear it at night and during the day, and charge it again the next evening.

With 3.1 I was usually somewhere between 45-55% before charging the watch again. Today with 3.1.3 I am at 59%.

It it just one day and as part the update the watch was restarted, so I wouldn't draw any definite conclusion out of this.

Still an increase is positive news. Curious to see where this leads for others reported battery results.
 
My feedback after 3 days ruining 3.1.3 on a series 2: battery life is definitely not worse and most likely slightly improved. But in any case there is no massive difference.
 
I'm a medium user and my watch still has yet to move from 100%. It's 11:52am, and I put it on at 7:50 am. Much better than it was before the update.
 

Attachments

  • IMG_2120.JPG
    IMG_2120.JPG
    955.8 KB · Views: 180
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.