yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] tikizondo94:
I'm running on both for now. I may switch to just big to see if there's any difference later on.
[OnePlus 3 & 3T Cross Device Development] Generalboii:
Does Fastlane work with AKT?
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
No, use r69 for the beta. It was a build just for the open beta. Dont expect updates or support however.

---------- Post added at 03:40 PM ---------- Previous post was at 03:40 PM ----------

No, because AKT tunes the interactive governor and fastlane is only available for blu_active
[OnePlus 3 & 3T Cross Device Development] eng.stk:
You're welcome :highfive:

Enjoy :good:

Nope, all good.

[YOUTUBE]gB_3MuFdZXo[/YOUTUBE]
[OnePlus 3 & 3T Cross Device Development] trAnwhiz:
Are you saying that AKT is bad or something? Or just that it doesn't work with the kernel?
[OnePlus 3 & 3T Cross Device Development] candiesdoodle:
Akt is for interactive. Not for blu_active governor.

Now stop posting about akt and suggest you do some search. This one is really obvious.
[OnePlus 3 & 3T Cross Device Development] trAnwhiz:
Yes, I asked what he thinks about AKT, not if it works with blu or not.
[OnePlus 3 & 3T Cross Device Development] Joloxx9:
Just want to say thx and confirm that new twrp doesn't wipe my memory like official one.
[OnePlus 3 & 3T Cross Device Development] Diegc5:
It come fastlane activated by default if I change to blue_active gobernor?

Thanks!!
[OnePlus 3 & 3T Cross Device Development] liver20:
No, go to governor settings and change fastlane from 0 to 1

Enviado desde mi unknown mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] Nevermindthelabel:
Been mentioned a few times already. Have to turn it on. Cpu - governor options - fastlane and change to 1 for on
[OnePlus 3 & 3T Cross Device Development] Diegc5:
I don't see on ex kernel manager

Where i can find?

Thanks
[OnePlus 3 & 3T Cross Device Development] aymahalawa:
You can adjust it through kernel auditor only
[OnePlus 3 & 3T Cross Device Development] Diegc5:
Ok, perfect.

Thanks
[OnePlus 3 & 3T Cross Device Development] Nevermindthelabel:
I'm using EX. Works fine. Are you on blue_active?
[OnePlus 3 & 3T Cross Device Development] Diegc5:
Yeah on both.
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
I was about to ask the same question. That looks like the options for interactive, because some of those don't exist for blu_active
[OnePlus 3 & 3T Cross Device Development] Nevermindthelabel:
Governor options and then fastlane is the second to last option
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
Then the option should be there. Which release of the kernel are you running? It should have these options under governor options

Edit lol, won't let me take off that picture. It's the wrong one
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
This should be the right one
[OnePlus 3 & 3T Cross Device Development] Nevermindthelabel:
LOL who's a good boy?!
[OnePlus 3 & 3T Cross Device Development] anttaz:
Does release 72 work with beta 3 for op3t being later version than beta kernel for the beta rom?
[OnePlus 3 & 3T Cross Device Development] Nevermindthelabel:
Nope. Been mentioned a couple times
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
No release 72 only supports OS 4.03 and LOS
[OnePlus 3 & 3T Cross Device Development] Diegc5:
I already found it.

Thanks for your help [emoji12] .
[OnePlus 3 & 3T Cross Device Development] Generalboii:
Well that's to bad... Thanks for the answer anyway. It's not like AKT can be set and then change the big cluster to blue_active to get Fastlane. So since we can't do that, I guess my question served for nothing...
[OnePlus 3 & 3T Cross Device Development] Xennet:
Official twrp updated to 3.1.0.1 for 3t...

No changelogs given...

Need to update or stay with bluspark twrp
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
Stay with Blu Spark. He had already pulled the upstream commits, so it's somewhere between 3.1 and 3.1.0.1
[OnePlus 3 & 3T Cross Device Development] mvlad:
I can't use my phone because of f2fs problems. I'm updating from v64 and I did the data format (changed to ext4 then back to f2fs, copied the old files on the sdcard and restored the Data backup with "use rm -rf instead of formatting" ticked) but the phone still has problems. I'm using your latest TWRP (v24) and latest bluspark (v72). I'm on Freedom OS v2.5. This didn't happen before updating (while I was on v64) [MENTION=3873953]eng.stk[/MENTION]
[OnePlus 3 & 3T Cross Device Development] alvin182:
Can you give more details?

In my case I did a wipe data and changed to ext4.

It did it but im still crypted idk why all these with the v22 recovery
[OnePlus 3 & 3T Cross Device Development] Schrotty35:
Latest twrp is very slow whene making backup.
[OnePlus 3 & 3T Cross Device Development] Aldideos:
Can't make a data backup if i use a password with latest twrp
[OnePlus 3 & 3T Cross Device Development] anttaz:
With this being a unified build will the blu spark beta 12 version named after the op3 work with beta 3 of the op3t rom?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Sure, that's why it says OB12-3
[OnePlus 3 & 3T Cross Device Development] anttaz:
Cheers, I hit thanks and off to try now.

Doest it detect device and set itself to target device or do I need to set for OP3T clockspeeds etc with it being slightly different to the OP3?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Flash and forget , all is auto.
[OnePlus 3 & 3T Cross Device Development] BZRK49:
Had the same experience, couldn't understand why.

F2FS on OB 12, r69 and v24
[OnePlus 3 & 3T Cross Device Development] mvlad:
Anything on my problem, eng.stk? I really want to get the benefits of both f2fs and your latest version.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
TWRP is fine, that's all about the support you will get here.

Now guys, stop cluttering the thread with TWRP, stuff. No support means no support.
[OnePlus 3 & 3T Cross Device Development] mvlad:
Well it was also related to the kernel, that's why I asked.
[OnePlus 3 & 3T Cross Device Development] Schrotty35:
You make a custom twrp. For me its related to for asking.
[OnePlus 3 & 3T Cross Device Development] andre0005:
He's not forced to give support for sharing software on xda. It's not like he's getting paid for this, so be happy that he shares his work.
[OnePlus 3 & 3T Cross Device Development] cpt.macp:
Camera crashes with r72 on 6.0

So reverted to r69
[OnePlus 3 & 3T Cross Device Development] marf28101995:
If you could read it wouldn't crash damn ! Use the search button doing so you're following the rules
[OnePlus 3 & 3T Cross Device Development] cpt.macp:
Dear sir , I did use the search thingy but it didn't help me .

So I just posted it so that others might get to know about it .
[OnePlus 3 & 3T Cross Device Development] marf28101995:
Read the release post and you will understand and it has been answered 100 times per day... 72 is for 4.0.3 it doesn't say beta 12/3 in the kernel version
[OnePlus 3 & 3T Cross Device Development] Explorer23:
This right there ...

Others that know how to search for information in a thread will get this info from many other (older) posts.

Those that will miss those posts (like you did) will most probably also miss your post for same reasons.

Repeating the same stuff again and again is kinda pointless.
[OnePlus 3 & 3T Cross Device Development] Scorpion70:
Can i change "system, data and cache" to f2fs ?

why we can't change the System to F2FS ? !
[OnePlus 3 & 3T Cross Device Development] ungeeked:
Also, why can't people use search
[OnePlus 3 & 3T Cross Device Development] Dieppy:
:silly:
[OnePlus 3 & 3T Cross Device Development] Funk Wizard:
Ext4 is a better option as the difference is negligible and recovery works better on ext4
[OnePlus 3 & 3T Cross Device Development] nihilista:
Why someone should do that? It wouldn't make anything better. There are many people gone back to ext4 for all partitions, because f2fs seems to have some bugs (btw, for me running fine...). F2fs for system partition isnt supported with every device, rom and kernel i know...
[OnePlus 3 & 3T Cross Device Development] Chaplan:
In the Land of the CAN you can do whatever you please.

In the Land of the WORK it won't work that way.

No it's not. F2FS makes an actual difference. Recovery works well in both scenarios

No bugs if you use the right kernel and TWRP combo. It's always stated by the OP on releases.
[OnePlus 3 & 3T Cross Device Development] Scorpion70:
so, if i run OOS with blu_spark, i can change only the data and cache. am i right?

and one more question, is disabling fsync safe or not?
[OnePlus 3 & 3T Cross Device Development] nihilista:
Yes, but if running OOS it will have data with f2fs without doing anything (with oneplus3t, dont know oneplus3).

Disabling fsync shouldn't make problems, but why? Never had problems with fsync on.
[OnePlus 3 & 3T Cross Device Development] Scorpion70:
thanks a lot:highfive:

because i heard that disabling it improve the performance. but it may cause data loss! is this right too?
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
Disabling fsync has the potential for data loss. If your phone crashes or randomly reboots before the data is stored(synced) it will corrupt data.
[OnePlus 3 & 3T Cross Device Development] lapapunk:
Omg. Since f2fs appear at opo, I was changed it. Now I have op3t and my data partition formatted in f2fs too. And I never, never had any kind of bugs with f2fs.

