I have had this happen twice in the last week using two different watches.
First on Sunday using my Series 4 LTE, I was about 40 minutes into a run, using iSmoothRun and streaming Apple Music when the watch just shut down. I restarted it and it showed 10% battery .. I started with the battery at 100%. I rebooted again, and the battery showed 70%. The watch created a LowBatteryLog in the diagnostic logs on the phone. So I thought must be a hardware issue.
Then today, I pulled out my older Series 3 LTE, switched my Verizon service to it, and went on a run again using iSmoothRun and streaming Pandora this time. Again, about 40 minutes or so in, the watch shutdown. I turned it back on, and the battery level was 67%. But again, a LowBatteryLog entry was created.
Both times the run data was lost .. which is the cardinal sin of running watches in my mind .. guess I am going back to my Garmin Fenix 6.
Both watches are running watchOS 7 .. the Series 3 had 7.03, and 7.02 on the Series 4.
This similar scenario happed to me while using Workoutdoors too, so I don't think it is iSmoothRun causing the issue. Seems like the combination of GPS, music streaming via LTE might be causing the watch to inaccurately report the battery level.
I did open a support request with Apple.
Here is the text of the LowBatteryLog from today:
{"os_version":"Watch OS 7.0.3 (18R410)","incident_id":"B0D5E488-360C-4AD4-84A7-CA8FF190C5B7","timestamp":"2020-10-21 11:47:03.00 -0400","bug_type":"120"}
{"os_version":"Watch OS 7.0.3 (18R410)","bug_type":"120"}
Incident Identifier: 952B6259-3859-48FE-A53D-6DD95A7BD532
CrashReporter Key: fac1d3d5bb155dacadcc0c79c2ba6c956a7a70e9
Date: 2020-10-21 11:47:01 -0400
OS Version: Watch OS 7.0.3 (18R410)
runningboardd: application<com.pandora.watchapp>72-51-2540:MediaExperience.227."com.pandora.watchapp.extension"."MediaPlaybackNoSpeaker".isPlayingProcessAssertion(MediaPlayback) SystemIsActive == 255, held for 00:09:12
runningboardd: application<com.lakehorizon.ismoothrun.watchkitapp>;72-199-2298:locationd(BackgroundLocationProcessing);72-67-2299:HealthKit Background Workout(WorkoutProcessing) SystemIsActive == 255, held for 00:38:50
locationd: com.apple.locationd.CLOdometerNotifier.1299be00(streaming odometer) NoIdleSleepAssertion == 255, held for 00:38:50
locationd: com.apple.locationd.CLMotionStateOverride.13141640(ctor) NoIdleSleepAssertion == 255, held for 00:38:50
bluetoothd: com.apple.BTStack PreventUserIdleSystemSleep == 255, held for 00:40:24
mediaserverd: MediaExperience.sid:0x336f1, Watch Extension(227), 'prim'(com.pandora.watchapp.extension).isplaying NoIdleSleepAssertion == 255, held for 00:09:03
mediaserverd: com.apple.audio.VAD [vdef] AggDev 5.context.preventuseridlesleep PreventUserIdleSystemSleep == 255, held for 00:09:07
Foreground Applications: com.lakehorizon.ismoothrun.watchkitapp
Screen Brightness: 0.000000
Hardware Model: N111sAP
Awake Time: 00:45:31 (2731)
Standby Time: 01:02:13 (3733)
Partial Charge: 0
Capacity: 64
Voltage: 3655 mV
VDD_OK1: 0
VDD_OK2: (null)
First on Sunday using my Series 4 LTE, I was about 40 minutes into a run, using iSmoothRun and streaming Apple Music when the watch just shut down. I restarted it and it showed 10% battery .. I started with the battery at 100%. I rebooted again, and the battery showed 70%. The watch created a LowBatteryLog in the diagnostic logs on the phone. So I thought must be a hardware issue.
Then today, I pulled out my older Series 3 LTE, switched my Verizon service to it, and went on a run again using iSmoothRun and streaming Pandora this time. Again, about 40 minutes or so in, the watch shutdown. I turned it back on, and the battery level was 67%. But again, a LowBatteryLog entry was created.
Both times the run data was lost .. which is the cardinal sin of running watches in my mind .. guess I am going back to my Garmin Fenix 6.
Both watches are running watchOS 7 .. the Series 3 had 7.03, and 7.02 on the Series 4.
This similar scenario happed to me while using Workoutdoors too, so I don't think it is iSmoothRun causing the issue. Seems like the combination of GPS, music streaming via LTE might be causing the watch to inaccurately report the battery level.
I did open a support request with Apple.
Here is the text of the LowBatteryLog from today:
{"os_version":"Watch OS 7.0.3 (18R410)","incident_id":"B0D5E488-360C-4AD4-84A7-CA8FF190C5B7","timestamp":"2020-10-21 11:47:03.00 -0400","bug_type":"120"}
{"os_version":"Watch OS 7.0.3 (18R410)","bug_type":"120"}
Incident Identifier: 952B6259-3859-48FE-A53D-6DD95A7BD532
CrashReporter Key: fac1d3d5bb155dacadcc0c79c2ba6c956a7a70e9
Date: 2020-10-21 11:47:01 -0400
OS Version: Watch OS 7.0.3 (18R410)
runningboardd: application<com.pandora.watchapp>72-51-2540:MediaExperience.227."com.pandora.watchapp.extension"."MediaPlaybackNoSpeaker".isPlayingProcessAssertion(MediaPlayback) SystemIsActive == 255, held for 00:09:12
runningboardd: application<com.lakehorizon.ismoothrun.watchkitapp>;72-199-2298:locationd(BackgroundLocationProcessing);72-67-2299:HealthKit Background Workout(WorkoutProcessing) SystemIsActive == 255, held for 00:38:50
locationd: com.apple.locationd.CLOdometerNotifier.1299be00(streaming odometer) NoIdleSleepAssertion == 255, held for 00:38:50
locationd: com.apple.locationd.CLMotionStateOverride.13141640(ctor) NoIdleSleepAssertion == 255, held for 00:38:50
bluetoothd: com.apple.BTStack PreventUserIdleSystemSleep == 255, held for 00:40:24
mediaserverd: MediaExperience.sid:0x336f1, Watch Extension(227), 'prim'(com.pandora.watchapp.extension).isplaying NoIdleSleepAssertion == 255, held for 00:09:03
mediaserverd: com.apple.audio.VAD [vdef] AggDev 5.context.preventuseridlesleep PreventUserIdleSystemSleep == 255, held for 00:09:07
Foreground Applications: com.lakehorizon.ismoothrun.watchkitapp
Screen Brightness: 0.000000
Hardware Model: N111sAP
Awake Time: 00:45:31 (2731)
Standby Time: 01:02:13 (3733)
Partial Charge: 0
Capacity: 64
Voltage: 3655 mV
VDD_OK1: 0
VDD_OK2: (null)