yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] suaverc118:
What it would do to me is when I turned on the boeffla app, the phone would go black and I would have to hardboot and reflash again. As long as I didn't start your app, the phone would run. Thanks for your explanation.
[ONE Original Android Development] andip71:
If that happens even more weird things go on.

The app brings all cpu cores online, and it seems some other process has conflicted with that.

I strongly advise to use official CM roms only, and do a fresh install when coming from another custom kernel. These are some prime reasons for it.

Andi
[ONE Original Android Development] ZETREK:
will CM13 snapshot work with boeffla beta 10 5.1?on RR 1503 it work with xposed too..
[ONE Original Android Development] Galaali:
It should work with the latest Boeffla CM13 beta kernel version.
[ONE Original Android Development] cloudx720:
Cos13 is close!
[ONE Original Android Development] andip71:
References, source of that information?

Andi
[ONE Original Android Development] infatality:
I think he meant this posted on G+ by Steve kondik.
[ONE Original Android Development] andip71:
Aaaah, nice.

Okies, let's see when they are ready for it.

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

There was one kernel commit applied to fix a bug with double tap registering as power key in today's nightly.

Will you make a maintenance update?
[ONE Original Android Development] andip71:
Not planned as double tap to wake still works fine with todays nightly and beta10.

I am not fully sure whether the change made it into todays nightly or not.

It will be in the next regular update only, or when it breaks with next nightly.

Andi
[ONE Original Android Development] kurtextrem:
You know the answer, Andi: When you're not at home :p
[ONE Original Android Development] Renosh:
The bug I'm referring to only applies during calls. If you double tap the screen while in call with your face or a finger and proximity sensor is covered. It registers as power key press. If you have power key set as end call, cuts calls or if not set your screen won't turn on during or after the call when proximity sensor is uncovered, an additional double tap or power key press is required to wake screen.

The second scenario I've experienced is if Press power button twice to launch camera is activated four consecutive double taps are detected as power key presses and launches camera. Double press power doesn't respect prevent accidental wakeup so there's a possibility of turning on camera with four double taps.

Both these issues are fixed thanks to that commit.

I'll be waiting for your next maintenance update.
[ONE Original Android Development] andip71:
Understand. I should use my phone for making calls sometimes as well, haha. I never do really.

But yes, I would like to wait for more changes to drop in for a maintenance update.

In the end, every kernel update is significant work for me, so I prefer doing it when it is more urgent.

Andi
[ONE Original Android Development] dudas89:
Just a quick post people... Since 5.1 beta 10 is only for CM based roms, it is supposed to be compatible with last Exodus Nighly (2016.3.17), right?

Thank you
[ONE Original Android Development] Rembi:
At the latest nightly CM13 5.1 beta 10 has a random reboots. At 5.1 bootloop: c
[ONE Original Android Development] Sander9847:
"At 5.1 bootloop" do you mean it bootloops when you install this on your 5.1 rom? If so then you are using the wrong verison. CM13 is only for marshmallow CM roms.

As for reboots on a cm13 rom, I've been using beta 10 since it was released and have had none. So it must be something on your end if this is the case. :)
[ONE Original Android Development] Rembi:
poorly I expressed. My bad.

CM13 Stable 5.0 - bootloop

CM13 Test 5.1-beta 10 random restart.
[ONE Original Android Development] Sander9847:
What rom do you use?

And did you do any tweaking in the Boeffla app like undervolting?
[ONE Original Android Development] andip71:
5.0 is too old for current Nightlies, this should be clear looking at the dates in the change log.

Latest 5.1 beta is rock stable on latest nightly.

Random reboots are not always caused by kernel only...

Andi
[ONE Original Android Development] bebybee:
Anyone test boeffla with sultan 12.1 ?

It support ??
[ONE Original Android Development] :
No it does not.
[ONE Original Android Development] andip71:
CM13 kernel update

Hi all,

quick maintenance update for CM13 kernel:

Version 5.1-beta11

21.03.2016

Update: Updated with latest official CM kernel commits as of 21.03.16, 10am CET

Update: Ramdisk of official CM13.0 build of 21.03.16

Enjoy

