yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Konskl:
That's what i thought myself but that doesn't seem to be the case....have you managed to succesfully flash blu 73 and still retain root? if yes on which rom? thank you.
[OnePlus 3 & 3T Cross Device Development] thelad:
True but only when flashed this kernel,so freedom mustn't be playing well with blu_spark or other way round
[OnePlus 3 & 3T Cross Device Development] Klobal:
I was running stock 3.2.2 with installed supersu and flashed r73 today. Supersu is still running as expected.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
As I said 100 times before, blu_spark uses whatever is in place before it's flashed.

In an already rooted ROM, just flash kernel zip and profit.

Kernel doesnt touch or care anything root related.

Also, as stated in OP, I support completly stock ROM without any mods appart from root.

Any varitation of that you're on your own.

Keep the thread clean of offtopic ROM discussion.
[OnePlus 3 & 3T Cross Device Development] evanxyj:
Dirty flashed the full ota zip and then kernel zip, fixed. Thanks.
[OnePlus 3 & 3T Cross Device Development] hellkun:
what a great job for eng.stk and Oneplus bringing dash charging to this great kernel!
[OnePlus 3 & 3T Cross Device Development] therebel88:
This is one incredible kernel. Many thanks for your work :svetius:
[OnePlus 3 & 3T Cross Device Development] NevaX1:
[MENTION=3873953]eng.stk[/MENTION] Can you add changelogs in OP please :)

I miss that
[OnePlus 3 & 3T Cross Device Development] yellowsn0w:
does dash charge work on latest official cm?
[OnePlus 3 & 3T Cross Device Development] nihilista:
Unified means you have one file for 2 devices (op3 and op3T), so there is only one oos file and one for custom rom, not more... And i see just one oos and one custom file in download section, so what did you see there?
[OnePlus 3 & 3T Cross Device Development] skyknife93:
That's because eng.stk develops the oos one on a daily basis and it's his daily driver.
[OnePlus 3 & 3T Cross Device Development] MarcTremonti:
He means that there wasnt a custom zip for r47 and r49, which is correct.
[OnePlus 3 & 3T Cross Device Development] Chaplan:
It sure is safe to do whatever you need to do on TWRP. Just flash and do your stuff.

TWRP moded by [MENTION=3873953]eng.stk[/MENTION] is all over the forums and the internet. It is the standard for the OP3 and 3T flashaholics.

Then there is the official version for those who like to wait for it to boot. :)

As for kernel, custom is for custom ROMs and OOS is for OOS ROM.

If a build for OOS is not accompanied with a Custom build you probably can keep using the latest custom build and eventually it should be updated as needed.

Custom builds have no official support by the OP but get the same "LOVE" as you would expect for the OOS builds.
[OnePlus 3 & 3T Cross Device Development] AcmE85:
Can't confirm that.

On my OP3, running OB 11 @F2FS + r55, there is no speed difference between latest official TWRP 3.0.4-1 and v16.

Both boot up at the same time and take the same amount of time to decrypt up until the main menu shows up.

I was curious after reading your post, that's why I did a quick test myself just now.

No meaning to discredit [MENTION=3873953]eng.stk[/MENTION]

I am thankful for his constant work and his modded TWRP.

The first one actually to fully decrypt Nougat+F2FS before the official one got updated.

Besides that, r55 works like a charm on OB11!
[OnePlus 3 & 3T Cross Device Development] Chaplan:
None taken I presume.

I never flashed the official one. No really need for it. Always used the modded one. Personal preference maybe.

Not trying to be disrespecfull to the maintainer either. It is just what I read on the official thread.

This modded TWRP has always been a step ahead. As you stated yourself.

It's XDA and everyone is free to use what they like.

Some use the good stuff, others use what the majority thinks is the best.

Be happy...
[OnePlus 3 & 3T Cross Device Development] Ducter:
Custom is just that, not stock oos. Lineage would fall under the custom umbrella, he has said in the past he did not update the custom as he saw no need, that's why you do not see a custom version for each stock version he releases.
[OnePlus 3 & 3T Cross Device Development] jocaboss:
Hi, it's possible to install a theme for this twrp recovery? I don't like the old fashion design at all.
[OnePlus 3 & 3T Cross Device Development] Sytis:
Might be possible so "try and let us know".

The best thing would be to make it look like the OnePlus recovery that has been modified.

But let's keep on topic
[OnePlus 3 & 3T Cross Device Development] Lownita:
I'm curious, what's different with modded TWRP so that it boots up fast with data partition on f2fs? Last time I checked the official thread, the maintainer said he couldn't solve that issue.
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Don't know how long it takes to boot official really.

Personally I use only the moded one.

It just works and has been like that ever since.

Like I said before.

I only use the good stuff.

There is a version that works and for me, the user, that is what is different.

Thank the DEV, profit and be happy.

Man, and it really works in all the various scenarios I have put it through.

:good:
[OnePlus 3 & 3T Cross Device Development] Hecke92:
You can't be serious. Look one reply above yours.
[OnePlus 3 & 3T Cross Device Development] Schrotty35:
Sorry dont read. Now flashed blu twrp and Kernel.

Edit: both flashed. No boot time differnt to 3.0.4-1 ?
[OnePlus 3 & 3T Cross Device Development] trawel:
I know this is probably not the right place to write but I might have found the reason why CPU stucks at max freq. Noticed that when using tapatalk, CPU gets stuck at max and I have to remove it from recents to unstuck the CPU. Anyone maybe has the same problem?
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Official TWRP takes a long time to boot when DATA is formated as F2FS.

It's stated on the Official TWRP OP and is confirmed/complained by it's users on it's thread.

If it is not the case anymore on the latest version I really don't care. It was never an issue for me.

Just because, wait, wait, I NEVER USED IT ANYWAY!!!

People use what they want... Plain and simple.

If they like to spend time waiting for stuff to boot and to be properly debugged. Not my problem.

Now enough OT about TWRP...

This is a kernel thread that happens to have a TWRP moded version that just works... and is pretty well known for it.
[OnePlus 3 & 3T Cross Device Development] Schrotty35:
I use f2fs and i dont convert to ext4 for faster boot in twrp. The Kernel is ok.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Not the reason but one of many reasons.

The reason in particular is framework boost OnePlus set in, that is derpy in some situations (noticeable when apps load ads for instance), which locks cpu on boosted state indefinitely.

Nothing we can do from the kernel side.

I just wished OnePlus continued with OOS 3.2 branch, I'm so tired of OOS 3.4 and 4.0 that I'm really considering rocking a custom ROM for daily driving.
[OnePlus 3 & 3T Cross Device Development] Mar-cel:
You don't understand what you read.....
[OnePlus 3 & 3T Cross Device Development] Schrotty35:
Lol is ok.
[OnePlus 3 & 3T Cross Device Development] daviss101:
Is it possible to flash your newest twrp v16 as an image inside twrp v15?
[OnePlus 3 & 3T Cross Device Development] Explorer23:
Sure
[OnePlus 3 & 3T Cross Device Development] daviss101:
Thanks for quick answer, IV never attempted before so just flash and reboot into twrp right?
[OnePlus 3 & 3T Cross Device Development] Explorer23:
Correct ☺️
[OnePlus 3 & 3T Cross Device Development] :
I have done searching, but hmm too lazy to read i guess if there is an answer :p

Not on the latest version, I'm on build v15.

I'm on OOS 3.2.8 (need xposed badly), data ext4, encrypted, blu spark kernel for M oc.

If I set finger and pass/pin at boot, TWRP ask for password which later failed to decrypt the data.

Is that supposed to be since eng_stk now focus on f2fs? or the latest build has fixed it? or should i get back to the previous build? but seems.. it has been deleted, i can't find it.

If i delete/set none first, it's okay though.

If logs needed, i'll be happy to pull it :good:
[OnePlus 3 & 3T Cross Device Development] t181:
Well, if you find a custom ROM worth using as a daily, please let us now! I've alawys returned to OOS so far.
[OnePlus 3 & 3T Cross Device Development] IvanSoria:
Exact. I support You

Regards
[OnePlus 3 & 3T Cross Device Development] liver20:
Well..... Try with slim rom , won't come back to oos sure

Enviado desde mi Slim OnePlus3-T mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] wokdogol:
Thnks for the update, seems smooth than the previous ver. No problem so far. Thanks [MENTION=3873953]eng.stk[/MENTION]
[OnePlus 3 & 3T Cross Device Development] B3501:
There's nothing really to post on this thread as there's no bugs and the kernel works so well! It just works great!
[OnePlus 3 & 3T Cross Device Development] jdavis7882:
Have you been using this kernel with Slim7? I tried flashing a while back and WiFi didn't work..
[OnePlus 3 & 3T Cross Device Development] Funk Wizard:
Yes it themes well, yet another reason to stay on the modified one :fingers-crossed:
[OnePlus 3 & 3T Cross Device Development] Krissyzen:
hmm. flashed r55 over r49 on 3t, sometimes phone freezes and I need to reboot it :crying:. flashed 49 again and it's okay.. am I the only one with this issue? oos4.0.2
[OnePlus 3 & 3T Cross Device Development] Skinpipe:
I think r55 is for 4.0.3, i might be wrong/making it up
[OnePlus 3 & 3T Cross Device Development] samisharora:
Thats right, if anyone is on OOS 4.0.2, its better to stay at r49 version. r55 include 4.0.3 code drop from Oneplus
[OnePlus 3 & 3T Cross Device Development] Stroky:
R55 is running great on the latest open beta.
[OnePlus 3 & 3T Cross Device Development] wokdogol:
No problem here, running great r55 at 4.0.2 :laugh:
[OnePlus 3 & 3T Cross Device Development] t181:
Same here!
[OnePlus 3 & 3T Cross Device Development] jocaboss:
It's already done. Looks awesome now.
[OnePlus 3 & 3T Cross Device Development] liver20:
No works.

But slim 7 for me is the more stable and Best rom.

Bluespark the Best kernel, if [MENTION=3873953]eng.stk[/MENTION] Could make work wifi....

Enviado desde mi Slim OnePlus3-T mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Nothing for me to fix, custom ROMs can use latest N configs and build kernel wifi driver builtin, all will work fine.

Edit: and on Slim 7.1.1.build.0.11 wifi actually works fine
[OnePlus 3 & 3T Cross Device Development] Hassan92:
I am in OOS 4.0.2 flashed r55 very 1st day no problem at all ... I think this is the most stable and smooth version till now .... Getting superb battery backup 5h + with heavy usage #OP3
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Yeah I'm happy with result, shouldn't be too much difference between latest 1 or 2 builds on that department.

N OOS is giving too much headaches a bit all over the forum, waiting for better times.

I found a small bug because of a mismerge in the custom build, let's see if anybody finds it.

Well depends in what you want/need from a ROM.

On the latest days I'm rocking between LOS and OMNI to test some stuff and because it suits me the best.
[OnePlus 3 & 3T Cross Device Development] t181:
Thank you! I think I'm gonna try out OMNI. Not sure about LOS, never been fan of CM.

Edit:

Your custom kernel should be fine, right? Or you are using it with an unreleased kernel of yours?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Custom will work with most custom ROMs out there.
[OnePlus 3 & 3T Cross Device Development] Flamehell:
Running Omni + Blu spark....rock solid!!!;)
[OnePlus 3 & 3T Cross Device Development] liver20:
WiFi works?

Try oms with omni?

Enviado desde mi Slim OnePlus3-T mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] Flamehell:
Is not the proper forum to talk about that,but wifi is working,and omni doesn't have oms support..:)
[OnePlus 3 & 3T Cross Device Development] Pollie81:
Wifi works!

