yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] Sam Nakamura:
Sure I loved it :highfive: working hard on this "space & time" thing ever since, if I'll ever be successful I'll teleport you some ice cold beer and goodies...

Maybe even a six pack - you definitely deserved it :p

Happy new year, hope you made it well into this bright new era of twenty-eighteen
[OnePlus 3 & 3T Cross Device Development] ansonnippon:
Can you tell me that r209 can operate on OOS 5.0.1?
[OnePlus 3 & 3T Cross Device Development] ceikokitkat:
For me it works, and works really good :)
[OnePlus 3 & 3T Cross Device Development] ansonnippon:
Got it

thanks

:good::good:
[OnePlus 3 & 3T Cross Device Development] Flypants101010:
Happens to me too.

Audio stutters playing games such as crashlands and sonny. Tried everything, seems like a kernel issue

Same problem with r207 and r209
[OnePlus 3 & 3T Cross Device Development] jeremyet:
Might be unrelated, but I've had audio issues on games built with unity a couple of times. I found that it was an issue related to deep buffer removal magisk module. Might be worth seeing if it helps in your situation....
[OnePlus 3 & 3T Cross Device Development] Flypants101010:
I tried installing the module, had no effect on the problem. I hope someone can have a look at my logcat and see what's causing it.
[OnePlus 3 & 3T Cross Device Development] Aveon:
Can someone help me

i want flash new blu spark twrp and i already have bluspark twrp 3.0.1 so should i flash bluspark 3.2.0 twrp .zip file or .img file?
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Hi.

.Zip files are kernel files.

.img files are Recovery files.

You need .img if want recovery.
[OnePlus 3 & 3T Cross Device Development] Aveon:
Thank you :D got confused from the warning note
[OnePlus 3 & 3T Cross Device Development] ak_bagade:
can i flash this on omni rom 8.1?
[OnePlus 3 & 3T Cross Device Development] johnholley123:
No, as there is not yet a custom ROM version for Oreo.
[OnePlus 3 & 3T Cross Device Development] @krishne35:
None of the kernel boots on Omni ATM
[OnePlus 3 & 3T Cross Device Development] 200:
airline USB charing mystery

Guys, it might be a complete red herring but just wanted to ask if USB charging issues (such as this one that i am facing) are related to kernel?
[OnePlus 3 & 3T Cross Device Development] krabban:
I dont know IF this is related . I just flashed the bluespark kernel on RR nougat. Now I can't open AKT app. Do I need to dirty flash ROM again and then flash kernel?
[OnePlus 3 & 3T Cross Device Development] marf28101995:
WTF

Now kernel is responsible for ****ty apps not working? Lol
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Facing the same issue with a lemon. (Log in the form of SS attached)

That USB port isn't providing enough "juice".

This kernel also features USB fast charge. Enable it, plug it into a decent USB port and check with Ampere.

PS: Got Ninjad by the OP... well, maybe he can check my Log.
[OnePlus 3 & 3T Cross Device Development] krabban:
My bad I had accedently uninstalled ex kernel manager haha
[OnePlus 3 & 3T Cross Device Development] Lvsitano:
Did OnePlus update the kernel source code to reflect current change in OOS 5.0.1 ? I am asking that, because there is no new blu_spark kernel.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
No kernel updates from OnePlus on 5.0.1
[OnePlus 3 & 3T Cross Device Development] Lvsitano:
Thanks for the quick reply. Those guys must be drunk or something :eek:
[OnePlus 3 & 3T Cross Device Development] eng.stk:
They pushed the 5.0.1 source during the night actually :victory:
[OnePlus 3 & 3T Cross Device Development] Lvsitano:
Maybe they ran out of booze :laugh:
[OnePlus 3 & 3T Cross Device Development] Krustak:
We all awaiting your fastlane magic now. Make it rain
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r210 oreo unified

All right crew!

New Oreo build is up :highfive:

Because of latest TWRP and Oreo changes, you'll need to use TWRP 3.2+ or my unified TWRP 3.2.1-x blu_spark v8.61 (recommended).

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

Because of latest Oreo changes, builds will touch system partition.

So if you want to go back to stock just backup boot and system or dirty flash you ROM zip.

This is for Oreo OOS only. Nougat is EOL.

blu_spark_r210-oos-oreo_op3-op3t_2e02d1f.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).

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.

