2820 Bluetooth Issues

EasySushi

Registered user
Joined
Jun 25, 2006
Messages
396
Reaction score
0
Location
Hampshire, Surrey England
Hi guys I sent this to garmin tech support

Hi Phil

I have a problem with my 2820, Sony K750i mobile and Cardo Scala-Rider Bluetooth helmet headset.

The problem is that the 2820 will intermittently drop the Bluetooth connection from the Scala-Rider, when this happens sometimes the phone will hang and will require it to be powered off and on. However when I am playing music constantly through to the Scala-Rider the connection is maintained.

I am also unable to voice dial through the Scala-Rider when connected to the 2820, but can voice dial when connected directly to my phone.

I am also unable to answer the phone when using the Scala-Rider when it is connected to the 2820, but when connected to my phone the Scala-Rider works perfectly.


and this is the response I got

Dear Tyrone

Thankyou For Contacting Garmin Europe

I have found out that there will be a software update released to tackle this problem but have no lead time on this. So it's a case of waiting for this to be released.

Hope this helps.


Anybody experienced similar problems?


Cheers

Ty
 
Can't say i know much about the bits that your using but it looks as though there doing something about it though. :clap
 
Ty,
I find this response somewhat unrealistic given that Garmin are supposed to be a premium product. You have brought the top of their range product on the basis of their advertising and now they are telling you that they acknowledge a problem with it which they will fix as and when they get around to it. Given that they were more than happy to take your money via one of their dealers is this really the sort of response you or any of us should be getting.
Matt
 
Matt Gibbs said:
Ty,
I find this response somewhat unrealistic given that Garmin are supposed to be a premium product.
Matt

Hmmm slightly unreal expectations of software bug fix lifecycles.. It often takes a while for a bug to be formally acknowledged let alone fixed. If its to be fixed in a reliable manner significant amount of testing, codeing and retesting is needed. It sucks when it doesnt work but aleast they are saying its going to be fixed.
 
IainMac said:
Hmmm slightly unreal expectations of software bug fix lifecycles.. It often takes a while for a bug to be formally acknowledged let alone fixed. If its to be fixed in a reliable manner significant amount of testing, codeing and retesting is needed. It sucks when it doesnt work but aleast they are saying its going to be fixed.
Shouldn't bugs be fixed during development and before the product is put on sale?(exc.R1200GS's).
 
I doubt if any software released is ever bug free. It is also unrealistic to expect them to be able to test every combination of equipment that might be connected together - that way nothing would ever be released.

Its a shame that Ty has found a combination that doesn't work but at least they are working on it.Many software producers would just say its a feature. ;)

Paul
 
Paul Wakefield said:
I doubt if any software released is ever bug free. It is also unrealistic to expect them to be able to test every combination of equipment that might be connected together - that way nothing would ever be released.

And take that thought with you when you next get onto an aircraft / train etc :eek:
 
[QUOTE=Paul Wakefield]I doubt if any software released is ever bug free.

I agree with you totally there Paul, Mapsourse V8 is still showing petrol stations I KNOW that have been shut down. One I know of was shut down 7 YEARS ago. :eek:

Pat
 
John Armstrong said:
And take that thought with you when you next get onto an aircraft / train etc :eek:


Now you know why I don't fly in anything which uses technology later than the 1940s and where you can't see things spinning around (fingers crossed). :D

Paul
 
Paul Wakefield said:
Its a shame that Ty has found a combination that doesn't work but at least they are working on it.Many software producers would just say its a feature. ;)

Yes it is a shame but Garmin has been aware of a bluetooth issue for over two months now & i am still waiting for a result, the booklet for the 2820 says it will work with any compatible bluetooth headset only problem is that every blutooth helmet/headset specific for motorbiker i have tried will not work (tried dainese airstream, Scala-Rider, Motorola HS830) it would be nice if garmin or fellow GS user could tell me of a compatible blutooth headset i could use :nenau i purchased the 2820 because of the bluetooth connection, if i had known that after 3 months of ownership i still would be unable to use the bluetooth function i would have got my money back, i really like the unit but feel like i have been let down & yes i know the BMW system 5 with bluetooth will work but its a tad too expensive for me
 
leman said:
Paul Wakefield said:
Its a shame that Ty has found a combination that doesn't work but at least they are working on it.Many software producers would just say its a feature. ;)

