yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Giocarro:
Yep, after a few hours of usage I can confirm r137 feels the smoothest experience ever!

Kudos [MENTION=3873953]eng.stk[/MENTION]! ^__^
[OnePlus 3 & 3T Cross Device Development] XeloOw:
BlueSpark on latest Freedom OS community Build 3.5.4

So good
[OnePlus 3 & 3T Cross Device Development] LELBOT:
theme name pl0x :p
[OnePlus 3 & 3T Cross Device Development] basvanasperdt:
+1

Very smooth indeed!

Will report later on how battery life is with this combination
[OnePlus 3 & 3T Cross Device Development] habylab:
I just achieved 5 and a half hours of SoT. No screenshots, but I'm not lying!
[OnePlus 3 & 3T Cross Device Development] House_Maniac:
Just flashed it too so far so good :D Could the developer add the option to increase the sound in the kernel please?
[OnePlus 3 & 3T Cross Device Development] immi803:
Do you really feel sound increase needed? :eek:
[OnePlus 3 & 3T Cross Device Development] Flasher8:
Any1 using Blu spark kernel with tweak governor profile?
[OnePlus 3 & 3T Cross Device Development] immi803:
Felt no need to tweak spark default settings, really amusing settings to use as it is ;)
[OnePlus 3 & 3T Cross Device Development] XeloOw:
I'm on 3.5.4 (Freedom OS CE) and I just changed my CPU Governor to Interactive, because I noticed some scrolling lags in some applications

So now everything flies !
[OnePlus 3 & 3T Cross Device Development] Crash:
Running fine here thanks for your hard work

Hugs
[OnePlus 3 & 3T Cross Device Development] Crash:
By the way pretty amazing deep sleep
[OnePlus 3 & 3T Cross Device Development] habylab:
I'm using FairPark profile, have a search of XDA if you don't know it, and I'm getting 6 hours SoT. Without, 4, maybe.
[OnePlus 3 & 3T Cross Device Development] evertking:
Is it compatible with drive droid yet?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
WIP

edit: Seems there's a beta with support http://softwarebakery.com/apps/drivedroid/versions.html
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_sp★rk r56

All right crew!

New builds are up. Wicked!

There's also a beta build for custom ROMs aka non-OOS build.

Keep in mind: I will give no active support for custom ROMs. I am only interested on debugging stuff in OOS.

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, it's free ;)
[OnePlus 3 & 3T Cross Device Development] JumboMan:
[MENTION=3873953]eng.stk[/MENTION], I'm following this kernel since it's available for OP3.

First build for kernel is r30 second r34,third r41 and now fourth build as r56.

Here i want to ask that whether I'm missing bulids in between two releases or these are for testing purposes which you have not uploaded for public or its just a naming pattern.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
All my kernels are named like that, named after the build number.

On the first builds, numbers jump more because I test more
[OnePlus 3 & 3T Cross Device Development] JumboMan:
Thank you for reply and clarification
[OnePlus 3 & 3T Cross Device Development] ctakah27:
How do I flash the update? Just flash it over existing (r48)?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Yep
[OnePlus 3 & 3T Cross Device Development] banjaminicc:
Is f2fs supported?
[OnePlus 3 & 3T Cross Device Development] ctakah27:
If you want to use F2FS, do the following (backup your data to external source before attempt this, it will erase all your sdcard data)

Flash latest TWRP and flash latest blu_sp★rk zip

Go to Wipe -> Advanced Wipe -> Select only Data -> Repair/Format File system -> Change partition type to F2FS

Go to Wipe -> Advanced Wipe -> Select only Cache -> Repair/Format File system -> Change partition type to F2FS

Reboot and profit
[OnePlus 3 & 3T Cross Device Development] banjaminicc:
thanks you!! The oneplus three i ordered will be arriving soon..yay!
[OnePlus 3 & 3T Cross Device Development] kwkw480:
Does this kernel work on cm13 base aka RR Rom

.?
[OnePlus 3 & 3T Cross Device Development] ctakah27:
Yep. Running it - but can't say I see any difference from the original cm kernel. It scores lower in benchmarks, but someone else said games are smoother.

If you're flashing, dirty re-flash the rom beforehand though
[OnePlus 3 & 3T Cross Device Development] kwkw480:
Thank you, Friend.
[OnePlus 3 & 3T Cross Device Development] nadejo:
In meanwhile cm kernel is faster i siad its smoother in gaming because back then cm kernel was slower. But arter kernel is on its way :D
[OnePlus 3 & 3T Cross Device Development] cloudx720:
Arter really is coming to oneplus 3? That guy was my hero with my S3 days :D
[OnePlus 3 & 3T Cross Device Development] nadejo:
Type arter97 twitter in google he is using already his own kernel on op3 im hyped as f....
[OnePlus 3 & 3T Cross Device Development] cloudx720:
Once oos release dash code it will be perfect day :D
[OnePlus 3 & 3T Cross Device Development] eng.stk:
How's is this of any relevance for blu_spark development?

Go hype somewhere else and stay on topic...
[OnePlus 3 & 3T Cross Device Development] cloudx720:
Sorry :/
[OnePlus 3 & 3T Cross Device Development] Lither:
You just applied the profile and that's it with no other changes? As I heard FairPark has a bit of lag like when scrolling etc, are you experiencing any of that?
[OnePlus 3 & 3T Cross Device Development] Funk Wizard:
I am not sure if we can apply a profile with Kernel Adiutor may be manually set or use a different app
[OnePlus 3 & 3T Cross Device Development] habylab:
Slight lag, but worth it for the battery!
[OnePlus 3 & 3T Cross Device Development] ram4ufriends:
Do you see any performance/battery improvements using f2fs against the traditional?
[OnePlus 3 & 3T Cross Device Development] ungeeked:
Haven't tried blu_spark on ext4 and f2fs. But blu_spark + f2fs is definitely smoother than stock
[OnePlus 3 & 3T Cross Device Development] Konskl:
[MENTION=3873953]eng.stk[/MENTION] the r137 is really the smoothest build I've used so far in combination with the 3.5.4 CB. One thing in my opinion that could be improved is the heat. I think that the blu governor is a bit too aggressive in ramping up the cpu and that results in excessive heat. I think that has to do with the governor tunables which unfortunately I'm a bit reluctant to touch. I tried to disable touchboost but doing that resulted in choppiness where it didn't exist before. Would you be able to check that in the incoming builds? Ty in advance.
[OnePlus 3 & 3T Cross Device Development] owaisnaim:
Hats off.!

#r137

CB 3.5.4
[OnePlus 3 & 3T Cross Device Development] immi803:
[MENTION=3873953]eng.stk[/MENTION]

It's not any cm rom related, just off kernel thread rules in op :p

Is current custom build 137 tested on noughat? Anyone

Should it boot?
[OnePlus 3 & 3T Cross Device Development] lxxs:
Is anyone having problems with Dash Charging not working in r137? (FreedomOS CB 3.5.4 here)
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Get it working is different from full support, but well taken nevertheless lol

Try it an d let us know.

There's no excessive heat on this device, it's the coolest I ever used so it's fine.

DASH works in every ROM that supports DASH.

Works fine in OOS 3.5.4 CB
[OnePlus 3 & 3T Cross Device Development] lxxs:
Started to work again, strange, CB things I guess :p

Thank you sir for this amazing kernel! I really appreciate your work.
[OnePlus 3 & 3T Cross Device Development] samisharora:
[MENTION=3873953]eng.stk[/MENTION] - Arter just updated its kernel for CM13 with following improvements -

New build.

1.5

ARM64 erratum fixes disabled to improve performance

Updated to Linux 3.18.43

Dozens of Google Pixel kernel commits merged to improve performance, smoothness and latency

CFQ upstreamed to Linux 4.9

BFQ disabled

Dirty COW vulnerability fixed

Do you see the bold update - improvements from Google pixel kernel commits can be included in the OOS version of blu_sp★rk.
[OnePlus 3 & 3T Cross Device Development] angdaminaman:
i love this kernel.

but sorry for being noob.

im now at 3.5.4, and want this kernel.

how can i install it without data loss?

instruction says it needs 3.2.7 firmware.

im quite confused with the instruction.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
That's old, just flash r137
[OnePlus 3 & 3T Cross Device Development] angdaminaman:
o' hail the official answer.

so i could just dirty flash it using your twrp-3.0.2-22-oneplus3.img?

thanks sir.
[OnePlus 3 & 3T Cross Device Development] angdaminaman:
update:

i nearly had a heart attack because of excitement, it booted after dirty flashing the 137 custom kernel.

but the wifi is not working. so i dirty flashed 3.5.4 again using latest twrp from eng.stk

am i doing something wrong? or i need a little backread because it was already answered?

thanks
[OnePlus 3 & 3T Cross Device Development] ungeeked:
If you flash ROM after Kernel, probably the stock kernel would replace blu_spark.

This is why you should ROM > Other stuff (SuperSU etc) and then blu_spark..
[OnePlus 3 & 3T Cross Device Development] angdaminaman:
thats exactly what i did sir:

clean flash cb 3.5.4 > supersu > (then using latest twrp from eng.stk) blu_spark_r137-custom_thulium_7304945.zip

i believe i should use the custom.

i just reflashed original cb 3.5.4 so i could use wifi again.
[OnePlus 3 & 3T Cross Device Development] ungeeked:
Wait for someone actually running CB to reply. I think custom version is for CM and Community build is still OOS based. Still, confirm before flashing.

Or you could search older posts
[OnePlus 3 & 3T Cross Device Development] ram4ufriends:
I installed freedom os 1.9 -> blu_spark_r137-OOS_thulium_72a5ef2....and all works fine
[OnePlus 3 & 3T Cross Device Development] angdaminaman:
i ask apology to the author for not reading well.

yes, i just flashed the oos 137 kernel zip and it actually works.

yes, thank you.

i believe this said it well:

thank you.
[OnePlus 3 & 3T Cross Device Development] Chris.nl:
:victory:

[IMG="baby seal"]http://1chris.nl/OP3/rsz_920x920.jpg[/IMG]
[OnePlus 3 & 3T Cross Device Development] Mar-cel:
Why shows your recovery 3.0.2.1 if I boot in to it?
[OnePlus 3 & 3T Cross Device Development] nmlssit:
Because probably eng.stk just modded it without touching the original version Number, that's what i said to myself after flashing it 3 times because it kept saying 3.0.2-1 instead of -22.
[OnePlus 3 & 3T Cross Device Development] Explorer23:
That is correct, all modified recoveries (-19, - 20, - 21, - 22, - 50) have always been showing the same version number as the official that they're based on - 3.0.2-1.
[OnePlus 3 & 3T Cross Device Development] epypro:
what about antutu with 137 build? (cb rom) For those who dont care about Antutu just ignore this, please.

Did the phone restarts after open Antutu? what score do u get? last time i tried i get arroud 126k, instead 150k with stock kernel. It seem to be the cpu score, it was lower with 136 kernel build.
[OnePlus 3 & 3T Cross Device Development] Tn_wijaya:
I am having similar situation, my phone turn off on booting to recovery after flashing over official twrp over modified twrp 3.0.2.22. I tried flashing using either twrp and fastboot but the result is the same. The phone backed to normal after re-flash the modified rom.

Is your procedure will be apply to my situation? Kindly hope your advice.
[OnePlus 3 & 3T Cross Device Development] ungeeked:
First command deletes stock recovery

2nd flashes twrp

After flashing twrp in fastboot, long press power button to reboot and go to recovery from bootloader warning screen.

Swipe to allow for modifications when twrp asks.

Reboot to system from within twrp

Also pm me or post the query in Q/A thread and tag me. Keep this thread clean because too many OT posts really make it difficult for anyone using the search function
[OnePlus 3 & 3T Cross Device Development] Funk Wizard:
I am running CB with r137 wifi and VoLTE both work fine

You might want to check the r137 version if it brakes your WiFi

The kernel version should correspond to the firmware version or if it still brakes the WiFi try flashing the 3.5.4 firmware modem combo again provided you've used the corresponding r137.

Its been like that since 3.0.2-19 all versions mentioned the same build no as all changes were made under the hood.
[MENTION=3873953]eng.stk[/MENTION] How about adding a blu spark logo like it used to happen with Onyx twrp builds, we would welcome that.

---------- Post added at 08:13 AM ---------- Previous post was at 08:07 AM ----------

Please be advised that the CB is not compatible with the official twrp that is why it gives you a black screen and that is why there was a need to build the modified versions. If you wish to change the rom or flash the official twrp I suggest you flash the official 3.2.6/3.2.7 firmware and then flash the official twrp or any other ROMs apart from CBs

Question: Why is there a need to switch to the official when 3.0.2-22 works fine for all builds?

---------- Post added at 08:18 AM ---------- Previous post was at 08:13 AM ----------

These is no need for this.

For everyone out there I'll keep it simple... Either remain on 3.0.2-22 or flash the firmware before you revert to the official or try to switch to a different rom from CBs
[OnePlus 3 & 3T Cross Device Development] eng.stk:
I don't touch the binaries, just ramdisk and kernel changes so it will appear like that.

I will not build or be a twrp maintainer like in OPX, so it will stay like it is.

It's just a number :silly:

It's rather easy to check the version, just type in TWRP terminal:

uname -a

should show blu_spark running :)
[OnePlus 3 & 3T Cross Device Development] Funk Wizard:
Thank you for the explanation :o Appreciate your contribution.
[OnePlus 3 & 3T Cross Device Development] Tn_wijaya:
I am switching to a different rom but I did not realize that 3.0.2-22 works well on others.

Thank you for your kind help.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_sp★rk r141

All right crew!

New build is up. Wicked... smooth!

This features a couple performance patches and wifi stack from Pixel, dirty COW fix and some more misc fixes/improvements.

For each " my wifi doesn't work", "my screen is black", "my phone doesn't boot", "snapchat doesn't' work on CB 3.5.4", a baby panda dies.

So read the damn thread and check what file you're flashing before posting noobness.

Keep in mind: I will give no active support for custom ROMs or CB. I am only interested on debugging stuff in stable OOS.

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, it's free ;)
[OnePlus 3 & 3T Cross Device Development] ZeppeMan:
No baby panda's were killed during the proces :good::D

Keep it up!
[OnePlus 3 & 3T Cross Device Development] NickosD:
Because I am not using cb, if anyone can try the latest version and can see if snapchat works.

Thx ☺️
[OnePlus 3 & 3T Cross Device Development] cookie1953:
I'm running CB3.5.4 with blu_sp*rk r141, wifi working, all looking good at this time....
[OnePlus 3 & 3T Cross Device Development] phil_greg2001:
+1

:cowboy:
[OnePlus 3 & 3T Cross Device Development] basvanasperdt:
Works beautifully smooth! r141 with FoS 1.9 (CB 3.5.4), no problems with flashing, confirm wifi working and everything.

I keep coming back to your kernel, best experience with smoothness and battery life. Keep up the good work!
[OnePlus 3 & 3T Cross Device Development] lil11b:
Well I use the cb 3.5.4 and bluspark and OFFICIAL twrp since otg does not work properly in my recovery when I use the modified version. Therefore using the official makes things a lot easier for me.

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] abuddlah:
Anyone on CB 3.5.4 can please help to check if Snapchat is working fine? Like it won't force close? Please!
[OnePlus 3 & 3T Cross Device Development] lil11b:
Snapchat still not working properly.

Btw Freedom OS 1.9.1 and Blu spark 141 oos flashed on official twrp is working without any problems

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] abuddlah:
oh well :( thank you anyway! :)
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Go ask OnePlus for CB 3.5.4 sources.

Enough of snapchat spam posts already.
[OnePlus 3 & 3T Cross Device Development] NickosD:
I didn't knew that I can't ask if it's working.

Till next update.
[OnePlus 3 & 3T Cross Device Development] myfluxi:
You have to ship the wifi config as well, else fun/2.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
No, I will never touch ROM config/files.

Driver is performing as any other CAF version, I just wanted to have same baseline as Pixel, so future google security monthly updates apply cleanly, nothing more.

You can post your changes for people that want to have fun :)
[OnePlus 3 & 3T Cross Device Development] myfluxi:
Kernel changes are tied to userspace changes, there is no way around it.
[OnePlus 3 & 3T Cross Device Development] abuddlah:
it is not spam, it is a legit question.
[OnePlus 3 & 3T Cross Device Development] SREEPRAJAY:
Can we end the snapchat here Sir?

Although I agree that it is not spam....can I suggest to open a Gen thread dedicated to Snapchat.

This developer does not develop snapchat and all he ask you is to reach the right place to report this.

and please...it is not pointed at you...it is applicable to all