No mirrors please

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] neinfricatu:
r210 works perfect on OB20. :)
[OnePlus 3 & 3T Cross Device Development] Kiceczek:
No more kernel update for Nougat version ?
[OnePlus 3 & 3T Cross Device Development] kentexcitebot:
Unless there is a compatibility problem with the ROM going rogue on custom kernels, there should be little to no difference with battery or performance between other kernels. Well-known kernels like this one and ElementalX should have no issues, but your mileage will vary depending on the ROM. The battery-drain people experience occurs from userspace.

Let's just stop talking about this please. It's been discussed way too many times. If there are still any questions about it, search Google and it'll take you to the appropriate XDA thread.
[OnePlus 3 & 3T Cross Device Development] crzykiller:
What the heck do you run on your phone? my cpu usage is around 1-5% at idle with the screen on. and yea it was a good time ago and the phone heated up massive
[OnePlus 3 & 3T Cross Device Development] Mostafa Wael:
That is called "optimisation" ;)
[OnePlus 3 & 3T Cross Device Development] habylab:
Bloody hell. What am I doing wrong to get *just* 4 hours? I've tried with Amplify, without it...

I don't want to go off topic anymore, so would you mind PMing me? Thanks!
[OnePlus 3 & 3T Cross Device Development] C.H.T.J.:
Is this kernel overclocked? If i run it out off the box? Ex kernel manager shows me big 2150 small 1593! Is this by default?
[OnePlus 3 & 3T Cross Device Development] derdjango:
I don't think that's too off topic, since a lot of people lile to worry and complain in kernel threads. From my experience, bad battery is mostly due to wonky apps and bad/unstable cell reception and wifi wakelocks. Also it highly depends on your usage. If you tend to check your phone often for a short time, you'll drain the battery faster than with a few longer sessions. Not much to do with actual usage drain, what you are looking to is to minimize idle drain by reducing wakelocks. So find out what wakes your phone ?
[OnePlus 3 & 3T Cross Device Development] habylab:
Hmm, interesting. So, do you use Amplify or Greenify at all? Thanks.
[OnePlus 3 & 3T Cross Device Development] derdjango:
Nope, no need.
[OnePlus 3 & 3T Cross Device Development] habylab:
Wow, okay. That's good news. I'll give it a go tomorrow.
[OnePlus 3 & 3T Cross Device Development] immi803:
[MENTION=3873953]eng.stk[/MENTION]

R107 superb work dev,awesome

Thanks
[OnePlus 3 & 3T Cross Device Development] habylab:
I was checking my logcat for an app error I came across, and I noticed this error appearing plenty of times. I have no kernel tuner installed, so is this kernel or something my side that is the issue? Thanks.

09-14 00:13:25.766 E/ANDR-PERF-OPTSHANDLER(5351): Failed to read /sys/devices/system/cpu/cpu0/cpufreq/interactive/above_hispeed_delay
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Thats because maybe something in powerhal checks the governir (which is not interactive)

Useless warning, ignore it.
[OnePlus 3 & 3T Cross Device Development] nazerro:
It's been two months since the last time i use this kernel. I'm very surprised on how far this kernel has improved. Amazing. Thank you very much [MENTION=3873953]eng.stk[/MENTION]. Now I feel like I'm back to my nexus.

Anyway, if you could consider this small request. Would you kindly make bluspark to be able to run /system f2fs? Thank you very much bro.
[OnePlus 3 & 3T Cross Device Development] andyman_187:
anyone tried this with the 3.2.5 system dump?

http://xdaforums.com/oneplus-3/how-to/untouched-oxygen-os-3-2-5-img-boot-img-t3460975/page4
[OnePlus 3 & 3T Cross Device Development] anirudhnyg:
Wow ! I never thought my OP3 could be more fluid and fast ! After flashing this I can really feel the difference while scrolling and general use . Battery life is excellent too 3% drain over night .

Very impressed. . thanks a lot
[OnePlus 3 & 3T Cross Device Development] otonieru:
Yes. It works fine
[OnePlus 3 & 3T Cross Device Development] habylab:
Okay, at least it doesn't mean anything bad. I have never seen it before, so thought I would just check!
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Nope...

RO partitions like system have no gains running f2fs.

And block updates (used by 99.9% of the ROMs) will automaticly format it to ext4.
[OnePlus 3 & 3T Cross Device Development] nazerro:
Well actually i successfully did a trick for that, i made nandroid for system, format system to f2fs, set use rm - rf instead of formatting, then restore my system nandroid back. That way my system will still be f2fs. The result for me is everything is super smooth and somehow my antutu score reached 159888.

