Develop Bugs

Seiko Smartpad and XDA

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.

Unistall hardwarekeyboard on Blue Angel?

is it possible to switch off the hardwarekeybord or uninstall the drivers??
thanks for your help.

Start / Settings / Connections tab and select Beam, turn off the receive all beams check box and that will have disabled the hardware keyboard (the keyboard still works but this action frees up the com port) mike

M-Ster said:
is it possible to switch off the hardwarekeybord or uninstall the drivers??
thanks for your help.
Click to expand...
Click to collapse
why would you want to??? :?:

I'd like to disable the KB so that TomTom5 will display its soft keyboard.
Tried the beam off and it didn't work. Must admit didn't think that it would though.
Anyone got an suggestions
Wayne

let us know how you get on. im not sure if someone has already tried it tho.
good luck
if it works i think i will do the same then i can re install tomtom5 as im back to using 3

mikealder said:
Start / Settings / Connections tab and select Beam, turn off the receive all beams check box and that will have disabled the hardware keyboard (the keyboard still works but this action frees up the com port) mike
Click to expand...
Click to collapse
just read this im sure this is not right. he wants to stop the device from recognising that it has a hard wired keyboard not an external one

OK fair point, I was pointing out the easy fix to get the wired GPS receiver unit to work - turn off IRdA, this will not as you correctly indicate force TT5 to use the on screen display keyboard, nothing will until they i.e. tomtom fix the situation - its just poor code untried and released on to the market - I would love to continue with vs3 but it will not work with my XDAIIs, vs 5 does (at last) but not hapy with the interface, lack of on screen keyboard and the inbuilt POI warner (speed cams etc) is rubbish compared to CheckPOI that I use on my ipaq-4700 - mike

Received this email back from TomTom support today.
"Thanks for your E-mail.
We are working on an update to solve the hardware keyboard problems and with 3rd party GPS receivers.
At the moment we can't give a release date but we hope in this month.
Please keep an eye on our wesbite for latest news."
Hopefully we should have a patch for TT5 this month

to mikealder
Just use overlays from checkpoint (copy ovl.files in tomtom dir)
Worked for me

Anybody find a way to disable the keyboard yet?

Found it, now I can use the on screen keyboard with TTN5
In register of PDA..
HKEY_CURRENT_USER\Software\Microsoft\Shell
Change..
HasKeyboard value from 1 to 0

upgrade to tomtom 5.1 solves the keyboard problem with XDA2s - go to tomtom web site to download update

PDA2K - Car Kit / In-Built GPS Comms

Hi All,
I have a i-Mate PDA2K-EVDO with the following specs:
ROM:2.03.00 WWE
Radio: HA01_140
Ex ROM: 2.03.11 WWE
Currently with eXpansys FSE9 Car Kit (Includes integrated GPS reciever) URL"http://www.expansys.com.au/product.asp?code=124312", with ALK (Travroute) CoPilot Live 5 for PPC.
The issue that I am having is that when the phone is docked in the car-kit all call functions work fine (except for volume being a little low, but that may be spk position), however I cannot get the GPS software to communicate with the reciever. I am not sure whether the com-port that is used to communicate with the reciever is only being half-opened (or not remaining open).
I have tried modifying the selected COM settings and am currently using (COM 1, 4800) which appears to have some communication with the device. When the unit first is powered-up the GPS recieving light is on (steady) and when GPS location is established the light starts flashing. I have installed GPSInfo (for WM5) and am able to scan ports to establish COM1, 4800 as the connected port. When I then press the "Cold Start" button the GPS reciever resets, and then goes through the re-establishment phase, but no GPS data is being parsed.
To top things off, I did manage to get the CoPilot software to work for all about 5 mins. So I am thinking that this may be a port issue (or something with the reciever).
Can anyone provide some help with the following:
1 - A utility that can check com port activity, and see what is happening at this level.
2 - Some insight as to what other programs may use the same ports as COM1 - As I believe that it is serially emulated as a COM.
3 - Any other insight would be greatly appreciated.
Thanks in advance.

