Go Back   Android Forums > Android Phones > HTC Hero (Sprint)

Get excited for the Samsung Galaxy S5! Find everything you need and discuss it in our Galaxy S5 Forum!

test: Reply
 
LinkBack Thread Tools
Old May 19th, 2010, 09:36 PM   #1 (permalink)
Member
Thread Author (OP)
 
astrobill's Avatar
 
Join Date: Dec 2009
Posts: 219
 
Device(s):
Carrier: Not Provided

Thanks: 7
Thanked 24 Times in 14 Posts
Default Bluetooth 2.1 the Good/Bad News

Good News/Bad News with regard to the new Bluetooth 2.1 in Android 2.1 on the Hero...

Good News:

I tested phone contact transfer and receive between my Hero and my other phone, an LG Rumor. Worked fine.

Bad News:

Still can't get FILES to transfer, but I'm working on it.

Worse news....

- My Hero no longer connects to the Bluetooth head unit in my car for telephone functions (still connects to audio streaming using AVCRP just fine)! The details are....

....It worked fine before the 2.1 update, but now the head unit now connects to the Hero for a second, then disconnects and reports that the phone is an "Invalid Device". I've noticed the head unit also seems to have trouble remembering the Bluetooth device name being reported by the Hero. Gets it right at first, then immediately says it can't determine the device name. Oddly, the Bluetooth audio streaming profile (AVCRP, etc.) still works and connects fine.

UPDATE:

The Bluetooth connectivity with the Hero under the 2.1 update is HIGHLY dependent on the car kit or Bluetooth device. For example, I was able to maintain a stable connection with a more modern Pioneer head unit in Best Buy, and it even saw the Hero's phone book automatically using the PBAP profile. However, I could not connect at all with an older Pioneer AVIC series unit. I had only partial success with other units, such as a Kenwood 6160 and some Garmin Nuvi's. On others, such as a Tom Tom with Bluetooth, I was unable to connect at all....

astrobill is offline  
Last edited by astrobill; May 22nd, 2010 at 03:44 PM.
Reply With Quote
sponsored links
Old May 19th, 2010, 11:09 PM   #2 (permalink)
Junior Member
 
Join Date: Nov 2009
Posts: 16
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

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.
yaeger is offline  
Last edited by yaeger; May 22nd, 2010 at 11:07 PM.
Reply With Quote
Old May 19th, 2010, 11:11 PM   #3 (permalink)
Junior Member
 
Join Date: Jan 2010
Posts: 30
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 5 Times in 3 Posts
Default

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.
ahmadshawki is offline  
Reply With Quote
Old May 19th, 2010, 11:21 PM   #4 (permalink)
Member
Thread Author (OP)
 
astrobill's Avatar
 
Join Date: Dec 2009
Posts: 219
 
Device(s):
Carrier: Not Provided

Thanks: 7
Thanked 24 Times in 14 Posts
Default

Quote:
Originally Posted by ahmadshawki View Post
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.
No, it's a clean, official update and my Hero connected to my car kit FINE with Android 1.5. There's nothing wrong with the car kit...
astrobill is offline  
Reply With Quote
Old May 19th, 2010, 11:56 PM   #5 (permalink)
Junior Member
 
americonium's Avatar
 
Join Date: Sep 2009
Location: Massapequa Park
Posts: 94
 
Device(s): HTC EVO Stock for now... NC now with 2.2 sd goodness
Carrier: Not Provided

Thanks: 15
Thanked 4 Times in 4 Posts
Default

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...
__________________
Good-bye my Hero, Hello EVO!

My nook has 2 personalities. By day, it's a simple book reader. By night, it's an Android powered PARTY ANIMAL!!!
americonium is offline  
Reply With Quote
Old May 20th, 2010, 12:34 AM   #6 (permalink)
Member
Thread Author (OP)
 
astrobill's Avatar
 
Join Date: Dec 2009
Posts: 219
 
Device(s):
Carrier: Not Provided

Thanks: 7
Thanked 24 Times in 14 Posts
Default

Okay guys, here are some more details....

My Hero's Bluetooth is "pairing" with the Bluetooth car kit (i.e., listing it as a remembered device and reading the car kit's Bluetooth name properly).

However, it's when I try to go to the next step...and CONNECT to the car kit ...that things go awry. What's happening is that nine times out of ten, the car kit cannot "read" (i.e., decode) the device name being reported by the Hero in the Bluetooth data stream, so the car kit declares the Hero to be called "Name Not Found" and refuses to connect, saying "Invalid Device."

About one time in ten, the car kit IS able to decode my Hero's name ("Bill's Hero") and connect for two seconds. Then the Hero immediately states "Bluetooth Headset Disconnected" on the touch screen just a fraction of a second before the car kit goes back to saying "No Connection." I can't tell if it's the Hero or the car kit that drops the connection first. But then again, I only get that far about 1 out of every ten tries, so it may be moot.

