yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
I inserted a wired headset with built-in mic, made a phone call from another phone, and everything worked fine, I could hear from the other end and the other end could hear me (from built-in mic of course).

Cannot reproduce the issue, did I miss anything?
[OnePlus 3 & 3T Cross Device Development] Hazuki Amamiya:
Thanks for the help from the forum! I am now able to complete the building of ROM. However, when I was attempting to boot the Pie after dirty flash from Oreo, my phone always shows "Decryption unsuccessful - The password you entered is correct, but unfortunately your data is corrupt."

I was able to revert back to Oreo by dirty flash without losing data. I wonder if there is any fix for this so that I can upgrade to Pie with dirty flash and an enrypted phone?

I used test-keys to build both Oreo and Pie, and I have installed TWRP3.2.3-1 and 5.0.7 firmware. Any help is appreciated :)
[OnePlus 3 & 3T Cross Device Development] :
https://github.com/nvertigo/local_manifest/blob/nlos-16.0/current.pick.sh#L12-17

Worked for me with encrypted (encryption initialized with 15.1) f2fs.
[OnePlus 3 & 3T Cross Device Development] legendavey:
I performed the exact same steps you mentioned here with a different wired headset, but the issue still persisted. Then rebooted the phone and now I cannot reproduce the issue on both the headsets. This is really weird. Will attach logs if it happens again. :/
[OnePlus 3 & 3T Cross Device Development] abhibnl:
No one would recommend a dirty flash between Android version flashing. It's totally your decision though but for me personally, it has always caused some issue or another. Your issue though, seems more like a commit issue as I assume you are flashing your personal build.
[OnePlus 3 & 3T Cross Device Development] namanjr:
Privacy guards menu isn't working for me. All apps are selected, taping, or long pressing also seem to do nothing. Is this not implemented yet or a rom specific bug?
[OnePlus 3 & 3T Cross Device Development] BillGoss:
Same here.
[OnePlus 3 & 3T Cross Device Development] dianlujitao:
It would be nice if you could figure out a way to 100% reproduce the issue.

PG is WIP
[OnePlus 3 & 3T Cross Device Development] :
Since a couple of days it's working quite well. I've realized that if you pick pie-privacy-guard after pie-su (even when compiling without WITH_SU) not only all merge conflicts are gone, but pg is also working... ;)
[OnePlus 3 & 3T Cross Device Development] Syssx:
Hey guys, here to report some things I noticed, as mentioned before - PG doesn't work for me and some icons doesn't show up in status bar e.g. NFC, Bluetooth - i noticed that switching switches in settings of status bar for some icons causes network signal bars to move around (with dual SIM), and lastly network speed indicator in status bar is broken too. I also noticed some scrolling and animation lag in menus using "balanced" power profile, which i switched to performance because of this. Very last thing that caught my eye was that when you scroll down the notifications with dual SIM, theres only one signal bar (i don't even know if its supposed to be like that.

I guess all of those problems are ROM specific, and not device-specific as LOS16 is still in beta. Also they're all just minor things.

Otherwise I didnt find any breaking things, I'll use last build as my daily driver for some days (now that it passes safetynet and I can use my banks mobile payments with NFC :))

Thanks for this rom and your work guys.

ps. if youll need any logs regarding issues above, just let me know.
[OnePlus 3 & 3T Cross Device Development] pitrus-:
For those that are interested to know. I've tested Google Pay on LOS16 with Magisk root, works flawlessly. [emoji4]

Skickat från min ONEPLUS A3003 via Tapatalk
[OnePlus 3 & 3T Cross Device Development] H. K. ROY:
bug report: enabling and then disabling on-screen navbar causes the hw navigation losing touch vibration until the device is restarted
[OnePlus 3 & 3T Cross Device Development] legendavey:
FWIW, I don't use Magisk or any other Safetynet hiding methods and I was surprised to see that simply flashing LOS + GApps results in a certified device and GPay working 100% + Netflix available via the Play store. :fingers-crossed:
[OnePlus 3 & 3T Cross Device Development] knpk13:
Really? That's weird. Since official LOS can't include the safety net patch. Maybe this unofficial build includes it. Doesn't matter to me since I need magisk for root anyway. But good for you lol.
[OnePlus 3 & 3T Cross Device Development] Master_TC:
New Release is up 20181222:good:
[OnePlus 3 & 3T Cross Device Development] laupuy:
Thanks :good:

and here the changelog: 2018.12.22:

Sync latest source

Slider key fix by [MENTION=4405529]nvertigo67[/MENTION] :good:

App launch boost & touch boost, hope it helps reduce lagging

;)
[OnePlus 3 & 3T Cross Device Development] legendavey:
You're right. Official LOS doesn't attempt to pass Safetynet, they explained it a while ago. But this build *appears to* be doing what flashing Franco kernel or EX kernel does - not reporting the bootloader as unlocked. That's the only reason I can think it passes here, besides having SELinux enforcing and no root solution flashed.