pro-integrator said:
Hi All,
I have a i-Mate PDA2K-EVDO with the following specs:
ROM:2.03.00 WWE
Radio: HA01_140
Ex ROM: 2.03.11 WWE
Currently with eXpansys FSE9 Car Kit (Includes integrated GPS reciever) URL"http://www.expansys.com.au/product.asp?code=124312", with ALK (Travroute) CoPilot Live 5 for PPC.
The issue that I am having is that when the phone is docked in the car-kit all call functions work fine (except for volume being a little low, but that may be spk position), however I cannot get the GPS software to communicate with the reciever. I am not sure whether the com-port that is used to communicate with the reciever is only being half-opened (or not remaining open).
I have tried modifying the selected COM settings and am currently using (COM 1, 4800) which appears to have some communication with the device. When the unit first is powered-up the GPS recieving light is on (steady) and when GPS location is established the light starts flashing. I have installed GPSInfo (for WM5) and am able to scan ports to establish COM1, 4800 as the connected port. When I then press the "Cold Start" button the GPS reciever resets, and then goes through the re-establishment phase, but no GPS data is being parsed.
To top things off, I did manage to get the CoPilot software to work for all about 5 mins. So I am thinking that this may be a port issue (or something with the reciever).
Can anyone provide some help with the following:
1 - A utility that can check com port activity, and see what is happening at this level.
2 - Some insight as to what other programs may use the same ports as COM1 - As I believe that it is serially emulated as a COM.
3 - Any other insight would be greatly appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Hi there,
Not too sure if this'll help but with TomTom 5, you need to disable incoming beams on the Start\Settings\Connections\Beam to enable the Hard-Wired GPS to be read..
Try it and let us know the outcome..
Cheers!

Still No Good
Hey Mr Philly,
No luck with the Beam Settings. I even went as fas as Hard Resetting the device :x as Active Sync to Exchange stopped working this morning....
Any other ideas?
Thanks again for your response.
Paul.[/quote]

Paul, you mentioned specificaly that you loaded GPS Info (for WM5) is this the OS you have on the device? if so the GPS applet in the control panel / connections tab might need playing with - BTW I should have mentioned as its a wired GPS unit leave the Receive all beams OFF on this device - Mike

Interesting Point
Hi Mike,
Thanks for joining in on this thread.
I have disabled beams on the device.
THe GPSInfo app loaded was WM5 although I only have WM2003 SE. I have searched through multiple ng's to find a 2K3SE version, but all seem to point to the new version.
This was also the file provided my the distributor of the car-kit & cradle. The GPS unit is integrated into the Car Kit, so that is what i refer to as hard-wired (opposed to GPS).
As for the applet, I do not have a GPS applet in the connections section :?:
Can you provide any more informationon this point.
Thanks again,
Paul.

Disregard it then, I thought you might have loaded up a 2005 OS by chance , this has no bearing on the problem on your device - more thinking time required - Mike

Re: Still No Good
pro-integrator said:
Hey Mr Philly,
No luck with the Beam Settings. I even went as fas as Hard Resetting the device :x as Active Sync to Exchange stopped working this morning....
Any other ideas?
Thanks again for your response.
Paul.
Click to expand...
Click to collapse
Hi Paul..
Apologies.. I also need more thinking time.. :lol:
If I think of anything else, I'll get back to you..

TP2 Bluetooth / JVC Car Kit trouble

I currently have a Diamond and TP2 with stock ROM's.
Diamond worked perfect with carkit untill i performed major ROM upgrade from htc.com. now it will connect and not reconnect on either device or carkit restart.
My TP2 behaves EXACTLY the same - connects and drops after either restarting. when connected it works fine - voice/dialing etc etc.
My car kit is a JVC KS-BTA200 connected to my KW-AVX810 head unit.
i've read all comments on google/xda's etc - well almost all! to no avail.
the devices are all set to visible obviously and all paired. ive read that a registry edit possibly fixes the issue but my TP2 & Diamond dont have the required reg strings. (that i can find!!)
i have the remote registry tool installed on my Desktop - so im ready to make changes!
please, if anyone can help i will very grateful!!

radak23 said:
I currently have a Diamond and TP2 with stock ROM's.
Diamond worked perfect with carkit untill i performed major ROM upgrade from htc.com. now it will connect and not reconnect on either device or carkit restart.
My TP2 behaves EXACTLY the same - connects and drops after either restarting. when connected it works fine - voice/dialing etc etc.
My car kit is a JVC KS-BTA200 connected to my KW-AVX810 head unit.
i've read all comments on google/xda's etc - well almost all! to no avail.
the devices are all set to visible obviously and all paired. ive read that a registry edit possibly fixes the issue but my TP2 & Diamond dont have the required reg strings. (that i can find!!)
i have the remote registry tool installed on my Desktop - so im ready to make changes!
please, if anyone can help i will very grateful!!
Click to expand...
Click to collapse
Hi, I am using my Touch Pro 2 with the same HU and Bluetooth adaptor as you but no such problem so far.
It used to have this problem then I try to connect using Window CE as the phone setup and choose another Connection Key instead of default 0000 to pair the phone with the HU.

ok, well i just tried connecting via searching for the device from the HU. it finds my device - i tap enter (to connect on HU) then it just jumps to a blue flashing 'connecting' then goes to a yellow 'error' straight away. if i select 'open' on the HU then it connects (connecting with a different ID - a number '6') but only untill i restart the HU.
also as a test i just tried an Xperia (just had one laying around LOL) and it does the exact same as mine!! ARRRRGHHH!
so im glad to say i believe it is not an HTC issue!

ok so i have an update - the problem is my HU will not pair correctly and it will not store a pairing. great.

another quick one - have found others are having trouble with their HU/adapters. thanks anyway everyone!

TP2 Bluetooth and voice dialing working fine ???

Have you tried to reset your carkit? I had the same problem after the rom-update with my TP1 and I put my carkit (Bury CC9060) back to factory settings. So I did the same this morning after I updated my TP2 and now it works just like a charm. Of course I don't know if your carkit has this possibility. Good luck, greetz Ton

'iznogoooog' - yes it work perfectly until you restart either device - 'ton66' - unfortunatley a reset is pretty much all i can do!!! eeeeek!
hopefully a reset will fix it! - i did unplug my b/tooth adapter then switch the unit on - then off then plug it back in.. didnt change anything.. oh well! will do complete re-set 2day!
BTW:
thanks so much for everyones help!

Got a questions. I am using the AVX-826 with build in Bluetooh. I want to know if you guys get the Signal Strength show on your Head unit is correct. on my unit pair with TP2. The Signal Strength indicator doesn't move. it always show the strength with my phone is connected to the unit and it stay that way.
The Battery Strength indicator does work and show the correct battery level.

I have exactly the same prob!
Hi,
I have a AXV800 and a BTA200.
My first device was a Artemis with WM6.0. No problem so far!
Then I changend to a Diamond with WM 6.1 and had the same problem as mentioned before. Now I tried my new TP2 and still the same problem.
And I tried the old Artemis again with a new 6.1 ROM and the same problem as on the other two phones.
Now I think it depends on the WM build. 6.0 seems to work 6.1 not!!!!!!!!!!
I did a reset on my AVX800 two times without luck!
I think I'm going to use a normal phone without Windows mobile for the next test!
Schelbi.

Bluetooth SPP Profile

Does anyone know how to enable the bluetooth SPP profile for any of the Sense 3.5 ROMs? What I would like to do is tether my GPS location to my Win7_64bit laptop. Verizon's latest OTA has it enabled and my laptop configures the modem/COM port just fine, but when I try to connect to any of the newer Sense 3.5 ROMs my laptop doesn't detect the SPP feature from my phone and doesn't create a COM port, but creates the other audio features.
Could it be as easy as copying the bluetooth.apk from the Verizon OTA and installing it in one of the 3.5 ROMs?

make a backup and try and let us know

Snag ShareGPS from the market, it will turn your phone into a bluetooth GPS transceiver.

Weselers said:
make a backup and try and let us know
Click to expand...
Click to collapse
I tried that, phone kept restarting when I went into Bluetooth settings. Understandable.
Nova5 said:
Snag ShareGPS from the market, it will turn your phone into a bluetooth GPS transceiver.
Click to expand...
Click to collapse
Thank you for the suggestion! Funny though that I tried this about a day before you replied! I'm such a noob So it seems that the OTA with its DUN, I think, tells my laptop that there's a COM port, and is constantly running, which now makes complete sense. I think it was when I was trying ShareGPS, and actually had it running when I added my phone as a bluetooth device, that I noticed the Serial Port (SPP) within the services of my phone properties on my laptop. The other times I didn't have any GPS tether app running when I added my phone, or any app that creates a bluetooth serial port for that matter, so the SPP service was not listed...brilliant Great learning experience though! In the end I prefer GPS over BT though...guess I'm a sucker for tons of info