Related
[/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 picked up a SGT from Verizon and am having trouble with bluetooth. It won't pair with either a Jabra or Motorola brand headset. I can get it to pair with my Apple Bluetooth keyboard, but it won't connect. It just says "Paired", but does not function. I'm using Skype and GV on this and would love to be able to use a bluetooth headset. Is this unique to the Verizon model? Has anyone else had better luck with a T-Mobile model?
Thanks!
Apparently vzw left the bluetooth HID out (unlike tmo). So the vzw tab can pair with keyboards and mice, but cannot connect to them. There are hid drivers in the market, but I haven't tried any yet. I have a bt keyboard on order. I tried a mouse,it paired fine but wouldn't connect. There have been many reports of this.
BT headsets haven't had any issues that I have heard. My moto s9hd paired and connected the first time and has been ready whenever I have needed it.
r
I have the T-Mo version and I can connect and pair BUT...
Audio from the other person plays through the BT headset and your voice is via the Tab's microphone... I put the Tab in another room and made a call and all the other person could hear was the TV in the other room.. Once I walked back and picked up the Tab they could hear me...
TMO Profiles?
I have a Sprint Tab and it pairs but refuses to connect. I'm wondering if there's some way to extract the TMO drivers from the device, and stick them elsewhere. Also, I don't know a lot about the bluetooth driver architecture. What exactly is it missing? The kernel drivers for it? Or some other thing?
I had the same trouble with my Jawbone and Think Outside stowaway keyboard.
I called Verizon about this and the tech told me they had no profile for headsets or HID. They have stereo headphone support for music.
Very disappointing that they would do extra work to remove functionality, but I'm certain a good rom will become available that fixes this Verizon blunder.
Sent from my SCH-I800 using XDA App
What I'm reading is that Android doesn't actually support BT HID in this release. I'm still wondering if it could be extracted from TMO or some of the European releases and pushed with ADB.
The other thing I'm wondering is about CyanogenMod. They've had an experimental bluetooth HID thing that's been working decently, or so say the posts, for a few months now. I'm wondering if it's a high enough level of abstraction that it could just be put variously on any device, as long as the processor architecture was the same (or is it up in the java level so that doesn't even matter?)
I know nothing, to be honest, but wanted to just advance a few questions. Not sure how many people are actually interested in BT HID, but for me, it's a dealbreaker for whether or not I hand this device back in.
I've had the same problems with my Verizon SGT. Verizon apparently deleted some Bluetooth drivers. Why? I don't know. This is the only problem I have come across with my tab. If anyone knows of a driver that will connect Bluetooth devices to the SGT please reply. I would greatly appreciate it. Thanks
Hello my friends!
I have searched a lot, but it seems that getting the FM receiver to work on our Snapdragon S4 devices will not happen, at least in the near future.
Anyone has any different (and encouraging) info here?
Does Microsoft give out resources that could make this possible by a dev, or they pretend it does not exist?
Thanx in advance.
Konstantinos
There are no APIs for it. So currently Developers can't use the feature in Apps. At the moment we don't even know if all the hardware required is even inside the phones. The Snapdragon SoC does support it but that is not all the hardware that is necessary.
Let's pretend it doesn't exist. However over at the TechMeShow I was making an FM Transmitter and now uses my Bluetooth module for "FM Radio" streaming. It's hardware, not just Software.
Hi all,
I'm thinking about buying a new car equipped with android auto. This car comes with an SD card slot where you can store music to use with the regular infotainment system. I was wondering if that SD card can also be accessed from android auto? I currently have a 16 GB Nexus 5X so it would be nice if I could use the SD card in the car, while driving.
I'm asking here because I'm sure the sales people don't even know what android auto is, so I don't really trust them.
Thanks.
My car stereo (Pioneer AVIC-F77DAB) has an SD card slot and I can't access it through android auto. I have to go into the stereos main screen to access music/video from SD card. Hope this helps
wallacerp said:
My car stereo (Pioneer AVIC-F77DAB) has an SD card slot and I can't access it through android auto. I have to go into the stereos main screen to access music/video from SD card. Hope this helps
Click to expand...
Click to collapse
Thanks for the answer, I was kind of expecting this but I wanted to make sure. If anybody has a different experience please let me know.
wallacerp is correct.
AA has no way at present to play audio sourced from the headunit, whether CDs, SDCard or AM/FM/HD/Sat etc.
Maybe in some future release 1-3 years from now.
There are strings within the AA code indicating Google might be experimenting with this. But it's in Googles interest to have us using Google Play Music. (Though deals with auto OEMs to share car data with Google could shift that interest.)
Hi,
Peharps, in the future a new release of the AA protocol will include this., However, HU manufacturers can implement this AT TIME:
* Share the SD content using DLNA over the WiFi. Typically, you mobile and your HU can be connected by WiFi, additionally to AA USB connection. On this wireless network you can use any PLAYER App compatible with AA that can play from DLNA sources... in this case the HU.
I found this solution quite complex but viable... I do something similar in my VW.
manos78 said:
Hi,
Peharps, in the future a new release of the AA protocol will include this., However, HU manufacturers can implement this AT TIME:
* Share the SD content using DLNA over the WiFi. Typically, you mobile and your HU can be connected by WiFi, additionally to AA USB connection. On this wireless network you can use any PLAYER App compatible with AA that can play from DLNA sources... in this case the HU.
I found this solution quite complex but viable... I do something similar in my VW.
Click to expand...
Click to collapse
Hmm, OK. But a bit complicated and potentially fragile I think.
I am not aware of any aftermarket AA HU that supports Wifi, never mind DLNA on top.
I presume your VW HU does, but I'm not sure about others.
My first thought was using flash USB connected to the phone, but I think it goes the wrong direction to use a hub to share the USB needed for AA. In theory AA over Wifi (or USB hub'd ethernet ?) could free up the USB, but it's not clear that Google will support AA over IP officially any time soon.
mikereidis said:
wallacerp is correct.
AA has no way at present to play audio sourced from the headunit, whether CDs, SDCard or AM/FM/HD/Sat etc.
Maybe in some future release 1-3 years from now.
There are strings within the AA code indicating Google might be experimenting with this. But it's in Googles interest to have us using Google Play Music. (Though deals with auto OEMs to share car data with Google could shift that interest.)
Click to expand...
Click to collapse
Well, it's kind of a no-brainer that people would want to listen to FM radio and use navigation at the same time. Same goes for an SD card or CD you might have in the car. As it is I'm leaning towards buying a cheaper car model and just using a mount for the phone when I need it. Especially since I have no guarantee that if Google does implement this in the future, it will work with my car.
This guy has a mode button on his device that allows him to switch between Android Auto and his normal infotainment system. That's at least an option, but I'm not sure if it works the same on the one that comes with VW cars.
https://youtu.be/Mw7BYxyC_3Q?t=13m31s
sorin7486 said:
This guy has a mode button on his device that allows him to switch between Android Auto and his normal infotainment system. That's at least an option, but I'm not sure if it works the same on the one that comes with VW cars.
https://youtu.be/Mw7BYxyC_3Q?t=13m31s
Click to expand...
Click to collapse
That is a standard Pioneer AA HU feature. I would have thought other HUs can do the same, but maybe some don't.
sorin7486 said:
Well, it's kind of a no-brainer that people would want to listen to FM radio and use navigation at the same time. Same goes for an SD card or CD you might have in the car. As it is I'm leaning towards buying a cheaper car model and just using a mount for the phone when I need it. Especially since I have no guarantee that if Google does implement this in the future, it will work with my car.
Click to expand...
Click to collapse
My negative reply was about not being able to control FM and other HU sourced audio from the Android Auto screen UI.
Pioneer HUs (at least) allow you to start FM (or whatever), then start AA and FM will continue playing. FM will pause or drop volume when using AA navigation, so that's a crude form of basic "integration".
But you have to leave the AA UI in order to deal with FM etc on the HU screen (buttons might work, I've never actually tried this.)
So there is no seamless integration that allows you to control FM etc on the HU screen while staying within the AA UI. And most of us find it a bit jarring to switch between UIs, so we try to stay within one UI, which effectively means the AA UI.
It may be a "no brainer" that we all want seamless integration, but that doesn't mean that Google will support it.
Google music services compete with FM radio. This is why Google has never supported FM on Nexus devices. Google also killed attempts to create standard FM radio APIs for Android (while pretending to support them).
Basically, Google wants us to use Google Play Music from within AA and purposely makes it difficult to access FM/HD/CD/etc... in a seamless manner.
Yah, I have a feeling that most HUs have AA as just another app of sorts instead of AA taking over completely. That was my impression because ever review only really shows the features of AA, not how you would use it day to day. And I get what you're saying about the radio but I think cars are a bit different: the people who listen to the radio on their phone have usually been a minority, while almost everyone uses it in the car. In any case, if AA doesn't take over completely I see no reason for them or the car companies to integrate other car functions into AA.
thanks for the reply
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?