So it's always about what users changed in kernel, roms, system files, restored apps by titanium. And after all this steps, they make clean install with changed filesystem to ext4, and says that all their bugs was in f2fs. So like I said early, I never get any bugs consisted in f2fs, with different devices, roms and kernels.

It's was a small report about my expirience. Btw, I prefer f2fs, because I see improved performance and speed.. :cowboy:
[OnePlus 3 & 3T Cross Device Development] Scorpion70:
what does it mean exactly? could you explain more please?
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
Basically when you disable it the storage system isn't forced to write your data to store immediately but caches it in the ram . When you turn off the screen and then sinks the data from the ram into the storage and writes to the drive. the lack of writing constantly to a physical this is what caused the performance again but in doing so if you lose power to the ram you lose your data or corrupted if it's being read from physical storage
[OnePlus 3 & 3T Cross Device Development] Scorpion70:
Wow!! that was very helpful:fingers-crossed: so according to your explain it's better to leave fsync On:good:
[OnePlus 3 & 3T Cross Device Development] fanbogo:
Very good kernel, I love r69 :o

Thanks!

Lol
[OnePlus 3 & 3T Cross Device Development] Chaplan:
You are shameless... LOL
[OnePlus 3 & 3T Cross Device Development] ndarkside93:
Yes
[OnePlus 3 & 3T Cross Device Development] motherninja:
I just tried to flash the latest OB on my OP3T, continued with flashing the r69 kernel. Everything's so far so good as expected.
[OnePlus 3 & 3T Cross Device Development] mido25:
Everyone loves 69 xD
[OnePlus 3 & 3T Cross Device Development] DragonSlayer240:
He like 69, you like 69, I like 69, EVERYONE LIKE 69! ?
[OnePlus 3 & 3T Cross Device Development] Scorpion70:
On which cluster should i enable fastlane? someone said for big, another one said little and other said for both!:eek::confused:
[OnePlus 3 & 3T Cross Device Development] candiesdoodle:
Try all three and see what works for you :) no hard rule
[OnePlus 3 & 3T Cross Device Development] Explorer23:
There really is no "should" because it comes down to personal preference. Depends heavily on your usage, battery vs performance preference and sensitivity to animation smoothness.

Perfect settings will be different for each user.

So try something, be amazed, then try different settings and be possibly even more amazed! ?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Spot on :highfive:
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Enjoy it while you can... maybe we can get on this topic again on 96.:confused:

This r69 got a lot of love going on here...

Has it ended to anyone else?
[OnePlus 3 & 3T Cross Device Development] DragonSlayer240:
Wow test build? When is it coming out for everyone?
[OnePlus 3 & 3T Cross Device Development] marf28101995:
I think you need to update too mate ??
[OnePlus 3 & 3T Cross Device Development] joakimbo:
I'm on a AOSP Extended, which version should I flash. And I heard some rumours that it breaks camera? I know blu_spark don't give support for custom ROMs, but anyone else who knows? Thanks
[OnePlus 3 & 3T Cross Device Development] skyknife93:
That's cheating:crying: I want the newest sparky goodness too:crying:
[OnePlus 3 & 3T Cross Device Development] marf28101995:
Download link for last version

Please don't share it's a closed beta

;)

https://goo.gl/lATILX
[OnePlus 3 & 3T Cross Device Development] skyknife93:
That's cold bro. Still... I'll wait.
[OnePlus 3 & 3T Cross Device Development] Explorer23:
The "custom" version is for all non-OOS ROMs.

EDIT: wrote a paragraph about camera compatibility, then checked and realized that my memory sucks... ? Release info for r72-custom says it's compatible with OB12 camera so you're good to.

Happy flashing!
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r77 unified OB test

All right crew!

New build is up. Wicked!

I decided to push one more test build for OB12/3.

This features a full rebase to 7.1 msm-3.18 CAF branch LA.UM.5.5.r1-03600-8x96.0, should be similar to the one used by OnePlus in the future 7.1 release (so we are in the lead atm ;p).

I also update blu_active with a couple patches and latest F2FS-stable backports

No support will be given, but feel free to share your thoughts on this stuff above.

