yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] joefso:
alright... what profile would you recommend for battery savings. usage: browsing, video watching, whatsapp, callling. That is about it
[ONE Original Android Development] andip71:
No, it is not available in OPO kernels.

Yes, indeed. I should either mark that very clearly in the documentation: Exynos platform only, not for Snapdragon phones (OnePlus and S5 European version).

Or I should update the documentation completely.

While the second would be the right thing to do, it would take me a few days work. So it is likely I do the first soon only.

Andi
[ONE Original Android Development] brisac:
Try zzmoove battery yank with 1497 max cpu and zzmoove native hotplug
[ONE Original Android Development] kurtextrem:
Hey Andi, have you seen my question about the HYPER governor? :)
[ONE Original Android Development] andip71:
Yes, I have. But I am not yet back, close to my pc.

As per governors: I can of course stick 40 more in, technically. But they must make sense.

So if you could find out what is so special about Hyper, which makes it worth being added, I would appreciate some more input or references.

Thanks

Andi
[ONE Original Android Development] joefso:
Do you still not recommend using system tweaks option in boefffla config?
[ONE Original Android Development] andip71:
Not for around 2 years anymore.

It was specifically put in for the Galaxy S3.

I think it is not required on the OPO. But well, some might still like it.

Andi
[ONE Original Android Development] molonad:
Hi i dont know if i can report bugs on cm12s , if not , iam sorry :-/ but i tried many governors and hotplugs and all other governors and hotplugs then zzmove dodnt work like it should , only once core is online and 3 others are not plugged anytime :-/
[ONE Original Android Development] Clark789:
Yes, that's the same like i observed first and described here: http://xdaforums.com/showpost.php?p=60358113&postcount=4251

But i think a restart can solve the problem - perhaps for a while. For the moment everything's fine for me. When three cores are offline, they will wake up, if they're needed...

Cheers

Clark
[ONE Original Android Development] molonad:
i restarted and even wiped cache and dalvik cache , doesnt work , but for me is only zzmove important which is working :)
[ONE Original Android Development] andip71:
What is your exact hotplug setting?

Andi
[ONE Original Android Development] andip71:
Tomorrow new kernels...

Hi all,

for heads up:

Tomorrow maintenance update for CM12s and CM12.1 kernels.

Bring all code and ramdisks up-to-date.

Cheers

Andi
[ONE Original Android Development] molonad:
sorry all other governors and hotplugs doesnt work like it should , optimized one core max , default one core max , only zzmove governor and zzmove hotplug works :) now trying fefault hotplug and interactive governor , only one core is on :)
[ONE Original Android Development] kurtextrem:
I can't tell you too much, but I think this graphic is quite nice:

It seems to safe battery quite nicely, but still gives smooth UI. I can't confirm that however as I don't have the SGS2 (where this graph is from).
[ONE Original Android Development] abhibnl:
Well somehow smartmax isn't working as it should. It keeps ramping up to higher freq even when i'm not touching the screen at all.

Sent from OnePlus One
[ONE Original Android Development] andip71:
And how should it work? [emoji3]
[ONE Original Android Development] bloof:
Why would it save now battery? There are plenty of other governors that use more lower frequencies than HYPER.

The most important is to reduce max cpu, something like 1.5 or 1.7 GHz is enough for most people. If you use also something like zzmove with "battery" in the title and with its own hotplugging it will use less cores and save even more, but it can become laggy at some point.

I prefer good governors with reduced cpu (interactive or zzmove moderate/performance), max cpu 1.7, gpu 389, zen i/o, keep i/o at 1024 (you can reduce for better performance if you don't use large apps).
[ONE Original Android Development] andip71:
Don't understand what exactly is working and what isn't for you. Sorry.

Just spot checked some combinations, at least what I tried quickly was working well.

Andi
[ONE Original Android Development] molonad:
hey sorry ,for example when i choose interactive governor and default hotplug , only one core is plugged weven in games , none of next theree cores are plugged ever :-/ , and this bug is on all cores and on all hotplug which is not made by zanezam :) like clark said

even if i tried zzmove hotplug and all other governors like intelliactive etc , only one core is on and next three cores are not plugged at anytime
[ONE Original Android Development] andip71:
Interactive with default hotplug is my daily driver. This works perfectly for me.

So... Which rom are you using then?

As you know, I only test against original cm and stock opo cms.

Andi
[ONE Original Android Development] molonad:
latest cm12s after wiped dalvik and cache :) , should i try something to get it fixed ?

---------- Post added at 09:25 PM ---------- Previous post was at 09:23 PM ----------

iam using system monitor to check how cores works , should i try some other app , if it is not connected with bugged monitoring app , what app do you use for it ? :)
[ONE Original Android Development] andip71:
I use Chainfire Perfmon for it.

Maybe tomorrow's cm12s Kernel update solves your issue...

Somehow it feels like mpdecision process is not running, so no cpu plugging.

Andi
[ONE Original Android Development] molonad:
THANX but even on zzmove native hotplug and interactive is bug still present for me :-/
[ONE Original Android Development] andip71:
Fully explainable.

Zzmoove native hotplugging only works when zzmoove is the active governor.

If you use this zzmoove native hotplugging with another governor, mpdecision is used again [emoji3]

Andi
[ONE Original Android Development] molonad:
i tried perfmon , so bug is not connected with app , and BTW think system monitor is better , you can change settings about refresh rate of cpu , so you see how cpu works in quicker intervals

---------- Post added at 09:38 PM ---------- Previous post was at 09:37 PM ----------

lol thanx :D
[ONE Original Android Development] andip71:
Then check if there is a process called mpdecision running at all.

For instance in a terminal window type:

su

ps | grep mpdecision

Andi
[ONE Original Android Development] molonad:
Tried right now In two apps I think it is ok, there is number 1, so it is on, and I notice that system is pretty fast not like with only one core, I think problem must be in monitoring..
[ONE Original Android Development] molonad:
and i must say i had problems with monitoring sometimes with your kernel , even in cm11s times :) cores were working and monitoring shows only one is working , restart every time fixed issue , but not now
[ONE Original Android Development] andip71:
Never had any monitoring issues.

But I rarely monitor, I just use it ?
[ONE Original Android Development] RohanKalra97:
Cm12s supported?
[ONE Original Android Development] molonad:
? Hey and now I tried again reset settings with your reset zip and when I started, all 4 cores were on and won't get unplug, so I change hotplug to optimized then back to default and bug is still present, only one core on and next three won't get plugged, weird, don't know how to check if it is only monitoring issue or not.
[ONE Original Android Development] thedao:
As the title says, yes :)
[ONE Original Android Development] molonad:
So I tried some speed test, and I know for sure, it is not monitoring issue, weird, but zzmove is working so iam satisfied
[ONE Original Android Development] andip71:
I am sure something blocks mpdecision at your side.
[ONE Original Android Development] molonad:
what should i do , dont say clean flash :D

can a log help you with resolving , should i send you it ? :) :(
[ONE Original Android Development] Saber:
HYPER is a super stable governor on the s2. That's a reason why it is used by default on dorimanx kernel. However, it won't be as battery efficient compared to other governors, this is because the governor aims to have smooth operation. Meaning that the governor will not ramp down too quickly and will stay at mid range frequencies to prevent lags and unsmoothness then slowly reduce to lowest possible frequency. When I created that graph, I noticed this :) There are better governors for other devices, HYPER is best on s2, Ondemand for others, PegasusQ for some and ElementalX for some. You get the point :)
[ONE Original Android Development] abhibnl:
I had an expeirnce with it on render kernel for the first time. As Smartmax is based on ondemand, it should ramp down to 300mhz in ideal state. But as i mentioned even when i'm not touching the screen at all, it hovere around 1190,1574freqs with 2 cores on. While it should be on 300mhz since i'm doing nothing with my phone.

Sent from OnePlus One
[ONE Original Android Development] Renosh:
That's actually how smartmax normally works. Render kernel is using specific settings to the governor more conservative. The profile was provided by [MENTION=1546609]gianton[/MENTION]. Search his posts in that thread and use those settings to get similar behavior
[ONE Original Android Development] Th3DaRk_Vampire:
oooouuuuhhhhhh yeahh do your magic, i'm whaiting for the update of your kernel to use in the new ota of cm12s
[ONE Original Android Development] kurtextrem:
You can do that already... I'm using it and I've noticed no problems at all.
[ONE Original Android Development] Th3DaRk_Vampire:
of course, the current version works, but at least to me has given me some lags
[ONE Original Android Development] andip71:
Already ready, just do the final testing now. Will be online soon...

I had this combination (latest CM12s and kernel beta3) in use for 170 hours without any restart - no lags at all.

