Development [ROM][OFFICIAL][dre][12L] LineageOS 19

Search This thread

Mobe1969

Senior Member
Apr 4, 2013
191
28
53
Brisbane
Xiaomi Mi 10T Lite
For anyone else that hits this snag that held me up for a few days, I would like to tell them as I kick myself for not following the instructions verbatim, UPDATE TO THE LATEST SECURITY PATCH LEVEL IN OXYGEN OS, else it will never work... I know its already in the instructions, but I thought I already had the latest and couldn't understand why I could get no further, low and behold, there was an update that I needed for this to install.. Problem arises from the fact I had a notification that system update failed and ultimately had to repartition and reflash stock OOS and then update to the latest sec patch, all before install the Lineage ROM would complete without error... But it was worth all the work and wait for sure!!! I'm dealing with audio loss that prevents ringing when I get a call or speakerphone right now though if anyone has a suggestion.
Not that I had that issue, but how do you update to the latest patch without it upgrading to Android 12? Eg keep it on Android 11 but still update?
 
Interested in trying this but need some confirmation, if it works properly on the AT&T network as when trying most GSI data, calls and text never worked properly.
I second this. Is anyone here using this phone with LineageOS on AT&T? Do VoLTE and MMS work properly? Our situation is a bit different from those who are on T-Mobile.
 

oCAPTCHA

Member
Sep 22, 2021
26
8
Thank you to the developers for making this! It is what I have been waiting for (for a year!)

I can confirm for those asking, that LineageOS works with AT&T network in VoLTE mode (Redpocket AT&T). No VoLTE symbol appears, and I strangely had to disable my firewall, but it registers and works. (With my firewall enabled and com.android.imsserviceentitlement allowed, the phone would initally work but lose registration after some hours passed)

I wasted much effort on GSI's that didn't work and probably never will. GSI's are not specific to our phone, and One Plus used a non standard VoLTE implementation. I assume the devs just copied the stock VoLTE implementation over, but I would like to hear the specifics.

The lineage recovery works fine, and is able to sideload Magisk.zip for root.
 
  • Like
Reactions: blueberry.sky

Tyreethetruth

Member
Jul 30, 2017
29
2
Does everything work for everyday and main use? Calls and text hotspot 5g etc work and other important features? Anything buggy or broken atm? I'm on t-mobile variant metro by tmobile
 

Dxgbtt

Member
Aug 12, 2022
6
5
Not that I had that issue, but how do you update to the latest patch without it upgrading to Android 12? Eg keep it on Android 11 but still update?
I had auto system update turned off in developer options, but still every week or so it would alert me that my security settings were out of date, but I wrote the comment you referred to before Android 12 was available for the n200, so I may have just ran system update
 

Dxgbtt

Member
Aug 12, 2022
6
5
Does everything work for everyday and main use? Calls and text hotspot 5g etc work and other important features? Anything buggy or broken atm? I'm on t-mobile variant metro by tmobile
I have the T-mobile version unlocked, I only had a minor issue at first boot, like if I turned the brightness below 25% then the screen would go black and I had to blindly figure where to touch to turn it back up enough that it would turn back on... But it seems a final factory data reset in recovery fixed that fully, used the device for a month rooted and had no issues, using a gsm sim from qlinkwireless, hotspot worked at full speed and the whole device in general is more responsive, less laggy and r/w speeds to the sd card are boosted so moving large files off device but still in device, lol, works a bit quicker
 
  • Like
Reactions: blueberry.sky

Link575

Senior Member
Dec 21, 2015
137
26
Samsung Galaxy S22 Ultra
I have the T-mobile version unlocked, I only had a minor issue at first boot, like if I turned the brightness below 25% then the screen would go black and I had to blindly figure where to touch to turn it back up enough that it would turn back on... But it seems a final factory data reset in recovery fixed that fully, used the device for a month rooted and had no issues, using a gsm sim from qlinkwireless, hotspot worked at full speed and the whole device in general is more responsive, less laggy and r/w speeds to the sd card are boosted so moving large files off device but still in device, lol, works a bit quicker
I actually went back to stock because I couldn't figure out why my display was blacking out on me. It almost exclusively happened while playing Pokemon Go though and brightness was decently high. If it's not too much trouble and you have an account would you mind using it on that phone for a while and letting me know if it happens for you? It generally happened during battles. TIA
 