This is an experimental build, although it's been solid in our testing. If your cat get's on fire you're on your own :eek:

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] evanxyj:
OB test build is not for custom Roms right?
[OnePlus 3 & 3T Cross Device Development] Ducter:
No, OB is open beta 12, OOS based.
[OnePlus 3 & 3T Cross Device Development] uudruid74:
I'm stupid
[OnePlus 3 & 3T Cross Device Development] Funk Wizard:
Yes mate you are one step ahead.

R78 working fine on the upcoming build as well, should be out tomorrow or later this week.

WiFi, Bluetooth all fine and no lags whatsoever.

Keep it up buddy [emoji2]

Sent from Funk Tuned 3T
[OnePlus 3 & 3T Cross Device Development] habylab:
Thanks for the latest update!

Out of curiosity, how do you know OP will use a similar chain to what you're on now? Github?
[OnePlus 3 & 3T Cross Device Development] FlyingMachete:
You must've missed that day he posted a picture of himself with his Cristal ball...
[OnePlus 3 & 3T Cross Device Development] donny110:
This might be the wrong place to ask, by all means redirect me if that's the case

But is it possible to add a backlight dimmer into the kernel (I've seen elementalx kernel do this for example).. It's the only thing I'm missing right now, my apoligies if this has already been asked:)
[OnePlus 3 & 3T Cross Device Development] Chaplan:
There is no true BackLight Dimmer kernel feature implemented over the custom kernels for the OP3.

What the so called backlight dimmer feature does can be easily obtained on stock kernel and blu_spark.

On OOS 3.x.x you have to disable the adaptive brightness and push the brightness slider all the way to the left.

On OOS 4.x.x you have to enable the battery saver option so you get the same result.

On custom ROMS the above method varies and on some is not even needed as they ship the minimum brightness already set to the minimum.

You can get a brightness app from the playstore and set it a bit down with that. You will get a lot of ghosting on those blacks though.
[OnePlus 3 & 3T Cross Device Development] Explorer23:
You could also use some app that turns off some of the pixels as we're having AMOLED displays.
[OnePlus 3 & 3T Cross Device Development] peddarson:
Hmm, when the screen is on, all the CPUs are almost at 100%...installed the latest kernel...
[OnePlus 3 & 3T Cross Device Development] NickosD:
Are you using kernel adiutor?
[OnePlus 3 & 3T Cross Device Development] Explorer23:
Not the kernel's fault. Try clean flashing the kernel (flash stock boot.img, then flash blu_spark again), if it doesn't help, try clean flashing whole ROM.

Issues with cores locked to max frequency and high load (usually by "Android System") are quite common on OP3 when you're messing around with ROMs and kernels, but it's pretty much never kernel's fault.

EDIT: probably should say first: wait a bit! If you cleaned cache/dalvik it has to be rebuilt so it's normal to have high load for some time after flashing.
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Are you giving this input on this thread (kernel) only or at all the apps and ROMs you use?

It's been asked, debated and answeard a gazillion times already.

Blu_spark Kernel won't give you the lock on high frequencies state you mention.

Use the search button. You can easily find all the steps to get out of that state and the theories​ behind it happening.

Battery drain and high temps suck, I know. But reading the same question all over again sucks even more...

Search and be amazed!
[OnePlus 3 & 3T Cross Device Development] harish_hpd:
does OB bluespark kernel r78 have force encryption disabled ? r69 encrypts storage.

Send From Oneplus A3003
[OnePlus 3 & 3T Cross Device Development] lombyzgz:
I have problems when I go out from my home, wifi dont disable with R78 on OB3- opo3T

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] harish_hpd:
bro storage encrypted after flashing r78?

Send From Oneplus A3003
[OnePlus 3 & 3T Cross Device Development] lombyzgz:
How can I know?

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] eng.stk:
All of my kernels since day one don't force encryption.

OB issue.
[OnePlus 3 & 3T Cross Device Development] peddarson:
Okay, you are right. Shame on me. I was only in a rush and was wandering since when I need a heating in my pocket :D
[OnePlus 3 & 3T Cross Device Development] lombyzgz:
I didnt have this issue with the last beta kernel.

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] Explorer23:
Last 24 hours recap:

- cats getting on fire

- baby seal genocide
[OnePlus 3 & 3T Cross Device Development] Funk Wizard:
No it does not, I am still decrypted after flashing the latest.

No such issue with my device, wifi connects and disconnects just as it should.

