yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] beany>:
To add to what [MENTION=5620792]DrNinjaa[/MENTION] has said, often you get one app misbehaving for no apparent reason. For example, last night Keep used 14% of my battery overnight, although I hadn't used it at all but do have a widget and I even Greenified it.

Sometimes things like that happen.

Also, the kernel and associated settings/governors/hotplugs etc have far less effect on battery for most users than signal, apps, settings, refreshes etc. I normally lose 10% overnight just because I have a poor signal.

View the kernel etc as another refinement rather than the main culprit.
[ONE Original Android Development] acuicultor:
Hi Andi, noticed that using load and flash function of boeffla app to upgrade to last cm12 kernel(3.1) not working properly, it download and flash 3.0 version, just FYI.
[ONE Original Android Development] andip71:
Thanks for spotting that. Fixed now.

Andi
[ONE Original Android Development] RCT1:
SElinux permissive isn't working after a reboot...
[ONE Original Android Development] acuicultor:
May be you don't noticed that option;)
[ONE Original Android Development] RCT1:
My mistake... I've installed the app instead of a restore and forget that option...
[ONE Original Android Development] andip71:
No problem, mate. That's what the communitiy is here for.

Andi
[ONE Original Android Development] bloof:
Thanks! But now i decided to ask: i am really confused by the busybox app itself... Is it still required if kernel installs its own?

I never install busybox through the app if i know my kernel installs its own version but i am wondering in what circumstances is the busybox app useful at all?
[ONE Original Android Development] andip71:
Well, CM and CM11s comes with their own busyboxes. Usually it is not required to flash a busybox on top using an app.

The kernel busybox is used internally by the kernel only (and by the boeffla-config app as it can rely on the features of it only).

On Samsung devices, the kernel busybox can be converted to a fully usable busybox. So also here no installation via a 3rd party app is required.

However, on the OnePlus, as said, you do not need to do anything. All is there.

Andi
[ONE Original Android Development] DrNinjaa:
Ahh....Thanks Lord,had this doubt for so long .:thumbup::thumbup:
[ONE Original Android Development] bloof:
Thanks for the long answer. I was really confused, coming from LG G2 and all that where it was sometimes required.

Now i will delete on my OPO.

Does anyone have the MD5 of stock CM11S05Q busybox? I just want to make sure i still have original.
[ONE Original Android Development] ricardowec:
Here my 5 cents: for a reason unknown to all, some apps are doing their thing int the BG instead of updating via the Store. One good example of what I am saying is whatsapp.

In the past few days I´ve been noticing an abnormal resources usage by this app . The reason is now known to all: whatsapp has been updating silently to provide for voice services.

There are a few tools that I use that help me get well over a day´s battery usage: BBS is one, GSam battery monitor is another. So yes, take care of your apps first and then go to the ROM and the Kernel.

Cheers
[ONE Original Android Development] xflowy:
hey. i am at Version 3.0. every time i open the boeffla app it says that there is a new version 3.1 avaiable. i flashed this version and it still says 3.0 and provides me with the update option.
[ONE Original Android Development] abhibnl:
I can confirm it as well! Whatsapp is ****ing the battery lyf from last 3-4 days. It's simply a pain in d @$$ nowadays draining battery like crazy. Any solutions? I checked BBS and the culprit is dmux_wakelock.

Sent from OnePlus One Powered by Boeffla
[ONE Original Android Development] Gamm86:
Try updating using the app instead of flashing it.
[ONE Original Android Development] beany>:
Whatsapp being a terrible drain is nothing to do with the kernel. IMO it isn't a good app. Telegram for example does the same thing without the constant drain.
[ONE Original Android Development] akz1x1:
Capacitive keys controlled by kernel

I've recently bought a OnePlus One and I'm a huge fan of Boeffla kernel since I was a Galaxy s3 user...

Just flashed it and starting to love it from the very few minutes of use...

Wanted to know whether is it possible to include capacitve keys controlled by kernel... Now whenever I touch my screen, the capacitive keys stats to lit up which is really annoying.. I actually wanted them to lit up only when I press the keys... Just curious to know whether is it possible...
[ONE Original Android Development] abhibnl:
Well, i've never said it's Kerne's fault. This kernel is the most stable and has all the features that i require with an awesome config app. What i'm saying is, it's lollipop's fault IMO. On KK the drain by whatsapp is negligible. On lollipop, it's terrible.
[ONE Original Android Development] lou2s:
Whatsapp drain. It happened to me 1 week ago. Whatsapp alone took care of 50% of battery use suddenly. I backup the chat history then uninstall and reinstall Whatsapp. Drain gone.
[ONE Original Android Development] andip71:
On the list for enhancements, yes. Should come.

Andi
[ONE Original Android Development] abhibnl:
I've done the same. Backup Chat > Uninstall > Reinstall Whatsapp > Clear Cache/Dalvik Cache from recovery

Still the ****ing drain is there and it's driving me nuts.
[ONE Original Android Development] anmar21:
Has someone tried to flash latest kernel on oxygenOS?

Just curious....
[ONE Original Android Development] fjsferreira:
Will do it now. I'll report back.

EDIT: as expected, doesn't boot with latest boeffla cm12.
[ONE Original Android Development] Renosh:
You'll have to wait for kernel sources for compatibility with boeffla to be possible. That's if he decides to do it
[ONE Original Android Development] andip71:
I will definitely have a look at oxygen os after Easter. Maybe someone can find already whether there is a dedicated kernel repo for it (should be).

Andi
[ONE Original Android Development] Hiro Nakamura:
Hey Lord Boeffla,

there were some kernel changes in cm12.1 for bacon on April 2.

Are those in your kernel yet?

https://github.com/CyanogenMod/android_kernel_oneplus_msm8974/commits/cm-12.1
[ONE Original Android Development] andip71:
No, not yet. They came after my last kernel version.

But before Easter is over, I will not work on anything. So, you have to wait a bit.

However, I do not see any critical commits at all.

Andi
[ONE Original Android Development] SaschaKH:
You might have that error, Andi fixed already. BTW I did the same withe the same result. My next step was downloading ZaneZam's linaro version and installing that, just before I read about that error.

That would have worked as well probably, but after all the way I did it works and battery seams to last even a bit longer. Will probably try his uber versions too.

I looked what ppl say about it and decided to not install it. The error list seams to be longer than the features list and battery drain is rather heavy. Well it's just out for about 8 hours, so who knows if the first impression is right but I probably wait for CM12s.
[ONE Original Android Development] ricardowec:
The problem with Whatsap was (and still is sometimes ) that it silently updates the app in the background. It was doing so a few days back in order to provide for voice services.

Cheers
[ONE Original Android Development] ivan0909:
One question. Wich is the TC you use to compile your Kernel? Especially CM12.1
[ONE Original Android Development] ZaneZam:
Lord Boeffla uses Google Stock TC 4.8
[ONE Original Android Development] tracerit:
how does "swipe screen gesture to sleep" work? the swipe capacitive buttons doesn't work for me because Euphoria ROM only allows either on screen or capacitive and not both, so i'm looking for a non hardware action to close the screen.
[ONE Original Android Development] andip71:
Boeffla-Kernel OnePlus One - swipe2wake + swipe2sleep: https://youtu.be/Hi5xKR-kh34
[ONE Original Android Development] laura almeida:
Can we restrict swipe2sleep only to captivate buttons ?
[ONE Original Android Development] slebit:
That's epic!
[ONE Original Android Development] tracerit:
so it seems the actual gesture is a diagonal swipe from top right to bottom left, correct? works great but it does get in the way of browsing and keyboard swiping unfortunately :/
[ONE Original Android Development] andip71:
Just don't enable them in Boeffla Config.
[ONE Original Android Development] xanthrax:
how much it hurts this word "that"...

the kernel doesn't work, if you're referring to it, O2 kernel sources aren't out yet and the developer stated already, no updates until the Easter days will pass

sent from my Darkside of SHIELD Tablet
[ONE Original Android Development] DrNinjaa:
Its XDA, be polite.... and its not a general discussion thread about kernels, please ask in the general discussion thread... this thread is for the development of Boeffla kernel. And FYI no kernel is still available for Oxygen OS.

Please visit this thread

http://xdaforums.com/showthread.php?t=3072259

#HappyFlashing#
[ONE Original Android Development] RcrdBrt:
Still hoping for the BLX to be added in the next release, I have not time to do that by myself

Why no TAP module? That would be useful for some (me for example lol)
[ONE Original Android Development] andip71:
I thought I told you the blx implementations around do not work on the charger chip of this device.

So it needs to be investigated from scratch, which I don't have the time for at the moment.

Tap... refer to op. I usually only put in the kernel what is interesting for me too. Tap is not on my list, but I need to check if it is statically already put into the zImage, as with tun.

Andi
[ONE Original Android Development] NickosD:
I'm back. Sound glitches are gone.

Yayyyyy

Sent from my bacon!!!!!
[ONE Original Android Development] RcrdBrt:
sorry, I missed your answer to my post. Sounds like a pretty hard work to do as I have seen, that's right. I hope the Li-Po technology keeps an acceptable performance for at least 2 years though.

Lowering Amp could help, at the expense of charge time and single charge duration.

"only time will tell us" :D
[ONE Original Android Development] NOSTALGIA:
power button press really is delayed for me

am i just the one experiencing this? im on the 05q rom with this kernel. sometimes instant. sometimes not.. its somehow bugging me
[ONE Original Android Development] andip71:
Interesting. Have nothing done about it. Or..? Maybe one reverted commit made the trick. Who knows :)

Sure, it is at least not a trivial thing. Messing around in the charging driver always comes with some significant risk of making things really bad.

That is why I would never to a quick shot but a proper and time consuming analysis first

But I consider it as something really useful, so it is on my list, definitely.

I never press power button as I use double tap to wake. But also when I try via power button, it comes up quite instantly.

Question is: What is your setup, especially governor.

Andi
[ONE Original Android Development] NOSTALGIA:
my governor is zanes governor
[ONE Original Android Development] andip71:
So, try interactive for a day and check if it makes a difference.

Andi
[ONE Original Android Development] Criton30:
optimal, battery saver, moderate?
[ONE Original Android Development] bloof:
Check also your ROM settings such as greenify, autokills and autostarts. Apps all trying to start at the same time when switching on will cause a lag.
[ONE Original Android Development] andip71:
Tomorrow new 12.1 kernel for you guys.

Lots of code updates incl. new wifi drivers included.

I am doing some last tests...

Andi
[ONE Original Android Development] fjsferreira:
[MENTION=947981]Lord Boeffla[/MENTION], can you tell if the new wifi drivers fix the horrible wifi in all 5.1 ROMS?
[ONE Original Android Development] tracerit:
are you referring to wifi disconnecting and showing an "Authentication Problem" requiring a reconnect? I get this on 5.02 on boht Euphoria and BlissPop ROMs.
[ONE Original Android Development] andip71:
Cannot tell you, I never had a single problem with wifi on any rom.

I am sure it has to do with used wifi router, channels, bands etc. Maybe even with hardware revisions of wifi hardware in the opo.

So, all I can say is: works as fine for me as before.

Andi
[ONE Original Android Development] ricardowec:
I agree. I've never had a WiFi issue with my OPO, your kernel and BlissPop. I have three routers at home and n at my office. The only tweak I have applied is the 100 sec in the scan interval.

Cheers
[ONE Original Android Development] HaTrED_:
I got that problem too some time ago! All of a sudden and without wondering why. Made some changes on my router - namely dhcp lease time that was infinite and from then it never gave me that error again!

Give it a try!

Tapatalked!
[ONE Original Android Development] andip71:
Good point.

An indefinite lease time already caused weird issues long time ago on the Galaxy S3.

So it is not recommended generally. And nothing is wrong to set the lease time to 24 or 48 hours.

Andi
[ONE Original Android Development] fmc000:
It was infinite and now how did you set it?
[ONE Original Android Development] andip71:
CM12.1 kernel update

Hi all,

new beta for cm12.1 is out for you:

Version 4.0-beta3

07.04.2015

Update: Updated with latest 6 official CM kernel commits as of 07.04.15

Side note: Due to latest CM kernel updates for CM12.1, Android logger is not configurable anymore as it has been completely removed

Ramdisk updated to version of 06.04.15

Cheers

Andi
[ONE Original Android Development] RCT1:
I've got that error for months on every roms, but since last week with Exodus rom this problem gone!
[ONE Original Android Development] HaTrED_:
5h!

Tapatalked!
[ONE Original Android Development] fmc000:
Thanks. Will try.

Speaking of the kernel: I couldn't be happier with it!! With my normal usage I had to charge the phone every two days, since I decided to try the Boeffla CM12 kernel I added at least one day. For example, at the moment after two days and a half I still have 30% of battery left. I'm using the Battery Friendly preset, some led tuning and nothing less.
[ONE Original Android Development] andip71:
Just to let you know:

The latest CM12.1 kernel I released this morning has updated wifi drivers included (LA.BF.1.1.1_rb1.17).

If these turn out to work well, I will also release them in all my other kernels (cm11, cm11s, cm12). The work on it is already done, so it would be just a question of putting them live for you.

But first I want to wait for some more feedback on these new drivers in combiation with cm12.1 :D

