[ROM][8.1][UNOFFICIAL][MP260&TP260] LineageOS 15.1 for LG K20 Plus

[Travisholt92]

I don't mess with the kernel, but I noticed a dramatic battery life difference between Travis's 14.1 and 15.1.... Under battery details it said the kernel was draining the battery then the os. I don't have that issue with 15.1. Must have been a bug but what do I know.

Battery life is decent on 15.1 but could be better. Stylo 3 plus is my daily driver now. Working on getting stable enough for Official Lineage then I can transfer compatible changes into the k20 plus trees.

 

[sidgallup]

Am i the only one having troubles getting camera to auto focus? i dont remember vahing this issue when i wsa on stock ROM. Is there a workaround? maybe installing another Cameara app or is it hardware related?

 

[mario0318]

Am i the only one having troubles getting camera to auto focus? i dont remember vahing this issue when i wsa on stock ROM. Is there a workaround? maybe installing another Cameara app or is it hardware related?

Stock ROMs would of course have the best software implementation for all the phone's hardware so camera app on stock is nearly flawless with the exception of it lacking some features.

The Lineage camera app has always buggy for me. In fact I don't really recall any custom ROM I've tested over the years to have a camera app that just works with no issues. Maybe once a long time ago on my previous phone. Regardless, whether on stock or custom ROM, I always install OpenCam for its customization, set of features, wide range compatibility that have worked fine on every phone I've used it on glaring a minor issue here or there, and best of all it's free to download.

Google cam is another potential candidate that some people have gotten to work but I can't ever seem to get a stable Google Camera app that doesn't have problems launching, completely hangs after any interaction, or gives you headaches trying out version after version.

 

[Brianswanson2011]

Am i the only one having troubles getting camera to auto focus? i dont remember vahing this issue when i wsa on stock ROM. Is there a workaround? maybe installing another Cameara app or is it hardware related?

Footej Camera is also a great alternative from the play store, it had allot of features and is compatible with allot of phones,

Update, Ok Travis STOCK SUCKS!

It is so buggy! And my device only charges at 240mah! Wow so I have made my decision, you are the best, you really optimized this rom to be amazing, there are things I can do on this rom that I took for granted till I went stock.

A HUGE THANK YOU TRAVIS ????

Thanks Travis for everything

 

[supermario2360]

Still hanging in there

Amid all the things going on, I still fond joy in this ROM. Just wanted to peek in and say thanks and cheers! Hope all is well Trav

 

[mario0318]

Amid all the things going on, I still fond joy in this ROM. Just wanted to peek in and say thanks and cheers! Hope all is well Trav

Likewise from the other mario. These stickler meseeks still on the K20 miss your updates. Existence is pain.

 

[supermario2360]

True Chainz

Ell yeah other Mario! Sorry to dilute thread even further, however I am looking into compiling ROMs from source and may make an attempt soon to make it happen for android 11... I'm a complete newbie to it but I do have YouTube on my side (; Anywhoo, take care 'yalls and God bless! :good::good:

---------- Post added at 04:00 AM ---------- Previous post was at 03:48 AM ----------

I also began writing init.d scripts to further enhance the wonderful experience Travis provided these little tweaks and modifications under the hood are furthering my exp. I have a pretty good understanding of the components of the os; esgetit

 

[cvmg333]

Thank you Travis for this wonderful Rom, coming from a Google Nexus phone, i did not expect the same class of community support with this device, but you have done an excellent job with it, battery last nearly like the oem Rom, android feels fast after several months with a lot of installed apps, (have to froze a few i did not use to often, remember our phone is a simple snapdragon 400 series), no problems with cellular network, bluetooth, and wifi, only gripe is (and asking anyone if you have this, and how to solve) with headphones, i feel volume to loud, if i decrese volume even at minimum there is no difference in calls and ringer or notifications sounds, when listening music its normal as any other phone (no glitch), i am happy with this phone thanks to you, using magisk and xposed as always, do you know any way i can try to solve this?
Thank you.

 

[mario0318]