Either my older car Bluetooth unit or HTC made an error in their Bluetooth stack when complying with the standard...not sure which. Darn...the only reason I kept the Hero was in the hopes this Bluetooth update would FINALLY allow me to "push" contacts to my car kit and use the phone book on the touch screen. Instead, I took a step backward and can't even connect at all...sigh.
astrobill is offline  
Last edited by astrobill; May 20th, 2010 at 12:40 AM.
Reply With Quote
Old May 20th, 2010, 12:37 AM   #7 (permalink)
Junior Member
 
Join Date: Jan 2010
Posts: 30
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 5 Times in 3 Posts
Default

May be you have to reset the bluetoothdevices first. I don't know, but mine works perfectly after the official update today...
ahmadshawki is offline  
Reply With Quote
Old May 20th, 2010, 12:55 AM   #8 (permalink)
Member
Thread Author (OP)
 
astrobill's Avatar
 
Join Date: Dec 2009
Posts: 219
 
Device(s):
Carrier: Not Provided

Thanks: 7
Thanked 24 Times in 14 Posts
Default

Quote:
Originally Posted by ahmadshawki View Post
May be you have to reset the bluetoothdevices first. I don't know, but mine works perfectly after the official update today...
Nah...that's not it. I did a number of restarts of the Bluetooth kit, and even took apart my dash and do a HARD refresh of the hidden Buetooth unit. It's not an issue with "resetting" the Bluetooth car kit.

Besides, the Bluetooth streaming audio piece of the same car kit works fine with the Hero using the AVCRP profile.

There can be no doubt...either the car kit and/or the Hero are not complying fully with the Bluetooth Hands-Free and/or Headset Profile (HFP, etc) communciations "stack" standards and protocols. Dammit. I'm going to have to junk one or the other...or simply give up on using the Hero in my car

Please note that the "free" LG Rumor that Sprint gave me when I bought the Hero works PERFECTLY with the car kit!!! Ironic, no?
astrobill is offline  
Last edited by astrobill; May 20th, 2010 at 01:04 AM.
Reply With Quote
Old May 20th, 2010, 01:17 AM   #9 (permalink)
Member
 
DaWeav's Avatar
 
Join Date: Nov 2009
Location: Lemoore, CA
Posts: 343
 
Device(s): Before: Sprint HTC Hero, Sprint HTC Evo Shift Now: Ting Samsung Galaxy S3
Carrier: Ting.com

Thanks: 2
Thanked 52 Times in 41 Posts
Default

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!
DaWeav is offline  
Reply With Quote
Old May 20th, 2010, 06:30 AM   #10 (permalink)
Junior Member
 
Join Date: Jan 2010
Posts: 42
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Default

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.
lil goat is offline  
Reply With Quote
sponsored links
Old May 20th, 2010, 09:35 AM   #11 (permalink)
Member
Thread Author (OP)
 
astrobill's Avatar
 
Join Date: Dec 2009
Posts: 219
 
Device(s):
Carrier: Not Provided

Thanks: 7
Thanked 24 Times in 14 Posts
Default

Quote:
Originally Posted by DaWeav View Post
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!
Yeah...this is broken. My LG Rumor paired with the 2.1 Hero okay, and the Hero is definitely telling the LG Rumor that the Hero supports the Object Push Profile (OPP) in Bluetooth....I was able to send contacts back and forth between the Rumor and the Hero, but I CANNOT get the Hero to maintain a connection with the car kit. Nine times out of ten it fails completely....and the one time in ten that it DOES connect, it disconnects immediately.
astrobill is offline  
Reply With Quote
Old May 20th, 2010, 09:35 AM   #12 (permalink)
Member
 
nick325i's Avatar
 
Join Date: Nov 2009
Posts: 491
 
Device(s): HTC Evo 4G
Carrier: Not Provided

Thanks: 16
Thanked 197 Times in 41 Posts
Default Official 2.1 Problems, Issues and Quirks

Reported in official 2.1 Problems thread.
__________________
EVO - ToastRoot - OCWidget for battery

Please click the Thanks to the right if I was helpful

Click here for this forums rules, guidelines and zero tolerance policy
nick325i is offline  
Last edited by nick325i; May 20th, 2010 at 09:43 AM.
Reply With Quote
The Following User Says Thank You to nick325i For This Useful Post:
astrobill (May 20th, 2010)
Old May 20th, 2010, 10:26 AM   #13 (permalink)
Member
 
RobAGD's Avatar
 
Join Date: Jan 2010
Posts: 143
 
Device(s): HTC Evo 4G - Sprint Rooted Stock Rom HTC Hero - Sprint Rooted w/ Fresh 2.1.1
Carrier: Not Provided

Thanks: 16
Thanked 5 Times in 4 Posts
Default

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
RobAGD is offline  
Reply With Quote
The Following 2 Users Say Thank You to RobAGD For This Useful Post:
astrobill (May 20th, 2010), johnnaryry (June 4th, 2010)
Old May 20th, 2010, 12:14 PM   #14 (permalink)
New Member
 
Join Date: May 2010
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default Same Bluetooth Issue

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......
stephned1003 is offline  
Reply With Quote
Old May 20th, 2010, 01:34 PM   #15 (permalink)
Junior Member
 
