yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] andip71:
This is really bad, have the kernel ready since yesterday, but can't test it. Hate that and need to try and patch the ota file later, maybe I get installed then.

But first I need some fresh air to get rid of some Wodka "impact" ?

Andi
[ONE Original Android Development] andip71:
Finally can test...

Finally managed (with lots of work) to upgrade my dev OPO to YOG7DAS2K1, so I can test the new kernel for this rom version now...

If I do not find anything bad till tomorrow, you will get it.

Thanks to the guys that gave me the boot.img, that speeded up things considerably.

Cheers

Andi
[ONE Original Android Development] MMWolverine:
Hi, Andi. I wish you a successful and happy New Year 2016. Thanks for the time spent building great kernels! :good:
[ONE Original Android Development] andip71:
CM13 kernel update

Hi all,

maintenance update for the CM13 kernel - "happy new year edition":

Version 5.0-beta19

01.01.2016

Note: You are

strongly adviced

to use CM13 nightly of 30.12.2015 or newer

Update: Updated with latest official CM kernel commits as of 01.01.16, 11am CET

Update: Ramdisk updated to official CM13.0 nightly version of 01.01.16

Enjoy and happy new year

Andi
[ONE Original Android Development] josip-k:
[MENTION=947981]Lord Boeffla[/MENTION] i have a non related question, you said you use OPO as your daily device. And you said you managed to update COS on your dev OPO. Does that mean you have two OPOs? :P
[ONE Original Android Development] ZaneZam:
from his signature :

not that up-to-date but answers your question ;)
[ONE Original Android Development] andip71:
Yes, I have one as daily driver and one for development.

And we have another one in our household, my wife has an opo too.

Andi
[ONE Original Android Development] josip-k:
Awesome. Seems like you really love this phone. How come you don't have any newer ones? I thought you had an op2 too. And i used your kernel on an s5, do you use any of the other phones?
[ONE Original Android Development] :
And you have OP2 as well ... I'm trying to get in touch with Oneplus to make you their brand ambassador :p
[ONE Original Android Development] andip71:
In fact I have newer ones... OP2 :)

Andi
[ONE Original Android Development] andip71:
COS12.1 YOG7DAS2K1 Kernel update

Hi all,

finally, as two pre-testers and myself did not find any apparent issues, here we go for the specialized COS12.1 YOG7DAS2K1 kernel.

Version

4.2-beta1 stable

02.01.2016

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

Update to be compatible with latest COS firmware YOG7DAS2K1

Ramdisk updated to rom version COS12.1 YOG7DAS2K1

Enjoy

Andi
[ONE Original Android Development] jgcaap:
pois, o melhor é que fique resolvido! benvindo!

The best is that is solved. Welcome!
[ONE Original Android Development] vikrant82:
On to Boeffla bandwagon. Thanks and looking forward to this.

Quick question on our hotplugging engine - Are we using mp-decision ? If yes - in hotplug settings on Boeffla app we have various profiles. What's happening in Optimized profile ?
[ONE Original Android Development] anybuddy:
As always, have a look at the changelog ? See Post 559 from Andi.

--------------------------------------------------

Gesendet von meinem Schinken

ROM: | CarbonRom | Kernel: | Boeffla-Kernel |

If I've helped you, please press the Thanks Button!
[ONE Original Android Development] ZaneZam:
yes we are using mpdecision here and basically on optimized hotplug profile all cores execpt one will be offline during "idle" times, this might save some juice then ;)
[ONE Original Android Development] Cris7ianO:
Well thanks mate :thumbup::D

Sent from my Bacon
[ONE Original Android Development] Roulianooo:
Hi Lord,

just to say , beta8 is impressive.

My one is up since 8 hours , 1 hour SOT and still 80 % batt :p

Zzmove optimal / fiops

Good job !:D
[ONE Original Android Development] vikrant82:
Thanks! Good to know. Though I wonder what's better - One core @ 1728MHz or two cores @ 960Mhz. I guess the former. But then it becomes subjective if I compare 1 [MENTION=5214291]176[/MENTION]8 to 2@1267 let's say. I know for sure higher voltage means even higher power (quadratic relationship).
[ONE Original Android Development] andip71:
This is all theory, and in theory you are right.

But reality is many times different, so I guess you should try and let us know ☺

Andi
[ONE Original Android Development] Aavion:
my testing so far:

- no noticeable performance decrease using optimized hotplug profile

- no stuck cores as far as i can tell

- slightly better power consumption
[ONE Original Android Development] DjDiabolik:
Simply question for a simple value... reading on changelog here:

I have recently flashed this kernel on my 1+1............... and i have VERY SERIUSLY DUBS about this strange value:

I have need to charge by AC my 1+1 last night....... i have notified a VERY FASTER CHARGED than all previous charged whit my 1+1!!! It's pass from about 15% to 100% in less a ONE HOURS !!!!! YEAHH ! It's very faster now!! But it's very strange!!

Reading about this value you have lowered this value from stock 2000mA to 1500mA............... if it's correct this:

A higher value will about a load faster...... whit 1500mA i was think to obtain a LOWER SPEED for load.... but it's happened exactly the opposite value............. at this point i have so many dubs about this value..... how it's works ?!?!?

And if it's works ?!??! I need absolutely to know about this value because i don't want to destroy my battery of my 1+1..... i hope i can obtain this explanation really fast :)

Thanks in advance......

P.S.

Sorry for my english... but i'm italian.......
[ONE Original Android Development] SaschaKH:
You mix things up. 1000mA is from the Samsung Galaxy S3. 2000mA is the charging rate of the OnePlus One. It might be that the instructions or the FAQ should be updated now.

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] gianton:
Just got my OPO today, unlocked bootloader, rooted it and flash 2.0 b8 on stock XNPH38R. Running it with stock settings but will try different setups after a few days. Touch wake is not working the setting is greyed out, is it disabled by default?

Thanks for your work!
[ONE Original Android Development] andip71:
Correct, I would need to change the documentation to also cover for the OPO.

By the way --- it seems, the standard charge rate on the OPO is as follows:

- wall charger: 900 mA

- usb charge: 500 mA

So, in order to be same as stock loader, put the values to these configuration in Boeffla-Config.

However: As I do fully understand, some people might be concerned about charging the battery too fast and maybe choosing wrong charge currents etc, I will put an important enhancement to my charge control implementation soon:

With next kernel beta, you can advice the charging logic to use stock logic again by setting the charge rate to 0.

So 0 triggers stock loading logic, everything else uses the configured charge current.

I will explain more when it is there.

But I decided to give the chance to fall back to stock implementation, especially as we cannot easily replace the battery of the OPO. So it is up to everyone to decide in future.

Also, to cover for the not so experienced users, the default for charge control will be stock in future. Then it is up to the users to move this to faster change rates.

Touch wake (or better double-touch-to-wake) is standard functionality of CM11(s) on the OPO. So there is no need to configure that anymore in Boeffla-Config.

Andi
[ONE Original Android Development] gianton:
I know that thanks, I have DT2W in ROMs settings. But I am talking about touch wake in a single tap after the screen goes off by itself and it returns in the last screen/app. Yank555 kernels have this option, where you can set the time that goes completely off.
[ONE Original Android Development] andip71:
Yes, I know... my S3 kernels had that as well.

For the OPO, I am not planning to implement single tap touch to wake, I think the double-tap-to-wake makes more sense.

So, it is greyed out because this specific feature is not available in the OPO kernel.

Andi
[ONE Original Android Development] andip71:
To answer your question very simple:

Put the AC charge slider to 900, and the USB slider to 500. Then you have stock values (based on latest investigation I did this morning).

However, also read my post above: I will give you the chance to completely bypass my charge control and use 100% stock logic if you prefer so. It will be in next beta version.

Andi
[ONE Original Android Development] andip71:
Hi,

as said before, it seems I have to correct this to stock charge rate for AC chargers is only 900 mA.

Latest investigation on latest kernel code done this morning confirmed that.

So: All that are concerned about lifespan of their battery, reduce the charge rate down to 900 for AC charger.

Next beta will default to stock logic automatically.

Andi
[ONE Original Android Development] gianton:
OK thanks mate.
[ONE Original Android Development] Velkam:
How did you make the investigation? I am sure that at least stock charger is charging at ~1800mA rate (if all requirements are met)
[ONE Original Android Development] Aavion:
andi? when i calculate an average charging current (0-100% in ca 80 mins with stock 38r debuggable kernel), then 900mA doesn't seem to be correct ;)

3100mA × 3.6V = 11.16W

11.16W ÷ 5V = 2232mA

@ 2232mA average, a full charge would take excactly one hour.

@ 900mA average, a full charge would take 149 minutes, so more than two hours...

looking at my observation (~80 mins), the average charging current would be around 1674mA. given the fact, that the average current is always below the nominal current, i'd say the stock current has to be between 1800mA and 2000mA...
[ONE Original Android Development] :
Thanks!

I'm still waiting for the full zip :(
[ONE Original Android Development] atulclassic:
can we overwrite 4.1 stable version directly or need to flash whole COS firmware again?
[ONE Original Android Development] andip71:
If you did not update your rom to YOG7DAS2K1, then you should stay on stable kernel.

If you updated already to YOG7..., you can just overwrite with latest beta kernel.

Andi
[ONE Original Android Development] infatality:
Though it's not recommended.. But I loved living on the edge.. It's works pretty well..
[ONE Original Android Development] RajRockyBalboa:
Facebook Video errors

Hi [MENTION=947981]Lord Boeffla[/MENTION], I am using the latest COS 12.1 beta with the updated COS build (YOG7DAS2K1). This is my favorite kernel for a long time. Just a glitch, many facebook app videos do not play on Boeffla. I checked with the stock kernel and all is fine. Can you please check the same.
[ONE Original Android Development] cloudx720:
Videos play fine just tested :)
[ONE Original Android Development] RajRockyBalboa:
Try the below videos please. It's just 2 samples. Will publish others

https://m.facebook.com/story.php?story_fbid=1102531756432066&id=833045873380657

https://m.facebook.com/story.php?story_fbid=1381437771912587&id=120674037988973
[ONE Original Android Development] cloudx720:
Film trailer plays fine yeah
[ONE Original Android Development] andip71:
Tested in Facebook app, playing well here.

Andi
[ONE Original Android Development] RajRockyBalboa:
Thanks...Playing fine with the latest beta...sorry...I erred :) was running on Boeffla COS 4.1 stable earlier.
[ONE Original Android Development] Notor1ouS-:
a question to boeffla:

did you ever notice the difference in battery life compared to KitKat? lollipop/MM have clearly problems getting over 4-5h SoT.

KitKat gets easily 8h SoT.

is this fixable with kernel tweaks? or is it a problem OS wise?

nobody is rly talking about that problem...
[ONE Original Android Development] andip71:
Yes, KitKat was much better in terms of battery consumption.

It is quite widely known, the culprit is in the rom. We cannot improve much more on kernel side afaik.

Andi
[ONE Original Android Development] infatality:
Facebook app video has a known issue with video gitch.. Try updating to a newer version.
[ONE Original Android Development] anuraag.neo:
How did you get that # su indicator icon on COS?
[ONE Original Android Development] deprofeet:
Can't always replicate, but with kernel 4.2-beta1 for YOG7DAS2K1, booting the phone takes a very long time and sometimes even hangs at the boot animation. Putting the stock kernel back solved the issue...
[ONE Original Android Development] andip71:
No boot issues here so far.

Maybe something is conflicting.

Andi
[ONE Original Android Development] andip71:
On oneplus forums, there is a zip that enables internal superuser. Don't have the link here though...

My kernel supports that, so you don't need SuperSu anymore.

Andi
[ONE Original Android Development] jejecule:
Cm commit is here : http://review.cyanogenmod.org/#/c/83970/4
[ONE Original Android Development] anuraag.neo:
Probably this one?

https://forums.oneplus.net/threads/flashable-zip-cm12-enable-integrated-superuser.297089/
[ONE Original Android Development] andip71:
Yes, exactly.

And latest version there also works for Yog7das2k1.

Just flash this zio, then straight after that Boeffla-Kernel, reboot, enable root in developer options, done.

Andi
[ONE Original Android Development] deprofeet:
Hi Andi, what could be conflicting? If I would know in what direction to look, I might be able to track the issue down. My ROM is pretty much stock, apart from root.

Other than the current issue, I've been using your kernel with great pleasure on several OPO ROM's and on a Samsung Galaxy S5.

Thanks for a great kernel!!! :)
[ONE Original Android Development] andip71:
I don't know as I don't know your fonfig, when you did a clean install last time, apps, mods, scripts you use.

It is kinda hard to say without any more info. There is not a "general" thing that can happen, it must be something really very specific...

Andi
[ONE Original Android Development] atulclassic:
Having random freezes y'day..device in sleep mode for about 2hrs and didn't wake up with double tap or power button.

Running cos12.1.1 with 4.2 beta 1..log attached

Just for information..xposed v78, greenify installed
[ONE Original Android Development] andip71:
Well, with xposed you already disqualified from getting my support :D

Pls refer to OP.

On the other side, I can just state:

3 OPO devices, running the combo since 31.12.15 already, two of the devices are daily driver phones = heavily used... no single freeze, reboot or other issue.

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

Good morning,

new week, new start, with an update to the CM13 kernel.

