yashsingh1/xdaforums huggingface dataset:
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] aniruddhavispute:
I developed 'Can't open camera issues' on LineageOS 18.1. None of the apps could open the camera, tried restarting, app data clear, none of it helped. So I updated the os to latest 18.1 with a dirty flash, then to Lineage OS 19 with a dirty flash, the problem was still there. Then I did a clean flash and the problem is still there. Can anyone help? Also, miss the customization bits on os19.

EDIT - Another bug that I noticed is, I'm not getting Call notifications, the phone rings, but the call screen doesn't show up. I then need to wait for call to stop ringing, then open call log, and then redial.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] madman:
Someone earlier in this thread had issues with camera and after doing a clean flash of OOS11 it was declared to be a hardware issue. If your issue just happened randomly on 18.1, it smells a lot like a hardware issue to me. You can read up the conversation that I had with the person and see if you can do something similar? If it doesn't work on OOS, there is nothing anyone here can do.

https://xdaforums.com/t/rom-official-enchilada-12-lineageos-19.4437321/post-86939021
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] CYB3R0ID694:
Nope.. Not Hardware Issue...

If things working on other ROM & not working in one, Problem lies in that one ROM..

Mostly ROM, DT, Vendor & DT need more patches..

OOS Cam working fine in Syberia ROM which means OOS CAM is fine.. It's just Other ROM missing same patches..

If cam is not working even in Stock OOS, then you can say it's Hardware issue. If it's not working in Custom ROM only, Then it's custom ROM issue(mostly DT & Kernel)..
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Tonip77:
On today's build nfc doesn't work for me. It keeps crashing while reading a tag (phone reboots after some time). Is someone else having the same issue?
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] CYB3R0ID694:
So many Sepolicy denials..
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] gamertag128:
Does somebody know, why todays update got revoked?
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] risheek7:
I have installed it and not facing any issues
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
Build was pulled due to the NFC service crashing when reading a tag after the changes in the June 2022 ASB (which @Tonip77 has encountered above). It has since been fixed and a new build has been released with the fix.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] [GER]Roxxor:
Ahh. And it als disables the clipboard listener. Thats great! I think this ROM is almost again flawless.

Only thing that is missing for me is: On previous versions (LOS 18.1 also took some time to get it, but it happened eventually) you could simply click on the time when the quick settings are open, to open the "clock" app. Someboday knows where the patch is on gerrit? :D cant find it...
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] olifee:
I'm a bit confused as on what is listed on LineageOS log — does this not indicate that the build was done at 2022-06-15 00:00 but the fix was merged only later (https://review.lineageos.org/332732), or is this a display issue on LineageOS log only?
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] [GER]Roxxor:
I think it's a display bug in the log. It's included. I don't get the clipboard thing anymore. And the patch is in the "not yet" included change.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] jabashque:
lineageoslog.com makes some really dumb assumptions about build times; it assumes that each build was started at precisely 12 AM UTC-0, when that's not correct at all.

Though... the official changelog seems to make the same kind of error too, so... I don't know. I do know for sure that the 2022-06-15 build was manually triggered after the fix was merged in.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Forage:
The official 19 builds have been working nicely from the start. Thank you for your efforts to keep supporting this phone.

There have been two issues that remain present though. LOS 18 did not have them.

1. The colour assigned to the SIM card in the settings doesn't get applied elsewhere. Especially with dual SIMs it makes it harder to distinguish them because both are grey when booting the phone and you get asked to enter the PIN code or when sending SMS messages (default SMS app) and you select the card to use (long press on send button).

2. In the "Calls and SMS" settings you can specify the default SIM to use for SMS messages. If you set it to "Ask every time" you will get an error when trying to send an SMS stating "No preferred SIM selected for sending SMS messages". It does work for calls though.

While the first one is not the end of the world, the second one makes it too easy to send messages with the wrong SIM as you are forced to set a default one.

Do any of you have the same issue?

Is it phone, Android 12 or app related?

Build: 19.1-20220607

Custom kernel: no

Xposed: no

Gapps: MicroG
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] olifee:
Thanks to both of you! I can confirm the new build works perfectly well, scanning tags works, and the annoying message is gone :-).
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] webtroter:
Hi

There's a setting I'm not finding.

Is it a wider lineage os problem, just this port, or something else?

To turn on this setting: Go to Settings Settings. Tap Connected devices and then Connection preferences and then NFC. Turn on Require device unlock for NFC.

Verify it’s you to make a purchase - Google Wallet Help

To make payments with Google Wallet, you must have a screen lock set up on your device and verify it’s you for your security. You can verify it's you in Google Wallet with several methods: PIN

support.google.com

Thank you.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] danc.940:
Hi, I have done a dirty flash from LOS 18.1 and everything went smoothly. Last week I installed one of the updates trying to keep magisk but rather than reboot with magisk I rebooted with the updater. Magisk has still been installed however the phone is a bit laggy now mainly when I use quick switch and lawnchair.

Could you please advise on how to update LOS while keeping magisk installed? Do you think I should try to reinstall magisk at this point? Thanks
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Forage:
As of Magisk 24.2 you don't need to bother to do anything special any more. Perform the LOS update using the updater and Magisk will remain present after reboot.

If you performed the LOS update with an older version of Magisk and you did not go to the app to install itself on the inactive slot just before reboot you'd need to install it manually again as you did the first time (sideloading the modified kernel or the app).
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] danc.940:
Thanks. I run magisk 24.3. Can I safely proceed with a normal update from the updater?
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Forage:
I just told you...
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] danc.940:
right sorry, I just wanted to be sure it applies also to the latest magisk. Thanks again :)
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] LautaroSicco:
Thank you very much for this excellent ROM!

Everything works very well, except for a problem that I am having with the GPS icon. It activates every 5 seconds without stopping and it's annoying. Do you know if this is a bug or an option that I can change?

From already thank you very much!
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] bre75:
Hi,

Since the last update (LineageOS for microG June 9 build) I have regular " 'Intent Filter Verification Service keeps stopping'" message popping up.

Any idea what it can be ?

I have a second question.

I'm actually using Bromite SystemWebview.

But does anyone knows if it's possible to install Mulch outside of DivestOS ?

Thanks for your answers.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] EGM92:
Just curious if this is a bug, is normal, or if there's a fix. Some of my apps that can use the finger print reader like one of my 2 banking apps, the app for my security cameras and a few other when enabling the fingerprint reader to login to said apps they crash/force close. For example I have 2 banking apps, one is Simplii the other Scotiabank (Canadian banks). Simplii I can setup logging in with biometrics but Scotiabank will crash instantly. Is this normal? can it be fixed?
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] raghavcinch:
Everything has been working great including Android Work Profile, however the banking apps doesn't work... Watsapp reported this as custom rom, but it worked fine.. but the banking apps (hdfc, payzap, citi) jus won't start - they would simply say this is a rooted device. Gpay worked though.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] EGM92:
you need to install magisk, flash a patched boot.img, add banking apps / google pay etc to the Denylist. As well as installing the Universal Safetynet fix.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] absinth:
Hi guys i have in my op6 a6000 the official 10.3.12 with root and i want to pass to this ROM, what is che procedure to passing keeping the root?

thanks
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] [GER]Roxxor:
Click on the icon/pull down notification area and click on the icon. See which app is accessing your location all the time, remove it. Or in case you are not on the latest build: Update.

Update to the newest OOS (https://www.oneplus.com/global/support/softwareupgrade/details?code=PM1574156173727). Install according to the installation isntruction. Install Magisk. Those are all the words you need. If questions, ask google. All your questions were asked a million times. You will lose all your data, backup.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] chemicalrage:
Installed

* lineage-19.1-20220615-recovery-enchilada.img

* copy-partitions-20210323_1922.zip

* lineage-19.1-20220615-nightly-enchilada-signed.zip

* MindTheGapps-12.1.0-arm64-20220605_112439.zip

* ih8sn-aarch64.zip

So far everything is working except the camera. It is slow and pathetic and gets stuck/hangs when taking a picture.

2 questions:

* I installed Google Camera from https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera as a workaround. What are you guys using for the Camera or suggest using?

* What are the steps to revert back to stock ROM if I want to sell the device? I have this firmware downloaded - https://www.oneplus.in/support/softwareupgrade/details?code=PM1574156173727 Can I just flash it in lineage recovery? 2 times for A & B slots and then lock bootloader?

PS: Thank you so much to all the developers for supporting our EOL device! :D
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] absinth:
the question is whether I can perform this procedure directly with the bootloader unlocked and with the root of the phone or if I have to carry out some other procedure first... thank you
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Spaceoid:
Regarding your GCam question:

Google Camera for the OnePlus 6/6T

Versions of Google Camera compatible with the OnePlus 6 and 6T. Google Pixel Camera for OP6/6T.

www.celsoazevedo.com

I use this one, with the advices regarding the configuarion file. Works kinda good. I am happy.

In the LOS 18.1 thread other mods of GCam are mentioned, too. I have no experience with those, though.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] HeadQuaker:
Hello, I don't understand what I did . (I have already flashed plenty of mobile)

I've followed the guide to install Lineage etc etc but when i have flashed the rom, my phone rebooted, the recovery was the lineage one and not TWRP, I was unable to transfert anything on the phone (.zip for twrp etc). It seems that everything I did (TWRP install, the initial backup, etc) has disapeared.

