yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] XDleader555:
I've encountered this once or twice, but haven't been able to reproduce it. If you can share your settings or even grab a logcat (I noticed adb still runs) then we can get this problem fixed fast.

EDIT: seems msm_hotplug causes the black screen. What a trouble maker. Switch to lazy plug or bricked hotplug and see if that solves your issue.

EDIT2: So it seems lazy plug isn't running to it's full potential right now. I forgot to enable state notifier, so the hotplug never really sleeps. when I do enable it, we get the same crashing issue as msm_hotplug. Right now afaik bricked hotplug isn't affected. I'll look into a fix.
[X Style (Pure) Android Development] lilcdroid:
So am I correct in assuming the interactive governor is supposed to act like the performance governor. It's at max frequency constantly so my profile tweaks are useless. Haven't had a chance to get a good feel for it yet but it is smooth.
[X Style (Pure) Android Development] XDleader555:
Yea I noticed that too. I'll try pulling in a different version of the interactive governor.
[X Style (Pure) Android Development] creeperlwd:
Is it normal that 768MHz is the lowest freq you can select in cpu settings? Any setting lower or higher just puts it back at 768.

E: just found out this was caused by vdd restriction

Other than that it was off when I took it out of my pocket a few times. Will attach logcat tomorrow because rebooting makes too much noise (vibrations)

E2: Forgot to thank you for your incredible work. First time with 4h+ SOT !!!!!
[X Style (Pure) Android Development] XDleader555:
Let's take it nice and slow

05/24/17 - 10:16PM - v1.7

Cleaned source code tree

Confirmed Lazyplug and msm_hotplug suspend correctly with the screen off

REVERT: Update linux from 3.10.102 -> 3.10.105

REVERT: Moved msm_hotplug to system_wq

REVERT: Interactive CPU governor pulled from Pixel source

REVERT: zRam, zSwap, zMalloc Updates

REVERT: Overclocking/Underclocking (Just temporary, ran out of time)

I've cleaned up the code tree, and I

think

I've found the source of our problems, and I've left it out. I'll check another time, but here's the commit if anyone is interested: https://github.com/nathanchance/bullhead/commit/e6288ede428470e825f37b198415e0318c10c566

I've also carefully looked at the cherry picks for the interactive governor, so now it's working again. I need someone to test if it's working correctly (scaling up and down, and no black screen issues).

Also anyone else getting < 2% per hour drain with lazy plug? (and that's without the hotplug going into suspend mode) I'm digging it.

Downloads at the same place: https://xdaforums.com/devdb/project/?id=20678#downloads

EDIT: I'm just retarded at merging. Missed a check which caused a pointer to go null.
[X Style (Pure) Android Development] lilcdroid:
I never had an issue with black screen so can't comment on that. Interactive is scaling properly now. Huge kudos. We'll see how lazy hot plug works for the duration of my night shift but for the last 20 minutes it is showing great idle time.

Edit: Lazyplug is giving me audio stutter with screen off while listening to a podcast. Bricked is working fine though.

Edit: disabled hotplug, rebooted and re applied Lazyplug the stutter is gone and running smooth.
[X Style (Pure) Android Development] dzidexx:
[MENTION=3623188]XDleader555[/MENTION]

Thanks for yours work.

Hi, flashed last build, did some tests with Kernel Adiutor.

Default after flash are interactive+lazy plug.

Interactive+msm hotplug - can't set six cores online.

Interactive+bricked - can do it.

Cant set hybrid, permissive back to enforcing after restart.

Didn't have freezes with any yours​ build.

Some logs, Catlog record & kernel adiutor.
[X Style (Pure) Android Development] xgerryx:
Why am I losing root when I flash this?
[X Style (Pure) Android Development] dzidexx:
Because you changed boot(modified by root).

Flash magisk or supersu again. [MENTION=4111023]xgerryx[/MENTION]
[X Style (Pure) Android Development] XDleader555:
Seems kernel aduitor doesn't recognize the max_big_cpu_online variable. Not sure if this is fixable through the kernel. Did it used to work before?

Hybrid mode was removed because it doesn't actually work. A few posts back I showed that auto sleep never kicks in. Panel mode is sufficient.

As for permissive, not sure what you mean. Are you using set enforce 0? That command is temporary on every kernel. Let me know what exactly you're doing with permissive mode and how you're getting to it.
[X Style (Pure) Android Development] XDleader555:
You shouldn't lose root afaik. What rom and root are you using?
[X Style (Pure) Android Development] xgerryx:
[MENTION=3623188]XDleader555[/MENTION], Using ViperOS right now with Magisk. It also happened when I was on CRdroid, also Magisk. Flashing Magisk after I flashed the kernel didn't help either, either immediately or after reboot.
[X Style (Pure) Android Development] smalldroid34:
Thank you for this!
[X Style (Pure) Android Development] tech_infinity:
Thanks a lot for this kernel [MENTION=3623188]XDleader555[/MENTION]

And the Information especially the detailed changelog on the 1st page is very helpful :)

