• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[OFFICIAL] LineageOS 18.1 for the OnePlus One

Search This thread

hybiepoo

Senior Member
Jan 14, 2008
55
1
Sydney
i have problems with MindTheGapps and paid apps from play store tried 3 times. so i have installed offical test opengapps from sourceforge https://sourceforge.net/projects/opengapps/files/arm/test/
Which version exactly, do you know? I'm trying to install even the PICO edition of the latest OpenGapps and it's saying I don't have enough room even after wipe and fresh install.

Edit: Nevermind.. another complete wipe and queued GApps with the ROM install and it seems to have worked fine. Weird.
 

hybiepoo

Senior Member
Jan 14, 2008
55
1
Sydney
Anyone have any issues with not being able to install any apps? "Not enough storage space".
Looking in the storage settings, it seems to be OK, so not sure what is going on. Perhaps permission issues?
 

hybiepoo

Senior Member
Jan 14, 2008
55
1
Sydney
Let's see. What do you mean by "complete wipe"? Which recovery did you use?
I tried the lineageos recovery first and then the latest TWRP. In TWRP I've tried factory reset and also advanced and selected all options.

The problem seems to be with storage:

Failed to find mounted volume for /storage/emulated/0/Android/data/com.android.vending/files/
 
Last edited:
LineageOS Wiki recommends MindTheGapps but somehow I missed to read it. Before flashing MindTheGapps, I've tried a few other Gapps but the results were either bootloop or Gapps crashing! Then I've flashed MindTheGapps-11.0.0-arm-20210412_124103.zip. I also flashed TWRP 3.5.2-9-0 and Magisk 23. All including Magisk are working but in Magisk, safetynet test shows attestation failed. Since Magisk is working without any problem I'm not bothering about attestation failed issue. My Oneplus One is 64GB version.
 

hybiepoo

Senior Member
Jan 14, 2008
55
1
Sydney
LineageOS Wiki recommends MindTheGapps but somehow I missed to read it. Before flashing MindTheGapps, I've tried a few other Gapps but the results were either bootloop or Gapps crashing! Then I've flashed MindTheGapps-11.0.0-arm-20210412_124103.zip. I also flashed TWRP 3.5.2-9-0 and Magisk 23. All including Magisk are working but in Magisk, safetynet test shows attestation failed. Since Magisk is working without any problem I'm not bothering about attestation failed issue. My Oneplus One is 64GB version.
MindTheGapps for me resulted in a loop when trying to assign the phone to a child using FamilyLink. I used the beta OpenGApps and it worked fine.
 

SethGeckoXDA

Senior Member
Feb 19, 2017
132
69
I have disabled the option Display/Lock screen/Wake screen for notifications. Nevertheless, when my calendar app (aCalendar+) sends a notification (e.g. reminder for an event), it wakes the screen. Other tested notifications (e.g. messages received via Signal) do not wake the screen.

I'm wondering...
- are notifications somehow prioritized? If so, how can I disable "waking the screen" for all notifications?
- or is this some kind of bug?
 

ynwakiran1892

New member
Jun 13, 2021
1
1
Hi. I just manually updated to Lineage OS 18.1 from 17.1 & installation went well. But now I am not able to open camera. It crashes. Tried other camera apps on play store, but gave Unable to Open Camera error. Please help
 
  • Like
Reactions: dookie23

SethGeckoXDA

Senior Member
Feb 19, 2017
132
69
Where to find Lineage 17.1. Can't get Netflix working. Also Ziggo Go TV doesn't work. Both worked fine on 17.1.

You can find an unofficial 17.1 build by one of the maintainers here.

Hi. I just manually updated to Lineage OS 18.1 from 17.1 & installation went well. But now I am not able to open camera. It crashes. Tried other camera apps on play store, but gave Unable to Open Camera error. Please help

When upgrading from 17.1 to 18.1, have you formatted/wiped your data partition? (if you successfully did, all your files (pictures, music, ...) should be deleted, which is a necessary step).
 

npjohnson

Recognized Developer
Which version exactly, do you know? I'm trying to install even the PICO edition of the latest OpenGapps and it's saying I don't have enough room even after wipe and fresh install.

