Develop Bugs

Bluetooth Headphones Problem

I have an O2 XDA Mini S and have just purchased a pair of Motorola HT820 Bluetooth headphones. I have paired the two; however, I only get the Hands Free service (which works) but NO Wireless Audio. I have not installed any other software / drives and I am using WMP 10 Mobile to play the music.
Any help with this problem would be very much appreciated.
Thanks, Harold Clements

...Ok, I have been on this for about 4 hours now and I am starting to get a bit annoyed.
I clicked on Motorola HT820 and then went ‘Refresh’ and up popped ‘Headset’ so I ticked that and saved. I then clicked (and held) on Motorola HT820. The options that I get are Edit – Delete – Set as Hands Free. I think I should also have ‘Set as Wireless Stereo’ or something, but I don’t.
Please, has anyone any ideas?
Thanks, Harold Clements

Wirless Audio Hacks
I really could do with someone’s help!
I have read about the ‘hacks’ (zoad2p.cab, Tornado asdp, AKU2.6) but I am unsure:
a) if this is a solution to for problem / PDA.
b) what a hack is and why is it needed?
Please can someone help!

I don't know wich kind of PDA you have, as you can see everyone here calls their PDAs by their HTC's code name (mine is a universal), go to look the pictures of all the PDAs, find yours and search directly inside there, it will be much easier for you to find an answer.
One simple comment, your PDA has to have the Bluetooth high quality audio (is called be some PDAs in this way), see if your PDA does contain such feature, you have to activate it if you want to hear stereo audio, generally when you pair your phones for the first time, your PDA will show you the option already ticked, if you haven't see it, chances are that something is missing in your bluetooth profiles, go to your PDA's specific part of this forum and read, with patience and some luck, I'm sure you'll find whatever you need to get your PDA's stereo audio to work.
Most of the cases, are just the lack of the profiles or even installing another BT stack.
good luck

Thanks...
Thank you very much for your advice / reply, it was very much appreciated. It seems that my PDA is a Wizard. I will indeed search that part of this forum.
Thanks again,
Harold Clements

I don't think your phone supports A2DP profile. Correct me if I'm wrong.

Neither do i know if his phone supports it, I use to have an Ipaq 6340, it suppose that it didn't supported A2DP but with an BT stack extracted from another PDA (don't remember wich one) it worked, it didn't worked very well, it dropped audio more or less each 30 seconds for 2 seconds, someone said at that time that was processor lack of power -I didn't agree with this-, but I did no further investigation.
As far as I've understood, the main bottleneck for stereo profiles (or any deamanding profile in BT) is the radio, of course, if We don't have access to the manufacturers good information, good tools, much time and even more will is very hard to find a solution to anything, most of us do not spend lots of time with this things -it's not easy for anyone with a "normal" life-, and I'm not complaining!
It's just fine for me, the whole thing it's quite enjoyable like this, some more time spent in this way and it would become a second work.
So, may us have fun and keep an excellent forum up.

haroldjclements said:
I have an O2 XDA Mini S and have just purchased a pair of Motorola HT820 Bluetooth headphones. I have paired the two; however, I only get the Hands Free service (which works) but NO Wireless Audio. I have not installed any other software / drives and I am using WMP 10 Mobile to play the music.
Any help with this problem would be very much appreciated.
Thanks, Harold Clements
Click to expand...
Click to collapse
on the front page not 2 rows (at the moment) below this thread in really big bold letters
MOTO HT820 SKIPPING SOLVED! NEW FIRMWARE INSIDE!
which covers the issues and varioius fixes (if any) for most phones.

To be truthful, I know very little about what I am trying to do. All I know is that I can’t get the music side of the Motorola headset working.
As I said in my previous post: I have an O2 XDA Mini S (Wizard) and have just purchased a pair of Motorola HT820 Bluetooth headphones. The two paired but I only get the Hands Free service but NO Wireless Audio. I clicked on Motorola HT820 and then went ‘Refresh’ and up popped ‘Headset’ so I ticked that and saved. I then clicked (and held) on Motorola HT820. The options that I get are Edit – Delete – Set as Hands Free. I think It should also have ‘Set as Wireless Stereo’ but It don’t.
I have read about the ‘hacks’ (zoad2p.cab, Tornado asdp, AKU2.6) but I am a) unsure if this is a solution to my problem, and b) what a hack is and why is it needed?
I just really want to know how to fix my problem.
Thanks for your help,
Harold Clements

a hack is getting a device which dont support a feature to do it anyway
if htc dident make your device to support a2dp == bluetooth stereo
you maybe be able to get it to do it anyway using a hack
if any hacks works for your device
as it differs
bluetooth support is never support for all profiles bluetooth have
plus there are bluetooth version 1 - 1.1 - 1.2 and 2.0

haroldjclements said:
To be truthful, I know very little about what I am trying to do. All I know is that I can’t get the music side of the Motorola headset working.
As I said in my previous post: I have an O2 XDA Mini S (Wizard) and have just purchased a pair of Motorola HT820 Bluetooth headphones. The two paired but I only get the Hands Free service but NO Wireless Audio. I clicked on Motorola HT820 and then went ‘Refresh’ and up popped ‘Headset’ so I ticked that and saved. I then clicked (and held) on Motorola HT820. The options that I get are Edit – Delete – Set as Hands Free. I think It should also have ‘Set as Wireless Stereo’ but It don’t.
I have read about the ‘hacks’ (zoad2p.cab, Tornado asdp, AKU2.6) but I am a) unsure if this is a solution to my problem, and b) what a hack is and why is it needed?
I just really want to know how to fix my problem.
Thanks for your help,
Harold Clements
Click to expand...
Click to collapse
The zoia a2dp hack (zoa2dp.cap) is what you need, it will give you "Set as wireless stereo" but be prepared for pretty bad skipping, that has not yet been solved for all of wizards.
Also if you flash to a custom rom (Like Molski's 2.26 it'll have the patch automatically.)

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?

Bluetooth A2DP on my Tilt2: WORTHLESS AS $H!T

Ok, so I finally got into the smartphone game to get a better music streaming experience. MFRadio and MFScorn just weren't cutting it for me anymore. I hated the skips and the ridiculously long (and repeated) buffering time. So I first looked at Android phones but went with WinMo because they say you can run both OS's with WinMo (and the only Android offering from AT&T has a 12-hour standby time before the battery dies, according to reviews).
I have a Bluetooth head unit and have had over a dozen phones paired with it. This phone however is a completely different story. I have installed the latest "release" from AT&T (from a thread on this site). At first I tried streaming with the bundled Windows Media Player which apparently doesn't stream anything at all (with both the bundled and downloaded releases of the OS), then downloaded TCPMP. TCPMP is everything I have ever dreamed of in a streaming media player, but the only problem I have with it is that it won't connect to a stream unless I have already opened up a browser window and went to a website. Not the end of the world.
So, I get in my truck and initiate pairing to the phone. It sees the head unit as a Hands-free and as Stereo Audio. I can get it to connect for a split second and then it dies. I get a popup notification that tells me that the phone cannot control volume when paired to the bluetooth device and audio must be adjusted from the device itself. Fine. But then it doesn't work at all. At first, I wanted to blame TCPMP until I realized that nothing at all was working with the head unit. I think I got it to work once but it never worked again.
So is there any way to fix this problem? This is the one thing I wanted working on my new phone. Yes, the notifications that my texts were successfully sent are very annoying (as well as the other notifications), and yes, Windows Media Player for Mobile is useless, but the fact that I can't stream Bluetooth audio on this phone really makes this phone worthless to me. Didn't anyone bother testing this stuff before releasing this garbage? The Tilt is a paperweight to me right now because it can't do the one thing I want it to do the most. I might as well go back to my Sony Ericsson W760a at this point!
What can I do? I have not yet unlocked anything (although I have a SIM unlock code waiting) and have not yet flashed Hard-SPL. My phone has Bluetooth for Windows Mobile Version 1.9.2 Build 600 HCI Version 4.84. I'd do anything at this point to get this working. Windows Mobile is not that precious to me either. PLEASE HELP!

e-thug said:
Ok, so I finally got into the smartphone game to get a better music streaming experience. MFRadio and MFScorn just weren't cutting it for me anymore. I hated the skips and the ridiculously long (and repeated) buffering time. So I first looked at Android phones but went with WinMo because they say you can run both OS's with WinMo (and the only Android offering from AT&T has a 12-hour standby time before the battery dies, according to reviews).
I have a Bluetooth head unit and have had over a dozen phones paired with it. This phone however is a completely different story. I have installed the latest "release" from AT&T (from a thread on this site). At first I tried streaming with the bundled Windows Media Player which apparently doesn't stream anything at all (with both the bundled and downloaded releases of the OS), then downloaded TCPMP. TCPMP is everything I have ever dreamed of in a streaming media player, but the only problem I have with it is that it won't connect to a stream unless I have already opened up a browser window and went to a website. Not the end of the world.
So, I get in my truck and initiate pairing to the phone. It sees the head unit as a Hands-free and as Stereo Audio. I can get it to connect for a split second and then it dies. I get a popup notification that tells me that the phone cannot control volume when paired to the bluetooth device and audio must be adjusted from the device itself. Fine. But then it doesn't work at all. At first, I wanted to blame TCPMP until I realized that nothing at all was working with the head unit. I think I got it to work once but it never worked again.
So is there any way to fix this problem? This is the one thing I wanted working on my new phone. Yes, the notifications that my texts were successfully sent are very annoying (as well as the other notifications), and yes, Windows Media Player for Mobile is useless, but the fact that I can't stream Bluetooth audio on this phone really makes this phone worthless to me. Didn't anyone bother testing this stuff before releasing this garbage? The Tilt is a paperweight to me right now because it can't do the one thing I want it to do the most. I might as well go back to my Sony Ericsson W760a at this point!
What can I do? I have not yet unlocked anything (although I have a SIM unlock code waiting) and have not yet flashed Hard-SPL. My phone has Bluetooth for Windows Mobile Version 1.9.2 Build 600 HCI Version 4.84. I'd do anything at this point to get this working. Windows Mobile is not that precious to me either. PLEASE HELP!
Click to expand...
Click to collapse
Hmmmm .... I don't believe you ever stated what type of headset you are trying to get working here? I find your problem to be very strange, even though WinMo does seem to be lacking in a lot of different areas, audio streaming via bluetooth stereo headset is definitely not a problem I have encountered. It even streams flawlessly through my 5.1 hooked to my pc via a crappy 8 buck bt dongle and still sounds excellent. Have you considered that the problem may lie with your bt headset itself?
Also, when you say that you installed latest "release" from AT&T (from a thread on this site), what exactly do you mean? I am running the "unofficial" leaked rom from AT&T on mine and I just paired my Motorola S9 stereo headset and it is playing great for me. You also may want to try using some different software, give S2P (Slide 2 Play) a try and see if you have different results. That's what I am using right now, but I have used TCPMP to play a few xVids through my headset and have had no problems.

The problem is not in the head unit. 25 other phones can't all be wrong. I have no problem using my bluetooth headset. That is probably why you don't see the problem. Anything more complex than a headset will not work with this release. The problem lies within the phone as soon as it displays a notification (which, of course I cannot disable) which reads, "The connected Bluetooth headset does not support volume adjustment from the device. Adjust volume on the headset itself."
That message is the kiss of death. So basically any Bluetooth head unit will not work with this phone? Sounds like shoddy programming to me. Yes, I am using the "leaked" release. I really don't think this release will ever see the light of day. Its horrible! You cannot disable notifications (I don't need to know when my text messages were sent successfully), and it looks like whenever I get a system notification, any program I am using crashes immediately. Like I said before, as soon as I get a notification, I lose the Bluetooth connection (which is like a split second before the notification comes up). I highly doubt this "leaked" copy will ever see the light of day, officially (unless AT&T and HTC do absolutely zero testing on it).

A little clarification for those who don't know... when I say "head unit" I'm talking about a Bluetooth-enabled car stereo and when I say "headset" I mean a Bluetooth headset

My Tilt 2 works absolutely fine with all my BT devices, including 2 Motorola headphone sets and my Sony Xplod head unit in my truck.

e-thug said:
A little clarification for those who don't know... when I say "head unit" I'm talking about a Bluetooth-enabled car stereo and when I say "headset" I mean a Bluetooth headset
Click to expand...
Click to collapse
I was mis-understanding you about the head unit, I did think you were talking about a headset. Sorry bout that, my Mustang doesn't have built-in BT so I have to use a Motorokr t505 for those chores. It works well but it does give me the same message that you are getting about "volume can't be cotrolled etc" but I can dismiss it and carry on without any problems.

but the fact that I can't stream Bluetooth audio on this phone really makes this phone worthless to me. Didn't anyone bother testing this stuff before releasing this garbage? The Tilt is a paperweight to me right now because it can't do the one thing I want it to do the most. I might as well go back to my Sony Ericsson W760a at this point!
Click to expand...
Click to collapse
Since you don't need your phone for calls, just get Sirius or XM. Ya know, considering you only stream music through the phone..

Did you try the BT headset or head unit with the original stock ROM before you flashed the "leaked official" ROM?
Seems like you might have a couple random issues, with the BT issues and the system notifications crashing programs. I haven't flashed the leaked ROM, but I do know that many random issues with cooked ROMs can often be cleared up by running Task29, which completely wipes the phone memory before you flash a new ROM. I think you will need to HardSPL before you run Task29. Might be worth a try, sometimes fragments of the old ROM interfere with the new one, and cause some bugs.

Bluetooth protocols can be implemented differently by different manufacturers.
I know of many people including myself who have NO PROBLEM with the tilt 2 and different Bluetooth products INCLUDING car radios.
I am using the "new" AT&T ROM and have no difficulties.
Clearly your pissed but your subject is wrong. I would suggest changing to "Worthless as $HIT to ME"

I think my problem is that I am getting notifications which seem to be killing my connection. Is there a way to turn all notifications OFF? The only ones I care about are missed calls, incoming SMS and maybe a birthday. I would like to try to kill the notifications first because I think this may solve my problem

You can get yourself a free reg editor (like Total Commander) and apply the following tweaks to modify the notifications:
SMS sent notification: http://www.mydigitallife.info/2008/06/24/enable-or-disable-the-sms-text-message-sent-notification-bubble/
Other notifications: http://www.mydigitallife.info/2008/06/24/tweak-and-configure-how-notifications-work-in-windows-mobile-notifications/
Although, this sounds like a band-aid just hiding a deeper problem. What you are describing is not typical behavior, and this is something else going on.

redpoint73 said:
You can get yourself a free reg editor (like Total Commander) and apply the following tweaks to modify the notifications:
SMS sent notification: http://www.mydigitallife.info/2008/...he-sms-text-message-sent-notification-bubble/
Other notifications: http://www.mydigitallife.info/2008/...cations-work-in-windows-mobile-notifications/
Although, this sounds like a band-aid just hiding a deeper problem. What you are describing is not typical behavior, and this is something else going on.
Click to expand...
Click to collapse
Thanks I will try these out and report back
For the record my head unit is a JVC KD-BT11 and I have never had any kind of problem pairing any other phone

Somebody else just posted a very similar issue, and found the app hAndyUtils to be helpful:
http://forum.xda-developers.com/showthread.php?t=741311
I think hAndyUtils might just be a app-based way to make the reg edits I posted earlier. But give it a try.

I scanned through the topic and did not see anyone mention this so I thought I would add my .02. The Tilt 2 is different than many other WM phones when it comes to bluetooth as it contains the Widcomm BT stack instead of the MS stack. (Just as an aside, on all my past phones, there were people bemoaning the the fact that it had MS, and trying to replace it with the Widcomm, so I am getting a real chuckle out of folks complaining about the Widcomm and wishing for MS )
In any case, the utilities (Blue music toggle etc...) that used to work for me to toggle between streaming in stereo and plain phone qulity no longer work. However, all my stereo headsets (I own three different brands/pairs) all work perfectly with the Tilt 2. And stay connected and streaming all day.
By the way, coming on a forum that is full of people helping each other and using profanity, anger and threats, is not the most conducive way to get your questions answered. The odds are that the problem you are having is already solved somewhere among the 6+ million posts in this forum. I do not know where or I would post it for you, but it is probably out there. Good luck. And if you find it, please post the link to the answer back here so that other serchers will find it too.

maybe it can come from the phone itself
i had a rhodium for almost a year and never got my motorola headset ht820 to work well enough for me to use it... (more skips than music...cant move my head without a skip)
i flashed to a NRG rom before trying my headset...i tried eveything as far as ref setting, different radios...even flashed my ht820...
no improvement...
then my phone fell in water not so long ago...got another rhodium same model (european)...and it worked perfect out the box on stock rom i can go in a different room than my device and still hear music with no skips...and it still does with nrg rom and latest radio...
so my guess is maybe some actual devices have bad bluetooth hardware ???

I have the Motorola S9 and the HT820 and both work absolutely fine on my Tilt 2.

yatrg said:
I scanned through the topic and did not see anyone mention this so I thought I would add my .02. The Tilt 2 is different than many other WM phones when it comes to bluetooth as it contains the Widcomm BT stack instead of the MS stack.
Click to expand...
Click to collapse
Can I change my Bluetooth stack to MS? I have installed Hard-SPL and have experimented with cooked ROMs to no avail.
I sent the phone back to AT&T, went to Trinidad & Tobago for a few weeks and came home to a new Tilt 2 waiting at my doorstep (which could have been stolen by anyone!) and I am still having the same problem. So I guess I sent back a perfectly good phone!
I would love to try some different Bluetooth stacks if possible. Where do I go from here?

e-thug said:
Can I change my Bluetooth stack to MS? I have installed Hard-SPL and have experimented with cooked ROMs to no avail.
I sent the phone back to AT&T, went to Trinidad & Tobago for a few weeks and came home to a new Tilt 2 waiting at my doorstep (which could have been stolen by anyone!) and I am still having the same problem. So I guess I sent back a perfectly good phone!
I would love to try some different Bluetooth stacks if possible. Where do I go from here?
Click to expand...
Click to collapse
Did you ever try the solution in this thread? It fixed a lot of issues people were having with bluetooth car kits. Maybe it will work for you: http://forum.xda-developers.com/showthread.php?t=591322
The solution source is here: http://www.everythingwm.com/forum/moto-q-9c/q9c-and-infiniti-g35x-bluetooth-problem-16833-4.html
And here is the solution. You need a registry editor to do this:
1. Modify the HandsFree plug-in:
HKLM\Software\WIDCOMM\Plugin\HandsFree
i. Change SupportedFeatures to 45 (default is 1135)
ii. Add value HFBDA binary, set to same value as LastConnectedBda
iii. Add value HFDeviceType decimal 2
2. Modify the WIDCOMM bluetooth general settings:
HKLM\Software\WIDCOMM\BtConfig\General
i. Change bdaddr to (no value)
ii. Change (or add if not there) DisableReopenAudio to 0 (default is 1)
3. Reboot device
You may also want to do the A2DP quality registry edit: Add a DWORD value of LineSpeed to HKLM\Software\WIDCOMM\Plugin\AV\ with a value of 320.
Give it a try, it may work for you.

I will give this a try and report back. Thank you very much for the response!

No luck. And my bdaddr keeps resetting to a binary value when I reset the phone

BT audio in my car...

I've just got a new (to me) car & BT isn't playing fair... It seems to be a known issue, but I'm keen to get it working...
The phone functions are working fine, but the music/audio function isn't. BT audio isn't showing up in the cars interface, nor on my HTC 10 when connected.
Is there a way to add more profiles or make the phone more visible to other BT devices. The issue is 100% with the car & it probably doesn't support enough protocols, but I'm hoping there's a useful app to help...

bluefoam said:
I've just got a new (to me) car & BT isn't playing fair... It seems to be a known issue, but I'm keen to get it working...
The phone functions are working fine, but the music/audio function isn't. BT audio isn't showing up in the cars interface, nor on my HTC 10 when connected.
Is there a way to add more profiles or make the phone more visible to other BT devices. The issue is 100% with the car & it probably doesn't support enough protocols, but I'm hoping there's a useful app to help...
Click to expand...
Click to collapse
Make and model of car?
I had a similar issue with a BMW and my wife's PRIV.
Had to update the BMW software. They had it on their website for download and install.
Sent from my HTC 10 using XDA-Developers mobile app

The car's a Porsche Cayman. I'm not sure there's a firmware update available... Feckin cheap German engineering!

My last car was a 2009 Nissan Altima and it had a horrible BT stack. I had to do some workarounds to even get a call to work properly. Newer cars seem to do much better these days.
Like Anandlal suggested, I'd take a look and see if there are any firmware updates for your car. Some makers have them available for download and make it easy to do yourself (Ford comes to mind here). Others may require an update to be applied at the dealer, and that might incur a charge. If they have to do it, you may want to have it done with an oil change or other service to minimize cost and inconvenience.
I feel for you. Cars can be picky and if you get a lazy manufacturer that doesn't update their stuff, you're SOL. I'd hope that for they'd take good care of you considering what you paid for that Porsche.
Good luck!

Alternate BT that can connect to XGPS160? [Rockchip PX5 A53 | Android 9.0 | 4GB RAM]

(@Admins I think this is the correct forum to post this in, but please feel free to move it if I've chosen the wrong forum. I'm still figuring out exactly what category my device is in)
TL;DR - Trying to figure out if it's possible to get an external USB Bluetooth dongle working on my radio instead of the built-in one, so I can connect to all types of bluetooth devices, not just streaming audio
Hi all,
I'm searching for a possible solution that would allow me to connect my Android radio (AUTOPUMPKIN AA0495B, using a PX5, MCU CSN2_06252019_163051) to a Dual XGPS160 device. I installed this stereo in my track car for the purpose of running Harry's Lap Timer; currently the app is running perfectly, with a wired OBDLink EX in use for OBDII data and also connecting to a GoPro via WiFi to control the camera. The last piece of the puzzle is I want to get an XGPS160 connected for better GPS data capture (10Hz vs 1Hz of the radio's GPS). After hours spent trying to get it to pair and connect to the device, I emailed AUTOPUMPKIN support and they confirmed that this radio cannot connect to such devices, as the Bluetooth module in the radio is essentially a glorified bluetooth headset and can only connect for streaming audio (I haven't been able to determine the model number of the bluetooth module it uses). My hope is there is a USB Bluetooth dongle that I could plug into the radio and then have the radio use that instead, which would then allow it to connect to the XGPS160 (and any other type of bluetooth device).
When I go into the Car Settings on the radio, it has the following options available for bluetooth:
IVT i140
IVT i145
FC6000TN
GOC_BC5
KD6
KD6 is what is selected from the factory. Please correct me if I'm wrong, but my understanding is this list is basically the different bluetooth hardware models the radio has driver support for? If I'm correct on that, then I'm also guessing if I were to plug in a bluetooth dongle using one of the other models and change this setting, the radio would use that instead of the built-in bluetooth? I don't use the bluetooth audio streaming or phone tethering feature, so I don't care if I lose those features if it allows me to connect the radio to the XGPS160. As long as the WiFi keeps working I'm ok with it.
Sorry if I'm asking any stupid questions; I'm a programmer by background, but even after hours of reading this forum my knowledge about the hardware in these Android radio units is still very limited. That being said, I'm not opposed to modifying config files to get this working. I have Android Developer mode enabled and I can connect to the radio via ADB; I spent some time looking at the file structure and various config files so modifying those if needed shouldn't be a problem for me.
thanks!

There was another (lengthy) thread on the subject of bluetooth dongles around here somewhere. You will have to do a search for it. If I remember correctly you had to open your head unit and physically disconnect your original bt module... and even with that there was limited success in getting the thing to actually work....and of those who claimed they did get it to work also said they couldn't get anything more to connect to the dongle than what the original BT could handle
It's too bad too. I have a sound processor on my system which uses an app through BT on my phone to make adjustments and I was HOPING it would connect to the head unit. It won't
BTW... your obdlink ex usb will also work with Torque (Pro). I use it with torque and it's blazing fast and reliable.... a lot more than a BT connection!

deja100 said:
(@Admins I think this is the correct forum to post this in, but please feel free to move it if I've chosen the wrong forum. I'm still figuring out exactly what category my device is in)
TL;DR - Trying to figure out if it's possible to get an external USB Bluetooth dongle working on my radio instead of the built-in one, so I can connect to all types of bluetooth devices, not just streaming audio
Hi all,
I'm searching for a possible solution that would allow me to connect my Android radio (AUTOPUMPKIN AA0495B, using a PX5, MCU CSN2_06252019_163051) to a Dual XGPS160 device. I installed this stereo in my track car for the purpose of running Harry's Lap Timer; currently the app is running perfectly, with a wired OBDLink EX in use for OBDII data and also connecting to a GoPro via WiFi to control the camera. The last piece of the puzzle is I want to get an XGPS160 connected for better GPS data capture (10Hz vs 1Hz of the radio's GPS). After hours spent trying to get it to pair and connect to the device, I emailed AUTOPUMPKIN support and they confirmed that this radio cannot connect to such devices, as the Bluetooth module in the radio is essentially a glorified bluetooth headset and can only connect for streaming audio (I haven't been able to determine the model number of the bluetooth module it uses). My hope is there is a USB Bluetooth dongle that I could plug into the radio and then have the radio use that instead, which would then allow it to connect to the XGPS160 (and any other type of bluetooth device).
When I go into the Car Settings on the radio, it has the following options available for bluetooth:
IVT i140
IVT i145
FC6000TN
GOC_BC5
KD6
KD6 is what is selected from the factory. Please correct me if I'm wrong, but my understanding is this list is basically the different bluetooth hardware models the radio has driver support for? If I'm correct on that, then I'm also guessing if I were to plug in a bluetooth dongle using one of the other models and change this setting, the radio would use that instead of the built-in bluetooth? I don't use the bluetooth audio streaming or phone tethering feature, so I don't care if I lose those features if it allows me to connect the radio to the XGPS160. As long as the WiFi keeps working I'm ok with it.
Sorry if I'm asking any stupid questions; I'm a programmer by background, but even after hours of reading this forum my knowledge about the hardware in these Android radio units is still very limited. That being said, I'm not opposed to modifying config files to get this working. I have Android Developer mode enabled and I can connect to the radio via ADB; I spent some time looking at the file structure and various config files so modifying those if needed shouldn't be a problem for me.
thanks!
Click to expand...
Click to collapse
No; it must be a specific BT type MD725 realtek device. No, you cant connect all manner of devices due to the hacked BT implementation.

Bob_Sanders said:
There was another (lengthy) thread on the subject of bluetooth dongles around here somewhere. You will have to do a search for it. If I remember correctly you had to open your head unit and physically disconnect your original bt module... and even with that there was limited success in getting the thing to actually work....and of those who claimed they did get it to work also said they couldn't get anything more to connect to the dongle than what the original BT could handle
It's too bad too. I have a sound processor on my system which uses an app through BT on my phone to make adjustments and I was HOPING it would connect to the head unit. It won't
BTW... your obdlink ex usb will also work with Torque (Pro). I use it with torque and it's blazing fast and reliable.... a lot more than a BT connection!
Click to expand...
Click to collapse
Yeh I found that threat in my searches, but no one in there quite mentioned this specific scenario (Selecting one of the other options in the Bluetooth settings) so I wasn't sure. And I'm definitely not opening up the unit and cutting on the hardware; hacking config files I can do all day long, but I have no skills when it comes to soldering so I'd probably just destroy the radio in the process of trying to cut that module :laugh:
Yeh I've run the OBDLink EX with Torque as well for data logging temps on track and it worked flawlessly for that as well. BT is definitely more convenient, especially since most are running apps from their phones, but if you have a dedicated radio like these then it's a no-brainer to permanently wire up a USB device.

