yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] jexsuzon:
no wonder why my whatsapp messages were gone..

Anyways, if i install kernel adiutor and disable fsync then uninstall KA does it still disable fsync?
[OnePlus 3 & 3T Cross Device Development] Dr. Narinder:
it is for stock oos and f2fs is not required to flash it, a custom rom variant is also available
[OnePlus 3 & 3T Cross Device Development] eng.stk:
O3 causes some issues, I may revisit in the future.

Voltage control nope.

zram is pointless in devices with 4gb or more

fastlane was removed because governor has load prediction and other nice goodies. I may revisit this in the future.

:good:

No, you can keep things as you got them and just flash the kernel.
[OnePlus 3 & 3T Cross Device Development] gillim74:
Never

Is there a different thread for the custom rom one.thanks for replying.

---------- Post added at 06:19 AM ---------- Previous post was at 06:17 AM ----------

Ok.thanks for your response.im coming from htc and the pixel which has no developement.nevermind figured out which one is for custom.
[OnePlus 3 & 3T Cross Device Development] chinmai560621:
Testing for the 3 rd day, end of cycle one: I was able to get 7.5-8hr SOT: Medium camera usage, lot of browsing and average use of WhatsApp Facebook and messenger. I get 6.5-7 hours along with light gaming and 5.x on heavy gaming. Beautiful.

I run data on f2fs: Normal- fsync off, UC -1.8, 1.4, laptop mode 1, input boost to 556 on two cores andreduced vibration to 50% ; Gaming- All default with OC frequencies(fsync off).

I get around 1% drain every two hours or sometimes 1% per hour. I'll soon figure out why.

I used AppOps to break some location permission of some apps(turn em on when needed). I use greenify with aggressive doze and doze on the go with all social apps hibernated.

Suggestion: don't use amplify - there's almost no benefit as it itself drains battery

I'm posting this because it might help people. please don't get too much off topic.

Hats off to the best kernel around!
[OnePlus 3 & 3T Cross Device Development] Gugus38:
Agree on amplify, literally wasted hours to create rules with zero results.

However I tried to install appops but it crashes on start. I am on F OS 1.11, is there anything special I have to do?
[OnePlus 3 & 3T Cross Device Development] chinmai560621:
Works perfect for me, I use stable and straight 3.2.8 . I don't follow freedom os. if it's based on the openbeta branch(h2o2 base), I'm telling you it's never gonna work . H2o2 is ****ing broken.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
For those interested in the 3T:

http://xdaforums.com/oneplus-3t/development/kernel-t3516012

:victory:
[OnePlus 3 & 3T Cross Device Development] derdjango:
Good thing that they sent you one.

Just don't get rid of the original one ;)
[OnePlus 3 & 3T Cross Device Development] chinmai560621:
Please..! Don't abandon the OnePlus 3. Ik it's at peak, but what if it get to more heights? And after its soo final, O3 optimizations will make it perfect.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Thank my wife, because Oneplus didn't gave me anything despite the huge amount of work I did on the OPX/OP3.

Seems like I don't fit on the "popstar" developer selection, so no device given to me to develop on.

I never monetized my work and I will continue to do so: I prefer to be a rock'n'rolla :)

O3 brings issues on the device, I will revisit it on the future but it's not a priority.

I will not drop OP3 support in a near future.
[OnePlus 3 & 3T Cross Device Development] derdjango:
Thanks wifey!

What a ducking shame, given that you have the second most popular OP3 kernel here on XDA. But hey, they rather provide 100 phones for a stupid giveaway.:rolleyes:
[OnePlus 3 & 3T Cross Device Development] Johnny199314:
Will it work on miui??
[OnePlus 3 & 3T Cross Device Development] manishsoni7689:
I am using version 165 on top of freedomOs 1.7 based on oxygen 3.2.8, I am barely getting 4 hours of SOT. And that with normal usage, no gaming. I use greefiny (boost mode) too, and keep heavy apps hibernated. Is that because most of time I am on 4G VOLTE, or is there any setting I have to do for getting better battery life. Right now I have all default settings (blu_active governor).
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Your usage makes the battery life, not the kernel.
[OnePlus 3 & 3T Cross Device Development] manishsoni7689:
Got it. Thanks.
[OnePlus 3 & 3T Cross Device Development] EinsteinXXL:
You are the best!!! ;)

PS: How to readd the verify and forced encryption?
[OnePlus 3 & 3T Cross Device Development] OmerElbaz:
r161 was very laggy for me, don't know why (FreedomOS 1.7 [OOS 3.2.8]).

However, r165 is amazing and works pretty much flawlessly!! :)

Thanks for all of the amazing work [MENTION=853975]ENG[/MENTION]stk :)
[OnePlus 3 & 3T Cross Device Development] eng.stk:
There's no kernel changes in next nightlies changelog, the storage stuff was revert because of issues.

This is a clear example why I don't give support to custom ROMs, specially CM that like to mess with stuff just because and all was working fine.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
I talked to Grarak, latst beta Adiutor should get that fixed.
[OnePlus 3 & 3T Cross Device Development] kenzolo:
just see the commit

https://github.com/CyanogenMod/andr...mmit/673c72c50f1b69621e9817c9bdefef015a3390f1

:good:
[OnePlus 3 & 3T Cross Device Development] otonieru:
You are awesome and you know that, lol
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Already checked that awhile ago, have no interest on it.
[OnePlus 3 & 3T Cross Device Development] Flamehell:
[MENTION=3873953]eng.stk[/MENTION] tnx for this amazing kernel bro!!!Makes my op3 and oos flying!!!!And the kcal is a bonus!!!:)
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_sp★rk r70

All right crew!

New builds are up. Wicked!

There's also a beta build for custom ROMs aka non-OOS build.

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 3 & 3T Cross Device Development] Flamehell:
Is it possible to dirty flash it right?looool i just install the previous one.....:D Tnx!!!
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Sure, flash away :)
[OnePlus 3 & 3T Cross Device Development] Flamehell:
Sorry mate,the defaul blu_active own governor is already for the best battery?Tnx mate :)
[OnePlus 3 & 3T Cross Device Development] eng.stk:
It's tweaked to be balanced, power savings without performance degradations.
[OnePlus 3 & 3T Cross Device Development] rui.ddevil:
Is there a stable Linaro based on GCC 6.1 available?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Nope, no yet.
[OnePlus 3 & 3T Cross Device Development] Jole7:
You must be joking right? On my previous device Glaxy S6 i used a custom kernel with Linaro 6.1.1 and it was very stable and fast.
[OnePlus 3 & 3T Cross Device Development] proag:
Have you thought about using CM kernel source as a base to your kernel for custom ROMs? Now, your kernel for customs is just less attractive than others (official, ElementalX) since it's based on OnePlus' kernel source which is 17 versions behind (3.18.20 < 3.18.37). Also, CM adds many tweaks and optimizations, so I guess you should consider using it as the base.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
I use my own custom build toolchains in other SoC, the msm8996 is a total new beast and we can't do everything we want.

The only joke joke is you talking about numbers without knowing what they mean.

That is just non sense. You clearly don't know what you're talking about.

My choices are my own, nobody forces you to use this...
[OnePlus 3 & 3T Cross Device Development] Flamehell:
Mate,really,just do your job as you already are doing and don t think about the other....your kernel is amazind,period :)
[OnePlus 3 & 3T Cross Device Development] fanbogo:
I don't think he is joking. So just to be sure, you have problem with someone who is sharing his job for free with us? Dude fword you
[OnePlus 3 & 3T Cross Device Development] Jole7:
I know more that you think anyways good luck with your kernel but i won't use it. Greetings!

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

Why this attack? just because i told him that already are more newer and stable Linaro toolchain? What is your problem man?
[OnePlus 3 & 3T Cross Device Development] proag:
Then please, clarify.

I'm not saying that you should use it as a base to your custom kernel, I just asked if you had thought about it.

I have no idea why you called it a nonsense, the 3.18.20 kernel which OnePlus uses is 1 year old and many bugs have been fixed since then. I see no reason for using it instead of the 3.18.37.
[OnePlus 3 & 3T Cross Device Development] chinmai560621:
I was going through my friend's brother's phone (motog3) and I see an option in the kernel adiuter to change the maximum frequency when the screen is off. can this be made available on the. OP 3? Do you think limiting this to idle will be essential to stop CPU wakeups when on doze?
[OnePlus 3 & 3T Cross Device Development] derdjango:
Limiting the frequency to idle will only prolong the time of the phone being awake.
[OnePlus 3 & 3T Cross Device Development] chinmai560621:
Lol kryo never switches off cores. That's why it's kryo. It doesn't throttle also like other phones. All the time the cores are on.
[OnePlus 3 & 3T Cross Device Development] laggardkernel:
[MENTION=3873953]eng.stk[/MENTION] Talking about the r165 compatibility with Magisk, the problem I encountered here #2147, maybe i get some hints.

