yashsingh1/xdaforums huggingface dataset:
[OnePlus X Original Android Development] eng.stk:
Think I managed to replicate the issue some people had on the N5 with previous f2fs update.

Seems like 4.6 backports still have the derp, I'm going to revert it guys :eek:
[OnePlus X Original Android Development] Part.0:
lol. so we have to re-flash it back? anyway i don't use f2fs (always failed when tried to). ok sir just give us a shout when new upload done :P thanks
[OnePlus X Original Android Development] eng.stk:
blu_sp★rk r137

All right crew!

New builds are up!

CM build is also updated, this is made for Marshmallow 6.0.1 ROMs.

I decided to take CM build from beta, but same remains: using custom ROMs you're on your own ;)

If you flash in CM 12.1 you will find broken stuff, just use an old build (r98).

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 X Original Android Development] seacowx:
it's up already. go get it cowboy lol

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

thanks for fast act to revert it. so twrp alls good or better to revert back to v32 before flashing r137? thanks again!
[OnePlus X Original Android Development] eng.stk:
TWRP seems to be good, but tomorrow I'll refresh it also :good:
[OnePlus X Original Android Development] Part.0:
:P olrite ! fly there

---------- Post added at 12:30 AM ---------- Previous post was at 12:29 AM ----------

:P olrite! fly there
[OnePlus X Original Android Development] iamelton:
so since i dont use f2fs, theres no need to flash r137 on top on r136 then?

tia..
[OnePlus X Original Android Development] Exodusche:
Yee haw working flawless on latest cm nightly! :)
[OnePlus X Original Android Development] namquang93:
What is the different between twrp-3.0.2-1-onyx_blu_spark-v34.img and official TWRP for onyx ? Thank you !
[OnePlus X Original Android Development] eng.stk:
TWRP 3.0.1-1 | blu_sp★rk v35

Updated TWP with latest kernel is up!

Enjoy :good:
[OnePlus X Original Android Development] ptblad:
Flashed r136 for OOS and shortly after a number of apps were force closing: chrome, gmail, messenger etc. My first thoght was that it was caused by f2fs on my cache partition, but all my efforts to solve the problems failed. I tried to flash r137 (with reverted f2fs), tried to wipe cache in TWRP, tried to change back to ext4 for cache in TWRP. But it didn't solve the problem. Even tried to restore a nandroid backup made before I installed r136, but even that didn't work.

Getting a bit desperate... But when I studied some catlogs, the cause of the problems pointed me in a completely diffrent direction: Amplify. I disabled it and voila: everything worked like a charm!

Further investigation led me to the conclusion that blocking the wakelock Icing in Amplify was the cause of the force closing apps. Removing Icing from limited wakelocks was the solution.

What did I learn by this? It's easy to blaim the last modification of your system, but it might be something else. Read logs and try to pinpoint the cause!
[OnePlus X Original Android Development] seacowx:
it's a good thing for people to handle the issue with comprehensive way, like you did.

so, leason learned.

enjoy your opx with blu_spark's sparks! ;) [MENTION=3873953]eng.stk[/MENTION]
[OnePlus X Original Android Development] dingermtb:
Thank you very much for the insight. I've been having similar issues but thought it was something in my latest ROM update. I'll give it a try?

Sent from Outside the 9 using my Zombiefied Exodus OnyX
[OnePlus X Original Android Development] eng.stk:
Nice troubleshoot, stuff like that happens all the time and people don't bother to try pinpoint stuff.
[OnePlus X Original Android Development] eng.stk:
MP-Decision? That's because it's disabled, nothing I can do.
[OnePlus X Original Android Development] criz.89:
Interactive is new default govenor?! Using r137.
[OnePlus X Original Android Development] seacowx:
is that a question mark or a statement one?

the default gov. for r137 and older ver. is "blu_active". yes, it's based on interactive gov which has been modified and tweaks flawlessly. well, need confirm that tho' [MENTION=3873953]eng.stk[/MENTION]
[OnePlus X Original Android Development] eng.stk:
blu_sp★rk r140

All right crew!

New builds are up, go get it!

I also pushed TWRP 3.0.2.-1 | blu_sp★rk v36 with updated kernel, components and upstream fixes and updates.

Important to say, this features crypto updates and set HW crypto baseline support ready (still needs work on it to make this mode available, if even it will ever work).

Crypto will work the same has in OOS (sw+cpu neon extensions). For use encryption on CM13, you will need to use at least nightly from 19/05 and you MUST format your data partition and only encrypt after (so make a backup before you attempt this).

CM build is also updated, this is made for Marshmallow 6.0.1 ROMs.

I decided to take CM build from beta, but same remains: using custom ROMs you're on your own ;)

If you flash in CM 12.1 you will find broken stuff, just use an old build (r98).

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 X Original Android Development] piotrpan:
Thanks a lot for your new releases:)

Tough its CM focused do you Have insight why data has to be wiped before encryption but OOS supports encryption without data loss?

Or is restoring data partition From a backup after it was crypted an Option here?

Gesendet von meinem ONE E1003 mit Tapatalk
[OnePlus X Original Android Development] seacowx:
thank you, it's great improvement. but i need to ask does it make more battery usage or more battery drain in this nu build r140? presently i am happy with r137. thanks sir!
[OnePlus X Original Android Development] soxfor:
What i think [MENTION=3873953]eng.stk[/MENTION] is saying is that before attempting encryption we need to perform a clean flash.
[OnePlus X Original Android Development] Kiras_PL:
Can anybody tell me what's all going with encryption ? What is that ?
[OnePlus X Original Android Development] variant0:
You won't pull twrp updates to the official tree anymore?
[OnePlus X Original Android Development] piotrpan:
The trouble with it of not working yet, before 19.5 build?

More or less if you lose your phone its an open piece of data for the finder, thus you want to encrypt it to not easily lose whatever stored credentials, pics or other sensitive data.

Gesendet von meinem ONE E1003 mit Tapatalk
[OnePlus X Original Android Development] Kiras_PL:
Yep, i understand :) thanks ;)
[OnePlus X Original Android Development] eng.stk:
When and if I feel like it :silly:

A clean flash (wipe), isn't enough because it will delete only the ROMand apps config.

You actually have to format data on TWRP.

THe thing is that in OSS encryption always worked.

If you wher on 17/05 nightly and try to encrypt it will fail.

If you dirty flash 19/05 nightly or later and try to encrypt it will fail.

You need to have a clean partition layout to encryption to work.

So, you format the partition and you will loss data, but after that if you're on 19/05 nightly or later encryption will work fine and your data will be kept.

Got it?
[OnePlus X Original Android Development] piotrpan:
Got it thanks. Last question to this restoring data after encryption via twrp is not an option to keep data instead starting phone setup from scratch?

Gesendet von meinem ONE E1003 mit Tapatalk
[OnePlus X Original Android Development] eng.stk:
I wouldn't mess with it.

Backup your data with TiBu or something like that and copy it to PC or external sdcard.

Don't be lazy :silly:
[OnePlus X Original Android Development] zedawow:
Anyone using this Kernal in daily basics please tell me the Screen On Time after using this. Now Um on Oxygen stock ROM and I'm only having 3 hours of SOT. Please share an image! Thanks :)
[OnePlus X Original Android Development] :
It depends on several factors, such as the phone's uptime (since last charge), mobile data usage, gps usage, etc etc. I usually get 3h SOT but it's during a 2-3 day run without charging it, so it's pretty good. I can get a much better SOT very easily, but the battery won't last 2-3 days, only 1 (or even less than 1).

tl;dr: it depends on how you use your phone
[OnePlus X Original Android Development] zedawow:
Well I don't use data also sim in on 3G mod. Always connected to the WiFi. Location and all are turned off. Only using my phone for WhatsApp and FB not even playing games. Will it last a day with 5 or higher SOT ?
[OnePlus X Original Android Development] :
Why not experiment? Anyway, the Facebook app is very well known for being a battery hog. Still, this thread should not be used to talk about things like SOT, because it has little to do with the kernel.
[OnePlus X Original Android Development] dingermtb:
As always, running phenomenal on Exodus 6. TWRP running awesome, as well. Thanks again for all your hard work?

Sent from Outside the 9 using my Zombiefied Exodus OnyX
[OnePlus X Original Android Development] iamelton:
[MENTION=3873953]eng.stk[/MENTION]

am running OOS 2.2.1-X..

flashed twrp 3.0.2-1 blu_spark v36, and kernel r140 over r137.. found out that the "Back" and "Recent Apps" virtual keys got swapped (back key on the left showed recent apps, and recent key on the right functioned as going back)..

then flashed r137 again, and the keys resumed normal behaviour..
[OnePlus X Original Android Development] eng.stk:
Every release I must repeat myself...

