[ROM][OFFICIAL][instantnoodlep][12] LineageOS 19

[LuK1337]

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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

Instructions :

• https://wiki.lineageos.org/devices/instantnoodlep

Downloads :

• https://download.lineageos.org/instantnoodlep

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.

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:

 

[Infraviored]

I am so much looking forward to this

Are there any 'typical' android 12 issues in this ROM?
-HDR bug?
-fast charging?
-wireless charging?

 

[hens1234]

Great to see this launch for the OP8P. I have tried to install it but can't. The steps I have followed are as follows:-

1. Used the MSM tool to flash Oxygen OS 11.0.4.4. Ran the System Update local update option with the same OTA Update file twice.
2. Updated my phone using the local update option to IN2021_11_C.33.
3. Flashed the given gtbo on the instructions page and then the LOS 19.1 recovery. I cannot boot into the LOS 19 recovery.
4. I flashed LOS 18 recovery which i could boot into and tried sideloading LOS 19 but I cannot seem to boot into it.

What am I doing wrong @LuK1337? Please help if you have any clue. Thanks.

 

[spoeckes]

Great to see this launch for the OP8P. I have tried to install it but can't. The steps I have followed are as follows:-

1. Used the MSM tool to flash Oxygen OS 11.0.4.4. Ran the System Update local update option with the same OTA Update file twice.
2. Updated my phone using the local update option to IN2021_11_C.33.
3. Flashed the given gtbo on the instructions page and then the LOS 19.1 recovery. I cannot boot into the LOS 19 recovery.
4. I flashed LOS 18 recovery which i could boot into and tried sideloading LOS 19 but I cannot seem to boot into it.

What am I doing wrong @LuK1337? Please help if you have any clue. Thanks.

same for me, got a damaged boot oder recovery image error. did exactly what was written in instructions

 

[gildardozamudioperez]

Great to see this launch for the OP8P. I have tried to install it but can't. The steps I have followed are as follows:-

1. Used the MSM tool to flash Oxygen OS 11.0.4.4. Ran the System Update local update option with the same OTA Update file twice.
2. Updated my phone using the local update option to IN2021_11_C.33.
3. Flashed the given gtbo on the instructions page and then the LOS 19.1 recovery. I cannot boot into the LOS 19 recovery.
4. I flashed LOS 18 recovery which i could boot into and tried sideloading LOS 19 but I cannot seem to boot into it.

What am I doing wrong @LuK1337? Please help if you have any clue. Thanks.

This ROM is based OOS 12, read the changelog.

must be in OOS12 C33

 

[daderman07]

This ROM is based OOS 12, read the changelog.

must be in OOS12 C33

That's what he said, he updated the phone to oos 12 c33 and it didn't work...

 

[LuK1337]

That's what he said, he updated the phone to oos 12 c33 and it didn't work...

He messaged me on discord and when i checked his FW it was still on Android 11 so idk about that. Would suggest booting whatever recovery you can, be it 18.1 or even 19.1 and just flash correct fw.

(eu c33)

https://gauss-componentotacostmanual-eu.allawnofs.com/remove-1b428217a7d48f5d0391c9efe10e7b35/component-ota/22/08/01/5565841946b44ae49923d95bfd8bd680.zip

 

[desosav]

Same issue here.
Used msm tool to go back to oos 11.0.4.4 and then updated the device up to c33.
Flashing the dtbo and then the recovery images damage the boot.

I have also tried flashing recovery from unofficial los and twrp. Nothing seems to be working

 

[manu_jedi]

I also could not boot the recovery but after flashing the IN2023_11_C.33 in fastboot (no recovery needed) everything worked. So that was my mistake.

I have two bugs:
Displayport-alt is not working. Not that it was ever useful or that i needed it but at least the phone was mirrored to the monitor.

When the phone receives a touch input the phone switches to 120Hz by the default settings and after about 5s with no input it switches back to 60Hz. But when my screen switches to 60Hz the screen has a really small tint (white switches to a warmer white, better visible at low brightness) and when touched again it has the original color. Annoying when reading on websites with white background. I do not have "Display white balance" enabled or auto brightness. Eventually this is a hardware thing, i never used dynamic refresh rate.

