yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] guillermorojaz:
cm-13.1-ZNH2KAS1KN-bacon-signed.zip

https://forums.oneplus.net/threads/mirrors-for-official-cyanogen-roms-ota-updates.141825/

https://www.androidfilehost.com/?fid=24591000424939817

Edited and added.

https://cyngn.com/support
[ONE Original Android Development] Hallux_:
Installed with latest TWRP over 13 no issues at all.
[ONE Original Android Development] guillermorojaz:
I'm downloading the file and battery charging of the oppo.

I still do not happen.

I'm with the TWRP TWRP-3.0.0-0-bacon-20160309.
[ONE Original Android Development] hellcat50:
http://elementalx.org/the-truth-about-kernels-and-battery-life

:good::good::good:
[ONE Original Android Development] hellcat50:
Hey Andi,

this weird bug happened today.

Rebooted and still the same. What should I do?
[ONE Original Android Development] andip71:
Uninstall app and install again from the apk (do not restore via Titanium backup etc).

Rom version?

Andi
[ONE Original Android Development] hellcat50:
Uninstalled, deleted boeffla data folder, restarted, still the same. I have the latest cm13 nightly from today.

Can't find any errors with catlog
[ONE Original Android Development] andip71:
Then I am running out of ideas.

I have the same setup and it is working fine.

Send me a recent bc.log file by mail.

What root method do you use, internal root or supersu?

Andi
[ONE Original Android Development] hellcat50:
I now know why. It's because SuperSU 2.74 I used before.

What I tried:

Re-flashed boeffla kernel without SuperSU - worked again

Then flashed SuperSU - doesn't work

But the strange thing is that it worked every time when I used temasek ROM. No problems there. + when I flashed the ROM it worked the first time :confused:

Edit: after deleting the SuperSU app and reflashed supersu, the first boot works. But after that - doesn't work. But root seems to be fine though
[ONE Original Android Development] andip71:
Supersu on CM is quite a pain in the a***

I know I had to do some changes in the past to make it work.

Seems I have to look into that one day, however I never used supersu myself on CM.

Means: can take some time.

Andi
[ONE Original Android Development] andip71:
Hm, this is weird really.

Just for you I flashed supersu 2.74 as well (systemless mode).

App works, rebooted, app works, opened many times, app works...

No idea why it is different for you.

Andi
[ONE Original Android Development] Renosh:
[MENTION=947981]Lord Boeffla[/MENTION]

Did anything change in COS13.1 related to charging in the kernel? Just fastboot flashed the latest image and getting some slow charging at the moment. I know I can flash your kernel and change that so not really asking for a fix from you, just curious if something's different

Oneplus 3 is looking beastly [emoji7]
[ONE Original Android Development] andip71:
I need to look that up, but believe they changed things in the charging driver, yes.

And I believe I ported the previous driver back in my kernel due to that. But I am not sure without looking into my repo again.

Andi
[ONE Original Android Development] hellcat50:
I deleted dalvik cache, and it seems to fixed the issue. don't know what went wrong there :confused:
[ONE Original Android Development] Renosh:
[MENTION=947981]Lord Boeffla[/MENTION]

Can't find the internal supersuser script, search isn't giving me useful results and can't find the location on the website.

I'd appreciate a link please

Edit:

Found it after searching manually

http://xdaforums.com/showpost.php?p=66520038&postcount=8323
[ONE Original Android Development] Mydnytefantasy89:
Dang, Boeffla. I'd hate to see you go, your kernels are kind of legendary. I was excited when I saw I could get it on this phone, it was my instant pick. I've been more than pleased with the results, it's great work. That said, I hope you do find that balance, I would gladly accept slower updates :D I currently have a little bit of free time, so I could help out if you needed, like posting links in the forums for you or something. That way alls you have to do is upload it. Idk, just a thought. Good luck on finding that balance!
[ONE Original Android Development] chenrp:
Good to hear that you won't stop the development. We all have to contribute and assist you in support and faq that other users ask.
[ONE Original Android Development] hellcat50:
You could hire some mods who makes the changes to the thread. You also could hire some maintainers to keep kernels up to date (like for the galaxy s3) and manage your website.

But well, you probably don't discuss this thing anymore.

Then it is how it is.

I know know you since 2013 and I now look back I smile because:

"Don't be sad because it's gone. Smile because it happened."
[ONE Original Android Development] andip71:
... and nothing is gone.

Kernels will be there, just slower updated, less support and active involvement from my side. That is all.

People that used my kernels nowadays will be able to do in future as well. Less updates, slower fixing of bugs and much slower introduction of new features.

But - I am not gone :) Just shifting to procedures that make my life better again.

Andi
[ONE Original Android Development] hellcat50:
Just wanted to post it here, because it always helps me when I've lost something and can probably help someone too :)
[ONE Original Android Development] chenrp:
BUG found: just flashed the latest temasek rom and with boeffla i get boot looped.

Without, no issue. There are many changes in the rom... Maybe incompatibility.

---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------

BUG found: just flashed the latest temasek rom and with boeffla i get boot looped.

Without, no issue. There are many changes in the rom... Maybe incompatibility.
[ONE Original Android Development] andip71:
First message to be ignored. You should know why.

Temasek = custom rom = I do not care.

Andi
[ONE Original Android Development] inzaghi89:
https://forums.oneplus.net/threads/oneplus-3-kernel-source-released-o.450121/ I'm not pushing on you Andi, only want to let you know about the source for OP3 :)
[ONE Original Android Development] chenrp:
​

Cool. Just thought it is in all the cm nightly
[ONE Original Android Development] andip71:
No, it is not.
[ONE Original Android Development] Fenvarien:
Thanks for all your great work, Andi! I will always be happy and thankful about a new kernel by you, but take your time. Real life and family always have the highest priority!
[ONE Original Android Development] Dhairya:
i mean the new kernel update for cos 13 is awsm but a bit high battery drain with 10mins gaming lost 15% battery ! And from 100% full charge it came to 65% within 2 hour with just whatsapp!
[ONE Original Android Development] andip71:
Can't comment on gaming.

65% after 2 hours is bad. I usually have around 80 still.

But anyways, this is not a kernel topic. Kernel influence on battery life is minor.

Andi
[ONE Original Android Development] chenrp:
Boeffla,

Off topic question :

are you using cm13.1 nightly? Do you suggest any custom rom?
[ONE Original Android Development] Renosh:
He's mentioned it a couple times but he has 2 OPO (CM13 and COS13.1). He doesn't use custom ROMs
[ONE Original Android Development] chenrp:
anyone uses headphones with controls? if i have headphones and the controls are not working, is it kernel or rom related issue?
[ONE Original Android Development] Mydnytefantasy89:
This isn't exactly the place to ask that. That said, if it has volume buttons, it most likely won't work for Android in general. It's just something that's kind of been accepted. The center button for pause/play should still work, but that's it. Next time, find the right thread though. Things are starting to change in this specific thread, so questions like this may not even be looked at a second time. Not trying to be rude, BTW, just speaking the truth. It comes across much meaner in text form.
[ONE Original Android Development] chenrp:
i think you are mistaking.

a lot of users report to have controls working in one rom and when upgrading to a new rom(witch includes a new kernel) the volume keys won't work.

i wanted to know if it is rom or kernel related.

thanks
[ONE Original Android Development] hellcat50:
I think temasek is based on stable branches, that's because it doesn't work
[ONE Original Android Development] Mydnytefantasy89:
I could be, but then I feel that the controls on my headphones would have worked over the past ~6 ROMs, ~4 kernels, and 2 phones, at least once. Kinda like the saying "a broken clock is still right twice a day". I've researched it a ton, and there aren't many options for getting those controls working if they never worked in the first place. Some features like that will require the stock ROM, like the two finger swipe for pause/play on OPO didn't work on cm, but once I got onto cos it worked fine.
[ONE Original Android Development] andip71:
Kernel updates:

COS13.1 -- Version

5.1-beta2

15.06.2015

Note: You have to update to COS13.1 version ZNH2KAS1KN to use this kernel version !!

Note: You have to use Boeffla-Config version 2.2.50 in order to use all functionality !!

New: Doze control - in latest Boeffla-Config, you can switch Doze completely on or off (I do not like Doze as it sometimes delays notifications, so I switch it off) at overview page

Change: Userspace processes are prohibited now to change CPU minimum frequencies, this means:

the CM13 typical boost to 1574 MHz frequency most of the time is removed (this rendered cpu-boost useless + consumed significant battery)

now cpu-boost is used again as only booster (as previously in Android L)

if you feel UI less smooth than before, then this is the reason. If that is disturbing for you, configure cpu-boost to 1574 MHz frequency and boost duration to 1500 ms

