Related
I'm using a T-Mobile Touch Pro2 which includes the Broadcom Bluetooth stack and Microsoft Voice Command 1.6.2105. The problem is the Bluetooth software is not compatible with Voice Command and I hate it.
Voice Command is unable to announce TTS events via any bluetooth headset despite having the option for that turned on. Also, activating Voice Command via a bluetooth headset button is either very slow, or unstable (doesn't work sometimes).
Has anyone been able to create a Rhodium ROM that uses the normal Microsoft Bluetooth stack, which has been known to actually work with 3rd party programs?
I had this issue and moved to NRG's Genesis 6.5 rom. everything works fine.
I have not seen a 6.1 rom that works tho.
My TMoUS TP2 works perfect with my Motorola S9's when using the MSVC that came on the stock ROM.
S
adamz said:
I'm using a T-Mobile Touch Pro2 which includes the Broadcom Bluetooth stack and Microsoft Voice Command 1.6.2105. The problem is the Bluetooth software is not compatible with Voice Command and I hate it.
Has anyone been able to create a Rhodium ROM that uses the normal Microsoft Bluetooth stack, which has been known to actually work with 3rd party programs?
Click to expand...
Click to collapse
Finally someone who has the same problems as I have.
There are also other annoying side effects of this Broadcom stack:
- As we all know the stereo output is nothing compared to for example an IPhone. Therefore I always used WOW SRS as a sound mixer which closed the gap at least to some degree on my Kaiser.
But now with the TP2 and its Broadcom stack as soon as WOW SRS is installed (I know about the different settings and driver versions to get it working, so this is not the cause) the BT stack is only connecting the hands free profile after this and the stereo profile is simply not working any more.
With the old MS stack this was not a problem.
So I'm back to the old crippled stereo output again
- One could imagine using the integrated HTC sound mixer/booster, but here another even more annoying thing comes into play:
The internal sound mixer (and also the FM radio by the way) are not working with BT at all!!!
Both are only working with a cabled headset and I found no way of getting the FM radio sound to the BT headset or using the sound mixer function on BT.
Together with the non working voice command thing this whole BT integration is so dilettantish that I can hardly believe HTC is selling it as a "professional smartphone".
If someone has any workaround for the above things I would highly appreciate it.
And of course if one of the chefs could implement the old MS BT stack in a cooked ROM this would also be a great thing, but I have not seen one so far.
But even if, I can only hope that some HTC people are reading these comments and that HTC is putting some more professionality into this issue and will soon get it together as a working whole and not as this amateurish implemantation it is currently
asango said:
Finally someone who has the same problems as I have.
There are also other annoying side effects of this Broadcom stack:
- As we all know the stereo output is nothing compared to for example an IPhone. Therefore I always used WOW SRS as a sound mixer which closed the gap at least to some degree on my Kaiser.
But now with the TP2 and its Broadcom stack as soon as WOW SRS is installed (I know about the different settings and driver versions to get it working, so this is not the cause) the BT stack is only connecting the hands free profile after this and the stereo profile is simply not working any more.
With the old MS stack this was not a problem.
So I'm back to the old crippled stereo output again
- One could imagine using the integrated HTC sound mixer/booster, but here another even more annoying thing comes into play:
The internal sound mixer (and also the FM radio by the way) are not working with BT at all!!!
Both are only working with a cabled headset and I found no way of getting the FM radio sound to the BT headset or using the sound mixer function on BT.
Together with the non working voice command thing this whole BT integration is so dilettantish that I can hardly believe HTC is selling it as a "professional smartphone".
If someone has any workaround for the above things I would highly appreciate it.
And of course if one of the chefs could implement the old MS BT stack in a cooked ROM this would also be a great thing, but I have not seen one so far.
But even if, I can only hope that some HTC people are reading these comments and that HTC is putting some more professionality into this issue and will soon get it together as a working whole and not as this amateurish implemantation it is currently
Click to expand...
Click to collapse
I to am having bluetooth problems. I have a sprint tp2. on the opposite end of you i like to use my stereo bt with my pioneer bt deck. with the tp1 i had no problems but now i cant end the call from the deck anymore, it lags when picking up the call, and some other minor bugs. the sound quality is still good.
p-slim said:
I to am having bluetooth problems. I have a sprint tp2. on the opposite end of you i like to use my stereo bt with my pioneer bt deck. with the tp1 i had no problems but now i cant end the call from the deck anymore, it lags when picking up the call, and some other minor bugs. the sound quality is still good.
Click to expand...
Click to collapse
What Pioneer headunit/Pioneer bluetooth unit are you using?
I have an AVIC-D3 with the Pioneer CD-BTB200 module for bluetooth. I have zero issues making it connect with the CD-BTB200 module. I can make calls, receive calls, play bluetooth stereo, etc. The ONLY issue that I have is that when the phone rings on an incoming call, I only hear the ring through my phone's speaker, not the speakers in my SUV. This was not an issue with the M$ Bluetooth stack, however. Go figure. If I can figure out how to make the phone sounds play through my speakers (yes, I have the send notifications/sounds box checked in the advanced bluetooth properties), everything will work 100%.
I wanted to do this, for my own as well. I think the problem we're facing is... drivers. The phone has a slightly different bt/wifi/radio module, therefore required the broadcom drivers. I'll look into making it work with the MS BT stack though... although I'm not too optimistic.
The worst thing in my opinion is the described fact that the internal FM radio and the equalizer/booster can not be used with any hooked up BT device.
Therefore listening to FM radio with BT headphones is simply not possible.
By the way I think this was also an issue in older models, so I don't think that this is a newly introduced thing with the TP2 and the Broadcom stack.
Does anyone of you guys see a solution for sending the FM radio output to the BT channel?
asango said:
Does anyone of you guys see a solution for sending the FM radio output to the BT channel?
Click to expand...
Click to collapse
No, because the cable of the wired headset is used as antenna. even if you manage to fool the radio application to start with the wired headset not connected you won't hear anything but noise.
adamz said:
I'm using a T-Mobile Touch Pro2 which includes the Broadcom Bluetooth stack and Microsoft Voice Command 1.6.2105. The problem is the Bluetooth software is not compatible with Voice Command and I hate it.
Voice Command is unable to announce TTS events via any bluetooth headset despite having the option for that turned on. Also, activating Voice Command via a bluetooth headset button is either very slow, or unstable (doesn't work sometimes).
Has anyone been able to create a Rhodium ROM that uses the normal Microsoft Bluetooth stack, which has been known to actually work with 3rd party programs?
Click to expand...
Click to collapse
asango said:
Finally someone who has the same problems as I have.
There are also other annoying side effects of this Broadcom stack:
- As we all know the stereo output is nothing compared to for example an IPhone. Therefore I always used WOW SRS as a sound mixer which closed the gap at least to some degree on my Kaiser.
But now with the TP2 and its Broadcom stack as soon as WOW SRS is installed (I know about the different settings and driver versions to get it working, so this is not the cause) the BT stack is only connecting the hands free profile after this and the stereo profile is simply not working any more.
With the old MS stack this was not a problem.
So I'm back to the old crippled stereo output again
- One could imagine using the integrated HTC sound mixer/booster, but here another even more annoying thing comes into play:
The internal sound mixer (and also the FM radio by the way) are not working with BT at all!!!
Both are only working with a cabled headset and I found no way of getting the FM radio sound to the BT headset or using the sound mixer function on BT.
Together with the non working voice command thing this whole BT integration is so dilettantish that I can hardly believe HTC is selling it as a "professional smartphone".
If someone has any workaround for the above things I would highly appreciate it.
And of course if one of the chefs could implement the old MS BT stack in a cooked ROM this would also be a great thing, but I have not seen one so far.
But even if, I can only hope that some HTC people are reading these comments and that HTC is putting some more professionality into this issue and will soon get it together as a working whole and not as this amateurish implemantation it is currently
Click to expand...
Click to collapse
p-slim said:
I to am having bluetooth problems. I have a sprint tp2. on the opposite end of you i like to use my stereo bt with my pioneer bt deck. with the tp1 i had no problems but now i cant end the call from the deck anymore, it lags when picking up the call, and some other minor bugs. the sound quality is still good.
Click to expand...
Click to collapse
ruinertt said:
What Pioneer headunit/Pioneer bluetooth unit are you using?
I have an AVIC-D3 with the Pioneer CD-BTB200 module for bluetooth. I have zero issues making it connect with the CD-BTB200 module. I can make calls, receive calls, play bluetooth stereo, etc. The ONLY issue that I have is that when the phone rings on an incoming call, I only hear the ring through my phone's speaker, not the speakers in my SUV. This was not an issue with the M$ Bluetooth stack, however. Go figure. If I can figure out how to make the phone sounds play through my speakers (yes, I have the send notifications/sounds box checked in the advanced bluetooth properties), everything will work 100%.
Click to expand...
Click to collapse
I am using a JVC deck and it connects great. Sound quality is a bit better than from my Wing; my only problem is that when I disconnect from the call it takes my TP2 2-3 minutes to show that the call is actually ended, it runs slower than molases like I have 50 programs running and all trying to access the internet and downloading large files. After the 2-3 minutes the phone has returned to normal like nothing was wrong. I am thinking of flashing to one of the good looking 6.5 roms that our wonderful chefs have cooked up for us, but I cant decide which one to try first!
asango said:
The worst thing in my opinion is the described fact that the internal FM radio and the equalizer/booster can not be used with any hooked up BT device.
Therefore listening to FM radio with BT headphones is simply not possible.
By the way I think this was also an issue in older models, so I don't think that this is a newly introduced thing with the TP2 and the Broadcom stack.
Does anyone of you guys see a solution for sending the FM radio output to the BT channel?
Click to expand...
Click to collapse
In the stock tmobile tp2 there is a app in the windows folder labeled btfm.exe I started it up but I I was only able to get about 15 seconds of audio play using my h500 motorola headset....no bt headphones to test out.
mastermarv said:
No, because the cable of the wired headset is used as antenna. even if you manage to fool the radio application to start with the wired headset not connected you won't hear anything but noise.
Click to expand...
Click to collapse
The point is that I want to be able to use the wireless BT headset with all the audio sources on the device. This would only be logical.
Having to use the wired headset as antenna is of course the other annoying thing in the hardware design of this device (since I think HTC should also have been able to get FM reception with a built in antenna or even the phone frame. Don't know why they have not done this in order to at least allow using the radio in situations where one has got no headset at hand, especially with the TP2, which has got no 3.5mm jack)
But apart from this issue still the only consequent thing would be to be able to use all audio sources with the attached wireless headset. That's what is it for...
pimppoet said:
In the stock tmobile tp2 there is a app in the windows folder labeled btfm.exe I started it up but I I was only able to get about 15 seconds of audio play using my h500 motorola headset....no bt headphones to test out.
Click to expand...
Click to collapse
Yes, this first seemed to be an option to me also, but on my TP2 if I open the btfm.exe I get absolutely no sound, no matter which speaker setting in the software. Not on the wired headphone, not on the internal speaker and also not on the BT headset, even though it is successfully attached with the stereo profile.
Have tried this with several ROMs, always the same problem: No output at all.
And on some it even won't start (error message Unable to extract skin template)
But since HTC has included this exe in the ROM but has not put a link in the start menu I think they know about this lack of functionality, but have not solved it.
Does anyone know more about btfm.exe and a way to get it working?
Hi Guys,
That is my first real complaint I have about the Touch Pro2 ! All is fine but the Widcomm stck it a bummer, my JetwareMobile Extension is now rendered useless, no more callername in my Bluetooth headset and lost some funtionality compared to befor too, but I have to be fair I gained some too, but if I need thoose that is a different topic.
Chris
Cyberon speed voice dial
Please need help to activate CSVD over BT in TP2
gompf said:
Hi Guys,
That is my first real complaint I have about the Touch Pro2 ! All is fine but the Widcomm stck it a bummer, my JetwareMobile Extension is now rendered useless, no more callername in my Bluetooth headset and lost some funtionality compared to befor too, but I have to be fair I gained some too, but if I need thoose that is a different topic.
Chris
Click to expand...
Click to collapse
I feel your pain. I miss having JetwareMobile to help interface with my car's head unit.
adamz said:
I'm using a T-Mobile Touch Pro2 which includes the Broadcom Bluetooth stack and Microsoft Voice Command 1.6.2105. The problem is the Bluetooth software is not compatible with Voice Command and I hate it.
Voice Command is unable to announce TTS events via any bluetooth headset despite having the option for that turned on. Also, activating Voice Command via a bluetooth headset button is either very slow, or unstable (doesn't work sometimes).
Has anyone been able to create a Rhodium ROM that uses the normal Microsoft Bluetooth stack, which has been known to actually work with 3rd party programs?
Click to expand...
Click to collapse
Check out this rom
http://forum.xda-developers.com/showthread.php?t=562161
it appears to do what you want.
Yes, and also the latest of NRGZ28's ROMs does have the BT triggered VC:
http://forum.xda-developers.com/showthread.php?t=562773
Seems like realls HTC has managed to get back this functionality into the latest BT stack version, even though there seem to be some bugs still in conjunction with the current V 1.6.21040 as I wrote here:
http://forum.xda-developers.com/showpost.php?p=4578993&postcount=30
Hi everyone, I have a similar question related to the Microsoft bluetooth stack. I have an ATT Tilt2 (stock ROM still) and have downloaded the Office 2010 beta programs from the Marketplace. A new feature (at least I think it is new) is the Presentation Companion for PowerPoint which allows you to control a PowerPoint presentation using your phone.
When I try to set up the Presentation Companion, however, it gives me a message about not being able to find any bluetooth devices. The instructions from Microsoft say that you must have the Microsoft bluetooth stack installed on the phone and the computer you want to control to get this functionality. I never get to the point of connecting to my computer so I figure it must be the phone.
Has anyone else had similar issues or tried the Presentation Companion? I tried applying the .CAB update listed earlier in this thread but it did not help.
On a side note, with the stock bluetooth stack I have had no issues connecting to my Pioneer headunit in my car for hands-free and A2DP stereo streaming. I have not tried to use the controls from my radio to control the playback, so I'n not sure if that works. The headunit I'm using is the DEH-710BT.
Thanks!
monkeyboy0076 said:
On a side note, with the stock bluetooth stack I have had no issues connecting to my Pioneer headunit in my car for hands-free and A2DP stereo streaming. I have not tried to use the controls from my radio to control the playback, so I'n not sure if that works. The headunit I'm using is the DEH-710BT.
Thanks!
Click to expand...
Click to collapse
I have a Pioneer AVIC-D3 and have no issues with playback (or the controls) using the BT stack in the Rhodium. This, of course, was tested with Windows Media Player. I can do forward, reverse, pause, stop, play, etc.
Which features of a ROM Kernel or Modem have the most influence on BT function. I recently purchased a Kenwood X994 for the car and the Captivate seems to have to be "connected" every time. Sometimes it loads the phone book, other times not. I have never been asked for a PIN code when pairing. Even after flashing a new ROM and reinitialization the Kenwood. It does work but even with th Gamin BT the connections were automatic.
I think the Developers might have an idea what influences the BT stack and if any ROM/Kernel/Modem is better in that regard.
If this post is in the wrong area please move it.
bump - I have the same concerns. Can't seem to find consistent bluetooth connection that was better than stock with lots of trying different roms with different modems and am totally confused on what directly affects the bluetooth connection
tbong777 said:
Which features of a ROM Kernel or Modem have the most influence on BT function. I recently purchased a Kenwood X994 for the car and the Captivate seems to have to be "connected" every time. Sometimes it loads the phone book, other times not. I have never been asked for a PIN code when pairing. Even after flashing a new ROM and reinitialization the Kenwood. It does work but even with th Gamin BT the connections were automatic.
I think the Developers might have an idea what influences the BT stack and if any ROM/Kernel/Modem is better in that regard.
If this post is in the wrong area please move it.
Click to expand...
Click to collapse
I am not trying to sell my ROM to you as I don't and am not here to make any money but I have not found a device that Phoenix Ultimate can not connect to. Just a thought for you.
Unless your making your own kernel thats special , their is some devices that it will have trouble connecting to, specifically certain car Bluetooth sets. this was a problem with every kernel I tried, and other users reported this also. I don't think it has anything to do at all with the Rom anyway,(it could, I didnt look into it too much), it think its an issue with kernels built from I9000 source.
adamholden85 said:
I am not trying to sell my ROM to you as I don't and am not here to make any money but I have not found a device that Phoenix Ultimate can not connect to. Just a thought for you.
Click to expand...
Click to collapse
Adam I have used (and am currenty trying out Phoenix Ultimate) and really find you ROMS useful, The BT works fine but the issue is I have to "connect" the phone even though it has been paired
The Kenwood X994 uses Parrot BT system which is supposed to be the best (which is why I chose the Kenwood LOL), I am just wondering why the device cannot auto connect when I get in the car as it did with the Garmin and the Honda. IS there a task I can set up using task manager?
Maybe its the Kenwood. But searches in that arena show no ill effect except with the Captivate and some Droids. IPhone is flawlwess with that system (wouldn't you know it) as are HTC phones it appears. I really hate having to select a phone based on BT in the car.
di11igaf said:
Unless your making your own kernel thats special , their is some devices that it will have trouble connecting to, specifically certain car Bluetooth sets. this was a problem with every kernel I tried, and other users reported this also. I don't think it has anything to do at all with the Rom anyway,(it could, I didnt look into it too much), it think its an issue with kernels built from I9000 source.
Click to expand...
Click to collapse
Which I thought as well so I flashed Cognition 4.2 and had the same issue...and decided to try Phoenix (GPS was terrible on Cog) Well I guess until I get another phone brand I will have to just make sure I connect the already paired devices. Although iPhone doesn't interest me...maybe HTC,
Moved as not android development
When I first got the new HU it worked fine (actually surprising clear given comments about mics here), but now bluetooth calling doesn't seem to go through the speakers although people on the other end of the line do hear me? Bluetooth streaming of music is fine though which confuses me. Also the sound isn't coming out of the phone itself and the Bluetooth options on the phone have send media and phone checked. So it is like the audio receiving of the call isn't reaching the speakers.
So I am guessing that it seems like something on the software or settings side has got a bit wrong rather than hardware (all I've done there is cut some rear speaker wires to add a hi lo convertor and add power to antenna). Main things I've done on software side since getting this are install add the Xposed Framework, Carservice (uninstalled) , Package Explorer, MTC Keys (disabled) , Xposed MTC (now uninstalled), but I have uninstalled most of this so don't understand how this could be impacting it..
Anyone had anything similar and might know what has caused the bluetooth phone to stop working?
Mine has suddenly decided to stop connecting to Bluetooth at all 90% of the time.
The Bluetooth in these radios is total and utter garbage... that's all I can say.
Went in the car today and everything worked fine!! Very confusing. I'm wondering if it was carservice or one of the other apps after all?
Not sure if it counts but there is a software fix for bluetooth in the Bluetooth mod .. Under hardware mods..
There might be a connection between the Bluetooth stack and other software coming in..
All I know is that this slight change of drivers for us has saved us from doing hardware mods and for now its working perfectly for a number of us..
Check it out if you get problems as a slight chance via settings may fix some of these problems for you.. Worth a try
Sent from my SM-G900I using Tapatalk
dgcruzing said:
Not sure if it counts but there is a software fix for bluetooth in the Bluetooth mod .. Under hardware mods..
There might be a connection between the Bluetooth stack and other software coming in..
All I know is that this slight change of drivers for us has saved us from doing hardware mods and for now its working perfectly for a number of us..
Check it out if you get problems as a slight chance via settings may fix some of these problems for you.. Worth a try
Sent from my SM-G900I using Tapatalk
Click to expand...
Click to collapse
Cheers- I'll keep this in mind if it happens again - it definitely seemed like a software issue.
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?
I've noticed in a few telegram channels that users are experiencing an issue with making calls on Bluetooth headsets. The audio is not heard at our end and at the other person's end they hear a lot of crackle. I've never made logs before but this is attached just incase anyone can use the information.
I am on CRDroid latest build.
Could this setting be why BT calls doesn't work for some speakers/headphones?
JimmyEatFood said:
Could this setting be why BT calls doesn't work for some speakers/headphones?
Click to expand...
Click to collapse
No its a kernel issue. That guy is a fantastic developer so i am sure that he will get it sorted.
But If you grow weary of waiting, the current Xiaomi.EU rom doesn't have any issues.
tsongming said:
No its a kernel issue. That guy is a fantastic developer so i am sure that he will get it sorted.
But If you grow weary of waiting, the current Xiaomi.EU rom doesn't have any issues.
Click to expand...
Click to collapse
It's happening with a variety of different kernels and roms it seems after being in a few different telegram channels. Affecting some users and not others. Happens with one of my BT devices and not the other. Other people reporting the same.
It's just annoying more than anything I guess as I don't want to walk around with a speaker attached to my head to be able to make Bluetooth calls.
Hi,
Any progress about issue?
This isn't just affecting the Mi 8. It seems to be a problem over a wide range of bluetooth chips, in particular those made by Broadcom. I haven't heard of a fix being available, however.
Bluetooth devices that use the SBC codec also aren't affected, AAC is another story, though.