yashsingh1/xdaforums huggingface dataset:
[OnePlus 11] Greatness_GH:
Nice ROM. Very stable and usable as a daily driver. Thanks to the Team and more importantly, the maintainer. I hope the outstanding bugs/issues (auto brightness, vibration, battery life) get sorted soon. I love it
[OnePlus 11] DragoWing:
Is it even worth it to use LineageOS? Since their kernels are banned? Can it still use Google stuff?
[OnePlus 11] bgcngm:
You're just misinformed.
[OnePlus 11] DragoWing:
I used to love LineageOS since it was CyanogenMod, but I saw an XDA post about banned kernels? Lineage and some other popular roms are on it, also wonder about battery sot tho, 😅

I have found this list, I'm not entirely understanding what it means or meant so I was just assuming basically

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/page-518#post-89308909
[OnePlus 11] Vvk380:
If ur kernel has name string out of given list then u might have problems pass integrity.
[OnePlus 11] forever_lol:
Unfortunately it didn't work either. I extracted init_boot from latest stock, patched it in kernelsu manager app and flashed in bootloader., no effect at all, "not installed" as usual.
[OnePlus 11] DragoWing:
Hmmm, you flashed the new kernelsu image to the init_boot partition?
[OnePlus 11] forever_lol:
I

I guess so:
[OnePlus 11] DragoWing:
You flashed kernelsu_patched_20240520_194211.img to the init_boot partition?
[OnePlus 11] forever_lol:
That is correct. For some reason it didn't do the trick.
[OnePlus 11] DragoWing:
Through fastboot? Fastboot flash init_boot kernelsu_patched_20240520_194211.img? That's so weird, it should've worked tho, what device do u use?
[OnePlus 11] forever_lol:
I agree it's weird :) I use EU version.

EDIT. I've just tried this method on latest stock 14.0.0.701 and it works like a charm. I cannot olny make it work on LOS for some reason. kernel version I chose was android 13-5.15 (just like on stock)
[OnePlus 11] DragoWing:
Ohhh, maybe it doesn't work on LOS, I never tried LOS cuz I thought kernels was on van list, I'm on stock now too, but my game center notifications and passkeys doesnt work
[OnePlus 11] MrSteelX:
Why not try apatch on los. It basically works just like kernelsu
[OnePlus 11] forever_lol:
i couldn't make it work either. Perhaps I was doing sth wrong, but I couldn't even patch a boot.img. Everytime I tried to do it I was getting some "error unable to patch boot.img" in apatch app.
[OnePlus 11] MrSteelX:
Can you upload your current boot.img and let me try patching it.
[OnePlus 11] forever_lol:
sure and thank you for your help!
[OnePlus 11] MrSteelX:
Here you go. It patch for me. Abcd1234 is the password. When you patch it. The password must at least be 8 characters with letters and numbers.
[OnePlus 11] DragoWing:
Apatch is also a good one but nog quite there yet, I still prefer kernelsu myself, I used it when LKM wasn't an option yet, but glad I can use it now, haha, XD
[OnePlus 11] forever_lol:
Thank you very much! I'll gove it a try.
[OnePlus 11] lukebukowiec:
Can anyone confirm if 80W fast charge still works with this ROM?
[OnePlus 11] R1ghtC:
It is
[OnePlus 11] R1ghtC:
Been using this ROM for a week, works very stable, but battery life is about 4-5 hours, screen consumes a lot even at <15% brightness. Hopefully this will be fixed soon.
[OnePlus 11] R1ghtC:
Also I think the vibrator configuration is imported from the stock firmware but not used in the build, is this true?

https://review.lineageos.org/c/LineageOS/android_device_oneplus_salami/+/366906
[OnePlus 11] bgcngm:
What do you mean with "not used in the build"?
[OnePlus 11] R1ghtC:
Maybe I don't understand how soong works, but I can't find where VibrationEffectConfig.h is included in the build process.

https://github.com/LineageOS/androi...2407261c37669a60c1027d64d7/BoardConfig.mk#L27

https://github.com/LineageOS/android_hardware_oplus/commit/478f00f3370995dee35503fc509d15de7f28cbcc

