I also noticed 2.1 based ROMs had problems with my car BT. Phone is paired successfully but no audio during a call. I make most of my calls in the car so this is a huge problem. Even to the point I may have to stay with 1.5 ROM.

If anyone has a solution. Please advise!

UPDATE: FYI, I pair my phone to 2007 Infiniti G35. 1.5 works, 2.1 no audio. I've notified HTC about the issue. If someone can issue a custom ROM that "downgrades" the BT similar to 1.5, that would be perfect.

 

Well, I just updated to 2.1 and everything is fine. I connected to my bluetooth headset anad my computer. I also sent and recieved a couple of photos and videos.
So, may be there is something wrong with your update or your device.

 

Pioneer F700bt. Prior to the update, any contacts that had multiple phone numbers just had a separate button, with no indication of what phone number it was related to. Post update, all contacts show mobile, home, work, so on and so forth.

Streaming Pandora to my FIPO blue tooth receiver worked almost flawlessly. Now it cuts out and skips and stops. Not sure if it's the Pandora or the bluetooth causing the issue.

That's all I've got to say about that...

 

May be you have to reset the bluetoothdevices first. I don't know, but mine works perfectly after the official update today...

 

Well, 2005 Toyota Prius Navigation system bluetooth functions handsfree with the 2.1 Hero like it did on 1.5, but contact file transfer is still not working. Now with 2.1, I can send the contact from the Hero, but the Prius system just receives the name with ||||||||| as the phone number. I was hoping the update would allow me to transfer contacts, but it still broken. I even tried the Bluetooth File Transfer program, but it locks up and gets hung on 'searching'. I have to kill the app to stop it. I would think in this day and age that manufactures would have Bluetooth all figured out and compatible, but NOT!

 

I have an Eclipse 726e, it used to work fine with my Hero, except for the address book, and I figure that is an Eclipse problem. Now It pairs and after a couple of tries connects, I can even make a phone call but no audio through the stereo but after the call connects having been dialed from the stereo I can hear it through the phone, this is a Hero issue for sure as it used to work quite well.

 

Reported in official 2.1 Problems thread.

 

Running Fresh 2.0d

I have a Dodge Magnum with the Johnson Controls uConnect system for the car ( BT hands free head set )

The Phone BT and my uConnect have been fighting a bit from day 1.

It pairs, finds the hands free device, I can make a call, but after that first call it looses connection and wouldn't rediscover the hands free unless I disabled BT and re enabled it.


With the 2.1 it will drop out in the middle of a call, or say it found a hands free device and then run the call through the phone.

It has to be the BT stack in the phone, my Katana never had any issues with the uConnect, and I have had repeted issues with the BT and my Netbook and Laptop.

-Robert

 

I have a Pioneer DEH-P7900BT and I am having EXACTLY the same problems that started this thread. It has spurred me to do further research as to the cause and here is what I have so far. Please keep in mind that I am not a developer and this is my first post. I work in outside sales and use the Bluetooth Phone function CONSTANTLY! So here is what I have. If someone can pick up the torch and run from here by all means please do so

Here are the protocols supported in the Android/Bluetooth 2.1 update for the HERO: GAP, SPP, HSP, HFP, A2DP, AVRCP. It was also stated the it lacks OBEX Remote Sim Access (although I have no idea what that means)

Here are the protocols supported in my Pioneer: GAP, SDP, OPP, HFP, A2DP, AVRCP

Here are the protocols in the Pioneer that ARE NOT supported by the Android/Bluetooth 2.1 update: SDP, OPP.
The Pioneer Manual states that it uses A2DP and AVRCP for streaming audio.

So my summary is that the lack of OBEX, SDP, and OPP support is the issue. The lack of at least one or all of them is affecting our earlier model head units. Which leads to 3 conclusions:

1) Downgrade the Firmware or change to a new smartphone altogether. Which I would rather not do because I like the phone but this is really a deal breaker for me.

2) Purchase a new head unit and make sure it supports the phone by syncing before buying. Imagine if you didnt buy a certain new car model because it didnt support your smartphone?

3) Hope that a company (Bluetooth?, HTC?, Android?, Sprint?) can impliment a fix through an update.

I am hoping for #3 through either pleading or public outcry. Can you imagine what the Evo Lanuch will be like if they have the same 2.1 Firmware out of the box?

Any further advice would be greatly appreciated.
Hope it helps......

 

I have the exact same problem in my Lexus. 1.5 worked, 2.1 doesn't. I am finally getting frustrated with the software testing that they are doing when the roll these updates out. Or lack of testing.

 

On 1.5 everything worked great on my Pioneer DEH P700BT

On Fresh 2.0d, 2.1.1 and DamageControl 2.08 and 2.08.1 I have issues getting it to connect and disconnect properly.

When I take calls, people can't usually hear me, but then I go on the phone and hit the button to activate headset and it starts working.

 

Well now the trick would be could a code monkey pull the BT code from 1.5 and compare it to the code 2.1 and see whats borked ? or maybe make a hack to put the older working variant into a 2.1 rom?

R

 

What you are describing sounds exactly the same as I get with the legend, which also runs 2.1, on my car kit. Bizarrely though, the Desire seems to be fine...

I'd suggest logging it with HTC, as the more people who log issues, the more likely it is to get looked at.

Sent from my HTC Legend using Tapatalk

 

Same problem here with a Pioneer Avic-D3 with BTB200 bluetooth adapter. Tries to connect, pairs up and disconnects right away

worked fine in 1.5 =(

streaming audio works fine though

 

No problems for me! Running Fresh 2.1.1 and have a Sony MEX-BT2800 receiver. Pairs to the phone in about 10-15 seconds. Works every time without any issues. Pandora in the car rocks!

 

Thanks much Astro. Also thanks for clearing up some of the jargon misnomers I butchered. After reading posts on HTC and hearing about the 2.2 update on the way from the Google I/O conference I ponder if the next update will finally put this to bed? Which should get down to us in an update in about one to three years?

 

lol 3 years, time for a new phone!


It bothers me that all these smartphones have these issues functioning as a PHONE. My damn sanyo 8400 had no problems with bluetooth with any devices. bleh.

It's either I go back to 1.5 and lose a working youtube app, or stick with 2.1 and not be able to use handsfree -_-

 

I'm using the Hero with uConnect as well. Mine is on an RER MyGig/Navigation unit. I never had issues with 1.5.

However, when I went to Fresh 2.0d, the only issue I faced was that the phonebook transfer would only work for one number, usually home. I no longer had the option to say "Call Sally Mobile" as it would not see the mobile number for Sally. With 1.5 it worked fine, I could say "Call Sally Mobile" or "Call Sally Home" and it worked.

On Fresh Toast 2.1 I had huge issues to where during a call after they hung up it destroyed my OS and I had to restore to 2.0d.

I'm now using Fresh 2.1.1 and it's been working OK, but I haven't confirmed the phonebook transfer issues.