yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] :
Sadly, the app creates a crash log saying nothing (the lines ending on "(Unknown Source:line number)")

01-11 16:42:08.920 31171 31171 E AndroidRuntime: FATAL EXCEPTION: main
01-11 16:42:08.920 31171 31171 E AndroidRuntime: Process: com.starfinanz.mobile.android.dkbpushtan, PID: 31171
01-11 16:42:08.920 31171 31171 E AndroidRuntime: jvduvnfw.wsbIBKIm: 00
01-11 16:42:08.920 31171 31171 E AndroidRuntime: at jvduvnfw.yyO1WyGO.RCXibBHY(Unknown Source:62)
01-11 16:42:08.920 31171 31171 E AndroidRuntime: at jvduvnfw.yyO1WyGO.cevoTAhS(Unknown Source:0)
01-11 16:42:08.920 31171 31171 E AndroidRuntime: at java.lang.Runtime.nativeLoad(Native Method)
01-11 16:42:08.920 31171 31171 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:1014)
01-11 16:42:08.920 31171 31171 E AndroidRuntime: at java.lang.System.loadLibrary(System.java:1669)
01-11 16:42:08.920 31171 31171 E AndroidRuntime: at jvduvnfw.jfLU2dDs.zZCjkfbS(Unknown Source:43)
01-11 16:42:08.920 31171 31171 E AndroidRuntime: at jvduvnfw.ItgtGofS.ez0AMo8A(Unknown Source:13)
01-11 16:42:08.920 31171 31171 E AndroidRuntime: at jvduvnfw.ItgtGofS.AZkPsqDr(Unknown Source:24)
01-11 16:42:08.920 31171 31171 E AndroidRuntime: at jvduvnfw.ItgtGofS.tG06FdZl(Unknown Source:6)
01-11 16:42:08.920 31171 31171 E AndroidRuntime: at ald.<clinit>(Unknown Source:0)
01-11 16:42:08.920 31171 31171 E AndroidRuntime: at java.lang.Class.newInstance(Native Method)
01-11 16:42:08.920 31171 31171 E AndroidRuntime: at android.app.AppComponentFactory.instantiateApplication(AppComponentFactory.java:50)
01-11 16:42:08.920 31171 31171 E AndroidRuntime: at android.app.Instrumentation.newApplication(Instrumentation.java:1120)
01-11 16:42:08.920 31171 31171 E AndroidRuntime: at android.app.LoadedApk.makeApplication(LoadedApk.java:1061)
01-11 16:42:08.920 31171 31171 E AndroidRuntime: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5891)
01-11 16:42:08.920 31171 31171 E AndroidRuntime: at android.app.ActivityThread.access$1100(ActivityThread.java:200)
01-11 16:42:08.920 31171 31171 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1656)
01-11 16:42:08.920 31171 31171 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
01-11 16:42:08.920 31171 31171 E AndroidRuntime: at android.os.Looper.loop(Looper.java:193)
01-11 16:42:08.920 31171 31171 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6718)
01-11 16:42:08.920 31171 31171 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
01-11 16:42:08.920 31171 31171 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
01-11 16:42:08.920 31171 31171 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)

Perhaps it's a follow-up error from package parsing, sepolicy or something else, which isn't contained in the log snippet. Since your bl is locked you can try without magisk - but that's guessing.
[OnePlus 3 & 3T Cross Device Development] thesplitter:
Had the same issue on my TAN app, double check that magisk hide hides root for it
[OnePlus 3 & 3T Cross Device Development] :
It does. See the log snippet [MENTION=4853899]Aservatenkammer[/MENTION] has posted:

01-11 16:42:08.527 485 502 I Magisk : proc_monitor: [com.starfinanz.mobile.android.dkbpushtan] PID=[31171] UID=[10195]

As allready stated: I can't see in the log-snippet if it's root at all, whats causing the crash - but since [MENTION=4853899]Aservatenkammer[/MENTION] has the bl of his device locked, it doesn't hurt to check w/o magisk. With bl locked and sec patch date adjusted, safetynet api is passing w/o magisk. If the com.starfinanz.mobile.android.dkbpushtan app is working w/o magisk - like on [MENTION=4853899]Aservatenkammer[/MENTION] nexus 7 - we would know it's magisk; if it's not working w/o magisk ot's some difference from cm/los-14 to los-16.
[OnePlus 3 & 3T Cross Device Development] Aservatenkammer:
I only installed magisk because the dkb tan app didnt started with pure LinageOS..

