yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] Macusercom:
So today I tested it again. Same settings as 10 pages before (GPU to 240 MHz although it often resets to 700 MHz), -75mV global voltage for the CPU, no msic_host wakelock, Play Services with disabled keep awake and disabled background data (made Play Services in battery jump from 12% to nothing) and AwesomePlayer instead of NuPlayer which caused 10% or even more out of 100% usage.

I seem to get up to 5,5h SoT. Standby time is awesome (1 hour on mobile and not even 1% is gone), but my reception never goes lower than 3 as I'm living in a big city. Ignore Dropsync for keep awake as it synced 1000 small files so no battery leak or issues here xP

So conclusion: My phone doesn't feel slower than before, but I get +1h SoT compared to stock with 4,5h SoT and on WiFi it doesn't drain as quick as on mobile, but saves more battery. This appears to be Vindicator. Handicaping Google Play Services appears to save a lot of juice, only location battery saving mode seems to be broken now (for cells, I think it works with WiFi). Will take a look into this, but mostly I use GPS.
[Nexus 6 Android Development] Xileforce:
You are still getting over an hour of wakelocks, and your music player seems to be using an abnormal amount of battery. Have you tried using a different player?
[Nexus 6 Android Development] Xileforce:
Which launcher? I'm using Nova and its working without issue. Have you tried a different CPU governor like conservative?
[Nexus 6 Android Development] wrongway213:
I used Rocket Player on my S5 but I have had nothing but problems with it on the N6 - I just use Eleven Music or Apollo now depending on the ROM.
[Nexus 6 Android Development] jarjar124:
Device is staying awake for some reason. Help? Switched to this kernel hoping to get rid of my wakelocks.
[Nexus 6 Android Development] XXX_YOlO_XXX:
What do I do if the phone doesn't boot?
[Nexus 6 Android Development] Xileforce:
If you use synapse you can reduce a few or completely remove some of the wakelocks. For instance you can remove msm_hsic_host wakelock completely. The serial_DMA one though, I've never seen. I think maybe its BT related though. Aside from the serial_dma one your wakelocks actually look pretty good. Maybe someone better at wakelocks can help you better.
[Nexus 6 Android Development] jarjar124:
I already did, but the device always stays awake never going into deep sleep. Strange.
[Nexus 6 Android Development] Mistertac:
Hard to say from just those screen shots but... You have Facebook Messenger, WhatsApp, OK Google hotword detection and BlueTooth showing up pretty hardcore for those 3 hours lol

Those aren't kernel related Wakelocks. I do see the oddball BT ones we were talking about earlier however but compared to the other stuff you have going on there it's minimal.
[Nexus 6 Android Development] taranfx:
How do I enable sw2wake permanently?. lkconfig settings vanish after reboot.
[Nexus 6 Android Development] rignfool:
Lkconfig settings should remain on reboot... The ramdisk calls the script and applies all values...

What ROM are you using...
[Nexus 6 Android Development] taranfx:
It forgets on reboot for me. I'm on Temasek CM12 nightly
[Nexus 6 Android Development] Xileforce:
Like rignfool said. S2w should def stay enabled. I believe you can also enable it using an app like kernel aduitor and then set it on boot. Maybe you have an app or something disabling it on boot.
[Nexus 6 Android Development] rignfool:
Are you playing with xposed?

Reason being... Lkconfig seems to not like soft reboots... Or at least I noticed that in my testing
[Nexus 6 Android Development] Mistertac:
The dreaded " X - Word "
[Nexus 6 Android Development] philosophics:
I took the time to install Xposed on LiquidSmooth but then I decided I didn't need it anymore. There is absolutely no reason I need it.

Sent by a Whale
[Nexus 6 Android Development] saramon:
Amplify, and YouTube adblock are good reasons
[Nexus 6 Android Development] Xileforce:
Lol. I can't say as though I've ever used xposed and I've been rooting since the G1 came out. From what I've hears tho its implemented in a pretty hacky way. I think it actually injects into art and modifies it. Probably not very secure especially considering it makes u use permissive selinux as well.
[Nexus 6 Android Development] Mistertac:
Amplify is definitely good stuff. That's about all I'd use it for myself however, like Woody said in the Amplify thread, I think I'm also going to wait a while before even thinking about installing xposed for that module... Just going to follow along and see how xposed progresses since it's still in the early stages for LP.
[Nexus 6 Android Development] Xileforce:
Wow! That's really good. And you didn't even UV. I would suggest at least a 36 UV across the board. One of the beta testers is a Bin 1 (poor soul...) So he's the ultimate test for stability lol. If it works for him we know it will work for everyone. Next build should squeeze out even more battery. Lowering the voltages for many regulators, as well as lowering the screens voltage and reducing the clock speed of the screen marginally as well. So far no detrimental effects. Mistertac got over 8h sot today with all 4 cores forced on and capped his max freq at 2.2. Does the 9% thing happen on every kernel or just this one?
[Nexus 6 Android Development] Xileforce:
Weird. Who knows. Maybe its some sort of thing put in to save the battery. I'm pretty sure lipos/li-ions don't like being discharged too low.
[Nexus 6 Android Development] Mistertac:
Alright here we go..

35 Min 2.2 Max

InteractiveX

FIOPS

Mako but with threshold set to 0 so all 4 cores are online at all times.

UV -36

ZRam ON

This is with Data mostly the entire time and Wi-Fi for only a little bit at the end of the day.

Tapatalk, Hangouts, Chrome, Texting, little Navigation..

My phone turns off at 5% but I plugged it back in at 10% no real reason to go any lower in my opinion.

Edit..

By the way I forgot to get my CPU Stats, however my phone was at 35mhz for most the time, then 1.5 then deep sleep.

So having 35mhz as your min certainly doesn't seem to hurt things. Whenever I'm not interacting with the phone the 4 cores idle at 35 and there's honestly not much jumping around like you'd think.
[Nexus 6 Android Development] Xileforce:
My sot on latest test build after adding a few more patches. Running min max at 2.88, all cores locked on. Fiops and GPU on performance to kill the lags. Overvolted 100mv. 8 hours is so lame. Get on my level. hoping I will get around 30-40 hours sot by the time I hit 10%.
[Nexus 6 Android Development] Mistertac:
Seems legit lol

No reason you can't get push for 48 hours!

---------- Post added at 06:13 AM ---------- Previous post was at 05:30 AM ----------

After an hour of sot using Hangouts, Tapatalk and Chrome this is what the CPU Stats are...

Thats a great representation of what everything looks like at the end of the day too.
[Nexus 6 Android Development] philosophics:
There is no way!

I must be doing something wrong...

Sent by a Whale
[Nexus 6 Android Development] Xileforce:
Lol I wish I got 13h sot :(. But mistertacs is legit. Yesterday he got like 7 1/2. And he uses a lot of BT. Must say tho. Mako hotplug with load threshold on 0, conservative governor seems nice what's your settings?.
[Nexus 6 Android Development] philosophics:
I think trickster and faux are conflicting with one another. Really wanted to try zram and couldn't find anything else to enable it so I took the plunge. But today, my phone was hardly used and it was dead before the end of my work day.

After I copy down all my settings, I'm more than likely removing trickster.

Currently, I'm using what was recommended.

35 min, 2.8 max

InteractiveX

Mako Hotplug, didn't change the threshold

1536 fiops

Intellithermal active with stock set from trickster, I think that's 60 80

Gpu left alone

Zram enabled

Oh, I'm bin 7. Not sure where to go with that...

Sent by a Whale
[Nexus 6 Android Development] Xileforce:
Hmmm. Yea def don't use two apps. Sometimes they tweak out and do stuff like force cores to max freq. Plus faux does everything :). I'll be interested to see how it goes!
[Nexus 6 Android Development] philosophics:
After removing trickster and using just faux, these are my settings. Please recommend changes if needed.

35 min, 2.8 max

InteractiveX

Mako Hotplug, didn't change the threshold (not sure how with faux)

1536 fiops

Intellithermal active with stock settings

Gpu left alone

Zram enabled with 35mb

Clear vfs cache after boot enabled

Power Suspend is set to LCD_PANEL

Tcp is set to reno

Battery temperature throttling enabled and left at default settings.

As for voltage settings, I dropped everything by 36 along with the following changes as a bin 7.

35 - 500mv

98 - 500mv

300 - 596mv

345 - 606mv

422 - 616mv

499 - 626mv

576 - 636mv

652 - 646mv

Now after I set all this up, I was typing this post and the device locked up and rebooted. This was most likely cause due to these settings, ha! But to be fair, my hot-spot has been on for about 5 hours as well streaming Netflix. That could be a reason as well but I wouldn't bet on it.

Further testing is needed...

Also, I tried to get the log but for some reason, it wasn't there to be found. I may be looking in the wrong areas? /sys/fs/pstore, correct?

Sent by a Whale
[Nexus 6 Android Development] jarjar124:
It's funny since I didn't use WhatsApp at all today. My Google search doesn't have the hotword detection on too. Hmm. Thanks. I'll need to look into it
[Nexus 6 Android Development] Mistertac:
Wasn't that one related to Android Wear? I think one or two of the testers had that popup and I don't remember what the fix was.

Jarjar.... Do you use Android Wear?
[Nexus 6 Android Development] jarjar124:
Yes I do. But that shouldn't be making my device stay awake? No?
[Nexus 6 Android Development] Xileforce:
It will keep your device awake because it needs to pull data from your phone every so often. Not constantly awake ofc but it will wakelock.
[Nexus 6 Android Development] Xileforce:
I'm not sure ATM. I don't run chroma so I can't say why it wouldn't boot. I do recall reading about some changes he made very recently that broke kernels. You could try an older build of chroma I guess.
[Nexus 6 Android Development] Mistertac:
Well technically no it should not keep your phone awake at all times, I'm trying to remember what was done to fix this ( I don't use Android Wear myself )

I'm leaning towards factory resetting your watch?! Or whatever it is lol I can't be 100% though and I'm sure that's a pain, so maybe you'll want to wait for someone else's input.
[Nexus 6 Android Development] jarjar124:
I understand that, but usually my device still goes into deep sleep. If you look here, it's not. Sorry about this guys. Not trying to be very pushy.. I just want to know what I'm doing wrong.
[Nexus 6 Android Development] Xileforce:
Definitely seems to be WhatsApp and Facebook messenger. Have you tried greenifying them?
[Nexus 6 Android Development] jarjar124:
Can't since I need the push notification lol. I disabled blue sleep before now I turned it back on. Now it's entering deep sleep. Interesting..
[Nexus 6 Android Development] Xileforce:
Interesting. Maybe disabling it isn't always the best. Ik some people disable without a problem, but maybe for some devices its bad.
[Nexus 6 Android Development] omvir:
Xileforce.. I'm not sure if you're already aware but when using the kernel in quad core mode (0 threshold), if the battery drops to 15 or below, 1 core goes offline permanently. Charging it to 100% doesn't bring the core back online.
[Nexus 6 Android Development] Xileforce:
Hmmm interesting, I've never tried this. I'll have to give it a shot. Thanks for telling me.
[Nexus 6 Android Development] bbedward:
I've noticed cores permanently offlining without mpdec. I've reworked zen decision to solve the issue, but ignoring onlining cpus by a configurable battery amount.

After I do some testing it may be good :p
[Nexus 6 Android Development] Xileforce:
But zen decision wouldnt work with mako right? :(
[Nexus 6 Android Development] hellsgod:
I've posted a comment in [MENTION=2632235]bbedward[/MENTION] thread to that matter. I also encountered this issue with a core stays offline after it hit 15% battery. Also other frequency locks like one or two cores stuck at max, or touch boost freq.

hells
[Nexus 6 Android Development] Xileforce:
Yea just saw that you had this problem too. Interesting. Is there some sort of power saving that kicks in at 15%?
[Nexus 6 Android Development] bbedward:
It will, but it'd probably be better to implement the functionality into mako. What I'm testing doesn't have the same type of functionality, it's all simpler:

- Enable all CPUs when screen comes on after X amounts of milliseconds (configurable)

- Don't do anything if battery is less than 15% (configurable)

The first one ensures cores come on in the event they don't from normal suspend resume (not sure why they don't always come on, but I've seen it happen)

The second one respects msm thermal defaults which unplugs cores on its own at <= 15% battery. It'd be best to read this from msm thermal itself but since the values are all defined in user space that's impossible.
[Nexus 6 Android Development] hellsgod:
Yes, one core gets plugged out by thermal.

I'll switch to zen-decision then. I don't care about active hot plugging anymore :)

hells
[Nexus 6 Android Development] bbedward:
I don't think there's any conflicts if you used both :) zen decision just handling the edge case of cores not coming online. (I only have this problem without MPDec enabled)

I need to test it a bit, and make sure the battery stat I'm reading is accurate.
[Nexus 6 Android Development] hellsgod:
Alright. Looking forward to give it a shot, thanks :)

hells
[Nexus 6 Android Development] tansuperman:
This has been my favorite kernel so far. I've always been a Franco guy, but might switch. Been on this for a week, and love everything so far. Battery is phenomenal.
[Nexus 6 Android Development] bbedward:
BTW people using msm hotplug don't have that issue I'm assuming, looks like it brings cores online with screen on, but it doesn't respect msm thermals choices.
[Nexus 6 Android Development] dwang:
for those who don't like using synapse, kernel adiutor has just been updated with the wlan_rx and msm_hsic wake lock sliders.
[Nexus 6 Android Development] wrongway213:
I would not be surprised at all to hear MSM does have issues with thermal as I consistently experienced thermal throttling on Hydra Kernel (it was set to 70C) until I disabled it entirely, even at perfectly normal temperatures with MSM hotplug, up until thermal was removed from the kernel as an option. .. all was well from there (well, with defaults - I had made the issue disappear by setting it to 80C). Setting to 80C to avoid throttling is nothing I have ever had to do with any other hotplug/even on any other kernel.. I'd expand on it but I sincerely doubt I'm telling you even a slight bit of information you don't already know - just hoping someone else reading this will benefit/understand things better based on my experience.
[Nexus 6 Android Development] Xileforce:
I believe 80c is stock thermal throttling default. I forget where I saw that though....
[Nexus 6 Android Development] bbedward:
Psst: [MENTION=4517211]Xileforce[/MENTION] [MENTION=647113]hellsgod[/MENTION]

https://github.com/bbedward/ZenKernel_Shamu/commit/d0248c34444eab25149c53a3564b858917dfdc50

Running it myself. Verified all calculations work correctly, haven't had any issues yet. But I haven't been running it long.
[Nexus 6 Android Development] hellsgod:
Thank you! Zen decision doesn't need the rq stats, right? Ive disabled them for mako hp. So if I revert mako, should i also reenable the rq stats? :)

hells
[Nexus 6 Android Development] bbedward:
No it doesn't need any of that :)
[Nexus 6 Android Development] Xileforce:
Oooooooo I think I may have to try this.
[Nexus 6 Android Development] wrongway213:
Everyone adding all these Franco conservative on steroids commits and possibly nuking Mako hotplug makes me a sad panda:( fingers crossed bbedward is right and they can coexist peacefully.
[Nexus 6 Android Development] simms22:
its either 65 or 70C where thermal throttle starts by default(stock). 80C is too high for thermal throttling, even though i either disable it completely or set it at 98C :angel:
[Nexus 6 Android Development] bbedward:
ZenDecision is simply a separate handler that happens to handle the specific edge case that mako isn't covering when mpdec is disabled. (Cores are never coming online in certain situations)

They can coexist at the same time, but the "best" solution to use both would be to execute the up_work and what not on the same worker thread mako hotplug is already using, whereas zen_decision is agnostic of all that and allocating its own work queue and creating its own worker threads.
[Nexus 6 Android Development] hellsgod:
[MENTION=2632235]bbedward[/MENTION]: I'm getting this error:

arch/arm/mach-msm/msm_zen_decision.c: In function 'fb_notifier_callback':
arch/arm/mach-msm/msm_zen_decision.c:135:7: warning: suggest explicit braces to avoid ambiguous 'else' [-Wparentheses]
error, forbidden warning: msm_zen_decision.c:135

hells
[Nexus 6 Android Development] bbedward:
Fixed in this cleanup commit: https://github.com/bbedward/ZenKernel_Shamu/commit/dcf804a71801a37b7244bd5daf88ab710d17af31
[Nexus 6 Android Development] hellsgod:
I was to slow, sorry :D Didn't fetch again before I hit build :D

hells
[Nexus 6 Android Development] USA-RedDragon:
You need to learn to whisper quieter. I think the whole thread heard
[Nexus 6 Android Development] bbedward:
I've been drinking pre-cavs game :D , everybody's louder after a few cocktails :p
[Nexus 6 Android Development] wrongway213:
Man... I don't drink alcohol but my avatar should serve to explain I too am pre-gaming:p So excited to see how this all plays out man
[Nexus 6 Android Development] simms22:
lol, how does sublime suggest pregaming? im anything, id say it suggests pre-puffing :silly:
[Nexus 6 Android Development] Macusercom:
I could try another player, but I don't consider it high. I've listened to music for over 2,5 hours so 3% including using the app itself a bit should be fine or am I wrong? 45 minutes are only the wakelocks when the screen was off ≠ playing time.

Wakelocks over an hour? Are you talking about CPU oder kernel? PowerManagement is over an hour, but I thought that's normal?

For CPU Rocket Player stayed 45 min in the background, I called someone so there's the call wake lock and Dropsync had this weird folder today with 1000 files which kept it awake at home (doesn't normally happen). The rest is is just a minute or so which I don't consider long.

Please correct me if I'm wrong that's just my thinking. I might be absolutely wrong about everything :S

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6 Android Development] wrongway213:
Tis exactly what I meant by pre-gaming, haha.. tis my pre-breathing, pre-flashing, pre-working, etc., lol. But to be honest, Sublime were all about getting wasted lol. "Drunk driving is what I like to do, I like drunk driving with you" is literally an entire song of theirs. Those are the whole lyrics, it's like seventeen seconds long and was actually not sung by Brad, but by their manager, Miguel for some strange reason. (I am a Sublime superfan, I have the 40 oz sun logo tattooed quite large on my arm and everything even though Brad died when I was only 7 - music just speaks to my soul).
[Nexus 6 Android Development] simms22:
i am still a huge fan, and was when Brad was still alive as well. a day doesnt go by without me listening to something sublime. some of there songs are just silly, but some of their music use words to live by :)
[Nexus 6 Android Development] wrongway213:
If it wasn't for "Greatest Hits" (the song, not the album) I would be a dead man, and I do mean that literally. Sublime got me through the darkest points in my time on this Earth - honestly I find peace in Brad's untimely death because I know for an absolute fact that he saved lives, at least one.. not a day goes by here without some Sublime either.. always knew you seemed like good people for a reason :p
[Nexus 6 Android Development] Xileforce:
Listening to music, especially if the screen is off should consume very little power. AFAIK most of the work isn't done on the CPU. I think its all done by special audio processors and stuff on the soc. That's why I suggested trying a different app.
[Nexus 6 Android Development] Xileforce:
So how would it work if we left it on hotplugging mode with mako? Would it try to force all 4 cores on despite mako letting it unplug cores?
[Nexus 6 Android Development] Macusercom:
Hmm interesting. I could try CM's Eleven for a while, but I have to say that Rocket Player is by far the best. Maybe it uses more CPU as I doubled the buffering cache? Moreover, Rocket Player is not the best coded app so maybe it always uses the CPU instead of the audio processor. Will look into this as it's still a huge wakelock.

Gesendet von meinem Nexus 6 mit Tapatalk
[Nexus 6 Android Development] Xileforce:
I've always used google play music so sadly I can't help much in this respect :(
[Nexus 6 Android Development] bbedward:
Yea ZD would force cores all online if battery is >= 15% (by default) when the screen comes on.

But Mako runs on a timer, and continuously makes its own determinations whether to remove cores actively. So when screen comes on there will be a very short time until mako begins making its own decisions.

However, it'd be "best" (theoretically) if zen_decision logic was merged into mako if you wanted to use both. It's a better way to do it, but they will both also work separately from each other without issues (just more overhead from an extra worker thread - but not that much).

Partly why the wake_delay_time tunable exists. By default (after screen comes on), we give 1s to either the PM wakeup functions or another hotplug driver to bring the cores online. If nobody else does it after wake_delay_time we do it ourselves.

Neither mako hotplug (not in all-core on mode) nor msm hotplug will respect the defaults of the MSMThermal driver. Normally we shut cores off at ~14% and maybe around ~5%. Neither of those drivers will care and will turn those cores on anyway in those situations. ZD's battery calculation means it can respect the MSMThermal driver settings (although we can't read from MSMThermal directly)
[Nexus 6 Android Development] Xileforce:
OK that makes sense, I'll have to try it and add the new settings to synapse.
[Nexus 6 Android Development] wrongway213:
I'm still unsure if I get a little smarter everytime I read one of your posts just based on the exposure principle, or if I get a little dumber based on periods of prolonged mental confusion :p In all seriousness though, what is the benefit of respecting MSMThermal driver? Does it actually really DO anything at any point during use, is it somehow unsafe to disable, or does it honestly just keep your phone from dying quickly when you hit 15%? If the latter, I could care less, but if if's a safety issue on the other hand...
[Nexus 6 Android Development] hellsgod:
[MENTION=2632235]bbedward[/MENTION]: Is there a chance for a bug in the thermal intervention? I had my first thermal shutdown ever :D

hells
[Nexus 6 Android Development] simms22:
did you reach 100C? i try and try, when plugged, at 3033mhz even. the hottest ive gotten it is 85C. if it didnt reach 100C, its not a thermal shutdown.
[Nexus 6 Android Development] bbedward:
Not sure, ZD doesn't actually interact with the thermal driver in any way. They behave entirely separately from one another. Nor does ZD affect voltages or anything like that, it strictly brings cores online at >15% battery when screen comes on.

Maybe I need to add a temperature condition, potentially MSMThermal shut down cores because of high temperature (but not because of battery) and ZD brought them online? Regardless i've never seen any thermal activity really in dmesg.

It disables cores at 15% battery and such. Potentially due to a weak sauce power supply. Maybe due to other considerations. Not sure exactly. Maybe compensation for no more active hot plugging in MPDec.