omni isn't oms compatible, only legacy support as far as i know.
[OnePlus 3 & 3T Cross Device Development] Dmega86:
Which is the last Kernel version that can be used with OOS 3.2.x?
[OnePlus 3 & 3T Cross Device Development] Butit:
I think someone said a few posts back that it's r49.
[OnePlus 3 & 3T Cross Device Development] Explorer23:
Umm ... R49 is second last version... Definitely for Nougat and not for 3.2.x.

Last for MM was somewhere around 160 iirc. Will check and report back.

UPDATE: it's 168. Here's the link: https://xdaforums.com/devdb/project/dl/?id=22067
[OnePlus 3 & 3T Cross Device Development] Chaplan:
r28 is the latest version released for MM (3.2.8)

It's great to help one another, just try to do it on a way they don't come back to say they have no Wifi and so on...

Clearly that version is for N.

Not bullseye but close... :good:

Keep up.... and sparked!
[OnePlus 3 & 3T Cross Device Development] Explorer23:
Yup, you're right, somehow missed that ... I'm getting old ?
[OnePlus 3 & 3T Cross Device Development] eroigaps:
Zenity RR. It's perfect.

On topic, thank you for the kernel! Running smoothly on said ROM.
[OnePlus 3 & 3T Cross Device Development] Butit:
My bad then...Apologies for the mistake.
[OnePlus 3 & 3T Cross Device Development] westenlive:
Hello to all

I thank you for this fantastic kernel.

I must ask you some information.

I'm used to hold the smartphone cpu always high with all cores enabled.

Since I bought the OnePlus 3 this it was not possible with any kernel that I have tried.

I wanted to know if I can have with your kernel CPU to the maximum frequency with 4 cores enabled.

thank you
[OnePlus 3 & 3T Cross Device Development] dante_nfs:
It's possible, not just in this kernel nearly in all kernels. You have some ways to do it, like putting the governor in performance mode(with some kernel modification apps like kernel auditor or EX kernel Manger) , in this mode all 4 cores will run in highest possible clock.
[OnePlus 3 & 3T Cross Device Development] westenlive:
not is easy.

When i try to set performance, the little cluster set to max mhz , the big cluster after many minutes go offline, and dont reactivate.

This cause many lags.

i try but dont know the solution.

wait a expert of kernel

thank you
[OnePlus 3 & 3T Cross Device Development] comediiian:
edited.
[OnePlus 3 & 3T Cross Device Development] dante_nfs:
That's because of throttling, the big cores can not run in highest clock for many minutes. This method will drain your battery fast without having an noticeable advantage. About being them disabled, the system will shuts them down to retain the normal temperature. If they don't come back online after cooling, that's what an dev can help you with.
[OnePlus 3 & 3T Cross Device Development] westenlive:
dont belive.

The big core stay off also when the smartphone is very cool.

I think this is a big bug.

I have oneplus 1 and not have this problem, same with nexus4,acer liquid, nexus7.

the termal problem is another question
[OnePlus 3 & 3T Cross Device Development] dante_nfs:
Downclock the little cores to 1478, and use the big ones without overclocking. Test and see if this solves your problem.
[OnePlus 3 & 3T Cross Device Development] cba1986:
using slim 7 with r55 and wifi works just fine!
[OnePlus 3 & 3T Cross Device Development] eng.stk:
There's no hotplug in kernel, cores will be always on.

If you use always max freq, you will enter continued thermal throttling so thermal daemon turns off cores to cool the device (adn turn them back on after cooling).

This is controlled from userspace, not kernel.

Also don't use OC freq if that's the case.
[OnePlus 3 & 3T Cross Device Development] Pavononer23:
Is this kernel working on OOS 4.0.3 without any problems on OP3T?

Thank you very much in advance!
[OnePlus 3 & 3T Cross Device Development] B3501:
Yes.
[OnePlus 3 & 3T Cross Device Development] immi803:
[MENTION=3873953]eng.stk[/MENTION]

Here to report two things regarding custom build r55

1. Gpu stays at 0

2. Wi-Fi hot-spot not working, says "error"

Reporting as checked on different custom roms, looks not rom related, just reporting as i know that no active support is available for customs

Thanks
[OnePlus 3 & 3T Cross Device Development] eng.stk:
1. Don't know what that is

2. Works on LOS
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r59 unified

All right crew!

New build is up. Wicked Valentine's!

Because of unified TWRP changes, you will need to use latest TWRP build from xda thread or flash my TWRP 3.0.3-x blu_spark v16 (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.

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] immi803:
Gpu states as 0, as in oos it stays

See Wi-Fi hot-spot error

Edit : sorry i mixed gpu clock speed with gpu state, you're right mate, nothing in gpu, apology

Only concern is wifi hot-spot
[OnePlus 3 & 3T Cross Device Development] Flamehell:
Tnx a lot buddy for this amazing job ?

Guys,if you are using omni rom,this is The Kernel...:good:
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Like I said works fine in LOS, nothing I can do for you.
[OnePlus 3 & 3T Cross Device Development] Flamehell:
It s an issue with omni and custom kernel bro...have the same :good:
[OnePlus 3 & 3T Cross Device Development] audinak2:
Sorry for the stupid question, but will TWRP 3.0.2-23 work with this build or will I have to flash a newer one? I'm on OOS 4.0.3 btw :)
[OnePlus 3 & 3T Cross Device Development] Lownita:
Omni doesn't like custom kernels, also screen gestures wouldn't work. Better stay on stock kernel using Omni ROM.
[OnePlus 3 & 3T Cross Device Development] Primokorn:
I had this issue on several LOS based ROMs. I didn't want to report here :p Actually the touchscreen didn't work as soon as I locked the phone.

I'm gonna flash your latest release and try your trick.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Read:

Because of unified TWRP changes, you will need to use latest TWRP build from xda thread or flash my TWRP 3.0.3-x blu_spark v16

It's a matter of using the latest patchsets sometimes. Gestures were expanded on LOS so needs updating on ROM controls to match kernel changes, wifi maybe it's similar idk.

I gave some links there to update gestures for instance, but didn't see any interest to update the stuff, at least for the time being. So, nothing I can do.

I'll check the hotspot later, see if there's something missing on my side.

It's will be always like this when comes to custom ROMs, everyone does things their way (sometimes just because) causing this kind of headaches.

That's why I don't give active support for custom ROMs, too much variables. I don't have the time or the need to do 1000 different kernel variations.

Yeah that's a weird one, I just gave up for the time being. Seems related to performance profiles and profound doze messing with the sensors when battery saver kicks in.

If anyone can help out on this, we can work on it.

Don't know why they added that stuff, on LOS for N5 (and others OP3 ROMs) there's nothing like that and all works nicely.

My "trick" will not fix anything, is just so the normal mode is set after unset battery saver. If using LOS, don't use battery saver for the time being.
[OnePlus 3 & 3T Cross Device Development] audinak2:
Thanks, wanted to know for sure. :o
[OnePlus 3 & 3T Cross Device Development] hill67:
Sorry, already searched this thread but link for kernel fails to open.

Anybody a working link?

Thanks.
[OnePlus 3 & 3T Cross Device Development] audinak2:
Downloads tab next to the discussion tab on top of this thread ;)
[OnePlus 3 & 3T Cross Device Development] eng.stk:
OK, I pushed a r59-v2-custom, hotspot should be peachy on custom ROMs now :good:
[OnePlus 3 & 3T Cross Device Development] jskasia:
[MENTION=3873953]eng.stk[/MENTION] Tried your twrp, impressive so far, boot faster that official one. However, on twrp v.16, adb sideload function did not work. Please check it out.

