FORUMS
Remove All Ads from XDA

Improve Bluetooth audio quality on headphones without aptX or LDAC

173 posts
Thanks Meter: 143
 
By ValdikSS, Senior Member on 22nd August 2018, 06:13 PM
Post Reply Email Thread
The test is over. I'm no longer accepting libraries to patch.
The latest information is available here

Many note low sound quality and lack of high frequencies when using the standard SBC Bluetooth codec, which is supported by all headphones and other Bluetooth devices. A common recommendation to get better sound quality is to buy devices and headphones with aptX or LDAC codecs supported. These codecs require licensing fees, so devices with them are more expensive.

It turns out that the low quality of SBC is caused by artificial limitations of all current Bluetooth stacks and headphones' configuration, and this limitation can be circumvented on any existing devices.
Everyone interested in Bluetooth audio, please take part in high-bitrate SBC compatibility testing on various headphones, receivers, stereo systems, or automotive head units.
If the vast majority of devices work with high bitrates, I will make a patch for Android and send it to AOSP and third-party ROMs, and high quality Bluetooth audio will be available to everyone on any headphones and smartphones, regardless of codecs with licensing fees.



Short technical information about SBC codec
SBC has lots of different parameters that are negotiated during the connection setup phase:
  • Audio channel type and number: Joint Stereo, Stereo, Dual Channel, Mono;
  • Number of frequency bands: 4 or 8;
  • Number of audio blocks in one packet: 4, 8, 12, 16;
  • Quantization bit allocation algorithm: Loudness, SNR;
  • Maximum and minimum bit pool used in quantization process: usually 2-53.

The decoder is required to support any combination of these parameters. Encoder may implement only a part of them.
Existing Bluetooth stacks usually negotiate the following profile: Joint Stereo, 8 bands, 16 blocks, Loudness, bitpool 2..53. This profile encodes 44.1 kHz audio with a bitrate of 328 kbps.
Bitpool parameter directly affects the bitrate within the same profile: the higher it is, the higher the bitrate, and hence the quality.
However, the bitpool parameter is not bound to a specific profile. The bitrate is also significantly affected by other parameters: audio channel type, number of frequency bands, number of audio blocks. You can increase the bitrate indirectly by negotiating non-standard profiles, without changing the bitpool.


For example, Dual Channel encodes channels separately, using the entire bitpool for each channel. Forcing the device to use Dual Channel instead of Joint Stereo will get us almost doubled bitrate at the same maximum bitpool, 617 kbps.
To me it feels that bitpool should be an internal variable. It is an A2DP specification design fault that bitpool value is not bound to other codec parameters and only defined as a global value.
These fixed Bitpool and Bitrate values originate from recommended values for high-quality audio. But the recommendation is not an excuse to limit the profile to these values.

A2DP specification v1.2, which was active from 2007 to 2015, requires all decoders to work correctly with bitrates up to 512 kbps:
Quote:

The decoder of the SNK shall support all possible bitpool values ​​that do not result in the excess of the maximum bit rate. This profile limits the available maximum bit rate to 320kb/s for mono, and 512kb/s for two-channel modes.

In the new version of the specification there is no bitrate limitation. It is assumed that modern headphones released after 2015 with EDR can support bitrates up to 730 kbps.

For some reason, all currently tested Bluetooth stacks (Linux (PulseAudio), Android, Blackberry and macOS) have artificial restrictions of maximum bitpool parameter, which directly affects the maximum bitrate. But this is not the biggest problem, almost all headphones also limit the maximum bitpool value to 53.
As I've already seen in my tests, most devices work fine on a modified Bluetooth stack with a bitrate of 507 kbps, without interrupts and crackling. But such a bitrate will never be negotiated under normal conditions, with stock Bluetooth stacks.

How to test on a PC
High bitrate SBC headphone compatibility test is the easiest to perform on the PC with a Bluetooth adapter. I've prepared Ubuntu image with a modified Bluetooth stack, which can be run as in a virtual machine (by connecting Bluetooth adapter as a USB device inside the virtual machine, it also works with the adapters built into the laptops) or by booting from the USB flash drive. This image uses the following profile: Dual Channel, 8 bands, 16 blocks, Loudness, bitpool 2..41, 44.1 kHz, which provides 485 kbps bitrate.
See the attachment in the end of this post.