EDIT 2: Ignore this, had no idea what I was talking about, OP clarified later and now I know better :)

EDIT: The latest build has a new vibrate mode for the alert slider. We now have a reliable 3-state volume control on LOS 16. Big thanks to [MENTION=4405529]nvertigo67[/MENTION] for this one!
[OnePlus 3 & 3T Cross Device Development] Kunqa:
Camera broken in last official update, just FC, i found only this change about camera https://yadi.sk/i/A_7LZk-eEbBOvQ
[OnePlus 3 & 3T Cross Device Development] :
No problems for me with today's LineageOS release (16th) and integrated camera app
[OnePlus 3 & 3T Cross Device Development] Kunqa:
my bad, now cam works, thanks :)
[OnePlus 3 & 3T Cross Device Development] :
Everybody suffering from delayed 5GHz AP scan, may wan't to tty this: https://xdaforums.com/oneplus-3/one...-nlos-16-0-t3879405/post80247634#post80247634
[OnePlus 3 & 3T Cross Device Development] felagund:
Will try tonight just need to get home first. I thought the delayed 5G was a feature and not a bug as I only recently got the ac router and thought even though I set it out of DFS ranges the phone still needed to follow routines for delayed scans and validation.
[OnePlus 3 & 3T Cross Device Development] :
I thought that, too. I was wrong... ;) Honestly, this setting is so much at the top of the config file, I've never realized, that it's there at all! *lol*

EDIT:

Since it's a configurable behaviour, it's indeed a feature. ;)
[OnePlus 3 & 3T Cross Device Development] felagund:
Confirmed this works.

I deleted the line through X-Plore and rebooted. Voila 2g and 5g popped up simultaneously and did so also in most of the next toggles of the wifi.

I just don't know why this happens. It's supposed to skip DFS channels only and only on initial scan.

Is turning WiFi on considered initial scan? I expect it is and I'm often switching it on.

https://gitlab.com/Codeaurora/platf...mmit/13ea0b968b0a24b8fcdc843c88733737fc8799b6

Also my router broadcasts on lowest channels with a 40mhz spread so it's 40mhz below lower border of the DFS range.
[OnePlus 3 & 3T Cross Device Development] :
At least the commit description is wrong. Obviously all 5GHz channels are effected by this setting. I'm afraid the complete DFS (and SRD) handling is somehow glitchy. I belive it's not (or not only) the kernel driver but the hostapd, fw/net and/or fw/base plays in here, too. See my analysis on 5GHz tethering hotspot. Also: if I enable automatic channel selection in the kernel driver hotspot stops working all together...
[OnePlus 3 & 3T Cross Device Development] BillGoss:
FWIW, I've never had any issues with 5g wifi. I've always used 5g to access my router because it's less crowded than 2g.

My phone sees both 2g and 5g APs almost instantaneously when I turn wifi on.

Removing the gInitialScanNoDFSChnl line makes no difference on my phone.

Fyi, my router is set to use channel 36 (rather than Auto) for 5G because when I first set things up this channel wasn't being used by other nearby routers.

Also, my wifi off icon behaves normally after editing the WCNSS_qcom_cfg.ini file.
[OnePlus 3 & 3T Cross Device Development] :
I'm glad to read that - I've started to mistrust my perception and memory:

When the delay discussion came up first a few months back, I couldn't reproduce what some users expirienced (the delay). When turning on wifi my device immidiatly connected to my 5GHz AP. A few weeks back my device started to connect to my 2.4GHz AP when wifi was switched on and after roughly 30 seconds reconnected to tje 5GHz AP. At this point I started to doubt my memory and perception, because when I first saw this I hadn't flashed something for 6 days. With each new try and each occurence of connecting to 2.4 GHz AP first and later reconnect to the 5GHz AP my doubts grew larger...

Though I have no explenation to offer, I'm happy only the wifi handling is broken, but not my perception or memory!

