Android Wear Smartwatch Owners Reporting Pairing Issues With iPhone 7

[MacRumors]

Several popular Android Wear devices like the Moto 360 and Fossil Q remain incompatible with the iPhone 7 and iPhone 7 Plus, according to a report by The Verge.

Owners of the Android smartwatches have been able to use the devices with the iPhone 5 or later since Google added support for iOS back in August of last year.

However, as evidenced by a raft of complaints in an Android Wear discussion thread, the Moto 360 (2015), Moto 360 Sport, Tag Heuer Connected, Asus Zenwatch 2, and Fossil Q Founder are all unable to properly pair with the iPhone 7, with many users' watches hanging during the setup process.

Apple recently fixed some compatibility issues between Android Wear devices and iOS 10 with the release of iOS 10.0.2, but the reported problems with specific models of watch appear to remain. Google says it is aware of a "serious pairing issue" and is investigating a fix.

The Android Wear iOS app supports Google's Voice search and enables iPhone lock screen notifications to be mirrored on the watch faces. It also lets owners of the devices make use of services like Google Now and Google Fit, as well as the watches' Weather and Translate features. In addition, the app includes a handful of 'curated' watch faces for users to choose from.

Article Link: Android Wear Smartwatch Owners Reporting Pairing Issues With iPhone 7

 

[44267547]

Apple's marketing scheme to convert Android wearers to the Apple Watch.

 

[Macwatcher123]

To be honest, you kind of lost me when you said "popular".
Perhaps they should all just invest in a proper smartwatch.

PS: This isn't really an Apple problem, is it? Google added iOS support, it's up to Google to maintain that support, and if it hasn't done so it is solely to make its competitor look bad. Android users should see it as a great example of how software and security updates work on their imitative and fragmented platform.

 

[WhiskeyTangoFoxtrot]

That's awful for those two people.

 

[555gallardo]

That's awful for those two people.

There's a lot of users here in Europe who chose Android Wear smartwatch instead of Apple Watch. The decision is mostly because of the design, where Apple Watch look like a smaller iPhone, most Android Wear watches look like regular watch.

 

[Macwatcher123]

There's a lot of users here in Europe who chose Android Wear smartwatch instead of Apple Watch. The decision is mostly because of the design, where Apple Watch look like a smaller iPhone, most Android Wear watches look like regular watch.

Yep, they really should hassle google. It's had access to the tools to enable iOS support since WWDC, like every other developer.

 

[Sirious]

But why would you buy an iPhone 7 and then buy an Android Wear watch?

Problems like this are inevitable.

 

[2457282]

One of the reasons I pay a premium for Apple devices is because of the tight integration accross the devices that is built in to the ecosystem. Given that, it is always strange to read about people that buy a premium Apple phone and then try to pair it with non Apple devices. Sure, it should work. But why? I mean why would you try to pair the iPhone with cromecast or with android wear when the integration with the Apple alternatives are significantly better?

I am not debating iOS over Android here, just the integration. To me this type of pairing seems like you get the worst of both worlds, at least in terms of integration.

 

[MH01]

To be honest, you kind of lost me when you said "popular".
Perhaps they should all just invest in a proper smartwatch.

PS: This isn't really an Apple problem, is it? Google added iOS support, it's up to Google to maintain that support, and if it hasn't done so it is solely to make its competitor look bad. Android users should see it as a great example of how software and security updates work on their imitative and fragmented platform.

A "proper" smartwatch ? I have an Apple Watch, and like my "proper" iPhone, it too has bugs I have to deal with

I think you are trying to create a issue here that is not present. We have a software bug, it's not a blame game nor a platform war.

The issue will be fixed .....just as bugs in my Apple Watch in software releases.
[doublepost=1475928902][/doublepost]

One of the reasons I pay a premium for Apple devices is because of the tight integration accross the devices that is built in to the ecosystem. Given that, it is always strange to read about people that buy a premium Apple phone and then try to pair it with non Apple devices. Sure, it should work. But why? I mean why would you try to pair the iPhone with cromecast or with android wear when the integration with the Apple alternatives are significantly better?

I am not debating iOS over Android here, just the integration. To me this type of pairing seems like you get the worst of both worlds, at least in terms of integration.

Just to jump in, using chromecast video and audio, they are a better product , for instance chrome cast audio is excellent in turning any speaker into a wireless hotspot, and they work great with my iPhone / Apple gears

 

[Abazigal]

Yep, they really should hassle google. It's had access to the tools to enable iOS support since WWDC, like every other developer.

Google has traditionally been very slow to update their iOS apps to support the newer software features.

Given their resources, Google should have detected this at the beta testing stage and rectified it there and then.

 

[Macwatcher123]

My argument is that they wilfully slow this update to make Apple look bad.google is a sociopath and cares not one jot about its customers

Google has traditionally been very slow to update their iOS apps to support the newer software features.

Given their resources, Google should have detected this at the beta testing stage and rectified it there and then.

 

[gigapocket1]

Who knows what the problem may really be.. Apple seems to always have problems with Bluetooth though.. so this shouldn't be a surprise lol..

 

[CoolGuy9890]

Android Wear iSO app

Macrumors, its spelled as "iOS" not iSO

 

[diamond.g]

Yep, they really should hassle google. It's had access to the tools to enable iOS support since WWDC, like every other developer.

Interesting, the article doesn't say the issue affects iPhones 6s. Which should rule out a problem with iOS, shouldn't it? Just folks with the new iPhone are having a problem. Which is hard for Google to fix until they get the phone in hand...

 

[Macyourdayy]

Android where?

 

[ArtOfWarfare]

Yep, they really should hassle google. It's had access to the tools to enable iOS support since WWDC, like every other developer.

It doesn't sound like it's an iOS 10 issue - it sounds like an iPhone 7 and 7+ issue. If Google got earlier access to those phones than the general public, I doubt it was a second before they were revealed at the iPhone 7 event. They may have been given access to the phones immediately after the event, but that would only have given them a month up to now to have fixed it.

And I doubt they were given even semi-special access like that. They probably had to buy the phones just like ordinary customers. Google and Apple are direct competitors - I doubt Apple is going to do anything to help Google. They'll probably do as much as they can legally get away with to hinder Google.

 

[Aluminum213]

You get a fraction of the features using android wear with iOS, I don't know why one wouldn't get Apple Watch if they really wanted a smart watch if they were an iPhone user. If looks of the Watch mattered that much then buy a regular watch

 

[Standupmac]

I had trouble with the Garmin Fenix not pairing also. But garmin updated the connect software and it works fine now. (Hopefully the Apple Watch 3 has enough exercise features to replace the Garmin!)

 

[symphara]

To be honest, you kind of lost me when you said "popular".
Perhaps they should all just invest in a proper smartwatch.

PS: This isn't really an Apple problem, is it? Google added iOS support, it's up to Google to maintain that support, and if it hasn't done so it is solely to make its competitor look bad. Android users should see it as a great example of how software and security updates work on their imitative and fragmented platform.

It sounds like an Apple problem, if they did an iOS update to fix some issues with Android Wear, and if some issues persist solely for the iPhone 7.

Perhaps there's nothing Google can do to fix this, if it's iPhone 7 specific software bugs (e.g. Bluetooth driver) causing this.
[doublepost=1475936213][/doublepost]

You get a fraction of the features using android wear with iOS, I don't know why one wouldn't get Apple Watch if they really wanted a smart watch if they were an iPhone user. If looks of the Watch mattered that much then buy a regular watch

Always-on display, round screens, just to name a couple of reasons.

 

[benson197]

I had this issue as well, so I traded in my Moto 360 Sport and bought an Apple Watch series 0. I liked the Moto 360, the always on display, the display was readable in light, the fact it was round, the activity tracking and built in GPS all worked really well. The Apple Watch is fine, the activity tracking is good, and the haptic feedback is pretty good.

 

[now i see it]

Intentional

 

[cdmoore74]

Really??? I've had pairing issues for months with my Moto 360. As soon as I went full time with the 7 Plus I also got a Series 1 AW and not one connection issue.
Bottom line is just get a AW. To be honest try to find a first gen on the cheap.

 

[Turk123]

It goes beyond a watch problem. IOS 10.0.2 has a serious bluetooth problem. I am working with Apple to resolve my hearing aids that no longer stay paired with the new IOS. Apples "hearing devices" will not stay paired, cycling on and off and causing my hearing aid software to disconnect. There are many other devices not working also like BMW and carplay not working. Also there are many speaker Bluetooth systems that have stopped connecting properly.

I have an Apple senior support person who is working with me and the Apple engineers. Only an IOS upgrade with fix the issue. I have been waiting for 3 weeks.

 

[pdaholic]

Somewhat off topic, but I noticed that a couple of Bluetooth headphones that paired with my original Apple Watch won't pair with my new Apple Watch.

 

[macfacts]

Why does Bluetooth under iOS suck?