LG Optimus 4X HD and Android 4.3 should support a BLE aka Bluetooth Smart. However I was unable to pair my bluetooth 4 heart rate monitor and use it.
So I looked into it and found that there was not "android.hardware.bluetooth_le.xml" file which I believe is necessary for BLE connections. I also found it in one of the LG Optimus G's custom roms. I put the file to system\etc\permissions file, extracted and installed the zip. Still I was unable to pair the device. I have tried latest CM, PA and Vanir roms.
Have you been able to get BLE working with your devices? Is there something developers might be able to do?
Thundermand said:
LG Optimus 4X HD and Android 4.3 should support a BLE aka Bluetooth Smart. However I was unable to pair my bluetooth 4 heart rate monitor and use it.
So I looked into it and found that there was not "android.hardware.bluetooth_le.xml" file which I believe is necessary for BLE connections. I also found it in one of the LG Optimus G's custom roms. I put the file to system\etc\permissions file, extracted and installed the zip. Still I was unable to pair the device. I have tried latest CM, PA and Vanir roms.
Have you been able to get BLE working with your devices? Is there something developers might be able to do?
Click to expand...
Click to collapse
have you tried it on stock rom?
Flying_Bear said:
have you tried it on stock rom?
Click to expand...
Click to collapse
No I haven't because to my knowledge Android 4.3 is needed because of its Bluetooth API.
E: I finally got it working. All that was needed was the bluetooth_le.xml and BLE Heart Rate Monitor -app from Google Play. It' still doesn't pair in in the Anroid's settings though. I am not sure yet if it works with other apps.
I would recommend developers to add bluetooth_le.xml to their roms
.
I am also having this problem. I have only tried cyanogenmod 11 though but I cannot get my ble heartrate monitor working.
Is there an optimus 4x rom that supports ble, or any plan on implementing in cyanogenmod or other roms?
All roms based on P880-dev sources have BLE support.
Is the CM11 based on P880-dev? It would seem it isn't because it wasn't possible to use the BLE with it. Instead I had to manually place the .xml file. It is quite impractical to do this every time instead of using OTA updates just because of a lack of one small file.
I have been using lately Vanir and unofficial CM11 and as many other roms they do support the BLE so I don't understand why the official CM11 couldn't as well.
Thundermand:
were you able to pair your bluetooth device in any of the roms?
I am able to use my heartrate monitor but only in some downloaded apps (BLE Heart Rate Monitor, IpSensorMan). When I am trying to pair it in the bluetooth setting it does nothing.
I have a noname monitor I hope that it is not the problem.
TJHookr said:
Thundermand:
were you able to pair your bluetooth device in any of the roms?
I am able to use my heartrate monitor but only in some downloaded apps (BLE Heart Rate Monitor, IpSensorMan). When I am trying to pair it in the bluetooth setting it does nothing.
I have a noname monitor I hope that it is not the problem.
Click to expand...
Click to collapse
No, the pairing in Android settings doesn't work (it didn't work on 4.3 too). I might have the same cheap noname HRM from eBay as you do. But all the programs which support Bluetooth Smart have built-in pairing so I suppose that the problem is more Android than HRM related.
You should try Polar Beat and Ride with GPS too. They are fine apps but there are some problems with RWGPS and my HRM.
Thundermand said:
No, the pairing in Android settings doesn't work (it didn't work on 4.3 too). I might have the same cheap noname HRM from eBay as you do. But all the programs which support Bluetooth Smart have built-in pairing so I suppose that the problem is more Android than HRM related.
You should try Polar Beat and Ride with GPS too. They are fine apps but there are some problems with RWGPS and my HRM.
Click to expand...
Click to collapse
Yes we probably have the same monitor.
Pairing would be important for me as I have been using endomondo pro for some time, and it has no built in pairing. But I'll try the ones you suggested, thanks.
Thundermand said:
No I haven't because to my knowledge Android 4.3 is needed because of its Bluetooth API.
E: I finally got it working. All that was needed was the bluetooth_le.xml and BLE Heart Rate Monitor -app from Google Play. It' still doesn't pair in in the Anroid's settings though. I am not sure yet if it works with other apps.
I would recommend developers to add bluetooth_le.xml to their roms
.
Click to expand...
Click to collapse
I got it working, too, using android.hardware.bluetooth_le.xml and it worked fine for a while but after an update of Cyanogenmod (cm-11-20140503-NIGHTLY) it stopped working. I looked and the file was gone. But even after putting it back in /etc/permissions/, it doesn't work anymore.
Any ideas?
giza1928 said:
I got it working, too, using android.hardware.bluetooth_le.xml and it worked fine for a while but after an update of Cyanogenmod (cm-11-20140503-NIGHTLY) it stopped working. I looked and the file was gone. But even after putting it back in /etc/permissions/, it doesn't work anymore.
Any ideas?
Click to expand...
Click to collapse
It has been disabled (commit).
Adam77Root said:
It has been disabled.
Click to expand...
Click to collapse
I use the unofficial cyanogenmod. I thought it was p880-dev based, at least partly (I remember there was a time when ble worked on unofficial when it was not working on official). Was it necessary to disable it also on unofficial? Did it cause that big of problem. Unfortunately this is a feature that I can not do without.
TJHookr said:
I use the unofficial cyanogenmod. I thought it was p880-dev based, at least partly (I remember there was a time when ble worked on unofficial when it was not working on official). Was it necessary to disable it also on unofficial? Did it cause that big of problem. Unfortunately this is a feature that I can not do without.
Click to expand...
Click to collapse
@Demetris included the disabling commit, because it got merged into official device tree.
I"ll revert it. Think is why Ricardo disable it in first place. I thought there was a bug or something
Sent from my Barnes & Noble Nook Tablet using Tapatalk
Demetris said:
I"ll revert it. Think is why Ricardo disable it in first place. I thought there was a bug or something
Sent from my Barnes & Noble Nook Tablet using Tapatalk
Click to expand...
Click to collapse
Hmm, I saw this: Add support for BLE and installed cm-11-20140605-NIGHTLY but BLE still doesn't work. Has the change not yet been merged? I'm relatively new to git and github, so I'm not sure if I understand how and when a change should show up in the NIGHTLY builds.
giza1928 said:
Hmm, I saw this: Add support for BLE and installed cm-11-20140605-NIGHTLY but BLE still doesn't work. Has the change not yet been merged? I'm relatively new to git and github, so I'm not sure if I understand how and when a change should show up in the NIGHTLY builds.
Click to expand...
Click to collapse
That's not the official repo.
Any news on this? Is BLE integrated in CM11, or are there any plans to do so? If not, can anyone please recommend a ROM that has BLE confirmed as working?
Thanks
ursinne said:
Any news on this? Is BLE integrated in CM11, or are there any plans to do so? If not, can anyone please recommend a ROM that has BLE confirmed as working?
Thanks
Click to expand...
Click to collapse
I 'm waiting for up
Same question but now for 5.0 roms.
Are there any information on this? I consider buying a BLE device and would like to know whether it would work.
Related
After some period of works on debugging every element of the android bluetooth stack i've found the solution, and it was so simple...
Taken from this post: (it seems that hero has the same bluetooth device as our tattoo)
http://forum.xda-developers.com/showthread.php?t=704976
Yes, it's enough to copy brf6350.bin from that thread to /etc/firmware/ to fix headset audio call problem.
I haven't an A2DP device, tell me if there are undesired issue...
I'll update SPQRom soon...
i have a nokia bh-214 and i have really no problem with the bluetooth headset ... the media controller work fine too
jigsaw956 said:
i have a nokia bh-214 and i have really no problem with the bluetooth headset ... the media controller work fine too
Click to expand...
Click to collapse
This fix is valid for every custom rom not based on the official ROM (AOSP, Cyanogen...), the official rom is OK
ivendor said:
After some period of works on debugging every element of the android bluetooth stack i've found the solution, and it was so simple...
Taken from this post: (it seems that hero has the same bluetooth device as our tattoo)
http://forum.xda-developers.com/showthread.php?t=704976
Yes, it's enough to copy brf6350.bin from that thread to /etc/firmware/ to fix headset audio call problem.
I haven't an A2DP device, tell me if there are undesired issue...
I'll update SPQRom soon...
Click to expand...
Click to collapse
You should recompile with latest source from CM
I've compiled myself with a slightly modified version of your vendor and it's fair bit less buggy now
ivendor said:
After some period of works on debugging every element of the android bluetooth stack i've found the solution, and it was so simple...
Taken from this post: (it seems that hero has the same bluetooth device as our tattoo)
http://forum.xda-developers.com/showthread.php?t=704976
Yes, it's enough to copy brf6350.bin from that thread to /etc/firmware/ to fix headset audio call problem.
I haven't an A2DP device, tell me if there are undesired issue...
I'll update SPQRom soon...
Click to expand...
Click to collapse
very nice! can you make 2 release? stable (6.0) and rc (6.1)?
Great work!!
francians said:
very nice! can you make 2 release? stable (6.0) and rc (6.1)?
Click to expand...
Click to collapse
i'll publish new version soon...
ivendor said:
This fix is valid for every custom rom not based on the official ROM (AOSP, Cyanogen...), the official rom is OK
Click to expand...
Click to collapse
i use your rom with 4.1 version
jigsaw956 said:
i use your rom with 4.1 version
Click to expand...
Click to collapse
The problem was with audio in phone call with, i think, all headset bluetooth. A2DP music was working fine.
I bought a handfree kit for ad2p, that part worked. But no sound for calls.
Tanks ivendor, i'll be able to get rid of my wired hand free now
ivendor said:
The problem was with audio in phone call with, i think, all headset bluetooth. A2DP music was working fine.
Click to expand...
Click to collapse
yes but there is a micro for call with the nokia and the call works fine with
subjective .. i know
but i have a hp touch pad and im not sure what to install. im leaning towards aokp because i have it on my phone and its amazing.... but is there anything better?
i just realized i have cyanogenmod version 9.0.0 rc0
i want to install nightly rom
but do i have to be on cyanogenmod v9 alpha 3?
when i look up alpha 3, it says cyanogenmod v7?
i have not tried every single one out there, but out of the ones i have tried, i have liked aokp the best. second would be oat's, but i dont like his inclusion of the hd go app launcher (or whatever its called).
oat's http://forum.xda-developers.com/showthread.php?t=1557111
aokp http://forum.xda-developers.com/showthread.php?t=1537636
I like the CM9 official nightlies. Used to run CherryKang until the dev stopped updating it.
CM9 right now has the bleeding edge with the mic working properly. There is also a headphone fix you can flash to make it so you can plug in headphones after the app is already playing audio.
NapalmDawn said:
CM9 right now has the bleeding edge with the mic working properly. There is also a headphone fix you can flash to make it so you can plug in headphones after the app is already playing audio.
Click to expand...
Click to collapse
I have been looking for this, can someone link me to it?
I'm having good luck with the nightlies which I install regularly through goomanager. But for the camera, which I don't need, everything seems to be working smoothly and reliably. Your mileage may vary (as I read these threads).
I find regular old CM9 to work just fine. Everything I need works fine now that the microphone has started working. I never use front facing cameras, even the one on my Droid 3 goes unused most of the time so that isn't an issue for me.
theReDkoolAiD said:
I have been looking for this, can someone link me to it?
Click to expand...
Click to collapse
Here you go sir. http://forum.xda-developers.com/showthread.php?t=1568685
It's in the thread.
Or more specifically http://goo.im/devs/jcsullins/cmtouchpad/testing/update-cm9-tenderloin-headphones-201207091600.zip
Hope this helps.
Anyone have a bluetooth controller that they can try with the One for me? I have an awesome little controller that i freakin love and it doesnt seem to be working properly with the HTC one. it says its paired but nothing on the phone uses it. Ive enabled it and everything. If anyone can give me some feedback id be very greatful!
Thanks
HaiKaiDo said:
Anyone have a bluetooth controller that they can try with the One for me? I have an awesome little controller that i freakin love and it doesnt seem to be working properly with the HTC one. it says its paired but nothing on the phone uses it. Ive enabled it and everything. If anyone can give me some feedback id be very greatful!
Thanks
Click to expand...
Click to collapse
If you are running a custom kernel that is likely the cause. I have the same problem with using a controller on my HTC One. The Sprint One is known to have issues with bluetooth. However one developer is working to resolve the issue soon (hopefully).
thicklizard said:
Bluetooth source is botched from HTC just for the Sprint variant. So on stock kernel you'll be fine but until fixed (which I'm working on) all custom kernels you won't be able to use bluetooth for calls. Streaming works fine.
Click to expand...
Click to collapse
Apparently HTC will be releasing the source for the new kernel soon.
http://forum.xda-developers.com/showpost.php?p=42438876&postcount=767
Hi,
As the questions says, I've got a garmin heartrate monitor working with the ANT+ app but I can't get any other app to see it (mainly runtastic pro) - wondering if anyone has any success with it?
N.
I might trying updating to the latest firmware, currently on 14.1.g.1.518.
I've got a Garmin monitor, and a PowerCal monitor running with IPBike. I tried to get the Garmin Fit app working but there's no option to add the sensors.
Iam using My tracks and Garmin heart rate monitor.Works well.Dont forget to download and install ANT Radio Service.
n33 said:
Iam using My tracks and Garmin heart rate monitor.Works well.Dont forget to download and install ANT Radio Service.
Click to expand...
Click to collapse
Anyone using ANT+ with anything but the stock ROM?
I'm using rooted stock rom(NUT .757), but ANT+ is not working.
frido_pl said:
I'm using rooted stock rom(NUT .757), but ANT+ is not working.
Click to expand...
Click to collapse
Oh no that is a nightmare. Maybe I won't be upgrading then!
I'm on NUT's .136 and ANT+ is unreliable but just about works. For example when I run an ANT+ app, the bluetooth icon appears. If I close bluetooth, ANT+ stops working! Both bluetooth and wifi continually switch themselves on without any intervention from me on this ROM. Anyway, the ANT+ often mysteriously stops working during a (bike) ride and I either have to toggle bluetooth on and off (twice) or reboot to get it working again.
Good luck, I do not think many Android devs are also fitness orientated.....
Doh, you cannot turn off BT, that's how the ANT+ works on the device.
madd0g said:
Doh, you cannot turn off BT, that's how the ANT+ works on the device.
Click to expand...
Click to collapse
Interesting - I was using my Samsung Galaxy Nexus with a ANT+ dongle which did not exhibit this behaviour i.e. I did not need bluetooth to be switched on to enable the ANT+. And my understanding is bluetooth and ANT+ are separate radios. Do you know different?
frumpy said:
Interesting - I was using my Samsung Galaxy Nexus with a ANT+ dongle which did not exhibit this behaviour i.e. I did not need bluetooth to be switched on to enable the ANT+. And my understanding is bluetooth and ANT+ are separate radios. Do you know different?
Click to expand...
Click to collapse
That because Bluetooth and ANT+ are integrated in the same Chip so you have to enable Bluetooth to let it work. In Samsung probably they are separated. Many Manufacturing use different Chips Radio so some can have this behaviour.
I recently upgraded to the latest (4.4.2), lo and behold bluetooth is not activated when I use ANT+
frumpy said:
I recently upgraded to the latest (4.4.2), lo and behold bluetooth is not activated when I use ANT+
Click to expand...
Click to collapse
That don't mean Bluetooth and ANT+ are not in the same chip.
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?