EDIT: for the record: my 5GHz hotspot runs on channel 36.
[OnePlus 3 & 3T Cross Device Development] jakito:
Just following that guide is enough?

I did everything you said from TWRP and restarted twice now. I've also checked the file using root explorer and the line has been correctly deleted...

I still have 30 seconds difference between the appearance of 2.4ghz and 5ghz wifi

Edit: clearing cache and dalvik made it work!

THANK YOU

This was driving me crazy because I have a mesh network with 2.4 and 5ghz and when the phone automatically switched between APs it always decided to go to the 2.4, breaking downloads, games...

Thank you so much!
[OnePlus 3 & 3T Cross Device Development] felagund:
My AC network is the only one on 5g around and everyone else is on insanely crowded 2.4g

My router is also on channel 36 and also only 40mhz bandwidth but I had the habit of switching wifi off when going to the room furthest away if I wanted to play a more demanding game on the phone as any latency was ruining and lte was faster.

Then when enabling it the 2g network connected first and the 5g 30+ seconds later. Due to this I kept disabling my 2g or manually checking the 5g one in saved networks to speed it up and prevent interruption on switching the network.

This has been pestering me and I am very happy this is solved for now (as I assume I'll need to reapply the fix when I flash a new version)
[OnePlus 3 & 3T Cross Device Development] ciarpame:
I'm having issues with recent Google Camera ports: white balance switch does not have effects on 6.2 versions for me (like AWB is always on), sometimes it works with 6.1 but I have to stick with a 5.x variant (Tolyan's v1.0.15_final_fix) to have white balance always working.

I wrote about this issue in the mentioned thread (https://xdaforums.com/oneplus-3/how...0fps-video-t3658552/post79524534#post79524534) but nobody replied so I guessed it was just me, maybe an issue related to interactions between LOS16 and recent Google Camera portings or maybe most people just do not use AWB settings.

I don't want to start an off-topic discussion here, I just take this chance to ask to other Google Camera users running LOS16 if they are experiencing similar issues. Thanks.
[OnePlus 3 & 3T Cross Device Development] Mr.Jay:
What happened to the blur effect when pulling down the notification bar?

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] jmadiaga:
TWRP 3.3.1-0 (unified) does work for me and also flashes the Magisk (add-on)
[OnePlus 3 & 3T Cross Device Development] :
Which fs setup? Encrypted? Secured boot?

---------- Post added at 09:08 ---------- Previous post was at 09:05 ----------

Examined the code:

An initial scan is done every time wifi is switched on or changed from SAP mode to client mode. Rescans are done while wifi is on.
[OnePlus 3 & 3T Cross Device Development] djplus:
Cache/System Ext4

Data f2fs

Encrypted.

Secure boot off.
[OnePlus 3 & 3T Cross Device Development] :
That's not the setup the well known updater issue occurs.

May I kindly ask you to raed and understand a widely and in depth discussed and debugged issue, before claiming it's working for you? Claiming it's working for you when I refered to the well known issue is confusing users, at best. Worst case: reading and beliving your claim will give users a bootloop (imagine a new user thread searches for "updater")... :(
[OnePlus 3 & 3T Cross Device Development] djplus:
Okay.
[OnePlus 3 & 3T Cross Device Development] Phalaea:
I am on build 190801 currently and would like to update to the latest nightly. Is there anything I have to be aware of? I feel like there are some issues currently but I can't bother to read pages and pages of this thread.

Is wifi working correctly?
[OnePlus 3 & 3T Cross Device Development] jakito:
That's not a good philosophy when dealing with your phone...

You should read the pages.
[OnePlus 3 & 3T Cross Device Development] Phalaea:
But a chronological thread for stuff like that is just very inefficient. Reading all the posts since the first of August is a lot of work.
[OnePlus 3 & 3T Cross Device Development] jakito:
True, but if you value your phone, you should still read everything. Otherwise, you may have double the work just to salvage your information.
[OnePlus 3 & 3T Cross Device Development] :
*lol* What an attitude...

Great point of view on efficieny: offload your homework to someone else making an excerpt for you...
[OnePlus 3 & 3T Cross Device Development] Phalaea:
I don't agree with that. I am not at all expecting anybody else to read through all the pages for me. I never said that. But it is very much possible for somebody to know the answer to my question.

I am sure you use libraries for your coding projects as well and don't reinvent the wheel every time. Asking for/accepting help is useful and efficient.

That is the risk in trusting somebody else. That's correct. :)
[OnePlus 3 & 3T Cross Device Development] :
Workaround (flashable zip):

https://xdaforums.com/oneplus-3/one...-nlos-16-0-t3879405/post78433984#post78433984
[OnePlus 3 & 3T Cross Device Development] :
Nor did I! Read my posting again!

You ofload your homework (reading so e pages since August ~ 30-60 minutes), to someone writing an exerpt for you (even someone, who has followed the thread needs ~ 15 - 30 minutes to write up all issues and glitches you may run into).

Interesting enough that you insist on cpunting your time as effort, but not summing it up for you, as long as no additional reading is done.

I don't understand your analogy: if I'm using someone else libs, I read the documentation. I'd never ask the dev of the lib: "The documentation is so large, would you write a summary for me? That's more efficient, because it consumes your time and not mine!"
[OnePlus 3 & 3T Cross Device Development] Phalaea:
Sorry, I misunderstoof your post then! However I was just asking for major issues like the firmware/encryption thing back in July (?) but I did not make that entirely clear. I actually read this thread quite a lot to not mess my system up completely. :)