Looks like SOONG_CONFIG_OPLUS_LINEAGE_VIBRATOR_HAL_INCLUDE_DIR need to be used
[OnePlus 11] cabagekiller:
I am trying to get root with KernelSU but when I patched init_boot and flashed it, it didn't work. anyone else have this issue? Trying kernelSU out some on my OP11. thank you for the help
[OnePlus 11] R1ghtC:
Use APatch
[OnePlus 11] EtherealRemnant:
Sucks that eSIM is still a problem for custom ROMs. I want to ditch OOS on my 12R because I'm annoyed with how hard they throttle games at 37C with the stock software but I don't want to be forced to use dual pSIM forever...
[OnePlus 11] theo72:
For those who use this ROM, Brightness control has been implemented?
[OnePlus 11] xty_:
I'm on the latest build (21-20240607-NIGHTLY-salami) with my CN variant (PHB110) and noticed my Bluetooth headphones aren't working: they can connect just fine but have no sound when playing media. Also tested were

Connecting and using a Magic Trackpad via Bluetooth

Bluetooth file transfer

In either case, it works without any problems.

Additional information that could come in handy:

Headphones in question: Jabra Elite 7 Pro with up-to-date firmware (2.2.0 (1033))

Baseband version: Q_V1_P14

Kernel version: 5.15.149-gcf9863dbdbf6 #1 Fri Jun 7 04:28:32 UTC 2024

@bgcngm Let me known if there is anything you need from me in order to pin down the issue.
[OnePlus 11] Skippyjan:
This is a known issue. Some headsets work with AAC audio otherwise in developer settings switch Bluetooth codec to sbc, audio should work then.
[OnePlus 11] xty_:
Thank you so much! I was indeed able to get around it by manually switching to SBC. This seems somewhat quirky though as my headphones do support AAC.
[OnePlus 11] ewong3:
issue accessing fastboot...

after PHB110 update over OTA, inadvertantly rebooted, resulting in the frozen animation issue mentioned further up the thread. But upon entering fastbootd from recovery, 'fastboot devices' is not showing the phone anymore on windows command prompt...

UPDATE: phone not recognised by windows, so this driver installation fixed it:

fastboot cannot recognize device but adb can

usb debugging is enabled on device. running latest version of adb, fastboot. Have tried on both mac and win10 but same issue on both. Oneplus 7 pro is running 10.3.0GM21AA >fastboot devices >adb devices List of devices attached 966c8016...

xdaforums.com
[OnePlus 11] b1czu:
Info about salami | LineageOS Wiki

wiki.lineageos.org

What the...
[OnePlus 11] R1ghtC:
Builds paused due to QPR3 release
[OnePlus 11] wkv2101:
Will builds be coming back soon? Is this the end?
[OnePlus 11] bgcngm:
QRP3 broke camera on every OnePlus device based on sm8450+. Builds will be back as soon as camera is fixed. So, don't worry, I am still alive.
[OnePlus 11] forever_lol:
We love you!
[OnePlus 11] wkv2101:
I agree with forever_lol!!! Thank you!
[OnePlus 11] enunna:
Thank you! Where do we find information on when a fix will be released? I'm pretty ignorant of the situation, would that be QPR4?
[OnePlus 11] enunna:
Is there anything I can do to help address this? A link to a particular bug report? I've gotten lineage building on my machine so could conceivably help debug.
[OnePlus 11] TheSayaMan:
Being a developer myself, the issue lies inside the Linux machine at vendor/qti & qcom. I haven't been able to figure it out myself. I tried making several changes there, to no avail so far. Nameless dev figured it out because the camera on his ROM works but most devs will ignore messages so it would be a complete waste of time asking him for the commit to resolve the issue. I do have bug reports from my ROM but have yet to figure it out.
[OnePlus 11] badmonopoly:
Just upgraded from the January release.

It works perfectly 😍

I was a little concerned it would go sideways since I was on such an old build.
[OnePlus 11] TheSayaMan:
Additional crash report

crDroid paste - share logs, bugs, code and whatever else remains in plan text

