Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Third party apps can't drain battery in background.
watchOS is VERY conservative with 3rd party background activity (except workouts).
It's a side effect.
 
  • Haha
Reactions: kristof461
I’ve been having similar issues with my Watch series 4 for two and a half months now. Like some others noted here, my issue seems to be playlists downloaded from my phone to my watch…. As soon as I enable it my battery drain starts occurring. I updated to watch OS 10.1.1 last night after being in constant communication with Apple and this issue is STILL not fixed.

My watch battery was just replaced by Apple a month ago so it’s 100% capacity.

This AM I had it charged at 100% two hours ago and it’s down to 60%
 
Tim? Is that you?

No, I am a watchOS app developer and I know how the OS handles background activity.
An app has just a limited time per day do have some background activity.
If an app eats to much CPU or RAM, or storage access, it's killed.
I have Watchla, it consumes nothing on my watch (that's why you have to run it manually, it stays a very limited time in bg).
Coincidence is not consequence.
Only apple system services (music, podcast sync, localization, health sensor, data sync ...) can eat battery in background, 3rd party apps have a very, very limited background activity budget

You can laugh, but it's better to read ...


Budget your app’s background time

The delivery of background tasks and the allocation of background execution time are completely up to the system. When making a watchOS app, schedule background updates based on these limits, and prepare for background task throttling. Understanding the limits helps you better design your app’s background update strategy.

To prevent background tasks from using too many system resources or excessively draining the battery, watchOS controls how often and how long background tasks can run. When scheduling background tasks, the system may:

  • Give each app an individual allotment of background execution time. The system only triggers an app’s background tasks when it has time remaining in its budget.
  • Throttle background tasks when system resources are tight. Even if individual apps have the budget for tasks, the system doesn’t trigger background tasks when the device’s battery is low or the system conditions are poor.
  • Throttle background execution when the user is performing high-priority activities, such as exercising or navigating.
 
Last edited:
No, I am a watchOS app developer and I know how the OS handles background activity.
An app has just a limited time per day do have some background activity.
If an app eats to much CPU or RAM, or storage access, it's killed.
I have Watchla, it consumes nothing on my watch (that's why you have to run it manually, it stays a very limited time in bg).
Coincidence is not consequence.
Only apple system services (music, podcast sync, localization, health sensor, data sync ...) can eat battery in background, 3rd party apps have a very, very limited background activity budget

You can laugh, but it's better to read ...


Budget your app’s background time

The delivery of background tasks and the allocation of background execution time are completely up to the system. When making a watchOS app, schedule background updates based on these limits, and prepare for background task throttling. Understanding the limits helps you better design your app’s background update strategy.

To prevent background tasks from using too many system resources or excessively draining the battery, watchOS controls how often and how long background tasks can run. When scheduling background tasks, the system may:

  • Give each app an individual allotment of background execution time. The system only triggers an app’s background tasks when it has time remaining in its budget.
  • Throttle background tasks when system resources are tight. Even if individual apps have the budget for tasks, the system doesn’t trigger background tasks when the device’s battery is low or the system conditions are poor.
  • Throttle background execution when the user is performing high-priority activities, such as exercising or navigating.
We all know that every consumer read sites for developer. But OK. So how you describe fact that just after I installed Watchla my battery started to drop % way more faster? I uninstall it and still draining is visible. I was at home all the time. Few minutes ago I back from 5km run. It took 18% while previously it was 12% (same conditions cellular and listening to music). Beside you say about limit. OK but there is no clear info what it means. Maybe 3 party apps are limited but if they are buggy or watchOS is buggy and you connect it with 3 party app even with a limit it takes so many %.
Today I also added my cards to Apple Pay. Don't say thet it is still working background. If so it is aboiuletly unacceptable.
That's so stupid that Apple doesn't want to let us know which app consume battery the most. I would like to see at least top 3. I would help us to know what is going on.
 
We all know that every consumer read sites for developer. But OK. So how you describe fact that just after I installed Watchla my battery started to drop % way more faster? I uninstall it and still draining is visible….
When you don’t know, it’s better to avoid trolling people who know …
You say that after uninstalling watchla, battery continues to drop, it’s another proof that the battery drain doesn’t come from bad 3rd party apps.
As I was saying before you laugh at me, it’s a side effect or a coincidence.
 
  • Like
Reactions: zecanard
When you don’t know, it’s better to avoid trolling people who know …
You say that after uninstalling watchla, battery continues to drop, it’s another proof that the battery drain doesn’t come from bad 3rd party apps.
As I was saying before you laugh at me, it’s a side effect or a coincidence.
Ok so you read only a part. Started after installing Watchla. How about that?
And you still say about side effect but no especially info. At the end you have no idea what’s going on. If it is a side effect it is a still third party app bug. Even if it is not a clear background activity it actives something else.
 
I am not Apple developer, I am app developer and I know what an app can do and what it can’t.
I don’t know what’s causing your problem, but it’s on Apple side, not on apps side
 
  • Like
Reactions: zecanard
I am not Apple developer, I am app developer and I know what an app can do and what it can’t.
I don’t know what’s causing your problem, but it’s on Apple side, not on apps side
You say that it is not an app. So why you said I quote “it is side effect”. So if I punch you in your face and you will say that your face is red and hurts i will tell you that it is not because of a punch. It is just side effect.
I made few tests yesterday and today. Every time third party app drains battery. Maybe not every app but people report that moby faces is also buggy. Maybe both of them trigger something like Apple’s location service etc. I don’t say no. But still it looks like even installing third party app can trigger something. It means watchOS 10 still has an issue with a third party app. No matter what exactly is happening while draining process is caused/triggered by third party app. That’s what I see. I understand your point you has to understand results if my tests. If we compare them we can ask Apple what is going on but they won’t reply. So I understand people who try to avoid third party app on watchOS 10
 
Last edited:
Third party apps can't drain battery in background.
watchOS is VERY conservative with 3rd party background activity (except workouts).
It's a side effect.

On the iPhone it's supposed to be that way too. Yet it isn't. Way too often, badly programmed apps can escape the background management and have a negative impact on the battery. I assume Apple just isn't able to control all apps properly 100% of the time. Some still escape the mechanism - willingly or not.

Who tells us there isn't the same issue on the watch too?
 
On the iPhone it's supposed to be that way too. Yet it isn't. Way too often, badly programmed apps can escape the background management and have a negative impact on the battery. I assume Apple just isn't able to control all apps properly 100% of the time. Some still escape the mechanism - willingly or not.

Who tells us there isn't the same issue on the watch too?
You could disable background activity but meta apps are still working background
Anyway. Limited background activity on watch could be something different. I appreciate his knowledge. But. He said “side effect”. No one knows what this or that app can trigger. And yes maybe whole draining story is all about broken apple’a service. Like location. App uses it once but a bug make it as a constant process even if uninstall app. Maybe third party developers can’t do anything about that. Ok. Got it. Anyway if you don’t want draining you don’t want to install third party app. For simple customer like me it doesn’t matter if it a third party app or Apple system. I am looking for solution at that’s what I found. That’s it.
 
  • Like
Reactions: ManuCH
On the iPhone it's supposed to be that way too. Yet it isn't. Way too often, badly programmed apps can escape the background management and have a negative impact on the battery. I assume Apple just isn't able to control all apps properly 100% of the time. Some still escape the mechanism - willingly or not.

Who tells us there isn't the same issue on the watch too?
It’s very different on iPhone
Background activity is incredibly free compared to watch OS
watchOS is very, very restrictive.
The API doesn’t allow developers to have long lasting or frequent activities.
It’s impossible.
The only exception is for workout
 
  • Like
Reactions: zecanard
You say that it is not an app. So why you said I quote “it is side effect”. So if I punch you in your face and you will say that your face is red and hurts i will tell you that it is not because of a punch. It is just side effect.
I made few tests yesterday and today. Every time third party app drains battery. Maybe not every app but people report that moby faces is also buggy. Maybe both of them trigger something like Apple’s location service etc. I don’t say no. But still it looks like even installing third party app can trigger something. It means watchOS 10 still has an issue with a third party app. No matter what exactly is happening while draining process is caused/triggered by third party app. That’s what I see. I understand your point you has to understand results if my tests. If we compare them we can ask Apple what is going on but they won’t reply. So I understand people who try to avoid third party app on watchOS 10
Most people have lot 3rd party apps and absolutely no battery issue (3 watches at home without any problem).
Some people have no 3rd party app and battery drain.
So what’s your conclusion ?
 
  • Like
Reactions: zecanard
It’s very different on iPhone
Background activity is incredibly free compared to watch OS
watchOS is very, very restrictive.
The API doesn’t allow developers to have long lasting or frequent activities.
It’s impossible.
The only exception is for workout

Got it, thank you! At that point, I really think it's the native apps creating issues. For example, my battery consumption decreased significantly once I changed my weather complications to use a static location instead of geolocating itself. It wasn't like that in watchOS 9.
 
Most people have lot 3rd party apps and absolutely no battery issue (3 watches at home without any problem).
Some people have no 3rd party app and battery drain.
So what’s your conclusion ?
Check apple community. Lot of people complain about third party app. Especially moby app. What about that? Oh I know. Nothing because you have no idea what is happening. You didn't test it. You will say about restricted background activity but what if watchOS 10 has buggy system and this restriction doesn't work. Huh? I did few test and you can read about it here but probably you don't want to. You really don't want to admit or understand. Does Apple pay you for saying stuff like this? Bug sometimes happens sometimes not. Sure. But if I checked this back and forth and every time I see more draining after third party install...well I know that something is wrong. Maybe this is bluetooth (watchla uses bluetooth) maybe something different.
 
I respect his developing knowledge. But he still can't be sure how this or that app affects on apple's service.
Especially that (I've already told it few times) he mentioned about "side effects". What does he mean?
Anyway. Let's take a look at my today's battery. Don't care about this bigger drop. It was a workout (running without iPhone and listening to music thought LTE). Still this workout took more % than before. It took 20% while it should be 12-13%. Anyway. Earlier today battery started to drain faster after watchla installation process. I delete it but nothing happened. Then I started my workout. As mentioned bigger drop. But after that draining was better than before. Strange. I know what @rbart will say. It is a clear evidence that it is not Watchla. OK. So why it was draining faster earlier (same home same wifi etc.) and what really causes all of our drainings? As I said. Even if it is not Tesla per se it still maybe triggered something. Until it is not clear I will stay without third party app. Especially that they are fewer and fewer.
 

Attachments

  • IMG_0003.jpeg
    IMG_0003.jpeg
    336.7 KB · Views: 61
I respect his developing knowledge. But he still can't be sure how this or that app affects on apple's service.
Especially that (I've already told it few times) he mentioned about "side effects". What does he mean?
Anyway. Let's take a look at my today's battery. Don't care about this bigger drop. It was a workout (running without iPhone and listening to music thought LTE). Still this workout took more % than before. It took 20% while it should be 12-13%. Anyway. Earlier today battery started to drain faster after watchla installation process. I delete it but nothing happened. Then I started my workout. As mentioned bigger drop. But after that draining was better than before. Strange. I know what @rbart will say. It is a clear evidence that it is not Watchla. OK. So why it was draining faster earlier (same home same wifi etc.) and what really causes all of our drainings? As I said. Even if it is not Tesla per se it still maybe triggered something. Until it is not clear I will stay without third party app. Especially that they are fewer and fewer.
Have you tried hard reset by press-hold the digital crown and home button until the watch restart?
 
Still this workout took more % than before. It took 20% while it should be 12-13%.

Anything that catches the eye when you look at cellular data consumption?

I am not convinced about the theory that 3rd party apps can not drain the battery too much. Not that I have an issue with any of them, but clearly Overcast can do a lot of stuff in the background, e.g. download large files. Something I am happy with.
 
  • Like
Reactions: kristof461
Check apple community. Lot of people complain about third party app. Especially moby app. What about that? Oh I know. Nothing because you have no idea what is happening. You didn't test it. You will say about restricted background activity but what if watchOS 10 has buggy system and this restriction doesn't work. Huh? I did few test and you can read about it here but probably you don't want to. You really don't want to admit or understand. Does Apple pay you for saying stuff like this? Bug sometimes happens sometimes not. Sure. But if I checked this back and forth and every time I see more draining after third party install...well I know that something is wrong. Maybe this is bluetooth (watchla uses bluetooth) maybe something different.
Ok, so I say since the beginning that 3rd party apps have no responsibility in excessive battery drain because the problem is in the OS (iOS and/or watchOS) and I am paid by Apple ????? :🤣🤣🤣😂😅
Well ...
It explains a lot :rolleyes:
 
  • Like
Reactions: zecanard
Ok, so I say since the beginning that 3rd party apps have no responsibility in excessive battery drain because the problem is in the OS (iOS and/or watchOS) and I am paid by Apple ????? :🤣🤣🤣😂😅
Well ...
It explains a lot :rolleyes:
You really can't explain one thing you said. "Side effects". You told that. Not me. So let's tell us more about that master. Oh you won't do that cause you don't know. That's the issue. I don't care if 3rd party app triggers some apple's process which is working background all the time even when 3rd party app is uninstalled or not. I see results of my tests. For standard customers it doesn't matter. They care about battery life. That's it. If you have problem with that you and other app developers should write call apple first to talk about watchOS 10. Without that I have absolutely no reason to believe in apple's theory about restricted background activity because it wouldn't be a first time when apple does something different they told previously. Do you have any evidence that Apple didn't do anything wrong in this case with watchOS 10?
Beside. Once you told us that iOS is completely different story but now you are talking about iOS " 3rd party apps have no responsibility in excessive battery drain because the problem is in the OS (iOS and/or watchOS)".
The more you talk the less things are right.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.