Join Date: May 2010
Posts: 17
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

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.
ls430cw is offline  
Reply With Quote
Old May 20th, 2010, 01:39 PM   #16 (permalink)
Junior Member
 
Join Date: Feb 2010
Posts: 15
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

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.
JRally is offline  
Reply With Quote
Old May 20th, 2010, 08:36 PM   #17 (permalink)
Member
Thread Author (OP)
 
astrobill's Avatar
 
Join Date: Dec 2009
Posts: 219
 
Device(s):
Carrier: Not Provided

Thanks: 7
Thanked 24 Times in 14 Posts
Default

Quote:
Originally Posted by stephned1003 View Post
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......
Stephen....

First a quick aside: OBEX stands for Object Exchange...it's actually not a Bluetooth PROFILE. Rather, it's a Bluetooth PROTOCOL one could use in developing NEW profiles.

Now...regarding what may be the issue here....

The OPP (Object Push Profile) is what's used to send/receive files and contacts. However, it is NOT what is used for simple connections and telephony between Bluetooth devices. Therefore, errors in programming the OPP "Bluetooth Stack" would NOT be responsible for the problems we're having connecting the new 2.1'ed Hero to Pioneer head units. I'm not saying HTC has implemented OPP correctly, but rather that it's not responsible for the simple connectivity problems. In fact, I successfully transfered contacts between my Hero and my LG Rumor, so I suspect they got OPP mostly correct.

So...what is MORE LIKELY the issue here? Well...

I believe HTC and Sprint must have changed something in how they implement the Headset Profile (HSP) within Android which is what many Pioneer head units use to connect to Bluetooth phones, for example. 2.1 has broken something in the basic Bluetooth HSP (and maybe the HFP as well?).

In contrast to the newly-upgraded Hero, my LG Rumor connects to my car kit just fine and even sends the numbers of incoming callers to my car kit, and the car kit even tells me the caller's name if they're in the car's phone book. Also. my five year old Motorola RAZR connects to the car kit just fine using the Headset and Hands-Free Profiles.

I'm pretty convinced that HTC just really broke the Hero's Bluetooth HSP and HFP profiles big time....too many other people are also reporting problems after the 2.1 upgrade!
astrobill is offline  
Last edited by astrobill; May 20th, 2010 at 10:46 PM.
Reply With Quote
The Following User Says Thank You to astrobill For This Useful Post:
johnnaryry (June 4th, 2010)
Old May 21st, 2010, 01:36 AM   #18 (permalink)
Member
 
RobAGD's Avatar
 
Join Date: Jan 2010
Posts: 143
 
Device(s): HTC Evo 4G - Sprint Rooted Stock Rom HTC Hero - Sprint Rooted w/ Fresh 2.1.1
Carrier: Not Provided

Thanks: 16
Thanked 5 Times in 4 Posts
Default

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
RobAGD is offline  
Reply With Quote
Old May 21st, 2010, 01:42 AM   #19 (permalink)
Member
 
Join Date: Apr 2010
Location: UK
Posts: 102
 
Device(s): Nexus S, Nexus 4
Carrier: Not Provided

Thanks: 0
Thanked 6 Times in 6 Posts
Default Re: Bluetooth 2.1 the Good/Bad News

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
Bootsock is offline  
Reply With Quote
Old May 21st, 2010, 04:35 AM   #20 (permalink)
New Member
 
Join Date: Nov 2009
Posts: 5
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

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
ConanOBrien is offline  
Reply With Quote
sponsored links
Old May 21st, 2010, 07:57 AM   #21 (permalink)
Member
Thread Author (OP)
 
astrobill's Avatar
 
Join Date: Dec 2009
Posts: 219
 
Device(s):
Carrier: Not Provided

Thanks: 7
Thanked 24 Times in 14 Posts
Default

Quote:
Originally Posted by ConanOBrien View Post
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
Conan...yep. Even though the guys over at AVIC411.COM will tell you that Pioneer did a REALLY crappy job on the BTB200 (I mean...REALLY bad...many Bluetooth stack errors), the one thing they DID get right was the Bluetooth HSP profile. Therefore, I'm pretty sure your issue is due to mistakes on the HTC end with the 2.1 update....
astrobill is offline  
Reply With Quote
Old May 21st, 2010, 08:49 AM   #22 (permalink)
Member
 
Join Date: Nov 2009
Posts: 111
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 6 Times in 4 Posts
Default

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!
sarspants is offline  
Reply With Quote
Old May 21st, 2010, 09:09 AM   #23 (permalink)
New Member
 
Join Date: May 2010
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default Thanks Astro

Quote:
Originally Posted by astrobill View Post
Stephen....

First a quick aside: OBEX stands for Object Exchange...it's actually not a Bluetooth PROFILE. Rather, it's a Bluetooth PROTOCOL one could use in developing NEW profiles.

Now...regarding what may be the issue here....

The OPP (Object Push Profile) is what's used to send/receive files and contacts. However, it is NOT what is used for simple connections and telephony between Bluetooth devices. Therefore, errors in programming the OPP "Bluetooth Stack" would NOT be responsible for the problems we're having connecting the new 2.1'ed Hero to Pioneer head units. I'm not saying HTC has implemented OPP correctly, but rather that it's not responsible for the simple connectivity problems. In fact, I successfully transfered contacts between my Hero and my LG Rumor, so I suspect they got OPP mostly correct.