Andi
[ONE Original Android Development] dudas89:
Still not compatible with the respective exodus nightly :( (bootloop)
[ONE Original Android Development] andip71:
Isn't Exodus CAF based meanwhile? Somebody told me, I did not check as I am not using that kind of roms.

If so, it will never be compatible again.

Andi
[ONE Original Android Development] Renosh:
Yes Exodus went CAF so its not compatible with any custom kernels
[ONE Original Android Development] dudas89:
Didn't know that, thank you.
[ONE Original Android Development] evronetwork:
Tried to flash kernel for my CM13(check my sig for details) ..result? stuck in 1+ logo, oh well maybe bad luck :P

EDIT: Stable build did fail to work but test build seems to be working just fine :D
[ONE Original Android Development] konrad496:
Always-Screen-On test results with moderate app usage and LTE constantly On. Boeffla forever!
[ONE Original Android Development] bigmase521:
I tried to flash the latest kernel v. 5.1 b11, on the latest BlissROM (http://downloads.blissroms.com/OtherProjects/PROTEUS/Bliss-v6.2-bacon-PROTEUS-20160321-0309.zip), and like the above post, it gets stuck at the 1+ logo.

Actually, none of the beta versions work for me on BlissROM (stuck on logo), but the Stable 5.0 version works fine. Any idea why? :eek:
[ONE Original Android Development] silvagroup:
Recall somewhere that there's a ported Boeffla kernel for ASOP specifically DU ROM ???? Can't seem to find that reference now ??? Help...
[ONE Original Android Development] kryshnakishore:
Thanks a ton for developing this kernal this is first time i am using custom kernal for my opo(cos 12.1).... Keep developing, will donate after 1 month of usage
[ONE Original Android Development] andip71:
Valid question to the Bliss team, yes.

Why did they make their rom incompatible with standard CM kernels...

But they will not answer you anyways when you try.

Andi
[ONE Original Android Development] kalpik:
AICP also changed something in their ramdisk I guess, and this kernel isn't booting on it anymore. I'm sad I have to stop using this kernel, as IMO it's the best one for OnePlus One :(
[ONE Original Android Development] andip71:
That is life.

When all rom devs start to cook their own soup which does not taste like CM anymore... bad enough. But will not influence my objectives.

Andi
[ONE Original Android Development] kryshnakishore:
How to ser background limit process to 3 permanently even after reboot.... No need of apps, is thier any script? Or any changes in build.Prop or inti.d???

2. using opo with COS 12.1@buffalo kernal, i heard opo can fast charge how to increase fast charging by setting values in BK app i.e value i should set for charge rates
[ONE Original Android Development] andip71:
It would really help if you could write complete sentences.

To one: I do not know, I would not recommend that at all. Stopping processes hardly is not a good idea IMHO.

To two: OPO has a 801 Snapdragon SoC which has fast charge built in, however OnePlus have not enabled afaik. So all you can do ist put the charge rate sliders in boeffla config to the maximum. More is not possible.

However still, for a healthy and long lasting battery, I would only do that if really urgently required. I usually go with setting zero, which means stock charging logic which is safest and adaptive.

Andi
[ONE Original Android Development] MZO:
Can I build my ROM with this kernel?
[ONE Original Android Development] Bitcloud30:
will this work on the latest CM13 of sultan?

*sorry if you already answered this. i dont know what page to look at.
[ONE Original Android Development] grusta:
Sultan's CM13 = CAF

This kernel is for official cm13

So, no.
[ONE Original Android Development] Bitcloud30:
thank you. how about on exodus 6.0?
[ONE Original Android Development] grusta:
Same
[ONE Original Android Development] twowheeler:
Andi what ROM are you using on your opo? Cm13 or the "official" cms12.1?

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] andip71:
My daily driver phone: cos12.1.

My test phone is on cm13.

Andi
[ONE Original Android Development] MZO:
Resking: Can I use this kernel with my builds? Please reply.
[ONE Original Android Development] andip71:
Yes.

Requirements: giving credits and the link to the thread.

And - no expectations to help you build it with your rom. I only build the kernel on it's own. So you need to figure out yourself how to do the complete build process (which is not that simple check my build script).

So
[ONE Original Android Development] MZO:
Cool, thanks, I'll try figuring it out :)
[ONE Original Android Development] andip71:
New beta

Hi all,

CM13 kernel update to be up-to-date with latest CM code and fix an annoying issue with module loading:

Version 5.1-beta12

26.03.2016

Update: Updated with latest official CM kernel commits as of 26.03.16, 10am CET

Update: Ramdisk of official CM13.0 build of 26.03.16

Fix: Module loading is working again (was broken as insmod command of latest CM toybox is currently broken)

Enjoy

Andi
[ONE Original Android Development] twowheeler:
Thanks!
[ONE Original Android Development] Setting.Out:
[MENTION=947981]Lord Boeffla[/MENTION]

Quick question, I've been running your COS12.1.1 kernel flawlessly in current 12.1 CM builds, is there any reason I should need to use the older less up to date normal CM version?

Thanks.. ;)
[ONE Original Android Development] kryshnakishore:
When next update is coming for cos12.1 beta??
[ONE Original Android Development] Aavion:
Why? There's no need for an update since there isn't anything new :D