when I boot on the lineage rom, plenty of things were bugged (unable to do file tranfert, unable to access storage, etc etc)

Any idea.

Maybe there is something about the Slot A & B
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] lm089:
There are plenbty of explanations in this thread here on how to do a first setup of LOS. It always boils down to these steps:

a) make sure your phone is having a reliable adb and fastboot access from the PC of your choice

b make sure you have latest OOS firmware on both slots

c) follow basic instructions including flashing LOS recovery then LOS itself (to both slots)

d) flash some suitable GAPPS solutoin if you want to go that way

Once you're finished doing basic setup of your phone you may want to go on installing TWRP as recovery solution if you feel like it. Not officially supported but useable; again you'll find some detailed instructions in this thread on how to get there

Good luck
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] lm089:
your bootloader won't be locked just by flashing a different ROM, at least I never heard of it.

Root is a different thing: after flashing this ROM you will start unrooted. You then will have to install Magisk to get root access, if you wish so.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] HeadQuaker:
I've done all those points... It seems that Lineage has some issues with the last OOS & TWRP?
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] lm089:
not on my side: OOS 11.1.2.2 + TWRP 3.6.1_11-0-enchilada.

Which OOS did you flash?

Are you able to do a basic system setup using latest LOS build?

How did you then proceed to get TWRP onto your phone?
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] madman:
I'm having a lot of issues on LOS19 related to notifications just not arriving until I open apps. This is happening across different apps as well so I can't really blame the apps themselves. I wonder if something has changed in Android 12. I don't get notifications from Signal, Whatsapp, Duo until I open the apps. I never had such problem on LOS18.1 with same apps (I upgraded from 18 to 19 and barely have installed additional apps). Yes, I have changed power settings for the said apps to be unrestricted from balanced. I know there was some issue that needed sideload of gapps again (the calender sync). I never did that. I wonder if notifications for the apps is related to this as well as its based of GMS as well.

Edit: I re-flased latest MTG, that fixed the calender sync issues and I think it also helped with notification issues (unless this is just a placebo?)
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] HeadQuaker:
the last one available 11.1.2.2

Hum maybe i did not do the sideload of the partition well, will retry.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Spaceoid:
Is anyone here experiencing SLIGHT problems with the MTP connection to the computer?

I like to copy folders with mp3s (music albums) to my phone. While copying, regularily my windows explorer crashes (that is, the explorer window of my phone storage just closes. The explorer does not crash completely). The copying process continues though. But, sometimes, my folders then will end up in the root path of the internal storage, not the path I have chosen.

No idea what causes this behavious. I also did not find anything with Google. I posted a thread here on XDA, but no fruitful help there either.

I have latest Win10 with all driver updates, latest LOS, latest OOS... :D
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] CrysisLTU:
MTP has been a broken mess on Windows for years. I switched to using FTP ages ago - with 5GHz WiFi it can be faster than USB 2.0 speeds anyway, and no wires!
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Spaceoid:
I will Google that, sounds good. Thanks for the input!
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Spaceoid:
So, I just tried this out with the latest OTA of today.

Just downloaded and installed the OTA through the system updater without doing anything special with Magisk. I am on Magisk 25.1.

As I kinda expected, I now lost root after reboot and need to reinstall Magisk. The manager is still present, ofc. I repacked my manager under a different name, so idk if that might have been an error on my side, but based on my experiences I think it is still necessary to install Magisk manually to inactive slot with every OTA. This is also still the official way of doing an OTA, according to the Magisk website.

Edit: This might sound a little salty. It is not intended in that way. Maybe the mistake is on my side, too. I just wanted to share my experience.

Edit2: Now I cannot reinstall Magisk, as the phone will not boot after I fastboot-flashed the patched boot image from Magisk. The sadness.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Forage:
In my case, after performing an OTA and before rebooting, Magisk does no longer even present me with the option to install to an inactive slot but after the reboot Magisk is still there as it should. Also, the website no longer talks about the manual procedure for OTAs as it did before.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Spaceoid:
Oh wow, okay. This is super weird.

I cannot even re-install Magisk now. After patching the boot.img and installing it through fastboot, my phone will not boot anymore. It is stuck on the "bootloader unlocked" warning screen. Any idea what I could do?

Edit: I sideloaded the manager app renaming it to "uninstall.zip", but instead of completely uninstalling Magisk, it properly re-installed it. Everything seems fine now.

I am interested, though, in to why I need to still install Magisk to inactive slot after every update. What am I doing wrong? Maybe it is a problem that I always have my Manager repacked under a different name?

Edit2: I did never patch my vbmeta partition, as this was stated optional in the installation instructions. Maybe that is the problem I lose root on every OTA without manually installing it to inactive slot?
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] madman:
I updated to today's build and everything went just fine on my side. I have Magisk 24.x installed (and renamed the app to different to hide it from other apps). I have never had issues with OTA not preserving root for me. I have LOS19 (with LOS recovery) + MTG + Magisk and OTA updates work just fine.

