yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] flar2:
I've have some baselines for idle drain now:

0.3% per hour with default settings

0.9% per hour with sweep2wake enabled

Still have to measure with stock doubletap2wake enabled.

For now, sweep2wake causes 0.6% per hour additional battery drain while idle. Sweep2wake does not cause any additional drain while the screen is on. This means that for a typical XDA user, sweep2wake is going to cost 5% to 8% battery on an average day. Not too bad for the convenience, but a little disappointing, since there is no battery cost on a couple of my other devices. I might be able to reduce it a bit more, I have a few things in mind. But first I'm going to switch attention to the CPU governor, because I believe there are some more significant gains to be made there.
[Nexus 6  Original Android Development] Nucleonic:
Anyone seeing any kernel panics? Kept getting a 504 error while downloading Pocket from the Play Store. After 3-4 times, it finally installed but the phone rebooted itself.
[Nexus 6  Original Android Development] BRKotucs:
Grab a log so the Dev can take a look at it.
[Nexus 6  Original Android Development] flar2:
I'm pretty sure the kernel is stable, but there are a few experimental commits. I'm thinking watchdog in this case, but if there are any reboots, I really want to know. Instead of /proc/last_kmsg, we now need to do this:

adb shell su -c cat /sys/fs/pstore/console-ramoops > kernel.log

