yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] felagund:
Makes sense. Usually people try to force AAC and not SBC.

Now I remembered I can also potentially check with my DIY rn52 based receiver in the car. Rn52 states SBC, AAC, aptx and I've used it without a problem. Actually I did have problems there but with OOS only when the volume control grouping was broken after one of the updates and I couldn't control the volume properly afterwards unless removing the grouping in Dev options.

But it looks device and settings specific to me so far.
[OnePlus 3 & 3T Cross Device Development] BruhToine:
Why would it only happen with Lineage OS if this is device specific ? I've test it today on the OnePlus 3 of my friend running OOS 9.0.6 and didn't have the issue.

Is it because of this code ? https://github.com/OnePlusOSS/andro...a8dfd51eaa3/device/include/interop_database.h

// Bose QuiteComfort 35, SoundSport and similar (because of older firmware)
{{{0x04, 0x52, 0xc7, 0, 0, 0}}, 3, INTEROP_2MBPS_LINK_ONLY}
[OnePlus 3 & 3T Cross Device Development] :
It's device specific with los.

Don't mix oos and oss. I.e. the code for camera is completely different from oos to oss. Have tried oss pie (build instructions: https://github.com/OnePlusOSS/android/blob/oneplus3/6.0.1/README.md)?

The code line you are mentioning is already in los sources:

https://github.com/LineageOS/androi...6.0/device/include/interop_database.h#L71-L72

EDIT: the longer I think of the comment (L71) and the 2Mbps limit, the more I think it's worth to try a build with L72 commented out - I'm no bt expert, but 2 Mbps may not be sufficient to serve SBC HD... Just guessing.
[OnePlus 3 & 3T Cross Device Development] BruhToine:
No I didn't build the rom. I was just looking to see if they put code specific to Bose QC 35 and found that.

I will try another rom this weekend to see if this is only happening in LOS.
[OnePlus 3 & 3T Cross Device Development] felagund:
MPOW bh129 works fine with SBC and hd audio:SBC settings.

The only difference I can see is hd audio switches Bluetooth audio channel mode from stereo to dual channel.
[OnePlus 3 & 3T Cross Device Development] :
It's needed - at least - for alipay fingerprint. If you don't use that, I think you can savely remove:

/system/app/SoterService/SoterService.apk
/system/vendor/bin/hw/vendor.qti.hardware.soter@1.0-service
/system/vendor/etc/init/vendor.qti.hardware.soter@1.0-service.rc
/system/vendor/lib64/hw/vendor.qti.hardware.soter@1.0-impl.so
/system/vendor/lib64/vendor.qti.hardware.soter@1.0.so
system/framework/org.ifaa.android.manager.jar
system/framework/boot-org.ifaa.android.manager.vdex
system/framework/arm/boot-org.ifaa.android.manager.art
system/framework/arm/boot-org.ifaa.android.manager.oat
system/framework/arm/boot-org.ifaa.android.manager.vdex
system/framework/arm/boot-org.ifaa.android.manager.art.rel
system/framework/arm64/boot-org.ifaa.android.manager.art
system/framework/arm64/boot-org.ifaa.android.manager.oat
system/framework/arm64/boot-org.ifaa.android.manager.vdex
system/framework/arm64/boot-org.ifaa.android.manager.art.rel
system/vendor/bin/hw/vendor.oneplus.hardware.ifaa@2.0-service
system/vendor/etc/init/vendor.oneplus.hardware.ifaa@2.0-service.rc
system/priv-app/IFAAService
system/priv-app/IFAAService/IFAAService.apk
system/lib64/vendor.oneplus.hardware.ifaa@2.0.so

If anything breaks by removing these, what you want to use, just dirty flash the rom again.

Not for flashing, but for reference (reading) this maybe interesting:

https://xdaforums.com/oneplus-6/one...ol-tomatot-debloater-basic-script-to-t3869427 especially: https://dl.xda-cdn.com/4/7/7/2/3/6/....txt?key=DJcrm6Sh25zhNyTbW2zl4g&ts=1580481743

