Hi SiliconS,
Thank you very much for your suggestion. My Xda can ActiveSync via Bluetooth now. I am very happy with it.
It was 3 weeks after upgrading, I searched thru the posting on the Internet. I share my problem and request help. Almost everyday looking the site waiting for the reply.
Tonight is my great night, you came with suggestion and solve my problem.
After I removed bonding device, I performed Soft Reset. On Bluetooth Setting, I unchecked Passkey Require, uncheck Inbound and Outbond Com Port, then select Start and continue rebounding device.
<Abah – XdaII WM2003SE, Upgrade with Asian Version>
SiliconS, Wrote : <<Maybe a stupid question, but did you re-create the ActiveSync bluetooth bond on your XDA2 before trying to use AS? I made this mistake after a ROM update a while ago.
After the ROM upgrade, don't just create a new bond to the PC through the Bluetooth page. You must go to Start -> Settings -> System -> Bluetooth Settings and then tap the 'Bluetooth ActiveSync Setup' button, which creates a bond ready for BT ActiveSync.
Of course, you may know this so this may seem like a silly suggestion, but this is the mistake I made after a ROM upgrade.>>
Related
Hi everybody,
I do really need an extra help with my XDA and Mapopolis GPS kit. I connected everything right, the GPS antenna (Holux 210) works fine bilinking since the sats are linked, but my Mapopolis software regularly mounted on my XDA doesn't want to work. It still keep itself "frozen" searching for on COM1 port and it did not reply to any command on touch screen.
What's wrong???? Anyone can help me? Please...
Thanks so much for your help....
Lele
ITALY
[email protected]
Not sure if this will fix your problem, but I had a similar situation with mapopolis a while ago.
I'll assume you already have your GPS set up to do NMEA at 4800 baud. Also, this process is described for PPC2002, I haven't been able to try out PPC2003 yet.
Go to the PPC settings window (Start Menu->Settings), and choose the "Connections" tab. Tap "Beam" and ensure that the box for "Recieve all incoming beams" is NOT checked. Click ok.
When this box is checked, it creates some kind of conflict over COM1 which prevents Mapopolis from connecting to the GPS. When I turned this option off, everything started working.
Good luck!
Hi,
Have just got my Navman and was hoping it would be a simple solution to connect to my XDA, but not so.
I've down loaded the BTHTools1012.exe and run it from my desktop, also have loaded EnableCharPin.exe onto my PocketPC.
When I do a bond bluetooth, it finds the Navman. When the passkey dialog box comes up I run EnableCharPin.exe but nothing seems to happen, so enter "NAVMAN" into orginal dialo box.
With the next step linking the COM port I only get Comm 7 as being avavible and when I run the Bluetooth settings from Inbound port is COMM4 but uncheck and Outbound is COMM5 checked. When start is pressed it says that need to bond.
Could some please help
XDA info is:
ROM: 1.60.00WWE the latest for Australia
ROM date: 12/3/03
Radio: 1.08.00
Protocol: 1337.18
ExtROM: 1.60.44
I also loaded SmartST V2 and it ran first time fast. Now it seams at the point of the PPC hanging. I,ve got the maps on a SD card (512M with about 235M free) and 24M for storage and 33M for programs on the XDA. I loaded 3 state maps totalling about 52M on the SD.
Thanks Gordon
Did you unbond and delete your navman before you installed the bluetooth tools?
I had Bt tools installed before I attempted to bod.
I have now also deleted BT Tools altogther but still cannot bond.
I must admit that just after my first post here I did notice that my XDA was not set to recieve "incoming beams". Activating this did not do a thing even with resets.
Thanks for your thoughts and have you got any other suggestions apart from me ring Navman on Monday (I'm in Sydney OZ).
Thanks Gordon
Its a tricky process, but mine is finally working with an XDA II, no blutooth tools and on COM 5. You definately need to DESELECT 'Receive all incoming beams" as if you are set to receive incoming beams, then it seems to interfer with the GPS set up and COM ports
Try selecting COM 5 as the port on the Navman and amke sure that "incoming beams are OFF" on the XDA.
I suggest you start over, uncheck the beams box, install bthtools, install enablecharpin, discover and bond the navman, let us know what happens.
Hi,
Well I did something along the lines of "start over, uncheck the beams box, install bthtools, install enablecharpin, discover and bond the navman" etc but not neccessarily in that order and finally got the thing to work.
Thanks for everyones comments. If I had not tried so many permitation, then I could heve been able to tell all what I actually did!
Now that the SmartST is working, my next task is to use topographic maps wth one of teh follwoing I'm about to try, GarmapCE, GPSDash, PSeasyCE etc. Any suggestions?
Gordon
Glad you got it working in the end. I really like the Navman Smart ST 2 software and their tech support is very good to.
You might check out "MapTech" for topo maps and nautical charts. You can purchace CD's or a subscription that lets you download unlimited maps and charts. If you play golf, and you want to use your GPS to help you pick a club or find out the distance to that bunker in front of the green, "Star Caddy" is fun too!!
Be sure to do a backup now its configured correctly, it may save some hair pulling later if you ever have to hard reset.
I do appreciate all the great mind here working together to put in a wonderful WM2003SE ROM for the XDA II. I too have nightmares with the bluetooth implementation and the difficulties in doing soft reset.
I have managed to solved one of the above issue, Bluetooth Headset, I was using the 1.72 previously and have a workable Bluetooth bonding and response, hence have export the Bluetooth registry from the 1.72 and imported into the new WM2003SE, guess what it works perfectly without anymore problem.
I have attached the Registry file from my 1.72ROM for general sharing, anyway, I have one paired device, my trustworthy HBH660, you may delete it and add your own device.
I have tested this with the headset profile, it works without any hassle.
DISCLAIMER - I am not responsible for any mishap, please backup before trying.
Thanks for posting this setting bro...
The bluetooth registry entiries from 1.72 was able to fix not only the headset profile but also bluetooth file transfer from pc to ppc....
I checked out the default setting of SE2 upgrade
It had only four listed entries on services... while the one you posted has nine including the file transfer protocol from pc to ppc...
I wonder if the rest of the entries work...
By the way i have the asian edition rom by zeroextreme
It was a great fix...
one thing though, how can i turn this registry setting to self extract to the registry so that i can add it in the extended rom...
Thanks!
I have a GPRS account @ my SP with all the things I need to check my mails, send wap based smses, or check/dl stuff from the net
it has worked OK with wm2003...
it has worked OK with wm2003se...
it has worked OK with wm2005...
but it is not working any more!
in the last two weeks I made hard resets on a regular basis (every another day) installing and trying out softwares on wm2005, sometimes when I needed destinator or tomtom, I uploded my wm2003se full install - after finished, back to wm2005...
as things and limitations clear now with wm2005 (and also have all get arounds for dest & tomtom problems) I would have a full WORKING version of my ppc with wm2005...
but I figured out, that regardless of I make all the correct setup with passwords, gatways, usernames and so on (which I now by heart now the thing refuses to go online...
it tries to connect then say: check your settings...
I am NOT about to check the setup, but to ask you guys has anybody same problem?
anyway it's an xdaII/bl 1.01/wm2005g/no other soft installed
thanks
and - after another hard reset - voila, it suddenly started to work and still working...
although - compared to wm2003 & wm2003se - it has a strange behaviour: when the connection lost (for some reason, usually after a few hours) I cannot reconnect, I have to soft reset
any comment?
Hi guys
could any one please be so kind as to help me with a problem im having.
i have a spv m5000 on orange which i have change the mother board over with a o2 exec mother board running windows mobile 6.1 seems to be working fine no issues however i have tried to pair both my gps units with it but to no avail, i have a Holox BT-541 and a navicore BT-GPS-32354D i have tried both of them and have same problem,
my xda see's them and adds them fine but when i try to connect to one in the xda it says unable to connect or wrong passkey i have used 0000 for holox which thats what it says in the holox pdf but have also tried 1234 but i think this is a com port problem i have tried all com ports some will go in ok but still cant connect to gps i also tried this "go into TomTom and use the NMEA devices with baud rate of 38400" this did not work, before i changed mother board i had these working fine on older tomtom and original spv m5000 mother board so i dont know if this is a win mobile 6.1 problem or not i see quite a few people with same problem but no solution that worked for me any way.
i have seen thred taking about pairing before tomtom installation but not sure that will fix my issue as i think i tried to pair before i installed any way.
has any one any ideas on this any help would be really appreciated this is getting to be a pain in the rear!.
also there is an icon in the system tab "external gps" can any one tell me the correct settings in there ie for program tab and hardware tab what com port and baud rate should be and whether the manage gps auto should be ticked
many Thanks in avance for any help you can give here.
Kind regards
Daz
Ok found solution,
after spending way too much time on this crap! I finally found the issue as I stated I thought
it was a mobile 6.1 issue and I was right, in mobile 6.1 they have added a external GPS shortcut
in system tab it is here the problem exists.
my problem was resolved by the following procedure.
On your XDA go to Start/Settings/Connections click on Bluetooth short then add new device once it has found it
enter passkey 0000 or whatever yours is once it has made the first connection then do the following,
1. Under "device tab" click on your unit and make sure the serial port is "UNCHECKED" disabled then click save.
2. Under "Mode tab" make sure (Turn on blue tooth) and (Make this device visible to other devices) are "CHECKED" enable them.
3. Under "COM ports" select a port, I chose 0 don't think it matters but if so chose another but remember what one you choose.
4. Under "Security tab" Authentication (passkey) required "CHECK" enable it click ok to come out of Bluetooth.
5. Under "System tab" click on "External GPS short cut.
6 Under "Programs tab" select (None) for GPS program port.
7. Under "Hardware tab" select port 0 or same as you gave your Bluetooth com port and issue the "Baud rate" 115200 or lower rate.
8. Under "Access tab" Manage GPS automatically (recommended) "CHECK" enable
9. Finally check your xda is blinking a blue light and turn on your tom-tom software it should now pick it up, all done.
Final note it seems that Microsoft have made one more buggy operating system, no change there then LOL
and as a result you can't seem to use the blue tooth pairing process as intended so this is a working work around
one more thing there is a 2nd bug found and that is when you turn off your GPS unit and try to use your xda you might
find that your last page froze up here you will have to mess around with it i.e. try turning off your tom-tom software first
and then your GPS, Thanks to bill gates for yet another windows operating system that doesn't work as advertised.
Well we had Hendrix king of rock, Marley king of reggae, Elvis king of rock'n'role then there's you bill gates king of crap!
Long live the king!!!!! LOVL
A big thank you goes' out markanthonypr on xda-developers for pointing this out, nice one m8
http://forum.xda-developers.com/archive/index.php/t-476940.html
hope this comes in handy for others "knowledge is the real king give it freely"
regards to all
Muzz