(going off memory here, it's something like that)
[Nexus 6  Original Android Development] antiochasylum:
I'm not having any issues, no reboots, nothing.

The only thing I see is when I set the max speed in Aroma and Elemental app, for some reason it always resets to 3033 as default. Even when I set max to 2746. ::shrug: oh well, being a PVS bin 9(granted this means nothing, but a better voltage table, I know) - my phone is stable as hell. Thanks again [MENTION=4684315]flar2[/MENTION] :good::good:
[Nexus 6  Original Android Development] flar2:
Mine has never reset to 3033, but if that's happening, it's no good and would cause instability for many people. I will have to go to my old way of overclocking in that case.
[Nexus 6  Original Android Development] antiochasylum:
I set 2726 as default in aroma, and in the app.

Flar your old way, I remember on the nexus 5 was, what ever you selected in aroma, that was the highest any app would allow you to select.

Should I wipe data in elemental and set it again?
[Nexus 6  Original Android Development] flar2:
You could try wiping, but it probably won't work. There are many things that mess with the frequencies on this device (mpdecision, powerhal, etc), one of them is probably changing the max.

It's like this on many devices, which is why I normally do the hard limit in the installer. I know a lot of people will complain that you can't make it higher in the app later, but I've always argued strongly against messing with frequencies anyways.
[Nexus 6  Original Android Development] paychex:
I just checked, mine is too
[Nexus 6  Original Android Development] antiochasylum:
Yea I've seen you tell someone else what all messes with frequencies. I just move it up ever so slightly.

I relate it to my BMW, it has the ability to run 19-20psi of boost. However I only run it at 12-13 daily. :p it gives me a slight performance boost lol. That's how I see the slight frequency increase.

You should have it set a hard limit, if people want higher they can reflash. It could save someone from frying his or her device.

I get that you aim to please the masses, however its still your kernel in the long run, you do as you please. You can't make everyone happy....
[Nexus 6  Original Android Development] simms22:
yup, i just noticed that, 40%.

---------- Post added at 11:15 PM ---------- Previous post was at 11:10 PM ----------

just hit 41% charging it, and it automatically went up to 3033mhz.
[Nexus 6  Original Android Development] flar2:
Same here, I couldn't even use it on cold mornings. I don't think we'll be seeing any more arctic temperatures this year (although there is still a foot of snow on the ground here!)

If you have a spare one, sure.
[Nexus 6  Original Android Development] Lancez:
Saw the news that this year's temp. will be the highest ever recorded.
[Nexus 6  Original Android Development] flar2:
I just pushed an update to the app for the new settings, and also to fix a bug where disabling mpdecision from the app would cause the third and fourth cores to stick at 1.5GHz.

The new settings for elementalx governor:

active_floor_freq: core will not drop below this frequency for a period equal to sampling_down_factor * sampling_rate. This replaces input boosting, ensuring both smoothness and stability (the previous quick frequency jumps aggravate the split screen defect and may have caused other instability)

sampling_down_factor: the period that active_floor_freq is in effect. The period is sampling_down_factor * sampling rate. Default is 8, which is about 80ms if you use the default sampling rate of 10000. You can safely set it lower, or set it to 0 to disable the active_floor_freq.
[Nexus 6  Original Android Development] flar2:
You mean lowest? I think we had the coldest February ever recorded. Down around 0F and lower almost every day.
[Nexus 6  Original Android Development] Lancez:
Highest temp. during the summer
[Nexus 6  Original Android Development] flar2:
I hope we have a hot summer to make up for this winter.
[Nexus 6  Original Android Development] Lancez:
If it's true I'll have to camp at beach for the entire summer :laugh:
[Nexus 6  Original Android Development] Simer03:
Yeah there's some here but its going away, and by some I mean patches here and there but not a foot! I live like 20 min from Minneapolis tho in Blaine
[Nexus 6  Original Android Development] tiernan22:
I had that problem too because my wireless charger is small compared to the size of the phone. Couple that with a rounded back and it's tough. The inductive coil is at the bottom of the back close to the micro usb port.

I haven't had any issues on this kernel since I started positioning it higher. It could be argued that I just sleep right through it though. :D
[Nexus 6  Original Android Development] kornklown69:
on 1.02 is all four cores not active anymore? i noticed my fourth core is usually offline

edit:switched to on demand then back yo ElementalX gov seems to be online again, weird.
[Nexus 6  Original Android Development] drawde40599:
CM is including Bootloader within the nightly ? Not separate
[Nexus 6  Original Android Development] flar2:
I currently have no hotplugging enabled, so if a core goes offline, there's nothing to bring it backup online automatically.

If we decide to stay with four online, I will have to fix up and re-enable the custom hotplugging.
[Nexus 6  Original Android Development] flar2:
I'm keeping an eye on the hsic wake lock this week too.

One thin to remember is that wake lock accumulates while the phone is awake, so I'm mostly interested in stats while the screen is off only.

If you are on mobile data and using your phone, it will add up quickly.

I noticed that it's triggered by an IRQ, which fires every few seconds whether the phone is awake or asleep.
[Nexus 6  Original Android Development] Remoteconcern:
My wakelock is always massive but I'm always on mobile data. I've not noticed any battery life improvements with the wakelock altered as per lean kernel.

I have noticed the frequencies are very jumpy with the new floor frequency. Anyone else? Constantly going up and down even at idle.
[Nexus 6  Original Android Development] flar2:
The commits in lk won't have any effect because the irq is often triggered more frequently than the timeout. Not sure my commit does anything either, I'm just trying to shave microseconds basically.

The frequency will seem to jump a bit more using a monitor like the Dashboard in ElementalX app, because after any increase in frequency, it makes a stop at 960 on the way back down. Before it was jumping to max and immediately back to min so quickly that a monitoring app wouldn't even see it most of the time.

I don't expect the floor freq to make a difference battery-wise, because 960 is not that different 300, and it's not jumping all the way up and down the frequency scale so often. It might be better from the voltage regulator's perspective.
[Nexus 6  Original Android Development] simms22:
1.02 is doing very nice. on 1, i had random reboots only when scrolling up and down in the browser. 1.02 with ondemand/deadline and no reboots.. yet :)
[Nexus 6  Original Android Development] flar2:
I had my screen off since lunchtime (just over 2.5 hours), on LTE, and the msm_hsic_host wakelock is only 2m38s. That seems a little better than normal, I'll continue testing. Battery drain is about same as normal (down 1%).

If you are testing it, remember, msm_hsic_host continues to accumulate time even when the screen is on. So you need to set a custom reference point in your battery monitoring app.
[Nexus 6  Original Android Development] Lancez:
Something for you guys to read memory leak on 5.1
[Nexus 6  Original Android Development] Mervingio:
lucky you for ondemand not matter what I do ever got a reboot [emoji53]
[Nexus 6  Original Android Development] flar2:
Should have some nice improvements for you guys tomorrow night.

I'm feeling very good about this phone now :D
[Nexus 6  Original Android Development] BladeRider:
So do I,after flashing Lollipop 5.1 and your kernel
[Nexus 6  Original Android Development] Casper34:
I will hold off till tomorrows update..... well looking at the time, today's update.

Sent from my Nexus 6
[Nexus 6  Original Android Development] BladeRider:
Hi [MENTION=4684315]flar2[/MENTION], I notice that occasionally the S2W Phone Call Disabler causing my N6 to reboot during phone calls. Besides that, after ending the call (after a period of time), the sweep2wake will not work until i manually press the power button a few times in order to wake up the screen.

