[Q] Bluetooth Problem since 2.3.3 - Desire HD Q&A, Help & Troubleshooting

Hello,
3 weeks before i get the update from provider from Froyo 2.2.1 up to 2.3.3
Since that, my stereo Headset Scale Rider Q2 Pro as all 2.30 min a break by playing music. Telephon works. I tried 4 diffrent players, Factory reset, pairing reset on both sides and complete new software in a shop, but nothing help.
Do someone know about these problem and as a workaround without flashing down or upgrade (then i lost garantie)?
Please help - i am full desperate!!!!!!

i have olmost a similar problem. i had to send back my phone for not functioning like it has to(left with the 2.2.1 software update). and returned with 2.3.3, not what i asked for but ok. then i discoverd the bleutooth function named ''scan for devices'' in the wireless connection section cant find my phillips SH9100 headphones(wireless bleutooth headphones)...
so what the **** now?(cencored myself)
my phone?: Xperia x10i
latest update, 2.3.3 .(my personal most unwanted update)
since i had to wait 3 weeks, and had to listen to other people, while no music around me?:O help me and this guy above me please!

Related

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

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

[Q] Blutooth calling and ICS updates

Hey guys, so I bought my galaxy nexus from a guy who bought it from his own carrier(bell) and i'm using it with another carrier(rogers). For some reason, my ics is stuck at 4.0.1 and I guess I can't update untill I root the phone? Why is that?
Is there anyway to get the updates if I don't root?
Also, when I use the bluetooth in my car, the music plays through the speakers of the car, but phone calls don't and I have to hear them through the phone speakers. I can get phone calls through my car speakers with an Iphone, but not the galaxy nexus. Anyone knows a solution?
I'm not 100% on your first question but for the bluetooth, make sure under your device in the BT settings it is paired as a media device AND a headset or handsfree kit. My guess is that it is only paired for media.
Sent from my Galaxy Nexus using Tapatalk
RTContent said:
I'm not 100% on your first question but for the bluetooth, make sure under your device in the BT settings it is paired as a media device AND a headset or handsfree kit. My guess is that it is only paired for media.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
My car has a single bluetooth device and under the bluetooth settings on my galaxy nexus I only have an option to pair with that device. I can't see the option of connecting as a media device or anything else. Anyone else is having an issue like this?? With an Iphone I connect to the same bluetooth device of the car and it connects everything, like music, calls, games sounds. However the galaxy nexus connects every sound in the phone to the speakers except the calls.
*#*#CHECKIN#*#*
input that into your dialer, treat it like a phone number, no need to press the call button. This forces your phone to check for updates, maybe it will help.
Other than waiting for the update to push to your phone there is not much you can do to manually update your phone without unlocking the bootloader and rooting. But you bought a Nexus branded phone for a reason right?
If you decided to open the hacking doors: Go over to the toolkit thread and read up. unlock the bootloader (this will erase EVERYTHING, including photos/media etc so back up), flash the stock Google image of 4.0.4 (http://code.google.com/android/nexus/images.html), root, do not flash CWM (that will ensure you can receive and install OTAs in the future).
Shahinbayat.90 said:
Hey guys, so I bought my galaxy nexus from a guy who bought it from his own carrier(bell) and i'm using it with another carrier(rogers). For some reason, my ics is stuck at 4.0.1 and I guess I can't update untill I root the phone? Why is that?
Is there anyway to get the updates if I don't root?
Click to expand...
Click to collapse
You have a non-"yakju" version of ICS (aka "yakju**" or "yakjuxx").
This means that your updates are handled by Samsung instead of Google because the carrier that sold the phone had some small, regional tweaks such as radios on it.
You will get updates slightly slower than yakju devices because of this. You don't have to root to update. If you want to switch to yakju and be on that update path, it is completely possible without rooting. You will need to unlock your bootloader and use Fastboot to flash the images from Google. You will remain stock but it will 100% wipe your device (of course). You will not be rooted. You will continue to receive OTAs.
There are literally dozens of guides and threads on this already. Just search it a bit and you'll find more than enough info on this.
Hi guys, thanks for the replies. So I guess I'll change to the yakju version.
But I still haven't figured out what to do with the bluetooth calling. This is really irritating since I use my phone to make lots of calls while driving and I can't do that now after switching to this phone. Anyone has had the same problem as me on this or have figured out a way to make calls with bluetooh? Even games have a sound on the speakers while connected to bluetooh!! as soon as I get a call or make a call I have to start listening via the speakers of the phone

[Q] Bluetooth voice dial on a HTC Desire Bravo with a Blueant S4

My wife has an Hong Kong sourced unbranded HTC Desire with 2.2.1, unrooted and we are trying to get it to communicate with Blueant s4. The phone did not come with VoiceDialer.apk.
I have searched quite a bit and found various suggestions such as using Vlingo, Choice Dialer and installing VoiceDialer.apk. Non of them really work properly.
Not being game to hack my wife's phone without a reasonable prospect of success, I have rooted my Wildfire (which has the same OS) and tried most suggestions I have come across with no success. (the only one I have not done is place VoiceDialer.apk in the system\app folder - keep getting a fail message)
Anyone got this working well?
Is the best solution to go to Gingerbread? Read something about the bluetooth stack not being complete in Froyo.
What about effective voice recognition? None of the above recognise my London British accent with a 25 year Aussie veneer. As this is really for my wife, recognition of a 'strine (Australian) accent is essential.
Welome your suggestions and advice
Bazzan

[Q] CM 10.1.3 RC1 Galay Note 2 N7100 Bluetooth Issues

Dear All,
This is the first time I am participating on such a technical forum. Please forgive me if I am a little lengthy in details. I own a Galaxy Note 2 N7100 in India. Mine is not a carrier locked unit as there is no such practice in India. I recently installed CM 10.1.3. RC1 on my phone. The installation was perfect and after installation the phone seemed to be working perfectly. I installed a large number of apps that I regularly use and there was no problem. However, later on when I tried to connect my phone with my Fiat Linea Blue & Me system via Bluetooth then it got connected with great difficulty but the phone and contacts app crashed. Thereafter if I dialled a number from my phone I could neither hear the ring going through to the other number nor the voice of the person on the other side even after the phone was connected. However, the person on the other side was able to hear my voice perfectly. I disconnected the bluetooth but the problem was not solved. I did a factory reset and without installing any apps again connected my phone to Jabra BT & Fiat Blue & Me. this time everything worked flawlessly. However, after having installed all my apps, the problem resurfaced. Finally i was compelled to unroot my stock rom and everything is back to normal. All the apps are still installed and everything works fine.
Someone please guide as to what might be the problem. I have nearly 70 apps on my phone. Can anyone please help me?
I've got the same problem. I use the final version 10.1.3. When I want to turn on Bluetooth, it instantly turns off. I've got no idea what this is. Maybe the next release helps.
Sorry for bad English.
KitCrafty

Categories

Resources