yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] andip71:
Sorry, but reboots or lesser reboots... this is not an option. You should have Zero reboots, or not more than one a month.

So if you even have reboots with another kernel version, it does not make any good.

COS12.1.1 is the most stable version for me ever, together with my kernel. So believe me, something is odd.

Also watchdog messages caused by any Facebook app on stock kernel are not correct. I also use Facebook app, zero issues (ok, I greenify it to make it not consuming cpu in the background).

Try resetting your configuration (flash reset script in recovery), wipe dalvik and cache, install beta3.

There is no reason why it should not work stable for just you on earth :)

Andi
[ONE Original Android Development] NeGriTa79:
[MENTION=947981]Lord Boeffla[/MENTION] you can have your kernel version CAF ????
[ONE Original Android Development] TorchaOne:
What build you have, what radio? 241 (the old one) is bad for someone, like to me, new c7 works just fine, but for some ppl calls fail (t-mobile).
[ONE Original Android Development] andip71:
Can you please read the OP again, especially section "This said, I will definitely NEVER implement:" ?

Then you know the answer :)

Sorry

Andi
[ONE Original Android Development] Aavion:
as i told you, the watchdogs were solved by updating the app... but there're many users (even friends of mine) complaining about phone lags, freezes and reboots using one specific version of the facebook app, even with different phones by different brands (sony, samsung, huawei), so i was not the only one :D

will try that again ;)

my radio is the c6 one shipped with the JL factory image, didn't know about any newer baseband :D

Gesendet von meinem Schinken.
[ONE Original Android Development] TorchaOne:
Aah, I did not notice that you are using some ancient SW.
[ONE Original Android Development] Aavion:
ancient?

i'm on K1 now, but there wasn't a baseband update within the ota package :D

Gesendet von meinem Schinken.
[ONE Original Android Development] Renosh:
? they actually reverted the new c7 baseband in CM13 so now everyone is on the 241 modem. So his ancient theory is dead in the water.
[ONE Original Android Development] atulclassic:
Me too facing these 'unrecoverable blocks error' but no random reboots..instead my phone black out and i have to long press power button to reboot
[ONE Original Android Development] andip71:
On cm13?

Cm13 is indeed not yet 100% stable from time to time.

But on cos12.1.1 there is no excuse, here everything has to be stable.

And it is for me on two daily driver devices (me and my wife).

Andi
[ONE Original Android Development] TorchaOne:
As stated, did not regon that u were using some 12.1 sw, that is ancient. I tried COS12.1.1 for 2 days last week and I puked a lot, awful, but I did not had any reboot with boeffla.
[ONE Original Android Development] Renosh:
Sadly I have to report the same. My phone froze while at the dialer and was totally unresponsive, had to force reboot. It was while using Beta 2 for COS12.1.1 my config at the time was Smartmax, Optimized, no UV. Only happened once (yesterday) so didn't think much of it
[ONE Original Android Development] andip71:
Use interactive governor for a test.

The old legacy governors are always a suspicion of causing instabilities.

Maybe I never have issues because I always use interactive (which is stock gov so by nature the most stable one).

But this reminds me again: people asking for help here must (!) explain their setup first. Otherwise this is just fishing in the dark and therefore a complete was of time.

Thanks for respecting that.

Andi

Andi
[ONE Original Android Development] atulclassic:
Using COS12.1.1 S2K1 here with interactive
[ONE Original Android Development] andip71:
S2K1 ?
[ONE Original Android Development] atulclassic:
build no.
[ONE Original Android Development] andip71:
Ok, I use the same.

Andi
[ONE Original Android Development] bombadier:
Off topic I know but open supersu and untick Mount namespace separation reboot and backup should work, was getting a insufficient storage error until I unticked that and rebooted, 2.67 working fine

Tapatyping fae the bacon
[ONE Original Android Development] udo 240:
Hi. I am on the actual kernel and app. Allways i changed the govenor to zzmove via presets or changing it manually and close the app, it ll change to default govenor interactiv /standard. Anyone knows something about the reason for?
[ONE Original Android Development] atulclassic:
wipe app data and restart app
[ONE Original Android Development] andip71:
Are you really using Boeffla-Config app, or another one?

Andi
[ONE Original Android Development] udo 240:
Of course!
[ONE Original Android Development] andip71:
Did you allow (in app settings) other tasks like the rom to overwrite the governors?

There is a setting for it.

Andi
[ONE Original Android Development] udo 240:
Hi Andi and thx. You mean this? No... I have Not
[ONE Original Android Development] cloudx720:
These random lockups are indeed true with cos12.1.1 had 1 with boeffla kernel, flashed stock kernel and I have had two random lockups where phone becomes extremely slow and have to force reboot. Imo something is wrong with latest cos12.1.1 update other people having same problem it seems seen on oneplus one forums.
[ONE Original Android Development] udo 240:
I flashed the 24er kernel another time via twrp. Nothing changed. I can t change the govenor. All changes were Not restored and changed into default settings
[ONE Original Android Development] MMWolverine:
No problems with governors here, but I've noticed RGB values won't stick. YOG7DAS2K1, 4.2-beta3.
[ONE Original Android Development] Aavion:
often, this is related to facebook app.. on nearly every phone, but only some are experiencing these problems... try updating to facebook beta until they figured it out... i also got a response from their support telling me, that this is a known problem and they're working on it... (some kind of compatibillity issue together with other apps which offer facebook login via the facebook app)

dunno if this may be the cause of your problem, but worth to mention ;)

[MENTION=947981]Lord Boeffla[/MENTION] I reflashed kernel via twrp (not via your app as usual) and until now, everything seems fine :)

Gesendet von meinem Schinken.
[ONE Original Android Development] andip71:
Then it is getting spooky.

Hm, but then it must have some other dependencies. Because I never had one since I upgraded to COS12.1.1.

Is it only the governor or also other settings not sticky?

How does it behave... you change the governor, close the app, start it straight away again and the governor is reset?

Or is it after a reboot? Or over some time?

Please create a debug info file in Boeffla-Config (action menu, last item) and mail it to my support address: support@boeffla-kernel.de

I will have a look.

Andi
[ONE Original Android Development] Renosh:
I saw some prompt earlier today when I tried to change voltages, it said not Default or something like that and blocked me from making changes. I closed the app and restarted it then it allowed me to change the values after but I couldn't do it while that warning was in effect

Forgot to add 2.2.21 Boeffla Config using latest beta 3. Never happened on previous versions of the app
[ONE Original Android Development] andip71:
CM13 kernel maintenance update

Hi folks,

before the weekend, one last update to the CM13 kernel. A pure maintenance update though.

Version 5.0-beta25

22.01.2016

Note: You need at least Boeffla-Config V2 in version 2.2.21 or higher for latest features !

Update: Updated with latest official CM kernel commits as of 22.01.16, 9am CET

Ramdisk updated to official CM13.0 version of 22.01.16

Enjoy

Andi
[ONE Original Android Development] udo 240:
Hi Andy, it works for me :)

I restored a nandroid backup and flahed the kernel (V25) and the app once again. I don´t know what it has been. Thx a lot for your great work!!!!
[ONE Original Android Development] twowheeler:
Have had a few freezes and reboots on beta 3 with the latest cms. Manly when I was typing. Rest of the kernel is great.

Using zzmoove batteryplus if that makes any difference

Verstuurd vanaf mijn A0001 met Tapatalk
[ONE Original Android Development] andip71:
Cool. Whatever it was, we will not find it out anymore.

Yes, try interactive for some days, or a different zzmoove profile.

I am sure you have 100% stability then...

Andi
[ONE Original Android Development] infatality:
[MENTION=947981]Lord Boeffla[/MENTION] Could you take a look at your apps.. There's seems like font size difference on both of my opo with the same configuration. One looks smaller another seems larger.
[ONE Original Android Development] xlollomanx:
You have a different DPI setting between your phones?

Sent from my Oneplus One
[ONE Original Android Development] infatality:
Nope.. Both are on same 480 dpi and 85% font size..
[ONE Original Android Development] andip71:
The app does not set font sizes itself, it takes the font sizes from system.

So I do not know what I should be looking now, sorry :)

Andi
[ONE Original Android Development] infatality:
Probably I found out how to replicate..

Change theme to material and force English back twice for it to restart the apps.. The font will be big after restarting the apps.. [emoji6]

I did an clean uninstall and clear all data, the font was fine until I change the above setting

..
[ONE Original Android Development] andip71:
I cannot replicate that here.

Really sorry.

But... Just don't do that.

Delete app and install it again, this will reset everything, also hidden stuff. Just an idea.

Andi
[ONE Original Android Development] anagramgenius:
[MENTION=947981]Lord Boeffla[/MENTION], was the kexec-hardboot patch removed in cos12.1.1 v4.2beta3?
[ONE Original Android Development] andip71:
No.

Not removed and not changed.

But I never use it myself.

Andi
[ONE Original Android Development] MMWolverine:
Actually kernel isn't recognized as patched anymore. Maybe outdated MultiROM issues finally caught up with the rest of us. :rolleyes:
[ONE Original Android Development] andip71:
Well, I cannot say more, I never even tried multi rom myself. Just can say it should be in.

I can verify on Monday to make sure I did not forget to take it in during last rebase.

When did you last time use multi rom with my kernel? Do you roughly know?

Andi
[ONE Original Android Development] anagramgenius:
Beta 2 can run multirom. But beta 3 can't.
[ONE Original Android Development] DjDiabolik:
Lol.. it's simply reply.... I had read that the stock value of this value it's 2000mA..... :) If the stock value it's 900mA now i know because at 1500mA we can obtain a lower charging times....

Great explanation........... at this point i don't know it's safe to leave it a 1500mA or it's safe to come back to 900mA.......
[ONE Original Android Development] andip71:
I put a hook in the function of the stock charging logic which sets the mA charge rate. And via this hook I found a stock wall charger rate of 900 mA.

It surprised me too, but also from a mathematical point of view it seems to be valid.

I charged my phone this morning from 14% to 100% which took 2 hours and 58 minutes = around 3 hours.

The OPO battery has a size of 3100 mAh, so the almost 3 hours charging to pump in the around 3000 mAh assumes a charge rate around 900-1000 mA.

So far my observations...

Andi
[ONE Original Android Development] andip71:
Well, this is a question which... I cannot answer. Nobody knows what the headroom in the OPO battery still is.

However, next kernel beta will default the loading logic to stock, so everyone is as safe as possible.

Then it is up to everyone to charge faster or not. I think, that is a fair deal :)

Andi
[ONE Original Android Development] Aavion:
from the mathematical point of view, battery capacities are always calculated at 3.6 volts.. carging rate is 5 volts.. see my maths on the previous page :)
[ONE Original Android Development] andip71:
Math or no math... :)

The hook in the function says, the stock charge logic (in my case this morning) set 900 mA.

And the charge took around 3 hours with stock kernel.

Or would you say, a full charge cycle with normal AC charger on stock kernel goes faster for you?

Andi
[ONE Original Android Development] andip71:
But nevertheless:

Next beta version gives everyone the option to use full stock charge logic - OR - apply any charge rate someone wants.

And it will also show, what is being requested by the charging logic and what actually flows.

Andi
[ONE Original Android Development] Velkam:
Are you using the stock charger and cable? Because according to my observations charging rate using stock charger and cable is:

~1800mA while screen is off

~1200mA while screen is on (probably to avoid the overheating)

~800-900mA on most third party chargers or with thin USB cable.
[ONE Original Android Development] andip71:
Nope, used my HP Touchpad loader and the cable from there.

Will redo with stock charger again for next cycle.

But interesting to know: Where do you have your charge current values from?

Andi
[ONE Original Android Development] Aavion:
excacly what i've observed... (and calculated)

as said before, around 80 mins for me...

i've calculated mine using android's stock calculator :D see my post on the previous page
[ONE Original Android Development] andip71:
Allright, then it might have been due to my charger here.

Because, long time ago when I implemented the charge logic, I am sure I have seen 2000 set by the stock logic. So was surprised as well when I saw 900 only this morning.

We will find out with new beta, as this allows you to select either stock charger logic, or any custom charge rate. And it will displayed with what charge rate the charge circuit will be programmed with finally.

Andi
[ONE Original Android Development] Velkam:
I am using 3C Toolbox (aka Android Tuner). To set up the monitoring: Battery manager>Settings>Battery>Monitoring>Record all the time>on. mA retrieval method > Reverse mA
[ONE Original Android Development] Vonnegut:
I admit my ignorance...anyway, the charger's label says that it can charge up to 2100mah.