Use the search button.
[OnePlus X Original Android Development] seacowx:
weird, i am facing random reboots once a day now, and 1/4 part of the screen is got flickering (at the bottom of the screen) never had such these problem before. how to fix?
[OnePlus X Original Android Development] pompe90:
Are you on cm13? Ive just got flickering on my cm13 and I'm not using blu_spark kernel, so not kernel related.

Ask somewhere else :)

Skickat från min ONE E1003 via Tapatalk
[OnePlus X Original Android Development] seacowx:
nope. im on oos 2.2.1 and blu spark r140
[OnePlus X Original Android Development] eng.stk:
No logs, no fun.

Never seen anyhting like that, I sugest you cleanflash.

Kernel is rock solid.
[OnePlus X Original Android Development] Mohit31:
Can you tell me which zip to flash..?

Does cm one works with exodus..??
[OnePlus X Original Android Development] dingermtb:
Yes, if you're on Exodus, flash CM version. The other is for stock Oxygen OS. CM version is awesome on Exodus. Been running this kernel for a couple months now (since I got this device) and haven't had one issue at all?

Sent from Outside the 9 using my Zombiefied Exodus OnyX
[OnePlus X Original Android Development] Mohit31:
Thanks for the help :)
[OnePlus X Original Android Development] soxfor:
Hey [MENTION=3873953]eng.stk[/MENTION]. By clean flash i always meant format data/cache.
[OnePlus X Original Android Development] seacowx:
s

as for today no more random reboots. but bottom screen flickering/pulsated still there. maybe i got false setting on my device or i unaccidentaly messed up the kernel setting. still trying to figure it outs..

sorry to bother, just didnt know where to post. all were busy wit wheres update MM bla bla
[OnePlus X Original Android Development] Kiras_PL:
Hi [MENTION=3873953]eng.stk[/MENTION] after some time of using r140 I think that r137 was a bit smoother. Can You do something with it ? Has Anyone else faced it ?
[OnePlus X Original Android Development] Kéno40:
I'm not sure it's smoother, but I've got "wake up" issues. Sometimes, I have to unwake twice to make it respond.

I know, it will require a logcat, but that's difficult to catch because it happens randomly.
[OnePlus X Original Android Development] eng.stk:
No issues like that here, sorry.

All good for me, nothing I can do for you mate.
[OnePlus X Original Android Development] Exodusche:
Just flashed on latest cm nightly running smooth as always. But did I excpect anything less. ;)
[OnePlus X Original Android Development] adity:
I am facing a lot of lag in games and the lav goes away with conservative governor. What am I doing wrong
[OnePlus X Original Android Development] ikedroid:
Do you have 'prevent accidental wake up' checked? I wonder if its better or worse with that setting.
[OnePlus X Original Android Development] Kéno40:
Don't know. never see this setting.
[OnePlus X Original Android Development] eng.stk:
blu_sp★rk r142

All right crew!

New builds are up, go get it!

I added some tunables to control kernel level thermal driver.

As you know, stock camera HAL depends in userspace Thermal Daemon, but if you use Sultan camera HAL or just want a better thermal management you can activate the custom thermal driver.

If you use blu_spark kernel in Sultan CM13, you must turn this new driver on in Kernel Adiutor, because this ROM doesn't use the stock Thermal Daemon.

I added a file you can use to deactivate the userspace thermal driver and use the custom one, just copy the 99_thermal.txt to /su/su.d (if using systemless SuperSU) or to /system/su.d (if using regular SuperSU install). Then rename the file to 99_thermal.sh, give 777 permissions and reboot.

I also updated TWRP 3.0.2.-1 | blu_sp★rk v37 with this new changes.

CM build is also updated, this is made for Marshmallow 6.0.1 ROMs.

I decided to take CM build from beta, but same remains: using custom ROMs you're on your own ;)

If you flash in CM 12.1 you will find broken stuff, just use an old build (r98).

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 X Original Android Development] dingermtb:
Just wanted to say thanks because i've reached my "Thanks" limit today, so thought I'd post it. I hate that rule, lol
[OnePlus X Original Android Development] robwleack:
Hi

Just flashed 142 on OOS 2.2.1 and my wifi keeps disconnecting after about ten seconds.

Any ideas?

Rob
[OnePlus X Original Android Development] mafioso16:
Thanks for the new version!

I'd like to ask a rather nooby question, I am using Sultan's HAL Camera, what does the custom thermal driver do exactly?

