yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] The.Scram:
Just went from 134 which was runing fine to 139 and now two cores are stuck at 1516MHz.

What can i do to find out whats wrong?

Already tried to toggle Touchboost, fastlane with no success so far.

FREEDOM OS on OP3t
[OnePlus 3 & 3T Cross Device Development] laupuy:
Hi,

Thanks to the dev [MENTION=3873953]eng.stk[/MENTION]

As usual it's rock solid on

Open Beta 17

Both twrp and kernel of course!

:svetius:
[OnePlus 3 & 3T Cross Device Development] anttaz:
Thanks for updating both recovery and kernel.

Device flying thanks
[OnePlus 3 & 3T Cross Device Development] immi803:
Nothing wrong found here, it's perfectly fine with the cores, indeed more snappier, both clusters absolutely fine :D
[OnePlus 3 & 3T Cross Device Development] B3501:
It's an OOS/firmware bug that's been talked about 10000000x on here. Clear the cache or reboot or reflash.
[OnePlus 3 & 3T Cross Device Development] The.Scram:
Probably posted a bit too early :eek:

It needed some more time to settle down. Everthing is cool again. Great stuff :cool:

I cleared cache as always
[OnePlus 3 & 3T Cross Device Development] Kiranb212:
it happens with me as well.. since many builds (I mean no complaints.. I just appreciate tye work from Dev).. the only fix that works for me to set Selinux permissive and back to enforce.. this trick works very well.. along with Experience OS.. [MENTION=3873953]eng.stk[/MENTION] new build is amazing.. thank you much :highfive:
[OnePlus 3 & 3T Cross Device Development] eng.stk:
You cleaned caches, you will have cache rebuild and it will use cpu until done.

Kernel is fine. Case closed.

Using stuff that have issues with selinux contexts has nothing to do with kernel.

Many builds or no builds make no difference. Not kernel related.
[OnePlus 3 & 3T Cross Device Development] crissbm:
Works fine for me also.. Apply on boot is working now . Didn't work on older versions .
[OnePlus 3 & 3T Cross Device Development] cultofluna:
Twrp & kernel installed..

Thanks for keeping us updated....

Works like a charm....
[OnePlus 3 & 3T Cross Device Development] Sefyron:
Guys, i just wanna know if this is a kernel related problem or not, voices calls draaains my battery really bad. Can someone help me i'm on stock OOS 4.1.3
[OnePlus 3 & 3T Cross Device Development] cultofluna:
It's a known issue on OOS 4.1.X...

It's​ fixed on latest OB 8....

Not kernel related..
[OnePlus 3 & 3T Cross Device Development] Sefyron:
Does this kernel work good on OB cuz i really like it
[OnePlus 3 & 3T Cross Device Development] The_Fry_Guy:
Yes. Works great on anything it's compatible with.
[OnePlus 3 & 3T Cross Device Development] tinuz97:
No idea if it is placebo, but looks more snappy vs r134. I also updated twrp. Realy smooth with FreedomOs 2.10ce, no problems with cores hanging or something like that. Thank you :highfive:
[OnePlus 3 & 3T Cross Device Development] pompe90:
Woops.. Wrong thread. Delete.
[OnePlus 3 & 3T Cross Device Development] Gauravlonkar:
Paranoid Android 7.1.2 support ?
[OnePlus 3 & 3T Cross Device Development] eroigaps:
Short answer: no
[OnePlus 3 & 3T Cross Device Development] antoniobarros:
Cache

the cache is better to clean it before or after a kernel update?
[OnePlus 3 & 3T Cross Device Development] Explorer23:
No need to touch it at all when you're just updating.
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
Haha I bet [MENTION=3873953]eng.stk[/MENTION] reads posts like this and is just like: "damn I'm so good".

No seriously best kernel I've used so far and I've tried plenty.
[OnePlus 3 & 3T Cross Device Development] lpsld:
Oneplus 3 is starting to vibrate more than 1 time on startup with latest Oxygen Open Beta, using the oos version of r139 & v35 Recovery

