Develop Bugs

Black 2.0 hidden benefit: Signal strength indicator shows on BMW screen now!

This has never shown up before with any Windows Mobile device I have used. Now I have the signal strength indicated in the screen which, along with all of the other features that I'm fortunate enough to have gotten to work properly, is a VERY nice thing to have.
What changed in this version that makes is possible for this to show up?

pinhead said:
This has never shown up before with any Windows Mobile device I have used. Now I have the signal strength indicated in the screen which, along with all of the other features that I'm fortunate enough to have gotten to work properly, is a VERY nice thing to have.
What changed in this version that makes is possible for this to show up?
Click to expand...
Click to collapse
I noticed this as well. I have an Acura. Previous ROM versions did not show the battery or signal strength. Now both show up. I would like to know what changed for this to work as well.

May be a feature of wm6 seeing black 2.0 is based off of a RTM rather then a beta version would explain why it works on black 2.0 rather then others.

pinhead said:
This has never shown up before with any Windows Mobile device I have used. Now I have the signal strength indicated in the screen which, along with all of the other features that I'm fortunate enough to have gotten to work properly, is a VERY nice thing to have.
What changed in this version that makes is possible for this to show up?
Click to expand...
Click to collapse
What BMW have you got?

anubus12 said:
I noticed this as well. I have an Acura. Previous ROM versions did not show the battery or signal strength. Now both show up. I would like to know what changed for this to work as well.
Click to expand...
Click to collapse
It's the bluetooth stack that has been updated in wm6. my bmw now works without jetware software, transferring full phonebook and no disconnects.
its well good!

eaglesrest said:
It's the bluetooth stack that has been updated in wm6. my bmw now works without jetware software, transferring full phonebook and no disconnects.
its well good!
Click to expand...
Click to collapse
Transferring phonebook to the in car system? Is that a function of the BMW system? Mine doesn't that function i don't think

Using this ROM on my BMW causes a funny. Once the device pairs with the car, it says I am connected in a call and starts timing, even when I am not in a call. I have to turn BT off and on again for it to stop the call status.

Yeah, the phonebook has always transferred over properly, caller ID has always worked, and the call quality has been excellent. However, I hadn't been getting this particular indication on the screen.
Rothes, it is an '07 3-Coupe. I will tell you though, the car is not the finicky part of the connection. While all of the Hermes phones work very well with the system's bluetooth setup, I tried for a few days with a Treo 750 and it dropped the connection after exactly 1 minute every single time, and this NEVER happens with my TyTN or 8525. These are the only phones I have ever tried in the car but I certainly suggest staying away from those Palm Treos for this reason and many, many, many others!!

pinhead said:
Yeah, the phonebook has always transferred over properly, caller ID has always worked, and the call quality has been excellent. However, I hadn't been getting this particular indication on the screen.
Rothes, it is an '07 3-Coupe. I will tell you though, the car is not the finicky part of the connection. While all of the Hermes phones work very well with the system's bluetooth setup, I tried for a few days with a Treo 750 and it dropped the connection after exactly 1 minute every single time, and this NEVER happens with my TyTN or 8525. These are the only phones I have ever tried in the car but I certainly suggest staying away from those Palm Treos for this reason and many, many, many others!!
Click to expand...
Click to collapse
I was trying to see what bluetooth set you have. Mine is on the normal radion, not the TFT and it does not display Batter and signal strength.
My wife has an X3 with bluetooth too, but a TyTN with WM5 still. It randomly does not see the phone and does not pair.
I have used the set with my iMate JAS, TyTN and ETEN M600, and all have worked fine, even a BlueAngel with WM5.
The earlier versions of WM6 have all worked fine, just the latest one that causes the fictitious connections.

Never paid much attention to the X3...just drove it as a service loaner a few times and never paired my phone in it. Pretty fun to drive though. I do know that with WM5 on the TyTN it might not always see the phone but I don't know why. I just turned off the bluetooth on the phone and turned it right back on. I am impressed by how reliable the BMW system seems to be. The phone is really the main variable. I am betting that when she upgrades her phone that the TyTN will pair and connect properly to the X3 with almost no issues.
Since I have only had WM6 on my 8525 I have not seen if is any different in connecting with the car using WM5 but with WM6 it has been nearly perfect.
Which BMW are you using besides the X3? Or is that the only one in which you experience (or your wife does) issues?

I have a '06 320d.

pinhead said:
This has never shown up before with any Windows Mobile device I have used. Now I have the signal strength indicated in the screen which, along with all of the other features that I'm fortunate enough to have gotten to work properly, is a VERY nice thing to have.
What changed in this version that makes is possible for this to show up?
Click to expand...
Click to collapse
Same with Jeep Cherokee. Battery guage shows up too.

