Although many owners of Android Wear smartwatches expected that the terminals iPhone 7 to work with them, unfortunately this does not happen. According to many people who tried to use the iPhone 7 with an Android Wear smartwatch, it seems that there are many compatibility issues between the new smartphone and smartwatches with that operating system.
Although Android Wear has supported iOS since 2015, the iPhone 7 cannot interconnect with a wide range of Android Wear smartwatches. Among them are: Moto 360 (2015), Tag Heuer Connected, Asus Zenwatch, Fossil Q, Michael Kors Access and others.
The Moto 360 is one of the most popular Android Wear smartwatches and cannot be connected to the iPhone 7 or iPhone 7 Plus at least for now. It is not known what kind of changes Apple made for terminals and iOs 10, but on the old iPhone terminals with iOS 10 there are no problems of this kind, they are limited only to the new products.
iPhone 7 cannot connect to any Android Wear smartwatch
iPhone 7 recognizes the existence of an Android Wear smartwatch in its vicinity, they are displayed in the application dedicated to this operating system, but pairing is impossible. When the user is asked to enter a code displayed on the phone in the iOS application, the entire pairing process is blocked without working.
Those from Google have already updated the application for Android Wear 2 times in a week, but the iPhone 7 still refuses to connect to smartwatches. Apple solved in iOS 10.0.2 a problem regarding compatibility with this operating system, but things have not improved in terms of the possibilities of interconnection.
The even bigger problem is that installing software updates on Android Wear smartwatches, to solve the iPhone 7 compatibility issue, can only be done from the iOS or Android app, but without being able to connect to an iDevice you can't the update, so it remains to be seen what those from Apple and Google will do.
Considering that the Apple Watch 2 has just been launched, we could easily conclude that these problems did not appear out of the blue.
