yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Hellera:
Hello friends! This has never happened to me before, nor with any other custom ROM ... that is, I was left without any sound ... no ringtone, no sound of notifications, alarm ... no sound! I checked in Settings-Sound, the respective sliders were at zero ... without me going to anything! It should be mentioned that I never activated DND, I did not go to the side slider button, I checked this in Settings-System-Buttons-Additional buttons ... and I do not use other applications related to sound ... So, did anybody else encountered this problem? Any helpis more then appreciated, thank you.
[OnePlus 3 & 3T Cross Device Development] Sudhangshu:
Well as you have said I think this issue is specific to you only, can you describe further like how it happened wether you installed or flashed something in your device, your recovery version, firmware version etc.

Well i had this issue on paranoid and flashing stable firmware solved this issue for me.
[OnePlus 3 & 3T Cross Device Development] Hellera:
First of all, latest firmware oxygen 9.0.6, latest TWRP 3.4.0, latest Laneage-OS 2020-07-27, latest nano-gapps. It has been working very well for several months, I can't complain about anything else. I didn't install anything special in TWRP, nothing flashed. How it happened? I had it in front of me on the table when I received a call ... but no sound! This happens the second time, the first time I didn't pay attention... so I can't say it happens with a certain periodicity. I'm not using any sound apps, tricks, I'm not using the phone for listening music atall... What should I do?
[OnePlus 3 & 3T Cross Device Development] Sudhangshu:
Well i couldn't pin point your issue but here's few things you can try look for any app in your phone that may have special access to change system sounds.

And does the sound works while connected to external speaker or headphones.

Or is there headphone plugged in icon displayed on the status bar.

And did you tried factory resetting your phone.
[OnePlus 3 & 3T Cross Device Development] :
If you've run los-17.1 for several months, why and when did you flash "latest nano gapps" (exact version is always better to decode for people trying to help you)? gapps and gservices are updated by playstore, if you reflash gapps manually to update, you are asking for trouble and starnge side effects!

See: https://xdaforums.com/showpost.php?p=83170309&postcount=7

BTW: without a log of the issue all advices are blindly guessing, though I guess a clean flash will do the trick.
[OnePlus 3 & 3T Cross Device Development] Hellera:
Thank you [MENTION=4405529]nvertigo67[/MENTION] for the link... I know that, I never reflash gapps at the ROM update... I'm not an advanced in android but I'm not a beginner either... I meant "latest nano-gapps" at that time of lineage install.
[OnePlus 3 & 3T Cross Device Development] :
Hopefully you see that "latest" and "latest at the time of install" is not only ambigous but in this case even misleading. Explaining "latest" as "latest at the time of install" without giving the time exact time of install is no additional onformation. Considering I've already written "exact version is always better to decode for people trying to help you", your answer doesn't motivate me to continue to try to help you.
[OnePlus 3 & 3T Cross Device Development] DroidFreak32:
Okay, I just faced this issue and I thought of investigating it further.

From the logs in the issue tracker, we see a lot of these errors:

04-18 13:20:11.705 E/audio_hw_primary( 3964): start_input_stream: use case assigned already in use, stream(0xe90768c0)usecase(18: audio-record)
04-18 13:20:11.705 D/audio_hw_primary( 3964): in_standby: enter: stream (0xe90768c0) usecase(18: audio-record)
04-18 13:20:11.726 D/audio_hw_primary( 3964): start_input_stream: enter: stream(0xe90768c0)usecase(18: audio-record)
04-18 13:20:11.726 E/audio_hw_primary( 3964): start_input_stream: use case assigned already in use, stream(0xe90768c0)usecase(18: audio-record)
04-18 13:20:11.726 D/audio_hw_primary( 3964): in_standby: enter: stream (0xe90768c0) usecase(18: audio-record)
04-18 13:20:11.746 D/audio_hw_primary( 3964): start_input_stream: enter: stream(0xe90768c0)usecase(18: audio-record)
04-18 13:20:11.746 E/audio_hw_primary( 3964): start_input_stream: use case assigned already in use, stream(0xe90768c0)usecase(18: audio-record)

I grep'd this and found it comes from this line on the current 8996 audio hal HEAD:

https://github.com/LineageOS/androi...033a8d45fa43fe617a218165/hal/audio_hw.c#L2535

So, I checked the history of this file and I think the following CAF merge could be one of the possible reason:

https://github.com/LineageOS/androi...mmit/3e32f8e7829e012e6d528821a5ca700e6e28cbd1

If you check the changes in this merge for audio_hw.c you do see VOIP related stuff.

Next, this particular commit description looks interesting as well (it is a part of the above merge):