Let's wait for COS13 and it's sources to be released ^^ Until then, every new kernel update would be a waste of time ^^

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] andip71:
If you are happy and have no negative effects, no need to change.

No immediate plans.

I am anywhere not around before next week.

And then a cos update is not a priority as there is no reason for it.

Andi
[ONE Original Android Development] nitishp7890:
On dirty unicorn with boeffla not booting up help will be appreciated thank u
[ONE Original Android Development] EvilPat:
Dirty Unicorns is caf based
[ONE Original Android Development] andip71:
Yep. And my kernel is only for cm.

And I will also not ever do caf, as stated in op.

Andi
[ONE Original Android Development] Franc38:
In the last few nightlies I have a nasty case of FCs in the Theme part. All is good with the cm kernel, but with yours every time I try to change something in the theme, I have to reboot else the FCs just make the phone unusable.

Not sure what's causing that...
[ONE Original Android Development] andip71:
I am sure it is caused by changes to the ramdisk in latest nightlies.

Meaning - it would require an kernel update.

It is planned for monthly as a normal regular maintenance update.

Andi
[ONE Original Android Development] bobstar3233:
Charging issues

I have charging issues with my oneplus one unity our kernel can anyone help

I have used all my 1a 2a and 4a chargers and various different leads

---------- Post added at 03:45 PM ---------- Previous post was at 03:39 PM ----------

The configuration app says like 5-55mA
[ONE Original Android Development] andip71:
Then something is broken with your cable or charger. This is by far too low.

Andi
[ONE Original Android Development] silvagroup:
Won't work with DU unfortunately. Radioactive or Lightning kernels for asop and CM. Although I have not tried either with my asop ROM, yet...
[ONE Original Android Development] TorchaOne:
That would be quite incredible, if 3 chargers and all cables are broken at the same :) Anyway, I have had randomly too very slow charging, reboot helped almost every time, sometimes just re-plugging helps.
[ONE Original Android Development] andip71:
Dirt in the plug, broken plug, thermal profile, environmental temperatures, there are plenty of factors...

Andi
[ONE Original Android Development] TorchaOne:
Heh, or just something wrong with charging. Lots of factors. For example if you boot from recovery to cm with boeffla, I have to reconnect the charger to be able to charger more that 100mA, repluging and it goes up to normal. And my chargers are just fine, thanks for asking and temp is ok. Not like living in India.
[ONE Original Android Development] xeltos:
Can anyone guide me?

Using CM 13 based Resurrection Remix. 5.6.6

Flashed The CM13 Boeffla Kernel. Flashed Caches

Phone wont go past OnePlus Logo.

Had to reflash the rom.

ANything I am doing wrong?
[ONE Original Android Development] Sander9847:
Make sure you reboot your Phone once inbetween flashing ResurrectionRemix and Boeffla.

This is what made it work for me, I'm using the same setup.
[ONE Original Android Development] xeltos:
Dont need to do factory reset?

Because I did flash after a reboot.

Do I need to flash some firmware?

I am not having a boot loop.
[ONE Original Android Development] andip71:
Hi all,

the promised maintenance update for the cm13 kernel.

Version 5.1-beta13

04.04.2016

Update: Ramdisk of official CM13.0 build of 04.04.16

Enjoy

Andi
[ONE Original Android Development] :
can i use this one with snapshot?
[ONE Original Android Development] andip71:
You can try.

I never use snapshots as they are too old when they come out.

So I cannot tell myself if it has side effects.

But worth a try when you do a nandroid backup first.

Andi
[ONE Original Android Development] Lookitfast:
Doesn't seem like color settings are sticking with latest app update & 13 test on cm13 upon reboot. I'm on RR 4-1-2016 release.

EDIT: Sticking now...go figure
[ONE Original Android Development] andip71:
Yep, sticking here.

Nevertheless... RR = custom rom = your responsibility when something does not work, refer to OP :)

Andi
[ONE Original Android Development] nachomagic:
Hi mates :)

I've heard really god thing about this kernel :)

Also I've heard that via kernel is possible customize off screen gestures to launch any app/shortcut.

Does this kernel support it?

