yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] gordito_gr:
I too jumped right now on the boeffla train!!

I wil use this kernel with Euphoria, try to improve my battery life.

I absolutely love the app and the power it gives me. Keep up the good work.
[ONE Original Android Development] andip71:
It would be always very helpful for me, if people that are happy and satisfied also let me know which kernel variant they use.

I mean, the cm11s, cm11 or cm12 variant. To get a grip on how they individually work.

Thanks, enjoy it!

Andi
[ONE Original Android Development] Roulianooo:
Beta8

Beta8 is fantastic with lastest CM12 nightly thanks Andi :)

ZZmove optimal , 1024 readahead , fiops, optimized hotplugg (exept when listening music, switch to zzmove 2 cores min )

1 hour since unplugging and still 100% battery left :D
[ONE Original Android Development] black.ic3:
Nice kernel

Updated to latest kernel\app, but app says that kernel is incompatible :confused:
[ONE Original Android Development] andip71:
Yep, I switched off the battery fuelgauge functions.

Hehe, no... kidding.

Screenshot?
[ONE Original Android Development] black.ic3:
Very strange

Removed rights, granted one more time, but same again :(
[ONE Original Android Development] andip71:
Yes, strange. Can you please send me the file bc.log you find in /boeffla-kernel-data folder as well.

It looks like something is wrong with root access or busybox is changed/removed... etc.

Andi
[ONE Original Android Development] black.ic3:
https://www.dropbox.com/s/26f0fufy89yxy1n/bc.log?dl=0

Maybe i need to reinstall busybox\root?
[ONE Original Android Development] nonoperez:
For some people (including me) it works with wpa, but not with wpa2, and use a static ip, not dynamic. Some times the speed is not good, but at least there are no authentication problems. Give it a try
[ONE Original Android Development] andip71:
Hmmmm, I see the error clearly in the log:

Exception: java.io.IOException: Error running exec(). Command: [/res/bc/bccontroller.sh, get_kernel_version2] Working Directory: null Environment: null

Message: Error running exec(). Command: [/res/bc/bccontroller.sh, get_kernel_version2] Working Directory: null Environment: null

The app cannot execute the script it needs to properly interact. Something is blocking it.

Hence the questions:

- did you reboot already once?

- what root do you use? the built-in or supersu? (if latter, flash it again)

- do you use any security apps that might block the app from doing something? (like xprivacy etc, or others...)

- can you clear dalvik cache and cache in recovery and try again?

So, something is not quite right. And I would not be surprised if some more apps (specifically ones that require root rights) are not running fine anymore...

Andi
[ONE Original Android Development] black.ic3:
3) Got it!

SELinux Manager is autostarting with Enforcing (needed to get ViperFX work), and blocking the app

thank you for quick response and good support :good:
[ONE Original Android Development] andip71:
Great, you are welcome!

Andi
[ONE Original Android Development] jcespi2005:
Tested with WPA at home, but no luck, performance is really poor compared to CM11s. At work can't test another combination cause is WPA2 enterprise model, and don't work with any new kernel except TYR62.

Thanks anyway ;) i guess it's on CM side...
[ONE Original Android Development] HaTrED_:
[MENTION=947981]Lord Boeffla[/MENTION]

Latest CM12's version - Beta8 - running extremely well under fusionjack's build! Seems very promising in terms of SOT. :)

Excellent work mate, thx!
[ONE Original Android Development] maxver0:
this new feature is bugged, watch video below to know why.

[YOUTUBE]FbvndFX2eYI[/YOUTUBE]
[ONE Original Android Development] CounterC:
Please share screenshot when cycle is finished...
[ONE Original Android Development] ZaneZam:
Nice video, even though I can not reproduce this (yet) will take a closer look when I have time (that's actually atm my biggest problem *g*)
[ONE Original Android Development] tobitege:
I have a feeling, that you won't be able to as it may just be a matter of user expectations and terminology.
[MENTION=5108269]maxver0[/MENTION]: I think it is a bit too simple and unfair to just say something is "bugged" without giving textual explanations what you expected to happen at what point and WHY. Like some remarks (time-based) about your video would be helpful.

Not all tests in Antutu benchmark are multi-threaded and thus only run on a single core, afaik, and thus may not require more cores to come online. If we'd knew what your expectations of certain situations are we could then determine if it is a matter of "works as designed/normal behavior" or "it's a bug/fringe case/etc.".

/rant :)
[ONE Original Android Development] maxver0:
You just have to watch whole video. New feature sets maximum cores onilne as the hotplug minimum ones. Example:

zzmove native hotplug with this finger stuff (feature) enabled will use as MAXIMUM one core. When you will set zzmove min 2, it will use only two cores as MAXIMUM. I tried 3 cores as well, but in this case it was different only 2 cores were used.

At the end I changed to my current profile without this new feature and you can see in 4 cores were running during stress, not 2 like earlier.
[ONE Original Android Development] ZaneZam:
ah u really were referring to the touch booster ok thx for clarifying and yes as said this beta6 is kind of a wip version so things might get improved in next version, but still i've enabled the inputbooster all of the time and can't reproduce this atm but i don't say there is no bug, as said will check that thx for info.
[ONE Original Android Development] :
b8 is tremendiously better then before. Could be some fizes from cm12 nightly also, the combo at least after one day use is awesome. Still needs improvement, but its way better then before (89% battery left now, vs 60-70% on previous combos cm12, cm11 I had 90-95%) lol
[ONE Original Android Development] tobitege:
I did watch the whole video, but it's not easy to see every setting. But thanks for the explanations, they are filling the gaps. :)
[ONE Original Android Development] andip71:
Yes, I think... CM11 was developed for more than a year, CM12 officially started a few weeks ago. So, there is enough time in the next months to make the stuff better :)

Andi
[ONE Original Android Development] maxver0:
That's why I grabbed antutu for, you silly :silly:
[ONE Original Android Development] abhishek.se:
Ever since I switched to lollipop roms on opo (cm12,blisspop,slimsaber) always had audio skipping issues over bluetooth with stock kernels in each of the rom. Never tried any custom kernel till I read about the fix for keeping 2 cores online during screen off, so flashed boeffla-3.0-beta8 over SlimSaber-5.0.2-20150129.

I'm happy to report that with default kernel setting i.e. even without changing any hotplug setting in the config app, this rom-kernel combo has totally resolved the bluetooth audio skipping. Great work dev :good:
[ONE Original Android Development] andip71:
Great, good to hear that.

Thanks for sharing.

Andi
[ONE Original Android Development] MickyMax:
I can also confirm that. I have no problem in Bluetooth neither, screen on with Waze or screen off while listening Spotify.

Kernel is smooth.

Very good job.
[ONE Original Android Development] Ofthecats:
I experienced bad audio skips (every 5 seconds) without keeping 2 cores minimum. This was over headphone jack too.

I haven't tested to see if interrupting audio on Bluetooth leads to volume going wild yet.

Dynamic fsync does not stick in the kernel app either.
[ONE Original Android Development] bagadj:
Guys could you explain how to set 2 core online with bloeffa config??
[ONE Original Android Development] maxver0:
Oh my god. In boeffla app just set 2 cores. :o
[ONE Original Android Development] andip71:
Dynamic fsync sticks for me. Never was different, and nobody else ever reported that.

Andi
[ONE Original Android Development] ZaneZam:
Hehe that's nice, U call me silly? Why so offensive? Actually I could call u that for using atuntuttututu for such a test and for not more explaining a video where u are switching hotplug profiles during running a benchmark app which is not constantly stressing the system and therefore generating a complete random hotplug behaving.

But well I will not do that and will still check if everything is working properly as I still take this report serious, you obviously not. ;)
[ONE Original Android Development] nicesoni_ash:
I doubt he was meant to call you silly.. I guess he tried to put a smiley in the end of his message and that didn't work out that good. :)

_____________

Sent from my "GT-I9300/1+1" powered by Carbon Rom & Boeffla/ak Kernel

Fueled by 7000mAh ZeroLemon Battery
[ONE Original Android Development] Ofthecats:
Doesn't stick after reboot *

Any idea why, or anything to check that would cause this? Slimsaber rom, patch pie, n5 sounds, PA gapps.

Also!

Haven't been able to catch a logcat of the following issue:

It seems after a few minutes, or possibly randomly, music volume attenuates on its own independent of volume set by user.

It stays that way until I pause and resume song, or press volume buttons.
[ONE Original Android Development] maxver0:
I'm just kidding buddy! I didn't want to offend you. It was kind of a joke.

