yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] andip71:
Well, not too much time so far to play with it.

But (after I recovered it from a medium level brick successfuly with the Qualcomm recovery tools) I begin more and more to like it.

Latest OxygenOs update ironed out lots of issues that were present before.

So... it is getting better, but I need some more time to really deal with it.

Allright, thanks.

So I will be very curious once I built the kernel for COS12.1, how GPU is being used then. Because my GPU implementation allows lower GPU frequencies. And I am interested to see whether they are being used or not.

Exciting stuff, just need to have some time to start working on it (as I prefer a fresh setup for such a new thing instead of updating the previous kernels, objective "close-to-stock" and stability).

Andi
[ONE Original Android Development] abhibnl:
I am very well aware of your objective Andi. A boeffla user from last 3 years surely has taught me that. ??

BTW i'll the latest cm12.1 kernel.of yours with it to test and see if gpu frequency can be controlled properly without reboot.

Sent from OnePlus One
[ONE Original Android Development] andip71:
The question is more... does the cm12.1 kernel work on COS12.1? I doubt...

Andi
[ONE Original Android Development] abhibnl:
It works flawlessly Andi. Using latest beta20 u511.

Sent from OnePlus One
[ONE Original Android Development] andip71:
Unexpected. Especially when it comes to features like the sunlight enhancement which usually is not working with CM genuine based kernels on COS.

But good it boots and at least seem to work, interesting info.

Andi
[ONE Original Android Development] abhibnl:
But i'll wait for your cos kernel based on official sources as we all are because of your close to stock objective. Since this cm12.1 is not that close to stock but it's working pretty fine. Will use it for the time being.

Sent from OnePlus One
[ONE Original Android Development] andip71:
Stable releases

Hi,

I hereby declare the new CM12s (COS12) and CM12.1 kernel versions as a stable releases.

CM12s/COS12 -- Version

3.1 stable

26.08.2015

zzmoove maintenance patch (scaling/zz_get_next_freq) to fix some minor issues (credits to ZaneZam)

Internal build script improvements

CM12.1 -- Version

4.1 stable

26.08.2015

zzmoove maintenance patch (scaling/zz_get_next_freq) to fix some minor issues (credits to ZaneZam)

Updated with latest official CM kernel commits as of 21.08.15

Internal build script improvements

Ramdisk updated to official CM12.1 version of 26.08.15

Any subsequent updates will be done in a new beta series.

Enjoy

Andi
[ONE Original Android Development] suaverc118:
I feel dumb for asking but the new cm that came out, I would use 4.1 stable?
[ONE Original Android Development] ZaneZam:
u mean the new stock one cos12.1? that would be the nearest version yes, if it boots then u are fine but expect compatibility issues. ;)
[ONE Original Android Development] andip71:
I suggest you guys wait for me releasing a dedicated version for cos12.1 to guarantee full compatibility.

I plan to start working on it tomorrow.

Andi
[ONE Original Android Development] rahulrai:
OT........ Andi you are doing a great job by giving the android community some of the best. I suggest you should take proper sleep and rest as well or do some yoga to keep yourself healthy.
[ONE Original Android Development] kurtextrem:
No, your kernels are magic... even the new livedisplay works (which means cf lumen is no longer needed :)). Impressive :D
[ONE Original Android Development] andip71:
Magic... hehe, I am a magician :D

On a more serious point, I have started working on the COS12.1 kernel.

And it is already compiled.

Just need to install COS12.1 now and see if it boots and works.

If all goes well, I can give it to you in a first beta already today.

Andi
[ONE Original Android Development] Clark789:
I'm convinced you are! ;)

And please let us know, how you flashed your phone. There are different hints how to flash in the correct way...

Cheers

Clark
[ONE Original Android Development] andip71:
COS12.1 beta

Hi guys,

ok, this is already looking quite good and promising.

Doing some stability testing, but expect a release for beta1 today when all goes well.

Andi
[ONE Original Android Development] akz1x1:
Yay ! ... looking forward to it :)
[ONE Original Android Development] andip71:
COS12.1

Hi all,

hhoooorraaayyy - managed to get the first native COS12.1 Boeffla beta kernel online now.

COS12.1 --

Version

4.0-beta1

27.08.2015

Initial release for COS12.1 (Version YOG4PAS1N0)

All functionalities implemented that are also in the previous COS12 stable kernel

It is completely built from scratch from the CM COS12.1 kernel branch, to provide you the best stability and compatibility.

If you find issues, please report and be patient for the fixes.