Please guys.... dont flood a Dev section thread with an app related issue (i know it is related to the new OS OTA but still it is related to the app-ROM.

Plz report to the oneplus.net teams as well create a GEN section thread.

Thanks a lot
[OnePlus 3 & 3T Cross Device Development] owaisnaim:
What's legit in it, oneplus haven't released CB 3.5.4 sources and the kernel we are running on it is a big hack, and eng.stk clearly mentioned that he will not support any questions regarding snapchat, so better wait for the sources.

Peace ✌
[OnePlus 3 & 3T Cross Device Development] ungeeked:
I think I'm going to get an award or something soon for saving baby seals and pandas :p :angel: :victory:
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Sure, but I'm not after different or more functionality, with no changes to config or fw the 4.4.25.26 driver performs similar to 4.4.31.76

If in the future Google changes make userspace changes mandatory (like those Google did in a point in time with the N5 bin fw) I will deal with that then.

If this is the case, OnePlus probably will do it also in future updates, so for me it's good as it is.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Wait for the dolphins, we'll try to save them all :silly:
[OnePlus 3 & 3T Cross Device Development] epypro:
why my Cache partition is always 0mb? is it not in use? its normal?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Always 0mb where? Let me guess, TWRP backup screen?

There's nothing on it those days in that partition, if you enter /cache you will see some empty folders and a couple recovery files/logs that are less than 1mb (why < than 1mb shows 0mb)
[OnePlus 3 & 3T Cross Device Development] epypro:
yeah, in that screen, but in the "wipe" section too. Cache is 0mb... ok. correctme if im worng, couse i dont know much about this, but theres no cache files generated by the use of my apps?

when i say Files, i mean more than 1mb, i have seen that partition with 50+ mb, and my apps where the same as today
[OnePlus 3 & 3T Cross Device Development] eng.stk:
No, app cache is not in the cache partition.

That partition was used back in the day when downloading OTA and other OS update stuff I think, but even that is downloaded to the sdcard in our device and TWRP uses the /tmp to deal with temporary files.

If you use f2fs that partition will have a couple used MB, but that's because of the logging and database from filesystem itself, the files and folders will be that few, just the same.
[OnePlus 3 & 3T Cross Device Development] ungeeked:
It is non zero for me but some difference.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
See above ^^^
[OnePlus 3 & 3T Cross Device Development] ungeeked:
Thanks. Best dev ever!
[OnePlus 3 & 3T Cross Device Development] immi803:
Non zero for me too
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Sure because you're using f2fs, like I said on the explanation

No need to confirm the confirmation :silly:
[OnePlus 3 & 3T Cross Device Development] immi803:
Overwhelmed by r141, fantastic job mate [MENTION=3873953]eng.stk[/MENTION]

You rock :laugh::good:
[OnePlus 3 & 3T Cross Device Development] nmlssit:
[MENTION=600147]THE[/MENTION] people reporting it: CB and custom kernel working with official twrp? How come?

Can we get rid of modified twrp with 141 or do i miss something?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Well I don't really do support for TWRP, bit OTG works fine in 3.0.2-22 twrp from this thread

They probably had he 3.2.7 fw on the device.

You can just flash 3.5.4 and twrp 3.0.2-22 and forget about all of that.

If you still want to use a broken recovery and hack around there's threads for that.

I'm a bit tired of this thread full of recovery and ROM talk to be honest.

Let's keep on topic.
[OnePlus 3 & 3T Cross Device Development] nmlssit:
Oh, right, i forgot about that lol
[OnePlus 3 & 3T Cross Device Development] Funk Wizard:
[MENTION=3873953]eng.stk[/MENTION] : Dirty flashed the latest r141 and all good :)
[OnePlus 3 & 3T Cross Device Development] eng.stk:
I'm very happy with r141, it's so smooth I'm afraid the phone will slip from my hands lol
[OnePlus 3 & 3T Cross Device Development] dwang:
I use the bleacher report app and that has always been laggy.

With r141 that lag is mostly gone.

Great job.
[OnePlus 3 & 3T Cross Device Development] NOSTALGIA:
pls stop releasing new builds. your making me more flashaholic. :p
[OnePlus 3 & 3T Cross Device Development] juginkrebs:
r141 Runing Very Very Very Smoooooth Great Job Bro and Keep up the Work ??

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] Flasher8:
May I ask, do you use any profile tweaking?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
The only profile I use is the default.
[OnePlus 3 & 3T Cross Device Development] xanthrax:
And of course, no baby goose died ever since, right? [emoji12]

Sent from my Darkside of Oneplus 3
[OnePlus 3 & 3T Cross Device Development] LKspro:
i have tried all official roms and they all have the thermal throttling issue when gaming. After flashing this kernel, with cpu throttling temp set to 70, the problem still exists, is this something set by oneplus and cannot be changed? The only rom that does not throttle is miui8, even during charging.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Thermal throttle is a protection mechanism present is all devices to protect the phone components, not an issue or a problem.

Throttle is set by userspace deamons, changing that values on kernel apps makes nothing.

The kernel driver is only for ROMs that use a kernel with custom thermal driver and have no userspace thermal control (like sultan CM for instance).
[OnePlus 3 & 3T Cross Device Development] LKspro:
i know that there is a performance mode in some roms which allows the phone to run at full speed no matter what temperature, such as the old miui5-7 roms, so does this mean that they have unlocked the protection mechanism?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
I don't know, maybe they don't even run any thermal protection, who knows.

You need to search on ROM threads.
[OnePlus 3 & 3T Cross Device Development] dreinulldrei:
I tried the kernel today on CB 3.5.4 and wanted CF.lumen to use a KCAL driver or similar. For some reason unknown to me, CF.lumen did not show sRGB or KCAL as an option for drivers.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Use Kernel Adiutor, kcal shows and works just fine.