Dxgbtt

Member
Aug 12, 2022
6
5
I actually went back to stock because I couldn't figure out why my display was blacking out on me. It almost exclusively happened while playing Pokemon Go though and brightness was decently high. If it's not too much trouble and you have an account would you mind using it on that phone for a while and letting me know if it happens for you? It generally happened during battles. TIA
I don't actually have a GO account, but I was going to try it for u anyway, for some reason it won't let me create an account from the n200... Nonetheless, somebody else I read earlier in this post needed to know how to generate a payload.bin and full OTA update package and I have done that loads of times with the n100 using msmtool to read back all partitions, packing the payload, configuring META-inf, soon as I get a guide together I'll link it here. After u have that, restoring to precisely the way it looks and works before any changes at all is as easy as flashing an OTA full update zip. With the lineage recovery, unsigned zips are no problem to flash
 
  • Like
Reactions: blueberry.sky

Link575

Senior Member
Dec 21, 2015
137
26
Samsung Galaxy S22 Ultra
I don't actually have a GO account, but I was going to try it for u anyway, for some reason it won't let me create an account from the n200... Nonetheless, somebody else I read earlier in this post needed to know how to generate a payload.bin and full OTA update package and I have done that loads of times with the n100 using msmtool to read back all partitions, packing the payload, configuring META-inf, soon as I get a guide together I'll link it here. After u have that, restoring to precisely the way it looks and works before any changes at all is as easy as flashing an OTA full update zip. With the lineage recovery, unsigned zips are no problem to flash
No problem man, thanks for trying. I may be wrong but I think the thread on here on how to convert de2118 to de2117 includes making a backup with the MSM tool. Again I don't know if its the same as you're speaking of but if it is it could save you some time writing it up.
 

thetesterman

Member
Aug 29, 2012
28
4
DE21127 Carrier Unlocked T-Mobile Build DE2117_11_C.18

Followed instructions to install Lineageos & Gapps 12.1
Only issue I had is that the Android Google setup would not finish but I was able to reset permissions and manually set wifi/cellular which allowed the app to finish. All working great, very smooth, thanks for the great instructions !!

How do I now get root ?

EDIT: add the latest Magisk package at Section "Installing LineageOS From Recovery" Step 6
 
Last edited:

riverstyxxx

Senior Member
May 9, 2015
168
24
Works just fine on the DE2118 if you get the bootloader unlocked.
I nearly had a heart attack, thanks for confirming.

EDIT: Spoke too soon. I had to fill out the form to unlock it and now I have to wait for a week. Damnit.

Double Edit: The guy sold me an unlocked DE2118 but I cant get a code for it because it doesn't have a carrier. That's why these things are $100 off of retail price on ebay.

Triple edit: Found another seller who confirmed some 2117's for $150,

Another edit: Got scammed, again. Sold me a locked 2118. Best buy has them for $50 off right now. Don't buy this model online!
 
Last edited:
  • Like
Reactions: blueberry.sky

radekmazur

Senior Member
Sep 20, 2015
126
33
I nearly had a heart attack, thanks for confirming.

EDIT: Spoke too soon. I had to fill out the form to unlock it and now I have to wait for a week. Damnit.

Double Edit: The guy sold me an unlocked DE2118 but I cant get a code for it because it doesn't have a carrier. That's why these things are $100 off of retail price on ebay.

Triple edit: Found another seller who confirmed some 2117's for $150, ebay #125223071860
I sold my extra de2118 but right before the sale, I called TMobile and they remotely unlocked it for me.
 

radekmazur

Senior Member
Sep 20, 2015
126
33
I just installed lineage. This phone is so much smoother with it compared to oxygen. Day and night.
 

radekmazur

Senior Member
Sep 20, 2015
126
33
Anyways to allow DUN into the rom? I'd like to tether TMobile but modifying APN is not allowed because of "DUN".
 

Aelis440

New member
Oct 13, 2022
2
1
What is your--
LineageOS version: 19.1
LineageOS Download url: https://mirrorbits.lineageos.org/full/dre/20221012/lineage-19.1-20221012-nightly-dre-signed.zip
Gapps version: none, MindTheGapps, and MicroG (tested all three, all have this issue)