Update: selinux policy taken from official COS debuggable images which came out recently - improved compatibility

Change: Kernel initialisation script fixes

CM13 -- Version 5.1-beta26

16.06.2016

Note: You have to use Boeffla-Config version 2.2.50 in order to use all functionality !!

New: Doze control - in latest Boeffla-Config, you can switch Doze completely on or off (I do not like Doze as it sometimes delays notifications, so I switch it off) at overview page

Change: Userspace processes are prohibited now to change CPU minimum frequencies, this means:

the CM13 typical boost to 1574 MHz frequency most of the time is removed (this rendered cpu-boost useless + consumed significant battery)

now cpu-boost is used again as only booster (as previously in Android L)

if you feel UI less smooth than before, then this is the reason. If that is disturbing for you, configure cpu-boost to 1574 MHz frequency and boost duration to 1500 ms

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

Update: Ramdisk of official CM13.0 build of 16.06.16

Change: Kernel initialisation script fixes
[ONE Original Android Development] chenrp:
thanks!

Doze control is great but it won't delay all of your notifications... if you are using ClashOfClans it will be a good idea to switch it off so you get a notification.

anyways, good feature!
[ONE Original Android Development] KaszasM:
as u answered there are some "dozeincompatble" apps still(idontuseanygame) , actually its never gonna work always until "doze"as new feature dosnt get" stable" the app devs dont give a sh..t, maybe we should just make a new thread to follow these apps. anyway i have also some notify delay but set notify to high priority(should baypass doze as i read somewhere) helps also sometimes, or turning batt.opt off on that app, if not you need to turn doze off atm

srry for OT
[ONE Original Android Development] Renosh:
This is most likely a ROM issue. On COS13.1 volume keys skip tracks works sometimes. On CM13 Nightlies, Sultan CM13, Omni etc the feature worked every single time with my headset and the phone.

I have never missed a notification on any ROM with doze on, for Clash of Clans or any of my apps weirdly enough. Do you guys use Titanium Backup?
[ONE Original Android Development] KaszasM:
of course as you too :D but it has nothing to doo with Tibu . this "bug" is just user(apps)or even doze(as newfeature)dpendend , but if your phone SLEEPS well and you got that delay its easy to recognize because you get the notifycations only if you turn the screen ON . :D (and as i say 1 app (viber) works well ,and same time a diffr. app NOT)

10 push ups for me for the OT again :D

anyway we NEVER GONNA FIND THE SOLUTION In that thread so stop spamming :D

pm me and we can make some directed tests ,but thats would be like a kiss for the dead for the community ,and /but eveyone going to experiment(use search tabhopefully ) with hes own roms/apps at home how ever got that delay
[ONE Original Android Development] Dhairya:
well thank u sir ! new update on kernel is pretty awsm wil tell about backup within one day but initial impression is good !
[ONE Original Android Development] Renosh:
What are you talking about?

I was asking a simple question not spamming. Others (other threads) have reported restoring apps like WhatsApp with titanium backup causes issues with receiving messages.
[ONE Original Android Development] andip71:
I can confirm that.

When you e.g. restore WhatsApp from a Titanium Backup, it will not work anymore as the GCM link is broken.

An uninstall and new install from play store (or the apk itself) fixes the issue again.

Andi
[ONE Original Android Development] tonyboy3:
After update the kernel i lost root access. In beta 1 flashing supersu works but now I can't boot! :-S any help on this please?

Last COS 13.1.

Tried: 2.65 stable and 2.74 beta

Flashed the kernel again, but doesnt have root access!
[ONE Original Android Development] Hallux_:
I had the same problem when updating, just flash supersu 2.74 again and everything is smooth as usual. Try flashing supersu after the kernel.
[ONE Original Android Development] Aavion:
Why do you guys flash SuperSU on a CM (based) rom, when you can also use cm's internal solution to obtain root access by just flashing the binary?!
[ONE Original Android Development] andip71:
Absolutely the proposed solution, I never use supersu (it tends to give more and more troubles since Android M).

Andi
[ONE Original Android Development] Aavion:
I'll never understand, why those guys prefer dirty hacks (supersu) over fully integrated solutions...
[ONE Original Android Development] tonyboy3:
Because after flash boeffla the internal solution doesn't work! With stock kernel I doesn't need to flash supersu!!
[ONE Original Android Development] Aavion:
Using COS 13.1 with latest Boeffla Kernel and internal superuser without any problems... Never used any other root method :)

Just need to flash cm's su binary and a debuggable kernel (Boeffla Kernel is debuggable) and then activate root access in dev-settings...
[ONE Original Android Development] tonyboy3:
Because the internal solution doesn't work after flash boeffla
[ONE Original Android Development] Hallux_:
My issue when using internal is that is does not remember which applications were granted permissions after reboot. Do you have any idea on how to solve that?
[ONE Original Android Development] kenboyles72:
SuperSU is not just some dirty hack as you call it. Chainfire, the developer of SuperSU, paved the way in getting root for thousands of phones and is held to the highest respect within the dev community. His work is the gold standard of rooting and other devs have used his work to create their own app versions. The built in root of CM is just a few lines of code to give su rights at a minimum and does not even compare to the versatility and power of SuperSU. This is why ALL apps are developed to work with SuperSU. The only reason SuperSU didn't work so well with CM13 based roms in the beginning, is because of new permissions, security and toybox, which is Google's blame and is now fixed. And just because CM has built in root does not mean that it's fully intergrated.
[ONE Original Android Development] guillermorojaz:
Please excuse this silly question, and previously did :eek:

Where is the COS13.1-eneble-internal-superuser-bacon.zip ??? :confused:

Thankful in advance and apologize again ;)
[ONE Original Android Development] glockman4519:
I just want to thank you for all you do. Your kernels are legendary and just function as they should. I completely agree and understand your decision to "trim the fat" so to speak. Thanks again and latest update is, as usual, perfect.

"Chance Favors the Prepared"
[ONE Original Android Development] Aavion:
You can still use the file provided for COS13 :)
[ONE Original Android Development] atulclassic:
Now that's a gold standard reply

no offense but i like supersu over CM inbuilt root
[ONE Original Android Development] andip71:
Not true. It works perfectly fine, I never use something else.

It works fine.

Never had that. Maybe you use other tweaks or mods that break it.

But it is a question to CM rom developers rather than a kernel thing.

SuperSu was great in the past before Android M.

And it still has it's worth for many stock roms out there.

But on CM there was never the need for it, and on CM internal solution always was better embedded and did not require dirty hacks like e.g. now flashing it again after every kernel update due to systemless-mode.

I use supersu for Samsung Stock and OOS roms, but always internal superuser for CM and COS.

Golden rule, was always serving me well.

But up to you guys of course. Tastes are different.

There is no new version, the previous one for COS13.0 works just fine, the binaries in the zip have not changed.

As said, personal taste. Just the fact is: On CM internal superuser causes much less trouble and work usually.

Andi
[ONE Original Android Development] Renosh:
There is no obvious place to find the superuser zip you posted, I looked at the OP, your site, Twitter and searched the thread but couldn't find it (had to go page by page backwards) so it would be better to put in the OP so people can find it, than stating it hasn't changed.
[ONE Original Android Development] andip71:
It is in the download folder of the kernel.

Should be the most obvious place to be.

Andi
[ONE Original Android Development] iorl_yagami:
I hope that can increase the thermal control
[ONE Original Android Development] chenrp:
Differences between cm13 and cos kernel? Besides the compatibility to the rom.
[ONE Original Android Development] infatality:
Different commits.. Check cynogenmod github.. Cos commits are mainly stable, where else cm commit are somewhat experimental.
[ONE Original Android Development] chenrp:
Thanks! Indeed, cm has a lot of changes and reverts.
[ONE Original Android Development] Paoliz:
To use internal superuser, have I to flash the enabler in download page? (Cos 13.1)

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] maxed4901:
flashed 5.1 beta 2 on bacon COS13.1.

Pleased with the battery so far.. just letting it drain today. Turned on Boeffla sound but bass is too high and not so nice. other than that- zzmove>battery and the core power saving is realy good. Thank you [MENTION=947981]Lord Boeffla[/MENTION]. have been your fan since galaxy note 2. Now COS13.1 is as it should be.
[ONE Original Android Development] Paoliz:
Flashed on Cos 13.1, no problems, amazing.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] hellcat50:
Well, I prefer supersu because:

1. It logs what a app is doing with root

2. simply more control over apps with root access
[ONE Original Android Development] tsiftsism:
Sorry of this post is irrelevant with this kernel, but maybe you can help me.

I just flashed the latest Nightly and the last version of this kernel and since i restored all my apps i found out that whenever my finger reaches the proximity sensor (the area near the front camera) display switches off.

Is anyone can help me with what may the problem be?

Thanks in advance.
[ONE Original Android Development] Naresh Rawat:
I flashed latest beta kernel and stable kernel..but still ma phone won't start up..its sticks on the boot company startup logo. (1+). My opo is running wid latest RR cm13 based ROM.(build20160617).. Some response expected..
[ONE Original Android Development] infatality:
[KERNEL] [Bacon] [COS / CM] Boeffla-Kernel (16-06-2016)

Why can't you guys just read? His kernel only officially support cm13 or cos 13.. And not others roms be it based on cm or forked cm.. [emoji49]
[ONE Original Android Development] chenrp:
Flash boeffla cos kernel. Not cm kernel.

The developer only supports original cm / cos roms.
[ONE Original Android Development] Naresh Rawat:
Dude in the previous builds of boeffla kernels...I did flashed the beta versions of it on ma opo running RR rom..n it worked as smooth as butter. But nowadays it don't support it...y???
[ONE Original Android Development] Renosh:
Something changed in RR to make it incompatible, its not Boeffla's problem. He only officially supports CM13 and COS13. It working before was good but now you'll have to fix it yourself or use another kernel. Not trying to be rude just telling you what he's repeated many times
[ONE Original Android Development] Naresh Rawat:
Thnx dude....?
[ONE Original Android Development] andip71:
Well, Boeffla Sound on oneplus phones does not influence frequency spectrum.

It only affects headphone volumes...

Yes. This zip + my kernel.

Andi
[ONE Original Android Development] andip71:
That was pure luck in the past.

My kernel is for cm and compatible. RR is not fully compatible anymore.

Andi
[ONE Original Android Development] Naresh Rawat:
Thnx for replying me dude....??
[ONE Original Android Development] sohansonu:
I just flashed Paranoid Android 6.0, now to use Boeffla kernel, which version of the kernel should I flash? The CM 13 one?
[ONE Original Android Development] maxed4901:
Geee... i would guess it should if they are cm based then cm based rom.. You may want to ask at a paranoid thread to confirm what base kernel they have.. if CM, then Boeffla CM will/should work unless Lord Boeffla confirms otherwise. If its CAF/No... i dont think so but i think i have seen some one had ported a CAF boeffla? Maybe m mistaken.

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

Thanks [MENTION=947981]Lord Boeffla[/MENTION] for reply. It must be because i raised the volume level to 8!.

Confirmed the internal root work much better!
[ONE Original Android Development] Shattermatter:
Hey! I'm totally new on this and I wanted to give this kernel a try.

So, I've got my OPO with the newest COS 13.1 installed and rooted with SuperSU Beta 2.74.

What's next? Just flash Boeffla-Kernel 5.1 - Beta 2 with TWRP Recovery? Does SuperSU cause any problems?
[ONE Original Android Development] jhn.pheonix:
Just flash the kernel zip in TWRP and you're good to go... SuperSU is known to cause problems in MM..so it's better to use cm internal root.

1+1 NevEr SeTTLe
[ONE Original Android Development] Shattermatter:
Thanks! But where do I find the internal root option in COS 13.1? I can't find them in my developer options.
[ONE Original Android Development] anagramgenius:
You will, if you flash Boeffla-Kernel.
[ONE Original Android Development] Shattermatter:
So there's no need to flash the additional internal superuser enabler script? Just flash Boeffla-Kernel and I'm good to go?
[ONE Original Android Development] Pablo.x:
1st flash boeffla kernel, then flash the internal superuser enabler

Enviado desde mi OnePlus One.
[ONE Original Android Development] atulclassic:
supersu doesn't cause any issues..flash 5.1 beta 2 kernel and then flash supersu zip on top of it..reboot.
[ONE Original Android Development] andip71:
I still don't recommend SuperSu on cm/cos based roms.

Internal superuser is better integrated and causing less issues in average.

Starting with the fact you don't need to reflash it again after a kernel update.

Andi
[ONE Original Android Development] atulclassic:
Is it only me or someone facing more battery drain with 5.1 beta2..reverting to 5.1 beta 1 solves the issue. [MENTION=947981]Lord Boeffla[/MENTION]..is it something related to changes with input boost?