root isnt enabled.
[OnePlus 3 & 3T Cross Device Development] thesplitter:
Does it start even when you clear the app data? Does the app have biometric protection enabled? If yes remove and add back again all fingerprints
[OnePlus 3 & 3T Cross Device Development] Aservatenkammer:
Nope, even when i deinstall and install it again.

The App cant even request the permissions, it instantly crashes.

So there are no permissions set.
[OnePlus 3 & 3T Cross Device Development] thesplitter:
Just tested on my device, it works perfectly, obviously it's your configuration.

Try removing the fingerprints from settings and add them back again, or perform a clean flash, that will surely solve it, remember to install magisk and add the banking app to hide before running it.
[OnePlus 3 & 3T Cross Device Development] pk_trixx:
Anyone been able to enable automatic call recording on the Dial app?

I come from Havoc ROM and that had an option on the default dialer app to enable call recording for all calls. While recording does work on LOS 16 as well, no option to record all calls automatically.

There is another [HOW TO] thread that explains how to hack the dialer app, but I did not find my provider's (Airtel-India) MCC inside the Dialer/res/ folder (after decompiling the Dial.apk).

Anyone know how to make it work?
[OnePlus 3 & 3T Cross Device Development] :
No way. Because you can't enable something, that's not compiled in:

https://review.lineageos.org/c/LineageOS/android_packages_apps_Dialer/+/251235

Workaround: use a los-16 based rom, which uses this commit.
[OnePlus 3 & 3T Cross Device Development] pk_trixx:
Any way to compile the dialer alone?
[OnePlus 3 & 3T Cross Device Development] :
Yes. But you need the full sources, so you can build the complete rom anyway. After setting up the build environment and initially syncing the sources (https://wiki.lineageos.org/devices/oneplus3/build ), from the root of the source tree:

. build/envsetup
breakfast oneplus3
repo sync #to fetch the newly added oneplus3 repos - paranoid, but doesn't hurt
repopick 251235 # apply the auto-record commit
mma -j [number: cpu cores + 1] Dialer 2>&1 |tee build.log

You'll find the Dialer.apk in

[BUILD_ROOT]/out/target/product/oneplus3/system/priv-app/Dialer/Dialer.apk

Check permissions and selinux context when replacing Dialer.apk.

Considering your question, you are better off with using a los-16 based rom with https://review.lineageos.org/c/LineageOS/android_packages_apps_Dialer/+/251235 applied, or pulling the Dialer.apk from such rom.
[OnePlus 3 & 3T Cross Device Development] pk_trixx:
I tried getting that from Havoc ROM, but they store everything in a single blob "system.new.dat.br" file. How do you extract it from there?
[OnePlus 3 & 3T Cross Device Development] :
Do you ever use a search engine before posting?

If you google for "unpack system.new.dat.br xda" the first hit is https://xdaforums.com/android/help/tut-how-to-convert-dat-br-to-dat-t3723926 Read the first two postings including their links.
[OnePlus 3 & 3T Cross Device Development] BruhToine:
I've installed LOS 16 (OpenGApps Nano/Without magisk) yestarday on my OnePlus 3T and everything is super smooth compared to OxygenOS and I get arround 6h SOT on my phone with this rom. But now I have some problems when playing sound from Spotify and Youtube on my Bose QC 35 IIs with bluetooth SBC. The first time I paired the devices everything was working and had no problem with the audio, but the second time I tried there was no sound playing on my headphones. The only thing I could get audio from was the phone call. I tried with both SBC and HD Audio AAC. The only way I found to get sound again was to forget the pairing on both devices and connecting to it again which is not permanent solution. Sometimes I could get sound by re-pairing multiple time with the QC 35 IIs. Is this something the devellopers of LOS are aware of ? If you have a solution for this please let me know.
[OnePlus 3 & 3T Cross Device Development] :
No, but to find a solution you can help:

Would you get a log (from pairing successfully and playing music succesfully to reconnecting and failed music; increase log buffer to 4 Mio - at least - before starting to pair), please? After that, do the same wit a build prior to 20200104, please.
[OnePlus 3 & 3T Cross Device Development] generalprobe:
[MENTION=4405529]nvertigo67[/MENTION]

You helped me quite a lot in the past and I am really grateful of that. Now I have another issue with my OnePlus3.

Till July/August I got four days of standby time out of my phone. In August, when I wanted to update to the latest security string, I deleted data instead of system, so I had to set up my phone from scratch. From that day I only got roughly two maybe 2.5 days out of my battery. "Betterbatterystats" shows me nothing of value from partial wakelocks. My Phone is in deep sleep only 88-91% of the time with 2% screen on and the rest "awake / screen off".

Do you have some advise for me, to debug this?

I still use the same launcher as I did before. (nova) I am really out of ideas here ...
[OnePlus 3 & 3T Cross Device Development] :
What do this numbers mean? Screen off drain? Overall? Which period?

Tricky, especially if you don't have detailed numbers from before...

As a first step, I'd check the usual suspects: fw up to date? Misbehaving apps? Strange settings? To exclude them update fw to 9.0.6 or modded 9.0.6 fw, if you javn't done so yet), clean flash with only gapps (nano/pico), magisk and bbs. No restores. Set up bbs (enable watchdog and wd on unlock). Check screen off drain and screen on drain by manually checking both (hard to tell, if you have no such data from your previous setup). If you know if it's screen off drain or screen on drain, start setting custom refs in bbs to narrow it down.

