yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] 1+3_FA:
Ok again, I know some of you will hate me for that question, but I cant find a plausible answer or solution. :crying: And I really want try blu_spark kernel

Why stays The frequencies of CPU on Max clock??

I reflashed kernel and the problem stays.

Is there a trick to solve that Problem or not?

I know many many other users have this issue, too.

So please somebody can help? I read about 30 pages The Last hour, but can't get any solution.

Thanks in advance! :good:
[OnePlus 3 & 3T Cross Device Development] ungeeked:
Uninstall any kernel apps that you have - KA/EXKM/Anything else

Wipe dalvik/cache

Dirty flash OOS 4.0.2

Flash SuperSU 2.79 stable

Flash kernel

Reboot and leave phone for 10mins

Use cpu-Z to test frequency

If this doesn't fix, you'll have to clean flash.

This issue is due to a number of things (SuperSU beta/permissive mode/ people checking while app optimization is going on/ KA) but definitely not due to kernel itself as you'll find such posts in all kernel thread. Probably post follow-up in q/a thread and more people will help you out
[OnePlus 3 & 3T Cross Device Development] 1+3_FA:
THANK YOU!!! :cowboy:
[OnePlus 3 & 3T Cross Device Development] samisharora:
[MENTION=3873953]eng.stk[/MENTION]-The first post (OP) mentions r79 unifed as current beta version. Should be r49. Time to correct the typo it seems
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Nobody reads the OP...

Some not even the thread a couple pages back, release posts or developer warnings :angel:
[OnePlus 3 & 3T Cross Device Development] dante_nfs:
Actually that made me laugh :) yeah it's correct. And thanks for your quick update man.
[OnePlus 3 & 3T Cross Device Development] mauley:
49 is silky smooth on stock OOS. Good job!
[OnePlus 3 & 3T Cross Device Development] jamesst20:
Hi,

Can you open the camera, take a picture and tell me if it works ? I am using the stock OnePlus camera, and the application close when I take a picture. However, it does save it.

I am just wondering if it is because of MultiROM or the Kernel

Edit : Dirty Flashed OxygenOS Beta 11, flashed this kernel, then SuperSU, then MultiROM. Camera works. I figured out what is wrong, it's when I change the DPI in build.prop to be 480 (default) that it breaks the camera. It's weird because it's the default DPI, but MultiROM, somehow, changed the DPI to something ugly and it's the only fix I have...
[OnePlus 3 & 3T Cross Device Development] Mar-cel:
Restore Boot and system is enough if what happens or I would revert back to stock Kernel?
[OnePlus 3 & 3T Cross Device Development] Midomad:
AFAIK,Boot is enough.
[OnePlus 3 & 3T Cross Device Development] deecept:
Unsure if it has been thouroughly answered yet, but ifyou are stuck with no wifi / wifi disabled (hello search phrases! =) - Flash the blu_spark TWRP v14 (op3) or v15 (op3t), and then the kernel again. That should fix it rightup.

You'll find the downloads in the same page you downloaded the kernel :) GLHF!
[OnePlus 3 & 3T Cross Device Development] Chaplan:
If you want to help others you should get your facts right.

First - There is no problem whatsoever with Blu_spark and Wifi. If you lost wifi either you flashed something you shouldn't or have not flashed on the right order.

Second - Blu_spark TWRP is V15 for both the OP3/3T devices as it is now a unified build, like the kernel is also.

Last but not least, if you root your device you should always Flash ROM, SU and Blu_spark in this exact order.

Most problems reported on the thread have been because people have flashed kernel and rooted after that.

If you need to root and have not done it prior to flashing the kernel you should go back to stock kernel and then flash in the correct sequence. (If you don't have a backup of original boot.img you can extract it from the ROM or you can just dirty flash it)
[OnePlus 3 & 3T Cross Device Development] eng.stk:
I might add that most of "wifi issues" comes from dirty boot.img from other kernel installs and system with "stock boot and system" that in the end was with magisk and module x y z and whatnot.

Not to mention the " kernel makes my freq stuck at max" and "my device is hot after flashing kernel" that is said 1000 times not to be kernel related.
[OnePlus 3 & 3T Cross Device Development] FishyFing:
Just a quick word of warning to anyone using Magisk.

If you update to v11+, it may remove your ability to use wifi with this kernel installed (not the kernels fault), so make sure to reflash kernel after the system has booted back up!
[OnePlus 3 & 3T Cross Device Development] mauley:
I am on magisk v11 and blu spark v49 and still have WiFi
[OnePlus 3 & 3T Cross Device Development] FishyFing:
huh, weird. i believe it had something to do with the su binary being changed, but if you updated before r49 came out then i guess you wouldn't have the problem, as flashing r49 would have fixed it
[OnePlus 3 & 3T Cross Device Development] mauley:
I already had v49 installed then updated magisk binary to v11. What I did do was uninstalled magisk v10.2 fist using the uninstaller then installed v11 fresh over blu spark v49.
[OnePlus 3 & 3T Cross Device Development] Sytis:
But my device is seriously hot after I flashed the update. I mean it's super f***ing smooth and sexy so it became hotter than my gf :p

No seriously, I'm worried that there won't be any further updates because it's so near to perfection :crying:
[OnePlus 3 & 3T Cross Device Development] paratox:
omg omg omg, my alarm did not ring this morning on r49. same setup as on r37, r41, and r47 but did never happen on this builds.

now i have to make a hard joice. have working alarm and slow device or insane speed and come too late to work. it`s really a hard joice! ^_^

alarm app is excluded from OOS aggressive doze. what could i do to work around this bug? i have all gestures and pocket mode enabled, maybe change something in this direction?
[OnePlus 3 & 3T Cross Device Development] FishyFing:
if it doesn't work with aggressive doze, turn it off!
[OnePlus 3 & 3T Cross Device Development] Primokorn:
I still have WiFi with Magisk v11.1 and blu_spark r41... Updated from Magisk Manager.

EDIT: oops, too late. I don't have the latest blu_spark version so I'll leave it here lol
[OnePlus 3 & 3T Cross Device Development] teldasur:
You need to disabled pocket mod and kernel adiutor if you use it... No problem since I disable pocket mod.
[OnePlus 3 & 3T Cross Device Development] Konskl:
[MENTION=3873953]eng.stk[/MENTION] i know you've said that only /data is formatted in f2fs in OOS but right now i'm using f2fs in /cache as well... any side effects to that? to my experience i've not noticed any weird behaviour. Thanks
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Format it? Yes.

Use it? Nope.
[OnePlus 3 & 3T Cross Device Development] Konskl:
Ye "format". Are there any side effects with /cache in f2fs?
[OnePlus 3 & 3T Cross Device Development] marf28101995:
He already answered mate why asking the same thing twice
[OnePlus 3 & 3T Cross Device Development] forcedairinduction:
Hi all. I accidentally flashed an earlier version of the kernel (didn't read post about newest build being in op3 thread, used the one from op3t) and performance was worse than stock, my bad!. I'm going to try r47 build now. I'm on stock ROM/kernel so can I just flash kernel or do I still need to flash SuperSU also?. Thanks :) I'm on op3t btw
[OnePlus 3 & 3T Cross Device Development] marf28101995:
SuperSU is optional you just flash if you need/use root and if you do be sure to always flash in the right order ( before the kernel)
[OnePlus 3 & 3T Cross Device Development] Konskl:
Pardon me, but the way the answer was given i couldn't understand it.
[OnePlus 3 & 3T Cross Device Development] forcedairinduction:
Thanks man. I am rooted already so just flash SuperSU again, then kernel

---------- Post added at 11:35 AM ---------- Previous post was at 11:19 AM ----------

I'm still learning. So a different kernel would knock out su?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
You can't use f2fs in OOS for cache.

This has already been discussed, search is your friend.

If you have stock kernel and ROM already rooted just flash blu_spark, don't need to re-root.

If you are in all stock and want to root, just be sure to flash root before flashing kernel zip.

If you come from another anything, dirty flash your ROM blablabla...

SuperSU zip after flashing custom kernels tend to restore stock boot img and derp your setup.

Instructions are in OP and have been discussion several times.

Use the search button people, damn laziness.
[OnePlus 3 & 3T Cross Device Development] vatsal8286:
r49 is stable or beta?
[OnePlus 3 & 3T Cross Device Development] lxxs:
Stable as a big rock in the mountains.
[OnePlus 3 & 3T Cross Device Development] kinfam:
Have you read the OP? Your answer lies there.
[OnePlus 3 & 3T Cross Device Development] vatsal8286:
can i flash r49 over r47?

---------- Post added at 01:27 PM ---------- Previous post was at 01:26 PM ----------

can i flash beta over the stable one?
[OnePlus 3 & 3T Cross Device Development] kinfam:
Yes. I prefer a clean kernel flash always but you can dirty flash.

*Edited for clarity *
[OnePlus 3 & 3T Cross Device Development] nmlssit:
Clean flash? For kernel updates? wtf
[OnePlus 3 & 3T Cross Device Development] Explorer23:
Yeah, clean flash for each kernel update is a bit too much, only do that if you face problems.

For those scared of dirty flashing, flashing stock kernel and then new version of custom is more than good enough, no need for extreme measures.
[OnePlus 3 & 3T Cross Device Development] kinfam:
I flash my rom via TWRP, then root, then kernel, not completely wipe my phone.

*note* it's a small rom (OOS), if it was larger I would just flash boot.
[OnePlus 3 & 3T Cross Device Development] nmlssit:
I always flash new ones over the olds, do I need to flash stock in between?

---------- Post added at 02:00 PM ---------- Previous post was at 02:00 PM ----------

Then you are dirty flashing, not clean
[OnePlus 3 & 3T Cross Device Development] Explorer23:
Not really ☺️

That's kinda an option between fully clean flashing and completely dirty, but dirty is fine for a kernel update.

Any "safer" method than dirty flashing is only necessary for bigger changes, like going for a different custom kernel. Or possibly if there are any major changes, but in that case the dev will probably say something about advised procedure.

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

If you mean data by wiping - that really has nothing to do with ROM and kernel stuff. And that's too much hassle for minor kernel updates.

I mean, it won't hurt anything, but you're doing more work than you need to.

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

Dirty, but it's dirty flashing whole ROM (which makes it clean for kernel), while only dirty flashing kernel would be enough.
[OnePlus 3 & 3T Cross Device Development] kinfam:
I guess I should of been more specific, clean flash kernel by dirty flashing rom, which replaces the boot.img with the stock boot.img. It's just a habit, but because my rom is so small it's worth the extra minute or two IMO, and if I come across issues I can strike that one off the list. Old SQA habit I suppose :)

Sorry for OT comments!
[OnePlus 3 & 3T Cross Device Development] Explorer23:
Yup, got it, just wrote my answer a bit weirdly (fixed it now).
[OnePlus 3 & 3T Cross Device Development] forcedairinduction:
Hi all. Not sure if I'm being a dufas but I've flashed kernel, downloaded kernel auditer but can't get it to work. It just sits saying 'collecting info'. Been doing it for an age. Tried re downloading it but same thing is happening :/

Is trixter mod compatible
[OnePlus 3 & 3T Cross Device Development] ggkameleon:
Hi ! Sorry just a precision my Rom are Root but if I flash my Stock Kernel Boot.img that remove SuperSu ? You said Flash SuperSu !?

Thank's
[OnePlus 3 & 3T Cross Device Development] vVJokervV:
did you grant root acess?
[OnePlus 3 & 3T Cross Device Development] forcedairinduction:
Doh!, sure I replied earlier :/ er no I didn't grant root access, it didn't request it. I thought the requests happen automatically?. Still new at this :)
[OnePlus 3 & 3T Cross Device Development] Krissyzen:
hello. thx for the kernel. Its very cool but where can I find any changelogs? are there any changelog thread/site/app??? or search tag? or should I just shut up and flash the newest version? ?
[OnePlus 3 & 3T Cross Device Development] kinfam:
Is your device rooted??
[OnePlus 3 & 3T Cross Device Development] forcedairinduction:
It is indeed mate
[OnePlus 3 & 3T Cross Device Development] AcmE85:
In the OP there is a link to the source code. Additionally [MENTION=3873953]eng.stk[/MENTION] posts the changes with every updated kernel inside the thread.

This is the mentioned kernel source which shows his kernel commits:

https://github.com/engstk/op3t/commits/blu_spark
[OnePlus 3 & 3T Cross Device Development] Klobal:
Search for wicked!
[OnePlus 3 & 3T Cross Device Development] GiovanniArpino:
Hi, what do you think [MENTION=3873953]eng.stk[/MENTION] to add voltages control to your amazing kernel?It would be really useful!
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Awesome answer! Wicked xD

Nope.
[OnePlus 3 & 3T Cross Device Development] paratox:
i was just caught in the lockscreen and unable to unlock the device. fingerprint sensor and swipe up to unlock did not react. power and volume buttons did work. pocketmode was disabled. only way to get it back working was a hard reboot with power button.
[OnePlus 3 & 3T Cross Device Development] cultofluna:
Have you set aggressive doze.....?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Nothing I can do for you.

Also your log is all garbled, use pastebin next time.
[OnePlus 3 & 3T Cross Device Development] 1+3_FA:
[MENTION=2370700]paratox[/MENTION]

Do you use naptime / greenify? Aggressive doze could be the reason for that
[OnePlus 3 & 3T Cross Device Development] paratox:
only inbuilt OOS aggressive doze. the strange thing is until r47 i had not a single problem with the same setup.

on r49 i got a missed alarm and this lockscreen thing. maybe i should try a clean flash.
[OnePlus 3 & 3T Cross Device Development] Primokorn:
The search feature doesn't work on my PC so sorry if the answer has already been given.

What are the differences between the OOS and Custom builds? I'm still on r41 until you provide the custom versions of the latest build.
[OnePlus 3 & 3T Cross Device Development] marf28101995:
Non need to search

Just read the OP lol

Custom for custom Roms

Oos for stock oxygen ( oos based Roms)
[OnePlus 3 & 3T Cross Device Development] 1+3_FA:
I would say oos build for OOS Rom

And custom build for custom rom ;)
[OnePlus 3 & 3T Cross Device Development] mrmcshagbag:
Same thing happened for me this morning after upgrading to r49. Clean flash is probably all we can do.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
OOS version is for OOS ROMs and it's wait I daily drive, so it's updated more often.

I don't always update the custom version, only when needed.

But hold on tight, soon...
[OnePlus 3 & 3T Cross Device Development] kiki059:
Hi guys

What a the best kernel manager for this kernel ?
[OnePlus 3 & 3T Cross Device Development] marf28101995:
Kernel adiutor

Pro tip: use search next time
[OnePlus 3 & 3T Cross Device Development] Facebooook:
How to set vibration intensity manually with root explorer ? and how to know where KA set the value ? any app who show that parameters where value change ?
[OnePlus 3 & 3T Cross Device Development] Sytis:
According to Kernel Adiutor it's under /sys/class/timed_output/vibrator/vtg_level
[OnePlus 3 & 3T Cross Device Development] cultofluna:
With EX kernel manager you can adjust vibration intensity...
[OnePlus 3 & 3T Cross Device Development] Primokorn:
Well I know that for years :p you misunderstood me or my questions wasn't clear enough.

I mean which modifications have to be done to release the same version for custom ROMs.
[OnePlus 3 & 3T Cross Device Development] marf28101995:
Follow lineage os upstream stuff
[OnePlus 3 & 3T Cross Device Development] a1ien.n3t:
Hello.

May I ask to enable CONFIG_IP_NF_TARGET_TTL?
[OnePlus 3 & 3T Cross Device Development] skyknife93:
Guys, I'm really sorry if this is a noob question, but I'm kinda worried. I used to be on oos ob10, data partition on ext4, Blu spark r47, twrp v15. Today after getting back home I wanted to try ob 11 and f2fs. So I did a wipe, changed data partition to f2fs, flashed ob11 , SU, and Blu spark r49. But now when I connect my phone to my PC, it shows shared internal storage and it's already filled to around 5gb even though I removed everything. Did I do something wrong. Sorry for the OT and please don't kill a baby seal. I'm just worried

It used to show up as just internal storage before. And shows 48.3gb free of 53 GB. Is that just normal or did I do something wrong in the above process.
[OnePlus 3 & 3T Cross Device Development] snippem:
https://github.com/OnePlusOSS/andro...mmit/5fc90890d4fad758911e9cc9998d4347b06f9073 [MENTION=3873953]eng.stk[/MENTION]
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Why you need this?

I don't like to add cruft and stuff I don't personally need.

A ROM after setup uses storage, already has apps and so on on it.

Also, f2fs uses more space for the same stuff compared with ext4.
[OnePlus 3 & 3T Cross Device Development] skyknife93:
Firstly, thanks for your fast response. That had me worried for a bit as I saw it showing up in internal storage (48g out of 53gb) even tho I had nothing on it. So it's ok then?

Secondly, it's great to be back on your kernel. I've used it on my Nexus 5 and I've loved the experience. It's one of the reasons I bought this phone actually.

Your work is epic and I thank you for it. I'm due to start my job in two months and as soon as I get my first paycheck I'm gonna donate:)

Thank you for an epic kernel
[OnePlus 3 & 3T Cross Device Development] nmlssit:
No issues with 4.0.3?
[OnePlus 3 & 3T Cross Device Development] fureshyu:
are you not supporting custom roms anymore with the latest kernel?
[OnePlus 3 & 3T Cross Device Development] NickosD:
Use the search tool to find your answer.
[OnePlus 3 & 3T Cross Device Development] frikakwa:
4.0.3 + Magisk 11.1 + Blue 49... so far so good (PoGo, Snapchat, Android Pay, Kernel Adiutor...)! :D
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r55 unified

All right crew!

New build is up. Wicked!

Because of unified TWRP changes, you will need to use latest TWRP build from xda thread or flash my TWRP 3.0.3-x blu_spark v16 (recommended).

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

This features latest OOS 4.0.3 codedrop, so I also updated twrp kernel.

The custom build on LOS has a bug when battery saver kicks in (lockup). Set performance profile to performance and back to balanced adn reboot if you encounter this.

I troubleshoot it a bit but couldn't find the culprit. Other ROMs battery saver like OMNI for instance works fine.

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

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

I am only interested on debugging stuff in 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] ungeeked:
Just in time. Was about to clean flash OOS 4.0.3 :D
[OnePlus 3 & 3T Cross Device Development] owaisnaim:
Is it only me or twrp v16 is not booting!
[OnePlus 3 & 3T Cross Device Development] Dieppy:
All fine here
[OnePlus 3 & 3T Cross Device Development] laupuy:
Hi,

works fine here

;)
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Is it just me or are you making a little confusion with the official TWRP? [MENTION=3873953]eng.stk[/MENTION] V16 TWRP is the one that boots in less than no time. (As did all the previous builds)

The official TWRP is reported to take less than a week to boot though, at least is what I read on the official thread...
[OnePlus 3 & 3T Cross Device Development] nihilista:
...and is it safe to boot, flash and backup with all newest oos4 or custom rom?are there advantages over official 3.0.4-1 twrp? I'm not sure which twrp works better...
[OnePlus 3 & 3T Cross Device Development] vVJokervV:
Why is there an R55 custom in the download aera? Where is the diffrence to the other one?
[OnePlus 3 & 3T Cross Device Development] laupuy:
Hi, it's for custom rom, the other one is for OOS

;)
[OnePlus 3 & 3T Cross Device Development] vVJokervV:
? and why is now the 2 versions? Previously there was just one unified zip file.

I know, one for custom. But where is the main diffrence?
[OnePlus 3 & 3T Cross Device Development] core_x:
No. It has always been that way.
[OnePlus 3 & 3T Cross Device Development] vVJokervV:
Not so for version 47 + 49!! There is just one "oos"!?
[OnePlus 3 & 3T Cross Device Development] habylab:
Great kernel so far! I always want a kernel that has a lot of tweaks to it, but not highly experimental. This is it!

---------- Post added at 10:38 PM ---------- Previous post was at 10:35 PM ----------

Why hello there again!
[OnePlus 3 & 3T Cross Device Development] Bradl79:
It does support, I was trying not to mention the other kernel, but with elementalx the install is with aroma which u set the desired frequency and settings u want in aroma and it sticks after reboot, so I was asking to do this one as aroma too so it sticks after reboot instead of relying on the kernel app to do so which majority of the times it does not apply, i like what this kernel has
[OnePlus 3 & 3T Cross Device Development] thelad:
When I flashed the latest for oss I lost supersu,tried few different ways and its not sticking, just to clarify do I flashed rom->>blu_spark-->>superSU??
[OnePlus 3 & 3T Cross Device Development] liver20:
I am in stock 3.2.2 rooted, later flash this kernel, the answer is awesome

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] 1ceb0x:
Sorry but I am standing by what I said, unless stated otherwise by the developer of this kernel - i do not think this kernel supports underclock. Cpu freqs not sticking after boot mostly appears in this situations.

Aroma or no aroma installer, it doesn't matter.

And anyway, lowering your cpu freq is useless if the voltage values are the same (i.e running min cpu at 133 mhz but with voltage values of 300 mhz), which should be the case here as there is no VDD support as well :)
[OnePlus 3 & 3T Cross Device Development] Konskl:
ahhhhhh thank god i thought i was the only one. I clean flashed stock oos (freedom oos). Flashed the oos -->bluspark-->supersu and i can't make it to stick. I can't get root no matter what i did. Just to clarify are u using f2fs on /data and /cache or stock ext4?
[OnePlus 3 & 3T Cross Device Development] Flamehell:
Freedom oos has is own supersu.....you don t need to flash it another time.....;)
[OnePlus 3 & 3T Cross Device Development] thelad:
But the superSU isn't sticking though
[OnePlus 3 & 3T Cross Device Development] Flamehell:
Better speak about that on the freedom oos thread.....;) anyway it's strange.....:(
[OnePlus 3 & 3T Cross Device Development] thelad:
I clean flashed that freedom os then blu_spark ,and once it booted had no superSU,so factory reset and still nothing

---------- Post added at 11:18 PM ---------- Previous post was at 11:15 PM ----------

True but only when flashed this kernel,so freedom mustn't be playing well with blu_spark or other way round
[OnePlus 3 & 3T Cross Device Development] RJMacReady:
FreedomOS, OP3Lite, and StockOS are basically the same. They're just variations of stock. I don't see how it would affect anything.