Running in a VM
  1. Download Virtualbox and Virtualbox Extension Pack: https://www.virtualbox.org/wiki/Downloads;
  2. Install Virtualbox, start it;
  3. Install Extension Pack using File → Preferences → Extensions;
  4. Create new virtual machine: Linux, Ubuntu (64-bit), 1024 RAM. Do not create a HDD.
  5. Navigate to virtual machine settings, in Storage choose Controller: IDE, Empty, press CD icon → Choose virtual optical disk file;
  6. Select downloaded bluetooth-dualchannel-test-ubuntu-18.04.1-desktop-amd64.iso;
  7. Save and close settings window, start virtual machine;
  8. Right-click USB cable icon in the bottom right, select your Bluetooth adapter;

Running on a PC
The image supports BIOS/CSM and UEFI booting.
  1. Burn the image to a USB flash drive using Etcher: https://etcher.io/. This operation will delete all existing files on a USB drive.
  2. Turn off the PC;
  3. Insert USB flash drive, turn on the PC and press boot order button (usually Esc or F12);
  4. Select your USB flash drive.

Performing the test
  1. (optional but recommended) Double click on "Btsnoop Dump" script on the desktop. It will start Bluetooth data capture for later analysis. Do not close terminal window.
  2. Switch the headphones to pairing mode;
  3. Click to the arrow in top right corner, select Bluetooth icon → Bluetooth Settings;
  4. Choose your headphones, wait until pairing is complete and close the window;
  5. Set Ubuntu volume to about 2/3. Also decrease volume using headset buttons as it could be very loud after pairing.
  6. Open "music" folder, play "testrecord1.flac";
  7. (optional but recommended) Close player, close terminal window. This will stop data capture.
  8. (optional but recommended) Open Firefox browser, upload data dump (btsnoop_hci.btsnoop on the desktop) to https://btcodecs.valdikss.org.ru/
  9. You can listen to other music in the music folder, or upload your own;
  10. Post in this topic your headphone model and test results.
There should be no cracklings, audio interruption or other sound distortion in the headphones. If you hear a good high-quality sound, that means your headphones support audio with a bit rate of 485 kbps.
If you upload data to the server, please carefully follow the algorithm above. Especially, if you power off the headphones or disconnect after pairing, it's important to connect to the headphones manually from the bluetooth settings, do not allow auto connection!
The Following 28 Users Say Thank You to ValdikSS For This Useful Post: [ View ] Gift ValdikSS Ad-Free
 
 
22nd August 2018, 06:14 PM |#2  
OP Senior Member
Thanks Meter: 143
 
More
How to test on Android device
In order to test from Android smartphone or tablet you need to use modified Bluetooth stack, which requires root privilege.

For regular users
Use PC method if possible.

Create backup before overwriting bluetooth library. Some patched libraries are attached to this post.
Unrestricted/unlimited versions negotiate Dual Channel mode and disable bitrate restriction (617-660 kbit/s will be used). Versions with 482 or 486 prefix negotiate 474-485 kbit/s.

For ROM developers (Android 5-7)
Patchset which increases maximum Bitpool value and adds Bluetooth Dual Channel option is available using the following link:
LineageOS 14.1 (Android 7.1.2)

The following information is outdated and is kept only for historical reasons:
Code:
These modifications are designed only for test and should not be applied to the main ROM repository!
If you're a ROM developer, please provide flashable modified bluetooth library if possible!
These modifications should be applied to stock Android bluetooth stacks Bluedroid (Android 5) and Fluoride (Android 6-7). Qualcomm-modified stack is not supported.
1. Replace Joint Stereo with Dual Channel in standard SBC configuration
android/platform/external/bluetooth/bluedroid/btif/co/bta_av_co.c:99
Code:
const tA2D_SBC_CIE btif_av_sbc_default_config =
{
    BTIF_AV_SBC_DEFAULT_SAMP_FREQ,   /* samp_freq */
    A2D_SBC_IE_CH_MD_JOINT,         /* ch_mode */
    A2D_SBC_IE_BLOCKS_16,           /* block_len */
    A2D_SBC_IE_SUBBAND_8,           /* num_subbands */
    A2D_SBC_IE_ALLOC_MD_L,          /* alloc_mthd */
    BTA_AV_CO_SBC_MAX_BITPOOL,      /* max_bitpool */
    A2D_SBC_IE_MIN_BITPOOL          /* min_bitpool */
};
Replace A2D_SBC_IE_CH_MD_JOINT with A2D_SBC_IE_CH_MD_DUAL. 2. Increase Dual Channel priority android/platform/external/bluetooth/bluedroid/btif/co/bta_av_co.c:411
Code:
    if (src_cap.ch_mode & A2D_SBC_IE_CH_MD_JOINT)
        pref_cap.ch_mode = A2D_SBC_IE_CH_MD_JOINT;
    else if (src_cap.ch_mode & A2D_SBC_IE_CH_MD_STEREO)
        pref_cap.ch_mode = A2D_SBC_IE_CH_MD_STEREO;
    else if (src_cap.ch_mode & A2D_SBC_IE_CH_MD_DUAL)
        pref_cap.ch_mode = A2D_SBC_IE_CH_MD_DUAL;
    else if (src_cap.ch_mode & A2D_SBC_IE_CH_MD_MONO)
        pref_cap.ch_mode = A2D_SBC_IE_CH_MD_MONO;
