yashsingh1/xdaforums huggingface dataset:
[Magisk] ilham_mochnoer:
###### LKT™ v1.4.3

###### PROFILE : Balanced

# START : 19-01-2019 12:17:55 AM

# =================================

# VENDOR : LGE

# DEVICE : LG-D838

# CPU : msm8974 @ 0.00 GHz (4 x cores)

# RAM : 3 GB

# =================================

# ANDROID : 7.1.2

# KERNEL : 3.4.113-Lineage-g29c8f95

# BUSYBOX : v1.29.3-topjohnwu

# =================================

# [✓] SOC CHECK OKAY

# [INFO] THIS DEVICE IS SUPPORTED BY LKT

# [INFO] SNAPDRAGON SOC DETECTED

# [WARNING] YOUR KERNEL DOESN'T SUPPORT POWER EFFICIENT WORKQUEUE

# [INFO] HMP KERNEL DETECTED

# [INFO] TUNING interactive

# [WARNING] YOUR KERNEL DOESN'T SUPPORT ADRENO IDLER

# [INFO] TUNING ANDROID VM

# [INFO] TUNING STORAGE I/O SCHEDULER

# [INFO] EXECUTING FS-TRIM

# =================================

# BATTERY LEVEL: 48 %

# BATTERY TECHNOLOGY: Li-poly

# BATTERY HEALTH: Good

# BATTERY TEMP: 33.3 °C

# BATTERY VOLTAGE: 3.7 VOLTS

# =================================

# FINISHED : 19-01-2019 12:18:33 AM

is that normal?

it should be 2.26 GHz cpu.
[Magisk] digdeep:
Im asking because I see that it supports Snapdragon 400, 410-412, 425, 430... but 415 is left out, is there any particular reason?
[Magisk] elraffa:
[MENTION=5033594]korom42[/MENTION] in 1.4.3 version it still fails detecting soc.. 1.3.1 version detect my soc well..

###### LKT[emoji769] v1.4.3

###### PROFILE : Battery # START : 18-01-2019 06:37:26 PM # ================================= # VENDOR : HUAWEI

# DEVICE : ALE-L23

# CPU : hi6210sft @ 0.00 GHz (6 x cores)

# RAM : 2 GB

# =================================

# ANDROID : 7.1.2

# KERNEL : 3.10.108-g959f965

# BUSYBOX : v1.29.3-topjohnwu

# =================================

# [×] SOC CHECK FAILED

# [INFO] THIS DEVICE IS UNSUPPORTED BY LKT # [WARNING] YOUR KERNEL DOESN'T SUPPORT ADRENO IDLER

# [INFO] TUNING ANDROID VM

# [INFO] TUNING STORAGE I/O SCHEDULER

# [INFO] EXECUTING FS-TRIM

# =================================

# BATTERY LEVEL: 92 %

# BATTERY TECHNOLOGY: Li-poly

# BATTERY HEALTH: Very Good

# BATTERY TEMP: 33 °C # BATTERY VOLTAGE: 3.9 VOLTS

# =================================

# FINISHED : 18-01-2019 06:37:56 PM
[Magisk] neverremembermyusername:
I think LKT ignores soc.txt if it thinks the other detection modes worked. At least, that's what it looks like from my cursory look at the code. soc.txt is only read if the SOC variable is empty, but in the case of the N6 it's not. In the case of the N6, it thinks it's figured out the SOC but it gets a result like "shamu" which is wrong.

Perhaps a change to make soc.txt, if it exists, take priority over the detection schemes would fix it?
[Magisk] korom42:
It can't read the available frequency on your device/ROM get in touch in tg group to figure out a workaround.

There is no particular reason,interactive parameters are not available in the current Project WIPE source or its forks for your SoC and some others as well.

Your SoC is hi6210sft which is KIRIN620 and it is not supported (at least for now).

Automatic SoC detection is prioritized to avoid mistakes and help newbie users.
[Magisk] Hemuli:
I read from your git log that you made sOmE cHAnGeS
[Magisk] psychoela:
[MENTION=5033594]korom42[/MENTION]
[Magisk] neverremembermyusername:
But in this case the automatic detection is wrong and the soc.txt is right but ignored.