Keep the good the work up!
[X Style (Pure) Android Development] dzidexx:
This log: 2017-05-25-default.txt is after 1st boot. KA installed only to check default settings: interactive+lazy, all six cores still online.

After changing with KA only 4 cores(max) can be online.

Setenforcing 0 is only until reboot. I'm on RRemix - there is switch in RR configuration. It is not important. I don't need it now.

Intelliactive also has some bugs. Time of Deep Sleep big cores is different than little(maybe KA has bugs).

Now i'm on wheatley+bricked.

Do you suggest any other kernel manager?

ExKM I did try and prefer KA.
[X Style (Pure) Android Development] XDleader555:
Small update

05/25/17 - 8:14PM - v1.7.1

Fixed overclock frequency not showing

Fixed enabling/disabling of state_notifier in tuning apps (turns off hotplug suspend)

converted msm_hotplug to use state_notifier I need to touch up on C

I haven't gotten around to fixing anything big, just the obvious things that broke after the code cleanup.

Downloads ala https://xdaforums.com/devdb/project/?id=20678#downloads

EDIT: Update pulled. I seem to have broke lazyplug and bricked hotplug while keeping msm_hotplug good. I should really test these more thoroughly.

EDIT2: Uploaded fixed build. *fingers crossed*
[X Style (Pure) Android Development] dzidexx:
Flashed​, no bugs.
[X Style (Pure) Android Development] DarwinJ94:
Just flashed latest version with current nightly of RR and works good no bugs. Wich governor you guys recommend me to use?
[X Style (Pure) Android Development] Sebeq1234:
I'm testing now "bricked" min cores 1 max 5, big cores - zzmove, little - wheatley

Ultra smooth and battery good :)
[X Style (Pure) Android Development] XDleader555:
05/26/17 - 3:38AM - v1.8

UNREVERT: Update linux from 3.10.102 -> 3.10.105

UNREVERT: zRam updates

disabled zSwap (I don't think anyone uses this, correct me if I'm wrong)

converted msm_hotplug to use state_notifier

converted bricked_hotplug to use state_notifier

Not much change here. Flash if you want.

Downloads: https://xdaforums.com/devdb/project/?id=20678#downloads
[X Style (Pure) Android Development] dzidexx:
Thanks,

I have 1.7.1 for 8 hours, battery at 90% - I didn't test it to much!

Wheatley + bricked hotplug(1, 6, 2).
[X Style (Pure) Android Development] GchildT:
Flashing 1.8 now! Thanks!
[X Style (Pure) Android Development] creeperlwd:
I'm still having the issue where my phone randomly turns off overnight or in my pocket, a logcat from 1.7 is attached. I just flashed 1.8 will post again tomorrow with a logcat from 1.8 if it happens again.

logcat: https://drive.google.com/open?id=0B3IzYu3saG9jWU9zTmhGMEZHZEU

the file is too big to attach it to this comment

this is from a normal boot after it being off (caused by the bug)
[X Style (Pure) Android Development] dzidexx:
[MENTION=6757160]creeperlwd[/MENTION]

Which rom do you have, which cpu governors did you set(big/little)?
[X Style (Pure) Android Development] creeperlwd:
zzmoove big/little

Lazyplug

Zen i/o

AICP 05/24 Build

Also cpu/gpu underclocked and using simple_ondemand for gpu
[X Style (Pure) Android Development] dzidexx:
Try:

Don't underclock - leave default min 384 and max for both, gpu default too - msm adreno.

Lazy plug or bricked hotplug.
[X Style (Pure) Android Development] creeperlwd:
Set it to that, thanks
[X Style (Pure) Android Development] branran:
How stable is this kernel? I've been lurking since the start of the thread but too scared to test it as a daily driver.
[X Style (Pure) Android Development] XDleader555:
I'll need the last_kmsg after it randomly turns off.