...only gripe is (and asking anyone if you have this, and how to solve) with headphones, i feel volume to loud, if i decrese volume even at minimum there is no difference in calls and ringer or notifications sounds, when listening music its normal as any other phone (no glitch), i am happy with this phone thanks to you, using magisk and xposed as always...

Backup first then tinker with the mixer volume xml files, in /vendor you'll have audio_policy_volumes.xml and default_volume_tables.xml. You can edit the volume curves and (i haven't tried this yet) maybe add an extra line to the parameter set in question so as to create a more subtle volume increase/decrease and make the oft annoying experience of having almost no loudness to sudden loudness more tolerable.

In these files, you can increase the max and min volume curves. The step index points go from 0 to 100, with the volume attenuation curve points going from -9000(min vol) to 0(max vol). So at 0 you'll want to set a low attenuation, probably not -9000 as that is completely silent. Likewise at point 100 you may not find the loudest attenuation of 0 desirable. It may be that for the headset or speaker, at index 100, a level of say -1500 might be enough. The points in between would form the overall curve, so at index 80 you might want -2800, index 30 -5000, index 10 -6800.

You'll find the values in nested sets each controlling a device audio channel and output.

 

[cvmg333]

Backup first then tinker with the mixer volume xml files, in /vendor you'll have audio_policy_volumes.xml and default_volume_tables.xml. You can edit the volume curves and (i haven't tried this yet) maybe add an extra line to the parameter set in question so as to create a more subtle volume increase/decrease and make the oft annoying experience of having almost no loudness to sudden loudness more tolerable.

In these files, you can increase the max and min volume curves. The step index points go from 0 to 100, with the volume attenuation curve points going from -9000(min vol) to 0(max vol). So at 0 you'll want to set a low attenuation, probably not -9000 as that is completely silent. Likewise at point 100 you may not find the loudest attenuation of 0 desirable. It may be that for the headset or speaker, at index 100, a level of say -1500 might be enough. The points in between would form the overall curve, so at index 80 you might want -2800, index 30 -5000, index 10 -6800.

You'll find the values in nested sets each controlling a device audio channel and output.

Will try, thank you :good:

 

[supermario2360]

Dang Mar, you got some skillets

 

[supermario2360]

I did some digging and Trav, you did some great work! Lineage 16?!? Anywhoo wanted to share a script to change GPU default MHz to 270 for slight power savings using msm adreno tz governor...

#!/system/bin/sh

#
#set power default power level to lowest frequency
#

echo 4 > /sys/class/kgsl/kgsl-3d0/default_pwrlevel

 

[NuttyGlock]

Camera stopped working

Hello, I do not know if someone else fails this but I got into the camera application that it brings by default and it tells me camera stopped working, to someone else that this happens?

 

[cvmg333]

Hi, no problems here with camera, but i use open camera the most, more adjustments than lineage camera.

 

[RebelLion_]

Hello, I do not know if someone else fails this but I got into the camera application that it brings by default and it tells me camera stopped working, to someone else that this happens?

Try dirty flashing lineage and using open camera as suggested. It should be the default for custom ROMs really as it seems to be the most universally compatible camera app

 

[626jose]

Hi i just installed this rom its great i read through all the posts to see if anyone else is having issues passing safety net with magisk ive tried everything and cant get it to pass had it pass basic once but not cts do i need an older version of magisk i dont know much tia for any help

 

[mario0318]

Hi i just installed this rom its great i read through all the posts to see if anyone else is having issues passing safety net with magisk ive tried everything and cant get it to pass had it pass basic once but not cts do i need an older version of magisk i dont know much tia for any help

Did you figure this out by now? This is a late reply but I'll post it for anyone else. All you need to do to ensure safetynet passes even with magisk 21.1 with manager 8.0.3 (314) or manager debug build aka canary, as well as with edxposed installed, and without having to format /data BUT be prepared to reset all of your Google apps and its account link in your device. You'll see why in the steps below.

Go boot into recovery and make a full nandroid backup then proceed to wipe /system, but to make it easier on you before you wipe be sure to have either in the phones external SD or a usb mountable drive your lineage rom zip, opengapps zip for 8.1 on arm64 with your choice of package type. And lastly have a copy of the latest stable magisk zip which will be installed LAST AND AFTER BOOTING TWICE INTO ROM. The order for this is absolutely crucial or you'll have to reset Google Play Services to not only get SafetyNet to pass but also be recognized as Play Certified.

Once /system is wiped, again no need to wipe /data, you'll need to run this command on the recovery terminal with /data mounted prior to running it. This is where you'll want to move any backups containing anything Google that may be in your internal storage and copy all of it unto any external drive. Then in the terminal type exactly as shown:

find /data -iname '*google*' -exec rm -rf '{}' \;

This will seek any and all files in data containing the term Google, so if you've got backups saved on internal storage with anything Google related, move them to your external drive BEFORE running this command. It should take a second or two for the command to execute and complete. No errors or warnings or any text should come up. If it does, inspect the whole command for mistyped characters. Once that finishes, REBOOT TO SYSTEM.

DO NOT INSTALL any gapps or magisk zip nor restore any boot or system images. The intention is to have a clean system without traces of Google app, framework, and play services remants that will either give you grief with nonstop 'x App Has Stopped' and the potential of majorly screwing the system with manual installations of Google play and framework apks which will assuredly be versions not fully compatible with the device and rom. You're better off starting with a clean slate and just delete all Google files from the phone then after booting once into lineage system, reboot back into recovery and now go ahead and install the openGapps zip. Personally I use the aroma package despite being the largest, for its graphical installer wizard while in recovery environment. Makes it easier to deal with what to install and what stock apps you want to keep or remove. The other packages allow the same customization but they require a text config file prior to installation. Your choice.

With opengapps installed, reboot again into the rom. Don't install magisk yet. You may install Magisk manager while in the rom though to get any of that set up but without magisk in boot image it won't do much yet. The idea is for Google to set up and gather that the system, though it is unofficial and flagged debuggable it is nonetheless "unrooted". With Google set up DO NOT LOG IN TO ANY APP YET, you may notice the play store reading the device as not certified. That's fine. But if you use Google Pay DO NOT LOG INTO IT TILL AFTER THE NEXT AND FINAL STEPS.

Lastly, and not too sure if the order for these final steps make any difference but go ahead and download and Magisk Hide Props Config module and any other module you might want to install when you boot back into recovery. This could include the latest Riru v23.1 and the edxposed framework v0.5.1.3 zips. Optional and again not sure if this was entirely crucial to install in recovery in a single sweep. I'm leaning towards it not being necessary. Anyway, boot into recovery and install the Magisk zip, once done swipe to wipe dalvik/cache and boot into the rom.

Install or make sure to set the play services and store and framework apps on magisk hide. Then install or set up the Magisk Hide Props Config module and set the fingerprint from the list (main menu option 1) to the LG TP260 (submitted by yours truly) and then ensure the sensitive props (main menu option 4) are all set to their safe counterparts and not their sensitive. This is done by magisk by default but from time to time any discrepancy may arise where maybe one such prop isn't properly hidden.

With that reboot once again into system rom and install Riru and edxposed, and edxposed manager (latest is pre v4.6.0) and after installed open and set the manager settings to enable Pass SafetyNet and Force client side verification. Then reboot again and make sure both magisk and edxposed managers are hiding Google Play Services, Play Store, Google Services Framework, and Google Pay. On magisk, you need to select to expand the app components in Magisk Hide to select all of the options which I believe is necessary. Otherwise it will merely select one or two components and there is a chance for any such component to leak out and determine the device as rooted.

This has worked for me and amazingly got Google Pay not detecting root, Play Store reading the device as certified, and with edxposed framework and accompanying modules, and all this without the HiddenCore module which only fakes SafetyNet status to magisk and a few other apps. I'm passing rootbeer fresh, SafetyNet check apps, and Google Pay among other annoying apps that check for root. Delicate process but very much possible.