Message from discussion
configure bluetooth GPS
Received: by 10.35.83.18 with SMTP id k18mr279651pyl.1170475906490;
Fri, 02 Feb 2007 20:11:46 -0800 (PST)
Received: from 68.100.79.49 by h3g2000cwc.googlegroups.com with HTTP;
Sat, 03 Feb 2007 04:11:45 +0000 (UTC)
From: "eva...@gmail.com" <eva...@gmail.com>
To: "Google Mobile Help Group - Google Maps for mobile" <Google-Maps-for-mobile@googlegroups.com>
Subject: Re: configure bluetooth GPS
Date: Sat, 03 Feb 2007 04:11:45 -0000
Message-ID: <1170475905.320259.246290@h3g2000cwc.googlegroups.com>
In-Reply-To: <1170459942.908210.266980@s48g2000cws.googlegroups.com>
References: <1170455852.324710.257980@v33g2000cwv.googlegroups.com>
<1170459707.630996.109770@a34g2000cwb.googlegroups.com>
<1170459942.908210.266980@s48g2000cws.googlegroups.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727),gzip(gfe),gzip(gfe)
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
I have this same problem with my 8525 and a holux bluetooth GPS.
GPS works fine with other applications, but not with Mobile Maps.
My _guess_ is that mobile maps is hard coded to read from 1 specific
com port (which the docs dont tell you what it is) If you have the
time and patience, you could try setting up your bluetooth on all of
the com ports and see if it will work on any of them. I can tell you
com9 wont work. Personally Ill just use Virtual Earth mobile until
its fixed.
On Feb 2, 6:45 pm, hrlaser wrote:
> On Feb 2, 3:41 pm, hrlaser wrote:
>
>
>
> > Again, these are both current model SiRF Star II GPS receivers.
>
> Sorry, typo, I meant to say SiRF Star III GPS receivers. Current new
> models
>
> Thanks
|
