yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Cris7ianO:
Hey after flashing latest beta and configuring kernel with boeffla config app wanted to go back to stock kernel. I tried dirty flashing the ROM and even clean installing but after using this kernel with the app other kernels are behaving strange, e.g. mp decision only has one core online. Is there something i have to do to get my phone totally clean for next kernel? Maybe the app inserted something that I have to remove :) please don't take this as an offense maybe I just missed something :)

Sent from my GT-N8000
[ONE Original Android Development] jgcaap:
Português?

Basically do a dirty flash of the rom
[ONE Original Android Development] BrunoNRG:
Sim ;) Não é que me apeteça muito flashar a rom, mas em último recurso lá terá de ser.

EDIT: Acabei de vir de uma loja Vodafone, que estava cheia de gente a reclamar do mesmo.... O problema

tem a haver com uma antena local e afecta as zonas de Leiria, Ourém, Tomar, Entroncamento e Torres Novas...

As a last resort I guess that's my only option...

EDIT: Solved, it was a local problem with the mobile network antenna. I tried the sim card a second time on the S3 and it was also not getting any network signal, did a manual search and it found all other networks except mine so, I went to a Vodafone store nearby, that was full of people with exactly the same problem, by the time I got home (10min ago) the problem had solved itself...

I reflashed beta 8 kernel, and everything is working fine again :good::good::good:
[ONE Original Android Development] andyfmking:
I experienced Sleep of Death twice today with the Kernel beta 7 on stock CM11s 38R with ondemand governor clocked at 2.5GHz with all other settings unchanged. Couldn't get a log but had to change to another kernel because of this. May be anyone knows the reason or a solutions?
[ONE Original Android Development] andip71:
Well, this sounds like the new kernel you used was probably an anykernel version?

To be 100% clean:

- delete folder /data/.boeffla (although no other kernels pay attention to it)

- delete anything in foder /system/lib/modules

- flash stock kernel (you can find on my homepage for cm11s) or flash rom all over

And no, why should I be offended? I really do not care which people use which kernel. I am not earning money with my stuff... so?

All good :)

Most likely going to interactive and not doing overclocking would help?

Or using beta8 could help...

Andi
[ONE Original Android Development] Crazy_Oni:
You have to install the app first. Download it at http://boeffla.df-kunde.de/bcv2 and install it. With it you can manage profiles.

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] dudas89:
What you are looking for is here: http://xdaforums.com/oneplus-one/general/unofficial-boeffla-kernel-profile-t2998145
[ONE Original Android Development] cloudx720:
Best gapps for cm13 guys? Micro,nano or pico ?
[ONE Original Android Development] chenrp:
1.any way to see the current charging rate? is there a build-in way to do so(or i have to install a 3rd party app?)?

2.where is the vibration intensity?

3. clean flashed CM13 temasek V1.5 (android 6.0.1) and boeffla kernel V5.0(latest so far) and everything working good!
[ONE Original Android Development] andip71:
Is this kernel related at all?

Is a rom thread question.

1) In boeffla-config overview page. other apps can only try to calculate the charge current via interpolating voltages, which is quite inaccurate. Boeffla-Config can get the data from the charging driver

2) In the roms settings, not in boeffla-config.

3) Excellent.

Andi
[ONE Original Android Development] HWAM:
I want to know if I can limit the "Android System" battery usage with a boeffla kernel on my OnePlus One? My wife has a ZUK Z1 (Lenovo) with COS12.1 (CyanogenOS) and "Android System" is using way less battery (using 1%) than my OPO with CM12.1 (last nightly 11/21). Why is COS12.1 (stock on ZUK Z1) way better with battery usage? Is it simple to revert to the default CM12.1 kernel if i want that?
[ONE Original Android Development] andip71:
To set expectations: The Android System has nothing to do with the kernel. So no kernel will help you getting better here.

It is simple to revert the kernel back, yes.

Just do a full nandroid backup in recovery first, then you can bring it back.

Also for COS12.1 I have the stock kernels to flash on my homepage.

Andi
[ONE Original Android Development] HWAM:
I don't understand why “Android System“ is using only 1%-2% Battery on a ZUK Z1 with stock COS12.1 and 10%-15% on my OnePlus One with CM12.1 nightly. Almost same circumstances. How can I find out what the problem is? My OnePlus One is using “Android System“ power in idle. I never have a flat line in idle. The ZUK Z1 does.
[ONE Original Android Development] andip71:
BetterBatteryStats app might help you to find out more about the differences.

But it is not really something for a kernel thread unless in the end a kernel process turned out to be the culprit.

Andi
[ONE Original Android Development] HWAM:
BBS is running for a few days now but all I can see is "System". Can you investigate the logging for me?
[ONE Original Android Development] andip71:
Sorry, I cannot analyse individual logs, have no capacity anymore for that, too busy.

Maybe someone else in the thread can volunteer.

Andi
[ONE Original Android Development] vicky2131:
Yes same issue on Cos12.1 latest build on my oneplus one. But its not related to kernel. All my friends on stock too have this issue. Android system gets drunk at times and rides on the battery :D lol

Anyway end of OT!
[ONE Original Android Development] magnamentis:
wrong thread but since i'm already at it, those names describe the amount of gapps the package contains, minimum, few, medium but then they are from the same source, hence they are all equally good but you have to decide whether you prefer to install a small or a larger package.

---------- Post added at 07:18 PM ---------- Previous post was at 07:16 PM ----------

this is the consumer but not the trigger. you need a monitoring app that shows you the triggering app which triggers tasks that are grouped in system or sometimes in kernel. Wake Lock Detector would do that quite well and easy to read while there are others of course.
[ONE Original Android Development] plantator:
Have any one worked gsam battery monitor? simple gsamworks but when I install root companion it goes laggy and unstable.
[ONE Original Android Development] kalapapa:
I suggest you try the app battery monitor widget

A much more in-depth app
[ONE Original Android Development] chenrp:
Thanks!
[ONE Original Android Development] plantator:
I'm wondering, is undervolting by 100mV can cause that apps or system is a litle bit laggy?
[ONE Original Android Development] magnamentis:
it can even force your device into random reboots and with a bit of bad luck keep it in a bootloop because the boot process often needs power. ok with boeffla app it won't happen, the worst case i mean, because kernel settings are applied quite a bit after the device has booted but still, 100mV is not recommended while it remains up to you. perhaps lord boeffla will reply in an even more straight forward manner LOL
[ONE Original Android Development] andip71:
In short: yes, this is possible.

Was seeing that in the past myself in the s3 when I was still undervolting myself.

Andi
[ONE Original Android Development] plantator:
About random reboots I faced it on ak kernel when I play with UV so know about it but now thinking about is -100uV can impact performance. Thanks for reply.
[ONE Original Android Development] cloudx720:
Hey Andi :) on stock cos12.1 is the min gpu 200mhz? Just so I know so I can set in boeffla app thanks ?
[ONE Original Android Development] andip71:
Yes, correct.

Andi
[ONE Original Android Development] magnamentis:
sure, as long as people are aware, know how to recover and don't blame rom and kernels for all kind of issues, it's totally legit to use that stuff to ones personal likings. i think all of us have played with voltages once, i just gave up because there were always more effective means to achieve the goal of battery efficiency. tasker is greating but means work :) :highfive:
[ONE Original Android Development] plantator:
I tested some kernel settings on Fallout Shelter, governors- interactive, smartass, zzmove gives it laggy, performance no lags and smooth playing, same on Sims free play
[ONE Original Android Development] infatality:
[MENTION=254166]Lord[/MENTION] bofflea tons of kernel commits raining on bacon tree!
[ONE Original Android Development] andip71:
Oh yes, I saw it already.

Just, all Cm13 builds today are not successful, so I will wait for the next successful build to put the commit into a new kernel update.

To ensure we are in sync.

Andi
[ONE Original Android Development] infatality:
Yup.. Today build failed.. Yesterday build was successfully but failed to update the link.
[ONE Original Android Development] cloudx720:
I upgraded at the worst time lol, gone back to cos12.1 until cos13 stuff it :D
[ONE Original Android Development] Mecca EL:
Give VM13 a go. It's one of the best running Android 6.0.1 available. Plus, custom features.
[ONE Original Android Development] cloudx720:
Can't do with the random reboots, might as well be a paper weight.
[ONE Original Android Development] Mecca EL:
I've not experienced random reboots on the latest release, but not discounting that it can happen. What I've found helpful is a couple of root tools. Titanium Backup is awesome for saving apps in the state you left them in, prior to an OS update. And I use the latest Philz beta, instead of TWRP, for ROM installs.