https://github.com/LineageOS/androi...mmit/5781b50b9caf684bf1455436b9a2eef2d47e0233

Currently, our CAF Audio HAL isn't synced with the latest CAF TAG "LA.UM.8.6.r1-04700-89xx.0"

So I thought of merging the latest tag and see if there are any new changes that look relevant.

I am not really sure but I found this new commit by CAF interesting.

I wish I could go further and make a build with my above findings to see if I am just looking at the wrong place or if it actually makes a difference, but I can't find free time to do so.

Hopefully the links help [MENTION=5091734]dianlujitao[/MENTION] / Lineage Devs to make it easy to identify the root cause for this issue. Any other home builders can try it out and report though!

PS: I am no c/c++ guru and I only have basic coding skills, so take my analysis with a spoonful of salt xD
[OnePlus 3 & 3T Cross Device Development] Hellera:
Ok [MENTION=4405529]nvertigo67[/MENTION], with the next update I'll format everything and reflash everything from the scratch... anyway, thanks for your answers. :good:
[OnePlus 3 & 3T Cross Device Development] bugrahul:
Thank you very very much for your analysis. [MENTION=5091734]dianlujitao[/MENTION] and others will find great value in your findings, hopefully. With this issue active, the builds barely meet daily driver caliber.

I had just made our new baby bird; Yoda, mimic some kissing sounds we make. It couldn't have been any better, cos I got it all on video!! When I share this with our friends and family, they are gonna melt in love with my Yoda :fingers-crossed:

When I reviewed the video, as great as it looked, it was completely mute. No audio, silence, no kiss sounds. :mad: I rage-flung my phone across the room & my wife came running hearing the noise. Thanks to carpeted flooring, nothing happened to the phone.

This bug, like I stated before, makes these builds far from daily driver material. But I tolerate it, as I have my old phone on Android Q with the latest security patches. It also passes compliance checks of MobileIron MDM, so work stuff's accessible too, without even rooting the build. I tried using Magisk, but the phone kept losing it every time there's an OTA update and ultimately I didn't really care for it once I realized that I didn't need it to pass MobileIron compliance checks. The only thing I am used to, that my phone can't do without root+mask is use NFC for Google Pay. But hey, something's gotta give, I'm over it.

Hopefully this issue can be put to rest soon. It has been happening since 17.1 builds started.
[OnePlus 3 & 3T Cross Device Development] melasuda:
Is it safe to dirty flash from the latest LineageOS 16.0?
[OnePlus 3 & 3T Cross Device Development] Sudhangshu:
No
[OnePlus 3 & 3T Cross Device Development] melasuda:
Alright, thanks. Is there any way to update to 17.1 from 16.0 without formatting everything and keeping the system settings?
[OnePlus 3 & 3T Cross Device Development] Sudhangshu:
Well if you're root you can try titanium back or migrate app to backup everything from your device including system settings. Or else you can use google backup also.

Google backup doesn't backup your files and folder only apps are backed up.
[OnePlus 3 & 3T Cross Device Development] :
With major updates like from 16 to 17.1 I would not recommend using migration or backup apps. Better do a fresh install and use the backups from the apps itself (or Google).

System settings are not completely the same so do not restore system settings between major updates anyway!

---------- Post added at 12:35 ---------- Previous post was at 12:34 ----------

No..... ;)
[OnePlus 3 & 3T Cross Device Development] Sudhangshu:
Well that was new for me thanks for sharing it.
[OnePlus 3 & 3T Cross Device Development] melasuda:
Alright thanks guys.
[OnePlus 3 & 3T Cross Device Development] :
After some months on LOS17 now and everything running fast and stable I thought it was time to tweak a little again.... ;)

To run my own userinit.sh script I tried to add a line to the end of /system/init.qcom.post_boot.sh (/system/etc/userinit.sh &), added /system/etc/userinit.sh, did a chmod 755 but the script is not executed (added a line with echo "executed" > /system/emulated/0/bootlog.txt).

Any other ideas to execute a script on (post) boot automatically?
[OnePlus 3 & 3T Cross Device Development] :
selinux denials - check the log. You can use magisk to allow the denials from the log (you need basic selinux and basic magisk knowledge) or magisk's script dirs (you only need basic magisk knowledge). The aosp sepolicy rules have broken init.d and /data/local/userinit.sh support back on cm14 or los15.
[OnePlus 3 & 3T Cross Device Development] :
Thanks [MENTION=4405529]nvertigo67[/MENTION], though that's exactly the reason I tried it with "injecting" one of the system scripts. Hoped that would work...

Will check log ;)