Thanks for the latest kernel update.
[OnePlus 3 & 3T Cross Device Development] BIGWORM:
For the life of me, I can't find the thread that has your recovery. I've been looking all over but it escapes me. Is it in the OP3 forum? Unified?
[OnePlus 3 & 3T Cross Device Development] crzykiller:
Press the download kernel zip in the OP for the OP3 and you should find the recovery under the R55 custom kernel
[OnePlus 3 & 3T Cross Device Development] BIGWORM:
Awesome! Thank you!
[OnePlus 3 & 3T Cross Device Development] anttaz:
Where is TWRP 3.0.3-x blu_spark v16 for oneplus 3T please??
[OnePlus 3 & 3T Cross Device Development] eroigaps:
http://xdaforums.com/devdb/project/?id=15934#downloads
[OnePlus 3 & 3T Cross Device Development] evanxyj:
anyone tried this custom kernel on mokee??
[OnePlus 3 & 3T Cross Device Development] osrox:
Hi,

I had earlier flashed bluespark kernel v55 using TWRP 3.0.2-1.28, on OOS based Experience ROM v11

& I did not notice any improvement in battery life.

I think, it did not got flashed properly.

So, this time, i first flashed TWRP 3.0.3x bluespark v16.

then flashed bluespark kernel v59.

But, apart from "flashed" msg from twrp,

Is there any other way on phone, to confirm, if indeed this bluespark kernel has been properly flashed ?

Edit:

Confirmed it on About page, in settings app.
[OnePlus 3 & 3T Cross Device Development] infamousvincci:
Thank you for this kernel.

DEVICE: OP3T

ROM: DIRTY UNICORN

KERNEL: BLU SPARK R59 CUSTOM
[OnePlus 3 & 3T Cross Device Development] Explorer23:
Someone literally answered this 2 posts before yours ...
[OnePlus 3 & 3T Cross Device Development] osrox:
Thanks to [MENTION=3873953]eng.stk[/MENTION]

Battery life increased from 4 hrs to more than 7 hrs, after flashing Bluespark kernel.
[OnePlus 3 & 3T Cross Device Development] infamousvincci:
Hellooo. [MENTION=3873953]eng.stk[/MENTION] do u have any idea why this qcom_rx_wakelock is showing up? I think its keeping my phone awake.

Thank you!!!!
[OnePlus 3 & 3T Cross Device Development] westenlive:
hello eng.stk

i found this in your kernel

# Update foreground and background cpusets

write /dev/cpuset/top-app/cpus 0-3

write /dev/cpuset/foreground/boost/cpus 2-3

write /dev/cpuset/foreground/cpus 0-3

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

write /dev/cpuset/system-background/cpus 0-3

I want enable ALL core in everytime.

I can set this:

on boot

# Update foreground and background cpusets

write /dev/cpuset/top-app/cpus 0-3

write /dev/cpuset/foreground/boost/cpus 0-3

write /dev/cpuset/foreground/cpus 0-3

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

write /dev/cpuset/system-background/cpus 0-3

please help me
[OnePlus 3 & 3T Cross Device Development] NickosD:
Why do you want to have all cores enabled? The battery won't last 5 hours like this.
[OnePlus 3 & 3T Cross Device Development] westenlive:
i like max performance of smartphone.

I work hard with my phone.

please help me
[OnePlus 3 & 3T Cross Device Development] westenlive:
i modify the """init.blu_spark.rc"""

but when i try flash

get this error:

"""cannot find meta-inf/com/google/android/update-binary"""

please help me
[OnePlus 3 & 3T Cross Device Development] Skinpipe:
Turn on performance governor?
[OnePlus 3 & 3T Cross Device Development] westenlive:
you try?

if set performance the cpu, the smartphone strart lags

in the kernel is the solution.

please help me
[OnePlus 3 & 3T Cross Device Development] dreinulldrei:
Yes, it needs to. Unless you don't want cellular standby. I think it's for the communication with the cell towers.