yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] AL2000EX:
Uh oh, I have no idea how no one has noticed anything yet, but as of r13 the device doesn't seem to throttle. At all.

Nvm, the throttling is working, but it seems to be polling the pa_therm sensor, which report temperatures a lot lower than the actual CPU temperature, at least in my case, so throttling kicks in way too late.
[OnePlus 3 & 3T Cross Device Development] J's:
hi thr, anyone tried flashing this kernel with recovery "twrp-3.2.1-x_blu_spark_v8.61-op3_op3t.img"?

edit: i will just use official twrp 3.2.3-0.
[OnePlus 3 & 3T Cross Device Development] Needles_one:
I also noticed phone still getting too hot.
[OnePlus 3 & 3T Cross Device Development] J's:
R13 is One of the best kernel for gaming. Ya it does heats up quite a bit but still in the comfortable zone. Now i don't have to delete my thermal engine file and underclock my device and thus don't even need to root my phone to perform all these... Tq!
[OnePlus 3 & 3T Cross Device Development] ggkameleon:
Hi ! I'm not an expert but after many mistake on my op3 I had roll back complety stock on Oos 5.0.8 with magisk.

Before when I use this custom kernel I see on Kernel Aduitor App the 1 hearth are many time on 2150mhz.

Now on stock kernel my Op3 comes never hot when reboot it and many times all hearts are on 307mhz.(photo)

I want to test r13 for see it again.

I just do to flash it on Twrp ? But if I don't like it what can backup before for don't dirty flash the rom ? I can backup boot.img ? Or do dirty flash Oos 5.0.8.

Thanks
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
mcd-kernel-r14

update time!

Changelog:

Merge latest stable-linux v3.18.131

anykernel2: merge upstream changes

Download:

mcd-kernel-r14.zip

changelog-r14.txt​

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
[OnePlus 3 & 3T Cross Device Development] ggkameleon:
Hi ! This kernel are for the oneplus 3T ? Or can flqsh it on oneplus 3 ? Thanks
[OnePlus 3 & 3T Cross Device Development] ggkameleon:
Hi ! I don't know because nobody response me.

But I think this kernel doesn't work fine on oneplus 3 ?

See the two photos.

The first on stock oos 5.0.8 kernel all are on 307mhz

And second with r14 ? But 2 cores are on max :confused:

I do restore my nandroid ? Or I make a mistake ?

If someone can help or explain me. Thanks
[OnePlus 3 & 3T Cross Device Development] rdNNNN:
It's the way the kernel is set up regarding the task alocation among cores. You can read the latest pages, I've asked how to change the behaviour and got a nice response which is working fine for me.
[OnePlus 3 & 3T Cross Device Development] bugultra:
hey may i know how to modify the cpuset? can i just modify the value using explorer?
[OnePlus 3 & 3T Cross Device Development] Bintang Krisna:
So,whats the thermal limit for this kernel?

I see no throttling when device finishes booting,which is amazing...

Our chip is prone to being easily overheated thats why we need ro increase thermal limit

Thank you dev for bringing Render Zenith with more features
[OnePlus 3 & 3T Cross Device Development] qhsusb_bulk:
This kernel's thermal throttling is way less aggresive than OOS's original kernel's. I am very happy with it and didn't see single crash or force closing. One time dash charging wasn't working, i think it wasn't kernel related anyway. I waited few minutes and it started to charge again.

Tested with various heavy benchmark apps. Stability is top notch! No crashes. You don't need to worry about temperature.
[OnePlus 3 & 3T Cross Device Development] vinoxflame:
best kernel for playing pubg ?
[OnePlus 3 & 3T Cross Device Development] Bintang Krisna:
Just a bit info if u dont already know,Dash Charge feature will turn off by its own when devices reaches 72°C temperature.I tested it by my own using stock kernel with Thermal engine deleted.

---------- Post added at 08:18 AM ---------- Previous post was at 07:57 AM ----------

And again,anyone using Adaptive stune service?how's it?

Im aiming for Snappiness and performance,not battery life XD
[OnePlus 3 & 3T Cross Device Development] qhsusb_bulk:
I am using it as is(i didn't understand a f*ck from tunables and could't find a guide).

It reduces some UI gliches and lag(which i really care). For battery, i can't say anything. It reduces battery usage when streaming etc. but i don't see any difference in daily usage. Maybe marginally improved.
[OnePlus 3 & 3T Cross Device Development] Bintang Krisna:
Thank you,i will try that one
[OnePlus 3 & 3T Cross Device Development] AL2000EX:
Adreno Idler doesn't seem to be doing much tbh, the GPU still idles perfectly fine at 133MHz with it disabled.

I remember some versions before the idler was introduced to this kernel, it used to idle at 100MHz, same as blu spark, which must have been more efficient than what we currently have.
[OnePlus 3 & 3T Cross Device Development] karkiankit:
Best Kernel for gaming, no thermal throttling while playing PUBG while playing on ultra balanced. Thank You dev thank you very much
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
do you have any reference commit for this statement? i just had a look at engstk's sources and couldn't find anything adreno_idler related
[OnePlus 3 & 3T Cross Device Development] Bintang Krisna:
Can anyone give me an article about EAS Stune boost?if not pls guide me about it i have zero idea about the "Stune boost"
[OnePlus 3 & 3T Cross Device Development] AL2000EX:
There isn't really an article so let me explain the best I can.

By default, EAS tries to find the most efficient way to execute a task; this involves deciding on which cores the task should run on how many "ticks" are scheduled for it to execute; it also passively influences CPU frequency through schedutil. However, for interactive apps efficiency usually doesn't equal smooth performance, which is where Stune boosting comes in. It allows you to set a percentage "boost" which essentially makes the task appear bigger to EAS than it really is, biasing it towards higher performance. This doesn't just increase the CPU frequency, but makes the boosted task preempt other tasks since more ticks are allocated towards it; basically, it's a smart way of selectively boosting performance. You can also set negative values, which obviously have an opposite effect (but they still reduce "efficiency", or at least the EAS's idea of efficiency).

EAS divides tasks into cgroups: top-app, foreground, background and system-background.

Top app group holds tasks which are essential for interactive performance (for example, app's UI), so it is usually the group in need of boosting.

Foreground holds tasks which are primary but not currently on screen (think stuff like resource loading, processes that are not tied into the user interface).

Background holds background tasks of apps such as broadcast receivers.

System-background is for sensors, alarms, etc.

Tasks that aren't assigned to any group show up in the parent directory (/dev/stune).

shedtune.boost is the basic, constant Stune boost, it doesn't change once you set it. Setting it to 1 for the top-app, and 0 for everything was found to be optimal.

shedtune.shed_boost only applies during MSM Performance events, such as scrolling and app launches. It's duration is decided automatically. It only works for the top-app group, setting it elsewhere won't do anything. Increase it until scrolling is smooth enough for you.

dynamic_stune_boost will apply Stune boost on every touch or input; it has a fixed duration that's shared with Input Boost. Increase it and it's duration until animations are smooth enough for you.

Setting prefer_idle to 1 will schedule tasks on idle, or least loaded cores. It only makes sense for top-app and foreground tasks.

---------- Post added at 12:40 AM ---------- Previous post was at 12:26 AM ----------

He doesn't use adreno_idler, he modifies the driver in some way that allows it to idle at 100MHz. I couldn't find a commit that does it, but I'm sure I've seen this same behavior in this kernel in builds right before you merged the Adreno Idler.

What I was saying is, there is no point for us to use Adreno Idler, since stock driver performs virtually the same, it's just bloating the kernel. Would be cool to see eng.stk's implementation tho.
[OnePlus 3 & 3T Cross Device Development] Bintang Krisna:
[MENTION=7030109]mcdachpappe[/MENTION]

Why not put that "Stune boost explanation" in the OP?

its very useful for anyone who wants to tinker more about the tunables.

Alex did a great job at explaining this,took me only 2 times reading his explanation to understand.

Thank you again Alex for this...
[OnePlus 3 & 3T Cross Device Development] metaspook:
[MENTION=7030109]mcdachpappe[/MENTION]

Please add "USB OTG Ethernet" support.

Actually I was misunderstood before about the term of 1."WiFi Monitor Mode"

2. "Packet Injection"

3. "Soft AP Mode"

I thought a kernel developer have to add these features in kernel as adding modules/drivers, that's why I requested you somedays ago to add these features sorry for that..? .. And after several study I've learned that these 3 features (useful for "Kali NetHunter", Andrax etc pentest suit for Android) are actually need to support by the external WiFi adapter that we going to use with our device OTG attached no business with Kernel.

? So actually what we need is just support USB OTG Ethernet to use external WiFi adapter that's it...

? Here is a well documented full instructions how to enable USB OTG Ethernet support.

https://github.com/The-Cracker-Tech...ki/How-to-enable-monitor-mode-in-all-devices?
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
You will find a test-build in your inbox/pm. Test it and let me know if it works for you
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
mcd-kernel-r15

update time!

This update comes with some changes which might be useful/interesting to the kali.nethunter users among us. People who don't use any of the kali.nethunter features won't notice anything.

Special thanks to [MENTION=6029298]metaspook[/MENTION] for testing and his feedback!

Changelog:

Merge latest stable-linux v3.18.132

anykernel2: merge upstream changes

mac80211: packet injection patch [kali.nethunter]

OTG External WiFi adapter support ("monitor mode") [kali.nethunter]

Download:

mcd-kernel-r15.zip

- removed, will be reuploaded soon

mcd-kernel-r15-f.zip

- fixed !

changelog-r15.txt​

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
[OnePlus 3 & 3T Cross Device Development] rdNNNN:
hey!

Sorry to bother you with an old issue. If you want to have a look again to the thermal stuff, you can try to take some 10-20 pictures in a row using gcam. My phone shuts down doing that almost 100% of the time. It also shuts down using AIbenchmark, geekbench, aimark, and other software that stresses the cpu with heavy loads (gcam included).If anyones facing the problem, I use 1.8ghz as max on the big cores to avoid the shutdown. It would be great if you could poll other more sensitive thermal sensors to have it thorottling more agressively.

Also, from my usage, 2.3 ghz seems fine for games, since they won't max out the cpu and your thermal config will "have time" to throttle accordingly. Btw, the game perfomance using this thermal manager is much better than the stock one.

Btw, I'm sure that if you use cpu z with the thermal tab open and you will get what I'm saying.

Thanks
[OnePlus 3 & 3T Cross Device Development] TookeX:
it seems r15 break hotspot function...

I came from original rz 1.3.0 after dirty flash oos 5.0.8 with magisk for root on my OP3.

but when I tried to enable hotspot today. there is a message prompt that please insert your sim card.

hotspot can be seen my others device but no internet access there when connect to this ssid.

btw bluetooth tethering is also failure I guess due to same reason.

revert to r14 dirty flash. now hotspot are working with this version.
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
confirmed.. will have a look at it

thanks for reporting.
[OnePlus 3 & 3T Cross Device Development] Bintang Krisna:
Yeap,latest version broke "Tethering" thingy.

Just look at the positive side,you will no longer had to share your precious mobile data with your friends mu ahahahaha
[OnePlus 3 & 3T Cross Device Development] metaspook:
Be patient and give feedback to the developer...I'm also testing..
[OnePlus 3 & 3T Cross Device Development] TookeX:
Thanks for your hard work on fix and bring features to this awesome EAS kernel.

I'm stay on r14 and looking forward to next stable release :good:
[OnePlus 3 & 3T Cross Device Development] AL2000EX:
Can anyone elaborate on what pa_therm sensor is even measuring (it's the one currently being polled by the kernel btw)? It's definitely not the actual CPU temperature, and seems to be extremely unresponsive to temp spikes. Would be surprised if that's what sultan did for his kernel, I can't read sauce well tho so idk.

Edit: after some digging, the qualcomm thermal debugging guide says the PA sensor is actually the modem's thermistor. Don't think we want to throttle based on that
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
mcd-kernel-r15-f [hotfix]

Hotfix!

Sorry for the trouble with the latest r15 update. Thanks to [MENTION=4609223]TookeX[/MENTION] for reporting this tethering issue. I was able to fix this problem - so here is your fixed version :)

[MENTION=6029298]metaspook[/MENTION] it would be great if you could confirm that your external wifi cards are still functional because i can't test this by myself.

Changelog:

fixed broken wifi and bt-tethering

Download:

mcd-kernel-r15-f.zip

changelog-r15.txt​

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
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
and at [MENTION=6263955]rdNNNN[/MENTION] :

here are the commits from sultan regarding this thermal solution and it's thermal-sensor:

msm: thermal: simple: Use VADC device for temperature polling

msm: thermal: simple: Remove TSENS dependency

I think he has exchanged the sensors with intention - see the notes in his commits. I don't know what i can do about your heating problems. I don't even know which sensor i should pick so i leave it as it is right now.
[OnePlus 3 & 3T Cross Device Development] TookeX:
Thank you for your effort.

how a quick response and appreciate it.

dirty flash r15f over previous r14.

confirmed wifi and bt tethering are both functional now. :good: :good:
[OnePlus 3 & 3T Cross Device Development] metaspook:
Wow! You already fixed the issue.. thanks :svetius:

In the meantime I was about to let you know that from your 3 builds u gave me to test "mcd-kernel-15-wifi" had no broken wifi and bt-tethering issue but other 2 had. But u already fixed great.

My OTG cable is broken :( tomorrow I'll buy a new one and test and give u feedback. ;)
[OnePlus 3 & 3T Cross Device Development] metaspook:
Guys .. in the meantime I could test, if you guys have ?OTG cable and a USB wifi dongle plug n test if it working or not ... Give feedback here.
[OnePlus 3 & 3T Cross Device Development] metaspook:
? How to Dirty and Clean flash a Kernel --

I saw many of you have misconception on dirty/clean flashing a kernel.. Read the instructions below..⤵️

** Pre-Task (One time)

| 1. Go to TWRP

| 2. Keep a backup of fresh unmodified (NO custom kernel, NO magisk installed) stock boot img/partition. If already modified than flash the stock rom/ota zip than keep backup, here you can keep whole stock rom boot, system etc. for future use. But we just need the boot img/partition in this case.

** Task (Clean Flash) | Useful in flashing hotfix version of same Kernel and if any issue occurs.

| 1. Go to TWRP

| 2. Restore backup of boot img/partition.

| 3. Flash the Kernel zip.

| 4. [Recommend to keep root] Now flash the root handler zip like Magisk.

| 5. [Optional] Wipe Cache/Dalvik.

** Task (Dirty Flash) | Useful in flashing update version of same Kernel.

| 1. Go to TWRP

| 2. Flash the Kernel zip.

| 3. [Optional] Wipe Cache/Dalvik.
[OnePlus 3 & 3T Cross Device Development] AL2000EX:
Ok, so how is increasing Adreno Idler's ramp down speed going to do anything if we're already using the lowest frequency at all times?

Talking about this commit in particular

https://github.com/mcdachpappe/andr...mmit/57716a3b007bc9df749c37dda4f79243996ead3b

I've tested GPU frequencies with Idler enabled and disabled and there isn't any difference whatsorever. I've tried finding scenarios where it was most likely to have any effect, positive or negative, and it just doesn't.

Arter97 himself didn't use it in his 3T kernel, because it does nothing. It's a waste of your time [MENTION=7030109]mcdachpappe[/MENTION]
[OnePlus 3 & 3T Cross Device Development] AL2000EX:
oh btw, disabling iostats in init after boot might give us some more i/o throughput. Pixels have it off by default.
[OnePlus 3 & 3T Cross Device Development] mady51:
Adreno idler is useful along with adrenoboost. Gpu will be boosted to a bit higher when required with adrenoboost. So, to make less use of this during idle times idler will be used. Atleast this is what that implementation means, as i cant say it 100% but even with default adreno u wont see any much diff with idler or booster.

---------- Post added at 03:22 AM ---------- Previous post was at 03:20 AM ----------

Technically yes. But ideally from user perspective u dont see any difference in ur usage
[OnePlus 3 & 3T Cross Device Development] AL2000EX:
Adrenoboost was removed some versions back. This all gives me flashbacks to 2013 when the Adreno driver was a broken piece of crap on most devices and we needed mods to fix it. Not the case now.
[OnePlus 3 & 3T Cross Device Development] metaspook:
[MENTION=7030109]mcdachpappe[/MENTION]

WiFi Monitor mode isn't working.. :(

Checking:

I connected my WiFi dongle through OTG cable and check in OTG checker app it shows a device is attached.

But in Terminal emulator using "ifconfig" command it found no wifi device and specially in Kali Nethunter and ANDRAX using "airmon-ng" command which is 'Monitor mode' checking and launching tool it shows only internal wifi device, not OTG attached wifi dongle. It means there is a problem with supporting External WiFi adapter or driver/firmware of the kernel.

My Device: TP-Link TL WN727N Chipset (Ralink RT2870 / RT3070)

This device supported for monitor mode https://www.wifi-antennas.com/topic/43-list-of-usb-wireless-adapters-monitor-mode/
[OnePlus 3 & 3T Cross Device Development] Hayatzada:
please add support for Pie Custom Roms
[OnePlus 3 & 3T Cross Device Development] metaspook:
Did you test this Kernel ? And if you using kali nethunter plz give feedback if it's works..
[OnePlus 3 & 3T Cross Device Development] AL2000EX:
That's not as easy as it may sound mate, EAS was brought up by different devs specifically for OOS Oreo and I doubt they plan on returning to this device.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
Hello! I am a new user of this kernel and has flashed it finally after playing around with all other OOS supporting non-EAS kernels. But Stock performed the best for me so far.

I have flashed this EAS based kernel today and would like to ask the regular users if there is any setting I shall play around to achieve a bit more balanced behaviour? My common usage is pretty basic - Watching Netflix for 2-3 hours max, play PubG for maybe 20-30 minutes, YT for 30-45 minutes, and then most of the time ideal with 4G ON always (no wifi). Then i usually unlock every 15-20 mins to check notifications and emails. Sync is off.
[OnePlus 3 & 3T Cross Device Development] theduke7:
Install any kernel manager and from the 2nd post install the Adaptive Stune App it'll automatically adjust some settings according to your usage.

Other than that I personally after some testing prefer to change the I/o sched to cfq , I tried Maple and zen , I prefer cfq balance ...that said the default Maple is great too for battery ., The difference is small to mention for most people (for me cfq preform better with pubg) ...you can test for yourself with this , try the default , of it's ok don't change it, or change to one of the other ones included ( fiops I found a little unstable) but you can test any of them...some like deadline will increase performance but decrease battery life.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
I'll try adaptive stune app
[OnePlus 3 & 3T Cross Device Development] Hayatzada:
i know it isn't but may someone listen for it, i requested in several threads long ago

---------- Post added at 11:45 AM ---------- Previous post was at 11:38 AM ----------

i used kali nethunter for wifi cracking and successfully cracked several password just for fun, but that was on NEXUS 5 and Samsung S5 G900t, can't use it on OP3T due to non-custom Rom support and also previous Android versions, there is no kernel or work after nougat.
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
Announcement

Sadly I was not able to implement kali.nethunter features for now. Monitoring-mode is still not working and that's the reason why i will revert the latest changes regarding nethunter. Let's have a look at mady's extended reborn8 kernel for now - he's trying the same and he's a way better developer than me.

I saw some developers raising config_hz to 1000 [current: 300]. This should lead into much smoother ux like they say.. Is anyone interested in testing such a build? I'm thinking of disabling touch-boost [input_boost] if this change receives some positive feedback.

Feel free to join our fresh mcd-kernel telegram group.

In this way i can share test-builds, receive much faster feedback and your feature-requests.

Link:

t.me/mcdkernel

​
[OnePlus 3 & 3T Cross Device Development] Bintang Krisna:
yes sir,i want to test
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
mcd-kernel-r16

update time!

We are disabling msm-touchboost and input_boost with this release because the new config_hz value seems to do a good job regarding a fluid user experience. Feel free to enable them again if you don't like the new default settings.

Thanks to you guys in our telegram-group for testing and your feedback!

Changelog:

Merge latest stable-linux v3.18.133

init: disable input_boost and msm-touchboost

increase config_hz from 300 to 1000 [further information: https://source.android.com/devices/tech/debug/jank_jitter]

misc: little changes to save some battery [codec, gpu]

revert: mac80211: packet injection patch [kali.nethunter]

revert: OTG External WiFi adapter support ("monitor mode") [kali.nethunter]

Download:

mcd-kernel-r16.zip

changelog-r16.txt​

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
[OnePlus 3 & 3T Cross Device Development] abhibnl:
[MENTION=7030109]mcdachpappe[/MENTION]

Any reason zram is disabled in your kernel? I hope I'm understanding it correctly from these values in kernel auditor.
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
because we don't need zram on our device - it has enough ram.
[OnePlus 3 & 3T Cross Device Development] abhibnl:
It's actually a misconception. A really respected and veteran developer did provide explanation on why zram is actually good and has nothing to do with physical ram. I'll try to find that write just for knowledge sake

Here's the write up:

https://xdaforums.com/oneplus-3/one...1-20180223-t3754855/post78334059#post78334059
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
you have convinced me.. will have a look at it for the next build. thanks for this
[OnePlus 3 & 3T Cross Device Development] uzumakivishal96:
What is the screen on time for this kernel. The best screen on time I have got is around 5hrs on version 4 of this kernel.
[OnePlus 3 & 3T Cross Device Development] spione2013:
Hello, I've used this kernel when it was on r4 version

Now I seen that there are wakelocks, that is very goooood, and many other fantastic features.

How's stable is now? Is a daily drive kernel?