Did you--
wipe: Yes
restore with titanium backup: No
reboot after having the issue: Yes

Are you using--
a task killer: No
a non-stock kernel: No
other modifications: No

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
The screen periodically dies (touch input still works) before turning back on a few seconds later. I saw a previous comment saying to disable LiveDisplay and have done so (I think), I have the following settings:

Code:
display_anti_flicker=0
display_auto_outdoor_mode=0
display_color_adjustment=1.0 1.0 1.0
display_color_enhance=0
display_low_power=0
display_temperature_mode=0
live_display_hinted=1

I'm seeing this in logcat:
Code:
10-12 21:33:08.941   917  2047 E audio_hw_primary: disable_snd_device: device ref cnt is already 0
10-12 21:33:10.980     0     0 E         : [20221012_21:33:10.976860]@2 BQ25600 bq2560x_iio_read_raw: bq2560x IIO channel 7a not supported
10-12 21:33:10.981     0     0 E [20221012_21:33:10.976902]@2 QCOM-BATT: is_parallel_available: Couldn't get fcc_max rc=-22
10-12 21:33:14.804     0     0 E [20221012_21:33:14.800738]@3 [drm: dsi_display_validate_status] *ERROR* mismatch: 0x98
10-12 21:33:14.805     0     0 E [20221012_21:33:14.800801]@3 [drm: dsi_display_check_status] *ERROR* [DSI]: [qcom,mdss_dsi_nt36672c_tm_video] read status failed on master,rc=-22
10-12 21:33:14.805     0     0 E [20221012_21:33:14.801776]@3 [drm: _sde_connector_report_panel_dead:2749] [sde error]esd check failed report PANEL_DEAD conn_id: 32 enc_id: 31
10-12 21:33:14.805     0     0 E [20221012_21:33:14.803892]@3 [drm: _sde_connector_update_power_locked:667] [sde error]conn 32 - dpms 0, lp 5, panel 5
10-12 21:33:14.805     0     0 E [20221012_21:33:14.803973]@3 [drm: dsi_display_set_backlight] *ERROR* [DSI]: DSI_CMD_CABC_OFF
10-12 21:33:14.805     0     0 E [20221012_21:33:14.804008]@3 [drm: dsi_panel_set_backlight] *ERROR* [DSI]: backlight type:nt36672c tm fhd plus video mode dsi panel lvl:383+
10-12 21:33:14.824     0     0 E [20221012_21:33:14.821342]@3 [drm: dsi_panel_set_backlight] *ERROR* [DSI]: backlight type:nt36672c tm fhd plus video mode dsi panel lvl:273+
10-12 21:33:14.840     0     0 E [20221012_21:33:14.838556]@3 [drm: dsi_panel_set_backlight] *ERROR* [DSI]: backlight type:nt36672c tm fhd plus video mode dsi panel lvl:170+
10-12 21:33:14.857     0     0 E [20221012_21:33:14.855784]@3 [drm: dsi_panel_set_backlight] *ERROR* [DSI]: backlight type:nt36672c tm fhd plus video mode dsi panel lvl:94+
10-12 21:33:14.876     0     0 E [20221012_21:33:14.873013]@3 [drm: dsi_panel_set_backlight] *ERROR* [DSI]: backlight type:nt36672c tm fhd plus video mode dsi panel lvl:47+
10-12 21:33:14.892     0     0 E [20221012_21:33:14.890102]@3 [drm: dsi_panel_set_backlight] *ERROR* [DSI]: backlight type:nt36672c tm fhd plus video mode dsi panel lvl:21+
10-12 21:33:14.908     0     0 E [20221012_21:33:14.907143]@3 [drm: dsi_panel_set_backlight] *ERROR* [DSI]: backlight type:nt36672c tm fhd plus video mode dsi panel lvl:5+
10-12 21:33:14.925     0     0 E [20221012_21:33:14.924236]@3 [drm: dsi_panel_set_backlight] *ERROR* [DSI]: backlight type:1 lvl:0
10-12 21:33:14.940     0     0 E [20221012_21:33:14.939803]@3 [drm: dsi_display_disable] *ERROR* [DSI]: DRM_PANEL_BLANK_POWERDOWN_CUST
10-12 21:33:14.941     0     0 E [20221012_21:33:14.939879]@3 [TP]touchpanel0: fb_drm_notifier_callback: event = 2, blank = 4
10-12 21:33:14.941     0     0 E [20221012_21:33:14.939905]@3 [TP]touchpanel0: tp_suspend: start.
10-12 21:33:14.941     0     0 E [20221012_21:33:14.939921]@3 [TP]touchpanel0: tp_suspend ts->bus_ready =1
10-12 21:33:14.941     0     0 E [20221012_21:33:14.939939]@3 [TP]: tp_suspend ts->is_suspended 1
10-12 21:33:14.941     0     0 E [20221012_21:33:14.939973]@3 [TP]touchpanel: Esd protector stoped!
10-12 21:33:14.941     0     0 E [20221012_21:33:14.939997]@3 [TP]novatek,nf_nt36672c: nvt_enable_game_mode:enable = 0, chip_info->is_sleep_writed = 0
10-12 21:33:14.968     0     0 E [20221012_21:33:14.965976]@3 [TP]novatek,nf_nt36672c: send Cmd 0x7E success, tried 0 times
10-12 21:33:14.968     0     0 E [20221012_21:33:14.966030]@3 [TP]novatek,nf_nt36672c: nvt_enable_black_gesture, enable = 1, chip_info->is_sleep_writed = 0
10-12 21:33:14.992     0     0 E [20221012_21:33:14.989937]@3 [TP]novatek,nf_nt36672c: send Cmd 0x13 success, tried 0 times
10-12 21:33:14.993     0     0 E [20221012_21:33:14.989988]@3 [TP]novatek,nf_nt36672c: nvt_enable_black_gesture: enable gesture success !
10-12 21:33:14.993     0     0 E [20221012_21:33:14.990008]@3 [TP]touchpanel0: tp_suspend: end.
10-12 21:33:14.993     0     0 E [20221012_21:33:14.990070]@3 [drm: dsi_panel_disable] *ERROR* [DSI]: start
10-12 21:33:14.993     0     0 E [20221012_21:33:14.990094]@3 [drm: dsi_panel_disable] *ERROR* [DSI]: end
10-12 21:33:14.993     0     0 E [20221012_21:33:14.990118]@3 [TP]touchpanel0: fb_drm_notifier_callback: event = 1, blank = 4
10-12 21:33:14.993     0     0 E         : [20221012_21:33:14.990149]@3 [TP] in dsi_panel_unprepare, mode=0
10-12 21:33:15.000     0     0 E         : [TP] in dsi_panel_power_off, mode=0
10-12 21:33:15.001     0     0 E         : [20221012_21:33:14.996965]@3 [TP] tp gesture is disenable, Display goto power off
10-12 21:33:15.001     0     0 E [20221012_21:33:14.997114]@3 [drm: dsi_panel_post_unprepare] *ERROR* [DSI]: disable reset gpio
10-12 21:33:15.001     0     0 E [20221012_21:33:14.997164]@3 [drm: dsi_panel_post_unprepare] *ERROR* [DSI]: set dsi panel pinctrl state false
10-12 21:33:15.021     0     0 E [20221012_21:33:15.017821]@2 [drm: dsi_panel_post_unprepare] *ERROR* [DSI]: disable dsi pwr regulator
10-12 21:33:15.056     0     0 E [20221012_21:33:15.052956]@2 fb_notifier_callback: receives wrong data EARLY_BLANK:7
10-12 21:33:15.064     0     0 E [20221012_21:33:15.061658]@2 [TP]: power_on-is_pd_with_guesture = false
10-12 21:33:15.128     0     0 E [20221012_21:33:15.128359]@2 [drm: dsi_panel_power_on] *ERROR* [DSI]: set dsi panel pinctrl state true
10-12 21:33:15.192     0     0 E [20221012_21:33:15.190060]@2 [drm: dsi_panel_power_on] *ERROR* [DSI]: reset panel
10-12 21:33:15.193     0     0 E [20221012_21:33:15.190183]@2 [drm: dsi_panel_enable] *ERROR* [DSI]: start
10-12 21:33:15.360     0     0 E [20221012_21:33:15.358545]@1 [drm: dsi_panel_enable] *ERROR* [DSI]: Send DSI_CMD_SET_ON cmds
10-12 21:33:15.360     0     0 E [20221012_21:33:15.358588]@1 fb_notifier_callback: receives wrong data EARLY_BLANK:6
10-12 21:33:15.361     0     0 E [20221012_21:33:15.358627]@1 [drm: dsi_panel_enable] *ERROR* [DSI]: Send dsi_panel_set_aod_mode 0 cmds
10-12 21:33:15.361     0     0 E [20221012_21:33:15.358648]@1 [drm: dsi_panel_enable] *ERROR* [DSI]: end
10-12 21:33:15.361     0     0 E [20221012_21:33:15.358822]@1 [drm: _sde_connector_update_power_locked:667] [sde error]conn 32 - dpms 0, lp 0, panel 0
10-12 21:33:15.361     0     0 E [20221012_21:33:15.358854]@1 [drm: dsi_display_set_power] *ERROR* [DSI]: SDE_MODE_DPMS_ON
10-12 21:33:15.361     0     0 E [20221012_21:33:15.358877]@1 [drm: dsi_display_set_power] *ERROR* [DSI]: DRM_PANEL_BLANK_UNBLANK_CUST
10-12 21:33:15.361     0     0 E [20221012_21:33:15.358913]@1 [TP]touchpanel0: fb_drm_notifier_callback: event = 2, blank = 8
10-12 21:33:15.361     0     0 E [20221012_21:33:15.358960]@1 [TP]touchpanel0: fb_drm_notifier_callback: event = 1, blank = 8
10-12 21:33:15.361     0     0 E [20221012_21:33:15.358976]@1 [TP]touchpanel0: tp_resume start.
10-12 21:33:15.361     0     0 E [20221012_21:33:15.359084]@0 [TP]touchpanel0: speedup_resume is called
10-12 21:33:15.361     0     0 E [20221012_21:33:15.359625]@1 [drm: dsi_display_set_backlight] *ERROR* [DSI]: DSI_CMD_CABC_MODE1
10-12 21:33:15.373     0     0 E [20221012_21:33:15.370794]@1 [drm: dsi_panel_set_backlight] *ERROR* [DSI]: backlight type:1 lvl:460
10-12 21:33:15.388     0     0 E [20221012_21:33:15.385955]@0 [TP]novatek,nf_nt36672c: fw_ver = 0xa, fw_type = 0x1
10-12 21:33:15.388     0     0 E [20221012_21:33:15.387610]@0 [TP]novatek,nf_nt36672c: fw_ver = 0xa, fw_type = 0x1
10-12 21:33:15.388     0     0 E [20221012_21:33:15.388424]@0 [TP]novatek,nf_nt36672c: nvt_fw_check: dev_version = 0A
10-12 21:33:15.440     0     0 E [20221012_21:33:15.437191]@3 [TP]novatek,nf_nt36672c: nvt_enable_black_gesture, enable = 0, chip_info->is_sleep_writed = 0
10-12 21:33:15.444     0     0 E [20221012_21:33:15.437240]@3 [TP]: nvt_mode_switch mode = 2 Wrong mode
10-12 21:33:15.444     0     0 E [20221012_21:33:15.437259]@3 [TP]novatek,nf_nt36672c: nvt_enable_charge_mode:enable = 0, chip_info->is_sleep_writed = 0
10-12 21:33:15.464     0     0 E [20221012_21:33:15.461597]@2 [TP]novatek,nf_nt36672c: send Cmd 0x51 success, tried 0 times
10-12 21:33:15.488     0     0 E [20221012_21:33:15.486236]@2 [TP]novatek,nf_nt36672c: send Cmd 0x78 success, tried 0 times
10-12 21:33:15.488     0     0 E [20221012_21:33:15.486281]@2 [TP]touchpanel: Esd protector started, cycle: 2 s
10-12 21:33:15.488     0     0 E [20221012_21:33:15.486704]@0 genirq: Flags mismatch irq 296. 00002002 (touch-00) vs. 00002002 (touch-00)
10-12 21:33:15.488     0     0 E [20221012_21:33:15.486862]@0 [TP]touchpanel0: tp_register_irq_func request_threaded_irq ret is -16
10-12 21:33:15.488     0     0 E [20221012_21:33:15.486884]@0 [TP]touchpanel0: speedup_resume: end!
I read through a bunch of the dsi_*.c files in the repo but I don't know enough about this kind of thing to guess where the problem is. Any help is appreciated!
 