Andi
[ONE Original Android Development] andip71:
Anyone interested in purchasing an OPO for someone?

I just got two invites which are valid for 2 days.

First come, first serve.

Andi
[ONE Original Android Development] acuicultor:
Never had problems with WiFi on 5.1 I can only test speed of connection and didn't notice anything relevant with the new WiFi drivers, same download and upload speed like before also any disconnection like always.
[ONE Original Android Development] andip71:
Something new by mateepunkt :)

http://www.boeffla-kernel.de/index.php/58-boeffla-kernel-fan-trailer

Andi
[ONE Original Android Development] fjsferreira:
The 5.1 issue with wifi is across the board (every 5.1ROM) and a known issue (unless it's fixed since 2 days ago). And the problem is that wifi simply turns off by itself from time to time in 5.1, and won't turn back on. It's not related to routers, channels, authentication methods, etc. Only a reboot or a quick toggle of the airplane mode fixes it. This is a known problem that a lot of people have in 5.1, not kernel dependant (happens in stock too).
[ONE Original Android Development] acuicultor:
I'm aware of that but like i said before I'm not having this issue on any 5.1, just suffered the bug twice since 5.1 arrived to the opo scene
[ONE Original Android Development] alexbk66:
Reboot doesn't help, only airplane mode toggle. I use Tasker to toggle airplane mode on boot.

---------- Post added at 01:42 PM ---------- Previous post was at 01:38 PM ----------

Just wondering, to update to latest version, can I just flash the new kernel?

I hope I don't need to reflash the ROM to update kernel version?
[ONE Original Android Development] DerRomtester:
Just flash it
[ONE Original Android Development] andip71:
Go into Boeffla-Config app. Choose Action menu, then load&flash, everything goes automagically.

Andi
[ONE Original Android Development] alexbk66:
Even better! Thank you!
[ONE Original Android Development] Formhault:
I just flashed the latest CM11S + Boeffla 2.5 CM11S kernel (as secondary ROM, using MultiROM here) and... the screen turns off as soon as I accept / initiate a call and doesn't come back on even if I press the power buton...

EDIT : I just reflashed CM11S (so... no Boeffla kernel) and I've got the same problem.

Perhaps it's worth mentioning that my primary ROM is a Lollipop 5.1 one... maybe the CM12 firmware (radio & whatnot) have something to do with that? If yes, is there anything I can do to restore this functionality? I remember the same issue happened when I switched from a Lollipop 5.0.2 ROM to SlimKat (no MultiROM back then). :eek:
[ONE Original Android Development] Spaulding89:
[MENTION=4129455]Formhault[/MENTION] it is because u have the cm12 firmware. For CM11 you need the older firmware.
[ONE Original Android Development] Formhault:
God damn it. I flashed the latest CM11S build (which was 500+ MB). I thought it contained everything...

I found a flashable XNPH05Q modem and loaded it on the CM11S ROM. Now it works fine... Sorry for the false alarm [MENTION=947981]Lord Boeffla[/MENTION] :\
[ONE Original Android Development] casshern94:
feedback :

problem 1 : signal bar is empty but calls/msg/data works well.

problem 2 : whenever restart the phone,whatsapp require adjust time as time automatic sets at year 1970.

using unofficial cm12.1 by CraZY_BoY^

other than that,doesnt notice any bugs.

once again thank you lord boeffla :)
[ONE Original Android Development] andip71:
Can't confirm both here. Version of today...

Andi
[ONE Original Android Development] Reed-Sternberg:
I second the signal bar thing. A reboot fixes it for me though. Same for me, lte works, but no signal showing.

Euphoria 5.1 if that matters, but didn't have this bug on beta 2.
[ONE Original Android Development] alexbk66:
I flashed new beta for cm12.1, now phone locksup with screen off and button lights on. I have to reset the phone.
[ONE Original Android Development] geekynoob:
These are cm. Issues or rom issues.. Not kernel problems.. :)

Check the rom thread loads of people have these issues..
[ONE Original Android Development] andip71:
Might be an Euphoria thing.

Think the ramdisk I use is not (yet) 100% compatible with Euphoria.

Result of not yet having official cm12.1 nightlies.

Can all happen when experimental kernel is installed on experimental rom.

However, have no such issues on my side.

Andi
[ONE Original Android Development] Formhault:
Using the latest available Boeffla kernel for CM11S... phone won't wake up by double tap / power button (at least not in 9 out of 10 tries, so to say). If I plug / unplug charger, it comes online every time. :eek:

Trying to get a log now.
[ONE Original Android Development] andip71:
I am using CM11s on my main phone here. Never having any of the mentioned problems.

Double tap to wake works with no issues. And I use it approx 100 times a day.

Andi
[ONE Original Android Development] Formhault:
Just rebooted... same thing. I didn't have this happening 14 hours ago :eek:

Logs below :(
[ONE Original Android Development] andip71:
Important info for all users using the experimental CM12.1 kernel

Please note the message ZaneZam posted yesterday night:

http://xdaforums.com/showpost.php?p=59988738&postcount=776

In short: Do not use zzmoove governor when on latest CM12.1 as it can and most probably lead to various issues. Of course, as always, Zane is looking into it.

Andi
[ONE Original Android Development] Formhault:
Got a log. Hope it's helpful...
[ONE Original Android Development] 99x:
Did you flash OxygenOS by any chance, then restore your CM11S backup? If so you need to flash the O5Q modem as the OxygenOS modem breaks the proximity sensor (prevents accidental wake up)
[ONE Original Android Development] Formhault:
That's fixed. Had to flash CM11S modem, yeah. I'm using MultiROM :

1st "partition" : Resurrection Remix (5.1) -> latest CM12 firmware, modem & whatnot.

2nd "partition" : CM11S + latest CM11S modem.

The proximity sensor works fine now. At least in calls, screen goes on and off as it should. But when I try to wake it up... :eek:
[ONE Original Android Development] andip71:
But note, now your proximity sensor is likely broken on cm12. The firmwares are just not compatible.

Andi
[ONE Original Android Development] Formhault:
I don't think so. They shouldn't interfere with each other, because the CM11S modem has been flashed specifically on the CM11S ROM "partition", while the CM12 firmware has been flashed specifically on the Resurrection Remix ROM "partition".

Everything works just fine. Except for the wake on CM11S... I guess I'll have to do a full wipe on that side and see how that goes.
[ONE Original Android Development] acuicultor:
I bet you don't know that is impossible to do in opo's multirom, you can see the option but in fact is useless, check the thread and see for yourself that this feature isn't implemented.
[ONE Original Android Development] 99x:
As a workaround, if you haven't already done so, try disabling the 'prevent accidental wake up' in display settings on CM11S. When you try to wake up the phone it checks the proximity sensor which likely isn't working properly and so fails to wake.
[ONE Original Android Development] andip71:
New CM11, CM11s and CM12 kernels

Hi all,

not really planned, but I decided to release another beta now for the CM11, CM11s and CM12 kernel.

Basically main change is, that I backported the latest wifi drivers from CM12.1. Maybe it is of help for some with wifi issues.

Here we go!

CM11/CM11s -- Version

2.6-beta1

CM12 -- Version 3

.2-beta1

09.04.2015

Wifi drivers LA.BF.1.1.1_rb1.17 backported from CM12.1 kernel branch

Flashable recovery zip file is now signed, i.e. you can use signature verification in TWRP or CWM recoveries

Minor internal improvement

Enjoy

Andi
[ONE Original Android Development] claptraw:
Still zzmove issues with this one?
[ONE Original Android Development] andip71:
Only on CM12.1, due to the latest code changes CM team did (suspicion).

And do not expect a quick fix, will take some time for ZaneZam to figure out where this is coming from.

On CM12, CM11s and CM11 all should be fine with zzmoove.

Andi
[ONE Original Android Development] NickosD:
No, just with the 12.1.

Sent from my bacon!!!!!
[ONE Original Android Development] suaverc118:
Would it be OK to stick with beta 3 then or will it cause some issues because there were some kernel merges?
[ONE Original Android Development] andip71:
Try it. If beta3 runs fine, there is no need to not use it.

Or latest beta and with a different governor for some time.

You have the choice :)

Andi
[ONE Original Android Development] suaverc118:
Sorry, I meant beta 2. Beta 2 had no issues but is slightly older. Is it OK to use with the latest nightly using the working zzmove?
[ONE Original Android Development] fmc000:
[MENTION=947981]Lord Boeffla[/MENTION] : when 3.4.107 is released (Tomorrow or Saturday), do you think you will port some or all your kernels to the new release?
[ONE Original Android Development] andip71:
Likely, yes.

Andi
[ONE Original Android Development] tracerit:
Possible to add swipe nav bar to turn display off?
[ONE Original Android Development] andip71:
Possible for sure.

However when you mean the notification bar at the top with "nav bar", I think it does not make too much sense as you just need to double tap it to put the device to sleep.

Andi