I discovered ElementalX 0.31 also mounts WiFi module, an image file, during boot and it works well together with Magisk. While the WiFi module provided by blu_spark is not mounted with Magisk installed. I found the difference located at the init.blu_spark.rc. ElementalX mounts the WiFi module during the "on boot" stage, while blu_spark mounts it during "on post-fs".

# original init.blu_spark.rc
on boot
# Update foreground and background cpusets
write /dev/cpuset/foreground/cpus 0-3
write /dev/cpuset/foreground/boost/cpus 0-3
write /dev/cpuset/background/cpus 0-3
write /dev/cpuset/system-background/cpus 0-3
write /dev/cpuset/top-app/cpus 0-3

# Enable sched boost
write /proc/sys/kernel/sched_boost 1

on post-fs
# Bind modules folder
mount none /sbin/modules/ /system/lib/modules/ bind

Since Magisk also mounts with this "on post-fs", I guess there is a collision between mounting WiFi modules by blu_spark and mounting Magisk modules by Magisk. Hence, I tried to change the WiFi module statements under "on boot", just like how ElementalX does. After this, WiFi module is mounted successfully and WiFi works with Magisk.

# modified init.blu_spark.rc
on boot
# Update foreground and background cpusets
write /dev/cpuset/foreground/cpus 0-3
write /dev/cpuset/foreground/boost/cpus 0-3
write /dev/cpuset/background/cpus 0-3
write /dev/cpuset/system-background/cpus 0-3
write /dev/cpuset/top-app/cpus 0-3

# Enable sched boost
write /proc/sys/kernel/sched_boost 1

# Bind modules folder
mount none /sbin/modules/ /system/lib/modules/ bind

# on post-fs
# Bind modules folder
# mount none /sbin/modules/ /system/lib/modules/ bind
[OnePlus 3 & 3T Cross Device Development] eng.stk:
It's not a good pratice to bind mount that so late.

Try with on post-fs-data (that was a typo).

Let me know how it goes.

There's nothing laggy about nay of my releases.

Nothing to do with kernel.
[OnePlus 3 & 3T Cross Device Development] shubhaemk:
I'm new to OP3 kernels and everything, it seems to be changed a lot from OPO. I'm on CB8 , I had flashed this using the twrp by eng.stk. My system is f2fs , can I flash this through twrp or should I format my system partition again? Thanks for any help. :cool:
[OnePlus 3 & 3T Cross Device Development] immi803:
This kernel yet not supporting ob8 as sources not published by op

Wait for op to release sources
[OnePlus 3 & 3T Cross Device Development] Konskl:
Hey [MENTION=3873953]eng.stk[/MENTION] the rq_affinity in previous builds had been set by default to 0. Any particular reason that you reverted the change to 1? Any particular side effect???
[OnePlus 3 & 3T Cross Device Development] nmlssit:
Talking about OB8: VoLTE arrived in my country (at last), i went to SIM Card option to check settings and the phone crashes. Set default theme they told me, but i was already on default theme. I tried then to wipe cache in recovery, realizing that even STOCK RECOVERY can't decrypt /data. What a joke. See ya Android N, let's meet again in stable branch.

/rant

Flashed back OOS 3.2.8 with r165 without issues :angel:
[OnePlus 3 & 3T Cross Device Development] laggardkernel:
Tried to mount the WiFi module during post-fs-data stage but not successful. Still Magisk mounting conflicts with the WiFi module mounting and the latter is left unmounted. :(
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Ok, on boot it is then, no prob.

Don't understand why Magisk does that, but oh well...
[OnePlus 3 & 3T Cross Device Development] Antsu:
Hey. Just flashed your latest kernel and I'm an magisk user. Sorry that I didn't read further background, but is there some problems with wifi and magisk?

I don't want to confuse more, but my wifi works.

Flashed this way, as I was on different kernel

Wipe cache and dalvik/art

Flash full oos 3.2.8

Kernel

Magisk v9

Magisk phh superuser

Reboot
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r168

All right crew!

New build is up. Wicked!

Keep in mind: I will give no active support for custom ROMs or CB. 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, it's free ;)
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r16 hybrid beta

All right crew!

New build is up. Wicked!

Now something completly different: first OP3/OP3T hybrid kernel.

Although it works nicely on the OP3T, keep in mind this is an experimental beta, you can brick your device. Highly untested!

This is base from the OP3T baseline with OP added bits. If this works good I'll be doing it like this from now on.

Let's see the feedback on this.

edit: pulled, new test will follow later

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

Don't forget to hit thanks, it's free ;)
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Testing the unified build at the moment. Booted fine here. Will take it for a spin to see how it performs...

Keep up.
[OnePlus 3 & 3T Cross Device Development] madsponge26:
Hybrid beta boots..
[OnePlus 3 & 3T Cross Device Development] tofuboi01:
Other than being a hybrid for the 3 and 3T, what other changes are there compared to latest v168?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Baseline is from the 3T, with updated drivers and so on.

There's also stuff like O3 build optimizations, etc, check the 3T thread.
[OnePlus 3 & 3T Cross Device Development] madsponge26:
R16 is smooth i can't test the battery juice though
[OnePlus 3 & 3T Cross Device Development] juginkrebs:
R16 only for op3t ?

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] otonieru:
Still kinda wishing that you will bring back CM version of the kernel, [MENTION=3873953]eng.stk[/MENTION]

Getting envious with every new update released LoL

Am still on your R161 and very happy with it though
[OnePlus 3 & 3T Cross Device Development] madsponge26:
Nope. Op3 updated drivers and engtsk magic!
[OnePlus 3 & 3T Cross Device Development] juginkrebs:
Yep Flashed and its Very Smooth !

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] nikhilsnigam:
I am assuming that since this build is unified and baselined from op3t this should work flawless on open beta roms(mm) for op3.

I am using it with open beta 7 with f2fs data and it flies.

Op3t 3.5.3 and op3 open beta 7 are essentially the same so its a win win situation for all of us.

I vote for this from now on and hope even rom developers do the same unified build for op3/T.

:good:
[OnePlus 3 & 3T Cross Device Development] immi803:
Unified build flies :good:
[OnePlus 3 & 3T Cross Device Development] daothanhduy1996:
You are right, 100% right. For instance, manual exposure in the camera app on open beta 7 doesn't hang and reboot anymore if we set the value to more than 4 seconds with the new unified kernel.
[OnePlus 3 & 3T Cross Device Development] NickosD:
Can you test if snapchat works? Or someone on beta 7 and r16
[OnePlus 3 & 3T Cross Device Development] aadityarulez:
If you don't support custom roms, then why say custom rom in the thread title? I'm confused and I mean no disrespect to you or your work.
[OnePlus 3 & 3T Cross Device Development] juginkrebs:
Battery usage is very better then r168

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] nikhilsnigam:
Yes snapchat works for me and has worked earlier too.

[MENTION=3873953]eng.stk[/MENTION] performance is top notch but I would like to report an issue.

You can totally ignore this because I am using this on open Beta 7.

Battery doesnt charge with phone more than 90% giving a message that phone is too hot even if it is at room temperature. (with phone on and off).

Fellow 3.2.8 users please confirm if this is an issue on your side too.

Check Image

EDIT: Reverted back to r168 and the message is gone and phone is charging properly.
[OnePlus 3 & 3T Cross Device Development] NickosD:
It's not charging at 3.2.8 either. I plugged in with 96 and it won't start charging.
[OnePlus 3 & 3T Cross Device Development] Giocarro:
This was answered some weeks ago: http://xdaforums.com/showpost.php?p=69663575&postcount=1714 .
[OnePlus 3 & 3T Cross Device Development] aadityarulez:
Understood.thanks
[OnePlus 3 & 3T Cross Device Development] immi803:
No such charging problem ever faced using [MENTION=3873953]eng.stk[/MENTION] kernel, hope you're not using any such battery app that is causing sick issues or xposed module typo

I'm on 3.2.8 , and now with hybrid build few hours ago , even nothing such found you stated in any build prior
[OnePlus 3 & 3T Cross Device Development] NickosD:
Which version are u using?
[OnePlus 3 & 3T Cross Device Development] immi803:
Rom oos stock 3.2.8

I was on every build by blu spark, starting from very beginning, 142, 148, 151, 161, 165 , 168 and now on hybrid build kernel r16 :D
[OnePlus 3 & 3T Cross Device Development] nikhilsnigam:
It charges fine upto 90%.

Can you check after that. Because reverting back to r168 solved the problem.
[OnePlus 3 & 3T Cross Device Development] NickosD:
It charges fine in twrp tho
[OnePlus 3 & 3T Cross Device Development] immi803:
Hybrid build is just released, I'll report further, didn't get time to charge up-to 100 percent, will report you soon

But i must say this hybrid build is very smooth in use overall till now
[OnePlus 3 & 3T Cross Device Development] nikhilsnigam:
oh yes it is.

Take your time.
[OnePlus 3 & 3T Cross Device Development] tofuboi01:
On 3.2.8 with latest hybrid build, LED isnt on to indicate charging. LED indicator works when back on v168.
[OnePlus 3 & 3T Cross Device Development] nikhilsnigam:
its not charging thats why led wont light up
[OnePlus 3 & 3T Cross Device Development] madsponge26:
Any dash charging problem in R16? Im stuck in 90%.