Everything else is great, thanks.

Edit: Displayport started working after booting it while connected to a Monitor.

 

[keaheng]

Same issue here.
Used msm tool to go back to oos 11.0.4.4 and then updated the device up to c33.
Flashing the dtbo and then the recovery images damage the boot.

I have also tried flashing recovery from unofficial los and twrp. Nothing seems to be working

Msmtool,
local update to c33,
reboot,
local update to c33 again to make sure both slots are C33
reboot,
flash dtbo
flash recovery
Sideload LOS.

 

[LuK1337]

I also could not boot the recovery but after flashing the IN2023_11_C.33 in fastboot (no recovery needed) everything worked. So that was my mistake.

I have two bugs:
Displayport-alt is not working. Not that it was ever useful or that i needed it but at least the phone was mirrored to the monitor.

When the phone receives a touch input the phone switches to 120Hz by the default settings and after about 5s with no input it switches back to 60Hz. But when my screen switches to 60Hz the screen has a really small tint (white switches to a warmer white, better visible at low brightness) and when touched again it has the original color. Annoying when reading on websites with white background. I do not have "Display white balance" enabled or auto brightness. Eventually this is a hardware thing, i never used dynamic refresh rate.

Everything else is great, thanks.

You can enable "Force peak refresh rate" in dev options.

 

[keaheng]

I also could not boot the recovery but after flashing the IN2023_11_C.33 in fastboot (no recovery needed) everything worked. So that was my mistake.

I have two bugs:
Displayport-alt is not working. Not that it was ever useful or that i needed it but at least the phone was mirrored to the monitor.

When the phone receives a touch input the phone switches to 120Hz by the default settings and after about 5s with no input it switches back to 60Hz. But when my screen switches to 60Hz the screen has a really small tint (white switches to a warmer white, better visible at low brightness) and when touched again it has the original color. Annoying when reading on websites with white background. I do not have "Display white balance" enabled or auto brightness. Eventually this is a hardware thing, i never used dynamic refresh rate.

Everything else is great, thanks.

Edit: Displayport started working after booting it while connected to a Monitor.

Enable dc dimming fixed for me

 

[manu_jedi]

You can enable "Force peak refresh rate" in dev options.

Yes that is what i did, but it kills the idea of using low refresh rate to save battery.

Enable dc dimming fixed for me

Can you point me to where i can find that settings? The search doesn't return anything.

 

[LuK1337]

Enable dc dimming fixed for me

Not sure where you see dc dimming?

 

[keaheng]

Not sure where you see dc dimming?

Yes that is what i did, but it kills the idea of using low refresh rate to save battery.


Can you point me to where i can find that settings? The search doesn't return anything.

This app is working but requires root

 

[LuK1337]

This app is working but requires root

This is basically just forcing fod dimlayer on, which also will not let you use night light etc.

 

[zioloiso]

Is there any backup method to quickly restore everything after changing the rom?

 

[desosav]

Msmtool,
local update to c33,
reboot,
local update to c33 again to make sure both slots are C33
reboot,
flash dtbo
flash recovery
Sideload LOS.

Thanks fot your post. just tried that but it didn't help either.
I had to flash boot, dtbo and recovery images from c33 version (extracted using payload dumper) to make my device bootable.
As soon as los dtbo and recovery images are flashed, i get the following error "The current image boot/recovery have been destroyed"

 

[manu_jedi]

Thanks fot your post. just tried that but it didn't help either.
I had to flash boot, dtbo and recovery images from c33 version (extracted using payload dumper) to make my device bootable.
As soon as los dtbo and recovery images are flashed, i get the following error "The current image boot/recovery have been destroyed"

What i did (although it should result in the same as what you did):
download IN****_11_C.33 from https://forum.xda-developers.com/t/oneplus-8-pro-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4084315/
extract with payload dumper
follow https://wiki.lineageos.org/devices/instantnoodlep/fw_update from step 3

 

[daderman07]

Thanks fot your post. just tried that but it didn't help either.
I had to flash boot, dtbo and recovery images from c33 version (extracted using payload dumper) to make my device bootable.
As soon as los dtbo and recovery images are flashed, i get the following error "The current image boot/recovery have been destroyed"

Same issue for me...