Also consider batt wear. Older batts doesn't get better. The degredation does not always happen linear.

Keep in mind, that it can be a combination of many factors...

Good luck!
[OnePlus 3 & 3T Cross Device Development] BruhToine:
Sorry for the late response...

Here's the log with the audio not working the first time and working the second time on my Bose using Spotify. This is done on lineage 20200119.

I don't know how to downgrade lineageos to do the same on build 20200104. Will I lose my data if I do it ?

I've also notice that sometimes the Bluetooth toggle is not enable in the quick setting when the Bluetooth is on. Not sure if this is related.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
I've visited friends some days ago.

They had a hidden WiFi network (no SSID broadcast).

I thought "no problem, add a new network, type in ssid, psk2 passphrase, go to advanced and tick 'hidden network'".

But it didn't work. The phone just didn't found the network.

Tried it several times. Wasn't a typo - and all other phones (apple, samsung) + my windows laptop also connected to it.

After switching to visible SSID, I could also connect to it.

Anybody else noticed this?

As I never use this feature, I cannot say if it worked before.

I'm on 20200118 with fw 9.0.6 (also tried 9.0.4 and 20200113)
[OnePlus 3 & 3T Cross Device Development] :
I'm confused. In your original posting you've said that it's working for the first time but can't connect on the second time....

The log is also missing the boot part and system initialization. Did you pump up the log buffers to 4 Mio?

Without mods it's just flash 20200103 (I've said PRIOR to 20200104!!!) and wipe dalvik and caches.

That's really strange. Since pie the bt notification icon is only displayed if a device is actually connected, but the QS tile is always on if bt is on, and always off if bt is off.

Do you use any mods? (Each and everything altering boot and/or system)
[OnePlus 3 & 3T Cross Device Development] BruhToine:
My bad if I didn't explain myself correctly, english is not my first language. But yeah, it is always working on the first pairing of the devices, but after that, the Bluetooth works randomly... Sometimes there is sounds, and other time there is none.

Yeah, I have set the log buffers to 4 Mio, but I cleared the logs before doing the Bluetooth problem because I didn't think you need the part before. If you want I can do it again, but leave the boot part.

I cannot find build 20200103 for the OnePlus 3/3T, it is not on the lineage website and didn't find it on androidfilehost.

I was on OOS 9.06 and only flash the rom and gapps nano. No Magisk, no root and no mods on my phone. I will try to provide the log and a screenshot if it happen again.
[OnePlus 3 & 3T Cross Device Development] :
I see. I want this test, because this commit https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/266291 is - according to it's commit message - tested on mSBC devices, but not on SBC devices...

You can also try deleting audiofx from twrp, but my gut feeling suspects the above commit.

[MENTION=9350973]All[/MENTION]: Can anybody provide a link for a los-16.0 build equal or prior to 20200103, please?

