[ROM][OFFICIAL][instantnoodle][13] LineageOS 20

Search This thread
By:
Advanced…
samhhmobil

samhhmobil

Senior Member
May 25, 2017
490
251
Hamburg
Since the update to April/08 build, LOS does not read the SIM-card correctly and does not connect to the phone network (T-Mobile Germany). When booting it requests and accepts the SIM PINcode, after unlocking the phone it requests the SIM PIN a second time, and does not connect.

What's to do now???

samhhmobil

EDIT:
After 5 minutes waiting it did reconnect to the mobile network again. Now it's working normal. But that behaviour did look very strange in the beginning.
 
C

CurlyTemple

Member
Jan 26, 2022
24
3
osetiopica said:
I'm having the same problem with usb-c earphones.
phone - usb-c to aux adapter - aux earphones < is working good.
but
phone - usb-c earphones < is not working.
Click to expand...
Click to collapse
Unfortunately for me, the adapters available in my country have horrific sound quality, and I don't use wireless. I commented on the OnePlus forum here but who knows if they'll take notice: https://community.oneplus.com/thread/1560279 [Type C headphones not working after oxygen 12 OS]
 
Y

YuTendo

Member
May 21, 2022
14
4
I just sideloaded the most reason image (from lineage-20.0-20230401 to lineage-20.0-20230429).

The sideload worked as usual but after the reboot the GooglePlay Store keeped crashing. I performed a reboot and now my phone is in a reboot loop :(
Any advice? Thank you!
 
rodken

rodken

Senior Member
Jan 11, 2010
1,872
860
YuTendo said:
I just sideloaded the most reason image (from lineage-20.0-20230401 to lineage-20.0-20230429).

The sideload worked as usual but after the reboot the GooglePlay Store keeped crashing. I performed a reboot and now my phone is in a reboot loop :(
Any advice? Thank you!
Click to expand...
Click to collapse
Start from scratch and clean flash the most recent build.
-- In the event that the bootloop persists, clean flash back to the prior build.
-- Wait for the next build to be released.
 
  • Like
Reactions: YuTendo
Y

YuTendo

Member
May 21, 2022
14
4
Thank you for your help!

I flashed the image again (without factory reset) but the bootloop did persist. I flashed the the previous image and now it boots again -but the Google Services are broken. The Playstore keeps telling me that I am offline (which is not true).
I noticed that a new version of the MindTheGapps was released between my current image and the new one (current image 20230401, new image 20230429, new MindTheGapps-13.0.0 20230408). I assume this is related? How likely is it that I broke the Google Services permantly? (without doing a factory reset)
 
rodken

rodken

Senior Member
Jan 11, 2010
1,872
860
YuTendo said:
Thank you for your help!

I flashed the image again (without factory reset) but the bootloop did persist. I flashed the the previous image and now it boots again -but the Google Services are broken. The Playstore keeps telling me that I am offline (which is not true).
I noticed that a new version of the MindTheGapps was released between my current image and the new one (current image 20230401, new image 20230429, new MindTheGapps-13.0.0 20230408). I assume this is related? How likely is it that I broke the Google Services permantly? (without doing a factory reset)
Click to expand...
Click to collapse
Google Services are not broken.
-- You need to allow data access to both Google Services and/or Playstore under App Info.
 
  • Like
Reactions: YuTendo
Y

YuTendo

Member
May 21, 2022
14
4
rodken said:
Google Services are not broken.
-- You need to allow data access to both Google Services and/or Playstore under App Info.
Click to expand...
Click to collapse
Thank you! You are absolutely right. I have not thought of that at all. Everything works again :3
Just out of curiosity. Why were the data access permissions revoked? (I am sure that I did not do it.)
 
rodken

rodken

Senior Member
Jan 11, 2010
1,872
860
YuTendo said:
Thank you! You are absolutely right. I have not thought of that at all. Everything works again :3
Just out of curiosity. Why were the data access permissions revoked? (I am sure that I did not do it.)
Click to expand...
Click to collapse
You would have to consult the Lineage team for further discussions regarding that matter.
 
N

Neoxal

Senior Member
Aug 27, 2012
195
67
On the 20230429 build, I wasn't able to get the scan function in Google Drive app working. It would attempt to open Aperture and then just go back to Google Drive. I tried changing the default camera but that didn't help. I reverted back to 20230422 build and it is now working again.
 
C

corke2013

Member
Jun 9, 2018
7
2
Not sure if anyone is still having this issue but the notification to ask what to do when a USB cable is connected doesn't show up when connecting the phone to a computer (Already tried multiple different cables and computers, even android auto).

The "Use USB for" options are also all greyed out until you enable developer options and change "Default USB configuration" from its default state, "No data transfer", to something else like "File Transfer". You can then set it back to "No data transfer" and the notification comes up each time you connect your phone asking what you want to do but the moment you restart the phone it "breaks" and you have to repeat the process again.

Is this expected behavior? I would really like the default to be "No data transfer" and be asked via the notification what mode I want.

Thanks :)
 
C

corke2013

Member
Jun 9, 2018
7
2
corke2013 said:
Not sure if anyone is still having this issue but the notification to ask what to do when a USB cable is connected doesn't show up when connecting the phone to a computer (Already tried multiple different cables and computers, even android auto).

The "Use USB for" options are also all greyed out until you enable developer options and change "Default USB configuration" from its default state, "No data transfer", to something else like "File Transfer". You can then set it back to "No data transfer" and the notification comes up each time you connect your phone asking what you want to do but the moment you restart the phone it "breaks" and you have to repeat the process again.

Is this expected behavior? I would really like the default to be "No data transfer" and be asked via the notification what mode I want.

Thanks :)
Click to expand...
Click to collapse
Also worth mentioning that if you set "Default USB configuration" to something other than "No data transfer" and disable developer options it works across reboots but it's not ideal to have any option other than "No data transfer" as the default.

