yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] andip71:
New version...

Hi all,

just to give you a quick teaser for the upcoming beta...

Today I worked to implement some control over the mpdecision hotplug mechanism.

So while still going with official Qualcomm mpdecision, you can in future select to save battery (maybe) by limiting usage to 1, 2 or 3 cores only (independent of governor).

Or for smoothness, you can choose to always let 2, 3 or all 4 CPU cores plugged in.

See screenshots of the next config app (sorry, only in German, but think you will understand)...

On top, I merged already 6 new CM patches into both kernels...

* camera_oppo: Upstream update svn9954

* misc: Update from Oppo release svn9954

* msm: mdss: Override partial update PP block using ioctl

* wcd9xxx: core: Fix crash while headset insert and remove

* ASoC: msm: qdsp6v2: Fix for cmd status overwrite

* ASoC: wcd9xxx: Set chopper settings for UHQA mode

Not yet sure if I try to tweak the LED driver still and wait, or if I should release this new version to you sooner. Thoughts?

Cheers

Andi
[ONE Original Android Development] OberstGrausam:
You're welcome. :good:

Yeah I got it and I also activated the pro version but I didn't really see much of a difference. I know that crossbreeder has a great benefit on "low performance" phones or tablets such as my former galaxy s2. Considering the oneplus one, I don't see much of a change but I have to test it further. While on my p605 I notice a slight improvement in responsivness, but I guess I would be better off with a custom kernel which is unfortunately non exsistent for that device. Thanks samsung knox.^^

Anyway thanks for your opinion.
[ONE Original Android Development] Roman91:
As you want :)

sig sig, boeffla audio
[ONE Original Android Development] nazfalas:
I always love updates. :D

Sent from my PAC-OPO
[ONE Original Android Development] andip71:
Hehe, understand.

But I am already in the process of changing the notification led driver (unbelievable piece of code btw... looks like a script kiddie developed it, what a crap) to support some additional features like

- brightness control (only lower brightness, more is not possible anymore)

- fading speed

- maybe switch between fading and blinking

Andi
[ONE Original Android Development] Albieri[SPAM]:
hotplug only in the pro version of the app?
[ONE Original Android Development] andip71:
No. Did I say that?

All important functions will always be free. So will be hotplug control.

But you cannot see it as I have not released anything at the moment...

Andi
[ONE Original Android Development] f100cleveland:
With your new hotplug driver options, will we be able to tune it like msm_hotplug where it'll idle on one core but activate the 2nd core upon touch?
[ONE Original Android Development] andip71:
Well, not exactly. Generally, I am not a supporter of 3rd party hotplugging mechanisms so far, so my decision (for objective close-to-stock) is to go with mpdecision.

Control options are quite limited due to that, but they are there. And you will see them once I release it :)

Andi
[ONE Original Android Development] gauravsaini964:
Does this kernel works with Vanir-Exodus? If yes then which version should I flash?
[ONE Original Android Development] Norapapa:
Which is the latest test kernel? Work the kernel with euphoria (5.1.1) from 3.5.
[ONE Original Android Development] JG:
check out this post
[ONE Original Android Development] denyo81:
When the euphoria os based on CM I think yes. Make a backup and then flash the kernel for 5.1.1.

http://boeffla.df-kunde.de/test_unofficial_opo/

After three days testing the new experimental for oxygen. All works fine for me. No dt2w battery drain more. Touch effects works like a charme! :)
[ONE Original Android Development] andip71:
And.... three new kernels (CM12.1, CM12s, and even a new test version for CM11s due to many requests) are due to be out soon...

Stay tuned!

Andi
[ONE Original Android Development] Roulianooo:
Thanks Andy :)

:fingers-crossed: Patiently waiting for your magic kernel to flash 0106 CM12.1 :D
[ONE Original Android Development] Fevves:
+1 My Lord ;) Thanks for taking into consideration the old farts like myself ;) Can't wait to flash the cm11s test build here.
[ONE Original Android Development] andip71:
New betas...

Hi all,

ok, finally new kernels for you with the unofficial new touch drivers (as they seem very good) and a new zzmoove governor (credits to ZaneZam).

Please note, the kernels are for CM12.1, CM12s/COS12 and for CM11s. However, I have not tested the CM11s kernel at all, so you will see how it behaves.

Here we go:

CM12.1 -- Version

4.0-beta18

Note: Only for CM nightlies of 14.05. or newer (and custom roms having these new changes in)

01.06.2015

