yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] melasuda:
Is this bug happening to anyone else? The icons for the current sound/notification settings do not show up correctly on the status bar when the phone is unlocked, but they show correctly when it is locked. I did a clean flash.

Here are some screenshots, look at the status bar at the top:

I'm on the 20190420 nightly.

You can see the alarm icon is gone, so is the do not disturb one, and the no ringing one. Instead, there's just a dot, and I don't know why.
[OnePlus 3 & 3T Cross Device Development] vinoxflame:
try putting back the clock on the left again and see if it's still there same
[OnePlus 3 & 3T Cross Device Development] Dirk:
Because notches.

People have mentioned this in the RR thread too. The dot is the overflow symbol meaning you have too many icons on that side of the notch so some are hidden. (Yes, i know the OP3/T doesn't have a notch, no it's not my fault, yes Google are often stupid to the point of absurdity).

File a bug report on Gitlab. Perhaps something can be done about it. For now you can reduce your icon clutter a bit or prioritise what you want to see. I assume you could put the Clock back to the left? I thought i'd hate having it there but i got used to it really quick.
[OnePlus 3 & 3T Cross Device Development] melasuda:
Oh that makes sense. I didn't know it was the overflow icon. I moved the clock to the center, they all appear now. Thanks!
[OnePlus 3 & 3T Cross Device Development] enochpc:
Still having audio issues, various things with the audio are making the phone lock up, on 4/23 build right now. Works fine for awhile and then I lose audio and once that happens it's only a few minutes before the phone locks up and I have to reboot. Trying to eliminate if it's and hardware issue. I am going to try the 4/25 build and if that doesn't work I will go back to something last week. If the problem doesn't go away I will try to get some logs. I am a little worried it's my phone as no one else seems to be having this issue.
[OnePlus 3 & 3T Cross Device Development] :
Did you forgot a "not" or a "doesn't"? The above doesn't make sense... ;)
[OnePlus 3 & 3T Cross Device Development] enochpc:
You are 100% correct, I have edited the post. I am going to blame the mental anguish my phone is causing my right now. ;)
[OnePlus 3 & 3T Cross Device Development] BillGoss:
But it's not bothering your left? :laugh:
[OnePlus 3 & 3T Cross Device Development] Dirk:
I feel your pain.

On both sides!
[OnePlus 3 & 3T Cross Device Development] HeXDeMoN:
I still have issues with AudioFX, it seems like Bluetooth has its own AudioFX setting as I recall having it disabled, connected to a Bluetooth device and then AudioFX showed it enabled, after I disabled it again with device connected it stayed disabled. I never tried to recreate this scenario so your milage may vary.
[OnePlus 3 & 3T Cross Device Development] kman93:
I have also been having audio issues, i don't mind audio fx so idk if that has to so with it, but a Bluetooth stream won't pause on disconnect (like turning off my truck), and if i pause it via any Bluetooth device (the default music app) I can only resume playing via that same control unless I kill the process and start it again
[OnePlus 3 & 3T Cross Device Development] :
Have the both of you tried the audiofx workaround mentioned earlier in this thread?
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
Good news (maybe), after communicating with oneplus stuff they promised fw upgrading with unlocked bl will be fixed in future builds.
[OnePlus 3 & 3T Cross Device Development] HeXDeMoN:
The workaround is disabling/deleting audiofx lol, I've had no issues after turning it off (had to turn off twice like stated once with Bluetooth device and again without)
[OnePlus 3 & 3T Cross Device Development] :
;) If you delete AudioFX, you doesn't need to disable it - not even once... ;)
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Thanks for the awesome news. Waiting for it to get fixed so that I can try OOS P again. Formatting internal memory on each P to O and vice versa flashing is a big PITA.
[OnePlus 3 & 3T Cross Device Development] Der-Knuffi:
My question is - I think - unrelated to developement, but I think here are the smartest people to answer it ;)

Is there a way to lock apps so they stay active in the background? I have "dooblou WiFi file explorer" running und to copy files on my OP3 it should stay running in the background. But some system process keeps killing the background apps after a certain time. On other ROMs I have seen a "lock" on the app in the recent menu.

I already have excepted the app from the battery optimization.
[OnePlus 3 & 3T Cross Device Development] Dirk:
If there were a way it would make millions of people happy. It's often referred to as bad RAM management, but it's really Battery management. Background processes are often killed long before RAM is even close to being fully utilised. As long as they're excluded from 'Optimisation', the apps i use stay in memory, although they might disappear from Recents. (Another issue entirely).

