Related
I'm using - Dell laptop with integrated Dell bluetooth, XDA2 with original 1.03 rom, ActiveSync 3.7.1, Windows XP+SP2. I *AM* able to: synchronize fine with USB cradle, synchronize with IR, and beam files directly to the XDA2 from the laptop via bluetooth.
I have successfully: removed all traces of Widcomm, removed and reinstalled the plain old XP/SP2 BT drivers, have removed the pairings and re-created the device pairings successfully, removed and re-created the incoming COM port, renumbered my incoming COM port to 3, set ActiveSync to 'allow serial connection' to COM3, turned off XDA infrared, tried out "Pocket Bluetooth Tools" too, disabled my firewall. I moved my modem from COM3 to COM13. All the devices are 'working properly' according to control panel. Bluetooth switched to 'On' on XDA, once already paired. Bluetooth Devices/Options/Connections/Allow BT devices to connect is ticked.
Now I have tried to connect as documented in the many webpages on this subject, including GeekZone:
A. On the desktop - ActiveSync/File/Get connected... gives the message 'looking for mobile device on IR and COM3' but then nothing happens. After failing, it shows the list, and COM3 is 'available'.
B. On the XDA2 - Start/Settings/System/Bluetooth settings/Start activesync setup - gives message 'Please bond with device supporting serial port' - then takes me to the bonding screen. But I am already bonded successfully!
C. On the XDA2 - ActiveSync/Tools/Connect via BT with 'Laptop' - gives the message 'Cannot start communications with the desktop computer, critical error 608'.
As the pessimistic bobopopo recommended, I tried doing these last things repeatedly in every possible order!
Possible clues as to the problem:
1. I can't get the bluetooth icon to come up in the system tray. It comes up temporarily if I uninstall and reinstall the XP-SP2 drivers, then goes away next time I reset - even though the item 'Show the BT icon in the notification area' is always checked.
2. The first time I make a pairing, the word 'connected' appears below the icon for my XDA2 in the "Bluetooth Devices" dialog, on XP. Once it goes away, thereafter I am unable to get it to say 'connected' again. How can I get it to connect?
3. First time I bonded I got the Pocket Bluetooth Tools profiles dialog on the XDA2 - and ticked all the boxes, including serial port. Now I can't seem to get that screen back again?
4. On the XP machine, if I go to Control panel/Bluetooth Devices/Devices, select the XDA2 that is paired, then Properties/Services, I get only 'Dial up networking', and no exciting stuff like COM, OBEX, audio, PAN etc. - is this right?
5. If I go to Control Panel/Bluetooth Devices/COM ports/Add/Outgoing, and put Browse.., it searches for a while then says 'Windows cannot find any Bluetooth devices. Make sure it is switched on' etc.. although the device is clearly visible. So I can't create an outgoing COM port.
6. Can't beam files from XDA2 to Laptop: though XDA can see the other machine when you try to pair, it can't see it when you go to File/Send To/Infrared recipient - just empty dialog 'Searching...' forever. ('Accept incoming beams' is on and Bluetooth is on.)
????? Is it me or is it Microsoft ?????
mate,
reading through your post (although don't consider me an expert on this) it appears that you have the same problems i had before. bottomline? i discovered that windows xp service pack 2 screws up installation of bluetooth software. took me ages to figure this out but what i did was uninstall sp2 and went for sp1 instead. i've read several posts here and in other sites that sp2 doesn't really do well for bt apps...not sure if this is the same for the other chaps but it sure was for me. anyway; i uninstalled all bt software, uninstalled sp2; installed sp1 (reboot, etc), and from there proceeded with reinstalling my bt and activesync apps. from there i followed the guide given in geek zone and presto bt activesync.
the items you described in 1-6 definitely remind me of the sp2 trouble i had.
hope that helps.
cheers mate
I found that if I use the cradle to link to activesync this will create the partnership, then use the bluetooth next time and it will work, it seems you cannot get an original partnership over bluetooth.
I don't think its SP2 itself thats the problem. Its the Microsoft bt stack built into SP2.
You can actually run SP2 and the Widcomm bt stack. If you install Widcomm before SP2, then it won't install the Microsoft bt stack. I had the same problem and this resolved it.
The Microsoft bt stack in SP2 is Microsoft's first attempt at bluetooth. Looks like they still have work to do.
JD
Bluetooth activesync is easy IF YOUR NOT in Windows XP SP2!!! best thing to do is to downgrade to SP1.. unfortunately for me im stuck with SP2 in my desktop... but upon discovering this problem i never upgraded my laptop to SP2.. i left it with SP1 nd everything works in harmony...
MORAL LESSON OF THE STORY: NEVER UPDATE TO XP-SP2 if your using bluetooth activesync. :wink:
I've had no problems syncing over BT with SP1, SP2 MS stack and widcomm.
Here's how.
First of all delete any pairings on both PC and XDA.
Sync over USB then on the computer use connection settings to select the correct BT com port.
On the XDA goto Settings->System->Bluetooth->Start
Now repair your device and select ok till you get back to today screen
Goto activesync and then tools->sync over bt
Always has worked for me. If you're still having problems its quite possible that you haven't got the right ports setup on the PC.
YUP! it's all about the COM ports... SP2 gives out extremely high COM ports that activesync doesnt recognize...
Is your PC using...
1. SP2 + MS bluetoooth stack
2. SP2 + Widcomm bluetooth stack
I've followed the method laid out by fruitloaf many times, and only the 2nd combination works for me.
You might also want to consider upgrading from rom 1.03 if you can.
JD
fruitloaf said:
I've had no problems syncing over BT with SP1, SP2 MS stack and widcomm.
Here's how.
First of all delete any pairings on both PC and XDA.
Sync over USB then on the computer use connection settings to select the correct BT com port.
On the XDA goto Settings->System->Bluetooth->Start
Now repair your device and select ok till you get back to today screen
Goto activesync and then tools->sync over bt
Always has worked for me. If you're still having problems its quite possible that you haven't got the right ports setup on the PC.
Click to expand...
Click to collapse
Fruitloaf, is yours an original Orange machine? I've heard this works with SP2 + MS stack, but the O2 Xda II doesn't.
JD
I had this problem constantly with my XDA II and a Toshiba Laptop. All routes of advice came to nought.
The answer for me was to install Pocket Bluetooth Tools, a BT connection manager which has a specific Activesync Profile. Using this has enabled me to use BT A/S with my Win XP Tablet SP2 PC without problems. You have to initiate the Activesync process from the XDA though.
Once you have installed BT Tools, and created an A/S profile using the cradle, go back to the XDA and delete all existing BT Pairings. Then go through the "Bluetooth / Paired Devices/ New routine again. After finding your PC, continuing will give a new Dialogue box with available pairing options. Select "Activesync" and finish. Do a soft reset.
From there, go to Start/Activesync, then tap Tools/Connect via Bluetooth and all should work.
I recommend using PBT Tols version 1.0.1.2 not the newer version, as the later version causes some power management problems with the XDA II.
Available Here
bluetooth virtual com port too high for activesync
I have a Belkin F8T001 v2 BT USB dongle. BT was working under win xp sp2 and could transfer file etc from PC to XDA IIs and back.
However I tried setting up a BT active sync connection and had the problem that the virtual com port picked by the belkin supplied widcomm BT driver was too high for activesync, it was com20. I followed this thread but could not uninstall the driver and use the driver from SP2 as it doesn't seem to support my belkin USB BT dongle. So I had to go back to the driver supplied by Belkin. I thought I was stuffed until I came across a post that sorted the problem, I'm afraid I dont have it to hand to give author the credit. But here is what he/she said to do.....
1. Disable bluetooth in device manager and remove the high numbered com port from device manager.
2. Then use regedit to change
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\COM name arbiter"
I followed the instructions and changed the first 3 entries in theComDB field to be "0f".
3. Enable Bluetooth in device manager
4. Use bluetooth settings -> local servies to add a new COM port, then set it to autostart in the profiles section.
This time it came up as com5, and bingo activesync could find it and I was off....
Hope this helps others with this problem, usual disclaiamer when fiddling with registry back it up and dont blame me if it doesn't work or your equipment goes up in smoke
Good luck, Wayne
http://www.geekzone.co.nz/content.asp?ContentId=3163
this guide works just fine for me
Marc MD said:
YUP! it's all about the COM ports... SP2 gives out extremely high COM ports that activesync doesnt recognize...
Click to expand...
Click to collapse
That's is my problem, the high COM ports are not recognised by ActiveSync! I think i have 2 downgrade to SP1 and then upgrade again to SP2, hopefully that will work.
The BT drivers is not my problem but it's impossible to select the com port in activesync (but the com ports are visible in the device manager!).
Thanks to this forum for geving me hope , now i know what the problem is.
If you read my post with the registry change above I think you will find it will solve your problem, as I stated this was the only problem I was having with the BT driver.
This is a lot simpler than downgrading to SP1 etc.
AT last I done with this help and use widcomm Bluetooh Software 1.4.2 bulid 10 now my active snc work great with winxp sp2and wm2003se ..
just flow the thats:.....
This issue may occur because the Bluetooth drivers that are provided by Microsoft support a different set of profiles than the drivers that are provided by some third-party vendors. The Microsoft-provided drivers are also signed and will therefore be installed instead of a third-party driver for supported Bluetooth adapters. The Windows XP SP2 Setup program will try to detect if a third-party driver is present. If the third-party driver is installed, the Microsoft-provided Bluetooth drivers will not install. This action makes sure that an existing configuration is not modified. If both provided drivers were installed, and the Bluetooth Radio were connected to the computer, the Microsoft-provided driver would load because it is signed.
If the missing functionality is critical, you may restore the third-party support. To do this, follow these steps.
Note The following steps assume that the third-party software is installed. If it is not, install the software according to the manufacturer's instructions. Then follow these steps from the point in the installation process where the adapter is connected to the computer.
1. Click Start, and then click Run, type devmgmt.msc, and then click OK.
2. Locate and then expand Bluetooth Radios.
3. Right-click the Bluetooth adapter, and then click Properties.
4. On the Driver tab, click Update Driver.
5. Install the updated driver manually by using the Have disk option in the wizard. Locate the manufacturer's installation files, and then find the .inf file that is required to install the driver.
6. Complete the manufacturer's software installation steps.
At this point, the third-party provided drivers should work. If at any point you re-enumerate the Bluetooth adapter, the Microsoft driver will be reinstalled, and you must repeat the procedure. This issue will occur only if the third-party driver is removed or if another model adapter installed.
thats link is for bluetooth software v 1.4.2.10
http://asia.giga-byte.com/Communication/FileList/Driver/btd01.v.1.4.2.10.zip
i've tried everything but it still gives out high COM ports...
Marc MD said:
i've tried everything but it still gives out high COM ports...
Click to expand...
Click to collapse
Go to device Manager, find those high Com Ports, choose Properties - Advanced and at the COM port number choose a low one, Like COM3 etc. Don't bother if it say that it is alreaddy in use...
The go to Active Sync and in the Connection Settings choose from the drop down menu COM 3...
Go to the Activesync in you XDA, in the Options choose connect using Bluetooth and the... click on Connect via Bluetooth from the XDA...
You're done...
I have an O2 Xda II Mini (Magician) and I am using an XMicro Dongle on my laptop (Win XP with SP2) and ActiveSync3.8. Initially syncing with BT was a problem but now its not a problem at all.
To reduce the COM port nos. on your computer try the following website
http://support.microsoft.com/default.aspx?scid=kb;en-us;315539
Once you can see the hidden devices and ports delete/uninstall all the ports which are not in use.
1 To sync with BT first delete all your pairing with your computer and phone on both devices.
2 Go to BT Manager on your phone and click both check boxes for Inbound and Outbound COM ports and pair the devices.
3 Once they are paired go to BT manager again and click on the start button (for BT activesync setup) and pair the devices again if you have to.
4 Once that is done check on the computer in BT Manager click on the phone device>property>services....the Serial Port Profile (SPP) "Serial Port COM4" will be checked.
5 After that on the computer's BT Manager itself ensure that the COM ports folder shows incoming and outgoing ports with the phone's name in front.
6 On the ActiveSync (on the ocmputer) ensure that the COM port no. is the same as the Incoming COM port no. given in step 5 above and it being shown as available. Sometimes if it is unavailable, the computer needs to be rebooted and then it will be shown as available.
7 Click on ActiveSync thru BT on the phone and it should work.
It has been working for me since the past couple of weeks. Initially it took a lot of time to set up but now even if the pairing gets deleted or something messes up its working fine. One thing to remember is that in case you are using a dongle with a laptop ensure that the dongle is plugged in BEFORE you boot up the laptop. A lot of people plug it in later and then ActiveSync on the computer shows the COM ports as unavailable.
Hope this helps.
Dear All,
Please help, my new O2 EXEC is sitting here almost totally useless without ActiveSync.
I did a very stupid thing:
I plugged in the Exec via the USB cable before installing ActiveSync 4.0.
What used to happen (back inthe day 2001 etc) would be that windows would install its own driver for the portable device and then when you subsequently installed ActiveSync its drivers would not go in and hence ActiveSync would not recognise your device.
What is happening now seems like the same sort of issue in that now having installed ActveSync it is just sitting there saying no connection.
For ActiveSync 3.6 and below this is a documented problem and here is the fix
http://support.microsoft.com/kb/264693/en-us
BUT for me this does not work (well because there is no yellow unknown device in Device managers other devices).
In AUDIBLE terms
a) I get a du-duh sound when I plug in EXEC (like if you plugged in a USB key for example)
b) It shows up in the Device Manager-> Network Adapters as "Windows Mobile-based Device"
c) ActiveSync 4.0 or 4.1 does NOT give me the dulde-de-dah sound
d) ActiveSync shows no connections
Anybody any bright ideas? Surely I am not the only twonk to have inadvertently plugged in the EXEC first
Answers greatly appreciated.
BASICALLY HELP
PS: Have also looked at ActiveSync trouble shooter 2001, the ActiveSync 4.0 troubleshooting article from Msoft, tried switching off firewall, no result. Have tried deleting the Mobile-based Device, uninstalling AS 4.0, rebooting, reinstalling AS 4.0 or 4.1 then plugging EXEC,no good.
PPS: I convinced a friend to let me install AS 4.1 on his computer and then plugged in the EXEC and all was fine, so the EXEC itself is sound.
Maybe this will help:
http://www.microsoft.com/windowsmobile/help/activesync/default.mspx
Sorry, didn't read your message good.
Just see now you already did looked at the link....
But another idea: if your device works on your friend PC, then why not
do a clean install for the OS on your own PC?
Maybe this will solve your problem.
Dodger,
Thanks for the thoughts. Well actually thinking about a reinstall of my computer due a moments lapse of concentration is a difficult undertaking. With the backup of the on computer databases as well as over 100 applications installed, I think this would take me several person days.
Currently my thoughts are to clone the partition and then do a windows "over install" onthe clone, but logically that will not work because <of course> the whole point of an over install is that the registry and all applications are preserved.
I spent over 3 solid hours of googling, installing, uninstalling drivers yesterday trying to fix and can't believe I am the only one who has had this problem!
Perhaps somebody with a working ActiveSync can elaborate how does the EXEC show up in device manager (when its plugged in and synced), and also what device driver XP and /or Windows 2003 server would be using.
Thanks mb.
I was facing similar issue. Solution? Yes, uninstall my firewall, connect and sync with my JasjAr and then install the Firewall with Jasjar already connected !
This may help:
Open network connections on ur PC so u can see all connections.
Make sure AS (PC side) is enabled for USB
turn off JJ and plug it in to USB
Turn on JJ whilst watching the window of netwrok connections on ur PC
A new connection icon should pop up, then MAYBE dissapear again
Right click this icon, before it dissapears, and check it's enabled, then select properties
Now check the following items:
- does top box say "windows mobile based device"
- click "configure"
- under configure, is there a button somewhere (mine's working so I can't recall exactly where) that says something like "enable mobile device". If so, then you need to click this.
If this all fails, then repeat but with another USB port. The reason for this seeming waste of time is that you will get a DIFFERENT "Local area connection nn" icon, which may work for you.
I cant believe there hasnt been one mention of rebooting your PC - Which I can assume you already have done?
What OS are you running on your PC?
I have only just got my MDA PRO but this may help! as I did the same thing and for a while XP Pro wouldnt recognise the device.
Uninstall ActiveSync
Reboot PC
Install Activesync V4.0
Plug in USB Device
If there is still a problem connecting you shoudl see a USB device not recognised in your deviuce manager.
It almost seems like there is a time you have to wait before XP will respond normally to you unplugging and replugging in the USB.
Failing this you may have to uninstall Activesync and tehn remove all activesync registry keys it may have left behind! Then reboot and start again!
Just having tisproblem now, this is pïss poor of MS to still be foisting off onto us this Activesync package in such a terible state.
I've just had activesync stop working on me. It would connect but then refuse to sync anything even though it previously worked fine. I think it got upset after I booted up the PC with the Exec connected.
Anyway an uninstall and reinstall of Activesync on the PC cured the problem. Not the most robust software though.
Moandal said:
I've just had activesync stop working on me. It would connect but then refuse to sync anything even though it previously worked fine. I think it got upset after I booted up the PC with the Exec connected.
Anyway an uninstall and reinstall of Activesync on the PC cured the problem. Not the most robust software though.
Click to expand...
Click to collapse
What works for me is to turn off the handheld, and connect the cable after that. Then turn on the device if needed. Works mot of the time then.... no excuse for MS though....
I could get my TyTn to sync with my computer occasionally after installing AS 4.2, but ActiveSync would still disconnect itself from my device after a few minutes (I could get it to sync most times though, but I'd have to shuffle round USB ports etc)... Installed ActiveSync 4.5.0 beta (build 5509 BETA) last night, and now my phone won't sync AT ALL with my PC. AS can't even see the device, it can see it's been plugged in because it kicks into action, but nothing more ever happens apart from the (useless) Troubleshooter coming up.
Just a word of warning... Don't install 4.5 beta unless you're absolutely certain it'll work. I've gone from a somewhat-functional sync ability to absolutely nothing at all, and now I'm going to have to rollback my ActiveSync installation (if I can!)
That and the fact my TyTn won't even see my bluetooth headset (an Avro GW-BT-002, which my Alpine can both see and use absolutely fine), I'm beginning to get a little frustrated with this device.
Further proof that more often than not:
BETA = BROKEN
I've had the beta AS 4.5 for a week now and no problems whatsoever with dopod CHT9000 (hardware) using latest i-mate, dopod, or cingular ROM's.
All of these ROM's all work perfectly with sony-ericsson hbh-ds970 bluetooth headset.
After you upgraded to 4.5, did you delete your PC from the activesync partnership and rebuild a new partnership?
* Activesync > Options > press on desktop computer's name and delete it. Then, delete mobile device from desktop AS. You'll then be asked if you want to keep your file directory. Afterwards, reboot pocketpc and connect with usb cable or over bt.
It does work.
Cheers
Yep, did exactly that.
AS 4.5 works perfect with my prophet.
Issues:
Had to set-up my device again (old settings disappeared)
All programs that I installed via active sync before were gone
Top:
Improved speed of syncing files
Easier change of settings
Robin
Hmm. Beginning to wonder if I have either a dodge device, because my Alpine always synced fine
4.5 works for me with my TyTN. (slow as hell - but works).
/Martin
I can't get it to work, either. It completely blew away my partnerships... :evil:
I've gone back to AS4.2 and will wait for this to go GA before making this mistake again...
Dopod 838 Pro
Worked a treat on mine. No issues whatsoever. Biggest difference I can see is a different looking AS icon
Bloody hell...
... Beginning to think it's my computer, might end up reinstalling Windows on it this weekend. Annoyinggggggggg.
After a crap installation of AS4.5, downgraded back to 4.2, but it's still not seeing my TyTn at all, so I'm figuring that it's more likely to be a PC problem. It's not the best Windows installation either, it's become bogged down with stuff, and it never worked right after I made a couple of 'tweaks'... That's me, always fiddling with things when they work fine in the first place :roll:
I'm having similar issues with my TyTN, installed 4.5 on my PC, plug in my PDA and it starts charging (via USB) but ActiveSync can't find it, although does state that USB is available, just keeps searching?!
ActiveSync needs rebuilding from the floor, its always been a rather 'naff' featureless product.
christopherwoods said:
Bloody hell...
... Beginning to think it's my computer, might end up reinstalling Windows on it this weekend. Annoyinggggggggg.
After a crap installation of AS4.5, downgraded back to 4.2, but it's still not seeing my TyTn at all, so I'm figuring that it's more likely to be a PC problem. It's not the best Windows installation either, it's become bogged down with stuff, and it never worked right after I made a couple of 'tweaks'... That's me, always fiddling with things when they work fine in the first place :roll:
Click to expand...
Click to collapse
I had the same problem. Hard reset of my XDA Exec and it worked. draw yor own conclusions.
Have you tried turning off the "USB advanced network functionality" - this seemed to sort the same problem out for me;
go start - settings - connections - USB to PC - untick box "Enable advanced network functionality"
You are aware that AS 4,5 REQUIRES Outlook 2003 !?!?
otherwise it will not work at all
That beta works fine. The only problem I've had is related to remote NDIS interfering with my soft firewall, even after all access rules allowing it. Only workaround is to disable smart ARP filtering in Outpost Firewall or change transfer mode of phone to Serial and everythin is gravy for sync.
Your problem seems related to device manager misconfig of the device or something else.
why don't you try this from start --> run --> cmd line
set devmgr_show_nonpresent_devices=1
start devmgmt.msc
Then, once device manager loads, click view --> show hidden devices. From there, scroll down to network adapters, expand, and delete any instance of Windows Mobile-based Device. On the phone, delete Activesync relationship with PC. Then reboot computer, and plug in your phone again. Let us know if that solved your problem.
I had numerous issues with AS4.2 and AS4.5 Beta initially. And I had issues with Vista RC2 (both x64 and x86) syncing with the WMDC B3 as well.
Then it dawned on me that I was connecting my 838pro to the computer via a Belkin USB hub. So I removed the sync cable from the hub and directly attached to the computer. Now I have no more problems whatsoever (that's in the past 2 weeks.....)
So the moral is: DIRECTLY CONNECT YOUR Hermes TO THE COMPUTER'S USB PORTS!
Just put AS4.5B2 on today - no real probs - no real improvements
R
Hi christopherwoods
I am sorry if this is the wrong forum but its the only one I could find with reference to my bluetooth headset.
I am the owner of an Avro GW-BT-002 bluetooth headset which was free with my old mobi. Unfortunately I can no longer remember how to set it up or any of the other settings to use with my new Motorola V3x 3G phone. Is there any possiblity that you could post the instructions of its settings etc to this forum for me.
Many many thanks
Craeg
Same Issue - Fixed
I had a problem with ActiveSync after upgrading to 4.2.
I am now running 4.5B and it is working after deleting prior partnerships from my handheld.
(I am running Outlook 2007)
ActiveSync 4.5 finally working!
I had the same problems with ActiveSync 4.5 (beta) until I actually put in the original install disk I had with the phone (it had ActiveSync 3.7 on it) when I first tried to connect my phone and it wouldn't detect it. 4.5 (beta) is now working fine for me!
Hey all,
I have some generic BT dongle for my computer that I bought a year or so ago to use with my old HTC Typhoon. The dongle allowed my phone at the time to ActiveSync over BT using the BluSoleil software that came with the dongle. However, with the HTC Wizard (MDA vario body with the AKU 3.3), I cannot for the life of me sync over BT. I have no idea what I need to set up and every time I try and do a new "partnership" in the phone for syncing over BT - i select my computer in the devices, yet nothing happens. I cannot establish any COM port communication with the computer and the only type of services that i can push are the vCard from the computer and a "personal area network"...
HOWEVER, if I take my Wizard and connect it to my Thinkpad T60 laptop that has native BT; I can sync to my hearts content... so... someone please give me a clue as to wtf I am supposed to do here to get this to work over BT
Thanks!!!
Anyone? Plweeze?
C'mon, someone must have an idea!
Gave up
I had the same dongle, or at least mine also came with Blue Soleil. I hated that software - it runs a dozen different programs that clog the computer and still doesn't connect properly. I took it off and tried the native MS XP software. It would work once, but when I put the PC to sleep I would have to reboot to get it to connect again. I finally realized that it was much easier to use a cable and gave up. I'll try again when I get a PC with built-in bluetooth.
prestonmcafee said:
I had the same dongle, or at least mine also came with Blue Soleil. I hated that software - it runs a dozen different programs that clog the computer and still doesn't connect properly. I took it off and tried the native MS XP software. It would work once, but when I put the PC to sleep I would have to reboot to get it to connect again. I finally realized that it was much easier to use a cable and gave up. I'll try again when I get a PC with built-in bluetooth.
Click to expand...
Click to collapse
Where did you get the native XP software? I could never find the native software
Plug and Play
If you don't install software, XP will operate it.
I had alot of probs with my old atom doing this. I have a dell xps running xp3 and I just cant activesync over bluetooth. Running duttys rom VERY GOOD. The process fails because the pda doesn,t appear to have the correct services.
Having same problem brother. See my thread here for details. I can get AS working using Widcomm drivers but no way with the built in Windows XP SP2/SP3 BT stack. Since Widcomm drivers are interfering with some of my other drivers in my computer, Widcomm is a no-go for me neither If you find a solution how to make BT ActiveSync work with default windows BT stack under XP, please share! I would appreciate it very-very much
More info
I have done a bit more investigating. Tried it on two other computers and realise that bt is flaky.
Well it apears that the touch is not offering up active sync as a service. HAs any body tried this on stock rom. It would be really nice to put this one to bed. I feel that its definatley the phone. Blue tooth is great when it works. I have hands free kit in car and on the old atom it would only link from phone but with the new one it only links from kit. battery indicator doesnt work and if you transferr phone numbers the phone sends them to quickly for the kit to copy every one so it leaves of every other one and then some at the end. Heres the solution go and stand behing a tree away from the car which slows every thing down and makes it work. I call it my Treepatch.exe
I do have a stock ROM v1.14.401.2 WWE (1.09.25.14 radio) and my PC (using default windows BT stack and Windows XP) does not recognize neither ActiveSync, nor DUN BT services. However it DOES RECOGNIZE under Windows Vista. I'd say Windows XP BT drivers are either outdated or somehow not compatible or missing something... just my 2 cents
EDIT: And yes, I have the same problem with the battery indicator when connected to my car's bluetooth handsfree kit
and i can't get it to work with vista, but it works flawlessly with Windows 7 Beta (64-bit). simply amazing...
Is it really xp
I kept feeling that it was the phone but if its xp can we get a new stack i need to look. I really would like to move this post up so that we can get a definative answer and then maybe a solution. How do yo move post up?
problem solved
Uninstalled bt drivers on laptop and installed stock ms drivers. Had to restart a couple of times. searched for phone tried to set up com. Still no good restarted again and then suddenly the machine actually started the active sync saying do,t waste batteries and euraca its done. So stock drivers seem to be best. I say give it a go.
pawebby said:
Uninstalled bt drivers on laptop and installed stock ms drivers.
Click to expand...
Click to collapse
Would you be little-bit more specific ? What BT drivers have you uninstalled from your laptop ? Toshiba ? Widcomm ? And what do you mean by stock MS drivers ? How did you install them ? Would you mind post a step-by-step procedure you've done ?
Also you're claiming your problem is solved. Would you please double click on the BT icon in the system tray next to clock, go to Devices tab, double click on your paired phone icon and then Services tab. Would you post a screenshot similar to this one to see what you have in there ?
Many thanks in advance!
Regards,
S.
heres how i did it.
Sorry I do not know how to do a screen grab?.
First I uninstalled the supplied bt drivers which were widdcomms and I unistalled the widdcomm software from settings-install software. I am affraid I do not know what release. Next I restarted and made sure the phone was unpaired and cleared of link data. Next i restarted and in system-hardware i scanned for hardware changes. When xp asked to visit the web to download drivers i said NO. I guess that forced it to use the stock xp drivers. Restarted machine at prompt.
When the machine restarted blue tooth icon was on task bar. Looks slightly different to widcomms. I linked the phone via this bluetooth icon. I also set up a com link. This was all most slower than the old widdcomms system?
I then made a cup of green tea. When I came back I restarted the machine again and went into the phone-activesync-sync by bluetooth.
It then did just that. I did not set up com on phone. When I switched on laptop this morning I sync again and it worked.
The xp bt doesn't have all the bells and whistles of the widcomm but it works.
The widcomm program/drivers just could not be confinced that the phone was capable of activesync it would not show it as a service.
I hope this helps.
I have my HD connected to XP sp 3 with no issues.
I have a broadcomm modem, 2.2.14.241 firmware version.
It has been a while since I set it up so it will be hard to offers the details on how.
Just figured that I would post to let everyone know it works and I have full access to all of the files on the device.