thanks in advance
[ONE Original Android Development] andip71:
Well, you heard a mix of different things.

The kernel can detect gestures = true.

The kernel can give the gestures to the rom to launch apps = true.

The kernel itself cannot launch an app however, as kernel and user space are clearly separated.

So what I want to say is: You need rom support for that.

Andi
[ONE Original Android Development] nachomagic:
Thanks for clarify me the concepts :)
[ONE Original Android Development] chrome6boy:
Many thanks great lord! Themes don't force close any more!
[ONE Original Android Development] shamru:
Kernel for CM13 Snapshot

Will you be making a kernel for cm13 snapshot or only for cm13 Nighties
[ONE Original Android Development] andip71:
Only nightlies.

But a snapshot is nothing else than an older nightly too. So there is no need to do separate kernels for it.

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

CM13 kernel update, many source code changes pushed by CM.

Version 5.1-beta14

06.04.2016

Update: Updated with latest official CM kernel commits as of 06.04.16, 10am CET

Change: Internal kernel busybox updated to latest version 1.24.1 (self-compiled from sources, www.busybox.net)

Update: Ramdisk of official CM13.0 build of 06.04.16

Enjoy

Andi
[ONE Original Android Development] notanapple:
I don't know if it has been already asked but why my phone doesn't boot (stay on 1+ logo) if I perform a dalvik/cache + cache wipe in twrp? I have installed the kernel without any issue after flashing the rom and boot but if i try to do those wipes i have to restore the backup to get the phone working. Thank u... I am using resurrection remix ROM without any issue but this...
[ONE Original Android Development] andip71:
This is because RR is not 100% compatible to CM, hence you have such glitches as my kernel is based on CM.

Andi
[ONE Original Android Development] notanapple:
Thanks man!
[ONE Original Android Development] Sander9847:
They have been working great together for me for the last 3 months, not a single issue.

All you have to do to get it working is boot phone once and let it optimize apps after flashing rom and wiping caches. Only then you can go back into recovery to flash kernel & don't wipe caches anymore.
[ONE Original Android Development] andip71:
Yeah, but honestly, this does also feel like a dirty thing, or?

Lets assume dalvik/art cache gets corrupted one day, then you always have to have the RR rom or at least stock kernel available to get the phone running again.

Just saying ... :)

andi
[ONE Original Android Development] notanapple:
Yes...in fact I asked this question due to a dalvik cache wipe to get app optimisation for other reasons...I know that flashing boeffla must be done after first boot in RR ROM but the main problem is how can I wipe cache and dalvik after days of phone usage? Never mind I'll try to flash the ROM (this installs the stock kernel) then wipe davik and cache and and boot phone and after first boot, back in recovery, flash boeffla..it's not time saving but maybe it works:D
[ONE Original Android Development] guillermorojaz:
cm-13.0-ZNH0EAS26M-bacon-signed.zip

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

EDIT.

A very bad joke :)
[ONE Original Android Development] bloof:
:) OTA is out. Full TWRP flashable should be out soon.
[ONE Original Android Development] hellcat50:
Flahed Boeffla kernel on C OS 13. So far so good. It boots and all working fine, will report back later if there are any problems.

btw I noticed that when I install apks the package installer fc's when finished installing. could be a c os 13 bug
[ONE Original Android Development] akash4357:
No bugs as such on Official COS13.
[ONE Original Android Development] bloof:
How did you root it? Did you install TWRP?
[ONE Original Android Development] hellcat50:
I flashed twrp after update and then boeffla kernel and super su 2.65
[ONE Original Android Development] andip71:
To all:

Will start looking at it from Monday onwards.

Hope we have a full zip compatible with twrp already by that time.

Andi
[ONE Original Android Development] bloof:
Try supersu 2.71 (or whatever latest is). I assume you used cm13 boeffla kernel, but it is not fully compatible with cos13 (i am sure of that).

I would wait until fully flashable ROM TWRP zip is available. And if someone makes a flashable zip to enable root (cyanogen integrated su), that would be even better.
[ONE Original Android Development] hellcat50:
Hey the issue fixed itself somehow. So it's all good now.
[ONE Original Android Development] atulclassic:
Which kernel you are using?
[ONE Original Android Development] andip71:
Whom was that question going to?