When my device started, its just a blackscreen and still vibrates every 1 or 2 sec

I know there is no support for OB builds but probably someone can help me
[OnePlus 3 & 3T Cross Device Development] Ramabi77:
Sorry for replying to this oot,

If you are using substratum, try to flash substratum rescue_legacy from twrp, definitely not kernel related, i have this issue a few days ago, and realize some substratum's theme is causing blackscreen on my op3t
[OnePlus 3 & 3T Cross Device Development] Chaplan:
A little search would be wise, but here you go.

https://xdaforums.com/oneplus-3/oneplus-3--3t-cross-device-development/kernel-t3404970/post72012239
[OnePlus 3 & 3T Cross Device Development] Stephen:
Moderator Information,

Thread has been cleaned, flaming other users in any form is not acceptable on XDA. If you have an issue with a user, best to simply ignore and move on. If they are breaking forum rules, report and we can look into it.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
No and probably won't, unless custom ROMs become more similar with PA or vice versa, in the future.

Some stuff PA is using just makes other stuff incompatible/work poorly and I'm not doing just a build for that ROM.
[OnePlus 3 & 3T Cross Device Development] Dieppy:
Don't know if I'm wrong but I feel the phone a little bit hotter using a lower fastlane threshold on big cluster than on little. So now I'm trying to use 40 on little and 60 on big. Anyone else noticed this thing?
[OnePlus 3 & 3T Cross Device Development] NickosD:
Lower the threshold, the more aggressive fast lane will be.
[OnePlus 3 & 3T Cross Device Development] B3501:
No.
[OnePlus 3 & 3T Cross Device Development] Dieppy:
Better this way
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Nope. Fastlane never made my phone go HOT.

That must be the environment you are @, or maybe an app or services making their usual mess.

You can take my word on this.

Fastlaning even without threshold on the Nexus 5 days never had any impact on temps.
[OnePlus 3 & 3T Cross Device Development] harryfornasier:
Can someone here explain fastlane to me or send to a thread that could?
[OnePlus 3 & 3T Cross Device Development] B3501:
It makes frequency switching more aggressive and dynamic. An alternative CPU scaling method if you will. Better performance whilst saving battery.
[OnePlus 3 & 3T Cross Device Development] harryfornasier:
Sorry to ask more noob questions, I've just come from a nexus 5x and it's all a bit different. But should I us EK kernel manager or kernel auditor? And also how do I enable it
[OnePlus 3 & 3T Cross Device Development] Nevermindthelabel:
Kernel Adiutor is recommended, but I use EXKM and it works great. Search for exact details for turning it on but it's in cpu>governor options or something like that. And set to 1 for on
[OnePlus 3 & 3T Cross Device Development] sakumaxp:
Kernel adiutor> cpu > tunable > set fast lane to "1" > set both thresholds to "35" > enjoy
[OnePlus 3 & 3T Cross Device Development] storytellerz:
Currently I have my both cluster fastlane enable with 35 threshold. If I want to update my blu_spark kernel to latest, I have to revert all the setting back to stock, uninstall the kernel adiutor then flash the new kernel? Is my understanding correct?
[OnePlus 3 & 3T Cross Device Development] B3501:
No, just flash the new version.
[OnePlus 3 & 3T Cross Device Development] storytellerz:
So I can just left my fastlane enable and flash a newer version on top of my current version?
[OnePlus 3 & 3T Cross Device Development] harryfornasier:
Is the lower the threshold for performance or battery life, I was looking for more battery life or is it even better to leave the setting off?
[OnePlus 3 & 3T Cross Device Development] nikexv2:
Decrease threshold =more performance increase =battery life
[OnePlus 3 & 3T Cross Device Development] Chaplan:
That's all theorical, and in theory I was under that assumption to.

In the real world a fine tunned fastlane threshold (and I mean Bellow stock 50 setting) on the Big cluster will have no negative battery impact.

I won't say the same about the Little cluster just because I haven't tested it yet, mainly because I don't feel the need to set it on the Little for the setups I use.

I have some battery tests on my todo list since Fastlane came out, but since I am happy with what i achieve using it on the Big only I refrained from those tests.

When OnePlus releases a new stable I might use it for a week or two and make the Little and combined tests.

But be sure no negative impact is achieved on the setup I mentioned. :good:
[OnePlus 3 & 3T Cross Device Development] storytellerz:
Thank you
[OnePlus 3 & 3T Cross Device Development] felonius:
Do u need blu twrp to flash blu kernel?
[OnePlus 3 & 3T Cross Device Development] twoxa:
Had all kinds of surprises with this kernel after flashing, from non working camera to disabled wifi switch and missing data connection.

Don't want to **** on it, but never had any of the above issues with other kernels for OOS.
[OnePlus 3 & 3T Cross Device Development] Nevermindthelabel:
Then you have something wrong on your end. Been running smoother than ever here, no glitches or anything and I'm on the unsupported beta 17 with my OP3. What's your setup?
[OnePlus 3 & 3T Cross Device Development] Nagi2195:
Make sure you flash the right version of it. It absolutely runs fine with no problems.
[OnePlus 3 & 3T Cross Device Development] Nevermindthelabel:
It's what [MENTION=3873953]eng.stk[/MENTION] recommends, and it's the best option for twrp. Haven't had any of the bugs reported from the official versions on my OP3
[OnePlus 3 & 3T Cross Device Development] knpk13:
No. You may use any recent version of TWRP, like red (unified) TWRP or green (optimized) TWRP.
[OnePlus 3 & 3T Cross Device Development] CRYPTfromCATACOMBZ:
Flashed the latest v35 version of TWRP, flashed on my Zenith RR rom (latest build) BLU r139 kernel and my both sims are not detected, my touch button and hardware keys are not working. Just simply don't do anything... And touch screen when i want to wake up my phone is not working too...
[OnePlus 3 & 3T Cross Device Development] marf28101995:
Flash the right version next time

All is fine with the kernel
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Non sense.

Follow OP instructions and flash proper version for custom ROMs.

If you really must flash a custom ROM there's plenty reportedly working nicely.

Some nice AOSP non EAS ROMs like Purity, DU and OMNI have been tested by team members.

If you want a stable and supported setup, flash OOS.

Anything else don't bother posting about it.
[OnePlus 3 & 3T Cross Device Development] Kord:
Hey,

Disable sdcardfs module is still needed?

Regards.
[OnePlus 3 & 3T Cross Device Development] MarcTremonti:
if you are on OB17 not i think. otherwise yes.
[OnePlus 3 & 3T Cross Device Development] nikexv2:
With the latest OB firmware it's not necessary anymore.
[OnePlus 3 & 3T Cross Device Development] Primokorn:
Next time please mention your ROM. You get answers for OOS but you may have other answers (or no support :)) for custom ROMs. It's fixed for a while on RR for example but you may need it for other custom ROMs (check in the thread of the custom ROM).
[OnePlus 3 & 3T Cross Device Development] Vixiebalistic:
What rom do you use? I'm on OOS 4.1.3 just test it by deleting 1 gb *. zip file and surprisingly my free storage back. AFAIK sdcardfs bug fixed in latest OB but i dont know why my storage back. It was never happen until i soft reboot my phone to get remaining storage reset after deleting some files. Now this issue fix with r139, at least for me.
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Nope

Either you have the sdcardfs disable module activated in Magisk, or you deleted with files picker or OnePlus File explorer.
[OnePlus 3 & 3T Cross Device Development] Vixiebalistic:
No mate, i dont use magisk at all and always use supersu. And i use solid explores as usual...but magic happen.
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Test it with a ROM zip file.

Media files get reported as cleared on the storage sometimes.

And are you using a OTG USB Drive by any chance?
[OnePlus 3 & 3T Cross Device Development] Vixiebalistic:
Just test it with whole rom zip file but it didnt work LOL... This make me crazy... My bad.
[OnePlus 3 & 3T Cross Device Development] Chaplan:
No problem.

Known issue, prone to get some placebo false positives either by forgetting the module is active (not your case) or by some file types.

It's solved on OB17/8. 4.1.3 is derped. Kernel won't solve this alone.

Let's hope OnePlus pushes it to the stable branch ASAP.
[OnePlus 3 & 3T Cross Device Development] RohanAJoshi:
So, now oneplus releasing kernel source before update release of os :D

Synchronize codes for OxygenOS 4.1.5

The changes list:

sdcardfs: update sdcardfs version

merge cve patch CVE-2017-6425 msm: mdss: Clear compat structures before copying to user)

merge cve patch CVE-2017-6423 soc: qcom: make debugfs support configurable for kryo l2 accessors)

merge cve patch CVE-2017-6426 platform: msm: spmi: Fix possible race condition in debugfs)

merge cve patch CVE-2017-0576 crypto: msm: check integer overflow on total data len in qcedev.c)

merge cve patch CVE-2017-0462 seemp: use local stack mem when encoding params)

merge cve patch CVE-2017-0454 ASoC: msm: qdspv2: add mutex lock when access output buffer length)

merge cve patch CVE-2016-10236 USB: gadget: mbim: Avoid copying uninitialized data to userspace)

usb: change product name to OnePlus for Android Auto

rtc: remove unused debug logs

https://github.com/OnePlusOSS/andro...mmit/33a109bb360e89182a0db0b00e0650b1b915f4a2

[MENTION=3873953]eng.stk[/MENTION] , [MENTION=3292224]franciscofranco[/MENTION], [MENTION=4684315]flar2[/MENTION]
[OnePlus 3 & 3T Cross Device Development] eng.stk:
What sorcery is this? :eek:
[OnePlus 3 & 3T Cross Device Development] harryfornasier:
I can't turn off touchboost on Ek kernel manager. It says disabled but whenever I touch the screen I can see the loads increase on the dashboard homescreen. I am on magisk, do I need to use super su?
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
Damn I have to say fastlane is the most awesome thing. Performance is simply amazing without destroying the Battery. I bet with fastlane enabled this phone would destroy every phone on the market right now when it comes to performance except maybe the Iphone.
[OnePlus 3 & 3T Cross Device Development] marqobazua:
Which values did you applied for fastline, and where? :p
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
I have a threshold of 35 for both big and little. You can enable fastlane using Kernel Auditor and then under CPU there is CPU governor Tunables. You can enable fastlane there by putting a 1 under "fastlane" and then adjust the threshold. You have to do this for both, Big and Little.
[OnePlus 3 & 3T Cross Device Development] marqobazua:
Ohh thank you so much, i am already on Blu_ active.. will this decrease the battery life in general?
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
It depends on the threshold. I'm getting through the day just fine using 35 on both Little and Big.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
You need to turn off (disable) cpu-boost, it also boosts on input.

That way you'll be running without any kond of touch/input boost, but that will ruin UX.
[OnePlus 3 & 3T Cross Device Development] Vixiebalistic:
Brace your self.. There will be someone asking "Is it compatible with OOS 4.1.5?" LOL.... Sorry just cant wait.
[OnePlus 3 & 3T Cross Device Development] Funk Wizard:
I rather see a new build coming up by [MENTION=3873953]eng.stk[/MENTION] with the updated sources [emoji6]

Sent from Funk Tuned 3T
[OnePlus 3 & 3T Cross Device Development] vatsal8286:
what is your fastlane settings?
[OnePlus 3 & 3T Cross Device Development] Nemuritor01:
Tested the custom Kernel version on PA Rom.

Everything seems to work. Very responsive.... No lags. Bluetooth, WiFi, everything is running.

Just the camera is not working. ?

Otherwise this would be the perfect Kernel, for PA, as well.

I know, that you don't support custom roms. But

If you could add this feature and release a PA Version, this would be really awsome.

I really don't know, how difficult it is to fix the camera driver? :rolleyes:
[OnePlus 3 & 3T Cross Device Development] Batfink33:
He's already said he's not doing a PA version! Forget it.
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
I wrote that 2 posts after the one you quoted.
[OnePlus 3 & 3T Cross Device Development] Nemuritor01:
I know, that he already said this.

I'm following the complete thread. I Just wanted to mention, that PA is completely working with the actual kernel, except the camera. Perhaps He was not aware.

And I really don't know, how difficult it is, porting camera drivers.

By the way... This Kernel and TWRP are awsome!!!!
[OnePlus 3 & 3T Cross Device Development] Explorer23:
It's not about difficulty, it's about compatibility. He'd need to make a kernel exclusive for PA, so we'd have 3 different blu_spark kernels ... I think there's enough confusion already (because people can't read and/or think) with 2 versions. Another version would mean more work, more questions, more OT ...

If (when?) more ROMs get based on PA, then we'll probably get PA compatible blu_spark.
[OnePlus 3 & 3T Cross Device Development] Chaplan:
[MENTION=5099202]Explorer23[/MENTION] has explained it quite well in the post above mine.

Of course the OP is aware of what works and what doesn't. We are not sleeping here.

It has been already discussed, internally, and on this thread as well.

For as much as we would like to have Blu running on PA it is not possible to follow every custom ROM so LOS based ROMS are what the custom version has been, is, and will be following/working on.

This was adressed by the OP in one of his latest posts. If you follow the thread closely you should know better.

4.1.5 is out. Aren't we lucky?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Best changelog ever :victory:

Tears of joy flow into my eyes...
[OnePlus 3 & 3T Cross Device Development] Flasher8:
Yeah....we waiting for your magic blu. :D
[OnePlus 3 & 3T Cross Device Development] Dieppy:
But no touch latency fix so we still need your magisk module?
[OnePlus 3 & 3T Cross Device Development] harryfornasier:
When I turn off touchboost and disable input boost the small cores seemed to be stuck at 1593 MHz and never dropped even if I left it idle for a few minutes. Once I turned touchboost back on the loads dropped.
[OnePlus 3 & 3T Cross Device Development] Chaplan:
I was hopping OPlus had forgotten to mention that on the changelog, tested, we need the module still.

No sweat. The Module works as good.

Metadata on BT has finally made it to stable.

Night mode is still green, and always will be. I need Amber on night mode no matter what.

But at least on stable it isn't turning sRGB off for the night mode. I don't understand that OB option.

I will leave the I/O bug/unbuged comment to [MENTION=3873953]eng.stk[/MENTION].

He started the revolution over that particular nasty thing.:good:
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Yep TP FW still not updated on 4.1.5, mod needed.

The sdcardfs bug is fixed, the struggle we've been doing for months, since I brought attention to this (and later xda portal feature exposure by [MENTION=7050182]MishaalRahman[/MENTION]) was worth it :highfive:
[OnePlus 3 & 3T Cross Device Development] Midomad:
I think they are doing great lately...

They release Kernel Sources in the release day(even before!)

I hope they will go on like this!
[OnePlus 3 & 3T Cross Device Development] misterepicwin:
true.

hoping they will do so after the release of the Op5
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Yeah, we have to give that to OnePlus on 4.1.5.

5 months after the initial no sources for N for more than a month and all the bumps on BT, I/O, Wi-Fi just to begin with on their stable branch.

I hope it's not an isolated case.

Making up for the OP2 poor update timeframe and opening up for the OP5, a good action was totally called for by OPlus.

A bit OFF Topic, but on release date, my opinion couldn't stay for me alone.

Let's hope they make of this a path for the future.

Being Dev friendly is more than just nice words.
[OnePlus 3 & 3T Cross Device Development] Mr.Crucial:
Oneplus is only doing all this in anticipation of op5 release.

?????
[OnePlus 3 & 3T Cross Device Development] Erik1805:
Can i flash the kernel over the latest OxygenOS 4.1.5 (7.1.1) OTA ?

Thanks
[OnePlus 3 & 3T Cross Device Development] Nemuritor01:
Why...????

Everything is clear.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r141 unified

All right crew!

New build is up. Wicked!

Because of latest TWRP changes, you'll need to use latest TWRP 3.1.0-1+ or flash my unified TWRP 3.1.1-x blu_spark v35 (recommended). Any other version will not have full support for the kernel and the installer.

Also take a look to the rest of blu_spark v35 extras to get some nice and useful additions to the kernel.

Keep it real, keep it true, keep it blu :highfive:

Keep in mind: I will give no active support for custom ROMs (including OOS based ones) or OB.

Meaning, if using anything besides stock and stable OOS don't bother posting about it.

I am only interested on debugging stuff in stock and stable OOS (with logs and reproducible steps to replicate the issue).

Don't spam this thread with CM or other ROMs stuff like "this don't work, my app doesn't open, etc" or debugging features.

Also don't go spam and bug reporting on ROM threads if using this.

If you like my work, donations are always welcome (but not mandatory).

Don't forget to hit thanks and rate the thread nicely, it's free ;)
[OnePlus 3 & 3T Cross Device Development] t181:
[MENTION=3873953]eng.stk[/MENTION]

I'm about to switch back to DU (from PA) and I was curious about what ROM are you using?
[OnePlus 3 & 3T Cross Device Development] Mar-cel:
I think [MENTION=3873953]eng.stk[/MENTION] uses Stock OOS stable.
[OnePlus 3 & 3T Cross Device Development] Primokorn:
Pretty obvious since he only supports OOS stock :p
[OnePlus 3 & 3T Cross Device Development] t181:
He used DU and Omni for quite some time. That's why I asked.
[OnePlus 3 & 3T Cross Device Development] mcdachpappe:
thank you very much for your work.

is there a chance that you release a custom version of your latest build (blu_spark_r141-oos_op3-op3t) as well?
[OnePlus 3 & 3T Cross Device Development] Sytis:
I don't think that the OOS source update affects us using the custom version. The other /proc/cmd fixes and the newer toolchain won't make a giant difference so maybe when there's more to change we get an update ;)
[OnePlus 3 & 3T Cross Device Development] The_Fry_Guy:
Hey guys, I really want to be on Stock Stable OOS so I am running what eng.stk supports, but I am a little confused when it comes to updates...

Does anyone know what the steps would be to actually update to a partial OTA after on stable OOS?

For example I install stable 4.1.5 with TWRP and then root and then OnePlus releases a partial OTA update (Under 1gb) and I want to install it... Would the steps be as below?

1. Full Unroot (Magisk Uninstaller)

2. Flash STOCK Recovery and reboot to system

3. Install partial OTA through system and reboot

4. Once booted reboot to fastboot and flash Blu_Spark TWRP and boot to recovery

5. Flash Custom Kernel and then Magisk

???

Thank you...
[OnePlus 3 & 3T Cross Device Development] DMagister:
Kernel should be the last
[OnePlus 3 & 3T Cross Device Development] andrea.ippo:
Dunno about Magisk cause I've always used SuperSU (and in fact I'm not even rooted, at the moment).

But in any case you can spare yourself some steps & time by getting the full image of the OTA (usually someone will share it on gdrive at some point).

What I used to do when I was SuperSU rooted:

1) flash full OTA image from blu_spark's TWRP recovery - this will remove root and apply the stock kernel, of course

2) flash SuperSU

3) flash the kernel

4) wipe cache
[OnePlus 3 & 3T Cross Device Development] lkbfreak:
When can we expect the v141 for custom roms?
[OnePlus 3 & 3T Cross Device Development] Stephen:
Moderator Information,

The OP of the thread has requested multiple times that there is zero offtopic on this thread. Please keep posts on topic.
[OnePlus 3 & 3T Cross Device Development] Puddi_Puddin:
Great Kernel thank you so much! <3