What connection is needed?

[foxbat121]

No, it has RIMs secret source in it. Not all Android phones are created equal.

 

[Tetragrammaton]

OK... I only wish these two devices to pair properly again, as it once did.

 

[foxbat121]

I have been using this watch since 11/2015 (swapped to new updated version in 4/2016 as the original one was recalled) and went through couple different Android phones (Nexus 5, Samsung Galaxy Alpha and HTC One M9) and never had any problem with Bluetooth pairing.

And from your posting, you haven't being successful pairing it with your PRIV since you got it last year. The answer seems quite obvious.

 

[Ha P McBroom]

Oh I wouldn't be so radical that you change your phone just to suite your AW watch. That's kinda extreme in my opinion. I have a BlackBerry Dtek 60 that's connected to my LG Urbane 2nd edition LTE via Bluetooth. While Bat is right to suggest that you explore the option of using another brand of phone to see if you have a better connection. My experience of switching around phone connections with other phones wasn't any better. Though I'm happy with my overall experience with the watch and phone pairing I don't expect my phone or watch to do tons just the basics. BlackBerry did tweak their Android skin and and more secure authentication systems within the phone but that doesn't mean that Android OS is compromised and won't work. My older Nexus 6p had the same issue when connected to my LG Urbane LTE so I took it to my phone carrier and they verified that the phone wasn't the issue so I was connected with the LG Tech support folks and they recommended that I send in the watch for they think it's a technical fault.

 

[Tetragrammaton]

I have been using this watch since 11/2015 (swapped to new updated version in 4/2016 as the original one was recalled) and went through couple different Android phones (Nexus 5, Samsung Galaxy Alpha and HTC One M9) and never had any problem with Bluetooth pairing.

And from your posting, you haven't being successful pairing it with your PRIV since you got it last year. The answer seems quite obvious.

Hi Foxbat,

it worked very well, when I received the watch. Only after some updates it stopped connecting.

BUT: I have tested the watch now with different Droids and even an iPhone7. All devices connected to the watch, thus I went to Vodafone and asked for a swap-phone. Will see, if that works then!

 

[Tetragrammaton]

Oh I wouldn't be so radical that you change your phone just to suite your AW watch. That's kinda extreme in my opinion. I have a BlackBerry Dtek 60 that's connected to my LG Urbane 2nd edition LTE via Bluetooth. While Bat is right to suggest that you explore the option of using another brand of phone to see if you have a better connection. My experience of switching around phone connections with other phones wasn't any better. Though I'm happy with my overall experience with the watch and phone pairing I don't expect my phone or watch to do tons just the basics. BlackBerry did tweak their Android skin and and more secure authentication systems within the phone but that doesn't mean that Android OS is compromised and won't work. My older Nexus 6p had the same issue when connected to my LG Urbane LTE so I took it to my phone carrier and they verified that the phone wasn't the issue so I was connected with the LG Tech support folks and they recommended that I send in the watch for they think it's a technical fault.

Hi McBroom,

thanks for your feedback. As I wrote a post earlier, I finally had the chance to test the watch's connection to other Droids and the newest iPhone. All of them connected smoothly. I narrowed it to the PRIV now. The PRIV and the LG Urbane 2nd edition worked very good at the beginning. Only after some updates and not using the watch for quite some time it did not connect properly anymore.

 

[afblangley]

The phone that's connected to your watch doesn't have to be your daily driver. If you're a devoted user of a phone that doesn't play well with your watch, get a cheap Android and use it solely for that purpose. As long as it's connected to WiFi, it doesn't need to leave the house.

 

[Tetragrammaton]

Hi afblangley, will give the substitute PRIV a chance. Thanks for the tip, I may go that way.

My original PRIV used to work that way with the LG Urbane 2nd edition. Mostly Saturdays I left for the groceries and the phone was at home, while the watch was connected and worked perfectly. That is why I am so astonished and kinda sad, that it ceased to to do.

One thing I have experienced the last time I disconnected the watch from the phone by deleting the Android Wear app on the PRIV was that all of a sudden my phone rebooted, without asking me for the PIN. That was really odd...

 

[Tetragrammaton]

Hopefully my last post in this matter: The substitute phone works fine with the watch now. Pairing worked smooth.

 

[scaots]

My wife has a Priv and doesn't use AW, but the BT is pretty wonky, frequently disconnecting in the car. I think one of the more recent updates helped quite a bit.

The other problem is the AW app seems to undergo limited testing. New versions frequently have issues. I always backup my apps and have several times had to revert to an earlier version of AW because of some problem. Seems like there shouldn't be so many issues with something like AW since Google has the software on the watches under fairly tight control.