The 'Lock' function you refer to is only there to keep the cards in Recents when 'Clear All' is used. It's not to keep them in memory. As far as i know nobody has yet figured out a way to force something to stay in memory, unless that option exists in the App itself, (which requires Accessibility access i believe).

I know people have tinkered with LMK settings but i don't think this is a panacea for all the causes of these issues. I don't know how relevant these are today, but you might find them an interesting read:

https://www.droid views.com/tweak-android-low-memory-killer-needs

https://android.stackexchange.com/q...vent-android-task-killer-from-killing-certain

You might try contacting the app developer to see if there's anything that can be done? Or perhaps get some logs and see if there's anything there that might explain why it's dying in the background? Try some different ROMs or Kernels if you have the patience. See if anything helps.

Edit: Something strange with that first URL. Had to put a space between 'droid' and 'views' to get it to show.
[OnePlus 3 & 3T Cross Device Development] anyone23:
First of all I wanted to thank dianlujitao & the LineageOS team for this great rom. I ordered my OP3 the day it was announced, installed LOS within 10 minutes of unboxing it and everything has been fantastic so far. I even had a 24 month period where the phone ran absolutely flawless with 0 crashes or issues. :D This just shows how reliable and stable this rom is.

However there is one thing I'm wondering about. Today I had an emergency and needed to call someone and unfortunately I had a really hard time understanding the other person because calls are extremely quiet on my OP3. I know that there is a workaround by editing mixer_paths_tasha.xml and increasing the value of "RX0 Digital Volume" however you have to repeat this every time you install an update. At the same time every single call I make is far too quiet and I have to enable speaker mode and so this feels like a bug to me.

That's why I was wondering if it's possible to increase this value by default in LOS. With a quick test a value of 95 seems to do the trick, at max. volume there is a bit of distortion but at the same time this gives you a bit of headroom to boost quieter calls.
[OnePlus 3 & 3T Cross Device Development] :
This is just not possible - the first (beta) release of los for op3 wasn't there, when the first op3 were shipped... Hopefully the other information from your posting is more accurate.

I don't know why some devices needs this. On normaly working devices this patch will surely break the speakers: if used it's not only much too loud, but on 40 - 50% volume the speakers start with dissorted sound. I've never gone behimd the 50%, but I'm pretty sure it will break the hardware!

Why not make a flashable zip with an entry in /system/addon.d for those who need it.

BTW: https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/29936
[OnePlus 3 & 3T Cross Device Development] anyone23:
Of course it was called CyanogenMod back then but the OP3 was announced on June 14th and an initial build of CM was released on June 15th: https://xdaforums.com/oneplus-3/development/rom-unofficial-cyanogenmod-13-t3399089

That was really crazy fast. :) I still remember flashing this build right away when I got my device. It ran surprisingly good already except for some reboots when using Bluetooth. :)

Okay, I understand. So changes to the mixerpath file would affect other devices in a negative way.

Weird how some people say the volume level is decent again with Nougat blobs. I have never noticed a difference between different blobs (recently switched to P firmware), the OP3 has always been very quiet with LOS. What do you think about the call volume?

Yeah, maybe that's the best way for me.
[OnePlus 3 & 3T Cross Device Development] :
Wow. I havn't realized ther was an 13 build.. Sorry...

This in call volume issue is a real mystery to me: I've tried to get down to the cause, finding different causes like physical dirt, blobs (back in 14.1 aka nougat times), audio mods. But after all, there are some devices with this persisting... Sadly, those devices have the same issue with different custom roms, but not with oos - that's why I guess (!!!) it's NOT the hardware itself(*).

That's why I think the best approach is a flashable zip, which replaces the mixer*xml and adds itself to addon.d (autoflashing after updates).

(*) differently manufctured audio chips (like the display panels on early op3ts compared to later manufactured op3ts). But then again we should have found some differences in the oss kernel sources...
[OnePlus 3 & 3T Cross Device Development] kman93:
i have disabled it with titanium backup but it appears i still have the same issues, both related to bluetooth, and neither make it stop working, it just continues playing through phone speaker on disconnect even with the default music app, and controlling media from a bluetooth remote of any sort seems to make apps fail to see the audio stream, but i can still control audio via bluetooth
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
In the next update

op3: fix OTA auto-flashing with encrypted f2fs.

==> https://review.lineageos.org/c/LineageOS/android_device_oneplus_oneplus3/+/247310

