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.
/article-new/2015/08/AndroidWearforiOS.jpg?lossy)
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.
Top Rated Comments
(View all)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.
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.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.
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.To be honest, you kind of lost me when you said "popular".
A "proper" smartwatch ? I have an Apple Watch, and like my "proper" iPhone, it too has bugs I have to deal with :pPerhaps 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.
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?
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 gearsI 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.