But nevermind, if you think that wouldn't be necessary, i still love your kernel and will still use it forward. I have test all kernels available for op3 and now i conclude that at this point, bluspark is the winner. Both for smoothness and battery life. [/QUOTE]
[OnePlus 3 & 3T Cross Device Development] phil_greg2001:
[/QUOTE]

Hi Nazerro,

Have you compare with EXT4 system ?

:cool:
[OnePlus 3 & 3T Cross Device Development] RaEsAcademy:
Two posts above yours,in the release note the dev said 'Nougat is EOL'
[OnePlus 3 & 3T Cross Device Development] Kiceczek:
Yea I saw that but I don't know what does it mean,until google helps me now I know.
[OnePlus 3 & 3T Cross Device Development] jaycelou:
Any advantage, in every and any aspect, of this kernel over the original OOS? Thanks.
[OnePlus 3 & 3T Cross Device Development] OmarvinG94:
Better at everything compared to stock kernel.. atleast from my experience
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r212 oreo unified

Removed, go for r214 instead.
[OnePlus 3 & 3T Cross Device Development] fossean:
r212 is bootlooping for me on FreedomOS 3.2; tried dirty flashing rom without success. r210 reflashed and boots fine.
[OnePlus 3 & 3T Cross Device Development] jenaplisken:
with r212 i have bootloop on ob29. with r210 everything is ok
[OnePlus 3 & 3T Cross Device Development] ceikokitkat:
r212 bootloops here on OOS 5.0.1
[OnePlus 3 & 3T Cross Device Development] akshay961:
Bootlooping for me also on Experience OS R30, back to r210
[OnePlus 3 & 3T Cross Device Development] theduke7:
yes i conform it bootloops in both stable and beta OOS
[OnePlus 3 & 3T Cross Device Development] acultr:
212 bricked my 3t
[OnePlus 3 & 3T Cross Device Development] theduke7:
it's not bricked, just flash 210 again
[OnePlus 3 & 3T Cross Device Development] acultr:
how if I can not boot into recovery and I can not turn on my phone ?
[OnePlus 3 & 3T Cross Device Development] theduke7:
long press the power button until the phone turns off, or power +vol up untill it reboots to the screen with warning, then press vol to selection menu

[MENTION=3873953]eng.stk[/MENTION] i attached a log of the bootloop.
[OnePlus 3 & 3T Cross Device Development] vishruthys:
Use power and volume down to restart. Then power and volume up to go to recovery
[OnePlus 3 & 3T Cross Device Development] acultr:
I've managed to solve it.
[OnePlus 3 & 3T Cross Device Development] deepongi:
Hold power + volume up for about 10 - 15 seconds, and report what happens.

Edit: ups.. duplicate awnser, didn't read until the end of the thread.
[OnePlus 3 & 3T Cross Device Development] acultr:
it's not helped I had only black screen. must turn the power button 40 seconds and after use the recovery boot method.

but thank you
[OnePlus 3 & 3T Cross Device Development] bc1977:
Maybe you should learn the basics (how to reboot in recovery, etc.) and know exactly what you're doing before flashing things...

It's so rude to accuse the dev (and especially this dev, recognized by all) to have bricked your phone.

XDA is becoming full of spoon fed users unable to do a little research by themselves.
[OnePlus 3 & 3T Cross Device Development] acultr:
ooo man my first costume rom was cyanogen 6.

do you think if I don't know how can I boot in recovery?

AND..... I did not accuse anyone

I'm wondering what you would have done if you just saw a black screen and none of the buttons respond to anything
[OnePlus 3 & 3T Cross Device Development] eng.stk:
MAybe meltdown patches acting up guys...

So much redundant crying and not one kernel log.

Typical xda day... get me kernel logs!
[OnePlus 3 & 3T Cross Device Development] acultr:
last kmsg
[OnePlus 3 & 3T Cross Device Development] acultr:
logcat
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Test this and let me know. An d logs in case of issues :)

https://xdaforums.com/devdb/project/dl/?id=28068
[OnePlus 3 & 3T Cross Device Development] acultr:
rec. log
[OnePlus 3 & 3T Cross Device Development] theduke7:
another log, kernel this time :)

213 actually freezes at the end of animation , then goes black, had to turn off the device with buttons.

