No. Bluetooth is fairly complicated, but the key here is that A2DP is a specific Bluetooth "Profile" type. If the new GPS _only_ does A2DP then the device you are pairing it with must also support that profile. If I am not mistaken, A2DP is only one way transmission of sound, typically for the purpose of music streaming. To the best of my knowledge it can not be used for pairing with a cellphone for the purpose of hands free calling. That would reqiure supporting the Headset Profile or Hands-Free Profile.IE, can a newer GPS with A2DP bluetooth talk to a helmet that uses regular bluetooth?
Agreed. The Chatterbox XBi2 is A2DP to get stereo and intercom range (we use it bike-bike) and pretty cool but it won't talk to Chatterbox's own XBi or with any other non-A2DP devices.No. Bluetooth is fairly complicated, but the key here is that A2DP is a specific Bluetooth "Profile" type.IE, can a newer GPS with A2DP bluetooth talk to a helmet that uses regular bluetooth?
A2DP was for the Stereo streaming. The increased range is achieved by becoming a class 1 device, rather than class 2. The classes dictate how much transmit power the device is capable of. A2DP did not increase the range. As for why the XBi and XBi2 wont talk with one another, I am not sure. Class 1 may not be "backwards" compatible with class 2 devices, I am not sure. A2DP is stereo one-way streaming, so the intercom is likely using a different Bluetooth profile for that functionality.Agreed. The Chatterbox XBi2 is A2DP to get stereo and intercom range (we use it bike-bike) and pretty cool but it won't talk to Chatterbox's own XBi or with any other non-A2DP devices.No. Bluetooth is fairly complicated, but the key here is that A2DP is a specific Bluetooth "Profile" type.IE, can a newer GPS with A2DP bluetooth talk to a helmet that uses regular bluetooth?
The GPS is a Nuvi 765T with A2DP.Just because the GPS has the A2DP standard does not mean it won't do regular bluetooth too. In this case since the gps has good chance of getting hooked up to an older device it might be backward compatible too. Leskid what GPS and helmet are we talking about?
The important thing there is that the 660 supports A2DP but not only A2DP. As ffejtable was saying, there are several Bluetooth profiles and Bluetooth devices may support some and not others. In fact, they can apparently support parts of some. I'm not too surprised (tho' amused) that Garmin was confused because, well, it's confusing.(major snippage)
Except that newer Zumo 660 DOES use A2DP like my Nuvi765T and it says you can pair phone / Zumo / helmet and the phone calls will come through to your helmet, as they should. Whether or not this is accomplished via A2DP, I have no idea, which is what started me on this post.
Well a single device can support multiple profiles, simultaneously, so your Garmin should use A2DP for stereo streaming and either the hands free or headset profile for talking on the phone. Bluetooth is still plagues with interoperability issues between some devices, even when they support the right profiles, and this might be part of the problem you are having.The GPS is a Nuvi 765T with A2DP.Just because the GPS has the A2DP standard does not mean it won't do regular bluetooth too. In this case since the gps has good chance of getting hooked up to an older device it might be backward compatible too. Leskid what GPS and helmet are we talking about?
My 'helmet' isn't a helmet (I actually have the Scala Q2 but given the history of issues with this unit, it's not part of my testing)
So to simulate the helmet, I used my motorola T505, which is an automotive hands-free speakerphone thingy (which is an A2DP audio device, so I believe the test results above are relevant)
by relevant, I was referring only to the motorola* to get those results which Garmin reproduced. ie Nuvi sends out MP3s and spoken directions but no phoneYou comments about replacing the Scala with the Motorola being relevant, is in fact not, since one device supports A2DP and the other does not.
Enter your email address to join: