[/B]Hi, just received my TD2 last week and is enjoying it. I have one major issue though. In my car I have a Pioneer AVIC X3 system including GPS, AV and BT. Its the one with the motorized monitor.
Unfortunately it seems that HTC has chosen a different type of BT that is NOT compatible with my Pioneer system.
Does anyone know of any fixes ?
Maybe you can draw more attention to your thread by adding an appropriate title. Good luck finding a solution!
I had a very high end pioneer, never again.
With mine, the problem was that the pioneer won't recognise PDAs, but it will recognise Smartphones and mobile phones. (Each bluetooth device broadcasts what type of device it is.)
I actually told pioneer the problem, how to fix it, and their support would only say "your phone is not on the supported device list". After i put the effort in to help them improve their systems dramatically, they couldn't even be bothered to acknowledge it / forward it to the development people.... so I spent £600 on a kenwood, worked like a charm, Kenwood's bluetooth modules are made by parrot. (also the £70 kenwood I also have works great too)
There are some registry edits that work to make your phone identify itself as a smartphone, as long as it has the MS bluetooth stack, not sure the exact details though, I've not needed to do that since I got rid of the pioneer.
Hi Trinode,
Thanks a lot for your comments. If I was to try the registry edit thing... would you know a link somewhere where I can get this information ? Otherwise I'm probably forced to change the Pioneer system also.
I have the dpx500bt, and I am trying to get an idea of whether or not the moto x will work well with it. I currently have an iphone, and kenwood seems to have gone out of their way to support that. With an android phone, it is unclear whether I will even be able to make/receive phone calls.
Hi Guys
Would really appreciate some help with this one, i am sure it been covered to some degree in other threads.
Since owning my unit I have wanted one application to run and I am not fussed about anything else, the app is ALPconnect.
ALPconnect is a application that connects to my radar detector via BT 4.0 only so it displays all the information on the dash for radar frequencies.
https://play.google.com/store/apps/details?id=com.alpriority.alpconnect&hl=en
Due to the limitations in the Bluetooth, no current rom has been able to allow the application to turn the BT on and search for the ALPconnnect Module
http://www.alpriority.com/product/alpconnect-bluetooth-module-gen2/
Over on the other forum i am apart of http://radarandlaserforum.com, one member has spent upwards of 2000$ buying android head-units to see if this app would run and connect on it.
our small thread is ongoing at @ http://radarandlaserforum.com/showt...-InCar-Enetertainment-unit-ALPconnect-Testing about this issue.
I don't normally ask for help, but I could really use some help and I am sure others on the forum that purchased it for that reason would greatly appreciate it too.
This is the last information I received from agentdr8, thank you aswell
agentdr8 said:
It's severely limited, when compared to any other Android device with BT. This is due to the OEM's choice of the BC5/BC6 module, and their poor BT implementation. Instead of routing BT audio traffic through the Android system, like a normal device would, they route it through the MCU. That would be fine on its own, except they route pretty much all BT interactions through the MCU, via serial AT commands, which is very non-standard. Simple things like pairing, or using SPP profile just don't work, or require a bit of finagling.
On top of that, there's code (at least in MTCB; dunno about newer MTCD) in MTCManager that filters which devices can pair via BT for OBD use. It checks the device name and if it starts with OBD, it will allow it to pass to the next step during pairing. I can only imagine they chose to do that so they could sell their companion BT OBD adapters with the headunits?
My XMTC module had accounted for this limitation in name-based filtering (apparently not the only limitation though; if your adapter was at least v1.4 it should work), but it hasn't been updated to work on any 2016 roms. Since I no longer have time to maintain that project, it's been open sourced on my github. The BT pieces could be extracted into their own module, but I thought I had read someone else (maybe MVG70?) had made a BT xposed module for these devices to try and address compatibility issues.
Click to expand...
Click to collapse
Just as a thought
Would the MTCB be able to support external USB BT 4.0 thus removing the need for the messy internal BT
Sent from my iPhone using Tapatalk
shanetrainST said:
Just as a thought
Would the MTCB be able to support external USB BT 4.0 thus removing the need for the messy internal BT
Click to expand...
Click to collapse
I think it's been discussed before, and no one has successfully added an external BT adapter to these headunits.
Has that group tried the app on the Parrot Asteroid? I know it wasn't the highest rated Android headunit, but it might be more "standard" than how these ones are configured.
agentdr8 said:
I think it's been discussed before, and no one has successfully added an external BT adapter to these headunits.
Has that group tried the app on the Parrot Asteroid? I know it wasn't the highest rated Android headunit, but it might be more "standard" than how these ones are configured.
Click to expand...
Click to collapse
Thanks agentdr8, but it does not really help the ones that splashed out and bought the HuFei units
Is the reasoning behind the external BT not working because nobody is interested in making it work or is it not technically possible?
shanetrainST said:
Thanks agentdr8, but it does not really help the ones that splashed out and bought the HuFei units
Is the reasoning behind the external BT not working because nobody is interested in making it work or is it not technically possible?
Click to expand...
Click to collapse
Since the kernel is not open source, there's very little hope of adding the necessary drivers to support external BT adapters. Aside from that, I don't believe the BT stack that is included in these roms is standard.
I won't say it's impossible, as given enough time and money, anything is possible. But I doubt it's something anyone here can address without the sources.
Guess the manufacturer is reluctant to release the source then.
Sent from my iPhone using Tapatalk
agentdr8 said:
Since the kernel is not open source, there's very little hope of adding the necessary drivers to support external BT adapters. Aside from that, I don't believe the BT stack that is included in these roms is standard.
I won't say it's impossible, as given enough time and money, anything is possible. But I doubt it's something anyone here can address without the sources.
Click to expand...
Click to collapse
Just a couple of questions
1.Do you know if any developer is currently working injecting the drivers into the kernel, as impossible as it sounds.
2.If the manufactures were to fix this issue, what things should they include to make external BT work?
3.Have any of the manufactures hinted at releasing the source and letting other developers fix the issue with custom roms
Just on another note
I have 30 emails from Eonon saying that their tech cannot do this and have assured me that.
We have our own brand and R&D department.
We use our software.
Click to expand...
Click to collapse
Which I don't believe for a second
I'm quite interested in getting this fixed as well - I have both an ODB2 adapter and Navdy that I'm unable to connect due to this limitation. And the fact that there's no available workaround via External BT is infuriating.
shanetrainST said:
Just a couple of questions
2.If the manufactures were to fix this issue, what things should they include to make external BT work?
Click to expand...
Click to collapse
From my understanding, the only way to get this to work is through an external (USB) BT adapter, since the built-in BT stack sends everything through the MCU instead of directly to android. So enabling the proper USB drivers for BT in the Kernel would fix it. I'm not aware of any other USB devices that don't work (maybe gamepads or other HID devices, unconfirmed) so it seems they've cherry picked which USB devices to allow. Considering the otherwise hackable nature of these devices, it'd make sense to me to just enable all available USB devices and let us plug in whatever we want to plug in.
I'm in the same boat. I have an OBD adapter (Hondash) which refuses to pair. I've tried 2 Xposed modules which are supposed to sort this. I'm wondering if my particular issue is down to my 5.1.1 ROM so might try it on my old RK3066 4.4.4 HU which I gave to my Dad.
So I'm monitoring this thread in the hope a fix is found.
I am doubtful, I have contacted Klyde/Eonon/others and nobody is willing to release the kernel source code or address the issue.
So when someone gets a copy from Klyde/some reseller/MTC or whoever and a developer has the motivation to correct it, that can be the only solution.
I have given up hope on this one
Sent from my iPhone using Tapatalk
Does anyone know the location in the Android file system where the Bluetooth pairings are saved?
FINALLY! Someone with a similar issue. I've got a Valentine One, and the BT module for android, (connecting using YaV1) and I've been trying to get my android unit to pair with it as well. In for potential solutions.
This question may be off topic, and I apologize for that, but are you referring to the app not being able to turn on BT and look for the adapter; just getting stuck at "Turning on bluetooth..."?
I have an OBDII scanner which I can pair no problem. When I use a specific app (OBD Card Doctor Pro (or reg)) and attempt to connect it, I get a prompt letting me know that an app wants to turn on BT. I click allow and then it just sits there and never does anything. Is that the problem ALPconnect has?
Torque does not prompt me with this and initiates the BT connection just fine.
The main issue here is that the bluetooth hardware is in effect emulated to the android subsystem for the nice bluetooth dialler front end so android has no real control over the bluetooth hardwrae. These headunits have some real downfalls and this is one of them What we need is to break this open and rewrite it. Without sources we can't do that. We could maybe dissasemble bits and replace them in code but the rom is factory odd and hacked to bits!
monza20vt said:
The main issue here is that the bluetooth hardware is in effect emulated to the android subsystem for the nice bluetooth dialler front end so android has no real control over the bluetooth hardwrae. These headunits have some real downfalls and this is one of them What we need is to break this open and rewrite it. Without sources we can't do that. We could maybe dissasemble bits and replace them in code but the rom is factory odd and hacked to bits!
Click to expand...
Click to collapse
So this emulated effect is what causes my system get stuck "Turnning on bluetooth..." if I understand you correctly? There's no Android control over the BT hardware so the request is just lot in limbo?
Hi all,
First: I used the search function, but I couldn't find a solution. So if there is one, just post the link to the topic.
And now my problem/idea: I have car that comes with a radio which supports Android Auto and Apple Carplay. Unfrotunately, it doesn't support DAB+. I was looking now for a solution to add DAB+ without any additional (visible) screen or remote control. There are some but they mostly are not really working properly.
So I had the idea to add DAB+ by Android Auto. Is there some hardware to do that (if possible without pressing 10 buttons every time I turn on the car/radio)?
Theoretical it should be:
- a USB-dongle (also powered by this)
- on which a Android system is running
- which starts DAB automaticaly
- has the hardware to receive DAB+ signals
- just have to be plugged into the USB-Port of the car
Is there something like that? If not, is it possible of did I forget something which prohibits this idea? How could this be built and what would be needed?
Thanks for your ideas/links/whatever...
PlatinCH
PlatinCH said:
Hi all,
First: I used the search function, but I couldn't find a solution. So if there is one, just post the link to the topic.
And now my problem/idea: I have car that comes with a radio which supports Android Auto and Apple Carplay. Unfrotunately, it doesn't support DAB+. I was looking now for a solution to add DAB+ without any additional (visible) screen or remote control. There are some but they mostly are not really working properly.
So I had the idea to add DAB+ by Android Auto. Is there some hardware to do that (if possible without pressing 10 buttons every time I turn on the car/radio)?
Theoretical it should be:
- a USB-dongle (also powered by this)
- on which a Android system is running
- which starts DAB automaticaly
- has the hardware to receive DAB+ signals
- just have to be plugged into the USB-Port of the car
Is there something like that? If not, is it possible of did I forget something which prohibits this idea? How could this be built and what would be needed?
Thanks for your ideas/links/whatever...
PlatinCH
Click to expand...
Click to collapse
A late but working solution...
USB-Stick (working fine with Android)
Thread for working software for this device. --> latest greatest one
Hi Rigattoni,
Thank you for your reply.
If I understand it correct, the stick is only the DAB-receiver and not the "head unit" on which the android system is running? Or can I make Android running directly on this stick?
Hi, I've recently bought a used car and installed a Xtrons PE98MTVPL on it.
Now I have discovered that the used car has TPMS sensors installed on the wheels. What would I need in order try and see if these work with the head unit? Do you need some additional hardware or can I pair the sensors with the head unit as default?
Best regards
David
You need an add-on USB device for TPMS like this: https://www.ebay.com.au/itm/USB-Car...ystem-with-4-External-Sensors-AU/263958460650
First thing you need to know is that there are two main frequencies used, so you would need to match the unit you buy to the frequency used on your wheels. Also I have no idea about compatibility across manufacturers sorry.