Related
I've searched around for this and can't find anything, so maybe someone can help to point me in the right direction or let me know that at least the problem is known but not fixed yet.
I can't get Wifi and Bluetooth to work on my 8525 with WM6, currently using Schap's 3.54c rom and radio version 1.48.
I have motorola s805 stereo bluetooth headphones and would like to stream radio over my work's wifi and hear it on my headphones.
The problem is Neither wifi or bluetooth work reliably when used at the same time, (no problems individually). I have even tried reducing the bit pool, but can't take it below 24 because it sounds to bad then, but it still doesn't work.
Anyone have any ideas or can at least verify you have the same problem?
I have the same issue when trying to play internet radio over wifi with my ht820 a2dp linked to the jasjam (Sleuths v2 rom). The only time i ever got a2dp and wifi streaming to work was with the widcomm bt driver that is now extinct.
Thus i have come to the conclusion that the problem is not with the hw but has more to do with the standard ms bt stack.
If anyone has found a workaround please do share
Thats a start
Thanks, that is helpful.
I remember seeing a widcomm stack thread....
http://wiki.xda-developers.com/index.php?pagename=Hermes_Widcomm_stack
I'm going to check that out, also if there is a specific rom that comes with the widcomm stack I'd be interested to know.
I find that with bluetooth turned on I can associate to my Cisco AP at all. As soon as I turn Bluetooth off it works fine.
I had hoped my issue was due to the way the particular WM6 was put together but now Im using offical Dopod and it is the same.
Widcomm stack
Well I found this
http://www.htc-devs.com/uploads/Univ...m_bt_stack.CAB
at the end of the Widcomm stack for Hermes development thread.
I'm not sure where it came from, but I installed it and so far I can use IE while connected to my home wireless network, and listen to music on my headphones.
The com manager will not show bluetooth as being on, but go to settings-bluetooth and you can re-pair.
Currently I'm getting some hiccups, but its working at least. I'll keep you updated and I would still like to see a rom that incorporates this stack so that the com manager works right.
It also changes the headset icon on the top bar.
Streaming!
I'm streaming SomaFM with no problems!
AVRCP problems
I didn't notice this at first, but after the widcomm stack has been installed the AVRCP functions don't work... so Im going back.
AVRCP
It works in WMP, just not audiomanager anymore.
Bricking Blog
Pretty much what this thread has turned into.
If you install that cab above, don't uninstall it, you'll get bricked.
helpful reading
I have the Motorolla S9 bluetooth A2DP stereo headset.
I also have the Hero currently running VillainROM 3.4 but I've been trying to run a bt connection for A2DP media playback with almost all Android 2.1 ROMS with same results.
The phone pairs fine but once I start playing any mp3 headset disconnects and reconnects at random.
I should mention that bluetooth works great in my car with the stock stereo system for simple phone calls.
I searched the entire forum but couldn't find anyone else with this issue ... Modaco 3.1 people report bt stereo playback to be working fine .. I think this is a 2.1 issue as VillainROM 3.3 and 3.4 and BeHero and other 2.1 based roms have this issue.
please HELP
Hello rafynet
i had same problem and i have solved with this method:
your phone must be rooted
there is a file in /etc/bluez/audio.conf
copy that to your pc.Change the lines
from
-----------------------------
Enable=Source,Control,Sink
Disable=Headset,Gateway
-----------------------------
to
-----------------------------
Enable=
Disable=Headset,Gateway,Source,Control,Sink
-------------------------------------------
save it.
copy the changed file back to /etc/bluez/
I have tried this solution in all rom that i have tested and all work well for me, watch the entire article:
Issue 3960: Bluetooth issues with car systems in Android 1.5 / 1.6
I'm sorry, i can't post this link on forum!!
search it in google.
sorry for my english!
I'm waiting your feedback!!
I hope this solution works well for you. Try this!
your solution helped a little bit ... but bluetooth connection still drops and re-connects all the time ... it's very annoying.
I'm fairly sure this will be fixed when we get the official Hero 2.1 update.
I had noticed the same thing with my Motorola T505 ROKR handsfree adapter. Worked fine in 1.5, but in 2.1 it would disconnect every 30 seconds or so, then reconnect.
However... I've just got a new car stereo (Pioneer DEH-P6100BT) and it actually works *BETTER* in VillianROM 4.0 than it did in Modaco 3.2. In Modaco, it would only connect to "phone audio" and not "media audio," and I had to go into the Android settings and enable "media audio" each time I got in my car. With VillainROM, it connects automatically and it doesn't disconnect. Also, I've found that in 2.1, when listening to BT Audio, the music doesn't get interrupted by notification sounds, which I hated about 1.5.
I've had nothing but problem with a2dp on the hero, and it's probably the feature I need to work the most. I tried a whole host of 1.5 and 2.1 roms but none of them would consistantly connect to my pioneer deh-p700bt. I read somewhere that it's been a problem for lots of people since the 2.73.x series of updates, so I downgraded to the T-Mobile 1.76.110.6 stock rom and it's worked perfectly for me ever since! I'll have to stick with that one for now and hope it gets fixed in the upcoming 2.1 update
Hi,
I have a question about this subject :
i have a bluetooth car stereo with phone handfree inclued.
With all ROMs I tried (and a tried a lot...)
the phone handsfree always worked
Depend of the ROM, some items were available or not : (battery indicator or signal level indicator for example)
With only one ROM (and I don't remember which one), I could transfer my contact list from the phone to the car stereo system (with bluetooth).
Does someones knows if this feature will be again available into the next ROM (official or not) ?
Thx
PS : sorry for my bad english
yan74s said:
Hi,
I have a question about this subject :
i have a bluetooth car stereo with phone handfree inclued.
With all ROMs I tried (and a tried a lot...)
the phone handsfree always worked
Depend of the ROM, some items were available or not : (battery indicator or signal level indicator for example)
With only one ROM (and I don't remember which one), I could transfer my contact list from the phone to the car stereo system (with bluetooth).
Does someones knows if this feature will be again available into the next ROM (official or not) ?
Thx
PS : sorry for my bad english
Click to expand...
Click to collapse
The Android SDK did not include a bluetooth API in 1.5, but it is included in 2.1. I would guess we'll see a big improvement with the official 2.1 update.
Apr. 15 update:
Thanks for all feedbacks.
I have made sure all changes of Bluetooth code in the recent kernel releases are alright.
Please install the latest tytung_r9 kernel for Bluetooth compatibility testing.
And flash audio.conf_update.zip to see if changing Bluetooth settings in ROM will improve the stability or not.
End of testing below:
Hello Everyone:
We have changed something in Bluetooth related source code in recent kernel releases. (Thanks all devs.)
Each kernel has different changes, and I would like to collect the info about which kernels can support your Bluetooth devices (headsets, car kits, or any devices) or not.
These info may help me develop the next kernel.
These four kernels may have different behaviors when using with your Bluetooth devices.
Apr 03: tytung_r9_beta
Supported unique Bluetooth MAC address.
Supported Bluetooth auto-reconnect.
Supported two-way call recording.
Included my modified initrd.gz (modify init.htcleo.rc to support unique Bluetooth MAC address)
Mar 27: tytung_r8.3
Updated Bluetooth stack from AOSP.
Mar 25: tytung_r8.2
Fixed Bluetooth 60mA battery drain (i.e. support Low Power Mode) (Big thanks to Trilu and Charansingh)
Included my modified initrd.gz (add --enable_lpm to support Low Power Mode)
Mar 24: tytung_r8.1
It represents all previous kernels which have Bluetooth 60mA battery drain.
For me, they all work with my Bluetooth enabled PC. (Acer Aspire Z5710)
And I can also use another native Android phone to transfer files to/from HD2 via Bluetooth by using ES File Explorer.
If you would like to help test tytung_r9 kernel, please flash it and give me the report.
Remember to make a nandroid backup before testing, to restore back after testing or if anything goes wrong.
You can replace /boot/initrd.gz in zip file with logwrapper version in attach files to output the detail log to ddms/logcat.
Before every kernel testing, please delete Bluetooth devices in Bluetooth settings on your phone, and then rescan, repair, and connect to your BT devices again.
Kernels tytung_r9 include initrd.gz which is optimized for an AOSP ROM (i.e. NexusHD2-Gingerbread) and may be not compatible with other ROMs (e.g. CM7 or MIUI).
For example, if tytung_r9 causes any problem, please replace /boot/initrd.gz of kernel_tytung_r9_update.zip with your original ROM's initrd.gz and then flash it again.
Besides, make sure you have the following lines in init.htcleo.rc located in initrd.gz to support the unique Bluetooth MAC address fix in r9.
Code:
# bluetooth MAC address programming
chown bluetooth bluetooth /sys/module/[COLOR="Red"]board_htcleo[/COLOR]/parameters/[COLOR="red"]bdaddr[/COLOR]
setprop ro.bt.bdaddr_path /sys/module/[COLOR="red"]board_htcleo[/COLOR]/parameters/[COLOR="red"]bdaddr[/COLOR]
Report format:
ROM that you are using:
Kernel version:
Bluetooth Headset/Device (brand):
Stereo music (A2DP):
Remote control (play/pause/skip music) (AVRCP):
Phonebook access (vCard exchange) (PBAP):
Files transfers (OPP/OBEX):
Personal Area Networking Profile (PAN):
Make or answer a call (HSP):
Detail description:
You can reply here and/or post in Google Docs: TYTUNG Kernel's Compatible Bluetooth Headsets List to be more organized.
I hope your time and effort for testing and sharing the results to XDA will help others purchase their next Bluetooth headset/device.
Thanks
--tytung
Will this help solving the stereo Bluetooth thing on sense?
white-energy said:
Will this help solving the stereo Bluetooth thing on sense?
Click to expand...
Click to collapse
Even a native Android phone cannot also support all brand of Bluetooth devices.
So this's mainly a compatible Bluetooth Headsets List, and maybe it will help develop the kernel.
i have typhoon 2.9.3
your kernel r9 works ok with motorola h300 bt headset.it is not stereo headset but with supermonofroyo bt app i can hear music from the headset.
boba23 said:
Hey tytung,
gonna give your new kernel a try, since I am also having BT issues with my car handsfree unit. I can't pair it with any gingerbread rom yet. The Pairing/PIN dialog to enter the pin code just doesn't come up.
But I don't think it's a kernel issue for me since I tried imilkas 2.3.3 Sense 2.1 rom and with that I can pair my device perfectly fine.
Right now I am playing around with the bluez config files (auto_pairing.conf etc) to see if that fixes anything for me.
What is more with froyo roms I never had trouble with my car handsfree, worked perfectly fine.
boba
Edit: back to your question, 8.3 BT is working with the following devices for me: Jabbra BT250 headset, FM9 BT TMC Receiver, Lenovo T60p Bluetooth - But NOT working, not pairing with my built in Parrot handsfree/headunit in a Peugeot 207cc.
boba
Click to expand...
Click to collapse
Sense ROMs and AOSP ROMs use different Bluetooth stack, so that'll be the cause.
In other words, HTC uses a modified BT stack in their Sense ROMs.
ROM:Typhoon2.9.4
BT Headset:SE MW600
Kernel:r9
Everything works. Good call recording sound even via BT Headset although it is louder via Phone.
A2DP and AVRCP all work.
Reconnects perfectly
Tytung,
Thanks so much for working on this!
Just tried with hyperdroid v11 and it boots ok and Bluetooth appears to have a full mac address now.
But, it still doesn't work properly with wireless tether in Bluetooth PAN mode to my iPad or Macbook Pro in OSX or Windows 7.
Wireless tether still says error :SIOCSIFFLAGS (cannot assign requested address)
So for some reason it isn't assigning an IP to the ipad/laptop.
Could be a problem with the app itself but others reported it was the mac address causing the problem so I'm not sure.
I'm very grateful for your effort in looking at this though so thank you!
Tytung,
despite the heavy battery drain r8.1 was working very well with my parrot ck3400 carkit (carkit and gps mouse).
kernel r8.3 (among in Tyween Typhoon cLK versions) was giving a lot of problems to connect and reconnect when making a phone call or connecting the gps mouse trough bluetooth. I always have to flash your cLK_tytung_bt fix for a working bluetooth connection. i don't know what kernel this is.
Will test r9 beta on Tyween Typhone 2.9.4 and report back to you asap
boba23 said:
Hey tytung,
gonna give your new kernel a try, since I am also having BT issues with my car handsfree unit. I can't pair it with any gingerbread rom yet. The Pairing/PIN dialog to enter the pin code just doesn't come up.
But I don't think it's a kernel issue for me since I tried imilkas 2.3.3 Sense 2.1 rom and with that I can pair my device perfectly fine.
Right now I am playing around with the bluez config files (auto_pairing.conf etc) to see if that fixes anything for me.
What is more with froyo roms I never had trouble with my car handsfree, worked perfectly fine.
boba
Edit: back to your question, 8.3 BT is working with the following devices for me: Jabbra BT250 headset, FM9 BT TMC Receiver, Lenovo T60p Bluetooth - But NOT working, not pairing with my built in Parrot handsfree/headunit in a Peugeot 207cc.
boba
Click to expand...
Click to collapse
side note:
a German driving a French car???? hmm
white-energy said:
Will this help solving the stereo Bluetooth thing on sense?
Click to expand...
Click to collapse
What problems do you have with sense ???
What i have also found - The pairing issue is also influenced by the bt firmware.
You know, that is the bcm4329.hcd file in /system/etc/firmware
With the latest htc sense firmware i can pair with my bluetooth devices, but i cant get any audio transmission.
BCM4329B1_002.002.023.0511.0538.hcd
Currently i use the bcm4329.hcd file with 14.172 Bytes.
What i have also seen, that the newer files saves some power....
Hi tytung, I don't have a log file for you unfortunately. I have personally had no problem with my bluetooth headset with any of your recent changes. However, with tytung r9 I think this is related to the callrecording patch, as I don't see how anything changing in bluetooth would affect this. With v2.9.4 yesterday I was testing with tytung r9... At work I need to use airplane mode because I get no signal in the office, only when I go to the restroom I can get signal. Upon leaving airplane mode, in 2 out of 8 times yesterday of turning airplane mode off, I was unable to get a data connection upon getting a signal. Switching data on or off did not help, only a reboot did. This is why I have decided to keep tytung r8.3 as the kernel used in the latest version of my ROM. Maybe I can do some more testing and try to get some logs for you, but I rolled back to r8.3 for now. Has anyone else experienced this? Thanks for your work on what I think is the best kernel for our phones currently
Edit: It may have been because I overlooked the requirements in initrd.gz but I am unsure. I saw the lines but mine say board_bravo instead of board_htcleo, and I thought I had what was required as the lines were very similar. I will begin testing again tonight and let you know if I experience the same problem I had before.
Touchscreen Frozen
Something weird is happens with my hd2.
When i longpress the redbutton to shutdown or reboot i cant touch the options (shutdown, reboot, profiles etc).
The bizarre is that happens with all roms with your newst kernels
Maybe a kernel related?
(all them has the tytyng 8.3 and 9.0b)
felipemadox said:
Something weird is happens with my hd2.
When i longpress the redbutton to shutdown or reboot i cant touch the options (shutdown, reboot, profiles etc).
The bizarre is that happens with all roms with your newst kernels
Maybe a kernel related?
(all them has the tytyng 8.3 and 9.0b)
Click to expand...
Click to collapse
Unfortunately I have the same problem for a few days, sometimes helped re-pressing the red button and after unlocking screen reacted normally. The problem is already present on all OS, and regardless of the kernel on Android builds. I suspect that is a hardware malfunction and my poor Leo soon will die. Actually i'm on CoreDroid 1.6 and i noticed that the problem doesen't appear as often as on tytung kernel.
Sent from my HTC HD2 using XDA App
boba23 said:
Yea, that's what I figured as well. You think it's possible (if everything else fails for me) to port/use that modded stack to a CM7 rom?
If you look at the files (bluetoothd, libs and so on) it's definately still bluez based. Question is what does HTC modify and what other files are needed ...
boba
Click to expand...
Click to collapse
No idea how to port/use that modded BT stack to a CM7 rom.
crunchie-uk said:
Tytung,
Thanks so much for working on this!
Just tried with hyperdroid v11 and it boots ok and Bluetooth appears to have a full mac address now.
But, it still doesn't work properly with wireless tether in Bluetooth PAN mode to my iPad or Macbook Pro in OSX or Windows 7.
Wireless tether still says error :SIOCSIFFLAGS (cannot assign requested address)
So for some reason it isn't assigning an IP to the ipad/laptop.
Could be a problem with the app itself but others reported it was the mac address causing the problem so I'm not sure.
I'm very grateful for your effort in looking at this though so thank you!
Click to expand...
Click to collapse
Wireless tether can run correctly in my ROM, and I don't see any SIOCSIFFLAGS (cannot assign requested address) error.
What steps will reproduce the problem?
trilu said:
What i have also found - The pairing issue is also influenced by the bt firmware.
You know, that is the bcm4329.hcd file in /system/etc/firmware
With the latest htc sense firmware i can pair with my bluetooth devices, but i cant get any audio transmission.
BCM4329B1_002.002.023.0511.0538.hcd
Currently i use the bcm4329.hcd file with 14.172 Bytes.
What i have also seen, that the newer files saves some power....
Click to expand...
Click to collapse
My bcm4329.hcd file has 17,684 Bytes and comes from Nexus One Gingerbread OTA.
tyween said:
Hi tytung, I don't have a log file for you unfortunately. I have personally had no problem with my bluetooth headset with any of your recent changes. However, with tytung r9 I think this is related to the callrecording patch, as I don't see how anything changing in bluetooth would affect this. With v2.9.4 yesterday I was testing with tytung r9... At work I need to use airplane mode because I get no signal in the office, only when I go to the restroom I can get signal. Upon leaving airplane mode, in 2 out of 8 times yesterday of turning airplane mode off, I was unable to get a data connection upon getting a signal. Switching data on or off did not help, only a reboot did. This is why I have decided to keep tytung r8.3 as the kernel used in the latest version of my ROM. Maybe I can do some more testing and try to get some logs for you, but I rolled back to r8.3 for now. Has anyone else experienced this? Thanks for your work on what I think is the best kernel for our phones currently
Edit: It may have been because I overlooked the requirements in initrd.gz but I am unsure. I saw the lines but mine say board_bravo instead of board_htcleo, and I thought I had what was required as the lines were very similar. I will begin testing again tonight and let you know if I experience the same problem I had before.
Click to expand...
Click to collapse
Well, in my ROM, r9 kernel will write unique BT Mac address into /sys/module/board_htcleo/parameters/bdaddr file.
You can read its content.
Then ROM will get BT address from bdaddr when booting. (via /system/bin/brcm_patchram_plus)
If your ROM has different condition, please change board_htcleo to something else.
tytung said:
Well, in my ROM, r9 kernel will write unique BT Mac address into /sys/module/board_htcleo/parameters/bdaddr file.
You can read its content.
Then ROM will get BT address from bdaddr when booting. (via /system/bin/brcm_patchram_plus)
Click to expand...
Click to collapse
Thanks for the information. Has anyone else experienced what I did with tytung r9 in regards to no data connection upon turning off airplane mode? I am going to begin my testing again with tytung r9 beta today after I update the initrd.gz used in my build. I did not experience this with any previous tytung kernels, and think that the cause may be the call recording feature.. I am unsure and have not done any serious analysis on it, just wanted to let you know what I have experienced.
felipemadox said:
Something weird is happens with my hd2.
When i longpress the redbutton to shutdown or reboot i cant touch the options (shutdown, reboot, profiles etc).
The bizarre is that happens with all roms with your newst kernels
Maybe a kernel related?
(all them has the tytyng 8.3 and 9.0b)
Click to expand...
Click to collapse
As mzebrowski13 said, I guess it's a hardware issue.
I have a Galaxy Note 2 running Jedi Master 13. Every single thing is awesome about this phone...
EXCEPT:
I have a Lincoln with the new MyLincoln Touch radio. It supports text messaging ONLY with ICS or more specifically, Bluetooth 3.x. The Bluetooth MAP (messaging access profile) is different in 4.0 and thus not supported. Is there any way to downgrade said Bluetooth version?
I only use BT stereo and phone headsets normally, never use file transfers so the 4.0 advantages wouldn't affect me (I hope).
Thanks in advance for the input! :good:
Did u try and call the dealership, maybe ur car has update they can do
BACARDILIMON said:
Did u try and call the dealership, maybe ur car has update they can do
Click to expand...
Click to collapse
Yes, yes I did. I was in touch with the people that make the MyLincoln Touch device that works with Microsoft Sync. I have the newest version, which supports up to Android 4.1.1 and the Bluetooth 3.0 software, which has advanced compatibility with MAP. The Bluetooth 4.0 doesn't work the same and makes it lose the ability to do SMS from the car itself. Ugh.
I was hoping I could somehow put the old Bluetooth stack onto my phone to make it work properly. As of right now, Ford/Lincoln say that only Android ICS' Bluetooth stack is compatible. I feel better than the Apple community, they don't even get pictures to transfer. At least It's cool having the address book picture on my phone.
So can it be downgraded or not?
I am also interested in this (for another device though). Is it possible in principle?
No this stuff is way too complex due to the new advancement of spamsung Knox controling everything, we have very little control of our devices any more
(@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.