Andi
[ONE Original Android Development] joefso:
Guys, I like AK color display settings ( think its called kcal?), how can I use boeffla to have these color settings too?
[ONE Original Android Development] andip71:
Not at all. I have not implemented this and also do not have it on my near-time roadmap.

So if this is very important for you, you need to use AK kernel.

Andi
[ONE Original Android Development] andip71:
New CM12s and CM12.1 kernels !!!

Hi and good morning,

there are two updated kernels for you:

3.0-beta4 for CM12s

4.0-beta9 for CM12.1 genuine CM

CM12s -- Version

3.0-beta4

27.04.2015

Kernel version upstreamed to 3.4.107 (www.kernel.org)

Ramdisk updated to latest CM12s version YNG1TAS17L

CM12.1 -- Version

4.0-beta9

27.04.2015

Updated with latest official CM kernel commits as of 26.04.15

Kernel version upstreamed to 3.4.107 (www.kernel.org)

Ramdisk updated to official CM12.1 version of 26.04.15

Enjoy

Andi
[ONE Original Android Development] molonad:
Thanx ☺ but my bug is still present after update, what should I do? ? I wanted to use other governors too, thanx
[ONE Original Android Development] andip71:
As I do not know what exactly goes wrong, I cannot recommend you something.

You said already, you do not want to go for a clean install. Then I am running out of ideas.

Andi
[ONE Original Android Development] Fenvarien:
Have you removed all other tuning, performance, kernel tweaking tools besides Boeffla app? (Synapse/UKM etc.) Have you any init.d scripts installed? Double check that you haven't activated any performance/governor settings of CM.

Did you flash Boeffla-Kernel over another custom kernel?
[ONE Original Android Development] molonad:
Installed AK then UKm Uninstall ed, then flashed boeffla then clean dalvik cache and cache and bug is here, all is stock I didn't touch nothing which is connected with performance. Synapse Uninstall ed
[ONE Original Android Development] andip71:
You could still do the following:

- take a nandroid backup

- flash CM12s over again (dirty flash)

If something before removed mpdecision etc, then it would be reinstalled.

Andi
[ONE Original Android Development] Clark789:
Hi Andi,

i can't see the update to beta 4 in the config-app yet. Will it take a little while?

Regards

Clark
[ONE Original Android Development] andip71:
Well, looks like it is still cached somewhere. I can see it already here.

But you can always download from the homepage and install manually if you do not want to wait.

Andi
[ONE Original Android Development] Clark789:
Thx and yes, the b4-zip-file is already on my PC. :)

Cheers

Clark
[ONE Original Android Development] molonad:
And after dirty flash I must flash boeffla again yes? ☺ I think xposed can be the issue? But don't have any Uninstall zip ? and I have only xposed for greenify..
[ONE Original Android Development] Renosh:
Wipe system in recovery first. Then flash CM12S then flash boeffla latest kernel beta 4. Let it boot first then check if the issue persists. If all is ok then you can install xposed, check after enabling modules again, if issue is back then xposed is likely the cause
[ONE Original Android Development] andip71:
XPosed.... you should not have said that :)

Yes, after a dirty flash of the rom, you need to install Boeffla again.

Andi
[ONE Original Android Development] kunal1540:
Roms build on aosp are not supported like Dirty unicorns.. Are they??
[ONE Original Android Development] rezor92:
Does it work on 17L OTA?
[ONE Original Android Development] davebugyi:
You are REALLY that lazy to read? Yes, it does.
[ONE Original Android Development] andip71:
Yes, this is unbelievable!!!

And I will ignore these kind of same questions over and over again in future.

Andi
[ONE Original Android Development] Leicxan:
I saw you installed ak kernel before you flashed boeffla kernel, you can take a look at this path, /system/bin there is a file called mpdecision, after you installed ak kernel, it will rename to mpdecision-rm

?And you can dirty flash cm12s, may be it can solve your problem.
[ONE Original Android Development] rezor92:
No, I'm not to lazy to read. I was not sure if it would work cause I read this @ the boeffla-kernel homepage.

I thought beta is for YNG1TAS0YL only
[ONE Original Android Development] molonad:
Oooh, ok all is ok now, I will not use xposed for now maybe, or is it connected with it?
[ONE Original Android Development] andip71:
Thanks Leicxan.

This would prove my theory, mpdecision process is broken. I did not know about this renaming done by ak kernel. Honestly, I even do not like it as mpdecision comes with the rom, no kernel should mess with it (my opinion) but instead preventing the process to start in ramdisk. But anyways.