Link575

Senior Member
Dec 21, 2015
137
26
Samsung Galaxy S22 Ultra
What is your--
LineageOS version: 19.1
LineageOS Download url: https://mirrorbits.lineageos.org/full/dre/20221012/lineage-19.1-20221012-nightly-dre-signed.zip
Gapps version: none, MindTheGapps, and MicroG (tested all three, all have this issue)

Did you--
wipe: Yes
restore with titanium backup: No
reboot after having the issue: Yes

Are you using--
a task killer: No
a non-stock kernel: No
other modifications: No

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
The screen periodically dies (touch input still works) before turning back on a few seconds later. I saw a previous comment saying to disable LiveDisplay and have done so (I think), I have the following settings:
This is the same issue I have had since the first version. I've made a bug report here and on the lineage site but at this point it appears no one is looking at it. It's quite an annoying occurrence.
 

Aelis440

New member
Oct 13, 2022
2
1
This is the same issue I have had since the first version. I've made a bug report here and on the lineage site but at this point it appears no one is looking at it. It's quite an annoying occurrence.
Yeah your post is what got me hunting down the LiveDisplay path - plus the screen dies far more often if I go to the LiveDisplay settings screen. I can't compile the source yet (possibly because I'm on Fedora instead of Ubuntu) so I've tried removing the LiveDisplay service from init and verified it's gone, but I'm still seeing the same errors. I'm starting to think there might just be a bug in the kernel but without being able to compile and test, it's just a guess at this point.

