yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] otonieru:
Then check your CPU time table,

which frequency used most in overnight time ? Maybe it's stuck on certain "too high" frequencies

have you wiped dalvik n cache?
[OnePlus 3 & 3T Cross Device Development] habylab:
Deep sleep is 90%, so it isn't stuck on anything, LITTLE is on 68% now but I suspect that is because I've been up for two hours.

Already wiped the caches, yep.
[OnePlus 3 & 3T Cross Device Development] habylab:
Really? What are your settings with the kernel - have you made any changes, and if so, what? Thanks.

Edit: completely forgot I rebooted before I went to sleep, as I made some root changes that needed a reboot. So perhaps I have 4 hour screen on time still! Apologies.
[OnePlus 3 & 3T Cross Device Development] Neuz:
Power nap and smart network switch.

Tapatalked from my OP3.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
You can track my release posts, otherwise check my git
[OnePlus 3 & 3T Cross Device Development] habylab:
What's the top image, are they limited or not?

Also, Power Nap gives you no notifications or network connectivity on screen off, right? If so, that's not for me. I'd just like 4% drain per night again.
[OnePlus 3 & 3T Cross Device Development] 1ceb0x:
Not sure about powernap but I use Naptime and I get notifications when screen is off and they both work under the same principle.

Just flashed this baby on top of Freedom OS 3.2.2 and I can confirm that root is working as before (for those that were complaining about losing root).
[OnePlus 3 & 3T Cross Device Development] Neuz:
No my bad, first image is for another thread :)

BTW I've all the notifications up when screen is off. Power nap is a similar to force doze but disactive motion sensor when goes into doze mode.

Tapatalked from my OP3.
[OnePlus 3 & 3T Cross Device Development] Konskl:
You know I actually managed to flash it but i can't get it to work with f2fs filesystem. In the end I managed to flash the kernel by switching back to ext4. Are you using ext4 or f2fs on /data partition and /cache?

---------- Post added at 11:15 AM ---------- Previous post was at 11:12 AM ----------

I was complaining about losing root but the problem was the f2fs filesystem. When i was flashing supersu with f2fs /data and /cache the flashing was forcefully aborted. Don't know why, cause supposedly this kernel lets you use f2fs. When i reformatted the phone to ext4 everything worked as it should.
[OnePlus 3 & 3T Cross Device Development] habylab:
All your notifications come through as normal? That's interesting.

Power Nap is the same as Naptime with Disable Sensors and Greenwich's Doze On The Go option, afaik.

Anyway, back to the kernel. I'm experiencing weird issues when tinkering with the screen settings, it seems washed out even after reverting changes? A reboot fixes it, though.

And you have Aggressive Doze and Disable Sensor both on? Or not? Just interested what your settings are for Naptime, to see how you get notifications.
[OnePlus 3 & 3T Cross Device Development] 1ceb0x:
I don't use agressive doze. I tweak my own settings as follows:

Sensors inactive timeout: 900

Idle after inactive timeout: 900

This will make doze to kick in faster but will still get your notifications while screen is off.
[OnePlus 3 & 3T Cross Device Development] nihilista:
So system_image is the partition to backup and restore (even if modifications made like magisk and some modified files in /system)? And whats the difference to backup/restore only system?

thx
[OnePlus 3 & 3T Cross Device Development] fbf2201:
One is image wise the other one file wise, I assume.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
First page of what? This is kernel thread mate...

OMNI like in source for TWRP binaries, not the ROM.

But thanks for the heads up, I'll take a look when/if I have the time :good:

When backing/restore OEM partitions like OOS you should use 1:1 block image backup so you can apply OTA and make 1:1 backups. And all will be good.

I should remember (yet again) that this is not a TWRP thread and my personal recovery is shared like it is.

Feel free to use anything else. It will be no discussion on it.
[OnePlus 3 & 3T Cross Device Development] nihilista:
Ok, thats what i wanted to know, sorry for bit OT, didnt want to discuss something ;)

thx
[OnePlus 3 & 3T Cross Device Development] anjo88:
I use last version off kernel with experience rom 13 clean install and kernel is draining my battery is there any fix?

Enviado do meu ONEPLUS A3003 através de Tapatalk
[OnePlus 3 & 3T Cross Device Development] ungeeked:
First of all, Kernel doesn't drain battery. Your os/settings/network is responsible. So your query will be better dealt with in ROM thread.
[OnePlus 3 & 3T Cross Device Development] Sytis:
First: There is no support for custom ROMs.

Second: Is this the first (or one of the first) charging cycles? If yes: Let the device settle so it properly adjusts everything.

