yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] venky716:
Had a similar profile running on AK, wanted to try out Render mainly for per core control and custom charging, brilliant implementations.

So basically it's running on quad core mode. 1457mhz seems to be way smoother than 1190mhz but obviously eats more battery. So I wanted two cores running on each, a mix of both worlds. Tried different gov on different cores but didn't work as well had a bit of lag and I'm in love with Smartmax so..

Anything not on the screenshots are stock settings.

Was mostly out all day with data, location and sync on so maybe a bit less SOT will probably have better stats the next cycle. Nevertheless very good for first charge on a new kernel.

2nd charge cycle, now back to normal stats. [emoji16]

Bacon
[ONE Original Android Development] :
Just because im curious:

Isn't there the princip:Work fast, go fast into sleep again? (no OC of course) I saw that a couple of times for Intel Notebooks or descriptions or Ondemand. But maybe im totally wrong with that and its more like a car which wont save fuel when you drive faster. Just would like to hear your opinion
[ONE Original Android Development] RenderBroken:
I would rather discuss them in this thread to keep things rolling and ppl participating. This thread is pretty open and I don't mind alittle OT when there is a lull in development. I want us all to be a group of friendly acquaintances. If it gets to the point where it clutters then for sure, we can open another thread.

Thanks for helping out!

All Profiles will be linked in OP#2 just for future reference when someone asks. BUT when someone asks without searching we will kindly ignore ;)
[ONE Original Android Development] RenderBroken:
Great info and even better SoT! Thanks for posting your screens! Only issue is the way the pictures were added to the post. To help prevent clutter and I would love for ppl to attach them to their post instead of posting the pics in post. that way it takes up less space. Also it makes it look much cleaner! Still thanks for everything. Cant wait to try it out!
[ONE Original Android Development] abhi08638:
This was the profile I originally made for AK kernel but it works well on here too. 4 cores always on. This is a multitasking profile

I found that there is no reason to be using 146400 except for two reasons. 1190000 can be just as efficient while being less laggy. The only downside to using 1190000 all the time is that heat output is increased slightly. Now for the two reasons to use 146400. (You have to use my custom intelliactive governor profile)

1) I use it as a CPU temperature control mechanism. It helps keep the CPU temp down while not being used too much. The CPU temp should peak at around 45°C

2) Again this is to control the temp, but this time on a charger when the screen is off. You don't want any extra heat when charging the battery so when the screen is off, the CPU will fluctuate between 146 and 300.

Notes

-min freq is 146

-max freq is 1190

-msm limiter is on

-CPU boost is off

-intelliactive is the governor

-4 cores always on with msm-mpdecision

-arch power on

-RQ Affinity is DISabled

-GPU min is 389

-GPU max is 578

-simple governor tunables is on at 5 and 5000

-no UV included (test it yourself)

abhi08638-Render-R3

https://www.dropbox.com/s/u9yllepbemj8out/abhi08638-Render-R3.tgz?dl=0

abhi08638-Render-R3-Screenshots

https://www.dropbox.com/s/oggqf233z2ihq6j/abhi08638-Render-R3-Screenshots.zip?dl=0

Currently at 5h15m at 31% over a period of 16 hours
[ONE Original Android Development] _ASSASSIN_:
Just going to say it's far more efficient just to disable hotplugging to keep all 4 cores on than to use hotplugging to do so
[ONE Original Android Development] abhi08638:
The problem with that is that if you're charging with the screen off, you get unnecessary heat from the other 3 cores
[ONE Original Android Development] RenderBroken:
Well I had done alot of research regarding how the N6 deals with no hotplugging. So the reason it works for the N6 is because of the way it handles with workload. So currently when a core is online and needs to transfer workload to another core it has to make sure the freq is equal or greater than that of the originating core before handing it over. This is done ever 20ms. There are alot of other things that go on during this notifier routine as well. Google pretty much removed this behavior so now from the start the workload is spread out and it acts like a try quad core and uses c states to handle sleep. Also with hotplugging disabled, workload is taken care of much faster allowing the freq to drop back down faster. Right now I don't believe this type of setup is really going to work properly with a 3.4 version kernel.

Still I believe you have been messing with it on the OPO. How has it been for you? How is batterylife? ETC.
[ONE Original Android Development] _ASSASSIN_:
Personally I don't experience that. I am using stock charging values with no fast charge. Last night I used 500 for AC and it was as cold as it is when idling.

