Edited title: Google Pixel XL phone acts weird with cootwo

[Landstander]

Not sure if this is already a known issue, but I've found that NitroxBuddy is completely unable to connect to my (known working) cootwo under Android 7.1.1 (build NMF26Q), using a Google Pixel XL phone. While it's able to see the cootwo during the device scan, attempting to connect simply results in an "Initializing" message which lasts for a minute or so, followed an unceremonious disconnection. It will then be listed under Paired Devices, but with the name "Unknown Name" instead of the expected "Divenav-cootwo". Any attempt to reconnect to the device after that point fails in the same manner as the original attempt.

I've made numerous attempts to contact DiveNav over the past 2 weeks, using various forums (email, DiveNav support forums, Twitter, and Facebook), and have yet to receive any sort of acknowledgement. So this is basically just one more attempt to get their attention.

 

[kelemvor]

Just curious if it worked on the pixel prior to upgrading or if your pixel had 7 before you tried it with cootwo?

I'm not a divenav guy, just another cootwo owner - sorry! Interested because I work for a cell carrier and have been eyeballing that pixel xl for my next device.

 

[Landstander]

Just curious if it worked on the pixel prior to upgrading or if your pixel had 7 before you tried it with cootwo?

I'm not a divenav guy, just another cootwo owner - sorry! Interested because I work for a cell carrier and have been eyeballing that pixel xl for my next device.

It worked fine with the Nexus 6P that I had prior to upgrading to the Pixel XL (which shipped with Android 7.0), but has never worked with the current phone. It still works fine with an old Nexus 5 (running Android 6), however, so I know it's not a broken cootwo. The N5 has a dead battery and only works when plugged into AC power, so it's usefulness really ends at testing.

My Pixel doesn't have issues with any other bluetooth devices (car, smartwatch, multiple speakers, etc.), so I'm pretty sure its not a hardware issue on that end either.

 

[rmssetc]

Not sure if this is already a known issue, but I've found that NitroxBuddy is completely unable to connect to my (known working) cootwo under Android 7.1.1 (build NMF26Q), using a Google Pixel XL phone. While it's able to see the cootwo during the device scan, attempting to connect simply results in an "Initializing" message which lasts for a minute or so, followed an unceremonious disconnection. It will then be listed under Paired Devices, but with the name "Unknown Name" instead of the expected "Divenav-cootwo". Any attempt to reconnect to the device after that point fails in the same manner as the original attempt.

I've made numerous attempts to contact DiveNav over the past 2 weeks, using various forums (email, DiveNav support forums, Twitter, and Facebook), and have yet to receive any sort of acknowledgement. So this is basically just one more attempt to get their attention.

Are you running the latest version of NitroxBuddy? I was unable to connect to my Cootwo with the previous version, with similar symptoms. Upgrading to the current version (1.6.6) fixed that. However, this is on much older hardware, on an older Android release, so I wouldn't be shocked if the problem is with Android 7.x.

BTW, you do need the app to reset the O2 sensor clock when replacing the sensor...the Cootwo doesn't do that automagically.

Good luck!

 

[Landstander]

Are you running the latest version of NitroxBuddy? I was unable to connect to my Cootwo with the previous version, with similar symptoms. Upgrading to the current version (1.6.6) fixed that. However, this is on much older hardware, on an older Android release, so I wouldn't be shocked if the problem is with Android 7.x.

Yes, I've got version 1.6.6 installed.

BTW, you do need the app to reset the O2 sensor clock when replacing the sensor...the Cootwo doesn't do that automagically.

Glad I've still got that N5 lying around, in that case.

Thanx!

 

[rhwestfall]

@DiveNav : Alberto, you seeing this?

 

[diversteve]

not since Friday..

 

[kelemvor]

The Nexus 5 has Bluetooth 4.0 hardware where the pixel xl has 4.2 hardware. It could be a factor. Check in your phone settings and see if you have an option to disable things like Bluetooth LE /LE Secure.

Just as a temporary test mind you, I know disabling new features wouldn't sit well with me. Although, unless you also buy new bluetooth devices the new features won't get used.

 

[Landstander]

The Nexus 5 has Bluetooth 4.0 hardware where the pixel xl has 4.2 hardware. It could be a factor. Check in your phone settings and see if you have an option to disable things like Bluetooth LE /LE Secure.

There don't appear to be any such options available. But thank you for the suggestion.

 

[DiveNav]

@DiveNav : Alberto, you seeing this?

Yes