So...what is MORE LIKELY the issue here? Well...

I believe HTC and Sprint must have changed something in how they implement the Headset Profile (HSP) within Android which is what many Pioneer head units use to connect to Bluetooth phones, for example. 2.1 has broken something in the basic Bluetooth HSP (and maybe the HFP as well?).

In contrast to the newly-upgraded Hero, my LG Rumor connects to my car kit just fine and even sends the numbers of incoming callers to my car kit, and the car kit even tells me the caller's name if they're in the car's phone book. Also. my five year old Motorola RAZR connects to the car kit just fine using the Headset and Hands-Free Profiles.

I'm pretty convinced that HTC just really broke the Hero's Bluetooth HSP and HFP profiles big time....too many other people are also reporting problems after the 2.1 upgrade!

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?
stephned1003 is offline  
Reply With Quote
Old May 21st, 2010, 05:15 PM   #24 (permalink)
New Member
 
Join Date: Nov 2009
Posts: 5
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by stephned1003 View Post
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 -_-
ConanOBrien is offline  
Reply With Quote
Old May 21st, 2010, 05:51 PM   #25 (permalink)
Junior Member
 
Join Date: Dec 2009
Location: Los Angeles
Posts: 77
 
Device(s): HTC Evo 4G
Carrier: Not Provided

Thanks: 0
Thanked 4 Times in 4 Posts
Default

Quote:
Originally Posted by RobAGD View Post
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'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.
armandov99 is offline  
Reply With Quote
Old May 21st, 2010, 06:43 PM   #26 (permalink)
Member
 
Join Date: Apr 2010
Posts: 150
 
Device(s):
Carrier: Not Provided

Thanks: 10
Thanked 7 Times in 7 Posts
Default

What do you do to send the contacts to your car system? I've never had a problem with connecting and staying connected with my Kenwood DNX 7600(I think that's the correct number) with 1.5 or 2.1. But I don't know how you send contacts. Can someone tell me please?
Linx is offline  
Reply With Quote
Old May 21st, 2010, 06:47 PM   #27 (permalink)
Junior Member
 
Join Date: Dec 2009
Location: Los Angeles
Posts: 77
 
Device(s): HTC Evo 4G
Carrier: Not Provided

Thanks: 0
Thanked 4 Times in 4 Posts
Default

Quote:
Originally Posted by Linx View Post
What do you do to send the contacts to your car system? I've never had a problem with connecting and staying connected with my Kenwood DNX 7600(I think that's the correct number) with 1.5 or 2.1. But I don't know how you send contacts. Can someone tell me please?
It depends on the headunit/system you're using. Yours may not support phonebook transfer. Maybe check in the manual?

On mine, it's automatic. When I start the car, the phone connects, and every time it downloads the phonebook. I kind of wish it wouldn't do that, as it's not usable for the first minute or so, but then again at least this way it's always current.
armandov99 is offline  
Reply With Quote
Old May 21st, 2010, 07:37 PM   #28 (permalink)
Member
Thread Author (OP)
 
astrobill's Avatar
 
Join Date: Dec 2009
Posts: 219
 
Device(s):
Carrier: Not Provided

Thanks: 7
Thanked 24 Times in 14 Posts
Default

Quote:
Originally Posted by armandov99 View Post
It depends on the headunit/system you're using. Yours may not support phonebook transfer. Maybe check in the manual?

On mine, it's automatic. When I start the car, the phone connects, and every time it downloads the phonebook. I kind of wish it wouldn't do that, as it's not usable for the first minute or so, but then again at least this way it's always current.
Sounds like your car unit supports the Bluetooth Phone Book Access Profile (PBAP). PBAP is the profile that allows a car kit or other Bluetooth device to automatically connect to the contact list with any other Bluetooth device it connects with (in this case, your Hero) that also supports PBAP. This is sometimes known as the car kit "pulling" the contacts from the phone.

If one's car kit DOESN'T support pulling contacts automatically using PBAP (e.g., like the Kenwood guy above), you can still transfer contacts using the Object Push Profile (OPP)....this is also known as "pushing" or sending the contacts...

...To do this, just open "People" on the Hero, long-press any contact, and choose "Send as vCard" ....make sure you're connected to your car kit before doing this. Remember that on some car kits, before you transfer the contact using the "push" method, you have to prepare the car kit to receive contacts. Specifics should be in the manual for your car kit.

Not sure yet how to transfer MULTIPLE contacts from the Hero now that it supports OPP. I suspect the method is to...

- open your "People" and then hit Menu.

- Then choose "Export to SD Card"

- choose either Google or Phone contacts. This appears to save the entire phone book as a Virtual Card File (VCF) on the SD card

- Transfer the VCF file to your car kit using a file manager on the Hero (e.g., ASTRO) or some other method....
astrobill is offline  
Reply With Quote
Old May 22nd, 2010, 09:05 AM   #29 (permalink)
Member
 
