05-22-2012 4:13 PM
Did the HTC upgrade of the VIVA to Android 4.0 (Ice Cream Sandwich) break the Bluetooth/Hands-free function?
I replaced my HTC ARIA with an HTC VIVID this week. Unfortunately, I immediately updated the phone to Android 4.0 (ICS). When I went to pair the phone to my 2012 KIA's Bluetooth phone system (UVO) the problems started. First, it took me several attempts to pair the phone and the UVO system. Then after pairing was accomplished (I thought), the phones would not connect properly nor would the would the phone's contacts upload into the UVO system.
This was very disappointing since my HTC ARIA running Android 2.2.2 had worked perfectly. Later on when I tested a couple of my old bluetooth headsets to see if I could use them as a work around, I discovered that they also were malfunctioning. I could receive calls but not initiate them using voice commands.
I've been working with computer hardware and software since DOS 2.0 and I'm pretty certain that this is an Android 4.0/Bluetooth software incompatibility issue, probably resulting from insufficient testing. After all, no company can test every possible hardware and software combination!
Unless someone has a ready solution to this problem, as much as I like the VIVID and ISC back it goes. I need hands-free calling for work and in Indiana it is illegal for a driver to use anything other than hands-free in a car. I suppose that means the VIVID is not "street legal"!
05-22-2012 6:32 PM
05-22-2012 7:24 PM
Thanks for the suggestion. That's exactly what I used to pair several headsets. All demonstrated the same behavior. They could receive calls but not initiate them.
The procedure for pairing the phone with the KIA/UVO phone system was downloaded from the the UVO web site which lists the VIVID as a compatable phone. A Customer Service Representative called me today and it appears that the VIVID was tested with Android 2.3 (Gingerbread) installed. Their technical support staff is now aware of the possible problem and will probably re-evaluate the VIVID with Android 4.0. installed.
- edited 05-23-2012 9:17 AM
The HTC Bluetooth stack on ICS is likely different from Gingerbread. Bluetooth on my One X will pair (and work once paired), but not auto connect with my 2012 Subaru with factory stereo. Worked fine with my old HTC Desire Z running Gingerbread. But Sense 3 ROMs had more reliable Bluetooth performance than Sense 2 ROMs. So it seems that HTC keeps updating the Bluetooth stack with each firmware version.
Also, when comparing the system files for the One X versus my old phone, there are many more car stereo brands added to the blacklist (as non-compatible) than previously. Seems like HTC is taking a bit of a step backward, as there seem to be more issues on the new Bluetooth stack (with various car stereos) than their used to be.
Your issue is almost certainly due to the software, and not anything you are doing on your end.
05-26-2012 8:14 PM
Update on my original post:
On Thursday, I was fiddling with my phone trying to some possible setting that would allow it to complete the Bluetooth connection to my car. Suddenly the screen went black (not usually a good thing), and then a small green window appeared which said “Android is installing an update”. After about 15-20 seconds, the screen went black and the phone re-booted. Another small green window appeared with the words “Updating item 1 of 10”. The window then counted up through 1-10 and completed the re-boot. Upon investigation, I found the Bluetooth option in the Settings app was dead: grayed-out and non-responsive. Not knowing what else to do, I shut down the phone, counted to 30 and re-started it. Guess what. The Bluetooth option was back. Not only that, but the connection to the car was now fully functional and I was able to upload the phone’s contacts to the car as well as place and receive calls.
Was this a “stealth” android update or the original ICS update spontaneously re-starting to correct a botched original install? Any ideas anyone?
In any case I am happy that the problem seems to have resolved itself because it was for certain that HTC wasn't going to help. They even deleted my identical post to their community support forums.
05-26-2012 10:17 PM
01-04-2013 9:45 PM