yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r159 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 v39 (recommended).

I refreshed TWRP 3.1.1-x blu_spark v39 with new kernel also, redownload and reflash.

Any other versions will not have full support for the kernel and the installer.

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

This has latest and all new f2fs 4.13 backports with lot's of fixes including GC and battery save stuff.

It's all good on our testing, but as always I recommend you to backup to PC or other external to be on the safe side.

blu_spark_r159-oos_op3-op3t_57eb2a8.zip

blu_spark_r159-custom_op3-op3t_df7508b.zip

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.

Custom build isn't compatible with EAS stuff.

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] laupuy:
Thanks :good:

I was wondering about f2fs when I read AOSPA thread

I think I have my answer :)

Have a good day
[OnePlus 3 & 3T Cross Device Development] DavisNoir:
As always, thanks for another update to your amazing kernel eng.stk!
[OnePlus 3 & 3T Cross Device Development] pratik_193:
[MENTION=3873953]eng.stk[/MENTION] bro, can u share the steps to increase the vibration strengths in op5? Oneplus reduced the vibration strengths in the latest update..
[OnePlus 3 & 3T Cross Device Development] purplepenguin:
Kernel adiutor -> misc tab if I remember right. There's a slider.
[OnePlus 3 & 3T Cross Device Development] Darkmasterhk:
Hi, based on the f2fs stuff would you recommend to keep using f2fs (especially with your patches in 159) or use ext4 instead?

Does it even have a noticeable effect? / Can I even use ext4 on/data on oos using your kernel? Thanks!
[OnePlus 3 & 3T Cross Device Development] eng.stk:
The GC issue (perf drop) happens overtime, yet doesn't manifest the same way always.

My OP3 is full stock and I never had it even when using custom stuff on it.

I never had it on OP3T until a couple days. I think the issue resides somewhere in some backports patches over time.

This latest f2fs update backport from upcoming linux 4.13 is huge, my recommendation is people to test it out what works better for them.

If you can, backup to external, format data partition in TWRP and only use r159 to get best results :fingers-crossed:

Obviously you can use any filesystem you prefer.
[OnePlus 3 & 3T Cross Device Development] corleone48:
Any hope to release your work on op5?
[OnePlus 3 & 3T Cross Device Development] marf28101995:
It will come when it's ready it's all you got for now ;)
[OnePlus 3 & 3T Cross Device Development] MoHed:
Choosing md5 checksum in TWRP

First, thanks for your excellent ROM.

I use AFV (Android File Verifier) to re-verify my nandroid backups in 1 easy step. It works with md5 hashes only.

The problem is that the blu-spark TWRP button to hash to sha2 is impossible to untick. As soon as you leave the page it gets chosen again.

How to make md5 the blu-spark TWRP default checksum ? :confused:
[OnePlus 3 & 3T Cross Device Development] amandeepsaini11:
Same happened with. I just disabled magisk modules and restarted mobile and re enabled them. And now wifi is working with latest 159.
[OnePlus 3 & 3T Cross Device Development] The.Scram:
Happened to me on every Magisk update. I just reflash my kernel (Bluespark) and WiFi is back again.
[OnePlus 3 & 3T Cross Device Development] Floydfire:
That's because you should flash the kernel after magisk, always.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
I just read some non sense and I feel that some light needs to be shed on this.

We all know that some people don't loose a chance to send some jabs towards fellow developers, most of the time with misleading talk.

Lot's of people use the said custom TWRP because, news flash: 99% of the time got better results than with the so called officials.

I worked on actually doing bringups (or at least helping out) on latest Oneplus devices since OPX. Users actually know what's better for them and lot's of them got their setups saved on doing so several times during OPX and OP3/3T TWRP life cycle (we all know how it went). At this time I think it's the only TWRP to support old crypto from 3.5.4 also for instance.

Let's not forget that were the users to ask me to share my personal recovery. I did because I saw people were in need and I could help.

I could maintain the devices if I wanted, but I prefer to do my own releases because I can manage the release window on my own (TWRP release just take too much time sometimes, because it's a big project).

Having support or not is pointless, most of the stuff come out of people don't knowing how to use TWRP and not bugs from the tool I publish.

Also, all the changes I personally do and specially the ones from TWRP team go for several review processes and when they are merged there's not really a huge danger on the 1 or 2 monthly releases. We all should stick with stock recovery, less potential bugs there :angel:

Only thing wrong is people being constantly talking about other people stuff. Specially about ones that everybody know said rant speakers constantly get stuff from.
[OnePlus 3 & 3T Cross Device Development] ps_minky16:
Mate you work is absolutely amazing.

You should ignore such people becoz you always clearly mentions what has to be done with new kernel and what twrp it requires. Some people just refuse to read op and then complaint abt things not working their ways. Just leave them and dont respond if they dont read few pages back.
[OnePlus 3 & 3T Cross Device Development] zedbg:
Your recovery is miles ahead of the official
[OnePlus 3 & 3T Cross Device Development] marf28101995:
FYI
[OnePlus 3 & 3T Cross Device Development] vatsal8286:
r160?
[OnePlus 3 & 3T Cross Device Development] Sytis:
Closed beta tease :p
[OnePlus 3 & 3T Cross Device Development] andyman_187:
soooo.....awfully quiet around here.....any news on R160?
[OnePlus 3 & 3T Cross Device Development] BIGWORM:
Is it posted, yet?
[OnePlus 3 & 3T Cross Device Development] andyman_187:
Nope, still with the testing group i think
[OnePlus 3 & 3T Cross Device Development] BIGWORM:
Well there you go. You'll definitely hear about it when eng.stk decides to release. Read the XDA rules.
[OnePlus 3 & 3T Cross Device Development] andyman_187:
I didn't ask for an ETA, I was asking about news. As in feedback and or general status update from anyone who's had the privilege of testing it.
[OnePlus 3 & 3T Cross Device Development] Renosh:
I'm sure it's got improvements but what kind of feedback are you expecting? 10hr battery life, 0 idle drain, zero heat while gaming? Just wait till it's announced ?
[OnePlus 3 & 3T Cross Device Development] Chaplan:
https://youtu.be/qFLhGq0060w?t=2m23s
[OnePlus 3 & 3T Cross Device Development] andyman_187:
Exactly, thank you!
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Are we amateurs like the guy next door? At least 20h SOT, battery will charge itself while using the device. And as a bonus, gaming will actually cool off the device (very handy to use at the beach for instance) :cyclops:
[OnePlus 3 & 3T Cross Device Development] Floydfire:
Uhm still not impressed. Will it be able to download more ram?
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Make a wish for it before flashing.

It will be magically added after you flash and reboot to Android.

The new build will bring a leprechaun with blue hat built in the installer, so all users wishes will be magically attended.:cyclops:

You will get a build bump for every wish so you know it's working.:crying:

Currently I'm on r6969 already. I have a great imagination and wish a lot, I admit that.
[OnePlus 3 & 3T Cross Device Development] Krustak:
https://downloadmoreram.com

I heard it works on phones too
[OnePlus 3 & 3T Cross Device Development] Clark K:
I just tried it, 32gb of ram added in less than a minute. :good:

AMAZING !!!
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r160 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 v39 (recommended).

Any other versions will not have full support for the kernel and the installer.

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

This has latest CVE security updates, qcacld-2.0 wifi updates, build with latest blu_naro

blu_spark_r160-oos_op3-op3t_624158f.zip

blu_spark_r160-custom_op3-op3t_642226a.zip

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.

Custom build isn't compatible with EAS stuff.

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

If you like my work, donations are always welcome.

Don't forget to hit thanks and rate the thread nicely, it's free ;)
[OnePlus 3 & 3T Cross Device Development] Astatin13:
Hi. After flash kernel do we need to use kernel auditor? And set apply at startup at kernel auditor ?
[OnePlus 3 & 3T Cross Device Development] laupuy:
Hello,

Yes probably, what do you want to settle?

:confused:

Edit: after re-reading I would say no, unless you want to change the kernel settings (default).
[OnePlus 3 & 3T Cross Device Development] Astatin13:
Thank you. I mean do we need this app for enable main kernel settings
[OnePlus 3 & 3T Cross Device Development] laupuy:
Yes, or you can choose another if you want, but this app works pretty good and recommended in OP

;)

Edit: to enable fastlane (for example): https://xdaforums.com/showpost.php?p=72208986&postcount=4717
[OnePlus 3 & 3T Cross Device Development] niwia:
Anyone flashed it with ob20?

(If not or you think this is ot don't create a mess)
[OnePlus 3 & 3T Cross Device Development] Red_Man 898:
works great ob20
[OnePlus 3 & 3T Cross Device Development] laupuy:
Hello,

yes and it's good (cf my signature) ;)

But little disappointed... by dev's promise

:p :D
[OnePlus 3 & 3T Cross Device Development] equlizer:
This is probably OT but does this phone support UVC in the kernel? I got one of those endoscopic cameras from amazon and it works great on my computer and my wifes LG G6 but not on this phone. Any ideas?
[OnePlus 3 & 3T Cross Device Development] chenrp:
Just updated on a custom rom. Works great. Thanks.
[OnePlus 3 & 3T Cross Device Development] luptatorul:
Do you recomend flashing this with 4.1.6 or with the latest beta? I am interested in battery life :). Which ROM should I go with, boiiizzz?
[OnePlus 3 & 3T Cross Device Development] kessaras:
You will discuss here which rom ? This ain't a general chat room ya know.

Best battery life was up until 4.0.3. Since then anything newer doesn't have any other negative effect to battery life. If you so much want the best battery life rollback to 4.0.3. Otherwise just live with it ! Besides this phone battery is going through a day easy even with Facebook apps
[OnePlus 3 & 3T Cross Device Development] stavca:
it works for me with CameraFi app ;)
[OnePlus 3 & 3T Cross Device Development] Sytis:
As there are no bugs like almost always I'd like to ask a question on which I probably already know the answer of but will ask nevertheless: As for PA support you said something like "No support in the near future and there probably won't be any". So now my question: As you used words that may indicate a version for PA in the far Future, are there still plans to add a version some day or is that completely abandoned now? And also: I'd like to test out PA but I don't want to miss blu_spark so could some report how the current custom version performs on the latest release of PA? Otherwise I'd happily take some recommendations to custom ROMs as I'm not really satisfied with LAOS. I think the first question is directed at development but if the rest is considered OT don't bother answering then.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
There will be no builds for PA for the reasons I already mention.

I recommend OOS. If custom is your thing, I can point the ROMs usually we test on: Carbon, Purity, OMNI. Maybe it suits you, give it a go :good:
[OnePlus 3 & 3T Cross Device Development] eng.stk:
In case you guys wonder about to check when the f2fs GC issue hits you, here's a comparae between normal high speed on blu_spark (1) and when the bug drops your RW speeds (2)
[OnePlus 3 & 3T Cross Device Development] andyman_187:
Mine even has lower write speeds @ 30mbps. What should we do to get rid of the bug? Reformat?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
While there's no definite fix for this, yes.

I'm sure eventually a fix will come, we're now closely to f2fs linux 4.13 mainline

Currently testing latest v4.13-rc2-3.18 from latest weekend.
[OnePlus 3 & 3T Cross Device Development] andyman_187:
Awesome will wait for the fix then, too lazy to reformat. I'm assuming there would be no need to reformat once a proper fix is in place?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
You probably will need to reformat anyways.

I didn't see any fix targeting this thing in particular, lot's of stuff should be merged on the Linux 4.13 window, we'll see how it goes.
[OnePlus 3 & 3T Cross Device Development] Hatshipuh:
Would it help to make a TWRP backup of data, reformat and restore or would that restore the bug too?

As I understood, it should work since only old data gets written on newly formatted fs, or am I wrong?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
[KERNEL] [blu_spark r160 unified OP3/3T] [OOS 4.1.* / custom ROMs]

Sure, you can restore your backup after format, should be good to go.
[OnePlus 3 & 3T Cross Device Development] Hatshipuh:
Thanks, I'll give it a shot as the test turned out to be only 21 MB/s...

Well that didn't work, restoring backup failed with error 255...

This will take a bit longer I guess...

New test it's up to 70 MB/s from 21, guess some improvement better than none after that ordeal.

Man I so regret doing this, now after clean flash I can't find a single Bluetooth device...
[OnePlus 3 & 3T Cross Device Development] aocboe:
No software support F2FS trim,and GC is very inefficient.So why not use EXT4?

The dynamic voltage can be adjusted by setting the upper and lower limits,can you add this function(feature)?
[OnePlus 3 & 3T Cross Device Development] andyman_187:
curious about how this bug gets triggered though? is there something in particular or does it just occur randomly as files get saved/deleted?
[OnePlus 3 & 3T Cross Device Development] arshu16:
I have even lower r/w speeds. What is the main cause for this ?
[OnePlus 3 & 3T Cross Device Development] dreinulldrei:
I understand this is not a support thread, so can someone please kindly point me where to look for a solution to the following:

OP 3T with OB10. Running blue_spark r159. Updated to OB11 (dirty flash), installed blue_spark r160. No Wifi. Tested several dirty flashes of update, also retested r159. But no Wifi. I know that this is a problem of wlan.ko not matching what's in the kernel, but don't see how this could happen when doing a complete (dirty) flash. Is there anything in the data partition that could cause this?

Again, please re-direct me where to ask, don't want to spam this thread.
[OnePlus 3 & 3T Cross Device Development] laupuy:
Hi,

Did you flash in the right way rom, root and blu_spark kernel (OOS) at last ?

Cf OP ;)
[OnePlus 3 & 3T Cross Device Development] eng.stk:
https://lwn.net/Articles/518988/

Mostly random, overtime.

GC requests becomes to pile up, derping the performance.

See my previous posts on this.

You can use whatever suits your needs. For some it's a dealbreaker, for others it isn't.

If people stopped using someting everytime a bug is found, you would be using paper and pencil still.

Give it some time, I'm sure a solution will come.

If not I'll probably revert back to 4.8 tag and merge some upstream goodies. Seems the most stable yet.

No voltage anything will be changed.

Doesn't seem you format the partition correctly to get such values.

You should go to recovery, unmount partition, format, reboot recovery and only then restore.

Your restore will be the same has your system running, there's no reason to make bluetooth stop working.
[OnePlus 3 & 3T Cross Device Development] andyman_187:
try

https://forum.hovatek.com/thread-15953.html
[OnePlus 3 & 3T Cross Device Development] chenrp:
any chance this kernel will support 2500ma charging current like dorimanx kernel does?

thanks.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
[KERNEL] [blu_spark r160 unified OP3/3T] [OOS 4.1.* / custom ROMs]

Format,reboot to recovery, copy your backup over MTP, unmount MTP, reboot to recovery again, restore backup.

Most of the errors is because people do the operations all at once and while resources became busy, you can't do the next thing.

Backup and restore works fine, this is not a TWRP support thread.

Enough of OT already.
[OnePlus 3 & 3T Cross Device Development] SynisterWolf:
Thread cleaned,

You must respect the developers wishes and stop with the off topic post.

Wolf
[OnePlus 3 & 3T Cross Device Development] Lochuan:
Thanks for your harding working

Fantastic work
[OnePlus 3 & 3T Cross Device Development] Hristos!:
Does this kernel support the spectrum app?
[OnePlus 3 & 3T Cross Device Development] Nevermindthelabel:
I believe not
[OnePlus 3 & 3T Cross Device Development] Chaplan:
From the hammerhead blu_spark kernel thread:

So no, expect no support for the said app.
[OnePlus 3 & 3T Cross Device Development] andrea.ippo:
Hi, could this be kernel related? Running 4.1.6 on my OP3 with Magisk and blue spark r160.

Thanks!

poll() has timed out for /sys/module/msm_performance/events/cpu_hotplug

https://photos.app.goo.gl/WDhxsdOxbC4uT1VH3
[OnePlus 3 & 3T Cross Device Development] eng.stk:
You have somethingb from userspace polling that sysfs and giving that warning.
[OnePlus 3 & 3T Cross Device Development] Hristos!:
Ooh ok, thank you sir.
[OnePlus 3 & 3T Cross Device Development] cpt.macp:
Do kernel need to have Hal blobs for camera to work .

Hal3 I mean.

Because I remember hal3.enable use to work in 7.1 .

But if you use 6.0 it doesn't work.

Camera2 apk crashes
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Nothing to do with kernel.
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Beta testing latest F2FS :good:

AndroBench made under the usual settings.

Encrypted, Fsync always ON, nothing changed to improve benchmark scores. The usual business.

We don't like placebo or erroneous reports.

You all already now the drill.
[OnePlus 3 & 3T Cross Device Development] Kiranb212:
good news.. looking forward for official release :svetius:
[OnePlus 3 & 3T Cross Device Development] Yusei:
r160 ext4

