Related
Recently bought this carstereo, as it got bluetooth buildt in. The combination with S200 works allmost excelent, but for two things.
What it does: It works well as a handsfree set, it mutes the sound, shows the number in the display, and the remote control either accept or reject the call. What it does'nt do (and the manual warns about this, I was aware of this before I bought it): It won't sync the phonebook. Either can I beam single contacts.
Anyone here tried this combination and had better luck than me? Any good advice?
HPN
I have the JAMin with this head unit. Exactly the same experience as you. I also have two other things I'd like to change or find a solution for:
1. Although auto-connect is on, I have to connect manually (the manual warns of this). I wonder if there's some way of automating this or at least making it one click form either the pda or the head unit.
2. Pressing and holding 'band' triggers VoiceCommander on my PDA but I can't give commands. It seems that the audio form the car's mic is not fed through to the pda. Any ideas?
Regards
I have the same problems and i don't find any solution
Anyone have any luck resolving these problems? I'm looking into a Pioneer DEH-9800bt and want to transfer my phonebook, as well as use voice commander.
Using Jetware you'll solve all your probs.
Hi all,
I know there are plenty of threads about the TyTN bluetooth issues, but my questions differs in two ways which I have yet to come across:
I do NOT have M$ VoiceCommander installed (and don't want to install it)
My bluetooth issue relates to my car's handsfree feature - my TyTN randomly connects and disconnects. Apparently Audis, VWs, BMWs, and Acura's all suffer from this this problem.
The situation:
When I start my car, the phone will successfully merge with my TyTN. Approximately 30 to 60 seconds later, the connection will be lost. Shortly after that the connection will re-establish itself, then it will disconnect itself a short period later. This pattern repeats endlessly.
I've tried each of the following Tweak programs but none have helped.
jetwaremobile
Tweak2k
HTweakC
I've heard that there is some kind of registry tweak that will prevent the bluetooth stack from disconnecting from my car's handsfree feature, but after looking for about 2 days now, I can't find it. Can anyone help?
thanks.
jm
Yep, got exactly the same on my BMW 630....
Can t find any tweak but....
I am a heavy email user (thru BlackBerry connect) and I noticed that
the higher the number of messages stored, the higher disconnections appears.
At the same time, the TyTn is slower and slower....so my idea that this is related to some timeouts somewhere....
For your complete info, the MS bluetooth stack in my previuos S100 have able to.....immobilize my 630 !!!!!!!!! yes, incredible...
The MS stack messed up with the BMW bt ...and this later would stay ON for ever...even after switching car s power off.
This was sucking the car s battery untill the car would start !...
BMW could not reset the BT module unless disconnecting battery....but...then the active steering had to be re adjusted with the proper BMW computer...
This is a real story.
johnmclean said:
Hi all,
I know there are plenty of threads about the TyTN bluetooth issues, but my questions differs in two ways which I have yet to come across:
I do NOT have M$ VoiceCommander installed (and don't want to install it)
My bluetooth issue relates to my car's handsfree feature - my TyTN randomly connects and disconnects. Apparently Audis, VWs, BMWs, and Acura's all suffer from this this problem.
The situation:
When I start my car, the phone will successfully merge with my TyTN. Approximately 30 to 60 seconds later, the connection will be lost. Shortly after that the connection will re-establish itself, then it will disconnect itself a short period later. This pattern repeats endlessly.
I've tried each of the following Tweak programs but none have helped.
jetwaremobile
Tweak2k
HTweakC
I've heard that there is some kind of registry tweak that will prevent the bluetooth stack from disconnecting from my car's handsfree feature, but after looking for about 2 days now, I can't find it. Can anyone help?
thanks.
jm
Click to expand...
Click to collapse
I have the same problem with a CK3100 kit, don't have a solution, but would like one, didn't have this problem with a Jasjar nor Wizard
TyTN bluetooth | random disconnect when using car handsfree - more details
Thanks for the replies so far.
Although the following thread did not help me with my problem, it might help one of you. If you're having problems mostly related to issuing voice commands using M$ VoiceCommander, I think there *might* be a solution in that other thread for you.
Just to reiterate my problem; my TyTN keeps randomly connecting and disconnecting from my car's built-in hands free bluetooth device.
There was a time when if i managed to made a call after first starting the car - before the first random disconnect - the phone would remain connected until the next time I started the car. That no longer appears to be the case.
-jm
I solved the BT problem with my Orange SPV M3100 by setting it to never switch off the display automatically (only switching off the backlight after 20 seconds or so). I also use an in-car charger to power the TyTN. The car is an A6 with RNS-E (BT enabled) and TyTN works fine and never loses the BT connection as long as the display is active.
This is a mid-term solution though and I'm still eagerly waiting for a ROM update that will solve the problem for good.
Has anyone tried a ROM with aku 3.3?
jasonrhcastle said:
Has anyone tried a ROM with aku 3.3?
Click to expand...
Click to collapse
Yes.
And on my CK3100 I now no longer get disconnects. I did have to uninstall jetware as it wasn't reliable. My TyTN now connects perfectly and no longer drops.
One thing I did find is that the TyTN hates it when more than one handsfree device is in its trusted list. Make sure that the ck3100 is the only handsfree device paired.
http://forum.xda-developers.com/showthread.php?t=247520&highlight=bluetooth+keeps+disconnecting
ajax007 said:
I solved the BT problem with my Orange SPV M3100 by setting it to never switch off the display automatically (only switching off the backlight after 20 seconds or so). I also use an in-car charger to power the TyTN. The car is an A6 with RNS-E (BT enabled) and TyTN works fine and never loses the BT connection as long as the display is active.
This is a mid-term solution though and I'm still eagerly waiting for a ROM update that will solve the problem for good.
Click to expand...
Click to collapse
I've tried changing the automatic switch off setting and it made no difference on my SPV M3100 (with Parrot CK3100) - I reckon that the external power is what fixed your problem (this has worked for others too).
Sadly it's not a convenient fix as I like to leave my phone in my pocket when I'm in and out of the car. Orange say there is no 'issue' so there's no sign of a ROM update but HTC know of the problem but I have to wait for Orange to release their ROM update. I can't use the HTC update. If only us Orange users could tell them enough times they might listen now that some AKU 3.3s are being released. Orange technical department won't speak to end users like me - they have actually refused to discuss it with me and just pass messages back and forth from customer relations. Any other ideas?
A solution - thanks to Parrot
Yippee - thanks to Parrot I have got a solution to the TYTN / CK3100 problem (my phone is the Orange SPV M3100).
As Orange and HTC can't find any solution I kept asking Parrot for ideas. Their excellent customer service department tried various settings which made no difference until I was offered a trial of some beta test software called VCF creator. Once you have the VCF from the PC's Outlook you just need to beam it by BT across to the CK3100 and alter some settings (takes 5 minutes maximum). The small sacrifice is that you don't have auto-synchronisation so if your numbers change a lot you will need to do another VCF upload. The extra bonus benefit is that all your numbers will be grouped together. So, for example, you access someones name and then you can see their mobile/home/work number rather than having a separate line in the main list for each phone number. The problem is a result of how Windows Mobile phones provide the data. With this bonus you can then use voice activation to input a name followed by a keyword mobile, home, work etc. Fantastic!
587dan said:
Yippee - thanks to Parrot I have got a solution to the TYTN / CK3100 problem (my phone is the Orange SPV M3100).
As Orange and HTC can't find any solution I kept asking Parrot for ideas. Their excellent customer service department tried various settings which made no difference until I was offered a trial of some beta test software called VCF creator. Once you have the VCF from the PC's Outlook you just need to beam it by BT across to the CK3100 and alter some settings (takes 5 minutes maximum). The small sacrifice is that you don't have auto-synchronisation so if your numbers change a lot you will need to do another VCF upload. The extra bonus benefit is that all your numbers will be grouped together. So, for example, you access someones name and then you can see their mobile/home/work number rather than having a separate line in the main list for each phone number. The problem is a result of how Windows Mobile phones provide the data. With this bonus you can then use voice activation to input a name followed by a keyword mobile, home, work etc. Fantastic!
Click to expand...
Click to collapse
If you use the Jetware BT software you can do the same thing e.g. beam the whole contact list in one go and then set the Parrot to not sync by choosing the Ericsson No Sync profile. This is how I have mine set up, also with the Jetware software it sends over the Service Provider, Battery and Signal strength settings to the Parrot, something which the native stack doesnt do.
Solution for this
Hey all, i have purchased a parrot 3100, the software in it was 1.6, i had the same problems but it's greatly and successfully solved using the new jetware 1.3 . i don't know if i can post some linx here, but here you go, if this is illegal for this site please remove them
http://rapidshare.com/files/30296941/JetWare_1.3.rar
http://www.megaupload.com/?d=PL5UX5KC
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.
ever since my G1 updated from 1.1 to 1.5, it has not been compatible with my nissan handsfree bluetooth system. i waited until another update, and now that i have my nexus one and it still doesn't work, i'm a little disappointed.
i am able to pair my phone to the car, but when i make or receive a call the car speakers shut off (as they should) but the audio comes out of the phone. i don't even know about whether or not the other people can hear me.
is this a known android issue? it may even be a nissan issue, but i'm sure it can be fixed within android (seeing as how my g1 used to do this). i'm 99% sure there's no easy way to update the nissan bluetooth firmware to help this.
anyone experiencing the same thing and is there some fix out there or some effort?
Well, I don't have a android device or nissan hands-free, but I do use a Touch Pro 2 with my sync equipped ford. Anyway, I had a very similar issue, and I had to go into the bluetooth manager and change a setting that had it default to audio over the hands-free device, rather than some other thing... It has worked great ever since then. Oh, I also learned that I had to answer the call using only the car's answer buttons otherwise if I hit answer on the device it would again send the audio only to the phone's speakers. Of course that seems logical, but my phone prior to that would allow me to answer and speak through the hands-free with either method of answering the phone.
At least it's something to look into.
Also, the phone I had before the TP2 required that I update my sync software before it would work. However, it wouldn't even pair before the update, so I don't think that's your issue. I don't know what the procedure is for updating your nissan firmware, but sync simply involves downloading a system version checker to a usb drive, plugging it into the car, return to computer and download available updates, and then return to car to install updates. I would guess nissan would have a similar method?
I realize we're dealing with two completely different systems here, but I figured I would chime in anyway since I had a very similar situation.
My Acura handsfree works like a charm. Perhaps you have too many contacts that are syncing?
awee man... I was hoping that there were no nissan/infiniti bt issues w/ this phone
I'll find out Saturday when I finally pick it up from the fedex place
rossiscatch said:
Well, I don't have a android device or nissan hands-free, but I do use a Touch Pro 2 with my sync equipped ford. Anyway, I had a very similar issue, and I had to go into the bluetooth manager and change a setting that had it default to audio over the hands-free device, rather than some other thing... It has worked great ever since then. Oh, I also learned that I had to answer the call using only the car's answer buttons otherwise if I hit answer on the device it would again send the audio only to the phone's speakers. Of course that seems logical, but my phone prior to that would allow me to answer and speak through the hands-free with either method of answering the phone.
At least it's something to look into.
Also, the phone I had before the TP2 required that I update my sync software before it would work. However, it wouldn't even pair before the update, so I don't think that's your issue. I don't know what the procedure is for updating your nissan firmware, but sync simply involves downloading a system version checker to a usb drive, plugging it into the car, return to computer and download available updates, and then return to car to install updates. I would guess nissan would have a similar method?
I realize we're dealing with two completely different systems here, but I figured I would chime in anyway since I had a very similar situation.
Click to expand...
Click to collapse
haha yeah, i don't have a "bluetooth settings manager" on my car, and i don't think i can update the firmware...which is ridiculous.
also, to the acura guy, my contacts aren't even syncing
niiiick said:
ever since my G1 updated from 1.1 to 1.5, it has not been compatible with my nissan handsfree bluetooth system. i waited until another update, and now that i have my nexus one and it still doesn't work, i'm a little disappointed.
i am able to pair my phone to the car, but when i make or receive a call the car speakers shut off (as they should) but the audio comes out of the phone. i don't even know about whether or not the other people can hear me.
is this a known android issue? it may even be a nissan issue, but i'm sure it can be fixed within android (seeing as how my g1 used to do this). i'm 99% sure there's no easy way to update the nissan bluetooth firmware to help this.
anyone experiencing the same thing and is there some fix out there or some effort?
Click to expand...
Click to collapse
I also just got an N1 and my Nissan handsfee bluetooth lets me voice-dial but the call doesn't get routed through the handsfree system. I have to take the phone out of my pocket and activate the speakerphone. Any solution would be much appreciated.
I don't have teh same system. Like the previous poster I use the N1 with my Ford Sync. If a call is initiated from the phone it starts out in "private" mode using my phone's speakers. If initiated from the car it uses the car's sound system. There's also an option in there allowing you to choose the default sound output of calls. I have the latest firmware installed.
That actually makes sense.. my previous phone always used the speakers which was a bit of a shock sometimes when I was sat in a car park wanting to make a quick call. Clearly it still has some rough edges on some cars.
There are some very old threads about this - but this is now, pretty certainly, a general stock android 4.3/4 problem with "older" car hands-free systems. My kit is a Galaxy Note with OmniROM right up to date. My car is an Opel/Vauxhall Zaphira with a Navi 900 onboard computer. However there are threads on many android forums complaining of the same symptoms for "pure" stock 4.3/4 devices (e.g. the Nexus range, including the Samsung Galaxy Nexus) and a variety of cars, and all describing the same workaround (and a few lamenting that Google haven't been very responsive in addressing the problem). The symptoms and workaround are:
The car recognizes and "partially" pairs with the phone
However, the contacts list and call lists are empty and the phone cannot be controlled from the car, neither for incoming calls nor for outgoing calls (dialing from the car interface always gives a failed message, while trying to receive or hangup from the interface just plain fails).
Calls using the phone work, and show up on the car interface, always as "Unknown" (not surprisingly - it doesn't have the contacts list)
HOWEVER if, after this "partial" pairing up, I make a 30-45 second call using just the phone itself, then, after the call has terminated, contacts and call lists are properly available through the car interface and the phone can be fully controlled from that interface (and, of course, the FIRST time this happens, I get the notification on the phone telling me the car wants this information, which, of course, I confirm)
A workaround like that can be scripted with something like "Tasker" and using, say, my voice mail number (with my provider here in France, plain fake number calls don't stay online long enough for the above to work).
But does ANYONE have any idea where to start looking for the root cause and possible solutions, or have any theories on those points?
EDIT:
Just to be clear - the workaround "make a call from the phone" trick has to be done every time the phone and car reconnect, not just the first time.
Had this happen in my ford the other day and it's sync system.
The fix for me was a not so visible notification upon establishing the Bluetooth pairing in the notification tray asking if I wanted to allow for my phonebook to be downloaded. Clicked yes and everything set up as normal.
Mgd_toronto said:
Had this happen in my ford the other day and it's sync system.
The fix for me was a not so visible notification upon establishing the Bluetooth pairing in the notification tray asking if I wanted to allow for my phonebook to be downloaded. Clicked yes and everything set up as normal.
Click to expand...
Click to collapse
I got that notification AFTER I had done the "make a call from the phone" trick, not before.
I should also point out that the "make a call from the phone" trick has to be done every time I want to reconnect to the phone to the car (while the notification only appeared the first time I did the trick - because subsequently the phone and the car "trust" each other).
Aside from maybe unpairing and trying to set it up again which I am certain something you've probably already tried; have you checked the cars firmware?
Could also try resetting your Vauxhall's system as well in case there is a gremlin in there causing a hang up with the sync.
Again with Fords sync I have had to do it a few times over the years when the systems been misbehaving with the Bluetooth and it fixed it.
Mgd_toronto said:
Aside from maybe unpairing and trying to set it up again which I am certain something you've probably already tried; have you checked the cars firmware?
Could also try resetting your Vauxhall's system as well in case there is a gremlin in there causing a hang up with the sync.
Again with Fords sync I have had to do it a few times over the years when the systems been misbehaving with the Bluetooth and it fixed it.
Click to expand...
Click to collapse
Indeed I did the resets. And yes, possibly, an upgrade of firmware MIGHT fix it, but these problems don't occur with Android 4.1.n (or, I, believe 4.2.n).
I've logged a bug with the OminROM developers, but would like some pointers so I myself can start looking at solutions and fixes.
Hmm... Unfortunately I don't know who to assign that JIRA bug to.
Problem is - none of us own vehicle headunits that we can reproduce/test this problem on. I used to have a Sony MEX-BT2500 (technically I still do...) but since I sold my old convertible it just sits and collects dust.
I would agree that this will be a difficult one to find. It reminds me of working with 802.11b/g with it's dozens of "pre-draft" variants that just didn't interoperate properly.
If you wanted to dig into this yourself, the first place I'd look is https://github.com/omnirom/android_external_bluetooth_bluedroid and its upstream and parallel variants. That is the code that generally handles the upper-level Bluetooth management functions.
Edit -- Also worth looking at https://source.android.com/devices/bluetooth.html if you want an overview of how Android implements Bluetooth.
The comments on commits there might also be worth reading through. For example
https://github.com/omnirom/android_...mmit/73ce8ab2ddd30cab6499d0062c46b3a16f9130a9
Fact is however, that the use of SDP features value for peer_features
is new since Android 4.2 and breaks existing good behavior on a BMW
2005/E46 car kit (navi professional). This kit never asks for AT+CHLD
and never via AT commands suggests it supports 3WAY (although it seems
to have the flag set via SDP).
Not the same issue, but there might be clues of that nature in the commit messages.