yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] resynx:
Lean has really been giving me consistently good battery life, something that is usually not easy to achieve for me :victory: Appreciate all the work you've put in Imoseyon! :)
[Nexus 6  Original Android Development] Pulsu:
Gotta say latest build (1.15) has been phenomenal.

First charge I got 6 hours sot and now second run seems that I get even more. :)

Everything what you can imagine syncing with default settings.. I only disabled ambient display.

Really great work! [MENTION=4899017]LMose[/MENTION]yon :)
[Nexus 6  Original Android Development] Krunk83:
I found a setting in chroma that prevents accidental wakeups and may mess with waking up the phone. I think this may be contributing to my issue of waking the phone. I've turned it off and will continue to test. Thanks again everyone that has helped.

Nexus 6
[Nexus 6  Original Android Development] Imoseyon:
I think that makes a lot of sense. Hopefully that is going to solve your issue - keep us posted.
[Nexus 6  Original Android Development] zephiK:
It says it in the settings that it may have a slight delay on screen wakeup.
[Nexus 6  Original Android Development] Krunk83:
I know but I didn't think it was to the extreme of not waking the phone and having to reboot. Hopefully this will fix it. Also, I thought that setting was more geared toward phone calls, etc.

Nexus 6
[Nexus 6  Original Android Development] timosuomi:
I've found that it's very sensitive. If your hand is anywhere near the proximity sensor your screen won't come on. Even if you're not covering the sensor, if you're within a few inches if it this happens.
[Nexus 6  Original Android Development] adrman:
I just turned it off. It made using haptic DT2W a hit or miss proposition.
[Nexus 6  Original Android Development] Krunk83:
Use both s2w and dt2w. It'll work every time.

Nexus 6
[Nexus 6  Original Android Development] spinkick:
So you recommend killing mp-decision? Is it for battery mostly or performance? What option to you run in lk-config?
[Nexus 6  Original Android Development] wrongway213:
Yes, I absolutely recommend killing it, I use option 1 in core configuration, 2 cores, cpu boost disabled. My min freq is set to 300mhz. It's for battery life - without disabling mp-decision my min freq would not stick at 300mhz, it would automatically reset itself to 1.4ghz - my phone would use WAY more processing power than it needs to perform minor tasks. Mp-decision is designed to give stock users a smooth experience - it boosts frequencies very aggressively and often when it is not needed. WIth mp-decision disabled even with only 2 cores enabled all 4 cores come online if load gets high.
[Nexus 6  Original Android Development] spinkick:
From what I read it reports 1.4 ghz but its really much lower than that on idle. How much difference do you see in battery life with mp-decision off? I'm worried about losing performance for the sake of getting just 15 more minuts of overall battery life a day. Is it a drastic difference, power saving wise?

What is cpu-boost used for? Ramping up even quicker?
[Nexus 6  Original Android Development] wrongway213:
It makes a huge difference and I notice no loss in performance whatsoever - I imagine my benchmarks on AnTuTu would be very similar to yours - I'm usually between 51 and 53k. I would say I get at least an extra hour of SOT if not 2 by disabling mp-decision with the way I use my device - I turn the screen on and off quite often. I don't understand cpu boost quite well enough to explain it to you, so I'm gonna let someone else answer that portion of your question to avoid misleading you or giving an incomplete answer - I will actually be curious to see if someone responds because I would like to gain a better understanding of cpu boost myself.
[Nexus 6  Original Android Development] lainemac:
Someone correct me if I'm wrong, but I believe CPU boost ramps up the CPU when touch is detected so as to keep everything smooth.
[Nexus 6  Original Android Development] wrongway213:
If CPU boost is just a synonym for touch boost then yes, that's what it is - I could have answered his question after all if they are the same, haha. Touch boost does exactly what you described to give the user the impression of a fluid, smooth, snappy and responsive experience - the good thing for those of us on optimized ROMs with optimized kernels (like lean), we don't need it to get great responsive performance - we have it already. Are CPU boost and touch boost synonymous? If so, that's how CPU boost works - if not, you just described touch boost for him lol.
[Nexus 6  Original Android Development] lainemac:
I thought they were synonymous, but I could be completely wrong haha.
[Nexus 6  Original Android Development] spinkick:
Haha, well Im sure with the braintrust we have here we will hash it out one way or the other, I really appreciate the quick explanation!
[Nexus 6  Original Android Development] Imoseyon:
mpdecision vs cpu-boost