Is there a way to specify the soc when the detection gets the wrong result?
[Magisk] NGOwner:
[MENTION=321344]karom42[/MENTION]

1.4.3 did not fix the problem Nexus 6 Custom ROM users are having. In my case, it seems the NitrogenOS developer did not follow the correct syntax in the source files that generate the cpu.prop file. The hardware section of the cpu.prop for the NitrogenOS 8.1.0 file looks like this:

When LKT parses the cpu.prop file, it returns:

And it seems that [MENTION=6263858]psychoela[/MENTION] and [MENTION=9690574]neverremembermyusername[/MENTION] are having the same issue. My guess is that if they check their cpu.prop files, they'll also see some weird line in the hardware section that's preventing fully accurate SOC identification.

It looks like our issue could be bypassed if there was a way for advanced users to override automatic SOC detection in the next release.

[NG]Owner
[Magisk] neverremembermyusername:
Indeed. My LKT.prop detects the soc as "shamu" rather than "tree)", though (forgive the corrupted characters, this file went from my phone through a circuitous Google Drive route into Windows, and something along the way goofed up the character encoding):

###### LKTâ„¢ v1.4.3
###### PROFILE : Battery
# START : 18-01-2019 10:49:14 PM
# =================================
# VENDOR : GOOGLE
# DEVICE : Nexus 6
# CPU : shamu @ 0.00 GHz (4 x cores)
# RAM : 4 GB
# =================================
# ANDROID : 8.1.0
# KERNEL : 3.10.108-gc7ca21a
# BUSYBOX : v1.29.3-topjohnwu
# =================================
# [Ã—] SOC CHECK FAILED
# [INFO] THIS DEVICE IS UNSUPPORTED BY LKT
# [WARNING] YOUR KERNEL DOESN'T SUPPORT ADRENO IDLER
# [INFO] TUNING ANDROID VM
# [INFO] TUNING STORAGE I/O SCHEDULER
# [INFO] EXECUTING FS-TRIM
# =================================
# BATTERY LEVEL: 70 %
# BATTERY TECHNOLOGY: Li-ion
# BATTERY HEALTH: Good
# BATTERY TEMP: 30.8 Â°C
# BATTERY VOLTAGE: 3.8 VOLTS
# =================================
# FINISHED : 18-01-2019 10:49:56 PM

From what I can see in the code, it tries to identify using /proc/cpuinfo, /sys/devices/soc0/machine, and getprop on ro.product.board, ro.product.platform, ro.chipname, and ro.hardware. I've grabbed the output of each of those from my N6 running LineageOS 15.1.

/proc/cpuinfo:

processor	: 0
model name	: ARMv7 Processor rev 1 (v7l)
BogoMIPS	: 38.00
Features	: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
CPU implementer	: 0x51
CPU architecture: 7
CPU variant	: 0x3
CPU part	: 0x06f
CPU revision	: 1

processor	: 1
model name	: ARMv7 Processor rev 1 (v7l)
BogoMIPS	: 38.00
Features	: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
CPU implementer	: 0x51
CPU architecture: 7
CPU variant	: 0x3
CPU part	: 0x06f
CPU revision	: 1

processor	: 2
model name	: ARMv7 Processor rev 1 (v7l)
BogoMIPS	: 38.00
Features	: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
CPU implementer	: 0x51
CPU architecture: 7
CPU variant	: 0x3
CPU part	: 0x06f
CPU revision	: 1

processor	: 3
model name	: ARMv7 Processor rev 1 (v7l)
BogoMIPS	: 38.00
Features	: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt
CPU implementer	: 0x51
CPU architecture: 7
CPU variant	: 0x3
CPU part	: 0x06f
CPU revision	: 1

Hardware	: Qualcomm APQ 8084 (Flattened Device Tree)
Revision	: 83a0
Serial	: 05dcd40111000000
Device	: shamu
Radio	: 6
MSM Hardware	: APQ8084 ES1.1

/sys/devices/soc0/machine:

Snapdragon

ro.product.board:

shamu

ro.product.platform seems to be empty.

ro.chipname seems to be empty.

ro.hardware:

shamu

Hopefully that can help troubleshoot the automatic soc detection routine for the N6 (at least running Lineage...it looks like the output is different depending on the kernel, at least in the some cases, though).
[Magisk] korom42:
[MENTION=4829973]NGOwner[/MENTION] [MENTION=9690574]neverremembermyusername[/MENTION] [MENTION=6263858]psychoela[/MENTION]

It would be better if you join telegram group for easier communication and file exchange https://t.me/LKT_XDA

I made some changes can you give this a try and report if it solves your issue, it should detect if the SoC is not a valid

Edit : try again with this https://drive.google.com/open?id=1rkjP07wvREx9hIYTp8zOzIRuapiFZWBN
[Magisk] NGOwner:
Success, donation on its way!

###### LKT™ v1.4.4

###### PROFILE : Balanced

# START : 19-01-2019 10:53:47 AM

# =================================

# VENDOR : GOOGLE

# DEVICE : Nexus 6

# CPU : msm8084 @ 2.65 GHz (4 x cores)

# RAM : 4 GB

# =================================

# ANDROID : 8.1.0

# KERNEL : 3.10.108-ElementalX-N6-5.22

# BUSYBOX : v1.29.3-topjohnwu

# =================================

# [✓] SOC CHECK SUCCEEDED

# [INFO] THIS DEVICE IS SUPPORTED BY LKT

# [INFO] SNAPDRAGON SOC DETECTED

# [WARNING] YOUR KERNEL DOESN'T SUPPORT POWER EFFICIENT WORKQUEUE

# [INFO] HMP KERNEL SUPPORT DETECTED

# [INFO] TUNING interactive GOVERNOR

# [WARNING] YOUR KERNEL DOESN'T SUPPORT ADRENO IDLER

# [INFO] TUNING ANDROID VM

# [INFO] TUNING STORAGE I/O SCHEDULER

# [INFO] ENABLING WESTWOOD TCP ALGORITHM

[NG]Owner
[Magisk] psychoela:
[MENTION=5033594]korom42[/MENTION] same here, let see the results:D thanks
[Magisk] drozo8o8:
This works with any gov like schedutil ?
[Magisk] immi803:
Yes, see OP, it works :D
[Magisk] elraffa:
could you take a look this soc please. would be great that my soc were supported since it has high battery drain even with microg and wakelocks controlled.
[Magisk] LNQ:
Hey [MENTION=5033594]korom42[/MENTION], awesome extension of the cli interface! I'd like to suggest an option to read the current profile.

Thank you for your work!
[Magisk] lexobys01:
Wow...never thought it will work on my crappy redmi 2 aokp :) ..
[Magisk] freg81:
It looks like LKT disables fast dormancy. I would like to keep this enabled. Could this be made configurable or optional?
[Magisk] dewois:
With Modul all my Widgets dont load, system settings dont open and back to last app in recent apps not work. Deinstall and all ok! First this Modul was a Placebo tweak now it is a franken-modul that do creapy thinks.
[Magisk] korom42:
It already does read the current profile both in command line and logs

Why would you do that? Fast dormancy is supposed to “reduce battery drain” caused by cellular network but if your network provider does not support it, it will increase your battery drain even more

hahaha
[Magisk] shamsul007:
love this module, I've set up profiles in tasker and I'm wondering if there's any way to remove the delay? I'd rather have settings applied instantaneously if possible.

many thanks
[Magisk] freg81:
Exactly my point. My network does support fast dormancy, and it reduces battery usage. Then it's completely contradictory that a set of tweaks which are supposed to reduce battery usage, disables this function for all its users.
[Magisk] korom42:
There's no delay when using direct commands like lkt 1, lkt 2 ...etc The mod itself takes about 20 seconds to be executed.

It's better to have it off considering most people in the world won't have this option. Even if you have it where you live now this won't be the case if you change your location often or travel ..etc

If you're still not convinced you can still navigate to

/sbin/.core/img/legendary_kernel_tweaks/system.prop

And change these lines to 1 then reboot

ro.fast.dormancy=1
ro.config.hw_fast_dormancy=1
ro.ril.fast.dormancy.rule=1

Or simply use terminal

setprop ro.fast.dormancy 1
setprop ro.config.hw_fast_dormancy 1
setprop ro.ril.fast.dormancy.rul 1
[Magisk] warchild98:
Will you add support for qualcomm snapdragon 630?