Yup :)
[ONE Original Android Development] malavan:
thanks for your awesome work.

the file in efs backup is only file i need if anything wrong.I mean if i lose my efs seetings.

29J56889YX844463L
[ONE Original Android Development] andip71:
Well, do the following:

Enable it in Boeffla-config V2

Then reboot

Enter Boeffla-config V2 and check if it is disabled again

Then create a debug info file in Boeffla-Config (Action menu, then last point)

Send me the debug info file

Then we will see.

About your sound thing... I have not experienced that so far. But I am using CM12 official nightly only. Maybe thats why...

Yes, correct. Move it to a safe location, to your pc, an USB stick or something. This is your life insurance in case it gets corrupted one day.

Andi
[ONE Original Android Development] Ofthecats:
Sent via email
[ONE Original Android Development] andip71:
You have an answer. There is an init.d script called UKM which might cause it.

Please delete it and try again.

Not sure, but worth a try as UKM is "universal kernel manager" script which is not required by my kernel.

Andi
[ONE Original Android Development] Ofthecats:
Seems to have been the culprit. Thanks for your time!

I didn't expect the script to survive a factory reset via twrp
[ONE Original Android Development] andip71:
At least we learned something.

And I really consider removing UKM scripts during flashing of my kernels in future. Might not be the worst option :)

I think about it.

Andi
[ONE Original Android Development] Ofthecats:
:P

I also just discovered the clean init.d option in the app. Does that clear it out completely? Sounds risky if someone doesn't know what they're doing.

PS: I donated for your speedy assistance. Thanks.
[ONE Original Android Development] andip71:
Yes, it does clean it completely. But I do not consider that risky because of

- a rom should always start properly also without init.d scripts

- the scripts are not just deleted, they are backed up before removing them. So they can be brought back one by one if required. The scripts are backed up to a tar archive in folder boeffla-kernel-data btw.

The thing is - there are so many different init.d scripts which can cause issues, UKM, all sort of mods, ... catching all of them intelligently is almost impossible.

Andi
[ONE Original Android Development] molonad:
I tried to turn off mobile data sometimes and look into wake lock detector and turn off Facebook and Google+ and i played little in app ops battery is much better then before, please I have question for all of you guys, is more battery friendly battery yang or battery? battery plus or battery extreme yang? thanx ?
[ONE Original Android Development] andip71:
Should be Yank battery extreme in theory.

Andi
[ONE Original Android Development] topp10:
Hi Andi,

Just wanted to say thanks.

I don't even bother trying any other kernels anymore, because when I do, I always come back to yours!

8WM520201L352754F
[ONE Original Android Development] jdpl123:
Fast Charge

Hey just trying out the kernel and it has everything that I need, so far no bootloops, random reboots or any laggy functions, actually a lot more fluid, but is it possible to implement a forced fast charge, this would be the icing to the cake?
[ONE Original Android Development] andip71:
That is implemented for a very long time already.

You can configure charge rates as you like in the app, separately for wqll charger and usb charging.

I think there is even more implemented in terms of charging as anywhere else.

I decided to not port the so called fast charging implementations around as... No, I won't tell.

But there were good reasons I changed the battery driver from scratch by my own.

Andi
[ONE Original Android Development] jdpl123:
OK not a problem in still trying to learn about kernels . First time using this kind of feature. So what would be a good setting for the usb and wall charger with out causing damage?
[ONE Original Android Development] andip71:
Try 1600 for a start. If you are brave go on 1800.

But nobody can assure you it doesn't have negative impact on battery life.

I usually put the sliders on 0, which means stock charge rates apply.

But when I need fast loading for some reason, I put it on 1800.

Andi
[ONE Original Android Development] saikm:
very good kernel

boeffla-config APP is better than Synapse

but 2.1.66 v2 is crashing often when load profiles
[ONE Original Android Development] tobitege:
I have a gut feeling, that it is only happening with custom themes...
[ONE Original Android Development] andip71:
This does not help to get anything improved.

I need at least more description of how often, sporadic or reproducable etc.

Und ultimately I need a logcat after a crash.

Have no chance otherwise. As I have no crashes myself.

Andi
[ONE Original Android Development] DarthOps:
I'm on the latest version of this kernel and the phone keeps restarting when the screen is off (it seems intermittent) . is this a know issue and is there a fix?

Thanks [emoji4]
[ONE Original Android Development] magnamentis:
this kernel does not cause such issues, except if you have undervolted or so. does it restart into bootimage or into bootloader? first means it's a rom or a userspace issue, the later would hint to the kernel, but again it would rather be your setup than the kernel itself as is. this simply does not happen that way as a kernel issue.
[ONE Original Android Development] schmitzekater:
Trying your settings on 30th-Vanir, but always with zzmove native 2 cores min. Feels really really good, even with CPU capped at 2265.

After 40 hours off charger and 3 hours SOT there is still 52% juice in my bacon.

Thanks to the Lord and ZZ. ?✌

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] jejecule:
Exactly same issue here with standard kernel setup, no changes made to the initial setup.

Phone soft boot every 4/5 hours, no real impact for me i just know it thanks to Boeffla app notification displayed when i wake up my device.

I'm on CM12 nightlies, it has been happening the last 3 days with the last 2 nightlies (no nightly built today).

Thanks Andi for your work (i remember having been one of your first S3 "client";))

I'll try to catch a logcat if needed.

Cheers

PS: happening with beta 7 & 8
[ONE Original Android Development] jgcaap:
You removed the quick charge? Why? Do you believe it damages the phone?
[ONE Original Android Development] HaTrED_:
No such issues under my setup!
[ONE Original Android Development] Jax Teller:
No issues here either.

Running SlimSaber with latest boeffla kernel.
[ONE Original Android Development] magnamentis:
no, nothing has been removed, he just made his own thing and it's still there as it has been for long :) it's under miscellaneous > charger rates
[ONE Original Android Development] jgcaap:
I didn't understand the post.... Lol quick-charge is good or bad? I find it awesome... But we need special chargers for that right?
[ONE Original Android Development] DarthOps:
Yup that sounds like exactly the same as me . cm12 nightly plus beta 7 or 8 does this but not on the stock kernel or franco
[ONE Original Android Development] magnamentis:
no, it basically allows to charge at higher amperage than out of the box, mostly for usb charging but with this kernel ac charging is tweakable as well. fact is that higher amperage let's the device suck as much as it wants while it cannot really damage anything. the part which can damage is the voltage ( pressure in a hose if you want an example ) while amperage just indicates the maximum available energy which only has a negative impact if it's force down the throat with high pressure which again would be voltage. so if you wanna fast charge an electric car (battery also ) you would need high voltages. albeit some say that the battery can still suffer, i must say that 9 of 10 batteries survived my devices usage lifespan by far and the only two batteries ever which collapsed were more than five years old and i'm not convinced that lesser amperage would have extended that for much longer if at all :) so we can choose if the batteries are best possibly charged during the real life ( use ) of a phone, or if we want to make sure that when we throw the phone away, the battery is still in good shape haha.... similar like screen protectors or cases, making phones ugly or thick during use time, so that it looks like new when we don't need it anymore. of course it's not that simple and nothing is wrong to see things differently, but generally i tend to see things like that LOL
[ONE Original Android Development] andip71:
No, I never implemented it.

I created my own charging driver from scratch, as the fast charge implementations around do not meet my quality standards.

Charging with higher charging rates is always a risk. Everyone should know what kind of risk he/she wants to accept.

No issues here, not a single reboot for weeks.

Hence, nothing to change for me, although it sounds hard.

On top: No debug info file or last_kmesg = no way for me to see what might have triggered your reboot.

Andi
[ONE Original Android Development] tracerit:
Switched to ondemand last night after using zzmoove for the last few weeks and experienced the screen of death again. Back to zzmoove haha.
[ONE Original Android Development] andip71:
I think I should try Ondemand as well one day, as I never had a screen of death ever. Maybe I can also see it once.

(what r u using? cm11s, cm11 or cm12?)

But going to zzmoove is anyways a very wise decision!!!

Andi
[ONE Original Android Development] ak:
And 'well known that ondemand and cpu-boost don't work well together, most of the time they just create problems.

You have two options to remedy the problem:

- find a fix

- remove
[ONE Original Android Development] Fenvarien:
Absolutely no issues here with Euphoria ROM 20150129 and Boeffla-Kernel beta8. Zzmove native hotplug 2 core min / zzmove optimal / zen scheduler / gpu 27/330 and cpu -50mv uv. Everything is rockstable and the battery life is amazing! Thanks [MENTION=947981]Lord Boeffla[/MENTION] and [MENTION=3279788]ZaneZam[/MENTION] :)
[ONE Original Android Development] jejecule:
I'll provide the files to you next time it occurs.