New, unofficial, selective touch screen drivers implemented (Gerrit) - this should fix the touch screen issues for many without draining battery

zzmoove governor updated to version 1.0-beta7 - stability improvements and hotplugging optimisations (credits to ZaneZam)

New zzmoove governor profile "relax" added, aiming to avoid audio stutters during screen off

Replaced kernel-internal busybox by a new version

Ramdisk updated to official CM12.1 version of 01.06.15

CM12s/COS12 -- Version

3.0-beta10

01.06.2015

New, unofficial, selective touch screen drivers implemented (Gerrit) - this should fix the touch screen issues for many without draining battery

zzmoove governor updated to version 1.0-beta7 - stability improvements and hotplugging optimisations (credits to ZaneZam)

New zzmoove governor profile "relax" added, aiming to avoid audio stutters during screen off

Replaced kernel-internal busybox by a new version

CM11s -- Version

2.10-beta1 stable

(untested by me !!!)

01.06.2015

New, unofficial, selective touch screen drivers implemented (Gerrit) - this should fix the touch screen issues for many without draining battery

zzmoove governor updated to version 1.0-beta7 - stability improvements and hotplugging optimisations (credits to ZaneZam)

New zzmoove governor profile "relax" added, aiming to avoid audio stutters during screen off

Replaced kernel-internal busybox by a new version

Enjoy

Andi
[ONE Original Android Development] Clark789:
Thanks a LOT to Andi and to ZaneZam too!!! His work for the governor is awesome as well!!!

Cheers

Clark
[ONE Original Android Development] Texan1:
Big thanks as always Lord Boeffla, all of us here appreciate your work! :good::good::good:
[ONE Original Android Development] anshad666:
Sent from my bacon powered by boeffla
[ONE Original Android Development] lippol94:
2 little question about zzmoove updates:

- What profile is "relax" based on?

- In order to take advantage of hotplugs improvements should we enable zzmoove hotplug profile (in your app)? Or default is fine?

Thank you :)
[ONE Original Android Development] andip71:
I let [MENTION=3279788]ZaneZam[/MENTION] directly answer this question, as then you get first level information directly by him (and not second level by me).

Thanks to you, Zane for the updates!!!

Andi
[ONE Original Android Development] SABman12:
Thanks alot Lord Boeffla.

I just checked the new beta kernel for CM11S.

I had stock 44S with your kernel from 18/05.

I installed your new kernel.

Seems to be great - no bootloop, no touch problems, and I can just hope that the battery will be good as it was!

I'll keep update about the battery drain.

Big thanks!
[ONE Original Android Development] andip71:
Thanks, sounds promising.

The drain should also not exist on CM11s when it was finally ok on CM12s and CM12.1.

So, fingers crossed.

Andi
[ONE Original Android Development] Emway:
Strange.... Black screen after install beta18 on Tugapower45 ?. (base cm12.1 30may)
[ONE Original Android Development] andip71:
Does beta17 or 16 work?

What when you download and flash it again?

Not knowing Tugapower. But it runs fine here on official CM12.1.

Andi
[ONE Original Android Development] ZaneZam:
1.) based on moderate but with other hotplug freq thresholds

2.) yes :)

2.1) but it's not a must u can also leave it on default if u like :)

"relax" just have no special sleep limits and have 2 cores online all the time, "default" mpdecision has this "2 cores online behaving" too so it's about the same ;)

i hope u guys enjoy the new beast! :)
[ONE Original Android Development] Emway:
Tried beta17 but also no screen.... Same on a older version of AK kernel. Tried the latest AK kernel and that one is working (and stock off course)
[ONE Original Android Development] Roulianooo:
Beta 18 works fine here with CM12.1 0601 nightly :)
[ONE Original Android Development] magnamentis:
i suspect wrong firmware, but you give not much info so it remains a guess.

from may 15th you need a firmware from may 15th or younger to flash a rom based on cm12.1 version may 15th or younger
[ONE Original Android Development] TorchaOne:
Do we have 0.7 or 1.0 beta7? Or does oneplus has own version history somewhere? :)
[ONE Original Android Development] andip71:
It is 1.0-beta7.

And here you go:

http://xdaforums.com/galaxy-s3/development/info-cpu-governor-zzmoove-t2326544

Andi
[ONE Original Android Development] gondsman:
Lord Boeffla, I'm really nitpicking, but on your website in the download page it says "CM12 (version 4.x)" isntead of "CM12.1 (version 4.x)". :)
[ONE Original Android Development] andip71:
Hm, can you please mail me a screenshot to support@boeffla-kernel.de?