Often the kernel drain is not related to a custom kernel but more of system services accessing kernel features (but correct me if I'm wrong).
[OnePlus 3 & 3T Cross Device Development] eng.stk:
It wasn't particulary torwards you, but in general.

No prob, doubt dismissed, let's move on.

Yep, start by reading the thread.

Kernel doesn't drain anything...
[OnePlus 3 & 3T Cross Device Development] anjo88:
Thank you for the help

Enviado do meu ONEPLUS A3003 através de Tapatalk
[OnePlus 3 & 3T Cross Device Development] ungeeked:
[MENTION=3873953]eng.stk[/MENTION] what are your thoughts on bumping the base Gpu frequency up slightly like OOS (it is using 214 as base). Currently performance is smooth but occasionally there is some stutter in animations
[OnePlus 3 & 3T Cross Device Development] immi803:
I feel 100 base is fine, any higher frequency is available when needed...

Just my thought, thanks
[OnePlus 3 & 3T Cross Device Development] eng.stk:
If I went from that to the min level, why would I go back?

I doubt you would feel any difference in animations with such change (in games maybe a bit).

100 is slumber (standby), first duty freq is 133 ;)
[OnePlus 3 & 3T Cross Device Development] liver20:
[MENTION=3873953]eng.stk[/MENTION] Why Big cluster max frecuency is 1062mhz and cannot upgrade

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Let me check...

[IMG="mage"]https://s-media-cache-ak0.pinimg.com/236x/0a/79/e8/0a79e8730e1031bf7021a26c7014013e.jpg[/IMG]
[OnePlus 3 & 3T Cross Device Development] Flamehell:
:laugh::laugh::laugh::laugh::laugh::laugh::laugh::laugh::laugh::laugh: Own it!!
[OnePlus 3 & 3T Cross Device Development] liver20:
[emoji23] [emoji23] [emoji23] [emoji23] sorry , rom problem

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r64 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 v20 (recommended). Any other version will not have full support for the kernel and the installer.

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.

No mirrors allowed.

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] eng.stk:
TWRP blu_spark v20

All right crew!

Here's an updated TWRP with all the blu_spark goodies inside and fully synced with TWRP Android-7.1 branch (including more recent upstream than official TWRP).

This has lot's of fixes inside, including this (which is related to libtar upstream needed fixes and not make_ext4fs binary [MENTION=5767887]NevaX1[/MENTION])

I'm just sharing my personal recovery build since people asked, meaning no support will be given

If your cat get's on fire you're on your own ;p

No mirrors allowed.

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] sator02:
Thanks for the updates

Sent from my ONEPLUS A3010
[OnePlus 3 & 3T Cross Device Development] MarcTremonti:
i have experienced this logcat spam (E QMI_FW : xport_reg Failed for service_id=0x35 version=0x1001 on 10) after restoring a nandroid (system, data) incl boot.

does it mean also restoring works fine now?
[OnePlus 3 & 3T Cross Device Development] android extreme:
Hi eng.stk thanks for the update i have just a question: all the partition are mounted with NOATIME option? I heard that this type of mount could improve significantly the filesystem performance
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Sure.

Yep since ages now.
[OnePlus 3 & 3T Cross Device Development] westkone:
oos one is for all OOS based ROMS (stock and custom like Freedom or Aurora)

custom is for all other customs (LOS, RR, AOSPX, OctOs...)

Tip : it has already been answered in previous posts ;)
[OnePlus 3 & 3T Cross Device Development] Lownita:
Yes.

It's 100% compatible with los based roms, might have some quirks on aosp based roms (eg gestures not working).
[OnePlus 3 & 3T Cross Device Development] westenlive:
sorry

help me

i want the smartphone to max performance.

i don't need 10hr display.

i need max performance.

which parameter must set?
[OnePlus 3 & 3T Cross Device Development] Chaplan:
If you go back 13 pages on the thread you can read some points of view from a few of us on this matter as you asked it already then.

Bluactive governor gives you performance when you need it.

You can even overclock Big and Little Cores one step if you feel the need.

I personally find the phone as smooth as it can be with this kernel and it's default settings so performance wise it is as satisfactory as it gets.

The great battery life it gives me is a bonus I get with no performance loss whatsoever.

It's just Blu. :good:
[OnePlus 3 & 3T Cross Device Development] kinfam:
Using the search function, I see that you have asked about this before, and have been given answers in regards to your question...

Even with the phone on "Max" settings, the phone will quickly throttle down to lower clock speeds due to excess heat to protect the phones hardware and yourself. This is NOT controlled by the kernel..

You are more then likely making the performance worse trying to run it 100% than if you just let the phone do its own thing... This phone is not a gaming computer. You can only do so much...

Sorry for slight OT.
[OnePlus 3 & 3T Cross Device Development] :
Thread cleaned.

Forum Rule #1:

Search Before Posting

Also, please treat all members with the same respect you ask for yourself. Most importantly, have fun! :)

The Merovingian

Senior Moderator
[OnePlus 3 & 3T Cross Device Development] FlyingMachete:
On the 8th day a borrowed character of a french actor from an american blockbuster acting as a comics superhero in a nerdy chit-chat opened the sea in half, and a whole bunch of magnetic-wave-cancer-ear-frying-device tweakers took more popcorns from the oven. Good god boyz please don't blame, but the fun I have around you. On-topic: awesome work with the kernel thingy and recovery whatever, I flash'em all, I don't feel no difference, I don't care, it's just awesome, I want new thing coming to swipe my blue bar to. Rule #1 Thou shall not kill the search button. God I'm crying. :'D Thanxx.
[OnePlus 3 & 3T Cross Device Development] :
I lol'd.
[OnePlus 3 & 3T Cross Device Development] Flamehell:
Laos + blu spark...best combo ever!:good: Tnx a lot buddy for your work!
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Actually is LOS, don't know why people think Lineage are 2 words.

But yeah, it's nice ;)

If you have wifi you have wifi wakelocks, if you have FPR you have FPR wakelocks, etc. It's a small value usage, if it was 50% then we would be worried.

I won't call that excessive or drainy, look at you FRP timmings. Do I need to turn it off also?

It's fine as it is.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Already said no.

cpu_boost is enabled that's why you're getting the boosts.

Already been discussed a few times.
[OnePlus 3 & 3T Cross Device Development] Schrotty35:
Themes not work with last twrp.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
ofc search works that's non sense.

0 ms there will be no boost.

Your themes need updating.

Not a problem actually, only them I need is the blu ;)
[OnePlus 3 & 3T Cross Device Development] nihilista:
Try this, that works ;) https://basketbuild.com/devs/z31s1g/Testing/a
[OnePlus 3 & 3T Cross Device Development] aydinbahadir88:
[MENTION=3873953]eng.stk[/MENTION]

Amazing Kernel, battery life is very good ;)

Thank You dev ;)
[OnePlus 3 & 3T Cross Device Development] cloudx720:
What ROM are you driving? ?
[OnePlus 3 & 3T Cross Device Development] aydinbahadir88:
Official RR Rom
[OnePlus 3 & 3T Cross Device Development] cpt.macp:
Can I use this kernel with ext4?

I read something about changing fs to f2fs

I have lost my data 2 times in installing pre encryption data handing like OOS and old LOS

So just wanna know will this work fine with ext4

As f2fs is good for benchmarks results and I don't a rat furry arse about benchmarks.

Latest TWRP handler is itself supporting ext4 over f2fs
[OnePlus 3 & 3T Cross Device Development] DesertVelo:
I converted the data partition to EXT4 for some time now, no issues. I am also encrypted using this kernel and OOS 4.0.3 stock.

Sent from the singletrack...
[OnePlus 3 & 3T Cross Device Development] cpt.macp:
Wait what? Kernel encrypted data? For real ??

I have un- encrypted pseudo partitioned data , ext4 fs.

Don't use encryption. If TWRP updates comes and it messes with the Current OS's encryption libs ( especially with OOS) as they are fkin ****s who claims they are " Dev friendly" but slowly showing true colors . Qualcomm Crypto Daemon used by TWRP always does mismatches because of the different keys used by OOS ( thanks One Plus AGAIN )

No , no encrypting. Simply use decrypted data unless you're are some big arse billionaire and wants encrypted data.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
You can use ext4/f2fs encrypted or un-encrypted, it will work all good.

Kernel doesn't force encryption.

TWRP will use firstly current installed ROM crypto libraries, so it should be future proof.

It goes out to default libraries if all rest fails.
[OnePlus 3 & 3T Cross Device Development] cpt.macp:
Ah sounds swell m8

Thanks for heads up
[OnePlus 3 & 3T Cross Device Development] MyStyle0714:
Can we OC to 2419MHz or above using the kernel?
[OnePlus 3 & 3T Cross Device Development] enzzo28:
I think the highest you could get is 2419...
[OnePlus 3 & 3T Cross Device Development] saberzaid:
It is my first time coming to this kernel . so after open the link there is blue recovery and the kernel etc

