yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] budbay:
After a reboot I am getting a kernel wakelock "6a00000.ssusb" that prevents phone from sleeping until I plug in a charger. Then after I unplug the charger, the wakelock disappears and phone sleeps normally. I had this on POSP pie encrypted with custom r3 but was planning on moving to skydragon so didn't think much of it. I moved to skydragon with custom r4 and did not have the wakelock, but because of encryption had some issues booting up occasionally, now I flashed custom r5 and it boots normally but the "6a00000.ssusb" wakelock is back until I plug in a charger. I grabbed log of dmesg after boot, its rather long so can post if needed.
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
thanks for reporting.. expect a fix in the next build
[OnePlus 3 & 3T Cross Device Development] shady_soldier:
I seem to be having issues with Magisk versions post v17.3. No matter what I do, installing magisk v18.1 or the latest beta breaks safetynet for me, going back to v17. 3 somehow is the only way I can use magisk without breaking safetynet.

Am I missing something?

Thanks in advance!

PS : I love this kernel and highly appreciate your work!
[OnePlus 3 & 3T Cross Device Development] MrxSiN:
Forgive me for asking, if im on stock oos, then unlocing boot loader, then flash this kernel and magisk, will it trigger dm-verify?
[OnePlus 3 & 3T Cross Device Development] iAmWiz:
No.
[OnePlus 3 & 3T Cross Device Development] henk717:
I am still getting boot issues on this kernel r5 release (Custom) when combined with AospExtended 5.8.

The device gets stuck at the OnePlus bootloader logo and then after a long wait reboots to the bootloader menu.
[OnePlus 3 & 3T Cross Device Development] phoberus:
I had the same thing one time on Los16. But for me, it rebooted to the recovery. I tried it 3-4 times to reboot to system and then it worked. Since then, no problems
[OnePlus 3 & 3T Cross Device Development] henk717:
Strange, not sure what it does between reboots but you are correct if you try it enough it will then start working consistently.
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
Try to use magisk 18.1. We assume that magisk version 19 could be one issue.
[OnePlus 3 & 3T Cross Device Development] Tibiti:
Mine is not encrypted yet I had the same issue with r5. On r4 without issues apart from an occasional white led death (only reboot helps).

Using the latest version of AOSiP.
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
which magisk version do you use ? try to use 18.1 if not already
[OnePlus 3 & 3T Cross Device Development] Tibiti:
v19
[OnePlus 3 & 3T Cross Device Development] iAmWiz:
The problem still persists. After the screen goes off twice, it doesn't come back on.

Hi, I want to try and get the exact commits from mady. He seems to have permanently solved my screen issue in his kernel. I'll pm them to you, once I get them.

Is it okay?

Got the link from Mady. Here it is >> https://github.com/mady51/OmniPie/commit/ebf6bfab321bfee0f243023a44f1c9ab57935acb

Thank you
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
mcd-kernel-custom-r6-1

[Custom-Rom-]Kernel update!

Encrypted devices and magisk v19 are supported now. No more random reboots or reboots to bootloader [finally].

Installation:

Do a dirty flash of your current ROM if you were on a mcd-kernel-custom build below version 4.

Magisk [or any other root solution] is mandatory on some ROM's [e.g. Havoc, LineageOS] to apply our custom values. Ensure that "schedutil" is your active governor after your phone booted.

Changelog:

reworked your anykernel2 installer

fix bootloop on encrypted devices

fix usb-otg wakelock

fix third party display wakeup

fixed spectrum support and adjusted a bit our profiles [profiles won't be exported anymore to your /sdcard]

rcu subsystem upstreamed

added governors: helix_schedutil, blu_schedutil, pwrutilx, emergy-dcfc, darknesssched, alucardsched

revert fsync toggle

revert latest op3/t slider changes - [you may need to re-configure your slider options again]

block [kernel] wakelocks by default

many misc stuff

disable even more log spam

Download:

mcd-kernel-custom-r6-1.zip

changelog-custom-r6-1.txt​

Notes:

Feedback is highly appreciated

You may delete the data of your kernel-tweak app to see/apply the new default values

Telegram-Group:

t.me/mcdkernel

Small note:

I do not like to say this, but since I spent a lot of time on this project, I would be happy if you would consider to do a little donation: paypal.me/mcdachpappe
[OnePlus 3 & 3T Cross Device Development] phil_greg2001:
Hi mcdachpappe,

Have you planned to add the changes in the OOS kernel?

Many thanks

:svetius:
[OnePlus 3 & 3T Cross Device Development] allgrey:
Please explain differencies betweeen these new governors. Whats more smoother?
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Are you planning to bring these governors over to OOS kernel build? Also, can you please provide a brief overview of battery life vs performance ration on these new governors?
[OnePlus 3 & 3T Cross Device Development] NetSkill:
Now based on holydragon kernel....

And here we go glitchy screen again :( I can't believe that caesium kernel is the only one without screen artifacts during video playback..

And no I don't have third party screen yes its been replaced but officially by OnePlus.
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
mcd-kernel-oos-r23

update time!

Changelog:

fix usb-otg wakelock

fix third party display wakeup issue

add spectrum support and import our profiles [balance, battery, performance, gaming]

added governors: helix_schedutil, blu_schedutil, pwrutilx, emergy-dcfc, darknesssched, alucardsched

add some missing K-Lapse changes

some minor adjustments

Download:

mcd-kernel-oos-r23.zip

changelog-oos-r23.txt​

No: I'm not going to explain all the governors - i'm confident that you can do some research by yourself.

Notes:

Feedback is highly appreciated

Dirty flashing is fine

You may delete the data of your kernel-tweak app to see/apply the new default values

Telegram-Group:

t.me/mcdkernel

Small note:

I do not like to say this, but since I spent a lot of time on this project, I would be happy if you would consider to do a little donation: paypal.me/mcdachpappe
[OnePlus 3 & 3T Cross Device Development] TangelSaki:
having the same doubt......
[OnePlus 3 & 3T Cross Device Development] phoberus:
Just had the same bug again. First I dirty flashed Rom and then r6-1. But my Los16 version is also about one month old, so this could be the reason. I am not encrypted.
[OnePlus 3 & 3T Cross Device Development] phil_greg2001:
Hi was on OOS 5.08 with FrancoKernel and after install your kernel the wifi doesn't work :crying:

I have try to install another kernel blu_spark r218 or FrancoKernel and the wifi works again... strange :silly:
[OnePlus 3 & 3T Cross Device Development] Paschfire:
Did you remember to dirty flash OOS 5.0.8 ROM between different custom kernel installs?

If not, you should be doing so. As it resets to stock any changes made from the previous custom kernel install.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Rule of kernel flashing: Never flash a custom kernel on top of another custom kernel, unless it's the same custom kernel but an upgraded version. Franco and mcd are two entirely different kernels and you should have dirty flashed OOS before flashing one on top of another.
[OnePlus 3 & 3T Cross Device Development] cacio_confusa:
Please allow 2.4A charging. Right now its capped at 1.5A . so while dash charge is awesome, the experience you have without it is really bad. Even Iphones charge faster.

And 2nd improvement you could add:

Make the LED much brighter. Its like a cheap ass 80€ phone. And even those have brighter LEDs

The Max rating is like 500mA ,

But the default value one plus sets is like 113mA iirc

Sultan XDA has made a patch back in the nougat days on his cm14 builds for improving camera quality @ night.

And even GCam does not trigger the camera "flash" power state if you have HDR+ on. Only of you have it disabled.

So for improving camera performance at night and pure flashlight use, please increase the power state values. I would start with 250mA and let it on for a while. Just to check the thermals. Which is the only thing we should worry about. As long it stays reasonably cooled, we could increase the mA further.

Thanks
[OnePlus 3 & 3T Cross Device Development] iceman0826:
Just my 2cents regarding the different flavors of Schedutil. Below are my findings regarding for best performance / gaming oriented governors (sure 60fps mode):

- Schedutil

- blu_schedutil

- Helix_schedutil

Battery saving only mode:

- pwrutilx

- energy-dcfc

Not so pure schedutil variant (defeats the purpose of schedutil feature):

- darknesssched

- alucardsched

PS. I know it's better if I post some numbers, but don't have much time to do that. I assure you though that I've researched about the 1st three flavors and they're good for daily use - assuming you're not hardcore about battery life. ?
[OnePlus 3 & 3T Cross Device Development] iAmWiz:
Hi there,

What governors are you using for little and big cores?

I am using schedutil for both cores and it's still great. I would just like to know your config.

Thank you
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
mcd-kernel-custom-r7

[Custom-Rom-]Kernel update!

I tried to add kali.nethunter support back again to our kernel. These changes still have to be verified. So please consider some feedback if you are able to test this somehow.

Installation:

Do a dirty flash of your current ROM if you were on a mcd-kernel-custom build below version 4.

Magisk [or any other root solution] is mandatory on some ROM's [e.g. Havoc, LineageOS] to apply our custom values. Ensure that "schedutil" is your active governor after your phone booted.

Changelog:

merged latest stable-linux v3.18.138

HID keyboard/mouse gadget support [by jcadduono]

Packet injection patch [needs testing]

USB - OTG External WiFi adapter support - "monitor mode" [needs testing]

Download:

mcd-kernel-custom-r7.zip

changelog-custom-r7.txt​

Notes:

Feedback is highly appreciated

You may delete the data of your kernel-tweak app to see/apply the new default values

Telegram-Group:

t.me/mcdkernel

Small note:

I do not like to say this, but since I spent a lot of time on this project, I would be happy if you would consider to do a little donation: paypal.me/mcdachpappe
[OnePlus 3 & 3T Cross Device Development] iceman0826:
I've set them both on Blu_schedutil, as it seems it provides better battery savings without sacrificing performance - it turns on when you need it (i.e. gaming).
[OnePlus 3 & 3T Cross Device Development] iAmWiz:
Thanks a lot. I'll set it on R7
[OnePlus 3 & 3T Cross Device Development] mrmcshagbag:
Let me know how this kernel works on pubg please. I'll try it out if its worth it later. I play 30fps 1600x900 resolution with very little lag on holy dragon kernel. ? thanks
[OnePlus 3 & 3T Cross Device Development] iceman0826:
Pretty much it's a hardware limitation, but still, PUBG is an unoptimized mess.
[OnePlus 3 & 3T Cross Device Development] mrmcshagbag:
Right with how much money they make on that game you would think they would optimize it to work on flip phones at 60fps by now haha ? sorry for the off topic OP.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
This is the only kernel that has helped me play pubg consistently for hours on 40fps on balanced with 720p resolution. But the issue is, pubg is more optimized for newer chipset and mostly works on them because of 8-core CPUs. It's an unoptimized mess that no kernel can really help us with.

If you want to try this one with OOS, the r18 was the last best release for pubg in particular. All released after that don't provide same performance. I'll flash and try r23 now
[OnePlus 3 & 3T Cross Device Development] iAmWiz:
Works great on PUBG.

720p

2x Aliasing

Balanced

40 fps

Light effects disabled.

I'm using blu_schedutil and helix_schedutil for little and big cores respectively.

Good luck, mate :)
[OnePlus 3 & 3T Cross Device Development] dzwietering:
Interesting, how did you choose the governors?
[OnePlus 3 & 3T Cross Device Development] iceman0826:
You need an Kernel App Manager for this (i.e. EX Kernel, Smart-pack etc.)
[OnePlus 3 & 3T Cross Device Development] dzwietering:
Thanks, I know how to do that. What I would like to know is how he made the choice for that configuration.
[OnePlus 3 & 3T Cross Device Development] iceman0826:
Depending on the app, you can assign different governor for the little and big cores. The general idea is, you just need to tap on it and select the available governors for each.
[OnePlus 3 & 3T Cross Device Development] dzwietering:
Right, I know the tools, I can change governors (since messing around on my Nexus One), was just wondering what the experience is with the various governors that led to using blu and helix in this case.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
I second this. I played a single 25 minutes' game of Pubg (i'm sorry for going off-topic here), and i can say this blu_schedutil on both big.little cores also works great! No lags, no frame drops (except scenarios where even my wife's OP6 also drops frames and lags), and what impressed me the most is, the heat generated was significantly lesser than what it used to be with r18. I was playing in the same usual room, same WiFi, same phone, same settings, and the phone heated up "to some extend", but it didn't get crazy hot like it used to with schedutil. I am impressed so far and will continue my tests going 40fps on balanced now.

---------- Post added at 07:23 PM ---------- Previous post was at 07:20 PM ----------

I think it all comes down to user preference. Since big little cores were introduced, it was really possible to set 2 different governors for the 2 types of cores to get desired results. I've played around a lot with interactive on Little and Conservative on Big cores but tbh, I've always found more fluidity with Interactive on both cores.

So you can just use some performance oriented governor on little cores and a battery friendly one on big cores. Just test and see what suits your needs! :)
[OnePlus 3 & 3T Cross Device Development] henk717:
Still getting the extremely unreliable boot experience on the latest custom_r7 release.

Wiping cache will fix it for a little while but the problem always comes back.

This is on the AospExtended 5.8 rom on a OnePlus 3T that is encrypted and contains a(n empty) vendor partition.
[OnePlus 3 & 3T Cross Device Development] essamnasir:
Has anybody tried this kernel with pixel experience ROM.
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
mcd-kernel-custom-r8

[Custom-Rom-]Kernel update!

Merged around 600 f2fs commits - we are up-to-date again.

Installation:

Do a dirty flash of your current ROM if you were on a mcd-kernel-custom build below version 4.

Magisk [or any other root solution] is mandatory on some ROM's [e.g. Havoc, LineageOS] to apply our custom values. Ensure that "schedutil" is your active governor after your phone booted.

Changelog:

init: update magiskpolicy; add custom sepolicy rules again

merged f2fs-upstream v5.1-rc1-3.18

update wlan qcacld-2.0 driver to v4.0.11.213X

silence more logspam

Download:

mcd-kernel-custom-r8.zip

changelog-custom-r8.txt​

Notes:

Feedback is highly appreciated

You may delete the data of your kernel-tweak app to see/apply the new default values

Telegram-Group:

t.me/mcdkernel

Small note:

I do not like to say this, but since I spent a lot of time on this project, I would be happy if you would consider to do a little donation: paypal.me/mcdachpappe
[OnePlus 3 & 3T Cross Device Development] cacio_confusa:
[MENTION=7030109]mcdachpappe[/MENTION] comment please. thanks
[OnePlus 3 & 3T Cross Device Development] habylab:
I'm interested in whether the majority of users are on custom ROMs or OOS. I've been away from the scene, using my OP6, and am updating my OP3 for a friend. Shall I stick to OOS, or are custom ROMs working really well now for this device (camera etc.) and on this kernel.
[OnePlus 3 & 3T Cross Device Development] Tibiti:
I'd wait until OOS Pie comes out if I set it up for a friend, but then again I only had factory firmware for 3 days in 6+ years.

Can't say about the camera but GCam ports give good enough pictures.

Custom pie roms seem very stable and usable to me, I use AOSiP (but DU is mighty fine as well) and it's a treat with this kernel. Skydragon or Havoc comes with OOS camera.
[OnePlus 3 & 3T Cross Device Development] phoberus:
Most people are on a Pie custom rom, but this will chance after OOS Pie open beta is released
[OnePlus 3 & 3T Cross Device Development] Tibiti:
Not for me, can't beat 'software support' of customs roms.. ?️

That's why I bought this phone.
[OnePlus 3 & 3T Cross Device Development] habylab:
Thanks. I don't think there will be an open beta, just a final release. It sounds like the closed beta has gone really well, so we could expect a final update before the end of the month.
[OnePlus 3 & 3T Cross Device Development] xuser_:
[MENTION=7030109]mcdachpappe[/MENTION]

Thanks for porting EAS to pie :)

Have heard that EAS would really perform better with kernel 4.9, how could we check if works closer to pixel's EAS kernel?

Thanks again for the hard and wonderful work.
[OnePlus 3 & 3T Cross Device Development] qhsusb_bulk:
It is really hard to port new kernel versions to android devices, especially with major version changes and especially for this device.

I saw many developers with different projects or cooperating in same project for porting 4.X kernel to OP3, all of them are abandoned because our phone's drivers are problematic and it has very deep issues. Example: they couldn't fix camera HAL so kernel failed to boot, etc. So 4.X kernel is probably a dream for this phone, sorry.
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
Alright let's see what we've got here:

Charging: Do you mean something like this? https://github.com/mcdachpappe/android_kernel_oneplus_msm8996-hdk/commit/f55af209f7fe3df36fb79a179d21e98724aa509c

Flash light: Are you talking about this? https://github.com/kerneltoast/android_kernel_oneplus_msm8996/commit/3188b6cf6708c23fa22004d7a5bc586d9213514d

1. Charging: The commit mentioned above has been reverted by holyangel [developer of holydragon-kernel]. I can [re-]add it again if you like.

2. Flash light: Sultan-xda reverted the commit i pointed out one month later: https://github.com/kerneltoast/android_kernel_oneplus_msm8996/commit/e1bfe28c4fa56cc45bc80b546577cc0e5e7d5849. Besides that: Our current value for torch is set to 120 and for flash it's set to 625 [our sourcecode] ... so where's the problem now?

One more thing: Instead of letting me do the research for these things you want - you could have done this in the meantime by yourself.
[OnePlus 3 & 3T Cross Device Development] Master_TC:
[MENTION=7030109]mcdachpappe[/MENTION]

Can i use one of your kernel on the leaked close beta pie of OP?
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
Let's read the opening post together... Oh no wait - we just need to read the 3rd sentence of the OP, yay!

And now a Question & Answer - Game:

- While having a look at point 1: Is the leaked OOS PIE ROM a custom rom? -> Answer:

NO -> so let's have a look at point 2.

- While having a look at point 2: Is the leaked OOS PIE ROM based on OREO ? -> Answer:

NO, i guess it's pie

Is this enough?
[OnePlus 3 & 3T Cross Device Development] Master_TC:
Thanks for the detailed answer. A "yes" or "no" would have been OK too.. ;)
[OnePlus 3 & 3T Cross Device Development] :
You've misapelled "Excuse me for violating xda rules by not reading the op". Please honor xda rules - you have agreed to follow them on sign up. Even though you state it's funny, it's not. :(
[OnePlus 3 & 3T Cross Device Development] cacio_confusa:
1. well not only I, but I think everyone would appreciate it. power banks etc, there are times dash charge is not available. so a big please to enable this.

2. originally sultanxda made it brighter because there was a bug in the camera Hal which has not triggered the camera flash state. But as I stated, if you use GCam with HDR+ at night, only the torch state is triggered, so 120mA. So I would simply try like 300mA and let it run for a while until it's reached the max temp to see if it's safe.

And anyway, just compare the torch brightness with any other phone of your friends. I'm sure that the 120mA on our OP3 will be the least brightest one.

And 3. You are right, I should have posted a little more details and links. Sorry and thank you
[OnePlus 3 & 3T Cross Device Development] Zielony360:
+1 for allowing to charge with current higher than 1,5 A. But the best would be to make this as an option, so the users can decide for theirselves, if they wish to take the risk.
[OnePlus 3 & 3T Cross Device Development] Tibiti:
:D

guess nothing's ever good enough for users..
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
it is an option: it's combined with "force fast charge" in the upcomming build

yes, sometimes i have exact the same feeling
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
custom-r9-f2 and oos-r24-f1

Kernel updates!

But first of all i have to announce that I've created a telegram channel [besides our existing telegram group] where new builds and other kernel related stuff will be shared.

So if you don't like groups and/or don't want to miss the latest development progress - Join:

t.me/mcdkernelchannel

1. Custom ROM Release:

I've added another type of input_boost [named: cpu_input_boost] to get advantage of it's wake_boost function. This means that when your screen is activated, all available cores will be boosted to their maximum frequency, for the amount of time you've set. In our case it's for 1000ms and it can be tuned via several kernel-manager-apps. Be adviced that if you are going to increase the boosting time [cpu_input_boost: boost duration] of this new driver you will have two input_boost drivers active at the same time! I would recommend you to stick to the default values if already set.

For the record: cpu_input_boost = 'new' added driver by kerneltoast || input_boost = 'old' driver to take advantage of dynamic_stune_boost

Changelog:

AK2: upstream [faster installation now]

introduce cpu_input_boost [by kerneltoast]

enabled wake_boost and set it to 1000ms

increase input_boost a little bit

charging: fix lockscreen message about rapidly charging

fast_charge: allow max 2500ma draw from normal charger

tri_state_key: fix on some custom roms

misc stuff

Download:

mcd-kernel-custom-r9-f2.zip

changelog-custom-r9-f2.txt​

2. OOS-Oreo Release:

Changelog:

merged stable-linux v3.18.138

merged CAF-Tag LA.UM.6.5.r1-10900-8x96

RCU sub-system upstreamed

AK2: upstream [faster installation now]

increase input_boost a little bit

fast_charge: allow max 2500ma draw from normal charger

misc stuff

Download:

mcd-kernel-oos-r24-f1.zip

changelog-oos-r24-f1.txt​

Notes:

Feedback is highly appreciated

You may delete the data of your kernel-tweak app to see/apply the new default values

Telegram-Group:

t.me/mcdkernel

Telegram-Channel:

t.me/mcdkernelchannel

Small note:

I do not like to say this, but since I spent a lot of time on this project, I would be happy if you would consider to do a little donation: paypal.me/mcdachpappe
[OnePlus 3 & 3T Cross Device Development] Sev_07:
[MENTION=7030109]mcdachpappe[/MENTION]

I Just read that in mady's thread referred to 2500ma draw.

Isn't It dangerous?
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
It's disabled by default and only active if you enable force_fast_charge - so it won't harm your device. Since kernel tweaking and changing kernel stuff is for advanced users only - and these persons should know what they are tweaking - we are safe to keep this change. Besides that i haven't heard about a device which blew up because of this, yet.
[OnePlus 3 & 3T Cross Device Development] crazymika:
I think it's okay, I've used dorimanx's kernel for a while and have no problem with any charger

it just remove some limitations and let the charger decide how much to push.

DASH charger goes much higher current than this mod.