I could not quickly find what you are spotting. So any help greatly appreciated.

Thanks

Andi
[ONE Original Android Development] ZaneZam:
indeed it had its own history (but only a little bit different to i9300 version due to platform specific changes) but now since 1.0b7 i synced the i9300 (exynos) and the OPO (snapdragon) versions

so there is now only one, and i try to keep that so in the future.
[ONE Original Android Development] ygor.almeida:
So Far so good here too CM12s ... no touch issues, and battery keeps going well ... lets see at the end of the day !!!
[ONE Original Android Development] eak1080:
Cm11s looking good.
[ONE Original Android Development] magnamentis:
[MENTION=947981]Lord Boeffla[/MENTION]

hi andy

what do you think about this post ?

i don't encounter any of that and i'm asking more as to know what i should answer there. i cannot reproduce anything like that, is it possible or

is it possible that unknown factors are responsible?

thanks ( for everything )

alles flutscht wie immer LOL
[ONE Original Android Development] andip71:
I think, the touch screen driver topic will be a neverending one.

The fix is still not official and the likelyhood CM team does not put it further is still not zero.

So far nobody else (apart from one user on OxygenOS, but this is a completely different story as the patch needed to be ported there, which can be error-prone) reported any issues so far.

And yes, might be the first fix was slightly better. But we know what it came with :)

Andi
[ONE Original Android Development] tr0ner:
Thanks for the quick update once again.

My first impression was the same. Screen got more laggy again compared to the first fix...cannot say anything about battery drain yet.
[ONE Original Android Development] Fevves:
cm11s here coming from 2.8 ver, flashed 2.10 now , dt2w enabled now, current battery level is now at 95% will monitor throughout 24hrs with my usual use with the same kernel profile, same habits and will report back.
[ONE Original Android Development] markvd90:
Is there any way to disable CABC? At low brightness, my screen is flickering from time to time...
[ONE Original Android Development] abhibnl:
Well i've noticed it too and was never really sure what it is. I blame OPO for it with a faulty hardware and it happens only on low brightness in a dark room and it's really noticeable.
[ONE Original Android Development] andrew2511:
[MENTION=947981]Lord Boeffla[/MENTION] may you have a look at this commit? http://review.cyanogenmod.org/#/c/99143/

This should revert a previous commit and solve the awful black screen not waking up from sleep (and optimizing all apps after crash)

Thank you so much for your great work!
[ONE Original Android Development] maxver0:
On which version did it occur?
[ONE Original Android Development] anshad666:
Using latest kernal for last couple of hours ..it seems pretty good..battery life was good.no deep sleep issue..i got 6 hour deep sleep with only 2 percentage of battery reduction..i dont have the touchscreen issues so i cant tell whether it is fixed or not..anyways feeling happy..great work lord...
[ONE Original Android Development] kalpik:
No, it's not the hardware. It's CABC. You can disable it in synapse for AK kernel, and the flickering goes away! Would be good to have the setting on the boeffla app.

Sent from my A0001
[ONE Original Android Development] Texan1:
New per-panel display firmware has now officially been inserted into latest 2/06 CM12.1 nightly - http://review.cyanogenmod.org/#/c/99607/
[ONE Original Android Development] andip71:
Well, on CMs this option is available in display settings (last point).

But apparently not on CM12.x.

I do not consider at the moment to make it available in Boeffla-Config, too less people would use it.

But you can place an init.d script which does the following:

echo 0 >/sys/class/graphics/fb0/cabc

It should do the trick after every reboot.

The only thing that makes me think is: This patch is lying around already for about 2 weeks and nobody cares about it.

Although I see, in previous kernel versions (like CM11... etc.) they have reverted it as well.

Will think about it, and if I include it, would release new kernels where this applies by tomorrow.

Yes, have seen it. And I am glad they did it, so the feature in my kernels is not "unofficial" anymore. Hehe.

Andi
[ONE Original Android Development] andip71:
CM11 and CM12

Hi all,

to be "complete" with the new touch drivers on all my kernels, please find also the last two kernels (genuine CM11 and CM12.0) compiled for those who still need it:

CM12 -- Version

3.6-beta1

18.05.2015

New selective touch screen drivers implemented (Gerrit) - this should fix the touch screen issues for many without draining battery

zzmoove governor updated to version 1.0-beta7 - stability improvements and hotplugging optimisations (credits to ZaneZam)

New zzmoove governor profile "relax" added, aiming to avoid audio stutters during screen off

Replaced kernel-internal busybox by a new version

CM11 -- Version

2.10-beta1

01.06.2015

New selective touch screen drivers implemented (Gerrit) - this should fix the touch screen issues for many without draining battery

zzmoove governor updated to version 1.0-beta7 - stability improvements and hotplugging optimisations (credits to ZaneZam)

New zzmoove governor profile "relax" added, aiming to avoid audio stutters during screen off

Replaced kernel-internal busybox by a new version

Enjoy

Andi
[ONE Original Android Development] andrew2511:
On every nightly recent than 14-05
[ONE Original Android Development] suaverc118:
Hey guys I'm having same issues with battery drain when I switched to Tamesek with latest kernel here. Its the damn Google app. Only way to get ANY deep sleep is to disable Google. Why am I having such a horrible issues with my phone? Will a clean Install of my ROM do anything? I'm getting on average 4 hours SOT. I don't get it. I'm someone who used to get 7.5 plus of SOT. The little deep sleep in the pic is because I disabled google., but I can't do that because I need it for my daily use.
[ONE Original Android Development] hp13:
what does this do?
[ONE Original Android Development] andip71:
Fixes the well-known touchscreen issues for almost everyone.

(ok, so far I even am aware of two users who had more problems after the new firmware was introduced, but it seems the bare minority really)

Andi
[ONE Original Android Development] hp13:
Ahh that explains it. Will beta 18 Boeffla kernel work fine with it or we should wait till an update? I enjoyed beta 17 with few reboot while running battery friendly preset profile. Other than it was stable.
[ONE Original Android Development] andip71:
What would you wait for?

I do not understand... of course use beta18 :)

And you should not have any single reboot, honestly. If you have, we need to investigate that.

In that case, change governor to interactive with standard profile and check again for some time.

Andi
[ONE Original Android Development] ZaneZam:
hasn't battery preset light undervolting?

might be too much for the device. just my 2 bananas :)
[ONE Original Android Development] andip71:
Right, true! I was fogetting about that. Many thanks for the hint !!!

Andi
[ONE Original Android Development] magnamentis:
bother to read?
[ONE Original Android Development] SLBoy:
How about alternate versions for folks who never had any touch issues? Flashed last beta10 but now im afraid I might have battery drain or maybe its placebo idk :D
[ONE Original Android Development] andip71:
Nope. Not provided by me at least.

Expect these drivers to show up in almost all kernels now officially, next updates of CM12s etc.

Everyone however can recompile my kernel and remove the drivers.

Just, pls do not expect me to do that on top of everything still. This is not feasable (unless you make my day approx. 2 hours longer :) )

Andi
[ONE Original Android Development] fmc000:
It seems that these drivers are included in the newest OxygenOS build too.
[ONE Original Android Development] andip71:
Oh, is there a new build? By Oxygen?

Because on their kernel code repo, nothing was changes for ages...

Andi
[ONE Original Android Development] fmc000:
Here.
[ONE Original Android Development] andip71:
Wow, these bastards have not updated their kernel repo so far.

I know they do not care, but I will drop a note there and request a kernel code push as per GPL license.

Anyways, my OxygenOS kernel had the fix already before :)

Andi
[ONE Original Android Development] akash4357:
On a sidenote, What is the ROM of your choice?
[ONE Original Android Development] andip71:
Daily driver OPO: CM12s

Andi
[ONE Original Android Development] akash4357:
May I know why? It's filled with bugs & outdated!
[ONE Original Android Development] SABman12:
I can confirm that the battery drain is not exist anymore or reduced alot.

I get good battery life with the new kernel.

(Im on CM11S 44S, with the lasted kernel)
[ONE Original Android Development] andip71:
It is working perfectly fine for me. No bugs encountered ever with my personal usage pattern.

Rock stable rom for me.

Andi
[ONE Original Android Development] andip71:
Ok, here is my official request to update their kernel repo which they are obliged to.

https://forums.oneplus.net/threads/ghost-touch-fix.314410/page-5#post-11427964

Still I do not expect a timely answer by them, based on experience so far.

Andi
[ONE Original Android Development] Stroky:
So here is an update from my side. I tested a lot and I noticed that the best battery life is on beta 7. I use cm 12S.

I tryed al other builds with exact the same settings.

For Info always gestures off and i never had Touchscreen problems.

The idle drain in airplanemode on beta 7. 0,1%/h on all other builds. 0,4%/h
[ONE Original Android Development] andip71:
Well, not that surprising.

I guess the only way to fix the touch issues for most of the people was to make touch screen driver/firmware changes that come with slightly higher battery consumption.

But whether 0,1% or 0,4% / h is marginal if the touch problems are history with it. Or?

And yes, beta7 had the "normal" old touch drivers without any "fix" in. So I am not suprised this has the least idle battery consumption.

Andi
[ONE Original Android Development] akz1x1:
Mpdecision process

I just flashed Boeffla beta 10 on my opo running cm12s since it was heating up to 70 degrees while charging... And I got this error when I opened Boeffla kernel app..

When I checked /system/bin mpdecision-rm is there...

Any help would be greatly appreciated
[ONE Original Android Development] andip71:
1) Which error did you get? (nothing was contained in your post)

2) which rom and/or kernel did you have before flashing boeffla?

3) the file must be named "mpdecision", not "mpdecision-rm". So someone renamed it. You can rename it back to mpdecision and reboot.

Andi
[ONE Original Android Development] akz1x1:
Okay thanks man.. Will try and report back ... And updated the post with screenshot

---------- Post added at 03:32 PM ---------- Previous post was at 03:30 PM ----------

I was using stock cm12s kernel before
[ONE Original Android Development] andip71:
And you are sure you were on official CM12s stock rom? Because in that rom the mpdecision is not called mpdecision-rm !!!

Any mods you installed? Any kernels in between before stock? Xposed? Anything...?

Your rom installation is not healthy anymore.

Explanation: Without mpdecision, CPU core hotplugging is not working anymore. So it could have been all your 4 cores were running all the time, creating heat.

Andi
[ONE Original Android Development] andip71:
Seems you were on AK kernel before, look here:

http://xdaforums.com/showpost.php?p=60384801&postcount=4334

Andi
[ONE Original Android Development] akz1x1:
Thanks man .... Renamed the file and that error is vanished ...

Any guess how the file was renamed or what is the need of that file?

I hope this will fix the overheating during charging
[ONE Original Android Development] andip71:
Look above, I am sure you were using AK kernel before and not stock kernel.

Or you used AK kernel before stock kernel one time.

Andi
[ONE Original Android Development] akz1x1:
Thanks again...

I once flashed ak and had weired touch issues and he told me ak is not yet compatible with cm12s

So I flashed stock 12s and then flashed boeffla ...

But then I had weired systemui force close like issue

For example when I'm playing video from gallery or playing games I'm sent to lock screen...

So I flashed stock cm12s and observed this weired heating ... Yeah over 70 degrees and had a burning smell

I hope that rename caused the problem and thank you so much for the wonderful kernel and awesome quick support .

.

May I know what that file actually do just curious?
[ONE Original Android Development] andip71:
Yes, let's see. But it should be sorted.

mpdecision does a bunch of tasks:

- it decides about how many CPU cores are working and which one are sleeping

- it takes care about thermal throttling (when phone gets too hot, it limits cpu usage)

AK and many other kernels remove that file (by renaming) it as they have implemented this natively in their kernel code.

However, I am staying close to stock with my kernels (this is one of my main objective for best compatibility), so my kernel needs mpdecision running just as it is out of the box with a stock or CM rom.

Andi
[ONE Original Android Development] akz1x1:
Okay man ... Been using boeffla since I was using my s3

Always so perfect...
[ONE Original Android Development] andip71:
I am glad I put some smart logic into boeffla-config app, to detect these kind of issues.

Just something pops into my mind... I could not only report but even offer to rename the file back for the user. Mh, maybe I will put that in one day.

Andi
[ONE Original Android Development] BlakeSm:
Is there anyway to disable sunlight enhancement? I have it off in my settings but it's still doing it.
[ONE Original Android Development] andip71:
No, as it is a function of the rom.

Maybe a rom bug...

Andi
[ONE Original Android Development] magnamentis:
rom feature ?

provide more info so that we know how to help please !
[ONE Original Android Development] nicolahaye:
Edit: nevermind sorry :s
[ONE Original Android Development] akz1x1:
Renaming the mpdecision-rm did the magic... No more overheating...

Using the battery saving profile and everything works fine...

Zero issues or bugs so far.. No apps crashes, freezing or overheating...

Thanks

Just a request.. Is it possible to include capacitive button lights up only when I touch the buttons (not every time I touch the screen)... It was one of my favorite on i9300 kernel
[ONE Original Android Development] andip71:
This is on the list when I find some hours free time, so it is supposed to come, yes.

Andi