yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Pollie81:
Hi Andi,

I took your advice and bought an OPO and so far i'm really happy with it.

Now i'm just getting familiar with the phone and this OPO section on Xda.

I already had a low volume issue on calls but i'm glad that's already fixed by editing mixer paths.xml

Now i'm trying to decide which rom to use. What is your personal favourite? Do you use the stock firmware (COS) or CM?

When it comes to CM, would you advice to flash nightlies or snapshots?

Thanks!
[ONE Original Android Development] Shadow Samurai:
Nevermind. I'm not on the latest updated cmos12.1 build. sorry;)

Sent from the one and only Oneplus One
[ONE Original Android Development] andip71:
I use COS12.1 on my daily phone.

Cm12.1 most of the time on my dev phone. And never Snapshots, I always use Nightlies only.

Would have been my first question.

Make sure the rom is the version mentioned in the kernel change log.

Andi
[ONE Original Android Development] andip71:
New cm12.1 beta kernel

Guys,

as CM pushed a kernel commit yesterday, which is apparently supposed to improve battery performance, I thought I will give another update straight away to you.

Version

4.2-beta12

19.11.2015

Updated with latest official CM kernel commits as of 18.11.15

Ramdisk updated to official CM12.1 version of 19.11.15

Enjoy

Andi
[ONE Original Android Development] KURDKiNG:
Boeffla Wat would be da mha for faster charging on original oneplus one charger on your config
[ONE Original Android Development] andip71:
Everything greater than 1900 mA.

Andi
[ONE Original Android Development] KURDKiNG:
Without it damaging??
[ONE Original Android Development] andip71:
That is not what I said.

Whenever you charge your battery faster, it comes with more heat and very likely reduces life span.

I would only charge faster if absolutely required, not always.

Andi
[ONE Original Android Development] dnikogosyan:
Hi there everyone. Trying out stable boeffla for cm12.1, was wondering if you have like profile options like ak, if not then what would be recommended settings for average everyday use no gaming but smooth, thank you.
[ONE Original Android Development] andip71:
Don't use an outdated release, use latest beta12 which I just released.

As I do not know about profile options in AK, I cannot comment.

But you should go there:

http://xdaforums.com/oneplus-one/general/unofficial-boeffla-kernel-profile-t2998145

Andi
[ONE Original Android Development] infatality:
[MENTION=947981]Lord Boeffla[/MENTION] possibe to review this commit for COS12.1? http://review.cyanogenmod.org/#/c/120377/

This was commited into YOG7D but not YOG4P.. :o
[ONE Original Android Development] andip71:
Yes, it is not required for YOG4P. Here the PIC was never disabled before.

I reviewed already this morning :D

Andi
[ONE Original Android Development] dnikogosyan:
OK thank you, I just usually trust stable versions more, but if beta is stable enough, then gr8. Also when i update nightlies, I have to reinstall your kernel right?
[ONE Original Android Development] andip71:
Take the beta, my betas are usually like stables.

And normally you need to install the kernel again after every rom flash, as it gets overwritten.

However, you can configure the so called "survival mode" in my apps settings, which prevent this.

Andi
[ONE Original Android Development] dnikogosyan:
Thank you, Lord,))) I gotta say I haven't seen this kind of support and attention for a long time!
[ONE Original Android Development] andip71:
All I can say is:

Welcome to the Boeffla family :)

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

Any ideas to support Omni 6.0?

Sent from my OmniBacon
[ONE Original Android Development] andip71:
No, I will not be developing based on Omni anymore.

Stopped that long ago on the S3 already, no intentions anymore to take that up again.

I am waiting for CM13.

Andi
[ONE Original Android Development] deepaklunked:
Oh okay.. Wish someone takes up development of custom builds. Really miss your kernel..

Sent from my OmniBacon
[ONE Original Android Development] Stroky:
Andi, i have one question.

I really love the zen Hotplug decission.

Would it be the same when i set the settings to "min 4 cores online" with your kernel?
[ONE Original Android Development] andip71:
I have no clue what you mean by zen hotplug?

Can you elaborate?

Andi
[ONE Original Android Development] omaralkha99:
sorry for the noob question, but im looking at the boeffla kernel page to download and I don't know cm12.1 genuine means, compared to the stock one. im guessing means a custom 12.1 rom? Thanks for any help
[ONE Original Android Development] andip71:
Cm means the original cm rom which you can download from cyanogenmod.org.

Cos is the rom the opo comes with, it is so called CyanogenOS.

