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

Search This thread

endim8

New member
Thank you for this! I've been waiting for an official LOS build 😌

I couldn't find an issue tracker, so I'll report here:
When turning off the screen, the night light immediately stops instead of waiting for the display to fade out completely. It seems like it's listening for the power button instead of `android.intent.action.SCREEN_OFF`

also, the log is spammed with
943-1028 qdmetadata - pid-943 - E paramType 32 not supported

finally, i'm having an issue with the fusedlocationprovider:
 
Last edited:

zezinho7

Senior Member
Jul 31, 2018
57
21
fingerprint is better, but still not great yet.
again sometimes issues but no longer completely stopping
 

zezinho7

Senior Member
Jul 31, 2018
57
21
a new issue for me:
phone conversation with loudspeaker on:
i hear partner great but partner hardly me. sometimes hears me sometimes not. very unstable.
switching loudspeaker off everything immeadiately fixed

do you also have this issue?
 

zezinho7

Senior Member
Jul 31, 2018
57
21
another thing i noticed now:
if recording with the lineage recorder app and phone is > 30centimeter away the recording is very quiet.
only directly speaking into one of the 2 mics increases volume to an acceptable level. even then only with volume rocker at max.
do you also have this issue?
 

zezinho7

Senior Member
Jul 31, 2018
57
21
1. did somebody test a phone conversation via loudspeaker?

2.currently i assume it has something to do with noise cancelling function or some wrong mic config in the rom.

in speakermode usually mainly upper mic is used.
in earpiece mode usually mainly bottom speaker is used.
(micro 3 on back only for video recording?)

if speaking with ~ cm 5cm distance to one of the 2 phone mics it is possible to talk in speaker mode. also if one of the 2 mics is covered with a fingertip.
when moving phone about 10-15cm away suddenly voice disappears on the other side.
going back to 5cm distance again possible to hear what is talked into op8p mics.
both mics are cleaned, totally free of dust.

3. in the mean time updates c35 + c36 were released by oneplus. is it possible to upgrade or do updates brake los compatibility ?

this thread is not really alive, what's up?
maybe we can change this?
 
Last edited:

HolyHog

Senior Member
Jun 11, 2015
194
74
Alaska
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
You have to get Android 12 on both slots. Just OTA'ing to C33 won't work because you have only flashed Android 12 once. C35 and C36 are available on my phone and I flash all 3 to make sure I am set up right.
In summary flash C33, then C35, then C36 and you will be good to install any custom A12 or A13 rom.
 

mchridz

Member
Dec 16, 2018
6
0
another thing i noticed now:
if recording with the lineage recorder app and phone is > 30centimeter away the recording is very quiet.
only directly speaking into one of the 2 mics increases volume to an acceptable level. even then only with volume rocker at max.
do you also have this issue?
I have the same problem, how we can fix it?
 

typhonling

New member
Nov 8, 2022
2
0
I am having a huge issue where despite everything functioning as expected I am unable to make calls or text. Depending on the SIM Card (I've tried 4 different ones) calls will simply terminate before starting or they will terminate and I am also informed that I need to turn off airplane mode (it is not enabled). AFAIK that means it is still searching for a network, however nothing happens no matter how long I wait. I've tried just about every solution I could think including going back to OOS and starting over again but nothing has helped. The SIM cards are clearly being read and recognized as I am queried for their respective PINs and all information about the card in the setting menu is complete. Any help would be greatly appreciated.
Same problem here when I upgraded my phone (IN2020) from 18.1 to 19. I didn't want to clear the data so I made a lot of attempts.
For my phone, the final solution was to flash the latest fw and it solved the problem. The link is at #96, I flashed the IN2023 version. It works fine in IN2020.
I checked the band support by using Network Signal Guru. The 4G bands is consistent with IN2020, and the 5G band on the main SIM card is also running on band 41. This seems to indicate that there is no difference in band support from the original. But the secondary SIM card does not have a 5G signal right now, it should run on band 78.
But this little problem doesn't really matter, I'm happy that my phone has been reborn.
 
Last edited:

zezinho7

Senior Member
Jul 31, 2018
57
21
i reported call issue in loudspeaker mode (mic not working, issue with noise cancelling?) so many times now.
please other downloaders, c'mon, can you talk to other people in speaker mode without issues?
i can only call if loudspeaker is off.
 
i reported call issue in loudspeaker mode (mic not working, issue with noise cancelling?) so many times now.
please other downloaders, c'mon, can you talk to other people in speaker mode without issues?
i can only call if loudspeaker is off.
I use the google dialer instead. i have not had any issues with that one on loudspeaker. the native dialer is disabled for me so i cannot tell you.
 

zezinho7

Senior Member
Jul 31, 2018
57
21
thanks for your answer @kingjelle123
i tried now also google dialer and several other dialers without success. also diabling every magisk module without any effect.
if i try mic recording apps all 3 mics are working, the upper mic on the top is recording a bit more quiet, but not much difference.
so pretty strange that all 3 mics work on the device but still not possible to call in speaker mode.
it seems as if the noise cancelling is cutting the voice immediately. tests with bluesip's echo call test confirm my suspicion.

would like to make a twrp backup now that twrp is available for a12 and then try msm tool and upgrade to latest oxy and test there. but the question is if it it possible to get beakc to lineage os 19.1 then without loosing all data.

did anybody try this rom with the new twrp already ? whats your experience ?

br boris
 

[email protected]_

Senior Member
Oct 18, 2012
79
3
Hey. Guys I wanted to ask you for help because I'm not exactly sure what to do here:

I downloaded an update via oxygen updater IN2023_11_C.36
So.. can I update via system update or do I have to follow this:
https://wiki.lineageos.org/devices/instantnoodlep/fw_update

If the option is to follow this wiki link - I noticed step 3 says: boot up lineageOS recovery. BUT I don't have a lineageOS recovery.
So as a first thing I should:
1.Flashing additional partitions
2.Installing a custom recovery using fastboot

And after this the process will continue with the update from the link above?

My bootloader is unlocked and phone is rooted running on android 11, build 11.0.11.11.IN11BA, model IN2023

And one more question. Will my phone stay rooted after flashing LineageOS or not?
 

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 out 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:
    3
    If someone has a workaround to get past the "The current image boot/recovery have been destroyed" after flashing dtbo&recovery images please let us know. I am stuck with oos12 which has become intolerable to use nowadays.
    Any advice or suggestion is welcome :)
    Can you try flashing vbmeta from https://mirror.math.princeton.edu/pub/lineageos/full/instantnoodlep/20220825/?
    2
    Does someone have a cheat on installing gapps? I've tried all of them with installing alongside lineage or installing after a reboot. NikGapps, Opengapps, and MindtheGapps from 12.1 arm64. One of the major problems I see is that the play store is hanging.

    I am using mindthegapps without having any kind of issue so far.
    How to pass SafetyNet and user GPay?

    I used magisk to flash "safetynet fix" and "magiskhide props config" modules. After that you need to run props configuration via terminal (search for termux app in playstore) and change the fingerprint of your device.
    That's it. You can also use yasnac app from play store to see if your device can pass safenet attestation successfully.

    good morning, does 5 g, face unlock and fingerprint work on the oneplus 8 pro (EU)?
    5g and fingerprint are working fine. Never checked face unlock, so i can't tell.
    2
    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.