Move if with A2D_SBC_IE_CH_MD_DUAL to the top. 3. Disable or increase bitrate restriction Android bluetooth stack has not only bitpool limit, but also bitrate limit, 328 kbit/s. If the headphones support, for example, bitpool 53 for 48 kHz, Android will decrease the bitpool down to fit into 328 kbit/s limit. This will happen AFTER codec negotiation, on the encoding stage, do not take into account bitpool value in Bluetooth SetCapabilities packet. android/platform/external/bluetooth/bluedroid/btif/src/btif_media_task.c:172
Code:
#define DEFAULT_SBC_BITRATE 328
Replace with 512. 4. (for experiments only) Disable MTU limit. This is required for bitrates higher than ~580 kbit/s. btif/src/btif_media_task.c:174
Code:
/* 2DH5 payload size of 679 bytes - (4 bytes L2CAP Header + 12 bytes AVDTP Header) */
#define MAX_2MBPS_AVDTP_MTU         663

For ROM developers (Android 8-9)
Patchset which increases maximum Bitpool value and adds Bluetooth Dual Channel option is available using the following links:If you're a ROM developer, please provide flashable modified bluetooth library if possible!

The following information is outdated and is kept only for historical reasons:
1. Add Dual Channel support into A2DP SBC Source
/platform/system/bt/stack/a2dp/a2dp_sbc.cc:55
Code:
/* SBC SRC codec capabilities */
static const tA2DP_SBC_CIE a2dp_sbc_caps = {
    A2DP_SBC_IE_SAMP_FREQ_44,                           /* samp_freq */
    (A2DP_SBC_IE_CH_MD_MONO | A2DP_SBC_IE_CH_MD_JOINT), /* ch_mode */
    (A2DP_SBC_IE_BLOCKS_16 | A2DP_SBC_IE_BLOCKS_12 | A2DP_SBC_IE_BLOCKS_8 |
     A2DP_SBC_IE_BLOCKS_4),            /* block_len */
    A2DP_SBC_IE_SUBBAND_8,             /* num_subbands */
    A2DP_SBC_IE_ALLOC_MD_L,            /* alloc_method */
    A2DP_SBC_IE_MIN_BITPOOL,           /* min_bitpool */
    A2DP_SBC_MAX_BITPOOL,              /* max_bitpool */
    BTAV_A2DP_CODEC_BITS_PER_SAMPLE_16 /* bits_per_sample */
};
add A2DP_SBC_IE_CH_MD_DUAL in ch_mode.

2. Replace Joint Stereo with Dual Channel in default config
/platform/system/bt/stack/a2dp/a2dp_sbc.cc:82
Code:
/* Default SBC codec configuration */
const tA2DP_SBC_CIE a2dp_sbc_default_config = {
    A2DP_SBC_IE_SAMP_FREQ_44,          /* samp_freq */
    A2DP_SBC_IE_CH_MD_JOINT,           /* ch_mode */
    A2DP_SBC_IE_BLOCKS_16,             /* block_len */
    A2DP_SBC_IE_SUBBAND_8,             /* num_subbands */
    A2DP_SBC_IE_ALLOC_MD_L,            /* alloc_method */
    A2DP_SBC_IE_MIN_BITPOOL,           /* min_bitpool */
    A2DP_SBC_MAX_BITPOOL,              /* max_bitpool */
    BTAV_A2DP_CODEC_BITS_PER_SAMPLE_16 /* bits_per_sample */
};
Replace A2DP_SBC_IE_CH_MD_JOINT with A2DP_SBC_IE_CH_MD_DUAL.