Andi
[ONE Original Android Development] twowheeler:
Something weird happened to me yesterday.

I decided I needed a fresh start, so i completely removed everything and reinstalled boeffla afterwards.

But the colours were pretty weird after that, the colour profilef for night and outdoors i mean. Allmost like they were amplified. After turning off colour control in the settings app everything went back to normal, and i can't reproduce it.
[ONE Original Android Development] Stroky:
yeah for sure!

It works perfect on the Nexus 6 and now im trying it with Android 6.0 and a custom Kernel and even with the our lovely One it works perfect!

Best performance and really good battery.

"ZEN uses zen decision hotplug. ZEN only onlines all cores on screen on, it also takes thermal events into account and wont online any core back, if you're under 15% battery, or currently have a thermal event, because of heat. So in the end it isn't a "real" hotplug driver, because it doesnt have any code for active hot plugging in it. That means you cant change its behavior."

The user "DerRomtester" included it for the oneplus One

source:

http://hc-kernel.blogspot.de/2015/06/nexus-6-zen-or-mako.html
[ONE Original Android Development] andip71:
Ok, then it was what I tought.

It is out of scope for me, as I solely rely on mpdecision for many reasons. I have never implemented any custom hot plugging (apart from zzmoove which can come with its own), and I certainly have to intentions to do that ever.

Objective close-to-stock together with questionable effort/benefit ratio does not allow me to do that.

Sorry, but if you like that so much, you need to change kernel.

Andi
[ONE Original Android Development] andip71:
Boeffla-Config App public evaluation phase

Guys,

today I have done some fundamental optimizations in Boeffla-Config internally.

And I decided to go for a public evaluation phase this time, for all users that want to help verifying the app still works as it should.

So if you are brave and want to give it a shot, you can download version 2.2.07up3 from here:

https://www.dropbox.com/s/rouvtonxi2c8omc/boeffla-config-v2.apk?dl=1

What have I changed?

The way the governor, cpu min and max frequencies and CPU voltages (undervolting, overvolting) has significantly changed internally

This applies to changes done directly in the app on-the-fly

This applies to changes done in the app and then applied after next reboot

So again: If you want to help testing and contribute, load this version and check if everything works for you as it was before. If so, feel happy. If not, let me know via mail to support@boeffla-kernel.de

Of course, this version will automatically still get updates once I push a new official version out. So you are safe.

Thanks for your time and support

Andi
[ONE Original Android Development] Jakkomo77:
Great digger, you are one of the best!

S5 & One + Boeffla Inside
[ONE Original Android Development] Tharun Gowd:
Hi Sir

I need real help now currently i have my OPO clean wiped with TWRP installed

I am very curious to try your developement over OPO

So pls do reply reply back to me with a ROM and kernel that i have to flash to feel the best of your developement.

Thanks & Regards

Tharun Gowd
[ONE Original Android Development] deepaklunked:
You can flash either COS ( Stock Cyanogen OS), or CM nightlies, or any ROM based on CM like exodus, euphoria.

There are custom boeffla kernels for Slim ROMs too, made by [MENTION=3306843]kantjer[/MENTION], only modified to work with slim, no other changes.. But, its not official.

Sent from my OmniBacon
[ONE Original Android Development] Tharun Gowd:
OK Bro can i use this with Sultan or Temasak Builds

Please send me the link to the recommended version of this kernel
[ONE Original Android Development] Adduu:
Sultan's builds are CAF, so no you can't use this kernel on it. Same goes for Temasek's CAF Builds.

If you're going to use non-caf build of Temasek (latest is 18.6) you can use the kernel made for CM12.1.

As for the recommended rom it's either COS12.1 or CM12.1.
[ONE Original Android Development] deepaklunked:
Dud, i replied for your PM.

Sent from my OmniBacon
[ONE Original Android Development] Pollie81:
Thanks Andi,

I'm very happy with my Opo together with your kernel.

I'm using Zanezam's profile and its fluid and great on battery.

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] twowheeler:
I don't think you get enough credit for having the stock kernels as flashable zip's on your website(although they say CWM, they should work fine in twrp right?). Comes in handy when you want to start fresh allover and do some testing (since you've updated the app).

Props to you! It's really professional and really helps the user. So thanks for doing that Andi!
[ONE Original Android Development] KURDKiNG:
Wats da link to it and hows performance
[ONE Original Android Development] Pollie81:
It's easy to find..

I believe it's in general (boeffla profile topic), it's in there.

I don't know how it performs on heavy duty tasks like games etc but it feels really smooth.

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] vicky2131:
[MENTION=947981]Lord Boeffla[/MENTION] i have brought good news for you today. Official cm13 nightlies have started rolling!

link---> https://download.cyanogenmod.org/?device=bacon

Would not ask for an eta, but il wait till you post some reply regarding it.

Blog from cm---> http://www.cyanogenmod.org/blog/a-marshmallowy-cm

Thank you :)
[ONE Original Android Development] andip71:
Saw this morning a cm13 nightly.

So, time to shift focus in the next days.

Andi
[ONE Original Android Development] KenjiHannya:
Good ?
[ONE Original Android Development] Mecca EL:
Woo-Hoo!!!! :victory:
[ONE Original Android Development] andip71:
Hi all,

in preparation to the new situation this morning, I just pushed an app update for Boeffla-Config to version 2.2.09.

This version is able to work under Android M :D

Andi
[ONE Original Android Development] andip71:
Development progress...

Hi all,

just to give you a quick update on the development progres...

:D :D :D

Cheers

Andi
[ONE Original Android Development] Stroky:
wow, just great!

Thank you Andi!!
[ONE Original Android Development] jokermithun:
that is fast:thumbup::)
[ONE Original Android Development] andip71:
Stable releases for COS12.1 and CM12.1

Hi all,

the first CM13 nightly arrived last night, so I took that as a good reason to make the current CM12.1 and COS12.1 kernels stable ones.

Here we go:

COS12.1 -- Version

4.0 stable

24.11.2015

Note: It is required to update to COS12.1 version YOG4PAS3JL to use this kernel version !!

Same version as 4.0-beta8

CM12.1 -- Version

4.2 stable

24.11.2015

Ramdisk updated to official CM12.1 version of 21.11.15

Now my focus is on the CM13 kernel, to come up with a first version of the kernel VERY SOON.

Andi
[ONE Original Android Development] vicky2131:
Thank you Andi for the quick updates :D now eagerly waiting for cm13 boeffla kernel. wohooo!
[ONE Original Android Development] andip71:
Well, it is looking good so far.

If all goes well, I can push it even today late afternoon etc.

Andi
[ONE Original Android Development] vicky2131:
This is GOD SPEED, period

Btw there seems to be a lot of changes in kernel for tomorrow as per this link http://www.cmxlog.com/13/bacon/

and also one more thing, does data connection work with your network on cm13(wifi works good)? Data via network doesnt work here.
[ONE Original Android Development] andip71:
Hm, but... no, I will keep my name "Lord Boeffla" - "God Boeffla" does not sound so nice.

Haha.

Andi
[ONE Original Android Development] vicky2131:
Ok then lets make it "LORD SPEED", ha ha

Anyway il end my OT here and i know its difficult to do free work as well as manage private life so once again a heartful thanks for all the hard work your putting on OPO kernel :) Cheers!
[ONE Original Android Development] Promez:
Looks like CM worked a lot on the kernel for CM13

Even the upstream! :D
[ONE Original Android Development] andip71:
Indeed.

That is why I decided to not try to backport the CM13 changes into an existing of my kernels (like the CM12.1 one), but to start freshly from scratch.

This ensures, all is 100% tailored to the CM13 kernel source base and there are no legacy code parts in the new kernel = clean kernel.

Andi
[ONE Original Android Development] andip71:
Very first kernel beta for CM13

*** FIRST CM13 BOEFFLA KERNEL *** FIRST CM13 BOEFFLA KERNEL *** FIRST CM13 BOEFFLA KERNEL *** FIRST CM13 BOEFFLA KERNEL *** FIRST CM13 BOEFFLA KERNEL ***

Good evening,

so finally I am feeling good enough to release the brand new CM13 kernel for the OnePlus One phone to you.

Please note - as always with a very first version:

- expect bugs

- expect the worst

- report the issues to me

- everything is on your own risk

Note: You need to use Boeffla-Config V2 in version 2.2.09 which came out today. Previous versions are not fully compatible to Android M.

And here we go:

CM13 -- Version 5.0-beta1

24.11.2015

First public release

All functionalities included as in latest CM12.1 Boeffla-Kernel 4.2

Ramdisk of fist official CM13.0 nightly of 24.11.15

One more note:

This kernel is tested only against the first official CM13 nightly of last night.

If you are using a custom rom which bases on CM13, it might work, or not. If not, it is your problem, not mine.

Where to download? As always: www.boeffla-kernel.de

And now - enjoy. Let the CM13 party start !!! :D

Andi
[ONE Original Android Development] andip71:
Ha !