Version 5.0-beta20

04.01.2016

Fix: GPU frequencies not sticky across reboots for some users

Update: Ramdisk updated to official CM13.0 nightly version of 04.01.16

Enjoy

Andi
[ONE Original Android Development] ManuBBXX:
Hello everyone !

First, Thanks Lord boeffla for this wonderful Kernel ! Running the CM12.1 version with Exodus ROM and it's smooth like butter :)

I want to upgrade to Marshmallow with Sultan's CM13 ROM

Is this Kernel compatible with Sultan's CM13 ROM ?
[ONE Original Android Development] cloudx720:
Nope sorry.
[ONE Original Android Development] ManuBBXX:
Thanks for the quick answer !

So Wich Android6 ROM do you guys recommand ?
[ONE Original Android Development] cloudx720:
imo I would stay with cos12.1.1 or cm12.1 and wait for the stable snapshot of either cos13 or cm13 :) just my 2cents ?
[ONE Original Android Development] Renosh:
Slimsaber has been the best MM ROM I've tried so far but I'm back on COS12.1.1 with Boeffla cause I got tired of flashing ROMs all the time
[ONE Original Android Development] :
[MENTION=947981]Lord Boeffla[/MENTION] THANKS!

https://github.com/andip71/boeffla-kernel-cm-bacon/commit/96f7c7fca4c41b17479f688bc73f25af55a62ede
[ONE Original Android Development] DjDiabolik:
Apparently not as been released "ufficially"....... :) I have read in past reply you have instaled latest cos12.1.1 by OTA incremental ? I try to watch now on xda if it's already present a unofficial ways to flash a full rom and after i can flash your last beta for my opo :)
[ONE Original Android Development] hellkun:
Just flashed this kernel to Temasek(non-CAF), it's smoothier than the CAF version. No offense to Vivek, but it's just like some post here said, CAF doesn't perform well on MM as on Lollipop, at least for now.
[ONE Original Android Development] ManuBBXX:
Well, sorry if thid question has already been asked, but I can't find the double tap to wake option.

I run since 1 hour the latest Boeffla CM13 version with NuclearROM.
[ONE Original Android Development] vicky2131:
[MENTION=947981]Lord Boeffla[/MENTION] hi andi, flashed latest beta on 2K1 and everything is rock solid. Thank you.

I just need a small doubt cleared from you. Is doze working properly for you nowdays on cm? Before new baseband release on cm13 i used to get 5 to 10% loss of battery over night. Actually it should not be more than 2% if doze works. Does it work well nowdays?
[ONE Original Android Development] andip71:
I cannot speak for that rom, but official CM and COS have it in the rom settings under gestures. There is no specific kernel setting for it, as it comes with the rom already.

Good question. I would be very surprised when Doze is already properly implemented. I doubt it is, but never investigated further on it.

Andi
[ONE Original Android Development] deprofeet:
I flashed again and this time the kernel runs fine... strange ;)

I noticed that when I started Boeffla-Config the first time, "bfq" had been set as scheduler (I think it was "row" in the previous kernel). Is there a specific reason for this?

Curious where the default values (no profile loaded) initially come from, are they being set by the kernel?
[ONE Original Android Development] andip71:
The default settings come from the kernel. And CM team changed between row, bfq and fiops in the past months.

And yes, currently on Bacon CM13 the default scheduler is BFQ, as per config:

# CONFIG_DEFAULT_DEADLINE is not set

# CONFIG_DEFAULT_ROW is not set

# CONFIG_DEFAULT_CFQ is not set

# CONFIG_DEFAULT_FIOPS is not set

CONFIG_DEFAULT_BFQ=y

# CONFIG_DEFAULT_NOOP is not set

CONFIG_DEFAULT_IOSCHED="bfq"

Andi
[ONE Original Android Development] josip-k:
[MENTION=947981]Lord Boeffla[/MENTION] i have a stupid question, but i think you can help me. I am currently trying to make an extreme battery profile with your kernel, and i want it to be stable as much as possible. It's stable with -75uV and max freq. Set to 1190Mhz, and gpu set to 330Mhz. But i can't decide wich governor would suit this config. Wich would you recommend? I'm running intellidemand, but i don't think that would be the best one since it's optimised for faux's hotplug driver.. And i don't know if smartmax, smartmax_eps and ondemandplus have some advantages..
[ONE Original Android Development] andip71:
Well, it is quite simple: If you want highest stability, I would recommend interactive governor as this is the stock governor and therefore absolutely stable.

As for the rest, I am not a fan of undervolting, so will not comment the rest :)