Thanks in advance, best wishes! :)
[OnePlus X Original Android Development] neopbm:
No problem with #142 and wifi here. Same Oos version as you.
[OnePlus X Original Android Development] robwleack:
Thanks, I'll have a bit of a poke around. It's probably just my router, but seemed coincidental that I'd just installed the kernel.

I was getting shocking battery on v140 so hoping it has improved with v142. Only went back to OOS today after six months with CM13, so maybe I just don't remember how the battery was in OOS.

Cheers

Rob
[OnePlus X Original Android Development] eng.stk:
Nope all good.

Better thermal control (you can change tunables).

In general I find kernel level drivers more efficient also and just made it so people can choose from.
[OnePlus X Original Android Development] neopbm:
If I use the non stock thermal driver, in camera app switching from back to front is slower. Does anyone notice that to?
[OnePlus X Original Android Development] eng.stk:
Anyone reads the release notes? No.
[OnePlus X Original Android Development] neopbm:
Well I have read your post but I didn't know that what you wrote here was about that. Don't know what HAL mean. My English is not perfect.

Thanks anyway
[OnePlus X Original Android Development] Part.0:
hey sir [MENTION=3873953]eng.stk[/MENTION] i don't use Sultan HAL, so do i need to flash the new build for good?
[OnePlus X Original Android Development] ptblad:
I don't usually care about benchmarks, but lately I've had the feeling that my OPX with OOS was smoother than ever for each iteration of bluespark kernel. Ran antutu and got 10k above what I used to get, confirming the improvement. Thanx alot [MENTION=3873953]eng.stk[/MENTION] for giving it to us
[OnePlus X Original Android Development] eng.stk:
You should always flash the latest version
[OnePlus X Original Android Development] W!ld:
dirty flashing the update will be ok?
[OnePlus X Original Android Development] neopbm:
Yes, no need to wipe anything to flash a new kernel version.
[OnePlus X Original Android Development] ashwinpilgaonkar:
[MENTION=3873953]eng.stk[/MENTION] does your kernel also include the fixes that Sultanxda has added into the stock kernel that comes with his ROM?

Like these-

Kernel:

*Fixed overexposure when capturing images with flash (images taken with flash look much nicer now)

*Flashlight is now 2x brighter

*Added various security fixes

*Fixed some random reboots

*Fixed touchscreen issue where the capacitive buttons at the bottom would mistakenly get pressed while scrolling

*Added an 8th thermal throttle zone
[OnePlus X Original Android Development] Part.0:
from the release notes i know this shouldn't have affected the device thermal throttle thing if i used stock thermal driver by default. but somehow, my opx gets warm to a bit hot so easily even when browsing, chats, or watch streaming for just couple mins using LTE (conn. is excelent). its not significant, but in previous r140 had no such 'exp' like this. i'll wait for further, if i still facing the same issue, i will swith back to r140.

(done wipe dalvick/cache, reboots,etc) ~stock oos 5.5.1
[OnePlus X Original Android Development] eng.stk:
There's some CAF and upstream stuff merged, some CM mods are in but other hw modifications I will not merge.

Some stuff I don't agree with, other are ported from OPO and I don't think we need it.

Some modifications I tested in earlier brings issues so I will not merge them.

Take that thermal driver: It's damn overkill, the simpler the better. MSM driver works fine.

There's no kernel changes that would make that. You must find the culprit elsewhere.
[OnePlus X Original Android Development] Exodusche:
I am never disappointed with this kernel. It just keeps getting better and better. A must on any of my cm13 ROMs. :D
[OnePlus X Original Android Development] jonrodz:
So I'm using bluspark 142 with dirty unicorns. I want to use custom thermal driver but I noticed that there was no su folder, so I created one, is that ok? Inside su folder created su.d and copied the txt in it. Gave 777 permissions and rebooted but after that, the folder disappeared, is that ok? Also can someone explain a little better what's that difference between systemless supersu and regular supersu install. Dirty unicorns flashes supersu zip automatically after rom flashes. Is that systemless supersu? Thanks, [MENTION=3873953]eng.stk[/MENTION]
[OnePlus X Original Android Development] eng.stk:
Ask you ROM developer and search SuperSU threads.

Systemless install creates automatic the the /su folder and inside is the su.d to put scripts.

If regular Supersu is used you need to create the /system/su.d folder
[OnePlus X Original Android Development] :
[MENTION=3873953]eng.stk[/MENTION],

