yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] spezi77:
Don't worry, in r07 this is nothing you need to be concerned about. However, you can use any version. Using version 4.9 was a temporary idea to make a few "backwards tests". I will no longer support the older version 4.9, but use version 5.3. If you are interested, TC stands for toolchain, which is a collection of cross-compiler tools for developers and/or rom builders.
[Nexus 4 Android Development] spezi77:
[MENTION=6262409]Mrcactuseater[/MENTION] you would like to test with UBERTC 7.0? On which rom are you, AOSP, BS, CM?
[Nexus 4 Android Development] dragos281993:
I would love to test that as well. But what is tc 7.0 supposed to bring over the older version? Is there gonna be any improvement? At least in theory?
[Nexus 4 Android Development] Mrcactuseater:
No problem! I'm on AOSP ?

Tapatalk'd from my Twisted, Despaired Nexus 5x

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

In comparison to other tc version of UBER, i notice performance is good like 6.0 but the battery savings are similar to 4.9, at least on my 5x.

Tapatalk'd from my Twisted, Despaired Nexus 5x
[Nexus 4 Android Development] dragos281993:
Spezzi, bro, we're waiting for a test version built with tc 7.0. I'm very excited to test me stuff. Don't worry if it's not gonna work properly or at all from the first try. The Etsy testing is after all.
[Nexus 4 Android Development] spezi77:
Hey guys,

I just did a benchmark with AnTuTu, and the kernel built with UBERTC 7.0 performs faster! Hold on.. for 20mins until builds are ready and up.. ;)
[Nexus 4 Android Development] dragos281993:
No problemo, ese.

Lol
[Nexus 4 Android Development] Mrcactuseater:
Knew you'd like it, now hit me with the good stuff!

Tapatalk'd from my Twisted, Despaired Nexus 5x
[Nexus 4 Android Development] spezi77:
Here you go.

hellspawn-N4-mm-6.0-r08-AOSP-UBERTC-7.0.zip

hellspawn-N4-mm-6.0-r08-BS-UBERTC-7.0.zip

hellspawn-N4-mm-6.0-r08-CM-UBERTC-7.0.zip
[Nexus 4 Android Development] dragos281993:
Damn... I see that you replaced Franco's gamma control for the AOSP version. No more tweaking the colors now.
[Nexus 4 Android Development] spezi77:
Yes and no. It was by mistake. I have already corrected this, rebuilt and uploaded a new aosp version. See my previous post. ;)
[Nexus 4 Android Development] dragos281993:
Thanks! I guess I was too quick.

---------- Post added at 08:18 PM ---------- Previous post was at 08:05 PM ----------

Ok. Done flashing it. Everything looks absolutely stable. I'll report back in case of a problem, which probably will not appear at all.

Thanks again, man!
[Nexus 4 Android Development] spezi77:
Hey guys,

damn, today it feels like all Christmases come at once! I added for testing purposes "lazyplug".. (Big thanks to arter97) and I did another series of test builds for ya, brothers. :D

I did a benchmark, as usual, and if we just consider the AnTuTu score, it seems to be fast as hell.. but I guess that this can be easily explained if we study the concepts behind..

What the hack is lazyplug?

Other hotplugging methods including mpdecision and intelli_plug focuses

on how should we turn off CPU cores. They hotplugs the individual CPU

cores based on the current load divided by thread capacity.

Lazyplug takes a whole new approach on how we should do hotplugging

based on the foundation of the other side of the coin;

"Linux's hotplugging is very inefficient."

Current hotplugging code on Linux is a total waste of CPU cycles and

delays, so rather than hotplugging and hurt performance & battery life,

just leaving the CPU cores on might be a better choice. This kind of

approach is spreading out more and more.

Samsung has been using this method for a very long time with big.LITTLE

devices and recent Nexus 6 firmware also does the similar thing.

Lazyplug just leaves them on, most of the time. It also tries to solve