I use Nokia 6.1
[Magisk] paffo:
What a bad assumption. Every provider in my country supports this option from more than 7 years now (at least I was checking this that time) and everytime I am leaving my country I cant complain about battery consumption.
[Magisk] alediniz:
Same problem here. Is fixed on recent build?
[Magisk] lehuuhieu:
ok, thanks you.
[Magisk] BloodEdge:
I noticed this need Busybox, but phone reboot when installing busybox, and the magisk one will make Oreo stuck at kernel splash
[Magisk] korom42:
Use this one by Stephen (Stericson) .. it works fine for me
[Magisk] Forbiddendnb:
Without magisk version 5 dont work?

eXistenZ 8.0 have busybox or need install?
[Magisk] snake218:
Existenz 8.0 is Nougat based. Don't know if LXT V5 would work in N or is O exclusive.
[Magisk] korom42:
V5 is magisk module so you need magisk and it works on also on older firmwares MM/N/O

For busybox use the app I linked in noted from #2nd post
[Magisk] BloodEdge:
busybox said install failed
[Magisk] snake218:
Installation must be in /system/bin/, not in /system/xbin/
[Magisk] BloodEdge:
working !!!

very appreciate :good::good::good:

---------- Post added at 10:21 AM ---------- Previous post was at 09:46 AM ----------

damn, my magisk is dead, even after I reflash it
[Magisk] snake218:
Flash magisk unistall from recovery, then reinstall magisk
[Magisk] BloodEdge:
never mind, fixed :D:D:D
[Magisk] nurav666:
I'd like to add a vote for making the newest version flashable by TWRP since I don't have Magisk installed. I've been using the V4.2 and it seems to be working decently. Though, I'm still trying to determine if it's better than the "Xperience Engine" mod. So far, this LXT V4.2 has been performing well.
[Magisk] Erayh:
Hi guys,

I was wondering: does this mod work with romaur?

Cheers,
[Magisk] simax:
Hey,

What exactly are the doze tweaks and the disabled wake locks?

EDIT:

and is it known/normal that this breaks safetynet pass?
[Magisk] Sharp7:
V5.1 is worse than V5, it reduced battery life, the UI lags at times and performance in benchmarks is clearly worse while V5 didn't have any drawback, the new changes don't seem to be that good...
[Magisk] korom42:
Maybe next version for know it seems that majority is using magisk

Yes but I won't recommend any rom except stock firmware .. if still want it flash the mods cleaner zip before flashing this mod

For doze tweaks changed sleep_mode to 1 for greater battery savings

And no it doesn't break anything

V5.1 works great for my usage pattern a bit better than V5 (especially battery profile) but I appreciate feedback and will do more testing in different situations.

Make sure you keep same usage pattern if you're comparing different versions/profiles or as close as possible.
[Magisk] Sharp7:
I kept my usage patterns as close as possible and I only use the balanced profile, v5.1 felt worse and it gave worse results.
[Magisk] bobladure:
Hi,

Like we can't uninstall this mod only when older version than V5 (from you said:"Use this remover only if you're updating from older versions than V5").

How could i do for uninstall after tested v5.1

thanks
[Magisk] snake218:
Didn't notice lag, and battery seems better in 5.1 (bal) at least for me
[Magisk] korom42:
Good I created telegram group for beta testing if someone is interested t.me/XZ_LXT

Just disable or remove it from magisk app (modules section)
[Magisk] cnjax:
I was running akt on Nougat, recently upgraded to oreo. LG v20, installed latest lkt via magisk verified via viewing the lkt build prop. Using ka to view changes upon boot I can see the lkt parameters however after a few minutes the settings do not stick. Any help would be appreciated
[Magisk] D1stRU3T0R:
You should activate it because almost every carrier supports it. Don't look at Asian poor country's tho... But even there its supported
[Magisk] coombech:
Where do I find the custom ROM cleaner? Thanks
[Magisk] 4K2K:
Am I not supposed apply other tweaks such as changing the governor or limiting max frequency?

Before LKT, on my SD821 device, I used Alucard governor and limited max core to 1900(big) and 1593mhz(little.) rather than 2342 and 2118mhz.

After LKT on battery setting, I noticed that big core max frequency is set at full speed and being utilized quite often: 7.4% for simple web browsing. I am wondering if I can limit it using a tweak tool like Ex Kernel Manager or doing so may cause LKT to not function improperly.
[Magisk] 64ashg:
I kept my sd821 big cores at 1824, the little unlocked amd the gpu at 510. Because i saw the same behavior.