DaWeav's Avatar
 
Join Date: Nov 2009
Location: Lemoore, CA
Posts: 343
 
Device(s): Before: Sprint HTC Hero, Sprint HTC Evo Shift Now: Ting Samsung Galaxy S3
Carrier: Ting.com

Thanks: 2
Thanked 52 Times in 41 Posts
Default

And yet again other issues with Bluetooth. I have a Samsung A2DP stereo headset. On Hero 1.5, the audio stream from the Hero to this headset would cut out occasionally. BUT NOW on Hero 2.1, the audio stream from the Hero to this headset cuts out every few seconds. YUK!

I wonder if this is the native Google Android's crappy Bluetooth enhanced code they put in Android 1.6 and above.

Anyway, OBEX, OPP, dot-dot-dot, I would believe in this day and age that all the Bluetooth profiles and protocols would be included in a 'SMART PHONE'!
DaWeav is offline  
Reply With Quote
Old May 22nd, 2010, 01:00 PM   #30 (permalink)
Member
Thread Author (OP)
 
astrobill's Avatar
 
Join Date: Dec 2009
Posts: 219
 
Device(s):
Carrier: Not Provided

Thanks: 7
Thanked 24 Times in 14 Posts
Default

Quote:
Originally Posted by DaWeav View Post
Anyway, OBEX, OPP, dot-dot-dot, I would believe in this day and age that all the Bluetooth profiles and protocols would be included in a 'SMART PHONE'!
Dude, you're right, OPP should've been included way back in 1.5 for the Hero....but that's not really the issue at the moment. It's in there now...

The issue now is that HTC has apparently broken the HSP and HFP profiles or mis-coded them...people are now having a lot of trouble connecting to older, legacy Bluetooth car kits and other devices that connected just fine before using the HFP and/or HSP profiles. They need to re-code the stack properly.
astrobill is offline  
Reply With Quote
sponsored links
Old May 22nd, 2010, 02:16 PM   #31 (permalink)
Member
 
AmericanHero's Avatar
 
Join Date: Nov 2009
Posts: 179
 
Device(s): Sprint Galaxy S4
Carrier: Not Provided

Thanks: 25
Thanked 16 Times in 11 Posts
Default

Bluetooth file transfer is working for me. I did have to update my Bluetooth stack on my PC notebook (Toshiba) to the latest drivers. After that files transfer fast and without problems. I don't use it for audio except for my ear plug which is a BlueAnt. It works fine. Still very primitive implementation compared to other flip phones I have had in the past several years.
AmericanHero is offline  
Reply With Quote
Old May 22nd, 2010, 03:38 PM   #32 (permalink)
Member
Thread Author (OP)
 
astrobill's Avatar
 
Join Date: Dec 2009
Posts: 219
 
Device(s):
Carrier: Not Provided

Thanks: 7
Thanked 24 Times in 14 Posts
Default

UPDATE:

The Bluetooth connectivity with the Hero under the 2.1 update is HIGHLY dependent on the car kit or Bluetooth device. For example, I was able to maintain a stable connection with a more modern Pioneer head unit in Best Buy, and it even saw the Hero's phone book automatically using the PBAP profile. However, I could not connect at all with an older Pioneer AVIC series unit. I had only partial success with other units, such as a Kenwood 6160. On others, such as Garmin Nuvi's and a Tom Tom with Bluetooth, I was unable to connect at all....
astrobill is offline  
Last edited by astrobill; May 22nd, 2010 at 08:28 PM.
Reply With Quote
Old May 22nd, 2010, 05:47 PM   #33 (permalink)
Member
 
DaWeav's Avatar
 
Join Date: Nov 2009
Location: Lemoore, CA
Posts: 343
 
Device(s): Before: Sprint HTC Hero, Sprint HTC Evo Shift Now: Ting Samsung Galaxy S3
Carrier: Ting.com

Thanks: 2
Thanked 52 Times in 41 Posts
Default

UPDATE:

Well, I finally found the trick to the 2.1 Sprint HTC Hero and the 2005 Prius. I had to have the contact's phone number properly formated to transfer it. I had them formated like (xxx) xxx-xxxx, but when I changed the phone number format to just xxxxxxxxxx the Prius displayed the number for the contact. I could only send one number per contact at a time, but it's something.
DaWeav is offline  
Reply With Quote
Old May 23rd, 2010, 05:15 AM   #34 (permalink)
New Member
 
Join Date: May 2010
Posts: 1
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

Still dont work, even before the 2.1 update!
nnvi is offline  
Reply With Quote
Old May 23rd, 2010, 07:53 AM   #35 (permalink)
Member
 
K4KAI's Avatar
 
Join Date: Apr 2010
Location: Northern Virginia
Posts: 128
 
Device(s): DROID RAZR MAXX
Carrier: Verizon

Thanks: 77
Thanked 11 Times in 8 Posts
Default

I downloaded the update from the Sprint website and installed it on my Hero. I then proceeded to configure it for my Garmin Nuvi760 where, after checking the Hero's "Trust this connection" query, it worked great.

Then on our new 2011 Toyota Sienna, I configured it on the Toyota Navigation System's Phone Connection, and it worked fine there, but I was not successful in downloading contacts, so I entered them manually, which only took a few minutes.

I wonder if there may be a difference in the Sprint Hero Android 2.1 LEAK and the 2.1 Official Sprint release? I say this because I initially loaded the "LEAKed" version which ran fine, but found it to be better once I downloaded the Official Sprint version. The Official version recognized more of my pre-upgrade downloads in the MARKET DOWNLOAD page, and seems overall to be more responsive.
__________________
Sam....
U.S. Navy (Retired)
K4KAI is offline  
Reply With Quote
Old May 23rd, 2010, 04:17 PM   #36 (permalink)
Junior Member
 
Join Date: Oct 2009
Posts: 58
 
Device(s):
Carrier: Not Provided

Thanks: 2
Thanked 10 Times in 5 Posts
Default

Quote:
Originally Posted by K4KAI View Post
I downloaded the update from the Sprint website and installed it on my Hero. I then proceeded to configure it for my Garmin Nuvi760 where, after checking the Hero's "Trust this connection" query, it worked great.

Then on our new 2011 Toyota Sienna, I configured it on the Toyota Navigation System's Phone Connection, and it worked fine there, but I was not successful in downloading contacts, so I entered them manually, which only took a few minutes.
When you were on the leaked ROM, were you able to pair and use your Toyota Sienna's Navigation System's bluetooth? Were you running the latest leaked ROM? With the official RUU from Sprint, don't you have any issues connecting and using your car's bluetooth?

I'm on the latest leaked ROM, and I have read many people confirming it's the same as the official sprint update. I hate to lose root but if it's the only way I can get my car's bluetooth to work with my hero, I might consider installing the official 2.1 update.
akkidy is offline  
Reply With Quote
Old May 23rd, 2010, 05:38 PM   #37 (permalink)
Premium Member
 
JB in AZ's Avatar
 
Join Date: Oct 2009
Location: Florida
Posts: 1,868
 
Device(s): Droid MAXX
Carrier: Not Provided

Thanks: 265
Thanked 268 Times in 208 Posts
Default

With my 2009 Toyota factory Bluetooth/NAV, using 1.5, I couldn't transfer the contacts, but I was able to do so with my old phone, so all was good.

Using 2.1 (DC 2.0.8.1) works fine for outbound and inbound calls, except now the car's screen shows "private caller" or something like that, rather than showing the number of the caller and the caller's name. Outbound calls continue to show both the name and phone # on the car's screen. Any ideas anyone?
JB in AZ is offline  
Reply With Quote
Old May 24th, 2010, 08:09 AM   #38 (permalink)
New Member
 
Join Date: May 2010
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

I own a panasonic kx-th1212b bluetooth enabled home phone system for my house. With 1.5 I was able to pair and connect my phone so that when I arrived home from work, I could send and receive calls with my house phone handsets. Now thanks to this great update, I can no longer connect my phone to the base. The phone will pair but never connect. I hope there is some work around to fix this because right now I'm stuck with 1.5 otherwise.
dbldown768 is offline  
Reply With Quote
Old May 24th, 2010, 09:47 AM   #39 (permalink)
New Member
 
Join Date: May 2010
Posts: 1
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

Double bluetooth wammy for me. I also own a panasonic kx-th1212b bluetooth enabled home phone system for my house with same issue. With 1.5, I was able to pair and connect, but with the 2.1 update, the phone will pair but never connect. Next issue is I have a Jensen VM9022HD car audio unit which will does connect for for phone and audio. However cannot hear incoming caller nor them me. Worked just fine with 1.5. Hoping for an update patch soon.
coolregireg is offline  
Reply With Quote
Old May 24th, 2010, 12:41 PM   #40 (permalink)
Junior Member
 
Join Date: Oct 2009
Posts: 58
 
Device(s):
Carrier: Not Provided

Thanks: 2
Thanked 10 Times in 5 Posts
Default

Same here, both car and home bluetooth connection problems. Somebody please find a fix for this, cannot be caught driving while using the phone without handsfree kit! I need my bluetooth back!

Does anybody know what the bluetooth.apk is for? If I replace that with the bluetooth.apk from 1.5, granted that I would be running a deodexed ROM, would that work and make any difference?
akkidy is offline  
Reply With Quote
sponsored links
Old May 24th, 2010, 11:56 PM   #41 (permalink)
Premium Member
 
JB in AZ's Avatar
 
Join Date: Oct 2009
Location: Florida
Posts: 1,868
 
Device(s): Droid MAXX
Carrier: Not Provided

Thanks: 265
Thanked 268 Times in 208 Posts
Default

Quote:
Originally Posted by JB in AZ View Post
With my 2009 Toyota factory Bluetooth/NAV, using 1.5, I couldn't transfer the contacts, but I was able to do so with my old phone, so all was good.

