yashsingh1/xdaforums huggingface dataset:
[Nexus 5X Original Android Development] loki993:
Can I flash this on stock Oreo or should I be using a custom ROM for best performance. Basically my phone has been very laggy and sluggish lately and I'm trying to wake it up a bit. So I rooted and figured some kernel tuning would help make it fresh again.
[Nexus 5X Original Android Development] kevtrysmoddin:
Yes you can use this on stock Oreo
[Nexus 5X Original Android Development] Andi17:
Hello,

I wanna try this Kernel and ask before How the battery life is?

Thanks
[Nexus 5X Original Android Development] joetheshmo:
http://elementalx.org/the-truth-about-kernels-and-battery-life/
[Nexus 5X Original Android Development] Nicktheprofessor:
Love that link but it's somewhat true at best.

In reality, you balance performance and battery life to gain more screen on time but that does NOT mean that you get more PRODUCTIVE screen on time. Lags and waits will pretty much cancel out all improvements at all times unless it's background processes that are being held back and you can't do that through the kernel.

Race to idle has merit, your cores scale up as soon as something happens and go all out so they can return to idle as fast as possible. Now the performance state is taxing for battery life but the idle state is damn near screen off state so it all depends on how well written drivers and the OS itself is if you are going to have the ability to race to idle and stay idle.

For Android O a LOT has been done to achieve just that so it's not a bad idea to at least try it.

