yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] phil_greg2001:
Hi all,

I have a wifi issue with OOS 5. 0.7

I'm the only one :confused:
[OnePlus 3 & 3T Cross Device Development] theduke7:
I have no issues here
[OnePlus 3 & 3T Cross Device Development] phil_greg2001:
OK, many thanks :cool:
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
mcd-kernel-r11

update time!

Nothing special again - see changelog..

Changelog:

Merge latest stable-linux v3.18.128

Download:

mcd-kernel-r11.zip

changelog-r11.txt​

mcd-kernel-r11b.zip

changelog-r11b.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] qhsusb_bulk:
Thanks for continuing support and pushing new updates [MENTION=7030109]mcdachpappe[/MENTION] . After death of Derp kernel i am trying to find an upstreamed and stable custom kernel for OOS(for now OOS has no alternatives from my point of view in terms of functionality and stability. I can't leave it).

Thanks to lovely work from [MENTION=5438598]RenderBroken[/MENTION] and [MENTION=6745491]joshuous[/MENTION], we have very nice EAS kernel for OOS but their primary focus is OP6 series, so they can't push updates regularly to OP3. In that point you saved us. Appreciated...
[OnePlus 3 & 3T Cross Device Development] ggkameleon:
Hi ! Thank you for your work :)

I use the custom based on oos TheOne3os and ÉlémentalX but not update.

I had dirty flash my Rom and flash your Kernel great no mistake. But which kernel manager App can use ? ÉlémentalX manager or Kernel Audiutor ?

I have install stune but don't understand it.

Thanks.
[OnePlus 3 & 3T Cross Device Development] Needles_one:
R11 breaks Bluetooth.
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
mcd-kernel-r11b

[MENTION=6622659]ggkameleon[/MENTION] i'm using ex kernel manager but kernel audiutor should work as well.

thanks for reporting.

build r11 has been fixed and the download link was updated. the latest [fixed] version is now r11

b

!
[OnePlus 3 & 3T Cross Device Development] ggkameleon:
Yes ! I do to remove it. Break Bluetooth too.

I have roll back to oos 5.0.7 root magisk.

This kernel work great ? I'm encrypted no mistake ? And use kernel auduitor.

Thanks
[OnePlus 3 & 3T Cross Device Development] pedrovb25:
This kernel works very very well. It doesn't have any bug. R11b is perfect :D
[OnePlus 3 & 3T Cross Device Development] theo.j22:
Was on OOS for a day, tried the kernel, loved it, smoothness was on point.
[OnePlus 3 & 3T Cross Device Development] ggkameleon:
Ok thank you. I had test the 11b work well.

But I have always the same mistake with my dialer.

After unbrick my op3 and apply root ! I don't understand why I boot on Twrp and flash Oos full firmware 5.0.7 and flash magisk 17.1 my op3 crash with white led. Or I do to restore my nandroid or force boot to recovery and flash again magisk 17.1 ?

I don't know if is encryption but :(
[OnePlus 3 & 3T Cross Device Development] theduke7:
It's normal... There's a bug whether on twep or something with the way boot image is on oos,

Of you flash oos full zip when you reboot itll freeze with white led or black screen with constant vibrate , you'll have to force shutdown the device and boot again

Also flashing recovery after full oos will not stick you'll have to flash with fastboot after 1st boot

A lot of devs looked into it, and so far no fix... There was one version of OOS that was.released but OnePlus retracted it just a day after , that release didn't cause the twrp issue...

That's why it thought that it might be something with the boot or boot sector.

What you need to do after any oos update (Even dirty flash) ،

Flash room, they manually force shut down

Start the phone to bootloader (fastboot) and fastboot twrp again

Reboot to twrp and do the rest of the stuff you need to do .
[OnePlus 3 & 3T Cross Device Development] ggkameleon:
Hi ! Thank you is not a manip mistake it's normal good.

Thanks for support :)

And you know why I have always the mistake of dialer ? Or the mic doesn't work or crash system and boot loop ???

I have unbrick my op3 two times but after some days use the mistake comes again. I don't understand why ???

Thank you.
[OnePlus 3 & 3T Cross Device Development] theduke7:
i don't really understand the dialer issue, can you elaborate what exactly happens!
[OnePlus 3 & 3T Cross Device Development] ggkameleon:
The issues stated 3 months ago in August after change Custom Rom base on Oos "ExperienceOS" to "TheOne3OS" an audio issue - I couldn't make or receive a call without the phone going to a boot loop. Then this stopped, I can now make calls The phone randomly stops or freezes system. I have unbrick it and comes to Oos 3.2.1 and update it to Oos 4 and 5.0.6 and 5.0.7 on stock recovery no root. After on fastboot flash TWRP 3.2.3-1 and flash Magisk. I use it no mistake. After with Titanium restore my App's and no mistake too. But after 3 days the dialer crash again ???

I don't know :confused::(:(
[OnePlus 3 & 3T Cross Device Development] theduke7:
that seems strange...

the one thing i can recommend is try to clean flash then don't restore any data with Titanium... i personally don't use it, but i read in several threads devs recommending against it

maybe just manually backup your data, and let the apps download again... setup the device as new... the problem might be caused by corrupted data restored by the Application.

best of luck , that's a really annoying issue.
[OnePlus 3 & 3T Cross Device Development] ggkameleon:
Hi ! Thank you.. yes perhaps the restore with titanium backup make mistake..

I never had this mistake but appaers after change my data partition to encrypted.

I have a backup make after unbrick it and just update to oos 5.0.7 without root. If I reboot to system with this backup I loose Twrp. I think make a clean install but decrypted with the method remove encryption dm-verity.

I can use oos with decrypted data ?

If I restore my backup reboot to fastboot and format my user data and reboot to twrp flash oos the boot modified reboot to recovery remove encryption and root magisk and reboot to system. And them configure it as a new phone.

After install all my App manually. I can't use titanium for install it manually with no data one per one not make a restore ? Because only adsl is so long... Or google restore is not good to or OnePlus backup too.

Thank you have a good day..
[OnePlus 3 & 3T Cross Device Development] theduke7:
what i mean is don't use titanium at all for now ( at least for few weeks and see if the problem is gone)...

i don't think encryption is the problem (i don't see the reason why it should)

finally don't mae it hard on yourself... just follow the steps

1- backup physical data (images and media...etc) to the sdcard then to the computer.

2- reboot to twrp flash the OnePlus Original recovery (found in their site) and then reboot to Original recovery

3- in Original recovery wipe everything (it wont wipe system but it will wipe data and internal storage)

4- in original recovery select install from adb

5- from your computer sideload the full zip using the following command

adb sideload full_zip_name.zip

the reason for this is when you want to get your device to perfect condition it's better to do it official (twrp and any probable issue eliminated) , make sure you have the correct drivers installed ( also the drivers in the cd drive that appears when you connect your phone to a PC) and use original cable

6- sideload takes more time than flashing with twrp and that's for good reason...

7- after sideload is done , reboot fully to OS and from OS do a factory reset with full wipe (yes again) to make sure any traces of error or corruption is gone

8- after the factory reset is done and you'r back to OOS , you can reboot to fast boot and fastboot twrp and immediately boot to it

i recommend this TWRP version

https://www.androidfilehost.com/?fid=3700668719832239620

it's a modified version by HolyDragon

9- in TWRP flash magisk then this kernel (or any kernel) , you don't need modified boot or dm-verity...etc, Magisk 17.1 will do that anyway.

10- reboot ...and that's it, if you want to flash anything else , just do that and always keep a Nandroid ( full backup from TWRP) , such back up can revert you back to a clean system with no issues in no time, you can make this back up after you install all your apps.

now you should have a clean fully functioning OOS .

best of luck m8, and if you need more help please PM me so we don't clutter this thread with unrelated stuff.
[OnePlus 3 & 3T Cross Device Development] ggkameleon:
Thanks a lot for your support :)

I never make this method. I make it.

Ps : I have make a support too with OnePlus and send log.

I hope that your solution will work while waiting for the return of the OnePlus support but to dissect the logs will be long. tomorrow afternoon I do it all thanks again.
[OnePlus 3 & 3T Cross Device Development] ggkameleon:
Great :):good: you save me that work fine !!! I can make call. 3 month doesn't work.

I stay with no root somes days and after test the kernel :mad:
[OnePlus 3 & 3T Cross Device Development] ggkameleon:
Hi ! I have a question is it possible to use grenify with this kernel ? and the mod magisk universal gms doze ? thank you
[OnePlus 3 & 3T Cross Device Development] theduke7:
You can use any app or magisk mod, it's totally unrelated to the kernel.

I personally don't recommend greenify, I used to use it, but it's not at least on our device has much benefit, actually some times it causes more drain

Use app ops instead, it requires more setting up, but it's much better .

GM's doze is fine, I'm using it myself.
[OnePlus 3 & 3T Cross Device Development] ggkameleon:
Hi ! Ok thank you ! The first day completely stock the phone comes never hot and good good battery drain :) I think Oneplus make good work on Oos 5.0.7.

But I can't stay stock many Times and I have flash the HD recovery is good and magisk. (I have make a nandroid)

This kernel are very good too :svetius:

I uninstall Greenify it's not important for me. But I don't understand use app ops instead ? No synchro if possible and no push notification it's right ?

I have a last question :confused: completely stock no mistake with my dialer and make a nandroid. But I have root it and install some mods & roots App : YouTube vanced emojione gms doze & sd maid kernel aduitor terminal adaway. But my dialer crash again I think comes with adaway ! I remove it ! Actually no crash but how many times.

If I want restore my nandroid and have again corrupt files. The nandroid restore don't factory reset the phone ?

If I have mistake again this time make your method again and stay with no root nothing I am tired.

Thanks for all. Have a good day.
[OnePlus 3 & 3T Cross Device Development] pedrovb25:
I have a question for people who use adaptive stune app... The app stops the background process (randomly) and stopping working (without adapt the stune to the activity). Is needed to disable and enable from accesibility settings for app continue working. Anyone experiences this? I disabled the app on doze but doesn't work.
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
mcd-kernel-r12

update time!

this time we've got something 'new' :)

This kernel has now sultanxda's thermal-solution [msm-thermal-simple] implemented which was introduced a while ago. We (speaking about [MENTION=3927764]theduke7[/MENTION] and me) were testing some custom values and have monitored really good results in idle state and while gaming. The downsize of this thermal-solution is that the user can't control it via sysfs via any kernelmanager app's. So you have to use the values as they are. You are still able to set your custom values but this has to be done on every reboot again e.g. with a script or something similar. You'll find these parameters at /sys/kernel/msm_thermal/... Please have a look at my repo for further explanation...

Any feedback or ideas for better thermal-values are highly appreciated.

..Tested on OxygenOS 5.0.8 [OP3T]

Changelog:

Merge latest stable-linux v3.18.129

AnyKernel2: adress more selinux denials

AnyKernel2: enable 2.4ghz wifi channel-bonding

init: use our custom thermal-values

thermal: introduce msm thermal-simple by sultanxda / kerneltoast

Download:

mcd-kernel-r12.zip

changelog-r12.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] qhsusb_bulk:
Thanks for update!

I want to ask you something [MENTION=7030109]mcdachpappe[/MENTION]. As you know, OnePlus hasn't updated kernel source for months and many OS updates. Is that will cause any problem when using it with new OS version?
[OnePlus 3 & 3T Cross Device Development] Abhishek_DK:
[MENTION=7030109]mcdachpappe[/MENTION] for some reason I get an Error after I flash Ramdisk Failed error ?
[OnePlus 3 & 3T Cross Device Development] theduke7:
because the OS is essentially the same they didn't change anything in it that requires them to change the kernel (it would be great if they did(, but that said, this is a EAS kernel and although OOS sources are important but as long as they're Oreo it doesn't amtter as long as this kernel is flashed on OOS Oreo Rom... obviously when (and if) they release Pie OOS , this EAS kernel will need a huge update from the source (not just OnePlus OOS sources) but from those who ported it, (RenderZenith KErnel)

what TWRP are you using? Official?
[OnePlus 3 & 3T Cross Device Development] metaspook:
[MENTION=7030109]mcdachpappe[/MENTION] If possible, please add "WiFi Monitor Mode" kernel feature in next release.
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
That's usually an issue caused by a specific twrp (or any other custom recovery) version. Try to use Official TWRP v3.2.3-0 (link in my signature) if not already.

Do you have any reference commit or know a kernel which has this feature included? Never heard something about it.
[OnePlus 3 & 3T Cross Device Development] metaspook:
WiFi Monitor mode and Packet Injection (Kernel Features of Kali Nethunter)

https://xdaforums.com/oneplus-3t/development/kernel-kali-nethunter-oneplus-3t-t3507816

https://github.com/offensive-security/kali-nethunter/wiki/Modifying-the-Kernel

[MENTION=7030109]mcdachpappe[/MENTION] If possible, please add these in next release.
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
sorry, i already stated that I'm not going to add those features because they require a selinux permissive state
[OnePlus 3 & 3T Cross Device Development] Abhishek_DK:
I'm on official TWRP I will try flashing the TWRP again and lets see how it goes.
[OnePlus 3 & 3T Cross Device Development] metaspook:
Oh.. it that case than ok.. thanks for reply :good:

keep developing/updating this kernel really appreciate with your afford..:good::good:
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
it depends on the version which you are using. the latest one is not always the best idea. twrp 3.2.3-0 works for me..

thank you for your kind words :)
[OnePlus 3 & 3T Cross Device Development] vinoxflame:
this is a very good update ?
[OnePlus 3 & 3T Cross Device Development] tofuboi01:
I'm on op3 but when flashing kernel it sees it as op3t.

Many thanks for this kernel and keep up the good work!
[OnePlus 3 & 3T Cross Device Development] rdNNNN:
Hey!

Just reporting my usage. The new thermal engine is not 100% stable, at least on my OP3T. I'm facing some forced shutdowns. Happenes in geekbench 4, gcam and on "CPU throttling test" from playstore. Afaik the problem is the same as reported a year (or more) by sultandxda

https://www.google.com/amp/s/amp.re...ultanxda_found_that_if_the_oneplus_3t_sd_821/

If I was to guess, I would say that there's at least one thermal sensor that might be getting very hot in comparison to the rest, so the SoC will shutdown. Perhaps there's a way to read the temp from "this" sensor and work the thermal engine arround that. You can also tune it more conservative. Also, be careful, since you use dynamic fsync there can be some data corruption if the phone shutdowns itself (as happening on my op3t right now)

Thanks for your work nevertheless
[OnePlus 3 & 3T Cross Device Development] Jadelor:
Can you disable dynamic fsync, set the big core maximum frequency to something lower like 1.8GHz and see if it persists?
[OnePlus 3 & 3T Cross Device Development] rdNNNN:
I will test it later, since im running low battery atm.

Meanwhile, take a look at this screenshot. See how some temps get incredible high just some secs after i've started that load. Sd820 is either a semi flawed chip or those sens have some kind of offset

https://m.imgur.com/a/XiomNPg
[OnePlus 3 & 3T Cross Device Development] Jadelor:
Over 100°C? Whoah.
[OnePlus 3 & 3T Cross Device Development] skymera:
Flashing now on 5.0.8

Thanks!
[OnePlus 3 & 3T Cross Device Development] 『Healer』:
H2os

WiFi cannot be used？？？
[OnePlus 3 & 3T Cross Device Development] vinoxflame:
Works fine
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
Now that's not quite true. I think you are mixing-up something.

First:

(unstable frequencies)

The problem you cited is something different. Sultanxda deactivated the thermal driver on his device (to make sure its power clusters never throttle and run at maximum speed) and found that the kernel crashes when both clusters reach their maximum frequencies - even at 40 ° C . High frequencies seem to be unstable on certain op3/t devices. That's why he added this commit to make sure his kernel was not using those unstable frequencies any more. Also known as [underclock].

Gcam mod works for me (nightsight / hdr) which should also cost more power (ie. use high frequencies) and I had no crash so far. Could you post a log after gcam crashes?

Second:

(thermal-driver)

This thermal solution should lower your frequencies at a certain temperature. I do not know how you can reach 100 ° C because at 70 ° C your phone should be less than half the power. Have a look at our thermal settings.

I'm not really a fan of these synthetic benchmarks. They don't represent my daily use or any app which i'm using. My phone works pretty well even while playing the worst game (pubg) which is available for our device right now. And the best thing: I can still hold my phone in my hand without burning me.

What should we do now?

Should we limit our performance because some benchmarks can crash your kernel? Underclocking our frequencies for these benchmarks?

My opinion:

I think I bought the op3t because of its higher frequencies instead of the op3 - otherwise the op3 would be enough. If these crashes do not occur during daily use, we probably do not need to underclock our device..
[OnePlus 3 & 3T Cross Device Development] skymera:
OP3 owner since mid 2016. I've never had my OP3 crash from using highest stock frequencies.

Idle drain on this kernel is pretty good so far. Phone did seem quite hot after 45mins of Waze navigation today.
[OnePlus 3 & 3T Cross Device Development] shivamgosain89:
Can you add more frequency options for little cores between 1.5 and 2.1 ghz ?
[OnePlus 3 & 3T Cross Device Development] rdNNNN:
First of all. Thanks for the insight

