[ROM][OFFICIAL][instantnoodle][13] LineageOS 20
- Thread starter jabashque
- Start date
AnierinB
Recognized Developer
Go to the Settings app, then navigate to Display -> LiveDisplay -> Display mode and select "Off" to disable automatic high brightness mode.
So I used MSM and so far it seemed to work, had to use my old junk laptop but everything seems to be in working order for now, SIM included.
Should I try my luck installing Lineage on it again? Or should I just cut my losses on that and save up for a GrapheneOS phone when my finances are alright? I'm super cautious on this rn
EDIT: Got into a long loop at the logo, but after clearing cache in recovery, it boots in, flashed and updating to A11, my current plan is to upgrade to A12 and await further steps from there to make sure I do everything right (fatal mistake last time was "fastboot flash boot twrp" instead of "fastboot boot twrp"), I know the step for LineageOS recovery but I don't know if there's a way to flash it without flashing recovery, in case something goes wrong again.
Should I try my luck installing Lineage on it again? Or should I just cut my losses on that and save up for a GrapheneOS phone when my finances are alright? I'm super cautious on this rn
EDIT: Got into a long loop at the logo, but after clearing cache in recovery, it boots in, flashed and updating to A11, my current plan is to upgrade to A12 and await further steps from there to make sure I do everything right (fatal mistake last time was "fastboot flash boot twrp" instead of "fastboot boot twrp"), I know the step for LineageOS recovery but I don't know if there's a way to flash it without flashing recovery, in case something goes wrong again.
Last edited:
Use the same thing you'd do for TWRP, fastboot boot recovery.img and it will boot instantly or within two minutes. Should it not, just reboot by holding a combination of hardware keys and your device will reboot normally.
Theoretically, I think this should let you adb sideload while not using LineageOS Recovery as a permanent recovery.
Just tried it a bit ago, the Lineage19/20 recovery didn't load (I did *update* to A12 but trying to flash recovery from there reverted me back to A11), so a thread suggested flashing a Lineage 18 recovery, which worked (flashed instantnoodle*p* by mistake but it was an easy fix at least after finding the right file), sideloaded a the relevant zip file and it worked (I'm on Lineage 19 and I'm not really in the mood to do more flashing anytime soon)
So now I'm on lineageOS (I used a MicroG build specifically) so that's good now. Not sure if I should go further and try to root it (not really confident in doing that but being able to better backup stuff wouldn't hurt), but for now it's fairly alright.
There are two ways you can root, by adb sideload (easier, safer in my opinion) or patched boot.img.
Using the adb sideload method, will install Magisk (the application) alongside the patch. You'll have to download and install the full application after #7 by tapping on the base APK from the launcher.
BY ADB SIDELOAD
- Connect your device via USB.
- Download the latest Magisk release on your computer (preferably GitHub).
- Rename it from magisk.apk to magisk.zip.
- Run adb reboot recovery.
- Select Apply update, then Apply from ADB.
- Using adb sideload <file>, sideload the file from #3.
- Reboot.
BY BOOT.IMG
- On your device, download the required boot.img.
- Open Magisk, then tap Install at the top right corner.
- Choose Select and Patch a File, then LET'S GO.
- Transfer the patched boot.img to your computer.
- Run adb reboot fastboot, then fastboot flash boot patched_magisk_boot.img.
- Reboot.
There is a safer way.
- Install Magisk.
- Patch boot.img
- Save it to PC
- adb reboot bootloader
- fastboot boot patchet_magisk_boot.img
- if loaded fine you are on root. Just patch system boot.img with Magisk.
Thats all.
If this step failed, you will get bootloop or stuck in fastboot mode . After that solution is either a clean reinstall or flash backup boot if you have it. Otherwise have to do dump img to extract correct boot.img.
I've just done a fresh install + MindTheGapps after a factory reset on OxygenOS 13. I noticed that the Gallery app doesn't seem to be affected by the Media volume (or any volume for that matter). When I use it to play a video, it plays sound at a constant volume, even if all volumes in the settings are set to 0. Does anyone else observe this?
Other apps (e.g. VLC) do seem to respect the media volume. In practice I probably won't use the gallery app much, but I thought I'd report it so that if it does turn out to be a wider issue, it can be included in the known issues overview.
I'm not entirely sure if this is an issue with this ROM, with GAPPS, or something else still.
Other apps (e.g. VLC) do seem to respect the media volume. In practice I probably won't use the gallery app much, but I thought I'd report it so that if it does turn out to be a wider issue, it can be included in the known issues overview.
I'm not entirely sure if this is an issue with this ROM, with GAPPS, or something else still.
Can someone help me out and backup their QCN, then upload it? I'm using an IN2017, but I'm willing to try any model as long as it's IN2013, IN2015, or IN2017.
forum.xda-developers.com
[GUIDE] Backup, edit and restore QCN. Fixing lost IMEI.
Introduction This is a guide to backup and restore the QCN, and to edit other's QCN in case you lost your IMEI and you don't have a backup of your QCN. There are other ways to do some steps (the most popular is via Fastboot) but I'm gonna...
forum.xda-developers.com
I just tried with the default gallery's video player, and I don't seem to have an issue with volume control at all.
Interesting. I just did another factory reset to no avail. I installed the Google Photos app because that's the one I tried for my battery health measurement on this same device before I flashed Lineage, and it suffered from this same problem. I might try a clean flash one of these days. Should it be safe to just wipe all partitions through recovery and then flash using the official install documentation?
You need to install the correct windows-device-driver for the OP8.
Or -- better -- don't use a windows desktop. IMHO one should use a Linux desktop instead, to avoid such trouble.
samhhmobil
Solved using Ubuntu terminal. I can't belive I went crazy for a while day. thanks a lot!
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
3Hi all, the chain of AoD related fixes has now been merged: https://review.lineageos.org/c/LineageOS/android_kernel_oneplus_sm8250/+/348992
Expect the next upcoming build on 2023-03-11 to have them.
According to https://review.lineageos.org/c/LineageOS/android_hardware_oplus/+/350382, it's under `/sys/class/oplus_chg/battery/mmi_charging_enable`. Other LineageOS devs are working on implementing charging control into LineageOS.1
Nevermind, this turned out to be a classic instance of PEBKAC: the update process unrooted my device, disabling the universal safetynet fix. Reinstalling Magisk resolved my issue. Sorry for the noise. -
9
DISCLAIMER
Anything you do to your own device is your responsibility and your responsibility only. You may NOT hold me responsible for any damage caused to your device.
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, 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.
The only official site with proper instructions to install LineageOS is https://wiki.lineageos.org/. Any instructions that come from anywhere else is not to be trusted at all.
You should especially distrust instructions from websites that try and impersonate LineageOS. One example of such a site islineageosroms[.]com.
Instructions
Scroll down to the 2nd post in this thread for installation and upgrade information.
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:8Telegram 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.
Upgrading from LineageOS 19.1:
If you are coming from LineageOS 19.1 AND using LineageOS 19.1 Recovery, then follow the instructions here to upgrade. Remember to flash Android 13 GApps if you used GApps previously.
We ship the required firmware (OxygenOS 13 11.F.13 as of 2022-12-31) in our OTA zips, so you do not need to install that firmware to both your slots on your OnePlus 8 before proceeding through the instructions.
Installing LineageOS 20 for the first time:
Prerequisites:
Ensure you've installed any version of OxygenOS/ColorOS 12 or 13 on the active slot on your device. The installation instructions recommend you be on OOS/COS 13 because on OOS/COS 12, touchscreen will end up not working while in LineageOS Recovery. However, you can still proceed while using OOS/COS 12 firmware; use the volume keys + power button to navigate recovery.
Instructions:
Once you satisfy the prerequisites above, then follow the instructions here to install LineageOS 20.
We ship the required firmware (OxygenOS 13 11.F.13 as of 2022-12-31) in our OTA zips, so you do not need to install that firmware to both your slots on your OnePlus 8 before proceeding through the instructions.6AoD blanking issue fix is up. I got some help from javelinanddart, who took a look at the LP1 command for our panel and deduced which part of it was causing the panel to blank.
Hoping to get it merged soon: https://review.lineageos.org/c/LineageOS/android_kernel_oneplus_sm8250/+/3471845Currently Known Bugs
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.
Light sensor readings do not filter out light coming from the screen
The light sensor is placed way too close to the top of the screen, so light bleed from the screen ends up affecting light sensor readings. On OOS, they use some algorithm to determine how much of the light detected by the sensor is actually coming from the display itself, and then subtract that value from the reading. We currently don't have anything to handle that for this LineageOS build. Some people have tried developing their own algorithm for this on the OnePlus 7 series of devices, but apparently, it doesn't work that well, so it was never brought over to the OnePlus 8 series of devices. In addition to that, novenary was reverse engineering OnePlus's implementation, but they stopped working on that since they no longer daily drive their hotdogb.
As such, expect Adaptive Brightness to be very much unusable, as the feedback loop caused by the light sensor sensing the light from the screen will result in Adaptive Brightness increasing the brightness all the time.
UDFPS (Under-display Fingerprint Sensor) doesn't work properly in 90° and 270° screen rotations
For both 90° and 270° (both of which are landscape orientations), the HWC layer for the UDFPS circle doesn't get excluded from the dimlayer, and as such, it doesn't end up illuminating bright enough to scan your finger. The circle is still positioned in the right place, so there could still be a possibility that one could figure out how to fix this.
UDFPS (Under-display Fingerprint Sensor) doesn't work properly in 180° screen rotation
For 180° (upside-down), not only is the auth dialog window in the wrong place, but the UDFPS circle doesn't even show up. This will not be fixed.
Mic input volume in speakerphone and video/audio recordings seems quieter than usual
This is still being explored, but it ends up seeming like the top mic's gain is too low or something? More details to come...
Ambient Display (Always-on Display) may not work properly if panel can't freely switch between 60Hz and 90Hz
(Fixed in 2023-01-21 build)
With Ambient Display enabled, when you "turn off" the screen, the panel will first show the Ambient Display info at normal brightness before trying to switch to LP1 mode. However, for instantnoodle, that mode seems to cause the panel to blank out entirely. It's only when Android decides to switch between 60/90Hz that the panel ends up turning back on, and that usually takes up to 6 seconds for that to happen.
This is under investigation still. Since the LP1 panel command's payloads are specific to this panel (Samsung amb655uv01), and since I have not found a datasheet for this panel, I may not be able to fix this. Either that, or I would need to prevent the LP1 command from running in the first place, and then see if that affects battery life.
EDIT: Fix is up: https://review.lineageos.org/c/LineageOS/android_kernel_oneplus_sm8250/+/347184
Thanks to @javelinanddart for taking a look and deducing which part of the LP1 command was causing the screen to blank.
While WiFi calling is enabled, VoIP calls (Google Voice, TextNow, etc.) starts stuttering frequently on WiFi
(Fixed in 2023-01-21 build)
A few hours after turning on WiFi Calling on the OnePlus 8, you'll likely notice that VoIP calls on apps like Google Voice and TextNow will seem to stutter while on WiFi, getting to the point where the call is unstable and neither party can really talk to each other. This bug is related to IMS making the cnd daemon from qcom's CNE request WiFi ext stats every two seconds. A race condition in the qcacmn kernel driver could end up happening during one of these requests, which potentially leads to every subsequent ext stats request timing out after waiting for 1.5 seconds. During that 1.5 second period, VoIP packets seem to get dropped entirely. This issue has been present since LineageOS 18.1, it seems.
I do have code that works around this race condition, but I don't think it's ready to review yet because I'm still trying to learn more about the qcacmn driver. I will update this space with more info when ready.
EDIT: Fix is up: https://review.lineageos.org/c/LineageOS/android_kernel_qcom_sm8250/+/347290
Thanks to Andrea for showing a way to work around this race condition that required fewer code changes.
CPU scheduler becomes reluctant to schedule tasks on the Gold and Prime CPU clusters 15-30 minutes after boot
(Fixed in 2023-01-21 build)
After rebasing on latest qcom sm8250 + Android Common Kernel source, we ended up getting a regression in how the CPU scheduler works. For some reason, 15-30 minutes after booting up, it ends up becoming very reluctant to schedule tasks on the Prime cluster, and (I suppose) somewhat reluctant to schedule tasks on the Gold cluster.
The fix for this is up: https://review.lineageos.org/c/LineageOS/android_kernel_qcom_sm8250/+/347313
Thanks to @V3NK4135H for their help in identifying the fix.
Ambient Display (Always-on Display) appears dimmer than usual if you have at least one fingerprint registered
(Fixed in 2023-03-11 build.)
With Ambient Display enabled, when the panel enters LP1 mode, the screen seems to dim by a significant amount. This is due to the biometrics HAL enabling dimlayer_hbm while listening for a fingerprint. Turning on dimlayer_hbm results in High Brightness mode being enabled, but with a dimlayer overlaying everything except for the UDFPS circle. This allows the UDFPS circle to shine at HBM levels of backlight while everything else remains at the original brightness level. However, if dimlayer_hbm is still on while the panel enters LP1 mode, then High Brightness mode turns off, but the dimlayer still remains. This results in everything being dimmer than it really should be.
I have a bunch of changes in the pipeline that not only fixes that, but also uses the dimlayer to mimic various brightness steps so that the perceived brightness in LP1 mode will match what your display had in ON mode. Will post updates in the thread once it gets merged.5Heads up, got a few fixes in the pipeline for the following bugs:
- Ambient Display (Always-on Display) may not work properly if panel can't freely switch between 60Hz and 90Hz
- thank you @javelinanddart for helping to identify the part of the LP1 command that blanked the screen
- While WiFi calling is enabled, VoIP calls (Google Voice, TextNow, etc.) starts stuttering frequently on WiFi
- thank you Andrea for helping with creating a simpler patchset than the one I initially wrote
- CPU scheduler becomes reluctant to schedule tasks on the Gold and Prime CPU clusters 15-30 minutes after boot
- thank you @V3NK4135H for pointing me toward the kernel commit that fixes this
EDIT: all of them are merged. Expect to see them in next Saturday's build on 2023-01-21. - 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).
