| Author |
 Topic  |
|
|
kevin2
Member
6 Posts |
 Posted - 07/23/2003 : 6:38:05 PM
|
I have been using Ipaq3975 and Socket BT GPS (Mynavigator GPS software) for 6 months. They both worked very well.
Recently I upgraded my Ipaq to new model 5555, and couple days ago, I just found there is a big problem with this set up: Ipaq 5555 + Socket BT Receiver + Any GPS applications
Here is the problem : First, just open up GPS application on my ipaq, and get connect as usual. Once the Ipaq ( 5555 or 2125 )get the signal from the GPS receiver, now go ahead power off the Ipaq without closing the GPS application on your Ipaq. Wait for few seconds, power up the Ipaq by hit the power button. You will find a big SUPRISE, it FAILS to power up, it is just black screen, there is no power led on, the only thing I can do is soft reset the Ipaq or pop out the battery.
I called HP for this issue, they refused to resolve, and point their finger to GPS software manuafacturer.
Can Socket take a look into this problem please ?
thanks
Kevin
|
|
|
kmalley
Member
5 Posts |
Posted - 07/24/2003 : 3:48:00 PM
|
| My 2215 does the same thing and it drives me nuts. |
 |
|
|
kevin2
Member
6 Posts |
Posted - 07/25/2003 : 09:00:45 AM
|
Socket techincal support please respond to this problem.
thanks |
|
|
|
PatrickLi
New Member
2 Posts |
Posted - 07/25/2003 : 9:51:00 PM
|
| I have same problem with iPAQ5555 and Nav Kit. I wonder there is no reply here with a solution |
|
|
|
sfhub
Senior Member
24 Posts |
Posted - 07/27/2003 : 7:11:39 PM
|
It's probably a Bluetooth driver issue on HP side. I had a similar
problem with Socket CF BT drivers on my Audiovox Maestro that were
fixed in a later version.
I have a IPAQ 2210 sitting in box so I'm not looking forward to
discovering the same thing you folks have, standby problems and
losing BT connection every few minutes.
IPAQ 2210/2215 is a very popular PPC and more people are going to see
these problems. Either Socket or HP needs to start taking a look at
it. I think if you are persistent you'll eventually get beyond the
pointing finger stage. Try calling Socket support. I don't think
these forums are considered official support so I wouldn't expect an
official response, but if you get one, all the better.
|
|
|
|
dynamius
New Member
1 Posts |
Posted - 07/27/2003 : 9:09:30 PM
|
it seems to be a problem with the my navigation software. if you connect to the socket gps through bluetooth manager, not having loaded my navigation software whatsoever, it will turn back on. it is only when my navigation is open that it doesn't seem to wanna turn back on. i've had an instance where the my navigation froze when it didn't detect the gps receiver, but when when i turned back on the receiver, it un-froze and all went back to normal.
if i were to point any fingers, i wanna say it's socket, although it working in conjunction with bluetooth may have something to do with it. |
|
|
|
kmalley
Member
5 Posts |
Posted - 07/28/2003 : 07:45:14 AM
|
| It's not the software, since my 2215 does it with both mapopolis and the other software I use to do farming with GPS. I don't know if being persistent will do any good, since no one from tech support ever seems to respond to this forum |
|
|
|
sfhub
Senior Member
24 Posts |
Posted - 07/28/2003 : 12:39:01 PM
|
I finally broke out my 2210 and tried Mapopolis + Socket BT GPS.
I haven't been seeing the periodic loss of BT connection to GPS
problem someone else mentioned, but I haven't tested for longer
periods of time.
I definitely do see the shutdown without exiting BT app lockup problem
with Socket BT GPS + Mapopolis v3.25
It's looking like HP BT drivers since the problem occurs with
multiple hardware software combinations.
1) Socket BT GPS + My Navigator
(from this thread)
2) Socket BT GPS + Mapopolis
(my experience)
3) Globalsat BT GPS + Routis
http://discussion.brighthand.com/showthread.php?s=&threadid=85192
3 different software and 2 different hardware, scales are tipping
towards HP.
Also, I've seen the similar problem with Socket CF BT + Socket BT GPS
+ Mapopolis drivers, which was fixed in later version of Socket CF BT
drivers. This was on my old Audiovox Maestro. So it is certainly
possible for BT drivers to cause this behavior.
We just need to be persistent in communicating with Socket and HP
support until someone at HP admits and fixes the problem (if they
haven't done so already) Sometimes going through first line support
at HP as an enduser results in runaround, and Socket can get more
progress going through their developer channels. |
Edited by - sfhub on 07/28/2003 12:40:50 PM |
|
|
|
kevin2
Member
6 Posts |
Posted - 07/28/2003 : 1:18:20 PM
|
I do not have to worry about this problem anymore, because ipaq5555 had been returned back to the store. I am quite happy with the combination 3975 + BT socket.
After expiriencing with going through tech support from both HP and Socket, I found out most of technical supports are useless, they did very good job on refering users to third party software vendors, instead of listening the feedback, and those feedbacks are free of charge from their customers.. 1 of the stupid and stuck up HP tech support in higher level told me this " Sir, at this point I refused to try duplicate the problem that you have, because it is issue of compatibility issue between 2002 and 2003 OS, i refer you to talk with microsoft or Socket... If you are not happy with the unit, you can go ahead return it to the store.. "
Sure, I did what you want me to, and please remmeber loosing 1 customer will contribute a small part of loosing your job as well.
Kevin |
|
|
|
sfhub
Senior Member
24 Posts |
|
|
kevin2
Member
6 Posts |
Posted - 07/28/2003 : 3:20:35 PM
|
Here is responding email from Socket tech support, that i just received regaring for this issue
Hello,
WOW! I have not heard this problem before. Does this only happen with
MyNavigator or with other GPS navigation software as well? We do not
have
a 5555 to test with nor do I know when we can get one so testing may
not
happen right away. Does this happen if you disconnect before powering
down? Can you test with other software? Here is a link to a demo
version
of Mapopolis:
http://www.mapopolis.com/downloadppc.jsp?s=1059427512171229&p=&q=27179.638
527585583
Give that a try and see if it reacts the same way. This is not a
problem
with any of the devices we have so it does not seem like a GPS software
issue. Could this have something to do with the Bluetooth manager? Do
you
have any other Bluetooth devices you can test with like a cell phone?
Try
a similar process to see if it does the same thing.
I will notify the product manager about this issue so we can hopefully
get
a device to test with. Let me know what your results are.
Thank you,
Mario Mancia
Socket Communications Technical Support
**************************************************
If there is no reply to this email message within 7 business days we
will
assume that your problem has been resolved and we will close this
incident
report. You can view a history of support incidents by logging in to
our
support page with your username and password and selecting 'submit a
problem' under technical support.
**************************************************
|
|
|
|
elvis
New Member
2 Posts |
Posted - 12/08/2003 : 08:10:34 AM
|
I have the same problem to my iPAQ 2215. But, I've found a solution for myself is whenever I exit the GPS application, I have to go to "File" and click on "Exit". By doing this way, I won't get the "black out" problem any more.
|
|
|
|
XPMCE
New Member
1 Posts |
|
|
johnd
Mobility Advocate
USA
1602 Posts |
Posted - 02/24/2004 : 11:09:20 AM
|
All,
Just a quick note of clarification. The problem initially posted is based upon the crashing, or more accurately the halting, of the Widcomm stack when the device is powered off and an active Bluetooth connection was in progress. I have duplicated this several times on my HP iPAQ 2200 series and my 5450 devices. The halting of the device with an active Bluetooth connection in progress is the root of the issue and not the GPS receiver (Socket's or any other) since the Pocket PC is the MASTER of the connection and ended the communication.
Has anyone tested the new ROM on this issue?? Has anyone checked for the same problem when in a GPRS session with their mobile??
Thanks in advance for any posting. 
Regards. |
John Doub
Mobility Advocate
-----
No affiliation with Socket
-----
No longer here folks... |
|
|
|
ldantzler
New Member
2 Posts |
Posted - 02/24/2004 : 2:34:24 PM
|
--------------------------------------------------------------------------------
I have a 2215, and just got the Socket Bluetooth GPS. My laptop was able to immediately connect with the unit, and the DeLorme software recognized it. My ipaq however will recognise the unit, and I can pair using the 0183 passkey. The software will not recognize the GPS unit, even though it shows up. I have the latest ipaq rom (1.01) and the nov'03 bluetooth patch applied. When I look at the paring screen, it indicates a good signal, however there is no data being recieved.
any ideas 0 bytes sent, 0 bytes recieved?
|
|
|
|
johnd
Mobility Advocate
USA
1602 Posts |
Posted - 02/25/2004 : 2:29:45 PM
|
ldantzler,
Are you connecting to the GPS through COM8?? The HP iPAQ family uses COM8 for MASTER connections to other devices. The SLAVE mode is either COM5 or COM7. These COM ports are not configurable and your application must allow you to select COM8 to connect to the GPS.
Regards. |
John Doub
Mobility Advocate
-----
No affiliation with Socket
-----
No longer here folks... |
|
|
|
hackerr
New Member
4 Posts |
Posted - 05/04/2004 : 06:01:12 AM
|
How do you check the com port settings in pocketpc. I am having the same issue with a hp5555. It is paring and doing all the bluetooth stuff but no transmission of data.
I can also do the autosyn in my navigator but no communicatiion.
Zaf |
|
|
|
hackerr
New Member
4 Posts |
Posted - 05/04/2004 : 08:16:13 AM
|
| I have noticed that the incoming port is com 5 and outgoing is com 8. I cannot change the incoming to 8 for some strange reason |
|
|
|
hackerr
New Member
4 Posts |
Posted - 05/04/2004 : 1:23:37 PM
|
I have a partial fix. Each time that I want to start My nav. I have to do a reset of the unit(ipaq) then it will work until I shut off the unit and then I have to do a reset once again to start.
Would the fix for the 2200's also work on the 5555 or is it a diffent fix for a different issue.
|
|
|
|
cholcomb
New Member
USA
2 Posts |
Posted - 05/08/2004 : 4:19:29 PM
|
It is the software. This sounds very fimiliar to the problem I am having with my XDA 2 running WM2003. I upgraded my rom that supports the bluetooth serial connection and every since then, the MyNavigator software will start up just fine until I change the serial port to com 5 and it locks up the system. If I turn off the gps and wait about 5 minutes then the system comes back and works fine.
On the same note I can launch my Teletype GPS Software using the socket Bluetooth GPS and every thing works fine. This is with out a doubt a software issue. |
|
|
| |
Topic |
|
Topic Locked
