Hey Folks!
Great work here... Coming from WM/Symbian/Blackberry I'll try Android for daily use now.
My actual only problem is, that my Hero won't reconnect with the bluetooth System MMI of my Audi A6. Pairing is fine, manually connecting works, but I found no way to automatically reconnect the Hero with MMI when I enter the car and turn on the ignition/engine.
Every other handset does this comfortable reconnect (Nokia E71, Blackberry Curve 8900, Palm Treo 750...).
Is this a problem of my Hero or of Android itself? Is there a workaround to solve the problem to get an automatic reconnect?
Thanx!
Tom
Maybe the problem with the Hero. I cannot connect the Hero to my BMW I-Drive at all.
My G1 connected to my alpine stereo fine, when it did a small microphone appeared on the stereo along with the bluetooth icon. The hero pairs, the bluetooth appears and the phonebook is browsable, however it doesnt display the mic icon on the stereo. I think this means it's not using the stereo to pick up voice. I need to test more.
It would appear that there is something different about the bluetooth stack on the hero. Which is worrying with it being a hybrid android build
There is definitely something different. My old G1 pairs and works flawlessly with my BMW I-drive. The Hero pairs but won't connect.
Works with my Audi A4 2009. Autoconnects, I can browse my contacts etc...
Lox_Dev said:
Works with my Audi A4 2009. Autoconnects, I can browse my contacts etc...
Click to expand...
Click to collapse
That's positive. Are your contacts on your SIM or straight from a Google account? Do you have the latest MMI?
I'm about to take delivery of an A6 with HDD 3G MMI with bluetooth and wondering what to expect.
I have some issues on Skoda Octavia as well. As Skoda/Audi/VW have some things in common, I thought to mention this.
Usually my Hero works fine, but maybe 33% of the times I cannot initiate a call from car bluetooth. It starts to make a call, but fails, on Hero I get some MMI error (have to write that down the next time I get it).
When the error occurs, I can still start a call from Hero and phone audio comes nicely through car bluetooth and stereo. It requires me to turn off the engine and turn it back on to get it working again, however, sometimes it will also start working by itself. Might be that if I initiate a call from phone, it will start working from car controls as well, but I cannot confirm that.
Ik works fine on my 2006 A4 MMI, and I did test it on my new A4 2009 Model coming in december.
No issues, both show contacts and auto connect.
Did you set the MMI device as "trusted"?
Automatic connection works fine with my Audi A6 4f MMI!
After a few seconds I have access to all Contacts through MMI.
No Problems at all..
Cheers, Otze
I just have a Motorola bluetooth/FM transmitter. It's not perfect, but what I have to do is turn the Hero's bluetooth on *AFTER* the Motorola unit is initialized. So maybe enter your car with the Hero's bluetooth off, turn on the car, then once the stereo's booted up, turn on the Hero's bluetooth.
It's a bit inconvenient, but it works for me.
Also, I suspect that when we get the Eclair update, our bluetooth will work better, as Eclair is said to finally include a bluetooth API (which has been missing from previous versions, as Google said they wanted to polish it up before releasing it to developers.)
I have a problem where my HD2 does not work properly with my Land Rover Freelander 2 in-built bluetooth car kit.
The HD2 pairs with the car and I can search my phone book, see my last dialled number, I can even dial a number, BUT, the phone does not connect properly - the car radio should cut out and phone audio come through the car speakers, but instead the radio just continues to play. And shortly after the call is connected to the other party the line is terminated.
My Nokia phone works perfectly with my car, but this phone does not. Even my Sony Ericsson Xperia X1 did not for properly with the Freelander 2.
I did manage to make one successful call, but after I stopped and restarted the car, the problem returned!! Arghhhhhhhhhhhhhhh!
So, does any one know of a fix? Surely hands free/car kit is a standard?
Help!
same problem here. i have a bluetooth car stereo. Always worked fine with my previous HTC's. But now with the HD2 i get the exact same problems as you... I think it's software bug. i have rom version 1.43.404.1 NLD
i hope this gets sorted out cause i use bluetooth audio streaming a lot in the car....same for handsfree calling
Paired it with my Pioneer FH-P80BT on my way to sell my 3GS and recieved a call. Got the same issue as described above - just a bug i presume.
I'm experiancing similar problems. All works fine (incoming call's or outgoing call's) but they get disconnected randomly it seems. I'm using a JVX NX7000 by the way. No problem with my iPhone. Hope they fix it soon!
I tested it with my BMW Idrive last night which is notoriously difficult and it worked fine, I was really surprised tbh! But was able to recieve and make calls, the stereo cut out and could see the phone book too. With my N82 i was only ever able to make/receive calls.
Same problem - Jaguar XF - it docks ok but I have to initiate calls from car (vs phone). Just some weirdness going on...
glenner05 said:
same problem here. i have a bluetooth car stereo. Always worked fine with my previous HTC's. But now with the HD2 i get the exact same problems as you... I think it's software bug. i have rom version 1.43.404.1 NLD
i hope this gets sorted out cause i use bluetooth audio streaming a lot in the car....same for handsfree calling
Click to expand...
Click to collapse
Mercedes brutality
I have a new Mercedes C, and when the HD2 is connected over bluetooth I get an extremely loud, strange ringtone when receiving a call. It is so loud it could really make your shoes go off.
Also it is none of the ringtones available to choose from, inside the phone - it sounds more like a BIOS beep from a PC and hits me while the normal ringtone is playing as well.
It definitely comes from the phone, not from the car stereo. I have not figured out how to resolve this, I think it is outright dangerous for unprepared drivers.
I have a Nissan Pathfinder; it paired ok, and dials from the Pathy without probs. Ringtone is ok too. Sound quality seems better than my old Tytn so all in all v happy.
Doesn't stream music, but that's Nissan's fault, not HTC.
Works fine with the Ford BT system in the Ford Focus (2009).
HTC HD2 Pairing with a Freelander 2 - SUCESS!!!
Success!!!
So far so good, I applied a known change to the HD2 registry and I am now making and answering calls without fuss!
Change Registry setting:
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\Sys
Add the DWORD setting COD=5374476
This makes devices see the HD2 as a 'Normal' phone.
Hope this helps everyone.
graemenwallace said:
Success!!!
So far so good, I applied a known change to the HD2 registry and I am now making and answering calls without fuss!
Change Registry setting:
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\Sys
Add the DWORD setting COD=5374476
This makes devices see the HD2 as a 'Normal' phone.
Hope this helps everyone.
Click to expand...
Click to collapse
Hello i have same problem with my BMW X5. Can you explain better your steps ?
graemenwallace said:
Success!!!
So far so good, I applied a known change to the HD2 registry and I am now making and answering calls without fuss!
Change Registry setting:
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\Sys
Add the DWORD setting COD=5374476
This makes devices see the HD2 as a 'Normal' phone.
Hope this helps everyone.
Click to expand...
Click to collapse
Interesting, I have a similar problem with my 2009 BMW 3 I explain here (sorry I posted before discovering this thread) and I'll try your registry tweak.
But you say that it is "a known change" to the HD2, could you tell us where you saw it ? Is there another discussion about the BT stack somewhere or more generaly about the Widcomm implementation in the HD2 ?
The HD2 being so recent and in short supply, I'm a bit surprised something like that is "well known"
Thanks for your help.
It works !
graemenwallace, I just tried after applying your tweak and... OMG, this is AWSOME man, it just WORKS !
I still just have one gripe though, it seems that the car doesn't always receive the RF level correctly at the first connection. Sometimes it sees the phone as having no carrier at all (no bars in the RX level display), preventing the car to make any calls, but as soon as I receive a call, the level resets to full bars and I can pick the call and make calls myself after that.
When the first call comes in, I can see the display with no bars and a "?" appearing on top of it for a short time before it becomes full bars.
So there is still some compatibility problems, but at least now I can pick-up incoming calls without risking my life.
So I suppose you are a potential life saver then
Thanks mate,
Yves.
Bluetooth is working YES with JVC KD-AVX44 ADV49
After the registry tweak from graemenwallace the bluetooth connection is working properly with my car radio (JVC KD-AVX44/KD-ADV49).
The phone functions ok now (incoming & outgoing calls) Also the AD2P connection is super (very good sound)
Also the ID3 tags are functioning (didn't function with the X1 Xperia)
I see the track title now into the JVC display
Skipping etc. all is functioning. I will tell HTC about it because I have a ticket running for this issue. I think they have to solve this issue
Big thanks for this trick
By doing a little search on the net, it seems like graemenwallace suggested that this problem is not new with smartphones that identify themselves as such.
The tweak above forces the BT stack of the phone to identify itself as a standard phone instead of a smartphone.
What's puzzling is that my BMW handsfree worked with other smartphones so far, including the iphone.
Anyway, it's ok now, but I wonder what bad press this will cause to HTC.
The majority of the users are unaware of this kind of wizardry and this justs adds up to the long list of bugs of the HD2.
When I first got the phone a few days ago I was rapidly convinced to return it immediatly as it's fancy interface wasn't enough to overcome all the shortcomings. It was plain unusable as a business phone.
Now after applying most of the tweaks, it begins to show potential, but HTC really has to work on the problems we can't fix by tweaking the registry.
I tried this also, but for me it didn't work.
But my situation is a bit different, as I am not able to connect the HD2 through the Sim Access Profile with my car, which is an Audi A6 mit Bluetooth preparation and I have also the Audi rSAP Adaptor installed in the centre arm rest.
My problem is, that I get a connection to the car, but SAP does not activate and I can't get access to my phonebook - so I only have kind of a handsfree profile...
Am I right that you all use the handsfree profile in your cars and no SAP?
jah said:
Works fine with the Ford BT system in the Ford Focus (2009).
Click to expand...
Click to collapse
Does your Ford system have the Bluetooth audio choice?
I get my Ford Focus changed every six months coz i'm a driving instructor and it comes as part of the deal.
On my last Ford Focus my htc tytn 2 connected ok and I could make and receive calls ok.
However, when the new car was delivered the Ford system had bluetooth audio choice and ipod integration which the other one didn't.
Now my htc tytn 2 didn't connect very well at all.
Now with my HD2 it does connect only if I have the bluetooth audio profile selected.
But now the music player keeps appearing and wants to play music all the time. If I pause the music on the phone it just starts replaying.
Anyway I will try the registry tweak in this thread and hopefully that will solve the problem.
Paul.
Jolig said:
I tried this also, but for me it didn't work.
But my situation is a bit different, as I am not able to connect the HD2 through the Sim Access Profile with my car, which is an Audi A6 mit Bluetooth preparation and I have also the Audi rSAP Adaptor installed in the centre arm rest.
My problem is, that I get a connection to the car, but SAP does not activate and I can't get access to my phonebook - so I only have kind of a handsfree profile...
Am I right that you all use the handsfree profile in your cars and no SAP?
Click to expand...
Click to collapse
I have the same problem. I`ll try to pair my HD2 with MB C-klass using SAP but i can`t get them connected it seems like a SAP adaptor can`t activate a PIN input window on HD2 (i guess). With other phones it works perfect (tryed with Nokia 5800, 6500).
Shark_Abuser said:
I have a new Mercedes C, and when the HD2 is connected over bluetooth I get an extremely loud, strange ringtone when receiving a call. It is so loud it could really make your shoes go off.
Also it is none of the ringtones available to choose from, inside the phone - it sounds more like a BIOS beep from a PC and hits me while the normal ringtone is playing as well.
It definitely comes from the phone, not from the car stereo. I have not figured out how to resolve this, I think it is outright dangerous for unprepared drivers.
Click to expand...
Click to collapse
could you pls describe, how did get them paired? when i try to pair them, i see the device`s id, try to "call" it, see pin code and after that i hear the descending tone. and it nothing occurs. SAP is enabled, device is discoverable, what else? Any idea?
Jolig said:
I tried this also, but for me it didn't work.
But my situation is a bit different, as I am not able to connect the HD2 through the Sim Access Profile with my car, which is an Audi A6 mit Bluetooth preparation and I have also the Audi rSAP Adaptor installed in the centre arm rest.
My problem is, that I get a connection to the car, but SAP does not activate and I can't get access to my phonebook - so I only have kind of a handsfree profile...
Am I right that you all use the handsfree profile in your cars and no SAP?
Click to expand...
Click to collapse
I feel your pain, my wife has a GolfPlus and the rSAP instalation is crap.
It's overly expensive and useless if you don't have one of the few phones compatible with it.
Unfortunately, many customers are falling in this trap, thinking it is a standard handsfree, but it is not, it is a full GSM build-in which only access your phone SIM card to log into the network and download your contacts.
In the case of my wife, the dealer was honest and clearly stated that it was a mistake to order this option.
The only problem is that he had no other alternative than proposing an Parrot retrofit which wasn't really an option for me as it wasn't integrated in the car and certainly not in the navigation system.
But internet is your friend and the solution is quite simple, the Kufatec kit.
This is brilliant, it is a small box that connects to the CAN bus of many german cars and integrates perfectly into existing navigators, it uses the steering wheels command buttons and so on.
It is much better (more functions) than original BT options, is tailored to each brand so that the displays are in the same style as the original ones etc.
More interesting, it is field upgradable (just a laptop with BT) so that it is potentialy compatible with anything existing or not yet.
And it only costs a fraction of this crappy rSAP option.
In your case, the good news is that it can simply replace your actual rSAP kit for a minimal installation fee. (the CAN bus has to be reprogramed however, so professional instalation needed)
There is another solution: to replace the unit you have (it is situated under the driver's seat) by a skoda unit. This unit has the same connector but is simple handsfree instead of rSAP.
Hope this helps.
So I've just bought a JVC KW-AVX 740. Great little unit, comes with bluetooth support built in.
Unfortunately, my Galaxy S doesn't integrate as well as it should. Both the unit and the Galaxy S support PBAP. The unit is capable of accessing dialled/received/missed call lists as well as the phonebook and voice dialling on compatible phones. However when pair/connect up my Galaxy S to the unit, the functionality is quite limited.
I can:
Make calls from the headunit
Receive calls via the headunit, so the handsfree element seems to work just fine. Quality is acceptable.
Send my phonebook across manually either one by one or in one go so it is stored on my headunit's memory (this worked flawlessly and was quick)
Play music from the Galaxy S over bluetooth through the headunit (quality is pretty good with no issues to report although I'm yet to do some more complex tests e.g. see what happens if I receive a call whilst streaming audio at the same time)
However, the unit is unable to:
Voice dial
Access the phonebook of my Galaxy S,
Access the dialled/received/missed calls lists
No SMS alerts
To double check it wasn't my unit playing up, I decided to hook up my Nokia 5130 Xpress Music - result?, it worked flawlessly.... Pairing was instant, as it is with the Galaxy S, except everything worked as it should. I could view the lists on my phone through the headunit and access the 5130s phonebook. Everything sync'd perfectly.
So it's not the headunit, meaning it's either Android or something Samsung have done to Android.
When I pair/connect the Galaxy S I do not get a prompt asking me if I want to grant the bluetooth device access to the phonebook - which is what is supposed to happen (and I've read about other peopel receiving this prompt when connecting their Galaxy S's to other car kits e.g. factory car bluetooth etc). When I check the device options in Bluetooth settings on the Galaxy S, under profiles all it shows is "Phone (use for phone audio)" and "Media (use for media audio)". Both boxes are ticked. Shouldn't it show other profiles like PBAP etc?
Does anyone have a picture of what the prompt looks like on the Galaxy S?
Phone details:
OS ver: Gingerbread 2.3.3 official and totally stock (no root, etc)
Basband: I9000XXJVO
Build num: GINGERBREAD.XXJVO
None of the contacts on my phone are synced up with Gmail/Exchange/Facebook. I added all my contacts by hand into the phone's memory.
Question: What's going on? Or more importantly how do I fix it?
Ok so I've done some more tests with some results I guess could be perceived as positive.
I tried my mum's Galaxy S on stock Orange UK branded 2.1 Eclair and to my delight the phone fully integrated... It disconnected the first time but I reconnected and it seemed to be ok.
I then tried a friends Orange San Francisco (aka Zte Blade) on stock Orange UK branded Eclair also, 2.1 - and this also worked fully!
As soon as either phone connects - both show a prompt stating the connecting device (JVC unit) is asking for phone book access - and when given - the stereo can access all lists and the phonebook.
My phone still doesn't work!
I'm putting the problem down to stupid Gingerbread - so WTF did they break?!
Hi,
has anyone had any experiences with trying to pair an SII (mine's running 2.3.4 stock) with an up to date Bluetooth phone module in a VW group vehicle. These support RSAP (GSMIII prep) as well as GSMII (lUHV/AD2P). I've sucessfully got the phone and BT module to pair but not always cleanly. When the handset is pairing via BT the signal bar display is replaced by the NO NETWORK (circle with diagonal slash) on the phone. If the pairing completes before this changes back to the normal signal bars then the BT module shows the phone as paired but with no network (even though the phone subsequently connects back to the service provider). Just wondered if anyone had experience pairing SII phones with VW group bluetooth modules... (I've actually replaced the module on my car with the latest D series one (5N0035730D).
Any feedback/experiences appreciated.
I have a Passat and it works like a charm with all used firmware version of GT-I9100 up to several 2.3.4 stock roms. I use currently I9100XXKG3-I9100XXKG3-I9100OXAKG3.
Just make you SG2 visible in Settings-Networks-Bluetooth and search with car's multimedia unit for a phone. Car display will show you a code like 1111222233334444 which you need to enter in SG2 when asked for it. Be quick otherwise it is canceled. If you have success you will be asked 2 (!) times to confirm permissions. Look in notification bar. One for connect and one for address book (Sorry if keyword are not fit 100%. I do this from my memory).
Works like a charm!
I also use my SII with great success in my Passat CC with the rSAP solution. The radio on the SII is supposed to turn off as the car has its own cellphone integrated and only "borrows" the SIM card over BT. My phone show two BT icons when it is working, and the phone in the car uses a few seconds to register on the network after it gained control over the SIM card.
Sent from my GT-I9100 using XDA App
thanks for the feeback.. Sounds like the sort of thing I'm seeing... I see two BT symbols too... sometimes with two little arrows pointing inward during pairing.. Still though, i get NO NETWORK on the BT unit unless my phone comes back online before the pairing completes. It would appear the BT unit i have has two RSAP modes but I've no idea what the difference between them is (you can flip modes from the car menus). Just wish I could get this working reliably.I can't figure out why its being so problematic when everyone else's seems to work fine. I've uplifted the RNS 510 f/w to 2764 and have the latest BT D series unit available. I guess I can try an alternative simcard and handset to see if its any different... if anyone else has any advice it's always welcome...
thanks anyways.
Ad
I'm having problems with paring my Samsung Galaxy S4 with the bluetooth carkit in my Toyota Corolla Verso. When I try to connect the carkit and the phone can find each other. When I try to pair them the phone asks for a pincode which is given by the carkit. When they are pairing up the carkit freezes and restarts and forgets all the settings from the phone.
I paired the carkit with my girlfriends phone (Samsung Galaxy S Plus) and then everything works flawless.
I googled this problem and a lot of people with the Galaxy S4 have similar problems, while all other phones seem to work but no one has a solution. Now I am wondering if this is software or hardware related? Is there a custom rom available which could solve this problem?
Thanks in advance,
Kierewiet
my s 4 works perfect with my 2013 verso [touch n go] when i paired it it gave me a code on the phone ,and on the touch n go it showed the phone code ,i just pressed accept .you have to make the touch n go visible .
westentertainer said:
my s 4 works perfect with my 2013 verso [touch n go] when i paired it it gave me a code on the phone ,and on the touch n go it showed the phone code ,i just pressed accept .you have to make the touch n go visible .
Click to expand...
Click to collapse
My Toyota is from 2006 and the bluetooth system is called Audio Blue so I guess it's a different system. It doesn't matter if I make the phone visible or not. It gives the same result.