Database Develop

[Q] FM Transmitter

Most references I see to the chip in the Galaxy S for handling the Bluetooth, WiFi, and FM are listed as a broadcom. I was unable to locate a chipset on broadcoms site that lists support for Bluetooth 3.0, but I did notice nearly all of the broacom chips that support FM radio support it as RX and TX. Is the chip in the Galaxy S a broadcom, and if so has anyone found a way to enable the TX portion? It was more a curiosity question as I'm sure the TX power is low as is the sound quality, but hey if it does offer it, why not exploit it?
Maybe this has already been answered for the Samsungs and I just missed it in my searches. The searches only returned other brand/model phones.
The other question I was wondering is if the FM range is hard coded in the chip, or if it's a soft radio where the RX frequencies could be shifted to say the Weather Band in the US, or some other area near the normal FM radio range? Again, this is all more out of curiosity than anything.
Edit>
I found this one that supports BT 3.0 and still lists FM RX/TX
BCM20751 - Bluetooth® + GPS + FM Combination ('Combo') Chip Solution

Well, this is like the only thing I'm missing from my old Nokia N97.. So I would like it.

mstrandbo said:
Well, this is like the only thing I'm missing from my old Nokia N97.. So I would like it.
Click to expand...
Click to collapse
Well, after looking at the Samsung source for the I9000, it appears they use the SI4709 chip for FM reception, and that chip doesn't support FM TX, just RX.

S4 active & Bluetooth APt-x

I recently purchase the At&t S4 active and a pairs of Sennheiser MM-550X,
Those of you who don't know apt-x is codec for bluetooth to keep the sound quality as the original (really close to) source sound files,
in compare to normal Bluetooth which downgrade sound quality to near 120Kbps.
SGS4 active supposed to support this but on the web there's so little information about it,
So.. I want to know how can i confirm Mine got the Apt-x? from what I heard some android version Not support this..
Does Acid audio engine support this?
Is anyone tried?
Thanks!

No need to create two identical threads.

[Q] Bluetooth 4 /Android 4.3 update - does The Xperia Z1 now support Bluetooth Smart?

Since the Z1 supports Bluetooth 4.0, therefore following the Android 4.3 update - does The Xperia Z1 now support Bluetooth Smart?

What is Bluetooth Smart
Sent from my C6902 using XDA Premium 4 mobile app

Yes it does.
---------- Post added at 05:23 PM ---------- Previous post was at 05:22 PM ----------
ron76426 said:
What is Bluetooth Smart
Sent from my C6902 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
http://en.m.wikipedia.org/wiki/Bluetooth_low_energy

OK, so I borrowed a Beets BLU Bluetooth Smart Heart rate monitor and it would see the device in the available devices list occasionally (1 out of 4) but would not pair, I also borrowed a Garmin Premium HRM (ANT+) and could not get that to connect at all.
I could of course be doing something completely wrong especially with the ANT+ device as I can find no instructions on home to pair the device
instructions or help with either?

tallguy_uk_98 said:
OK, so I borrowed a Beets BLU Bluetooth Smart Heart rate monitor and it would see the device in the available devices list occasionally (1 out of 4) but would not pair, I also borrowed a Garmin Premium HRM (ANT+) and could not get that to connect at all.
I could of course be doing something completely wrong especially with the ANT+ device as I can find no instructions on home to pair the device
instructions or help with either?
Click to expand...
Click to collapse
You might just have be having the typical 290 issues with Bluetooth where devices can't pair. Maybe someone else will chime in with more feedback, but I don't have any BLE devices to test.

Ok So I managed to get the ANT+ device to work by installing ANT Radio Service & ANT+ Plugins from the play store following guidance from this website
http://www.thisisant.com/consumer/ant-101/ant-in-phones/
Which was really helpful, especially as the Z1 is slated as being ANT+ native supporting but still needs additional software drivers installed, but there is nothing on Sony's documentation to drive you to this conclusion.
As for the Bluetooth 4.0/Bluetooth Smart device still no joy - Anybody any further ideas or is it just a case of waiting for a bug fix?

Install BLE Heart Rate Monitor from store. In the settings pair with your HRM. Don't try and pair through phone bluetooth settings. Bluetooth smart isn't designed to be paired like this apparently.

SeanyC said:
Install BLE Heart Rate Monitor from store. In the settings pair with your HRM. Don't try and pair through phone bluetooth settings. Bluetooth smart isn't designed to be paired like this apparently.
Click to expand...
Click to collapse
Thanks for the info - partially works, connects but drops the connection routinely even after refreshing the Bluetooth system , as suggested by the app - probably needs a bug fix

This happens sometimes unfortunately. I had no problems on my Nexus 4.

I would like to understand whether it's possible to activate bluetooth 4 and bluetooth "classic" individually. The background: I want to use a bluetooth 4 tag in combination with tasker to automate certain things once the tag is within reach. I got a Texas Instruments SensorTag which is recognized by the Z1 and can be accessed via the TI software. Tasker is currently being improved to play with BT4 devices. The issue is that there is just a single bluetooth switch within Android, but of course I want to avoid the power hungry classic bluetooth and use bluetooth instead.
Any ideas if there is a solution? Maybe via an Xposed module?
Cheers,
Torsten

sumerland said:
I would like to understand whether it's possible to activate bluetooth 4 and bluetooth "classic" individually. The background: I want to use a bluetooth 4 tag in combination with tasker to automate certain things once the tag is within reach. I got a Texas Instruments SensorTag which is recognized by the Z1 and can be accessed via the TI software. Tasker is currently being improved to play with BT4 devices. The issue is that there is just a single bluetooth switch within Android, but of course I want to avoid the power hungry classic bluetooth and use bluetooth instead.
Any ideas if there is a solution? Maybe via an Xposed module?
Cheers,
Torsten
Click to expand...
Click to collapse
It is already BT 4.0 as long as device you use has it too, no further activation needed. If you try to use it with device that has older version like BT 2.1 functionality of BT 4.0 will be downscaled to work with older version.

zimbashka said:
It is already BT 4.0 as long as device you use has it too, no further activation needed. If you try to use it with device that has older version like BT 2.1 functionality of BT 4.0 will be downscaled to work with older version.
Click to expand...
Click to collapse
Many thanks! This sounds good! To be fully sure: once a BT2.1 device disconnects, BT falls "back" to 4.0? The longer I think about it I wonder whether it really makes a difference if a phone waiting for a connection is using BT2.1 or BT4.0. Do the 4.0 improvements have an effect on the power consumption before the connection is established?

sumerland said:
Many thanks! This sounds good! To be fully sure: once a BT2.1 device disconnects, BT falls "back" to 4.0? The longer I think about it I wonder whether it really makes a difference if a phone waiting for a connection is using BT2.1 or BT4.0. Do the 4.0 improvements have an effect on the power consumption before the connection is established?
Click to expand...
Click to collapse
It is more like imposed limits by older version go away. Power consumption in BT 4.0 is more like: little power used to connect, pair and then it uses more power when large amount of information needs to be transferred (like opening higher bandwidth based on Wi-Fi that uses more power for shorter period of time). While discovering device awaits connection it consumes very little of battery on either 2.1 or 4.0. from what I can see versions of BT evolve in added functionality that is based mainly on transfer rate as well as better power management.
Here more info:
http://en.wikipedia.org/wiki/Bluetooth

[Q] Bluetooth rSAP support

Hi folks,
would it anyhow be possible to get bluetooth rsap working by using one of those custom roms or kernels available here ?
I'm pretty satisfied with this phone, but the missing rsap in combination with my car is annoying.
Could anyone help ?
Thanks a lot in advance !

Tsadan said:
Hi folks,
would it anyhow be possible to get bluetooth rsap working by using one of those custom roms or kernels available here ?
I'm pretty satisfied with this phone, but the missing rsap in combination with my car is annoying.
Could anyone help ?
Thanks a lot in advance !
Click to expand...
Click to collapse
is rSAP supported by stock rom? If so I can try to get it working on CM based ones.

LuK1337 said:
is rSAP supported by stock rom? If so I can try to get it working on CM based ones.
Click to expand...
Click to collapse
No, rSAP is not supported in stock. Searching around in the net showed, that the kernel of the stock rom has been complied without rSAP.
build.prop shows:
Code:
#
# system property for Bluetooth SAP support
# Motorola disabled SAP
#
ro.qualcomm.bluetooth.sap=false
What I was wondering, wouldn't it be possible to just activate what Moto disabled in a custom rom/kernel ?
What else would be missing in an android build to provide access to the SIM by a bluetooth device ?
Best regards
Tsadan

Update for CM13
Hi Guys,
now, just a view days ago I updated my Moto G 2014 to CM13 aka Android 6.
The release of it gave new hope to get SAP support for my phone, as per feature list of Android Marshmallow, SAP is now natively included in Android:
[Quote from Android.com]
<snip>
Connectivity
More power efficient Bluetooth Low Energy (“BLE”) scanning for nearby beacons and your accessories.
Hotspot 2.0: Connect to compatible Wi-Fi networks seamlessly and securely.
Bluetooth SAP: Make calls from your carphone using your phone’s SIM.
Portable Wi-Fi hotspot now supports 5GHz frequency bands.
</snip>
I was a bit disappointed when I noticed, that there seems no option to activate SAP for a bluetooth connection.
My question now would be: Is there now SAP support in CM13 on Moto G 2014 ? When yes, could you give me a hint how to activate it ? When there is actually no support for SAP, is it planned to implement it ?
Thanks in advance, best regards
Tsadan

Tsadan said:
Hi Guys,
now, just a view days ago I updated my Moto G 2014 to CM13 aka Android 6.
The release of it gave new hope to get SAP support for my phone, as per feature list of Android Marshmallow, SAP is now natively included in Android:
[Quote from Android.com]
<snip>
Connectivity
More power efficient Bluetooth Low Energy (“BLE”) scanning for nearby beacons and your accessories.
Hotspot 2.0: Connect to compatible Wi-Fi networks seamlessly and securely.
Bluetooth SAP: Make calls from your carphone using your phone’s SIM.
Portable Wi-Fi hotspot now supports 5GHz frequency bands.
</snip>
I was a bit disappointed when I noticed, that there seems no option to activate SAP for a bluetooth connection.
My question now would be: Is there now SAP support in CM13 on Moto G 2014 ? When yes, could you give me a hint how to activate it ? When there is actually no support for SAP, is it planned to implement it ?
Thanks in advance, best regards
Tsadan
Click to expand...
Click to collapse
We aren't planning on implementing SAP and I doubt it's possible as it needs RIL driver support.
Code:
For this profile to work, the RIL driver must allow for this feature
to be used, and it must provide the API needed. The API is based on
protoBuf.

Please check the news on the android-rsap homepage. I found out how to enable rSAP on those Qualcomm phones where it did not work so far.

MTCB/MTCC Rom issues with ALPconnect app and Bluetooth

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?