Yes it is a shame but Garmin has been aware of a bluetooth issue for over two months now & i am still waiting for a result, the booklet for the 2820 says it will work with any compatible bluetooth headset only problem is that every blutooth helmet/headset specific for motorbiker i have tried will not work (tried dainese airstream, Scala-Rider, Motorola HS830) it would be nice if garmin or fellow GS user could tell me of a compatible blutooth headset i could use :nenau i purchased the 2820 because of the bluetooth connection, if i had known that after 3 months of ownership i still would be unable to use the bluetooth function i would have got my money back, i really like the unit but feel like i have been let down & yes i know the BMW system 5 with bluetooth will work but its a tad too expensive for me


Leman

does your scala not work or are you having the same trouble as me


Ty
 
gpsonaPan said:
[QUOTE=Paul Wakefield]I doubt if any software released is ever bug free.

I agree with you totally there Paul, Mapsourse V8 is still showing petrol stations I KNOW that have been shut down. One I know of was shut down 7 YEARS ago. :eek:

Pat
Pat, sorry to be a pedant but your issue is with data quality not software bugs. The two are fundamentally different. Try thinking of it like this:

You type a document using MS Word and when you try to print it the program crashes. That's a software bug. Alternatively, you type a document using MS Word and when you print it the document is full of spelling mistakes and typo's. That's a data quality issue. In the first example it's Microsoft's problem and it's up to them to correct it; in the second example it's your inability to spell and type correctly and it's your problem to correct it ;)
 
Paul Wakefield said:
I doubt if any software released is ever bug free. It is also unrealistic to expect them to be able to test every combination of equipment that might be connected together - that way nothing would ever be released.

Its a shame that Ty has found a combination that doesn't work but at least they are working on it.Many software producers would just say its a feature. ;)

Paul
Although I have no direct knowledge of Bluetooth hardware or software development, I have worked in software development in the past and have implemented many large-scale business systems. I get the impression that the real issue with incompatible Bluetooth devices is a combination of three factors:
  1. Poorly defined standards that permit interpretation rather than demand adherence
  2. Individual deployments including manufacturer-specific "extensions" to provide additional functionality that result in incompatibility in certain circumstances
  3. Sloppy coding and/or testing
This is a common and endemic problem in the modern IT industry and one that damages the end-users faith in technology :nono Lessons must be learned.

Ahh... I feel better now :bounce1
 
Ty, very interesting that you have a bluetooth problem as well. I have posted various things about the problems I have being experiencing with a BMW Nav 3 and its inability to work with the Dainese Airstream lid.

Garmin Europe were on the case with this but I understand it has since been sent back to the states for them to dela with as they can not figure why the Zumo (allegedly) works and the 2820/Nav 3 does not.

Im told its likely that a firmware update will dela with the issue but I have no timescales.

Having bought my 2820 in the form of a BMW Nav 3 and paid a handsome premium for it, I am very unhappy with the current situation. To my knowledge only the system 5 bluetooth lid works with the Nav 3 and there are major problems with the bluetooth product in that as well.

One of the main reasons I bought the Nav 3 was because of the wireless benefits, I would not have bought the prodcut knowing what I know now. Also dare I say but I think the 2820 and the Nav 3 are currently being miss sold.
 
Where would i stand with my consumer rights if i was to ask for a refund on my Garmin 2820/Nav111 i have had it three months & i emailed garmin two months ago complaining about the bluetooth issues & still no fix, the sales literature & the product manual state it will work with any compatible bluetooth headset but clearly it does not, a new one would also be the same so the product is technically faulty & they cannot fix it within a reasonable timescale as they have proved, am i wasting my time trying to get a refund ?I am now very slightly annoyed :spitfire

Thanks Leman
 
leman said:
Where would i stand with my consumer rights if i was to ask for a refund on my Garmin 2820/Nav111
I suspect that the key phrase in the rest of your quote is "the product manual state it will work with any compatible bluetooth headset". So what, exactly, does "compatible" mean in this instance? Does it mean it will work with any device that complies with an internationally recognised standard, or a device that complies to a standard chosen by Garmin? Or just a device that works (and is therefore demonstrably "compatible") with the 2820?

Under the UK's Sale of Goods legislation your rights are against the retailer, not the manufacturer - so that's where you'll need to start. But expect a long haul, because the retailer will almost certainly require that the manufacturer "test" the product (as they themselves are unable to) and I suspect it would be found to be working fine "with a compatible bluetooth headset". It'll then be up to you to prove that your headset meets an appropriate, recognised, Bluetooth standard and that the claims of "compatibility" are therefore incorrect.

Sorry to paint such a dark picture, and I completely understand your anger, but I suspect that this is one of those cases when asking nicely for a mutually acceptable solution to the problem may provide a more effective path than "demanding your rights".
 


Back
Top Bottom