Hi,
I have the Orange SPV M2000 with TuMa 1.3 rom set onboard. I'm trying to get my device to talk with my new Macbook using third party software from The Missing Sync. It is listed as working with WM2005 devices such as M5000 but i cannot get it to work with my BA. It seems to revolve around its inability to list activesyncing via BT as one of the BT services available. I have been in touch with the Missing Sync guys but no joy as yet. Any thoughts here?
The process sugested by Missing Sync is to set up a new BT partnership via the activesync tool on the BA. The two devices recognise each other and even seem to pair but after that no joy. Apparantly Activesync should be listed as a BT service but it isn't...
Really appreciate any help on this one.
Related
Hey Guys, I've been following the cool stuff on this site for some time. It's always appreciated to have people working this stuff out. The default ROM that came with my Verizon (Harrier) is crap compared to the Testra ROM I got from this site.
Anyways, the reason for my post is in regards to setting up the Harrier as a DUN Client to a BT DUN enabled phone.
I have BT DUN working from the phone to a PC so I know it works.
When I browse the available services on the phone from the PC I see bluetooth serial port and bluetooth DUN.
When I browse the available services on the phone from within the Bluetooth manager on the Harrier the only available service I see available is Bluetooth Serial Port.
I tried setting up a 'Connection' using the Bluetooth serial port to no avail.
Has anyone had any success with BT DUN out from WM 2003SE using
BT ROM 1.0.0 Build 3500? or with any other similar setup?
Any suggestions?
Thx,
Ian
1. Copy this file "BTWizardProfiles.dll" to IIs
2. Modified Registry in following:
[HKEY_LOCAL_MACHINE\ExtModems\bluetooth_dun]
"port"="COM7:"
"DeviceType"=dword:00000009
"FriendlyName"="Bluetooth"
iroessle said:
Hey Guys, I've been following the cool stuff on this site for some time. It's always appreciated to have people working this stuff out. The default ROM that came with my Verizon (Harrier) is crap compared to the Testra ROM I got from this site.
Anyways, the reason for my post is in regards to setting up the Harrier as a DUN Client to a BT DUN enabled phone.
I have BT DUN working from the phone to a PC so I know it works.
When I browse the available services on the phone from the PC I see bluetooth serial port and bluetooth DUN.
When I browse the available services on the phone from within the Bluetooth manager on the Harrier the only available service I see available is Bluetooth Serial Port.
I tried setting up a 'Connection' using the Bluetooth serial port to no avail.
Has anyone had any success with BT DUN out from WM 2003SE using
BT ROM 1.0.0 Build 3500? or with any other similar setup?
Any suggestions?
Thx,
Ian
Click to expand...
Click to collapse
Woot, It's working
Just wanted to say thx for the inf.
Thanks for the inf,
Ian
Dear All
Please help: I have an O2 XDA IIs which MS Activesync 4.1 does not detect, despite all my efforts during the last few days (I also have an old iPAQ 1940 which Activesync detects fine).
The XDA is from work, so could it be that it is somehow locked, and if so, how can I unlock it?
Also, as an alternative, can I sync the XDA with my PC via Bluetooth through the iPAQ's?
Any ideas will be gratefully received!
Many thanks in advance,
L
Hi there,
I've Looked through hundreds of forums and although I have seem similiar I haven't found a resolution to my exact problem.
Due to the fact that I've been trying to resolve this issue on and off all day it's probably something really simple... :roll:
HISTORY
PDA
Was running WM2003SE on a Xda IIS.
PC
ActiveSync 3.8 on Laptop with Windows 2000 SP4 and all updates. Laptop on a home LAN with router. No firewall software and have since removed all Spyware removal software, (after doing one last scan).
My Task \ Issue \ Problem
I wanted to to the upgrade to WM2005 and followed all the usual procedures. The one mistake I may have made was to install the very very latest 4.1 Activesync without removing 3.8. However at this stage my XDA was still on 2003SE and synced perfectly with 4.1 Activesync.
I performed the upgrade to WM2005 including patches and as far as the XDA is concerned everything appears to be working.
Activesync however doesn't work. Via the USB cradle Windows 2000 detected a device and under device properties it's was listed as Generic RNDIS, it's now listed as a windows mobile based-device. I don't have an entry in my network connections, although I think this only happens with Windows XP. I've tried uninstalling Activesync, removing the rapi.dll file, reinstalling etc, I even did the former and removed entries within the registry and running a registry fixer but to no avail.
I then decided the Bluetooth route but cannot sync via this method either. I can actually succesfully connect from PC to XDA and vice versa but cannot use these connections for Activesync.
I have another Hard Drive for this Laptop which I use for testing. I can simply shut down, swap drives and boot again to another build. The other build is also Windows 2000 with SP4 and pretty much nothing else. I've installed Activesync 4.1 onto this machine, plugged in the cradle and everything works fine.
So..... I know the XDA is fine, The cradle's okay and Activesync 4.1 actually works with my XDA OS. The problem is it doesn't work on one particular build. I believe this is actually a Activesync issue but due to some form of conflict with my build. It's currently out of the question for me to rebuild so my mission is to find out what's conflicting.
Just to summarise though..... Activesync 4.1 was working fine, I upgraded XDA to WM2003 to WM2005 and then it stopped. The other harddisk proves that Activesync does actually work with my XDA.
Pheeeew...... I hope somebody doesn't suggest lack of information.... :lol: :lol:
So the reason for the post?? Well if anybody else is having frustrations, (which I'm sure I'm not the only one judging my my searching), your not alone.
I think a lot of people's problems have actually been resolved by the latest version of Activesync, (4.1), and other people have resolved by sorting out the main culprit of firewalls.
For me though I'll keep searching..... if any of you can think of any other ideas I can use for diagnosing the problem I'll appreciate it.
Thanks in advance..... sorry for the waffle.....
RESOLVED
Okay.... During further searching I noticed people mentioning VPN clients interfering.
I did have SecureRemote VPN installed which I use for work purposes.
I uninstalled SecureRemote but had to uninstall & re-install Activesync again. This time it's working.....
I will, (but not tonight), re-install the VPN client and see what happens. If Activesync countinues to work then, apart from being happy, it's worth making a note of.
If it doesn't work then I'll start to investigate why...... I know the new active sync does some form of IP connection but I cannot accept that it won't work with VPN's installed.
use windows XP (SP2) ...
first install the activesyn and then restart your computer.
then attach your pocket pc with usb cable.
and try to connect.
its works for me...
I'm pretty sure i have everything setup on the pc right. Serial port is configured in WIDCOMM drivers as COM5. Activesync is setup to listen for COM5.. but on the ppc all i see is a serial port selection in the bluetooth mgr and not activesync.. Anyone have any tips to get it working correctly?
It isn't real clear from your post, but I assume you are trying to set up bluetooth sync.
Some avenues for you to explore:
Have you set up a partnership through USB connection? If not, this should be first on your list of things to do.
Have you paired the devices? Turn your PPC to discoverable in bluetooth settings and have your PC search for new devices. The wizard should pick up the PPC and walk you through the pairing process.
Does your bluetooth module support the correct services? Older bluetooth dongles and radios might not support syncing pim info.
I have the exact same Problem.
Did everything like it is described here in the forums. Firewalls and antivir deactivated. Used the right COM ports. Settings in Active Sync match. Pairing successful. The WIDCOMM-Driver even renames the Serial Port to ActiveSync after pairing. But even after all that, if I'm trying to get a Connection from my phone by using the ActiveSync on my phone with "connect via bluetooth", I cannot see ActiveSync there, just Serial Port. Switching on the Beam (like in some boards suggested) had no success either.
I tried reinstalling all. I tried my desktop PC and my Laptop (same problem). ActiveSync does know the XDA when I'm using a cable. I tried deleting the profile and create it again. I tried the Microsoft bluetooth stack instead on my laptop. I tried using another COM-Port. I tried deleting the pairing from the registry on the phone.
I have a XDA Neo / HTC Prophet with WM6 ProphetTouchIX, an Anycom BT-200 Bluetooth Dongle with WIDCOMM based driver. WINXP SP2 with the newest Security updates and Active Sync 4.5.
If anyone has any new suggestions, please post them here. If you have the exact same problem, post here, what you've tried to solve it, maybe we can at least find out, what's causing it.
found this one here:
http://forum.xda-developers.com/showthread.php?t=287820&highlight=widcomm+bluetooth
seems to be the same problem.
if you have Touch IX installed, you need the bluetooth fix from here:
http://forum.xda-developers.com/showthread.php?t=342302 .
worked for me. Give it a try!
Can someone give a definitive answer to this, I am using an Orange SPV M700 which I have flashed with the generic Dopod WM5 rom Version 1.23.405.2.
I have tried various WM6 roms and have had the same issues with them all, I loose bluetooth pairing authority, the wirless keys are lost and Tomtom map activations are lost too.
Is there a way to resolve this issue as I see there are a lot of users with the Trinity and WM6 in signatures, so someone must be doing something right.
After having flashed my phone from WM5 to WM6, the tomtom ID of my phone changed too... Perhaps Tomtom's support will help you with that?
I have no problem with bluetooth...
It's not that, perhaps I should have been a bit clearer.
After flashing to WM6 & pairing across bluetooth for the activesync, connecting it to my wireless & activating the tomtom maps, give it 24hours or so and these details are lost. Although the bluetooth PC is still in the paired devices, the pairing code needs to be re-entered as does the wireless key if I try to connect to that.
The Tomtom map needs reactivating again also.
peterelliott11 said:
The Tomtom map needs reactivating again also.
Click to expand...
Click to collapse
I already read somewhere about this.
When you do some pairing with bluetooth and PC sometimes you lose the maps!!
Don't have further details though
I have had the TP2 for a couple of weeks now and am generally very happy with it, but for some reason the Sim Access Profile is not working correctly with my Audi. I have paired the phone with the car and have enabled SAP in the phone's BT advanced settings page. Unfortunately the car will only access part of my phone book (only contacts under A to B are showing). The phone has all of my contacts on it and all of the other features of SAP seem to be working. I know that I can use JETware as an alternative but would like to know if I am doing something stupid with the phone before I go down the JETware route.
Any help would be appreciated, thanks.
I put my problem / question in this thread:
I use the TP2 in my skoda with a audi BT-SAP-Adapter this combination works, tested it before with my S/// X1.
When i pair my phone with the sap-Adapter the adapter recognizes that the TP2 can use the SAP-BT-profile and use the longer pairing PIN (when you pair a mobilephone wich has no SAP-profile the adapter use the Handsfree-profile and shows you a shorter PIN). As far, everything seems to work great.
But when my TP2 want´s than to connect with the adapter i see that the statusline shows the typical symbol for the flight mode and in the BT-menu at the BT-adapter i see the words "SIM-Access" for very short time (~ one second). Next the line “Stereo-profile” or something else (it is to fast to read) appears and half a second later the line “Handfsree” appears. The Symbol for a handsfree connection is shown at the statusline and the sign for flightmode changes back to the normal symbol for filedstrength.
what i tried as far to solve the problem:
1) i contacted the HTC-Support. They told me. that they made, at the moment, a test-row to solve specially the problems between HTC-WINMob-Handsets and car-handsfree-sets. So i got from there a software which i had to install at my phone and got a error-report. This i had to sent to HTC. No further comment from them.
2) i searched at very much forums at the car and mobilephone scene.
3) I tested the combination with different SIM-cards from different Providers and different ages.
4) I deleted my contacts at my SIM and wrote some newer one with an NOKIA Phone (this helped by some other SAP-car-FSEs)
5) I used No-Data
6) I installed the newest radio-rom.
Nothing of this brought some solution.
As i found at my recherches i´m not the only one who hast this problem with the HTC and sap-car-handsfree-set.
I thing, that this is a problem with the BT-Stack which is used at the TP2 and other HTC, is it?
Dose somebody solved this problem? Even with an other HTC with the same BT-Stack???
Has somebody any other idea to solve the problem??
Any help??
Merci
Quino666
I had no problems with SIM access on my 2010 A3 TDI -- worked flawlessly with my Tilt 2 with stock ROM. I haven't checked the car's phonebook lately, but last time I looked, everything was there.
1) With update on WM 6.5 or the first WM 6-version of the ROM?
2) Do you use a build in Handsfree solution with sap-profile or the adapter-solution?
Merci
Quino666
Hey,
I have a similiar Problem with the rSAP snap-in Adapter in my 2010 iDrive BMW. rSAP (telephony) just works great, but it only syncs the simcard's PhoneBook entries.
The BT-Monitor on my TP2 (Energy Rom WiMo 6.5.6) shows an active SAP and PBAP connection. Any ideas how I tell my TP2 to distribute the internal Exchange contacts and not the SIM-Contacts?
bye
Darky