If userdata is on f2fs and encrypted (OOS stock config for userdata),

neither /cache/recovery/block.map, nor /cache/recovery/uncrypt_file

are created due to theses denials:

03-12 11:14:40.568 1290 1290 W Thread-26: type=1400 audit(0.0:176): avc: denied { getattr } for path="/data/lineageos_updates" dev="dm-0" ino=25753 scontext=u: r:system_server: s0 tcontext=u:object_r:ota_package_file:s0 tclass=dir permissive=0

03-12 11:14:41.575 6803 6803 W uncrypt : type=1400 audit(0.0:178): avc: denied { fowner } for capability=3 scontext=u:r:uncrypt:s0 tcontext=u:r:uncrypt:s0 tclass=capability permissive=0

Without block.map and uncrypt_file the automatic flashing of the OTA

without user interaction fails, and the user needs to manually mount

data, and flash the OTA manually.

Credit: [MENTION=5091734]dianlujitao[/MENTION] and [MENTION=4405529]nvertigo67[/MENTION] (==> https://review.lineageos.org/c/LineageOS/android_device_lineage_sepolicy/+/244801)
[OnePlus 3 & 3T Cross Device Development] linrunner:
[Workaround] Hotspot not starting "hostadp.conf permission denied"

Hotspot refused to activate. Simple workarounds didn't help at all.

Constraints:

OP3, 5.0.8 firmware

lineage-16.0-20190429-nightly-oneplus3-signed.zip

MindTheGapps

su addon

/data formatted with f2fs, encrypted

"Dirty" upgrade from 15.1, 14.1

Log message was:

... E hostapd : Cannot write hostapd config to /data/vendor/wifi/hostapd/hostapd_wlan0.conf, error: Permission denied

So I removed the whole directory /data/vendor/wifi within TWRP:

adb shell
su
rm -r /data/vendor/wifi

System rebooted. Works again :o.
[OnePlus 3 & 3T Cross Device Development] Oyorf:
What would be best kernel for this? As it seems that next nightly will be possible to install with autoupdate with f2fs I think I will install that, but then I think I need also some custom kernel to pass safetynet as it seems that Magisk is not 100 %.
[OnePlus 3 & 3T Cross Device Development] Dirk:
Personally i prefer to use a ROM that passes Safetynet rather than roll the dice with 3rd party Kernels. You'd have to ask around to see what other people are having success with.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
I find that Magisk works just fine and I have no issues with Google Pay (don't need to hide it or Magisk Manager or anything else). I'm on 19.1 stable.
[OnePlus 3 & 3T Cross Device Development] Zebnastien:
I updated TWRP, Lineageos and Gapps in a row and got Google Pay disabled ("your phone is in root mode or has been modified"). My phone is not rooted. I will investigate but as a noob, I don't expect getting so far.
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Los does not pass safety net (unlocked bootloader). You need a custom kernel or Magisk.
[OnePlus 3 & 3T Cross Device Development] Der-Knuffi:
Is the new TWRP 3.3 safe to use? I've seen there were some problems in the beginning.

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] :
This question is too unspecific (3.3 can mean two different builds) and is better asked in the twrp thread.
[OnePlus 3 & 3T Cross Device Development] wjazdbitu:
I've got f2fs encrypted and the 20190504 nightly still required manual action in TWRP to install.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Of course, OTA Updater should work to automatically flash the next build... not the 20190504 build (which should fix this issue).
[OnePlus 3 & 3T Cross Device Development] vijaysivakula:
When i tried to update from 20190420 version to 20190502 version, it never came to the home screen. Showed "Phone is loading" or something like that.... for many reboots. Ultimately had to downgrade to 20190430 version which booted fine and is working normally now. Can we try the 20190504 version? Or is everyone aware of some problems with that version?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
No sweat with the 20190504 build (and previous)

I've already been faced with this issue.

An alternative:

- boot in recovery

- wipe cache/dalvik and system (only... not data of course).

- Flash the latest build, Gapp (nano or pico) and SU if needed.

- Reboot system.

- Enjoy ... hope so.
[OnePlus 3 & 3T Cross Device Development] Oyorf:
I updated from 20190315 to 20190504 and had to swipe once in twrp but other than that no problems at all and I have encrypted f2fs. Did not wipe anything but everything works just fine.
[OnePlus 3 & 3T Cross Device Development] spione2013:
Updated from 20190428 to 20190504 and all ok for now.. Dirty flashed, only wiped cache and dalvik.
[OnePlus 3 & 3T Cross Device Development] OTAx1:
Ready for that magic moment! :fingers-crossed:

20190504

f2fs

TWRP 3.3.0.1

Magisk 19.1
[OnePlus 3 & 3T Cross Device Development] Dirk:
Looking at that list i see a man who likes living dangerously! :p

Good luck. :)
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
It's time for the magic moment ... Perhaps ... ;)