I already HV a custom recovery so I only need to download the kernel or I should flash the blue spark recovery first
[OnePlus 3 & 3T Cross Device Development] ungeeked:
It is recommended (but not mandatory) to use bluspark recovery
[OnePlus 3 & 3T Cross Device Development] Funk Wizard:
To flash the latest you need the compatible V20 recovery.
[OnePlus 3 & 3T Cross Device Development] cpt.macp:
3.0.4.1 is also useable .
[OnePlus 3 & 3T Cross Device Development] Funk Wizard:
Blu Spark boots quicker for me as I am on F2FS and it does everything a recovery needs to, just a matter of personal preference though.
[OnePlus 3 & 3T Cross Device Development] cpt.macp:
Obviously because the OP gonna make a custom recovery to make his kernel more compatible

I was using 3.0.4.1 because of updated CAF kernels and f2f2 back port drivers ( well when I was using f2fs been there used that and moved back to ext4).

Since I fked my data 2 times with the retardness of self encrypting roms like OOS ( thanks Oneplus and Again), I said **** it and went back to ext4 as all data was lost .

Whenever I use to install OOS and super SU ( system mode to patch boot.img) it still encrypts the data . So I'm not going to install OOS again now. Or until OnePlus 4 gets a fkin micro sd card because losing data every 2 weeks is surely pleasurable and sweet like honey.
[OnePlus 3 & 3T Cross Device Development] Funk Wizard:
Let's not go OT on this kernel thread, if you want to discuss there is a TWRP and OOS thread. OP already mentioned that he gives no support for recovery.

Let me also assure you I've been testing OOS roms and have always stayed decrypted on f2fs, if you follow the right procedure OOS won't be able to force decrypted.

Apologies again for going OT
[OnePlus 3 & 3T Cross Device Development] cpt.macp:
Oh yes

My bad , if needed I'll remove my reply

Lost my cool sorry lads .
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Been going back and forth from OOS and custom ROMS. Always f2fs, always encrypted. Never lost data in the process.

I always have a backup on the computer just in case.

When you encrypt you should not loose data. It just gets encrypted and is still accessible after that.

Just my insight on this. Might be something on your side.

Blu_spark does not force encryption. But you can encrypt from Android settings with it to. Tested with Blu_spark kernel and TWRP.

No problems whatsoever.
[OnePlus 3 & 3T Cross Device Development] aydinbahadir88:
Very good battery life

Thank you Dev ;)
[OnePlus 3 & 3T Cross Device Development] fossean:
Wifi is disabled if I run r64 with both Viper and MagiskSu. Running Stock OOS 4.0.3, Magisk 11.1. All versions of Viper (without addons).

No problem with wifi if running r64 with just MagiskSu, or r64 with Viper and SuperSu.

No problem with running stock kernel or Elementalx. Custom kernels were installed after reflashing stock boot.img.

Logs attached.
[OnePlus 3 & 3T Cross Device Development] cpt.macp:
Dear sir I didn't point the issue with encrypting I was saying it encrypts the data when the data is unencrypted because of OOS. And kernel does not force encrypt as give in OP .

It's all cool
[OnePlus 3 & 3T Cross Device Development] marf28101995:
Thanks for the logs but no support if you flash other mods other than root as stated in op

Hope you dirty flashed the ROM between all those kernels
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Nothing I can do mate.

Already been discussed about Magisk. It seems some modules/install sequence derps mountpoints.

Search is your friend.
[OnePlus 3 & 3T Cross Device Development] enzzo28:
It's been discussed before, what I did to make wifi work again was to uninstall Magisk, and flash the kernel, then reflash Magisk and finally flash the kernel again..
[OnePlus 3 & 3T Cross Device Development] fossean:
Thanks for replying; I agree with the OP, obviously other mods add further layers of complexity that are not the responsibility of engstk. I don't expect support, I just supplied the logs for information purposes ;)
[OnePlus 3 & 3T Cross Device Development] ahrion:
His current project is to fix compstibility between boot images. If you look at his git
[OnePlus 3 & 3T Cross Device Development] saberzaid:
Is the blue spark recovery support multirom ?
[OnePlus 3 & 3T Cross Device Development] Bearthquake:
I would assume not
[OnePlus 3 & 3T Cross Device Development] BIGWORM:
Nope. Multirom needs the specific TWRP to work properly.
[OnePlus 3 & 3T Cross Device Development] marf28101995:
Before anyone asks

You can flash beta 12 with Blu TWRP

And even better.....

Powa

