Search results

This is probably obvious, but try to ensure the retainer (assuming you didn't purchase directly from DiveNav) understands that it's being returned because the company is unresponsive to legitimate support requests. It may prompt them to reevaluate whether or not the DiveNav line is even worth...

That looks very nice. Thank you!

I've had quite a few people express interest in my cootwo, and until recently have always sung it's praises and heartily recommended that people get one. Since they recently made it very clear that they loathe customers using Android (and no, I don't think that's an inaccurate term, nor too...

If you don't mind, let me know what you end up getting and how well you end up liking it. Don't have the $$$ set aside to do that right at the moment, but I expect that I'll be doing the same in the near future. Minus the return, unfortunately, since mine is one of the first units released and...

That's actually how I took it... my apologies if it appeared otherwise. And I do very much appreciate your suggestions! :)

I wouldn't rule it out, but on the other hand I've seen several other posts in various forums concerning cootwo pairing issue with other phones. So the question of where the problem is really isn't as clear cut as DiveNav would like to believe. Again, all I know for certain is that bluetooth has...

And DiveNav has just made it very clear that they have no intention of supporting the Android platform, despite having happily marketed the cootwo for it and accepted money from Android users. Good luck with your issue @Dan Brown, not that I hold a great deal of hope that you'll get any sort of...

I'd recommend marketing it as an iOS-only device, since you clearly have no intention of supporting your product on Android. That would at least be honest.

Since the original thread was unceremoniously locked. Not necessarily, it could just as easily be a internal setting on the cootwo which was "flipped" by the successful connection/pairing. Until and unless it can be reproduced again, there's no way to know for certain. All I can say for sure...

I did that last night, extending the deadline by two months, just to get things up and running until I decide for certain how I'm going to handle this scenario going forward. Not without a bit of trepidation, however, since I can't really be sure of how long is too long. Still, it's good that...

I'd say the response was an utter cop out. DiveNav knew full well that Android had numerous vendors going into the cootwo project, and obviously decided that the market was worth pursuing. If this means a bit of extra work is required to keep the app functional, then so be it... that's exactly...

I did get a response from Divenav this afternoon, simply asking for a screenshot, from my email inquiry to the customer.service@divenav.com address. So progress, to an extent. After seeing DiveNav's reply to my post concerning that issue, however, I've decided that I can't in good conscience...

Unfortunately, mine needs the O2 sensor replaced. I'm certainly not buying one from DiveNav, however, so it's out of commission until and unless I can find the part from another source. EDIT: Fortunately they were good enough to list some compatible sensors on the cootwo product page, and the...

Fortunately I found a workaround this morning, allowing me to use the cootwo again with my current phone. If that's DiveNav's attitude to support requests, however, I can guarantee you that I'll never send another dime in your direction. Not to mention discourage anyone who inquires about my...

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

Yes, I've got version 1.6.6 installed. Glad I've still got that N5 lying around, in that case. Thanx!

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...

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...

You're not alone. I've been trying to report a NitroxBuddy bug (inability to connect to cootwo under Android 7.1) for nearly 2 weeks now, via multiple forums... their "contact us" page, support forum, Twitter, and Facebook. Haven't received so much as an autoreply, much less any sort of...

For the curious, this was indeed caused the battery. I replaced it just before another trip to Bonne Terre Mine last weekend, and the unit performed flawlessly. (-;