Every kernel completely built from scratch could potentially have some broken functionalities, although I do not believe so as I tested it briefly.

Enjoy

Andi
[ONE Original Android Development] Clark789:
Dear Andi,

it's a kind of magic!!

Especially, when i see the release date is the 27.04.2015! You kept in reserve until now??? ;)

Thx a lot for your work, your eagerness and your patience in answering lots of questions!!!

Cheers

Clark
[ONE Original Android Development] andip71:
Lol, thanks for spotting. Indeed this was a copy and paste error. Corrected in a few minutes.

Andi
[ONE Original Android Development] infatality:
Anyone can confirm vibrator intensity in setting sound is causing fc? Just want to confirm if it's cause by kernel.
[ONE Original Android Development] andip71:
Yes, seems to be kernel related. I can replicate that with Boeffla, do not have the issue with stock kernel.

At the moment, I have zero idea why, as this should not be changed at all.

I can only assume, the kernel sources CM pushed out are not 100% complete at the moment.

Andi
[ONE Original Android Development] infatality:
I thought so too.. As I flashed cos12.1 and your kernel together thus the rom had never booted stock kernel.. Thanks for your confirmation.. Will be waiting for upcoming changes.
[ONE Original Android Development] abhibnl:
Vibrator intensity is working fine with the latest cm 12.1 kernel.

Sent from OnePlus One
[ONE Original Android Development] infatality:
Yup.. Seems to works fine now.. After several reboots.. Will continue to monitor and see if it's go bonkers again.
[ONE Original Android Development] andip71:
Have a strong idea now... ZaneZam gave me a hint it seems to be SeLinux related. So will in worst case compile a beta2 already :D

Andi
[ONE Original Android Development] infatality:
Ring a bell now.. After that I did change to permissive..
[ONE Original Android Development] andip71:
Yep, was what I expected.

beta2 will go out in the next 1-2 hours.

Andi
[ONE Original Android Development] suaverc118:
Hey Andi. I'm running your 4.1 from Wednesday with latest release of 12.1 with no issues... How will your beta2 be any different from a users stand point?
[ONE Original Android Development] andip71:
The vibrator settings will not FC anymore in settings menu.

Also some potential other Selinux related things that we have not yet discovered to be broken will be working again.

Andi
[ONE Original Android Development] andip71:
COS12.1 beta2

Hi all,

some cleanup required to fix the mysterious vibrator settings FC (which was not so mysterious anymore afterwards). This beta2 would potentially fix some more issues regarding to selinux which have not yet been uncovered.

So I highly recommend everyone to step up to beta2 !!

COS12.1 -- Version

4.0-beta2

27.08.2015

Fix various selinux related things that were broken (e.g. vibrator settings FC in settings menu) due to some forgotten leftovers of the previous CM12s kernel

Thanks

Andi
[ONE Original Android Development] abhibnl:
[MENTION=3279788]ZaneZam[/MENTION] a life saver as always! :D Waiting for his uber builds.

I'm using selinux as permissive from the very first minute. lol :silly:
[ONE Original Android Development] Orphee:
Hi,

I just updated to COS 12.1 and flashed your kernel, it works great currently :)

Not related to the OP, but did you notice this ? : http://www.xda-developers.com/cyngn-to-leech-user-contacts-to-truecaller/

I deleted this "True Caller Service" with Titanium backup... It is just unbeleavable...
[ONE Original Android Development] vicky2131:
awesome!! flashing now

thanks andi
[ONE Original Android Development] kurtextrem:
I've found a bug in IntelliMM. It uses CU frequencies over the limit (for example I set the limit to 19XX, it still uses up to 24XX). (not new in the cos12.1 version, I noticed it before).
[ONE Original Android Development] andip71:
This was always the case apparently.

Because intellimm has not changed since introduction.

Maybe I should remove it. I have no tendency to fix governors myself in future. If they are not clean, I am happy to remove it.

But wait... Where do you see that? Maybe I can still explain it.

For instance during start, the phone uses 24xx until the kernel configuration gets applied. This is normal.

But afterwards it should not use it anymore.

Andi
[ONE Original Android Development] andip71:
Just tested for 5 minutes. It does not go over max frequency on my end...

Andi
[ONE Original Android Development] guillermorojaz:
Greetings Lord Boeffla.

Small question :p

I'm downloading this Rom: http://xdaforums.com/oneplus-one/development/rom-cyanogen-os-12-1-t3186593

After installing, I install your Kernel, Wipe Dalvik Cache/Cache and restart install the 2.2.01-boeffla-config-v2 ?
[ONE Original Android Development] andip71:
Yup. Exactly like that.