Sadly, I can't check myself. I've hamds on two aptx devices, but neither SBC nor mSBC. :(

(If no old build is available, and you are willing to clean flash, you'll find a nlos-16.0 build at https://drive.google.com/drive/folders/1bV5ViyIhh-AwZcjWQDTfHOy2zBSqNVRK)
[OnePlus 3 & 3T Cross Device Development] BruhToine:
Ok I will try to delete audiofx and will let you know what happen.

Are the logs that I gave you sufficient or you also want the boot part ?
[OnePlus 3 & 3T Cross Device Development] anyone23:
Here is LOS16 20191224: https://we.tl/t-0k2k3Dn7Td
[OnePlus 3 & 3T Cross Device Development] :
Only if the mSBC commit can be excluded.

Another idea: if it's not working, what's in dev-opts->Bluetooth audi codec? Does switching (i.e. from SBC to LDAC, or to System default and back) the codec makes any difference?

[MENTION=9350973]All[/MENTION]: anyone else here around with a SBC (not mSBC) bt device?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
How can one tell whether a device is SBC or mSBC?
[OnePlus 3 & 3T Cross Device Development] :
If it's not in the tech specs of the devicr, I have no clue at all. Honestly: until I've read the message of the commit, I havn't known there is something called mSBC...
[OnePlus 3 & 3T Cross Device Development] BruhToine:
Here's the log from the build 20191224 given by [MENTION=6151062]anyone23[/MENTION] ... Thanks again

I still had the same problem on this version. It is reproduce around 15h32-33 in the log.

I have attached a screenshot of the bluetooth options in the developer settings.

I tried your suggestion to remove audiofx, but it didn't fix the problem.

I was also able to reproduce the bluetooth toggle bug. I think it is just a problem with the UI refresh. I have take 2 screenshot. In the first one the toggle is not enable but in the second one it is (Maximize quick setting). I have include the log in the logs.zip

Thanks for your help [MENTION=4405529]nvertigo67[/MENTION]
[OnePlus 3 & 3T Cross Device Development] :
I'm clueless here, because tnere are no log entries for this time stamp:

01-22 15:32:32.512 2419 2419 D StatusBar: disable<e i a s b h r c s > disable2<q i n >
01-22 15:32:35.956 975 975 V SettingsProvider: Notifying for 0: content://settings/system/screen_brightness

In deed there are no log entries for three seconds - it seems the bad happens exactly, when the log is silent.

On the otter hand: this explains why we can't see any bt errors in the logs.

Have you tried switching tne codecs as suggested in my last posting?

My last ideas are

clearing the complete device list in the QC35 II headphones (or factory resetting) and clean flashing los

updating the QC35's firmware

using the bose connect app

asking the bose support

This is strange. I've never expirienced that, nor I've read about it.

...an other hint it's time for a clean flash.
[OnePlus 3 & 3T Cross Device Development] felagund:
I'm using Bose qc35 ii daily.

Works with little to no problems (sometimes there is latency that is fixed when I reconnect the headset and force close the app (netflix / hbo go, etc. )

I do experience no audio on Spotify occasionally but it's due to Spotify losing network and gets fixed after some toggles ,.force close, reboot, etc. And in the same time other apps work ok on the headset.

I'm on 13th Jan build and with latest firmware, micro gapps and magisk as well as the fix for the update date for safety net.

If I can help with anything just give me a shout.
[OnePlus 3 & 3T Cross Device Development] MarkMRL:
Thank you, it seems to have worked. Anyway, I assume that it will go back to not being able to play as soon as I do a system update, right? Shouldn't this be added to the official builds? Seems like an easy enough fix, but then again I don't know anything about this kind of stuff, I'm just a tinkerer.
[OnePlus 3 & 3T Cross Device Development] :
It's not wanted, I tried to discuss this in the 15.1 thread, but nobody confirmed the issue:

https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/229392

If you like, cherry pick it to 16.0, but don't expect me to restart something nobody but you, the original bug-bash author (got commentless deleted when issies moved to gitlab) and me wants. Needless to say that my builds doesn't suffer from this issue since three years... ;)
[OnePlus 3 & 3T Cross Device Development] BruhToine:
It's weird, there is no log at all about the Bluetooth connection or media sent to the Bose ?

Yeah it just reverted back to SBC automatically and did nothing.

- I already test to clear the devices list and clear the bluetooth cache, but it did not help.

- I already have the latest QC35's firmware

I just wipe my phone completely a couple day ago before installing Lineage OS, I don't think this is the problem.

Could it be this patch the cause the no audio ? https://lineageos.org/engineering/Bluetooth-SBC-XQ/

I didn't have this issue at all on OOS 9.0.6

---------- Post added at 06:58 PM ---------- Previous post was at 06:49 PM ----------

When you have no audio on spotify, did you check if the sound was still send on other apps like youtube ?

For me, when I have the problem, only the phone call work.

To reproduce my problem try this multiple times :

- Close the bluetooth on your phone and close the bose headset

- Turn on the Bose and wait about 5 sec (You will hear some voices that it tries to connect )

- Turn on the bluetooth on your phone

- Check if there is sound on spotify or youtube

Let me know if your able to reproduce my problem.

Thanks
[OnePlus 3 & 3T Cross Device Development] :
Did you ever look yourself in the logs? Did you reed my responses? Of course I can sse logs from bt and connecting the QC35 (how should I know the bt device). But there is no error as stated in the part of my answer you've quoted...

Since it's working for [MENTION=2725640]felagund[/MENTION] but not for you, it's most probably setup related.

This is not a patch but an article. Since the related commits (https://review.lineageos.org/q/topic:%22bt-sbc-hd-dualchannel-pie%22) date back to mid of May and most devices not using aptx or other high end codecs working fine it's highly unprobable that these are responsible for the issues you are expiriencing.

If it's not your setup (which is most probable IMHo), it's the qc35 itself. Either it's configuration (a factory reset of the qc35 may help) or a hardware issue.
[OnePlus 3 & 3T Cross Device Development] felagund:
Couldn't replicate the bug.

Works fine and I haven't touched any developer settings.

A few months ago I had the fx audio bug but now it's all ok.

In the rare cases when Spotify doesn't work usually force closing fixes it and at the same time other apps work.

I'm on default settings.
[OnePlus 3 & 3T Cross Device Development] PiereMallao:
i have a op3 with oxygenos 9.0.6 installed with the latest twrp 3.3.1-1. I could flash the magisk.zip and root works fine with oxygenos.

After that i tried to installed lineageos. i booted into twrp, wiped data (Wipe -> Swipe to Factory Reset) and then i flashed the zip. After reboot i see the lineageos logo for some minutes and then the devices starts twrp again. i also tried wiping twice - before flashing and after that. the same behaviour.

whats wrong here? do i need to re-install a stock rom first before flashing lineageos again?

edit

solved: problem was the twrp manager.
[OnePlus 3 & 3T Cross Device Development] BruhToine:
I see on your screenshot that you are using AAC which is not recommended on Android (Lower quality than SBC and use more battery). See this link : https://www.soundguys.com/the-ultimate-guide-to-bluetooth-headphones-aac-20296/

Anyway, I tried to enable AAC to try if the problem is codec related and it seems this is the case. I wasn't able to reproduce my problem with AAC.

Since I did not have that problem with SBC on OOS 9.0.6, I'm pretty sure this is something to do with the SBC implementation on Lineage OS.

I will need to try on another rom to comfirm this. Do you guys have any recommendation for a rom closest to AOSP or CAF ?
[OnePlus 3 & 3T Cross Device Development] felagund:
I'm glad I could help then with the screenshot. The aim there was to show the default settings - I specifically enabled dev settings to capture it.

I was with the impression the codec would change depending on the device and that's why I took the capture with the Bose connected. Doesn't it do so? Still the quality of the headset is very good and without altering any settings I was able to find the lossless amongst a mix of 128 kbps/320kbps/uncompressed on the subway with ANC on high despite the default Bluetooth settings so I'm not seeing much potential for proper SBC codec use.

https://www.npr.org/sections/therecord/2015/06/02/411473508/how-well-can-you-hear-audio-quality

Anyways it's good that there is a lead for investigation. I can test to replicate on my side with settings changes tomorrow when I'm traveling to work.

I'll also validate with my MPOW Bluetooth stereo receiver (erm pocket sized cheapo SBC adapter from China might be better wording) that I used with IEMs before I got the Bose.

Here is another screenshot of the settings with no device connected. No values seem to be selected which is what makes me think they are selected automatically when a device connects and then does it negotiate with the device or how does it actually select?

Also here's a LOS setting related to SBC to try out of this is still applicable

https://lineageos.org/engineering/Bluetooth-SBC-XQ/
[OnePlus 3 & 3T Cross Device Development] BruhToine:
I think the Bose default is AAC even for Android, but I changed it because I can see I slight difference in audio quality between those two codec. If you want to test, you need to disable the HD Audio AAC in the bluetooth setting of the device (Not in dev options).

If you are able to replicate on your bose or mpow, it would confirm that this is not my setup and not an hardware issue. Be sure to turn off the bluetooth and the device each time you test. Sometime it happen on the second try, sometime after 5 times or after rebooting the phone. It mostly happen when I turn on the bose first and after ~3 second I turn on the bluetooth on my phone.

Thanks for your help.
[OnePlus 3 & 3T Cross Device Development] felagund:
When I disable HD audio on Bose I experience the same problems. Couldn't test MPOW today.
[OnePlus 3 & 3T Cross Device Development] BruhToine:
Nice, at least I am not alone with the bug. Would you mind the test the SBC with the MPOW to confirm this is not only with the Bose ?

[MENTION=4405529]nvertigo67[/MENTION] Could we do something more to help to fix the problem on Lineage OS ?
[OnePlus 3 & 3T Cross Device Development] :
This seems device specific: I've borrowed a cheap noname headset which works flawlessly for a couple of hours including some reconnects with SBC (pain to listen, if used to Teufel BT Move with aptx). The last 2 days I had a rental car with bt, music app works great with SBC and about 20 reconnects. Both devices connects with SBC without forcing it to do so (dev-opts set to system defaults).

Sidenote: the car sounds much better when forcing AAC. The noname headset doesn't work with AAC at all.