==> https://mirrorbits.lineageos.org/fu...age-16.0-20190505-nightly-oneplus3-signed.zip
[OnePlus 3 & 3T Cross Device Development] Calum 2:
Twrp 3.2.3-1

Data f2fs

LOS 20190504

Successfully auto updated to 20190505.

You guys are awesome! Thanks so much!
[OnePlus 3 & 3T Cross Device Development] OTAx1:
Yes working. Thanks everyone! :D
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Good news and thank you [MENTION=6911010]Calum 2[/MENTION] and [MENTION=9794780]OTAx1[/MENTION]

We have to give credit to [MENTION=4405529]nvertigo67[/MENTION] for fixing OTA auto-flashing with encrypted f2fs and [MENTION=5091734]dianlujitao[/MENTION] for merging it… Thanks to both of you!
[OnePlus 3 & 3T Cross Device Development] :
Don't...
[OnePlus 3 & 3T Cross Device Development] Calum 2:
Well, sh!t. Which one should I use? I thought that was the safe one still..?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
TWRP 3.2.3-10 (@dianlujitao's TWRP) : https://androidfilehost.com/?fid=1395089523397907195
[OnePlus 3 & 3T Cross Device Development] Dirk:
3.2.3-10 is the safe bet right now as everything works. You can use it to carry out format operations in either EXT4 or f2fs without issue.

Edit: Beaten by Eric ninja post. :D
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
except the time bug. But that issue isn't important :)
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
For removing date/time issue:

==> flash 3.3.0-1, reboot recovery and then flash 3.2.3-10 ... ;)
[OnePlus 3 & 3T Cross Device Development] Dirk:
You are correct on both counts.

You sir are also correct, and this is exactly what i did after you discovered this previously. Funny enough i had the exact same issue on my OP5. The existing 'working' TWRP also had the time bug, and just like this device, the new TWRP builds are broken. (In different ways). The solution to the time bug was the same though. :)
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
Didn't fix it for me, but that doesn't matter for me...
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Did you reboot system before checking?
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
flashed it via fastboot, booted to it and flashed the old recovery again via fastboot.

Should I do a reboot after booting to the recovery?
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Flash 3.3.0-1, reboot recovery, flash 3.2.3-10, reboot recovery, reboot system and then reboot recovery for checking date/time issue.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
nope, didn't work. don't mind...
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
Sorry, I am wrong:

1- Flash 3.3.0-1, reboot recovery, reboot system and then reboot recovery for checking date/time issue.

2- Flash 3.2.3-10, reboot recovery, reboot system and then reboot recovery for checking date/time issue.

NB: You can flash *.img via Install in recovery.