Andi
[ONE Original Android Development] guillermorojaz:
Thanked.

Let you know how it goes around.

Thanks again for your work, I hope this is just as magnificent as the version for CM12.1 :good:
[ONE Original Android Development] kurtextrem:
Weird. I also double checked with CPU Spy.

And please don't remove - I still can't decide which to use, IntelliMM or ZZMove Optimal :/
[ONE Original Android Development] andip71:
Are you sure you have not booted with intellimm active?

The 58 seconds could very well be tge time until the config gets loaded after the boot.

Set a reference in Boeffla Config (button at bottom) so you see if any higher freq is ever used after that time.

Andi
[ONE Original Android Development] abhibnl:
Here's mine. And trust me, i have never used max frequency beyond 1957 from day one of buying this device. So it's perfectly normal. 58 seconds on that step won't eat all you battery.

Sent from OnePlus One
[ONE Original Android Development] Clark789:
Everybody seen, that there is a supposedly new build of the new update?

Here you find it: http://cyanogen-ota-bacon.somee.com/

The comment of the original thread was:

Quote:

Update WAS put on hold, but it was resumed yesterday at roughly 20:00 UTC with a new build. I updated with the new build and so far it has been good. No glaring issues thus far, though I did replace the dialer with the one posted earlier in this thread.

Cheers

Clark
[ONE Original Android Development] vicky2131:
[MENTION=947981]Lord Boeffla[/MENTION] mate, the phone used to wake up properly unlike the cm nightlies when a call comes. after flashing the kernel it doesnt wake. Have to press the power button first to wake it up to know whose calling. any idea? using zzmove with battery yank

edit: i restarted and it worked properly :) thanks mate
[ONE Original Android Development] The Dork Knight Rises:
[MENTION=947981]Lord Boeffla[/MENTION] OT, but any idea why the touchscreen doesnt work on Ambient Display screen (on both stock and Boeffla kernel)?

Is it like that for everyone else?
[ONE Original Android Development] andip71:
Dunno. Ambient display is the first thing I switch off.

But when I tried it some months ago it worked.

Maybe it is now broken. And when it is broken in stock kernel too, then it will for sure be fixed by CM again.

Andi
[ONE Original Android Development] Mandrake2010:
Hi andi, i have cos12.1 and for root embedded i have used unofficial 12.1s superuser zip, with adb and app access enable in developer option.(alla OK)

Now i have flashed boeffla 4.0 beta 2 but i have lost root ( in deve.optional i can seee option for root). Boeffla 3 was compatibile with embedded root. Boeffla 4 no?

Sorry for bad english

Best regarts
[ONE Original Android Development] andip71:
No, boeffla 4 is currently not compatible with internal root.

So far there was no rom available with internal root enabled, hence I built no compatibility in.

And I consider to maybe not do that anymore in future. SuperSu is good, don't see a strong reason to make it compatible again.

BTW: What inofficial superuser zip did you install? Curious...

Andi
[ONE Original Android Development] Mandrake2010:
https://forums.oneplus.net/threads/flashable-zip-cm12-enable-integrated-superuser.297089/

Now i flash supersu zip. I can't lost your kernel

P.s: with stock kernel 12.1 i have read fiops scheduler as default.
[ONE Original Android Development] andip71:
Just select fiops also with Boeffla if you want.

Andi
[ONE Original Android Development] andip71:
Breaking news - OnePlus Two

*** breaking news *** breaking news *** breaking news *** breaking news ***

OnePlus Two

I have a very first proof-of-concept kernel up and running. It is nothing like a stock kernel recompiled by me, but this is always the first step to a custom kernel. Screenshots attached.

Just for expectation management: I am still light years away from a first real custom kernel for the OnePlus Two as (again) the OnePlus kernel sources are very low quality. In short, the device tree blobs are not complete, so we cannot use them and therefore things like frequency and/or voltage changes are not possible at the moment.

But I am confident I can fix this, just as I did for the OnePlus One as well for the OxygenOS kernel.

However, I am happy I reached this stage finally today.

Cheers

Andi
[ONE Original Android Development] andip71:
Ok, I have beta3 ready which supports internal root again, just like the CM12s kernels did.

Will ship out either today or latest on Monday.

Andi
[ONE Original Android Development] kurtextrem:
Hm.. really weird. 11min on that step - and booting doesn't take as long as that.
[ONE Original Android Development] andip71:
Yes, weird. I cannot replicate.

MY phone behaves as it should :)

No idea what happens over there at your side.

Sorry

