yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Pointless.

Old stuff isn't new just because is written today.
[OnePlus 3 & 3T Cross Device Development] fbf2201:
Didn't you read this in the article?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r67 unified

All right crew!

New build is up. Wicked!

I have merged f2fs upstream, all seems solid and retro safe but I do recommend backup just in case.

Because of unified adn f2fs TWRP changes, you will need to use latest TWRP build from xda thread or flash my TWRP 3.0.4-x blu_spark v22 (recommended). Any other version will not have full support for the kernel and the installer.

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

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

I am only interested on debugging stuff in 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.

No mirrors allowed

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] eng.stk:
TWRP blu_spark v22

All right crew!

Here's an updated TWRP with all the blu_spark goodies inside and fully synced with TWRP Android-7.1 branch (including more recent upstream than official TWRP).

I'm just sharing my personal recovery build since people asked, meaning no support will be given

If your cat get's on fire you're on your own ;p

No mirrors allowed

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] Chabola:
So is blue_spark #67 is for 7.1.1? cause when I flashed it the camera doesn't work
[OnePlus 3 & 3T Cross Device Development] Nevermindthelabel:
So I think you have your awnser...
[OnePlus 3 & 3T Cross Device Development] skyknife93:
No. Eng.Stk said he might release a test build if he feels like it. Get back to ob11 if you want sparky goodness:p (although you still can't expect support)

Sorry for the OT bro, but if possible, can you explain why my back button stopped working all of a sudden on Ob12? I know it's beta and will have bugs, but only getting back to 11 got it working again. I've searched the thread but couldn't find it so i hoped to get your opinion.

Just curious
[OnePlus 3 & 3T Cross Device Development] habylab:
You changed your mind about not expecting support very quickly there.
[OnePlus 3 & 3T Cross Device Development] skyknife93:
Just a question. Out of curiosity.
[OnePlus 3 & 3T Cross Device Development] habylab:
No support provided, as you say.
[OnePlus 3 & 3T Cross Device Development] skyknife93:
I'm already back on stable oos. Just asked if he knew why it happened. Wasn't expecting a fix.
[OnePlus 3 & 3T Cross Device Development] Chaplan:
If you flashed a kernel build for a different version of the OOS it was released for there really is no need to ask why this or that function does not work.

The answer is already given by your answer.

I keep hoping cats really got on fire when people do that.

But then again they would come back asking how the fire was caused....

:angel:
[OnePlus 3 & 3T Cross Device Development] skyknife93:
I already reported it broke camera after flashing it. It's my mistake i must have been clearer. I tried running Ob12 without blu_spark, after that. As it was. And out of the blue the back button stopped working. So i just sought his professional opinion on why it might have happened as it's working again on 4.0.3. That's all guys. I'm sorry about all this OT.
[OnePlus 3 & 3T Cross Device Development] abalam:
Hi everybody. Precisely update done from v14 to v22 version TWRP version. Have just made a backup of my ROM and now see a yellow text message that the backup does not take you all the files eg downloads etc. What is the reason for this? Thanks in advance.
[OnePlus 3 & 3T Cross Device Development] Dariusdd:
It wasn't backing up you

personal data

(photos, music, documents etc) before either. It's just a message to note the user of that fact. And if you're asking why it doesn't do that, the answer is pretty obvious: it wouldn't fit in your storage. And it wouldn't be feasible either, as it's much simpler and faster to copy those files over on a PC or a flash drive.
[OnePlus 3 & 3T Cross Device Development] abalam:
Okay so just a notification. Okay dude thanks for the explanation.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r69 unified OB test

All right crew!

New build is up. Wicked!

I decided to push a test build for OB12/3. Why? Because I can :angel:

This features the camera fix on OB and also brings back fastlane (revamped) on a rebased blu_active from android-4.4 linux.

You can now use fastlane by cluster( it's disabled by default) and choose a threshold for it to kick in (default is 50 which is somewhat conservative, probably we can go a little lower).

Don't forget I will give no support for this beta builds, but you're welcome to share your thoughts on fastlane v2 :highfive:

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

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

I am only interested on debugging stuff in 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.

No mirrors allowed

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] B3501:
Incredible support! Thanks!
[OnePlus 3 & 3T Cross Device Development] ricardowec:
Hello, Is r69 good for OB 12 only?
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
Yes, the current release is a test build for ob12. Give him time and most likely there will be a release with the updates for stable OOS and LOS as is the normal custom. Just be patient.
[OnePlus 3 & 3T Cross Device Development] yung40oz84:
Is the recovery only for f2fs or for ext4 also?
[OnePlus 3 & 3T Cross Device Development] marf28101995:
Come on mate .. the support for ext4 dropped long time ago
[OnePlus 3 & 3T Cross Device Development] yung40oz84:
OK, and I don't keep up with this thread.... Simple question, no smart reply needed. Yes or no would have sufficed.
[OnePlus 3 & 3T Cross Device Development] DragonSlayer240:
Cool! Already flashed it and I could say the camera is working fine here... Not sure about​ battery life but the smoothness is literally no difference compared to stock kernel but so far so good... Keep it up!
[OnePlus 3 & 3T Cross Device Development] MrMeeseeks:
[MENTION=3873953]eng.stk[/MENTION] Sorry to spam the thread, but thanks for releasing r69. It's working great so far and I can pass SafetyNet with it. I did thank the post for it as well.

Edit: Just didn't want you to think I was one of those guys that doesn't know how to hit the thanks button.
[OnePlus 3 & 3T Cross Device Development] Nevermindthelabel:
Sure is nice to have fastlane back! Feels smoother and quicker than ever. Almost not fair every other device I have feels ancient. Latest twrp is amazing as well. Thanks [MENTION=3873953]eng.stk[/MENTION]
[OnePlus 3 & 3T Cross Device Development] marf28101995:
If you don't keep up with this thread is your problem, follow the rules next time and you won't have a "smart answer " because you'll search before

;)
[OnePlus 3 & 3T Cross Device Development] Lownita:
Flashed r69, big cluster is stuck on 2150 MHz for me, rooted OB with SuperSU.
[OnePlus 3 & 3T Cross Device Development] DragonSlayer240:
Already tried rebooting?
[OnePlus 3 & 3T Cross Device Development] B3501:
Reboot. Or flash again
[OnePlus 3 & 3T Cross Device Development] peshellas:
Also try running in terminal,

Su

Setenforce 0

Even if you are in permissive already.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Yes only for OB 12/3. A beta for a beta.

We are on OOS with 7.1 and people still post about this in kernel threads? Geez.

No need for anything like that.
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Haha. Just had a good laugh there... I felt the same way but only when I had the screen off. :cyclops:

Won't go into details but FASTLANE is the only thing I missed from my Nexus 5 on Blu_kernel for the OP3.

FAAAASSSSTLANE...

Sorry. Apart from my obvious OCD I suffer from Tourette from time to time.

FAAAASSSSTLANE...

Test it out... It's superb.

No not superb... It is wicked... as stated by the OP.
[OnePlus 3 & 3T Cross Device Development] habylab:
Why do you say OB12/3, are you just guessing it will support the next OB?

On top of this, is there any chance you can block the IPA_WS and wlan_rx_wake kernel Wakelocks​? I know Franco blocks these, along with one other Wakelocks, and it does take up a fair amount of battery (currently 6-7% per battery cycle).

https://github.com/franciscofranco/one_plus_3T/commit/f21dd7def52fb5d77b83e8232f3a9b390b0108d3

https://github.com/franciscofranco/one_plus_3T/commit/7ec73dc5052be0906c87a3770b6f7d980a73e2fd

They are the links I believe!
[OnePlus 3 & 3T Cross Device Development] Nevermindthelabel:
OB3 is the 3T equivalent of OB12. And he's already said not interested in blocking the wakelocks
[OnePlus 3 & 3T Cross Device Development] habylab:
Oh sorry, on both of those!

As you were.
[OnePlus 3 & 3T Cross Device Development] sarus_b:
I'll just repeat for 4635th time.. Don't use kernel adiutor.. Bug in app causes that cpu freq locking.. Use paid Kernel adiutor or any other alternative..
[OnePlus 3 & 3T Cross Device Development] Achu Gowda:
Dude use ex kernel app dnt use kernel auditor, dis app behaves differently automatically it locks little and big cluster threshold....

I've flashed r69.. Awesome battery n god like stable...Thank ueng.stk for releasing test version..

---------- Post added at 09:07 PM ---------- Previous post was at 09:04 PM ----------

Can anyone of you explain what fast lane is..

Sry for being dumb
[OnePlus 3 & 3T Cross Device Development] eng.stk:
fastlane is a well know tunable for blu_active on other devices.

It makes freq switching more agressive and dinamic.

I updated it for HMP and now you can activate it and get it only to kick in after a given threshold.

This will get the device to be more responsive, but also keep power draw not to get wild.
[OnePlus 3 & 3T Cross Device Development] B3501:
It happens in paid kernel auditor for me as well. It's a Rom bug.
[OnePlus 3 & 3T Cross Device Development] Achu Gowda:
Thanks for d explanation

So u tld default is set to 50...Lowering it will increase aggressiveness​ or vice versa.??

---------- Post added at 09:44 PM ---------- Previous post was at 09:42 PM ----------

If it's a rom bug..Then it shud happen for all kernel apps...Y can't it happen in ex kernel..?
[OnePlus 3 & 3T Cross Device Development] B3501:
It happens even when not rooted with me, also check the One Plus community forum loads of threads about it on there where people aren't even rooted. OOS is a mess.
[OnePlus 3 & 3T Cross Device Development] Achu Gowda:
What's d use of kernel manager app if phone is not rooted in the first place:confused:
[OnePlus 3 & 3T Cross Device Development] eng.stk:
It happens with some apps, it has been discussed.

It has to do with the way OnePlus uses the boost framework.

The fastlane threshold if it's lower it will make fastlane kick in sooner yes.

Exactly.

Yep, people just continue to ask same questions when stuff has been discussed so many times.

Now enough of this OT.
[OnePlus 3 & 3T Cross Device Development] habylab:
Never had this issue, and there was a brand new beta release just now...
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Lucky you!

I have had it on the

first N OOS Beta with stock kernel

so definitely not kernel related. The ROM has these hiccups.

You may encounter this in many scenarios.

Gonna leave here a spoon to feed all those that can't read more than a few pages a day and search properly:

1 - Clear Adiutor cache and data and reboot. Make sure you are using only one app for kernel management.

2 - If coming from another custom kernel flash ROM or original boot.img first. If you need root flash it and only then flash Blu_spark. (ROM/SU/Blu_spark is always the mandatory sequence for flashing)

3 - If none of the above works you need to wipe Cache and Dalvik (in recovery). This will make App Optimization kick in when you boot to android so let it settle for a while before you check frequencies again.

4 - If none of the above works your only option is to clean flash from the start. Never really had to do it but i leave that option to myself as a last resort.

5 - Enough OT means exactly that... enough OT. This is a kernel development thread.

Now on Fastlane and Back to Topic:

Fastlane is Blazing fast on frequency switching.

I have enabled it on Big Cores only. It may look like they are a bit stuck at 1248MHz on Adiutor if you check frequencies with it when Fastlane is on.

Use DevCheck instead. It has a higher refresh rate than Adiutor and you can see it is just fine.
[OnePlus 3 & 3T Cross Device Development] snippem:
Maybe a noob question but what is the right way to enable fastlane.

And how to interpretate the settings ?? In the screenshot I haven't touched any settings.
[OnePlus 3 & 3T Cross Device Development] Nevermindthelabel:
Set fastlane to 1 to enable
[OnePlus 3 & 3T Cross Device Development] deepongi:
Anyone having issues flashing this?

I tried to flash the zip via TWRP, but I end up with the same kernel, stock from the 28th.

I even tried to flash via TWRP, the newboot.img stored on /tmp during the procedure.

I then recalled to flash it via FlashFire apk, and it was successful.

Which logs are needed to debug this?

Great work btw, in providing these builds for the open betas.

Regards.
[OnePlus 3 & 3T Cross Device Development] snippem:
Delete have to learn reading :cyclops:
[OnePlus 3 & 3T Cross Device Development] slothdabski:
on OP3 has the OB12 kernel broke wifi?

i looked pages back since the OB12 beta kernel release and havent seen this mentioned.

not looking for support, just wondering if anyone else is experiencing this or if its another issue on my end.

Thanks!!!
[OnePlus 3 & 3T Cross Device Development] manjartens:
WiFi is okay here on r69.

Try reflash Rom and then kernel
[OnePlus 3 & 3T Cross Device Development] slothdabski:
Thanks for the info, I just flashed stock boot image, then the OB12 kernel and now wifi is working great! not sure why it derped on the first flash, but oh well! :)
[OnePlus 3 & 3T Cross Device Development] volldez:
Love this kernel man!! was soooo happy to see you bought kernel over to OB12, was seriously thinking going back to 4.03 just so I could use your kernel. Everything working great with fastlane enabled on big core with no effect on already exceptional battery life!! :) :D
[OnePlus 3 & 3T Cross Device Development] stavca:
I had the same issue on OB3 on OP3T but I flashed magisk also
[OnePlus 3 & 3T Cross Device Development] immi803:
Probably most of you not flashing kernel after clean install or flashing before super su flash, no wifi problems or any big core stuck problems found with ob3 op3t

Yes I'm curious to hear where most of you have set threshold?

Fast lane 2 is awesome mate [MENTION=3873953]eng.stk[/MENTION]

I'm using default 50 threshold by the way, snappier
[OnePlus 3 & 3T Cross Device Development] CroW_D:
[MENTION=3873953]eng.stk[/MENTION] so fast lane is only present on the ob build will it be available on the custom version tho ?
[OnePlus 3 & 3T Cross Device Development] immi803:
[MENTION=3873953]eng.stk[/MENTION]

Do you recommend fast lane on both clusters?
[OnePlus 3 & 3T Cross Device Development] FlyingMachete:
:laugh: I loved that!! When Junior-Truth comes ****-slapping :laugh: I mostly stick around for TWRP now, as my ROM handles the kernel like a cloistered nun on meth. :D
[OnePlus 3 & 3T Cross Device Development] emuandco:
OK, no support is known, buuut... am I the only one with no WIFI with r69 @ OB12? Only thing I did is adding Magisk 11.1, too.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
If people were fast using the search button instead of complain...

You issue resides with Magisk, nothing to do with kernel.

Eventually will come to stable brancbes, right now is time to test.

I recomend people to test and let us know.
[OnePlus 3 & 3T Cross Device Development] spetrie:
I have no WiFi too. Have reverted back to stock kernel as no support for this beta on OB12.
[OnePlus 3 & 3T Cross Device Development] NickosD:
I have WiFi and I use the magisk version that comes with freedom os
[OnePlus 3 & 3T Cross Device Development] Chaplan:
It has been discussed before on the thread.

If only users searched a bit more than nothing at all.

Only root option with support is Chainfire's SuperSU.

If your root option is another one you are on your own.

Magisk has already been reported to have some modules that derp wifi.

Now back to Topic as we were!
[OnePlus 3 & 3T Cross Device Development] joakimbo:
I have OB3 rooted with Magisk. Just flashed r69 and working supersmooth. Performance is stunning. Never seen a phone so smooth. Fastlane enabled on big core. Battery life seems also really good so far. Wifi and everything working.
[OnePlus 3 & 3T Cross Device Development] ed33:
I've never been blown away using this phone. Came from a nexus 5 using blu spark kernel. Nexus 5 was a great phone really smooth and fast, think the smaller screen has alot to do with it feeling faster.

But now with this latest beta kernel and fast lane enabled on both clusters its really quick and smooth.

First time I've felt it matches my good old nexus 5 since having the one plus3.

Well done. ?
[OnePlus 3 & 3T Cross Device Development] liver20:
Fast lane can be used in custom build of kernel?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Yet another hammerhead :highfive:

Welcome mate :good:
[OnePlus 3 & 3T Cross Device Development] B3501:
Can I ask a question [MENTION=3873953]eng.stk[/MENTION]? How do you make the 7.1.1 kernel since there are no sources? Do you take the 7.0 kernel and see what doesn't work and then fix it?
[OnePlus 3 & 3T Cross Device Development] NickosD:
Hint for the next time. READ THE WHOLE POST LOUD AND CLEAR so you can understand what I'm writing.

BTW, even if I had issues, it's better not to answer at all if you're not gonna give a helpful answer.
[OnePlus 3 & 3T Cross Device Development] DragonSlayer240:
Ok so I already tried with Fastlane enabled... Pretty smooth actually with fastlane threshold on 50 at the moment since its the default one from Blu_Spark... Is there any preferable tweaks for it? Would like to see other users' tweaks for it
[OnePlus 3 & 3T Cross Device Development] Chaplan:
I have not quoted YOU in that post have I?

Well I for sure am quoting YOU now.

I was not talking to YOU in particular but in general to the "Magisk thingy" OffToping on the thread.

Since i have not quoted YOU in particular but nevertheless YOU were offended by my statement (do not confuse statement with answear) maybe not using CAPS to address me would be nicer and just fine.

I have read the whole thread not just the whole post. It has been discussed before.

The answear to the "I have no WIFI on this kernel with Magisk" had (past tense for days not just a few hours) been already given.

The problem is not kernel related and the discussion should be taken elsewhere. Maybe ask for the Magisk thread to be open and discuss the troubled Modules there instead.

In this thread rules apply and are stated in the OP.

In this thread Search is also your friend... (Again "your" in general and with no CAPs, don't get offended)

So to YOU that's all, hope WE can keep it that way and you are of course welcome to participate on the thread.

After all it's an open thread with a few basic rules.

Now back to the Topic

That's exactly what [MENTION=3873953]eng.stk[/MENTION] is asking us.

For users to test it and tweak it a bit for their likes and then report on the thread.

Involving the users on the process is what is on the table since it's in beta stage.

I am using it on BIG cluster only with a threshold of 50.

I see no impact on battery so gonna lower the value in the next days for testing purposes although 50 is already a huge improvement overall in my case.
[OnePlus 3 & 3T Cross Device Development] slothdabski:
I had this issue at first too. It's because you flashed r69 over a kernel patched by magisk. Flash magisk uninstall zip or restore stock boot IMG, the flash r 69, the flash magisk. You'll will then have wifi!
[OnePlus 3 & 3T Cross Device Development] candiesdoodle:
With fastlane enabled on both clusters and with the usual settings on cpu boost, my fingers literally gave up keeping pace with the quickness on the screen! I mean it. Super super quick and ultra fast.

And so to make it more manageable I have disabled cpu boost and enabled fastlane only on smaller cores.:laugh: it's much more 'human' now.

Loving it.
[OnePlus 3 & 3T Cross Device Development] immi803:
With both clusters on, how was your battery?
[OnePlus 3 & 3T Cross Device Development] emuandco:
Thats true, it was Magiskified STOCK. Works :D Thx ^^
[OnePlus 3 & 3T Cross Device Development] NickosD:
Anyone is having any issues with proximity sensor in beta 12? Today someone called me and noticed that the screen didn't went off.

---------- Post added at 12:20 AM ---------- Previous post was at 12:02 AM ----------

*after a reboot it's OK again.
[OnePlus 3 & 3T Cross Device Development] Duncan1982:
Been Testing Fastlane on both clusters almost since release & running well :good:

Also tweaked the threshold to 60 (why hmmm no idea larger numbers are better....:p)

Appreciation to eng.stk for all his efforts, and for maintaining and keeping thread on track....:laugh:
[OnePlus 3 & 3T Cross Device Development] nikhilsnigam:
lower the better according to OP
[OnePlus 3 & 3T Cross Device Development] habylab:
Tried fastlane on both clusters today, stock settings otherwise. Just over 3 hours screen on time. Beforehand was similar. I'd say a tiny extra bit of SOT, but definitely feels faster.

Can you clarify please, I see you think 50 for fastlane_threshold is too conservative. So which was would perhaps be faster or better for battery life? I suspect going down. Tried 5 (to see) and it didn't seem to jump up quickly.
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
You should see faster speeds by lowering the fastlane threshold to a lower value. I suspect 5 to be much to low and cause your frequencies to spike frequently
[OnePlus 3 & 3T Cross Device Development] habylab:
I'll raise it first then, and see if there is an improvement.
[OnePlus 3 & 3T Cross Device Development] candiesdoodle:
Active drain was a bit higher I would say.
[OnePlus 3 & 3T Cross Device Development] snippem:
Lol just my opinion about the value discussion.

If 50 means milliseconds that is already really fast( 20 times faster then a second )what is the point of lowering it?It instantly kicks in?
[OnePlus 3 & 3T Cross Device Development] alvin182:
WiFi on FreedomOS CE + Blu Spark r69 its working fine for me and im using akt profiles too with magisksu.

Only the smart WiFi changer are not working well.

Well done anyway.
[OnePlus 3 & 3T Cross Device Development] sator02:
H2OS + Blu spark r69 is really awesome, smooth, fast and good battery back up (enable fastlane 1, big only).

Thanks for this great custom kernel.

Sent from my ONEPLUS A3010
[OnePlus 3 & 3T Cross Device Development] brmbjn:
Mr otto. Thanks.