Confirm issue?
[OnePlus 3 & 3T Cross Device Development] tofuboi01:
It is charging, the battery icon shows it is charging, just no LED indicator >__>

Plus i did mention flashing v168 it came back. cable was plugged in the whole time.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
That can be because of the higher battery capacity on the OP3T.

The charge and the battery meter checks if the high capacity battery to use it, maybe something is missing in the tree that checks the safe values for temperatures (are different for the 2 models).

What you guys have in /sys/module/qpnp_smbcharger/parameters/cutoff_volt_with_charger ?

I'm pulling the build, so far all is working fine, next one will try to tackle that charging situation.
[OnePlus 3 & 3T Cross Device Development] tofuboi01:
I am hazarding a guess it is stuck on 90% because op3t battery is 3400mah and op3 is 3000...rough calculation shows 3000/3400 is approx 88%. Maybe the values needs to be fixed for op3 side.
[OnePlus 3 & 3T Cross Device Development] nikhilsnigam:
I got 3240
[OnePlus 3 & 3T Cross Device Development] chinmai560621:
Hell man!! O3 for 3T and Os for 3 IS NOT FAIR!!!
[OnePlus 3 & 3T Cross Device Development] eng.stk:
And with r168?
[OnePlus 3 & 3T Cross Device Development] chinmai560621:
Why the hell ain O3 for OP3?!!!! You know it's better than Os. :'(
[OnePlus 3 & 3T Cross Device Development] NickosD:
Nothing? r168

Anyone else without that file?
[OnePlus 3 & 3T Cross Device Development] Remorcer:
Because O3 causes some issues on this device.
[OnePlus 3 & 3T Cross Device Development] chinmai560621:
If it were to cause issues on OP3, so will it on OP3T. It's just the SD821 that is the change. Anyways, will wait. Maybe he will apply later.
[OnePlus 3 & 3T Cross Device Development] Sytis:
Same, I'm also missing that file.
[OnePlus 3 & 3T Cross Device Development] nikhilsnigam:
there was no such file with r168
[OnePlus 3 & 3T Cross Device Development] candiesdoodle:
Actually I had no issues in charging all the way to 100%. It wouldn't charge on the first plug in, then plugged out and plugged in again a couple of times for it to start charging.

Then it went fine all the way to 100...

The graph seems to indicate the charging behavior is indeed a bit wiered... Looking at the slow charging corresponding to the flat lines.
[OnePlus 3 & 3T Cross Device Development] immi803:
You're right mate

Not only it stucks at high temperature warning and secondly at 0 battery, mobile is off and plug in charger reveals the same message for high temperature and doesn't charge :rolleyes:
[OnePlus 3 & 3T Cross Device Development] Rawwrius:
i have a problem :D

i would like to try f2fs and do it like in op

flash twrp by blue spark

flash latest blue spark

data change to f2fs

cache change f2fs

now everything is wiped ( took a backup and saved it to pc)

but my op3 stuck at bootanimation and wont boot

im on freedom os 1.7 latest blue spark no mods

any idea ??
[OnePlus 3 & 3T Cross Device Development] _PrEzi_:
Bolded is your problem. blu_spark supports data only for f2fs.
[OnePlus 3 & 3T Cross Device Development] Rawwrius:
op says cache and data ??
[OnePlus 3 & 3T Cross Device Development] _PrEzi_:
Since r15x (can't remember exactly) was syncronized with OP Sources - not anymore.

Change cache back to ext4 and you should be fine.
[OnePlus 3 & 3T Cross Device Development] Rawwrius:
thx :) that could be the point xD

but i would correct the op then :D
[OnePlus 3 & 3T Cross Device Development] eng.stk:
I would read the thread then :)

Custom ROMs support f2fs on data and cache, I follow CM.

OOS f2fs is on data only, like OB and stable OOS 3.5 ob the 3T
[OnePlus 3 & 3T Cross Device Development] shavendum:
I would like to ask if there were any updates to the twrp decryption bug on ob8. Is there a possible solution apart from decrypting the device
[OnePlus 3 & 3T Cross Device Development] dreinulldrei:
Yes, latest TWRP should work (the one by eng.stk).

Any of course you don't need to decrypt, it's just about the encryption KEY. So all you have to do is turn off boot encryption, e.g. by simply turning of PIN protection temporarily. Then boot into TWRP, then reboot and re-enable.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
No and I will not work on TWRP anymore.

Stop asking.