Guys,
The wife is having problems getting the above to work properly. The setup is as follows
* Zumo 500 connected to Scala G4 using cable
* Both Zumo and the G4 are on latest software
* iPhone paired with Zumo
* Zumo paired with G4 and set to use Bluetooth for "Phone only"
When she first turns everything on it connects OK. The Zumo connects to both the G4 and the iPhone. She can play music from the Zumo which goes to the G4 via the cable. This works fine.
Now for the problem:
When she receives her 1st call it displays the incoming call alert on the Zumo. When she answers it everything works OK (music pauses, Scala rings etc).
If she then receives another call the phone handset rings, but there's no incoming call display on the Zumo and the G4 doesn't produce an incoming call alert. The Zumo does, however, pause her music. There is then no way to answer the call. This then gets the Zumo stuck in the situation where it thinks that she's on a call but she isn't, and so she can't get back any navigation or music without rebooting the Zumo and sometimes the G4 too.
The same also happens when making a call. The 1st call goes through fine. When she makes a second call using the Zumo it pauses the music, but then goes back to the navigation screen. It doesn't, however, display the phone icon on the display that you normally get when on a call. Again there's no way out of it except by rebooting the Zumo. The Zumo also sometimes comes up and says "Phone disconnected", but the iPhone still shows the Zumo as connected. The Zumo then also sometimes also disconnects at the same time from the G4 and a reboot of the G4 is required too.
I hope all that was easy to understand as it isn't that easy to explain in detail. The summary is 2nd call (in or out) causes Bluetooth stack on the Zumo to get all confused and requires a reboot. Sometimes a reboot of the G4 is also required.
I also had the same setup with the exception that mine was a Zumo 550 and had similar issues, but I've since traded up to a Zumo 660 to eliminate the cable which the 500 and 550 need for stereo music. I also sold the 550 so don't have it available to test.
Anyone any ideas? Scala says it's Garmin's problem and Garmin say it's Apple's or Scala's problem. Interestingly enough neither of us had this problem on the old bikes which the Zumos where previously installed on, but used an Autocom instead of the G4s.
Thanks
Dae.
The wife is having problems getting the above to work properly. The setup is as follows
* Zumo 500 connected to Scala G4 using cable
* Both Zumo and the G4 are on latest software
* iPhone paired with Zumo
* Zumo paired with G4 and set to use Bluetooth for "Phone only"
When she first turns everything on it connects OK. The Zumo connects to both the G4 and the iPhone. She can play music from the Zumo which goes to the G4 via the cable. This works fine.
Now for the problem:
When she receives her 1st call it displays the incoming call alert on the Zumo. When she answers it everything works OK (music pauses, Scala rings etc).
If she then receives another call the phone handset rings, but there's no incoming call display on the Zumo and the G4 doesn't produce an incoming call alert. The Zumo does, however, pause her music. There is then no way to answer the call. This then gets the Zumo stuck in the situation where it thinks that she's on a call but she isn't, and so she can't get back any navigation or music without rebooting the Zumo and sometimes the G4 too.
The same also happens when making a call. The 1st call goes through fine. When she makes a second call using the Zumo it pauses the music, but then goes back to the navigation screen. It doesn't, however, display the phone icon on the display that you normally get when on a call. Again there's no way out of it except by rebooting the Zumo. The Zumo also sometimes comes up and says "Phone disconnected", but the iPhone still shows the Zumo as connected. The Zumo then also sometimes also disconnects at the same time from the G4 and a reboot of the G4 is required too.
I hope all that was easy to understand as it isn't that easy to explain in detail. The summary is 2nd call (in or out) causes Bluetooth stack on the Zumo to get all confused and requires a reboot. Sometimes a reboot of the G4 is also required.
I also had the same setup with the exception that mine was a Zumo 550 and had similar issues, but I've since traded up to a Zumo 660 to eliminate the cable which the 500 and 550 need for stereo music. I also sold the 550 so don't have it available to test.
Anyone any ideas? Scala says it's Garmin's problem and Garmin say it's Apple's or Scala's problem. Interestingly enough neither of us had this problem on the old bikes which the Zumos where previously installed on, but used an Autocom instead of the G4s.
Thanks
Dae.