Using 2.1 (DC 2.0.8.1) works fine for outbound and inbound calls, except now the car's screen shows "private caller" or something like that, rather than showing the number of the caller and the caller's name. Outbound calls continue to show both the name and phone # on the car's screen. Any ideas anyone?
Yesterday I reported the above. Today, the car's display began showing the incoming caller's name and phone # again! Weird, but it's certainly makes me happy. Why this happened? I don't know, but I guess when Google syncs the contacts with the phone, it initially only gets part of the information...andthe rest comes with time. Since I had just upraded to 2.1, maybe all the info wasn't there yet when I tested it yesterday??? Anyone have any ideas, or comments?
JB in AZ is offline  
Reply With Quote
Old May 25th, 2010, 05:58 AM   #42 (permalink)
Junior Member
 
Join Date: Jan 2010
Posts: 42
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Default

Just want to remind folks there are a couple of issue's
1. Audio transfer or Bluetooth streaming, ie Pandora and others, that works for me.
2. Bluetooth handsfree pairing and connection, some can pair and not connect, some can connect and have no audio (that's me)
3. Then there is the contact transfer, that has never worked for me and still doesn't.
lil goat is offline  
Reply With Quote
Old May 25th, 2010, 07:46 AM   #43 (permalink)
Member
 
K4KAI's Avatar
 
Join Date: Apr 2010
Location: Northern Virginia
Posts: 128
 
Device(s): DROID RAZR MAXX
Carrier: Verizon

Thanks: 77
Thanked 11 Times in 8 Posts
Default

Quote:
Originally Posted by akkidy View Post
When you were on the leaked ROM, were you able to pair and use your Toyota Sienna's Navigation System's bluetooth? Were you running the latest leaked ROM? With the official RUU from Sprint, don't you have any issues connecting and using your car's bluetooth?

I'm on the latest leaked ROM, and I have read many people confirming it's the same as the official sprint update. I hate to lose root but if it's the only way I can get my car's bluetooth to work with my hero, I might consider installing the official 2.1 update.
I DID NOT try to link up the LEAKED ROM to the Toyota Navigation system, but I was able to link with the NUVI760, which worked as it should.
K4KAI is offline  
Reply With Quote
Old May 28th, 2010, 04:47 PM   #44 (permalink)
New Member
 
Join Date: May 2010
Posts: 1
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

I too have an Eclipse AVN-726E in Dash Navigation device and now the Phone will not do bluetooth anymore! I'd rather go back to 1.5 and HAVE bluetooth functionatlity, especially since it's against the law to not be hands free in CA. Anyone know some kind of workaround or fix (or even a way to go back to 1.5)? Is this an Android 2.1 issue or just a botched 2.1 version for the Hero?
bearfan is offline  
Reply With Quote
Old May 29th, 2010, 10:27 AM   #45 (permalink)
Member
 
DaWeav's Avatar
 
Join Date: Nov 2009
Location: Lemoore, CA
Posts: 343
 
Device(s): Before: Sprint HTC Hero, Sprint HTC Evo Shift Now: Ting Samsung Galaxy S3
Carrier: Ting.com

Thanks: 2
Thanked 52 Times in 41 Posts
Default

Multiple Contacts Transfered from Sprint Hero to Toyota Prius 2005 Navigation system.

If you have not tried this procedure, give it a try. It worked for me on my Toyota Prius Navigation system to transfer entire groups of contacts to the car. Your mileage may vary though.

I exported all of the contacts I wanted to transfer to a .vcf file. I first exported all the contacts to a .vcf file on the phone using the People app (export), but my car only accepted the last phone number for each contact in this .vcf file when I transfered it to the car, but your's system combination might work. Anyway, I used Google GMail on the web which allowed me to export contacts for any group of contacts I had in my Gmail to a .vcf file. Then because my car system only likes one phone number per contact, I edited the file manually for each contact with multiple phone numbers. Then I copied this .vcf file on my SDCard.

Quote:
  1. Downloaded Astro File Manager from the Android market.
  2. Opened Astro File Manager and hit MENU/More/Preferences and select 'Edit File Extensions'.
  3. Selected the 'New Extension' button.
  4. Input 'vcf' (without quotes) as the Extension Name.
  5. Input 'text' (without quotes) as the Mime Type.
  6. Input 'x-vcalendar' (without quotes) as the SubType.
  7. Hit Save.
I then backed out until I got to my SDCard file listings in ASTRO, I Long-Pressed the .vcf file on my SDCard, I hit 'Send', I hit 'Bluetooth', I put my car in contact transferring receive mode, and then on the phone I selected the car handsfree system which transfered the .vcf contact file to the car successfully and all the contacts appeared on my car's phone list.
DaWeav is offline  
Reply With Quote
Old May 29th, 2010, 11:28 AM   #46 (permalink)
New Member
 
Join Date: May 2010
Posts: 3
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

I was having issues with my Sonata not downloading my phonebook until I noticed that when the phone was connecting to the car, a bluetooth authentication request would pop up in notifications on the phone. I approved the request and BT has worked perfectly since.
finalnight is offline  
Reply With Quote
Old May 29th, 2010, 05:59 PM   #47 (permalink)
Junior Member
 
FdxRider's Avatar
 
Join Date: May 2010
Location: Northeast Ohio
Posts: 47
 
Device(s): Sprint HTC Evo 4G LTE
Carrier: Not Provided

Thanks: 23
Thanked 12 Times in 10 Posts
Default

Quote:
Originally Posted by astrobill View Post
Good News/Bad News with regard to the new Bluetooth 2.1 in Android 2.1 on the Hero...

Good News:

I tested phone contact transfer and receive between my Hero and my other phone, an LG Rumor. Worked fine.

Bad News:

Still can't get FILES to transfer, but I'm working on it.

Worse news....

- My Hero no longer connects to the Bluetooth head unit in my car for telephone functions (still connects to audio streaming using AVCRP just fine)! The details are....

....It worked fine before the 2.1 update, but now the head unit now connects to the Hero for a second, then disconnects and reports that the phone is an "Invalid Device". I've noticed the head unit also seems to have trouble remembering the Bluetooth device name being reported by the Hero. Gets it right at first, then immediately says it can't determine the device name. Oddly, the Bluetooth audio streaming profile (AVCRP, etc.) still works and connects fine.

UPDATE:

The Bluetooth connectivity with the Hero under the 2.1 update is HIGHLY dependent on the car kit or Bluetooth device. For example, I was able to maintain a stable connection with a more modern Pioneer head unit in Best Buy, and it even saw the Hero's phone book automatically using the PBAP profile. However, I could not connect at all with an older Pioneer AVIC series unit. I had only partial success with other units, such as a Kenwood 6160 and some Garmin Nuvi's. On others, such as a Tom Tom with Bluetooth, I was unable to connect at all....
I am a noob to the Android seen but, I was wondering you all are banging your heads against the wall. Maybe it something simple like reset the head units! Then try to re-pair and connect. ????? That what i would try. BTW Hello everybody!!
FdxRider is offline  
Reply With Quote
Old May 30th, 2010, 04:37 PM   #48 (permalink)
Junior Member
 
Join Date: Apr 2010
Posts: 26
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 3 Times in 2 Posts
Default

I reported my problems with my Magellen GPS/BT to HTC. Here is the reply I (finally) got.

"Hi, Stephen. I apologize for the length of time it took me to respond to your email regarding your bluetooth. For the Android 2.1 update, Google has slightly altered the bluetooth stack of the Android operating system to change some functionality, for example adding new profiles to the existing programming. Unfortunately, this did somewhat change the compatibility of the device when pairing to other units. You can attempt to remove the bluetooth partnership with the device by pressing Menu while on the Home screen>Settings>Wireless & Networks>Bluetooth settings. Tap and hold on the device in question and selecting Unpair. After this, you can try to attempt to reconnect the devices via bluetooth to test functionality. Unfortunately, due to the change in bluetooth programming, it not guaranteed to function."

Not so satifying, I think. Needless to say, the suggestion made no difference.
sbillard is offline  
Reply With Quote
Old June 1st, 2010, 05:49 PM   #49 (permalink)
New Member
 
Join Date: Jun 2010
Posts: 1
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

I am having the same BT issues with my Hero 2.1, pairs & connects fine with my G37 but no audio.

Today I spoke with Advanced Tech Support with Sprint and she said that HTC is well aware of this issue and are releasing a small update to fix these issues and that this update is forthcoming over the next few weeks.
jindusingh is offline  
Reply With Quote
Old June 1st, 2010, 08:13 PM   #50 (permalink)
New Member
 
Join Date: May 2010
Posts: 8
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 4 Times in 2 Posts
Default

I don't think this has anything to do with 2.1 - I have two Android 2.1 phones - An HTC Hero with 2.1 where the bluetooth is broken and I get a connect/disconnect scenario in my car every 10 seconds or so.. I also have an HTC Incredible with 2.1, works perfectly in my car. So this seems to me that it's more of an HTC issue and not a Google issue.

Quote:
Originally Posted by sbillard View Post
I reported my problems with my Magellen GPS/BT to HTC. Here is the reply I (finally) got.

"Hi, Stephen. I apologize for the length of time it took me to respond to your email regarding your bluetooth. For the Android 2.1 update, Google has slightly altered the bluetooth stack of the Android operating system to change some functionality, for example adding new profiles to the existing programming. Unfortunately, this did somewhat change the compatibility of the device when pairing to other units. You can attempt to remove the bluetooth partnership with the device by pressing Menu while on the Home screen>Settings>Wireless & Networks>Bluetooth settings. Tap and hold on the device in question and selecting Unpair. After this, you can try to attempt to reconnect the devices via bluetooth to test functionality. Unfortunately, due to the change in bluetooth programming, it not guaranteed to function."

Not so satifying, I think. Needless to say, the suggestion made no difference.
southflguy is offline  
Reply With Quote
Reply

Sprint HTC Hero
Current Rating:
Rate this Phone:

The Sprint HTC Hero was announced on September 3rd, 2009, making Sprint the 2nd American mobile carrier to offer a phone based on Google's Android operating system. While HTC had already launched the Hero, making it available on European carrie... Read More



Go Back   Android Forums > Android Phones > HTC Hero (Sprint)
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 04:05 AM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.