you can find this at /sys/fs/pstore/console-ramoops (it's a text file)

You can try upping the underclock up one frequency. Your phone might not be able to go that low.

Rather stable at this point. Fixing a bug here or there. Just flash it, if it doesnt work, then flash your rom again to revert.
[X Style (Pure) Android Development] rayparlour:
Im on AICP and having the same problem
[X Style (Pure) Android Development] mddunner:
Using zzmove on big and little as well as lazy hotplug, Im at 10% battery and the phone has been on 48 hours. About 2 hours SOT.
[X Style (Pure) Android Development] XDleader555:
See my previous post of getting the last_kmsg or upping your min frequency to 384Mhz.
[X Style (Pure) Android Development] creeperlwd:
link: https://drive.google.com/open?id=0B3IzYu3saG9jU1ROam5ESms4Q0U

edit: happened on 1.8 with default cpu clocks, zzmoove, lazyplug on "lazy" and zen io sched
[X Style (Pure) Android Development] rayparlour:
It happens with 384Mhz also. i think it may have something to due with hotplugging but im not sure.

Heres a link to my last_kmsg right after it happened, hope it helps :)

https://drive.google.com/file/d/0B0PvTiIuxJjvWHcta3dpb2VMa1U/view?usp=drivesdk
[X Style (Pure) Android Development] XDleader555:
I actually think it might have something to do with powersuspend. In both your cases after powersuspend never enters sleep (while everything else does). I'll check the code and see if there's anything obvious.

For now, can you set powersuspend to userspace (basically disabled, mode=1) to see if the issue still occurs?

Thanks

EDIT: You know what, because I converted everything to state_notifier, powersuspend isn't actually needed. They do the exact same thing (notify modules when the screen is on or off/when it's safe to sleep). I'll remove powersuspend in the next update. Look at me not reading what code does and then adding it *head_desk*

EDIT2: That being said powersuspend might not be the issue. I'll keep looking for a solution.
[X Style (Pure) Android Development] creeperlwd:
I enable the "Power Key Suspend" option in the wake section (Kernel Adiutor), correct?
[X Style (Pure) Android Development] XDleader555:
Under Misc -> Power Suspend Mode, select userspace
[X Style (Pure) Android Development] creeperlwd:
Thanks, enabled it will come back tomorrow if it fixed it or not
[X Style (Pure) Android Development] dbolivar:
Can you provide more information about state_notifier? Never heard of it. Is it supposed to be more power efficient than powersuspend? Thanks!
[X Style (Pure) Android Development] XDleader555:
From what I've learned, PowerSuspend lets modules know when the screen has turned off (or when the device is entering sleep). Modules have to hook into PowerSuspend, but most of the time they have their own implementation of checking if the screen is off.

It doesn't actually add efficiency. It doesn't hook into other modules. It seems to just be a way to simplify code and prevent a few repeats of checking if the screen is off.

If you're code savvy or can at least figure out how code works, you can take a read for yourself.

https://github.com/XDleader555/HandBag-Kernel-Clark/commit/60ea7534fbff7de842e88ef25dddfc1274b55222
[X Style (Pure) Android Development] dzidexx:
Wow,

Very good sleeping for my Moto - 1% by night!

Wifi, cell.data - off.
[X Style (Pure) Android Development] Bwangster12:
Are there presets or recos for killer battery life? I haven't flashed yet, but would only move to this from stock lineage kernel for the killer battery life.
[X Style (Pure) Android Development] creeperlwd:
Thank you [MENTION=3623188]XDleader555[/MENTION] setting powersuspend to userspace fixed the issue
[X Style (Pure) Android Development] XDleader555:
"Killer battery life" is completely the opinion of the users. There haven't actually been any real day to day tests, and so far for me it's about the same. The difference between stock lineage and this Kernel is more features to play with.

As for settings for a little more juice, you can set it to more conservative governor's, such as elementalx and msm_hotplug, but I really like the idea of lazy plug (which keeps the cores online) to save battery life by getting to the lowest frequency/voltage as fast as possible keeping a smooth UI. It's all up to your tastes.

I do suggest switching from interactive to another Governor. Right now interactive seems to have a glitch here or there. zzmove and blu_active work rather well without any tweaks.
[X Style (Pure) Android Development] XDleader555:
On a plus side that's great, on the down side it means either power suspend or something which hooked into it isn't working correctly, and now I have to figure out which.
[X Style (Pure) Android Development] tech_infinity:
Can someone please tell me what exactly one has to do in the swipe gesture?
[X Style (Pure) Android Development] Curlyfry2121:
Swipe to wake is when you have your screen off you can make a swipe up or down or left or right on the screen and it'll turn off. Swipe to sleep is right or left and you swipe left or right on the navigation bar to put the phone back into sleep.
[X Style (Pure) Android Development] seatibiza:
Works fine with Viper OS

Gesendet von meinem XT1572 mit Tapatalk
[X Style (Pure) Android Development] Foolson:
Are there any advantages to install this kernel even without root? Running latest LOS. :)
[X Style (Pure) Android Development] dzidexx:
Without root you cannot use any kernel manager.

Don't do it or install magisk too.
[X Style (Pure) Android Development] R77:
Have the Moto X Pure XT1575 running android version 7.1.2 AICP Nighties 12.1. Will it work for my ROM?

---------- Post added at 05:33 PM ---------- Previous post was at 05:19 PM ----------

How do I enable the swipe gesture?
[X Style (Pure) Android Development] Curlyfry2121:
Download a kernel manager and you should find a gestures section, kernel auditor lets you enable them. And guys idk if I'll be able to use this phone much, dropped it in my tub and was in there for like a split second and now the screen is starting to discolor and the front facing camera has condensation. Power button was wonky and charging just a minute ago was going on and off. Might get a moto e or g or something until I get enough money for a real replacement. Hopefully In the next week this phone recovers. Idc about the screen, just wanna be able to use the phone haha.

It's even saying I have headphones plugged in
[X Style (Pure) Android Development] Spencervb256:
Man hopefully your phone recovers!! Good luck life sucks without a working phone :p
[X Style (Pure) Android Development] redemptionx11:
There sure are a bunch of governors and I/O schedulers. Is there someplace that has description of what kind of use their for? It's obvious what performance and conservative govs do, but I've got no idea about some of these.
[X Style (Pure) Android Development] Andvark:
Try leaving the phone in a bowl of uncooked rice overnight.

---------- Post added at 06:18 PM ---------- Previous post was at 06:16 PM ----------

https://xdaforums.com/general/general/ref-to-date-guide-cpu-governors-o-t3048957
[X Style (Pure) Android Development] Curlyfry2121:
Yeah it works lol. But the screen is like brighter in the place where water has gotten in through the headphone jack. And it always thinks it has headphones in so voice calls and all that won't work. I would take it apart but I don't have a screw driver that small. Using the sound about app to hopefully make it a workaround. So I think I'm good for now lol. Will see tomorrow.
[X Style (Pure) Android Development] rayparlour:
https://xdaforums.com/general/general/ref-to-date-guide-cpu-governors-o-t3048957

Prob a good place to start
[X Style (Pure) Android Development] hellboyborn:
Thanks man for the kernel and for including the KCAL control. Its working great.
[X Style (Pure) Android Development] dzidexx:
Wheatley + bricked was better sleeping than wheatley +lazy(4% by night).
[X Style (Pure) Android Development] tech_infinity:
Man with this kernel the double tap wake features work great. Much better than roms where dt2w comes inbuilt where it only works 1 out of 2 times.
[X Style (Pure) Android Development] dzidexx:
[MENTION=3623188]XDleader555[/MENTION]

I had some bugs with 1.8+bricked hotplug.

Few soft reboots, not keeping governor,

Flashed back 1.7.1.
[X Style (Pure) Android Development] XDleader555:
I'll see if I can recreate your condition with bricked hotplug and fix any errors.
[X Style (Pure) Android Development] XDleader555:
05/30/17 - 1:37AM - v1.9

Switch toolchains from UberTC 6.0 to Linero 6.3.1

Add relaxed cpu governor

Show cpu voltages (No editing unfortunately)

Slimbus overclock

UNREVERT: zSwap, zMalloc Updates

Removed powersuspend (not needed)

linux/random backport from linux 4.1.40

Various optimizations I probably missed

See previous posts if you're curious about the powersuspend removal.

Downloads: https://xdaforums.com/devdb/project/?id=20678#downloads
[X Style (Pure) Android Development] dzidexx:
I will flash 1.9, forget 1.8.

Thanks. [MENTION=3623188]XDleader555[/MENTION]

Bricked hotplug I always have such settings(kernel adiutor):

Cpu min/max/screen off max - 1/6/2, 1st core 768 MHz, wheatley or zzmove. The same now at 1.9.

Soft reboots I saw in battery stats and today morning I had interactive(big)+zzmove(little) but I set zzmove for both.

It's all what I remember.

Maybe changing should be done this way:

1st settings for cpu, apply,

Set cpu to performance, apply, after few minutes:

2nd settings, apply.
[X Style (Pure) Android Development] GchildT:
Flashing 1.9 now. No SOD or random reboots for me yet. Interactive was still not cooperating though.
[X Style (Pure) Android Development] xgerryx:
Delete.

I am on XOSP ROM now and I am not losing root like I did on ViperOS, just for anyone who happens to have that happen.
[X Style (Pure) Android Development] DeliriousHD:
I can confirm it works on xosp as well.
[X Style (Pure) Android Development] Curlyfry2121:
Interactive working fine for me on validus
[X Style (Pure) Android Development] JoshuaUB78:
I'm not getting any deep sleep, only phone awake, screen off.

Intelliactive on both big & small,

Tripindroid on both internal & external memory

Lazy hotplug with balance profile
[X Style (Pure) Android Development] XDleader555:
Try a different governor. Intelliactive and Interactive might be broken?
[X Style (Pure) Android Development] Curlyfry2121:
Interactive has been working fine on both tipsy and validus on the latest version.
[X Style (Pure) Android Development] JoshuaUB78:
Well it's easy enough to try a different governor. Switching to blu-active.

Running latest stable dirty unicorns.
[X Style (Pure) Android Development] Curlyfry2121:
Yeah I only stay on interactive to mess with the parameters.

Snapdragon 808 is the same one as in the Nexus 5x so I use these profiles from this thread. Maybe one of the profiles like drunk sauce can be implemented into the stock values for this kernel, drunk sauce is the default for the Nexus 5x for dirty unicorns.

https://xdaforums.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557
[X Style (Pure) Android Development] tdg2k15:
Could also nitpick features from the 5x and bring them to the Moto X Pure.. Would be nice to see f2fs available for this phone
[X Style (Pure) Android Development] XDleader555:
Yeah, I've been cherrypicking from bullhead (nexus 5x) and ether (nextbit robin). They both run msm8992 (snapdragon 808).

I'll see about adding f2fs to the kernel if it's not already enabled.
[Magisk] cl0g:
Hi guys,

i tried some Roms for my op3 (sultans 14.1 / OOS OB) and always got WiFi problems, when installed Magisk + some modules. (Google Assistant Enabler and Dolby Atmos Lenovo with audiolib v4)

Running Magisk alone, it did not has problems. Also it seems that the problems came with Android 7, but unsure.

Could only be fixed by clean flashing the rom (dirty flashing and uninstalling Magisk did not help).

Someone can explain, how it is possible?

kmsg was something like wifi couldnt suspend device, and did a random reboot. before it rebooted it could not connect to any WiFi-network.

if needed, i can add some more complete logs ;)

[ 324.876840] PM: Some devices failed to suspend, or early wake event detected
[ 325.063045] legacy_suspend(): wiphy_suspend+0x0/0x68 returns -11
[Magisk] tech_head:
Remove all modules and reboot into recovery.

Wipe caches and reboot.

I have found that I can end up with WiFi, Bluetooth, SIM issue if something happens with the modules.

Before I figured out what it was, I was re-installing the ROM, etc.

Try just deleting the modules and wiping the caches and rebooting.
[Magisk] cl0g:
[MENTION=702877]tech_head[/MENTION]

Thanks for your answer, but this was unnecessary.

I did not ask for a solution to resolve this on my phone, but a explanation, how Magisk(+modules) mess with kernel/firmware or something.

If you read the whole post, then you would have seen, that it was fixed by clean flashing the Rom.

Thanks anyway.
[Magisk] tech_head:
Hi,

I actually did read the whole post and was offering a solution that DID NOT require re-installing the ROM.

I'm not 100% sure why the problem persist but I have seen it affect Bluetooth, Wireless and SIM recognition.

Typically it happens after a reboot. Wiping the cache on my phone causes it more than 50% of the time if I don't disable modules first.

I don't know why it happens but you are right, removing Magisk does not solve the problem.

There is something corrupted in the data partition and the only way to clean that up is to remove the modules and wipe the cache or do what you proposed.
[Magisk] davidzam:
Nevermind
[Magisk] iHenry:
I recently had the same problem. I'm currently trying to fix it without reinstalling. I've uninstalled all modules, cleared both caches and still no wifi and I'm getting random crashes. Has anyone found fix a reliable fix?

While posting, I tried resetting my network and everything started working again. If this happens again, I'll try that first.

BTW

Also, it happened after a failed installation of Crossfire and Tethering, both thru Magisk. Tethering actually installed but after the reboot, I've got no wifi. :(
[Magisk] mellus:
I was able to fix the wifi problem by following this tutorial: https://************/root-razer-phone-fix-wifi-root/

But: JUST UNTIL INSTALLING TWRP INSTALLER. Until this step I got a working wifi (I am on Android Pie Custom rom). After flashing Magisk v18 or v19 same problem as before: No more wifi. Su installer does not work on my Razer Phone 1 ( failure while patching sepolicy, no permission ), so what to do? Any hints?

Best regards and thx in advance

Michael