Andi
[ONE Original Android Development] deprofeet:
Thanks for the reply, Andi!

Is BFQ also the default scheduler for COS12.1 YOG7DAS2K1?
[ONE Original Android Development] andip71:
No, according to kernel config it is noop.

But the rom could overwrite it as part of the ramdisk. I have no access to this information right now.

Edit: it is bfq too, it is configured to bfq in the ramdisk.

Andi
[ONE Original Android Development] josip-k:
I know you said you aren't a fan of uV, but my question was wich-by your means would be the most battery frendly governor(obviously not powersave). I know that interactive is the most stable one.
[ONE Original Android Development] andip71:
There is no "best" or battery friendly governor. Everything is dependent on your usage pattern.

Maybe zzmoove with a battery profile is what you need.

Really hard to say.

Andi
[ONE Original Android Development] ManuBBXX:
Smartmax rocks a lot !!

Extreme smoothness, and nice for battery I think
[ONE Original Android Development] andip71:
CM13 kernel maintenance update

Good morning folks,

CM released some changes in the CM-13 branch, so here you go for an updated Boeffla-Kernel.

Version 5.0-beta21

06.01.2016

Update: Updated with latest official CM kernel commits as of 06.01.16, 6am CET

Update: Ramdisk updated to official CM13.0 nightly version of 06.01.16

Enjoy

Andi
[ONE Original Android Development] Hilmesh:
smartmax or smartmax eps???
[ONE Original Android Development] Stroky:
If you want to gain Performance over Battery then smartmax if you want to save battery then use smartmax eps!
[ONE Original Android Development] Jole7:
Smartmax
[ONE Original Android Development] akz1x1:
CAF Rom compatibility

Will there by support for caf based roms in future ?
[ONE Original Android Development] andip71:
No.

Andi
[ONE Original Android Development] kurtextrem:
Honstely, there is little difference in responsiveness. smartmax uses slightly higher CPU freqs, while smartmax_eps stay low most of the time. But that staying low is not noticeable.

I guess if you notice hangs, change your I/O scheduler first. If you still experience hangs, switch to smartmax.
[ONE Original Android Development] roxdragon:
Hi i nave a galaxy s5 900f with cm12.1

1. What's the correct versione for me? COS or Cm? Whats the difference?

2. Can i flash this using twrp?

Thank you
[ONE Original Android Development] andip71:
My friend, you are in the wrong thread. You are in the kernel thread for OnePlus One...

Here you go:

http://xdaforums.com/galaxy-s5/orig-development/kernel-boeffla-kernel-1-0-beta1-23-03-t3062078

Andi
[ONE Original Android Development] roxdragon:
Ops sorry :)
[ONE Original Android Development] pilspeda:
Hi,

while using AK Kernel on 5.1.1 I have now switched to Boeffla for CM13.

However: I always used the following screen color settings:

How can I set these settings in Boeffla config app ?

In Boeffla config app I can change the following settings:

- Color

- Saturation

- Hue

- Display Value

- Contrast

The "Min"-Setting is somehow missing, or am I missing a corresponding value ?

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

Next time you make a beta for COS can you change the naming scheme to reflect the newest version i.e. COS 12.1.1 instead of COS 12.1

Would be better for users to be able to tell at a glance which is the correct one
[ONE Original Android Development] andip71:
Yup, good idea, I completely missed that we have 12.1.1 now :)

Andi
[ONE Original Android Development] stab244:
Would like to know this as well. Also would like to ask if it would be possible to do per app profiles with the app at some point in time.
[ONE Original Android Development] lchiocca:
I don't think that Andi would want to change the app to be able to do this. As far as I understand his motivation: The app should not run in the background. But fear not, there is a simple way of doing what you want if you have tasker (or any other tasker equvalent tool). You can send an intent (something like a message) to the app to change profile when an app starts.
[ONE Original Android Development] stab244:
I see. I used to use that but its just easier to use an app. Guess its time to start poking around to find the files I need to write to.
[ONE Original Android Development] andip71:
As lchiocca already explained: No, I will not implement something like that.

My app can maintain multiple profiles with multiple settings and you can switch them very powerful (more powerful than any other per app functionality) by using apps like tasker, llama etc. Any app that can send an intent can be used.

Very well said, many thanks for this!

Andi
[ONE Original Android Development] rolarocka:
Sorry if this has been asked before but the selinux status doesn't stay unchecked after each reboot, I need it to stay permissive but it's always strict after a reboot. Ty

Gesendet von meinem GT-S7275R mit Tapatalk