I don't know if it is something i did or something wrong with the recent custom roms, and yes i did search but could not find this specific issue.
In Bluetooth setting under com ports I do not have the option for "New Outgoing Port" I was going to use GPS2Blue but can't unless i can add an outgoing port.
If this is answered in another thread i apologize but i couldn't find it.
BTW thanks for all the great work DCD, your kitchen and all the work you have done is amazing. (but i did root against the red wings, being a STARS fan and all)
anyone have a suggestion?
Something reminded me of bluetooth issues, and I thought I would look into it for you. Unfortunately, I can't be of much help because I don't use the setup. However, I was wondering if you already set up the devices you want to use. I think the port can only be set up once the devices are talking.
It does say on the bluetooth settings on the COM ports tab that "After pairing with a device, to setup aup a COM port tap New Outpoing Port"
I only have my Plantronics BT headset so not needing an outgoing port so none show up for me.
i have the devices paired up but still the option for "new outgoing port" is not available
I have tried this on several version of dcd and still no go. I am pairing up with a nokia n800 which i know works with other windows mobile devices.
any ideas would be great.
thanks
Related
I'm just recently using tom tom for first time and TOM TOM tells me everytime that COM1 doesn't exist.
I'm able to downgrade back to plain old 2003 to try it , however I'd rather have a fix or work around before I do so....
any thoughts or experiences?
Hi,
This will happen if the GPS cable is not connected correctly. Disconnect the cable and reconnect then start TomTom. I get this now and then. Everytime i reconnect it works just fine. Also check within TomTom if it is configured to use COM1 via serial and not Bluetooth.
Cheers
Jay
Right, just been down to the car, everythings plugged in correctly, tried multiple soft resets but keep getting the message "cannot open COM1: Port Does not Exist"
I tried using the serial on USB option instead (just clutching at straws) and get no error messages, just GPS Position unreliable. As far as I can see TOM TOM knows something is being plugged in as the flashing disconnct icon dissapears when i plug in the GPS reciever.
Any further ideas? I want to try it having downgraded back to 2003 but I don't have any backup software apart from xBackup and I'm reall yfond of SE.
Solution to Com 1 problem
Hi,
Go to connections, and disable the IR search for other devices, and IR in total, then the COM 1 is released.
Took me quite some time to figure that out my selv when having the problem.
Cheers.
Esor
Missing COM1 Port
This happened to me too and I discovered that it was being caused by the IR Beam being on receive by default. This inhibits the use of COM1. Solution - Navigate through the System functions to find the IR Beam option. Disable that and this may solve your problem.
Cheers Hissing Syd, I was just about to try flashing my rom but this fixed the com1 issue, next to try it in the car..
Going through the development forums I discovered this thread http://forum.xda-developers.com/showthread.php?t=353774 .Someone posted a link to download a better bluetooth manager , after downloading and started installing it, the installer said it was helmi universal stack.And after looking around I discovered helmi was testing this new stack he was porting to htc universal and had headset and a2dp profiles working.So after installing I rebooted and the icon showed at the bottom so to test i clicked start bluetooth and to my surprise IT WORKED !! on my x7500 runnin the official wm6 from htc.On helmis thread he noted that it might work for apache but I confirm it runs on athena.Anybody else have feed back?
!!!!! BACKUP AFTER FURTHER READING SOME FOLKS HAD PROBLEMS IN TERMS OF TOM TOM AND AUDIO MESSUPS AND LOCKING SO BACK UP FAIR WARNING!!! THIS FOR PLAYING WITH IF YOU BACKED UP OTHERWISE YOU CAN MESS UP UR PHONE!!!! I TAKE NO RESPONSIBILITY AS IM TAKING A RISK MYSELF WITH NO PROBLEMS THUS FAR ON MY PHONE.
you can download it from
http://rapidshare.com/files/78498277/Broadcom_Bluetooth_Manager.CAB
helmi universal broadcomm stack thread here,also tells how to restore msft stack
http://forum.xda-developers.com/showthread.php?t=291639
supported profiles is avrp,a2dp,obex,sap,handset.bt dun,pan,serial.
THIS IS NOT MADE BY ME I SIMPLY FOUND IT IN THE FORUMS.I KNOW THIS WORKS FOR MY DEVICE (X7500 Running Official WM6 From HTC) .ANY OTHER DEVICE OR CONFIGURATION I DONT KNOW CHECK RESPECTED FORUMS FOR POSSIBLE SOLUTION
SPECIAL THANKS TO HELMI FOR PORTING THIS WONDERFUL STACK SO CHECK OUT HIS THREAD ABOVE.
How have you got on with this? BT is really the last bit of the Athena that I am not 100% happy with.
It's seems to work.
Installation with no problem and the bluetooth start.
But i think there is probleme with serial port.
I want to pair a bluetooth barcode reader (Opticon OPL2724). The dongle's driver installs a serial port on the PDA X7500 wich is used by the barcode reader to transmit the data.
I can connect the barcode and i can see in bluetooth manager that the barcode reader is connected (ingoing connection). Just like with my asus P535 with a native widcomm stack.
But I can't receive any data from the barcode reader
Is there a problem with registry setting for serial port ? This stack is for Universal and maybe there is some fix for X7500 especially for the serial port profile.
Please M. Helmi, can you help me. I would love to have this stack working with serial port and my barcode reader !!!
Hmm - just tried this to see if it fixes the problem with my Style-i going out of range all the time and although it shows as connected and I get the headphones on my Athena nothing I do on the Style-i Gets sent to the Athena and music playing comes out on the Athena not the Style-i - so it's just like it isn't connected really!
Oops - went to uninstall it and my phone hung - rebooted and it didn't - after first splash screen it just went bright white. Had to reflash.
Oh well, it probably needed it anyway!
Is there an impact on the GPS? The earlier post mentions possible problems with TomTom
Mrsums said:
Is there an impact on the GPS? The earlier post mentions possible problems with TomTom
Click to expand...
Click to collapse
Yeah I found out later on the stack is configurd to the free ports on universal but on athena it conflicts with gps.Gps port is com 5 ,but the bluetooth stack uses com 5 as outgoing serial port.What i did in registry is simply change the gps comm port in registry to comm 9 then configure progs to use that for gps port and it works.Using builtin gps option doesnt work because gpd0 keeps using comm 5 and I believe thats coded in a dll somewhere.
In my original post I mention if you wanted to uninstall the stack to check out that helmi thread because it explained how to do so and it even had a activate ms stack cab there.I Did say backup before install.
Also found out that if you have stack running and reset it deletes connection settings, activesync settings and hides phone setting tabs ( I used schaps tools to fix that)
For now I dont use this stack anymore untill helmi or someone who has the knowledge to make a few simple fixes ( I GUESS MOSTLY REGISTRY) to get this working 100 percent on athena.
the file is expired, could someone who has it post it with a little bit more details about installation process
thansk
I would like to see this as well
I used the older Helmi stack on my Universal and it was much better it's the only one that works with the Chainpus/Random branded Bluetooth Gamepad as their MS Stack drivers does not work with their own product but generally seemed a better stack overall. I'm tempted to give this one a whirl and see if it behaves as the older one was a bit buggy when I tried it before and had to do the whole hard reset thing.
Hopefully this will be the topping on the cake now I have AP4 up and running
Hello,
I setup my voip on the PK3.0 rom, its dialing and it almost works. Except that I can not hear anything, I can speak and the other party hears me just fine, but I can not hear them, anyone came across this? What can you recommend to fix this?
bump, still no resolution to this, it works fine one way. But I can't hear anything the other person is talking....
Anyone?
marek101 said:
Hello,
I can speak and the other party hears me just fine, but I can not hear them
Click to expand...
Click to collapse
This isn't going to help much but .... sounds like the perfect setup to me.
Hi Guys,
I am trying to run VoIP on my device (which is not athena by the way) and have absolutely the same issue. I have very good knowledge in the voip networks and very good experience and this thing makes me crazy (believe me)
As what i already found is there shouldn`t be any issue:
the RTP is going between the end points without any troubles on the correct ports and everything looks just perfect - i.e. there is no any network issue, SIP communication (SDP related) issue or whatever like that
The possible problems for me are as follow:
- codecs issue - actually if you can make a call and the other side pick it up without the line to be dropped, then this is not the case (at least the codec on windows mobile is working)
- the audio output device - the audio is trying to go out trough a device which is not present on your system - so you are not hearing anything.
I will be glad to chat to anyone who have the same issue and can help me to debug the problem and find the permanent solution. I don`t have big knowledge on windows mobile devices (but at least know how to install cab files and modify the registry settings - hehe) so to anyone who is in deep relationships to this system and can help me -- give me your msn/icq/skype/jabber contact and lets pray together
salasbg said:
Hi Guys,
I am trying to run VoIP on my device (which is not athena by the way) and have absolutely the same issue. I have very good knowledge in the voip networks and very good experience and this thing makes me crazy (believe me)
As what i already found is there shouldn`t be any issue:
the RTP is going between the end points without any troubles on the correct ports and everything looks just perfect - i.e. there is no any network issue, SIP communication (SDP related) issue or whatever like that
The possible problems for me are as follow:
- codecs issue - actually if you can make a call and the other side pick it up without the line to be dropped, then this is not the case (at least the codec on windows mobile is working)
- the audio output device - the audio is trying to go out trough a device which is not present on your system - so you are not hearing anything.
I will be glad to chat to anyone who have the same issue and can help me to debug the problem and find the permanent solution. I don`t have big knowledge on windows mobile devices (but at least know how to install cab files and modify the registry settings - hehe) so to anyone who is in deep relationships to this system and can help me -- give me your msn/icq/skype/jabber contact and lets pray together
Click to expand...
Click to collapse
I would be very much interested, how would you go about by debugin' this ?
salasbg said:
Hi Guys,
I am trying to run VoIP on my device (which is not athena by the way) and have absolutely the same issue. I have very good knowledge in the voip networks and very good experience and this thing makes me crazy (believe me)
As what i already found is there shouldn`t be any issue:
the RTP is going between the end points without any troubles on the correct ports and everything looks just perfect - i.e. there is no any network issue, SIP communication (SDP related) issue or whatever like that
The possible problems for me are as follow:
- codecs issue - actually if you can make a call and the other side pick it up without the line to be dropped, then this is not the case (at least the codec on windows mobile is working)
- the audio output device - the audio is trying to go out trough a device which is not present on your system - so you are not hearing anything.
I will be glad to chat to anyone who have the same issue and can help me to debug the problem and find the permanent solution. I don`t have big knowledge on windows mobile devices (but at least know how to install cab files and modify the registry settings - hehe) so to anyone who is in deep relationships to this system and can help me -- give me your msn/icq/skype/jabber contact and lets pray together
Click to expand...
Click to collapse
Hi!
I start by stating that I finally got it "working"! Yeahh! This "thing" costed me a hard reset and a lot of frustration. Let me write down what I think is the issue/"solution".
I say "working" because it is almost impossible to get the sound out of the Athena, unless you use a bluetooth headset (I haven't tried the wired one) and the supplied Voice Dialer.
To keep it short, for the Athena X7501 here is what you need to do to have "native" VoiP working partially as thought:
Connect the BT headset
Leave the Voice Dialer activated (Cyberon Dialer, provided in the original ROM). That means that the relevant entry in the registry shouldn't be set to '0': HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\LaunchAPEnable
Connect to your VoiP Servce and launch the phone. Now you should see your VoiP provider as agent. Dial the number (Good luck with the ipdialplan.xml) and you see that the Voice Dialer pops-up! Ignore it. The relevant communication port is happily already taken by the VoiP. You hear the sound on your bluetooth Headset. If you like, you can now transfer the sound to the speaker!
To my understanding, after having spent hours on this issue, I think that this is due to a DLL modified by HTC. Don't ask me which one. There is NO registry entry you can play with to solve it, unless you 're really lucky with the DLLs provided. It seems that there was some kind of agreement to make life very difficult to those trying to communicate through VoiP. I personally use VoiP only at home and don't bother too much. Maybe all this is history in the cooked ROM. Let's see.
If you don't need the Voice Dialer, then I suggest you use Fring. It works well both ways. However to use a Bluetooth Headset, you need to deactivate the Voice Dialer in the registry.
I hope this helps.
Rgds
Dod
P.S. The above are applicable to the original US Rom of X7501
There has been a discussion at Skype with respect to 6.1 and Skype failing to work correctly http://forum.skype.com/index.php?showtopic=112059
Maybe this might be of help.
Strange problem. Maybe you can try with software like fring.
Ran it on pk3 without any trouble and now running it with the 6.1 rom and still working fine
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
The SF didnt show this question, yet.
While trying to connect a BT device (mouse) I encounter the following problem: The S3 asks for a PIN for this device and the field cannot be left blank cause the continue button remains inactive then. The BT mouse does neither require a PIN nor does it work when any key is entered here.
Anyone got a solution for this issue?
Thanks, Don
every BT device like you have, have specific method to pair.
I have Jabra bluetooth headset, and I have to press the specific button on my jabra, so it can be paired with another blutooth (PC/cellphone).
try read manual on your mouse official website.
for me, that's not S3's issue.
bibia said:
every BT device like you have, have specific method to pair.
I have Jabra bluetooth headset, and I have to press the specific button on my jabra, so it can be paired with another blutooth (PC/cellphone).
try read manual on your mouse official website.
for me, that's not S3's issue.
Click to expand...
Click to collapse
Men never read manuals, u know
OK maybe some additional details are helpful to grasp the problem.
I used this mouse with several different hosts, Win7 PC, Galaxy S2 and others. Pairing is usually easy as you just pair it and leave the PIN blank and that's it. The problem simply is that u can't leave the entry field for the PIN blank on the SGS3 (rooted with stock rom) wheras u can do so on other devices. And that makes it an S3 issue I assume.
Cheers,
DON