On another device i wrote a specific handler for a specific governor that was based on ondemand to try this out. Measured processing time did exceed any other solution by almost an hour but screen on time was about 30 minutes less. That means that about an hour and a half was spent on just waiting or for background processes to finish (something that won't be happening with Android O) and the screen on time was actually an hour better, it just removed the time waiting for tasks to finish.

Now on a mobile device background tasks should not be running unless there is an absolute need and with Android O this has finally been the target so a high performance setting might just save you some battery.
[Nexus 5X Original Android Development] Vink67:
Hi, I'm on Oreo stock with ElementalX kernel and I can't do the update. What I must do to update ? Lock the bootloader I think no ?

Thanks.
[Nexus 5X Original Android Development] :
You can't update phone with custom kernel lol
[Nexus 5X Original Android Development] Vink67:
Really useful lol ! Already did it. Lock bootloader but what else.
[Nexus 5X Original Android Development] flar2:
Do NOT lock the bootloader!

All you need to do is download the factory image from Google and flash it. Easiest way is the remove the "-w" from the flash-all script so it doesn't wipe your data. Takes less than 10 minutes to flash the update, reroot and reflash elementalx. I do it on all my phones every month.
[Nexus 5X Original Android Development] Vink67:
Thanks ! That's the answer I hopping for.
[Nexus 5X Original Android Development] Vink67:
Last time loose my data and lock bootloader.

With your method, -w remove all good and fast.

Big thx.
[Nexus 5X Original Android Development] CazeW:
I think it's even easier to just flash the full OTA with TWRP or Flashfire.
[Nexus 5X Original Android Development] Vink67:
Already try by TWRP, and if I'm not wrong it's impossible
[Nexus 5X Original Android Development] yochananmarqos:
All you have to do is flash the stock boot.img & recovery.img if you haven't modified the system partition. You can then accept the OTA and flash TWRP + kernel, etc. after.
[Nexus 5X Original Android Development] Vink67:
Ok so another method but I think the other is faster or same.
[Nexus 5X Original Android Development] flar2:
Lately, I've just been fastboot booting TRWP so I can backup the original recovery and boot for OTAs.
[Nexus 5X Original Android Development] CazeW:
You can flash the full Oreo OTAs with TWRP if you modify the updater-script in the zip a little bit. Having stock recovery and boot is obviously going to be easiest but I'd say flashing the OTA or full OTA with Flashfire is the second easiest as it restores the stock recovery and boot.img and flashes root for you.
[Nexus 5X Original Android Development] LoneWanderer_97:
Hey guys ive asked this before, before but.. Do all I need to do to properly load and use a governor profile is to

•Obviously load the profile under Governor options and hit apply on boot

•Set the Min/Max core frequencies to their respective minimum and maximum values and to apply on boot

• And to lastly disable touchboost and apply on boot.

So are those all the things I need to once ive "loaded" a profile or am I missing something? Just curious.
[Nexus 5X Original Android Development] Lughnasadh:
Also apply on boot the CPU Boost values that changed with the profile. And make sure core_control is enabled and msm_thermal is disabled. Some profiles change these, but a reboot will also set core-control to enabled and msm-thermal to disabled so you don't usually have to apply on boot these.

Also, sometimes you have to apply a profile twice, such as with Heimdall.
[Nexus 5X Original Android Development] LoneWanderer_97:
Thanks, so would i would i load heimdall then reboot and apply again?
[Nexus 5X Original Android Development] Lughnasadh:
Quote from the author...

Because of the Dual-Cluster InputBoost make sure inputboost is enabled and input_boost_freq and input_boost_ms are set (apply on boot for all!!!)

WHEN YOU SWITCH BETWEEN MY (or any other) PROFILES IN EXKM YOU NEED TO APPLY THEM TWICE!!!

Because of a bug(?) in EXKM, changing the governor and values at the same time could prevent the values from being applied.

To apply the profiles successfully you MUST

1. go back to CPU after applying the profile for the first time

2. reopen Governor-Options and load the profile again.

3. all values should be set now.
[Nexus 5X Original Android Development] LoneWanderer_97:
Okay did everything except I cant find a "input boost" option under cpu, there is however input boost freq. and input boost ms both of which I hit apply on boot. theres just no general "input boost" to hit apply on boot for.
[Nexus 5X Original Android Development] Lughnasadh:
Input Boost should be enabled by default so you shouldn't have to worry about that.
[Nexus 5X Original Android Development] dc239:
Does the vdd_restriction affect the thermal control, or it's useless for the snapdragon 808 as the msm_thermal?
[Nexus 5X Original Android Development] gorilla p:
Sorry if already mentioned.

I had an issue when adjusting the BIG core frequency during the AROMA setup. I reduced the frequency to 1689MHz. Upon booting, I noticed performance was horrible. I checked frequencies and the BIG cores wouldn't go above 480MHz. Minimum was 633MHz and maximum was 480MHz. This occurred on PixelROM and AOSPExtended Oreo ROMs.

I reflashed the kernel without adjusting the frequencies and it then performed normally.
[Nexus 5X Original Android Development] flar2:
That's due to thermal throttling
[Nexus 5X Original Android Development] gorilla p:
Just to clarify,

When lowering max frequency of big cores to 1689 in AROMA setup, they will not go above 480MHz. They are permanently stuck at 480 or below. When the frequencies are left alone during setup, they behave normally. So this isn't normal thermal throttling behavior.
[Nexus 5X Original Android Development] Ryder.:
If i want to change the max frequency of the cores can i reflash the kernel for setting up on aroma installer or issues can happen?
[Nexus 5X Original Android Development] joetheshmo:
Yes, you can reflash
[Nexus 5X Original Android Development] gorilla p:
I'm having issues after lowing the maximum frequency of the big cores in Aroma. I would just adjust them in EXKM or KA for nowm
[Nexus 5X Original Android Development] flar2:
That's strange, it shouldn't do that. Unfortunately it's impossible for me to check this because my 5X will not boot with the big cluster enabled.
[Nexus 5X Original Android Development] gorilla p:
Is there anything that I can provide that will assist? Perhaps logs will show what is actually causing the freq to stay at 480mhz?

Can someone else test this also to see if this is an isolated case or of it is recurring?

If anyone is using AICP 8.0 or AOSPE 8.0,

Please try flashing latest EX kernel and during AROMA setup, lower BIG cores maximum frequency to 1689 MHz. Open EXKM after startup to see if BIG cores stick between offline and 480MHz.
[Nexus 5X Original Android Development] ChemBot:
Actually, I remember this happening to me a few weeks ago on Lineage, except I tried to set the big cluster max frequency to 1440. I thought it was from a bad flash so I reflashed and left the max frequency at the default which fixed it.
[Nexus 5X Original Android Development] marcelojudoka:
Any chance to update the nougat kernel version with the latest security patches, like blueborne and KRACK (WPA2 vulnerability)?

Thanks!
[Nexus 5X Original Android Development] joetheshmo:
Google is putting it out in the November security update.
[Nexus 5X Original Android Development] gorilla p:
Yeah, I suspect it doesn't matter what its lowered to, simply lowering it seems to change something.
[Nexus 5X Original Android Development] Vink67:
Correct me if I'm wrong but when using profiles like Heimdall or GlassFish you shouldn't apply on boot the min/max core frequency because its the profile who do all the magic !
[Nexus 5X Original Android Development] Vink67:
Have a question and can't find any information.

Someone can help me?

I try to know what is : align_windows and use_migration_notif in the CPU governor profile.

use_migration_notif is always set to 1 but align_windows is sometimes 1 or 0.

Do research and testing but what is this parameters?

Thanks
[Nexus 5X Original Android Development] drik05:
Hi ! does the latest ElementalX kernel works on new android 8.1 opp5 ?
[Nexus 5X Original Android Development] tim.smart:
It froze up during boot for me. Had to reflash the stock boot.img to get it booting into the launcher.
[Nexus 5X Original Android Development] fire7777777:
Kernel oreo It work forma 8.1 de preview ?
[Nexus 5X Original Android Development] Audriuskins:
Njet. No it does not work, but shadow kernel does. You should read rules before posting next time.
[Nexus 5X Original Android Development] drik05:
Thanks. will wait for the new release of ElementalX kernel. Hope it supports 8.1 soon. [emoji4]
[Nexus 5X Original Android Development] fire7777777:
ok thanks, is it possible to add feature that when screen is of the big core sleep?
[Nexus 5X Original Android Development] Audriuskins:
Im not a developer.
[Nexus 5X Original Android Development] :
hello, will just ask if do you have any plans to support 8.1 dev preview? :o
[Nexus 5X Original Android Development] zurik:
Sources for 8.1 Developer Preview didn't released yet.
[Nexus 5X Original Android Development] zurik:
Hello [MENTION=4684315]flar2[/MENTION] .

I don't know if is related to kernel or not, when I plugged in my phone to charger at night, and today morning (GMT +2) I saw that it stuck at bootanimation (I think random reboot) and I press the power button 10 seconds to force reboot and booted up now. My device running 8.0.0 with October's security patch and Ex kernel.

Dmesg file attached
[Nexus 5X Original Android Development] flar2:
There is no kernel error. Everything should be totally stable on the kernel side.
[Nexus 5X Original Android Development] zurik:
That means is something other (or Magisk Module or App or System Side issue)
[Nexus 5X Original Android Development] Andi17:
Hello [MENTION=4684315]flar2[/MENTION]

is this solution with remove -w from flash-all possible if i want change from custom rom to factory image? or is this solution olny possible for update an factory image?

Thanks in advanced
[Nexus 5X Original Android Development] flar2:
It works in either case. The factory images are full partition images and replace your current system and firmware.
[Nexus 5X Original Android Development] Andi17:
very much thanks for your help.

After flashing factory image with deleted -w the bootloader won´t be locked or?
[Nexus 5X Original Android Development] zurik:
Flashing Factory images will not relock the bootloader.
[Nexus 5X Original Android Development] Octane70:
Kernel good to flash over Nov patch? with stock Kernel. Looks like its been merged.
[Nexus 5X Original Android Development] yochananmarqos:
Yes, 5.0.4 is working fine.
[Nexus 5X Original Android Development] srnoth:
Same here.
[Nexus 5X Original Android Development] tuhinxp04:
New patch are merged but New build not uploaded...!! After merged new version will be 5.05
[Nexus 5X Original Android Development] SlimSnoopOS:
Let the developer live his life and update if he has time. He doesn't owe us anything.

Now go enjoy your day.
[Nexus 5X Original Android Development] Aijen:
Hi dudes! I buy the Kernel App....so what settings can please recommend me? Im in Nougat running DU 11.7.2, want the beat multitasking and great battery life. Please somebody can share some configurations with caps :) thanks a look and good work! ?
[Nexus 5X Original Android Development] yochananmarqos:
This thread is for kernel discussion. The Kernel Manager discussion thread is here. Custom profiles and such can be found here.
[Nexus 5X Original Android Development] BrunoSnickers:
After a few months my phone is sometimes very slow with 4.14. Start writing something, you can see 1-2 sec later the word you can see in the textbox. Sometimes it shows immediatly, but sometimes you can watch, you tip the letters on the keyboard. Any solutions except reset and wipe the phone?
[Nexus 5X Original Android Development] mireste:
... also the swipe to lock?

