Related
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.
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
I have problems with my Bluetooth and the paired device in the car with almost every recent ROM.
After about 10 minutes driving with a connected phone, the Bluetooth shuts down on my Diamond. When I go to Settings -> ... > Bluetooth -> Mode -> Turn on Bluetooth is unchecked. If I check it again it connects again with the phone and about 10 minutes later it's off again.
I went back to the RUU_Diamond_HTC_WWE_EastEurope_1.93.479.3_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship.exe. It's against my feelings, believe, etc. but I want to solve it .....
I installed Advanced Configuration Tool (3.0), went to Bluetooth -> Audio gateway power save and Disabled it. I did it because I was reading about suspended devices and power save features. I thought that the loss of Bluetooth is been caused by a saving power feature.
After a soft reset, the Bluetooth stays connected.
It's a start, but I'm not happy with it ... I would like to use cooked ROM's and optimal settings in the ROM.
There are other tweaks too in Bluetooth, for example the supported bitpool, etc. Perhaps those settings cause the shutdown of a connected Bluetooth device instaed of the power save feature.
Has anyone this kind of problems too with paired Bluetooth devices?
If so, would you like to help me to find the cause?
If not, can you describe what device you use (Jabra, TomTom, car radio, etc.), which ROM, which radio and extra tweaks?
Hi
I do have the same problem. I am using my Diamond with my Opel Astra (Vauxhall) and a CD70 radio with built in handsfree (Opel UHP). It disconnects after 10 minutes and after calls. Everything else works fine. Changing rom and radios has not helped so far. If I don't close the comm manager it stays connected but disconnects after a call because the comm manager is closed with the end of the call. Is there a way to force the comm manager not to close?
Olli
olliver said:
Hi
I do have the same problem. I am using my Diamond with my Opel Astra (Vauxhall) and a CD70 radio with built in handsfree (Opel UHP). It disconnects after 10 minutes and after calls. Everything else works fine. Changing rom and radios has not helped so far. If I don't close the comm manager it stays connected but disconnects after a call because the comm manager is closed with the end of the call. Is there a way to force the comm manager not to close?
Olli
Click to expand...
Click to collapse
I have a CD70 too in a Opel Zafira.
This "comm manager" thing is interesting, but it looks to me like an Opel issue.
Can't you flash firmwares by opel?
Riel said:
Can't you flash firmwares by opel?
Click to expand...
Click to collapse
That's an option, but my Trinity (P3600) performed great with the same car. Will an upgrade solve my problems? I know one thing, it's not cheap either.
I tried it with different ROM's, but it still happens.
I tried it with different radio's, nothing changed.
Till today, I've got now the new radio (v1.05.25.BS14).
http://forum.xda-developers.com/showthread.php?t=432770
It has fixed the delays in GPS + faster GPS fix and more important fo me Bluetooth didn't stop today.
I'm sure 100% sure yet, but seems to be better.
I got something to complain too about the new radio. The radio signal is less strong than the .05 radio.
Same problem here
My Vectra is equipped with CD70.
Previously I've owned a Kaiser and the problem was solved by one of the 6.1 radios, bluetooth connection was rock solid.
Right now I have the same problem with Diamond - after every single phone connection, when I'll hangup, the phone disconnects CD70. When I'll try to reconnect manually using CD70 everything is fine.
I've noticed that the same problem exists when I'm using Nokia bluetooth headset - one call, bluetooth connection dropped...
I've tried following Diamond radios:
.05
.07
.08
.BS14
and two Raphael radios by Bepe:
1.03.25.18
1.02.25.11
Each Diamond radio behaves the same way. Each Raphael radio adds a bonus - random bluetooth connection problems.
Right now I'm back with .05, I think I'll look for the software I've seen once (can't recall the name) - it's a PDA application designed for connecting to the car bluetooth systems and it has been cerftified to work fine with CD70.
Use Jetware Mobile for htc-diamond.
jetware
That's the software I couldn't remember the name.
Anyway I gave it a shot and it gets even worse, I couldnt get the connection lasting longer then 2-3 minutes, totally unstable
Right now I got back to radio .08 - the bluetooth link is rock solid, I guess I'll just need to get used to reconnecting after each phone call
Same bluetooth system in my car, same problems as you guys.
To avoid the disconnections after calls you need to go, with 'Advanced Config' to bluetooth->Audio gateway power save, and switch it to disabled.
For me this little change solve the 'first' problem, but I have another one that I don't know how to solve: the aparently random bluetooth disconections. Sometimes BT is not disconnected in hours, sometimes in days.
I am also using Jetware Mobile, but i didn't feel any improve...
The random ones depend on the radio rom version - I was using .05 and it was rock solid.
I will try .16 with audio gateway started and with power save disabled as you advised - I thought about it earler but previously I tried to disable the power save without enabling audiogateway service
Well, we will see if it works or not.
Hi,
I also have a Vectra CD/70 combination, for 2 yrs now.
I had a HTC3300 and 2years i had not a single problem with Bluetooth connection.
Now i have a HTC Diamond Touch Pro and have the same problems you guys have.
I tried all your suggestions, radio's and so on with no good result.
The good news is .. its an Opel problem and it seems to be that a Bluetooth Firmware Upgrade is available from Opel Germany. I just contacted my dealer and next week he will Upgrade my bluetooth firmware.
I will keep you guys informed.
Hello,
had the same problem with my Opel CD70.
Using Jetware Mobile and limited the entrys who copied to the car to a max. of 5. Also disable the call lists. Now it works.
I think the Opel/Vauxhall Bluetooth Connection disabels if to many entries are copied to the car.
Hello,
any News about our Bluetooth Problem ???
I also have a CD70 from Opel and I cannot understand why my Diamond swich of Bluetooth after a while ?
Is it an Opel-Problem or does anybody now an Application which helps ?
Thanks a lot for Your help,
Stepos
Hi,
I am currently using BTrestore (http://home.casema.nl/rgschmidt/WM/Downloads/BTRestore_V_1_0_0_PPC.ARMV4.CAB). This utility checks the status of the bluetooth stack every 5 secs and (re)enables it everytime it's down. It seems that the 5 secs are short enough to keep the phone connected. It's not a real solution and unfortunately this tool is sometimes instable too, but it absolutely extends the connection time with the UHP.
Maybe bullock can tell us if the carkit upgrade solves anything...??
I also created a ticket at HTC, but they refuse to troubleshoot user specific issues. They told me they only look into issues if they get enough calls from different users and to keep an eye on the update site (they seem to be able to solve issues without knowing what the actual issue is...). So I would encourage everyone here to create a HTC ticket for this issue. I still think it is an HTC issue: a bluetooth stack should never go down without any user intervention.
Good luck!
BTrestart and Jetware Mobile doesn`t help, my Touch diamond disconnect again from Opel CD70 and swiched off Bluetooth !
Can anybody help ?
Sorry guys, the OpelDealer is still "searching" for the Bluetooth upgrade.
After several phonecalls maybe next week (1st week of Febr) it will be made available to the dealer.
Like i said ... i willl keep you informed ... still have this lousy problem !!
..does anybody use the new Rom 2.03 ? Any difference ?
I also asked my Opel-Dealer for an Update of UHP, next week I 'll get new Information....
... well guys I had my CD70 updated !! I am/was very sceptical because the only thing they did was a re-install of the Language of the Navi System with a version 2005 CD. I asked if that was all to correct my Bluetooth problem .... the (smiling) answer was YES.
I have it now for 24hrs ...... and Bluetooth is still on )
I will let you know the result after a week !!
..i can't beleave it works with a 2005-update ! Great !
My Opel-Dealer is still busy in selling 10 Opel Corsa every day (..the magic word is "Abwrackprämie") , so I'll have a date there next week...
When I bought my Vectra the dealer had also to reinstall the Language-CD, maybey it was the wrong version....
...... Sorry guys ......
This update DOES not do the magic trick !! So we have to find another solution
who has the right idea ??
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
My girlfriend and I both have HTC Desires (one unbranded and one Vodafone). We recently got a 2005 BMW 5 series with the I-Drive Pro Nav system in it.
When I try to use BT to connect to the car, I can manage to pair them, but when the phone goes to connect to the car, it only connects for a few seconds and then disconnects. It then connects again and the whole thing repeats. The disconnect is frequent enough (every few seconds) to render the whole thing unusable. It also means that it isn't connected long enough to transfer the phone book.
Both our Desire's have this problem (they have different firmwares). I thought that maybe it was the car, but I put my SIM into my old Xperia X1 and it worked flawlessly with the car.
Is there a setting on the phone that needs adjusting or is it a firmware problem? I hear other people with the same car having no problems with the Desire. I've also used my Desire in a Toyota Avensis and a Vauxhall Insignia with no problems.
Any advice would be gratefully received.
tifosi256 said:
My girlfriend and I both have HTC Desires (one unbranded and one Vodafone). We recently got a 2005 BMW 5 series with the I-Drive Pro Nav system in it.
When I try to use BT to connect to the car, I can manage to pair them, but when the phone goes to connect to the car, it only connects for a few seconds and then disconnects. It then connects again and the whole thing repeats. The disconnect is frequent enough (every few seconds) to render the whole thing unusable. It also means that it isn't connected long enough to transfer the phone book.
Both our Desire's have this problem (they have different firmwares). I thought that maybe it was the car, but I put my SIM into my old Xperia X1 and it worked flawlessly with the car.
Is there a setting on the phone that needs adjusting or is it a firmware problem? I hear other people with the same car having no problems with the Desire. I've also used my Desire in a Toyota Avensis and a Vauxhall Insignia with no problems.
Any advice would be gratefully received.
Click to expand...
Click to collapse
Hi,
I know there are some issues when it comes to Bluetooth and Android, and especially car kits.
Ref (sound quality): http://code.google.com/p/android/issues/detail?id=9888
Ref (disconnections): http://code.google.com/p/android/issues/detail?id=5452
This is supposed to be a fix (I did not get it to work properly): http://forum.xda-developers.com/showthread.php?t=731626
I know that Cyanogenmod has made some changes to their kernel in 6.1 that adresses audio quality (bitpool increased), and I also think that the disconnection is adressed. I'm actually testing it for the moment (6.1RC2).
Thanks very much for your reply - very useful. The link to disconnections that you gave shows someone else with the same car as us (slightly different model) with the same issue.
It's very strange as there are people reporting no problems at all with that car/phone combination.
Unfortunately, I can't try the suggested fix as I don't want to start mucking around with my ROM.
I have a problem with my Volvo and the Desire. No disconnections, but I can't get into the phonebook, using PBAP.
Flashing a MIUI Rom works charming for the bluetooth connectivity, however I'm missing my SenseUI.
Just hoping, praying, some def will include the AOSP bluetoothstack in a SenseUI-Rom
BMW Software update
Hi
I´d try contacting your local BMW workshop, to let them do a reading on your car to establish which software version your car have.
If it´s a rather old software version your car have, I´d suggest that you have it updated.
The software update might be the answer to your problems, and can also explain why other users with the same car don´t have this issue (they might have a newer software version than you).
Remember, this phone is way newer than the car, and also the software in it.
I´d give it a try
PS: Be advised. Updating from very old software to new software might cause "in car-hardware" compatibility issues, and demand new hardware in the car (computer modules ect.), so make sure you talk over which consequences the update could have for your specific car before the update is carried out
Cheers
-Buggi- (BMW workshop foreman in Denmark)
Thanks for that advice. I'll talk to the dealership and see about software upgrades. Fingers crossed!
I have a 2008 530i and my Desire (and my other halfs) work fine, so hopefully there is some newer firmware for yours. They facelifted the cars and slightly changed the iDrive in 2007 though so fingers crossed there is an update that fixes the pre-LCI models with a Desire.
Just for reference, this is sorted out now.
My I-Drive actually broke and I had a whole new unit put in (under warranty thankfully!). Since they were doing that, I begged them for the latest software, not just for the Bluetooth module, but for the system as a whole.
Since the software upgrade, the phone stays connected and everything works great.
The only fly in the ointment is that it seems that for some reason, not all numbers of contacts (or all contacts) make it into the car's phone book (most of them do).
Anyway, for anyone else having this issue, get BMW to upgrade your BT software (or the whole system if you're brave).
I have similar problem when i try to pair the phone with volkswagen tiguan 2010, it says "your phone in not supported"