Andi
[ONE Original Android Development] Leicxan:
Flashed CM13 5.1 beta14 on Cos13.0 ZNH0EAS26M for tempery use. So far so good. Waiting for Lord's cos13 kernel base on cyanogen's source:)
[ONE Original Android Development] johnsin5393:
Where to get the cos 13 rom? Tqvm
[ONE Original Android Development] anagramgenius:
Clear data of package installer.
[ONE Original Android Development] :
Guys, stop flashing CM13 kernels on COS13 ... Both ain't same.
[ONE Original Android Development] chenrp:
any way of increasing the call volume?
[ONE Original Android Development] bloof:
Ota is out, google and you will find. Full official zip is not out but a flashable zip has been made. Search xda.
[ONE Original Android Development] atulclassic:
sorry..app didn't quoted the message i replied

I was asking in order to konw which kernel that user is using since CM13 kernel is not recommended and COS13 will take time
[ONE Original Android Development] Renosh:
https://forums.oneplus.net/threads/mirrors-for-official-cyanogen-roms-ota-updates.141825/

There's a full signed flashable zip above
[ONE Original Android Development] HaTrED_:
And what a zip Sir! [emoji3] [emoji3]
[ONE Original Android Development] Renosh:
Lol it goes to some random YouTube video [emoji23] [emoji23] [emoji23]
[ONE Original Android Development] Levivig:
We just got Rick rolled! lol

Well played! :D
[ONE Original Android Development] andip71:
Ha?
[ONE Original Android Development] bloof:
https://forums.oneplus.net/threads/mirrors-for-official-cyanogen-roms-ota-updates.141825/

Link for CM13 full flashable zip directs to Rick Astley youtube video.

OP will not remove link until Cyanogen OS gives the full image.
[ONE Original Android Development] kunal1540:
http://xdaforums.com/oneplus-one/de...13-znh0eas26m-untouched-t3355423/post66279906

Can the zip in this thread be used for making boeffla kernel for cos 13.
[ONE Original Android Development] andip71:
I think so, although I went the (painful) OTA way to not rely on something potential unofficial. I tried it once with this full zip but got wrong toybox links, so I dumped it again.

But I am already almost there as you can see in the screenshot. I do internal smoke testing right now.

Andi
[ONE Original Android Development] bloof:
Any issues with /system mounted as read only in COS13? Can that be changed with some kernel implementation and/or selinux? (pardon my ignorance)
[ONE Original Android Development] andip71:
Have you flashed the full zip to update to COS13 or the incremental?

With the full zip I had the same issues (see above), wrong toybox links etc.

So I tried with incremental and here all is fine now.

Andi
[ONE Original Android Development] bloof:
I haven't flashed anything yet, when i see that many issues I wait and see. If you're not seeing any issues with the long painful OTA way then i will definitely wait for full flashable zip (or go the painful way if i get impatient).

By the way, how did you root?
[ONE Original Android Development] andip71:
Yes, as said:

- with this inofficial full zip I could confirm all these issues

- the long painful OTA way worked perfectly however, I can mount system rw without any issues (mount, ps, grep commands working, which they were not with the inofficial full)

I guess we have to wait for the official full to see if that is better.

Root: Only systemless root with 2.71 supersu beta so far, everything else I tried did not work.

Also built-in root is not yet possible before we get the debuggable kernels provided by CM.

Andi
[ONE Original Android Development] andip71:
But I can already say - I will not jump very quickly on COS13 myself.

I realized on my development OPO, Doze does it's work and prevents / delays notifications from coming in.

A whatsapp message does not go through anymore until I open Whatsapp. And I have excluded it already from Doze in Battery settings.

This is a complete no-go for me...

I wonder if everyone faces this?

Andi
[ONE Original Android Development] andip71:
COS12.1.1 stable kernel

Hi all,

after COS13 got released a few days ago, I decided to release the COS12.1.1 kernel as stable finally. This also means, this is the final version and therefore end-of-life.

Version

4.2 stable - final

11.04.2016

Note: It is required to update to COS12.1.1 version YOG7DAS2K1 to use this kernel version !!

Change: Internal kernel busybox updated to latest version 1.24.1 (self-compiled from sources, www.busybox.net)

Fix: Security flaw CVE-2015-1805 (memory corruption in pipe) fixed

Change: Hardening of Boeffla scripts for Supersu

Change: Cleanup of ramdisk after removing legacy files

Enjoy

Andi
[ONE Original Android Development] andip71:
CM13 kernel update

Hi all,

maintenance update for CM13 kernel:

Version 5.1-beta15

11.04.2016

Update: Updated with latest official CM kernel commits as of 11.04.16, 10am CET

Update: Ramdisk of official CM13.0 build of 11.04.16

Enjoy

Andi