3. Increase Dual Channel priority
/platform/system/bt/stack/a2dp/a2dp_sbc.cc:1155
Code:
static bool select_best_channel_mode(uint8_t ch_mode, tA2DP_SBC_CIE* p_result,
                                     btav_a2dp_codec_config_t* p_codec_config) {
  if (ch_mode & A2DP_SBC_IE_CH_MD_JOINT) {
    p_result->ch_mode = A2DP_SBC_IE_CH_MD_JOINT;
    p_codec_config->channel_mode = BTAV_A2DP_CODEC_CHANNEL_MODE_STEREO;
    return true;
  }
  if (ch_mode & A2DP_SBC_IE_CH_MD_STEREO) {
    p_result->ch_mode = A2DP_SBC_IE_CH_MD_STEREO;
    p_codec_config->channel_mode = BTAV_A2DP_CODEC_CHANNEL_MODE_STEREO;
    return true;
  }
  if (ch_mode & A2DP_SBC_IE_CH_MD_DUAL) {
    p_result->ch_mode = A2DP_SBC_IE_CH_MD_DUAL;
    p_codec_config->channel_mode = BTAV_A2DP_CODEC_CHANNEL_MODE_STEREO;
    return true;
  }
  if (ch_mode & A2DP_SBC_IE_CH_MD_MONO) {
    p_result->ch_mode = A2DP_SBC_IE_CH_MD_MONO;
    p_codec_config->channel_mode = BTAV_A2DP_CODEC_CHANNEL_MODE_MONO;
    return true;
  }
  return false;
}
Move if with A2DP_SBC_IE_CH_MD_DUAL to the top.


4. Increase bitrate limit
/platform/system/bt/stack/a2dp/a2dp_sbc_encoder.cc:42
Code:
#define A2DP_SBC_DEFAULT_BITRATE 328
Replace with 512.

5. (for experiments only) Disable MTU limit
This is required for bitrates higher than ~580 kbit/s.
/platform/system/bt/stack/a2dp/a2dp_sbc_encoder.cc:47
Code:
#define MAX_2MBPS_AVDTP_MTU 663
[/code]

For advanced users and ROM developers (Android 5-7 binary patch)
Please refer to this post in Russian (use Google Translate): https://4pda.ru/forum/index.php?s=&s...ost&p=76169677

How to capture Bluetooth data dump on Android
  1. Turn off Bluetooth;
  2. In Developer Settings, enable the "Enable Bluetooth HCI snoop log" switch;
  3. Turn on Bluetooth, connect to your headset using Bluetooth menu (this is important! Do not allow auto connection!);
  4. Play short audio sample;
  5. Open developer settings, disable the "Enable Bluetooth HCI snoop log" switch;
  6. There should be /storage/emulated/0/btsnoop_hci.log or /data/misc/bluetooth/logs/btsnoop_hci.log created. If it's missing, open /etc/bluetooth/bt_stack.conf with a text editor and see the path in BtSnoopFileName option.
  7. Upload btsnoop_hci.log to https://btcodecs.valdikss.org.ru/;
  8. Post in this topic your headphone model and test results.
There should be no cracklings, audio interruption or other sound distortion in the headphones. If you hear a good high-quality sound with the patched library, that means your headphones support audio with a bit rate of 512 kbps.
If you upload data to the server, please carefully follow the algorithm above. Especially, if you power off the headphones or disconnect after pairing, it's important to connect to the headphones manually from the bluetooth settings, do not allow auto connection!

