Related
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.
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.
Hello,
does anybody know how to programm the GPS Modul?
I tried to change GGA to 1.
Can somebody help me?
Have a look here ...
www.franson.com They sell a module which you can easily program to with visual basic. They demo programs work without a modification. With Visual Studio you can start programming in a hour or so, after having had a look at the samples.
I think meer wants to adjust the SIRF-III-Chipset, which is used in the Orbit.
Most tools "Sirfdemo" etc. wont work on the Orbit. :-(
I'm searching for a tool which can toggle SN (Static Navigation) off on this device.
Hi,
I tried almost everything to program the internal GPS receiver of my P3300, but did not succeed :-(
First, I tried to get direct access to the hardware GPS port (COM 3), but failed to open this by any way. Eventually, I even sent my device into the Boot-Loader mode, redirected the GPS receiver to the USB port by using the GPSRouting command and connected via USB the SirfDemo 3.81 program. Results were very strange:
Using GPSRouting without a parameter gave me binary output data which SirfDemo was not able to handle.
Starting the the receiver at 57600 baud (by using the command "GPSRouting 57600" gave me NMEA output, which SirfDemo was partly able to handle. Some messages appeared correctly in the debug window, but most output of the GPS receiver resulted in SirfDemo in error messages. Really stranges!
I DID NOT FIND ANY WAY TO SWITCH TO SIRF MODE, which is necessary to program the internal sirfIII chipset.
I finally gave up and hope that one day HTC will surprise us with a nice tool to enable/disable Static Navigation and SBAS mode.
GeenZ
Have you tried using COM4 which is where the actual GPS receiver can be found? - Mike
mikealder said:
Have you tried using COM4 which is where the actual GPS receiver can be found? - Mike
Click to expand...
Click to collapse
Of course, trying to use COM4 was my first attempt.
However, COM4 is the output port of the MS GPS Intermediate Driver (GID). This is a software com port, which seems to be not the best implementation of a virtual comport splitter. There are a couple of programs out there, which have serious problems with the GID port, but do work with other (better) virtual comport splitter such as GPSGate.
Anyway, trying to program the internal GPS via the GID port did not work at all. That's why I was next trying to get direct access to the hardware GPS port (COM3), which did not work either, before I bravely sent my device into boot loader mode (unfortunately with also no success)...
Any other hints or suggestion are still highly appreciated.
GeenZ
Can i disable Static Navigation on XDA Orbit?
Any news about this?
do we have to give up any hope !? :'(
Please read my thread
Explains it, i could post some code to get you up and running, but what language are u working?
Slovek said:
but what language are u working?
Click to expand...
Click to collapse
thanks but just trying right now to understand how to get rid of this infamous GPSID !
Anyone knows how to turn off static navigation now? A programmer gave me a tool which perhaps can turn off static navigation on the p3300. But I'm afraid of testing it.
Minipli said:
Anyone knows how to turn off static navigation now? A programmer gave me a tool which perhaps can turn off static navigation on the p3300. But I'm afraid of testing it.
Click to expand...
Click to collapse
are you talking about spGPSView ?!
The name of the tool is SirfTech. What about spGPSview? Can you disable SN with it?
Minipli said:
Can you disable SN with it?
Click to expand...
Click to collapse
Yes, Moreover, this prog. seems to be more "accessible" than SirfTech !
Are you serious? You can really disable static navigation on htc p3300 (artemis) with spGPSview? I often read that it wouldn't be possible....
Minipli said:
Are you serious? You can really disable static navigation on htc p3300 (artemis) with spGPSview? I often read that it wouldn't be possible....
Click to expand...
Click to collapse
the question should be : is it effective or not ? but it can be changed !
What port do you set?
Ward said:
What port do you set?
Click to expand...
Click to collapse
com4 but the gpsid implementation of Orange is different from the HTC one as they are selling the M650 with their own navigation soft...
I have an XDA Orbit, so...
I've had no luck connecting to the GPS hardware with or without the MS Software splitter. Although other applications such as Beeline and iGo work fine.
spGPSview doesn't work with htc p3300/ xda orbit ....
First let me apologize for spamming the forums with some similar threads... each time I overcame a hurdle and a new one presented itself, I just began a new thread to discuss that. From now on I will append the initial thread... thanks for your patience.
1. WM6.1 and WMDC 6.1 (vista x64) are not too friendly... as the interface, though designed to be intuitive.... is anything but. I am sure it will get worked out in the future... but now it is one tough SOB to conquer
2. From doing enough reading on the web, though recently updated (12-17-07)... the Toshiba BT stack also does not play nicely with WM6.1 ... as numerous smartphone and PPC users are experiencing issues across multiple mobile platforms.
3. In Vista x64 (this is my personal experience) the only way for me to sync via bluetooth is to drop the Toshiba BT stack and use the generic M$ drivers. However... doing so I lose the stereo and serial port services
4. For whatever reason, it seems that activesync locks up STK (R08). When I disable STK, I can establish a connection infintely quicker. Alternatively... when I have activesync disabled, STK is much snappier and its failure/crash rate drops substantially
If anyone has had similar and/or different/"better" experiences with similar hardware... I'd love to hear about it
OS: Vista ultimate x64
ROM: Kavana/Rickwyatt .18
BT adapter: Kensington Micro USB (toshiba rebadge)
HTC: s620
Poser said:
First let me apologize for spamming the forums with some similar threads... each time I overcame a hurdle and a new one presented itself, I just began a new thread to discuss that. From now on I will append the initial thread... thanks for your patience.
1. WM6.1 and WMDC 6.1 (vista x64) are not too friendly... as the interface, though designed to be intuitive.... is anything but. I am sure it will get worked out in the future... but now it is one tough SOB to conquer
2. From doing enough reading on the web, though recently updated (12-17-07)... the Toshiba BT stack also does not play nicely with WM6.1 ... as numerous smartphone and PPC users are experiencing issues across multiple mobile platforms.
3. In Vista x64 (this is my personal experience) the only way for me to sync via bluetooth is to drop the Toshiba BT stack and use the generic M$ drivers. However... doing so I lose the stereo and serial port services
4. For whatever reason, it seems that activesync locks up STK (R08). When I disable STK, I can establish a connection infintely quicker. Alternatively... when I have activesync disabled, STK is much snappier and its failure/crash rate drops substantially
If anyone has had similar and/or different/"better" experiences with similar hardware... I'd love to hear about it
OS: Vista ultimate x64
ROM: Kavana/Rickwyatt .18
BT adapter: Kensington Micro USB (toshiba rebadge)
HTC: s620
Click to expand...
Click to collapse
Never thought of STK being the culprit of activesync issues. Since i didnt have these issues with WM 6.0 . Now i also use the toshiba bluetooth stack but i use winXP and there was a way that i could get activesync to work. (not sure how this would translate to WMDC) here it goes. Basically i created another bluetooth COM port with the toshiba BT configurator. then made sure that COM port # was selected in connection settings under activesync then i opened activesnc on my phone searched for new bluetooth devices and when it found my PC and connected, activesync was one of the options. Trying to go the other way around by pairing the phone starting with toshibas program did not yield the same results, in fact i could never get it to paired the other way around.
very interesting...
I will try the technique with today... usually my issue comes about when the devices cant exchange passkeys... although they are identical.
pudge.... should I set the com port as server or client?
Poser said:
pudge.... should I set the com port as server or client?
Click to expand...
Click to collapse
Do what? the com port needs to be a serial COM port. not a bluetooth DUN or PAN com port
pudgedaddy said:
Do what? the com port needs to be a serial COM port. not a bluetooth DUN or PAN com port
Click to expand...
Click to collapse
I gotcha... when I use the BT com port utility it asks whether I want to create a client-side or server-side port
since its serial it needs to be "server" side...
I tried, but still no luck, it pairs.... lists stereo and activesync in the services, but then refuses to sync
I think this is a flaw in WMDC 6.1
Poser said:
I gotcha... when I use the BT com port utility it asks whether I want to create a client-side or server-side port
since its serial it needs to be "server" side...
I tried, but still no luck, it pairs.... lists stereo and activesync in the services, but then refuses to sync
I think this is a flaw in WMDC 6.1
Click to expand...
Click to collapse
the only other thing you might try is in bluetooth settings -->security on your device. disable (temporarily) the OBEX security option and try again.
You can also try and create a COM port on your device. When you're on the screen where you add a new bluetooth device. press right soft key and select COM ports. right soft key again and then select new outgoing port. then select your PC (or laptop) on the list of devices that shows up. then add a com port . and it will let you pick com 6 or com 7. Then try again
pudgedaddy said:
the only other thing you might try is in bluetooth settings -->security on your device. disable (temporarily) the OBEX security option and try again.
You can also try and create a COM port on your device. When you're on the screen where you add a new bluetooth device. press right soft key and select COM ports. right soft key again and then select new outgoing port. then select your PC (or laptop) on the list of devices that shows up. then add a com port . and it will let you pick com 6 or com 7. Then try again
Click to expand...
Click to collapse
already been down that road, trying to set up a new outgoing com port (6,7) no dice.
I think the deal is WMDC6.1 ... it makes me sad
Poser said:
already been down that road, trying to set up a new outgoing com port (6,7) no dice.
I think the deal is WMDC6.1 ... it makes me sad
Click to expand...
Click to collapse
sorry to hear that. Well since i have the same drivers, i will not be using vista anytime soon (not that i needed this as an excuse to begin with)
I was thinking of perhaps looking for some compatable drivers to replace the Toshiba stack. The generic MS drivers allow me to connect via activesync... but thats all, I lose all serial services (including object push, file transfer, stereo etc....)
I'll be honest though, I have been an XP guy for a long time... but after learning how to tweak, hack and optimize my vista install, I love it.
Hey,
i want to start programming an app for my HD2 which should connect one of my bluetooth devices by starting it. I only know a bit about programming under desktop-windows. Where do I find a reference for the programmers api on WM6.5 / where can i look for the commands i need?
//Edit: The functions i found in the MSDN are for connecting - communicating - closing in this way, but i only want to connect a profile (serialport for tmc) and end.
Hope you can help. Thanks.
125
Found the 32Feet.net SDK but still i can't get the procedures i need.
Nobody with information on programming bluetooth apps?
Somebody must have down something similiar in the past or?
These?:
http://www.codeproject.com/KB/windows/BluetoothDevicesDiscovery.aspx
http://www.mobile-soft-dev.blogspot.com/2010/03/c-wrapper-for-nearby-bluetooth-devices.html
Thanks for the links. Ok that is how to enumerate the devices and i could do a connection over winsock, but still i can't find information on not really do a connection but only pair the bt device so other applications can use it afterwards. Damn
(More Information: App should be used on WIDCOMM stack to connect tmc and start navigation after that to get rid of the annoying selector window which disappears to quick)