paste.crdroid.net
[OnePlus 11] enunna:
Who is "Nameless dev"? Is that "bgcngm" above?
[OnePlus 11] TheSayaMan:
chandu dyavanapelli

Expect not to get a response. Most developers ignore PM's!
[OnePlus 11] enunna:
Ah I see. I hadn't heard of Nameless AOSP before. Looks like they are taking advantage of the Apache license and keeping it closed source, which would explain why they don't respond.
[OnePlus 11] TheSayaMan:
Correct, he doesn't have any of the commits on github except the kernel and the kernel has nothing to do with the camera problem. The reason for that is because XDA rules require a dev to have a link to the kernel or let the members know the kernel being used.
[OnePlus 11] JoeF2:
Nameless is a different rom, different devs. Unfortunately, they don't have their sources on github, at least I couldn't find them.
[OnePlus 11] TheSayaMan:
Question was already answered
[OnePlus 11] JoeF2:
Yeah, saw that after I refreshed.
[OnePlus 11] TheSayaMan:
I have been told that deleting the vendor/oneplus/sm8550-common with this one will fix the camera issue but I'm too busy right now to build and test. If there is another experienced dev that wants to try it out.

ninja-turtles / proprietary_vendor_oneplus_sm8550-common · GitLab

LibreMobileOS GitLab

git.libremobileos.com
[OnePlus 11] JoeF2:
That looks pretty much like the current tree on TheMuppets. Didn't work for me the last time I tried.
[OnePlus 11] TheSayaMan:
Ok I wasn't aware of that and correct, I tried the one on the muppets as well, total fail. It builds but camera still broken.
[OnePlus 11] JoeF2:
Looks like there is a fork of the muppets proprietary sm8550-common tree by the Nameless dev, with changes:

https://github.com/chandu078/proprietary_vendor_oneplus_sm8550-common

It may be worth trying a build with that.

I'll be running a build, but I may not be able to test it, because I am traveling for the rest of the week.
[OnePlus 11] TheSayaMan:
I'll try now before work
[OnePlus 11] TheSayaMan:
Nope, camera still broken
[OnePlus 11] enunna:
Someone put effort at some point to get the 11 5G working with Lineage. Is there a way to find out who did that work? What Id like to know is if that person or anyone else is considering putting in the effort to get it working again, as I'm still within the return window for this phone.
[OnePlus 11] TheSayaMan:
It worked prior to this month. To my knowledge, no one has gotten it working after, because of changes which caused the camera to break.
[OnePlus 11] enunna:
How was that determined? Is there an automated test that caught the breakage? Or did someone report it and have it removed from the Lineage supported devices list? If it was automated, then it would be a lot easier to reproduce locally and try to figure out what broke. If not, it might be helpful to know who submitted the original changes to enable support and try to get in touch, even if it's unlikely that they will respond.
[OnePlus 11] TheSayaMan:
Most developers ignore PM's on xda. Sometimes things need extra time to fix. Just be patient and it will get fixed. If you go back one page, you will see what happened. I'm not going to hold your hand and tell you. READ the post by bgcngm
[OnePlus 11] enunna:
I missed that post, sorry. Will take a look and I appreciate your replies.
[OnePlus 11] keaheng:
Nameless have a flashable firmware zip in the download section.

@bgcngm do you still update los20 or only working on los21?

BTW the touch feedback haptic is too strong even at the lowest setting. Do you plane to make a change or leave it as is?
[OnePlus 11] bgcngm:
Just a heads-up, new build uploaded and old one removed since some users were having issues updating. Should now be possible to update through recovery (be sure to also download the new install package, containing updated boot, recovery and vendor_boot images).
[OnePlus 11] w2y89dk1:
I use latest build lineage-21.0-20231116-UNOFFICIAL-salami. Adding esim doesn't work, tapping on "Add SIM" button doesn't do anything. I have installed gapps. In logcat i see lines

11-16 22:01:34.885 4203 4203 W EuiccConnector: No valid component found for intent: Intent { act=android.service.euicc.action.PROVISION_EMBEDDED_SUBSCRIPTION (has extras) }
11-16 22:01:34.885 4203 4203 W EuiccUiDispatcher: Could not resolve activity for intent: Intent { act=android.service.euicc.action.PROVISION_EMBEDDED_SUBSCRIPTION (has extras) }

does it mean that there's no app in LOS to handle adding esim?

I have tried installing this app https://gitea.angry.im/PeterCxy/OpenEUICC and it opens when i tap "Add SIM" but still no options to add esim in app and there are errors in logcat

any workarounds?
[OnePlus 11] ePHDiSK:
This is amazing work!

Do the OTA Lineage Updates work for the OP11? Will this be moved to official soon?
[OnePlus 11] texasaggie1:
FYI y'all, I followed the instructions in Post 1 except I dirty flashed using the updated files, rom, and GAPPS and everything works perfectly. I dirty flashed over the first LOS21 version. Thanks OP
[OnePlus 11] w2y89dk1:
On latest build phone hangs and restarts when enabling Settings - Network & internet - Hotspot & tethering - USB tethering
[OnePlus 11] vnod:
[OP11] EDL DownloadTool to restore your device to OxygenOS/ColorOS

Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...

xdaforums.com
[OnePlus 11] Abdul Rafé:
Thanks
[OnePlus 11] justanutt:
OK I just installed the latest Lineage 21. I was on the stock 595 firmware for CPH2451 and installed the 3 files from Lineage on XDA in fastboot. I was able to install via recovery adb sideload. 👍
[OnePlus 11] chemicalboyxda:
Can I flash this ROM to OnePlus ace 2 pro? Or can you make a ROM to this device? It's very similar to op11. In fact TWRP works
[OnePlus 11] bgcngm:
No, you can't.
[OnePlus 11] matoq:
I am currently on a Mi Mix 2 which is on its dying breath after 6 glorious years. It's running LOS20 with microG built in from lineage.microg.org with no further modifications and I'm loving it. For reference: That's not an a/b device and I used TWRP 3311 (iirc).

I've since set up a few 1+ a/b devices for friends using the LOS+microG ROM with its respective recoveries just fine.

This is all to say that I'm aware of how to unlock bootloader, boot into recovery, flash a ROM etc. But I have zero experience with baking microG (or Magisk, for that matter) into a ROM that doesn't come with it.

So here's where I'd like to ask your advice. My main objective is to use a de-googled phone from day one with microG capabilites enabled (primarily: push and safety net attestation). I don't necessarily need the banking apps, which have started to break with recent updates due to bootloader and possibly other things.

Of all the ROMs in development for the 1+ 11 and posted here, this LOS appears to be closest to my use case. I don't mind this being unofficial with no OTA updates (yet).

Please help me out with the following questions, as I'm now considering buying this device:

To the dear developer, prospective maintainer: are you planning to go official with LOS? This is mainly a quality of life matter with the prospect of getting microG baked in and OTA updates.

I understand Magisk comes with microG included now. If so: for the time being, could you give me a short walk through the flashing routine?

I'm a Magisk noob: do I have to re-flash Magisk each time I update LOS manually? Or even with OTA updates down the road?

For those already on this device with LOS + microG and/or Magisk: do you get bank apps, push messages, etc to work with it?

I greatly appreciate you weighing in while I ponder buying the 1+ 11.

I am aware that the future is quite uncertain with safety net being phased out and Google eventually locking Aurora out for good with pass keys. So all I need atm really is a status report on the potential alignment of this ROM with my use case.

Thanks, guys.
[OnePlus 11] DX.Deception:
Is there a suggested method to Gain root and Pass Saftey Net for Gpay?
[OnePlus 11] neelchauhan:
Play Integrity worked with the well-known module until yesterday on this ROM. Now you need to get the fingerprints yourself, so Google doesn't find out.

I reverted to OxygenOS for now, I need to make sure a test device can pass PI with the new tweaks before I re-flash LineageOS again.

EDIT: I got LineageOS working again, with working Google Pay. Surprisingly I got it right on the first try 🥳.
[OnePlus 11] coolgoose1:
Got a new OnePlus11 CPH2451. I was able to unlock bootloader and install TWRP. I sideloaded LineageOS 21 from TWRP and rebooted to recovery to install Gapps but nothing is showing on the screen. It is completely black screen. I tried pressing the power button with and without volume up or volume down or both and nothing is showing on the screen. Anyone ran into this or has ideas on how to enter recovery or fastboot ?
[OnePlus 11] neelchauhan:
You need Lineage Recovery. Don't use TWRP, it's not designed for modern versions of Lineage. For OxygenOS or other ROMs, maybe TWRP works fine. For modern LineageOS, stay away.

In fact, I couldn't install LOS18 on a S4 using TWRP, but could using Lineage Recovery, and the same exact TWRP worked for CM14. And the S4 is 10 years apart from the OP11.
[OnePlus 11] coolgoose1:
Thanks, my device is now showing in EDL mode on my Linux USB list. Is anyone aware of a guide on how to unbrick OnePlus 11 from EDL mode ?
[OnePlus 11] neelchauhan:
You sadly need both Windows and Linux (or Mac) for EDL.

Use this guide: https://xdaforums.com/t/op11-edl-downloadtool-to-restore-your-device-to-oxygenos-coloros.4607995/

Linux alone can't do EDL, since unlike Google Pixels, OnePlus MSM/EDL tool is Windows-only, but Linux/Mac is needed to run a fake authentication server for the MSM.
[OnePlus 11] coolgoose1:
Got everything working on a Linux machine with Windows10 VM except that DownloadTool.exe does not see the phone connected.

On Linux I see the phone in QDL mode

Bus 003 Device 003: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)

But on Windows, when installing drives from https://www.getdroidtips.com/download-qualcomm-qdloader-hs-usb-driver/, I do not see the phone in QDL mode. I see 'Unknown USB Device (Device Descriptor Request Failed)'. Any ideas on that ?
[OnePlus 11] neelchauhan:
I hate to say it, but a Windows VM won't work for this. Try dual-booting with Windows, and run the Linux part in a VM on Windows.
[OnePlus 11] coolgoose1:
Thank you, finally unbricked using a dualboot machine. Now trying to install LineageOS again.
[OnePlus 11] coolgoose1:
I installed Lineage recovery as mentioned in the OP and then sideloaded LineageOS zip. At around 47% on the computer, got a message to reboot to recovery to install other zips. I rebooted to recovery and EDL black screen again.
[OnePlus 11] coolgoose1:
I thought it was LineageOS 21, so tried LineageOS20. That one sideloaded to the end but still EDL black screen as soon as I rebooted to recovery. Anyone has any ideas ?
[OnePlus 11] bgcngm:
What firmware were you running before? Make sure you're running CPH2449_13.1.0.596(EX01). The current build isn't compatible yet with OOS 14.
[OnePlus 11] coolgoose1:
I think I was originally on OOS 13, did not note the original version. But now I have EDL flashed the packages from here. So I am guessing I should have overwritten whatever I had originally.
[OnePlus 11] bgcngm:
Alright, but then boot once to OOS. Then flash the firmware from the version I mentioned above and start over.
[OnePlus 11] coolgoose1:
Sure, will try that. Can you point me to some place where CPH2449_13.1.0.596 is available ? And also instructions to install it ? I am assuming I do not need to EDL flash it.
[OnePlus 11] bgcngm:
No, just EDL flash one of the latest and then update OTA.
[OnePlus 11] coolgoose1:
I think my issue could be this. I just got the new CPH2451, and unlocked bootloader and then tried to install LIneageOS. Did not do any OTA update on the phone, so slot B must be empty, did not even configure Wi-fi on OxygenOS.
[OnePlus 11] neelchauhan:
That is it.