(a lot of the word "panic" at the end of the log lol)
[OnePlus 3 & 3T Cross Device Development] eng.stk:
ok thanks. same drill:

https://xdaforums.com/devdb/project/dl/?id=28071

let me know how it goes guys:fingers-crossed:
[OnePlus 3 & 3T Cross Device Development] theduke7:
214 works m8 ... thanks.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Hum meltdown stuff indeed... I'll take alook at some more upstream realted to this that dropped in aosp-common, it will be postponed to next releaese
[OnePlus 3 & 3T Cross Device Development] bc1977:
What would have i done?

1) Not cry my device is bricked (at least in public lol)

2) search a little bit (xda or google) about how to re-launch a soft bricked device (there are many examples for our beloved device)

3) cross fingers and try to figure it out :)

Sorry, but i'm just fed up with people who don't bother to try to search a little bit, complain about everything, etc.

It's not especially aim at you, it's just my daily mood :)
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r214 unified (oreo)

All right crew!

New Oreo build is up :highfive:

Because of latest TWRP and Oreo changes, you'll need to use TWRP 3.2+ or my unified TWRP 3.2.1-x blu_spark v8.61 (recommended).

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

Because of latest Oreo changes, builds will touch system partition.

So if you want to go back to stock just backup boot and system or dirty flash you ROM zip.

This is for Oreo OOS only. Nougat is EOL.

blu_spark_r214-oos-oreo_op3-op3t_cfebe51.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).

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.

No mirrors please

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] neinfricatu:
r214 working fine with OB20.
[OnePlus 3 & 3T Cross Device Development] acultr:
:good:
[OnePlus 3 & 3T Cross Device Development] FrailtyXYZ:
can i use the latest blu spark twrp to convert to ext4 or is it recommended to use official twrp for that?
[OnePlus 3 & 3T Cross Device Development] calvinistmac:
You can use either one.
[OnePlus 3 & 3T Cross Device Development] theduke7:
[MENTION=3873953]eng.stk[/MENTION] i don;t know how to get you a log for this, and i don't know if its only me, but the following happened to me 4 times using Blu TWRP 8.61

this happens only when i flash a rom (namely for may case OOS) , the flashing goes well and finishes, but when i press reboot to system button, it freezes for around 10 seconds, then the screen goes black and the from small light flashes white, i just long press the power button the devices turns off and everything is normal from there...

i tried it in almost all posible scenario...i wipe at least system and caches before any flashing.

flashed oos only the reboot (issue occurs)

flashed oos then blu_spark twrp then reboot (issue occurs)

flashed oos then blu_spark Kernel then TWRP then reboot (issue occurs) ...etc

it happened since 8.61 was released, i thought it's something i'm doing wrong, or something corrupted at 1st, but it happened after fullwipe + adb flash of OOS then i fastboot 8.61, the following time i flashed with it the same thing happened.

just to give you all the info , i'm encrypted and i'm on EXt4 not f2fs .

although it would mean i have to flash again, but if you need a log some how please let me know where and how to get it and I'll be glad to get it.
[OnePlus 3 & 3T Cross Device Development] theduke7:
[MENTION=3873953]eng.stk[/MENTION] i don't know how to get you a log for this, and i don't know if its only me, but the following happened to me 4 times using Blu TWRP 8.61

this happens only when i flash a rom (namely for my case OOS) , the flashing goes well and finishes, but when i press reboot to system button, it freezes for around 10 seconds, then the screen goes black and the from small light flashes white, i just long press the power button the devices turns off and everything is normal from there...

i tried it in almost all possible scenario...i wipe at least system and caches before any flashing.

flashed oos only the reboot (issue occurs)

flashed oos then blu_spark twrp then reboot (issue occurs)

flashed oos then blu_spark Kernel then TWRP then reboot (issue occurs) ...etc

it happened since 8.61 was released, i thought it's something i'm doing wrong, or something corrupted at 1st, but it happened after fullwipe + adb flash of OOS then i fastboot 8.61, the following time i flashed with it the same thing happened.

just to give you all the info , i'm encrypted and i'm on EXt4 not f2fs .

although it would mean i have to flash again, but if you need a log some how please let me know where and how to get it and I'll be glad to get it.
[OnePlus 3 & 3T Cross Device Development] Flasher8:
I got this black screen issued when restored my twrp backup. Same scenario as your and using latest Blu twrp 8.61:confused:
[OnePlus 3 & 3T Cross Device Development] Stryker_Echo9er:
This is not an issue with the Kernel or the custom TWRP i suppose, many people are facing this issue.

