yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] BillGoss:
You don't need to be rooted. Use the file manager in TWRP to copy the init.qcom.rc file to the correct location. That's what I did.
[OnePlus 3 & 3T Cross Device Development] nucleerz:
Ok, this worked fine. Now I've got SIM/IMEI. Thanks again guys!
[OnePlus 3 & 3T Cross Device Development] Osama nisar:
Facing Sim detection issue
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
Read the last pages and you'll understand what you need to do
[OnePlus 3 & 3T Cross Device Development] pcesar.cercal:
Hi, wen you put the next update with sim card fix?
[OnePlus 3 & 3T Cross Device Development] chtitlou:
Golden rule : never ask for ETA.

Besides, Safetynet check failed for me with this build (20191231) compared to the previous one. Applying the patch (editing build.prop) solved it as expected.
[OnePlus 3 & 3T Cross Device Development] knpk13:
I'm having issues with play store notifications not showing up. Do we still have to do this workaround for LOS 17? [MENTION=5083335]SpasilliumNexus[/MENTION]

https://xdaforums.com/oneplus-3/one...ageos-16-0-oneplus-3-3t-t3866517/post78437249

Also I noticed there a lot of "stub" apks that show up in the launcher, unlike in Pie where they got hidden automatically. Nova Launcher Premium, Titanium Backup PRO, or Poweramp Unlocker for example. I'm currently hiding them manually but just wanted to know if that's the expected behavior now.
[OnePlus 3 & 3T Cross Device Development] realtos:
omg look at the post RIGHT ABOVE!!!!!!!!!!!!!!!!!!!!!
[OnePlus 3 & 3T Cross Device Development] chtitlou:
Not sure of what it was on Pie (never seen it) but here I just see silent notifications on my phone. They don't appear in status bar but you can see them when sliding the notification drawer. If you long press on the header of the notification, you can switch it from silent to alert. Then the icons will appear in the status bar as normal.

I have them too, but such "bugs" seem to be ROM related, not device specific. I don't think it's expected, and such issues will disappear when the nighties will be rolling out, just like the battery icon bugs and other minor/cosmetic stuff.
[OnePlus 3 & 3T Cross Device Development] knpk13:
No I don't get any notifications at all from play store even after applying that fix. I get silent notifications from download manager when downloading an app from the store, but no update/install notifications for progress or availability of updates.

Maybe. It might also be the expected behavior for Android 10 (or just Android 10 custom Roms), since the same thing happens on my OnePlus2 with LOS 17.
[OnePlus 3 & 3T Cross Device Development] bfm.95:
it Shows "No Sim card"...

before updating it was working...
[OnePlus 3 & 3T Cross Device Development] sammy9005:
Hi i clean flashed Oxygen os 9.0.6 from stock oreo firmware. I then clean flashed to the 2019.11.20 version of this rom but for some reason when on a call the person I'm speaking to can hear their own voice. I do not have ok Google voice recognition on and this issue was not present when i was using oxygen os. There is also no indication of it being fixed in the latest update or any comments on this thread of anyone also facing the issue ?
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
Known issue, the solution was posted by the dev a few pages before. Please read the last pages before post
[OnePlus 3 & 3T Cross Device Development] xuser_:
1. google pay works?

2. selinux enforcing?
[OnePlus 3 & 3T Cross Device Development] chtitlou:
Come on guys ! Read the thread or use the search box before posting !!!
[OnePlus 3 & 3T Cross Device Development] Viper The Ripper:
TAKEN from OP!!!
[OnePlus 3 & 3T Cross Device Development] bfm.95:
what line exactly???
[OnePlus 3 & 3T Cross Device Development] :
The marked one, of course. (Line 522)
[OnePlus 3 & 3T Cross Device Development] :
it's not wanted:

See the comments to this commit: https://review.lineageos.org/c/LineageOS/android_packages_apps_Settings/+/247884 ; though this is for 16.0, I'm pretty sure that's the reason why it hasn't been ported to 17.1:
[OnePlus 3 & 3T Cross Device Development] bugrahul:
I'd like to confirm that after [MENTION=5091734]dianlujitao[/MENTION] took up Issue #1805 on Gitlab, he was able to get it fixed with the Aug 31st 2020 build. Finally, it is a really good daily driver now. Thanks [MENTION=5091734]dianlujitao[/MENTION]!
[OnePlus 3 & 3T Cross Device Development] knpk13:
The comments said "Besides, check the history of this patch and you will understand why it's not merged."

