Apple Watch losing connection to iPhone

Discussion in 'Apple Watch' started by zmunkz, Sep 19, 2016.

  1. zmunkz macrumors 6502a

    zmunkz

    Joined:
    Nov 4, 2007
    #1
    I got my new iPhone 7+ on Friday, and I've noticed ever since that my Watch (1st gen) disconnects from the phone pretty much constantly. Every time I look at it that damn red icon is back and I have to go toggle bluetooth from the phone to reconnect it. The minutes later, red icon is back.

    Anyone else noticed this? I'm re-pairing the watch now, but curious if I'm the only one with this problem.
     
  2. smarks90 macrumors regular

    Joined:
    Sep 19, 2013
    Location:
    Cleveland, Ohio
    #2

    had this SAME thing happen! have you updated to most recent iOS release? specific line item in update regarding "Bluetooth connection issues for Apple Watch" after I did that update on my new 7+ I was good to go!
     
  3. zmunkz thread starter macrumors 6502a

    zmunkz

    Joined:
    Nov 4, 2007
    #3
    Thanks I'm giving that a try... Looks like I was still on the WatchOS 3 beta
     
  4. smarks90 macrumors regular

    Joined:
    Sep 19, 2013
    Location:
    Cleveland, Ohio
    #4
    I think it had more to do with the build version of iOS 10. I had the issue on my fresh iPhone 7+ as it shipped with iOS 10. I looked and saw there was already iOS 10.1 available and the 10.1 update had the line about AW BT connection being fixed with that update.
     
  5. zmunkz thread starter macrumors 6502a

    zmunkz

    Joined:
    Nov 4, 2007
    #5
    I updated everything last night and so far so good -- thanks for pointing me in the right direction!
     
  6. smarks90 macrumors regular

    Joined:
    Sep 19, 2013
    Location:
    Cleveland, Ohio
    #6
    no problem! now if I only I could figure out the issue with the activitiy app not syncing up right when have two watches paired to one iPhone and switching back and forth...something not quite right there from a software standpoint....
     
  7. has.marvel macrumors member

    Joined:
    Jan 13, 2012
    #7
    I am having problems with my iPhone 6 and my original Watch. Ever since I updated to iOS 10 and Watch 3.0, I keep losing bluetooth connection. The only way to get it back is restart the iPhone. I try to reconnect and it does not see the watch without the restart. A real pain in the bum. Not sure where the issue is.
     
  8. smarks90 macrumors regular

    Joined:
    Sep 19, 2013
    Location:
    Cleveland, Ohio
    #8
    has.marvel- are you on 10.0.1 or just 10.0? The issues I replied about were resolved with the 10.0.1 update. if you're still having issues and are on 10.0.1, perhaps it's related to something else.
     
  9. has.marvel macrumors member

    Joined:
    Jan 13, 2012
    #9
    10.0.1. I will try and update toe 10.0.2 this weekend and see if that helps.
     
  10. has.marvel macrumors member

    Joined:
    Jan 13, 2012
    #10
    The update to 10.0.2 appears to have solved my issue. Not sure if it was that release or just a reinstall that fixed it but....
     
  11. has.marvel macrumors member

    Joined:
    Jan 13, 2012
    #11
    I spoke too soon. Does not seem to happen as often but after a day or so from a reboot of the phone, I start losing connection again. It is a real pain. Never had this problem with iOS 9 or Watch 2 just since software upgrades.
     
  12. slburse macrumors newbie

    Joined:
    Sep 26, 2016
    #12
    I had the same issue with the Watch losing connectivity. At the time, I was running iOS9 with the original Watch. Decided to return the Watch and only assumed it was competing against my FitBit for the connection with the Phone.
     
  13. has.marvel macrumors member

    Joined:
    Jan 13, 2012
    #13
    Well, I tried resetting and repairing the watch the the phone this afternoon. Again it started with a bluetooth connection. I had the phone and watch on me the whole time and it lost the connection within just a few hours. I guess I will have to call Apple and see if there is anything they can do to fix/explain the issue.
     
  14. Buran macrumors 6502

    Buran

    Joined:
    Oct 22, 2007
    #14
    I'm fully patched and it's happening to me also. First gen watch, iPhone 7, latest iOS.
     
  15. bronzi macrumors member

    Joined:
    Aug 13, 2015
    Location:
    Earth
    #15
    Yeah, happened to me yesterday. and I'm up to date on all OS, 1st Gen watch and iPhone 7.
     
  16. Buran macrumors 6502

    Buran

    Joined:
    Oct 22, 2007
    #16
    Have any of you tried resetting the watch and pairing as new?
     
  17. has.marvel macrumors member

    Joined:
    Jan 13, 2012
    #17
    I spent time on the phone with Apple support this afternoon. Looks like there might be an issue here. We went thru some diagnostics and stuff and he asked me to try some things the next time connection was lost. After he gathers more info it will go to the engineers to look at. I would suggest if you are having the issue to also call support.
     
  18. jhobe6678 macrumors newbie

    Joined:
    Nov 6, 2016
    Location:
    Treasure Coast, FL
    #18

    I'm in the same boat. iPhone 7 Plus, Series 2 Watch, only this time when it loses connection, even if I reset the watch and unpair and everything else, I can't get the watch to pair back to the phone for at least a day or two. Engineers are looking at it and I still have no answer.
     
  19. has.marvel macrumors member

    Joined:
    Jan 13, 2012
    #19
    Well, I have been working with Apple support and we still do not have an answer. I am getting back in touch with them this afternoon to continue the quest. They keep wanting me to capture new and different info when the connection fails. I guess, they are as puzzled as I am.
     
  20. jhobe6678 macrumors newbie

    Joined:
    Nov 6, 2016
    Location:
    Treasure Coast, FL
    #20
    Same thing here. I have been waiting two weeks for a reply from my last upload of a gig of logs and they contacted me saying the engineers want more information. I have no idea what more they can get. The phone is obviously fine and I still have a dead watch. Hell, the watch was running for DAYS on its battery reserves and still telling the wrong time. I'm getting a call back tonight. We will see.
     

Share This Page