Then the proposed dirty flash would have helped as well. But this is - of course - simpler.

Lession learned: I will have Boeffla-Config checking if mpdecision is running, if not a warning message will be shown. Will start to implement this after I made a first OxygenOs alpha kernel (yes, now I am almost there, these bastards made it really hard, but... )

Andi
[ONE Original Android Development] Clark789:
I still see after updating to 3.0b4 the phenomen, that with zzmove and zzmove native hotplugging and 3 cores are offline, they don't go online, when they are needed. There is only one core working...

Is it possible, that this this problem with mpdecision is the solution for the phenomen, which i still see?

Btw: all cores are working, when i change to 4 zzmove 4 cores native... But when i change back to zzmove native default, the phenomen is shown again.

Regards

Clark
[ONE Original Android Development] Leicxan:
lol, i found this two month ago, i was using CM11s XNPH05Q and i flashed ak kernel, then i had same problem, i finally found something in dmesg log, i couldnt remember very clear, it looks like [25.00879] mpdecision: can't find /system/bin/mpdecision
[ONE Original Android Development] andip71:
No, this is something only [MENTION=3279788]ZaneZam[/MENTION] could answer.

When using native hot plugging, mpdecision is completely irrelevant.

Then it is 100% up to zzmoove to do the plugging.

Andi
[ONE Original Android Development] davebugyi:
1 page back - updated the latest ramdisk from 17 OTA.

2 pages back - people confirming it does work on latest OTA.

Sorry for being rude, just saying that info is avaiable if you take a look.
[ONE Original Android Development] molonad:
All is ok after dirty flash ,so AK kernel did my problem? Weird
[ONE Original Android Development] andip71:
Not weird. If installing ak kernel leads to renaming a rom program to another name, it is quite clear it breaks all other kernels (incl. stock) that rely on it.

Andi
[ONE Original Android Development] molonad:
So every time I will install render or AK ok metalized and I will want to switch to your kernel I will must dirty flash? Nooo ? think I will stay on your kernel
[ONE Original Android Development] andip71:
No clue whether all kernel go the hard way and rename files. But if so, yes, then this is a must (or you copy mpdecision file to a safe place and put it back once you go back to my kernel).

Andi
[ONE Original Android Development] Fenvarien:
[MENTION=2451647]molonad[/MENTION] Instead of the wonky xposed/greenify combination you could use Servicely. https://play.google.com/store/apps/details?id=com.franco.servicely
[ONE Original Android Development] molonad:
Thanx trying, but don't understand how to work with it
[ONE Original Android Development] ak:
No one had ever complained about this.

What my kernel does is:

# Rename mpdecsion binary

mv $ bindir / mpdecision $ bindir / mpdecision-rm

if you want you can return by renaming "mpdecision", and than reboot the phone.

It was enough to report it in my thread.

however, I have created a zip for revert after seeing this exchange:

http://ak.hiddenbytes.org/

UKM_AK_uninstaller_v3.zip

thanks a lot

ak
[ONE Original Android Development] rezor92:
Okay you are right. Sorry, I will search better next time :D
[ONE Original Android Development] molonad:
Oooh Thank you very much, so if I want to go from your kernel to boeffla, I only must Uninstall UKm and then flash boeffla? ☺
[ONE Original Android Development] ZaneZam:
thx mate shows up your kindness to react to such a problem in another kernel thread :good:. yeah we had to fiddle around to get the native hotplug to work with zzmoove

because of this damn mpdecision "spell" but Lord Boeffla and i never thought about what happens if it isn't there any more, actually it should work because zzmoove doesn't

need it but well this an uncaught situation :)

would be great to hear from u if it works after using ak's script, if not we maybe have to dig deeper ;)
[ONE Original Android Development] RCT1:
Getting this error, but can't figure which is the error...
[ONE Original Android Development] Clark789:
Shall i use it for Boeffla kernel? I understood AK made it for his kernel. Am i wrong?

And btw: sometimes it works and sometimes 3 cores keeping offline...

Cheers

Clark
[ONE Original Android Development] ZaneZam:
ehm yes it's there to revert ak kernel changes. then it's clean to use another kernel.

and just to be sure: u are stressing the system enough, right ? for example depending on the used zzmoove profile (or also with other govs) it might take a bit till Cores come up but they of course should finally

"stability test" app would be good one to use for testing. if the Cores stay offline when u have 100% system load then something is really wrong. except u use one of the "one core" hotplug profiles ;)
[ONE Original Android Development] kunal1540:
Old version of config app maybe.. Not sure.
[ONE Original Android Development] davebugyi:
Maybe root access denied? No busybox?
[ONE Original Android Development] RCT1:
Nope, other apps have root and I've authorised root on supersu more than once.
[ONE Original Android Development] andip71:
Old app version.

Load and install 2.1.74 from homepage and manually install.

Andi
[ONE Original Android Development] Clark789:
Will test it tomorrow morning and report back...

Always used zzmove default hotplugging... :)
[ONE Original Android Development] alexbk66:
There's even a demo video, watch it:good:
[ONE Original Android Development] Clark789:
Hello ZaneZam,

i installed the script from ak and then made a simple reboot. The result was: in the first seconds all cores were running and when 3 of them got offline, they didn't went online again, for instance when i start Antutu. I made a simple restart again and saw the same behaviour. Then i switched the OPO off, waited a few seconds and restarted again. From then on all cores are doing, what they should. Getting offline, when nothing is to do and going online, if there is a little work to do. So far fine... But i got the impressions somewhere is a detail, which won't work at 100%....

Regards

Clark
[ONE Original Android Development] Mohdsultan:
Same here!!! 3 cores offline whatever happens.

I think this is a bug or something with exodus rom?
[ONE Original Android Development] abhibnl:
Well i used the render kernel when [MENTION=1546609]gianton[/MENTION] profile was not the default one. It was r4 i guess and smartmax showed the same ondemand behaviour.

Hi gianton bro!

I wanted to but in boeffla we don't have that much control over hotplugging and cpu boost. Could you please suggest if changing the tunable values ij governor only will do the trick as well?

Sent from OnePlus One
[ONE Original Android Development] andip71:
We will find out soon.

I will push an Boeffla-Config App update today. If the app detects mpdecision is not running for whatever reason (therefore preventing hot plugging to work), a big red warning will be displayed at app start.

Andi
[ONE Original Android Development] Mohdsultan:
Ohh nice I am waiting for the update.
[ONE Original Android Development] gianton:
You'd have to buy the full version of the app to have more control, that's the only way.
[ONE Original Android Development] andip71:
Pushed.

App 2.1.75.

Andi
[ONE Original Android Development] Clark789:
Thx, Andi.

Installed and no warning regarding mpdecision...

Cheers

Clark
[ONE Original Android Development] andip71:
Good. Then hotplugging when not using the zzmoove native hotplug modes should definitely work for you.

Andi
[ONE Original Android Development] netcitizen:
Hi, I am not much into configuring the parameters offered by custom kernels. Am looking for a stable, battery friendly kernel. I have flashed this one. is that enough or is there any profile that I need to load. If so , please link to the profile config files.
[ONE Original Android Development] fmc000:
Just apply the battery-friendly preset and you'll be fine.
[ONE Original Android Development] claptraw:
1. Make a backup of Boeffla app with titanium backup

2. completely deinstall Boeffla app from your phone

3. Install Boeffla app apk again

4. Restore titanium backup data to keep all your profiles
[ONE Original Android Development] netcitizen:
ok got it.
[ONE Original Android Development] Clark789:
And for the time being the zzmove native default works as well... ;)

Clark
[ONE Original Android Development] abhibnl:
Gianton, i've applied the tunable values exactly like your profile screenshots but still the governor don't want to touch the 300Mhz freq even when i'm doing nothing. Zzmove,interactive both works fine and ramp down to 300Mhz as soon as i stop using the phone but Smartmax keep ramping up and down but never reached 300mhz even 499mz. I guess it would also need hotplug tweaks to behave exactly like your profile.
[ONE Original Android Development] andip71:
Frequencies do not have anything to do with hotplugging.

Frequencies are solely decided by the governor, hotplugging (in my kernel) by mpdecision.

Just for clarification.

Andi
[ONE Original Android Development] andip71:
Oxygen OS

Hi all,

just as a little teaser for all Oxygen OS fanboys (and fangirls) here.

Kernel for Oxygen OS is progressing slowly but well. Almost all features already there. And the issues with source code (device tree blob, missing wifi drivers etc.) I could resolve by doing (painful and time consuming) reverse engineering of their stock kernel binary.

So, no timeline at all. Still some work to do, but it is pretty obvious, there will be an Oxygen OS Boeffla-Kernel soon :)

Cheers

Andi