Best kernel by far.
[OnePlus 3 & 3T Cross Device Development] seenahermes:
What app is that?
[OnePlus 3 & 3T Cross Device Development] cha0zine:
Check the screenshot again. On the top right. Androbench.
[OnePlus 3 & 3T Cross Device Development] agrageraldis:
f2fs.

pictures speak louder than words ;)
[OnePlus 3 & 3T Cross Device Development] The.Scram:
Not so great here

Bluespark 160, f2fs
[OnePlus 3 & 3T Cross Device Development] andyman_187:
Mine improved somewhat after doing some steps:

Copy a large single file to your device which would take up the remainder of your storage space. Mine had about 6gb left so I copied a 6gb video file into my internal storage. There was still about 100mb available so i started taking a 4k video until no storage space was left. After a few minutes, delete the large files you copied, then wait for a few minutes and try the benchmark again. According to arter97 who advised me to do this, this forces garbage collection to kick in, but only fixes the issue temporarily until a proper f2fs fix is implemented
[OnePlus 3 & 3T Cross Device Development] atiqul:
i have an issue. i cannot configure i/o sceduler with the latest version of the kernel. using unofficial rr by eliminator
[OnePlus 3 & 3T Cross Device Development] BIGWORM:
No support here as RR is LOS and OP strictly only gives support for Stable OOS.
[OnePlus 3 & 3T Cross Device Development] Alahoy27:
Wow. The DCI P3 works!
[OnePlus 3 & 3T Cross Device Development] jocaboss:
Works how?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Yeah that could work, using all the space left will reset GC (not making it kick in).

For those interested in testing, can try in twrp terminal (on twrp terminal should make better results, on android there's min free space protection, can't get full data partition):

dd if=/dev/zero of=/sdcard/zero

You can check the space of data (or dm-0 if encrypted) with:

df -h

Then delete the file zero on sdcard root to get space back, before reboot.
[OnePlus 3 & 3T Cross Device Development] Alahoy27:
I flashed this kernel and have the 3T switcher installed and you can see the difference once you enable the DCI P3.
[OnePlus 3 & 3T Cross Device Development] amirarsyad97:
I have been experiencing bug on system services where almost all of app memory are allocated as system memory (pic). I've tried dirty flashed stock rom and enabling magisk core only mode, but the result is still the same. However, when I returned to stock kernel, the bug disappeared. :eek: The functionality of the kernel and the usage of the app is not affected though. Any idea why this happened? Is is just how the memory allocation on this kernel works? I'm still new to this kernel so any help is appreciated.

OOS 4.1.6, blu_spark r160 with default settings, magisk 13.3.
[OnePlus 3 & 3T Cross Device Development] arshu16:
I tried this and it doubled my sequential write speeds. From 21 Mb/s to 40 Mb/s but still quite low from what i am seeing here. Hope we find a permanent solution to clear those GC requests.

Will changing to ext4 make a lot of difference? I don't want to do it unless it will.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
There's nothing on kernel to do that.

You can try running a couple more times.

We tried that today immediatly after the bug kicked in, got the normal speed operation back. Other than that, maybe in your case it's so far off only formating can cut it.
[OnePlus 3 & 3T Cross Device Development] arshu16:
How much time would you say this issue will take to recur after formatting?
[OnePlus 3 & 3T Cross Device Development] laupuy:
Hi, [MENTION=3873953]eng.stk[/MENTION] thanks for the tip :svetius:

Before (screen 1)

After 1 zero file (2)

After x zero files (until sdcard full) (3+4)

For info, zero file seems to be 3.7GB (5)

/data f2fs of course

Edit

F2FS GC issue solved

Ok my bad, tried another test and just wait 475sec for 31GB and it's ok

TWRP terminal

dd if=/dev/zero of=/sdard/zero

Wait 475sec for 31GB

df - h

To control

Delete zero file on /sdcard

Reboot

Thanks [MENTION=3873953]eng.stk[/MENTION] [MENTION=774530]Chaplan[/MENTION]
[OnePlus 3 & 3T Cross Device Development] beta990:
Thanks again for your hard work, kernel works fine here. :)

Question: is NFS4 supported by the kernel? I'm trying to mount, but it keeps complaining about missing `/etc/fstab` - but I think this is an issue elsewhere - but if you can confirm it works, I'm happy to find out why this doesn't work. :)