I surprisingly did update to OOS14 and yet could flash this ROM afterwards, when Play Integrity Fix worked again.
[OnePlus 11] coolgoose1:
To fix this, I could flash img files in slot B or try to copy them from slot A to B. In order to flash img's, I guess, I will have to find the latest img files or payload.bin and dump those. I was wondering if there is a copy_partitions type script that can copy partitions from slot A to slot B.
[OnePlus 11] neelchauhan:
You can just boot into OOS and maybe do an OTA once (if you didn't earlier) before flashing LOS.
[OnePlus 11] coolgoose1:
I tried flashing the img files from CPH2451 13.1.0.596 using a script like:

fastboot flash --slot=other abl abl.img
fastboot flash --slot=other aop_config aop_config.img
fastboot flash --slot=other aop aop.img
fastboot flash --slot=other bluetooth bluetooth.img
fastboot flash --slot=other cpucp cpucp.img
fastboot flash --slot=other devcfg devcfg.img
fastboot flash --slot=other dsp dsp.img
fastboot flash --slot=other engineering_cdt engineering_cdt.img
fastboot flash --slot=other featenabler featenabler.img
fastboot flash --slot=other hyp hyp.img
fastboot flash --slot=other imagefv imagefv.img
fastboot flash --slot=other keymaster keymaster.img
fastboot flash --slot=other modem modem.img
fastboot flash --slot=other oplus_sec oplus_sec.img
fastboot flash --slot=other oplusstanvbk oplusstanvbk.img
fastboot flash --slot=other qupfw qupfw.img
fastboot flash --slot=other shrm shrm.img
fastboot flash --slot=other splash splash.img
fastboot flash --slot=other tz tz.img
fastboot flash --slot=other uefi uefi.img
fastboot flash --slot=other uefisecapp uefisecapp.img
fastboot flash --slot=other xbl_config xbl_config.img
fastboot flash --slot=other xbl_ramdump xbl_ramdump.img
fastboot flash --slot=other xbl xbl.img

Gist is that I flashed all partitions except my_* partitions that were in stock OTA but not in LineageOS payload.

Things worked better than the last time. I was able to install recovery, install system and reboot to recovery. Booting system gave me a bootloop and I think that is because my Linux fastboot could not flash modem.img properly due to an issue that gives std:: out_of_range error. I am now going to install an OTA and then try again.

In all, anyone trying to flash LineageOS on a new device, keep in mind that you should have A.23 or newer firmware on the slot you are trying to flash LineageOS to. Either use a script like the above to flash it (preferably to all slots) or take at least one OTA on your new device.
[OnePlus 11] abc1054:
Is there any way to get your abl.img to get rid of orange warning . On cph2451 14.0.0.201(EX01)
[OnePlus 11] coolgoose1:
I was able to install and boot LineageOS after installing an OTA. The OTA was installed on Slot B and I installed LineageOS on Slot B. One thing I noticed that may help others is that the instructions overwrite current slot's recovery and it is needed. But OxygenOS does not boot as soon as you replace recovery. So if you want to have OxygenOS boot, you will have to go back to stock recovery on the current slot.

I still see Orange State warning with this stock abl.img.
[OnePlus 11] btflyrose:
This may be a stupid question, and maybe already answered, but I'm not finding much help.

How do I revert back to stock?
[OnePlus 11] neelchauhan:
One word: MSM.

You need this guide: https://xdaforums.com/t/op11-edl-downloadtool-to-restore-your-device-to-oxygenos-coloros.4607995/

And both a Windows PC (not a VM, dual-boot is fine) and a Linux/Mac system.
[OnePlus 11] fanticgamerw633:
you acc just need one pc to do it. there is a script in the comments that allows this.
[OnePlus 11] neelchauhan:
Got it, I normally use Linux at home so my muscle memory lies there.
[OnePlus 11] abc1054:
is it rooted,? or do I have to put magisk..
[OnePlus 11] abc1054:
I have lastest OnePlus 11 android 14.0.0.201(EX01).. can I use this rom and root
[OnePlus 11] cujo11:
you need to downgrade to 13.1.0.596(EX01) (even 13.1.0.595(EX01) should work since the 596 update was just a security one) before flashing this rom as this build uses 596 proprietary blobs, if you flash without downgrading it will result in a bootloop.
[OnePlus 11] cujo11:
you need to root it yourself
[OnePlus 11] abc1054:
Me too, I downgrade it to 13.1 but still bootlooped. Went back to original.