I'm going to try to get an Ubuntu container set up this weekend so I can build and if I can hunt down a fix, I'll submit it but I'm well out of my wheelhouse on this kind of thing. : P
 
  • Like
Reactions: blueberry.sky

Link575

Senior Member
Dec 21, 2015
137
26
Samsung Galaxy S22 Ultra
Yeah your post is what got me hunting down the LiveDisplay path - plus the screen dies far more often if I go to the LiveDisplay settings screen. I can't compile the source yet (possibly because I'm on Fedora instead of Ubuntu) so I've tried removing the LiveDisplay service from init and verified it's gone, but I'm still seeing the same errors. I'm starting to think there might just be a bug in the kernel but without being able to compile and test, it's just a guess at this point.

I'm going to try to get an Ubuntu container set up this weekend so I can build and if I can hunt down a fix, I'll submit it but I'm well out of my wheelhouse on this kind of thing. : P
Cool man, all the power to you cause I have zero experience in this stuff. The most "code" I know is SQL lol. Good luck in your endeavors.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 14
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS GitHub repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    Instructions:
    Downloads:
    Reporting Bugs:
    • DO NOT report bugs if you're running a custom kernel or you installed Xposed.
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download url:
    Gapps version:
    
    Did you--
    wipe:
    restore with titanium backup:
    reboot after having the issue:
    
    Are you using--
    a task killer:
    a non-stock kernel:
    other modifications:
    
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
    2
    Not that I had that issue, but how do you update to the latest patch without it upgrading to Android 12? Eg keep it on Android 11 but still update?
    I had auto system update turned off in developer options, but still every week or so it would alert me that my security settings were out of date, but I wrote the comment you referred to before Android 12 was available for the n200, so I may have just ran system update
    2
    Has anyone tried on a DE2118 (tmobile) yet?
    Works just fine on the DE2118 if you get the bootloader unlocked.
    2
    Thanks, this ROM made me realize that I don't hate my phone, I hate OxygenOS.
    Everyone should hate OxygsnOS on non-flagship oneplus devices.
    Oneplus puts ZERO effort into optimizing OxygenOs for its budget devices.
    2
    Thanks, this ROM made me realize that I don't hate my phone, I hate OxygenOS.