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.
Siri Watchface
- Thread starter Fayette3001
- Start date
- Sort by reaction score
I believe that is common as it is constantly updating not to mention listening for your voice etc.
Yes, and a lot of times, those complication faces use a lot of battery as well.
No. Well designed complication would use a timeline. Like calendar app complication for example. It would create a timeline of events for its complication and submit it to the OS. Then OS will update that complication with data from that timeline at specific point in time. The app might do a background refresh every now and then and either change or extend that timeline. Background tasks are budgeted by OS very strictly. So if you have stock Calendar complication for example it wont drain your battery unless of course your calendar is changing like 100-1000s times a day.
Siri watchface would be different, like BasicGreatGuy said, it pulls data live from many data sources so it would use connectivity and this will drain battery from Wi-Fi, Bluetooth or Cellular radio use not to mention if you actually use Siri itself which does not do on-device processing AFAIK and has to send and receive data in order to work.
TLDR; well designed complications should have very little if any effect on Watch battery life.
Can I just check something.....
Reading this thread about battery drain due to a particular complication, if that complication was part of one of “my faces” but NOT the ‘active’ face, does it still drain the battery ?
Reading this thread about battery drain due to a particular complication, if that complication was part of one of “my faces” but NOT the ‘active’ face, does it still drain the battery ?
Nope
When a face is defined but not active, none of its data (Siri face) and its complication(s) is / are refreshed.
I think they get initialized when Watch starts and stay in memory (otherwise swiping from one to another would be dead slow) tho I have no idea what their memory footprint really is. It probably isnt that much to matter but I only keep those Watch faces that I need and remove all the rest.
Yes you are right, they are initialized, and each defined complication as well, with a placeholder template that is provided by its application. But the app does not need to be launched to provide this sample template.
So the memory used is probably a matter of few Kb IMHO.