Sent from Funk Tuned 3T
[OnePlus 3 & 3T Cross Device Development] cba1986:
Its gonna be a release for custom roms? Happy using r72 along citrus caf. :good:
[OnePlus 3 & 3T Cross Device Development] Chaplan:
There are actually 3 ways to make your pocket hot, with the OP3 in it, that can be replicated on stock kernel. One goes back to OOS 3.x.x. and can be replicated on N as well. (2 are N specific only)

None of the 3 need a custom kernel or root prieveligies.

One is attainable using full stock (stock recovery and closed bootloader).

None need any specific app to be running.

Lets keep that in mind the next time we see our frequencies go over the top.

They can easily come down with little hassle.

This is not towards you in specific. But has been a constant strange question that keeps coming back.
[OnePlus 3 & 3T Cross Device Development] vampire36:
I know you don't support OB build but this wasn't a problem onr69. Only on r78 it started where wifi doesn't auto disconnect when out of range. Am sure.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Well enjoy it then ;)

Builds come when they come, no etas.

Well given the huge change on the baseline between builds results may vary.

Most of us are glad to have me working on a very usable version while OnePlus provides no support for OB.

When they push stuff all will be peachy. Until then, is live with what we have I guess.
[OnePlus 3 & 3T Cross Device Development] Chabola:
Blue_spark r78 on ob12 is so smooth and fast. :svetius:
[OnePlus 3 & 3T Cross Device Development] motherninja:
Same exact problem here... However, I didn't post it here even tough I already noticed it since yesterday, given that eng.stk already stated there is really no support for OB stuff.
[OnePlus 3 & 3T Cross Device Development] poczynek:
Same problem here. I reverted to r69.
[OnePlus 3 & 3T Cross Device Development] motherninja:
Yes, me too. I reverted back to r69, tested it once again by walking far from my access point and the problem is gone... Now the phone can disconnect and connect again automatically.
[OnePlus 3 & 3T Cross Device Development] Batfink33:
Yeah, WiFi seems broken on 78 for me with OB12 but it's an unsupported test kernel with no sources so it can't really be considered an issue.
[OnePlus 3 & 3T Cross Device Development] fanbogo:
WiFi is not broken. 78 is great. Battery life is impressive.
[OnePlus 3 & 3T Cross Device Development] Batfink33:
Interesting, perhaps it's a Magisk issue then. That seemed to cause problems searching through the thread, anyway this is getting OT.
[OnePlus 3 & 3T Cross Device Development] fanbogo:
No issue with magisk and WiFi
[OnePlus 3 & 3T Cross Device Development] Needles_one:
I had this issue. Wi-Fi connection to my home network remained even though I was out of range saying - connected but no internet. When appeared in the range it didn't reestablish connection by itself but I had to switch off- switch on Wi-Fi in order to bring it back.

On 69 everything is perfectly fine. No blame here. Just a fact. OP you da real MVP with these builds! Btw, came from a hammerhead :)
[OnePlus 3 & 3T Cross Device Development] Chaplan:
Ok guys.

Enough OT about the BETA releases.

They are labeled BETA, and so is the OOS (OB 12/3) they pair with so results may vary as stated already by the OP.

No support is given to OB builds.

On r78 some have a "new feature" on their devices where the wifi will just report as connected after going away from the AP. Some clearly don't.

Some went back to r69. Others prefer to surf the wave and stick to r78 which has been fully rebased to 7.1 branch.

We have WiFi working here. We can manage the connection manually at any time if needed.

BETAS are shared for the convenience of the users and not for bug reporting and cluttering the thread with OT.

Stable build is rock solid as always and that's the focus of this thread.

Keep up. But keep that in mind!
[OnePlus 3 & 3T Cross Device Development] lombyzgz:
We are just reporting that for future updates! Thanks for your work!

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[OnePlus 3 & 3T Cross Device Development] marf28101995:
And you guys need to report it 20 times per day ? Jesus
[OnePlus 3 & 3T Cross Device Development] Chaplan:
My arm hurts.

Actually after it being reported once, acknowledged​ and already answered by the OP it is just rude and OT like hell to keep reporting the same thing all over again.

My arm hurts.

I wouldn't be surprised if he thinks again before releasing a beta after all the clutter I have read on the last posts.

My arm hurts.

My arm hurts.

BETAS are a take it or leave it release.

Have I already told that my arm hurts?

I think I might have.

Sorry for the "my arm" OT.

My arm hurts.

Yeah. Pretty dumb of me to keep saying that.
[OnePlus 3 & 3T Cross Device Development] NickosD:
I actually have this issue with tuga rom and fusion kernel (and with kronicCore kernel). So it might be something else. Maybe the firmware?