1824 big and 510 gpu is the max config of sd820lite. So i believe anything beyond its values is overclocked to somewhat diminished returns if you aren't gaming.
[Magisk] 4K2K:
It appears that with LKT, max cores are being used a lot more even for simple web browsing. I do think I should limit it manually but I am not sure if it will cause adverse effect.
[Magisk] 64ashg:
No 'adverse' effect here, running nlos 15.1 with the above settings on a oneplus 3t. No gaming whatsoever though.
[Magisk] cahyo_diegol:
can be combined with the extreme kernel ???
[Magisk] Abdou mike:
After installing LKT 1.4.5,

Facebook keeps crashing. I'm not sure why though.

Edit: Yes. What caused Facebook to crash is the new update. I uninstalled the module and it's back to working fine.
[Magisk] korom42:
No you are not supposed to change anything just let the Mod take care of the tweaking. If you are using an outdated version then please update to the latest v1.4.6 (02.02.2019)

You can use any kernel you want :)
[Magisk] sadiku:
Just want to ask if any recommend kernel you prefer to use?
[Magisk] crazix:
Does holydragon kernel for op3 interfere with lkt? Just curious.
[Magisk] smohanv:
Very clever mod. I am using it without any issue. You can add another menu for the users to change their device DNS with options to select between Cloudflare, OpenDNS or Adguard etc. Thanks.
[Magisk] tamjan:
Thanks for this module!

I'd love a feature for setting the profile to be used at next load. Use case: Setting the profile to performance at reboot (with tasker for instance) without applying the profile (as there isn't enough time to complete that) - and then go back to balanced or battery when the phone has booted and started everything (again using tasker). This to enable quicker (re-)boots. My phone can take two or three minutes to load all widgets and stuff.

Alternatively, the time after which lkt kicks in after boot could be user-tunable.
[Magisk] Hemuli:
Have you measured a difference in boot time between different profiles?
[Magisk] :
The tweaks are applied 60 seconds AFTER the boot. I doubt there's a difference.
[Magisk] tamjan:
Yeah well, I haven't measured in other ways than subjectively. And, it was slow before, when the profile was applied at once. Now, after the introduction of a delay, I think it's better. I haven't checked if it's even more better with an increased delay.

I wonder though, what "after boot" actually means here. My phone is encrypted; so is 60 secs after boot measured as 60 secs (or more) uptime reported by the kernel, or 60 secs after the loading of the module (after I've unlocked, that is)?
[Magisk] ToXiTe:
Probably not getting those obnoxious amount of RAM it needs.
[Magisk] djgarr:
Since last install (5 feb) , many apps dont work.

Chrome, maps, player pro....
[Magisk] edu24lal:
Still no deep sleep :/
[Magisk] 64ashg:
Install bbs and check out bbs thread to indentify wakelocks :)
[Magisk] edu24lal:
Whats draining battery is this module, with module no deep sleep ,without module everything is fine
[Magisk] meph02:
My deep sleep is very good for me with this module
[Magisk] otonieru:
not happening. its what you install together combined with this module that might actually the culprit.

using this module on 2 phones, both sleeping like baby on idle
[Magisk] das-angst:
Apologies if this is a dumb question but can this be used in conjunction with Advanced Charging Controller module on Magisk? From my understanding they shouldn't interfere with each other but better to ask.
[Magisk] pr1jker:
Tried it, but got some strange errors, like "com.google.acore" had stopped. Then machine very laggy. Dropped to twrp and disabled it. Everything back OK.

Samsung A6+ 8.0.0
[Magisk] famusc:
It's a couple of days I'm experiencing faster battery drain. I noticed that on the changelog it's stated that deep sleep fixes were removed on feb 4th. Could it be the reason of increased battery drain on idle?
[Magisk] edu24lal:
I have elementalx and universal gsm doze, dont know if thats the problem with deep sleep
[Magisk] pakudaboy:
i have elementalx purchased + installed and it's fine for me.

