yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Z3r0byte:
Thank you, using version 3.1.1-0 indeed fixed the problem. :good:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Another solution is to flash latest beta kernel instead of stable version.

Changes to provide compatibility with latest TWRP version are only in latest betas.

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Hi all,

new update of Boeffla-Kernel is just released.

Version

2.2-beta3

27.07.2017

New: Boeffla charge analysis (display of charger type and charge current in Boeffla-Config app in real time - note, the charge current may not be extremely accurate)

Enjoy

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] erifla:
Run in beta 11
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Was that a statement or a question?

If it was a question, look at OP.

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lstion:
Support wakelock?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Can you please try to ask a proper question, which is a full sentence and not only two word?

Support wakelock means nothing to me, so the natural anwer is: of course.

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lstion:
Sorry:angel:,Support IPA/TIMERFD/WIFI/NETLINK wakelocks disable?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
No, I do not support that.

These wakelocks are there for a reason, I personally don't think they should be disabled.

But convince me, why would you want to have it? Do you have experience with those disabled wakelocks, if so... what kind of?

Which device, rom, kernel etc?

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] FloGatt:
I am very interested in the reason. Can you explain that?

I personally disable these wakelocks since a few months and i do not have any problems (like not getting notifications).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Wakelocks exist to prevent the device to go into sleep mode within specific code blocks.

Sometimes this is very neccessary, especially in device drivers where a sleep condition causes unexpected effects.

If there were no reason for a wakelock, why would the original developer put them in? (it is something he actively needs to do, this does not come from itself). And I assume, the developer of some code knows why he put a wakelock in.

This my general opinion, people can share or not.

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] kessaras:
Only 3rd party app or gapps wakelocks are really safe to block but not in a kernel level. The dev is not a magician to start adding random wakelocks blockers. For example one wakelock, not really important , is in the Google maps. Google knows where I parked my car ! Google knows where I live due to the time I spend there. Google knows where I go to swim. Google knows my every move ! Lol. Anyway those are wakelocks for example safe to block.

Wakelocks such those mentioned may cause other random bugs. Maybe not for you , but for someone else , depending the way we use the phone ! Not all of us make the same use
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Thanks, this confirms my opinion 100% :)

We are on the same track!

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] valence23e:
this is compatible with opern betas right? installed this on my OB11, but after that, i cant connect to my wifi. did i do womething wrong? I tried reflashing without the kernel and the wifi works. so definitely its not a hardware issue. hope you can help me with this. thanks!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
No!

It is clearly stated in the OP it is NOT compatible with open betas.

And no, I cannot help you with this as I do not make any changes for inofficial (open beta) stuff.

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] EinsteinXXL:
[MENTION=947981]Lord Boeffla[/MENTION] Are the Qualcomm DIAG kernel drivers (DIAG_CHAR) included in your kernel? Need this for snoopsnitch app.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Quoting from boeffla_defconfig file:

#

# Diag Support

#

CONFIG_DIAG_CHAR=y​

So, yes, are activated.

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Hi all,

new kernel update is out:

Version

2.2-beta4

17.08.2017

Note: Boeffla-Config version 2.4.49 or newer is required to configure all functions !!

New: Display backlight limiters added (for min and max brightness)

- This ensures brightness is within a configured range, perfect to "fix" for e.g. aggressive automatic brightness control

New: Added maple IO scheduler (Click here for some details)

Change: Improve safetynet handling (credits to SultanXDA)

Change: Internal improvements in kernel start script

Update: Build warning fixes

Enjoy

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Rootax:
Working great here, as always.

Thx !
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] MartinMo:
Hi Lord Boeffla,

I just stumbeled upon a bug in Boeffla Config V2 version 2.4.50 on my OnePlus 3T with OOS 4.1.6. I wanted to copy the name of a profile to paste this name in MacroDroid to activate this profile via "send intent" when the battery drops below 20 %. So I opened the menu with all the profiles and choosed "Namen editieren", marked the complete name, copied it and then I clicked "OK". Afterwards the profile was gone, it had disappeared, because I renamed the profile to the name it already had. I can reproduce this problem anytime, even with the active profile. Afterwards I had to reboot the phone twice for the app to work normal again. Renaming only works, if I choose a different name. Now I know I should have chosen "Abbrechen" (cancel) instead. Could you fix this? Would a fix make my lost profile reappear again? Thanks for all the good work. I especially appreciate the new possibility to limit the display brightness. Which would be a better name, would it? As its an OLED display there is no backlight, right? Anyway: Thank you very much!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Will look into this problem with the app. Thanks for reporting.

I cannot comment on whether you can get back your profile before I analyzed what the problem is. But I assume it is probably deleted.

Good you surely took an export into a bcprofile file before, or you have a titanium backup which would restore the profile again [emoji6]

And on the other input... Technically it is still called backlight in the drivers, so it is just a terminology thing.

I think about a rename later.

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] MartinMo:
Thank you Andi!

I just did a "rebuild" of the profile and already have done a Titanium backup (the previous was to old).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Thanks MartinMo, that was really an "ugly" bug in the app since day one. Interesting nobody ever stumbled across it.

I fixed it already and will test it now. Then will ship app version 2.4.51 still today.

Thanks for reporting it.

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Hi all,

OnePlus just released OOS 4.1.7, so here we go for an updated kernel already (seems to run on 4.1.6 too in a quick smoke test):

Version 2.2-beta5

22.08.2017

Note: This kernel version is only for OOS 4.1.7 or newer!

Change: Update with latest OnePlus code drop as of 22.08.2017 for OOS 4.1.7

Change: Internal kernel busybox updated to latest version 1.27.2 (self-compiled from sources, www.busybox.net)

Enjoy

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] androidware:
Hi andi, i follow You from galaxy S3 forums.. my New device op3t and i'm happy to see you here..

ONEPLUS A3010 cihazımdan Tapatalk kullanılarak gönderildi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Thanks my friend. Nice to hear :)

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Hi all,

new update is out.

Version 2.2-beta6

06.09.2017

Note: This kernel version is only for OOS 4.1.7 or newer!

New: Boeffla generic wakelock blocker added in version 1.1.0 - this is an expert function only, so please click for the usage guide on Boeffla homepage

(Note - the following wakelocks are blocked by default already: qcom_rx_wakelock, wlan, wlan_wow_wl, wlan_extscan_wl, netmgr_wl and NETLINK)

New: Boeffla touchkey LED control driver - which gives you full control over your touchkey light (LEDs fully off, LED on screen touch, configurable duration etc.)

Change: cpuidle driver tweaked

Enjoy

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Sam Nakamura:
Hey Andi,

what changed your mind regarding the wakelock blocking, I remember your previous statement from not to long ago where you explained in detail why you see blocking this system functions rather counterproductive...

I found it to be a conclusive reasoning, that's why I wonder what made you change your mind :)

Regards

Sam
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
It was... knowing the theory on one hand side, but giving it a trial in real life on the other side. Call it curiosity :)

Indeed I could not find any negative side effects (till now) with some blocked wakelocks while it seems to improve battery life quite a bit (at least on the OP5 where I tested it).

Sometimes one has to try something to be more open minded. This is what I did.

But also: My implementation of the wakelock blocker is fully flexible. This is the key for me, so if it causes an issue for someone under specific circumstances, also the default wakelocks can be changed without me having to push a new kernel version. And of course the way I did the blocker driver is generic, so you can freely add additional kernel wakelocks and experiment without any risk.

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] crian:
Is the newest stuff from the oos beta merged in?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] uaiclout:
I don't think so as beta is generally not supposed (mentioned in OP)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
NOOOOOOOOOOOOO !!!

Just read the OP, I am not caring about the open beta stuff. Never did, never will...

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] ScratMan38:
It's really nice to provide such feature. However, it looks like your wakelock blocker simply blocks the wakelock forever. I was using Amplify on Android 6.0 with Xposed framework to block wakelocks, and the most interesting feature was to be able to block wakelocks for a selectable duration.

Example on the NLPwakelock from Google services. It constantly polls the location of the device, several per minutes, and it is known to be a major battery drainer. Blocking this wakelock dramatically reduces the capability of the phone to notify you according to your location (for example for "time to leave" notifications from the agenda).

With Amplify, the user could select the duration in seconds between two accepted wakelocks ; so you could only accept to make it wake your phone once every 5 minutes.

This allows to keep some functionality active, while controlling its recurrence, hence reducing battery drain.

Maybe you could add such timer option in your blocker, in order to give more flexibility.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Hi,

yes, the blocked kernel (!) wakelocks are blocked forever, do not mix it up with wakelocks created by apps which are not affected by the wakelock blocker in my kernel (for this you have to still use other ways of blocking it).

A functionality to block wakelocks ony for specific durations would be over the top and not efficient anymore (would require keeping wakelock statistic lists in kernel memory = no go).

That is why only "safe" wakelocks on kernel level are blocked by default. People can try and add additional kernel wakelocks as they want and experiment.

I will keep this simple wakelock blocker therefore. Someone who wants more granularity can still use the existing apps and frameworks for it.

I - by the way - am against blocking any wakelocks required by apps as usually there is a reason for it.

So I am sorry, no further extensions planned. It was never the intention to replace other solutions for it, but provide a simple way of efficiently blocking specific, safe, kernel wakelocks. So I am coming from a different angle.

Thanks

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Ok folks, time has come: I am starting to a small 10-days holiday break now. Visiting Oktoberfest in Munich and roaming around with my friends from Florida in the Berlin area.

This means: No update on kernels an app in the next days. Whatever happens in the world, I am away from home and could not do anything.

Please also note, support from myself will be reduced to a bare minimum per nature. I try to read from time to time in the forums, but I will not have the chance for any detailed answers.

CU all again Monday the week after next.

Have a great time

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Rootax:
Enjoy your holidays :)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] xQuantum:
How to block wakelocks using boeffla app? I didn't find that option like the one on EXKM app
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Sam Nakamura:
Try Boeffla's own wonderful kernel manager then, I'm sure you'll find there...

Edit: EX puts wakelock control usually under "miscellaneous", if you haven't checked already :)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] xQuantum:
I said I'm already using that app and didn't find it.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Sam Nakamura:
Yeah, lol :) my eyes, am sorry...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Saenic:
I tried installing the Oneplus 3T kernel on my Oneplus 3T and the installer says it's a Oneplus 3 and therefore it does not install.

I'm using Freedom OS Rom (for Oneplus 3T obviously), might this be the case ? My device is correctly displayed as A3010 in preferences. Should I use the Oneplus 3 kernel then?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] dcop7:
Check if you have the last version of TWRP. If you have TWRP 3.1.1-2 it was a bug identifying the correct device.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Saenic:
I'm using the latest TWRP 3.1.1-2 from https://eu.dl.twrp.me/oneplus3t/
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] dcop7:
Flash TWRP 3.1.1-0 and try it.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Saenic:
This did the trick, thanks
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Hi all,

update of Boeffla-Kernel for yesterdays OOS 4.5.0 release:

Version 2.2-beta7

26.09.2017

Note: This kernel version is only for OOS 4.5.0 or newer!

Change: Update with latest OnePlus code drop as of 25.09.2017 for OOS 4.5.0

Enjoy

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] MartinMo:
Thank you Andi! I was a hole day without Boeffla Kernel, since I already had done the backups I didn't want to wait with updating to 4.5.0. I missed quite a few things, nice to have the update.

---------- Post added at 08:14 PM ---------- Previous post was at 07:56 PM ----------

I noticed a bug on my 3t: The setting of the notification LED brightness doesn't change the brightness at all. It doesn't matter what I set there as a value the brightness stays the same. Is this only happening on my phone or is there anyone else who can replicate this?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Not a bug, it is a feature.

It does only influence the brightness of "static" lights (i.e. no blinking or fading, here it seems impossible to control it).

So you can for instance put it on 1 to switch off the battery charging light. Thats the only thing it is useful for.

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] draiyan:
Can you post and share your profiles/settings/configs?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Whom did you ask now?

There is a dedicated thread for the OnePlus3 (T) profiles, link is on www.boeffla.de in the download section.

I personally do not use the OP3(T) as my daily driver phone anymore, but I remember I was sticking pretty much to Boeffla defaults when it came to hard stuff like governors and schedulers as I needed highest stability. I did more change some comfort stuff like notification LED settings etc.

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] draiyan:
It was meant for everybody. Thank you for responding :)

Thanks for the info, I didn't see that, but I'll check. I was trying the swipetoopen, wouldn't work. Is it supposed to open the screen when you swipe on the proximity sensor?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Swipe to wake: Phone is sleeping, then you swipe the screen from left to right, right to left, up to down, down to up, to have screen going on. Has nothing to do with proximity as such.

It works.

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] draiyan:
Thanks! I was doing it wrong.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] dave2775:
Anyone having issues with WiFi? Can't use mine at all? Never had issue before and just flashed this kernel for the first time
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] seabro01:
Been using this kernel for a couple months. Never had any WiFi issues. Are you on official stock OOS?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Nope. No wifi issues known.

Did you you flash stock kernel first?

Flash again, maybe the wifi drivers were not flashed correctly.

Otherwise it would be good to get some more details what "can't use at all" means.

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] gr8techie:
I am facing such issues but they seem to be caused by the recovery that you are using. Seems unrelated to kernels at the moment.

The problem it seems is that our 3t shows up as a OP3 and this is why it may be happening. All this started with the official twrp 3.1.1 and above. When i was using Blu_spark v37 twrp it was ok initially but had to upgrade TWRP as flashing OOS 4.1.7 with it was messing up things.

The wifi problem is that it will scan and find the WIFI network but when you give the network key or wifi password, it will try to connect, fail and then just show as saved.

I tried flashing the firmware, the stock boot image and then the kernel.

Is there something I am doing wrong or you can help me with this problem? If you need logs them from where can i get them?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Weird. I think you do everything right.

Are you using latest official LineageOS rom, or something else?

It works just fine here...

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Pablo.x:
Hi Andi, I have a problem running boeffla-config on OOS 4.5.0

Everytime I start the app it shows a pop-up asking to disable "battery optimization", despite I mark the app as "not optimized", it makes no change.

I mean, it stills as "optimized". Also, that menu isn't accessible on OxygenOS settings, only via boeffla-config app at the start.

Anybody facing this too? It's so weird :(

Thanks for your great work anyway, this kernel rocks as always!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
First - make sure you have latest Boeffla-Config version installed (2.5.02).

Second - do the following:

Open rom settings

Go to battery

Go on the three dots in the right upper corner and select "aggresive doze & app hibernation"

Then switch the switch to ON for Boeffla-Config V2

When you leave the screen and go in again, Boeffla-Config must show under "not optimized", if not something is wrong in your rom.

This is the only way that really works. OnePlus team changed the standard screen Android comes with for battery optimizations with their own one, however both screens are still available in code (and can be opened independently when you know how + the settings are not the same even).

The thing is now... OnePlus does not use these screens consistently across devices. In OOS 4.5.x for OP5 the new screen is used, on OOS 4.5.0 for OP3(T) the old screen is used, but the new one is available too. So my app always tries to open the OnePlus-specific screen first, which is wrong on the OP3T.

I honestly have no idea how to better fix this, apart from putting some real ugly version check stuff into the app - which I would love to avoid. Will think about it...

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Pablo.x:
Wow great! Now it's working fine, thanks a lot Andi.

Didn't know anything about that <3
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Oh yeah, sometimes OnePlus makes it really hard to develop for them.

I assumed in the app, when they have the new screen in code, they also use it. Which is only true on the OP5, but not OP3. Bummer.

Anyways, I changed the app now to handle this for the moment. I am just waiting for the point in time when they start to use their new screen on the OP3 too. Then my app cannot do it right anymore for everyone. But we will see.

Anyways - this improvement will be in the next app for the OP3...

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] RASTAVIPER:
No such problems with 4.1.7/4.5 and the TWRP that you have mentioned.

Unleashed by ONEPLUS 3T rooted
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] lrobberl:
Hi guys!

Ever since I have updated to the 7.1.1 built ROM I face random soft-reboots happening during the night (more than once according to the graph of Gsam Battery Monitor). This happens while the phone is charging, and I noticed it because I saw the Boeffla notification of the profile I have applied every morning. I saw the official forum that other people face the same issue. Can anyone help me? How can I create a log to try to understand more about the issue?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
What do you mean by "official forum"?

There is no way to get a useful log for soft reboots most of the time.

We cannot help more, as you have not given us any useful info about rom information, configuration, etc etc.

Also, soft reboots are no kernel panics but usually come from user space (rom, apps).

I personally do not have any reboots on OOS on this phone. So I guess you should consider a fresh install, and not use the usual crap that can cause soft reboots.

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] thethinkman:
Thank you for making this brilliant kernel available! I am on latest official lineage OS nightly, my device is encrypted, and I use Magisk for root. On the page Miscellaneous 1, the System Tweaks section is gray and not expandable. Is this expected behavior?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
On the OnePlus 3 (T) devices - yes, there are no system tweaks implemented for these phones.

And btw - you are in the wrong thread. This is the OOS thread, not LineageOS.

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] RASTAVIPER:
I updated your app today and noticed one message about Xposed.

Do you expect some sort of conflict with your app in the future, so you prefer to warn users in advance?

Unleashed by ONEPLUS 3T rooted
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
This message is in for more than a year already, funny you saw it only today :)

There are no conflicts per nature as such, but users should be aware xposed can cause all sort of issues. I warn about it, as I also do not provide support when someone uses xposed - just like vendors and LineageOS team too.

So, if you have your xposed and your modules fully under control, you can ignore the message.

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Pablo.x:
Going to flash new Oxygen 4.5.1, let's see what Optimized apps menu it has hahaha.

I don't know if there are any kernel changes so I'm not sure if it's safe to install latest beta.

I will come back in a few minutes to report about oxygen's menu :)

Edit: well running lastest boeffla kernel beta fine and optimized apps menu it's still the same that was on 4.5.0 (the new one)