Why don't you search the thtead before posting (See: https://xdaforums.com/announcement.php?a=81 #1)?

https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3866517/post81183465#post81183465 ff. (expected behaviour; can be changed by flashing Magisk)
[OnePlus 3 & 3T Cross Device Development] myrthain:
How did you solve your problem back then? Or did it just end in a wipe and fresh installation?
[OnePlus 3 & 3T Cross Device Development] myrthain:
My problem was a corrupted LOS16 system due to the automatic update process in combination with TWRP 3.3.1-1.

Exactly that helped me to have my system back without the need to wipe everything. Thank you! Now I got my lesson to manually flash all updates.
[OnePlus 3 & 3T Cross Device Development] knpk13:
It says 410 gone.
[OnePlus 3 & 3T Cross Device Development] :
The link still works for me. Try https://xdaforums.com/oneplus-6/one...ol-tomatot-debloater-basic-script-to-t3869427 and select the mentioned file ( List_of_systems_apps_SORTED___EXPLAINED_3.3.txt - fourth in the list of attached files).
[OnePlus 3 & 3T Cross Device Development] BruhToine:
Ok so tried different rom to test the problem and got different result :

1 - Lineage OS 17.1 : The problem is still there and when it happen, I got the error "this song is not available on mobile" with the soundclound application

2 - Havoc 3.1 : The problem is not there, but sometimes it takes longer for the song to play. I also got the toggle bug on this rom (Maybe launcher related)

3 - Pixel Experience (Gaurav24) : This rom as no problem at all with the bluetooth SBC with my Bose QC II

Not sure if lineage os include some CAF patch and this is causing the problem since the other roms are based on AOSP. Or this is some patch in lineage os that cause the bug ?
[OnePlus 3 & 3T Cross Device Development] :
Why don't you compare the sources? I recommend comparing 10 to 10 or 9 to 9. Comparing i.e. los-16 (this thread's rom) with pixel exporience ten will be a pain in the arse...

BTW: I've bought a new (used) car with intellilink R 4.0 (lg manufactured???). It's the first bt device, I've hands on, which is detected natively as sbc hd. I've tested (played around with... ;) ) extensively the last 5 days. I've learned

sbc hd works flawlessly for all kinds of media.

sbc hd (natively detected) is hearable better then aac.

sbc (w/o hd) is much, much, much worse then aac, if the device is detected as sbc hd.
[OnePlus 3 & 3T Cross Device Development] BruhToine:
Would compare the source between Lineage OS 17.1 and Pixel Experience but not sure where to look in the code. Which part should I look for bluetooth related stuff ?

Do you know if I could only download that part since the code base is huge and would take less time to compare.

Would love to enable SBC HD, but it is not available in the bluetooth settings of my bose headphone. Maybe because AAC HD have priority over SBC HD or because of the code with the 2mbps limit ?

