yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] ashwin.kj:
Thank you for the quick response. My bad, I forgot to mention I am on CM.

Just curious, why is the kernel different for COS and CM even with anykernel?
[ONE Original Android Development] andip71:
Source codes are not 100% the same.

COS has some features CM does not have etc.

As my objective is "close to stock", I do not want to have broken functionalities just for having one base code. I rather maintain two repos and can be sure everything is fine.

Andi
[ONE Original Android Development] ashwin.kj:
Definitely going to try and will report back. Thank you for the kernel and the clarification.
[ONE Original Android Development] hellcat50:
f2fs works fine with this kernel, but on COS it makes some problems.
[ONE Original Android Development] andip71:
What exactly do you mean?

Thanks

Andi
[ONE Original Android Development] hellcat50:
I mean the rom itself. For e.g. long time exposure crashes the cos camera app. I always flash the cos camera app on other rom's as well an what i have noticed is as long as you have f2fs and the rom fully supports it the camera app just works fine. (tugapower, jgcaap cm13, temasek)
[ONE Original Android Development] chenrp:
touch not working when using a running arm case.

in the previous kernel it worked...(can't remmember the version)

any solution?

update:

the touch does work, but i can't wake the phone with double tap while the phone in the armpband case.

edit:

it is not kernel related, the proximity sensor is covered. armband issue. I probably changed the option of accidental wake up.
[ONE Original Android Development] andip71:
Interesting and very special use case :)

Andi
[ONE Original Android Development] dhavietz:
I'm using CM13 Jgcaap ROM.

Using this kernel v.5.1 or v5.2 resulting camera error/cannot connect camera.
[ONE Original Android Development] Renosh:
Reflash ROM then flash cafcam CM13 version from this thread

http://xdaforums.com/showthread.php?t=2910357

Boeffla doesn't officially support color OS based ROMs but Zanezam has a compatible build
[ONE Original Android Development] andip71:
What would you expect with that combination?

It cannot work as my kernel supports standard camera only, of course.

Andi
[ONE Original Android Development] I3ig Al:
Hey Boeffla, Thank you for your work, I havent messed with kernals since my nexus 4 and Franco, so its really nice to see a similar kernal/app combo that makes things easy to tinker with.

I have been trying for months to get an Xbox One controller working with my OPO and so far have had zero success. I have tried modifying my keylayout files, different versions of CM from 11 to present, stock from beginning to present, and nothing has worked.

When I connect a controller with OTG, it will vibrate randomly in duration and period between vibration, but no prompt will come up for USB input. Even the app Moonlight which has a specially coded driver does not function, it will see my controller and prompt for USB input but then it disconnects.

With your kernel flashed and the xbox module enabled it is no different. Strangest of all, using the app USB Device Info, every single time I connect the controller and scan for info, it gives a new Product ID under the Android tab, but the proper/true Product ID under the Linux tab. I have NO idea why this happens or what it means.

I am not a Linux user so I really don't know what else I can do from here short of learning everything and integrating the newest XPad.c driver from the main linux git. Is there anything you can suggest I try or that you could do to help me on this?
[ONE Original Android Development] andip71:
Unfortunately I cannot be of any help.

I do not own a xbox nor a controller. So I just enabled the kernel modue, but never testet it. It was working in previous devices kernels however.

So I am sorry, I cannot do anything.

I could just remove the module when it does not work.

Andi
[ONE Original Android Development] andip71:
Hi alll,

for some it maybe a sad day today, as I just switched to me new OP3 as my new daily driver.

It does not mean I will abandon the OPO kernels, but do not expect new fancy features anymore. This would not be realistic.

However, I continue maintaining the OPO still of course. At least it is a device that always supported me in the last years without any issues. So I am still in love with my OPO.

Andi
[ONE Original Android Development] I3ig Al:
thats unfortunate but I totally understand, thanks for reading/replying. may I ask, does the CM source include the latest Xpad.c from the linux master? I will link here, but its latest commit was Jul 27 and the text specifically lists the controller I am attempting to use. if possible would you be willing to pull it and build into your next release?

https://github.com/torvalds/linux/blob/master/drivers/input/joystick/xpad.c
[ONE Original Android Development] suaverc118:
Will you be working on a kernel for 7.0 ROMs eventually for the OPO?? Also I'm trying to decide between the OP3 and axon pro. Totally different phones, but specs are pretty good except for it only having 2 gigs of ram and not any dev support as of now
[ONE Original Android Development] andip71:
Hm... this is a good question. I have not yet decided. Depends on how good it runs, I would say.

For sure I will drop Galaxy S3 and S5 for Android 7.

For the OPO I will think about it when the time has come.

Andi
[ONE Original Android Development] hellcat50:
rip galaxy s3 :crying:
[ONE Original Android Development] DjDiabolik:
hi boys... i have a question:

i have upgraded my supersu to last 2.77... i flash the zip from twrp also i ever do but when i restart my opo to system i look and i have found a old beta version of kernel.

Before that i have the beta7 correctly installed.... and after supersu upgrading i have found installed back the beta5 and i need to reflash again the beta7 from config app.

Because there's appening this? how i can "fix" this?
[ONE Original Android Development] hellcat50:
this is supersu restoring an old backup. this is an ongoing issue.
[ONE Original Android Development] kryshnakishore:
Irrespective of app updates, atleast kernal will be updated based on latest releases. Thanks Andi for support till now. Missing
[ONE Original Android Development] andip71:
This is odd supersu behaviour.

I always recommend the following sequence:

- flash CM

- flash supersu

- flash boeffla

...and not supersu after Boeffla as supersu detects something has been changed and then restores an old kernel version.

BTW, once again: If you are on cm, there is even no need to use supersu as the inbuilt superuser does fine.

Yes, it is.

Andi
[ONE Original Android Development] andip71:
(Do NOT ask for ETA...)
[ONE Original Android Development] Nichie:
Wrong thread [emoji13]
[ONE Original Android Development] MMWolverine:
Time to start scraping some cash together for a new device...
[ONE Original Android Development] hellcat50:
me too, as soon as i sold my opo i will be getting a op3
[ONE Original Android Development] andip71:
Nope, fully intentional in this thread :)

Very wise idea.

Andi
[ONE Original Android Development] DjDiabolik:
And i can/we can avoid this?

i understand... every time i need to update supersu i need to use this order and need to use the full zip (like dirty flash) of cos13.x?
[ONE Original Android Development] chenrp:
why move from opo to op3? is it worth the money? i don't think so...

for me, battery time and versatile is top priority.
[ONE Original Android Development] hellcat50:
so i will be leaving the opo. today i sucessfully sold it and bought a op3. it was a great time
[ONE Original Android Development] andip71:
Hm. Maybe. I am not using SuperSu a lot myself.

But usually the in-the-fly update of SuperSu when opening the app works without issues.

Oh, it is so much a better phone. I don't regret the move at all.

Welcome to the op3.

If interested, I plan to release my kernels soon for it.

Andi
[ONE Original Android Development] DjDiabolik:
Yeah i know... otherwise i have received the 2.78 stable from play store and i have upgrade my binary directly from supersu app and the kernel it's remain untouched.

It's possibly this is a "issue" caused by twrp or caused by zip of supersu.... i have make same question on supersu thread also... if i obtain some info about this i try to report here :)
[ONE Original Android Development] andip71:
It is by design.

If supersu detects a kernel is installed which was already modified in a way in the ramdisk, it tries to restore previous kernel (assuming it was a stock kernel).

To start with an as fresh as possible basis.

It is not a very sophisticated approach, hence people keep on having issues.

Andi
[ONE Original Android Development] silvagroup:
Awesome, great to hear there is now a need for your kernel on the OP 3!!!!!! Have been waiting for awhile now so looking froward to it !!!! Will you still be updating the OPO also?
[ONE Original Android Development] andip71:
The kernel is out already.

And as for future updates, there is a roadmap on the site:

http://www.boeffla.de/index.php/info/kernel-status-roadmap

Andi
[ONE Original Android Development] silvagroup:
Wonderful, great news all around !!!! And again thanks for your great work !!!!!
[ONE Original Android Development] chenrp:
will this kernel development for the oneplus one stop? is it already since u moved to oneplus 3?
[ONE Original Android Development] ZaneZam:
http://www.boeffla.de/index.php/info/kernel-status-roadmap ;)
[ONE Original Android Development] andip71:
Update to CM13 kernel:

Version 5.1-beta6

09.09.2016

Update: Updated with latest official CM kernel commits as of 09.09.16, 8am CET

Change: Improved compatibility with SuperSu

Change: Default entropies changed from 128/256 to 64/128 again, as this is now configurable by users anyways

Change: Support Boeffla-Config app with entropy configuration

Change: Improvements to anykernel script (credits to Osm0sis)

Change: Controller cleanup

Change: Build script improvements

Enjoy

Andi
[ONE Original Android Development] bebybee:
Where i can get ur lastest version kernel ?
[ONE Original Android Development] andip71:
This is clearly stated in OP.

You can also download and flash directly in Boeffla-Config.

Andi
[ONE Original Android Development] Fevves:
Or... If you have the nandroid (twrp) backup of your original boot partition (your fault if you don't have it), just restore that one alone (as it restores the original ramdisk without supersu poking) and flash away in sequence. Can't go wrong here...

For me the problem rose up if I had supesu before boeffla at all, which on the other hand would leave me without root if I would root again after the boeffla kernel, I would lose the kernel after flashing supersu libs via twrp (waking up with the previous kernel and/or version).... Solved with the original boot partition.
[ONE Original Android Development] bebybee:
Thanks dude

Sorry for noob question
[ONE Original Android Development] ovaxivanov:
KK Kernel for Bootloader 41.18

Hello Sir, Lord Boeffla.

I would like to ask you, if you can, and of course, if you have time can you help us?

http://xdaforums.com/moto-g/help/kk-kernel-bootloader-41-18-t3060538

Can you make your Kernel with Bootloader 41.18 compliant?

I like, very mutch, CM11 (MahdiROM) + your kernel, but i have screen flickering (https://www.youtube.com/watch?v=_vSN1dcscMs)

on my oneplus one with any KK Rom, but not with LP or MM.

I like KK for good battery. Dont like LP or MM.

Thank you for your time and sorry if i bother you.

(sorry for my bad english)
[ONE Original Android Development] rolear8:
On your page nor on your app which redirect me to your page to download the latest kernel is showing the latest version. The newest one is from August 16, what am I missing?
[ONE Original Android Development] DjDiabolik:
i can also wait for next ota/next full zip...

otherwise on recently released of cos13.1.2 i have used that exact order:

1) full zip

2) boeffla kernel 5.2beta5 (beta 6 and 7 it's released on next days)

3) supersu 2.76 stable zip

After some days whit config app i upgraded to 5.2 beta 6 and beta 7..... instead the 2.77 beta of supersu it's been released and i have flash it by twrp and on reboot i have advice the 5.2 beta 5 it's been restored and on log nothing it's been reported.

The only things i need to do it's reuse the config app to update again to 5.2 beta 7.

On next days the 2.78 stable of supersu it's be released on goole play... i have received the update but apparently the binary it's not changed infact this time the kernel it's remained untoched whitout any restore....

I don't have idea how it's the problem... i thinks i have ever use correct procedure for installing the update of cos....
[ONE Original Android Development] 9282gkg:
What is safest and quick charge value for ac charging current and USB charging current?
[ONE Original Android Development] thedoctor.gz:
0 = stock logic
[ONE Original Android Development] Fevves:
Like I was writing - you can restore your original boot partition (assumed you made the twrp backup before tinkering with kernel and supersu) and then flash the latest kernel and afterwards the supersu libs, then power up the phone and all of it will stick.
[ONE Original Android Development] DjDiabolik:
yeah... i understand that :) but i don't have a recently twrp backup for the moment :)

i can for example extract it from full zip?

And now.. if a next supersu released how order i can use for use the zip?

Original boot + last kernel and finally the updated supersu zip it's right?
[ONE Original Android Development] Nichie:
You don't need to do that. Just flash latest supersu then flash latest boeffla kernel

*edit* actually if you are already on the latest kernel, flashing supersu shouldn't remove the kernel but if it does, just flash boeffla kernel over it again and root will remain.
[ONE Original Android Development] andip71:
I have to say, I am not changing anything in the kernel to make stuff compatible with old, outdated (and insecure) Android versions. Please understand this is not a priority for me.

Don't know what you are missing? Where did you try to download it?

The only valid way is: www.boeffla.de and then on downloads.

This is the wrong sequence. Install stock kernel or rom, then supersu, then boeffla.

http://boeffla.de/index.php/support/installation-how-to

Andi
[ONE Original Android Development] Fevves:
Strangely, for me it was not working and it was looping into supersu disabling boeffla kernel & restoring the original COS kernel, while on successive boeffla kernel flash I would lose the root. Fixed with original boot partition recovery and then flashing the kernel (yes, I did all the system, data, cache and art cleaning prior to it all and prior to flashing the clean COS 13.1.2 zip), then flashing the kernel and then supersu is yielding an OK result for me.

Flashed cm-13.1.2-ZNH2KAS3P0-bacon-signed.zip from COS

Flashed boeffla-kernel-5.2-beta7-COS13.1-bacon-anykernel.recovery.zip from your official DL repo.

Flashed BETA-SuperSU-v2.77-20160827190633.zip from Chainfire

Updated Supersu from the store and libs afterwards, the boeffla kernel persisted and is OK.

Not trying to contradict anyone, just stating what is working just fine for me ;)
[ONE Original Android Development] DjDiabolik:
Azz............ at this point it's possibly if a new supersu zip (for stable i can use the google play store upgrade.... i suppose a new beta it's releasrd) has been relased at this point i can use this sequence ?

1) Flash stock kernel

2) Flash newest zip of supersu

3) Flash the last version of boeffla

In this sequence i thinks no restore or similar........... wait for next updated :)

Ah.... about 5.2beta7:

About the possibly of "end" on developing on opo..... you don't thinks it's time to released a 5.2 stable ?
[ONE Original Android Development] andip71:
The development on opo is not ended as such. I am just not adding new features.

But yes, I will release stable kernels soon for it.

Andi
[ONE Original Android Development] DjDiabolik:
infact i have put phrase end inside "" :)
[ONE Original Android Development] andip71:
Attention - Prior notice

================================

All, please be aware, I will remove two governors from all my kernels for the msm8974 platform (OnePlus One, OnePlus X and Galaxy S5) with the next updates.

The affected governors are slim and intellimm.

The reason is: Both contribute around 5% to the idle cpu utilization (when screen on) - even when they are not actively used.

Instead of having an average of around 10-11% idle cpu load, these governors cause an average idle load of around 20%.

After I pinpointed the two governors as the root cause, I am of the opinion this is not an acceptable behaviour and not meeting my quality criteria.

So - if you use these governors or profiles that use these governors, be aware you need to move on to one of the many supported other governors asap.

Thanks to XDA user fbs for the report which made me investigate this.

And thanks to the user base for supporting this maybe unpopular but neccessary step to improve kernel quality.

Andi
[ONE Original Android Development] chenrp:
very strange as these governors are used in multiple device and i haven't heard this issue...

but, if you did an investigation and come to this conclusion, i am glad we have a developer like you!

thanks!
[ONE Original Android Development] andip71:
I guess not many investigate in depth the idle load of stock vanilla kernels vs custom kernels.

It was also a surprise for you.

Look at the attached thread for details, you can really measure it easily on your own:

http://xdaforums.com/galaxy-s5/general/cpu-load-custom-cm13-kernels-t3460972

Andi
[ONE Original Android Development] andip71:
Stable releases for CM13 and COS13 are out now.

COS13.1 -- Version

5.2 stable

16.09.2016

Change: Removed slim and intellimm governors (read here about it)

Change: Build script improvements

CM13.0 -- Version

5.2 stable

16.09.2016

Change: Removed slim and intellimm governors (read here about it)

Change: Build script improvements

Enjoy

Andi
[ONE Original Android Development] pijas82:
Time to flash , thanks master

O win 1h sot with this kernel, stock settings, and more fluidity
[ONE Original Android Development] portugt30:
Your kernel is to much bugy , to much time to boot ,some times freez the screen and the go's off (not reboot) just turn off,........and other things ,i only like your kernel for the quick charge and the sound control, now im on stock krenel, miss the older krenel that tou make on kitkat, sorry for the bad rate and the bad englis lol?
[ONE Original Android Development] andip71:
Lol. You made my day :)

Everything you report is not the case here and with hundreds of other users.

But I am happy for you to use stock or another kernel.

Andi
[ONE Original Android Development] JG:
I always love reading posts like this,Someone complaining about what they dont like and making the comment of how they are nolonger using it .Makes you wonder why they even bothered making the post in the first place.

Just for the record [MENTION=947981]Lord Boeffla[/MENTION] Kernels never disappoint and I have not experienced any of these issues.
[ONE Original Android Development] pijas82:
Hi, who is better boeefla tweeks or mattiadj tweeks?

I search about... But...

If i changed profiles , dont see in app changes, like governor, cpu....

Its normal?
[ONE Original Android Development] andip71:
Yes, normal.

The system tweaks only change parameters of the vm.

I recommend to not use any on modern phones (it was more for the Galaxy s3 long way back).

Andi
[ONE Original Android Development] DjDiabolik:
Little OT my friends:

Now i can't but tomorrow i try to flash the newest supersu 2.78 sr1 beta :)

I have extracted boot.img from latest full zip of cos... i have download the 5.2 stable and latest supersu.

i flash in correct order..... boot.img -> supersu -> boeffla 5.2.... if i have obtain the restore issue i try to give some info...

Wait some my feedback :)
[ONE Original Android Development] DjDiabolik:
Stupid question:

What's it a Oneplus msm device? opo it's not msm? the recent mic feature on config app it's settable from?
[ONE Original Android Development] Leicxan:
OPO is msm8974, so it's a msm device.

But the mic feature it's for oneplus 2.
[ONE Original Android Development] andip71:
msm... means a Snapdragon device. MSM is the platform name for Qualcomm Snapdragon.

OnePlus One kernels do not have this enabled, only OP2 and OP3. But even on those devices this is completely experimental and untested.

So you won't miss anything.

Andi
[ONE Original Android Development] DjDiabolik:
i want to personally thanks both for great explanation :)
[ONE Original Android Development] andip71:
You are very welcome.

People asking in a nice and proper way always get comprehensive answers :)

Have a nice day

Andi
[ONE Original Android Development] kryshnakishore:
Using opo with RR rom. Does kernal settings has affect on wifi connection? I am using battery extreme profile. Using such battery saving profiles affect WiFi connection?
[ONE Original Android Development] andip71:
No, wifi is not affected in any way by kernel profiles.

Not in my kernel at least.

Andi
[ONE Original Android Development] Pezmet:
It does not affect WiFi only cpu and gpu speeds and the guvernator as far as I know
[ONE Original Android Development] Leicxan:
Hi Lord,

Can you take a look about KCAL configuration? Because i turn KCAL switcher to off, after reboot it turn on again, I saw you changed it on op2, so any chance on opo?

Many Thanks,
[ONE Original Android Development] andip71:
This is not a reason to look into it, because if that happens something is wrong.

When I turn it off, reboot, it sticks turned off.

You might have another app that is switching it on afterwards, or a script, or...

I cannot say what it is without seeing your phone.

PS: the change is in the pipeline, but it really has nothing to do with your issue. Something else is switching it...

Andi
[ONE Original Android Development] andip71:
Boeffla-Universe:

I will be quiet now for the rest of the week, being on holidays at the North-East coast of Germany.

Will be back next Monday.

Have a good time.

Andi
[ONE Original Android Development] KenjiHannya:
Boeffla Kernel work fine on Tesla N
[ONE Original Android Development] suaverc118:
Wow, so a cm13 kernel will work on this?! I've been missing me some boeffla kernel ever since I switched to 14!
[ONE Original Android Development] KenjiHannya:
Work good
[ONE Original Android Development] fjsferreira:
Lord Boeffla, again, great release, everything seems fine and dandy.

I only have one feature suggestion, in sound control, could you add more specific parameters? For example, in ear speaker for increasing in call volume, or headphone volumes for when in call (headphone volume by itself doens't affect headphone volume when in a call)...

Thank you!
[ONE Original Android Development] Mash87:
nice to hear. Looking forward to use our great kernel on a CM12 build. Appreciate your hard work!
[ONE Original Android Development] andip71:
Do you know someone who implemented this already?

Or can you get me a technical documentation on the WDC9320 audio chip?

No seriously... I am not sure this can be done as I do not have any documentation on the sound chip. Reverse engineering everything takes time and sometimes is even impossible.

I will look into the whole sound topic again after I am finished with first cm12 kernel beta.

Andi
[ONE Original Android Development] andip71:
Okies, as you can see... 3.0-alpha1 running on my phone already on CM12 (build of 16.11.14 by bpear96).

So far so good for an alpha rom and kernel, some minor glitches here and there, but nothing really major so far.

I will this evening upgrade the rom to todays build and check how this goes.

If all goes well, I might ask for a few brave testers by tomorrow which are eager to give it a try.

Cheers

Andi
[ONE Original Android Development] gianton:
Great news, glad to be a beta tester mate.