And now we go fast... already beta2.

Nothing wrong with beta1, just there are some new CM kernel commits which were not in beta1. So the party moves on:

Version 5.0-beta2

24.11.2015

Updated with latest official CM kernel commits as of 24.11.15

Enjoy

Andi
[ONE Original Android Development] brisac:
Seems like a lot of parties will be throwing these days by CM :D
[ONE Original Android Development] thedoctor.gz:
[MENTION=947981]Lord Boeffla[/MENTION] what did you do, a dirty flash on latest 12.1 Nightly or a 13.0 fresh install?

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] magnamentis:
hoping for the lazy way to go ? LOL [semi humor]

from 12.1 you can dirty flash but don't forget to use 6.0 compatible gapps ( open gapps seem the currently best choice ) and choose the right variant which for this device is ARM (NOT ARM64 or x.86 )

PS: i'd be surprised if he dirtied LOL let's see, game on
[ONE Original Android Development] chineel:
Don't do a dirty flash at least semi clean wipe Dalvik system and cache than ROM and Gapps and super SU than kernel

But to be on safer side do a clean install for this time

I am compiling and flashing CM-13 since last 15 days or more.
[ONE Original Android Development] magnamentis:
you're right but the point was that cm officially states that it's possible to dirty flash over 12.1 while coming from another rom a clean flash is mandatory. the fact that a cleany is always best is self-evident and undisputet, does not even has to be asked or discussed IMO.

in short, agree, clean flash on API updates is strongly recommended and after all the most hassle free way to go.
[ONE Original Android Development] chineel:
current testing app is not compatible with your CM13 kernel
[ONE Original Android Development] andip71:
I was trying a dirty flash first. But it did not properly work.

Had FC errors and extremely laggy behaviour.

So I ended up with a clean install. Since then it is working like a breeze.

Andi
[ONE Original Android Development] andip71:
What testing app do you mean???

You need app version 2.2.09, as I have clearly stated in the post of the CM13 kernel release.

Andi
[ONE Original Android Development] thedoctor.gz:
Thanks for your feedback :)

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] chineel:
Sorry My bad I downloaded the latest but installed 0.8 build my yesterday download.

Same error even with 2.2.09-boeffla-config-v2
[ONE Original Android Development] andip71:
No problem.

2.2.09 is the one you need. And you need to update manually if you have an older version, as sthe update from 2.2.08 to newer version does not work (because of incompatibility :) )

Andi
[ONE Original Android Development] suaverc118:
This is what I get with 2.2.09. I am using vinman12 latest build.
[ONE Original Android Development] chineel:
Thanks now I will test it agin in My morning once I will compile new build as there are many changes since nightly.

it seems I need to do some cleaning on my data as I am using your app since long
[ONE Original Android Development] andip71:
No clue. I do not know the vinman12 build.

I wrote it was only tested against official CM build.

If something is (again, as so many times with custom roms) not compatible, I have no idea.

Maybe an incompatible security setting, root method etc.... just belly feeling.

Andi
[ONE Original Android Development] suaverc118:
Well looks like your kernel is working at least. I'll try another kernel tuner to play with it.
[ONE Original Android Development] andip71:
Although this will not be big fun, you are very limited with other apps...

Andi
[ONE Original Android Development] suaverc118:
I know, doesn't hurt to try. I really miss boeffla kernel since I've been running cm13 for a few weeks now. I honestly don't think his is straight up cm, but aosp. I think. Here is the link to his thread. A very good builder.

http://xdaforums.com/showthread.php?t=3234143
[ONE Original Android Development] andip71:
Well, something must be different.

Or it would work. Maybe with next update.

Andi
[ONE Original Android Development] striked0wn:
You use supersu? It seems to be working for me with integrated root but isn't with supersu

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] andip71:
Yes, I only use internal superuser.

Guess then SuperSu needs to get another update.

I will look at it tomorrow, maybe I can find a workaround for you.

Andi
[ONE Original Android Development] suaverc118:
I use SuperSU 2.52
[ONE Original Android Development] Stroky:
Thanks Andi.

Flashed CM 13 and the Boeffla Kernel.

Runnig really smooth and fast for this early stage!

Perfect!
[ONE Original Android Development] Mecca EL:
Same problem for me also. I'm on VM13 11/23 build. Busybox issue stems from compatibility problem within the OS? I'll bring it to [MENTION=4406894]vinman12[/MENTION] attention. Maybe fixed in the next release he has planned.

---------- Post added at 11:13 PM ---------- Previous post was at 11:11 PM ----------