I couldn't figure out how to check the history (sorry, not that used to Gerrit) and didn't find a reason in the comments of the related patches. Did they give any further reasoning other than that they just don't want it?

P.S I personally wouldn't use it on OP3/T but it should probably still be there as an option like it's on OOS.
[OnePlus 3 & 3T Cross Device Development] :
You tend to make things more complicated then they are. The history of a patch are the patchsets - at the time of the comment you've quoted these are patchsets 1 to 5. Since I don't understand that comment though reviewing every single set, I've quoted Dan's comment, which I understand. The short version is "it's not wanted".
[OnePlus 3 & 3T Cross Device Development] bian_ki:
SIM card not connecting

After upgrading 16.0 to 17.1 I have SIM card connection problem.

Firmware is updated to 9.0.6.

One SIM card works well in both slots.

Others don't work in any slot. They are detected, their name is shown but there's no connection, it doesn't scan for networks and instead of the big choice LTE/WCDMA/TDSCDMA/GSM/EVDO/... (2 screens total) it only shown "Prefer LTE", 3G or 2G.

Is there any way to fix?
[OnePlus 3 & 3T Cross Device Development] rohan164:
+1

I have also faced this

Workarround is, go to flight mode and come back.
[OnePlus 3 & 3T Cross Device Development] Keyvannn:
So there is no problem with Echo right now?
[OnePlus 3 & 3T Cross Device Development] bugrahul:
Maybe but it's not the same issue. Voice quality issues need to be addressed separately. There's a noise cancellation presence in video recording too. Noise cancelling should only happen during voice calls.
[OnePlus 3 & 3T Cross Device Development] gabrielex:
Hello guys, just flashed today this cool ROM on my 3T, had some hiccups at the beginning for the setup that wasn't working at all with full Gapps, then flashed the mini ones and was going in loop but after going back and forth a while I managed to solve.

Haven't tested it extensively, one thing that sort of bugs me is the impossibility to disable a single SIM card, the other thing is that I can't find Netflix in the Play Store, so what I did was to download it from the official website through the APK they provide but it still says it's not supported,

at that point I installed Magisk and enabled Magisk hide, still no luck in finding the Netflix app in the Play Store or running it directly from the downloaded APK, Safetynet checks are green, and in the Play Store the device is marked as certified, any hint?

Bootloader is still unlocked and encryption enabled.

Also I miss the scrolling screenshot feature which was really useful, I know there's an app but I'm not sure to trust it since it requires full permissions.

P.S. Finally I can have dark mode Gmail ;)

Thanks a lot!
[OnePlus 3 & 3T Cross Device Development] :
https://help.netflix.com/en/node/12983

if playstore is certified, it should shows up unless you're on unsupported/restrictied countries
[OnePlus 3 & 3T Cross Device Development] bian_ki:
I feel that battery usage is noticeably more drainy on 17.1 compared to 16.0, I and use all the same apps.
[OnePlus 3 & 3T Cross Device Development] Johannes1098:
When safetynet checks are passing but playstore isn't certified - delete data of playstore app and reboot device..
[OnePlus 3 & 3T Cross Device Development] gabrielex:
Thanks but as I said the device was already marked as certified in the Play Store, what was missing was the second reboot!

I managed to download Netflix from the Play Store now and it's working.
[OnePlus 3 & 3T Cross Device Development] Kurt Krummbein:
I found another problem with my wife's 3T and bluetooth car connection ... when a call comes in, neither the phone nor the car-phone is rinning, i just see the message on the car-display (and the phone ... but usually, this is hidden in a bag ;). Car is a Audi Q5 (2013). I connected my Onyx with the car, called myself and both car-phone and Onyx where ringing. Then i deleted the pairing on car-phone and 3T, repaired them ... no change :(. Can't tell, with which build this started, currently i'm running 20200907 build on the 3T. Any hints?

Greetz

Kurt
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
3 Weeks ago I also clean installed LineageOS 17.1, I came from LOS 16. I had to install 17.1 twice because I locked the bootloader after encrypting the device and it deleted all my data. :eek:

So remember first to lock the bootloader and to encrypt the device later. :cyclops:

Besides that it works quite nice, thanks a lot for your good work, [MENTION=507649]devs[/MENTION]. :good: :highfive:

I am missing the Mac randomisation feature in LOS.