Its just the way the installation of the Oreo OOS works i would say.

The steps that I follow while clean flashing are as below:

1. Boot into TWRP -> Wipe -> Advanced Wipe -> (Select all

except Internal Storage

) -> Wipe.

2. Copy the necessary files to the phone (E.g. Rom, Magisk, Mods (if any) & the Blu-Spark Kernel).

3. Go to install -> Select the ROM -> Install -> Wait for installation to complete -> Force Reboot to recovery if phone reboots. (Dont Worry, the rom has been installed).

4. In TWRP -> Wipe -> Advanced Wipe -> (Select all

except Internal Storage & System Partition

) -> Wipe.

5. Go to Install -> Select Mods (If any) -> Install -> Wipe Dalvik & Cache.

6. Go to Install -> Select Magisk -> Install -> Install -> Wipe Dalvik & Cache.

7. Go to Install -> Select Blu-Spark Kernel -> Install -> Wipe Dalvik & Cache.

8. Go to Wipe -> Advanced Wipe -> Wipe Dalvik & Cache again (just to be sure) -> Reboot.

9. VOILA, Enjoy. :)

Note: I always follow the order ROM->GAPPS (Not needed in this case)->MODS (Bootanimation, Audio Mods, Debloater, etc)->ROOT (Magisk/SuperSU)->KERNEL.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
You probably used other twrp, delete your twrp settings file.

All solid here.

Sent from my blu_spark'd OP5/5T
[OnePlus 3 & 3T Cross Device Development] :
Same
[OnePlus 3 & 3T Cross Device Development] Sam Nakamura:
If you have a PC somewhere near I would think that "device monitor" from SDK would be your best bet to get at least something, not sure but maybe worth a shot...

https://developer.android.com/studio/profile/monitor.html

or last_kmsg or a recovery log?

Actually interesting question, I'm not sure either, rather guessing :)...

But I can confirm that flashing OOS and blu_spark's kernel also produced the "black screen w/white LED" for me, flashing process crashed exactly when TWRP flashes the kernel out of the file stack I chose (ROM, Kernel, Magisk), after crashing it switched to BSw/wLED, long pressing gets me back to recovery, no issues there, I reflashed the stack in every case that happened to me, just to ensure it's all bootable and indeed, the second time it was always fine, no errors nothing, it only happened when clean flashing OOS5.x on first attempt to flash blu_spark's kernel on blu_spark's recovery, as this is easy to fix I didn't spend much thoughts on this but as you mention it I thought I tell my experience...
[OnePlus 3 & 3T Cross Device Development] theduke7:
that's exactly what i do now ... i was just informing eng.stk if he wanted to look at it.

i understand it's not a kernel issue.

---------- Post added at 11:07 PM ---------- Previous post was at 11:02 PM ----------

not really m8, since OOS Oreo came out i 1st used the edited one , but once your TWRP was released , i flashed it then wiped everything (including external drive)...actually, i wiped every thing also when 8.61 also.

not complaining here, just letting you know , and as it was mentioned by another member above , we work around it by force rebooting after rom and twrp flash, it might be as it was said something with OOS ...anyway next time i flash i will delete the setting file 1st. and reboot to recovery before flashing.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Nope, nothing I can do for you.

Let's get back on topic.

Sent from my blu_spark'd OP5/5T
[OnePlus 3 & 3T Cross Device Development] theduke7:
yeah, i didn't give it much though either, until last night when i was sure the entire proccess was clean , i t doesn't bother me really (at least for now), but i thought why would it do that, it might be nothing now but maybe in the future may affect something!!!

i don't know about adb monitor, will check it and might give a try, but last_kmsg will only start capturing from boot animation (i'm not sure), and recovery log will just capture the process that was... i don't know if twrp keeps logs from session to session or not, or is it something to be enabled, if it's it might be there.

apparenltly not needed though, so when (if) asked, will provide log.

---------- Post added at 11:17 PM ---------- Previous post was at 11:16 PM ----------

sure
[OnePlus 3 & 3T Cross Device Development] stewwert:
On oreo beta 30 installing blu-spark r210 or r214 broke my WLAN. Anyone the same issue?
[OnePlus 3 & 3T Cross Device Development] marf28101995:
Flash it properly next time

Search because that's been answered already

Flashing order

Rom +Root + kernel

Be sure to use the right version of the kernel