pinhead said:
This has never shown up before with any Windows Mobile device I have used. Now I have the signal strength indicated in the screen which, along with all of the other features that I'm fortunate enough to have gotten to work properly, is a VERY nice thing to have.
What changed in this version that makes is possible for this to show up?
Click to expand...
Click to collapse
Hi Pinhead,
I would be more than happy to figure it out and provide a free report of what I found. But I would need to borrow your BMW for a few weeks. Just let me know when I can pick it up, ok.
But really, as others have stated it is the updated Bluetooth stack, which should even be better in the newer wm6 builds.

anubus12 said:
Transferring phonebook to the in car system? Is that a function of the BMW system? Mine doesn't that function i don't think
Click to expand...
Click to collapse
The Acura's bluetooth used to be one of the coolest 'high tech' device and the FIRST in cars...but..thanks for being the FIRST, now it is obsolute compare to other newer bluetooth device in other cars.

trashcan said:
The Acura's bluetooth used to be one of the coolest 'high tech' device and the FIRST in cars...but..thanks for being the FIRST, now it is obsolute compare to other newer bluetooth device in other cars.
Click to expand...
Click to collapse
I don't know about that...from what I remember about the Acura's system I think it is quite simple to use. Instead of messing with that awfully inconvenient (and sometimes downright annoying) BMW iDrive, the Acuras use a touchscreen interface, which is much easier to use. I think this applies to the phone controls too...right?
Rothes, nice choice! It is funny...everyone sees that 320d on the back and thinks it can't move...they don't know that it has all that torque.
Eagle 1, sorry but my sister has already claimed the car! I'll have to go buy myself something soon so she can have it...I guess it is time though.

I have a Parrot CK3100 and for the first time showing batt. and signal

this is great news!
now all I need is a BMW.

thanks for discovering this
I guess the new build does have hidden benefits

I've had signal and battery for ages on my Parrot CK3300, by installing Jetware Mobile on my TyTN.

I also discovered the new "signal strength" indicator with my BMW.
Strange part was that I "thought" I had seen it previously, until yesterday, when a new "phone icon" showed up.
I realized that it was the "phone icon" that I had previously (briefly) seen, so I now have the "phone icon", "antenna icon" and "signal strength icon".
So what is the "phone icon" supposed to mean?

8525 + Jawbone + 3 seperate ROMS = No Sound!!!