Andi
[ONE Original Android Development] Clark789:
Installed COS 12.1 and 4.0b2.

Perfect!

Absolutely no issues!

Thx, Andi!

Cheers

Clark
[ONE Original Android Development] magnamentis:
another kernel tweaking app, knowingly or as a hidden feature like in rom-toolbox ? just brainstorming a bit, while i can confirm that all works as expected here :)
[ONE Original Android Development] andip71:
COS12.1 beta3

Good evening,

new beta for COS12.1, which now supports also CM internal root for users that prefer that over Chainfires supersu.

To use it, you need to fully uninstall supersu, then flash the superuser enabler (see link below for more information and download) followed by the beta3 kernel again.

COS12.1 -- Version

4.0-beta3

28.08.2015

Support for CM internal root (more information here)

Enjoy

Andi
[ONE Original Android Development] kurtextrem:
Nothing like that. I've recently flashed COS12.1 and I didn't flash anything apart from SuperSU and Xposed. I've also checked: The checkbox "Allow apps to overwrite max cpu freq" is not checked.

Could it be that it is because of hotplugging: 2min?
[ONE Original Android Development] andip71:
No, hotplugging has nothing to do with frequency scaling.

I will keep an eye on it on my side, as I have also COS12.1 now on my main phone and max cpu also limited to 1954.

Andi
[ONE Original Android Development] magnamentis:
does that rom have a built in "performance" feature, that would be a way to tweak the kernel ( very limited though ) without installing a third party app. i'm asking because all my roms have that and it's too long that i tested COS, hence don't know anymore by heart, just have a look quick and if yes check if the settings are set in a way that coulde cause your issue. i don't really believe that's it but that's all that comes to my mind when pondering over your weird issue.
[ONE Original Android Development] kurtextrem:
Yes, it has. It's COS12.1, but of course I turned off the per-profile thing, and the performance profile is set to "Balanced". For now I'll stick to Intelliactive, it seems to like 300MHz.
[ONE Original Android Development] efattal:
Hi [MENTION=947981]Lord Boeffla[/MENTION],

As [MENTION=2332422]temasek[/MENTION] ROM now fully supports f2fs, are you planning to support it also? I'd like to continue using your kernel.
[ONE Original Android Development] twowheeler:
Just updated to cos12.1. What about all this selunix stuff? Can i just flash the latest beta and use it like normal or do i first need to change it to permissive again?
[ONE Original Android Development] ZaneZam:
just flash latest beta 3 the Selinux thing is fixed ;)
[ONE Original Android Development] twowheeler:
Awesome! Thanks

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] andip71:
Look at OP, section what I never will implement"...

Nope, f2fs will not come, I consider it over hyped and pretty useless on such a strong phone as the Opo.

If that is a deal breaker for you, I am afraid you need to move on to a different kernel.

Andi
[ONE Original Android Development] andip71:
If it is a bug, then from rom or codecs.

Try again with stock kernel to find out if it works there.

Andi
[ONE Original Android Development] infatality:
[MENTION=947981]Lord Boeffla[/MENTION] new updates for kcal. Any good for us?

http://xdaforums.com/showthread.php?p=62573328
[ONE Original Android Development] lchiocca:
Let me assume that you are on cm12.1 (nightly or s). If that's the case then have a look at cm's latest blog entry about having merged a batch of additional bugfixes (www.cyanogenmod.org/blog/cve-2015-3833-and-you). You are probably using greenify or some other memory optimizer that is trying to get the forground process(es). But this is no longer possible with the latest cm rom.

Really dont think this is kernel or rom related. Turn off you memory mananger.
[ONE Original Android Development] andip71:
Not sure.

Seems the op has been deleted again.

Also I think the current implementation does what it should do.

Personally I don't use it at all even.

Andi
[ONE Original Android Development] wahuka:
Hello friends.

When I receive a call, the phone screen takes between 3 and 5 seconds to start.

You can tell me how should configure the kernel to prevent this from happening?

My config on CM12.1 Nightlies OPO

zzmoove

zzmoove-battery yank

Programmer: Fiops

Buffer Readahead: 1408

CPU

Max Freq: 1574

Min Frreq: 300

Hotplug profile: zzmoove nativa default

Undervolt Medium

GPU

Max Freq 330

Min Freq 27

Touch boost: 1497

System tweaks: off

Kernel logger: disabled

What i should change, I intend to saving battery without sacrificing performance
[ONE Original Android Development] andip71:
Use search. This was 10x answered already.

Andi
[ONE Original Android Development] wahuka:
Thanks, but my english is very poor and i dont know what i must write to search

