Develop Bugs

XDA IIs and Bluetooth Problem.

When I turn on Bluetooth on XDA IIs, I got this error message :
"The bluetooth radio radio failed to turn on due to insufficient driver memory available. You must perform a normal reset before you can turn on the bluetooth radio."
Anyone can advise how to resolve this ? Soft reset does not cure the problem. Thanks.

have you upgraded to bluetooth stack version 3900 ???
if you have then im fresh outta ideas, if you havent find this at our FTP site,
ftp://xda-developers.com/
login and password = xda

got the same problem when i installed one of the bluetooth upgrades on its own. then i installed the new rom and everything was fine. not sure where the connection is but thought id share my problem

Problem solved.
By the way, what is the latest version of ROM for XDA2s, and where to get it from ?
Thanks.

So I was wrong.
After upgrading the BT upgrade, things was OK yesterday. But this morning i got the same error again.
Went to ftp://xda-developers.com/ as suggested, can anyone mentioned the filename of the ROM mentioned by thakkergaurav above ?
Thanks.

The latest ROM is 1.40
You can find it here: http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel

Hmmm..... :?
This BT issue is really getting to be NOT FUNNY! :evil:
Running the new ROM 1.40 and BT 3900 I'm now getting the "no sound" problem on the handset and caller cannot hear me on a HS801!
I use the turn on/turn off BT trick or soft re-set and the handset is OK for a couple of hours but the HS801 still does not work even though its OK with my old PocketPC,a nokia and a Motorola V3!
Is there any consistancy with this problem? It seems the different ROMs, Radio Stacks and BT versions are being effected.

Well, emailed the tech support, and all they can say was ...
"There is a ROM upgrade in development which is in the final stages.
We request your patience as we are trying to release the upgrade as soon as possible."
And that was 2 weeks ago.

even my bluetooth is upgraded to 3900,
i get the same error message also..
i cannot believe a 96mb memory is still not enough
i never get this kinda nonsense when i was using the 5450 ipaq
my today plugins was all over the screen and I had never encountered low memory...

I had the same problem but I have a Harrier not a BA so I thought it was related to that and you BA guys wouldn't get it.
Anyway, the solution on the harrier was to
-turn flight mode on
-soft reset
-turn bluetooth on
-turn flight mode off
Hope this helps

Here is a possible solution from wiki:
The ExSenetoR wrote:
Delete Run_BTTrayCE_10.lnk from your Windows\Startup folder and soft reset. Now you wont have the BT icon on the tray bar, but you wont have the no sound problem. If you still need bluetooth you can start it from the Windows directory as BTTrayCE.lnk.
Have fun.
Click to expand...
Click to collapse
Have not tried this myself, but I believe others have had success with it. You may want to save the file somewhere else, in case you want to reinstate it later...
Hope this helps
Chris

I posted this in another thread.
It really does look like a combo of the 1.40 ROM and 1.12 Radio Stack that is causing this problem (in this case, anyway. See sig). After trolling various forums, it seems that both BT build 3900 and 3500 are having the same issues.
IMHO it seems that the Blue Angel is trying to send the call to my HS801 even when BT is not activated.
Has anyone had a good look at the current radio stack? I've tried contacting Broadcom (BT chipset supplier) but it has been 3 weeks with no answer.
I've done the Run_BTTrayCE_10.lnk workaround but this is only a bandaid and I don't really have enough experience to attempt to cook the ROM. Any ideas?

I have a Motorola HS801 as well and I can receive calls just fine but when I make calls the other party can't hear me. I'm giving up on the HS801 - it's a cheapie anyway and I don't know of anyone else who's got it working either. Running BT3900

Difficulties with phone after upgrading to the new ROM