3100/2100=1,476

That's about 1 hour and 29 minutes...and that's what i actually have to wait.

May you go a bit more in depth with you math?
[ONE Original Android Development] Aavion:
80 mins = 1h20m.. so only 9 minutes difference?

as i said before: average charging current is a bit lower than the set current due to technical reasons i don't want to go into too far atm.

battery capacities are always calculated at 3.6 volts, so you have a capacity of 11160 Wh -> 2232mAh@5V.

2232÷2000 = 1.116 hours.

given the fact, that the average current is lower, everything arount 1.5h is legit ;)

edit: [MENTION=947981]Lord Boeffla[/MENTION] 2000mA kommt hin. um sicher zu sein kann man auch 1800mA einstellen, da der akku meist eh nicht schneller lädt da die meisten kabel nicht mehr zulassen, ohne dass die spannung instabil wird...

---------- Post added at 02:55 PM ---------- Previous post was at 02:38 PM ----------

current set to 2000mA, you see, the actual current is lower than set (1702mA).. sometimes it's 1908, sometimes 1667.. i assume, that this behavior is the same using stock charging logic ;)
[ONE Original Android Development] andip71:
Just did a very quick test... OPO stock charger in my case was triggering a stock charge rate of 1200 mA.

So... interesting topic for the future :)

But for now I will stop commenting on it, first want to get the new kernel out so we can gather more useful information, also will check with different chargers on 3 different OPOs in the next days. I will be going on holidays this Friday morning for around 10 days, so enough time to get some empiric data.

Andi
[ONE Original Android Development] Aavion:
please make [MENTION=3279788]ZaneZam[/MENTION] provide me a linaro build for testing as soon it's ready 'coz i don' t want to miss that awesome zero-ui/scrolling stutter anymore :D
[ONE Original Android Development] andip71:
Well, thats up to Zane how quickly he can provide it.

But usually he is really fast :)

Andi
[ONE Original Android Development] magnamentis:
ampere meter

i have an ampere meter (real hardware industry standard quality ) to test things like that, if you like i can check the real thing, best probably when all the features will be available in the app to compare settings with facts. the best results i got with the stock charger, especially the cable must be special it beats all of the douzens of cables i already have by far. max i got was around 2 Ampere

i had to buy this thing because i had problems to charge enough on the motorbike since i needed an 90 degree angled micro usb which in good quality was not easy to find.
[ONE Original Android Development] Detailed:
Anybody get video recording problems [MENTION=921577]1080P[/MENTION]/4k? (AOSP camera or 11S 38R camera dont work properly). I'm on Mahdi ROM + latest beta of this kernel, everything stock. This is a near perfect kernel for me (Hotplugging cores option, OC etc.) though and definitely the fastest though. If I try to record 1080p/4K they cut off at about 3 seconds and the file doesn't even save.
[ONE Original Android Development] andip71:
Just tested on cm11s 38R with latest beta kernel, successfully did a 20 seconds video clip in 4.

I have not tested on CM11 kernel as this kernel is under heavy rework at the moment. But not sure I will be ready still today with it, not looking good for the planned update today. And from tomorrow on I am on holidays for a week.

Andi
[ONE Original Android Development] gianton:
+1 same here, no issues recording a video with CM11s 38R and latest beta.
[ONE Original Android Development] Shiningbro:
Hi boeffla, i have Problems with your kernel in all New Cm13 builds since build 17 January. My Phone reboots and the Phone is very laggie. With cm Stock kernel is all fine
[ONE Original Android Development] infatality:
Ramdom is an known issues.. Lag has nothing to do with the kernel.. It's most likely you configuration or apps.
[ONE Original Android Development] Shiningbro:
Nope, i can reproduce it. With Stock kernel is all fine. I dont use an kernel app.
[ONE Original Android Development] infatality:
Boeffla kernel is essentially an stock kernel with additional features.. I'm running cm13 with this kernel and all is fine.

Post some log and someone will look into it.
[ONE Original Android Development] andip71:
You have verified that really by switching back and forward a few times on that?

Because it could then mean, the switching off of some debug options as per newest cm standards has caused this side effect.

