Still awaiting on my Apple Watch but could someone explain to me why you would leave the companion app opened? Does the Watch need it to run in any fashion? I was under the impression the Companion App was used to make changes to settings, apps, etc. no reason to leave it opened processing in the background unless you simply forget to quit it. Am I correct in saying this?
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.
Apple Watch Impacts iPhone Battery Life... One Way or the Other
- Thread starter MacRumors
- Start date
- Sort by reaction score
I wonder do any of you actually know how theWatch works? This should have been reported a long time ago, even before the watch was launched.
If you read the Apple Watch Programming Guide (i'm surprised that the staff on Macrumors didn't) you'll notice the figure bellow which explains how the apps are actually executed (and where).
Image
The UI elements are kept on the watch while the code and processing is done on the phone. The dashed blue line is the bluetooth connection.
Image
This is why there is lag on the watch when browsing through pages or clicking buttons: for every UI interaction, the watch "talks" to the phone and waits until the phone "responds". This is a very inefficient way to run apps, but at least it conserves the watch's battery, while draining the phone's. So even if your phone is in your pocket and you're not using it, it isn't idle, it runs apps for the watch, and constantly responding to every interaction the user makes on the watch.
The bottom line is that if you're using apps on the watch, especially non native ones (which i'm sure run in a different way), your phone battery is expected to be way lower.
Read more about this, here:
https://developer.apple.com/library...p.html#//apple_ref/doc/uid/TP40014969-CH3-SW1
There are a few things you should consider in your analysis:
- WK extensions running on a phone don't need to power the phone's display. How significant is that, do you think?
- WK extensions running on the phone don't render the Watch UI -- that happens on the watch itself. (In many kinds of mobile apps, the processing to render the UI dwarfs all other processing).
Considering the limitations of the WK API and the nature of the Watch, what high-power activities are there that really make sense for the extension that runs on the phone to do?
An extension mainly reads data, adjusts a small UI consisting of a fixed set of preexisting elements on the watch based on that data, and perhaps writes some data. The amount of data is typically going to be very small -- this is for display on a 1.3-1.5" screen. So I don't see the processor, radios, sensors or storage system working hard, typically.
Now, I'm sure it's possible to write inefficient WK apps that drain the phone's battery. But I don't see anything inherent in the architecture of WK that makes that inevitable. In fact, it looks like it makes it easy to be efficient.
I'd be interested in seeing data from actual power usage profiling before drawing conclusions about the impact of WK apps on phone battery life. Just considering what we know from analyzing the SDK I'd expect it to be pretty small.
----------
On iPhone, you don't need to close or quit apps to have them stop using power. It happens automatically.
My advice to you is don't listen to random people's anecdote-fueled theories about battery life. Most of them are complete hogwash.
Instead, use your phone and watch in the most useful and convenient way for your own needs. Do that for a week or so. If you end up having no problems with battery life then, great! The Watch and phone are doing what you want and you didn't have to give up anything. And if you do end up having battery life issues, at least you'll have some good info that is relevant to you rather than the random impressions from the internet, and you'll be a lot more likely to be able to find a workable solution.
The two devices for me average about 36hrs each when connected. Key factor is to keep GPS on but in power saving mode, whereby it uses the cell/wifi for determining location. I don't need to use High Accuracy mode unless I"m driving and using it.
I have 4 emails, 1 for work is on push, the other 3 are 2hr intervals. I get anywhere between 100-150 emails per day and manage a large team of individuals. Not sure how many notifications I get per day but it's easily 150-200 in all. The above is easy with the Gear S and Note 3.
Back OT I would say there should likely be a lift in run-time for the iPhone peeps with a watch as the BT4.0 LE as they will likely be using the watch vs lighting up their phone to check notifications. I know I see that with my Note.
Last edited:
I have noticed a slight drain due to the Bluetooth being on all the time but i still get almost 2 days out of my 6 Plus with normal usage. Watch gets about 18 hours for me.
Well, I thought the same every time the processor was updated to a less energy hungry version...but Jony likes to take those advantages away from me (us) by making the phone slimmer (=reducing the batterysize)...so maybe holding your breath for better battery life on the 6s may not be adviseable
----------
Correct me if I am wrong but does that not depend on how the app is programmed or if it does have processes that run in the background (like navigation or tracking apps that do not only run in the background when not "shut down" but also use gps which in turn loves to drain battery quick)
I may be wrong, but that is how it seems to be with many apps...
Exactly why I'm not bothering with an Apple Watch.
And I have an iPhone 6, so things would be even worse.
It's simply not worth the trade off.
Have you considered returning the watch, or are you going to live with the battery drain?
Or maybe, considering that person is one of the only who had that, see if its some setting or particular usage pattern that causes that. Or just sell the watch, you can probably sell it for more than retail right now...
----------
AGAIN point me to a review that's even 100 mile from what you state. I do not believe you. Simple as that. I'm not going to go further than that because I'm going to get banned.
I don't know where you're getting that a Gear S doesn't last 36hrs. Anyone that owns one will be able to confirm when the full GPS is off that it will last that long easily. I've had mine since day one and enjoy it every day. Check out XDA or any of the Gear S forums and you'll see. I turn mine on every day at 6am and only goes into airplane mode when I sleep but it stays on and tracks my sleep patterns. I wake at 6am, turn it on fully, charge it and take it off the charger between 7:30-8am and I'm usually onto my day by then.
If you don't believe me, that's fine. I'm not here to convince you or anyone of anything, only to share the facts and correct inaccuracies such as I've done. Connected remotely it doesn't take a huge battery hit at all. Not unless you make conference calls all day long with it. Many folks keep it connected remotely as to avoid any hiccups whereby it fails to auto-forward calls when it drops out of range. It's rare to happen but I state that as there are some on XDA forums that run remotely all the time because of it.
My experience with one first hand is far more real than a tester spending a few hours or days with one. Anyone in Columbus, Ohio care to meet for lunch and check it out is welcome to. Just PM me.
Last edited:
Battery life is strongest in the following order:
1. blue tooth
2. wifi
3 remotely
Not sure what you mean by less functionality either. I'll give Apple 100% credit for a nicer appearing interface and quality aesthetics when it comes to apps, but outside NFC it's not necessarily more functional. If anything the Gear S is.[/QUOTE]
The Gear S is definitely the closest of them all but took what, 5 iterations before Samsung got there? Of course that's the order that battery life is strongest, you just listed those radios in the order of their power consumption.
When you say you "used it all day", I'm sure your use of that watch at this point is nothing like people who just got an Apple Watch on Friday and are playing with it all weekend. I think we are going to find that this issue with phone battery life is a rogue app or bug or a both.
The Gear S operates with its own SIM and receives its own calls and texts - that's the sort of thing I would call "half-baked". If Apple were to ever go this route, it would be a data only connection and would share a universal phone number with your phone. Of course, it's too early for that right now.
I'm not sure what release for Samsung the Gear S was. If it was their fifth, that's fine. I'm sure at some point Apple will release a watch with a sim card. That's a must have for me, especially now that I'm used to it. Power wise, yes, I listed power consumptions in that order just to clarify. I would imagine the
Watch will follow suit in that BT will be more efficient than WiFi.I agree that
watch fans were likely lighting theirs up on Friday. I did the same thing with the Gear S when I got it on launch day. My use over the weekend was pretty hefty though and usually is. I've integrated the watch into my day more and more as time has gone on. This weekend was the first 2.5 day period where I completely left my Note 3 at home though and left for a 5k run for charity and hotel, etc. without anything but my Gear S. Loved it and saw no issues. Got several calls and even over the weekend tons of alerts and emails.
The way the Gear S operates with it's own sim isn't half-baked. The seperate sim vs a dual/shared sim is how such things are set up here in the states. In Europe I believe they permit mirrored sims but not here. It also isn't half-baked as when it's connected remotely as it's transparent and not noticeable to anyone that I'm not on my phone. Thus why it's state is shown as "connected remotely". It's still connected just via AT&T's network. No one I message or call notices anything different.
The ONLY difference is when you call me and I'm connected remotely is that you will hear the phone ring 3-4 more times as your call hits my Note 3 first, rings there and then relays over to my Gear S. Otherwise, you see everything as you would just the same as if I'm using my Note 3. Same email, Caller ID, etc. I can have it forward instantly too, I just choose not to.
It's only when my Note 3 is OFF or not connected in any way (full airplane mode) that the Gear S will use it's own number or display it's own number on texts or calls to others. Otherwise, again, it's one in the same. When connected remotely it's exactly that, my watch connects to you as a caller via my Note 3 as a relay. Seamless and transparent. I think in the 6 months I've used it there's been 1-2 instances where I've used it while it ran off it's own sim card only. One was because I forgot to turn my Note 3 on in the morning and left for work without it.
Last edited:
I bought a watch from Timex two weeks ago, and I haven't noticed any difference in battery life with my iPhone 6.
Yesterday (I counted) I received 132 text messages due to being in two separate text chains, and 86 emails. Also had a ton of notifications due to the earthquake and sports from ESPN. I was also loading apps on the phone, changing settings, arranging icons, etc.... Went to bed with 58% battery on the watch and my iPhone close to dead. In the past, this would have killed the phone completely by 7pm (several phone calls as well, including one for 5 minutes on the watch). I would say the battery life on the watch is much better than anticipated, and not much different from my old pebble (except the pebble would have crashed twice by now). Still not even close to my Garmin that got 6 days easily, but then again, it would disconnect for hours without me noticing it. I'm still not 100% sold on the watch, but it's definitely growing on me!
BTW: why is Siri so much more accurate on the watch? My text responses have needed no editing compared to when I create a text with siri on the phone.
BTW: why is Siri so much more accurate on the watch? My text responses have needed no editing compared to when I create a text with siri on the phone.
Well.....yea.....
If anyone thought of just putting the Apple watch on and expect any smart phone to have the SAME battery life needs to re-read the manual..
Battery life is tested and figures reported by Apple is done with wireless browsing, typically not Bluetooth.. and definitely *not* tested at the same time.
So, this is expected behavior... it would be for any phone...
Its like saying if i'm playing video on a Mac, I expect the same 10 hour battery life....... Well. no u won't.
If anyone thought of just putting the Apple watch on and expect any smart phone to have the SAME battery life needs to re-read the manual..
Battery life is tested and figures reported by Apple is done with wireless browsing, typically not Bluetooth.. and definitely *not* tested at the same time.
So, this is expected behavior... it would be for any phone...
Its like saying if i'm playing video on a Mac, I expect the same 10 hour battery life....... Well. no u won't.
Yes, I believe David Pogue discovered this undocumented Watch ability in his review a couple weeks ago. Scroll back here on MR a few weeks and you should see the story. I agree. Great feature.
In other news..
Driving your car less could result in using less gas. On the other hand, if you drive more you may be spending more at the pump..
Driving your car less could result in using less gas. On the other hand, if you drive more you may be spending more at the pump..
My battery life has been okay for the past 2 days. It might have been a software glitch or something in a buggy software as all the software is new.
I will report again if it gets worse, but for now it's good!
A typical cocky MacRumors comment.
P***k!
----------
Ahaaaaaaaaa ...
He's "WEARING" it wrong!!
No it doesn't push the notifications as everything works just fine without the app open. The app is kinda like the settings app on your phone- it even looks like it in places, but it is for initially pairing and setting up the watch, controlling a lot of settings on your watch, choosing which apps already installed on the phone appear on the watch, downloading new apps for the watch, and other things like that.
----------
No you are not being dense at all. It's new kit and takes a little getting used to. Anyone who makes you feel stupid for asking genuine questions is a dick.
If you have updated your phone software to the latest version, included with it is an app on the home screen called "Apple Watch". It is a black icon with a picture of the watch sideways on on it. It is used to control, pair and setup the watch. Once the watch is paired, the app looks a little like the iPhone's own settings app, but in black, and is used to control some settings on the watch, load apps onto it and things like that. I have found that the app isn't actually driving the apps or the notifications in the same way as the companion app for the Pebble watch does- the Pebble is very much dependant on the app. The Apple Watch however works just fine once paired, and you don't need to open the Apple Watch app on your phone unless you actually need to access a setting or load a new app.
To close an app on your phone simply double-tap the home button and the screen changes to show the apps you have open at the time. Swipe right until you find the app you want to close. Swipe up on the app and it is forced to close.
Hope this is helpful. Don't hesitate to ask if I've rambled and something isn't clear.
Last edited:
I had noticed my iPhone battery was impacted starting a day after I got the Apple Watch (but not on the first day). I finally figured it out last night.
I have the Runkeeper app on my iPhone, and it has a Watch app as well. I had started it up on my Watch just to see how it worked. But even though I had ended the workout activity in the app, it was apparently still using my phone's GPS. Finally spotted that this was happening by looking at the battery usage breakdown on my iPhone's settings and seeing Runkeeper at the top of the list.
Once I turned off the Location Services for Runkeeper, my phone's battery has been back to normal today.
I suggest anyone who is having battery issues with their phone check to see if any Watch apps have iPhone apps that are using location services more than they should. I'm guessing either the APIs or the developers' code need to be updated to handle
I have the Runkeeper app on my iPhone, and it has a Watch app as well. I had started it up on my Watch just to see how it worked. But even though I had ended the workout activity in the app, it was apparently still using my phone's GPS. Finally spotted that this was happening by looking at the battery usage breakdown on my iPhone's settings and seeing Runkeeper at the top of the list.
Once I turned off the Location Services for Runkeeper, my phone's battery has been back to normal today.
I suggest anyone who is having battery issues with their phone check to see if any Watch apps have iPhone apps that are using location services more than they should. I'm guessing either the APIs or the developers' code need to be updated to handle