some problems with the "Always on" approach. On situations such as video

playback, turning on all CPU cores is not battery friendly. So Lazyplug

*does* actually turns off CPU cores, but only when idle state is long

enough(to reduce the number of CPU core switchings) and when the device

has its screen off(determination is done via earlysuspend or

powersuspend because framebuffer API causes troubles on hotplugging CPU

cores).

Basic methodology :

Lazyplug uses majority of the codes from intelli_plug by faux123 to

determine when to turn off CPU cores. If the system has been idle for

(DEF_SAMPLING_MS * DEF_IDLE_COUNT)ms, it turns off the CPU cores. And if

the next poll determines 1 core isnâ€™t enough, it fires up all CPU cores

(instead of selective CPU cores; which is the traditional intelli_plug's

method).

Lazyplug also takes touch-screen input events to fire up CPU cores to

minimize noticeable performance degradation.

There's also a "lazy mode" for *not* aggressively turning on CPU cores

on scenario such as video playback. For example, if you hook up

lazyplug_enter_lazy() to the video session open function, Lazyplug won't

aggressively turn on CPU cores and tries to handle it with 1 CPU core.

IMPORTANT:

Lazyplug does not appear in "hotplugs" section, although it is per default enabled in my testbuild. Therefore please don't touch any of the other the knobs!!! If you do, don't complain about issues, e.g. instabilities, battery drain, etc.

You got me? ;)

Then please move on to your lazyplug test build:

hellspawn-N4-mm-6.0-r08-lazyplug-AOSP-UBERTC-7.0-lazyplug.zip

hellspawn-N4-mm-6.0-r08-lazyplug-BS-UBERTC-7.0-lazyplug.zip

hellspawn-N4-mm-6.0-r08-lazyplug-CM-UBERTC-7.0-lazyplug.zip
[Nexus 4 Android Development] dragos281993:
Flashing right away. This boring day turned out to be great after all, with these test builds.
[Nexus 4 Android Development] sidnoit22:
What does "BS" reefers to. I use AOSP ROM and want to flash kernel, I know I should use AOSP version but what is BS?
[Nexus 4 Android Development] dragos281993:
"Bean Stalk". It's not Bull S#!t, don't worry.
[Nexus 4 Android Development] sidnoit22:
You are currently the best Dev for our Nexus 4 and you are the real MVP! :) Thanks for making my day.
[Nexus 4 Android Development] str3tch72:
UberTC 7.0 - best thing that meets Mako. Definetely. Thank You [MENTION=5091819]spezi77[/MENTION], You are the man!

Wysłane z mojego Nexus 4 przy użyciu Tapatalka
[Nexus 4 Android Development] ivanich:
First of all it contains security patches and ofcource bugfixes for different kernel subsystems(memory, fs, etc). As you may know most of the cyanogenmod kernels patched to actual vanilla status.

Отправлено с моего Nexus 4 через Tapatalk
[Nexus 4 Android Development] dragos281993:
I sense a new build might be on the way. lol
[Nexus 4 Android Development] t181:
Why is that? :D
[Nexus 4 Android Development] dragos281993:
Today we got a bunch of builds so now that you came back with an explanation about what 3.4.111 includes compared to older versions, and the fact that Spezzi approved your comment with a like, he might release a new "new build" with the newer stuff included.
[Nexus 4 Android Development] spezi77:
Maybe, on a boring weekend. First of all, I need your feedback and test results on the latest changes. Once that is stable, I'll continue with adding new stuff... ;)

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] dragos281993:
Right now, all I can say is that the battery drain a bit higher. This behaviour was present in Quanta v13 where all the cores were online most of the time. But I have to keep testing it further, in order to see how higher the drain actually is.

My suggestion would be that you only keep 2 hotplugs in the next build, "AutoSMP" and "Lazyplug". The others are not used by too many users anyway so having these 2 in the Hotplug section, would give the user the possibility to choose the one he wants.
[Nexus 4 Android Development] spezi77:
Sounds like a good plan. I'll try my best to write an extension in Kernel Adiutor for lazyplug support. Once we have this, there should be enough test results, and we can figure out what are the optimal adjustments.

Have fun with hellspawn..

Cheers [emoji16]

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] ivanich:
Tried r8 today and looks like it have issues with min freq for almost all governors, if I set min freq lower than 384 it stuck at 1134 at one core most of the time. Previously I had similar issues with another device and KA app, for some reason KA messing with two_phaze governors.
[Nexus 4 Android Development] spezi77:
Thanks for mentioning. Maybe then I shall raise the min frequency settings in the future.

Did this occur for you also before playing with KA?

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] ivanich:
Double checked it without KA and after reboot when screen on freq is

root@mako:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
1350000

When screen off it stuck at 1026000 as by default configured. So it's not KA fault as I thought before but issue with cpufreq in general.

Tested it with cm13 latest nightly
[Nexus 4 Android Development] bart.found:
[MENTION=5091819]spezi77[/MENTION] I'm still testing r07 and can confirm that this kernel has awesome deep sleep.

However I noticed that my phone has some difficulties to exit from deep sleep.. The screen takes about a second to wakeup and the phone lags a lot for about a minute, than, back to normal. Do you know what is causing this behaviour?
[Nexus 4 Android Development] dragos281993:
Increase the minimum frequency from 94 mhz to 189 MHz, then if you still get the same behaviour, increase it to 243. 384 MHz is the minimum frequency the CPU is set at with kernels that are not underclocked so this frequency will, more than sure, get rid of the problem.
[Nexus 4 Android Development] kanishkad:
Is there a benefit to setting the min frequency below 384? 384 & below frequencies all require the same voltage level, 850mv.

Hats off to the developer. Tried R08 & it looks awesome. It's always good to have options & choice. I'll report on the stability after using it for a while. Keep up the good work..
[Nexus 4 Android Development] dragos281993:
It isn't a benefit, not really. Only if you're using, for example, Viper4Android, if the minimum frequency is not above 384 MHz, you'll hear a lot of static noise.

For the other things you can do on your phone, there isn't a benefit. The performance is the same.
[Nexus 4 Android Development] mperezm77:
What are the conditions to be met for the kernel enters deep sleep mode?

I'm using fake Nexus Rom and tried with Hellspawn 07 and 08, but AK says that deep sleep frequency is never used.

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Android Development] bart.found:
power is the result of frequency&voltage this means that:

same frequency + lower voltage = less power

but also:

lower frequency + same voltage = less power

Trouble is that lowest frequency values easily reach the load value that cause a frequency ramp-up (usually to 1026MHz or 1512MHz), while 384MHz is able to handle some simple tasks without reaching that load and without ramping to 1026MHz or 1512MHz!!! And power needed is the same if not lower ;)

Install Better Battery Stats and check wakelocks to understand which app/process is keeping your device awake
[Nexus 4 Android Development] mperezm77:
PowerManagement.Service is the one which seems responsible of keeping my phone awake. See screenshot. Am I right?

View attachment 3723130

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Android Development] dragos281993:
Go to the "Partial wakelocks" section and the first app in the list is the problem. But pretty much everyone has this problem. It's present with every kernel, so it's more likely a ROM problem. It appeared about 2 months ago.
[Nexus 4 Android Development] mperezm77:
First application is the GoogleUpdateService...

That means than we can not do anything to fix it?

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Android Development] dragos281993:
All I know is that it's related to the damn Google services. For me "Inbox" (by Gmail) is the first in the list and the Google Play services have the highest count for awaking the device when it's in deepsleep. Tried everything, nothing fixed it. But for me the these wakelocks don't drain much battery. Try rebooting your phone.
[Nexus 4 Android Development] bart.found:
Wow!!! That wakelock is huge!!! Which ROM are you using? I don't have this on Krexus..