Some of the files attached below have no MTU limit patched. Unlocked/unrestricted versions most probably will introduce cracklings.
Attached Files
File Type: zip LeEco Cool Changer S1 EUI_5.8.19S.zip - [Click for QR Code] (1.69 MB, 222 views)
File Type: zip Leeco LE2 (EUI 5.9.26s, Android 6).zip - [Click for QR Code] (1.64 MB, 158 views)
File Type: zip Xiaomi Mi Note (Miui 9 Miui.su usnkreal v8.4.12, Android 6.0.1).zip - [Click for QR Code] (1.63 MB, 108 views)
File Type: zip Xiaomi mi note 3 (MIUI 9, Android 7).zip - [Click for QR Code] (1.75 MB, 96 views)
File Type: zip Xiaomi Mi4c (Android 7.0 NRD90M, MIUI-9.5 9.5.1.0 (NXKCNFA)).zip - [Click for QR Code] (1.49 MB, 84 views)
File Type: zip Xiaomi MI5s (MIUI Global 9.6.1.0, Android 7).zip - [Click for QR Code] (1.49 MB, 100 views)
File Type: zip Xiaomi Redmi 3s (android 6.01, mmb29m, miui global 9.6.1.0).zip - [Click for QR Code] (1.65 MB, 74 views)
File Type: zip Xiaomi Redmi 4 (MiuiPro 10 8.8.2, Android 6.0.1, MMB29M).zip - [Click for QR Code] (1.66 MB, 98 views)
File Type: zip Xiaomi Redmi 4 Prime.zip - [Click for QR Code] (885.0 KB, 74 views)
File Type: zip Xiaomi Redmi 4 pro (MIUI 9, miuipro 8.4.26).zip - [Click for QR Code] (1.65 MB, 84 views)
File Type: zip Xiaomi Redmi Note 3 (Resurrection Remix Android 7.1.2_r36).zip - [Click for QR Code] (772.2 KB, 108 views)
File Type: zip Redmi Note 4x (Masik Premium, android 7.0).zip - [Click for QR Code] (1.49 MB, 238 views)
File Type: zip Asus Zoom (Android 5, 2.26.40.108_20160520).zip - [Click for QR Code] (2.84 MB, 106 views)
File Type: zip Le Max 2 Oreo Patched.zip - [Click for QR Code] (7.06 MB, 136 views)
File Type: zip Huawei P9 (Android 7).zip - [Click for QR Code] (2.23 MB, 144 views)
File Type: zip Samsung Galaxy S4 LTE GT-I9505 (Android 7.1.2; LineageOS 14.1-20180615-NIGHTLY-jfltexx).zip - [Click for QR Code] (2.24 MB, 306 views)
File Type: zip Huawei P9 lite (Resurrection Remix Nougat 7.1.2).zip - [Click for QR Code] (2.23 MB, 112 views)
File Type: zip Pixel 2 XL (Pie 9.0).zip - [Click for QR Code] (12.01 MB, 306 views)
File Type: zip Essential Phone (9.0 Pie).zip - [Click for QR Code] (12.00 MB, 202 views)
File Type: zip Redmi 3S (LineageOS 15.1 with 9.5.8.0 MALMIFD).zip - [Click for QR Code] (7.05 MB, 170 views)
The Following 17 Users Say Thank You to ValdikSS For This Useful Post: [ View ] Gift ValdikSS Ad-Free
22nd August 2018, 06:14 PM |#3  
OP Senior Member
Thanks Meter: 143
 
More
Tested devices
Devices which support at least 512 kbit/s SBCDevices which support SBC higher than 512 kbit/sDevices which don't work with higher bitrates or Dual Channel
  • Harper HB-202 (cracklings; Beken BK3256 chip)
  • Sony Ericsson MW600 (high frequency distortion, cracklings; device from 2009)
  • Sony SBH52 (too slow to handle packet rate)
  • BlitzWolf BW-F2 (no sound)
  • Overfly mini Bluetooth receiver (no sound)
The Following 11 Users Say Thank You to ValdikSS For This Useful Post: [ View ] Gift ValdikSS Ad-Free
22nd August 2018, 06:14 PM |#4  
OP Senior Member
Thanks Meter: 143
 
More
Why this is important: SBC 328k and 485k vs aptX
Contrary to popular belief of aptX sound quality, in some cases it can produce worse audio quality than SBC with a standard 328k bitrate.

SBC dynamically allocates quantization bits for frequency bands, acting on a "bottom-to-top" basis. If the whole bitrate was used for the lower and middle frequencies, the upper frequencies are "cut off" (silenced).
aptX quantizes frequency bands with the same number of bits constantly, which makes it a constant bitrate codec: 352 kbps for 44.1 kHz, 384 kbps for 48 kHz. It can't "transfer bits" to frequencies that are mostly needed in them. Unlike SBC, aptX will not "cut" frequencies, but will add quantization noise to them, reducing the dynamic range of audio, and sometimes introducing crackles. SBC, on the contrary, "eats the details" - discards the quietest areas.
On average, compared to SBC 328k, aptX makes less distortion in music with a wide frequency range, but on music with a narrow frequency range and a wide dynamic range SBC 328k sometimes wins.

Let us consider a special case, a piano recording. Here's a spectrogram:


The most energy lies in the 0-4 kHz frequencies, and lasts up to 10 kHz.
The spectrogram of the file aptX file looks like this:


Here is SBC 328k:


It can be seen that the SBC 328k periodically completely cut off the range above 16 kHz, and used all available bitrates for ranges below this value. However, aptX introduced more distortions into the frequency spectrum audible by the human ear, which can be seen on the subtracted original spectrogram from the aptX spectrogram (the brighter, the more distortion):


