[Q] Holden Cars / Bluetooth and HTC Desire - Desire General

Hi,
We have a company that is upgrading their fleet of cars to the latest Holden. The new Holden stereo has a touch screen setup that allows pariing with phones via Bluetooth.
I have tested the Android and it pairs fine, and I can make and receive calls.
However it won't allow me to view contacts or make calls from the contacts list.
The Holden Website ( http://www.holden.com.au/owners-info/bluetooth-and-devices/bluetooth-compatibility ) states that this is not possible with the HTC Magic (Android 1.6) but doesn't list any other Android phones. (Window Phones will do PBAP / Phonebook App no problems).
I was just wondering if anyone knows if this is a phone issue, and should work with future updates to the Android's ROM or if it's a Car issue and the HTC Desire will never work with these cars?
OR - is there anything that can be done to get the Android to allow the phones contacts to work with the car?
Cheers
Adam.

OK - Looks like the problem isn't just with Holden.
Came across this thread, and it would appear as though there is a problem with Android and the Bluetooth PBAP protocol.
http://code.google.com/p/android/issues/detail?id=8846

Related

TP2 / Kenwood BT Contacts Download Issue

I have a Kenwood KDC-MP642U car audio system with Bluetooth capabilities and I have my HTC Touch Pro 2 [t-mobile] successfully paired and working great with 1 annoying exception.
As soon as the units connect to each other the contacts / phone book start downloading from the phone to the Kenwood system which is fine, however..... after EVERY call the contacts download fully again making the phone barely usable [slow] until the full phone book is downloaded. [90 secs for 150 contacts]
There is no setting on the Kenwood unit to not allow automatic download... if the phone supports it.... it will download. I was told by sales rep that his Kenwood did that as well and just to live with it ? ? ? ? ? ?
I have tried to find the appropriate registry setting on TP2 to deny auto PBAP access and download and cant find any help on this...... any help would be greatly appreciated.
I have the same setup, and noticed it on my prior phone as well (Motorola KRZR K1). I believe that the phone is updating the "recent calls" list on the headunit. I know for me the second download is MUCH faster than the first.
I haven't seen any information about preventing the update download.
this should do the trick:
http://forum.xda-developers.com/showthread.php?p=3848325
Question: does it show up as one of the profiles under the bluetooth paired devices list?

Does Desire have rSAP (VW/Audi/Skoda) Nav

Hi all,
Anyone can confirm that Desire has a rSAP (remote Sim access)?
Some people are saying it doesn't work with their Nav, some say it is working.
Any one got it hooked up to their Vw/Audi/Skoda RNS Nav?
Looking to change from my TouchHD.
Cheers,
Android does not support the SAP/rSAP protocol. It may be that some people have it working on cars that use the HFP or HSP profiles.
Thanks mate, not good at all!!!
A little up now the phone's live...
Does it support rsap? is there any way to push contacts etc...?
I got an audi with a built in Bluetooth system, pairing ok, phone etc ok, but no possibilities with my desire to have rsap working
swissman said:
A little up now the phone's live...
Does it support rsap? is there any way to push contacts etc...?
I got an audi with a built in Bluetooth system, pairing ok, phone etc ok, but no possibilities with my desire to have rsap working
Click to expand...
Click to collapse
I also have the Audi built in BT system, and it works fine except that from what I've read about rSAP, I don't think it's working in that mode with the Audi.
The only difference (problem) I've been facing with my HTC phones vs. Nokia e71 is that the phone ring tone is not pushed to the car speakers when receiving a call. I was hoping it would work with the Desire as the default Audi BT ringtone is stupidly annoying.
Sorry off topic again, but I was wondering, are Bluetooth profiles generally defined by hardware or software? Or some by this, some by that?
Maybe you could check if it has another setting to retrieve data from the phone.
From what i know the new modules used in audi/vw/skoda are Novero modules (part of the nokia business) which only supports rsap.
The older modules are from harman/Becker and do support al the possible connectiontypes.
You can check which type you have under the passengers frontseat, the modules are build in under the seat, not in the radio.
If you have a Novero, tough luck. But you can always check on the local car junkyard if you can find an old car which does have a harman/becker, and build that one in
salahag said:
I also have the Audi built in BT system, and it works fine except that from what I've read about rSAP, I don't think it's working in that mode with the Audi.
The only difference (problem) I've been facing with my HTC phones vs. Nokia e71 is that the phone ring tone is not pushed to the car speakers when receiving a call. I was hoping it would work with the Desire as the default Audi BT ringtone is stupidly annoying.
Sorry off topic again, but I was wondering, are Bluetooth profiles generally defined by hardware or software? Or some by this, some by that?
Click to expand...
Click to collapse
Just wanted to add to eliminate any confusion. I can dial contacts saved on the phone and directly search for them on the car screen. But what I understood is that rSAP profile connects to the SIM card and fully replaces the phone, where it goes into some kind of sleep mode!
salahag said:
Just wanted to add to eliminate any confusion. I can dial contacts saved on the phone and directly search for them on the car screen. But what I understood is that rSAP profile connects to the SIM card and fully replaces the phone, where it goes into some kind of sleep mode!
Click to expand...
Click to collapse
Exactly... you can even read/send sms directly through the display and through your car multimedia system.
Ford
Just a little extra info, Desire now works with the Ford Convers+ system but ONLY on Android 2.1 Update1 (the stock Android 2.1 didn't work).
Just thought that may be why there's mixed reports of working/not working?
Tirinoarim said:
Just a little extra info, Desire now works with the Ford Convers+ system but ONLY on Android 2.1 Update1 (the stock Android 2.1 didn't work).
Just thought that may be why there's mixed reports of working/not working?
Click to expand...
Click to collapse
I got the stock Android and it's showing Android 2.1 update 1.... but not working ;-)
Hmm - well I'm trying to use my HTC Desire with a 2010 Audi A3 with BT and not having any luck so far. Although it paired and transferred the phonebook (took quite a few minutes with a couple of hundred contacts), it's now being really flaky and sometimes just refusing to connect at all. I tried un-pairing/re-pairing but to no avail. It just seems to work sometimes for a bit then stop again. By comparison pairing my Desire with a Jabra BT headset worked fine.
Anyone else having these problems? Anyone know of any updates for the Audi software? (if not I suppose I'll just need to wait for Froyo and hope that it fixes things )
my desire works well with my VW golf.
phone book, calls (dialing and receiving) and status dispay working. not working is SMS
Hey Folks,
there is room for some BT "education", because most people don't know the difference between rSAP and Handsfree.
Handsfree is working like a BT headset - most disadvantage - you are using the phoneunit of your mobile.
rSAP is using BT protocoll to get only the SIM card of your mobile and work together with the phoneunit of your car.
For Audi you can see on which mode your are conntected at the MMI-Display => "SIM card icon" stands for rSAP while "Mobilephone icon" represents handsfree mode.
no rSAP
I could be wrong, but I was of the impression that Nokia had patented the RSAP protocol, so you're not going to see it on non-Nokia phones. Irritating, really. Some car users have retrofitted their handsfree kits with a module that uses handsfree profile with some success but it's not going to use the car antennae etc in this case.
rSAP is a "STANDARD" for bluetooth protocoll in general.
Nokia was one of the first, thatswhy the Nokia unit has some "problems" in early releases....
Well I picked up my Skoda Superb last week, dealer told me they were fitting the new GSM 3 units that had just recently changed, not that it meant much to me.
Anyways it did work fine first couple days then started playing up with not connecting, I went into the options because I found it was connecting to media, but not phone, so I disabled the media option on the phone for the bluetooth connections and its been fine ever since.
Desire running Modaco R4, R5 & R6 now also ok.
Also saw a file posted on there that is meant to fix the iffy bluetooth connection problems, its been confirmed as working but I've not tried it as I've not had any more problems with it.
Will take a look though see if its connecting with a phone or sim card, I had noticed the signal always seemed really good even if the phone was berried in the car somewhere so maybe the rSAP explains it.
Tinyk said:
Also saw a file posted on there that is meant to fix the iffy bluetooth connection problems, its been confirmed as working but I've not tried it as I've not had any more problems with it.
Click to expand...
Click to collapse
Do you have a link to the thread that includes this file by any chance?
Do not mix up android 2.1 and 2.2.
AFAIK the modaco roms are froyo which should have a better bluetooth stack than eclair.
Well some good news! The FroYo/2.2 update on the Desire seemed to do the trick for me and I now seem to be able to get a stable BT connection with my A3. Phonebook transfer working fine too and it's reacquiring the connection when getting back into the car.
Any hope for Android 2.1?
Alanjrobertson: did you say you got your HTC Desire Android v2.1 phone working with your Audi, albeit a bit flaky? I cant get my HTC Desire Android v2.1 phone working with my VW EOS working at all.
What was the process you followed? The process I went through was to turn on phone’s bluetooth and make my phone discoverable. I then initiated a search from the car. It found my phone and displayed the correct name. However, when I chose the “connect” option on the car, it gave the error message: "mobile telephone phone is not compatible" on the car’s MFD.
Is this what you did? Is there a better way of connecting?
The car’s entertainment system is RNS510. I’m not sure if this is associated with Bluetooth or not.
My previous phone (Nokia 5800) worked OK, but my Desire doesn’t.
I am hoping that the Android v2.2 upgrade will fix my problems, but I’m still waiting for the update from Orange. It could take a while by the sounds of things.
I contacted HTC and they told me “The HTC Desire does not have the remote sim access profile. we currently have no plans to update the Bluetooth profiles on the device.” This makes me worried that when I eventually do get the Android v2.2 upgrade it will not work.
Any ideas other than waiting for the Android v2.2 upgrade?

rSAP Support In WP7?

Now that the European market has the WP7, has anyone here tried rSAP in their car? Please report back, thank you.
I was trying with a HTC Mozart to connect to my Volkswagen Tiguan's rSAP. No success (it says "Phone is not compatible" when trying to peer)
WP7 officially does not include the BT rSAP profile.. Current solution: Use WM6.5 device with 2nd SIM card... well...
Oh frack, that is why i was avoiding the Android as 1.6 and 2.1 supported rSAP yet 2.2 did not. Do American software developers realize there are people outside the States who use cars that need rSAP? Generally, these are very expensive cars too. Yes, i know there is the ability to insert a SIM card in my vehicle, yet that would have a different tele number and defeats the purpose of being available at a single # easily as with the Win 6.x phone currently here.
There are many thousands of complaints against the Android due to 2.2 not supporting rSAP, and here i was hoping MS would be a bit brighter than Google.
Will be trying the Samsung Focus and hopefully Samsung realizes rSAP is a necessity.
Android never supported rSAP in any build, only the Samsung Galaxy does, and it was Samsung not Google who did that, and rSAP is supported in Android 2.2 on Galaxy S.
I emailed HTC about WP7 rSAP support, and they were very clear that it does not! it is weird 'cause WM6.5 supports it.
Well... maybe (crossing fingers) the Samsung Focus has rSAP (still crossing fingers). And yes, Win 6.x supports rSAP nicely (even my HTC).
elibi said:
Android never supported rSAP in any build, only the Samsung Galaxy does, and it was Samsung not Google who did that, and rSAP is supported in Android 2.2 on Galaxy S.
I emailed HTC about WP7 rSAP support, and they were very clear that it does not! it is weird 'cause WM6.5 supports it.
Click to expand...
Click to collapse
Hi ..Have you actually tried the Galaxy S 2.2 with rSAP on a particular car system? I have an Audi and a Porsche and SGS 2.1 rSAP works fine with both of them but I read that the SGS Froyo 'leaked builds' from a couple of weeks ago didn't suport rSAP. Makes me kind of nervous about upgrading the firmware...
Yes, I have galaxy S and tried rSAP on both 2.1 and 2.2 on my VW GTI and it works perfectly. You need to copy your contacts to the sim card for the car to download it, there is an app that does that for you 'copy2sim'
rSAP is a bit of a throwback given modern phones don't store contacts on the SIM anymore.
Modern handsfree kits (e.g. Parrot) use OBEX.
Agree rSAP is a small throwback, yet many current European cars do indeed use it. While my car (from the VW Group) does work with the Samsung Focus, it is just HF and not rSAP so can not access ease of steering wheel choosing of whom to call
elibi said:
Yes, I have galaxy S and tried rSAP on both 2.1 and 2.2 on my VW GTI and it works perfectly. You need to copy your contacts to the sim card for the car to download it, there is an app that does that for you 'copy2sim'
Click to expand...
Click to collapse
Which build of 2.2 did you try? I have heard reports that rsap doesn't work on the Galaxy S after the official upgrade.
Just installed the VW 3C8035730A module to replace the rSap only 5N0035730C.
I have a HTC Touch HD that works as a rSap and a Iphone 4 that works as HF now. WP7 should should work i guess too. Full download of adressbook, media player and all that.
At least a solution for phones that do not support RSAP.
You can read my post here: http://briskoda.net/forums/topic/182537-installed-rns510-module-3c8035730a-rsap-bluetooth/
If only Mercedez-Benz offered a similar upgrade to the BT SAP module. The new Mercedez-Benz do have the same HFP/SAP functionality but I can't afford the £90k to upgrade my CL500 right now.
rSap and address book on Galaxy S
I purchased a Galaxy S to use with my Audio because my HD 2 kept dropping the connection.
Upgraded to the released build 2.2 and it works fine with rSap. And it downloads the address book from the phone (as well as the SIM).
Problem is the 2.2 build I have with an Exchange Active Sync connection runs the battery down in hours and the phone often locks up completely.
So the Rsap is great, OS features are great. But the implementation is useless.
Interesting to hear that there is an Active Sync connection, enabling the download of the phone's address book. Sadly I use the Google address book so IR probably won't work for me. Where is this found on the phone?
I always have the phone on a Brodit mount with charger for long journeys as Bluetooth is a battery killer.
Address Book
I don't think the Car Kit cares where the contacts came from.
It just asks the phone for an address book. So Any contacts on the phone should come down not matter how they got there.
I can't check if my Gmail contacts arrived as I had to change back to the HD2.
What's the Car Kit?
Car Kt
It's the factory Audi Full Phone Kit.
I think it is called Audi MMI 1638 but I don't know the part number.
It was an option at build on my RS5 which arrived last week.

[Q] bluetooth problem (with Parrot CK3100, logitech z715, and in general)

Hallo
First of all, my English is not the best because it's not my first language.
I have problems with pairing my Desire HD to an Parrot CK3100 and also problems with connecting it to an Logitech Z715. For your information the parrot and logitech are both working fine with other products.
I have an HTC Desire HD running Android Revolution HD 6.3.2 and using Radio 12.65.60.29_26.14.04.28_M as recommended by the rom.
Wel my question is What is wrong? Does anybody have suggestions for me what to do? I hope so.
Nils
nilsdeboer said:
Hallo
First of all, my English is not the best because it's not my first language.
I have problems with pairing my Desire HD to an Parrot CK3100 and also problems with connecting it to an Logitech Z715. For your information the parrot and logitech are both working fine with other products.
I have an HTC Desire HD running Android Revolution HD 6.3.2 and using Radio 12.65.60.29_26.14.04.28_M as recommended by the rom.
Wel my question is What is wrong? Does anybody have suggestions for me what to do? I hope so.
Nils
Click to expand...
Click to collapse
What is the problem you are having? I have stock ROM 2.3.5 with sense 3.0 and no issue with pairing with my parrot CK3100. Have you tried updating parrot firmware.
Sent from my HTC Desire HD A9191 using xda premium
yes parrot is up to date and the problem is that 99/100 times i try to search for a bluetooth device with my desire hd i can't find one. I said 99 of the 100 times because pairing with the parrot was successful once. but after 20 seconds of connection the connection was gone. so i deleted the device from the parrot and tried to pair again with no results.
Here a post of mine from another topic which indicates another issue but maybe will solve yours.
deechte said:
Well, Parrot support has been great so far. They have made me try a couple of different ways of pairing my device with the Parrot. In the end, my problem is solved my using a special paring mode. I go to Advance settings > Pair phone > and choose for the "Auto-pair no sync" option. No more crashing of the phone process on my Desire HD since.
Click to expand...
Click to collapse
But it is the auto-sync of contacts that causes com.android.phone to crash or not responding or in some cases just disconnects the device.
Besides if you disable this option you don't have any contacts in your address book in the CK3100.
As stated you can connect your phone without the auto-sync contacts option and then do the following to manual sync your contacts:
Alternately, any Bluetooth device that can send contacts can be used to populate your car kit phonebook. On the CK3100, allow the phone to connect automatically and then go to Settings -> Paired devices, Select your phone and then Select Disconnect. Press the Red button until you return to the main screen and verify the display shows your phone’s name with “DISCONNECTED” on the second line. In this mode, you can use other Bluetooth devices to send contacts to the kit and have them associated with your phone when connected. This phonebook will be available until the kit is updated, the phone pairing is deleted or the vehicle battery is disconnected.
Click to expand...
Click to collapse
Source: www.parrot.com
I first checked if there was a newer firmware version of the CK3100 and there is!
And this fixes all problems, after installing this version I just paired my phone and everything worked as it should, auto-syncing contacts working properly. No need to adjust anything.
http://www.parrot.com/nl/support/parrotck3100ck3300ck3500
I had version 4.18A so see below the fixes from that version or check:
http://www.parrot.com/documents/en/support/ck3100_notes_new.txt
Release notes - CK3X00
----------------------
List of changes:
----------------
Version 5.00
Available to download from www.parrot.com, the new software 5.0 of the CK3100 LCD brings significant improvements for the user:
- Synchronization of contacts and call log optimized: faster and more spread, with a new protocol built-in for better synchronization with iPhone in particular.
- Greater compatibility: interoperability and compatibility with all Bluetooth ® telephones and Smartphones, current and future.
- Simplified navigation: complete revision of the pairing menu for a more intuitive user interface.
Version 4.30
-[iPhone]: Allow to invert "name" and "first name" in the phonebook using the "Preferences / Display / sort order" menu
-[iPhone]: fix some connection loss cases during calls
-Fix bad menu sounds during phone synchronization
Version 4.23
- Fix bug of previous version : Microphone volume settings was not saved
Version 4.22
- Fix audio quality with phones Nokia 6700 and Nokia 6730c.
- Add three "Auto-pair" modes:
."Auto-pair no sync" : Pairing code is "0000" and no synchronization will be done (replacement for "Casio G'z One Boulder" pairing mode).
."Auto-pair with sync": Pairing code is "0000" and standard synchronization will be done.
."Auto-pair AT sync" : Pairing code is "0000" and synchronization is forced to "AT type".
- Add new menu "SE C902,C905": For Sony Ericsson C9xx series.
- Remove "Win CE" mode.
Version 4.21
- Fix ring tone issue with some phones: Nokia, Blackberry, etc...
Version 4.20
- Fix potential display issue during Bluetooth update
Version 4.19
- Better compatibility with phones: Nokia E51, Casio Boulder, Motorola U9
Version 4.18b
- Bug fix [Apple iPhone v2.1] 3rd incoming call: no audio
Good Evening
Sirs. and Thatrunks
Could you please send the software 5.0 of the CK3100 LCD file ? )
Cause, using the links, that have been posted - are not working already.
Probably cause - the source from official site is no more actual.
my e-mail
[email protected]

Bluetooth PBAP issue

I just got a new Wildfire S phone and I'm experiencing some issues with my Volvo carkit.
I can pair the devices and answering and making phone calls is working fine. The only thing I can't figure out is why my Phonebook sometimes is synchronizing and sometimes it isn't.
It seems that it works when I repair the devices and I ignore the accept phonebook access message on the phone. Only in this case the connection between the devices gets broken after a couple of minutes. If I accept the connection once, it seems to be working evenry now and then. As soon as I select always to connect to the phonebook (checkbox when I grant phonebook access on the phone), it seems that all contacts are no longer available in my car.
According to Volvo the wildfire S is certified to work, but with all other phones I don't have these issues.
Does anyone have an idea of where I should look for a solution to this problem?
Phone versions:
Android 2.3.5
Software version: 2.26.401.3
Smallbanversion: 47.23e.35.3038H_7.57.39.10M

Categories

Resources