Has anybody managed to get the smartpad 2E working with xda? wwwsiibusinessproducts.com
i got it working with the xda2 with out a problem
I have a Seiko InkLink, which works fine with the PCA over USB, but I can't get the infra-red clip-on to work with the XDA2.
I've gone to connections and made sure that "Receive Incoming Beams" was checked, and I've fooled around with changing the COM ports (which one is it supposed to be?), but aside from that, can't think what else to do. Anyone any ideas?
Oh, and another thing.
When I run the InkLink software, the XDA soft-resets itself after a few minutes. If I don't run the InkLink software, it runs fine, so I strongly suspect the software isn't quite right.
This is all on the XDA2. I haven't tried with XDA1. Maybe its a WM2003 thing?
i have the same problem. it works with the desktop but not the xda2.
The ir lights up on the device that clips to the top of the A4pad and the light changes speed when I write but nothing appears on the XDA2 screen. I have tried running the test program but I get a message stating the IR port (i assume it means the XDA2 port) is being used by another program but I dont have anything else running in the background.
receive beam is turned on - i have tried it both on and off. My XDA2 has reset itself a couple of times since installing the software - so i have given up and removed it.
i wonder if there is another program installed that is effecting things.
any clues ?
There is something screwy about the irda on the xda1 and the xda2, if you install tomtom2 on the ipaq and look for the ports available, you see the com ports and also generic infrared port, I have an infrared adaptor which allows me to use gps on ipaq 1910 which doesnt have a serial port, however trying to do the same with xda, all thats offered is infrared port, choose that and the machine locks. I wonder if other pda's besides xda1 and 2 allocate the irda to a virtual port. I have asked about this numerous times here on the forum and scoured the web but to no avail.
After various teething problems, it now works flawlessly on my XDA2, and I'm really very impressed.
I've no idea why InkLink was resetting my machine, but I think maybe it was because I had the wrong port selected and it was just picking up rubbish from an unconnected port. Still shouldn't crash, but anyway, it works if you connect to the right port.
Also, I think the batteries they supply with it only last 5 minutes. Having replaced them, my troubles seem to be over.
Only fault is the general hassle factor of the IR clip. If there was a bluetooth version, it would be so much better (provided the bluetooth worked!)
onepieceman said:
After various teething problems, it now works flawlessly on my XDA2, and I'm really very impressed.
Click to expand...
Click to collapse
I'm dying to know how you made it work?
I don't think I did anything specific.
I think the most likely thing was I finally selected the correct COM port. You need to select COM1, and this won't be available if you have something else using that port (such as the "receive beams" application, but maybe you have something else). Just to confirm, "receive beams" must be OFF!
Also, make sure your batteries are OK.
I suggest you get it working first with the InkLink connected via USB to your PC. If that works, then you can be sure that the pen and the InkLink clip work OK. That will then leave the IrDA transmitter, its battery, and the PocketPC hardware/software/config as sources of potential trouble. I can vouch for the software working on an XDA2, so that should just leave the IrDA transmitter and its battery.
Oh, just forgot, I did download the latest version of InkLink from the Seiko site. My version is 3.3, while it came supplied with 3.2. Don't know if it makes a difference, but worth a try. Also, make sure you select InkLink as your hardware. I believe it defaults to SmartPad.
Can't think of anything else you need to do. You certainly don't need to do anything weird.
Related
It is from an HP 6315 from 3/31/05
http://h18007.www1.hp.com/support/files/HandheldiPAQ/us/download/22539.html
I would love to see if we could get this stack and the settings on our XDAII and other HTC devices,,, THAT would be cool.
Bluetooth build 1.0.0.3701:
Corrects inaccurate display of headset icon when a call is in progress.
Adds a check to determine if Bluetooth stack is initialized before accepting messages from phone.
Adds a user interface (UI) change to enable a connected headset to automatically disconnect before attempting to connect to a different headset when the user chooses to connect to a second headset.
Corrects check for invalid device name.
Corrects issue where handheld could not reconnect to remote device after a page timeout.
Corrects Object push profile update so it sends all files.
Updates FTP connection wizard to correct service discovery issue.
Corrects issue with call waiting for incoming call handling while dialing out.
Corrects issue with headset connection icon so it is correctly displayed after power cycling.
Corrects audio to make it compatible with an in-car solution.
Corrects audio issue where the right channel for a headset was unavailable for playing audio and during calls.
Corrects issue where the LED and network status were not properly synchronized.
Corrects issue where the user could not send multimedia messaging (MMS) message.
Hmmmm....a few remarks, correct me if I am wrong:
1. There is already a BT version 1.0.0.3900 available
2. This is not a HTC device, so I doubt the tools developed here will work on it.
HappyGoat said:
2. This is not a HTC device, so I doubt the tools developed here will work on it.
Click to expand...
Click to collapse
This is an HTC device. All HPs are designed by HTC.
Well, even though I don't want to stop progress because I would like to have the ROM taken apart for my own personal reasons, the 6315 was actually made by Compal. Bad move on the part of HP in my opinion. However, the bluetooth stack that was taken from an iMate JAM worked on the 6315 and that is how most survived until the update was released. So it very well could work on the HTC's. On a side note, if someone could point me in the right direction, I will take the ROM apart, just don't know where to start.
mamaich said:
HappyGoat said:
2. This is not a HTC device, so I doubt the tools developed here will work on it.
Click to expand...
Click to collapse
This is an HTC device. All HPs are designed by HTC.
Click to expand...
Click to collapse
Oops....my bad....excuses!
no htc dont make ALL hp's pda's the H5400's was oem'd from LG
and even if the ipaq in question is made by HTC then that dont garentee that the xda tools work as they are not made by HTC
I can tell you now that the XDA tools do not work on that ROM as it stands. However, looking through the HEX, it is laid out a little differently than the XDA ROM's but have some of the same portions, just in different locations. Now if I knew more about what I was looking at, I could take it apart for you. The 6315 uses Widcomm BT and like I stated before the BT drivers ripped from a JAM worked great on the 6315 so I have a feeling the 6315 drivers will work on the XDA's.
I can also tell anyone looking at it that in the first header of the ROM the letters are shifted 13 characters. So when you see RAT it equals ENG and so on. It looks like they don't do that for very long though.
BT
HappyGoat said:
Hmmmm....a few remarks, correct me if I am wrong:
1. There is already a BT version 1.0.0.3900 available
Click to expand...
Click to collapse
BT 3900 and 3500 do not support Hands Free Profile or even Headset Profile on my XDAII.. This is important so people can use Caller ID on a BT device and OR a Car Kit with the Hands Free Profile....
Switching stacks is a pain in the but...
Even so, the only OS that even slightly works with Hands Free on the Himalaya, is 2.20 translated but even that has bugs that makes it very frustrating. The 2005 did have a fully functional BT, even having separate serial ports for each BT device, (like GPS), but the other bugs and the limited memory left over from the useless and unerasable Extended ROM from the other OS made it no good..
With this new ROM, I may be tempted to buy the HP again.. When I first bought one, it was DAM slow and the BT SUCKED!!!
Maybe now it is usable.
I love my Himalaya and it's 128 of built in..
http://www.expansys.com/product.asp?code=PDA2&asource=IMATE
http://www.expansys-usa.com/product.asp?code=PDA2&asource=IMATE
I will just have to keep waiting for one of the above unless someone finds a fix for the BT Hands Free.
So my phone took a **** and did a hard reset on me for the first time in almost a year. Don’t know why – just happened. No biggie.
I took the opportunity to go back to the latest official firmware available (HA_SPCS_13600_112_00140_6601) since I always had trouble connecting to Vision.
Everything went smoothly, so I am running the latest firmware again.
However, I can no longer use any GPS related software.
Usually I would use GPS Speed Sentry and TomTom with COM1, but neither applications "see" the GPS antenna.
Using GPS Speed Sentry I tried every port from COM0 to COM16 without any luck.
Just wondering if anybody has any ideas or suggestions.
Do I need to perform any OS tweaks since I went back to the "older" real firmware?
Thanks!
EDIT: Forgot to mention I'm using a GoMadic cradle with a generic NMEA antenna.
Have you got receive all beams selected for the IrDA? - this clogs up the Serial Com port and will be selected as default when hard reset - Mike
mikealder said:
Have you got receive all beams selected for the IrDA? - this clogs up the Serial Com port and will be selected as default when hard reset - Mike
Click to expand...
Click to collapse
Yes it's on. Does IrDA use COM1 as a "virtual" port of sorts?
I'll turn it off and try it out when I get into my car.
Thanks for the suggestion!
Went down to my car and tried it out with IrDA disabled.
My GPS apps fired up perfectly!
Thanks a million Mike! I wouldn't have figured this one out without your assistance.
I was getting close to going back to the EVDO firmware assuming that would fix the problem, but in all honesty I would have never thought about the IrDA port.
Thanks again Mike! I'm a very happy camper right now.
HeHe - this one has caught me out a few times to be honest, its not something you will forget though now you know! - yes the IrDA does use the same connection as the serial port so if enabled (which it is by default) you get no data, the other one that can screw up this device is when using an external keyboard, so if you ever get one of these for the unit make sure you use the software to control what is using the port - IrDA, External Keyboard or Com Port - Mike
mikealder said:
HeHe - this one has caught me out a few times to be honest, its not something you will forget though now you know! - yes the IrDA does use the same connection as the serial port so if enabled (which it is by default) you get no data, the other one that can screw up this device is when using an external keyboard, so if you ever get one of these for the unit make sure you use the software to control what is using the port - IrDA, External Keyboard or Com Port - Mike
Click to expand...
Click to collapse
Thanks again Mike... You really are a life saver!
I starting looking at BT GPS units as I was getting desperate, but you saved me.
I purchased marbella GB-6205 V2.2 for my dopod900 but pairing problem is encountered.There shows ? in the icon. I'm running out of tips. ROM 1.30.230WWE. Somebody got any advice
Dont really have a tip i just wanted to see what people came up with. I am haveing the same problem with my Gsat 359. My issue is with the 8525 and Wayfinder. im on VP3gs offical wm6. Also having issues with some of the menus looking like half circules but that is more an issue with the software.
For both posts, I think that you have to be more specific, not being able to pair a device might have lots of causes, in example:
- Are you sure that your devices are indeed in pairing mode, having them to enter in pairing mode can be tricky sometimes
- Usually any device in pairing mode within range will be detected by the PDA/phone.
- Sometimes the keyboard applet appears just above the passkey request window not permitting to see it (happens sometimes with my universal), also there are at least two "common" paskeys used for bluetooth devices (this doesn't mean that some more could exist), usually "0000" and "8888".
- Are you sure that both (PDA/phone and bluetooth device) devices work? Try to pair another bluetooth device with your PDA/phone and try to pair your BT device with another PDA/phone; defective items are always a possibility.
- You might even have had success to pair your devices, the problem might be the software, see all the post that To_mT_om have generated because of problems with third parties BT GPSs, verify your software and a very practical way of being sure that everything went ok with the pairing is to install the app that usually all BT GPSs have included, normally a very simple app that displays geodesic coordinates or even raw NMEA info.
- Some PDAs/OSs might have the need to "create" another serial port for the new BT GPS in order to be accessed by the software, also see the other posts for this information.
Do you need more info?
Verify all the possibilities, perform all the test mentioned and then be very specific about the exact problem, most of the best gurus (and I'm not talking about me!) ask for a tough research of the forum's posts before asking for something that might have been already answered, I understand them when they say that it is not funny to answer to the same question (in various flavors) several times.
One last thing, it's holidays time, many people could be missing in these days.
Good luck
got mine up and runnning. My problem was software related. Downloaded software from handango and i just wasnt working right. Went to the manufacture website...wayfinder.com and the new software found my gps with no problem.
We've tended to find that simultaneously restarting the BT GPS and PDA at the same time (and often with a battery removal on the GPS) can solve issues where the GPS simply doesn't want to complete pairing.
When this fails, it's usually software related or a corrupted Bluetooth stack / registry settings on the PDA..
Worst case, hard reset the PDA..
Good luck
Andy
www.pressdigital.com.au
Press Digital Support Team
The device is Holux GPSlim 236. The phone is Hermes. The phone will pair without question on a 6.0 rom, does not matter who cooked it.
It will specifically not pair with 6.1 roms.
I can see the device when scanning for bluetooth devices, i can choose it, it asks me for passcode, but will not accept the "0000" as the passcode. (tried hardware and software keyboards). IF i type in a passcode OTHER than "0000", it appears to pair, i can see the spp slave service and select it, but once the gps software tries to talk with it, it asks to pair again.
Something is definitely different in the pairing process between 6.0 and 6.1.
Any suggestions are greatly appreciated.
Also see thread about it here from the Himelaya:
http://forum.xda-developers.com/showthread.php?t=378103
Thanks,
Rock
Did you select it as a serial port? You have to do this after you pair the device with the phone!
I am not familar with gps units, does it have a pairing mode like a headset? I know with my Plantronics headset, if I let my phone discover it without the headset being in pairing mode, the phone says it pairs with it, but it really doesn't, so I put it in pair mode then turn on bluetooth on my phone and pair up as normal(0000 passkey) and all works fine.
I have exactly the same GPS unit and have no problem pairing it with the probably 15+ WM6.1 roms I have tried.
Try leaving the battery out of the 236 slim for a few minutes and see if that helps. (can't remember is there is another way to reset it)
Bluetooth Pairing with 6.1
In the latest PC Pro magazine in the UK, there is an article on WM 6.1. It says:
"There's another neat feature in WM 6.1, namely that when you try to pair the phone with something like a GPS dongle or hands-free kit that has a fixed PIN, the operating system will cycle through a set of common codes (0000, 1234, 8888 and so on) to try to find the right one."
It goes on to say that there is the potential to get locked out of the pairing if it goes wrong.
I have to say that I have not had any problems pairing with my GPS unit and my car kit, using a number of 6.1 ROMs. Indeed I have seen no evidence of the above software routine trying to pair for me. Possibly, that routine will only appear in the production ROMs, rather than the development ones which we use on XDA Developers.
I had issues with the same device on some roms. I eventually changed BT drivers from WM6 and all went back to normal.
On some WM6.1 roms things went OK though.
Try not using any password when you try and pair it manually.
If it asks would you like to pair your device automatically select no and do it manually.
I was having this problem but WM6.1 does not require a bluetooth passcode for most devices.
mines gps is a holux 240 and i have the same probs
ive mentioned it on a couple of threads, im glad to know im not the only one
im stickin with K's 6 final until this problem gets sorted out
this thread doesnt seem to getting any viewing, so im asking could a mod move this to General Discussion>networking please, it might be sutible there
crusti said:
this thread doesnt seem to getting any viewing, so im asking could a mod move this to General Discussion>networking please, it might be sutible there
Click to expand...
Click to collapse
ummm no, dont move my thread thanks. you can start one over there if you would like.
crusti said:
mines gps is a holux 240 and i have the same probs
ive mentioned it on a couple of threads, im glad to know im not the only one
im stickin with K's 6 final until this problem gets sorted out
Click to expand...
Click to collapse
You are not the only one
I reverted back to the 6.0 and it pairs without issue. I am thinking that alot of these cookers do not pay much attention to the development of bluetooth in some of their roms. Its not like I changed something on the GPS, so something must have happened with the software.... Still investigating. I hope it works on schaps new rom.
miffymiffy said:
Try not using any password when you try and pair it manually.
If it asks would you like to pair your device automatically select no and do it manually.
I was having this problem but WM6.1 does not require a bluetooth passcode for most devices.
Click to expand...
Click to collapse
this method paired my jabra automatically, it didnt even ask if i wanted to do it auto, i juck clicked "pair" and there it was.
When pairing the holux 236 on the other hand, it would ask for a passcode, then reject it if you put in the correct code of "0000". If you canceled it, it would appear in the connected devices list!!, but still ask to pair once the gps application tries to connect. VERY jacked up.
Hissing Syd said:
In the latest PC Pro magazine in the UK, there is an article on WM 6.1. It says:
"There's another neat feature in WM 6.1, namely that when you try to pair the phone with something like a GPS dongle or hands-free kit that has a fixed PIN, the operating system will cycle through a set of common codes (0000, 1234, 8888 and so on) to try to find the right one."
It goes on to say that there is the potential to get locked out of the pairing if it goes wrong.
I have to say that I have not had any problems pairing with my GPS unit and my car kit, using a number of 6.1 ROMs. Indeed I have seen no evidence of the above software routine trying to pair for me. Possibly, that routine will only appear in the production ROMs, rather than the development ones which we use on XDA Developers.
Click to expand...
Click to collapse
Did that article describe any way of disabling that feature? That functionality could easily trick a simple bluetooth device if it is not expecting such a rampage of codes...
rock99rock said:
Did that article describe any way of disabling that feature? That functionality could easily trick a simple bluetooth device if it is not expecting such a rampage of codes...
Click to expand...
Click to collapse
No, there was no mention of if it could be disabled.
Wam7 said:
I have exactly the same GPS unit and have no problem pairing it with the probably 15+ WM6.1 roms I have tried.
Try leaving the battery out of the 236 slim for a few minutes and see if that helps. (can't remember is there is another way to reset it)
Click to expand...
Click to collapse
Wam, which rom are you using now that it works with? id like to download and try it. The 5 or so ive tried did not work.
I power cycle the device without any change in pairing succession.
Thanks!
BTW: Other users experiencing differences between 6.0 and 6.1
http://forum.xda-developers.com/showthread.php?t=391488
http://forum.xda-developers.com/showthread.php?p=2240665
My Garmin XT doesn't able to connect to COM4. It just automatically changed to intermediate driver. The intermediate driver works, means, it can get a fix, but the data are incorrect. It misses about 500m from where am I now. also the elevation seems not correct, it shows -78m, where with visual gpsce, i get 21m.
Oh, one more, with intermediate driver, it seems get a lock for a second, and lose on next second.
Anybody experiencing the same issues?
btw, on my TyTN II, it works fine.
you need to tweak it, the thread is around here somewhere, sorry am using my phone, a bit hard to search and copy paste
Do you mean tweaking the registry? I tried it, but doesn't change a thing..
So basically, I get accurate data with visual gpsce, but not with garmin.
Did you downloaded the latest version of Mobile XT?
yes I did. It's 5.00.20wp
i am using a similar version of garmin mobile xt with no issues on the touchpro2
Are you able to connect directly to com4?
mine only able to connect via intermediate driver.
Is it possible to connect directly to com4 at all? I always assumed that whatever you do, when selecting the com port, it still goes through the driver?
I have no problem using Mobile XT (same version as you). Position is quite accurate (maybe just 20m off). And I'm using the standard settings for the PPC version.
rob_p said:
Is it possible to connect directly to com4 at all? I always assumed that whatever you do, when selecting the com port, it still goes through the driver?
Click to expand...
Click to collapse
Yes, that's true. Also check your current elevation. Is the data correct? mine always shows negative value. (I'm +- 20m above sea level)
Does Garmin works smoothly for you? Mine seems to lag by 1-2 seconds like on TomTom. Works smoothly on iGo 8.
I did do the registry hacks but still no luck. Any other suggestions?
bumping an old thread because i have the same problem, garmin is GOOD, but lags a second or two behind, causing me to miss my exits. i've done the registry tweaks but to no avail... anybody? i've also read about gpsgate and the gps driver on the site, can anyone confirm them working?
heres an example: (not my video) http://www.youtube.com/watch?v=gJ2gQx48Zng
watch 0:54-1:00
you see that the person passes under the overpass at 56, but it doesnt register on the garmin mobile until 58.
HOW CAN I ELIMINATE THAT LAG?!
bump :*( nobody has any problems with garmin?