P.S For me the SBC audio quality is better than AAC and with less audio latency on video and game.
[OnePlus 3 & 3T Cross Device Development] :
I would guess (since there was no error in the logs, it's hard to tell for sure which software package exactly is failing):

https://github.com/PixelExperience/system_bt

https://github.com/LineageOS/android_system_bt

To verify your findings you need to build it after patching, which requires a complete source tree.

For comparing you can use something like this:

mkdir bt
cd bt
git init
git remote add los https://github.com/LineageOS/android_system_bt.git
git fetch los lineage-17.1
git remote add pixel https://github.com/PixelExperience/system_bt.git
git fetch pixel ten
git checkout pixel/ten #optional at thiy point
git diff pixel/ten los/lineage-17.1
# if you've found something you think it's the cause, note the file name and the code snippet missing in los and checkout pixel/ten if you've skipped tjat earlier
git blame path/to/file/you've/noted #search for the code snippet and you see the commit it belongs to; note the commits hash
git show hash #just to check
git checkout los/lineage-17.1 #prepare for applying the commit in question to los
git cherry-pick hash #completely resolve all conflicts and commit this before continuing, maybe it cherry-picks without comflicts

Now it's time to build.

If it's working on pixel expirience the answer is no:

https://github.com/PixelExperience/system_bt/blob/ten/device/include/interop_database.h#L71-L72 (I've checked this first after your posting)

Honestly I'm not playing games often - and not at all, if the bt device is my car... *lol* Logically this makes sense to me: since aac (especially hd) has a higher bandwith then sbc (especially w/o hd), lower latency on sbc is not surprising.

General thought (I'm not paid by qcom!):

The best audio quality (never really looked for latency) I've heard is aptx and aptx hd. With my source devices (op3t, chagallwifi, bacon, surface pro 4) I've never expirienced any issues.

I really wonder why bose doesn't implement a high quality codec like aptx, aptx hd or ldac (theoretically even better then aptx hd - but I've never tested a device with ldac) within a highend device as qc35. I've always belived if any company out there knows how to optimize sound by hard- and software, it's bose...
[OnePlus 3 & 3T Cross Device Development] BruhToine:
Thanks for the step, I tried on those branch but no diff were found. Will try on each branch with Bluetooth or BT in it.

To be able to use SBC HD, I think the device has to support at least 3mbps. Found this in this review:

/* 3DH5 maximum bitrates */
if (a2dp_sbc_encoder_cb.peer_supports_3mbps &&
a2dp_sbc_encoder_cb.TxAaMtuSize >= MIN_3MBPS_AVDTP_SAFE_MTU) {
rate = A2DP_SBC_3DH5_DEFAULT_BITRATE;
if (a2dp_sbc_encoder_cb.sbc_encoder_params.s16SamplingFreq == SBC_sf48000)
rate = A2DP_SBC_3DH5_48KHZ_BITRATE;
}

/* 2DH5 alternative bitrates */
if (!a2dp_sbc_encoder_cb.peer_supports_3mbps &&
osi_property_get_int32(A2DP_SBC_HD_PROP, 0)) {
rate = A2DP_SBC_2DH5_ALT_BITRATE;
if (a2dp_sbc_encoder_cb.sbc_encoder_params.s16SamplingFreq == SBC_sf48000)
rate = A2DP_SBC_2DH5_ALT_48KHZ_BITRATE;
}

Honestly with with my bose, I see almost no difference when I plug it or use it with bluetooth on spotify since the highest bitrate of spotify is 320kbps. Normally SBC support up to 328kbps and AAC 256kbps.

The only reason for I could see to use APTX or LDAC is if you listen to loseless song with flac or service like Tidal. Anyway the future of bluetooth is with LE audio standard : https://www.androidcentral.com/what-you-need-know-about-bluetooth-le-audio
[OnePlus 3 & 3T Cross Device Development] :
If system/bt is the same, packages/apps/Bluetooth, frameworks/base (frameworks/base/packages/SettingsLib/src/com/android/settingslib/bluetooth) and hardware/interfaces/bluetooth came to my mind (from memory, most probably not complete!).
[OnePlus 3 & 3T Cross Device Development] BruhToine:
[MENTION=4405529]nvertigo67[/MENTION]

Not sure if this help, but I was able to reproduce the bug on

the Samsung S7 of my friend running LOS 16. So this is not

related to the phone.
[OnePlus 3 & 3T Cross Device Development] :
Exynos or Snapdragon model?
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
SM-G930F is the Exynos model
[OnePlus 3 & 3T Cross Device Development] :
Then we can drop the "caf-patches-conspiracy"-theory ( ;) SCNR).
[OnePlus 3 & 3T Cross Device Development] :
merging qcacld-2.0

[MENTION=5091734]dianlujitao[/MENTION] and [MENTION=9350973]All[/MENTION]:

How to merge https://source.codeaurora.org/quic/...n/qcacld-2.0/tag/?h=LA.UM.7.6.r1-06700-89xx.0 in our los kernel sources without initializing a git in drivers/staging/qcacld-2.0/? Though I'm completely brain locked after searching for and thinking of a solution, initializing a git in drivers/staging/qcacld-2.0 doesn't "feel" right....
[OnePlus 3 & 3T Cross Device Development] :
This "feels" much better:

git subtree pull --prefix drivers/staging/qcacld-2.0/ https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0 LA.UM.7.6.r1-06700-89xx.0
[OnePlus 3 & 3T Cross Device Development] ppajdek:
Initial merge:

git remote add qcacld-2.0 https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0
git fetch qcacld-2.0 <TAG>
git merge -s ours --no-commit --allow-unrelated-histories FETCH_HEAD
git read-tree --prefix=drivers/staging/qcacld-2.0 -u FETCH_HEAD
git commit

Updating to a newer tag:

git fetch qcacld-2.0 <TAG>
git merge -X subtree=drivers/staging/qcacld-2.0 FETCH_HEAD
[OnePlus 3 & 3T Cross Device Development] :
Sadly, this bails out at

git read-tree --prefix=drivers/staging/qcacld-2.0 -u FETCH_HEAD
error: Entry 'drivers/staging/qcacld-2.0/CORE/CLD_TXRX/HTT/htt.c' overlaps with 'drivers/staging/qcacld-2.0/CORE/CLD_TXRX/HTT/htt.c'. Cannot bind.

Does this require an empty drivers/staging/qcacld-2.0?

git subtree pull --prefix drivers/staging/qcacld-2.0/ https://source.codeaurora.org/quic/la/platform/vendor/qcom-opensource/wlan/qcacld-2.0 LA.UM.7.6.r1-06700-89xx.0

works flawlessly with all previous commits in our tree.
[OnePlus 3 & 3T Cross Device Development] ppajdek:
drivers/staging without qcacld-2.0 dir, it will be created at initial merge
[OnePlus 3 & 3T Cross Device Development] :
I want to merge the current caf commits to the existing qcalcd-2.0, because it's already caf based and has quite some commits to make it los. Idon't want to throw that away and just replace the current los status with tje curtent caf status. The subtree command does exactly that merge.

Anyway, thank you very much, sooner or later it's needed! I'm always surprised what I don't know about git.
[OnePlus 3 & 3T Cross Device Development] 64ashg:
Slight ot but [MENTION=4405529]nvertigo67[/MENTION] whenever and whichever phone you decide to upgrade, please give a heads up, i for one will definitely be biased to it.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=5091734]dianlujitao[/MENTION]:

Since I've got no answer at all, I guess it's not useable at all:

If it's not usable at all:

Is this by desgin and purpose? If so, why not remove the useless code from snap?

If it's not intended to be useless, van it be fixed?
[OnePlus 3 & 3T Cross Device Development] pijas82:
I'm back to lineage 16, because du drop support on 3t.

I find a small bug, can't change notification sound in WhatsApp, works in all ROMs I've used
[OnePlus 3 & 3T Cross Device Development] :
This is one year old and outdated information. The reddit posting is completely misleading because of the term "latest" instead of giving versions. The encryption footer bug is not present anymore. This is an good example why all postings refering to "latest" instead of "version" are completely useless and misleading after the next version of something is released - as you was mislead in this case. Don't spread this false information, please.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
and if NFC doesn'T work after this upgrade:

delete /data/nfc/nfaStorage.bin1 and reboot device
[OnePlus 3 & 3T Cross Device Development] spandy992:
Thank you dev for supporting this device.
[OnePlus 3 & 3T Cross Device Development] TomConVerd:
I get your point, and yes, I did not feel right to refer to a outdated software version. One should always try to use the latest version of TWRP before getting an old and patched version. However, the latest version twrp-3.3.1 didn't work for me (hope I did everything correct), the encryption would not happen (it just stops with a short message that it failed). That's why I posted it because it took some time to find a solution for that problem.
[OnePlus 3 & 3T Cross Device Development] :
Hard to say. I've tested 3.3.1-0 (which works). The latest version is 3.3.1-1. There is no official 3.3.1 version (or it's ambigous - at least). Maybe a regression from 3.3.1-0 to 3.3.1-1. But much more probable, you've missed to read the official thread: since 3.3.0-0 it's possible to format the md container without touching the encryption footer in addition to recreate an empty encryption footer. The first one will not work for your guide. The "Format Data"-Button located at TWRP-Main-Page->Wipe recreares an empty encryption footer (as stated: tested on 3.3.1-0; no regression reports for 3.3.1-1).
[OnePlus 3 & 3T Cross Device Development] multiwirth:
Anyone here experiencing issues with fingerprint not waking and unlocking the phone (no reaction at all) ?

