Goose
Registered user
This is the method I use.
The Zumo's phone handling capability is very nice for gloved use, that's why it's a pity we cannot get it to work properly.
I can't be heard when using Bluetooth
- Thread starter Cornwallis
- Start date
This is the method I use.
The Zumo's phone handling capability is very nice for gloved use, that's why it's a pity we cannot get it to work properly.
Looks like a call to Garmin again
Has anyone got to the bottom of this issue, I have a 550 with an autocom pro duo (i think) and the phone used to work fine but now the caller cannot hear me but I can hear them clearly.
As per the other posts
rider to pillion works fine
I can hear my own voice in the speakers
VOX works perfetly etc etc
BTW the Zuno is hard wired to the autocom for music and directions and bluetoothed for phone.
Everything did work but now its stopped, my gut feeling is it is the Zumo???
As per the other posts
rider to pillion works fine
I can hear my own voice in the speakers
VOX works perfetly etc etc
BTW the Zuno is hard wired to the autocom for music and directions and bluetoothed for phone.
Everything did work but now its stopped, my gut feeling is it is the Zumo???
APW
Registered user
had a similar problem with my iphone......could not be heard while making a call
solution:
I re-connected the sat nav to the phone input of the starcom/autocom not the sat nav connection of the starcom/autocom.......sounds wrong I know but it works for me
solution:
I re-connected the sat nav to the phone input of the starcom/autocom not the sat nav connection of the starcom/autocom.......sounds wrong I know but it works for me
Mines the same
Music perfect nav perfect but the caller cant hear me for crap, im using an Iphone 3gs with an autocom pro 7, phone connected via bluetooth, useless
Music perfect nav perfect but the caller cant hear me for crap, im using an Iphone 3gs with an autocom pro 7, phone connected via bluetooth, useless
Mine was like this and it would drop bits of both the call and rining tone completely, until yesterday when I did a hard reset of the Zumo and much to my suprise, it appears to have fixed the problem. I've only tried it in the car so far but my wife reported that she could hear me clearly.
Goose
Registered user
I had a response from the Starcom agents who suggested
"turn the volume of the phone down before connecting via bluetooth..."
sorry for being ignorant, but in my 30 years of working as an electronics engineer............... I have yet to discover how the speaker volume of the phone (which is the headphone bit - not the mic and should have no affect on the sensitivity of the Mic) would influence the sensitivity of the Mic in one's helmet that's actually hard-wired to the ZUMO's Mic input?
maybe I'm too old................
or is this just the BEST twaddle you've heard?
"turn the volume of the phone down before connecting via bluetooth..."
sorry for being ignorant, but in my 30 years of working as an electronics engineer............... I have yet to discover how the speaker volume of the phone (which is the headphone bit - not the mic and should have no affect on the sensitivity of the Mic) would influence the sensitivity of the Mic in one's helmet that's actually hard-wired to the ZUMO's Mic input?
maybe I'm too old................
or is this just the BEST twaddle you've heard?
andyclift
Registered user
THE ANSWER
I had exactly this problem. My phone worked OK with a 550 but not with a 660. A quick call to Autocom (before the Starcom takeover) and I was immediately told they had discovered an undocumented change in the electronics in the 660 which meant the GPS isolator Version 2 (which I had) was the cause of the problem.
They offered to change it FOC for a Version 3 and a couple of days later and a V3 installed everything works perfectly.
So if your isolator has a sticker on it saying V2 that is probably the culprit.
I use a Blackberry 9000 BTed to the 660 and a basic Autocom Logic hardwired to the Zumo with the GPS adapter. Everything works including phone book download and voice dialling via my helmet.
I had exactly this problem. My phone worked OK with a 550 but not with a 660. A quick call to Autocom (before the Starcom takeover) and I was immediately told they had discovered an undocumented change in the electronics in the 660 which meant the GPS isolator Version 2 (which I had) was the cause of the problem.
They offered to change it FOC for a Version 3 and a couple of days later and a V3 installed everything works perfectly.
So if your isolator has a sticker on it saying V2 that is probably the culprit.
I use a Blackberry 9000 BTed to the 660 and a basic Autocom Logic hardwired to the Zumo with the GPS adapter. Everything works including phone book download and voice dialling via my helmet.
Goose
Registered user
I bought my Zumo 660 as a pre-order from Handtec in the UK in May 2009, it was one of the first batches released, so without checking the isolator I would assume it's one of the earlier versions.......
erm............. is this the isolator on the Zumo or the Autocom......
The info is indeed really appreciated and I'll try follow up on that route!
bluetooth
Hi,
I too am having the same problem as you,have even changed my autocom.
What i have found is that if i unplug the mic lead at auto com via the red filter box connection B, then i can use the phone, but with only a little voice coming from me,have tried all the aux holes still no joy.sat nav works fine music also just the dam phone.One other thing left is to change phone,the one am using now is a LG arena.seems not right that by disconnecting the mic lead it still all works.why have the lead in the first place??
Mine is where the ABS would be, so it looks like it's just a rubbish system. I'm going to power it from another 12v supply and try again (mine is perm live from battery too). If not it's not fit for purpose!
Hi,
I too am having the same problem as you,have even changed my autocom.
What i have found is that if i unplug the mic lead at auto com via the red filter box connection B, then i can use the phone, but with only a little voice coming from me,have tried all the aux holes still no joy.sat nav works fine music also just the dam phone.One other thing left is to change phone,the one am using now is a LG arena.seems not right that by disconnecting the mic lead it still all works.why have the lead in the first place??
I bought my Zumo 660 as a pre-order from Handtec in the UK in May 2009, it was one of the first batches released, so without checking the isolator I would assume it's one of the earlier versions.......
erm............. is this the isolator on the Zumo or the Autocom......
The info is indeed really appreciated and I'll try follow up on that route!
Same question realy as Goosepilt and me both have the Starcoms
andyclift
Registered user
I thought my post was clear - it's the Autocom Isolator. Can't remember part No. and bike is not with me so can't check.
RichyEstonia
Registered user
Mine Now Works
I have full checked my Starcom out and all is working now.
The Zumo 550 is now connected to an iPhone via Bluetooth, and the Zumo is connected to the Starcom with Bluetooth, and I can now make calls and be heard. Ended up having to buy a 2nd Bluetooth module to connect the passenger phone!!
The iPhone is hard wired to the music input at the same time, so I get the music directly to the Starcom and it works brilliantly.
I did upgrade the Zumo recently and now a couple of issues more appeared, when I power up the bike the Zumo turns on (connected through the BMW headstock connector) at which stage it doesnt find any bluetooth devices, and even when trying to manually connect it doesnt work, turning just the Zumo off then on again it finds both the phone and the starcom BT.
Also when the nav commands come through they are heard over the music, a few seconds latter after the directions come through the music tuns off for a few seconds, not critical just a bit anoying.
I suspect the Starcom cable to the Zumo is the fault, or noice from the bike when running the cable.
But its working and I can be heard now on the phone......
I have full checked my Starcom out and all is working now.
The Zumo 550 is now connected to an iPhone via Bluetooth, and the Zumo is connected to the Starcom with Bluetooth, and I can now make calls and be heard. Ended up having to buy a 2nd Bluetooth module to connect the passenger phone!!
The iPhone is hard wired to the music input at the same time, so I get the music directly to the Starcom and it works brilliantly.
I did upgrade the Zumo recently and now a couple of issues more appeared, when I power up the bike the Zumo turns on (connected through the BMW headstock connector) at which stage it doesnt find any bluetooth devices, and even when trying to manually connect it doesnt work, turning just the Zumo off then on again it finds both the phone and the starcom BT.
Also when the nav commands come through they are heard over the music, a few seconds latter after the directions come through the music tuns off for a few seconds, not critical just a bit anoying.
I suspect the Starcom cable to the Zumo is the fault, or noice from the bike when running the cable.
But its working and I can be heard now on the phone......
andyclift
Registered user
AndrewD
Check out my earlier post on this. It probably isn't a Garmin problem.
The thread seems to have been hijacked by other issues but going back to the first question which was being heard on a phone using a 660 and an Autocom I had the same problem.
My system worked OK with my older 550 but NOT a 660. Everything else was the same, i.e. no change to Autocom set up. I could hear the satnav instructions and people I called - but they could not hear me.
A call to Autocom (before they went broke) got the answer very quickly. Autocom had become aware that Garmin had made some undocumented changes to the electronics in the 660 which prevented the Autocom satnav isolator working properly(the box you plug the Garmin's ear and mic leads into).
To solve the problem Autocom had redesigned the isolator. If you have a V1 or V2 Autocom isolator IT WONT WORK WITH A 660. Autocom changed my V2 to their new V3 free of charge and the result was everything working as it should. Whether they will do this now it has been taken over by another company, I don't know.
Incidentally, the 660 also has a different flavour of Bluetooth which means that phones that worked OK with a 550 may not work with a 660. For example my Palm worked 100% with the 550 but would not sync the Phone book on a 660 meaning every call had to be dialed. A change to a Blackberry solved the problem, everything works including phone book sync and even voice dialing
Check out my earlier post on this. It probably isn't a Garmin problem.
The thread seems to have been hijacked by other issues but going back to the first question which was being heard on a phone using a 660 and an Autocom I had the same problem.
My system worked OK with my older 550 but NOT a 660. Everything else was the same, i.e. no change to Autocom set up. I could hear the satnav instructions and people I called - but they could not hear me.
A call to Autocom (before they went broke) got the answer very quickly. Autocom had become aware that Garmin had made some undocumented changes to the electronics in the 660 which prevented the Autocom satnav isolator working properly(the box you plug the Garmin's ear and mic leads into).
To solve the problem Autocom had redesigned the isolator. If you have a V1 or V2 Autocom isolator IT WONT WORK WITH A 660. Autocom changed my V2 to their new V3 free of charge and the result was everything working as it should. Whether they will do this now it has been taken over by another company, I don't know.
Incidentally, the 660 also has a different flavour of Bluetooth which means that phones that worked OK with a 550 may not work with a 660. For example my Palm worked 100% with the 550 but would not sync the Phone book on a 660 meaning every call had to be dialed. A change to a Blackberry solved the problem, everything works including phone book sync and even voice dialing
Thanks, that prompted me to look again on Starcom's website as they have brought out Autocom.........Guess what they now have?
A 'new' Zumo lead
UPDATE
Just rang Starcom and they suggest installing 3.8 on the 660 as it has improvements to the mic output, Woo-Hoo new set of 'undocumented features' to sort out!