i had issue with gsm doze before, so probably remove that one and try again.
[Magisk] edu24lal:
Yeah i disabled doze and not deep sleep its fine...but now google play will use more battery so :(
[Magisk] serpent android:
Hi all.im on an lg v20 alpha omega rom oreo with mk2000 kernel will this work on me via magisk?thanks
[Magisk] Predatorhaze:
No deep sleep,high CPU freqs...this mod does the opposite way,drain your battery
[Magisk] :
I have problems with deep sleep too running the latest version of lkt.
[Magisk] korom42:
I don't know about bthe Pixel 2 but I use [MENTION=576495]kirisaku[/MENTION]ra EAS for my htc U11 and it's awesome. I would say avoid heavy featured kernels with experimental stuff if you're unsure then just stick to your stock kernel.

No we don't do that here. Magisk Repo is already full with plenty of modules that do this job.

Sorry buy I can't see the benefit of doing such thing. If your phone is too slow at booting maybe you should use a lighter ROM like LOS,slim etc.. also doing a simple factory reset once in while may help.

I can't help you without providing your LKT.prop logs
[Magisk] korom42:
Yes you can, it should be fine

People don't seem to understand that there is no deep sleep related tweaks in LKT anymore so it's not the module causing it for you, if you're using other mods with this then it's your problem. And [MENTION=7288053]Predatorhaze[/MENTION] keep in mind if you're just trash talking and hating then nobody gives a fu** . But if you actually encountered a bug then you should post a proper explanation with logs and screenshots as a proof at least then I'll will see what I can do, if not you will be ignored and this is for everyone else too.
[Magisk] sikita:
1.4.7. was fine, 1.4.8. drain problems. Does anyone have 1.4.7. saved?
[Magisk] smohanv:
It would be a one stop place where the users can have LKT tweak and also DNS change. Choice is yours.
[Magisk] k3dar7:
Look in your Download folder where is Magisk modules downloaded/saved and not deleted...
[Magisk] sikita:
Yes, unfortunately I deleted previous files there. :(
[Magisk] j-a-d-z:
LKT 1.4.7:

https://drive.google.com/file/d/1VJyNGv2tlhDLGmzHnDL5NvWoIpFi5OwA/view?usp=drivesdk
[Magisk] sikita:
Sorry, it seems that battery drain was not issue of LKT. Thank you for help.
[Magisk] EBeatFLA:
Just an FYI ... The guy has been posting all over the Axon 7 threads for months crying about his battery, with some off the wall claims about why it's messed up. It's obvious his battery has been failing and he's been instructed numerous times to change his battery. He refuses to listen to anyone, even though he finally admitted a couple of times his realization that his battery is most likely bad.

He's been banned twice from XDA already because he gets so enraged about it, that he attacks the devs in their threads as well as the moderators when confronted. Take any input he has about battery life and dispose of it. It's worthless to listen to him about the subject.
[Magisk] beeshyams:
[MENTION=5033594]korom42[/MENTION]

Thanks for your efforts

I am on the latest version arm64-v8a device (MiA1) with battery mode

In addition to your tweaks I wanted to reduce CPU /GPU frequency to have better battery life. Does this help or is it counter productive? Stock Android including kernel on Pie

Edit: sorry, just now saw a similar post about tweaking big/little frequency so I guess the same logic holds here but would appreciate your views

Thanks for your response in advance

Seeing you on line bumping [MENTION=5033594]korom42[/MENTION]
[Magisk] Predatorhaze:
Thank you for sharing lies,and get 15 thanks on a comment that only tells your story.And what you say here is not true.Even in china forum they report the same behavior as what i complained about.My battery is not bad,and it was not degraded.The battery was 10 months old when the problem occured.

My battery life is still 3-5 hours sot with the same battery so wthell are you talking about?Is this bad? Is it degraded?

You guys really dont know what your saying

Have a look how many users roll back to nougat because oreo give battery problems,and its not hardware related.

And then i have not spoken about the fact how the axon 7 community handles on switching to treble partition,not know wich vendor to use,outdated vendors,corrupted vendors,corrupted bootstack and the list goes on...but still though you guys are recommending these vendors and saying the corrupt messages are normal....

I use NFS with no problems,but lkt drains battery,thats how i experienced.
[Magisk] Pandemic:
Then uninstall it of yoi think that, quite easy ^^
[Magisk] nreuge:
Thx, good to know :)