I'm not sure if it's an bug of current nightlies or if my lineage installation messed up during updated or faulty hardware...
[OnePlus 3 & 3T Cross Device Development] :
No problems with fingerprint and latest LineageOS and fw 9.0.6.
[OnePlus 3 & 3T Cross Device Development] punio4:
Happening to me all the time. I often need to use the power button to unlock when the fingerprint reader becomes unresponsive
[OnePlus 3 & 3T Cross Device Development] felagund:
At times it seems unresponsive but I realised it's in cases when the phone prompts me for pin/pattern actually. When it's unresponsive and I wake it with the power button there is a message for this.

It works fine in my opinion.

I was experiencing random freezes with screen off with a white led turning on but updated to latest nightly today and will see if it happens again. Might be specific to my setup and once happened on screen on when I hit the power button until the advanced reboot menu popped up. Might be related to my usage and settings.

Edit: can anyone recommend a good way to preserve the logs on this LOS version past a reboot? I searched but couldn't find a suitable solution and it seems /proc/last_kmsg has been deprecated for some time.

I'm experiencing lots of freezes on black screen in the last few days (4-5 times today and it's only the first half of the day) and I suspect it might be a hardware issue or app related problem and not necessarily lineageos or kernel related one. I'll do a fresh reinstall but would prefer to capture some logs for comparison first.

Edit 2 and today is fine and no freezes or crashes
[OnePlus 3 & 3T Cross Device Development] punio4:
I keep getting daily "bug report captured" notifications. Any way to make sense of them?
[OnePlus 3 & 3T Cross Device Development] :
Not with this amount of information... I'd guess the answeres you are looking for are in the bugreport.
[OnePlus 3 & 3T Cross Device Development] punio4:
Would it be ok for me to upload them somewhere and have someone else take a look at them?
[OnePlus 3 & 3T Cross Device Development] thesplitter:
I get them too sometimes, happens when I long press a button, not exactly sure which one. there must be some kind of shortcut to start wrapping a bug report
[OnePlus 3 & 3T Cross Device Development] digitaldai:
Hello

just looking to be pointed in the direction of updating firmware to work with latest nightly lineage 16.

I am still running a lineage 16 version from jan2019. I want to update to latest nightly but it fails when i do, likely I have an old firmware version.

would be appreciated, I just can't see it, probably buried here somewhere, was just some time ago.

still using this phone daily some 2 1/2 3 years....

many thanks

Dai
[OnePlus 3 & 3T Cross Device Development] :
Don't blindly flash! Read and make an educated decission: https://xdaforums.com/oneplus-3t/how-to/guide-cope-9-0-3-5-0-8-firmware-barrier-t3941164
[OnePlus 3 & 3T Cross Device Development] felagund:
Also setting that is often left out of guides - safety net will it pass on latest versions even with magisk hide as the security patch is more recent/up to date compared to what is registered on Google side for the device (I oversimplify but I forgot the details) do you will also need a change on security date setting on build prop to pass it. I think Dirk had updated a nice package for this.

On a separate point for my earlier problems with freezes - definitely hardware related as it is very consistent when I press one of the lower corners of the phone between my fingers
[OnePlus 3 & 3T Cross Device Development] :
For reading - not for blindly flashing: https://xdaforums.com/oneplus-3/one...-nlos-16-0-t3879405/post78433987#post78433987
[OnePlus 3 & 3T Cross Device Development] felagund:
My bad it was your scripts.
[OnePlus 3 & 3T Cross Device Development] :
No. [MENTION=5092836]Dirk H[/MENTION]as done a Magisk Script. Two different scripts/approaches. In deed there are three different approaches:

Changing the security patch date (https://xdaforums.com/oneplus-3/one...-nlos-16-0-t3879405/post78433987#post78433987 )

Changing the the build fingerprint AND the date (Magisk module)

Changing only the build fingerprint to an old oos 5.x (Magisk script)

I linked my posting because of the background information.
[OnePlus 3 & 3T Cross Device Development] Andrew1999:
hey everyone, i apologize for the question i realize its probably been asked before multiple times but i saw many conflicting posts regarding this

im currently running oos 9.0.5 rooted with magisk and twrp recovery. what are the steps I have to go through to install this rom

as far as i know from my older devices:

wipe system data cache dalvik cache

install rom gapps and magisk

reboot

are there any extra steps i have to go through like decryption or extra firmwares or such?

also from what i've read in the recent posts hotspot is broken in the latest builds so please let me know what is the latest build with functioning hotspot.

sorry for the many questions and long post

thank you
[OnePlus 3 & 3T Cross Device Development] :
You are posting in the wrong thread. If you check the last pages and/or use the thread search, you'll see this rom dpes not suffer from broken hotspot.
[OnePlus 3 & 3T Cross Device Development] Andrew1999:
I apologise. I guess my information has gotten mixed up from all the threads I've viewed in the past few days.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
The steps are correct, you can perform an installation from OOS 9.x without any patched firmware etc.

But watch your TWRP version, use the newest one from https://dl.twrp.me/oneplus3/
[OnePlus 3 & 3T Cross Device Development] Andrew1999:
alright thanks alot.

quick question any particular gapps you recommend?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
OpenGapps Pico is my preference.
[OnePlus 3 & 3T Cross Device Development] Andrew1999:
Does always on display have burn in protection implemented?
[OnePlus 3 & 3T Cross Device Development] :
Yes: https://github.com/LineageOS/androi...base/core/res/res/values/config.xml#L398-L399
[OnePlus 3 & 3T Cross Device Development] prateektaneja:
Some of the previous posts suggest the possibility of being able to lock the bootloader on this ROM? Is this true? And if possible, can this be done irrespective of ROMs?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Yes, you can lock the bootloader on this rom.

This is also true for the official TWRP.

A rom has to have the boot image signed with the keys used by OnePlus and then it'll work on a locked bootloader.

But don't ask me how to do that - I don't know.
[OnePlus 3 & 3T Cross Device Development] Xydia:
Hi Team,

I want to dirty flash the latest LOS 16 ROM. My proposed plan:

- blu_spark TWRP 3.2.3-1 -> TWRP 3.3.1-1

- LOS 16.0-20190928 -> LOS 16.0-2020

- SuperSU 2.82 -> ?

- Firmware? -> OxygenOS 9.03?

Questions:

- Is SuperSU considered a mod? If so, how else can I gain root? I don't want to get ignored :angel:.

- From TWRP: `dm-verity must be disabled in fstab`. Does this ROM disable dm-verity?

- What does this ROM use, EXT4 or F2FS?

- Where is OxygenOS 9.0.3 Firmware?

- What is the order of flashing? TWRP Bootloader < OxygenOS Firmware, LOS ROM, SuperSU?

Thanks!
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Su:I wouldn't use SuperSU (it's not been supported for a long time). I'd use the latest (stable) Magisk 20.3.

Dm-verity: not an issue

Format: You can use either ext4 or f2fs for the data partition. Your choice.

Firmware: the latest is 9.0.6, so use that. If you're coming from 5.0.8 I suggest you read https://xdaforums.com/oneplus-3t/ho...-5-0-8-firmware-barrier-t3941164/post79758055

Flashing: flash updated TWRP, firmware, rom, Magisk
[OnePlus 3 & 3T Cross Device Development] prateektaneja:
Thank you for the response. I flashed the official TWRP, am running this ROM and just tries fastboot oem lock. On choosing to lock the bootloader from the phone using the volume keys, the phone reboots without unlocking the bootloader. Any help on what might I be missing out on?

Edit: Got it! Turns out you have to chose to NOT lock your bootloader in order to lock it.