Bluetooth pairing process is different, 6.0 vs. 6.1 - 8525, TyTN, MDA Vario II, JasJam ROM Development

The device is Holux GPSlim 236. The phone is Hermes. The phone will pair without question on a 6.0 rom, does not matter who cooked it.
It will specifically not pair with 6.1 roms.
I can see the device when scanning for bluetooth devices, i can choose it, it asks me for passcode, but will not accept the "0000" as the passcode. (tried hardware and software keyboards). IF i type in a passcode OTHER than "0000", it appears to pair, i can see the spp slave service and select it, but once the gps software tries to talk with it, it asks to pair again.
Something is definitely different in the pairing process between 6.0 and 6.1.
Any suggestions are greatly appreciated.
Also see thread about it here from the Himelaya:
http://forum.xda-developers.com/showthread.php?t=378103
Thanks,
Rock

Did you select it as a serial port? You have to do this after you pair the device with the phone!

I am not familar with gps units, does it have a pairing mode like a headset? I know with my Plantronics headset, if I let my phone discover it without the headset being in pairing mode, the phone says it pairs with it, but it really doesn't, so I put it in pair mode then turn on bluetooth on my phone and pair up as normal(0000 passkey) and all works fine.

I have exactly the same GPS unit and have no problem pairing it with the probably 15+ WM6.1 roms I have tried.
Try leaving the battery out of the 236 slim for a few minutes and see if that helps. (can't remember is there is another way to reset it)

Bluetooth Pairing with 6.1
In the latest PC Pro magazine in the UK, there is an article on WM 6.1. It says:
"There's another neat feature in WM 6.1, namely that when you try to pair the phone with something like a GPS dongle or hands-free kit that has a fixed PIN, the operating system will cycle through a set of common codes (0000, 1234, 8888 and so on) to try to find the right one."
It goes on to say that there is the potential to get locked out of the pairing if it goes wrong.
I have to say that I have not had any problems pairing with my GPS unit and my car kit, using a number of 6.1 ROMs. Indeed I have seen no evidence of the above software routine trying to pair for me. Possibly, that routine will only appear in the production ROMs, rather than the development ones which we use on XDA Developers.

I had issues with the same device on some roms. I eventually changed BT drivers from WM6 and all went back to normal.
On some WM6.1 roms things went OK though.

Try not using any password when you try and pair it manually.
If it asks would you like to pair your device automatically select no and do it manually.
I was having this problem but WM6.1 does not require a bluetooth passcode for most devices.

mines gps is a holux 240 and i have the same probs
ive mentioned it on a couple of threads, im glad to know im not the only one
im stickin with K's 6 final until this problem gets sorted out

this thread doesnt seem to getting any viewing, so im asking could a mod move this to General Discussion>networking please, it might be sutible there

crusti said:
this thread doesnt seem to getting any viewing, so im asking could a mod move this to General Discussion>networking please, it might be sutible there
Click to expand...
Click to collapse
ummm no, dont move my thread thanks. you can start one over there if you would like.

crusti said:
mines gps is a holux 240 and i have the same probs
ive mentioned it on a couple of threads, im glad to know im not the only one
im stickin with K's 6 final until this problem gets sorted out
Click to expand...
Click to collapse
You are not the only one
I reverted back to the 6.0 and it pairs without issue. I am thinking that alot of these cookers do not pay much attention to the development of bluetooth in some of their roms. Its not like I changed something on the GPS, so something must have happened with the software.... Still investigating. I hope it works on schaps new rom.

miffymiffy said:
Try not using any password when you try and pair it manually.
If it asks would you like to pair your device automatically select no and do it manually.
I was having this problem but WM6.1 does not require a bluetooth passcode for most devices.
Click to expand...
Click to collapse
this method paired my jabra automatically, it didnt even ask if i wanted to do it auto, i juck clicked "pair" and there it was.
When pairing the holux 236 on the other hand, it would ask for a passcode, then reject it if you put in the correct code of "0000". If you canceled it, it would appear in the connected devices list!!, but still ask to pair once the gps application tries to connect. VERY jacked up.

Hissing Syd said:
In the latest PC Pro magazine in the UK, there is an article on WM 6.1. It says:
"There's another neat feature in WM 6.1, namely that when you try to pair the phone with something like a GPS dongle or hands-free kit that has a fixed PIN, the operating system will cycle through a set of common codes (0000, 1234, 8888 and so on) to try to find the right one."
It goes on to say that there is the potential to get locked out of the pairing if it goes wrong.
I have to say that I have not had any problems pairing with my GPS unit and my car kit, using a number of 6.1 ROMs. Indeed I have seen no evidence of the above software routine trying to pair for me. Possibly, that routine will only appear in the production ROMs, rather than the development ones which we use on XDA Developers.
Click to expand...
Click to collapse
Did that article describe any way of disabling that feature? That functionality could easily trick a simple bluetooth device if it is not expecting such a rampage of codes...

rock99rock said:
Did that article describe any way of disabling that feature? That functionality could easily trick a simple bluetooth device if it is not expecting such a rampage of codes...
Click to expand...
Click to collapse
No, there was no mention of if it could be disabled.

Wam7 said:
I have exactly the same GPS unit and have no problem pairing it with the probably 15+ WM6.1 roms I have tried.
Try leaving the battery out of the 236 slim for a few minutes and see if that helps. (can't remember is there is another way to reset it)
Click to expand...
Click to collapse
Wam, which rom are you using now that it works with? id like to download and try it. The 5 or so ive tried did not work.
I power cycle the device without any change in pairing succession.
Thanks!
BTW: Other users experiencing differences between 6.0 and 6.1
http://forum.xda-developers.com/showthread.php?t=391488
http://forum.xda-developers.com/showthread.php?p=2240665

Related

Has any one taken this ROM appart yet? It has uptated BT.

It is from an HP 6315 from 3/31/05
http://h18007.www1.hp.com/support/files/HandheldiPAQ/us/download/22539.html
I would love to see if we could get this stack and the settings on our XDAII and other HTC devices,,, THAT would be cool.
Bluetooth build 1.0.0.3701:
Corrects inaccurate display of headset icon when a call is in progress.
Adds a check to determine if Bluetooth stack is initialized before accepting messages from phone.
Adds a user interface (UI) change to enable a connected headset to automatically disconnect before attempting to connect to a different headset when the user chooses to connect to a second headset.
Corrects check for invalid device name.
Corrects issue where handheld could not reconnect to remote device after a page timeout.
Corrects Object push profile update so it sends all files.
Updates FTP connection wizard to correct service discovery issue.
Corrects issue with call waiting for incoming call handling while dialing out.
Corrects issue with headset connection icon so it is correctly displayed after power cycling.
Corrects audio to make it compatible with an in-car solution.
Corrects audio issue where the right channel for a headset was unavailable for playing audio and during calls.
Corrects issue where the LED and network status were not properly synchronized.
Corrects issue where the user could not send multimedia messaging (MMS) message.
Hmmmm....a few remarks, correct me if I am wrong:
1. There is already a BT version 1.0.0.3900 available
2. This is not a HTC device, so I doubt the tools developed here will work on it.
HappyGoat said:
2. This is not a HTC device, so I doubt the tools developed here will work on it.
Click to expand...
Click to collapse
This is an HTC device. All HPs are designed by HTC.
Well, even though I don't want to stop progress because I would like to have the ROM taken apart for my own personal reasons, the 6315 was actually made by Compal. Bad move on the part of HP in my opinion. However, the bluetooth stack that was taken from an iMate JAM worked on the 6315 and that is how most survived until the update was released. So it very well could work on the HTC's. On a side note, if someone could point me in the right direction, I will take the ROM apart, just don't know where to start.
mamaich said:
HappyGoat said:
2. This is not a HTC device, so I doubt the tools developed here will work on it.
Click to expand...
Click to collapse
This is an HTC device. All HPs are designed by HTC.
Click to expand...
Click to collapse
Oops....my bad....excuses!
no htc dont make ALL hp's pda's the H5400's was oem'd from LG
and even if the ipaq in question is made by HTC then that dont garentee that the xda tools work as they are not made by HTC
I can tell you now that the XDA tools do not work on that ROM as it stands. However, looking through the HEX, it is laid out a little differently than the XDA ROM's but have some of the same portions, just in different locations. Now if I knew more about what I was looking at, I could take it apart for you. The 6315 uses Widcomm BT and like I stated before the BT drivers ripped from a JAM worked great on the 6315 so I have a feeling the 6315 drivers will work on the XDA's.
I can also tell anyone looking at it that in the first header of the ROM the letters are shifted 13 characters. So when you see RAT it equals ENG and so on. It looks like they don't do that for very long though.
BT
HappyGoat said:
Hmmmm....a few remarks, correct me if I am wrong:
1. There is already a BT version 1.0.0.3900 available
Click to expand...
Click to collapse
BT 3900 and 3500 do not support Hands Free Profile or even Headset Profile on my XDAII.. This is important so people can use Caller ID on a BT device and OR a Car Kit with the Hands Free Profile....
Switching stacks is a pain in the but...
Even so, the only OS that even slightly works with Hands Free on the Himalaya, is 2.20 translated but even that has bugs that makes it very frustrating. The 2005 did have a fully functional BT, even having separate serial ports for each BT device, (like GPS), but the other bugs and the limited memory left over from the useless and unerasable Extended ROM from the other OS made it no good..
With this new ROM, I may be tempted to buy the HP again.. When I first bought one, it was DAM slow and the BT SUCKED!!!
Maybe now it is usable.
I love my Himalaya and it's 128 of built in..
http://www.expansys.com/product.asp?code=PDA2&asource=IMATE
http://www.expansys-usa.com/product.asp?code=PDA2&asource=IMATE
I will just have to keep waiting for one of the above unless someone finds a fix for the BT Hands Free.

Different Bluetooth Stack?

I've been struggling for several months now to get my MDAC III working with my built-in car Bluetooth hands-free. The full details are below, but in short, I'm told that the system seems to work OK with Wizard, and I'm wondering what about the Wizard could be different to the Artemis (Bluetooth stack perhaps?), and if there is a difference, is there anything I can do about it?
The full issue: The system I'm trying to connect with is in a Land Rover Freelander 2 (LR2 in the US) Initial pairing was a bit hit and miss, but now I've got the the phone paired with the PTI, that's not a problem and they automatically pair whenever I start the car.
I can succesfully initiate or answer a call from the car, but the call itself isn't routed through the car's speakers/mic, it just goes through the phone as normal. However, once in a call if I select the "privacy" option on the PTI (which would normally have the effect I've already got of passing the call to the phone), and then select the "hands free" option, it does what it should and routes the call through the car. Effectively, it's as if the system starts in "privacy" mode rather than "hands free". Once I've done this once, subsequent calls work fine, routing straight through the car, but only until the ignition's turned off. The next time I start the car up I'm still paired, but calls go through the phone again.
If anyone's got any suggestions, I'd really appreciate them.
Thanks!
Try this
Had similar in a BMW...
Try www.jetwaremobile.com
Thanks, did try that but didn't seem to help, it seemed to be more geared towards additional functions like phonebook syncing rather than just getting a working connection in the first place. Maybe I'll give it another go.
Same Probleme On 207
hi,
I have the same ....
I precise that work fine with the original m650 rom, i search many hours but i found nothing, i try bluetooth toggle with no effect...
please help us !
thank for dev for everything they do !
RE
I try many combinaison so:
if i want to use my bt car kit, i'm forced to validate hands free option at every phone call...
I think it's btaudiotoggle the cause of mly problem, he is included in the aje rom...
you think it's possible ?
TangerineTractor said:
Had similar in a BMW...
Try www.jetwaremobile.com
Click to expand...
Click to collapse
Thanks TangerineTractor!
I fixed the problem I have with car kit of OPEL ANTARA using the software you said. It works disable sending Phonebooks.
I am having a similar problem with Wizard Mobile 6 cooked ROM. Before with the official O2 ROM on my Xda Mini S, it worked fine. The car would automatically recognise the phone whenever in proximity, and all calls would go through the speaker.
Now, I have to press the car kit's button (Nokia Bluetooth) each time I get in the car, to tell it to search for devices - i.e. the phone doesn't automatically announce its presence.
So, is there a different Bluetooth Stack we can try?
My Orbit works fine with my Nokia CK-7W using a B&B ROM.
Thanks, and yep that's the same car kit I have.
When you get in the car, do you have to do anything, or does the car kit automatically detect the phone? Mine doesn't since getting the Wizard Mobile 6 cooked ROM.
Do you know what Bluetooth Stack you use, and if I can download it anywhere for the Wizard?
No, just switch on the ignition key and away it goes. Also if the car kit is set as the default hands free if the phone rings it should try to connect to the car kit.
The radio I am using is 2.95.90 I have no idea what bluetooth stack it is, Tom Codin cooked the ROM, he will know.
Okay thanks. Does anyone know if the BT Stack is part of the Radio ROM? If so I'll just try a different Radio ROM.

Tomtom 6 is purposedly disable for the Tytn ??

Having just bought a Tytn I found that my tomtom 6 didn't work. I seemed to have two issues. 1) It hung up frequently and 2) It kept losing my external bluetooth GPS receiver.
I thought I'd go to Tomtom's page to see if there was a fix given that HTC mention this saying that Tomtom have updated version 6 for the device.
http://www.europe.htc.com/en/htctytn/support/faq.html?id=539&cat=applications
To my horror I I found this page which suggests that the device is not supported, never has been and never will be. The reason according to Tomtom is due to an agreement with HTC,
http://www.europe.htc.com/en/htctytn/support/faq.html?id=539&cat=applications
I am trying to catch up on this device so am swamped by data at the moment but this is a real blow to me as one of the main priorities is to run Tomtom 6. When I bought the device I assumed that it was just a pocket pc with a phone in it. Seemingly I am wrong as there appears to be differences with the hardware or Tomtom checks the device it's running on and presumably refuses to work properly.
Can anyone enlighten me as to how ( if at all to get around this issue). Currently my device still has mobile 5 but I am ploughing through the plethora of information on this site trying to figure out exactly what I should and shouldn't do. I've a lot of catching up to do..
Any advice / suggestions would be most welcome, it seems too strange a concept to be locked out of running a pc app just because of the hardware it's running on.
EDIT: Apologies moderator this probably shouldn't be posted in the wm6 thread even though I am intending to move over and would like to use tomtom on that. Please move it if necessary.
louiscar said:
Having just bought a Tytn I found that my tomtom 6 didn't work. I seemed to have two issues. 1) It hung up frequently and 2) It kept losing my external bluetooth GPS receiver.
I thought I'd go to Tomtom's page to see if there was a fix given that HTC mention this saying that Tomtom have updated version 6 for the device.
http://www.europe.htc.com/en/htctytn/support/faq.html?id=539&cat=applications
To my horror I I found this page which suggests that the device is not supported, never has been and never will be. The reason according to Tomtom is due to an agreement with HTC,
http://www.europe.htc.com/en/htctytn/support/faq.html?id=539&cat=applications
I am trying to catch up on this device so am swamped by data at the moment but this is a real blow to me as one of the main priorities is to run Tomtom 6. When I bought the device I assumed that it was just a pocket pc with a phone in it. Seemingly I am wrong as there appears to be differences with the hardware or Tomtom checks the device it's running on and presumably refuses to work properly.
Can anyone enlighten me as to how ( if at all to get around this issue). Currently my device still has mobile 5 but I am ploughing through the plethora of information on this site trying to figure out exactly what I should and shouldn't do. I've a lot of catching up to do..
Any advice / suggestions would be most welcome, it seems too strange a concept to be locked out of running a pc app just because of the hardware it's running on.
EDIT: Apologies moderator this probably shouldn't be posted in the wm6 thread even though I am intending to move over and would like to use tomtom on that. Please move it if necessary.
Click to expand...
Click to collapse
Try a search on the Hermes forum. I found lots of stuff.
I found THIS ONE . But there were MANY others. Some users reported success with some ROMs.
Don't fret, it works fine on mine... Are you running a WM6 image - you may wish to upgrade to wm6 if you're not. (or downgrade to TT5.....)
Treat the issue as 2 separate problems, bluetooth related loss of GPS unit, and the stability of the TT6 software.
There are any number of other applications that will let you connect and read signals from the GPS unit, try these to see if you have a faulty gps unit or if its TT playing up.
Once you're happy with this look at the TT issue.....
I have 2 Varios II and I can admit that I had some issues with TT6 with WM5. TT liked to freeze when I was typing in the address or browsing through menus. When I changed to WM5 AKU3.2 it was better, but still not perfect. Eventually, it was WM6 that helped me. Now TT6 is running without any issues (of course it can freeze from time to time when I have too many programmes running in the background). Just try any of new WM6 and everything should be fine.
I had TT5.21 which people said run fine which didnt on wm6 but TT6.1 works fine
Long time since i've been on here but while i was browsing about, i saw this problem. All i can suggest is using the inbuilt GPS and see how that works? I have TT6 as well and i have used it perfectly well on an XDA Mini, XDA Orbit, SPV M700, HTC Touch, HTC TyTn II... seems a bit odd that you're having these problems. Have you since cured the fault or is it still being a bit of a ****bag?!
While i'm here... anyone got the latest maps at all for TT6? Shout me on [email protected] if you have any info on TT6 or need any PDA / Pocket PC help.
Griz
ibanyard said:
Don't fret, it works fine on mine... Are you running a WM6 image - you may wish to upgrade to wm6 if you're not. (or downgrade to TT5.....)
Treat the issue as 2 separate problems, bluetooth related loss of GPS unit, and the stability of the TT6 software.
There are any number of other applications that will let you connect and read signals from the GPS unit, try these to see if you have a faulty gps unit or if its TT playing up.
Once you're happy with this look at the TT issue.....
Click to expand...
Click to collapse
Yeah, I had established that the gps was working fine, I've been happily using it on my ipaq 2210 for ages. Then with the Hermes testing with gpsgate and some other stuff showed no problems.
The problem I had was that my TT6 was a 2GB SD card version and I didn't have micro SD big enough to test it. I had about 1hour to play with my friend's one and that's when I discovered the two problems.
He lent me the card to play with this evening and I've made a little progress now. I've sorted the flakey GPS operation, primarily by changing the com port, deleting the pairing and pairing again. So far that's not dropped out since.
Tomtom runs but freezes, this appears to be a confirmed problem which I hope that WM6 will solve as (mean-machine) suggests.
I feel a lot happier that the damn thing runs at least. The freezing appears to be related to cpu usage as I find that that zooming right out on a map is a good way to cause this to happen. The menu screens can be a problem too and the rest appear intermittent. As others have stated in other threads, hitting the red button and then switching back to TT will free it up.
I guess the next thing is to study the Wiki and try an make sense of the order things need to be done to put WM6 in, which Rom if any, which version of WM6. ... Information overload, so I think I need to take it slow and ingest the data .
Thanks for all the replys guys, it amazes me how much support HTC has and how many of you are passionate about them. Up till a few months ago I had never heard of HTC, now I doubt I'd consider anything else.
TomTom6
louiscar said:
Having just bought a Tytn I found that my tomtom 6 didn't work. I seemed to have two issues. 1) It hung up frequently and 2) It kept losing my external bluetooth GPS receiver.
I thought I'd go to Tomtom's page to see if there was a fix given that HTC mention this saying that Tomtom have updated version 6 for the device.
http://www.europe.htc.com/en/htctytn/support/faq.html?id=539&cat=applications
To my horror I I found this page which suggests that the device is not supported, never has been and never will be. The reason according to Tomtom is due to an agreement with HTC,
http://www.europe.htc.com/en/htctytn/support/faq.html?id=539&cat=applications
I am trying to catch up on this device so am swamped by data at the moment but this is a real blow to me as one of the main priorities is to run Tomtom 6. When I bought the device I assumed that it was just a pocket pc with a phone in it. Seemingly I am wrong as there appears to be differences with the hardware or Tomtom checks the device it's running on and presumably refuses to work properly.
Can anyone enlighten me as to how ( if at all to get around this issue). Currently my device still has mobile 5 but I am ploughing through the plethora of information on this site trying to figure out exactly what I should and shouldn't do. I've a lot of catching up to do..
Any advice / suggestions would be most welcome, it seems too strange a concept to be locked out of running a pc app just because of the hardware it's running on.
EDIT: Apologies moderator this probably shouldn't be posted in the wm6 thread even though I am intending to move over and would like to use tomtom on that. Please move it if necessary.
Click to expand...
Click to collapse
I have been using TomTom 6 on my Imate Jasjam (TyTn) both with WM5 and many versions of WM6. It works flawlessly never missing a beat. What com port are you using? Have you turned off secure connection?
@louiscar: a good place to start with upgrading info (to avoid the overload) is THIS SITE . Great guides that make it simple.
rbin said:
I have been using TomTom 6 on my Imate Jasjam (TyTn) both with WM5 and many versions of WM6. It works flawlessly never missing a beat. What com port are you using? Have you turned off secure connection?
Click to expand...
Click to collapse
Hi rbin,
I've currently got the GPS panel set to 'program port = com2', 'hardware port = com0' and my bluetooth gps is set to 'outgoing = com0'
Currently this works well so the GPS issue has been resolved.
Tomtom on the other hand freezes pretty much as described here:
http://forum.xda-developers.com/showthread.php?t=299892&highlight=tomtom+freezes
and in a number of other threads.
todd_jg said:
@louiscar: a good place to start with upgrading info (to avoid the overload) is THIS SITE . Great guides that make it simple.
Click to expand...
Click to collapse
Great link, thanks Todd. Reading glasses are on already.
TT6 w/Pharos and Holux recievers work great
I've an AT&T Tytn upgraded to WM6 and have no troubles with my Holux or Pharos receivers and TT6.
Everything works great EXCEPT issues with data connections such as TT Buddies or traffic. This isn't unique to the PDA version of the software though, as I also have a standalone TomTom GO 910 paired with the phone and it works almost okay as a bluetooth speaker phone, but constantly has trouble getting a good data connection.
My $0.02
louiscar said:
Having just bought a Tytn I found that my tomtom 6 didn't work. I seemed to have two issues. 1) It hung up frequently and 2) It kept losing my external bluetooth GPS receiver.
I thought I'd go to Tomtom's page to see if there was a fix given that HTC mention this saying that Tomtom have updated version 6 for the device.
http://www.europe.htc.com/en/htctytn/support/faq.html?id=539&cat=applications
To my horror I I found this page which suggests that the device is not supported, never has been and never will be. The reason according to Tomtom is due to an agreement with HTC,
http://www.europe.htc.com/en/htctytn/support/faq.html?id=539&cat=applications
I am trying to catch up on this device so am swamped by data at the moment but this is a real blow to me as one of the main priorities is to run Tomtom 6. When I bought the device I assumed that it was just a pocket pc with a phone in it. Seemingly I am wrong as there appears to be differences with the hardware or Tomtom checks the device it's running on and presumably refuses to work properly.
Can anyone enlighten me as to how ( if at all to get around this issue). Currently my device still has mobile 5 but I am ploughing through the plethora of information on this site trying to figure out exactly what I should and shouldn't do. I've a lot of catching up to do..
Any advice / suggestions would be most welcome, it seems too strange a concept to be locked out of running a pc app just because of the hardware it's running on.
EDIT: Apologies moderator this probably shouldn't be posted in the wm6 thread even though I am intending to move over and would like to use tomtom on that. Please move it if necessary.
Click to expand...
Click to collapse
I have used TT6 on my MDA VArio II (TyTn) for almost a year...no problem. Now I have the TyTn II
Same here.. been using Tom tom 6 on my Tytn since the day i installed wm6, no problems here, works like a charm!
HEAT???
I have been using TT6 on my Imate JASJAM running the DOPOD WM6 ROM without much trouble (no hanging etc). The only problem I am experiencing is huge power drain and the unit being physically hot when running TT. Maybe this power drain and potential overheating can cause some units to hang and playup, or potentially any unit given the right environment!
Anyone else finding their units getting a bit hot?
I've been using TT6 on my Tytn (MDA Vario II) almost one year now. No problems. Started using TT6 while running WM5, upgraded to WM6 (schaps rom), reinstalled TT6 and it just continued as before. No problems, no hangups no freezing. I've been using all kinds of different charts with TT6, so I don't think the problem is with TT.
louiscar said:
Hi rbin,
I've currently got the GPS panel set to 'program port = com2', 'hardware port = com0' and my bluetooth gps is set to 'outgoing = com0'
Currently this works well so the GPS issue has been resolved.
Tomtom on the other hand freezes pretty much as described here:
http://forum.xda-developers.com/showthread.php?t=299892&highlight=tomtom+freezes
and in a number of other threads.
Click to expand...
Click to collapse
Going to try your settings too, cause on all WM6 roms I tried I keep losing my GPS BT connection. I'm not damn sure it got nothing to do with TT6. But when I delete my gps and reconnect it while TT6 is up and running, TT will find the gps straight away. So imho it's the BT connection that fails and not TT.
It's really annoying though.
Cheers, M
I have been running TomTom Navigator 6 on my JASJAM for some time. The hanging problem described is probably caused by having all the Points Of Interest (POI) active.
Go into the TomTom settings menu and de-activate ALL the POIs. Try it, then only turn on the ones you actually require.
oltp said:
Going to try your settings too, cause on all WM6 roms I tried I keep losing my GPS BT connection. I'm not damn sure it got nothing to do with TT6. But when I delete my gps and reconnect it while TT6 is up and running, TT will find the gps straight away. So imho it's the BT connection that fails and not TT.
It's really annoying though.
Cheers, M
Click to expand...
Click to collapse
Doesn't work either. Seems that after a soft-reset the BT connection with my GPS is f*d. Very strange because the BT headset doesn't suffer any of this. Maybe time to buy a new GPS, but with WM5 I never experienced this behaviour.
I found that with tt6 you need to have the WM6 internal gps settings set to "None" for both program and hardware port. Then make sure the box is checked in the last tab so it autodetects the com ports. Once all this is set and you goto add a bluetooth gps device in tt6 it gives you the option to use com port 0. select this port and it should detect your gps unit with no probs. Been running tt6 on my 8525 with tnt's latest cooked rom and things couldn't be running smoother.
Edit: On another note. I used to use Telenav with my 8525 with the original at&t rom. I had the worst luck with that application. I would constantly lose my gps connect and I almost always had to do a soft-reset to get it working again. It is quite possible that Telenav was not the issue and that the particular rom I was using had bluetooth connection issues that were resolved when I switched to a cooked rom such as the tnt one. So for those using tt6 with BT connection problems you may want to try a different rom and see how your luck goes.

Bluetooth - Handsfree Devices!

Hello xda community!
I have a huge problem with my Hermes using Shaps Roms (latest), besides I tried all of the roms till now, and bluetooth devices!
I tried 3 devices till now:
Parrot 3200
Audi UHV
and a Sennheiser VMX 100 ear- handsfree
so first I had problems with the Audi to get a stable BT transmission without disconnect which is solved due to a rom change!
Now the problem is with picking up, or dialing.
For example BT -> Audi UHV connected!
Using phonebook to dial a number -> dialing ... it displays in the Audi -> Dialing.. and when the connection is established its shoud says connected like in phone but sometimes just shows "Hanging up.." -> while the Hermes display says connected!
And I am definitly connected to the person but I cant hear anything not on the phone or the BT Kit!
This is extremly anoying -> and not only withe the Audi, even the simple Sennheiser earphone there is exactly the same problem! or the Parrot!
The phone is not able to send correct "commands" Pick UP -> Connected -> Disconnected. I mean THIS IS A HORROR!
Its not a permanent error but it it shows quite often (6 tomes out of 10 calls) up it does it again and again till sofot reset!
Please someone help me !!!!!
PS i also tried Jetware Mobile same problem no difference ....
Greets,
fire
Out of interest, try my ROM and see if this works. I use bluetooth dialing on a car kit and it works fine for me...
CRCinAU said:
Out of interest, try my ROM and see if this works. I use bluetooth dialing on a car kit and it works fine for me...
Click to expand...
Click to collapse
ok, i will give ot a try - first without jhetware mobile and with it!
Is this problem typical or known or just affects me?
Not to sure - although I install a certain version of the BT kit that may affect your issue. I don't know if it will fix it, however I would be interested to see your results.
firefoxy said:
ok, i will give ot a try - first without jhetware mobile and with it!
Is this problem typical or known or just affects me?
Click to expand...
Click to collapse
I have used a number of Schaps ROMS and others, and I have never had a problem making or receiving calls through my car kit (a Ford).
Having said that, I have had probelms getting the car kit to access my contacts on most of them, but Schaps latest ROM worked 'straight out of the box' in every respect.
Hissing Syd said:
I have used a number of Schaps ROMS and others, and I have never had a problem making or receiving calls through my car kit (a Ford).
Having said that, I have had probelms getting the car kit to access my contacts on most of them, but Schaps latest ROM worked 'straight out of the box' in every respect.
Click to expand...
Click to collapse
interesting.. so if you dial a number the tytn sends to your ford the correct status of the calling process ?
start - call - stop ?
never had such issue:
Ford: start - stop
Hermes: start - call ...
silence on both ?
CRCinAU said:
Not to sure - although I install a certain version of the BT kit that may affect your issue. I don't know if it will fix it, however I would be interested to see your results.
Click to expand...
Click to collapse
First results:
15 minutes it works like a charm - no phonebook entries just the plain rom.
now I ll snyc with outlook and start another test!
* Stange thing is that the Audi UHV found my phonebook entries although i dind´t snyced them. Sim is empy ...
can there be something in extended rom ?
Sounds like it uses BT SAP to access the contacts on the phone. I haven't built the ROM with that in it - as I haven't until now come up with a device that actually uses SAP!
Maybe try doing a search to see if you can find a cab for BT SAP and see if that helps?
CRCinAU said:
Sounds like it uses BT SAP to access the contacts on the phone. I haven't built the ROM with that in it - as I haven't until now come up with a device that actually uses SAP!
Maybe try doing a search to see if you can find a cab for BT SAP and see if that helps?
Click to expand...
Click to collapse
First of all thanks for all the replies!!
The Audi UHV is capable to use rSAP, but I have no idea what it does and what it´s good for.
What is the difference between SAP and HFP ? I have nothing on the sim card.
Now you're getting a bit beyond my knowledge as I don't have any of these systems to test or experiment with
+1
I have had the same problems with multiple ROMs.
Trying to link a Garmin GPS, and other Hands Free devices.
Seems like a Hermes thing rather than the ROMs.
Try deleting the BT device from the Hermes, but not the device. Re-sync from the device.
Not sure if that will help, but I had weird BT problems with the 4.30 rom and that fixed it. No problems at all with the 4.31 though.
I will start some testing today and report back tonight!
Maybe it was the rsap being enabled in Shaps roms .... we will see!
The question is, should I install Jetware Mobile or not ?
It seems to be faster in syncing if I have it installed.
So far I tested it yesterday for half an hour and it worked!

Bluetooth A2DP on my Tilt2: WORTHLESS AS $H!T

Ok, so I finally got into the smartphone game to get a better music streaming experience. MFRadio and MFScorn just weren't cutting it for me anymore. I hated the skips and the ridiculously long (and repeated) buffering time. So I first looked at Android phones but went with WinMo because they say you can run both OS's with WinMo (and the only Android offering from AT&T has a 12-hour standby time before the battery dies, according to reviews).
I have a Bluetooth head unit and have had over a dozen phones paired with it. This phone however is a completely different story. I have installed the latest "release" from AT&T (from a thread on this site). At first I tried streaming with the bundled Windows Media Player which apparently doesn't stream anything at all (with both the bundled and downloaded releases of the OS), then downloaded TCPMP. TCPMP is everything I have ever dreamed of in a streaming media player, but the only problem I have with it is that it won't connect to a stream unless I have already opened up a browser window and went to a website. Not the end of the world.
So, I get in my truck and initiate pairing to the phone. It sees the head unit as a Hands-free and as Stereo Audio. I can get it to connect for a split second and then it dies. I get a popup notification that tells me that the phone cannot control volume when paired to the bluetooth device and audio must be adjusted from the device itself. Fine. But then it doesn't work at all. At first, I wanted to blame TCPMP until I realized that nothing at all was working with the head unit. I think I got it to work once but it never worked again.
So is there any way to fix this problem? This is the one thing I wanted working on my new phone. Yes, the notifications that my texts were successfully sent are very annoying (as well as the other notifications), and yes, Windows Media Player for Mobile is useless, but the fact that I can't stream Bluetooth audio on this phone really makes this phone worthless to me. Didn't anyone bother testing this stuff before releasing this garbage? The Tilt is a paperweight to me right now because it can't do the one thing I want it to do the most. I might as well go back to my Sony Ericsson W760a at this point!
What can I do? I have not yet unlocked anything (although I have a SIM unlock code waiting) and have not yet flashed Hard-SPL. My phone has Bluetooth for Windows Mobile Version 1.9.2 Build 600 HCI Version 4.84. I'd do anything at this point to get this working. Windows Mobile is not that precious to me either. PLEASE HELP!
e-thug said:
Ok, so I finally got into the smartphone game to get a better music streaming experience. MFRadio and MFScorn just weren't cutting it for me anymore. I hated the skips and the ridiculously long (and repeated) buffering time. So I first looked at Android phones but went with WinMo because they say you can run both OS's with WinMo (and the only Android offering from AT&T has a 12-hour standby time before the battery dies, according to reviews).
I have a Bluetooth head unit and have had over a dozen phones paired with it. This phone however is a completely different story. I have installed the latest "release" from AT&T (from a thread on this site). At first I tried streaming with the bundled Windows Media Player which apparently doesn't stream anything at all (with both the bundled and downloaded releases of the OS), then downloaded TCPMP. TCPMP is everything I have ever dreamed of in a streaming media player, but the only problem I have with it is that it won't connect to a stream unless I have already opened up a browser window and went to a website. Not the end of the world.
So, I get in my truck and initiate pairing to the phone. It sees the head unit as a Hands-free and as Stereo Audio. I can get it to connect for a split second and then it dies. I get a popup notification that tells me that the phone cannot control volume when paired to the bluetooth device and audio must be adjusted from the device itself. Fine. But then it doesn't work at all. At first, I wanted to blame TCPMP until I realized that nothing at all was working with the head unit. I think I got it to work once but it never worked again.
So is there any way to fix this problem? This is the one thing I wanted working on my new phone. Yes, the notifications that my texts were successfully sent are very annoying (as well as the other notifications), and yes, Windows Media Player for Mobile is useless, but the fact that I can't stream Bluetooth audio on this phone really makes this phone worthless to me. Didn't anyone bother testing this stuff before releasing this garbage? The Tilt is a paperweight to me right now because it can't do the one thing I want it to do the most. I might as well go back to my Sony Ericsson W760a at this point!
What can I do? I have not yet unlocked anything (although I have a SIM unlock code waiting) and have not yet flashed Hard-SPL. My phone has Bluetooth for Windows Mobile Version 1.9.2 Build 600 HCI Version 4.84. I'd do anything at this point to get this working. Windows Mobile is not that precious to me either. PLEASE HELP!
Click to expand...
Click to collapse
Hmmmm .... I don't believe you ever stated what type of headset you are trying to get working here? I find your problem to be very strange, even though WinMo does seem to be lacking in a lot of different areas, audio streaming via bluetooth stereo headset is definitely not a problem I have encountered. It even streams flawlessly through my 5.1 hooked to my pc via a crappy 8 buck bt dongle and still sounds excellent. Have you considered that the problem may lie with your bt headset itself?
Also, when you say that you installed latest "release" from AT&T (from a thread on this site), what exactly do you mean? I am running the "unofficial" leaked rom from AT&T on mine and I just paired my Motorola S9 stereo headset and it is playing great for me. You also may want to try using some different software, give S2P (Slide 2 Play) a try and see if you have different results. That's what I am using right now, but I have used TCPMP to play a few xVids through my headset and have had no problems.
The problem is not in the head unit. 25 other phones can't all be wrong. I have no problem using my bluetooth headset. That is probably why you don't see the problem. Anything more complex than a headset will not work with this release. The problem lies within the phone as soon as it displays a notification (which, of course I cannot disable) which reads, "The connected Bluetooth headset does not support volume adjustment from the device. Adjust volume on the headset itself."
That message is the kiss of death. So basically any Bluetooth head unit will not work with this phone? Sounds like shoddy programming to me. Yes, I am using the "leaked" release. I really don't think this release will ever see the light of day. Its horrible! You cannot disable notifications (I don't need to know when my text messages were sent successfully), and it looks like whenever I get a system notification, any program I am using crashes immediately. Like I said before, as soon as I get a notification, I lose the Bluetooth connection (which is like a split second before the notification comes up). I highly doubt this "leaked" copy will ever see the light of day, officially (unless AT&T and HTC do absolutely zero testing on it).
A little clarification for those who don't know... when I say "head unit" I'm talking about a Bluetooth-enabled car stereo and when I say "headset" I mean a Bluetooth headset
My Tilt 2 works absolutely fine with all my BT devices, including 2 Motorola headphone sets and my Sony Xplod head unit in my truck.
e-thug said:
A little clarification for those who don't know... when I say "head unit" I'm talking about a Bluetooth-enabled car stereo and when I say "headset" I mean a Bluetooth headset
Click to expand...
Click to collapse
I was mis-understanding you about the head unit, I did think you were talking about a headset. Sorry bout that, my Mustang doesn't have built-in BT so I have to use a Motorokr t505 for those chores. It works well but it does give me the same message that you are getting about "volume can't be cotrolled etc" but I can dismiss it and carry on without any problems.
but the fact that I can't stream Bluetooth audio on this phone really makes this phone worthless to me. Didn't anyone bother testing this stuff before releasing this garbage? The Tilt is a paperweight to me right now because it can't do the one thing I want it to do the most. I might as well go back to my Sony Ericsson W760a at this point!
Click to expand...
Click to collapse
Since you don't need your phone for calls, just get Sirius or XM. Ya know, considering you only stream music through the phone..
Did you try the BT headset or head unit with the original stock ROM before you flashed the "leaked official" ROM?
Seems like you might have a couple random issues, with the BT issues and the system notifications crashing programs. I haven't flashed the leaked ROM, but I do know that many random issues with cooked ROMs can often be cleared up by running Task29, which completely wipes the phone memory before you flash a new ROM. I think you will need to HardSPL before you run Task29. Might be worth a try, sometimes fragments of the old ROM interfere with the new one, and cause some bugs.
Bluetooth protocols can be implemented differently by different manufacturers.
I know of many people including myself who have NO PROBLEM with the tilt 2 and different Bluetooth products INCLUDING car radios.
I am using the "new" AT&T ROM and have no difficulties.
Clearly your pissed but your subject is wrong. I would suggest changing to "Worthless as $HIT to ME"
I think my problem is that I am getting notifications which seem to be killing my connection. Is there a way to turn all notifications OFF? The only ones I care about are missed calls, incoming SMS and maybe a birthday. I would like to try to kill the notifications first because I think this may solve my problem
You can get yourself a free reg editor (like Total Commander) and apply the following tweaks to modify the notifications:
SMS sent notification: http://www.mydigitallife.info/2008/06/24/enable-or-disable-the-sms-text-message-sent-notification-bubble/
Other notifications: http://www.mydigitallife.info/2008/06/24/tweak-and-configure-how-notifications-work-in-windows-mobile-notifications/
Although, this sounds like a band-aid just hiding a deeper problem. What you are describing is not typical behavior, and this is something else going on.
redpoint73 said:
You can get yourself a free reg editor (like Total Commander) and apply the following tweaks to modify the notifications:
SMS sent notification: http://www.mydigitallife.info/2008/...he-sms-text-message-sent-notification-bubble/
Other notifications: http://www.mydigitallife.info/2008/...cations-work-in-windows-mobile-notifications/
Although, this sounds like a band-aid just hiding a deeper problem. What you are describing is not typical behavior, and this is something else going on.
Click to expand...
Click to collapse
Thanks I will try these out and report back
For the record my head unit is a JVC KD-BT11 and I have never had any kind of problem pairing any other phone
Somebody else just posted a very similar issue, and found the app hAndyUtils to be helpful:
http://forum.xda-developers.com/showthread.php?t=741311
I think hAndyUtils might just be a app-based way to make the reg edits I posted earlier. But give it a try.
I scanned through the topic and did not see anyone mention this so I thought I would add my .02. The Tilt 2 is different than many other WM phones when it comes to bluetooth as it contains the Widcomm BT stack instead of the MS stack. (Just as an aside, on all my past phones, there were people bemoaning the the fact that it had MS, and trying to replace it with the Widcomm, so I am getting a real chuckle out of folks complaining about the Widcomm and wishing for MS )
In any case, the utilities (Blue music toggle etc...) that used to work for me to toggle between streaming in stereo and plain phone qulity no longer work. However, all my stereo headsets (I own three different brands/pairs) all work perfectly with the Tilt 2. And stay connected and streaming all day.
By the way, coming on a forum that is full of people helping each other and using profanity, anger and threats, is not the most conducive way to get your questions answered. The odds are that the problem you are having is already solved somewhere among the 6+ million posts in this forum. I do not know where or I would post it for you, but it is probably out there. Good luck. And if you find it, please post the link to the answer back here so that other serchers will find it too.
maybe it can come from the phone itself
i had a rhodium for almost a year and never got my motorola headset ht820 to work well enough for me to use it... (more skips than music...cant move my head without a skip)
i flashed to a NRG rom before trying my headset...i tried eveything as far as ref setting, different radios...even flashed my ht820...
no improvement...
then my phone fell in water not so long ago...got another rhodium same model (european)...and it worked perfect out the box on stock rom i can go in a different room than my device and still hear music with no skips...and it still does with nrg rom and latest radio...
so my guess is maybe some actual devices have bad bluetooth hardware ???
I have the Motorola S9 and the HT820 and both work absolutely fine on my Tilt 2.
yatrg said:
I scanned through the topic and did not see anyone mention this so I thought I would add my .02. The Tilt 2 is different than many other WM phones when it comes to bluetooth as it contains the Widcomm BT stack instead of the MS stack.
Click to expand...
Click to collapse
Can I change my Bluetooth stack to MS? I have installed Hard-SPL and have experimented with cooked ROMs to no avail.
I sent the phone back to AT&T, went to Trinidad & Tobago for a few weeks and came home to a new Tilt 2 waiting at my doorstep (which could have been stolen by anyone!) and I am still having the same problem. So I guess I sent back a perfectly good phone!
I would love to try some different Bluetooth stacks if possible. Where do I go from here?
e-thug said:
Can I change my Bluetooth stack to MS? I have installed Hard-SPL and have experimented with cooked ROMs to no avail.
I sent the phone back to AT&T, went to Trinidad & Tobago for a few weeks and came home to a new Tilt 2 waiting at my doorstep (which could have been stolen by anyone!) and I am still having the same problem. So I guess I sent back a perfectly good phone!
I would love to try some different Bluetooth stacks if possible. Where do I go from here?
Click to expand...
Click to collapse
Did you ever try the solution in this thread? It fixed a lot of issues people were having with bluetooth car kits. Maybe it will work for you: http://forum.xda-developers.com/showthread.php?t=591322
The solution source is here: http://www.everythingwm.com/forum/moto-q-9c/q9c-and-infiniti-g35x-bluetooth-problem-16833-4.html
And here is the solution. You need a registry editor to do this:
1. Modify the HandsFree plug-in:
HKLM\Software\WIDCOMM\Plugin\HandsFree
i. Change SupportedFeatures to 45 (default is 1135)
ii. Add value HFBDA binary, set to same value as LastConnectedBda
iii. Add value HFDeviceType decimal 2
2. Modify the WIDCOMM bluetooth general settings:
HKLM\Software\WIDCOMM\BtConfig\General
i. Change bdaddr to (no value)
ii. Change (or add if not there) DisableReopenAudio to 0 (default is 1)
3. Reboot device
You may also want to do the A2DP quality registry edit: Add a DWORD value of LineSpeed to HKLM\Software\WIDCOMM\Plugin\AV\ with a value of 320.
Give it a try, it may work for you.
I will give this a try and report back. Thank you very much for the response!
No luck. And my bdaddr keeps resetting to a binary value when I reset the phone

Categories

Resources