Hi all
First post, so be gentle with me
I am running CoPilot Live 8 on my HTC Desire, and it works really well for actually getting from A to B, but amongst the small list of annoyances with this app is that the audio output from the app doesnt switch to using the headphone socket when they are being used, and keeps using the speaker on the rear of the phone.
I usually drive with the desire in a screen mounted holder, using an "iTrip" device to play MP3 from the phone through my radio, so anything that comes out of the onboard speaker (a) stops the music playback by switching to speaker only for the duration, and (b) is being drowned out by the noises in a moving car.
The other navigation apps I have tried all work fine through the headphone->iTrip system (Google Navigate, Navigon), so is this just a case of ALK coders not knowing the Android system as well as they should, or shoddy coding, or a straighjt port from iPhone version, or just a bug for the first android release of the app? Anyone found this issue to be just a little annoying?
ALK email support is notoriously poor from what I read from other CoPilot users, but I sent a feature request / bug report to them anyway (no response, not even a "yes, we are aware" or "thanks for letting us know").
First post, so be gentle with me
I am running CoPilot Live 8 on my HTC Desire, and it works really well for actually getting from A to B, but amongst the small list of annoyances with this app is that the audio output from the app doesnt switch to using the headphone socket when they are being used, and keeps using the speaker on the rear of the phone.
I usually drive with the desire in a screen mounted holder, using an "iTrip" device to play MP3 from the phone through my radio, so anything that comes out of the onboard speaker (a) stops the music playback by switching to speaker only for the duration, and (b) is being drowned out by the noises in a moving car.
The other navigation apps I have tried all work fine through the headphone->iTrip system (Google Navigate, Navigon), so is this just a case of ALK coders not knowing the Android system as well as they should, or shoddy coding, or a straighjt port from iPhone version, or just a bug for the first android release of the app? Anyone found this issue to be just a little annoying?
ALK email support is notoriously poor from what I read from other CoPilot users, but I sent a feature request / bug report to them anyway (no response, not even a "yes, we are aware" or "thanks for letting us know").