Is there a list of sysfs tunables we can use to change kernel behaviour from an init.d script? (like the 99_thermal.sh script you provided earlier)
[OnePlus X Original Android Development] nihilista:
Just for better understanding, i'm using kernel adiutor and have 3 switches: Intellithermal, kernel control and VDD limitation. So if i disable intellithermal, enable kernel control is that OK or do i have to use the script in addition? And what if i enable intellithermal (and disable kernel control)?

I have sultans camera installed, but not his cm13 build (on RR here).

I found it bit confusing (camera hal, userspace thermal and kernel thermal....), maybe i misunderstood something, but maybe you can help? ;)
[OnePlus X Original Android Development] :
If I understood eng.stk correctly, you can either enable the Intellithermal and core control options in Kernel Adiutor or you can use eng.stk's script. It's the same end-result.
[OnePlus X Original Android Development] eng.stk:
Those 2 are the ones to enable, but actually if enabling the kernel driver without setting off the thermal daemon it will have both running and this is not optimal.

Using the provided script is the best.
[OnePlus X Original Android Development] eng.stk:
You have some sysfs in /sys/module and /sys/kernel

Searxh on my N5 thread, there's so.e info on that.

Kernel Adiutor git also have lot's of tunables paths
[OnePlus X Original Android Development] nihilista:
OK, thx, thats what i wanted to know :good:
[OnePlus X Original Android Development] hearmeart:
it's good on H2OS but i try the CM shocked really2 the kernel so powerful perfomance

i change the core minimum = 1

the core active minimum = 1

(it's work on H2OS and very2 smooth and save my battery)

but i try in CM

The core is stay at 22xx Mhz! (one core)

my Battery drain :(
[OnePlus X Original Android Development] eng.stk:
Using only one core is pointless.

You probably have a higher average load on CM that's why it spikes more. Or you have a locked task that hogs the CPU.

But nothing to do with kernel.
[OnePlus X Original Android Development] Exodusche:
Battery life is great. Running smooth like a criminal. ;)
[OnePlus X Original Android Development] eng.stk:
?

https://youtu.be/CDl9ZMfj6aE
[OnePlus X Original Android Development] TarushS:
Thermal driver

Is it possible to enable custom driver when you don't have SuperSU but root enabled from the ROM (selinux enforcing) ? Or I have to flash SuperSU ?
[OnePlus X Original Android Development] tet-bundy:
Sorry i can not answer this. However i wonder why not to install supersu...
[OnePlus X Original Android Development] eng.stk:
init.d is deprecated since lollipop, probably it won't work.

flash SuperSU and follow the instructions if you want to test the kernel thermal driver.
[OnePlus X Original Android Development] FabioSan:
Hey dude, the last version of your kernel for cm based Roms cause wifi network to go on off continuously :/ I have founded this problem on purity rom :/

Inviato dal mio ONE E1003 utilizzando Tapatalk
[OnePlus X Original Android Development] piotrpan:
Cant confirm that on different wifi routers.

Gesendet von meinem ONE E1003 mit Tapatalk
[OnePlus X Original Android Development] eng.stk:
No, it doesn't.

Latest CM changes on wifi and network managemen probably are merged in that ROM and cause that.

Don't post this kind of stuff without logs or development based info.
[OnePlus X Original Android Development] dingermtb:
Using CM based on Exodus ROM and no wifi issues. In fact, no issues at all. Works perfect, as always?

Sent from Outside the 9 using my Zombiefied Exodus SGS3
[OnePlus X Original Android Development] FabioSan:
Another question:

Isn't Blu_active a bit too much aggressive?

I see also no input boost and similar :o

Inviato dal mio ONE E1003 utilizzando Tapatalk
[OnePlus X Original Android Development] eng.stk:
No, blu_active is perfectly balanced.

If you think it's qgressive by default, turn on fastlane... be careful, your phone can run from your hands lol

Input boost works fine.
[OnePlus X Original Android Development] FabioSan:
Input boost isn't shown on kernel adiutor xD

Inviato dal mio ONE E1003 utilizzando Tapatalk
[OnePlus X Original Android Development] eng.stk:
You need glasses.

boostpulse_duration is the duration os the boost.

input_boost_freq is the input boost value.
[OnePlus X Original Android Development] FabioSan:
Usually I see on the main cpu screen, forgive my error xD

Inviato dal mio ONE E1003 utilizzando Tapatalk