marchnz said:
No; it must be a specific BT type MD725 realtek device. No, you cant connect all manner of devices due to the hacked BT implementation.
Click to expand...
Click to collapse
When you say "hacked BT implementation" I'm assuming you mean they don't use the standard Bluetooth stack built into the Android OS? That would make sense, as when I try to do anything with bluetooth from the standard Bluetooth settings menu, it doesn't do anything, doesn't see any devices available for pairing, or anything else. You can only see other devices and pair to them from the PUMPKIN Bluetooth app; the funny thing is it will go through the first steps and show the XGPS160 as being paired, but none of the apps that use the GPS actually see it as a paired device (my OBD dongle shows up, but not the GPS).
I don't understand why they didn't just use standard bluetooth that's already part of the OS, rather than use some hacky custom solution

Quick update since the last post. Spent some time tonight on google looking up the information I could find on those other bluetooth modules in the list of options on my stereo. Based on technical manuals and FCC documents, it appears the FC6000TN and BC5 are audio-only bluetooth chips that only support A2DP profile (basically the same as what I have now with the KD6); Now the IVT i140 and IVT i145 on the other hand appear to be full fledged bluetooth chips, and do support the SPP (Serial Port Protocol) that is needed by the XGPS160 (and many other bluetooth profiles) so in theory that would work. Unfortunately after searching for both of those, all I can find are ones in bare module form (i145 and i140) that would have to be soldered onto the board (assuming the pins are even compatible) and there are no USB versions of them that I could just plug in to my radio's free USB-A slot. The only thing even remotely close that comes up in Google in USB form is this adapter and I'm pretty sure it's not based on the i140 or i145.
Given that my soldering skills are non-existent, it seems I'm pretty much out of luck on getting this to work. Disappointing for sure, as I would gladly have paid more $ for the unit to come with a fully functional bluetooth module instead of this hacked audio only junk they put in it :/

deja100 said:
Quick update since the last post. Spent some time tonight on google looking up the information I could find on those other bluetooth modules in the list of options on my stereo. Based on technical manuals and FCC documents, it appears the FC6000TN and BC5 are audio-only bluetooth chips that only support A2DP profile (basically the same as what I have now with the KD6); Now the IVT i140 and IVT i145 on the other hand appear to be full fledged bluetooth chips, and do support the SPP (Serial Port Protocol) that is needed by the XGPS160 (and many other bluetooth profiles) so in theory that would work. Unfortunately after searching for both of those, all I can find are ones in bare module form (i145 and i140) that would have to be soldered onto the board (assuming the pins are even compatible) and there are no USB versions of them that I could just plug in to my radio's free USB-A slot. The only thing even remotely close that comes up in Google in USB form is this adapter and I'm pretty sure it's not based on the i140 or i145.
Given that my soldering skills are non-existent, it seems I'm pretty much out of luck on getting this to work. Disappointing for sure, as I would gladly have paid more $ for the unit to come with a fully functional bluetooth module instead of this hacked audio only junk they put in it :/
Click to expand...
Click to collapse
Unfortunately, It wouldn't matter which BT you use from the supported BT types, BT implementation is non-standard to do stuff like act as a BT hands-free.

marchnz said:
Unfortunately, It wouldn't matter which BT you use from the supported BT types, BT implementation is non-standard to do stuff like act as a BT hands-free.
Click to expand...
Click to collapse
Yeh, that's extremely disappointing Does anyone know of any Android based radio units that have full working bluetooth? I don't mind buying a new unit for the car if I know it will work with everything.

The old intel sofia units (mtcd as well) had the bluetooth & wifi ibtegrated into the soc...and they had a standard (or at least more profiles) implemented
Enviado desde mi SM-G975F mediante Tapatalk

ikerg said:
The old intel sofia units (mtcd as well) had the bluetooth & wifi ibtegrated into the soc...and they had a standard (or at least more profiles) implemented
Enviado desde mi SM-G975F mediante Tapatalk
Click to expand...
Click to collapse
Bummer they don't make those units anymore :/ Then again, they may not have been powerful enough to run my track timer apps anyway.