PSA: If some OTA is dead stuck, you can revert back to old slot from fastboot.

https://www.reddit.com/r/LineageOS/comments/s6ca3y
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Forage:
Just to verify: did you manually install Magisk to the inactive slot between the OTA update and reboot by using the Magisk app or did you simply reboot right after the OTA update?
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] madman:
Nope. Received OTA update, installed it and rebooted. No manual action or reflash of Magisk of any kind in between. That has been the case for me since LOS18 (which was first install on my enchilada).
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Spaceoid:
That is what I am trying to achieve now, too. But after OTA without any additional steps I seem to lose root. Which is not a problem per se, because there is the inactive-slot-installation workaround, but like that it would be much more comfortable.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] lm089:
The option to install to inactive slot is still there on my side (just updated LOS, Magisk 25.1). Strange that there are so many variations...
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Forage:
I still do have the option to do so, just not in between the OTA and reboot. Could it be related to the modules installed or the presence of Gapps? I'm on MicroG with only the modules AuroraServices, MagiskHide Props Config, Shamiko and Universal SafetyNet Fix.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Spaceoid:
No idea actually. I also asked in the general Magisk thread on XDA, but no answer yet. I am on MindTheGapps, only Universal SafetyNet Fix (and ACC) as modules installed.

How did you install Magisk for the very first time? Just by installing the manager.apk, then patching and fastboot-flashing boot.img?
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] madman:
I personally installed Magisk through adb sideload Magisk-24.x.apk . I know this is deprecated method but it still worked fine for me at the time.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] lm089:
Different topic, probably not quite the right thread, but I'll try anyways, as I think I might have f*** up big. Here's what happened (I know, I shouldn't have started all this in the first place, but I did...):

Before I had updated this morning I had removed the security pattern then created a full NANDROID through TWRP.

after successfully installing today's OTA I decided to give MindTheGapps a try NikGapps because of that location indicator flaw. Uninstalled Nik, flashed MTG, which worked fine. But then realized MTG had installed quite a few modules I didn't want and that constantly bugged me to be updated (OK Google and others). So I decided to simply go back to TWRP and restore my backup. Done that before so I felt safe. Not this time though:

after having restored I clicked "reboot to system" which booted twice and sent me back to TWRP. But unfortunately now my entire /sdcard is encrypted!

Switching slots, rebooting to TWRP, whatever did not help.

Next I started ADB sideload from TWRP then flashed latest LOS19.1.

Tried to reboot which appeared to work but it only got me to a never-ending LOS boot animation

I can boot into bootloader or into LOS recovery. I also can temp boot TWRP, but I cannot access my data.

Before I take the pain wiping everything and reinstalling: anyone having an idea what I could do to get out of this situation, or at least how I could recover my data?

UPDATE: phiooo - at least I could get TWRP to have unencrypted access to my data, so at least I now should be able to backup everything I need to my PC...
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Forage:
Yeah, I used the recommended way by having the app patch boot.img, followed by flashing it.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] olifee:
The problem is discussed here:

Nothing installed in Lineage /system/addon.d/ via Magisk app Direct Install + fix_env · Issue #3820 · topjohnwu/Magisk

I installed Magisk by using the "patch boot.img and flash with fastboot" method, since the installation instructions say that using the installer zip via a custom recovery is no longer recommended....

github.com

In short, when installed via the recommended method, Magisk will not survive OTAs. This appears to be by design by the developer, see this comment:

Nothing installed in Lineage /system/addon.d/ via Magisk app Direct Install + fix_env · Issue #3820 · topjohnwu/Magisk

I installed Magisk by using the "patch boot.img and flash with fastboot" method, since the installation instructions say that using the installer zip via a custom recovery is no longer recommended....

github.com

The old, unsupported approach (sideloading the .zip) still installs the retention script. That's also how I installed, and retention during OTAs is also still working for me, but that seems not officially supported anymore.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] Spaceoid:
This makes SO much sense now. Thank you!!!

Still super weird that after OTA I was not able to re-install Magisk again through the boot.img method (phone would get stuck in bootloader warning screen upon boot). Now idea what happened there. Maybe somebody here has a clever idea? XD

I now have Magisk installed through the sideload method and everything works, so let's hope it is still some time till the retention skript breaks.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] CrysisLTU:
Can confirm Magisk stayed after just installing OTA and not doing anything in Magisk Manager. I did originally install via adb sideload.
[OnePlus 6 ROMs, Kernels, Recoveries, & Other Devel] EGM92:
I'm new to OP6 roms and magisk. Do other roms normally remove Magisk when installing OTA updates?