Share your experience!
since i bought the phone on 31st of May 2012, it came with GingerBread .42 and once i open it; it ask to update to .62, every thing was fine and the Bluetooth was working fine with my buit-in Bluetooth car kit for Honda Accord EX which does not has a screen to browse the contacts, no, just voice dial, call reject call, and end call, thats all, very simple, now since i update to Ice Cream Sandwich, ICS Android 4.0.4 on 14th June 2012, it refuse to pair, or in other words, it try to pair and keep trying but nothing happen, i reset the car kit, and tried to pair with other phones, Blackberry, Samsung Ace, all good, so i reset again and try with Xperia mini pro, nothing again, so i google the issue and i found people who had Ford, Fiat, Volvo, Alfa Romio, all had the same problem with even different Xperia ARC and XPERIA Pro
is there a solution or we had to wait for another update to fix the bluetooth - will it be in the same update that will fix the qwerty-azerty problem or we had to wait for two updates?
any one else had the same problem with their car kit?
P.S: i cannot pair from my car kit as i don't have any screen to monitor, so i had to do the pairing from my phone, and already tested to assure that the car kit is working fine, any suggesstions?
Hi Mattias. Thanks for the workaround using bluetooth file transfer (Medieval Sostware). It worked first time on my Land Rover for both my Sony phones.
I just downloaded bluetooth file transfer. The phone sees my car (as a headset), but it still doesn't pair. I get a "communication error". I'm using an xperia ray st18 on ICS.
this solution or the work around did not work with Xperia Mini Sk17i and Honda Accord 2008 Built in BT
Hello everyone!
Tough I have Xperia S still with Gingerbread, I encountered the same problem as many of you, and as many people in the web.
But let’s start the history step by step…
I tried to pair my Xperia with factory installed Bluetooth car kit (Citroen C5 - mfd. 2007).
The problem was that when I was trying to connect, there was a “connection failure” announcement.
Phone was finding the car properly, but when connecting, there was no option for typing in the PIN code.
After searching many forums and “ask & answer” sites, I found that the phone is automatically send “0000” PIN code. In my car kit the PIN code is “1234”. Normally the phone, after trying those quad-zeros should ask for other PIN code, but it didn’t.
I asked SONY about this bug, but no one could answer the question, why it doesn’t ask for alternative PIN and they were starting the “song” about incompatibility. Meanwhile I connected to the car kit Xperia Live with Walkman (Gingerbread), which also tried quad-zeros, but after few seconds, asked for PIN code. J
Some people wrote that helped them trying to send the contact or any file to the Bluetooth car kit system…during this phone asked for PIN code and managed to pair the phone.
My problem was that when trying to send contact or file, phone didn’t detect the car… probably because it recognized it as the headset, not a device able to receive files.
I tried different programs advised for Bluetooth file transfers and Bluetooth connection “helpers”.
None of them was successful except one… ASTRO!
I had already installed ASTRO file manager, and I added to this ASTRO Bluetooth plugin. Both you available at GooglePlay.
I turned on Bluetooth in the phone, then turned on ignition in the car (without starting engine – pairing method can vary in cars of course), then Opened ASTRO file manager and chose jpg to send via Bluetooth… ASTRO found the car kit (which wasn’t found by the phone J) . I press send and then it tried to pair asking for PIN code. Of course sending the file failed, but the car remembered the pairing as well as the phone.
Now I just turn on Bluetooth in the phone and it connects with car, moreover it reads phonebook and call list form the phone without any problem.
So don’t believe manufacturer that some malfunctions are not their problems send you to car kit manufacturers.
OK everyone, I know all of us struggle hard with all these issues since we upgrade to ICS, starting by the keyboard QWERTY and AZERTY, and then the Bluetooth issue which is 100% SONY firmware issue not the phone issue, as the Bluetooth was working on the gingerbread as fine as possible before we upgrade to ICS,
now some of us might bought a new carkit device and others had bought another phone or downgrade to gingerbread, as of myself and thanks to SONY dev team who worked very hard to hate the brand of SONY where ever I go, I couldn't downgrade because of the SONY support in my country don't want to do it, and they want me to buy another device which will hang ugly inside my car, so I decide to root my device and install cyanogen mod 9 which amazingly everything works, not only that, I discover that my phone can host as much as I think of applications without losing my phone internal memory, so the Bluetooth is back to normal, and sound became even better more than it was on gingerbread, I don't know how, but I think it is some feature added in cyanogen mod,
I lost my guarantee after buying the phone after three months of buying my XPERIA Mini Pro, because I found that keep using this phone for another one more month will drive me crazy, specially that I cannot refund it and I cannot change it because Kuwait Sony Support are not allowing such things, so after paying much money in my point of view investing in a phone that it should be small in size and yet powerful with 1GHz processer, I cannot just drop it in home and buy another one, so I choose to root it and change to an aftermarket firmware
Thanks to SONY again, this will be the last time in my life buy or use any product that has the trademark of SONY every again
A few weeks ago I ve got a Xperia Go and experinced similar problems described here. By trying to get connection to my car radio Sony mex-bt3700u bluetooth scanning finished without adding an item in list of pairable bluetooth devices. So I struggled back to my old Yendo and handsfree phoning works with my Sony mex-bt3700u. Is the new bluetooth standard not downward compatible? It is hard to believe.