PS camera doesn't work if you flash latest Blu spark
[OnePlus 3 & 3T Cross Device Development] matheus_sc:
will work in one plus 3t too?
[OnePlus 3 & 3T Cross Device Development] t181:
Are you from the future?
[OnePlus 3 & 3T Cross Device Development] marf28101995:
Pssscht don't tell anybody ;)

---------- Post added at 11:15 AM ---------- Previous post was at 11:14 AM ----------

Should work

Backup boot.img just in case
[OnePlus 3 & 3T Cross Device Development] skyknife93:
[MENTION=3873953]eng.stk[/MENTION] sorry for the OT. Boots with OB12 but, the camera doesn't seem to work when I flashed the r64. Not expecting support either. Just saying.
[OnePlus 3 & 3T Cross Device Development] marf28101995:
Yep camera doesn't work
[OnePlus 3 & 3T Cross Device Development] Chaplan:
With that said we begin a whole new Dejavu Era sourcewise.

If Beta is out sources should be out to.

Can't really understand this policy of OnePlus.

Developer friendly is a beautiful place to be. With one foot in and the other out in their case.

No Source no dance. Takes two to tango.
[OnePlus 3 & 3T Cross Device Development] castaway1:
can i use blue_spark recovery for OP3T and new OOS 7.1.1?
[OnePlus 3 & 3T Cross Device Development] eroigaps:
Yes! Best recovery
[OnePlus 3 & 3T Cross Device Development] eng.stk:
If only got that broken, it isn't all that bad ;p

I already have the OB camera fixed on my kernel beta, but it breaks the camera on stable OOS.

So, I can't push out a build that will work both on stable and beta OOS.
[OnePlus 3 & 3T Cross Device Development] Achu Gowda:
Please post kernel beta for beta users.... Really wanted to try...

Your's best kernel for OP3..
[OnePlus 3 & 3T Cross Device Development] Acxjet:
Kernel sources for the Beta ROM's aren't released.

If his kernel works on the open beta, then it does, if not then you're on your own.
[OnePlus 3 & 3T Cross Device Development] Achu Gowda:
Cool bro I was just asking kernel beta for open beta 12 where flashing kernel breaks d camera...

I was asking dats it... No harm buddy:good:
[OnePlus 3 & 3T Cross Device Development] B3501:
Kernel sources should be released for Betas. One Plus are in the wrong. Not saying there should be a bluspark beta kernel, just that One Plus should be releasing sources.
[OnePlus 3 & 3T Cross Device Development] Midomad:
Nop OnePlus are doing great(look if there is an update with android 7.1.1 on others OEM?!)

The update is just released so c'mon...just wait,kernel sources will be released.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Not really in the mood for that.

I'll think about it, we'll see.

Well, given we struggle just to get regular releases sources, don't count on sources for betas.

But enough of this discussion guys.

If stuff is updated I'll take a look into it. If not, we'll have to wait.

Maybe I'll push a OB12/3 test build on the meanwhile or maybe I don't.

We'll see.
[OnePlus 3 & 3T Cross Device Development] Cris7ianO:
I flashed latest bluspark recovery and tried to backup my ROM, it goes until the end and then shows backup complete, backup failed. Weird.

Same with the official and unofficial TWRP. I read something about encryption, maybe someone in this thread could help me and clarify^^
[OnePlus 3 & 3T Cross Device Development] MarcTremonti:
Wrong thread. This is bluspark kernel thread, not TWRP.
[OnePlus 3 & 3T Cross Device Development] NickosD:
Well, there isn't a Blu_spark recovery thread, so...
[OnePlus 3 & 3T Cross Device Development] MarcTremonti:
Yes, because eng.stk doesnt give support for his recovery. Its only his private recovery he shared.

And since Cris7ian0 said same issue with official TWRP its not even bluspark TWRP related. So, wrong thread!

Enough OT now.
[OnePlus 3 & 3T Cross Device Development] mido25:
* just strolling here to see if Eng stk has changed his mind and released Blu spark for OB 12*
[OnePlus 3 & 3T Cross Device Development] Midomad:
Don't think so,

No kernel source!No kernel available For OB!
[OnePlus 3 & 3T Cross Device Development] B3501:
He fixed the camera on OB12 with the sources we already have and said he might release it as a test.
[OnePlus 3 & 3T Cross Device Development] immi803:
[MENTION=3873953]eng.stk[/MENTION]

Hope you like it mate

https://www.xda-developers.com/onep...s-with-conservative-governor-for-some-reason/
[OnePlus 3 & 3T Cross Device Development] ungeeked:
It makes light tasks smooth but gaming is severely affected