Now before anyone goes bashing me for not searching the forum, lemme tell everyone, I've done just that. I just haven't found the answer to my problem.
I recently acquired an 8525 (which I'm loving BTW ). I have a Jawbone headset that pairs up fine with all of my phones (BB Pearl, 8125, & 8525). Only problem is, I can actually *use* the Jawbone with my Pearl and my Wizard, just not my Hermes.
I've paired, deleted, and re-paired again but to no avail. I've tried to get an actual conversation going using 3 different ROMs: AT&T's official WM6, Schaps 4.30 Full, and vp3G's 3.62 Full, but nothing works. I've reset the Jawbone more times than I can count, and I still can't use it.
ANY input on this would be GREATLY appreciated, since I actually *need* to use it for work...

BombaMyte said:
Now before anyone goes bashing me for not searching the forum, lemme tell everyone, I've done just that. I just haven't found the answer to my problem.
I recently acquired an 8525 (which I'm loving BTW ). I have a Jawbone headset that pairs up fine with all of my phones (BB Pearl, 8125, & 8525). Only problem is, I can actually *use* the Jawbone with my Pearl and my Wizard, just not my Hermes.
I've paired, deleted, and re-paired again but to no avail. I've tried to get an actual conversation going using 3 different ROMs: AT&T's official WM6, Schaps 4.30 Full, and vp3G's 3.62 Full, but nothing works. I've reset the Jawbone more times than I can count, and I still can't use it.
ANY input on this would be GREATLY appreciated, since I actually *need* to use it for work...
Click to expand...
Click to collapse
I am currently using my Jawbone with Schnaps 4.01 Lite rom and no problem. Before that I have been using all of Matt's Pandora Kitchen roms, right up to the latest and never had a problem. I ran Schnaps 4.30 Full rom too, but really can't remember if I used the Jawbone during the testing time. If someone else can't help I can flash that rom again and test the Jawbone with it too. Let me know ho wit goes.

works with vp3g3.62. no issues, didnt require anything special. Does bt radio on your 8525 work?

I have an 8525 running Schaps 4.30 with radio 1.48.00 and mine is working. I did however have to return one Jawbone because it would connect and I could hear the conversation but the mic didn't pick up my voice. I tried that one on my wife's razor and it had the same symptoms though. What radio are you running?

Using with TNT's latest ROM and no problems, however not real impressed with Jawbone so far. Most people I call say it sounds "tinny".

mthomas said:
works with vp3g3.62. no issues, didnt require anything special. Does bt radio on your 8525 work?
Click to expand...
Click to collapse
AFAIK, the BT radio works. Like I said, I can pair up with it just fine, and even see the other BT-enabled phones/devices at my job. I just can't get any type of audio from my JB. I'm currently using vp3G as well.
UPDATE: Well to be on the safe side, I tested my Jawbone on a couple other phones; sure enough it's working fine, so it's got to be something up with my poor Hermes... Any advice?

Mine Jawbone Works fine also. I remember when I first got it I was having trouble with my sound. I remember changing the audio bitrate from 48 bit to 44 bit in the advanced config utility 1.1 Also try changing the stereo setting to mono.
May help you out, hope so.

Just a quick update: I reflashed vp3G's 3.62 ROM, reset my JB and repaired it; same effect, nothing. Just to be on the safe side I paired the JB with my Wizard, BB Pearl, and a couple of phones at my store and it works as it should.
@ mthomas: I'm using 1.48.00 for my radio. Since you and I seem to have the same type of setup, did you install any other cabs that help your BT out?

Do you have another Bluetooth headset to test. Even thought it can pair ok, it only means the "data" channel is working. The problem could easily be the voice channel which is not working. If possible, may be borrow another headset to try.

That's my next idea. I think I have an old Plantronics I can charge up and test out...

*BUMP!*
Gotta keep this fresh. Funny thing I noticed though: when I have the Jawbone connected and the phone rings, I still hear it's little tone in my ear, but no audio comes or goes through. No registry edits have been made; I've even done a hard reset, re-paired and tried again, to no avail.
C'mon you guys! Why am I the only 8525/Jawbone user around here that *can't* use his Jawbone??? Help me out here...

wish i had the answer. im using the most current att radio 1.54.07.00. how did your device work w/ another headset?no additional tweaks

Okay, now I'm getting pissed.
I tried using my old Plantronics 320. It pairs fine with the Hermes, but making phone calls is a no-go.
The only thing I removed (from anyone using vp3G's 3.62 Full) was Sleuth's PTT Fix; I need PTT more than being able to re-map the button. So I doubt this is the culprit.
WTH can't I use my good Jawbone with this thing?!?!

Quick *bump*

Same Problem
I have tried everything, I can hear the calls just fine but no sound from my mic. I have paired with other phones & it works fine. Please let me know if you find a fix!!

UPDATE: I tried using a Moto H700 and a Plantronics 340-no dice. Now I'm starting to think if it's a BT stack issue...

Now I'm completely stumped. I just flashed back to the original ATT WM5 rom, paired up, SR, then made a phone call to my 8525 from my house line. Jawbone rang in my ear, sure. I answer the call, no sound.
Could there be a problem with my BT radio? And if there is, how can I be sure/troubleshoot it?

Just throwing someting into the pot. have you tried unpairing it with your other phones? I know i was trying to pair my to my wifes and it would work because it was paired to my phone. Try deleting the relationship between the other phones. Other than that if its new enough just take it back and get another

myv6mustang said:
Just throwing someting into the pot. have you tried unpairing it with your other phones? I know i was trying to pair my to my wifes and it would work because it was paired to my phone. Try deleting the relationship between the other phones. Other than that if its new enough just take it back and get another
Click to expand...
Click to collapse
Good thought... But I already did that, still no joy. In fact, I just flashed over to HTC's official TyTN rom, and still nothing. I'm going to call a friend of mine and see if I can get it to work on their 8525. Here's a good ? tho: Should it matter if it's Cingular or AT&T branded? Are there any differences in hardware between the two types? Or could it be a faulty BT radio? I'm racking my brain trying to figure this out.
Worse comes to worse, I'm sure I could exchange my Jawbone; I *do* work for AT&T so it should be okay...

Okay, here's another question: If I were to flash *ALL* the way down to the original Cingular shipped ROM, RUU_HER_Cingular_1.34.502.1_1.16.00.00_wwe_cws_ship, would this have any effect on the BT stack? I'm only asking because I can't seem to find any type of information about replacing the built-in stack (outside of the Widcomm project and that's too beta for me ATM), and I still can't understand why so many headsets that I've tried with this damned 8525 don't seem to work, but so many people here @ XDA can use theirs. There's no differences between the Cingular branded and AT&T branded models (at least hardware/software-wise), and if I pair up my trusty Jawbone with another 8525 (AT&T branded, btw), it works fine.
I know I've been going back and forth with this, but I did pay a good amount for my 8525 and I don't want it to be partially or mostly functional. Hell, if my poor Wizard can handle my Jawbone, why can't my Hermes?
BTW, thanks for all of the suggestions you guys have given me to help me with this problem. Even though none of them have worked, I still need to give props where they're due.

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

Bluetooth issue with wm 6.5 and sense 2.5

Ok here's my problem:
I make custom dutch roms for the Rhodium (touch pro 2).
I use the latest XIP/SYS builds (28009 at this moment) and I use manila/sense 2.5
(Almost) everything works great!
I also own a pioneer car-entertainment set (avic f900bt) which has a built in parrot bluetooth carkit.
Pairing goes perfect and I can transfer my phonebook and make calls.
The problem is that when I recieve a call and try to hang up the system hangs and needs a reset. My TP2 also hangs for a while after such an event and then after minutes goes back to the today screen.
At first I thought it was my carkit, but my wife's samsung and my brother in law's blackberry work fine.
Then I tried my own phone with the latest OFFICIAL 6.5 rom (dutch) and it worked great.
So I started to trial and error with different adjusted roms. I got it all working with the newest XIP/SYS builds. But the problem seems to lie somewhere in manila 2.5. I even got it working in manila 2.1 without any bugs
But with 2.5 I get the problems above. And I forgot to mention another bug:
- When I make a call or recieve a call I do not see a 'red phone' button to hang up which I do see with other phone's or roms without manila 2.5. So I have to end a call on my HTC instead of my carkit. And when I try after recieving a call it hangs as described above.
After 2 weeks of flashing and trying I give up...
I use the OEM from the latest official dutch 6.5 rom so those drivers can not be the issue. As stated before...It's all pointing to manila 2.5. But after flashing disabling manila does not fix the problem. So it must be somewhere in the cooking proces (Ervius VK 1.82)
Please one of you supreme chefs help me out here because it's frustrating me now and I want to get it working as it should.
Thanks a milion in advance!!
EDIT: to the mods; I did not know where exactly to post this after the re-organisation. So please move if neccesary.

Almost 170 views and no comments??
Please fellow cooks...I'm desperate...

Well i do think you already have an answer.
But the actual non existing pressure you feel from users that always want the latest no matter how buggy it might be
When MS started to "Leak" builds beyond 20000 (But before 21054).
I also started noticing Bluetooth pairings going haywire and acting differently.
As i don't care that much about what most "Flashers" think and tend to believe that the choices i make concerning cooking a rom are probably more founded in what is right.
I tend to stick to stable OS Builds. It's the New Age XDA dilemma, either dish out unpredictable New Builds, or make a ROM that in the first place Suits you and has the functionality You need.
In this case that would be an older SYS.
I think that also because of TP2 has now switched to different Bluetooth Stack and 2.1+EDR isn't helping.
And it might be that MS is actually working on getting up to speed and changing their own BT Stack, so HTC will not need to turn to WidComm for the BT Stack.
I do believe that there are a few Senior Cheffs and some Non Cheffs do probably know which other parts (besides the Obviously named Bluetooth related SYStem parts), might be related to dealing with Bluetooth Pairing and such.
Whatever solution there might or might not be, don't hesitate to make it hybrid.
Use the old fashioned method of dividing and conquering.
(Get a good supply off Coffee)
Start with Stable Release Build SYS replace 50% test. (leaving all obviously Bluetooth related Packages from Stable Build)
Replace the Next 25% Test etc, you know the drill.
And hopefully isolate the Packages from SYS that have related Files to Bluetooth.
Luckily there's already enough SYS packages you can rule out like enterprise, entertainment, Office and such.
I know it's not a cut and dried answer, but hopefully i can "Je een hart onder de riem steken" that your up against this alone ATM.
But consider this, how many time do you have at hand, and is it worth it putting a lot of time into it, only finding out MS fixes it in a few "Leaked" Beta Builds.
Who knows maybe this Bump does get a few others on to this thread that has already tackled this problem.
(Da_G is the most likely, that i know that might know other Bluetooth dependencies inside the SYS)
Cheerz,
PS: don't forget to enjoy the snow a bit.

Pairing with Avic f900BT
I too have the exact same problems. The phone is straight out of the box.
Any easy ansewrs as yer?

Magic3091 said:
I too have the exact same problems. The phone is straight out of the box.
Any easy ansewrs as yer?
Click to expand...
Click to collapse
I got it working on mine using the attached cab