yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r111 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.0-x blu_spark v26 (recommended). Any other version will not have full support for the kernel and the installer.

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

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

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

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

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

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

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

Don't forget to hit thanks and rate the thread nicely, it's free ;)
[OnePlus 3 & 3T Cross Device Development] andrea.ippo:
Hi,

what's the difference between r106 and r111 to flag r111 as "beta" and r106 as stable in your OP?

Thanks :)
[OnePlus 3 & 3T Cross Device Development] marf28101995:
Check it yourself

https://github.com/engstk/op3t/commits/blu_spark
[OnePlus 3 & 3T Cross Device Development] Giocarro:
I always find funny when someone answers to a request for explanation pointing to a github repository.

I mean: do you really think that the average user will read that stuff?

Is it meant to be an helpful answer or a joking one?
[OnePlus 3 & 3T Cross Device Development] andrea.ippo:
Thanks, but my question was not about the diff between the two versions, but rather about what qualifies r111 as a "beta" whereas the r106 is considered a "stable"
[OnePlus 3 & 3T Cross Device Development] eng.stk:
CAF tag is recent and sdcardfs in AOSP is WIP for instance.

So I'm testing that stuff and others. For the average user don't worry, is just a name.

Also from now on, I will only tag stable when I'm happy with the testing and/or OnePlus pushes source updates.
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Chance the What for Who.

If the OP qualified it as BETA it's BETA.

It's quite stable, but everyone gets the perks for being a beta tester for a day. :cyclops:

There's GitHub, the release was made available with a changelog to.

And that's not something new on this thread.

Don't really see what this question is all about.
[OnePlus 3 & 3T Cross Device Development] vatsal8286:
so it can be flashed over r106?
[OnePlus 3 & 3T Cross Device Development] marf28101995:
Glad you like my "funny" answers stay here for next one

No problem mate, I used and use all the betas of blu_spark and even the betas are more stable than others kernels in stable stable versions because our dev actually knows what he is doing unlike.... Blu_powa!

---------- Post added at 02:54 PM ---------- Previous post was at 02:53 PM ----------

Yes if it wasn't op would state it mate
[OnePlus 3 & 3T Cross Device Development] andrea.ippo:
Thanks!
[OnePlus 3 & 3T Cross Device Development] Dieppy:
r111 seems smoother than previous version, wow!
[OnePlus 3 & 3T Cross Device Development] knpk13:
Doesn't this fix the sdcardfs issue?

https://github.com/andip71/boeffla-...mmit/ad270da4ddf9a24b1fb1150e63d56711b2dd944b
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Lineage code is "old", so no.

Let's say on this matter, anything most people merge today I probably already tested 4 weeks ago lol

We have userspace dependencies on the delete files issue, so kernel fixes alone probably won't cut it.

Don't know if in the meanwhile Lineage pushed anything on the ROM side to tackle this, but from the tests people did in several ROMs the issue persisted.

edit: I even been working with Samsung S source ports (which is very different from AOSP) to no avail.
[OnePlus 3 & 3T Cross Device Development] knpk13:
Huh, I thought it was a problem only on OOS.

Oh. Then does that mean this doesn't fix the issue as claimed in this post?

https://xdaforums.com/oneplus-3t/development/kernel-boeffla-kernel-xx-12-2016-t3520455/post71942761
[OnePlus 3 & 3T Cross Device Development] Vixiebalistic:
Blazing fast n smoooth..... Again great work from the master
[OnePlus 3 & 3T Cross Device Development] eng.stk:
I discovered yet another sdcardfs nasty bug (present on r111).

If you rename a folder with a 3rd party file manager other than OnePlus one, it will hang and reboot your device.

The folder will be renamed after rebooting, but all the content is lost :eek:

This is because of a upstream commit, I already found it and will push a quick fix later.

I'll add a couple new commits pushed this afternoon while I'm at it.

Of course this only happens if you're using sdcardfs :silly:

Neverthless is curious to find that ye again, the shipped file manager behaves ok it seems.
[OnePlus 3 & 3T Cross Device Development] jocaboss:
Did you removed r111 from download page?
[OnePlus 3 & 3T Cross Device Development] marf28101995:
You know the answer why are you asking lol

Another useless post
[OnePlus 3 & 3T Cross Device Development] Xennet:
Not happening with es file explorer

Working fine OOS 4.1.3 stock with the wonderful sparky r111

Or is it because I use your magisk sdcard module

Again you score sparky

Sparkling everywhere
[OnePlus 3 & 3T Cross Device Development] marf28101995:
It's because you use the SD card magisk module ;)
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r112 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.0-x blu_spark v26 (recommended). Any other version will not have full support for the kernel and the installer.

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

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

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

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

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

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

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

Don't forget to hit thanks and rate the thread nicely, it's free ;)
[OnePlus 3 & 3T Cross Device Development] Chaplan:
I wonder who else is using the module, and placeboing about storage and SDcardfs related stuff.

If somebody points at me I'll just say: Noooooooo, not me.

Or have I? Hum...:confused:

A bit private, Sorry.

On the new release. Smoothies are on the house.

And they are the smoothiest ever!

I'm afraid of fastlane these days. Afraid to drop the phone because off all the butter...

But I enable it anyway. :good:
[OnePlus 3 & 3T Cross Device Development] anttaz:
[MENTION=3873953]eng.stk[/MENTION] thanks for all the updates and big moves forward today for our device. Such a dedicated Dev. Respect to you :good:
[OnePlus 3 & 3T Cross Device Development] GamaX320:
should i disable touch boost for more battery life?
[OnePlus 3 & 3T Cross Device Development] saberzaid:
First time install this kernel looks good
[OnePlus 3 & 3T Cross Device Development] DesertVelo:
The recovery images are in the same download area as the kernels. Look further down the list for the files with .img file extension https://xdaforums.com/devdb/project/?id=15934#downloads.

Sent from the singletrack...
[OnePlus 3 & 3T Cross Device Development] zulnawae:
can i use this kernal with oxygen Open Beta 5 ?
[OnePlus 3 & 3T Cross Device Development] eroigaps:
Yes
[OnePlus 3 & 3T Cross Device Development] zulnawae:
Thank you :D
[OnePlus 3 & 3T Cross Device Development] vampire36:
Hardly would make a difference...
[OnePlus 3 & 3T Cross Device Development] PhilPan:
So when I went to flash this on official RR, my screen just went black and wouldn't boot?

I have the Twrp Blue spark flashed as well.

Did I do something wrong
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Only 2 things.

Asking for support on an unsupported setup.

Not using the search button, your symptoms have been discussed again and again here.

Search and profit!:confused:
[OnePlus 3 & 3T Cross Device Development] laupuy:
Hi,

did you flash "custom" version?
[OnePlus 3 & 3T Cross Device Development] PhilPan:
No just regular
[OnePlus 3 & 3T Cross Device Development] Konskl:
So you got your answer. Custom kernel for custom roms. OOS kernel for oxygen based roms.
[OnePlus 3 & 3T Cross Device Development] PhilPan:
Thanks man..
[OnePlus 3 & 3T Cross Device Development] crzykiller:
It's almost as if this guy cant make the logical conclusion that the kernel with "OOS" is for OOS ROMs and the "custom" one is for custom ROMs...
[OnePlus 3 & 3T Cross Device Development] Rebel7022:
So why does he always say this is for oos only but he has a custom kernel zip? Why doesn't dev show lineage based roms some luv?
[OnePlus 3 & 3T Cross Device Development] Explorer23:
Noone ever said the kernel is for OOS only. Kernel is often made for both OOS and custom (Lineage etc.).

But the support is there for OOS only because there are just way too many variables with custom ROMs. So you have a kernel for custom ROMs if you want it, but if something goes wrong you're on your own.
[OnePlus 3 & 3T Cross Device Development] Sytis:
He doesn't say it is for OOS only. He says that he only supports (giving help and debugging stuff) OOS which is something completely different. By providing a custom ROM kernel zip he shows lineage enough love don't you think? Btw., using it on latest lineage with no problem whatsoever.
[OnePlus 3 & 3T Cross Device Development] Chabola:
Really?!! Because ppl pester him for custom kernels since they can't live without the bluespark awesomeness and he goes out of his way to make it like the nice guy he is. Then you guys spam thread that it doesn't work because multiple reasons not related to kernel. The Dev himself is on stock oos and im pretty sure he has real life situations and can't be flashing every custom rom for his kernel to work hence it's unsupported.
[OnePlus 3 & 3T Cross Device Development] Rebel7022:
Ok thanks. So should I use this kernel on RR varun version?:cyclops:
[OnePlus 3 & 3T Cross Device Development] Chabola:
You can Try but if it doesn't work you know what you shouldn't do...
[OnePlus 3 & 3T Cross Device Development] Rebel7022:
I want to try but kernels kinda confuse me, after I install I can never tell a difference, is there anything I should look out for in a good kernel? Since its not ok to submit bug reports for custom im gonna flash it still ! :fingers-crossed:
[OnePlus 3 & 3T Cross Device Development] Sytis:
First of all check under your phone info if the kernel is present. You should get some faster app opening times and with fastlane improved cpu scaling which results for example in less scrolling lag. Also check Kernel Adiutor to adjust some values. The Battery life is also a bit better for me. Overall a lot of little pluses that add up to a great stable all day kernel.
[OnePlus 3 & 3T Cross Device Development] Djulio91:
What settings do you recommend? Thanks in advance
[OnePlus 3 & 3T Cross Device Development] Dieppy:
Stock settings are awesome
[OnePlus 3 & 3T Cross Device Development] Rebel7022:
What rom you using oos or custom? We can communicate about custom but we can't ask dev to trouble shoot cause he ain't got Time to find out what rom your using stuff like that:highfive:
[OnePlus 3 & 3T Cross Device Development] Dieppy:
Stock oos 4.1.3 with r112
[OnePlus 3 & 3T Cross Device Development] Diaze:
what should i flash if im on freedom os 2.8? custom or oos one ?
[OnePlus 3 & 3T Cross Device Development] Dieppy:
Freedom OS is oos based so you got the answer.

Please use search next time :good:
[OnePlus 3 & 3T Cross Device Development] Sytis:
They are for most of the users. But as I don't perform any heavy task or anything like this I underclocked the CPU but also enabled fastlane on both clusters on which I made the threshold a bit more conservative; this way I can save some battery without the device getting wonky (at least it feels like this :good:). Also some minor changes like USB fastcharge and the fine-tuning of the vibration strength for my likings.
[OnePlus 3 & 3T Cross Device Development] ricardowec:
Sorry, can you point out where?
[OnePlus 3 & 3T Cross Device Development] nadejo:
when i turn off touchboost the big cores dont go under 1ghz anymore

(resurection remix)
[OnePlus 3 & 3T Cross Device Development] cultofluna:
Turn the touchboost toggle on and off few times...And check the frequencies afterwards... Should be ok after....

It works for me this way...
[OnePlus 3 & 3T Cross Device Development] kamilnazar:
I'm on FreedomOS 2.8 (OOS 4.1.3). I can't get blue_spark to work. Boots up normally and then after sometime becomes unresponsive and display becomes black. Had to hold power button to restart. Tried to clean flash from beginning with both freedom and stock, but that same problem persist. If i flash any other kernel or stock OOS kernel, everything is back to normal.

I don't know what I am doing wrong. blue_spark was working on previous build os OOS and Freedom. I need some help please.

Device: OnePlus 3T
[OnePlus 3 & 3T Cross Device Development] marf28101995:
You need some help yes because you can't read

Your setup isn't supported you're on your own

✌️
[OnePlus 3 & 3T Cross Device Development] kamilnazar:
OOS isn't supported? :confused:
[OnePlus 3 & 3T Cross Device Development] eroigaps:
Freedom OS is a custom ROM, based on OOS but still custom.
[OnePlus 3 & 3T Cross Device Development] Midomad:
Custom roms aren't supported.
[OnePlus 3 & 3T Cross Device Development] kamilnazar:
At least read my post before judging. I clearly said I clean flashed stock OOS. That same thing happened.

I think I followed proper procedures for bug reporting. I am not looking for a fight or any arguments. Please don't take me wrong.
[OnePlus 3 & 3T Cross Device Development] kokobooster:
[MENTION=7251197]kamilnazar[/MENTION] theres two version of blu kernel. Flash the blu_spark_r112-oos_op3-op3t_f0037e4 version. Im on FreedomOS with that kernel.
[OnePlus 3 & 3T Cross Device Development] skyknife93:
Which build did you download? The oos one or custom?
[OnePlus 3 & 3T Cross Device Development] kamilnazar:
I Flashed OOS build.
[OnePlus 3 & 3T Cross Device Development] Chaplan:
And here we go again. Of course he flashed the custom version, as opposed to the OOS.

If the ROM is based on OOS, OOS version of Kernel is what applies.

It has been discussed here many times, 2 days ago another user had the same problem.

Users should start reading both the ROM and Kernel OP's.

We are always flooding this development thread with the same problems, that reside on the users not reading a bit more.
[OnePlus 3 & 3T Cross Device Development] kamilnazar:
These are the files I downloaded.
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Come on. You know you shared the logs.

We are not sleeping here.
[OnePlus 3 & 3T Cross Device Development] marf28101995:
Go troll anywhere else... You say A your logs shows B so leave this thread please
[OnePlus 3 & 3T Cross Device Development] kamilnazar:
ok then. I will flash it again and share the logs.
[OnePlus 3 & 3T Cross Device Development] B3501:
Your logs say you were using the custom version.
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Exactly, an outdated custom version with no pair to the photo he shared.

Not even the same build number on the photos where we see OOS versions.

And that's why unsupported means unsupported.

Users can have an educated choice when they read a bit. Not 2 days have passed and the boat sails to the same shore.

It is what it is, but it doesn't mean it's alright.:eek:
[OnePlus 3 & 3T Cross Device Development] uudruid74:
Normally, I would say that it could be possible that a custom kernel got the wrong filename ... but I just flashed the very same kernel release with no issue. I'm also pretty sure all that is set up by scripts that won't make silly mistakes.

More than likely, there is a custom kernel on that filesystem with the name "custom" just not in the ADM folder. Maybe it's in Downloads?

---------- Post added at 08:29 AM ---------- Previous post was at 08:27 AM ----------

Quick note. I still get some jitter in K@ mail when scrolling long lists. Changing CPU Boost to 750 fixes it. I'll retest at lower values, but perhaps the default of 500 may not be enough.
[OnePlus 3 & 3T Cross Device Development] Chaplan:
So we are to admit that you flashed an outdated version to? Just asking.

And about scroll lag. That is usually a problem with rogue apps, G+ is on the top of the list for me. I use only fastlane to bypass that and it works pretty well.

Apart from that all my settings are stock.

Give it a try if you haven't already, should make a huge difference.
[OnePlus 3 & 3T Cross Device Development] kamilnazar:
Ok I flashed it again. I am attaching current logs with screenshots. The log still showing custom but elementelx kernel maneger shows oos blu_spark. I took that along with date since you guys didn't believe me.

I am not trolling. I will provide whatever info you need.
[OnePlus 3 & 3T Cross Device Development] Dieppy:
Hi man, how do you feel your battery life with fastlane? Which values do you use? I use it too but I'm curious to know your settings
[OnePlus 3 & 3T Cross Device Development] kamilnazar:
It happened again. I'm not trolling or spamming this thread. This is a genuine problem.

I even checked the md5 of the file I'm flashing.
[OnePlus 3 & 3T Cross Device Development] A Sad Napkin:
Jesus when you gonna listen. That custom roms whether they are oos or lineage or caf or aosp aren't supported. Even beta stock oos isn't supported.

Flash stock oos not beta not freedom. But Stock. Then flash blu spark.

These threads just go round in circles. People don't read or listen.
[OnePlus 3 & 3T Cross Device Development] B3501:
There's something wrong at your end. Never ever had that with Blu spark.
[OnePlus 3 & 3T Cross Device Development] kamilnazar:
Ok. Let me say this one more time since you didnt read my previous posts. I tried both stock and Freedom. Clean flashed.
[OnePlus 3 & 3T Cross Device Development] A Sad Napkin:
Its a problem on your end. Nothing to do with the kernel.

Loads of people are using the latest version.

Are you using BLuSpark TWRP? Did you flash the kernel after flashing root access?

Have you tried redownloading it just in case its a dodgy download?

If you actually flashed the stock rom for your phone then TWRP would of been replaced. Did you reflash TWRP after flashing stock rom?
[OnePlus 3 & 3T Cross Device Development] Vaizen:
[MENTION=3873953]eng.stk[/MENTION] I'm amazed with latest release. I achieved almost 8h of SoT with stock values no need to apply profiles, such as AKT.

I've followed your work since I had my N5, but haven't tested your work on the OP3. Amazing really amazing.
[OnePlus 3 & 3T Cross Device Development] cloudx720:
i returned to stock to get rid of the dm-verity error screen, im currently on beta14 and want to unlock and installed your twrp. How do i avoid getting the dm verity error?? if i swipe right to alow mods and then flash magisk 12 good to go or is there noway of avoiding the error? thanks :D
[OnePlus 3 & 3T Cross Device Development] Chaplan:
I adjust it to my needs on a per ROM/Kernel build basis.

On OOS stable I usually set the threshold between 30 to 50.

On custom ROMS it varies. But never above the 50 value (I find it way to conservative above 50 for my needs, and must say that even 30 to 50 is conservative enough but I don't feel the need to go lower for now).

Big cluster only, on any scenario I have tested it on. It just suits my needs that way so I'm not enabling it on little cluster nowadays. I keep that window open though.

I would like to add only that it is highly parametrizable and if you know what you are looking for from Fastlane you probably can get it by testing some values.

As for battery, which is always a concern to every user. I have to say I never found it to drain more with fastlane enabled, and the truth is I was always looking for it to drain a tiny bit on the beginning.

I came to believe I can get more battery with it on than off. My load is always low with it on.

These conclusions are not mine alone, those involved on testing it came to similar conclusions.

And that's Fastlane for me!:cool:
[OnePlus 3 & 3T Cross Device Development] Dieppy:
You're fantastic, really appreciate your answer :highfive:
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
I have a noob question here. What exactly is fastlane?
[OnePlus 3 & 3T Cross Device Development] habylab:
If you search this thread, you can find a thorough answer. But essentially any high load operations will be pushed through quicker by ramping up the CPU.
[OnePlus 3 & 3T Cross Device Development] vatsal8286:
which one r112?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
You're welcome :highfive:
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Stop spaming my thread with non kernel crap.

Thanks
[OnePlus 3 & 3T Cross Device Development] eng.stk:
I don't give support to neither custom ROMs neither to outdated builds (why the hell are you on r98?).

Kernel is fine, whatever you got there you need to troubleshoot it yourself.
[OnePlus 3 & 3T Cross Device Development] Vaizen:
Exactly.
[OnePlus 3 & 3T Cross Device Development] uudruid74:
How is 112 outdated? I'm just saying that I downloaded the exact kernel in the screenshot with no issues.

And yes, the problem IS with the app, but its not rogue. It's simply doing a lot of work during the scroll. In this case, when K@ is first started scrolling is slow, who knows if its doing IMAP or just heavy SQL. Its the combined inbox with 4 email accounts. That's not my point. There is no bug and I'm not pointing blame. I'm just saying it needs more juice and a particular tweak was working very well at giving it the juice it needs. It a majority of people find they need a bit more push, change the defaults.

I felt it was perfectly valid feedback, on both points.

---------- Post added at 04:58 PM ---------- Previous post was at 04:46 PM ----------

Uhmm ... why do people keep saying this? I always download the full OTA since I'm rooted and I have NEVER had this happen. Please find me an OTA zip file that has a recovery.img in it. I have 3 or 4 on my phone right now, including the main 4.0.3 release, and none of them contain a recovery.img.

Sorry for off topic, but let's not assert things that aren't true.

---------- Post added at 05:13 PM ---------- Previous post was at 04:58 PM ----------

All these screenshots are a waste of bandwidth. The two dmesg logs you posted are byte for byte identicle. Same md5sums and everything. Since a dmesg is is actively written constantly, then these are both from the same dmesg command.

I think you are not gathering this info correctly and you keep posting some old dmesg from when you ran the custom ROM rather than a fresh run. Flash stock, flash the blu spark. Now root it. Now use "adb shell" or however you want to get a shell and do something like this immediately after boot ...

su

dmesg >/sdcard/dmesg-OOS.txt

Now send THAT one.