yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] andip71:
No, he actually meant beta15. He is one of the pre-testers and did not read I specifically mentioned to not post results in the thread but via pm to not confuse people...

Andi
[ONE Original Android Development] Fenvarien:
Sorry about that and for the foreseeable confusion... My kids got me before I finished reading the pm. ;) Too much multitasking with two kids and a smartphone, hehe!
[ONE Original Android Development] andip71:
Not a biggie. Sh*t happens, like we Germans say [emoji6]

Andi
[ONE Original Android Development] Criton30:
OFF: two kids is nothing :) I have three :D and flashing new rom and kernel and soo on its not so easy :) I have time only in the night :mad:
[ONE Original Android Development] Criton30:
Thanks for good working [MENTION=947981]Lord Boeffla[/MENTION] and [MENTION=3279788]ZaneZam[/MENTION] for Linaro. Kernel working very good with CM12 Temasek Linaro v8.3 :good:
[ONE Original Android Development] yanner2012:
I agree, it work very fast and smooth on Exodus also. Thank you.
[ONE Original Android Development] 530farm:
Slimsaber just implemented "live display" and fusion said there are special kernel commits required to be compatible, wondering if anyone knows if boeffla has these. Thanks!
[ONE Original Android Development] andip71:
Only if they are merged by cm team in official kernel sources.

Andi
[ONE Original Android Development] crazydude10:
I am trying to install this kernel for the first time using TWRP 2.8.5 with CM 11 Latest Nightly

I got the kernel from two sources - The link in the 1 st post and from the Kernel Config app. The file hashes match.

But whenever I try to install from recovery, I get the Zip Signature verification failed. I this can be disabled, but the last time I did that, the ROM didn't boot. Any way to solve this issue ?
[ONE Original Android Development] andip71:
Seems like for some reason the download got corrupted.

Try downloading on PC and then moving the file via USB to the phone.

Andi
[ONE Original Android Development] P1nGu1n_:
Zip signature verification has always failed on your kernels for me, even when TWRP was able to verify the file by using the provided checksum file. CM rom zip signature check always succeeds, so I always disable it for Boeffla-kernel. Not sure if this is useful.

Sent from my phone, please forgive any tpyos.
[ONE Original Android Development] crazydude10:
Thanks, I disabled the feature, and was able to install it.
[ONE Original Android Development] saikm:
use PCC instead of kcal？
[ONE Original Android Development] andip71:
Ok, I will look into that.

I never used TWRP until a few days ago, so this md5 check was not tested by me ever. Also with TWRP I always have it switched off, so never came across an issue.

But will look into that.

Edit: Ok, seems I just need to rename the checksum file to have md5 instead of checksum at the end. I will try that.

Edit2: Just realized it has nothing to do with zip file signature verification. That is something else, and yes... I do not sign my zips. Never did...

Not in near future plans, search the thread, then you will find my explanation.

Andi
[ONE Original Android Development] shaheen7m:
Oh my lord, Great to see you here. Remembering the good old days of my s3
[ONE Original Android Development] sathish804:
Can we use one governor and hotplug from other governor like in posted screens.
[ONE Original Android Development] andip71:
No, that will not work.

It will just do normal default hot plugging in that case.

Andi
[ONE Original Android Development] maxver0:
My prayers have been listened. Hurray boeffla. Hurray duarte. Hurray material design
[ONE Original Android Development] andip71:
Well, honestly, material design is not new... it was there for a long time already.

But it was not preselected on Android L.

Andi
[ONE Original Android Development] maxver0:
I'm aware of that ;)
[ONE Original Android Development] andip71:
CM12 beta15

Hi all,

after I got green light from the pre-testers, I finally release a new CM12 beta kernel for you.

Note, you need to update to Boeffla-Config 2.1.69 before you flash the new kernel. Make sure you have done this.

As perviously said, the biggest change is SELinux is now set to enforcing after the kernel booted. So the security level is the same as with CM12 stock kernel, i.e. it follows CM12 standards now.

If you are facing issues with SELinux to strict, you can configure the kernel in Boeffla-Config to boot in permissive mode again (like all the previous versions). See below in change log where you can configure that if required.

Version 3.0-beta15

04.03.2015

Note: You need Boeffla-Config App version 2.1.69 or higher for this kernel !!!

This kernel version now boots in SELinux enforced mode by default, according to CM12 standards.