I know most of us call a "clean install", wiping our device, installing a ROM and then reinstalling from a backup. If there's a change in the system settings, between the two ROM, the backup will contaminate the clean install, and we have problems.

Just my 2 cents.
[ONE Original Android Development] cloudx720:
I had 5 random reboots while restoring apps from playstore after clean fresh install of cm13 of yesterdays nightly :(
[ONE Original Android Development] andip71:
To be honest, I also had not a single random reboot on CM13 ever.

It must be some combination of factors leading to it...

Andi
[ONE Original Android Development] vinman12:
Your kidding right?

Myself, and my testers have not experenced any reboots.

Something not right, and I am using lords kernels.

---------- Post added at 02:00 PM ---------- Previous post was at 01:55 PM ----------

Same here, my guess is 3rd party apps or perhaps gapps.

Sometimes restoring app and its data.

So many possibilities.
[ONE Original Android Development] magnamentis:
undervolters? just a guess, could as well be something else, i'm sure a clean install and before that reverting to default settings will solve this. there might be another kernel tweaking in place or an app, a theme or xposed module. i'm using all of that stuff except undervolt and secondary kernel tweakers, but still, some mods modules and themes work and others don't, as well undervolting my work on one rom version but not anymore on another. not sayin' one of those things are true, just trying to point to possible culprits among many more possibilties of course.
[ONE Original Android Development] cloudx720:
Even after formating sdcard along with wiping and clean installing cm13 random reboots. Lots of people confirming this not just me lol
[ONE Original Android Development] Orphee:
It could be a carrier trigger problem on some countries, I had a lot of issues on my last razr hd not experienced by others... Lot of factors can lead to issue
[ONE Original Android Development] nyronjay:
how much sot? and settings?
[ONE Original Android Development] copi:
Yes the battery is good with vm13, from100-55 I've managed to reach 4hrs sot with setting underclock to 1958 interactive standard and hotplug optimized
[ONE Original Android Development] vicky2131:
[MENTION=947981]Lord Boeffla[/MENTION] actually what is the difference between "default" and "optimized" hotplugs? i know default but what does optimized do(save battery or for performance)? I read somewer optimized is for gaming and it confused me as i though it was optimized for battery savings.

Btw im waiting for latest update :D
[ONE Original Android Development] MBurns2:
In my opinion optimized tends to use less cores =more performance=less battery

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] andip71:
Default means: mpdecision is in full control and tends sometimes in idle to keep 2 CPU cores plugged in.

Optimized changes that in a way, when phone is idle only one core is used.

Andi
[ONE Original Android Development] kurtextrem:
Really? I've read other-wise. Good to know.
[ONE Original Android Development] andip71:
Yep, really.

BTW... just testing a kernel update for CM13 as CM pushed a hell lot of commits in the past 2 days...

Andi
[ONE Original Android Development] vicky2131:
Thank you guys! That cleared my doubt :)

btw after reading your post somewer only i got confused if optimized was for performance. ha ha :D
[ONE Original Android Development] kurtextrem:
Yeah, I know. But an other guide said optimized would be "optimized for gaming" :(

I'll edit my post.
[ONE Original Android Development] brath23:
Hi everybody,

I set MAX CPU speed to 1958 and hotplug Optimized. I would want to know if the changes made with Boeffla Kernel App are persistent or they are set in every startup by the APP.

That means, if I disable Boeffla APP from startup the kernel modifications will be present?
[ONE Original Android Development] andip71:
Yes.

The app does not apply the settings itself during the start. The kernel does.

So you could even uninstall the app and the settings will still be applied (in theory).

I do however NOT recommend to exlude the app from startup as the app does some checking and displays if everything was applied fine before it terminates itself completely (not consuming cpu cycles, memory, network anymore - this was my primary design goal for the app).

Andi
[ONE Original Android Development] Semper80:
[MENTION=947981]Lord Boeffla[/MENTION] Your kernel will work fine in RR M? I tried. It installs but when I apply my settings in Boeffla Config, battery is draining quickly. With the same settings I obtained 7h SOT in official CM13 Bacon. In RR M only 3 hours.
[ONE Original Android Development] andip71:
My kernels are made for official CM/COS only.

So I cannot comment on any other custom roms. I simply do not recommend them (don't flame at me now, this is my opinion for good reasons).

Andi
[ONE Original Android Development] Semper80:
K. Thx
[ONE Original Android Development] cloudx720:
Quick question, after clean flash of cos12.1 and I install boeffla kernel load the app the default I/O scheduler is fiops? Thought it was row. Is the default on stock kernel fiops I wonder... Kinda strange as row is Qualcomm's recommended scheduler ?
[ONE Original Android Development] andip71:
They change it back and forwards, so I stopped maintaining that in the app. Especially as they are not consistent across COS and CM anymore.

I would need to look up what the default scheduler is for each rom currently. When I find some time...

(or you flash the reset zip in recover, restart and open boeffla-config, then the correct default scheduler is shown too)

Andi
[ONE Original Android Development] Renosh:
I'm not on CM or Boeffla at the moment but I've noticed on COS12.1 default is Fiops, CM12.1 and CM13 it's bfq
[ONE Original Android Development] andip71:
CM13 maintenance update

Hi all,

huge maintenance update on the CM13 kernel, CM team pushed 63 commits since my last kernel.

Version 5.0-beta11

17.12.2015

Update: Updated with latest official 63 (!!!) CM kernel commits as of 17.12.15

Update: Ramdisk updated to official CM13.0 version of 17.12.15

Enjoy

Andi
[ONE Original Android Development] Hugomm:
That sounds good. Alredy running 17.12.15 nigthly + beta 11 boeffla kernel.

Thanks for your work.
[ONE Original Android Development] andip71:
Next maintenance update

Hi all,

CM team pushed another 4 commits after my last build, so you get the next maintenance update for the CM13 kernel right now:

Version 5.0-beta12

18.12.2015

Update: Updated with latest official 4 CM kernel commits as of 18.12.15

Update: Ramdisk updated to official CM13.0 version of 18.12.15

Enjoy

Andi
[ONE Original Android Development] tsiftsism:
Sorry for this post since my problem may not be related to kernel but any help would be appreciated.

When i updated my device to the 1st 6.0.1 Nightly back in 9th December without preforming any wiping it rebooted every few minutes so i went back to the 1st December's Nightly by restoring my nand backup.

Now that i flashed yesterday's Nightly after having done a full wipe (no SuperSU or/and xposed installed) my device keeps rebooting every few minutes.

Attached you can find the 2 logs i created between 2 reboots.

Thanks.
[ONE Original Android Development] infatality:
[KERNEL] [Bacon] [CM13/COS12.1/CM12s/CM12.x/CM11s/CM11] Boeffla-Kernel (18-12...

Known cm13 issues.. Not kernel related.

Trying going on to setting / location / scanning. Disabled both wifi and bluetooth scanning and see if it's help lessen the ramdom reboot..

Some people will see more random reboot some don't.. Like my self I had yet to encounter any reboot on cm13.
[ONE Original Android Development] andip71:
Known issue for some for quite a while.

Some say it has to do with WIFI drivers. But others never have any reboots.

Some change a configuration file for wifi the rom comes with and it fixes the issue for them, others do the same and it does not get fixed.

The logs are clean, the kernel does not trigger the reboot.

And here is where it ends. I cannot provide more insight.

Try to use stock kernel, you should at least see you have the same reboots.

Andi
[ONE Original Android Development] andip71:
beta13

Hi all,

I realized, CM apparently silently did a rebase in their kernel repo, so I put these differences in as well now.

Last maintenance update therefore before this weekend:

Version 5.0-beta13

18.12.2015

Update: Cleanup of differences to official CM kernel branch CM-13.0 due to CM rebasing

Enjoy

Andi
[ONE Original Android Development] KURDKiNG:
Are u gonna support 13.1??
[ONE Original Android Development] andip71:
When it arrives...

Andi
[ONE Original Android Development] KURDKiNG:
Oh wait i feel dumm bruh so it already support 6.0.1?
[ONE Original Android Development] andip71:
Sure. CM13.

Andi
[ONE Original Android Development] cloudx720:
Really can't wait for cos13. For me cos12.1 runs and performs like a dream ??
[ONE Original Android Development] Matteo_666:
Yea, for me as well. Thats the Main reason i havent tried cm13 for more than 2 hours... COS12.1 is Brill.
[ONE Original Android Development] cloudx720:
Hey Andi will +25mV be enough to stabilize 2.8ghz step for me you reckon? ?
[ONE Original Android Development] andip71:
Sorry, I cannot remember what your device needed.

Mine runs without any overvolting, but I do not overclock anyways. You can try step by step going 25mV higher.

Andi
[ONE Original Android Development] cloudx720:
What is your ASV/PSV level? Mines 6 ?
[ONE Original Android Development] andip71:
I think 4, need to look that up.

But the ASV/PSV level does also not say a lot about how much overvolting is required or not. It defines the base voltages, not the deltas.

Andi
[ONE Original Android Development] molonad:
Hello Mistr Lord, iam again back with your kernel, but iam not sure how zzmove profiles work, for. Example zzmove extreme baterry yank is. Really aggresive, it every time goes fast straight to max frequency, all zzmove profiles work like they are not edited, or i Dont know. It is weird, i rememmber that battery extreme Wasnt in max frequencies so often like now. Or am i wrong?

Odesláno z mého A0001 pomocí Tapatalk

---------- Post added at 07:06 PM ---------- Previous post was at 07:04 PM ----------

All governors just seem too agresive. Even on stock settings.

Odesláno z mého A0001 pomocí Tapatalk
[ONE Original Android Development] andip71:
For zzmoove ZaneZam can answer best. He is the developer of it.

There is even a thread for it.

Andi
[ONE Original Android Development] JeanEatsWorld:
Hi Lord,

Thanks for your hard work.

I tried with beta 10 and now with beta 11..now I'm pretty sure i can say that smartmax eps has something wrong because it gave me random reboots.. I mean.. Not a big deal but that's just a little feedback from me..
[ONE Original Android Development] andip71:
I can remove it, but others use it without problems.

So use another governor instead, I would recommend.

Andi
[ONE Original Android Development] kurtextrem:
No issue on my end with smartmax_eps. COS12.1
[ONE Original Android Development] molonad:
Hello iam typing again about my opinion. I was little while on caf, now iam back with boeffla but it is unusual then before, all governors werent so much aggresive as old boeffla kernel , all governors agresivelly rump up to max frequency really fast when opening apps , even zzmove battery extreme is not really battery Oriented, all zzmove profiles work same, opening apps is same, it aggresively goes to max frequency. It is. Unusual for. Me and even battery Oriented governors work with this aggresive way.

Odesláno z mého A0001 pomocí Tapatalk
[ONE Original Android Development] andip71:
I answered to the same question already in the other thread. You should not do cross posts.

Governors are 100% unchanged in Boeffla compared to stock cm code.

I have not made them more or less aggressive.

Andi
[ONE Original Android Development] molonad:
Ok iam sorry, i Dont know why i have this feeling thanx for answer

Odesláno z mého A0001 pomocí Tapatalk
[ONE Original Android Development] vicky2131:
Smartmax_eps works fine on cos12.1. Cm13 is not yet optimized as well as cos. So wait for it for sometime.
[ONE Original Android Development] indesisiv:
As opposed to the random reboots that everyone is getting on cm13?
[ONE Original Android Development] andip71:
Yes, cm13 is still buggy.

Even cm team themselves announced, nobody should expect something really stable before mid/end January 16.

But people do not want to believe... ?

Andi
[ONE Original Android Development] Mecca EL:
Most are trapped in unreasonable levels of expectation. When it comes to electronics, everything is always in beta.
[ONE Original Android Development] Traace:
Hi Boeffla, this is a very stange one.

first of all, dont take this as a serious bug report (As i'm running unofficial zanezam builds of your kernel) at all.. I'm just reporting this because its more config APP related in my opinion.

I'm not ask for any hard support on this, just if u can reproduce it->

This is what i do and what happen to me every single time.

- Started up Boeffla Config.

- Made some settings related to battery, saved them as default profile.

- Activated the default profile to see if its work -> Its works ofc!

- Setting up another profile more performance related, with a different Governor.

- Activated both, first the default and afterwards the perfmormance related one to see if they both work -> They both do ofc.

- Restarted the APP or reboot the system-> the default profile gets loaded but with the performance governor.

- Loading the default profile per hand(not due auto setting) and relized that the governor is back conservative as it should

- Restartet the APP once more afterwards brings back the performance governor again in default

So, no matter what profile i'm going to use, the APP always switch the governor to the most fastetst (usually performance or lionhearth) until i've deleted all performance related profiles with such a governor in.

Even if i reset the default profile, all app related data, kernel configs etc. the issue is still here.

Unfortunately this issue isn't virtual, it does really change the governor.