Thanks
[Nexus 5X Original Android Development] yochananmarqos:
Yes.
[Nexus 5X Original Android Development] Flyview:
Thanks for the informative post. I found it while researching ZRAM as I tried to tweak it. Since our 5x's are bottlenecked by a low amount of RAM, and since you say the effect is negligible, is it in our best interest to set the ZRAM as high as possible (1024mB)? That way a lot of the RAM will be compressed thereby giving us effectively a bit more RAM (depending on how well data is actually compressed).
[Nexus 5X Original Android Development] flar2:
You can try it and see how it goes. There may be a point where too much memory is compressed and a performance hit becomes noticeable.
[Nexus 5X Original Android Development] BS86:
Franco.Kernel uses 1024MB zRAM - there are no drawbacks.

I use ElementalX Kernel for weeks now with 1024MB zRAM and can also see no drawbacks from doing so.
[Nexus 5X Original Android Development] Flyview:
Seems fine so far, but it isn't all being used. According to EXKM, RAM is always at around 80% use and I've only seen ZRAM go up to about 550mB of the 1024 total. Right now it's actually only at 360mB. Has anyone played with the snappiness? I have it set at 100 for testing to see if it encourages it to use more of the ZRAM instead of killing apps. I've also lowered all the the low memory killer thresholds by 40mB.
[Nexus 5X Original Android Development] flar2:
That seems to be working out pretty well
[Nexus 5X Original Android Development] BS86:
I have swapiness at 100, too. Your apps don't need more ram, so why should it use more?
[Nexus 5X Original Android Development] Flyview:
Isn't the idea to keep RAM full with apps you've been using? I'm still getting apps reloading when switching between one I used a few apps back when it could have already been loaded in memory.
[Nexus 5X Original Android Development] BS86:
some apps automatically close themselves as soon as they go to background - the amount of available RAM can not change that behaviour. For a lot of apps, that behaviour has to be that way, especially if the app consumes a lot of energy (by keeping the CPU awake for example).
[Nexus 5X Original Android Development] Flyview:
Yea you might be right. That sounds like bad practice to me. You should be able to pause all activity (CPU work, network calls etc) without calling finish.