I remember I had this on Lollipop due to a buggy version of Google Play Services! I hope that your phone just needs a clean flash.. because last time Google took months to fix the issue... (I remember that you could stop the wakelock by ENABLING the "system update service" through the app "disable services", but after a reboot it was there again!!!!)
[Nexus 4 Android Development] TheArt.:
Your kernel seems going strong! But I have some problems with Kernel Adiutor because it messes up my voltage parameters every time, sometimes it doesn't save my vibration strength :confused:. I used it in the past and it didn't have these problems if I remember.

Now I installed the HellScore manager linked in the first page of the topic.
[Nexus 4 Android Development] spezi77:
Besides HKM you could also give this mod a try: http://xdaforums.com/showthread.php?t=3333549

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] Cristiano Lira:
I am testing the test build with lazy hotplug and I can say that the battery is worse with it. I can't imagine how the battery could be better with all the cores on all the time. I can't get more than 3 minutes per % sot with it like it's possible with mako hotplug. Another thing, badass governor Is unusable for me, it lags so hard that It's not even an option, and I am left with just conservative for having a decent battery life as the others governors keep kicking high frequencies in idle without any need.

Edit: after further testing I noticed that after activating mako hotplug in lazyplug testbuild (lol) I got a better battery life: ~4m20s per % sot.
[Nexus 4 Android Development] jer_ying_fd:
The problem with having 4 cores always online is that the phone will become very hot quickly, which increases battery usage quite a bit. Is it possible to make it so 2 of the CPUs are responsible for heavy tasks while the remaining 2 are only boosted a little to help, and all 4 at maximum when required?
[Nexus 4 Android Development] Cristiano Lira:
I think you are correct, the phone gets hot very quicky and another thing I noticed is that I can't charge my phone with all 4 cores on all the time, the drain is so high that nulls the charging. And I think that mako hotplug works as you said, and this is why I prefer it over the others hotplugs. Can you confirm that mako hotplug works as you described?
[Nexus 4 Android Development] jer_ying_fd:
I didn't mean turning off the remaining 2 CPUs, I only meant that the 3rd and 4th CPUs will use low frequencies until there are heavy loads. I'm curious to see if this can negate the heat problem enough. Performance-wise it should be a very tiny bit slower but not easily noticeable at all since it really is about the main 2 cores with high frequencies that matter for normal tasks such as opening settings app, dialler, chrome etc so I think it should help with the heat problem.
[Nexus 4 Android Development] Cristiano Lira:
Hmm. I would like to test this approach. But I think it's a matter of CPU governor. What you think, spezi77?
[Nexus 4 Android Development] TheArt.:
Same. KA shifts voltages of some frequencies every time I apply my profile. Tried many things to solve it, it does it anyway..
[Nexus 4 Android Development] bart.found:
UKM+Synapse work correctly
[Nexus 4 Android Development] mperezm77:
Much better now. After installing Disable Service and just enabling and disabling SysyemUpdateService, the wakelock has been almost eliminated and my phone enters deep sleep mode as it should.

Thanks for the hint!!

Isn't there any way to do it automatically after every reboot?

View attachment 3724427View attachment 3724428

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Android Development] spezi77:
*advertising:on*

BeanStalk ROM has a built-in Wakelock Blocker. Afaik it automatically applies your settings after every reboot.

*advertising: off*

:D

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] spezi77:
Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] bart.found:
Glad it helped you!

If only your rom was AOSP based and not CM based... but I'm too curious about beanstalk and probably I'll try it the same soon
[Nexus 4 Android Development] mesaj:
Oh, now I know why this kernel never worked for me, gonna try it now when my phone charges. :D
[Nexus 4 Android Development] Cristiano Lira:
Anything, spezi77?
[Nexus 4 Android Development] redj12:
Hey buddy, I did it ! 3h45 of happiness and pain :highfive:

I switched to Pure Nexus ROM because there was some issues with CM. I flashed also your kernel and will test it . Thank you.
[Nexus 4 Android Development] spezi77:
Nope, I am @ work these dayz. Furthermore, I don't know whether tweaking lazyplug to use 2 cores is an option which can be easily implemented and whether it is worth to do this.

For high performance mode we already have AutoSMP. Is there a big/significant difference for you between AutoSMP and Lazyplug?

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] bart.found:
Autosmp seems to be smoother on my end (in r07).. If I understood we can't change hotpplug in this release to avoid issues
[Nexus 4 Android Development] spezi77:
In case that you no longer want lazyplug, you can flash the "normal" r07. In that one you can change hotplugs without any side effect. ;)

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] jer_ying_fd:
Actually, for me lazyplug was faster and around the same smoothness, but it really heated up quite a lot and battery life suffered.
[Nexus 4 Android Development] bart.found:
Yes, I know, but I can live with r08.. I need some more testing to decide which one I prefer..

I checked my CPU usage with perfmon and noticed that 94, 189 and 243 can't handle, actually, any load!! And if your minimum frequency is set to one of this values, your governor will keep kicking high frequencies even while idling -> more heat and more battery drain!!! Setting minimum frequency to 384, CPU can handle some minor task or just idling without ramping to high frequencies! ;)
[Nexus 4 Android Development] Cristiano Lira:
I didn't mean I would like to test it aiming in performance but instead to see if this way we could get better battery than with the others hotplugs we have.
[Nexus 4 Android Development] bart.found:
[MENTION=5337411]Cristiano Lira[/MENTION] [MENTION=4493540]TheArt.[/MENTION] [MENTION=5091819]spezi77[/MENTION]

This is my first battery cycle with r08.. almost WiFi, browsing, youtube, video streaming, texting, some voice calls...

Not bad!

[IMG="battery screenshot"]https://lh3.googleusercontent.com/WMlj0HjXwUNO-NZ7aIzeTKg-9Mki7p-ZbxaWVAiTY7GglL1B06hSLx0VTgxhFdNNnUnRuhz-uS9DqmeaFyz0_CNvtqAn4qfjnXcM_Ocq8rF-N7Hwtct7ZE_hhPt4RO6ZkxjLT3av3BpBfSq28fqiCPoW3VgViKT0KhsJgIhP47HjL8hgE4LxSKw4GxnQGCSGODz9GqQqxBnMm4AVeAf6Wya9ebO8GdsBBi6FT4jZC8rIA2q3bpvS-NOZzjINNiFexnpoxwKG-tS_Sghkx0jekxoi2QCsMDCc9-NaCz4ndNQV7skmNkusHk5ezj5dGCEiqXPhLROQox3HmgDqqSv0S99FOuKv4_sseYNWTjyE2w3FjtrbnOgcmHg878sVU78-i3ulS7ec_DrUQY1UVgEBb94pahBL2aJLkZ8rGfjOAYnt6f47U-jfDbniJhyPGR8KnzQ4fkR1ujkB6VKpUVfqzsJkyWSsWV07HPLrlzBPnDOh4ZaEjWuOtmYYRyXe_ynkHZdgPUf98oADMeHCAdNlVL3Jdggb7EEggYmXGBnlGcm9a7tqkPiyFxzmOgjMBeYUAVab3A=w420-h699-no[/IMG]

