Has anyone successfully connected to serial and communicated with the Note 4? I have attempted to with several terminal programs and cannot get it to work.
The overall purpose is I have a .NET bluetooth plugin that uses Bluesoleil and when I send AT commands to attempt to determine phonebook entries I get nothing but jibberish. I know this normally means COM port settings, but I have tried all baud speeds and settings with the same luck.
When I try my wife's iPhone, it responds to the commands perfectly. This either means the phone has issues with AT commands or the driver has compatibility issues with just the Note.
Anyone have a similar setup that has made it work?
Related
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!
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.
OK so this may sound like a broken record, but i will NOT ask 4 help if i feel if i haven't already tried everything else. So here goes (takes a biiig deep breath) .......
This has worked exactly one time since i've upgraded to the kavana 6.1 ROM. I know it's not something wrong with the ROM that would require a reset, since this currently works on my work PC which uses the bluesoleil BT stack.
These are the many many steps I have already tried ( with a little assistance by a few of you already) :
I have made sure that i have gone on my PC to control panel-->bluetooth local COM. Created a toshiba COM port (server-side not client) and have created COM ports ranging from COM Port(s) 2,3,5,6,7,8,9,10,15,16,17,18&19 and each time I've created those COM Ports, I have also mirrored that COM port in Activesync (v 4.5) on my PC to read that COM Port. Second, I have removed any previous pairings from both the PC and from my phone. I then start activesync on my phone and of course it does not detect a partnership, so I search for BT devices and find my PC. I pair to it and when I get to services, it shows wireless stereo and serial port. At this point, I know that I am connected to the PC via BT since my BT icon on my sytem tray has gone from blue w/white BT log to blue w/green BT logo. I then refresh my services several times only for it to give me the same previous 2 services as before. So I thought "maybe it's detecting a serial port that im not assigning Activesync to?"
I then delete the serial COM port I just added in the control panel and refresh my services again on my phone and low and behold, the only service it now shows is wireless stereo. ( SO THIS MUST MEAN THAT IT IS ONLY DETECTING THE SERIAL COM PORT THAT I AM CREATING RIGHT?) I have tried creating a new outgoing COM port on my phone. ( have tried both COM 6 & 7 and also secure connection checked and unchecked. I have also turned on and off OBEX security on my phone. ) I have even tried completely removing activesync and the toshiba bluetooth stack from my PC and re-installing. I have even gone as far as installing toshiba BT stack ver. 4,5 & 6.
Heck, I even found a trial version of bluesoliel just to see if it worked and it didn't even work, same thing with the default MS BT stack. Same issue. I have tried the pairing process from my PC but the only service it wants to connect going that route is wireless file transfer. I have my security on my toshiba BT stack set to low, ( I've even tried standard too) I have tried turning off my firewall (windows firewall only). I have tried disabling my anti-virus ( avast! home edition). I even tried chaning the device name to see if that would work. But no go. Both devices (PC & Phone) have been reset a multitude of times. I have absolutely no problems connecting my device via ActiveSync using the USB Cable. I have tried checking and uncheking the allow USB Connections in connection settings in AS.) I have even tried connecting via connection settings to sniff out the COM ports while I'm trying to refresh the services on my phone at the exact same time it shows smiffing the com port I'm connected to.
So, as you can see by my book I have now written. I am at my wits end on this. Hopefully that wasnt too much to read. I felt like it was important to give you everything I have done so far as not to leave no stone unturned. I really hope this is some sort of simple oversigt on my part. and will welcome any suggestions from anyone, but please, only post a suggestion if you have read what I've already been through. I am not a novice, not a noob and and extremely proficient on my own handling these issues usually. However, I am humbling myself this time for any suggestions that might be a great help.
Thank you and Godspeed.
Anyway. I'm closing my thread. I didnt necessarily figure out exactly what the problem was, but i did somehow, some way fix it.
What id did do in addition to the aforementioned steps was:
i went into regedit on my PC @ HKCU-->Software-->Windows CE Services and i noticed the "defname" value was set to a previous name i had set for the phone. So i changed that to reflect my current phone name. I also changed HKCU-->Software-->Windows CE Services the "serialport" value from COM7 to COM6.
I then went to HKLM-->Software-->Microsoft-->Windows CE Services and Set the "serialport" value to from COM7 to COM6.
So i then opened up control panel and went to bluetooth local COM and deleted any com ports that windows would let me. I then created Com port 6 to be server side serial port. Then i went into activesync on my PC--> connection settings and set it to read COM Port 6. I then removed any pairings from both my PC and my phone and from the phone, I searched for new bluetooth device. When it found the PC it I then saw the bluetooth icon change to green in my taskbar and the active sync symbol started spinning for a couple of seconds. Once i finished adding the device on my phone, I then attempted a connectiion via bluetooth from my phone and voila! i was connected! I went ahead and rebooted both my phone and my PC after i saw that it worked to see if it wasn't a fluke and tried again once both devices were rebooted. And this time......wait for it......It works still! Hooray! So now that i have less than half of the hair in my head since starting this gauntlet of terror. I can now say. PROBLEM SOLVED. Maybe this will help others that may have had this issue b-4. The one thing i read on another forum that i hadn't tried yet (which is most likely what solved it 4 me) was that i made sure i removed any com ports, whether it me server or client side com ports on my PC and i left them off when i created just one new server serial COM port.
Greetings,
Does the ModemLink application support the T-Mobile Dash? I am attempting to use it with WM6 over USB, but when I attempt to activate it I get an error stating "Unsupported or Unavailable connection."
I have found several articles detailing very specific steps for creating a USB ModemLink connection, but none of them have resolved my issue. I have reset my phone to factory defaults to ensure that no settings are to blame. I need my phone to appear as a literal Modem (more specifically a GSM Modem) to the computer, capable of using HyperTerminal to issue AT Commands to the Phone.
Dozens of Google searches into this, the only info I have been able to find is that ModemLink tries to connect over Com8, and apparently Bluetooth connections also use Com8. I can see in the registry (HKLM\Software\Microsoft\ATCIUI) a 'Connections' entry of 'USB|COM8:|' which would lend credibility to that bit of research. However, I have disabled both activesync and bluetooth entirely, and the error persists.
Any help on this would be great. I intend to try modifying the Reg to use Com6 as a basic test, but other than that I am at a loss.
Thanks in advance.
I've searched all over for this and I haven't found a solution. I've even decompiled APKs and deodexed the bluetooth odex searching for some clue on any way to change this, but I haven't found anything.
I've actually found a workaround in my particular case, but I'm still curious as to why this is happening and how no one has noticed...
So my Galaxy S3 will not pair with a bluetooth SPP device that has no passcode. I've paired with devices that support SSP without a passcode, but I can't pair with insecure devices. The reason I am trying to do this is because I need to stream GNSS data to a GPS receiver. The receiver is a Navcom SF-3040. For anyone searching, the workaround was to change to the PIN on the device to something other than "no pin". It was a pain in the ass though considering I can't find any 64 bit driver for this receiver and had to find a 32 bit Windows PC to use.
But my question still remains and I'm curious if anyone knows anything about this. After I successfully paired my phone with the receiver, I deleted the profile off my phone and I deleted the PIN from the receiver again just to reset it and see if it would work, but it didn't. The phone would still ask me for a PIN even when the device didn't have one, and there's no option to continue without inputting a PIN. Inputting any standard PIN like "0000" or "1234" didn't work. The only way to pair my phone with the receiver was to set a PIN for it.