Speech choppy in CoPilot 6

Weetobix · Occasional Visitor Joined: Feb 17, 2006 Posts: 2

Hey everyone
I've just got CoPilot 6 installed on my MDA Vario. Everything seems to work fine, but the speech is very choppy, ie. breaking up.
Does anyone else have this problem or know how to fix it?

Thanks

Weet

PONDEROUS · Posted: Fri Feb 17, 2006 6:53 pm Post subject:

I don't know if you are using bluetooth, Weetobix.

I use bluetooth audio devices and I get a problem similar to the one you describe on my Dell Axim X30, but not on my X50v.

I am trying to find time to see if it is a new ROM that I installed on the X30 (I can't remember if I had the problem before) as Dell's bluetooth gateways tend to be problematic. Is it possible that the MDA vario has similar issues?
_________________
Dell Axims X50v & X30 (both WM 2003 2nd Edition). Copilot BTGPS3 and Fortuna Clip-on BT receivers. Jabra BT 250 audio headsets. Welltech 40032/AF32 BT handsfree audio. Copilot 6.0.4.110. TomTom Navigator 5.21. MS Autoroute/Pocket Streets 2005

Weetobix · Occasional Visitor Joined: Feb 17, 2006 Posts: 2

i use bluetooth to connect to the gps reciever but not for anything else

PONDEROUS · Posted: Fri Feb 17, 2006 10:40 pm Post subject:

That's worth knowing. Maybe it isn't bluetooth, then.
_________________
Dell Axims X50v & X30 (both WM 2003 2nd Edition). Copilot BTGPS3 and Fortuna Clip-on BT receivers. Jabra BT 250 audio headsets. Welltech 40032/AF32 BT handsfree audio. Copilot 6.0.4.110. TomTom Navigator 5.21. MS Autoroute/Pocket Streets 2005

alix776 · Posted: Fri Feb 17, 2006 10:47 pm Post subject:

it dose it in smartphone to on a regular basis
_________________
currently using aponia truck navigation on windows phone. Good bye IOS don't let the door hit you on the way out .

Oh the joys of being a courier.
device Lumia 950 xl

PONDEROUS · Posted: Fri Feb 17, 2006 11:37 pm Post subject:

Presumably no bluetooth involved in your Smartphone setup, Alix?
_________________
Dell Axims X50v & X30 (both WM 2003 2nd Edition). Copilot BTGPS3 and Fortuna Clip-on BT receivers. Jabra BT 250 audio headsets. Welltech 40032/AF32 BT handsfree audio. Copilot 6.0.4.110. TomTom Navigator 5.21. MS Autoroute/Pocket Streets 2005

alix776 · Posted: Fri Feb 17, 2006 11:41 pm Post subject:

nope just bt for gps and lots of crashes
_________________
currently using aponia truck navigation on windows phone. Good bye IOS don't let the door hit you on the way out .

Oh the joys of being a courier.
device Lumia 950 xl

PONDEROUS · Posted: Sat Feb 18, 2006 12:23 am Post subject:

Alix, thanks; that's what I thought. I suppose what hardware is in use is relevant, as it doesn't happen on all PDAs. Also, I don't remember it on either of mine with CP 5.
_________________
Dell Axims X50v & X30 (both WM 2003 2nd Edition). Copilot BTGPS3 and Fortuna Clip-on BT receivers. Jabra BT 250 audio headsets. Welltech 40032/AF32 BT handsfree audio. Copilot 6.0.4.110. TomTom Navigator 5.21. MS Autoroute/Pocket Streets 2005

alix776 · Posted: Sat Feb 18, 2006 2:05 am Post subject:

cp5 smartphone was much more stable and crashed alot lessi cant even plan a rout over 100miles on cp6 at the moment
_________________
currently using aponia truck navigation on windows phone. Good bye IOS don't let the door hit you on the way out .

Oh the joys of being a courier.
device Lumia 950 xl

H_O_D · Occasional Visitor Joined: Jan 13, 2006 Posts: 12

I have the same setup as yourself only the O2 variant of the K-JAM (XDA mini S).

I very occasionally get the breakup of the text to speech, but not enough to annoy me. I think this was slightly worse on the T-mobile "tweaked" version of Windows Mobile (as I briefly had their package).

One tip I've discovered myself - make sure nothing else is running before starting up CoPilot! I've even re-assigned my "Explorer" button as a shortcut to Task Manager in order to make this easier. Do an "end task" on everything before you start CoPilot. It seems to be more reliable (or less UN-reliable?) if you do that.

I don't know if this is a quirk of my setup but I often find that "Active Sync" has started ITSELF and possibly there is some conflict between that and CoPilot?

One other "quirk" I've found (that you might be able to confirm as you have the same setup?) If I've had bluetooth DISABLED, start up CoPilot (which obviously then can't detect the GPS device) and only THEN load Comm Manager to start bluetooth, Comm Manager will fail to start bluetooth and more than likely hang the PPC! Not much good when you're already driving! Sad

Another reason it's useful to have that shortcut to Task Manager! ;)

	PocketGPS
	Web