[ROM][OFFICIAL][instantnoodlep][13] LineageOS 20

[mattgyver]

It's strange because it doesn't happen with my ear buds.

Doesn't do that with my ear buds or Plantronics headset for work.

 

[Kuronosu]

BUG REPORT 1 @LuK1337

In the Sound & Vibration settings, you have the option to unlink the ring and notification volumes.

Once you do this, a fourth volume slider should appear in the volume panel, when you press volume up or down. However, it doesn't.

Meaning: once the ring and notification volumes are UNlinked, the only way to change the notification volume is through the Android settings menu.

I distinctly remember seeing an extra slider in this case. Maybe it was in OxygenOS, I'm unsure.


REQUEST: Can I be cheeky and also request considering an improvement (in my opinion)? Larger/longer volume sliders when volume up/down are pressed.

 

[Kuronosu]

BUG REPORT 2 @LuK1337

Searching for "Smart Lock" in Android settings does not show any results.

However, searching for e.g. "Device admin apps" shows the expected result, even though this setting is located within the same "Security" > "More security settings" where "Smart Lock" is also located.

Edit: I also found menu options that show up in the search, but can not be found after you click on them, even though you get transported to the actual sub-menu where they're apparently supposed to be located.

 

[rx149]

Is the 48MP sensor on the camera still locked? Just wondering considering the changes with the camera app and API with LOS 20.

Still would like an answer to this.

 

[kststz]

Disregard, managed to get LOS recovery to work by manually fastboot flashing all the partition images in the repo.
boot, dtbo, recovery, super, vbmeta
Had to wipe data after LOS 20 install, then it booted.

The correct order is the one you mention? Or it doesn't mater?

Also, how can I flash the file super_empty ?

 

[Scotsman828]

The correct order is the one you mention? Or it doesn't mater?

Also, how can I flash the file super_empty ?

fastboot flash super super.img
Order doesn't matter, just make sure that you flash all partitions before you reboot the bootloader.

 

[kststz]

fastboot flash super super.img
Order doesn't matter, just make sure that you flash all partitions before you reboot the bootloader.

Thank you for your reply!

I have been struggling all day, following the directions from the official site. But everytime I get stuck in the Warning about the Unlocked Bootloaded. It seems that the flashing of the recovery does not work and the phone ggets bricked. I've tried so many times, going back to MSM tool, reverting to stock, and again. But no success!

Can someone help? What were your steps exactly? Do I miss something or should I try your way flashing all partitions one-by-one?

Thanks in advance!

 

[justanutt]

Thank you for your reply!

I have been struggling all day, following the directions from the official site. But everytime I get stuck in the Warning about the Unlocked Bootloaded. It seems that the flashing of the recovery does not work and the phone ggets bricked. I've tried so many times, going back to MSM tool, reverting to stock, and again. But no success!

Can someone help? What were your steps exactly? Do I miss something or should I try your way flashing all partitions one-by-one?

Thanks in advance!

1. Download the following files from the directory named with the latest date here.
   • dtbo.img
   • vbmeta.img
2. Power off the device, and boot it into bootloader mode:
   • With the device powered off, hold Volume Up + Volume Down + Power.
3. Flash the downloaded image files to your device by typing (replace <...> with the actual filenames!):
   fastboot flash dtbo <dtbo>.img
   fastboot flash vbmeta <vbmeta>.img

Installing a custom recovery using fastboot​

1. Download Lineage Recovery. Simply download the latest recovery file, named something like lineage-20.0-20230202-recovery-instantnoodlep.img.
   warning
   IMPORTANT: Other recoveries may not work for installation or updates. We strongly recommend to use the one linked above!
2. Connect your device to your PC via USB if it isn’t already.
3. If your device isn’t already in fastboot mode, on the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
   adb reboot bootloader
   
   You can also boot into fastboot mode via a key combination:
   • With the device powered off, hold Volume Up + Volume Down + Power.
4. Once the device is in fastboot mode, verify your PC finds it by typing:
   fastboot devices
   
   If you don’t get any output or an error:
   • on Windows: make sure the device appears in the device manager without a triangle. Try other drivers until the command above works!
   • on Linux or macOS: If you see no permissions fastboot try running fastboot as root. When the output is empty, check your USB cable and port!
   • check
     TIP: Some devices have buggy USB support while in bootloader mode, if you see fastboot hanging with no output when using commands such as fastboot getvar ..., fastboot boot ..., fastboot flash ... you may want to try a different USB port (preferably a USB Type-A 2.0 one) or a USB hub.
5. Flash recovery onto your device (replace <recovery_filename> with the actual filename!):
   fastboot flash recovery <recovery_filename>.img
   
   
6. Now reboot into recovery to verify the installation.
   • Use the menu to navigate to and to select the Recovery option

I did this exactly. I did not flash any super.img.

I was able to flash in recovery and boot up.

 

[kststz]

1. Download the following files from the directory named with the latest date here.
   • dtbo.img
   • vbmeta.img
2. Power off the device, and boot it into bootloader mode:
   • With the device powered off, hold Volume Up + Volume Down + Power.
3. Flash the downloaded image files to your device by typing (replace <...> with the actual filenames!):
   fastboot flash dtbo <dtbo>.img
   fastboot flash vbmeta <vbmeta>.img

Installing a custom recovery using fastboot​

1. Download Lineage Recovery. Simply download the latest recovery file, named something like lineage-20.0-20230202-recovery-instantnoodlep.img.
   warning
   IMPORTANT: Other recoveries may not work for installation or updates. We strongly recommend to use the one linked above!
2. Connect your device to your PC via USB if it isn’t already.
3. If your device isn’t already in fastboot mode, on the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
   adb reboot bootloader
   
   You can also boot into fastboot mode via a key combination:
   • With the device powered off, hold Volume Up + Volume Down + Power.
4. Once the device is in fastboot mode, verify your PC finds it by typing:
   fastboot devices
   
   If you don’t get any output or an error:
   • on Windows: make sure the device appears in the device manager without a triangle. Try other drivers until the command above works!
   • on Linux or macOS: If you see no permissions fastboot try running fastboot as root. When the output is empty, check your USB cable and port!
   • check
     TIP: Some devices have buggy USB support while in bootloader mode, if you see fastboot hanging with no output when using commands such as fastboot getvar ..., fastboot boot ..., fastboot flash ... you may want to try a different USB port (preferably a USB Type-A 2.0 one) or a USB hub.
5. Flash recovery onto your device (replace <recovery_filename> with the actual filename!):
   fastboot flash recovery <recovery_filename>.img
   
   
6. Now reboot into recovery to verify the installation.
   • Use the menu to navigate to and to select the Recovery option

I did this exactly. I did not flash any super.img.

I was able to flash in recovery and boot up.

Thanks for the info!

I followed exactly the suggested steps. The problem was that I never saw the warning about the prerequisite of having OOS A13 installed before starting.

All good now!

 

[kststz]

Concerning the SafetyNet check, I thought it would pass when device is not rooted.

Any suggestion on how to pass the check (preferably without root)?

 

[Ag_Smith]

My phone powers off in my pocket. It doesn't power on after that if I press the power button. I have to boot into fastboot (volume buttons+power) and power on. The same sometimes happens when my phone is on a wireless charger in my car.
I tried to disabled "tap to wake", "tap to sleep" and "prevent accidental wake-up". But it didn't help.
Have somebody had similar problems? Any advice is appreciated.

 

[dude_se]

A good ROM thanks.
My only issues are that my Barclays banking app refuses to work with fingerprints, despite all the others working after using magisk, etc. The auto brightness seems hit and miss too I often have to keep turning it down as it's high brightness indoors. Lastly, since using dual SIM it seems that sometimes when I get a call I can feel the phone vibrate, but nothing comes up on the screen and no way to answer the call. I'll only be using dual SIM for a couple more days and I can still use my banking app that's the main thing, so not major issues luckily. Apart from that, everything seems pretty nice and smooth.
Just thought I'd share my experience of the ROM.

 

[desosav]

My phone powers off in my pocket. It doesn't power on after that if I press the power button. I have to boot into fastboot (volume buttons+power) and power on. The same sometimes happens when my phone is on a wireless charger in my car.
I tried to disabled "tap to wake", "tap to sleep" and "prevent accidental wake-up". But it didn't help.
Have somebody had similar problems? Any advice is appreciated.

I've been having the same issue as well. I always thought there was a hardware issue since noone else ever mentioned this. It is something that was happening with los 19 as well. I think that my device had the same issue when i was testing the pixelexperience build, but i am not 100% sure about it. Not sure what is causing it or how to prevent that from happening

 

[Aqyx]

Hi, I'm wondering if anyone can help me. I built this from source using the guide on the LOS wiki and I'm getting a bug with the GPS. It isn't finding the magnetic sensor. When I open Google maps, it doesn't show a direction. When I open compass apps they give an error "No magnetic sensor". Did I do something wrong when building it? Or is it another problem? Any help would be greatly appreciated

 

[Kuronosu]

Hi, I'm wondering if anyone can help me. I built this from source using the guide on the LOS wiki and I'm getting a bug with the GPS. It isn't finding the magnetic sensor. When I open Google maps, it doesn't show a direction. When I open compass apps they give an error "No magnetic sensor". Did I do something wrong when building it? Or is it another problem? Any help would be greatly appreciated

Just out of curiosity, can I ask why you don't use the official build?

 

[Aqyx]

Just out of curiosity, can I ask why you don't use the official build?

I enable call recording as it is legal in my state but LOS applies the rules per country