My analogy to your reading the docs would be to asking if anybody can help me as opposed to reading the entire thread (or for the library analogy: reading the source code). It's not like I am doing no work at all. But it's admittedly not very much. You're right! I just think it is much better to ask for help in cases like this where the "documentation" (the thread) is really inefficient to read.

It would be great if - as soon as an issue gets known - it could be added to a "known issues" list in the first post of this thread. Maybe with a link to the corresponding post so people can make an effort to help resolving the issue. What do you think? It could save a lot of time for people who are just not as interested in contributing or just want a stable system (with more or less frequent updates).
[OnePlus 3 & 3T Cross Device Development] felagund:
How do you check the 5g hotspot band?

I can test with my OP3 and will probably go full reset to oos next weeks and move back to lineage os do I can check there and also on other devices and ROMs.
[OnePlus 3 & 3T Cross Device Development] :
Isn't that the same? In a classic c lib the documentation is in the files ending on ".h". Manpages and info files are generated automatically from the comments in the headers, arn't they? ;) If details matter there's no way around the files ending on ".c".

It has come to my mind, that you treat the knowledge of a human being as a library at your hands. But I've decided to assume you are not that ignorant - now I know better.

Personal note: I don't know of human beings feeling respected and motivated to help, if treated as available knowledge base or lib... ;)

That's a great idea. If you start such a posting, I'm sure [MENTION=5091734]dianlujitao[/MENTION] agrees to move that posting to #2.

All people normaly claiming "I would like to help, but I'm no dev" have the chance to contribute to the community by doing the above - the "you" in the above sentence is not refering to [MENTION=5944791]Phalaea[/MENTION] only!
[OnePlus 3 & 3T Cross Device Development] :
It's over a month now (indeed 33 days). Has anybody expirienced PIS since 0821?

BTW: Has anybody using the "5GHz APs showing up after 30s"-Workaround expirienced any side effects or wifi issues?
[OnePlus 3 & 3T Cross Device Development] Dirk:
Haven't seen any reports anywhere. I don't know if people are still using the fix.zip though, perhaps not realising that they should be testing the native fix.

I've stopped using the fix.zip personally. Only just got a ROM build with the native fix recently on my 3T, so too early to say. No problems yet though. On my OP5 i've probably only rebooted six times since the native fix made it into the ROM. No problems there so far either. On balance i'm pretty positive we've seen the last of PIS.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Yes. Rarely. But it goes away after a few seconds so I didn't really mind. I'm using NLOS as you already know.
[OnePlus 3 & 3T Cross Device Development] :
I always thought the nature of this bug is that the messege is shown for ever, isn't it?

Do you mean: "No, the PIS bug is gone, tje messege shows up and disapears after some seconds."
[OnePlus 3 & 3T Cross Device Development] Dirk:
Yes, it hangs until force reboot.

I'm not sure if we're talking about the same thing.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Ah ok, my bad. I thought the message was the bug and it should not be displayed at all.
[OnePlus 3 & 3T Cross Device Development] realtos:
sorry to butt in but whats the PIS issue? never heard of it and i have zero problems here and been for long time
[OnePlus 3 & 3T Cross Device Development] :
Search before posting, please!

https://xdaforums.com/search/thread/3866517?query=PIS
[OnePlus 3 & 3T Cross Device Development] sky321:
Thank you for commiting the patch

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

Works like charm!
[OnePlus 3 & 3T Cross Device Development] lokeshjt:
I went back to stock OOS after reading about the problems with updating to the Pie firmware and safetynet issues. But I am already missing LOS and thinking of jumping back. I have been reading the thread but I'm not sure if my understanding of the issues is 100% correct, so hoping the more experienced guys can confirm or correct me where required.

As I understand, the firmware upgrade issue happens only when moving from 5.x.x to 9.x.x. If I am already on OOS 9.0.5 there should be no problem in flashing LOS or future updates, right?

For passing safety net (without magisk/custom kernel), is it sufficient to lock the bootloader? Locking bootlader would wipe the phone so i should probably setup my device after locking bootloader. So the steps should be :

1. Unlock Bootloader

2. Flash TWRP latest version

3. Flash LOS and gapps

4. Lock bootloader

5. Reboot and setup device.

As i understand, with latest TWRP OTA updates can't be flashed automatically and must be flashed*manually from twrp. Automatic updates should work on older versions but those don't support locked bootloader. I am okay to give up automatic updates for safetynet without magisk/custom kernel, so I should go with 3.3.1-0. Hope I got that right.

There was some issue with an older version of TWRP where encryption was breaking (3.2.3-1). I am assuming this is not an issue anymore in the latest version (3.3.1.0) ? I didn't find anything explicitly about this so I wanted to confirm or know if I have to take any specific steps.

I didn't find any other major issues while going through the thread but please let me know if there is any other thing i should be aware of...
[OnePlus 3 & 3T Cross Device Development] :
[MENTION=8379211]lokeshjt[/MENTION]

You're good, go ahead
[OnePlus 3 & 3T Cross Device Development] :
Absolutly. If you are on 9.0.5, just stick with it.

I'd lock the bl after flashing twrp, and reboot to twrp once after the bl is locked - just to be sure it's working before proceding.

If data is encypted (just for completeness to avoid false positive reports... ;) ).

Depends... ;) See completeness comment above. ;)

Exactly. As long as you don't format data with 3.2.3-1, you don't need to care about encryption footers.

I think so.

Happy flashing!
[OnePlus 3 & 3T Cross Device Development] LorBer13:
Anyone using Android auto? When I try to connect the smartphone to the car it connects and disconnects continuously. I am sure it’s not a cable problem nor a car problem.
[OnePlus 3 & 3T Cross Device Development] Notor1ouS-:
using it nearly daily and it works perfectly for me.
[OnePlus 3 & 3T Cross Device Development] LorBer13:
Which gapps are you using? Any mods or custom kernels? Usb configs/settings? Which firmware are you using?
[OnePlus 3 & 3T Cross Device Development] Notor1ouS-:
i always flash Pico gapps (from opengapps) at first and get other needed google apps from playstore.

latest LineageOS, stock kernel + magisk root with viper4android module.

firmware latest (9.0.5.)

i didn't change anything else.
[OnePlus 3 & 3T Cross Device Development] :
For your own risc: https://www.cyanogenmods.org/forums/topic/lineageos-17-for-oneplus-3/
[OnePlus 3 & 3T Cross Device Development] mottenkiller:
I am using AA without any issues, too.

Running on 2019-08-29 (fw 9.0.5) with pico opengapps.

Seems like AA is very sensitive to any cable-issues. My old phone reconnected everytime I touched the cable. So if I were you, I would test another (high quality) cable.
[OnePlus 3 & 3T Cross Device Development] LorBer13:
I bought an Anker cable which Is recommended to be used with AA. Dash cable same problem. I returned back to oos and the problem remains the same as Los... I don't know what to do
[OnePlus 3 & 3T Cross Device Development] mottenkiller:
New Anker should work...

Cable length should not exceed 1,8m. (mine is a rampow 1m)

So I don't know the solution, but here are some guesses, what could help, just try:

Do you use the latest AA-Version?

Which usb-mode do you use? I can not test right now, but I think mine is running in data-mode.

Maybe initiating the connection from your car's display helps? Mine isn't connecting otherwise...

There are issues if time of your car and your phone are not in sync.

Since obviously many people are facing problems connecting AA, there is a step-by-step guide on google support:

https://support.google.com/androidauto/thread/2467281

Hopefully you find your solution there. :)
[OnePlus 3 & 3T Cross Device Development] LorBer13:
The cable is an anker powerline 0.9m... I’ve tried all types of connections (even ptp, ecc). It connects intermittently, with both los and oos. The car hasn’t AA by itself but if i connect other phones running it AA appears on the car’s display.