[IMG="battery screenshot"]https://lh3.googleusercontent.com/BJnaJzLsmShxHhBtuaastWlOu1j0kqx7FPHNdsd4I1JTRfcR7VUIYoYdTIclIMnQ0wzH0hYAHP-dh2M-lwbldme-lkEU3tvvrThnt7B994iU9N6NsAa0jiWmmx3MBGeTK5jkxdaGCY0MMlqF6OzGXlpQ3Ty3hCr3Lw_tBP8Kcafl2IePbNBsbi9vdHOFTmuP4NI3SNcHohGgZX6g-LbFcehcn8QfHHjGTJ7_S5I5WTrzE4V-KGZBzTRDPxiJ6_DU-EyMueZsz5zBdDnWo8gu13JYC5_568nYoFEwPT7tMrd-fK0oXJ8s0CDNWUnrjjaBCcSDAI7jzQVCPJjQ-PF5-eMi2M038TioMTZN2Bv826W7QX0XDFoHw6ZaIbLf-nfD12gNw7FmnanjXoRsF7OHeh4BWFNfrd1Vr6Et71oX6AYS_Bm0GgZia-TZQo7w2PiEHEJjqU4Xbdh8d4HCQdMo9a52zDkPY0I_G3oDS_ug-Hap9y3fiVOs5LJKoRmTPIoIxD7P37q499hEkLWxBFLi0r7Rm6N3cuNo4hYqXIiDNdDoCqZLKZxuKaN9UMLXv510WeO7Cg=w420-h699-no[/IMG]
[Nexus 4 Android Development] jer_ying_fd:
I already did that, but I also seem to notice that on the lazyplug build CPUs 1,2,3 do not switch to the minimum frequency I set, with only 0 on 384 MHz. Can anyone confirm?
[Nexus 4 Android Development] bart.found:
I can't confirm, on my end works as expected! Maybe the app you are using to check frequencies, generates a load on the CPU and the governor boosts your cores.

I use PerfMon and all four cores sit on 384MHz while idling, they, obviously, boost if I touch the screen
[Nexus 4 Android Development] Cristiano Lira:
The screens isn't loading here.
[Nexus 4 Android Development] bart.found:
I attached them! ;)
[Nexus 4 Android Development] Cristiano Lira:
Less than 4 hours? No, thanks. I get 5h+ with mako hotplug and am good with it. I guess having all cores on all the time isn't better for battery life (of course, lol). But I don't know if making it work like jer_ying_fd said could be better - keeping cores 3 and 4 at low frequency unless there's heavy load on phone and then quickly boost these 2 cores when needed.
[Nexus 4 Android Development] bart.found:
You probably didn't notice that was almost two days uptime
[Nexus 4 Android Development] Cristiano Lira:
spezi77, could you build r08-lazyplug with ubertc5.3? Just to do some testing. Thanks in advance.

Almost forgot, aosp.
[Nexus 4 Android Development] spezi77:
Here you go. https://www.androidfilehost.com/?fid=24499762636005232
[Nexus 4 Android Development] Thrikiller18:
Using last r8 with fakenexus (only d2tw is enabled) everything is just perfect. Thanks spezi you're keeping alive our makos
[Nexus 4 Android Development] kanishkad:
Usually on other kernels, AutoSMP is battery friendly than Mako Hotplug. But here it seems the opposite. Is it because some parameters of AutoSMP has been changed or is it the result of the min frequency being below 384mhz & the governer boosting it to higher frequencies more often as mentioned above in the thread? The performance is awesome with AutoSMP, but it has a negative impact on battery life.
[Nexus 4 Android Development] xenyz:
Try 384 MHz min freq, elementalx governor, and autosmp hotplug. With elementalx, there is a two phase freq at 1350 MHz that is below the autosmp trigger (90%) which keeps cores from turning off and on frequently when idle.
[Nexus 4 Android Development] spezi77:
I think that min frequency below 384mhz is counterproductive to battery life. I raised min frequency via KA, and this time battery stats promise > 24h. Using 94mhz resulted in appr. 14h.

Thanks for sharing your observations and opinions! :)

Sent from my beanstalk'd & hellspawn'd N4.
[Nexus 4 Android Development] jacomail95:
Loving the latest r08 ubertc 7.0, thanks spezi77 :):thumbup:

Inviato dal mio Nexus 4 con Tapatalk 2