Here is what I mean:

KLICK

Here it how is seems to be implemented:

KLICK
[OnePlus 3 & 3T Cross Device Development] :
Please, search before posting, this topic has been discussed already:

https://xdaforums.com/search/thread/3990061?query=mac randomization

Short story: if the resource you've mentiomed is enabled by the device specific overlay, the mac address is randomozed correctly, but the device is no longer able to connect to any ap.
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
Thanks a lot! I do read here frequently, maybe I've missed that.
[OnePlus 3 & 3T Cross Device Development] brmbjn:
try to install on my oneplus 3t
[OnePlus 3 & 3T Cross Device Development] Phalaea:
Hello guys, does the latest nightly still have the problem of dropping wifi connection? I have searched the forum a little and I only found a workaround of disabling mobile data while connected to wifi. Is this

needed for this rom?
[OnePlus 3 & 3T Cross Device Development] Hemuli:
For me, wifi drops occasionally and reconnects within a couple seconds. Disabling "mobile data always active" from developer options, as I suggested earlier, didn't help me. I haven't tried the methods mentioned by others yet as the problem hasn't bothered me enough.
[OnePlus 3 & 3T Cross Device Development] tim-scrap:
Was never a issue for most people, but you could check LOS changelog what was done on Wifi.

Otherwise the only solution is test the Rom and if you have drops you can post your log that dev could check.
[OnePlus 3 & 3T Cross Device Development] rhaaa:
Hello, I have a related problem. I don't know for the car audio, but LOS17.1's behaviour is inconsistent with my bluetooth headset.

When the headset is not connected, the phone behaves as it is configured and all is well.

When the headset is connected and a call comes in, the behaviour is inconsistent. Sometimes the phone vibrates, and the headset announces the incoming call, but no ring anywhere. Sometimes I have a faint ringer on the phone, but a lot fainter than normal, and no matter what I do I can't have it louder. So for now I just shut down my headset most of the time, otherwise I miss calls, which is bad.

With LOS16 the phone rang, with or without headset, which is the expected behaviour.

Do you need any information to diagnose this problem ?

Thanks,

--

Rémi
[OnePlus 3 & 3T Cross Device Development] gabrielex:
So I'm still test running the lastest nightly build and I'll give some info and try to get some info too:

Useful to know

Before installing:

- disable bootloader lock

- flash TWRP, at that point resize system partition because GApps won't fit if you don't.

- speaking of Gapps get the mini ones or smaller, the other ones are bugged or anyway won't work, get them from https://opengapps.org/

- if you're planning to re-lock the bootloader DO NOT encrypt your phone (this is the mistake I made, so now I'll keep my phone encrypted with bootloader unlocked as I don't want to re-sync and download all the apps again).

After installing:

If you plan on using Netflix and banking apps with unlocked bootloader you should get Magisk and Magisk Hide, once enabled delete cache and storage from the Play Store app and reboot.

What I've found myself missing:

- I can't install the official OnePlus apps from the Play Store anymore, they are marked as not compatible.

- I really miss the scrolling screenshot feature.

- Also I miss the alarm clock auto turn on feature of the official OnePlus clock and the possibility to set an alarm for a set date so I can turn off the phone and be sure it will ring let's say at 4:00am on Sept 22.

I've tried getting the OnePlus clock APK from apkmirror but it force closes.

- If you're using 2 SIM cards you can't disable one of them as you could do before, which is EXTREMELY useful if you're traveling, so now you're forced to physically remove the SIM from the phone, quite annoying.

Besides this, if I'm not forgetting anything ,the ROM runs pretty smoothly and didn't have any major issue yet, but really wish I could solve the points above.

P.S. For some reason before flashing the ROM I could use the OTG feature of TWRP, now it just won't detect or mount any OTG storage devices while inside the recovery.
[OnePlus 3 & 3T Cross Device Development] WilliamConnor:
OnePlus 3t always boots into TWRP after installing GApps

Hi there!

I wanted to set up my OP3T today with LOS 17.1 coming from another CustomRom and test its capabilities with Google's Family Link for my son.

What I did was:

- I updated TWRP to 3.4.00.

- I wiped everything (Dalvik, cache, data, Internal storage, system)

- I downloaded the latest nightly built lineage-17.1-20200914-nightly-oneplus3-signed.zip and copied it to the device

- I downloaded the latest Gapps pico (and mini) (ARM64/Android 10) and copied it to the device