Edit: Nevermind.. another complete wipe and queued GApps with the ROM install and it seems to have worked fine. Weird.
Use MindTheGapps like it is listed on our Wiki.
Anyone have any issues with not being able to install any apps? "Not enough storage space".
Looking in the storage settings, it seems to be OK, so not sure what is going on. Perhaps permission issues?
Use MindTheGapps like it is listed on our Wiki.
LineageOS Wiki recommends MindTheGapps but somehow I missed to read it. Before flashing MindTheGapps, I've tried a few other Gapps but the results were either bootloop or Gapps crashing! Then I've flashed MindTheGapps-11.0.0-arm-20210412_124103.zip. I also flashed TWRP 3.5.2-9-0 and Magisk 23. All including Magisk are working but in Magisk, safetynet test shows attestation failed. Since Magisk is working without any problem I'm not bothering about attestation failed issue. My Oneplus One is 64GB version.
Good man, yeah MTG is the way to go :)
 

goomStar

New member
Aug 15, 2020
3
1
First of all: It is such a nice feeling to still see passionate people maintaining this one-of-a-kind device that so many people still love and use. Huge KUDOS to all maintainers, who ever touched this piece of phone history :)

On to the topic then: I've got SLOW WIFI issues. I recognize them from earlier major releases (at least 17, maybe even 16 in some custom OSes). After a good amount of phone usage (not directly after install.. it's more like days or weeks), the WiFi-transferrate sometimes drops down really hard (for me it's like below 10% of network capacity).
Switching Bluetooth OFF can resolve this (but can't be a permanent solution) - and it is 100% NOT an "2.4GHz interferes with Bluetooth so use 5GHz WiFi" issue.
In earlier releases a workaround was to visit "running processes", open the PlayServices and KILL the "NearbyMessageblabla" routine.
As I can't find anything similar sounding in the 18.1 release, I wondered if there is another switch I could try to get stable WiFi rates back.

Maybe people encountered the same behaviour, found a dirty fix or implementing an official fix could be possible with the history of former solutions in past releases.

[Android 11 (RQ2A.210505.003) // 10 June]
 

piens

Member
Sep 23, 2010
46
6
Anybody know how to get Netflix working with lineage 18.1.

Tried:
without ROOT (magisk)
with Root (magisk)
with Root (magisk hide)

No luck: Device not supported. Both with the Netflix app (from the netflix site for not supported devices) as the latest netflix app from different app-store). I can install the app, but it doesn't work

Reverted back to Lineage 17.1, wich works fine, because I couldn't get it working under 18.1. Same with the Ziggo Go TV app, not working with 18.1, fine with 17.1: this video can not be played
 

ardicli2000

Senior Member
Sep 30, 2011
588
184
OnePlus One
OnePlus 9R
Anybody know how to get Netflix working with lineage 18.1.

Tried:
without ROOT (magisk)
with Root (magisk)
with Root (magisk hide)

No luck: Device not supported. Both with the Netflix app (from the netflix site for not supported devices) as the latest netflix app from different app-store). I can install the app, but it doesn't work

Reverted back to Lineage 17.1, wich works fine, because I couldn't get it working under 18.1. Same with the Ziggo Go TV app, not working with 18.1, fine with 17.1: this video can not be played
Which version of 17.1 would you recommend?
 

piens

Member
Sep 23, 2010
46
6
Which version of 17.1 would you recommend?
It worked fine with the last official 17.1 from lineage. I cannot find this version anymore. Unfortunately my twrp backup from the last working 17.1, which I made before installing 18.1 in march 2021, was corrupt. After restoring this backup I got into a bootloop. I had an older version on my HD, version 17.1-20200806-nightly which is older than the last version I had working. So I installed this old version I found on my HD. Now Netfix and Ziggo work again. I also have a OnePlus 2 and a OnePlus 3T, but I don't dare to upgrade them to Lineage 18.1, afraid I run into the same problems with Netflix and Ziggo
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    First of all: It is such a nice feeling to still see passionate people maintaining this one-of-a-kind device that so many people still love and use. Huge KUDOS to all maintainers, who ever touched this piece of phone history :)

    On to the topic then: I've got SLOW WIFI issues. I recognize them from earlier major releases (at least 17, maybe even 16 in some custom OSes). After a good amount of phone usage (not directly after install.. it's more like days or weeks), the WiFi-transferrate sometimes drops down really hard (for me it's like below 10% of network capacity).
    Switching Bluetooth OFF can resolve this (but can't be a permanent solution) - and it is 100% NOT an "2.4GHz interferes with Bluetooth so use 5GHz WiFi" issue.
    In earlier releases a workaround was to visit "running processes", open the PlayServices and KILL the "NearbyMessageblabla" routine.
    As I can't find anything similar sounding in the 18.1 release, I wondered if there is another switch I could try to get stable WiFi rates back.

    Maybe people encountered the same behaviour, found a dirty fix or implementing an official fix could be possible with the history of former solutions in past releases.

    [Android 11 (RQ2A.210505.003) // 10 June]
    Fix merged. Sorry about that!
    Anybody know how to get Netflix working with lineage 18.1.

    Tried:
    without ROOT (magisk)
    with Root (magisk)
    with Root (magisk hide)

    No luck: Device not supported. Both with the Netflix app (from the netflix site for not supported devices) as the latest netflix app from different app-store). I can install the app, but it doesn't work

    Reverted back to Lineage 17.1, wich works fine, because I couldn't get it working under 18.1. Same with the Ziggo Go TV app, not working with 18.1, fine with 17.1: this video can not be played
    Works now.
    It is a shame that LOS 18.1 have so many bugs and problems. Will have to wait few more months before try to again deal with. Not all of them are the result of LOS implementation/development. Few features not balancing the problem and lost functions that we know and love (from 17.1). On the end (for today) - big disappointment.
    What bugs?

    Camera being 50/50 is the only one I'm aware of.
    yes its a clean install, i think i found the issue LOS overwrites the TWRP recovery with its own one which only allows to wipe the data cache i installed twrp again booted into recovery after that so that it doesnt get overwritten again and wiped dalvik and data cache seems to work now ill post an update if this error would occur again
    Not unless you check the box in Updater app to do so...
    Thank you for maintaining and updating the ROM until now.

    I have installed it and I see that the UI is smooth with most of important functionality works.
    However I notice that the battery performance is not good on my unit. I only get 1hr44min from 100% to 20% which is quite low even with a new battery installed.

    Also I found out that the face unlock no longer available in this ROM,
    Does anyone having the same issue?
    Old phone, much more demanding OS requirements?

    Face unlock was killed by Google a while ago.
    Hi there,
    i´m not sure, maybe i´ve found a bug. I tried to install my sons child-account on my old oneplus one with a fresh installed lineageos. Everything works fine - except the login to the "google family link-manager". I can add his account and validate it with my adult-account, but it hungs in a window (translated from german) "Activate Family Link-Manager". When i go next a popup goes up (again, translated from german) "This profilemanager is required for family link managed google-accounts". Press on ok brings me back to the "Activate"-Page.
    I have tried to install all google-apps from the store, no problems - maybe there is a service missing...
    Can anybody help me?

    Regards
    Matthias
    Yeah, that uses SafetyNet and requires Magisk/MagiskHide.
    Now that opengapps have Android 11 release. It is compatible with this rom?
    Yup. Only small packages. Still recommend MTG personally. Guaranteed to work.
    Latest update
    lineage-18.1-20210729-nightly-bacon-signed.zip can flash and boot fine but Touchscreen does not work/respond..power and volume buttons work 😒😒
    Yeah, platform wide unfortunately, will be fixed ASAP. Disable accessibility apps for now to fix it.
    1
    Edit: microphone isnt working with signal normal calls work fine
    Works for me. Check the permissions given to the app, maybe the permission to use the microphone is missing?

    Ok, that actually hit me as well today (Mic not working in a Signal call). It worked properly after rebooting the device. So, it seems the issue happens only sporadically. If somebody knows how to reliably reproduce the issue, shoot!

    Might be related to this issue.

    Log:

    Code:
    07-09 14:11:32.970 12400 12400 I TelecomFramework: UserCallIntentProcessor: sendIntentToDestination: trampoline to Telecom.: [email protected]
    07-09 14:11:33.095 12400 12400 I TelecomFramework: UserCallActivity: onCreate done
    07-09 14:11:33.206   715   715 I chatty  : uid=1000 system_server expire 59 lines
    07-09 14:11:33.206   715  2860 I chatty  : uid=1000(system) uteStateMachine expire 45 lines
    07-09 14:11:33.207   715  2864 I chatty  : uid=1000(system) CallAudioModeSt expire 9 lines
    --------- beginning of crash
    07-09 14:11:33.300   377  2197 F libc    : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xe0 in tid 2197 (Binder:377_3), pid 377 (audioserver)
    07-09 14:11:33.366 12435 12435 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    07-09 14:11:33.367 12435 12435 F DEBUG   : LineageOS Version: '18.1-20210708-NIGHTLY-bacon'
    07-09 14:11:33.367 12435 12435 F DEBUG   : Build fingerprint: 'oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS0YL:user/release-keys'
    07-09 14:11:33.367 12435 12435 F DEBUG   : Revision: '0'
    07-09 14:11:33.367 12435 12435 F DEBUG   : ABI: 'arm'
    07-09 14:11:33.370 12435 12435 F DEBUG   : Timestamp: 2021-07-09 14:11:33+0200
    07-09 14:11:33.371 12435 12435 F DEBUG   : pid: 377, tid: 2197, name: Binder:377_3  >>> /system/bin/audioserver <<<
    07-09 14:11:33.371 12435 12435 F DEBUG   : uid: 1041
    07-09 14:11:33.371 12435 12435 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xe0
    07-09 14:11:33.371 12435 12435 F DEBUG   : Cause: null pointer dereference
    07-09 14:11:33.371 12435 12435 F DEBUG   :     r0  00000000  r1  008c0055  r2  00000000  r3  00000000
    07-09 14:11:33.371 12435 12435 F DEBUG   :     r4  ad0c0564  r5  00000001  r6  abe79d30  r7  abe79cd0
    07-09 14:11:33.371 12435 12435 F DEBUG   :     r8  af4d9124  r9  af4d9124  r10 af24a448  r11 b0300490
    07-09 14:11:33.371 12435 12435 F DEBUG   :     ip  af24bbcc  sp  abe79950  lr  af2263e7  pc  af2244ac
    07-09 14:11:33.422 12435 12435 F DEBUG   : backtrace:
    07-09 14:11:33.422 12435 12435 F DEBUG   :       #00 pc 0001a4ac  /system/lib/libaudiopolicyenginedefault.so (android::audio_policy::Engine::getDevicesForStrategyInt(android::audio_policy::legacy_strategy, android::DeviceVector, android::DeviceVector, android::SwAudioOutputCollection const&) const+988) (BuildId: c5f2ef6861302a88743da59d367a6053)
    07-09 14:11:33.422 12435 12435 F DEBUG   :       #01 pc 0001caa7  /system/lib/libaudiopolicyenginedefault.so (android::audio_policy::Engine::getDevicesForProductStrategy(android::product_strategy_t) const+438) (BuildId: c5f2ef6861302a88743da59d367a6053)
    07-09 14:11:33.422 12435 12435 F DEBUG   :       #02 pc 0001cd1b  /system/lib/libaudiopolicyenginedefault.so (android::audio_policy::Engine::getOutputDevicesForAttributes(audio_attributes_t const&, android::sp<android::DeviceDescriptor> const&, bool) const+226) (BuildId: c5f2ef6861302a88743da59d367a6053)
    07-09 14:11:33.423 12435 12435 F DEBUG   :       #03 pc 0000bd3d  /system/lib/libaudiopolicymanager.so (android::AudioPolicyManagerCustom::checkOutputForAttributes(audio_attributes_t const&)+124) (BuildId: 05f2083db6bf114b31d36564d32778f9)
    07-09 14:11:33.423 12435 12435 F DEBUG   :       #04 pc 0003a467  /system/lib/libaudiopolicymanagerdefault.so (android::AudioPolicyManager::checkOutputForAllStrategies()+106) (BuildId: b0140817566edd506b711b6a0890171f)
    07-09 14:11:33.423 12435 12435 F DEBUG   :       #05 pc 000254f9  /system/lib/libaudiopolicymanagerdefault.so (android::AudioPolicyManager::checkForDeviceAndOutputChanges(std::__1::function<bool ()>)+32) (BuildId: b0140817566edd506b711b6a0890171f)
    07-09 14:11:33.423 12435 12435 F DEBUG   :       #06 pc 0000c42b  /system/lib/libaudiopolicymanager.so (android::AudioPolicyManagerCustom::setPhoneState(audio_mode_t)+146) (BuildId: 05f2083db6bf114b31d36564d32778f9)
    07-09 14:11:33.423 12435 12435 F DEBUG   :       #07 pc 000104eb  /system/lib/libaudiopolicyservice.so (android::AudioPolicyService::setPhoneState(audio_mode_t, unsigned int)+80) (BuildId: 89396bf069d4e8387bc5f6930d86e70e)
    07-09 14:11:33.423 12435 12435 F DEBUG   :       #08 pc 00054c75  /system/lib/libaudioclient.so (android::BnAudioPolicyService::onTransact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+5768) (BuildId: b7e6b5c02d0fcfd799ee2a6f4d39c929)
    07-09 14:11:33.423 12435 12435 F DEBUG   :       #09 pc 0003451d  /system/lib/libbinder.so (android::BBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+144) (BuildId: 486e8e257fc611836c4c865eb1db580b)
    07-09 14:11:33.423 12435 12435 F DEBUG   :       #10 pc 0003a38f  /system/lib/libbinder.so (android::IPCThreadState::executeCommand(int)+626) (BuildId: 486e8e257fc611836c4c865eb1db580b)
    07-09 14:11:33.423 12435 12435 F DEBUG   :       #11 pc 0003a05f  /system/lib/libbinder.so (android::IPCThreadState::getAndExecuteCommand()+98) (BuildId: 486e8e257fc611836c4c865eb1db580b)
    07-09 14:11:33.423 12435 12435 F DEBUG   :       #12 pc 0003a6eb  /system/lib/libbinder.so (android::IPCThreadState::joinThreadPool(bool)+38) (BuildId: 486e8e257fc611836c4c865eb1db580b)
    07-09 14:11:33.423 12435 12435 F DEBUG   :       #13 pc 000542ad  /system/lib/libbinder.so (android::PoolThread::threadLoop()+12) (BuildId: 486e8e257fc611836c4c865eb1db580b)
    07-09 14:11:33.423 12435 12435 F DEBUG   :       #14 pc 0000ed43  /system/lib/libutils.so (android::Thread::_threadLoop(void*)+170) (BuildId: b8dfed2088aad5ea02c25267aaef3e88)
    07-09 14:11:33.423 12435 12435 F DEBUG   :       #15 pc 0000e881  /system/lib/libutils.so (thread_data_t::trampoline(thread_data_t const*)+264) (BuildId: b8dfed2088aad5ea02c25267aaef3e88)
    07-09 14:11:33.423 12435 12435 F DEBUG   :       #16 pc 0008221b  /apex/com.android.runtime/lib/bionic/libc.so (__pthread_start(void*)+40) (BuildId: dfd35824296878c5e25149d780dd7d13)
    07-09 14:11:33.424 12435 12435 F DEBUG   :       #17 pc 0003a3fd  /apex/com.android.runtime/lib/bionic/libc.so (__start_thread+30) (BuildId: dfd35824296878c5e25149d780dd7d13)
  • 31
    lineage-os-logo.png

    OnePlus One

    Code:
    - Your warranty is now void.
    - You have been warned.
    - Use at your own risk.

    Introduction:
    This is the Official Lineage OS 18.1 thread for the OnePlus One.

    Downloads:
    Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
    If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

    Known Bugs:
    • None.
    • Hardware-backed encryption is broken thanks to Google dropping support for legacy credential storage from AOSP 11.0, so we just feel back to software-backed encryption. This means it is a little slower, and taxing on the CPU, in addition to the fact upgrades from older LineageOS versions are not supported. The Wiki upgrade guide notes this as well.
    • Find any? Report them according to this guide.
    Notes:
    • The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps!

    Kernel Source: https://github.com/LineageOS/android_kernel_oppo_msm8974
    5
    First of all: It is such a nice feeling to still see passionate people maintaining this one-of-a-kind device that so many people still love and use. Huge KUDOS to all maintainers, who ever touched this piece of phone history :)

    On to the topic then: I've got SLOW WIFI issues. I recognize them from earlier major releases (at least 17, maybe even 16 in some custom OSes). After a good amount of phone usage (not directly after install.. it's more like days or weeks), the WiFi-transferrate sometimes drops down really hard (for me it's like below 10% of network capacity).
    Switching Bluetooth OFF can resolve this (but can't be a permanent solution) - and it is 100% NOT an "2.4GHz interferes with Bluetooth so use 5GHz WiFi" issue.
    In earlier releases a workaround was to visit "running processes", open the PlayServices and KILL the "NearbyMessageblabla" routine.
    As I can't find anything similar sounding in the 18.1 release, I wondered if there is another switch I could try to get stable WiFi rates back.

    Maybe people encountered the same behaviour, found a dirty fix or implementing an official fix could be possible with the history of former solutions in past releases.

    [Android 11 (RQ2A.210505.003) // 10 June]
    Fix merged. Sorry about that!
    Anybody know how to get Netflix working with lineage 18.1.

    Tried:
    without ROOT (magisk)
    with Root (magisk)
    with Root (magisk hide)

    No luck: Device not supported. Both with the Netflix app (from the netflix site for not supported devices) as the latest netflix app from different app-store). I can install the app, but it doesn't work

    Reverted back to Lineage 17.1, wich works fine, because I couldn't get it working under 18.1. Same with the Ziggo Go TV app, not working with 18.1, fine with 17.1: this video can not be played
    Works now.
    It is a shame that LOS 18.1 have so many bugs and problems. Will have to wait few more months before try to again deal with. Not all of them are the result of LOS implementation/development. Few features not balancing the problem and lost functions that we know and love (from 17.1). On the end (for today) - big disappointment.
    What bugs?

    Camera being 50/50 is the only one I'm aware of.
    yes its a clean install, i think i found the issue LOS overwrites the TWRP recovery with its own one which only allows to wipe the data cache i installed twrp again booted into recovery after that so that it doesnt get overwritten again and wiped dalvik and data cache seems to work now ill post an update if this error would occur again
    Not unless you check the box in Updater app to do so...
    Thank you for maintaining and updating the ROM until now.

    I have installed it and I see that the UI is smooth with most of important functionality works.
    However I notice that the battery performance is not good on my unit. I only get 1hr44min from 100% to 20% which is quite low even with a new battery installed.

    Also I found out that the face unlock no longer available in this ROM,
    Does anyone having the same issue?
    Old phone, much more demanding OS requirements?

    Face unlock was killed by Google a while ago.
    Hi there,
    i´m not sure, maybe i´ve found a bug. I tried to install my sons child-account on my old oneplus one with a fresh installed lineageos. Everything works fine - except the login to the "google family link-manager". I can add his account and validate it with my adult-account, but it hungs in a window (translated from german) "Activate Family Link-Manager". When i go next a popup goes up (again, translated from german) "This profilemanager is required for family link managed google-accounts". Press on ok brings me back to the "Activate"-Page.
    I have tried to install all google-apps from the store, no problems - maybe there is a service missing...
    Can anybody help me?

    Regards
    Matthias
    Yeah, that uses SafetyNet and requires Magisk/MagiskHide.
    Now that opengapps have Android 11 release. It is compatible with this rom?
    Yup. Only small packages. Still recommend MTG personally. Guaranteed to work.
    Latest update
    lineage-18.1-20210729-nightly-bacon-signed.zip can flash and boot fine but Touchscreen does not work/respond..power and volume buttons work 😒😒
    Yeah, platform wide unfortunately, will be fixed ASAP. Disable accessibility apps for now to fix it.
    4
    @npjohnson Thank you for your continued efforts into maintaining official builds for bacon. Thanks a lot. Really appreciate this. :)
    3
    With the latest update the camera is still not responding. Anyone found something to fix that already or am I missing something?
    After the last update i had also a problem with camera app, it doesn't open. I solved it with following, boot into recovery mode and delete cache and dalvik/art cache in twrp, then reboot to system. After that camera is working again. Maybe this helps you.
    2
    Dirty flash from :
    • Lineage OS 17.1
    • TWRP 3.5.1
    • Deactivate your unlock protection (pattern, PIN etc.) so it unlocks by simply sliding up
    Now, boot into TWRP and install (in same order and without rebooting inbetween)

    • Lineage OS 18.1
    • GApps (must be Android 11 )
    • Remove or rename the file /data/system/locksettings.db by using TWRPs explorer functionality
    • Magisk
    • Reboot and unlock into Lineage 18.1 like normal and reactivate your unlock protection of choice