Hi folks ...
I face this problem with the phone many times a day. I can confirm it happens each time there is a failed call attempt (you couldn't make the call) ... the only way is to switch off the phone and turn it on again.
I thought it's something with RSU 1.09.00 but it happens also after downgrading to 1.08.00 ... so I think it has to do with the new ROM. It tells the signal maybe unavailable while you can see it is on the max level.
Edit: last observation ... it can receive SMS :?:
Any one faced this experience ??

Me Too
I Have the same problem :-(

Me Too
I Have the same problem :-(

Ive noticed in your screen shot the active sync is trying to connect with the internet which will prevent you phone from making the call. To give a example .... if I was downloading a file using my universal and someone tried to call me they would get my mail instead of ringing as the phone is using the internet connection however as soon as the file downloaded the phone would break the internet connection and allow the call. Hope that made sense!

I thought the service is supposed to interrupt the download if the phone rings as the primary function of the device is a telephone and secondary as a mobile computing platform.

numanoids said:
I thought the service is supposed to interrupt the download if the phone rings as the primary function of the device is a telephone and secondary as a mobile computing platform.
Click to expand...
Click to collapse
That's what I always thought but even with my trusty old imate jam I found if I got a call as I was downloading say mail the call would not make it though, try downloading a biggish file then ring your phone number at the same time I bet it will not make it This as ALWAYS been the case btw - don't matter which rom you have. oh and this applies to gsm (2.5 gprs) only as 3G is a totally different ball game!

thx for all inputs but it happens even without activesync running ... it doesn't work again except by switching the phone off then on ... the most exciting part: u will never notice that your phone is frozen till you try to make a call :evil: ... this will make me to go back to the old rom

More observation on this issue ... I made a hard reset and started without any problems with the phone part ... I restored a system backup and all went well ... the phone issue appeared again when I paired my BT headset with the device ... this might mean something to do with the BT stack ... I believe it happens mostly during or after using the headset :?:
Any similar experiences ?

Biso007 said:
Hi folks ...
I face this problem with the phone many times a day. I can confirm it happens each time there is a failed call attempt (you couldn't make the call) ... the only way is to switch off the phone and turn it on again.
I thought it's something with RSU 1.09.00 but it happens also after downgrading to 1.08.00 ... so I think it has to do with the new ROM. It tells the signal maybe unavailable while you can see it is on the max level.
Edit: last observation ... it can receive SMS :?:
Any one faced this experience ??
Click to expand...
Click to collapse
Same Problem Here... I was going to downgrade to 1.08.00, but now I may not... Don't want to lose the speed increase, so don't want to downgrade ROM...

back again ...
I made another hard reset and staretd without any s/w installed for a week .. the phone seemed to be stable but with the same annoying BT disconnect issue ... the above issue started to appear again after installing some phone related s/w like Smart Filter and PZP ... I think the new Radio ROMs starting with 1.08 have an issue with such applications that would continously check on phone traffic or have OS hooks to catch some events ... this wasn't the case with Radio 1.02 or 1.03 ... I 'm thinking to get back to 1.03 since I got nothing from 1.08 or 1.09 except quick battery draining!!

Bluetooth Devices Lost

All,
I've just upgraded from WM5 to WM6 with HTC Home RevROM, which is excellent, however, I have this strange issue.
First, I paired my laptop through Internet Sharing over a Bluetooth PAN - works perfectly.
Second, I paired my Jabra BT2020 earpiece.
As soon as the Jabra was paired, the list of devices under Settings->Bluetooth->Devices was empty. Not even the words "Add new device" is present........
I have checked, and I can still continue to use my laptop through Internet Sharing, and I can also use my Jabra earpiece to take phone calls.
Switching the phone off/on and Soft Resets do not solve this problem. Only a hard reset will solve it - but then of course I have to re-enter everything - which I have done, only to have the problem re-occur, hence it is repeatable.
Has anyone else seen this issue and could help me with a solution. I have searched the forum (and Google) to no avail.
Many thanks,
BrianP6

BrianP6 said:
All,
I've just upgraded from WM5 to WM6 with HTC Home RevROM, which is excellent, however, I have this strange issue.
First, I paired my laptop through Internet Sharing over a Bluetooth PAN - works perfectly.
Second, I paired my Jabra BT2020 earpiece.
As soon as the Jabra was paired, the list of devices under Settings->Bluetooth->Devices was empty. Not even the words "Add new device" is present........
I have checked, and I can still continue to use my laptop through Internet Sharing, and I can also use my Jabra earpiece to take phone calls.
Switching the phone off/on and Soft Resets do not solve this problem. Only a hard reset will solve it - but then of course I have to re-enter everything - which I have done, only to have the problem re-occur, hence it is repeatable.
Has anyone else seen this issue and could help me with a solution. I have searched the forum (and Google) to no avail.
Many thanks,
BrianP6
Click to expand...
Click to collapse
Hey man, Unfortunatly this is a bug with my current kitchen, I believe he is using parts of it for making roms. I'm working to fix it soon in my kitchens.
Peace,
Josh

Thanks for the quick reply Josh,
Do you have any ideas at the moment as to the cause? Is it the number of connections, type of connections....... so that I can avoid the bug cropping up.
Also is there a workaround that you're aware of....
oh, and nice work chef
Cheers,
Bri.

BrianP6 said:
Thanks for the quick reply Josh,
Do you have any ideas at the moment as to the cause? Is it the number of connections, type of connections....... so that I can avoid the bug cropping up.
Also is there a workaround that you're aware of....
oh, and nice work chef
Cheers,
Bri.
Click to expand...
Click to collapse
This bug appears only when 2 or more devices get paired.
I've been trying everything, even abusalza himself suggested some module replacement. i'm working on replacing drivers and certain folders in sys in my kitchen but still nothing yet... so far not yet, but it's fixable, i just gotta figure it out.

Thanks Josh,
I guess you'd know this anyway, but for completeness and for the benefit of the whole forum.........
Even though the paired devices are no longer shown in the Bluetooth Devices window, and you can no-longer use your HTC to pair more devices, then so long as you carefully initiate the pairing from the other device, it will be recognised, PINs will be requested and devices configured appropriately. I have just done:
Audi A4 in car kit
Laptop via Internet sharing
Jabra earpiece
None appear on the Devices window, but all (so far) appear to work perfectly.
Cheers,
Brian.

I have had a similar nagging problem with my Motorola S9 and Hermes 100/Cingular 8525. After a new flash, I can pair the headset and the phone relatively easily. During first pairing, I am *not* prompted for the headset's PIN. Over time, switching between phone and music functions becomes more unreliable. Icons disappear while the headset is in use. Discontinuing a call with the headset results in audio resuming through the external speaker instead of the headset, etc.
Eventually, out of the blue, the headset will fail to pair; and I will receive a prompt to enter the PIN number for the headset. I enter the PIN and the phone refuses to accept that it's the correct PIN. From that point on, I'm screwed until I reflash the phone. It never works properly anymore.
This has happened across multiple ROMS, including some of Josh's that I've tried. It happened again the day before yesterday with one of TAI_Sw's ROMS I'm currently using. In this case the profile in Bluetooth settings appeared to be corrupted. The profile no longer read "Motorola S9". Instead it showed a series of block characters (like unsupported fonts). I was able to delete the profile, and, after multiple resets (hard and soft) the phone finally redetected the headset and we went through the configuration wizard again. It's been mostly working well since then.
Has this happened to anyone else?

austinsmartie said:
Has this happened to anyone else?
Click to expand...
Click to collapse
Yep, I have experienced everything you mentioned at one time or another, even the square characters showing up in the device list.
I have gone all the way back to test Faria R32 ROM. It's amongst the best I've found for A2DP with the S9's along with some of PDACorners early ROM's. The drawback are that it doesn't have the 1% battery increase .dll cooked in and also still exhibits the "numbers for character during a call" bug.
It does have nearly 31 MB of memory free after fresh install though. (using 4MB pagepool - default is 6MB)

austinsmartie said:
I have had a similar nagging problem with my Motorola S9 and Hermes 100/Cingular 8525. After a new flash, I can pair the headset and the phone relatively easily. During first pairing, I am *not* prompted for the headset's PIN. Over time, switching between phone and music functions becomes more unreliable. Icons disappear while the headset is in use. Discontinuing a call with the headset results in audio resuming through the external speaker instead of the headset, etc.
Eventually, out of the blue, the headset will fail to pair; and I will receive a prompt to enter the PIN number for the headset. I enter the PIN and the phone refuses to accept that it's the correct PIN. From that point on, I'm screwed until I reflash the phone. It never works properly anymore.
This has happened across multiple ROMS, including some of Josh's that I've tried. It happened again the day before yesterday with one of TAI_Sw's ROMS I'm currently using. In this case the profile in Bluetooth settings appeared to be corrupted. The profile no longer read "Motorola S9". Instead it showed a series of block characters (like unsupported fonts). I was able to delete the profile, and, after multiple resets (hard and soft) the phone finally redetected the headset and we went through the configuration wizard again. It's been mostly working well since then.
Has this happened to anyone else?
Click to expand...
Click to collapse
It frustrated me enough that I started building my own rom!
I released one version here that I have been running for quite some time with no issues in the bluetooth at all.
I need to tweak it a bit more to make it "polished" but it is very useable and stable. I just wanted to run it for a while to see how it is going to act over a longer duration before I continue to fool with it, and I have been rather busy here lately.

Well, if you have a magic potion, please share with the community. And, by the way, this is the only device I pair to my Hermes; so this may be different from the problem Josh and others have described.

joshkoss said:
Hey man, Unfortunatly this is a bug with my current kitchen, I believe he is using parts of it for making roms. I'm working to fix it soon in my kitchens.
Peace,
Josh
Click to expand...
Click to collapse
i just installed your new v15 color(thanks very much for that release it looks great) and i definitely want to pair 2 devices with the phone. this has worked for me in whichever random wm6 rom i found on the web last year and i have been trying to find the right rom for me this week so my question: is this a random bug, is there a trick to doing it right or am i just plain sol?

Hmmm - doesn't happen on my ROMs...
The suspect things I'd be looking at in SYS are:
Bluetooth
Bth_A2DP
Bth_HID
Try replacing those folders with known good ones and see if the problem still happens...

austinsmartie said:
Well, if you have a magic potion, please share with the community. And, by the way, this is the only device I pair to my Hermes; so this may be different from the problem Josh and others have described.
Click to expand...
Click to collapse
No Magic potion! lol
I basically did what CRCinAU described. (His rom doesn't have the issue, and feels a bit faster than mine. But, I was looking to create "My perfect rom").
But I also replaced files in the redist folder with "bt" in their name, with files from a known working rom (anryl's 20755). Like I said I wanted to run the rom for a while, now I just need to go back and tweak and clean up some things in the rom before I make another release.

summary
stickybud said:
i just installed your new v15 color(thanks very much for that release it looks great) and i definitely want to pair 2 devices with the phone. this has worked for me in whichever random wm6 rom i found on the web last year and i have been trying to find the right rom for me this week so my question: is this a random bug, is there a trick to doing it right or am i just plain sol?
Click to expand...
Click to collapse
it is a really odd issue and seems to only affect the hermes... Here is the deal, Some chefs when porting sys grab the cplmain.dll to get the build number and keep some other items in their kitchen sys for stability purposes... I have noticed in my experience when porting, if the cplmain.dll does not match some other components with the same build number it will cause this issue. usually resist, shell, os, folders have been containing these sensitive items. so in short, if the issue is occuring cplmain.dll in redist folder does not match other components in your sys causign the conflict.
edit, and oh. i've tried replacing all bluetooth which had no effect.
So to fix this, the chef needs to report sys correctly and recook the rom.

Pairing problem with VW Scirocco (RCD 510)

Hello everyone,
I'm having a problem with the RCD 510 Premium Bluetooth kit that is installed on the new VW Scirocco and its been troubling me for over 2 months now.
When I first got my Scirocco the Bluetooth connection was working fine (for 3-4 months). One day out of a sudden the Touch Pro II was not pairing anymore with the car's bluetooth kit.
At the time I was using Windows Mobile 6.1 that originally came along with the phone. I tried the basics - deleting the connection, re-pairing - with no success.
So I gave a shot at phone's factory reset - still no luck. The phone is recognized when I use the "Device Search" function on the car, it prompts me to enter the pass code provided, I do so, the phone loses the GSM signal (which of course is normal) but then suddenly I get a message on the RCD510's main screen "No bluetooth connection to phone" that lasts for about 2 seconds.
Since the problem began, I tried factory reset the phone (as I mentioned before), and tried pairing before installing even a single software, still no luck.
I tried multiple ROM's in the meanwhile (I mean third-party ROMs from this forum) and now I am using the official Windows Mobile 6.5 from HTC for my phone.
I also did many tests using third-party applications for the rSAP protocol (JetWare hands-free extension, SAPSettings, some patches and drivers found around the net here and there) even though there is native support for rSAP since the first firmware that came along with the device.
As I mentioned before, the phone was pairing fine the first 3-4 months.
Please note that this phone uses the Widcomm Bluetooth Stack - not the Microsoft one.
Any help/ideas would be greatly appreciated.
PS: I apologize for the big length of the post, but I believe the more the information I provide, the more the chances to get proper help

Sorry i cant help you but.. I want your CAR...
Any pics?
Well.. try this
Unhook the cars battery. Let it reset the radio (make sure you have the radio code if any) and try again.. maybe the radio is holding some sort of setting. Resetting to default (like with the device) might do the trick..

.
Thanks for the idea. I'm kind of worried though plugging out the battery, because there are many settings besides the radio that probably will be lost if I do so.
You know all these new cars and their complicated electronic sensors...I don't mind losing minor settings for the car that I have adjusted, my main concern is that if anything goes wrong, I will probably have issues with the car's warranty. I still have 2 and a half years of warranty.
I' will probably have a talk with the dealership before doing that.
Many thanks for your thought though

hi i like to know if pairing went okay with the 6.1 rom because if so maybe when you switch back to this rom problems are solved

Nop
Unfortunately no
It was one of the first things I tried. Switching back to the official 6.1 ROM. I actually kept it saved on my hard disk and I tried it a couple of times - I mean when I tried other ROMs from time to time - hoping it would resolve the issue.
And that's the strange of this case. I mean, it was working (pairing) fine the first couple 3-4 months when I unboxed the phone, and then out of a sudden, no pairing.
First logical thought would be that something has changed in the car's settings. But I have an Athena X7500 that pairs fine with the car up to this day. My car's dealership isn't much of a help...
Second thought - phone settings mess-up. But as stated in my original post, no factory reset helped, no switching to other ROMs, no playing around with settings.....
I'm really desperate. I'm thinking to switch to another phone, but besides this problem I'm quite satisfied with the TP2. And I do "need" Windows Mobile based phones, because I sync with Thunderbird's Lightning via BirdieSync for a long time now, and I am not willing to revert back to the horror days of MS Outlook. I carry my TB profile for over 2 years now and its customized the way it suits me for manipulating my 10+ email accounts.
Thank you very much for your reply though
Any other thoughts/recommendations?

i downloaded firmware 1.20 from volkswagen hope this will help me will try tomorrow with my laptop i am with a touch adapter connected to rns 510 no pairing with tp 2 at the moment for me the only workable solution is a duo sim with my old blackberry bold meanwhile i love he TP2 so hope i can get it to pair with my premium touch adapter volkswagen carkit any other suggestion or solutions are very welcome cheers

And that's the strange of this case. I mean, it was working (pairing) fine the first couple 3-4 months when I unboxed the phone, and then out of a sudden, no pairing.
what radio where you on first couple of months

Nice thought about the radio....but unfortunately I don't remember.
Currently I am using v4.49.25.17 that was upgraded with the latest official HTC firmware of WinMo 6.5 if I am not mistaken.
I am 90% positive though that the problem started before even upgrading, back when I was using the first release of WinMo 6.1 and the unknown version of radio, and everything was working ok at the beginning.
I know, I am not helpful at all but frankly, this problem surprises me as much as you.
You mentioned a firmware upgrade - for the RNS right? Not the RCD....
Do you by any chance happen to know if there is a firmware upgrade for the RCD510 and where can I get it from?
Thanks for your help.

looking-g:
I just realized that you are having a problem with the RNS.
Did you had this all along? I mean, did you ever managed to get it working and then it stopped, or you never had it paired?
I am just asking to see if I can be of any help...

well the problem is not with the rns 510 but with the touch adapter which come delivered as premium carkit i use to pair everything with it blackberry,s nokia,s and also a touch dual (niki) without any problem but now with my new phone the tp2 its not pairing it also never did after i fill in the pincode it gives an error message it should connect with the touch adapter my car by the way is a golf gti mk6 cheers, mark

You kind of lost me there.
What do you mean "touch adapter"? Is this a component of the RNS 510? Because I have never heard of it...

Have you determined a solution?
I just picked up a new VW Jetta with premium bluetooth and it worked the first time and not since.....

You guys are scaring me -- I have an Audi A3 TDI scheduled for delivery in January, and it'd be a bummer if its Bluetooth didn't work. FWIW, my current car has a Sony MEX-BT3700U headunit and the Tilt 2 pairs with it in both handsfree & A2DP modes.

3waygeek: You will be probably fine. I think Audi does not have anything to do with Nokia regarding building their units.
Wish you best luck with that.

Extra info
Some more information regarding the whole subject:
I found out that when I press the "Emergency Call" option on the touch screen of the RCD510 (i.e. try to call the international emergency number - 112) and then immediately end that emergency call, the next time I try to pair the Touch Pro 2, it does pair!!! But it has no signal at all, and if you try to make a call you get a "Dial up error" (or something like that, can't remember exactly)!
Any ideas what could be the reason for that?
Thanks.

Your problem is common to VW/Audi's. Chances are the car kits have the rSAP Bluetooth unit. I had exactly the same issue in my A6 using rSAP, as soon as i upgraded to wm 6.5 the problem went away.

Yes, indeed the car kit uses the rSAP profile, as well as the Phonebook Access Protocol (PBAP), but both of these protocols are supported by the TP2. Actually the rSAP functionality I believe is support in Windows Mobile 6.1 and above - I mean besides the fact that your phone's BT radio must support it in order to work correctly. (Without being entirely sure for the above comment).
And some more info for those who are willing to give an opinion:
I did eventually decided to remove the car's battery. I left the car without battery for approximately 40 minutes. Now here's the strange part: All the settings of the card indeed reset (window settings, light settings, etc) BUT the RCD510 was not affected at all by the battery removal! Yes, as weird as it might sound, the station list was there, bass/tremble customizations were there also, everything in place (regarding the radio unit always).
Side note for all those who might remove the battery from a similar VW car:
As soon as I plugged the battery back on, I had somewhere 15+ warning indicators on my dashboard turned on. From ABS malfunctions, air pressure, EPS malfunctions etc. But after rolling the car for 3m or so everything turned off. Back to normal. Probably had something to do with the electronic sensors giving proper signal to the car's "brain". Just my opinion.
Now, besides that - the fact that removing the battery didn't perform a reset of the radio (RCD510) unit, I also tried reverting my Touch Pro II to a WM 6.1 cooked ROM - don't remember which one exactly - but that didn't helped either. Same stupid error message after pairing for 2 secs: "No bluetooth connection to mobile phone".
And to confirm again: My X7500 (Athena) with a cooked WM6.1 ROM from michy still pairs and works fine. (Tested it last night, just to make sure that battery removal didn't had any side-effects)
PLEASE help me if you can. Any suggestion/recommendation will be greatly appreciated.
PS: I decided to contact the car's dealership to inform them about the whole problem. I will post soon regarding how that went...
Thanks for your time everyone...

By the way, does anyone knows the proper way to reset the RCD 510 to it's factory default settings? Besides the function that is given inside the menu itself - I already tried that. I was just wondering if there was a "hidden" way that will entirely wipe all settings/customizations from the unit....

Hi guys! I m in the same situation: Sirocco + TP2 with 6.5 from Orange. Any progress from your side? Ideas would be greatly appreciated!! Cheers, P

Unfortunately!
No friend, sorry. No news yet.
I do keep the post open hoping that someone will give me a new year's present
It's nice to know that I am not alone though

Bluetooth issues with car

All;
I've tried several ROMs (including my stock one for my Tilt 2) and I still can't seem to get my phone to work correctly with my car. The phone will dial, connect for about 2 minutes, then the sound will stop coming from my car and go back to the phone. It still says the call is connected from the car, but no more sound and the phone won't reconnect by telling it to use hands-free. It also takes a good minute or so to kill the connection when I hit end on my car.
Any ideas/tweaks/registry hacks you guys can think of? I looked at the MS site for registry changes and those only messed up the phone My car worked fine with other phones and my phone will work fine with other bluetooth devices (headsets, other cars, computer, etc), its just this unholy union seems to be causing problems. I've tried bitpool changes, profile tweaks, etc to no avail. The car manufacturer says my phone 'should' work, but of course, they won't troubleshoot it...
Thanks!
J

Have the same problem with my volvo carkit. Manual switching off the data connection in con.man. may solve your problem temporaly. Bluetooth on HTC really sucks......

same here with vw premium phone with touch adapter and rns 510 all new but not able to connect with my tp2 all other phones work can somebody produce a solution i am happy to donate for it

Dunno if this helps, but I have a TomTom GO 750 and connect to it with the TP2 for handsfree. Im running stock wm6.5
Most of the time its OK. Occasionally the phone wont allow connections, so I have to disable/re-enable Bluetooth on the phone and all is good.
Also, sometimes, every 25 secs or so there is a beep while on a call. Kinda weird. But acceptable.

Well, at least it's not just me
Is there anyway we can change out bluetooth stacks or 'downgrade' the Bluetooth version through software/registry hack? I don't need any fancy bluetooth features, I would just really like my car to work with it!
I'll try the data connection and see, but you're right, not really a long-term fix. Thanks for the idea, I think I tried everything else and option in the gui...

looking-g said:
same here with vw premium phone with touch adapter and rns 510 all new but not able to connect with my tp2 all other phones work can somebody produce a solution i am happy to donate for it
Click to expand...
Click to collapse
I had this same issue where it wouldn't connect. What it ended up being was mis-matched bluetooth names in the various places. Check your bluetooth configuration as well as any tweak programs that may allow bluetooth tweaks, mine were set differently and freaked my car out.

Had the same issues: connection seems fine, but most of the time no sound at all.
I tried different solutions found on different websites, but for me, this one fixed all my bluetooth issues: http://www.everythingwm.com/forum/moto-q-9c/q9c-and-infiniti-g35x-bluetooth-problem-16833-4.html
I applied the registry settings (not all reg keys mentioned did exist on my phone), re-paired (renault built-in carkit), and bluetooth is working fine now.

Similar Problems on GM
I wonder if we are having problems stemming from the same root cause or multiple root causes.
Regardless, I'm having similar problems on a 2009 GMC Yukon with built in Bluetooth. The phone is connected and rings through the auto, but when I hit the off hook to answer, I get no sound and the caller gets no sound. It appears everything connects and the phone says the call is connected, but no good. Usually if I initiate the call from the phone it will work correctly and sometimes not.
I solve it be deleting the phone from the car and the car from the phone and re-pairing, but it only works well for a short while then it fails again.
I'm hoping someone comes up with a great solution(s).

farhope said:
Have the same problem with my volvo carkit. Manual switching off the data connection in con.man. may solve your problem temporaly. Bluetooth on HTC really sucks......
Click to expand...
Click to collapse
Well I'll be... That is what fixed it! Well, not really a fix as I have to disable my data, but actually makes it usable.
Do you know if there is an app out there for this? NoData, while great, doesn't shut down the connection. There is a donation if someone will write one for me

aert said:
Had the same issues: connection seems fine, but most of the time no sound at all.
I tried different solutions found on different websites, but for me, this one fixed all my bluetooth issues: http://www.everythingwm.com/forum/moto-q-9c/q9c-and-infiniti-g35x-bluetooth-problem-16833-4.html
I applied the registry settings (not all reg keys mentioned did exist on my phone), re-paired (renault built-in carkit), and bluetooth is working fine now.
Click to expand...
Click to collapse
Did you create the missing keys/folders or just make changes to the keys you had?
I'm willing to try anything to not have to disable my data everytime I want my phone to work! Yes, I'm that lazy to expect things to work right the first time

All right! Got it fixed, thanks guys.
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 DisableReopenAudio to 0 (default is 1)
3. Reboot device
I tested it for a few minutes and it was solid and sounded good, no freaky occurances. We should sticky these for other people having BT issues...
Credit to EverythingWM and aert for the pointers!

thats good news loki but some values i can not find in my registry i will try to add them and then give it a go

looking-g said:
thats good news loki but some values i can not find in my registry i will try to add them and then give it a go
Click to expand...
Click to collapse
Yes, I added the missing ones, restarted the phone, re-paired with my car and, so far, works great. I'll give it a week before I start doing the happy dance.

is it possible to make a cab or reg key file for it

I can create a reg for all the keys except the HFBDA key. That should match the LastConnectedBDA key which may be different on our phones. What is yours set to? Mine is 00,1e,ae,20,c2,80. I wouldn't want to have someone import it when the setting isn't right for their particular build/version/etc.

Loki007 said:
All right! Got it fixed, thanks guys.
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 DisableReopenAudio to 0 (default is 1)
3. Reboot device
I tested it for a few minutes and it was solid and sounded good, no freaky occurances. We should sticky these for other people having BT issues...
Credit to EverythingWM and aert for the pointers!
Click to expand...
Click to collapse
Could anyone explain what these settings mean? There is no point of tweakin something if I do not know what each of setting does, well of course it has a point of tweaking it, but I would really like to know what it means. Does anyone has a problem syncing the phonebook after aplying that tweak or it is just me?
Thanks for help!

Can someone explain what all of these REG changes do?? I dont want to end up like before. There was a CAB floating around that was supposed to fix the BT issues and while it made it better it drained my battery VERY VERY quick.
Do these changes have any effect on battery life???

aert said:
Had the same issues: connection seems fine, but most of the time no sound at all.
I tried different solutions found on different websites, but for me, this one fixed all my bluetooth issues: http://www.everythingwm.com/forum/moto-q-9c/q9c-and-infiniti-g35x-bluetooth-problem-16833-4.html
I applied the registry settings (not all reg keys mentioned did exist on my phone), re-paired (renault built-in carkit), and bluetooth is working fine now.
Click to expand...
Click to collapse
WOW.. now when my TP2 rings, I actually get the custom RINGTONE out of my GARMIN NUVI SPEAKERPHONE and it doesnt DROP calls right after the first ring AND I can answer and hangup fine.. the phone book is still a little messed up in that any contact with ONLY a COMPANY NAME and not a first and last name loads as a phone number in the name field...
Does anyone know if any of these REG changes degrade battery life? I am asking because a while back I had a CAB that was supposed to fix the bluetooth and while it improved the paring, it drained my battery live very very fast.
Also can someone explain WHAT these reg changes and additions do? I would really like to know what I am doing to fix the issue...
-- Dave

One more thing, now with the fix, it appears on my garmin, when I press LAST DIALER, LAST RECEIVED or MISSED, I get NO DATA AVAILABLE .. I didnt have this problem before the fix.. Is there a solution??
Thanks....

Loki007 said:
I can create a reg for all the keys except the HFBDA key. That should match the LastConnectedBDA key which may be different on our phones. What is yours set to? Mine is 00,1e,ae,20,c2,80. I wouldn't want to have someone import it when the setting isn't right for their particular build/version/etc.
Click to expand...
Click to collapse
correct; mine is different from that.
also, the bdaddr key keeps resetting itself when I reboot my phone.
I even tried changing the key type to something other than binary, and it still reset itself to binary, and changed back tot he default value.
These hacks did not work at all.
I came across this cab that changes some BT settings, but at least one guy reported it draining the battery very quickly (not enough posts to post links...sheesh):
forum.ppcgeeks.com/showthread.php?t=90155&highlight=bluetooth