In any case it's definitely keeping more apps in memory than it used to so that's great. It used to kill off foreground services if I was taking an Instagram story video for example.
[Nexus 5X Original Android Development] mattcooper:
Could you take a minute to explain the Low Memory Killer option? Can't seem to find conclusive info...
[Nexus 5X Original Android Development] Flyview:
Here's an article I just read on it as I'm also trying to understand:

www.droidviews.com/tweak-android-low-memory-killer-needs

I just lowered mine drastically (12, 20, 40, 60, 90mB) and FINALLY recently used apps are staying in memory. With the stock value of over 300mB for "empty" apps, our N5x would be hitting that threshold all the time and killing off recently used apps. We don't have that much memory to spare to "free" RAM. I'd rather it stay loaded with apps I'll switch back to so they don't have to keep re-loading.
[Nexus 5X Original Android Development] yochananmarqos:
You only listed 5 values when there are 6. What did you set Empty Applications to?
[Nexus 5X Original Android Development] flar2:
Update!!!

I was hoping to add the little core mod, but ran in to some trouble and no time to debug.

Download

ElementalX-N5X-5.05

Changes:

-November security update
[Nexus 5X Original Android Development] Milan P.:
Does this support 8.1?
[Nexus 5X Original Android Development] flar2:
Source for 8.1 has not been released
[Nexus 5X Original Android Development] srnoth:
Is that the mod to allow the phone to run on the little cores only? (For folks with bootlooped phones).

It would be awesome to have that option built in to ElementalX!
[Nexus 5X Original Android Development] Flyview:
Hmm yes looks like I missed one of the middle ones. It turns out those might have been a little too aggressive as sometimes the phone became extremely unresponsive to the point where you'd have to restart it. Not sure if it was related to LMK, but that's my best guess. Here is a screenshot of my current settings. I divided all the stock values by 3 and it's working well so far.

P.s. has anyone noticed the CPU gets throttled to 1.25GHz on the small cores as soon as you enter any camera apps (stock camera, Snapchat, Instagram)? I monitor frequencies with SystemGlow. This makes Snapchat extremely laggy, especially because the big cluster quickly throttles.
[Nexus 5X Original Android Development] Ryrynz:
By your reasoning no one should ever need to upgrade ever.

MOD EDIT: [MENTION=3135643]Ryrynz[/MENTION] please cool off

No one knows everything
[Nexus 5X Original Android Development] yochananmarqos:
I just tested using DevCheck Pro's floating system monitor and could not reproduce that with Camera NX. The little cores ramped up to 1440 MHz & the big.little cores ramped up to 1824 MHz.

---------- Post added at 07:19 AM ---------- Previous post was at 07:10 AM ----------

@flar2

I just noticed with 5.05 the Block Wakelocks section shows Not available.
[Nexus 5X Original Android Development] Flyview:
Camera NX? Try the stock camera. After leaving it open a few seconds frequencies drop to 1.25GHz and 0.38GHz. I have touchboost and CPU touch boost disabled.
[Nexus 5X Original Android Development] yochananmarqos:
I was able to reproduce it with the stock camera. Strange. With Camera NX (stock camera mod), the floating system monitor disappears right about when the CPU throttles down to 1248 MHz.
[Nexus 5X Original Android Development] flar2:
Update!!!

A quick update to enable the wakelock blocker. You can use EXKM to block any kernel wakelocks you want.

Download

ElementalX-N5X-5.06

Changes:

-enable wakelock blocker
[Nexus 5X Original Android Development] Flyview:
It's not a big deal in the stock camera as it still ramps up when processing a picture you just took, but it sucks for Snapchat and instagram when you're trying to record a story and working with face filters etc.
[Nexus 5X Original Android Development] synesthete:
Ever since I have upgraded to Oreo, I have had problems keeping apps in memory. I am unable to have Google Maps and Play Music open/running at the same time. They kick each other out of memory. What Kernel settings would help remedy this?
[Nexus 5X Original Android Development] :
Enable zram and ksm and set higher values for the low memory Killer.

Please note that setting higher values may drain a little bit quicker.
[Nexus 5X Original Android Development] BS86:
I never use Google Maps because it is a resource hog.

Check out Waze, it is a lot more battery friendly and also RAM wise it is better.
[Nexus 5X Original Android Development] synesthete:
zram and ksm were on, but I will try playing with the individual values. I just turned on low memory

killer and will play around with that, too. Thanks

I have Waze, but have always used Google Maps as my primary navigation app. Waze does seem a bit more responsive. Maybe I will see how Waze works with Play Music.
[Nexus 5X Original Android Development] kridster:
I'm on LineageOS 14.1 and want to update to the current nightly with the up to date security patch level. If I want to use this kernel, of course I have to use the nougat version, 4.14.

Here comes my question: Are the security patches part of the kernel? Since it hasn't been updated after the Oero release, they would be missing, wouldn't they?

If anyone has further information and/or links regarding this topic, that would be great! Thanks.
[Nexus 5X Original Android Development] Lughnasadh:
Just flashed and working great. I like the way you implemented and combined a default and user defined list. :) It definitely detected kernel wakelocks not on the default list. Thank you so much for this feature. :good::cool:
[Nexus 5X Original Android Development] flar2:
I just updated the kernel yesterday. I do a release at least once a month with the latest security patches.
[Nexus 5X Original Android Development] :
In fact you must not play with all settings but only increasing the number of visible apps (in amount of RAM)
[Nexus 5X Original Android Development] Flyview:
I was just talking about this in my previous posts. The biggest help I've seen is changing the Low Memory Killer (LMK) values. Just to be clear, it's always on, and you want LOWER values to keep more apps in memory. I've been experimenting the last few days. If you go too low I've found the phone can become super laggy and unresponsive even. I started with a quarter, then a third and now half of the stock values. Screenshot of my current values attached.

[MENTION=4684315]flar2[/MENTION], unrelated to the above, is it possible to get overclock values above 1.63GHz for the small cluster cores? I'm disabling the big cores through EXKM as it quickly makes the phone too hot and throttles anyway. I've had no problems at 1.63GHz with freezes or temperature (with big cores off) and wondering if I could push it even farther, even if it's just for fun to find the limit.
[Nexus 5X Original Android Development] Flyview:
Adding LMK screenshot.
[Nexus 5X Original Android Development] yochananmarqos:
With those values Chrome froze while a page was almost finished loading.

FYI, since I started using the thermal throttle tweak my phone rarely gets above 130 degrees Fahrenheit. I use the extreme v4 profile.
[Nexus 5X Original Android Development] Flyview:
What page? I'll try loading the same one. I haven't had any freezing with these values yet all day and I run a lot of memory intensive apps (Instagram, Snapchat, Chrome with 14+ tabs, etc).

What thermal throttle tweak? Please explain!
[Nexus 5X Original Android Development] yochananmarqos:
I was reading my RSS feeds in Palabre and opened this RT News article in Chrome.

This thermal throttle tweak.
[Nexus 5X Original Android Development] OhioYJ:
Really? So when do you switch version numbers? I always assumed you did that whenever you made changes. I've been checking and every time it still said 4.14 I assumed it was the same.
[Nexus 5X Original Android Development] flar2:
You are still on Nougat? All development has been on the Oreo branch for a few months now.