But do not want to use Magisk, so when it is not possible without, I will let it go..
[OnePlus 3 & 3T Cross Device Development] :
It should be possible to build the policy and contexts alone and replace them in the sar partition, but I've never tried to rebuild sepolicy and stuff out of tree.
[OnePlus 3 & 3T Cross Device Development] Flippiej:
If anyone is wondering if the new Nearby Share function is already working in LOS:

Yes it is for me.
[OnePlus 3 & 3T Cross Device Development] counterfeit187:
Are the MMI codes not working for anyone on this rom? Can't use conditional call forwarding for voicemail with Google voice. I just get errors when I try.
[OnePlus 3 & 3T Cross Device Development] vikasbharaj30@gmail.com:
How is battery life compared to STOCK Oxygen OS ?

---------- Post added at 12:31 PM ---------- Previous post was at 12:29 PM ----------

what about battery life compared STOCK os ?
[OnePlus 3 & 3T Cross Device Development] gatoshino:
Hello dear community :)

I'm facing issues with WiFi. The connection is unstable and i lose connection almost every 5 Minute with the latest 17.1 LOS for the Oneplus 3T. Does anyone know a solution?
[OnePlus 3 & 3T Cross Device Development] tim-scrap:
What did you find with using the search function in this thread?
[OnePlus 3 & 3T Cross Device Development] vikasbharaj30@gmail.com:
thanks
[OnePlus 3 & 3T Cross Device Development] ycode:
I'm having the same issue. Disabling mobile data makes my wifi stable. So, after searching for clues, I found someone using MacroDroid would automate disabling mobile data when on any network and enabling mobile data when not connected to any wifi network. This is no solution, but makes my phone useable. I did have the same problem on PixelExperience Rom.
[OnePlus 3 & 3T Cross Device Development] gatoshino:
Thanks for your help! This is a great workaround i guess. Just need to check my wifi connection while disabling mobile data. I tried MacroDroid but it doesn't work. It just doesn't switch my mobile data from on/off
[OnePlus 3 & 3T Cross Device Development] ycode:
It only switches when noticing a change in network. So, walk outside or disable wifi to test.
[OnePlus 3 & 3T Cross Device Development] Ihe87:
You can use build in system profiles to do that.

Wifi connected -> turn off mobile data.

Worked for me. :svetius:
[OnePlus 3 & 3T Cross Device Development] Hemuli:
There's also a related setting in the developer settings: Mobile data always active. Default seems to be on. Does disabling that have a positive effect?
[OnePlus 3 & 3T Cross Device Development] ycode:
Thank you for your reply. No it does not. I can easily test this by watching HD content using my TV provider with both wifi and mobile data on. After just a few minutes the wifi has no signal anymore.

Update:

After a restart this seems more stable. Will keep testing with this setting.
[OnePlus 3 & 3T Cross Device Development] gatoshino:
Thanks a lot! This works! I will check if the connection is more stable :)
[OnePlus 3 & 3T Cross Device Development] IonutGherman:
Is [MENTION=5091734]dianlujitao[/MENTION] reverting back to OOS 5.0.8 firmware with Android 11 (LineageOS 18?)?

We want to get rid of Mobile network standby drainage and the only thing to do is to revert back to 5.0.8. I really love this phone and the only thing that is getting me mad is that drainage and I'm sure the other users too that left with this phone.
[OnePlus 3 & 3T Cross Device Development] ContactFront:
I dirty flashed when upgrading from 16.0 (wiped system, kept user data) and everything worked fine.

You could certainly try but there's no guarantee it will be 'safe'. There's always the risk. Make sure you have full backup and know what to do if things go south.
[OnePlus 3 & 3T Cross Device Development] xanadux:
Hi all! I clean flashed last build on my 3T, but I am facing "Voice match" issue on "Ok Google" module (grayed out and download failed).

I flashed open gapps nano.

Any solution?

Thanks
[OnePlus 3 & 3T Cross Device Development] Max1306:
Hi! Is VoLTE possible with LOS 17.1 without root?

Is GPS, Glonass and Beidou supported, like in stock-rom or is Galileo supported too?

Max
[OnePlus 3 & 3T Cross Device Development] :
Depends on mcc/mnc.

https://xdaforums.com/search/thread/3990061?query=galileo (Always search and read before posting.)
[OnePlus 3 & 3T Cross Device Development] MrKartupelis:
LOS 17.1 has been rock stable and fastest ever especially since downgrading GNSS HAL, thank you [MENTION=5091734]dianlujitao[/MENTION] for maintaining and keeping it up to date.
[OnePlus 3 & 3T Cross Device Development] Joshmccullough:
Working fine for me, I've tested it and everything. Might it be carrier-specific? I'm on Mint Mobile/T-Mobile, no problems here.
[OnePlus 3 & 3T Cross Device Development] Cotopaxi42:
Hi there,

My roommate and I both have the same phone: a OnePlus 3 With LOS 17.1 installed on it. But... We also have the same MAC address on both phones. Is this normal? And how can we change the MAC address of one of the phones? Because it gives us problems to connect to the wifi (only one phone can connect and not both, conflict of mac address I guess) and we can't create access points for each other (same cause).

Please, if you can help us, that would be great! :)
[OnePlus 3 & 3T Cross Device Development] BillGoss:
No, that's not normal - each device should have a unique MAC address.

I do know that the MAC address can be found in the persist partition (sda2) which is mounted as /mnt/vendor/persist and you'll see it in wlan_mac.bin. You might be able to change it, but I've never tried doing that.
[OnePlus 3 & 3T Cross Device Development] knpk13:
This reminds me, some other devices on Android 10 have an option to "use randomized MAC addresses for this network" in network settings to spoof MAC addresses for privacy. I don't see it on LOS for the OP3/T. Does anyone know why? If you can find the option to do that, I'd recommend using it. Although it shouldn't be required, because like BillGoss said, every device has a unique MAC address. I'm not a networking expert, but there's probably cases which result in duplicate MAC addresses, like certain hardware/configuration in the network, or if your device was obtained from a sketchy reseller/manufacturer.
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=2911853]BillGoss[/MENTION] is completely correct. Still one question is left behind: change wlan_mac.bin to which value (btw: though it ends on bin it's a plain ascii file)? The very best solution is using the backup (I guess it's not present, since you need to backup the persist partition by hand, it's not included in twrp backups). The worst solution is guessing one (not all macs work, needs some patience and trail and error to find a workimg one). The most practical solution is using the msm unbrick tool, it should restore the persist partition.

Checking the help (and eventually how-to) forums for op3 and op3t should be helpfull, too (this topic is ot in a rom specific thread):

https://xdaforums.com/search/forum/5476?query=mac address

https://xdaforums.com/search/forum/6011?query=mac address

Good luck!

[MENTION=9350973]All[/MENTION]: sorry for OT!

---------- Post added at 08:51 ---------- Previous post was at 08:24 ----------

It's not working for op3/t. Tried enabling it since los-15. The mac is randomized (if the framework/base setting is overlayed; see below), but since only some macs are working (the non-working ones just can't connect to any ap), the randomized macs generally break wifi. I guess the framework doesn't like the qcacld driver on mac configuration (or vice versa) or the wlan firmware. Changing the mac settings in the ini file doesn't make it work.

For homebuilders: you can enable mac randomization by overlaying config_wifi_connected_mac_randomization_supported in $DEVICE_TREE/overlay/frameworks/base/core/res/res/values/config.xml
[OnePlus 3 & 3T Cross Device Development] Hemuli:
Have you looked into the HAL methods to see if there's something obvious missing? https://source.android.com/devices/tech/connect/wifi-mac-randomization
[OnePlus 3 & 3T Cross Device Development] RKS96:
MYB you could send mac to trusted maintainers and check if someone else on XDA have the same mac as you do!! What ever the case is it is weird that 2 devices have a same mac address. I thought that mac is backed with hardware, so it can't be changed - at least permanently.

Only realistic possibility is if it indeed is randomly generated mac and for a generation as random input is used, your network name, gateway act (stuff that is same for both devices).
[OnePlus 3 & 3T Cross Device Development] :
As stated in my last posting: the randomization is working. Most macs just doesn't work (if setup correctly; just doesn't connect anymore), no matter if chanhed manually or automatically.