Overall, I am happy with the kernel. :D
[Nexus 6  Original Android Development] nEUTRon666:
If i update to 1.02, can i still have the old behaviour with boost and stuff ?!
[Nexus 6  Original Android Development] flar2:
You don't need that anymore

Don't need that anymore either, especially after the next release. 1.02 is already snappier than earlier veraions.

Gboost is still there, cpuboost is now enabled, and if you want more, enable mpdecision.
[Nexus 6  Original Android Development] BladeRider:
Wish I can give u a BIGGER thanks !!
[Nexus 6  Original Android Development] bigxie:
In case anyone is wondering, this kernel works fine with the new 5.1 (LMY47E) build that Google just posted.

I didn't bother checking if the default kernel was even changed from LMY47D before flashing ElementalX :p
[Nexus 6  Original Android Development] manup456:
Yeah I flashed the kernel over LMY47E and all is well for me to. I did backup stock ROM with stock kernel just in case, but so far so good.
[Nexus 6  Original Android Development] flar2:
I didn't have time to finish things up tonight, will have to wait til tomorrow.
[Nexus 6  Original Android Development] purian23:
This is very acceptable, thanks lol
[Nexus 6  Original Android Development] antiochasylum:
No it's not. That's not how xda works. WE WANT IT NOW. NOW. NOW.

LOLOL kidding. :P
[Nexus 6  Original Android Development] Frozt:
Hey is there something special I have to do to use your kernel with euphoria it is not working with 5.1
[Nexus 6  Original Android Development] purian23:
This is flar2 kernel :) I'm not sure why it wouldn't be though.
[Nexus 6  Original Android Development] Frozt:
Well it boots the ROM but after going through optimizing apps it bootloops and restarts. Its the first time I have experienced an error like this lol

Nexus Titan 6
[Nexus 6  Original Android Development] simms22:
works great on 5.1 here. im using an aosp rom, rastapop. you have to be using version 1.0 or higher though, i recommend version 1.02 :)
[Nexus 6  Original Android Development] PDP///M:
Any way to turn this crap off where the cpu drops to 2265 max under 40% battery?
[Nexus 6  Original Android Development] simms22:
that same error happened to me when trying a different 5.1 rom. well, i was dirry flashing it. i clean flashed it and it flashed fine :)

---------- Post added at 09:44 PM ---------- Previous post was at 09:43 PM ----------

not that i know of.. yet!
[Nexus 6  Original Android Development] Frozt:
Yea but we are on too different ROMs.

Elementalx is the only kernel I use and if I can't use it on 5.1 I'm reverting back to 5.0.2 even though I love the performance boost.

Nexus Titan 6
[Nexus 6  Original Android Development] flar2:
Did you try a clean flash (ie, wipe data)?
[Nexus 6  Original Android Development] Frozt:
Yes of course I am anti dirty flash unless its a small update. I am going to try it again once temasek is done downloading, in case it doesn't work again I'm going to just flash it.

Nexus Titan 6
[Nexus 6  Original Android Development] purian23:
I'd change ROMs before ever going back to 5.0.2 lol. They did fix up a lot :)
[Nexus 6  Original Android Development] Frozt:
But its so hard to decide. I'm a blisspop junkie and I want all the packed in features. And I miss xposed as well I use unicon for a full system icon theme.

Any suggestions? I'm also waiting for liquid smooth.

Nexus Titan 6
[Nexus 6  Original Android Development] flar2:
Update is delayed one more day while I figure out how to make sure all ROMs boot properly. I know what to do, just have to do it. And also get some sleep so I can go to work in the morning.
[Nexus 6  Original Android Development] c@p:
Same ROM, same problem (ex 1.02)

Tapatalked with Nexus 6
[Nexus 6  Original Android Development] simms22:
have you tried a clean flash first?
[Nexus 6  Original Android Development] flar2:
I just have to make a minor tweak to my installer and it will work on Euphoria and everything else.
[Nexus 6  Original Android Development] Frozt:
Awesome! Will it still be 1.0.2?
[Nexus 6  Original Android Development] Lancez:
No, It'll be 1.0 all over again :eek:
[Nexus 6  Original Android Development] Frozt:
Oh that's great! maybe we can just jump from 1.0 to 5.1 Lightning Edition.

And make my phones camera emit a magical unicorn hologram I can time travel with

Maybe even realm jump. O.o
[Nexus 6  Original Android Development] Casper34:
Could be worse..... could revert back to .27 and Bork everyone's wifi!

Sent from my Nexus 6
[Nexus 6  Original Android Development] Frozt:
Haha right.

This is me until tomorrow:
[Nexus 6  Original Android Development] flyinj54:
Do u leave mpdecision on for hotplugging running on demand? I noticed turning it off pegs cores 3 and 4 at 1497 and never decreases for me which is touch boost freq I have set. Just curious.
[Nexus 6  Original Android Development] flar2:
Are you using the EX app to disable mpdecision? On the latest version I thought I fixed the frequency getting stuck at 1497 when going from mpdecision to disabled.

If it still gets stuck, just reset the min frequency to 300 and it will stay there.

This is why I always advise against messing with frequencies and hotplugging, best is to set it and forget it.
[Nexus 6  Original Android Development] flyinj54:
I'm actually using kernel aduitor. Possibly could be an issue with the app itself? Can anyone else confirm that this is not the case on flar2 app? I know I shouldn't tinker with it but I love to:). Thanks
[Nexus 6  Original Android Development] flar2:
It works in the EX app, although I'm about to break it slightly with the next kernel update (and then fix it tomorrow with the next app update)

mpdecision->disabled will still work, but after the update, mpdecision->custom hotplugging will make the freqs stick at 1497 (until tomorrow's app udpate:D)
[Nexus 6  Original Android Development] simms22:
i dont hotplug. i let all four cores stay enebled 100% all the time :)
[Nexus 6  Original Android Development] flyinj54:
Good stuff thanks
[Nexus 6  Original Android Development] flar2:
In version 1.00 and 1.02, there is no hotplugging at all. mpdecision is disabled and custom hotplugging is disabled. If a core shuts off for some reason, it will stay off. That's why in version 1.03 (which really is coming soon!) I will re-enable the custom hotplugging, but all it's going to do (with default settings) is put cores back online if they happen to be offline for some reason.
[Nexus 6  Original Android Development] flyinj54:
Awesome. Now I'm assuming that this all only has to do with your custom governor.? When running on the on-demand let's say whatever defaults that Governor has is how it will be controlled. Turn mpdecision on and you will have default hot plug and turn it off and you will have no hot plugging but shouldn't have any issues with a core falling off not coming back on. Once again I'm just assuming. Last question for the night I promise lol
[Nexus 6  Original Android Development] Frozt:
So this is what is causing the system to loop?

Ex app an integrated performance app conflicting?

And awesome 1.0.3

#lurking
[Nexus 6  Original Android Development] flar2:
Here's the next version, 1.03, for testing:

I had one of my cores go offline once, and a few users have also noted this. I'm guessing the thermal daemon was responsible. So, the hotplug driver is enabled again, but all it does is make sure all cores are online (ie: it brings cores back online if for some reason they were taken offline).

I made more changes to the elementalx governor, it's less aggressive but I hope it's still smooth in all situations. I will be doing more tuning for sure.

This should boot on all ROMs, but I can't possibly test them all.

Note: I didn't push it to the app yet, need to test first.

Download:

ElementalX-N6-1.03
[Nexus 6  Original Android Development] simms22:
didnt boot for me, with my usual setup. seriously! lol.

it bootlooped. then i flashed 1.02 over it, and it got that weird updating android bootloop. weird!

---------- Post added at 01:58 AM ---------- Previous post was at 01:37 AM ----------

ok, redownloaded 1.03, and flashed it again. booted fine the second try :angel:
[Nexus 6  Original Android Development] Frozt:
I was about to say "did you clean flash?" Haha.
[Nexus 6  Original Android Development] :
No more testing for you! :silly:
[Nexus 6  Original Android Development] teddy sheringam:
Great work with your kernel... Just bought your app... You earned it..?
[Nexus 6  Original Android Development] tiernan22:
Boots and runs nicely on DU 5.1. Well done, Flar. Great work...
[Nexus 6  Original Android Development] flar2:
^^Good, I need to hear that it's booting on the most popular ROMs. It should work with the latest changes I made to the installer, but I want to be sure before I push the update to the app. Can't have people bootlooping from the app.

Governor is one thing, hotplugging is another.

hotplugging was totally disabled in 1.00 and 1.02

In 1.03, it is enabled, but only to ensure that the cores are online. Without the hotplug driver, there is a risk of thermald or something else shutting down a core and then it never comes back.

Governor controls the frequency scaling, not whether the core is on or off.

It was because I was overwriting init.shamu.rc in the ramdisk. Now I edit the file in place.

The installer is really complicated, unpacking the boot.img, searching through files and editing certain lines, then repacking the boot.img with ElementalX. This ensures total compatibility, but needs to be well tested because there is potential for something to go wrong. Once I cover all cases, it works flawlessly.
[Nexus 6  Original Android Development] italia0101:
[MENTION=4684315]flar2[/MENTION] working well for me too, feels smooth!

PS: i'm loving your wake gestures app, quick question , is there a way i can enable / disable the service via tasker?
[Nexus 6  Original Android Development] flar2:
No, the intents are not exported. I'll try to remember to add that functionality when I next update the app.
[Nexus 6  Original Android Development] italia0101:
Awesome, would love it if you could do that!

No worries if its too much trouble, i'm currently using autoinput to enable it at the moment
[Nexus 6  Original Android Development] Z-Man™:
I know its been a few days but just catching up in the thread and saw this. Im just in east bethel, come through Blaine quite frequently, small world.
[Nexus 6  Original Android Development] mwebb34:
I'm on Validus ROM 7.0 5.0.2 and this kernal is running like a Lamborghini
[Nexus 6  Original Android Development] mwebb34:
Is there any other apps I need to add with this kernel? Thanks
[Nexus 6  Original Android Development] flyinj54:
It seems for me on 1.03 that cpu hot plugging keeps disabling itself. I am using kernel auditor app. Anyone else? Not sure if hot plugging is actually working or not since it keeps flipping the switch off
[Nexus 6  Original Android Development] jpierce:
Same issue here.
[Nexus 6  Original Android Development] flyinj54:
Thanks for confirming.
[Nexus 6  Original Android Development] mwebb34:
Deleted
[Nexus 6  Original Android Development] flar2:
You don't need an app, but I make the ElementalX app to control all the features

I have no issue with hotplugging disabling itself. It's impossible for it to disable itself. Something has to disable it.

Maybe its an issue with kernel auditor.

Or perhaps you misunderstand what hotplugging does on 1.03? It just looks like its disabled. There are supposed to be four cores online.
[Nexus 6  Original Android Development] flar2:
From the ElementalX app?

Go to settings and turn off Check for updates and it won't notify of updates.

There are also settings for the powersave/performance notifications.
[Nexus 6  Original Android Development] mwebb34:
What would be the recommended CPU voltage settings? I'm using kernel auditor. I have no issues with hot plug its staying enabled.

---------- Post added at 05:29 PM ---------- Previous post was at 05:24 PM ----------

There's a lot of settings and tweaks to play around with and I just wanna make sure I don't tweak the wrong one,that's why I'm asking what I should adjust and how much I should adjust.
[Nexus 6  Original Android Development] jpierce:
2 cores showed being offline along with hot plug disabled and I didn't disable it. Restored backup of 1.02 and all good, no worries.
[Nexus 6  Original Android Development] flar2:
Recommended voltage is default. Generally the default settings are best.

But I don't know if that app has correct settings for this kernel.
[Nexus 6  Original Android Development] flar2:
Something is interfering with the setting. Hotplug can't disable itself.

If you have the ElementalX app and have previous hotplig settings, wipe the app data.

If you have other kernel management apps, please uninstall them.
[Nexus 6  Original Android Development] mwebb34:
With this ROM I have omni performance in the settings,should I just use it and scrap kernel auditor?
[Nexus 6  Original Android Development] flar2:
I haven't used either of them, so I don't know. I would guess they don't have the specific settings for this kernel.

I wouldn't mess with frequencies and stuff like that anyway, best to leave alone.
[Nexus 6  Original Android Development] jpierce:
Will do. Only ElementalX for Kernel settings. Will wipe app data.
[Nexus 6  Original Android Development] italia0101:
I had the strangest drop in battery last night..

I pretty much went to bed on the line and you can see it dropped a tonne... Stranger yet is my wake locks don't show anything suspicious, you can see its not awake and my deep sleep is around 82%... Confused [emoji53]

A drop from 80% to 45% overnight?
[Nexus 6  Original Android Development] flar2:
Probably just a glitch. I wouldn't worry about it.
[Nexus 6  Original Android Development] teddy sheringam:
Hey flar2 when will you release version 1.03? Im currently testing and everything's fine... The app always telling me there's an update available... 1.02...lol
[Nexus 6  Original Android Development] :
Hmm, 1.03 seems to have brought back msm_hsic_host as a near-top wakelock for me. didn't have this issue on 1.02
[Nexus 6  Original Android Development] flar2:
No difference between 1.02 and 1.03 for that, another factor is responsible.