While the SBC 328k has introduced less distortion the signal in the range from 0 to 10 kHz, and the rest has been сut:


Bitrate 485k for SBC was enough to save the entire frequency range, without cutting off the bands.


SBC 485k on this audio sample is much better than aptX in the range of 0-15 kHz, and with a smaller but still noticeable difference - at 15-22 kHz (the darker, the less distortion):


Switching to a high-bitrate SBC, you will get a sound superior to aptX most of the time, on any headphones.
Attached Files
File Type: zip original_and_aptx.zip - [Click for QR Code] (11.29 MB, 610 views)
File Type: zip sbc.zip - [Click for QR Code] (11.17 MB, 734 views)
The Following 8 Users Say Thank You to ValdikSS For This Useful Post: [ View ] Gift ValdikSS Ad-Free
23rd August 2018, 10:48 AM |#5  
rohit3192's Avatar
Senior Member
Thanks Meter: 64
 
More
Bro. The concepts sound amazing.
I have Le Max 2 (Oreo). I have attached Bluetooth .so files.
If you patch I will try on Sony Bluetooth system and share with my friends patched files to see how much it works.
Thanks.
Attached Files
File Type: zip Backup.zip - [Click for QR Code] (2.41 MB, 188 views)
23rd August 2018, 10:58 AM |#6  
OP Senior Member
Thanks Meter: 143
 
More
Quote:
Originally Posted by rohit3192

Bro. The concepts sound amazing.
I have Le Max 2 (Oreo). I have attached Bluetooth .so files.
If you patch I will try on Sony Bluetooth system and share with my friends patched files to see how much it works.
Thanks.

For some reason I can't download your file, always get 404 not found. Another person with LeEco LeMax 2 (x820) contacted me and I made a patch, but only for 32-bit library. Since your archive is >2 MB, I suppose it contains 32 and 64 bit libraries. Please write your exact OS version and build number.
Would you mind to try? Backup your files first, replace 32-bit library with the file from the archive and rename 64-bit library, so it won't be used, and follow the instructions in the second post to capture the dump and upload it to btcodecs.
Attached Files
File Type: zip leeco_lemax2_32bit_patched.zip - [Click for QR Code] (3.36 MB, 116 views)
The Following User Says Thank You to ValdikSS For This Useful Post: [ View ] Gift ValdikSS Ad-Free
23rd August 2018, 11:51 AM |#7  
rohit3192's Avatar
Senior Member
Thanks Meter: 64
 
More
OK .
I try. Allow me some time.
Yes both libs were in one file. Now sending you separate libs.
Attached Files
File Type: zip lib.zip - [Click for QR Code] (1.14 MB, 154 views)
File Type: zip lib64.zip - [Click for QR Code] (1.27 MB, 180 views)
23rd August 2018, 11:52 AM |#8  
OP Senior Member
Thanks Meter: 143
 
More
Quote:
Originally Posted by rohit3192

OK .
I try. Allow me some time.
Yes both libs were in one file. Now sending you separate libs.

Try these.
Attached Files
File Type: zip Le Max 2 Oreo Patched.zip - [Click for QR Code] (7.06 MB, 156 views)
23rd August 2018, 12:06 PM |#9  
rohit3192's Avatar
Senior Member
Thanks Meter: 64
 
More
I have replaced file in /system/lib with permission.
And renamed /lib64 file as instructed.
Bluetooth switch doing nothing.
After renaming lib64 to original name the Bluetooth switch works and connects.
Build no attached.
Attached Thumbnails
Click image for larger version

Name:	Screenshot_Settings_20180823-163228.png
Views:	1828
Size:	208.4 KB
ID:	4578922   Click image for larger version

Name:	Screenshot_Settings_20180823-163233.png
Views:	1802
Size:	213.7 KB
ID:	4578924  
23rd August 2018, 12:11 PM |#10  
OP Senior Member
Thanks Meter: 143
 
More
Quote:
Originally Posted by rohit3192

I have replaced file in /system/lib with permission.
And renamed /lib64 file as instructed.
Bluetooth switch doing nothing.
After renaming lib64 to original name the Bluetooth switch works and connects.
Build no attached.

Please try the latest archive. It includes patched 64 bit libraries.
23rd August 2018, 12:28 PM |#11  
rohit3192's Avatar
Senior Member
Thanks Meter: 64
 
More
The new patched 64bit file worked.
Tried 486 one only.
Here is Bluetooth log. (Upload was too slow at given link so sending GD link)

Post edited: thanks @ValdikSS a lot.
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes