yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] andip71:
Thanks. No idea. It is running just fine for me here. With yesterdays beta, with todays...

And I also have only one more report about this issue on Twitter. No further reports, so it is on the "normal" level.

I can just suggest, as I did not know how you updated:

- redownload the kernel manually again from www.boeffla.de, ensure MD5 checksum is correct

- flash latest nightly again

- then flash the newly downloaded beta4

If that does not help, I cannot be of any help as all is running great here on my side.

Then stick with beta3 for the time being.

Although, the only changes between beta3 and beta4 are these 4 CM commits:

https://github.com/CyanogenMod/android_kernel_oneplus_msm8974/commits/cm-13.0

So it seems one of them is causing your issue. Which is weird enough.

You could also try to flash latest nightly, then boot with the kernel of that nightly first. And afterwards flash Boeffla. Just one last idea.

Well, as said, I cannot guarantee. But I would rate chances extremely high all is fine with that update too.

Andi
[ONE Original Android Development] andip71:
Please note about my upcoming holidays.

http://boeffla.de/index.php/74-vacation-till-05-08-16

Andi
[ONE Original Android Development] ch-vox:
so far so good.

no particular issue with latest COS

thank you

have a nice time, get some rest ! ;)
[ONE Original Android Development] billbuds:
Support CM12.1 ??
[ONE Original Android Development] MMWolverine:
Check EOL Kernel Versions under downloads on boeffla kernel download page. Last stable version for CM12.1 is 4.4.
[ONE Original Android Development] maxed4901:
[MENTION=947981]Lord Boeffla[/MENTION] greed yes... greed in love is good!!! hoping for an update before you go on your well deserved leave.
[ONE Original Android Development] kingsathurthi:
Hi bros, I would like to flash Boeffla kernel in my rom COS 13.1.1 please any one suggest me correct version of kernel to flash... Thanks in advance!!!
[ONE Original Android Development] ch-vox:
http://kernel.boeffla.de/bacon/boeffla-kernel-cms/cm13.1s_download/
[ONE Original Android Development] DjDiabolik:
you have flashed the 5.2beta5 on cos13.1.1 recently released? it's working whitout problems?
[ONE Original Android Development] c_brown93:
I am running 5.2B5 right now on COS 13.1.1 and it is running excellent.
[ONE Original Android Development] ch-vox:
yes & yes
[ONE Original Android Development] kingsathurthi:
Can u say me best kernel settings to increase battery backup
[ONE Original Android Development] 6061361:
to install the latest version of the kernel on the last COS ZNH2KAS2X1 must always flash the stock kernel first, someone could pass the link where to download it?
[ONE Original Android Development] DjDiabolik:
Thanks friends... i prepare all for upgrade tonight :)

You can extract the boot.img from the full rom zip and you can flash it by TWRP or you can also use the full zip for a dirty flash and the kernel it's be replaced whit stock..........
[ONE Original Android Development] Matteo_666:
I can confirm that. It runs smooth and stable, no issues encountered...

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] andip71:
Hi all,

maintenance updates to both COS13.1 and CM13 kernels available now.

COS13.1 -- Version

5.2-beta6

15.08.2015

Note: This kernel version runs best on COS13.1 firmware ZNH2KAS2X1

Update: Updated to latest kernel code for firmware ZNH2KAS2X1

Update: Updated sepolicy and adb deamon from firmware ZNH2KAS2X1

Change: Ported change from CM13 branch to prevent a wakelock held by the kernel when using device encryption

CM13 -- Version 3.1-beta5

15.08.2016

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

Enjoy

Andi
[ONE Original Android Development] chenrp:
cool! good 2 have u back.

but... couldn't find it via app nor your web site...
[ONE Original Android Development] kingsathurthi:
COS13.1-enable-internal-superuser-bacon.zip

What is this file means?
[ONE Original Android Development] JMS74:
You can use the root of Cyanogen OS that's available on the dev setting instead of having to add SuperSU to the os.

That file allows for enabling it on this kernel.

Enviado do meu A0001 através de Tapatalk
[ONE Original Android Development] kalapapa:
To access root in cos13 similar to how it is in cm13
[ONE Original Android Development] andip71:
Hmmmm...

Andi
[ONE Original Android Development] Gawd:
I'm on COS13.1.1

When I flash the latest Kernel beta6, I somehow lose root. I install root again and I lose the kernel(stock kernel restores somehow).
[ONE Original Android Development] Pablo.x:
Look few pages back, Andi said how to update boeffla kernel using SuperSu

Enviado desde mi OnePlus One.
[ONE Original Android Development] CoinCoin88:
[MENTION=947981]Lord Boeffla[/MENTION] : reporting back after a week or so of use using your test build (with merged commit regarding qcrypto wakelock).

The batterye life has drastingly improved. No suspicious kernel wakelock using BBS. I feel like I've had a bit more random reboots that with the stock kernel, but I don't believe it can be related to the commit. I would need to test more extensively using your 'normal' kernel, although I don't see why it would introduce any instability considering the very good feedback it gets. I will do a real clean wipe/upgrade to the latest OTA that was released by the cyanogenOS team, wiping even the internal storage, and then re-encrypt + use your kernel... but overall, I think you can safely keep this commit merged with your release, since it clearly fix an issue in the qcrypto driver.

Hope that helps! I'd be happy to provide any log that you feel would be useful to you.

Thomas
[ONE Original Android Development] Nichie:
If you are using supersu, boot into recovery, flash stock kernel, don't reboot, flash boeffla, don't reboot, flash supersu, reboot, profit??
[ONE Original Android Development] hellcat50:
hey andi i want to test the new cm snapshot which kernel should i use for it?
[ONE Original Android Development] Gawd:
No profit.

Steps I did:

Method 1-

1. Boot to recovery

2. Flash SuperSU

3. Flash kernel

4. Wipe dalvik/cache

Phone boots with Boeffla kernel and no root

Method 2-

1. Boot into recovery

2. Flash kernel

3. Flash SuperSU

4. Wipe dalvik/cache

Phone boot with root but with stock kernel

Method 3(going to try now)-

1. Boot into recovery

2. Flash SuperSU

3. Flash kernel

4. Flash SuperSU again

5. Wipe dalvik/cache

*Results in a few minutes*

**Note that I'm flashing over stock kernel
[ONE Original Android Development] atulclassic:
flash kernel

reboot

flash super su

reboot

profit
[ONE Original Android Development] Gawd:
It boots with stock kernel the second time
[ONE Original Android Development] andip71:
Guys, SuperSu on CM or COS is a pain in the a....

Why are you not using internal CM root and save all that hassle?

I recommended that hundreds of times already.

Because I have no intention to do supersu support here in this thread.

Apart from that, this is what I would do:

- flash CM nightly

- flash supersu

- flash boeffla

Andi
[ONE Original Android Development] atulclassic:
although Lord has provided the solution but this is what i would do

flash stock kernel thru fastboot

reboot

flash boeffla kernel

reboot

flash supersu

reboot
[ONE Original Android Development] Nichie:
Well I did say you have to flash stock kernel first didn't I? Even if you are currently on stock you still have to do it

---------- Post added at 08:12 AM ---------- Previous post was at 08:10 AM ----------

Internal CM root is not systemless so can't use it with some apps especially banking ones ie Android Pay
[ONE Original Android Development] andip71:
True, but for >95% of the users this is not a problem as they do not use Android Pay (so far).

Andi
[ONE Original Android Development] andip71:
Thanks for the info. Meanwhile this commit is even in the official public kernel update I pushed on Monday.

However, you should have ZERO random reboots. If not, something is not correct.

I did not have a random reboot in the past 5-6 months, at least cannot remember one.

But I am not using potentially "dangerous" things like undervolting, overclocking etc. and I use only interactive governor (which is known to be most stable compared to others).

Andi
[ONE Original Android Development] Gawd:
I forgot to mention that the internal root worked. I flashed Boeffla over the stock kernel and set Root to Apps and ADB and it worked.

**ONLY INTERNAL ROOT WORKS ON COS13.1.1 ZNH2KAS2X1 WITH BOEFFLA KERNEL.

Edit- Above text in capital not confirmed yet.
[ONE Original Android Development] CoinCoin88:
I haven't touched anything in the ad-hoc setting app. So undervoltage is out of the way, as well as over/under clocking.

I've been outside of the android game for long now, but if memory serves me right, after a reboot logs are cleared so it's nearly impossible to find out what caused it. Is that still the case ? Otherwise, next time it happens (which is arguably rare enough, but maybe once every 1-2 or 3 weeks?) I'll dump whatever is necessary to investigate the cause.

edit: I believe this is OS-related rather than kernel, but I find the phone to get really hot around the camera even under "normal use". However this is a general feeling I've had since CM13, so I don't believe it has anything to do with the kernel. It also happens with the stock kernel anyway. Not sure if that can be associated with any reboots I've experienced in the past.
[ONE Original Android Development] Nichie:
Nope. Supersu still works
[ONE Original Android Development] andip71:
I would be surprised if it would not, nothing has changed regarding this handling ever.

But as I am not using it, I was not able to confirm myself.

Andi
[ONE Original Android Development] ZaneZam:
eh eh eh.. don't conclude too early especially if it works for others and me, im running cf system-less root w/o issues on ...2X1 rom like on all other versions before that rom.

so now what i do is i ALWAYS flash dirty (the whole rom actually not only the kernel) before boeffla kernel and THEN supersu (stable version) to have a clean base. i didn't analyse exactly but supersu

makes kernel backups which get automatically restored (same idea from chainfire, to have a clean base) if u reflash supersu cf assumes that pure stock ramdisks r used and not already

customized ones like after using boeffla before. so i think that might lead to some troubles (which i also had, a similiar problem which had to do with that and was fixed by lord boeffla some

versions ago! that was a flash sequence problem with sepoilcy file) anyhow since i use that sequence by dirty flashing complete rom (might be the reason?) -> flash boeffla -> supersu (or vice versa, doesn't matter with newer boeffla kernel images) -> other stuff which i dont dare to mention here *g* all is fine and that reproduceable. as sayed i didn't analyse it deeper and it doesn't mean that ur problem gets fixed with that method but u for sure have to revert the big letter statement now, don't u? im currently on my OP3 but i also can send some screenshots in addition a bit later if that is necessary :)
[ONE Original Android Development] Gawd:
"Other stuff"

yeah *cough* xposed *cough * *cough*
[ONE Original Android Development] ZaneZam:
beside of :D

no seriuosly maybe u can try flashing whole rom over and see?
[ONE Original Android Development] Gawd:
I just hopped back dirty flashed the entire ROM(latest COS), then I flashed SuperSU, then Boeffla kernel. Didn't wipe Dalvik/Cache. The phone booted with Boeffla kernel but no root. The same thing that was happening previously. So I flashed the .zip to enable internal root and its working like normal.

Can you please let me know your kernel settings, though?
[ONE Original Android Development] maicasajusta:
Hi, I'm running the last COS 13.1 and in next few hours I'm going to flash the last version of this kernel, the 5.2 beta 6.

One of the reason I'm doin' this, is that some apps, just as secure settings or es file explorer, can't find the root. Now I've read this can be related to the disappear of internal root on cyanogen, so, looking at the files in the download page of boeffla kernel, do you think I need to flash COS13.1-enable-internal-superuser-bacon.zip too, in order to get rid of that issue? Is this zip strictly related to the kernel or it could be flashed even while running stock kernel?

Thanks.
[ONE Original Android Development] CoinCoin88:
It can be flashed regardless of the kernel. If you unpack this zip and look at the updater script, you'll find what it does is :

- remove any possible remnants of supersu

- restore su binary in /system/bin and /system/xbin

- set permissions on these two files

You then need to enable root in the developer options (settings)
[ONE Original Android Development] ela1103:
[MENTION=947981]Lord Boeffla[/MENTION]

Hi iam waiting for One Plus Three Boeffla-Kernel.Is it possible to build Kernel for OP3 Device .If Your Going to Built For OP3.I can Buy OP3 If Else i going to buy OP1 .BecauseI'm a Die-Hard Fan of your Boeffla - Kernel.
[ONE Original Android Development] ZaneZam:
want a suggestion? get a op3 we already have something to test ;)

Well it was worth a try ;) something strange prevents u from getting supersu root.

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[ONE Original Android Development] andip71:
You should start following me on Twitter :D

http://twitter.com/andip71

Then you would know an OP3 kernel is already in work and basically even close to be released.

I am waiting for OnePlus to deliver me my ordered OP3, so I have enough devices to provide good support. But the kernel is pretty much done and in heavy testing.

Andi
[ONE Original Android Development] andip71:
Ok, thinking through everything, I might know a reason when it potentially does not work.

Hm, I could create a test kernel for you to check this. Would you be willing to test it?

Thanks

Andi
[ONE Original Android Development] Nichie:
I'm ok the latest kernel and supersu works. Not sure why it doesn't work for him.

Flash stock kernel, flash boeffla, flash supersu
[ONE Original Android Development] andip71:
Well, it is not that easy. Especially when he had stock kernel already rooted before.

In some cases SuperSu would restore stock kernel when flashed again after Boeffla.

Yes, I find this SuperSu behaviour completely mad, but it is the supersu design.

So I changed my kernel to detect when the phone is rooted already with systemless supersu and in this case it would not flash some parts which could potentially break it.

Systemless root is really a pain :)

But there is room to improve, hence I did the test kernel.

Forgot to tell: If you are up to a quick test, let me know. I would be grateful for the results (I cannot test myself, I have no COS13.1 running with Supersu here)

Andi
[ONE Original Android Development] Nichie:
What happened with mine was that even though I was already on stock kernel, I still had to flash stock kernel first

Sure! I'll be game to test it out
[ONE Original Android Development] andip71:
Great, would really help.

Download the test build beta6test1 from here:

http://kernel.boeffla.de/test_9aue7

Then just flash it over your existing setup (I assume you are on beta6 + cos13.1 + supersu at the moment).

During the flash in recovery, a message should be displayed about "SuperSu systemless found"...

Please just let me know if you can see this message, and if after boot supersu is still intact for you.

Thanks

Andi
[ONE Original Android Development] Nichie:
Works! And root survives
[ONE Original Android Development] andip71:
Great stuff.

And you saw the message when flashing in recovery too?

Andi
[ONE Original Android Development] Nichie:
Yup saw it too
[ONE Original Android Development] andip71:
Ok, superb. I have one more tester giving it a smoke test in a few hours, then I could release it.

Andi
[ONE Original Android Development] andip71:
Verrry good. Thank you!

Andi
[ONE Original Android Development] Gawd:
Sorry for the late reply. I was busy in school.

I'd love to test the kernel, but I have an exam tomorrow so I can't do it right now(just in case it messes up, *this is my daily driver). Thanks for your support!
[ONE Original Android Development] andip71:
Understand. No worries.

And good luck for your exam, this has much higher priority than smartphones :)

Take care

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

Andi , flashing the latest cm nightly kernel over the newly released snapshot build should be fine I suppose ?
[ONE Original Android Development] andip71:
Not tested by me, but yes - should be fine.

Andi
[ONE Original Android Development] merothh:
Let's say I flash the latest kernel on the snapshot from April , any chance it would work ?
[ONE Original Android Development] andip71:
Probably not... this is a very old snapshot, with 4 months difference in code (and it happened a lot in 4 months).

But a more recent one (don't know when the newest snapshot came out - I never use them) is likely to work.

For your April snapshot, you should search my kernel change log for a kernel version that came out in that time frame.

Andi
[ONE Original Android Development] guillermorojaz:
Greetings.

Each time you reboot or turn on my OPO me the window appears with the message "Starting Android Starting applications"

It is constant, I have already dealt with WIPE Dalvik/ART Cache - Cache and the message still appears at startup :silly:

Anyone else happens? this is happening to me since install the Boefla-Kernel-5.2-beta6.

Otherwise my OPO is a rocket without wings :laugh:

Grateful any help :good:
[ONE Original Android Development] andip71:
This is a known issue for years, which appears from time to time.

The forums are full with that topic.

It is not directly related to the kernel, but seems to occur randomly after flashing something (kernel, mod, rom, etc.)

Unfortunately nobody has a real solution to this, suspicion is that some files are corrupted. So only a full wipe with a new installation seems to help - until it happens again one day.

But at least I can say - I do not have this seen on my COS13 OPO so far.

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

update to the COS13.1 Boeffla-Kernel for you.

Version

5.2-beta7

19.08.2015

Note: This kernel version runs best on COS13.1 firmware ZNH2KAS2X1

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

Make sure, you update to latest Boeffla-Config app 2.3.8 as well.

Enjoy

Andi
[ONE Original Android Development] Gawd:
Can we flash boeffla kernel over the already present boeffla kernel?
[ONE Original Android Development] Nichie:
Yes
[ONE Original Android Development] nig3d:
I am having problems with the last resurrection remix rom related to fast battery draining. Would this kernel help on this side?
[ONE Original Android Development] hellcat50:
i don't think so.
[ONE Original Android Development] Gawd:
Doesn't cost a penny to try.
[ONE Original Android Development] pijas82:
Well, im back to this fantastic kernel,

Great app

---------- Post added at 01:33 PM ---------- Previous post was at 01:08 PM ----------

Any profiles for app? Thanks
[ONE Original Android Development] ela1103:
wow its great .then iam going to buy OP3 because of Only One Reason Boeffla-Kernel
[ONE Original Android Development] kurtextrem:
So which entropy settings would you recommend for COS13.1?
[ONE Original Android Development] andip71:
I personally double the stock settings and use 128/256.

Andi
[ONE Original Android Development] erad1:
On COS...2X1 and flashed the latest stable Boeffla version over rooted stock kernel successfully, then flashed Magisk system-less root files and modded SuperSu without a problem. Doesn't seem to want to flash the latest Test version of Boeffla though. But I'm at work now and will play around with it some more this evening.
[ONE Original Android Development] andip71:
Again... Cos stock kernel, supersu, Boeffla.

Or just avoid any weird stuff and hassle and use cm internal superuser (my recommendation).

Andi
[ONE Original Android Development] erad1:
Just had to get home to my machine to fastboot flash the stock kernel...and just as you say, it works perfectly with Magisk system less root and your 5.2 beta7.
[ONE Original Android Development] CoinCoin88:
Some update after running this kernel on my encrypted device. I've done a massive full-wipe / setup new phone / encrypt / restore some data, which proves highly efficient. If that can be of any help, I have put together a gist to keep in mind the steps to perform such a full-wipe.

My "awake" graph bar is nearly identical to my "screen on" bar, yesterday I was aroudn 3hrs of screen time, with browsing, youtube etc and still had 35% at night. Which is MUCH better that whatever I had with the stock kernel.

Thank you [MENTION=947981]Lord Boeffla[/MENTION] for putting up this kernel and following up this thread :)
[ONE Original Android Development] joaogalvao89:
this kernel works correctly with the new stock rom cm-13.1.1-ZNH2KAS2X1?
[ONE Original Android Development] NickosD:
Did you even read the last changelog?
[ONE Original Android Development] joaogalvao89:
as you say your signature , English is not your native language and bad, it is not mine. I read the changelog and the last post and not found . this being a forum, which is to help the people, i asked.
[ONE Original Android Development] erad1:
Absolutely does work if flashed correctly. :good:
[ONE Original Android Development] KaszasM:
deleted pushed to q&a
[ONE Original Android Development] ch-vox:
It also works fine with latest ZNH2KAS3P0 ;)
[ONE Original Android Development] andip71:
What... again a new version out?????

Ouch.

Edit: Found it - just a rom update, no new kernel code. So the kernel will work perfectly fine.

Andi
[ONE Original Android Development] ch-vox:
yep, a new version but no changelog as the previous one.

is it mostly a minor security update ? :confused:
[ONE Original Android Development] andip71:
This is the common rumors, it is just having August security patches in apparently.

But not 100% confirmed.

Andi
[ONE Original Android Development] rshbhghelani:
September it is !
[ONE Original Android Development] andip71:
Oh yeah, even better!

Andi
[ONE Original Android Development] kryshnakishore:
Thought to use multirom. RR ROM as 1st, cos13 as second. Do I need to use kernal that comes in multirom app in order to boot 2nd rom or our kernal is ok?
[ONE Original Android Development] kryshnakishore:
Off topic :

PM ----------

Instead of signed zip, I have downloaded signed fastboot zip. Is there any way to make changes in zip so that I can escape from downloading entire zip again. Any help
[ONE Original Android Development] kalapapa:
Why don't you just extract the system and boot img and flash it in fast boot

That's the same thing as flashing a zip anyways

Or if you don't want to deal with fastboot then just flash img in recovery

Make sure you wipe first

If it doesn't boot, you might also need to flash the recovery IMG to allow it to boot the first time and then go back and reflash twrp
[ONE Original Android Development] MMWolverine:
I have this combination only reversed. Flash boeffla-kernel-5.2-beta5-CM13.0, inject boot.img and you're good to go.
[ONE Original Android Development] ashwin.kj:
Hi, I am new to this thread. I was going to try this out, when in the FAQ I read that f2fs is not supported. Sorry if this is a stupid question, but that support is for the system partition right? If my data partition is f2fs, it will work without any problems?
[ONE Original Android Development] andip71:
Let's phrase the answer in an easy way:

My kernel supports F2FS as much as the CM or COS stock kernel.

In short: I never add F2FS myself as I consider it quite useless. But if F2FS is in the stock kernel, which source code I base on, then it is support as much.

As you did not specify whether you are on CM or COS, this is all that I can answer.

Andi