- I copied them both to the root folder

- I executed the install (first together and then seperately), was done without any problems.

- I wiped Dalvik and cache

- Rebooted system.

What happens now is: instead of booting to the system, it starts with the green LOS logo and after some time it reboots and starts TWRP again.

BTW, when I only install LOS 17.1. the systems comes up and everything works. Only if I add GApps to the mix (pico or mini) this behaviour start.

Any suggestions? :)
[OnePlus 3 & 3T Cross Device Development] knpk13:
As you can probably figure out, it's a gapps bug. Already reported and fixed in the gapps thread. Use a newer or older gapps package. And next time mention the exact date of the package you flash, not just "latest". I'm assuming you flashed a buggy one as mentioned in this link. Read the last few posts in the thread for more info.

https://xdaforums.com/android/software/pa-gapps-continuation-t3098071/post83537311
[OnePlus 3 & 3T Cross Device Development] WilliamConnor:
Thanks mate! Wasn't aware that that could happen. Used arm64-10.0 build 20200919. :) Will try again!
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
Don't forget to lock the Bootloader via fastboot!
[OnePlus 3 & 3T Cross Device Development] WilliamConnor:
Thanks, is there a manual how to do that? I thought that would make the phone go back to OnePlus OS?
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
No, of course that won't!

Boot to TWRP, as you know how that works. Then reboot from within TWRP to "fastboot".

Connect the phone to your PC run, for example, Minimal ADB and Fastboot and type:

fastboot oem lock

Note: When you have encrypted your phone before, you'll lose all Data. If not, feel free to go.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Why do you want to lock your bootloader? It has nothing to do with your issue of buggy gapps. And no, relocking does not flash the stock OOS rom.

Edit: Relocking will make flashing harder in the future, and whether you can flash/run a custom rom with a locked bootloader depends on the device. In case you find a reason to lock your bootloader, search this thread for instructions and device specific bootloader related discussion.

Be extra careful when reading instructions related to bootloader stuff to avoid any data loss or bricking. You don't need to lock your bootloader to use gapps. The only real reasons to relock are some amount of security and passing safetynet, and both are possible on an unlocked bootloader as well with different methods.
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
No.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Yes, it restricts what you can do with fastboot. TWRP not as much. Btw relocking on newer devices with a custom rom is a lot trickier because of increased bootloader security. It's safer to stick to an unlocked bootloader in general (especially with devices from brands not as dev friendly as OnePlus) when dealing with custom ROMs.
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
No.

In this thread we're talking about this single device. TWRP and LineageOS are signed, Magisk signs, too. So there's no reason to leave it open und nothing is harder to fastboot with, when it's locked.
[OnePlus 3 & 3T Cross Device Development] :
i.e.

fastboot boot filename_of_bootimage

will not work anymore.

YMMV if you consider booting a file via fastboot usefull or not - but this feature is no longer available with a locked bootloader, as well as flashing recoveries via fastboot. Both features are disabled by purpose with a locked bootloader for security measures.
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
That is true and extremely wanted, or not?
[OnePlus 3 & 3T Cross Device Development] :
As stated: YMMV

I think when testing kernels and twrp versions (especially to check if a backup from one version is restoreable on another bersion) "fastboot boot" saved me roughly 2h of lifetime. Additionally: as long as the installed recovery allows to flash boot images and recovery images from otg or sideload, locking the bootloader does not add more security.

Considering this my answer for me is "no, it's not wanted at all." On the other hand: if you don't use "fastboot boot" at all (and "fastboot flash" only once when installing twrp), relocking the bl is the easiest way to pass safetynet api.
[OnePlus 3 & 3T Cross Device Development] Celphor:
Voice messages (Whatsapp, Threema)

I still have problems with the microphone. Phone calls and Whatsapp calls are ok, but I have empty recordings when recording voice messages in Whatsapp or Threema. I can only record using my BT Headset, but not with the builtin mic. No error, nothing, only silent recordings. Anyone else experiencing this or any tips? I am on the latest nightly. It stopped working maybe around 6 weeks before and it already worked on 17.1

"Ok Google" is also not working, I already tried to switch it off/on
[OnePlus 3 & 3T Cross Device Development] gabrielex:
Hello,

did anyone manage to make Oneplus clock app work on this ROM?

I really need the scheduled alarm and switch on from off state features.

The APK I got from APK mirror force closes.