Mpdecision runs entirely in userspace (ROM) and cpu-boost runs in kernel space (cpu governor). They both have similar goals though - they aim to improve user experience by artificially boosting cpu frequency.

They have some interesting differences like cpu-boost's ability to detect tasks migrating from one core to another, and boosting the latter core's frequency to quickly match the former. And mpdecision also hotplugs cpu cores based on userspace workload.

I don't have a strong feeling on either really. I'd say experiment with it - or when it doubt just leave things stock.
[Nexus 6  Original Android Development] spinkick:
which do you run? ;)
[Nexus 6  Original Android Development] natezire71:
Has anyone else noticed a change in the touch responsiveness after using the Color Control app? I thought it was the kernel, but once I uninstalled and rebooted, everything was normal again. I had difficulty inputting my lock screen pattern and difficulty scrolling.
[Nexus 6  Original Android Development] spinkick:
Not anything here.
[Nexus 6  Original Android Development] wrongway213:
+1, curious how the kernel genius himself runs his own goodness.
[Nexus 6  Original Android Development] Imoseyon:
hehe I mostly run stock configs because I have to ensure that everything still works well with default settings. I did run 4 cores on with cpu-boost off for a while and I thought it ran pretty well. :)
[Nexus 6  Original Android Development] smclaughlin3:
If i use lkconfig do i need any other kernel app. Thanks

1.15.2 what's different ? Thanks
[Nexus 6  Original Android Development] wrongway213:
Nope, lkconfig can do it all within lkconfig. The only app you need is for kcal control if you want it, not sure about 1.15.2 though.
[Nexus 6  Original Android Development] beyeond:
Yeah no need for those kernel apps. Lkconfig is brilliant and easy to use. Never have to worry about settings not sticking either.
[Nexus 6  Original Android Development] poczynek:
Ok so I got a log when my screen refused to turn on! Pages and pages of this...
[Nexus 6  Original Android Development] wrongway213:
In my experience it lives through every dirty flash of ROM and all kernel updates too, unless of course lkconfig has new settings added - even then, though, your prior settings will still stick. The new ones will just be defaulted until you set them. It really is brilliant indeed - I keep Trickster out of habit but I turn set on boot and notification and all that off - lkconfig is all you need.
[Nexus 6  Original Android Development] s2d4:
What ROM are you using?
[Nexus 6  Original Android Development] poczynek:
Blisspop.
[Nexus 6  Original Android Development] rignfool:
That's the powerhal being cranky about mpdecision....
[Nexus 6  Original Android Development] poczynek:
Ah ok yes it's happened with it both on and off.
[Nexus 6  Original Android Development] Yank555:
I've seen this in many configs, maybe even full stock ?

I've put on my todo to look at the ROM side what that's all about...

This likely needs disabling in the ROM.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.0.2 LRX22G on Yank555.lu v0.65 kernel.
[Nexus 6  Original Android Development] elijahah:
My device also seemed a little less responsive after enabling the color controls, and it seems smoother now after uninstalling. Might be in my head though lol.
[Nexus 6  Original Android Development] garyd9:
Got a spontanous reboot on .15 this morning. Phone was just sitting on a Qi charger in front of me, and suddenly got the google logo. Everything in the kernel is stock except some color tweaking. Attached /sys/fs/pstore contents (just the one file) gzip'd.
[Nexus 6  Original Android Development] natezire71:
There is definitely something wrong. I was having difficulty swiping up on the lockscreen.
[Nexus 6  Original Android Development] Damon13:
I am glad you mentioned it, I also got a spontaneous reboot early this morning but I was not able to pull any logs (will try for the next time, if it happens), I haven't mess the with the color tweaks yet.
[Nexus 6  Original Android Development] Imoseyon:
Thanks for the console logs. Unfortunately there's absolutely nothing there that indicates something bad happened to the kernel. It almost seems like the reboot was induced by the ROM. Were there any other files in /sys/fs/pstore?
[Nexus 6  Original Android Development] Imoseyon:
Was there anything before or after these lines? Also, see if you can grab dmesg next time this happens (i know that's a bit more challenging). It does sound like this is a ROM issue so far though (agree with [MENTION=2033478]Yank555[/MENTION]).
[Nexus 6  Original Android Development] garyd9:
That was everything in there. I agree that there doesn't seem to be anything unusual in there, but I figured I'd give it to you anyway in case I missed something in my quick scan of it.

The "ROM" (I really, really, really HATE when people call it that. It's NOT read-only when I can mount it read/write) is google's stock nexus 6 firmware LRX22XC (5.0.1) with the following system partition changes:

1. rooted (supersu)

2. build.prop: density changed to 500

...and (wow) that's it. I didn't even change liblights on this one.

I'll keep an eye out for it in case it happens again. If a good cause doesn't come up, you can always blame it on [MENTION=3292224]franciscofranco[/MENTION] ;)

Take care

Gary
[Nexus 6  Original Android Development] smclaughlin3:
imoseyon i know you said you tried 4 cores and touch boost off how does this differ from having the 2 cores online and them being used when needed battery life wise. would the latter mean a definite technical battery difference? thanks
[Nexus 6  Original Android Development] PhilPan:
Anyone have some sample settings they are using within lkconfig, to save battery.

What's everyone doing with the wake lock controls?
[Nexus 6  Original Android Development] Yank555:
OK, so I've just started looking into this to find at least located where this is coming from, it's definately also in AOSP (found the same for flo and hammerhead, those I also have locally) :

https://android.googlesource.com/device/moto/shamu/+/lollipop-release/power/power_shamu.c

Look at line 181.

Also, line 242 is where the dt2w is (potentially) activated all the time (at least it's the case on SlimLP).

So there's definately nothing to be done on the kernel side of things. I'll have a closer look when I have time to teach my own ROM build to stop doing that ;)

JP.

Edit : I get these on Flo, Hammerhead and Shamu as soon as I disable mpdecision.
[Nexus 6  Original Android Development] wrongway213:
disable mp-decision, option 1, 2 cores no cpu-boost

min freq 300

sensor_ind disabled, wlan and msm_hsic both set to 4, smb left enabled (never seen it lol)

Performance profile (stock one, I leave 8 untouched - believe that's Performance)

Faux sound and haptic dt2w on not that it matters
[Nexus 6  Original Android Development] jiv101:
Could you have faux sound enabled and viper also baked in and turned on
[Nexus 6  Original Android Development] wrongway213:
Yup, I do all the time. Well my Viper is not usually baked in, but I always have Viper and Faux both - they don't conflict. I have used Faux in the past on ROMs with baked in V4A, no problems.
[Nexus 6  Original Android Development] Imoseyon:
Offline cores should consume less power than online cores for obvious reasons. I do think the difference is smaller than we think especially if you take into account the overhead of offlining/onlining cores though.

Thanks for finding that. At first glance, it tries to write to the file descriptor being held by mpdecision and complains when it can't write to it. It's not obvious to me if there's a direct correlation between this error and the screen not turning on.

Those of you having this issue regularly, re-enable mpdecision and see if the issue disappears? Perhaps my method of completely disabling mpdecision is not entirely harmless - I may want to just modify sysfs node permissions like everyone else. ;)
[Nexus 6  Original Android Development] droidguy22:
Did you disable any wakelock options under "wakelock control"?

I have below wakelock stats at 60% battery level:

msm_hsic_host – 12667 – 1871

PowerManager-Service_Wakelocks – 12698 – 2626

Powermanager-Service_display – 9101 – 2702

Smb135x_wake – 7705 -4342

I see msm_hsic_host and Smb135x_wake can be controlled from lkconfig, is it safe to disable them? Any help is appreciated.
[Nexus 6  Original Android Development] spinkick:
See his post. My settings were even more locked down but I'm not sure they make much of a difference. You can disable those
[Nexus 6  Original Android Development] Yank555:
I simply do a 'stop mpdecision' and 'stop thermal-engine' for my kernel in my config script (runs as an own serice, like your's I think does as well) since I use in-kernel hotplug and thermal driver, I want both stopped.

That at least hasn't ever caused any wakeup issues at all on my end.

Don't think it's related with wakeup issues...

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.0.2 LRX22G on Yank555.lu v0.65 kernel.
[Nexus 6  Original Android Development] wrongway213:
As spinkick said, it's all in my post. I disabled sensor_ind entirely (0), left smb135x untouched, and set msm_hsic_host and wlan_rx_wake both to 4. Powermanag anything cannot be disabled - that wakelock means your device is in use, lol
[Nexus 6  Original Android Development] Imoseyon:
Yup I do the same thing with mpdecision (I don't touch thermal-engine though). Based on the power_shamu.c code, this will cause touch-boost errors because mpdecision is no longer listening on that socket. I'm going to experiment a bit with just permission changes (ie. trickster) to circumvent mpdecision.

Also, the wakeup problem is very rare or non-existent for most people. I haven't seen it myself for over a month. Not sure why for some people it happens more often.

EDIT: yup confirmed that with mpdecision stopped you will incur these touch_boost errors. Still not sure how detrimental this is.
[Nexus 6  Original Android Development] beyeond:
To me the wake up problem is a maybe twice a day thing where I have to hit power a couple times before it goes on. It's not even really an issue to me. It's easy to deal with that for the performance and battery life I'm getting otherwise from the kernel.
[Nexus 6  Original Android Development] Imoseyon:
Do you have mpdecision disabled? Also if your ROM has a feature that prevents accidental wakeups, disable it.
[Nexus 6  Original Android Development] IcipherPT:
Sorry for this question but are we able to change governor through lkconfig? Or this need to be done using an app?

Imoseyon, I really like your kernel, thanks for your hard work on this! :D
[Nexus 6  Original Android Development] Imoseyon:
lkconfig does not support changing cpu governors. I don't recommend anything other than interactive anyway.... But if you really want to, you can use an app like trickster or kernel tweaker.
[Nexus 6  Original Android Development] beyeond:
Yes I have it disabled and also have accidental wakeup disabled but only as of yesterday because I just noticed that option. I'm on a SlimpLP build for the record.

I haven't been paying attention to the wake up problem closely, but it's possible that changing the accidental wakeup option fixed it because I don't recall it happening today.

Will let you know after a little while of testing whether or not the issue persists.
[Nexus 6  Original Android Development] Yank555:
I've been running my shamu this way for months, except for the fact that it pollutes logcat and my OCD not liking to know this is happening (it's wasting resources on each touch), I've seen no drawback personally ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.0.2 LRX22G on Yank555.lu v0.65 kernel.

---------- Post added at 06:27 AM ---------- Previous post was at 06:21 AM ----------

Dunno if it's related to that option, actually, I have it enabled personally (stock SlimLP code on that end), all that can happen is active display not showing if you pickup the device while covering the proxy, but that's all there is. Power button always brings the display up for me on first hit... weird. That option is supposed to avoid active display from accidently showing while the device is in your pocket for example.

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.0.2 LRX22G on Yank555.lu v0.65 kernel.
[Nexus 6  Original Android Development] neobuddy89:
Delete /system/lib/hw/power.shamu.so to curb touch boost errors.

Also, which toolchain do you prefer to build?

ROM cooks:

Please use QCOM PowerHAL?

https://github.com/CyanogenMod/andr...mmit/b4e984746fb1e875ecedf637a6413410d8df1489
[Nexus 6  Original Android Development] Imoseyon:
Yup that will definitely remove the touch_boost errors lol. Is it completely harmless to remove it?

As for toolchain I use Christopher83's linaro toolchain.
[Nexus 6  Original Android Development] neobuddy89:
Well, I already removed it, no issue so far.

Best remedy is to use shamu built QCOM PowerHAL.

I replaced with Hammy built QCOM powerhal (not good idea but doesn't harm in anyway).

https://github.com/neobuddy89/shamu/commit/ef273edd1aae7319f35f853a3123dc70ecf64d8c

EDIT:

CPU Boost driver is good enough to provide all the required boost. If you use load_based_syncs = 1 and input_boost_ms = 500, device will be silky smooth. :)

The only thing that needs to be tested after removal of shamu HAL is wireless charging.
[Nexus 6  Original Android Development] suku_patel_22:
And maybe turbocharging?

Sent from my Nexus 6
[Nexus 6  Original Android Development] Yank555:
Or just remove touch_boost from PowerHAL : https://bitbucket.org/yank555-lu/sl...mits/23173f8ec2a351909e1108ff182cc93370654f3e

And also have PowerHAL stop activating stock dt2w all the time : https://bitbucket.org/yank555-lu/sl...mits/8ea2566dafd54d1e40994758cc3a921dbff71e0e

Works just fine, no more stupid log entries ;)

And cpu_boost is enough indeed, no need for more than one touch_boost in a system imho.

Though, I've also removed cpu_boost completely from my kernel (don't like the migration sync personally, works just fine without) and use my own 2-step touchboost (part of my CPU Hardlimit driver), all just running nicely now ;)

JP.
[Nexus 6  Original Android Development] franciscofranco:
Don't remove the PowerHal. It has other functionalities other than boosting the CPU on touch events. And it will also break future OTA's, they'll check for the .so file during the ota assert routine. Just leave it be, the log saying "omg no touch file error" is harmless. App developers know (at least they should) how to filter logcat for their own purposes, so they'll never see the log spam.
[Nexus 6  Original Android Development] creepinm3:
Loving this kernel. Getting through work and a good part of my morning with no issues and battery life is phenomenal. ✊
[Nexus 6  Original Android Development] Yank555:
Well at least for source compiled ROMs, OTA is less of a topic, and it's no big deal to keep PowerHAL with just removing the touch_boost bit.

The amount of log entries is pretty huge, so I think it's good to get rid of it, though totally agree, I'd not just remove the whole thing, either compile without that tiny bit or accept the log entries seems the proper way to go.

JP.
[Nexus 6  Original Android Development] akellar:
So will the kernel, root, etc. I think we're well down the road from worrying about if OTA's will work if we're using custom kernels.
[Nexus 6  Original Android Development] Imoseyon:
This thread should be called kernel dev central! :p

(kidding - all kernel devs are welcome and their input highly valued)
[Nexus 6  Original Android Development] Franzie3:
I noticed today with my Wifi turned off when not in use my battery drastically improves. I use to scale down to roughtly 75-70% before i hit 1 hr screen on time on my normal day to day use.....today im at just under an hour of SOT and down to 84% its also the first full day i turn mpedecsion off but i did that yesterday and didnt see much change. Maybe placebo effect maybe not.
[Nexus 6  Original Android Development] akellar:
Well yeah seems pretty logical that having Wifi turned off and not scanning if you aren't connected will save battery.
[Nexus 6  Original Android Development] Franzie3:
Well yea, but i think a combination of that and the other wakelock limits are making it a bit better then normal. on previous devices/setups it wasn't a big difference or at least noticeable enough to warrant me wanting to turn it off. I think i need to invest in tasker or something to automate a little better
[Nexus 6  Original Android Development] mugendon:
Talking about wifi, since 1.14 the stock battery stats show wifi always on although I don't have wifi activated while not at home.
[Nexus 6  Original Android Development] __NBH__:
I think that is a general lollipop problem that even exists on stock. The only way to get it to show accurately is to turn off WiFi and reboot the phone so it doesn't show in the battery chart.
[Nexus 6  Original Android Development] Circaflex:
b4 rocking with slim alpha :)
[Nexus 6  Original Android Development] Xileforce:
Where everyone getting slim :(
[Nexus 6  Original Android Development] lightsout:
I know! Someone send a brother a link.
[Nexus 6  Original Android Development] Xileforce:
Preach it!
[Nexus 6  Original Android Development] clothednblack:
I'll upload my copy when I get home from work if Cordell is cool with it. I'll let you know

Posted from a Nexus 6 running Slim Rom
[Nexus 6  Original Android Development] Circaflex:
the link was killed, slim said they should have official thread sometime tonight or tomorrow for us :)

now back to lean kernel!
[Nexus 6  Original Android Development] Imoseyon:
Confirmed this is an issue. I'll fix this.
[Nexus 6  Original Android Development] simms22:
do you have any idea whats causing this? on beta4 with ondemand/deadline, so far no lockup.
[Nexus 6  Original Android Development] lightsout:
Excellent thanks.
[Nexus 6  Original Android Development] simms22:
never mind.. just rebooted on ondemand :angel:
[Nexus 6  Original Android Development] epicnoob66:
https://www.dropbox.com/s/n3v8xz4u5jtblzq/Slim-shamu-5.0.alpha.0.5-UNOFFICIAL-20141128-1235.zip?dl=0

This is the slim build I'm running.
[Nexus 6  Original Android Development] glensta:
Thank you for the link, d/l the slim rom and this kernel, seems like a good combo. :good:

By Chance do you have a link to the slim rom forum? Just had questions about tethering and would like to read up on that rom?
[Nexus 6  Original Android Development] Pilz:
Glad to know it works, mine rebooted instantly the last time I tried to use it. I just flashed the beta4.
[Nexus 6  Original Android Development] Circaflex:
something isnt right on your end, try with b4 i just hit 50K while my device is syncing and i didnt get time to mess with cpu settings in trickster so im sure i could do better; not bad for an alpha
[Nexus 6  Original Android Development] simms22:
sometimes its only a minute or two. regardless, itll always end up freezing then rebooting.
[Nexus 6  Original Android Development] Imoseyon:
Had similar issues on hlte. Code aurora's version of ondemand is just broken. Either way I'll know for sure tonight when I'm back at home.
[Nexus 6  Original Android Development] simms22:
cool :)