If you want to still run in permissive mode (e.g. for xposed working), you can switch this in Boeffla-Config settings -> kernel startup options and it will be active with next restart.

On-the-fly (and not sticky), SELinux can be toggled as well from Boeffla-Config overview tab.

Improvement: zzmoove updated to version 1.0-beta6a (with improved backlight notification instead of backlight hook)

Improvement: dynamic fsync improved (with improved backlight notification instead of backlight hook)

Improvement: Backlight notification improved to cater for special scenarios like enabled "ambient mode"

Update: Updated with latest 11 official CM kernel commits as of 04.03.15

Update: Touchscreen firmware now on same version than in CM12 official stock kernel

Update: Ramdisk updated to official nightly of 04.03.15

Improvement: Some internal optimisations

As always, enjoy.

Thanks

Andi
[ONE Original Android Development] acuicultor:
Awesome battery life with cm12 last nightly and beta15. Thanks lord.
[ONE Original Android Development] bloof:
[MENTION=5286554]sathish804[/MENTION]

But you can still use optimized HP, or other non zzmove HPs.

Also, another question for [MENTION=947981]Lord Boeffla[/MENTION]: if you use zzmove governors, what happens if you use non-zzmove HPs (not that i would) ? Does it default to zzmove native hotplugging from the governors?
[ONE Original Android Development] andip71:
No. When you use zzmoove and a normal hotplugging profile, standard mpdecision takes care of hotplugging. As with all other governors too.

Just zzmoove can take it over itself.

Andi
[ONE Original Android Development] spanish33:
[MENTION=947981]Lord Boeffla[/MENTION] cannot boot beta 15 on SlimLP build date 4th March . Only boot up to boot logo.

The default kernel in slimlp is set to enforcing so I am not sure what is the issue. Maybe the rom need to update.

App version 2.1.69

Edit : still doesn't boot with updated rom.
[ONE Original Android Development] kalpik:
Can you please explain a bit more about "backlight notification vs backlight hook"? I'm just curious ?

Sent from my A0001
[ONE Original Android Development] andip71:
Then SlimLP is currently not compatible anymore to CM12 main branch.

If beta14 boots up for you, just continue using it. Beta15 has the updated CM ramdisk included, maybe it is too new for Slim.

Hm, no? It is a functional feature. You can can wake up and put to sleep with additional gestures. Has zero effect to battery usage.

This is a very technical, internal implementation detail.

There are some functionalities in my kernel that require to know whether the screen is actually on or off.

Examples: zzmoove needs it, dynamic fsync too, and the sweep2sleep gestures.

So previously I called the respective triggers in these three components by a call out of the OPO lm360 backlight driver. Which perfectly worked, but architecturally it was not a "nice" solution.

Now, this is changed by a call chain. Means, instead of having hard function calls hooked into the backlight driver, all areas interested in whether the screen is on or off register themselves at a handler with callback functions.

This means, no more changes to the lm360 driver code anymore when someone else wants to be informed about screen on/off changes.

So, now this is a very generic and clean solution.

That's all about it :)

Andi
[ONE Original Android Development] 530farm:
I'm on slimsaber and beta15 linaro with out issue
[ONE Original Android Development] Vially:
Just chiming in here. I just got the OPO 2 days ago, and the first thing I did after charging it over the night was to clean install BlissPop and Boeffla kernel. This is such a nice solution, man, I couldn't have even imagined it. Not only have you built a well running kernel, but also the app. That app is the best thing that has ever happened to a kernel, hands down. Even thought everything is on beta level, all new, I haven't seen a single reboot or anything funny.

Excellent work Andi, excellent. Thank you for your wonderful contribution, it is things like this that bring life into the open source community and why not, humanity as well. Thank you once again!

P.S. I love that you also take the time to come with explanations for the things you do, for example the backlight thing above. I was also curious to find out what that means, and the fact that you also answer beginner technical questions like that is making everything so much more interesting and fun!
[ONE Original Android Development] aswinrulez:
Lord Boeffla i think the touch screen issue is solved in beta 15. So far i didn't face any problem.

Edit: Ok, so the touch is not becoming unresponsive like before but i cant still type fast without screwing up the text.Only some letters are getting registered and sometimes its taken as a swipe when typing to fast. But this speed is perfectly fine in nexus 5 and other phone :\
[ONE Original Android Development] Vially:
Did anyone notice anything funny about the colors in the latest beta? I have just flashed beta 15, and after a reboot it looks like all my desktop icon colors are... strange. It's like the screen is overblow, like someone has pushed a saturation slider all the way up. It does not manifest itself in screenshots, I tried.

I am on the latest Bliss Pop and everything was fine on beta 14. I have clicked ACTION, Load & flash/store kernel, found beta 15, then flashed that. The phone rebooted, and then I saw the colors. I have later wiped cache and Dalvik, but I have the same result. Latest app version as well (69).

I have the debug file, not sure if I should mail it or I can attach it here. Let me know if interested, otherwise I will just return to beta 14 :)
[ONE Original Android Development] eleete0712:
Disable Sunlight Enhancement in Display Settings. Worked for me :)

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] Vially:
I think this did the trick. But why is this happening, I didn't have this problem on beta14, and the setting was on (Sunlight Enhancement). Could anything be wrong with the light sensor readings, or what do you think? I haven't changed the location of the phone between flashing kernels (inside), so I am not sure why things would change with the new kernel :(
[ONE Original Android Development] eleete0712:
I think there are some recent commits regarding color calibration in cm12 nightlys and kernel.

And I read somewhere that sunlight enhancement option will be removed in future releases.

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] andip71:
Well, now there is not more I can do anymore. Now the touchscreen drivers are like CM12 stock.

Yes, there were some commits to both kernel and rom on this color stuff by CM team.

The kernel commits were done after beta14, so I contained them in beta15.

Let's see if they still work on it and this is just an "in-transit" issue until the finished the implementation. Or they will roll that stuff back one day.

Andi
[ONE Original Android Development] ruggedknot:
----Rooting concern------

Seeking some pointers here.

After flashing the Kernel through recovery, phone isn't rooted anymore. Using SuperSU as my root app. I've tried searching through the thread but haven't found any solutions with what I've come across so far. Is there any other root app zip that I can flash? Any help would be greatly appreciated.
[ONE Original Android Development] xanthrax:
Update your recovery
[ONE Original Android Development] andip71:
Why don't you reinstall supersu then? This is usually the first thing to do when root gets lost.

Andi
[ONE Original Android Development] aswinrulez:
I understand. I think CM itself has to fix it. Already this excat same issue is raised by a lot of users in jira as well as oneplus one forum.

https://forums.oneplus.net/threads/touch-screen-issues-were-listening.186829/page-46

and also in jira

https://jira.cyanogenmod.org/browse...status = "In Progress" ORDER BY priority DESC

but atleast half of the issue is solved. Thank you for that :)
[ONE Original Android Development] GabrielSousa:
great kernel, i luv it ;)
[ONE Original Android Development] ruggedknot:
I was certain that I'd done that - between swapping/installing trying different ROMs with Boeffla via MultiBoot. Naive that I didn't doubly check the obvious but thank you for pointing it out. Goes without saying that your work is greatly appreciated.
[ONE Original Android Development] Lord-D:
Does the 2.3 kernel work on 44S?
[ONE Original Android Development] andip71:
As long as you take the one for cm11s and not cm11, then yes. It is optimised for cm11s.

Andi
[ONE Original Android Development] RCT1:
Getting error connecting wifi as SS.

I've tried almost all CM12 roms and the problem remain.

Any ideas what is causing this issue?
[ONE Original Android Development] andip71:
No. Never had any wifi issues.

Andi
[ONE Original Android Development] RCT1:
Have to try everything stock...
[ONE Original Android Development] WhiteHartMart:
Just popped in to say thank you for a great kernel. Running CM12 nightlies came from another custom kernel - but already battery life seems amazing with no damage to the smoothness of the phone - most are saying CM12 has a detrimental effect on battery after CM11s - they can't have tried this :)

Brought to you by a CM12 Lollipopped OnePlus One :)
[ONE Original Android Development] slebit:
[MENTION=947981]Lord Boeffla[/MENTION] Confirmation number: 3US23253KX2381154
[ONE Original Android Development] andip71:
Thank you very very much.

Much appreciated [emoji2] [emoji106]

Andi
[ONE Original Android Development] cr0wnest:
Lord Boeffla I'm so glad you're developing kernels for the OnePlus One. I was a big fan of your kernels for the Galaxy S3, they really helped improve the experience on that phone, and I expect you'll do the same for this one too. I just got my OnePlus One several days ago and I'm gonna give your kernel a shot first. :D
[ONE Original Android Development] Tunasty:
You won't be disappointed at all! This kernel is one of the best and up to date all the time. Best part is that there's no drama in this thread lol.
[ONE Original Android Development] andip71:
Thanks, much appreciated.

And yes... I do not need dramas in my threads. I just have too many open threads across 5 boards. If people start trolling and pestering the party mood here, I would certainly stop sharing my work.

But fortunately all is good here, as it also is and was in my Galaxy S3 threads (and hopefully soon in a new thread I will open approx. next week on another device).

There were a few trolls in the beginning, but they realized here is no place for them to be.

So, wanna take the opportunity and thank my community here for being that polite, respectful and helping each other. Really appreciated!

Andi
[ONE Original Android Development] Clark789:
Giving back that compliment: if there wouldn't be such a polite and capable support, there would be not such a respective atmosphere here...

One little hint for the new device for the weekend? ;)

Cheers

Clark
[ONE Original Android Development] bloof:
The iphone 6
[ONE Original Android Development] cr0wnest:
I've just noticed my AnTuTu scores are significantly lower on this kernel compared to stock CM11S. The 3D performance just seems a tad worser than before, was this done on purpose to conserve battery? I've already tried on both interactive and intelliactive governors, I didnt touch the GPU settings. But the battery life seems pretty decent so far. :)
[ONE Original Android Development] hhp_211:
as stated in the OP

"And: I do not really care about benchmark numbers, they say almost nothing as long as something is not completely wrong. Important for me is the feel-good factor.

I am also not interested in gaming at all, so never expect a gamer kernel. It will just not happen...

"
[ONE Original Android Development] cr0wnest:
Ah that explains it, I cant believe I missed that out.

Im not a heavy mobile gamer too so its not a deal breaker for me. The kernel feels really smooth for normal usage. :good:
[ONE Original Android Development] andip71:
Mmmmmh. Not yet. Longer story. Soon (I like teasing too much).

Andi
[ONE Original Android Development] andip71:
Still should not be worse when you have same settings.

Increase min gpu to 200 Mhz and try again.

But yes, battery life is more important for me than benchmarks that do not mean a lot.

Andi
[ONE Original Android Development] HaTrED_:
Whatever it may be, please don't neglect our beloved 1+ 1... [emoji6] [emoji14]

Tapatalked!
[ONE Original Android Development] andip71:
No worries. I clearly prefer the OnePlus over the other phone.

OnePlus is my main phone and will be for next year at least...

Andi
[ONE Original Android Development] ricardowec:
Let just put mi five cents into this: Over the past few years Ive owned so many Android devices I cant remember, all rooted and customized with the best roms and kernels I could find in XDA

This Kernel is one of the finest pieces of art ever flashed in one of these gadgets.

Thanks again LB.

Cheers
[ONE Original Android Development] Mrwargod:
That is really good to hear. :)

Keep up your awssome job with this kernel.
[ONE Original Android Development] Cris7ianO:
Does current beta 15 boot with latest slimsaber of 06-03-15? :D

Anyone tested?

Sent from my Bacon
[ONE Original Android Development] Mrwargod:
Yes it does. I'm running it.
[ONE Original Android Development] RCT1:
It as to be some app, but how can I find witch one?

During the night wifi disconnects and I have to activate manually...
[ONE Original Android Development] maxver0:
Nooo, lastest update broke double tap to wake. It works the same way blisspop did, I have to tap 10 or sometimes 50 times to make it wake. Works just fine on 14 release. :(
[ONE Original Android Development] digkong:
Can we use this kernel on vanir aosp ?
[ONE Original Android Development] andip71:
Not for me and >80% of the users.

Beta15 has newest touchscreen firmware included, just like official cm12 kernel.

Beta14 has the older firmware included. So you have to stay on 14 then until cm team finally provides a firmware which works flawlessly for everyone.

Andi
[ONE Original Android Development] WhiteHartMart:
Beta 15 was working great on previous CM12 nightlies - seems not on the 08/03 one. Reverting to stock kernel and dttw works fine again.

Brought to you by a CM12 Lollipopped OnePlus One :)
[ONE Original Android Development] andip71:
Flashed nightly 08/03 as well now.

Dttw working as always, no problems at all here.

Andi
[ONE Original Android Development] WhiteHartMart:
Strange. Mine did to start but after a reboot the option kept deselecting itself from settings?

Brought to you by a CM12 Lollipopped OnePlus One :)
[ONE Original Android Development] aswinrulez:
Touchscreen firmware is really messed up and causing people problems. My roommate is on the same rom as I am but beta 14 worked well for him whereas I had touch screen issue. I raised a support ticket with OPO. They asked me to take it to service center to repair/replace it.

I am now on official cm12 nightlies with beta15. Unresponsive touch issue is gone but I still cant type fast in keyboard
[ONE Original Android Development] chineel:
It works fine till I had not installed any theme and enabled it for first time.

after that it is not remained enabled.
[ONE Original Android Development] WhiteHartMart:
No theme here and it still happened. Seems to be a common problem with any custom kernel on the 08/03 nightly. I'll stick with stock kernel just for now until the issue gets resolved :)

Brought to you by a CM12 Lollipopped OnePlus One :)
[ONE Original Android Development] dud3me:
Strange. For me it's auto disabling as well. Seemed to work fine at the beginning but then just stopped
[ONE Original Android Development] theelle:
[MENTION=947981]Lord Boeffla[/MENTION] for me dttw is autodisabling in options, but still works. I'm On last nightly and beta 15....
[ONE Original Android Development] dud3me:
Does it work well, though? It does for me as well if I tap it 10+ times
[ONE Original Android Development] theelle:
Works very well!
[ONE Original Android Development] fjsferreira:
I'm having same problems with dt2w on euphoria. I know euphoria is not supported but at least I know it's kernel related now. Dt2w disables itself in settings and doesn't work at all in euphoria :(
[ONE Original Android Development] Fenvarien:
I use and recommend the kernel's options "swipe to wake" and "swipe capac. buttons to sleep". I've never missed D2tw... ;) You find these options in the Boeffla-Config app in the section "display and led".
[ONE Original Android Development] andip71:
Is it kernel related?

Aha. I would disagree completely as it works flawlessly here with latest nightly.

Dttw is 1 year old functionality which did not change since cm11. At least not in the kernels.

Andi
[ONE Original Android Development] gondsman:
People with issues using dt2w could have touchscreen issues with the latest firmware. When my phone was on 33R I had every kind of touchscreen ghost touches and it made dt2w unusable (I had to tap 10 times in a row). With more recent firmwares, it works well for me.
[ONE Original Android Development] fjsferreira:
I don't thinks it's kernel related but settings of the kernel related. In latest Euphoria build, with AK, we can force dt2w with synapse, and dt2w then works even if the ROM is still disabling the option in Screen settings.

With Boeffla config, while there is swipe to wake options, there isn't a dt2w option to force it, so it doesn't work :(

Damn, I miss my Boeffla. Euphoria is amazing, but AK, with it's buggy sound control, doesn't cut it for me.
[ONE Original Android Development] izi975:
I did a quick test and set Boeffla ro run permissive. Now the dttw sticks. Im using lateat Euphoria and latest Boeffla.
[ONE Original Android Development] kalpik:
[MENTION=4593553]Mahdi786[/MENTION] said something about picking up latest selinux changes from CM in the kernel to have DT2W working. So it does seem to be something missing on the kernel side.
[ONE Original Android Development] fjsferreira:
Confirmed working, thanks man! :D
[ONE Original Android Development] andip71:
There is only one patch missing in my kernel, which is irrelevant because it is a pure clean up patch.

But these changes are typically in the ramdisk, so I will refresh my kernel later in a few hours with it [emoji2]

It's anyways time for a quick maintenance update.

Andi
[ONE Original Android Development] kunal1540:
Thanx andi for such a brilliant kernel..

BlissPop rom with beta 15..

Just loving it..

I still use your kernel on my old s3 running like a beast still...

Thanx again...

Press thanx if i helped you in anyway...
[ONE Original Android Development] nokia_16:
Is it possible for you to share complete kernel setting? Also which date bliss pop u r running?:confused:
[ONE Original Android Development] andip71:
CM12 beta16

Hi guys,

I promised a few hours before, so here we go:

CM12 kernel update to version 3.0-beta16, but it is only a maintenance update to keep the kernel on latest CM code.

Version 3.0-beta16

09.03.2015

Update: Updated with latest 2 official CM kernel commits as of 09.03.15

Update: Ramdisk updated to official nightly of 08.03.15

Enjoy

Andi
[ONE Original Android Development] WhiteHartMart:
Thank you - installed and dt2w working like a charm again.

Happy again now :)

Brought to you by a CM12 Lollipopped OnePlus One :)