Additional information - fresh Lineage OS install using the latest version 20-20230603
 
C

CurlyTemple

Member
Jan 26, 2022
24
3
jabashque

jabashque

Senior Member
Feb 17, 2017
241
246
Nextbit Robin
LeEco Le Pro3
Hi all:

Sorry about the radio silence. I'm still using my instantnoodle, but I haven't really made any device-specific changes in quite some time. I probably will be working on this device again maybe 2-3 weeks from now, but till then, I'm mostly working on other things and playing games.

corke2013 said:
Not sure if anyone is still having this issue but the notification to ask what to do when a USB cable is connected doesn't show up when connecting the phone to a computer (Already tried multiple different cables and computers, even android auto).

The "Use USB for" options are also all greyed out until you enable developer options and change "Default USB configuration" from its default state, "No data transfer", to something else like "File Transfer". You can then set it back to "No data transfer" and the notification comes up each time you connect your phone asking what you want to do but the moment you restart the phone it "breaks" and you have to repeat the process again.

Is this expected behavior? I would really like the default to be "No data transfer" and be asked via the notification what mode I want.

Thanks :)
Click to expand...
Click to collapse
No, this shouldn't be expected behavior. Can you describe what devices you connect your phone to and how you connect them (e.g. Macbook Pro, using USB-C to USB-C cable)? I want to see if I can replicate this on my end, as I'm not really good at trying to search through another person's logs for the cause of the problem.
 
  • Like
Reactions: wawanRedblack, Neoxal and osetiopica
C

corke2013

Member
Jun 9, 2018
7
2
jabashque said:
Hi all:

Sorry about the radio silence. I'm still using my instantnoodle, but I haven't really made any device-specific changes in quite some time. I probably will be working on this device again maybe 2-3 weeks from now, but till then, I'm mostly working on other things and playing games.


No, this shouldn't be expected behavior. Can you describe what devices you connect your phone to and how you connect them (e.g. Macbook Pro, using USB-C to USB-C cable)? I want to see if I can replicate this on my end, as I'm not really good at trying to search through another person's logs for the cause of the problem.
Click to expand...
Click to collapse
So I've tried only with a normal USB A to USB C cable and have tried it both on a linux and windows computer as well as android auto. In each case the phone just charges and doesn't let me select any of the usb data transfer options as they are all greyed out.

I have tried different USB cables so its definitely not the cable that has an issue.

The only fix for me is enabling developer settings and changing the default USB mode like I mentioned before. You can then turn developer options off and the phone will work, but the moment you restart it will have the same issue.

Thanks for looking into it!
 
osetiopica

osetiopica

Member
Mar 5, 2018
25
2
I'm glad they added a battery charge control feature. Can I get reset the battery state when reaching the limit?
 
You must log in or register to reply here.

Similar threads

anishpratheepan
[ROM][OFFICIAL][instantnoodle][11] LineageOS 18.1
Replies
225
Views
48K
B
brezzz
firebird11
ROM[OFFICIAL][instantnoodle][11.0]**crDroid**[V7.14]
Replies
223
Views
45K
E
Ezzell
optimumpro
[ROM][11.0_r71]JAGUAR ONEPLUS 8 OFFICIAL V36 Updated september 8, 2023
Replies
512
Views
68K
optimumpro
optimumpro
jabashque
[ROM][OFFICIAL][instantnoodle][12] LineageOS 19
Replies
170
Views
15K
YukikazeMywaifu
YukikazeMywaifu
AvgPhoneUser
[ROM][11.0_r34][OFFICIAL][STABLE] ShapeShiftOS [instantnoodle]
Replies
70
Views
20K
rodken
rodken

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 1
    A
    AiM2LeaRn
    great rom, thanks for the development.

    only small "bug" problem i notice is that when in Landscape orientation (flipping the phone sideways) it seems the finger print sensor doesnt work correctly in landscape orientation. i noticed it when playing a game and trying to make a google play purchase while the phone was sideways, i end up having to authenticate using password rather than fingerprint when in "landscape mode". fingerprint works fine in "portrait mode"
    1693629361479.png
    View
  • 10
    jabashque
    jabashque

    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.

    2okPze5.png


    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 is lineageosroms[.]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
    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:
    View
    9
    jabashque
    jabashque

    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)
    IN2017 (T-Mobile) is unofficially supported, as that's what I did my device bringup against.

    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.
    View
    6
    jabashque
    jabashque
    AoD 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/+/347184
    View
    5
    jabashque
    jabashque

    Currently 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.
    View
    5
    jabashque
    jabashque
    Heads 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
    Hopefully the last two bugs will make it in time for next week's build. Not sure when I can get the first one merged.

    EDIT: all of them are merged. Expect to see them in next Saturday's build on 2023-01-21.
    View

New posts