Newbe Dev Stack

Answer : The following terminal command should enable Bluetooth via adb shell or Terminal Emulator app: su am start -a android.bluetooth.adapter.action.REQUEST_ENABLE On most versions of Android, this command will present a pop-up window to the user asking to confirm request to enable BT. I believe this was done for security purposes whenever an app that is not system is toggling BT. I haven't found a way to disable BT via a shell command unfortunately. With WiFi it's a lot easier, and does not prompt user for permission: su svc wifi enable will turn it on, and su svc wifi disable will turn it off. in android.bluetooth.IBluetoothManager, there some parameters TRANSACTION_registerAdapter = (android.os.IBinder.FIRST_CALL_TRANSACTION + 0); TRANSACTION_unregisterAdapter = (android.os.IBinder.FIRST_CALL_TRANSACTION + 1); TRANSACTION_registerStateChangeCallback = (android.os.IBinder.FIRST_CALL_TRANSACTION + 2); TRANSACTION_unregisterStateChangeCallback...

Answer : OP here – I'd just like to add to the answer below, that I've been in contact with Apple Support. Explanation Apple claims that the poor Mono 8kHz quality which affects recording and indeed simultaneously playback on Mac when the AirPod microphones are activated, is because the SCO codec then gets employed over the entire Mac audio system. This is supposedly "expected behaviour" when trying to use the AirPods and other Bluetooth headsets together with a computer, according to Apple. The AAC codec is normally used when just listening to playback on the AirPods. It's just very unfortunate that SCO – low-quality as it may be – upon AirPod microphone activation is not only limited to doing recording, but also displaces AAC and audio playback. Apple Support claims that Apple is looking at this issue, and that improvements might be coming in future firmware updates, but I did not interpret that as a promise to be honest. But for the time being, I'd ...

Answer : UPDATE: The btsnoop hci log seems to be getting phased out of the user-accessible areas on a lot of phones. Assuming you have hci logging enabled, you can get a bugreport adb bugreport anewbugreportfolder Then decompress the folder. If you're lucky there is an 'FS' folder that contains the btsnoop_hci.log log several layers down (not sure why some phones have this and some don't.) If you don`t have it, grab the bug report text file that looks like this bugreport-2018-08-01-15-08-01.txt Run btsnooz.py against it. Per Google`s instructions, To extract snoop logs from the bug report, use the btsnooz script. Get btsnooz.py. Extract the text version of the bug report. Run btsnooz.py on the text version of the bug report: btsnooz.py BUG_REPORT.txt > BTSNOOP.log As of 8/1/18 the link to btsnooz is here: https://android.googlesource.com/platform/system/bt/+/master/tools/scripts/btsnooz.py LEGACY ANSWER: You can see where your phone is storing th...

Answer : One way to solve the problem is to: unpair the device run the following command on terminal: sudo pkill pulseaudio and then pair again the speaker via bluetooth. The speaker is now displayed on the output audio list, which needs to selected for obtaining output sound. Remember to, under Sound Settings, change Mode to High Fidelity Playback (A2DP Sink) . This is what is working for me for Bose QuietComfort 35 on Ubuntu 16.04. pauvcontrol didn't do it for me, and neither did the numerous settings changes and module loadings recommended elsewhere. So give this a try: Install blueman sudo apt install blueman Delete the paired device in the bluetooth settings. Run these commands in terminal: $ sudo pkill pulseaudio $ sudo /etc/init.d/bluetooth restart Turn off headphones. Turn on headphones, and press green/go until headphones notification voice says "Ready to pair." Launch blueman, and from the upper right menu, right-click the icon to b...

Answer : Solution from reddit from @ashughes in an above comment -https://www.reddit.com/r/linuxquestions/comments/bc15f8/bluetooth_mouse_is_laggy_very_limited_pollrate/ez3ufhs/ sudo nano /var/lib/bluetooth/xx\:xx\:xx\:xx\:xx\:xx/yy\:yy\:yy\:yy\:yy\:yy/info where xx:xx.... is pc bluetooth address and yy:yy... is the mouse bluetooth address. In the file, I added the section at the end: [ConnectionParameters] MinInterval=6 MaxInterval=7 Latency=0 Timeout=216 You may also need to reconnect the mouse. I also tracked this proposal on ubuntu bug here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824559?comments=all I'm using Ubuntu 18.04 on a Dell Precision 7740 laptop and a Logitech MX Master 3 and had a pretty bad lag over Bluetooth. Setting the parameters as noted in @alenz316's answer did not make a difference for me. However, @Eraph's settings in that thread DID work. I originally found the answer on https://forum.manjaro.org/t/logitech-mx-master...

Answer : First of all, your bluetooth audio receiver (Philips AEA2700) supports decoding aptX. That's listed in its specification. Then it comes to the transmitter. AFAIK there are two types of transmitter for bluetooth audio. The first type is a USB audio class device (i.e. a USB sound card) with hardware codec. Examples are the ones from Creative, such as BT-W2. For this type of transmitter, you can safely assume that it will automatically use the "best" codec (i.e. aptX Low-Latency > aptX > SBC) available on both itself and the receiver. And I don't suppose you have ways other than checking its specification to know whether aptX is available. The second type is a general bluetooth transmitter that supports the A2DP profile. The ones that are equipped in laptops are pretty much always of this type. This type of transmitter usually relies on software codec(s), which are provided its driver / software stack, such as CSR Harmony . Take CSR Harmony ...