Thanks so much Andi. So happy to have your kernel running on MM. Woo-hoo!!!
[ONE Original Android Development] Bobbi lim:
[MENTION=947981]Lord Boeffla[/MENTION] any plans on making a kernel for other Mashmallow based ROMs like Omni or AOSParadox based ROM? I like your kernel a lot but just don't really like CM13 as you and everyone here all knows how buggy can CM13 be unlike other ROMs...
[ONE Original Android Development] infatality:
It's already stated again and again that only cm will be supported.. And bugs on the cm13 is an common issues for new version/api roms, same goes for other MM based roms.. No new version/api will start with bugless issues.. All bugs will be iron out as time goes by..
[ONE Original Android Development] andip71:
Search the thread, no AOSP or caf.

Andi
[ONE Original Android Development] TorchaOne:
Not my business but

VM13 is a AOSP Team-Nocturnal project with performance and features in mind.*

?? He has cm13 build too so not sure we which one they are using.
[ONE Original Android Development] andip71:
Good morning,

good news. I could find and fix the issue with Boeffla-Config not working when using SuperSu on CM13 instead of built-in root.

I will push a beta3 kernel soon, which will make Boeffla-Config to finally work also with SuperSu.

Cheers

Andi
[ONE Original Android Development] suaverc118:
We appreciate you
[ONE Original Android Development] vicky2131:
Hey andi, just a small doubt. Super user by chainfire(2.52 zip) causes bootloop and rom doesnt boot, isnt it? So how did you check for config app?

Did i miss something?
[ONE Original Android Development] andip71:
SuperSu 2.52 worked for me.

I got a boot loop with 2.49 and 2.56, but not with 2.52.

However, if I installed 2.52 over one of these two not-working versions, the boot loops where still there.

So, you need to install 2.52 on a fresh system in order to make it work.

However, internal CM superuser is much more robust with CM13 at the moment. I would suggest to use it.

Andi
[ONE Original Android Development] vicky2131:
Thank you for the suggestions. Will continue with the internal root till things get pretty stable.
[ONE Original Android Development] andip71:
Beta3

Good morning,

the known issue with SuperSu on CM13 found and fixed in some kernel code.

So please go for the latest kernel now:

Version 5.0-beta3

25.11.2015

SuperSU 2.52 is now also supported with CM13 (Boeffla-Config will work now, I still recommend built-in superuser however)

Updated with latest official CM kernel commits as of 25.11.15

su binary updated to 2.52 (credits to Chainfire)

Ramdisk updated to official CM13.0 version of 25.11.15

Linked with lfd linker instead of gold linker

Enjoy

Andi
[ONE Original Android Development] andip71:
It is very simple:

You pay my monthly salary for the next 25 years, then I can drop my job and add more kernels :)

Ready for it? :D

Andi
[ONE Original Android Development] dkryder:
hello, the cm13 ROM coming out recently made me get my oneplus one back in service today. one issue i'm having is that even with the root i can not write /system/build.prop. i'm unable to change permissions to allow a change to data, mostly lcd density to get smaller icons. i've read the boot.img/kernel write these files at each boot. i looked for alternate kernel and yours seemed most regarded among the members, so i flashed it. this is my first experience with your kernel and for the past 6 hours the device has been rebooted several times then used continuously and it has been very stable for me. but, i wanted to ask you about the build.prop and also the default.prop. is there anything you can do from your kernel to help keep /system read/write? thanks for any education you can provide on my issue.
[ONE Original Android Development] andip71:
Hi, this is a known CM13 issue at the moment. Same with stock kernel as it is a flaw in the toybox implementation it seems.

Maybe once this patch gets merged, it will be fixed:

http://review.cyanogenmod.org/#/c/119929/

So far, if you need to remount system volume, the only way to do it is by doing an "adb remount" connected via USB. This will remount your system volume with RW and you can modify your default.prop.

Andi
[ONE Original Android Development] KenjiHannya:
Man, already I made a donation and I use your app with more options. Unfortunately I can not pay your salary, sorry.
[ONE Original Android Development] andip71:
This was a joke.

What I wanted to say with it is:

I habe a busy professional and private life. There is no space for additional kernel variants.

Andi
[ONE Original Android Development] laura almeida:
https://github.com/PureNexus/android_external_sepolicy/commit/d502eb337d26692f33b7fd0f0f168081e89375bf

The above patch will fix SuperSU related issues
[ONE Original Android Development] andip71:
Thanks Laura.

However I think, with beta3 all should work fine.

Andi