Of course it's hardware backed, otherwise msm unbrick tool wouldn't be able to restore it. As a matter of fact, los (and aosp) set it from wlan_mac.bin (as long as randomization or any third party tools arn't enabled/used).
[OnePlus 3 & 3T Cross Device Development] Holgott:
Hi, can anyone guide me how to increase max. media volume? Couldn't find mixer_paths in system/etc like it was in years before. Any help would be much appreciated.
[OnePlus 3 & 3T Cross Device Development] tim-scrap:
Just use search function in this thread, you will find the new location of the file
[OnePlus 3 & 3T Cross Device Development] Aservatenkammer:
Why is there no new Build since over 10 days?
[OnePlus 3 & 3T Cross Device Development] :
You can check the build logs yourself: https://buildkite.com/lineageos/android/builds?branch=lineage-17.1

Disclaimer: it's a pain in the arse to find a build on buildkite.
[OnePlus 3 & 3T Cross Device Development] Hemuli:
It's easier from this page https://buildkite.com/lineageos/android-nightly/builds

Seems like the pipeline was not run last Monday for some reason. Oneplus3 seems to be built always on Mondays.
[OnePlus 3 & 3T Cross Device Development] :
I can't find a single 17.1 build in the android-nightly builds: https://buildkite.com/lineageos/android-nightly/builds?branch=lineage-17.1

Disclaimer: it's a pain in the arse to find a build on buildkite.
[OnePlus 3 & 3T Cross Device Development] Hemuli:
The builds started by the pipeline are lineage-17.1 even though the pipeline deceptively says 16.0
[OnePlus 3 & 3T Cross Device Development] Cotopaxi42:
Thanks for your answers folks! I tried to change my mac address using this tutorial for rooted devices and Buxybox installed: https://www.**********.com/change-mac-address-android-devices/#Change_MAC_Address_Using_Terminal but it didn't work...

How do you know which new mac address to choose? And how do I see the file wlan_mac.bin? Can't see it with file explorer of the phone.

And more importantly, maybe, does it mean that all people using a OP3 with LOS installed on it have the same MAC address?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
If you're rooted, then a good file manager (my favourite is Solid Explorer) should let you access and edit the wlan_mac.bin file.

My MAC address is 94********01 which I expect will be different to yours. The rom (system) doesn't include the MAC address but reads it from the firmware/hardware.
[OnePlus 3 & 3T Cross Device Development] Cotopaxi42:
My MAC address is 00:xx:xx:xx:xx:43, which is different from yours but you own a OP3T and not a OP3, or am I wrong?

Thanks for your help, again! :)
[OnePlus 3 & 3T Cross Device Development] Hemuli:
No build this week either. The build failed before it even started to what looks like a manifest problem.
[OnePlus 3 & 3T Cross Device Development] :
The model doesn't matter her at all. Every ip-enabled piece of silicon has to have a UNIQUE mac address by definition:

https://www.ieee802.org/

https://tools.ietf.org/html/rfc5342

https://tools.ietf.org/html/rfc7042

https://en.wikipedia.org/wiki/MAC_address

Each device (also the same model) is required to have a unique mac address.

EDIT: Sorry for OT.
[OnePlus 3 & 3T Cross Device Development] Hemuli:
The first half of the mac address should tell which company allocated the mac address range. I tried to look up which address ranges are allocated to oneplus. None of them began with 00. You could try looking up yourself whose range does that address belong to.
[OnePlus 3 & 3T Cross Device Development] apon97:
I clean flashed the last build, didn't root it, and I'm having problems with setting up GPay (or other apps that require the phone not to be rooted).

Is this normal for custom ROMs? Is there any workaround?

Thanks
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
It's due to the open BL.

Install Magisk.

And read/search through this thread, it's mentioned X times before...
[OnePlus 3 & 3T Cross Device Development] punio4:
Anyone else having trouble with car stereo bluetooth connecting?

Works fine on 16, but on 17.1 it takes forever to connect, and sometimes it even doesn't connect. OOS works fine, as do iOS devices.

The car stereo has to be in exclusive bluetooth playback mode (doesn't work for voice navigation while in other modes like radio), and I need to disable phone functionality via bluetooth for it to even have a chance to work.

Changing AVCPR modes doesn't help. Any ideas who to ping? I'm not sure this is a OP3-only issue.
[OnePlus 3 & 3T Cross Device Development] Holgott:
I have to ask about this topic once again. Do anyone know which value in Mixer_paths I have to edit to increase maximum speaker volume?
[OnePlus 3 & 3T Cross Device Development] :
https://github.com/LineageOS/android_device_oneplus_oneplus3/blob/lineage-17.1/device.mk#L155

TARGET_COPY_OUT_VENDOR is system/vendor
[OnePlus 3 & 3T Cross Device Development] Holgott:
Thank you but I meant which line within this file I have to edit to increase the maximum speaker volume.
[OnePlus 3 & 3T Cross Device Development] :
If you search this thread (https://xdaforums.com/search/thread/3990061?query=mixer_paths) you'll find https://xdaforums.com/oneplus-3/one...eplus-3-3t-t3990061/post82338635#post82338635 .

DISCLAIMER: Be carefull, you may damage your hardware, ny increasing these values.

Sidenote: please search and read before posting for future issues.
[OnePlus 3 & 3T Cross Device Development] Holgott:
Thank you once again, but I searched alrdy and found the post you linked. But the values described in this post are for increasing the earpiece volume. I want to increase the speaker volume on the bottom of the device.