---------- Post added at 01:27 AM ---------- Previous post was at 01:24 AM ----------

Ah, good to know! Glad I got an explanation :)

In terms of my usage, Idle times are god like and it's not a massive battery drain when using it. I am using R3 which now has the tweaked CPU boost and I have been using that in tandem with impulse and it works fantastically for me.

However in terms of performance, it still needs something like CPU boost to have a buttery smooth feeling, so I have tweaked as stated previously so I can scroll through apps and not lag.

I'll post my setup here soon :D.
[ONE Original Android Development] abhi08638:
Franco said that he already disabled that in his kernels. Was he talking about disabling RQ Affinity?

Also disabling hotplugging is working pretty well if you have the right settings
[ONE Original Android Development] RenderBroken:
So from Franco's G+

"the device is now running full quad-core mode all the time which helps tremendously because the Kernel task scheduler can distribute the workload through all these cores so you'll get the perception that the device is not hanging anymore.

They also disabled the built-in thread migration boost routines - if you don't know what this is about it's a driver made by Qualcomm that receives a notifier from the task scheduler when one thread migrated from one cpu core to another, and to minimize perceived lag it boosted the destination core to the same, or greated, frequency than the origin core:

1 - thread moves from cpu0 to cpu2

2 - driver is notified

3 - reads the current cpu0 frequency

4 - if cpu2 current frequency is less than cpu0's read frequency it boosts cpu2 to that freq, or, if the origin freq is lower than the threshold (which is 1.7GHz by default AFAIK) it boosts to that threshold value.

5 - the boosted frequency on cpu2 stays there for at least 20ms

These migrations can occur dozens of times per-second. One of the things that I did on FK was disabling all this to conserve battery (and we don't really need all that boosting with this chip).

I'm sure Google did the math and a lot of power measurements and found out that the gains outgain the losses, so they disabled this, and I applaud them.

So these two changes balance themselves out, and I can imagine that 100% stock users will be pleasantly surprised by the improved battery life."

This is not the whole post but whats relevant.

I think it is possible but it will not be running as well as it relly con without alot more work. Not sure about what Franco has done. Do you think you can find it and link me? commits or post?
[ONE Original Android Development] _ASSASSIN_:
My setup

This is my personal setup, works great on Exodus nightlies.

CPU:

-Min: 96 mhz (all)

-Max: 2457 mhz (all)

-governor: impulse (all)

MSM limiter

-Disabled

CPU boost

-all stock BUT

-CPU0 input boost frequency: 652 mhz

-CPU1-3 input boost frequency: 576 mhz

Hotplugging

-Disabled to enable all 4 cores (to do this I recommend disabling MSM hotplug, enabling intelliplug with performance mode enabled, and then disable intelliplug)

Thermal

-stock

I/O

512 kb read ahead with sioplus

GPU

min: 200 mhz

max: 657 mhz

governor: simple_ondemand

That's all the important stuff.

This is just idling with this setup!

https://i.imgur.com/KSglsXL.png

my usage when idling

https://imgur.com/q8Z0thT

I also have the profile for synapse downloadable here: https://drive.google.com/file/d/0B4jMoQTFXGOaazBVNjduNDRSb2c/view?usp=sharing
[ONE Original Android Development] gianton:
Idle overnight with R3 on Euphoria is awesome, lost 0% in 7h! Thanks for the fix [MENTION=5438598]RenderBroken[/MENTION]
[ONE Original Android Development] RenderBroken:
Thanks! Looks interesting! Just to remind everyone, I am placing these in OP#3. I believe I said OP#2 earlier but I was wrong. Lets keep this going. If you don't have a profiles that is fairly different than the ones reported so far, I may not link to it. Thanks again everyone!
[ONE Original Android Development] RenderBroken:
wow that is awesome! Thanks for posting. Glad that it worked out! R4 is looking to be a fun build. Bringing in zzmoove. I would love to add that to the playlist. lol But, now that I got scheduler working right with the new CPU Boost Changes, I am bringing in some pretty cool changes there should further enhance this.
[ONE Original Android Development] aamitabh28:
Getting 7 h SOT in a day.. Will post my settings later today!

This is such a fun thread..The development of the kernel and the dev are both really awesome.. Thanks man!!
[ONE Original Android Development] RenderBroken:
It is hard work but. . .I try ;)

Thats the goal here, I enjoy development. I discuss with devs all the time on hangouts and pm. Being able to create something out of lines of code is interesting to me. Igniting that passion in others is exciting too.
[ONE Original Android Development] ahaq:
Hell yah! Waiting for the settings
[ONE Original Android Development] RenderBroken:
Well too much of the new sched stuff had other 3.10 dependacies. So I dont see it happening now. But I have brought it some sched changes nonetheless, just not what I really wanted. Still I will test these new changes out and see if they are stable enough for release. Lastly zzmoove caused reboot upon changing to it. I may need to do more to make it stable for my own kernel. Now, time for bed, lol 230a here.
[ONE Original Android Development] aftmkt:
Take your time. :D

BTW, when you wake up, we might have OxygenOS released already.

Are you planning to support it, when the source drops? :)
[ONE Original Android Development] usmani:
OxygenOs is here :D
[ONE Original Android Development] DerRomtester:
I had problems with powersuspend and zzmove but when i have removed powersuspend it wasnt rebooting anymore. Check kmsg for more info.
[ONE Original Android Development] marvi0:
really strange, I was able to flash this kernel on the latest slimlp, and it worked great. I ran into some issues and now when I try and flash even on a clean install, am getting bootloops, any advice please?
[ONE Original Android Development] RenderBroken:
I would like to.

thanks bro, I didn't see anything in kmsg but it's something I can test.

Really weird, is it the same exact rom build? Like date and all?
[ONE Original Android Development] marvi0:
Yes exact same build, very odd. Have been flashing via recovery for a while so at loss as to how this could be happening. Could it be a custom recovery issue?
[ONE Original Android Development] RenderBroken:
Man , I am not sure at this point lol
[ONE Original Android Development] ak:
[MENTION=1546609]gianton[/MENTION]

you are a great supporter, thanks a lot for your hard work.
[ONE Original Android Development] Formhault:
It's nice to see you chiming in on other development threads, other than your own. :good:

Recognized Contributor status only? Lol. Something's not right.
[ONE Original Android Development] ak:
it's a long story! :)
[ONE Original Android Development] RenderBroken:
I know, [MENTION=3685904]ak[/MENTION] is a beast!

I agree as well, [MENTION=1546609]gianton[/MENTION] is an amazing supporter. I will more were like him. Still I think the climate is changing here on XDA. Instead of arrogant devs, we have those that want to learn and teach.
[ONE Original Android Development] ak:
since many have moved on N6, Opo threads, in general, have Reached the right peace for all ... we can enjoy Android without criticism or other problems.

thanks A Lot @RenderBroken
[ONE Original Android Development] Formhault:
You mean there were bad devs on the OPO that have moved to the N6? If that is so, good for us heh? :D

Hope it stays like that and you guys don't wake up one day with the fixed idea of "I'm gonna get myself a Exynos device, YEAH!". :silly:
[ONE Original Android Development] Andromendous:
Hey render, did you do work on the moto g about a year ago? You and your kernel seem familiar.
[ONE Original Android Development] RenderBroken:
Yes, that was I. I have come such a long way since those days! lol.
[ONE Original Android Development] Andromendous:
Haha! I thought that was you! You were doin great work then, as you are now! good to see you around again!
[ONE Original Android Development] _ASSASSIN_:
ay, exynos ain't half bad with the galaxy S6...
[ONE Original Android Development] Formhault:
As far as I know, Exynos isn't dev friendly. At least Exynos 4210 and such weren't...

Anyway, point was for devs to not let go of their OPO's :silly:
[ONE Original Android Development] gianton:
Thanks a lot for your kind words really feel honoured to be of any help to devs like you. Keep up your great work!
[ONE Original Android Development] Thunderbolt:
Like Formhault said, i Flash aicp Rom with this kernel and i can say, that is better combo than euphoria with render.
[ONE Original Android Development] MBurns2:
[MENTION=5438598]RenderBroken[/MENTION]

i'm using R3 on slimsaber, in the past i had problems. Now all is working good !

I really appreciate your kernel, thanks for your hard work my friend :good:
[ONE Original Android Development] molonad:
Great i noticed that this kernel is getting better and better nice ! great work ! iam now waiting for my phone to get repaired and i will replace ak with this kernel :) nice !

and please dev I had problems with r2 with microphone (known bug here ) and that hotplug have some bad behaviour(all 4 cores online, when they shoudnt) , i posted you guide when that glitch showed :-O do you remember ? did you look into it ? thanx
[ONE Original Android Development] RenderBroken:
Hey! Thanks!

I don't remember the guide or log. Sorry. But the Mic issues is fixed and as for the hotplug it should be good to go. I adjusted the "fast_lane_load" to 100. If you are still getting all four cores hotplugged when you don't want them to, then just adjust the Fast Lane Load a little higher by steps of 5 till you get the results you wanted. Let me know how it goes! Thanks again!
[ONE Original Android Development] gianton:
Here are my battery stats on 3rd full charge cycle with Euphoria 5.0.2 03/29 and render kernel v3. Smartmax gov @ 146/2726MHz (see screenshots) rest default. This is a test with Lux Auto Brightness app at night mode, rest of my setup is PA Pico GApps with 70 user apps most of them Greenified. This is the best combo I've tested on this device so far!
[ONE Original Android Development] MBurns2:
[MENTION=1546609]gianton[/MENTION]

mate do you think that night mode in lux can increase battery life?

for battery life which hotplug do you prefer? both msm and mp are good and they give me the same battery result
[ONE Original Android Development] schaggo:
No, Lux Night Mode has no impact on battery life. In night mode, Lux simply puts a half-transparent gray overlay over the UI to make it look "dim". The actual backlight is still the same brightness as without the night mode.

While Lux itself may or may not conserve some battery over the course of a day, I dont know and cant judge, but the night mode surely doesnt impact the battery, no. Night mode is only meant to be easier on the eyes at nights or in very dark environments, thats all.

Remark: the above holds true for LCDs like the Oneplus One has one, AMOLED displays do in fact use less energy when displaying "darker" graphics the way AMOLED works. Not LCD though.
[ONE Original Android Development] Andromendous:
I have a question. If i want to use intelliplug, do i need to disable mpdecision and msmhotplug?

Cus their both enabled by default
[ONE Original Android Development] DerRomtester:
Yep disable them. Only one hotplug should be enabled.
[ONE Original Android Development] RenderBroken:
Just. . .wow. over 10 hours SoT is very very impressive! AND with WiFi on. . . Just unreal. Thanks for sharing. I will play with this to see if I want to make it the default loadout. Thanks for your info and thanks for your pictures!
[ONE Original Android Development] Andromendous:
What about "cpu boost driver" it says in the description that its a replacement for mpdecision. Is something wrong with my setup? Because their all enabled by default except intelliplug
[ONE Original Android Development] abhi08638:
CPU boost driver is not a hotplug so it can remain checked.

However only 1 option on the hotplugging section should be checked.

As for your issue, try clearing synapse data, disable apply on reboot and then reboot. That way you will get the stock settings. Also make sure you are using the UKM version from Renderbroken's site in the OP
[ONE Original Android Development] Andromendous:
Ok thanks for the info. I am using the one he specifically posted in a reply to me. I will try your suggestion

---------- Post added at 08:27 PM ---------- Previous post was at 07:41 PM ----------

Ok i tried what you said and their both still enabled by default. Also i noticed that the first core is set to interactive and the second and third are on performance then the fourth on interactive. Is it supposed to be like that?
[ONE Original Android Development] abhi08638:
Not at all, try reflashing UKM and make sure you disable any other kernel tweaking apps
[ONE Original Android Development] RenderBroken:
OK The problem I am hearing is you are now on Android 5.1. Init.d support no longer works right on 5.1. Something with SELinux and Rom changes. If you want my script to set everything accordingly you will ned to place it in userinit.d. Its somewhere in /data. I am working on a new way to apply my values. So no, ALL governors should really be the same or at least not set to performance.
[ONE Original Android Development] Andromendous:
Ok thanksnagain, that sounds to me like the issue. You are correct i am on 5.1 i will search for yhe script in a bit.
[ONE Original Android Development] Andromendous:
Im sorry, but i cannot find your script anywhere. Btw, i am using geeky's cm12 rom which i guess is built with your kernel. So i must be missing something

Edit: actually, i found your script, its already in the init'd folder
[ONE Original Android Development] RenderBroken:
I would just set it manually for now. R4 is incoming and it will have a new script setup so it should set properly on boot. There really isn't much that it sets but it is needed.
[ONE Original Android Development] clockworkstop:
You really spent ten hours on your phone in one day? I'm not sure if I should be impressed or sad.
[ONE Original Android Development] gianton:
This was a test as already mentioned, usually I get 6-8 SOT with 1 to 2 days total time.

In my tests in various devices including Amoled and LCD screens, I get higher battery life but not that much with Lux night mode (maybe 5-10%). I find MSM hotplug the perfect hotplug for both smoothness and battery life. Bricked hotplug is targeted more to battery life with a sacrifice of smoothness. For example with MSM hotplug and only one core min with screen on/off I get a smoother UI than bricked hotplug with two cores min.
[ONE Original Android Development] smoki3:
Omg.... Its incredible smooth. If I get similar battery life as you then That's my favourite setting's
[ONE Original Android Development] clockworkstop:
That's still quite a lot of time spent looking at a screen. Oh well, who am I to judge.
[ONE Original Android Development] ahaq:
dude, this is XDA. developers test out certain things and SOT is one of a feature that users look for. He was just testing.

[MENTION=1546609]gianton[/MENTION] im going back from 5.1 Europhia to 5.02 and gonna apply your setting!

---------- Post added at 06:47 PM ---------- Previous post was at 06:36 PM ----------

[MENTION=1546609]gianton[/MENTION] for 5.0 which Gapps?
[ONE Original Android Development] gianton:
PA Pico from here,

http://xdaforums.com/showthread.php?p=59925693
[ONE Original Android Development] ahaq:
thanks a ton! and thanks a ton for always providing settings to use!
[ONE Original Android Development] eddyville:
sorry for bothering, ...i tried to reboot my phone into bootloader without haviung installed sdk tools...now the phone rebooted and is only showing android logo, i cannot even access recovery mode..........pls i reallyneed help. my device is a polaris-ibt phone and allwinner tab
[ONE Original Android Development] RenderBroken:
If your phone is not a one plus one then you are in the wrong thread. Sorry I cant help more than that
[ONE Original Android Development] RenderBroken:
SO I have been playing with [MENTION=1546609]gianton[/MENTION] 's settings and have to say I am quite impressed. I think the biggest thing here is SmartMAX coupled with my version of MSM_Hotplug. Mine has been modified to allow for sleep and settings the MAX allowable number of cores allowed to be online at a time. The special thing about SmartMAX is that it ramps up really quickly but as soon as the workload is done, it also ramps back down VERY quickly. Whats good about this is:

The way hotplugging works in general is when load is at a certain point, the hotplug driver decides if it should hotplug a core or not. The different hotplugs out there ALL essentially follow this rule. Whats different about them is HOW they follow this rule. I feel that MSM_Hotplug is the smartest hotplug out there with minimal amount of code (Looking at you Bricked (MSM_MPDecision) ). You may see when using CPU Spy or something similar the the Online Core jumps around sometimes. Well whats happening is workload and the systems kinda dictates what core to place said load, well the hotplug driver sees this coming and meets the load with the right amount of force. Remember that the hotplug's job is to finish all the work, meaning that it wants to get to idle asap. Where as another hotplug driver may online the other core, bring it to speed (To match the core that is currently carrying the load) to then hand it over then it ramps down to go offline. See the difference?

So the significance of this "smarter" hotplug driver coupled with SmartMAX works as follows:

SmartMAX Ramps up so fast that when it handles load it does it so quickly that the load spike is taken care of with ONLY 2 cores instead of the usually 3 or 4. MSM_Hotplug is smart enough to gauge that the load was handled fast enough that it doesn't hotplug the usually requisite 3rd of 4th core. IT just uses the 2. So now we are no longer wasting precious battery hotplugging multiple cores all the time. I believe this is why we are able to achieve amazing SoT even though we have two cores fairly maxed out. This is why your UX (User Experience) remains so smooth using this driver.

Another thing that verifies what I am trying to explain is, I have the Screen Off Freq set to 1.2GHz and have 0 skipping or audio issues. If I used another governor I would have artifacts. Test this out to see what I mean.

I believe going forward I will use SmartMAX as my default driver. I will be using Gianton's setup. I am still at 67% and its freaking 2pm. I Always have WiFi and BT on all the time while listening to music or Audiobooks (Day Watch Series right now ;) ) I would normally have about 45% battery left.
[ONE Original Android Development] gianton:
Thanks for such a thorough explanation, not seen this from other devs since I first signed in XDA 6 years ago! Appreciate all the work you put in this kernel!