Edit: I just did the procedure and it works for me.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
After Step 1 the date is correct (as it's fixed in 3.3). But then after step 2, it's again wrong in 3.2.3-10...

But it's getting OT here. I can live with the wrong time.. :)
[OnePlus 3 & 3T Cross Device Development] pbergonzi:
Is hotspot working properly in this rom? After Nougat, Oreo and Pie roms would not allow the "dun" parameter to be inserted in the APN with error "Carrier does not allow type dun", so tether was broken.
[OnePlus 3 & 3T Cross Device Development] :
This is not broken, but intended (aka aosp standard behaviour). I've tried to get this into 15.1, but it wasn't wanted:

https://xdaforums.com/showpost.php?p=77879631&postcount=3887 I'm pretty sure, this is still the case for 16.0.

As an alternative, I can offer to push something lile this https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/230186 (aka adding dun to your carrier), if you tell me your carrier's mcc/mnc.

BTW: 5GHz Hotspot will most proberly not work (depending on the region). See my analysis on channel selection:

https://xdaforums.com/showpost.php?p=78801979&postcount=569
[OnePlus 3 & 3T Cross Device Development] pbergonzi:
I understand that it is intended, emplaced by google for the benefit of providers, and that the rom is not broken. I'm sorry your work wasn't accepted, and appreciate that you tried to fix it.

I still use PA Nougat because of this, having found nothing yet that corrects google's faux pas in Orea or Pie.

Seemingly, I will never be able to get a new OnePlus phone, because they are all on O or P etc., unless someone decides to hack--I mean, "fix" this.

The network is still 4G where I am, so 5G is not a concern.

mcc=310 mnc=260

Thank you.
[OnePlus 3 & 3T Cross Device Development] :
I'm talking about the ap on the 5GHz (instead of 2.4GHz) band (needed to offer 802.11 ac to the clients) - not of 5G mobile standard. op3/t's hardware isn't 5G capable, so this will never work!
[OnePlus 3 & 3T Cross Device Development] pbergonzi:
Oh, thank you--I apologize.
[OnePlus 3 & 3T Cross Device Development] Calum 2:
Working here.
[OnePlus 3 & 3T Cross Device Development] bschmidy10:
Is there a pie firmware flashable zip? Or is there any reason to update from 8.0.0 firmware? I know official came our recently from oneplus.

Sorry if this has been discussed, didn't see any links in OP and search wasn't too helpful

Thank you ?
[OnePlus 3 & 3T Cross Device Development] :
I can't belive, you've read the op:

The op clearly states to use latest OxygenOS 5.0 firmware.

I can't belive, you've tried thread search:

https://xdaforums.com/search/thread/3866517?query=firmware

Click on the 5th hit and read the hit and the very next answer.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
You can read this thread: https://xdaforums.com/oneplus-3t/how-to/firmware-beta-10-t3631166

and more specifically .... https://xdaforums.com/showpost.php?p=79397249&postcount=492

Edit : But this is not recommended on official LOS 16.0 as [MENTION=4405529]nvertigo67[/MENTION] just pointed out...!
[OnePlus 3 & 3T Cross Device Development] :
Is "T-Mobile US LTE" the apn shown in the settings list you want dun added? (too much 260s... ;) )
[OnePlus 3 & 3T Cross Device Development] pbergonzi:
That is the name of several choices of APN currently, however for easier identification, the name "TMO" might be better.

The one I made separately is called "tmo", however anything will do.
[OnePlus 3 & 3T Cross Device Development] :
I don't want to add an additional apn, but add the type dun to the existing apn. I also don't want to change/add a name (this leads to endless discussions in gerrit). So I need to now the name displayed in the apn settings list, which is selected after a clean flash (aka your default apn). From the current apns-conf.xml I would guess it's "T-Mobile US LTE" (https://github.com/LineageOS/androi...-16.0/prebuilt/common/etc/apns-conf.xml#L1390 ). Since I can't test this myself (mcc=262), I don't want to rely on guessing.
[OnePlus 3 & 3T Cross Device Development] pbergonzi:
Ohh..., I see what you mean.

Yes, that is the correct name of the default APN.

There are 2 indentical--one has "default,supl", and the other has "ia". Neither of these work with tether, as there is no "dun" parameter, however the one that the rom defaults to at install is "default,supl".

The new functioning one I made that works as hotspot, has "default,supl,mms,dun".
[OnePlus 3 & 3T Cross Device Development] :
I've made this commit: https://github.com/nvertigo/android...e039d63#diff-88a8f4af39dc96e37de2afd231aa4628

To test the patch, reset you network settings (Settings->System->Advanced->Reset options->Reset Wi-Fi, mobile & Bluetooth), reboot to recovery, flash attached zip (and check the output for messages), save a recovery log and reboot to system. Check if dun appears in apn settings, if so: check if tetering is working.

As soon as you've verified it's working, I'll push it to los' gerrit.

BTW: There should be only one list entry of "T-Mobile US LTE". If there's more then one, reset your network options again and reboot.
[OnePlus 3 & 3T Cross Device Development] pbergonzi:
Thank you.

I will test within a few days.
[OnePlus 3 & 3T Cross Device Development] Eric_Lev:
May I ask a few questions:

1- On LOS 16.0? Which TWRP? ext4 or f2fs? Encrypted data or not?

2- Does this make a difference compared to the previous firmware (5.08)?

3- Do you recommend the open beta Pie firmware?
[OnePlus 3 & 3T Cross Device Development] bschmidy10:
Happy to help

Yes running LOS 16.0

Ext4, unencrypted

I notice no difference in performance or battery life, however it appears to not be compatible with the fingerprint reader, which led me to reflash 5.0.8

As I asked before, I'm not sure how the firmwares affect custom ROMs, so at this point I would suggest to just stick with 5.0.8 at least until LOS is using the (presumably stable) OnePlus 3/t PIE firmware as it's base