And it would also mean, I need to provide you a number of test kernels to find which logging option caused this side effe. Bummer, I really like the reduced debug stuff a lot...

Andi
[ONE Original Android Development] MMWolverine:
I can verify that, switching back to beta-2 MR works. I even reverted back to 15-5-2015 firmware, which is used again in cm13 nightlies.
[ONE Original Android Development] andip71:
Ok, so... when I provide you a few test kernels, would you be willing to test when the multi boot option is back for you?

As I refuse to use multi boot, I cannot take this work away from you unfortunately.

Andi
[ONE Original Android Development] MMWolverine:
Yeah sure, I'll be available tomorrow late afternoon and in the evening.
[ONE Original Android Development] andip71:
Cool. I am pretty sure I see already what change broke it.

I will do a test version asap and send you a PM. then you can test it whenever you want.

Andi
[ONE Original Android Development] Champi12301:
Hello mate. What is your Multirom config? Version of Multirom?? Versions of Cm at primary and secondary? . I tought Boeffla Kernel doesnt support multirom.

Tecleado desde mi 1+1.
[ONE Original Android Development] andip71:
This is wrong. It always supported it (untested, as I do not like and need it)

Andi
[ONE Original Android Development] MMWolverine:
Hi,

I'm using MultiROM v32L and MR TWRP v2.8.7.0 recovery, both unofficial mods. Check here... http://xdaforums.com/showpost.php?p=64837149&postcount=2985

My primary rom is always latest stock COS (12.1.1) and secondary atm ResurrectionRemix - v5.6.2 - Marshmallow 6.0.1_r10. Boeffla always had MR support and worked great thus far.
[ONE Original Android Development] andip71:
You have a PM with a link to a beta3 based test kernel :)

Andi
[ONE Original Android Development] MMWolverine:
Thanks mate, testing right now. ;)
[ONE Original Android Development] Orphee:
Hello,

I have a question, not really about kernel, but about Cyanogen OS vs Oxygen OS...

I never tried Oxygen, I like COS, but the craps like truecaller and recently cortana, I really don't like it... I know we can uninstall it, but I don't like the way it turns...

As you are building a kernel for Oxygen, I guess you tried it... Is it as good as Cyanogen ? I'm thinking about switching...

Thank you
[ONE Original Android Development] andip71:
Hi,

I think my honest answer will give you my opinion:

OOS is the reason why the OnePlus 2 is not yet my daily driver.

I do not like OOS a lot in it's current state. Many things missing and not as smooth as CM (for me).

But yes, I just installed OOS 2.1.4 on my OPO to wait for the kernel sources to be updated soon. Then I will also provide an updated kernel there. And maybe I give it again some testing on the OP for a few days.

Andi
[ONE Original Android Development] andip71:
Multi boot

Hi all,

the multi boot issues with COS12.1.1 and CM13 will be fixed in the next kernel updates, most probably tomorrow.

Thanks to [MENTION=4842497]MMWolverine[/MENTION] for the quick verification.

Andi
[ONE Original Android Development] Orphee:
I made a backup and tried OOS just a few minutes ago... started messaging app, no dark theme... wiped and restored COS...
[ONE Original Android Development] andip71:
I told you... [emoji1]

Andi
[ONE Original Android Development] mrhamed:
do you have plan to add vibration intensity?!
[ONE Original Android Development] Champi12301:
Uoaaa... The multiboot is breaking my head right now. Since the firmware update of Cm13 it broke my Roms and flashed a Cm13 primary without multirom working. Now i am with Unnoficial Cm13 Caf, with lightening, but with problems with the secondary. Andi, this New kernel update Will work with Cm13 as primary? If yes tell me i want to test and make a fresh a install of a non Caf based Rom, and your Kernel. It always give me the Best results. [emoji106]

Tecleado desde mi 1+1.
[ONE Original Android Development] andip71:
I never ever used multi boot once, I simply don't like it.

I just can confirm it is broken in both cm12.1.1 and cm13 Boeffla Kernels.

And it will be fixed again with the next version of both kernels.

Hope that helps

Andi
[ONE Original Android Development] ch-vox:
Hi Andi,

I am using zzmove governor with battery yank profile and I experienced freezes with reboots too.

as you said I'll try interactive governor, but will you fix this in the next release ?

thank you anyway for all your work