Regarding the unstable freqs, i've just theorized that these two things might be somewhat related. There are thermal sensors who read much more high temps than the one that is normally reported by software, like kernel adiutor. Using stock kernel i've seen some of these sensors spike over 90 degress celsius, just before beeing throttled by the stock thermal driver.

What i think is that these top frequencies are there just for very short (duration) loads, and i've nothing against it. It's somewhat expectable. About sultanxda stuff, since he disabled the thermal control, the problems he faced could also be related to these hot spots on the soc. Again, With stock stuff, i've seen those spots hit over 90 in short loads, when the kernel adiutor reported soc as 50 something.

I would advise you to log those temperatures in your phone. Simple system monitor allows this afaik. if you allow my opinion, the thermal driver should be more agressive on the high freqs to make this kernel fully stable. I found 1.5 ghz on little and 1.8 on big to be thermal stable on sustained loads, so it would't be a big difference. Don't know if it's possible, but a nice way make this better would be to poll some of those sensors and make the thermal driver adjust based on the highest value read at a given time to try to keep the temps of these hot spots under something 85/90/95°

Also, I also know that the software i used to test the stability is a worse case scenario and puts more strain on soc than 99% of the workloads.

Bonus question, can you explain me how to get background tasks assigned to core 0 and 1 (instead of only core0). With my usage, i often see the Core0 with 100% usage while others idle. I would prefer to get those tasks split over those two little cores.

Thanks for the support
[OnePlus 3 & 3T Cross Device Development] AL2000EX:
In your mcd.init modify

write /dev/cpuset/background/cpus 0

to

write /dev/cpuset/background/cpus 0-1

You will still see higher core 0 usage because EAS will still prefer to pack background tasks rather than spread them. Also, usage is calculated using the current freq, not the highest available freq (afaik, don't quote me on this) so you may still see 100% use when the core is at 300mhz.

There is a reason why bg tasks are forced to core0 even on 8 core devices, allowing them to spread can slow down foreground tasks and cause higher idle drain as I've found through my testing.

Here's what I personally use. It leaves a bit more space for the top-app (smoothness over throughput) and may save some battery

# update cpusets now that boot is complete and we want better load balancing
write /dev/cpuset/top-app/cpus 0-3
write /dev/cpuset/foreground/boost/cpus 0-3
write /dev/cpuset/foreground/cpus 0-2
write /dev/cpuset/background/cpus 0
write /dev/cpuset/system-background/cpus 0-1
write /dev/cpuset/audio-app/cpus 0-1

---------- Post added at 05:41 PM ---------- Previous post was at 05:20 PM ----------

Btw, [MENTION=7030109]mcdachpappe[/MENTION], some things in your init do nothing at best, like recreating the already existing camera cpuset and enabling LPMs that are already enabled by default. Also, the boot up I/O tweak is intended for a/b devices so I doubt it helps us at all.

And please, for the sake of other users' data, don't enable dynamic fsync by default, it's snake oil especially when combined with f2fs. Even Boeffla tweeted against it. Recovering from a broken f2fs partition is not fun, been there done that
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
mcd-kernel-r13

update time!

merged latest stable-linux and did some minor changes to our ramdisk.

Changelog:

Merge latest stable-linux v3.18.130

init: update cpu-sets

init: clean-up some useless code; don't enable dynamic-fsync by default [as suggested by [MENTION=5397938]AL2000EX[/MENTION]]

misc: clean-up the kernel-tree

Download:

mcd-kernel-r13.zip

changelog-r13.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] AL2000EX:
Woah, that was quick, cheerios for the update

So for whatever reason special powers don't seem to work for me. Those processes still run at whatever cores they feel like. Do I need root / magic for it to work?

OnePlus3T:/ $ CORENUM=3
d,psr,cpu,cmd | grep -E "^[[:space:]][[:digit:]]+[[:space:]]+${CORENUM}" <
1065 3 3 MHI_XPRT22:23
1258 3 3 ipawq50
2606 3 3 file-storage
2771 3 3 kdmflush
2867 3 3 f2fs_flush-254:
2878 3 3 time_daemon
2879 3 3 thermal-engine
2885 3 3 cameraserver
2887 3 3 Binder:2887_2
2890 3 3 mediaextractor
3086 3 3 adbd
3117 3 3 imsdatadaemon
3136 3 3 rild
3141 3 3 qti
3145 3 3 netmgrd