Thanks & Cheers
[ONE Original Android Development] DarthOps:
EDIT: attached the file for you
[ONE Original Android Development] tracerit:
I'm on Liquidsmooth CM11. I just remember switching to ondemand at night and woke up 15 hours later to an unresponsive screen.
[ONE Original Android Development] DerRomtester:
Linux version 3.4.67-cyanogenmod-g0187e28-dirty (dees_troy@ded1.ktechnology.net) (gcc version 4.7 (GCC) )
[ONE Original Android Development] DarthOps:
Hmm, does that mean that its an old message from the old kernel or something ( sorry not familiar with the way the kmessage works. I just assumed that it would have been from the last reboot)

If it is I apologise but can assure you I'm running the beta 8 kernel as attached. If there is another way to get the info for you I'll do it!
[ONE Original Android Development] lchiocca:
Hi saikm. You will need to be a bit more 'chatty' about the reproduction steps. It's really hard to guess what you were doing before it crashed. Let me give you a real example on what i mean:

0) system is a cm11s running test-2.2-beta1 with config app version 2.1.66

1) open the config app

2) create a new profile called "NPESUX"

3) change to that profile

4) frow the current "overview" tab, go to the "boeffla sound" tab

5) crash of app

6) can also be reproduced by resetting an existing profile and then going to "boeffla sound" tab

If i follow these steps, i can always reproduce the crash and that is something that helps any developer get rid of bugs.
[ONE Original Android Development] gnan10:
Hi. Does this kernel supports 2partition f2fs roms?

I am not able to boot from temasek unofficial linaro 6.6_ 2p rom

PS: flashed latest 3.XX boeffla kernel version(CM12)
[ONE Original Android Development] Criton30:
I have removed ak kernel (ukm removed>synapse removed>ak kernel removed) and flashed boeffla stable kernel 2.1 for stock 44s, config app is also installed. Is there any good profile? Should I install UKM for boeffla?
[ONE Original Android Development] evertking:
Donation sent.

Thank you for your work!
[ONE Original Android Development] molonad:
Noo, only boeffla config app v2,you can download it on boeffla^s site
[ONE Original Android Development] maxver0:
No it doesn't.
[ONE Original Android Development] Criton30:
config app is installed, but after phone reboot I get "Google Application has stopped (Google Quick Search Box)", why? and I get 3G connection very slow... with stock kernel and with ak kernel I did not noticed this two issue. Should I check something in the config app?
[ONE Original Android Development] gordito_gr:
This is my setup, with latest Euphoria.

My performance is really bad, too much lag and stutter, and i see no difference in battery life, compared to Euphoria's stock kernel.

~5hours SOT in 2 days, 80-90% on wifi and no gaming.

Am i missing something?
[ONE Original Android Development] andip71:
This last_kmesg was not something created while using my kernel. It is a completely different krenel.

Yes, there is such an easy way, I alway wonder why people fiddle around with last_kmesg, terminal windows etc.

Just go in Boeffla-Config V2, Action Menu, last point is "create debug info file".

Done. Send this file to my support address and I see everything I need.

No, does not, and never will. See OP for that.

I think you should head over to the thread where all the configuration experts share their profiles:

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

Thank you. Very much appreciated.

If you are missing your code for longer than 24 hours, please inform me.

If you are using gmail, check your spam folder.

This is both not connected to the kernel.

The first issue comes from the rom, the second from the modem.

Also, nobody reported that so far, so it seems to be an individual issue on your phone.

Well, you have chosen one of the hardest battery saving governor/profiles.

So it is quite obvious the system is not that fluid anymore.

And depending on your usage pattern, it is also not said this is the right choice for you to save battery. Unfortunately it is not that easy and simple in general.

I would also recommend you to head over to the experts regarding configuration:

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

Andi
[ONE Original Android Development] Criton30:
Thanks, I have 28112014 nightly modem, ROM is stock 44S. If i choose only LTE under settings, then after reboot I get very quick LTE connection, but if 3G mode only enabled then I must wat 4-10seconds to get 3G connection.... for test I have flashed the stock kernel back and with it no issue noticed if I choose only 3G....