[gps-talkusers] Re: uggestions
- From: "don bishop" <w6smb@xxxxxxxxxxxxx>
- To: "gps-talkusers@xxxxxxxxxxxxx" <gps-talkusers@xxxxxxxxxxxxx>
- Date: Mon, 08 May 2006 18:02:05 -0700
Hi Robert,
I know this is probably obvious, but since I've tripped over the obvious
things myself more than once maybe somebody else does too. <smile>
AFter you first turn on the MPower you need to wait 5 to 10 seconds for
bluetooth to start up, even if you had it on when you shut down the MPower.
Based on some other bluetooth devices I have around here, I'll bet the same
holds true for the Holux.
So, be sure you leave that little extra time before you attempt to start gps.
If you're already doing this then maybe someone else such as Carl will have
ideas.
Don
On Mon, 08 May 2006 16:51:44 +1200, robert stigile wrote:
Hello all,
I am looking for some suggestions for a problem I seem to have.
I cannot seem to keep the pairing with my Holux receiver.
I thought that once it was paired, all I would have to do, is
turn on the receiver and the braillenote, press n and then g.
Well, if I do that, it says bluetooth not detected.
I either have to go to the bluetooth connection, and pair the
receiver everytime I turn it on, or at least, go to the bluetooth
settings, and activate activesync.
I was told that I might want to try reinstalling keysoft, and I
did this, and it did not help.
I had performed a reset, so I knew I had to go and repair, so I
did this, and had the gps working great. So, then about 2 hours
later, I turned the braillenote on, pressed n and then g,
thinking it would just go into the gps menu, but it told me that
bluetooth was not detected, so I tried going to the connections
and said no to search for bluetooth and then I pressed enter on
activesync, and went back to the gps menu, and it still said
bluetooth not detected, so I had to go back to the bluetooth and
pair it.
If anyone has any suggestions as to how I can fix this, I would
very much appreciate it.
Thanks,
Robert
__________ NOD32 1.1525 (20060508) Information __________
This message was checked by NOD32 antivirus system.
http://www.eset.com
Other related posts: