yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] Cristiano Lira:
I have some news, after testing lazyplug builds using a config that is close to [MENTION=5579519]jer_ying_fd[/MENTION]'s idea - using pegasusq I noticed that it generally uses 2 cores for heavy tasks (although it boosts more than 2 cores too, but these are boosted for a lower amount of time) and could see some improvement using lazyplug. Here are the results of my quick tests, using only r08 versions, varying only hotplug and toolchain:

90-80% with lazyplug-ubertc7.0: 38m35s

90-80% with lazyplug-ubertc5.3: 40m18s

90-80% with mako-ubertc7.0: 37m33s

The rest of the configs are:

CPU minimum frequency of 384Mhz, and 1512Mhz maximum.

GPU governor: on demand with 200Mhz maximum frequency.

Undervolt: -80mV.

IO scheduler: noop

Also set freq_for_responsiveness setting from pegasusq to 1026000.

Another thing we can notice from the tests is that with ubertc5.3 we have better battery.

Final considerations: yet not having an governor that work ideally as [MENTION=5579519]jer_ying_fd[/MENTION] said we had some gains regarding battery life and I think that if we find a CPU governor that work as he idealized (by his words: "the 3rd and 4th CPUs will use low frequencies until there are heavy loads.") we could do something incredible.

PS: just web browsing, without playing musics or videos or gifs, mostly just facebook.
[Nexus 4 Android Development] ivke101:
How about alucard TC and governor? In lollipop days with unleashed kernel I have great result!

Poslano sa mog Nexus 4 koristeći Tapatalk
[Nexus 4 Android Development] Cristiano Lira:
How does this governor works?
[Nexus 4 Android Development] ivke101:
Alucard is based on ondemand but has been heavily tweaked to bring better battery life and performance. It has been known to be battery friendly without sacrificing much performance.

Copy pasted from XDA

http://www.androidmodguide.blogspot.de/p/blog-page.html?m=1

Poslano sa mog Nexus 4 koristeći Tapatalk
[Nexus 4 Android Development] spezi77:
Sounds interesting. Maybe an option to test in a future build. ;)

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] spezi77:
What do you mean with alucard TC? Hotplug?

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] GiovanniArpino:
Soory,what's the difference between aosp and bs version of this kernel?it's the first time I hear bs
[Nexus 4 Android Development] dragos281993:
AOSP is meant for AOSP based ROMs, like Chroma or Pure Nexus, and the BS version is meant for BeanStalk, hence the abbreviation.
[Nexus 4 Android Development] GiovanniArpino:
Thank you!
[Nexus 4 Android Development] kanishkad:
I will try this, thanks for sharing.. :)

Keep up the good work :good:
[Nexus 4 Android Development] ivke101:
Yes hotplug sorry

Poslano sa mog Nexus 4 koristeći Tapatalk
[Nexus 4 Android Development] bart.found:
I'm testing this! Reverted to r07 as I feel it's more balanced.. Lazyplug seems to be too hungry, at least for me.
[Nexus 4 Android Development] Cristiano Lira:
"64. DevilQ

An aggressive pegasusq governor which keeps the hotplugging at max 2 cpu cores to offline). This is pretty much a more optimized pegasusq for phone's with quad core processors."

It sounds insteresting, although I can't understand correctly what this part says: "keeps the hotplugging at max 2 cpu cores to offline". What does it mean?

http://xdaforums.com/general/general/ref-to-date-guide-cpu-governors-o-t3048957

---------- Post added at 12:58 PM ---------- Previous post was at 12:42 PM ----------

For me, lazyplug-ubertc5.3 is better at battery than any other option, try it with pegasusq governor, with frequency_for_responsiveness set to 1026000, GPU governor set to ondemand, and maximum frequency of 200Mhz, undervolt of -80mv and noop IO scheduler and tell the results.
[Nexus 4 Android Development] filjusz:
It is possible to add 487 mhz GPU overlock to hellspawn kernel?
[Nexus 4 Android Development] bart.found:
I tried this setup, you wrote it some posts above (I didn't modify GPU tab anyway) and I felt it a bit too laggy... It's only me?
[Nexus 4 Android Development] Cristiano Lira:
Not lagging to me, and you need to modify GPU as I said or you won't get 4m+ per % sot -at least it's true to me. If it's any help, I'm using Dirty Unicorns as it's the best at battery/smoothness balance for me.
[Nexus 4 Android Development] spezi77:
Nothing is impossible. Do you think that 87MHz makes a big difference? ;)

I used CPU/GPU o'clocking in mako, but I really couldn't feel significant performance improvements. In my point of view o'clocking can be described as "placebo effect".. and as every device is a little different, it might even give us negative impacts, e.g. your hardware could be damaged or get worn out faster. Just my 2 cents.. :p
[Nexus 4 Android Development] filjusz:
I have CM 13.0 by stephanMC and YayPrime kernel and that 87 mhz make big difference especially in games but its only my opinion, maybe its placebo.
[Nexus 4 Android Development] dragos281993:
The extra MHz pay off especially if you have the "force GPU rendering" option activated in the Developer options section. It doesn't have a huge impact on the battery though. Anyway, if it takes too long to implement that, then don't bother adding it, but if it doesn't, then it wouldn't be a bad option to have there.
[Nexus 4 Android Development] spezi77:
OK, guys you have provided good arguments. Then let's add extra MHz in GPU for experimental purposes. :)

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] g33k0 b3lk0w:
Since I flashed your kernel and changed nothing but Undervolt -120, my phone can't go to deep sleep at all, I am checking now with stock purenexus kernel to see if kt makes difference, just maybe a possible problem since at top of my battery stats was android os
[Nexus 4 Android Development] Mrcactuseater:
It's probably the fact you undervolted so much. Try it without undervolting and check back

Tapatalk'd from my Twisted, Despaired Nexus 5x
[Nexus 4 Android Development] spezi77:
R09 is up.

You might be interested in why it doesn't include layzplug. To my suprise lazyplug wasn't working/enabled in the test builds (which means that you were using no hotplug solution at all). After I have added support for altering the lazyplug tunables in KA, I have observed quite a few issues (e.g. black screen and reboots) with lazyplug. Currently I have no clue if I am able to fix it.

If someone is interested in figuring out/testing lazyplug, you can use my r08-lazyplug-build with the KA-mod attached below.

But be warned, that this could result in total data loss. In my case I had to restore a nandroid backup of my current ROM.

If possible please take a logcat! This could be useful to further investigate on those issues..

Have a nice day!

;)
[Nexus 4 Android Development] dragos281993:
Most probably the UV is NOT the cause but, to be safe, just set the voltage value back to stock, reboot the phone and then start monitoring the phone's activity again. The easiest and most detailed way is with a wakelock monitoring app. I suggest BetterBatteryStats which you can find here on xda. It will show you how much time your phone spent asleep while the screen was off, the kernel wakelocks and the apps that are usually the culprits for such behaviour (in the "Partial Wakelocks" section). The phone's battery stats found in settings are way too vague to draw a conclusion to what's causing these problems so a dedicated app is recommended for more detailed stats.
[Nexus 4 Android Development] Cristiano Lira:
No cores are being turned off after I activated it. I think it's not working. But the sleep of death is, ouch. Going to test r09....

Edit: it's actually it's behavior and I think it's really better than turning the cores on and off all the time, like my tests showed. I'm noticing that using no hotplug at all (or leaving all the cores on) is better than any hotplugging solution that keeps turning cores on and off, and as lazyplug fix some problems with the always on approach it really could be the best solution for us.

Another thing, after reading about it here: https://bitbucket.org/arter97/andro...mits/d8b40b44754fb7e0aa336c3654f63701e7364b7d, this dual-core mode thing is interesting, what happened to it, the dev abandoned it?
[Nexus 4 Android Development] spezi77:
It seems that changing tunables in KA for lazyplug has no effect. If you set nr. of available cores to 2, it jumps back to 4 cores.

I could not record a logcat unfortunately, because my ADB connection didn't work. Could you provide a logcat, by chance?

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] kol1124:
Anyone testing Alucard for a while?

Is it better than AutoSMP?

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Android Development] Cristiano Lira:
Yep. I have edited my post, take a read.

---------- Post added at 11:26 AM ---------- Previous post was at 11:25 AM ----------

I think it's the same, and both are worse than having no hotplug at all.
[Nexus 4 Android Development] dragos281993:
From my short testing, there seems to be a bit more stutters here and there compared to AutoSMP, with like 45,50% more. That obviously makes me think that Alucard is more towards battery life while AutoSMP more towards performance. Further testing is required, of course, but this is my initial conclusion. And that's obviously a good thing. If I'm right and the new hotplug gives users a bit more battery life, they will have 2 very solid choices.
[Nexus 4 Android Development] kol1124:
Thanks guys, anyway great job by [MENTION=5091819]spezi77[/MENTION] ?

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Android Development] Cristiano Lira:
I think the only problem with lazyplug is that it is unable to come out of low freq state after entering in idle and this is why the phone freezes when it soft reboot itselfs - the phone boots with lazyplug already activated.

last_kmsg when I manually rebooted when SoD happened: http://pastebin.com/e9BHrf7V

Waiting to auto-reboot happens again so I can take a log and will edit this post asap.

Edit: it don't save last_kmsg after it auto-reboots.

I took a dmesg if it's any help: http://pastebin.com/dZ54R6ME
[Nexus 4 Android Development] spezi77:
Great, that's a good base for starting an analysis. Maybe I could also try to reach out for arter97 to get his opinion.

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] bart.found:
Check your wakelocks with better battery stats, probably it's a rogue app in background..

---------- Post added at 06:51 PM ---------- Previous post was at 06:49 PM ----------

So you fooled us for a week!!! :silly: Nice try! I hope you debug lazyplug.. because I'm really curious to try the "real" one!
[Nexus 4 Android Development] Cristiano Lira:
Also ask about the dual-core mode so we can implement it. :)

---------- Post added at 02:07 PM ---------- Previous post was at 02:04 PM ----------

It's almost the same, see: https://bitbucket.org/arter97/andro...mits/d8b40b44754fb7e0aa336c3654f63701e7364b7d

But it also fixes some problems with the “Always on” approach, so it's the best choice after all.
[Nexus 4 Android Development] spezi77:
Yep, I checked all of his commits, didn't forget a single one. I guess that there should be an important aspect which is different between flo and mako, and needs a special treatment.

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] dragos281993:
I'm curious to see what arter97 has to say.
[Nexus 4 Android Development] Cristiano Lira:
Have you seen Zen hotplug, [MENTION=5091819]spezi77[/MENTION]? It's used on hellscore for N6 and have the same approach, but it is only a little worse because it won't turn off any core even after a long idle state. But here he says that just because all cores are always on don't mean that it can't enter in battery saving idle state: http://hc-kernel.blogspot.com.br/2015/06/nexus-6-zen-or-mako.html. Maybe it could be a good option if we can't fix lazyplug.
[Nexus 4 Android Development] ivke101:
Charged to100% and flashed new kernel. Booted and changed in KA hotplug to alucard and governor to alucard. So what's going on?

Poslano sa mog Nexus 4 koristeći Tapatalk
[Nexus 4 Android Development] dragos281993:
Facebook, bro. Haven't you heard that this app is complete and utter s#!t and despite the fact that the company makes billions/year, they can't make a decent app ?

Even browsing your Facebook from the browser, is better than with the dedicated app.

First uninstall that joke of an app and make sure you forget about it forever.

Then go to the Play Store and download either "Metal for Facebook" or "Tinfoil for Facebook". Try them both and choose the one that you prefer.
[Nexus 4 Android Development] ivke101:
Battery is good. I mean how kernel is good.

From 100 to 72 is taken for installing kernel and then flat line. You understand wrong.

Poslano sa mog Nexus 4 koristeći Tapatalk
[Nexus 4 Android Development] dragos281993:
You've got almost 1h SOT. What else do you want ? At that rate, you'll end up getting 3.5, 4 hours SOT.

AND you didn't just flash the kernel, rebooted and the battery wait straight to 72%. The stats don't show any immediate reboot. What are talking about ?! You used your phone and that's why the battery went to 72%, most of the usage being taken up by the Facebook app. It's in the stats you posted.
[Nexus 4 Android Development] ivke101:
Halo, I don't complain!!!

I'm bragging because I never have so good battery! Read with understanding!

Poslano sa mog Nexus 4 koristeći Tapatalk
[Nexus 4 Android Development] espionage724:
Hi; I tried flashing this kernel and BS on my N4 about a week ago but didn't get past the Google screen. It was a quick attempt, so it could be possible I missed something or maybe I just didn't wait long enough.

I flashed TWRP, wiped all partitions and formatted data (so no OS was installed), rebooted back to recovery and installed BS, then the Gapps, and then this kernel. Is that the correct process?

Edit: Works fine now; not sure what happened the first time.
[Nexus 4 Android Development] kol1124:
What is the first wakelock?

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Android Development] dragos281993:
Did you download something that might've taken 5 minute ?
[Nexus 4 Android Development] kol1124:
No, I don't.

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Android Development] dragos281993:
This wakelock usually appears when you download something. Do you have "auto update" in the Play Store's settings turned on ? Some apps might've been updated.
[Nexus 4 Android Development] kol1124:
Yeah, that's the point. Thanks ?

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Android Development] arvindgr:
Thanks a lot for working alpha built. Since its for CM based ROM, I can't use this in my AOSP based chroma ROM, can you add s2w to your stable releases so that its there for everyone on all AOSP, CM as well as BS...
[Nexus 4 Android Development] kamilmirza:
its really good to see such great development going on such old device as N4

keep up the good work [MENTION=5091819]spezi77[/MENTION] :good:
[Nexus 4 Android Development] HubrisRev5:
I really appreciate the work you put into this kernel! One of the (very) few that still implements OTG and every other feature you could want.

I wanted to ask, since this is based on Hellscore, if the Knock Lock feature can be enabled?

see this thread http://xdaforums.com/nexus-4/orig-development/app-hellscode-knockcode-mod-hellscore-t3135899
[Nexus 4 Android Development] spezi77:
Yes, the Knock Lock feature is also included into this kernel and you can enable it by yourself. Turn on doubletap2wake in your favorite Kernel manager, and also enable the mod with

echo 1 > "/sys/devices/virtual/input/lge_touch/hells_code_enabled"

I suggest to add a knob for "Knock Lock" into KA app. What do you think?
[Nexus 4 Android Development] spezi77:
That build will only work in BS rom. I don't like to add s2w into my stable releases without confirmation that it works. If you find a little time, it would be great if you install BS and give it a shot.

Secondly, in order to add s2w I would have to remove KnockCode / "Knock Lock" feature. And I think that removing this feature isn't a good idea.
[Nexus 4 Android Development] Cristiano Lira:
I did a test with r08-ubertc5.3 with lazyplug. I tried to drain the battery in a row but I fell asleep and the phone entered into sod that sucked the battery till I wake up and restarted the phone, so the sot should yet be greater but the result I got is already amazing. Only got this once in the past, with a very capped setting. See:
[Nexus 4 Android Development] kol1124:
@up

But which settings? Did you even use your phone? ?

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Android Development] sidnoit22:
Tinder ;)
[Nexus 4 Android Development] dragos281993:
That's VERY VERY light usage, don't worry. If you use more than a bit of Tinder and a tiny bit of Watsapp, you won't get anything like that.
[Nexus 4 Android Development] kol1124:
Hah, I think so ?

Never saw that stats on my phone.

Anyway, I'm still looking for best profile for CPU and stable hotelu for battery ? ?

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Android Development] dragos281993:
You can always reduce the max frequency for both CPU and GPU. Set the CPU's max freq to 1.2 GHz, 200 MHz for the GPU, choose "conservative" as governor, or "hellasctive", choose "alucard" as hotplug, reduce the screen brightness, turn off the GPS if you're not using it, make sure there aren't any apps that always sync in the background, like Facebook and make the vibration a bit softer.
[Nexus 4 Android Development] Cristiano Lira:
Best settings I found for battery without loosing smoothness is pegasusq with frequency_for_responsiveness set to 1026000, CPU min frequency of 384Mhz, undervolt of -80mv, lazyplug hotplug (just disable it when you will let the screen off to prevent the sod) and with input/touch boost off, ondemand GPU governor with 200Mhz of maximum frequency, noop IO scheduler, vibration at 45% and, finally, use Dirty Unicorns.
[Nexus 4 Android Development] kol1124:
Thanks, I'll try these settings. Will report my stats later. ☑️

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Android Development] TheArt.:
Yes, It should be included into KA app!

BTW I didn't understand how to activate KnockLock permanently, Do I have to write that command in terminal emulator and that's it? At the next reboot it will be on? And how to configure KnockLock?

Thank you
[Nexus 4 Android Development] dragos281993:
You need Xposed to make it work. Here's all the information you need to make it work:

http://xdaforums.com/nexus-4/orig-development/app-hellscode-knockcode-mod-hellscore-t3135899
[Nexus 4 Android Development] Cristiano Lira:
[MENTION=5091819]spezi77[/MENTION], I managed to take logs after the phone entered in sod and woke up by itself (no reboot) and I think that these have more info:

See:

last_kmsg: http://pastebin.com/YsM3RqX4

dmesg: http://pastebin.com/7rXa8nXc
[Nexus 4 Android Development] g33k0 b3lk0w:
Wasn't kernels fault for phone not deep sleeping, resolved it and flashed hellspawn again fot that awesome smooth performance :D keep up the good work
[Nexus 4 Android Development] dragos281993:
Could you share it with the class, if you don't mind ? Any info is welcome around here. What caused your wakelocks and how did you manage to fix them ? Don't spare the details.
[Nexus 4 Android Development] g33k0 b3lk0w:
Of course. I had Android System wakelock on latest PureNexus CMTE version and I just reflashed it with formating only system and caches. Then just flashed adreno drivers, supersu and Hellspawn and also cleared cache of Kernel auditor and re-set everything in it. It works perfectly now works with -125UV and all wakelocks are gone. Performance is really amazing. Just changed the UV and minimal frequency when screen is off to 300~Mhz.
[Nexus 4 Android Development] dragos281993:
If you flashed the new adreno drivers, they'll cause you problems, sooner or later. It gave me a complete freeze right in the middle of a game then it didn't let me turn on the screen while I was receiving a call. Very annoying but they're beta drivers after all, so bugs are VERY expected.
[Nexus 4 Android Development] g33k0 b3lk0w:
Don't play any games but really should've tried without them, will do if any problems occur, thx for feedback
[Nexus 4 Android Development] dragos281993:
Just found out that the new adreno drivers are for MOB30D, so, considering that Pure Nexus hasn't been updated yet and the build number is older and the drivers are meant for the newer one, it's a matter if time till you run into problems. That's why I got freezes.
[Nexus 4 Android Development] matteus198701:
What's the best settings to great battery life?

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Android Development] spezi77:
Yes, dirty flashing will work.

Thanks for your feedback about UKM. I personally use KA as it supports almost every kernel feature, except for extended touch support. I have only seen that in HKM until now.
[Nexus 4 Android Development] spezi77:
Anyone having issues with copying files via MTP? I am in doubt whether my USB cable/ports are worn out or whether the kernel is to be blamed?
[Nexus 4 Android Development] str3tch72:
Nope, I copy this kernel to my phone and no issues. Also other files copied without problem.

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Android Development] tom0769:
Using this kernel with PN, KA as manager, really promising so far.

There is the opportunity to prevent msm_hsic_host wakelock in misc setting (Verschiedene Einstellungen in german).

In general this is the most markable wakelock for our device.

The toggle is on by default.

Does this mean wakelocks are blocked or has the toggle to be off to prevent wakelocks.

This could be an effective way to save battery if it was working.

Of course the connectivity would suffer from it, like less sync when screen is off.
[Nexus 4 Android Development] snacs:
Dirty flash didn't work. I had to install original boot.img after =/ but it's ok now.
[Nexus 4 Android Development] cell2011:
What is a good combo to you for good battery life? Im on latest CM Hells and BS and 1512/384 ondemand and cfq
[Nexus 4 Android Development] spezi77:
r04 up.

This time dirty flash should work.
[Nexus 4 Android Development] spezi77:
Edit: Sorry, I have mixed this up.. here comes the corrected description.

Toggle on will allow the service to acquire a wakelock -> So, this will NOT prevent wakelocks.

Toggle off will prevent the service from acquiring a wakelock. -> Use this one to actually prevent wakelocks.

The description shown next to the toggle in KA is really confusing in this point (mistake in translation).
[Nexus 4 Android Development] cell2011:
Whats a good governor/io combo on BS? Im at 384/1512
[Nexus 4 Android Development] spezi77:
The hellspawn defaults are my recommendation: hellsactive/bfq. CPU frequency range: 94/1512. CPU boost: wake up and input boost enabled. Boost intervall: 1000ms.
[Nexus 4 Android Development] ivanich:
[MENTION=5091819]spezi77[/MENTION] Is there any plans to update your kernel to the latest vanilla patches, e.g. 3.4.111?
[Nexus 4 Android Development] spezi77:
[MENTION=4329165]ivanich[/MENTION] nope. Could you please explain why do you suggest this, e.g. what are the potential benefits?

Thanks.

Sent from my beanstalked N4.
[Nexus 4 Android Development] mesaj:
Could you please add multirom kernel kexec - hardboot patch?
[Nexus 4 Android Development] spezi77:
Kexec-hardboot should be therein. Have you tested it? Are u sure that multiboot doesn't work?

Sent from my beanstalked N4.
[Nexus 4 Android Development] jcgalon:
this kernel works for stock rom? if yes, i'll get better performance and battery life?
[Nexus 4 Android Development] spezi77:
It should also work with stock Android. Just make a backup of your current rom and then give it a shot.

Sent from my beanstalked N4.