sorry if my message has upset
[ONE Original Android Development] abhibnl:
Please use search box from next time. You can search for e.g. "wake screen", screen delay, etc..

For your issue, your governor, zzmove battery yank, is the culprit. Use some other governor or sue ZZmove relax profile.
[ONE Original Android Development] wahuka:
Thanks friend and sorry if this has answered.

for me it is difficult to write in English

I hope you understand
[ONE Original Android Development] liver20:
Hi, i am now in cos12.1.

All stock oficial cyanogen. Sometimes try to wake and have to shutdown because screen not turn on.

Your kernel fix it?

Somebody have the same problem?
[ONE Original Android Development] EasyGoingXD:
why could i not set the gpu frequency?
[ONE Original Android Development] andip71:
Where would you like to set it?

Who said you can set it?

Andi
[ONE Original Android Development] EasyGoingXD:
because there is the option inside your app and in your informationsbox about your rom (here on xda) it says overclocking gpu enabled
[ONE Original Android Development] andip71:
Ok. The app is for all my kernels.

But the app says absolutely correct: not implemented in the kernel. It is so far only in my Samsung kernels...

This kernels feature list does also not mention gpu overclocking somewhere, neither does a change log.

I do not have a rom...

So sometimes I just don't understand what people do interpret... [emoji51]

Andi
[ONE Original Android Development] EasyGoingXD:
my bad i am sry, btw kernel runs great with temasek!!!!

AWESOME
[ONE Original Android Development] jgcaap:
Guys on cm11 ,not cm11s there is a big improvement of touch.
[ONE Original Android Development] suaverc118:
So shall I wait for him to update the kernel and not flash this latest one? And for crDroid do I flash the cm11? I assume it but i also know that its based off of cm11s. Thanks.
[ONE Original Android Development] Albieri[SPAM]:
I think the feature to turn on the screen with 2 clicks does not work in beta6.

Anyone noticed this?

NOTE: The flashlight is still working making the "V" motion. And camera "O".
[ONE Original Android Development] andip71:
It does work without problems.

Are you sure it is still switched on?

Andi
[ONE Original Android Development] andip71:
New beta7

Hi all,

thanks to the CM team releasing a series of patches yesterday, and thanks to the broken video playback due to that, already a new beta7 for you now.

Beta7 for both Cm11 and Cm11s kernels, as usual :)

This time it is pretty much untested by me in order to push it out fast, but I assume there should be no issues.

Version 2.0-beta7

31.10.2014

New touchscreen firmware 14001221 (30.10.14)

Merged latest CM11 patches in - this fixes the video playback issues on genuine CM11 kernel (YouTube etc.)

Use load&flash in Boeffla-Config for convenient update, or grab it from the Download folder on the homepage.

Quick note: There seems to be a bug triggering in zzmoove from time to time (refer to ZaneZam's post yesterday http://xdaforums.com/showpost.php?p=56388983&postcount=599).

So if you use zzmoove and face some hot reboots, please switch to another governor for the time being. ZaneZam is trying to pinpoint the problem, but it can take some good amount of time as this is a complex debugging activity.

Enjoy

Andi
[ONE Original Android Development] NeGriTa79:
I was going to write last night, then I fell asleep ... with the new updates cm ... also operate the video now ... tried the new kernel AK and that's fine ... now I put it to download Beta7 .. .

Thank you and I'm sorry about last night ...
[ONE Original Android Development] andip71:
Yes, with beta7 it is also fine again.

I have to apologize to you. But I never dared even to think, CM team is crazy to break this functionality ever in this way.

All good :)

Andi
[ONE Original Android Development] NeGriTa79:
The important thing was to settle ... and in the end everything went well ... I ask you to understand me because I write and I read through the google translator ... and sometimes it does not translate well and I have to try to understand ...

Now finish the test with the new version Ak 74 ... and then get back your kernel ... since the beta 2 or 3 I could do no less than 3 days without charging the phone.

Thanks again !!!!
[ONE Original Android Development] AES256thetic:
This is a question more about the Boeffla Config app, hopefully not too off-topic.

Is there a way to disable the "Applying Settings" screen, even only when triggered via intent from Tasker?

I am hoping to toggle between "low power" "normal power" and "high power" (for example if the screen has been off for a while, slow everything down, then speed up next time the phone is interacted with, or maximise performance for certain games). I have the intents working correctly, but the pop-up is annoying if they get triggered frequently. The toast by itself is enough information.

No worries if not, not exactly a major issue to focus on :)