Thanks
[OnePlus 3 & 3T Cross Device Development] not_su:
I have a mid-August release of this ROM installed. It was working fine until this morning. This morning when first trying to login into my phone, pressing the fingerprint sensor resulted in the phone prompting me to enter my password for additional security. I entered my password and after a momentary blank screen, it returned to the lockscreen. The same thing keeps happening each time. Just to be clear, I am entering the correct password - it does not say "wrong password" when I enter it, and when I deliberately enter the wrong password, it just says that and doesn't blank out the screen then return me to the lockscreen.

The other problem with this situation is that I can't reboot the phone or boot into recovery, as I've installed security software (Cerberus) that prevents the phone from being shut down or rebooted unless it's unlocked.

I'm at a bit of a loss as to how to address this. Any suggestions would be most appreciated.
[OnePlus 3 & 3T Cross Device Development] christantoan:
Do you have EdXposed installed? If you have, try disabling it temporarily through TWRP (you'll need Magisk Manager for Recovery Mode flashed first). Otherwise try rebooting.

You can always restart the phone by holding the power button for a while.
[OnePlus 3 & 3T Cross Device Development] mrplowdan:
Try holding the power button for a full minute. I'm pretty sure that will cause almost all phones, that don't have a user replaceable battery, to reboot the phone at the hardware level.
[OnePlus 3 & 3T Cross Device Development] Saamyo:
Guys for some reason I'm not passing Safetynet on a fresh install. Could it be due to the GApps I used? I used OpenGApps nano.

Edit: To clarify, by not passing Safetynet I mean ctsProfile: false, but basicIntegrity: true.
[OnePlus 3 & 3T Cross Device Development] :
What's the status of the bootloader? If it's unlocked, you need either a patched kernel or magisk. If it's locked, I don't know. It's not gapps related.
[OnePlus 3 & 3T Cross Device Development] Saamyo:
It's unlocked :D

I'm sorry but I wasn't aware of needing a patched kernel to pass Safetynet (I'm returning to Lineage after a long long time and most other ROMs seem to pass Safetynet with the stock kernel). Anway, thank you so much for the input :)
[OnePlus 3 & 3T Cross Device Development] :
Please search and read the thread!!! This has been discussed many times in this thread.

Read my posting again.

I've never said you need a patched kernel!!! I clearly stated that you need a locked bl OR magisk OR a patched kernel. Any rom, that passes safetynet api out of the box with an unlocked bl drops the tripped verity bit on kernel level - otherwisse safetynet api will fail.
[OnePlus 3 & 3T Cross Device Development] tyler19820201:
I have got so many issue with the last LineageOS. Got fed up and swap havoc. My life is hassle-free now. I am wondering when will come up Lineage with Android11 on OP3T...as i am already using it on OP3T:good:
[OnePlus 3 & 3T Cross Device Development] bian_ki:
I'm having this weird problem with GPS.

If I insert a second SIM and switch mobile data to second SIM, GPS stops working at all — GPS Test doesn't detect any satellites.

Switching mobile data to first SIM fixes GPS again...

I have this modem firmware flashed, if it's relevant: oxygenos-9.0.6-no-alipay-firmware-3T.zip (47.2 MiB)
[OnePlus 3 & 3T Cross Device Development] rhaaa:
Hello, there are quite a few audio bluetooth related problems in this thread, but they hardly ever get any answer. Is there something that we need to do to help diagnose those problems ?

Thanks

--

Rémi
[OnePlus 3 & 3T Cross Device Development] WilliamConnor:
I did all the above and I got an OKAY after executing the command and selected yes afterwards and rebooted. Yet the unlocked screen in the boot section is still there stating that the bootloader is still unlocked?
[OnePlus 3 & 3T Cross Device Development] Not-Aus:
Yes, it is still unlocked.

It is a bug within the firmware. You need to select "No" for locking it.
[OnePlus 3 & 3T Cross Device Development] WilliamConnor:
Wow!! That's the weirdest bug I've ever seen!! But thanks!!! It did the trick!! Only problem now is my PIN and Fingerprint is not working anymore and I can't unlock my device.... I had to set it up from scratch again but ok now!
[OnePlus 3 & 3T Cross Device Development] :
I suggest you take your time to read this thread. It has many usefull information. As well for the well known bootloader bug as for the lockscreen issue. For the latter see https://xdaforums.com/showpost.php?p=82299329&postcount=877