6
[ROM][OFFICIAL][instantnoodle][12] LineageOS 19
source link: https://forum.xda-developers.com/t/rom-official-instantnoodle-12-lineageos-19.4484561/page-5#post-87390547
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
[ROM][OFFICIAL][instantnoodle][12] LineageOS 19
[ROM][OFFICIAL][instantnoodle][12] LineageOS 19
So I threw 19.1 on my new phone (with MindTheGapps) and it seems to work pretty well. Things I've noticed:
-The first OTA update I clicked on booted into an OS without a functioning touchscreen. Installing latest (not sure if was the same) via recovery worked again. -Video over USB-c doesn't work with either HDMI or USB-c. As I understood the Oneplus 8 should support this? Could be a Oneplus issue, read reports it doesn't work on OO either. -Downgrading to anything 18.1 (to test the above) doesn't work. The recovery image won't show and installing from the newer one fails. But I think this expected?
Last edited: Today at 7:52 PM
So I threw 19.1 on my new phone (with MindTheGapps) and it seems to work pretty well. Things I've noticed:
-The first OTA update I clicked on booted into an OS without a functioning touchscreen. Installing latest (not sure if was the same) via recovery worked again.
That's... odd. Let me know if that happens again.
-Video over USB-c doesn't work with either HDMI or USB-c. As I understood the Oneplus 8 should support this? Could be a Oneplus issue, read reports it doesn't work on OO either.
I remember this used to work on custom roms using OOS 11 firmware and blobs (including when I was running my own builds of Lineage 19 from before we moved over to using OOS 12 oplus fw and blobs). I haven't been able to test this that well because all my equipment for connecting my phone to a display has suddenly become defective... but I can try to find out if I decide to purchase a USB-C to HDMI cable.
-Downgrading to anything 18.1 (to test the above) doesn't work. The recovery image won't show and installing from the newer one fails. But I think this expected?
Yeah, that's expected. Way too much was changed by OnePlus/Oppo on the backend side between OOS 11 and OOS 12.
Top Liked Posts
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
Downloads
Reporting Bugs
Please follow the instructions here to report your bug to our GitLab issues if you can, as it makes it easier for us to keep track of bugs and progress on fixing them.However, should you be unable to do so and must post your bug report in this thread instead, then please adhere to the following guidelines:
- DO NOT Report bugs if you're running a custom kernel, have installed Magisk, Xposed, or have done modifications to your device that touch any of the read-only partitions (with GApps being the only exception).
- As this is an A/B device, recovery will not run addon.d scripts. As such, try undoing all the modifications by reflashing the rom + GApps (if you used them) in recovery--no need to wipe data. After that, check to see if the bug is still there.
- 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
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:Telegram Chat:
I have a Telegram group that you can join if you prefer to chat that way, as opposed to posting on a forum thread. Join here.Supported models:
The only officially supported models are the following:- IN2010 (China)
- IN2011 (India)
- IN2013 (Europe/Asia)
- IN2015 ("Global"/NA)
IN2019 (Verizon) is not supported. VZW sensor configs are not bundled in this ROM, so accelerometer/gyroscope and magnetometer readings are going to be incorrect. In addition, battery gauge reading seems to be broken, based on one user trying this ROM on their IN2019 despite it being unsupported. I am likely not going to fix this anytime soon, as I do not have an IN2019 to validate my fixes against.
Minimum required firmware:
IN2010 (China)
Follow the instructions for IN2013. Another user (@cinnamonizer) tried running LineageOS 19 on ColorOS 12.1 C.32 firmware, and while it was working for the most part, their fingerprint sensor would periodically have trouble trying to recognize their finger. That problem seeemed to have gone away when they migrated to IN2013 firmware.IN2011 (India)
You need to be on at least IN2011_11_C.20 or later to run LineageOS. Otherwise, your touchscreen and audio will be broken if you try to boot into LineageOS.Grab your OTA zip from this thread. If you're upgrading from LineageOS 18.1 and don't want to wipe data, follow this guide to flash the updated firmware.
IN2013 (Europe/Asia)
You need to be on at least IN2013_11_C.20 or later to run LineageOS. Otherwise, your touchscreen and audio will be broken if you try to boot into LineageOS.Grab your OTA zip from this thread. If you're upgrading from LineageOS 18.1 and don't want to wipe data, follow this guide to flash the updated firmware.
IN2015 ("Global"/NA)
You need to be on at least IN2015_11_C.20 or later to run LineageOS. Otherwise, your touchscreen and audio will be broken if you try to boot into LineageOS.However, unlike IN2011 and IN2013, the last full OTA zip that OnePlus has ever released (as of now, 2022-08-28) was for IN2015_11_C.11. This shouldn't be a problem if you're coming from OxygenOS, as you can just apply incremental OTA updates until you're at least at version 11_C.20. However, if you're upgrading from LineageOS 18.1 and don't want to wipe data, then this will pose a problem. For that case, you can pretend you have an IN2013 and follow the instructions for that model instead; you can run the IN2013 firmware/modem on an IN2015 still.
IN2017 (T-Mobile)
So, I actually did my bringup work against an IN2017, so despite this model not being officially supported, I can at least say that I unofficially support this model with our official builds. However, I migrated over to the IN2015 firmware back on OOS 10 and OTA updated to OOS 11 from there, allowing me to use IN2013/IN2015 firmware on my IN2017. Since then, I'm currently running IN2013's OOS 12 firmware on my IN2017 right now.I've only ever tested running LineageOS 19 on IN2013/IN2015 firmware on my IN2017 OnePlus 8. As such, I will expect for you to run IN2013/IN2015 firmware on your IN2017 when using LineageOS. Follow the appropriate steps based on the answer to these questions: "Did you migrate to IN2013/IN2015 OOS back when you were on OOS 10? And if you did, did you flash the IN2013/IN2015 modem too before OTA updating to OOS 11 or later?":
- If you answered yes to both questions, then treat your IN2017 like it's an IN2013 or IN2015 (depending on which one you prefer) and follow the instructions for that model instead, as both models' firmware will work on your IN2017, modem included.
- If you answered no to either question, then you can still follow the instructions for IN2013 or IN2015, even if you're migrating over form IN2017 OOS 11/12, but you will lose cellular connectivity if you try flashing the modem from IN2013 or IN2015. Flash the firmware for IN2013/IN2015, but skip flashing the modem. Instead, extract the modem image from the latest IN2017 OTA (IN2017_11_C.41 as of 2022-08-28) and flash that on your IN2017.
Currently Known Bugs
Lowered brightness when switching between SDR color profiles
If you have turned your display off and back on at least once ever since booting up your phone, you will find that if you switch to any SDR or HDR display color profile at any point (such as going to Settings -> Display -> Colors and changing settings there, or watching an HDR video on YouTube), then your screen brightness will suddenly be lowered until next reboot. If you were watching an HDR video when the brightness got lowered, then you'll also find that if you switch back to an SDR color profile (by closing the video) and then switch back to an HDR color profile (by opening the video again, your brightness gets restored back to how it originally was. However, as soon as you switch back to an SDR color space (by closing said HDR video), then your brightness gets lowered again.This issue might be related to Pixelworks Soft Iris, but I have not yet looked far enough to figure out more details about why this is broken or how to fix it. If this issue annoys you enough, you can flash a modified boot.img that contains this change. This will break the ability to change SDR color profiles, but switching to an HDR color profile will still work and will not mess up your screen brightness. Download the boot image here.
Occasional 1-2 second freezes when waking the device from sleep
Sometimes, when you wake the device, you can see the display seemingly freeze for 1-2 seconds while it's fading in the lockscreen. Unfortunately, I don't know why that happens, and I don't think I'll be able to fix that myself anytime soon.How did you manage to update your firmware to OOS12? I tried the instructions on the lineage wiki page for the device and it led me to links that downloaded OOS11 firmware.
Head over to this thread and grab the OTA package for IN2013_11.C.33 to run the latest EU fw on your OnePlus 8. I would say that the oldest you can run on your OnePlus 8 is maybe 11.C.16?
(Also, note that you can run EU fw on devices from other regions.)
So, for some odd reason, whenever I try to do any of the "fastboot flash __ ___.img" commands, it says "Flashing is not allowed for Critical Partitions," but I have already unlocked my bootloader and done `fastboot flashing critical_unlock` and it was unlocked (when i try to do that command it says "Device already : unlocked!"). I have been totally puzzled by this. Is there something I have to do in particular or am I plum out of luck?
If you're following the instructions at https://wiki.lineageos.org/devices/instantnoodle/fw_update, you will notice that it tells you to "Go to “Advanced” -> “Enter fastboot”", along with a warning that "it cannot be substituted with “Reboot to bootloader”". The fastboot implementation in OnePlus's bootloader blocks you from flashing critical partitions no matter what, hence why the instructions tell you to tap on "Enter fastboot", which launches fastbootd instead.
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK