yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] dreinulldrei:
Sorry to ask, but haven't been able to find the answers by searching:

Was wondering where the difference between removed verify and fsync off is. In other words... is verify something that the user can turn on/off somewhere? Just asking because every layer of verify (by CRC, EDC etc.) usually serves a purpose.

I noticed that the -22 version does not mount data if it's PIN protected if using CB 3.5.5. When running stock OOS 3.2.7, all seems fine. Is there something special about formatting with 3.5.5 or does it just use some salt added to the PIN that the -22 recovery is unaware of? Turning off PIN protection for boot works, but fear in case of data loss or other problem I might be unable to boot to turn off PIN protection...
[OnePlus 3 & 3T Cross Device Development] eng.stk:
fsync: https://linux.die.net/man/2/fsync

verify: https://source.android.com/security/verifiedboot/verified-boot.html

I don't give support for CB editions (and specially not TWRP).

The provided TWRP is so people can have access to ROMs using diferent fw and to have correct f2fs driver.

Nevertheless, I think other people use encrypted data with CB adn it works normal.

Bottom line, Beta software (and worse even, without sources) can and will have broken stuff.
[OnePlus 3 & 3T Cross Device Development] dreinulldrei:
Ahhh, verified boot. Ok, got it. Thanks!

Totally understood. I was asking because of, yes, it works with the encrypted partition but only as long as I haven't set a PIN. When I chose to protect the device with a PIN, TWRP is unable to the decrypt.

https://source.android.com/security...g_an_encrypted_device_with_default_encryption

But I see there's nothing that can be done without the source...
[OnePlus 3 & 3T Cross Device Development] eng.stk:
OnePlus pushed op3t sources even before the device is on sale.

Big shouts.
[OnePlus 3 & 3T Cross Device Development] Konskl:
Well...they did the same with op3. We all know that afterwards they'll stop being that punctual...are you upgrading to the op3t ? Or might be given a dev device by OnePlus?
[OnePlus 3 & 3T Cross Device Development] Dieppy:
R147 is amazing!
[OnePlus 3 & 3T Cross Device Development] dreinulldrei:
Should be latest kernel source I guess...
[OnePlus 3 & 3T Cross Device Development] immi803:
Open Oxygen OS beta 6 ?
[OnePlus 3 & 3T Cross Device Development] niwia:
It's cb 3.5.5 right?
[OnePlus 3 & 3T Cross Device Development] dreinulldrei:
Yes.
[OnePlus 3 & 3T Cross Device Development] ungeeked:
It seems like 3T has native f2fs support.
[OnePlus 3 & 3T Cross Device Development] habylab:
It also seems slightly, very pointless. I paid £309 for my OP3, and it's £399 for the OP3t.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Not a big deal, CB 3.5 for the OP3 also has...

Nope, not worth the upgrade, specially because it comes out of mybown pocket.

I supported OP devices sure, but they never gave me anything.

I don't think they will start now.
[OnePlus 3 & 3T Cross Device Development] unease:
I truly appreciate your efforts and selflessness to share with us all one of the best Kernel ever designed for OP3. And I am sure this community feels the same way too. :svetius:
[OnePlus 3 & 3T Cross Device Development] galaxy16:
Hi.. just wondering.. always when im on stock kernel if i wanna flash custom kernel like bluspark or elemental.. after flashing it.. my wifi cant be switch on.. unless i do a clean flash.. anyone can teach me to prevent that? Im using stock oxygen os 3.2.7

Thanks
[OnePlus 3 & 3T Cross Device Development] Chris.nl:
In and out of context

Flashing the wrong kernel breaks wifi, and has broken infant animals in the past. To prevent all of this, just flash the OOS version because you're running a stock ROM.

To wheel it into a hospital.
[OnePlus 3 & 3T Cross Device Development] galaxy16:
Err... Im flashing kernel for oos.. i just don't know why it makes my wifi cant be switch on after flashing.. unless i flash from a clean wipe its ok
[OnePlus 3 & 3T Cross Device Development] otonieru:
You are not flashing SU after kernel right?
[OnePlus 3 & 3T Cross Device Development] galaxy16:
I think i did.. should i just flash kernel n boot only?
[OnePlus 3 & 3T Cross Device Development] otonieru:
The right sequences is :

1. ROM

2. Su

3. Boot into system

4. Back to recovery

5. Flash kernel

6. We save all panda babies

If you flash su after kernel, it will patch your kernel, make modules unusable, thus, wifi off
[OnePlus 3 & 3T Cross Device Development] galaxy16:
I see.. thanks for clearing that up.. so now if i wanna change to this kernel.. i go into recovery.. flash kernel then reboot to system... After that then flash SuperSU again? Im rooted already for now..
[OnePlus 3 & 3T Cross Device Development] otonieru:
NO.

You read my post again, and do it in that sequence

Kernel always flashed last. DONT flash su after kernel.
[OnePlus 3 & 3T Cross Device Development] candiesdoodle:
The bluespark kernel overwrites the WiFi module. That's why wofo breaks probably. The OP has mention of backup of the modules. Use that to restore the module if flashing stock kernel.

The sequence of flashing SuperSU should not matter IMO.
[OnePlus 3 & 3T Cross Device Development] Antsu:
You were on stock rom and STOCK KERNEL before flashing blu_spark? The wifi should work then. I'm on oos 3.2.7 too, maybe I'll try how it goes.... I'll let you know soon.

Edit. Ok, I read previous posts, maybe that's the culprit. But anyway, I'm gonna flash it still.

Edit.2 Now on blu_spark and everything works. Oh, this is so damn snappy kernel. I think I'm gonna use this for awhile. Thanks [MENTION=3873953]eng.stk[/MENTION]
[OnePlus 3 & 3T Cross Device Development] galaxy16:
Yes stock kernel and stock rom.. just rooted only.. i flashed it already.. i always thought i had to flash supersu always even after change of kernel.. i just flashed the kernel and everything is still working.. wont ever flash supersu again after flashing of kernels..
[OnePlus 3 & 3T Cross Device Development] candiesdoodle:
Hi guys. Is there a way to keep the hardware buttons lighted up all the time? Like as long as the screen is on. Couldn't find an option....

On oos 3.2.7+bluspark latest

(Posted in another thread didn't get an answer)
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Like said, when you flash SuperSU after the kernel, it sometimes restores it's backup (that usually is the stock kernel), that's why you don't get it working, because in fact you're using the stock kernel.

In OP there's the correct order to flash: blu_spark is always last and you don't need to flash anything but the kernel zip between kernel updates.

I don0't have any kind of hw keys control, I leave that to the ROMs side.
[OnePlus 3 & 3T Cross Device Development] SaneQ:
I am now on stock 3.5.5 and no root or anything and my question is if i flash this with TWRP, will i receive future OTA updates for the phone?

Lähetetty minun ONEPLUS A3003 laitteesta Tapatalkilla
[OnePlus 3 & 3T Cross Device Development] dreinulldrei:
As soon as you change partitions the user has no access to with normal use (so anything else than /data or /media), OTAs should cease to work. But you can easily flash unmodified /system, recovery and boot when you see there's an OTA available. All you have to do is re-install SuperSu, TWRP and Kernel...
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Soon™
[OnePlus 3 & 3T Cross Device Development] dreinulldrei:
Impressive.
[OnePlus 3 & 3T Cross Device Development] immi803:
Awesome :laugh:
[OnePlus 3 & 3T Cross Device Development] derdjango:
Any cool things you've found in the 3T sources that can be 'backported'?
[OnePlus 3 & 3T Cross Device Development] hasenbein1966:
r147 really is super-snappy.

Nerdgasm. ?
[OnePlus 3 & 3T Cross Device Development] dreinulldrei:
But since these sources are based on CB 3.5.5 they maybe shed some light the the encryption specialty in TWRP. *duck* :D
[OnePlus 3 & 3T Cross Device Development] eng.stk:
I already said I don't support CB or TWRP and I will not look into it.

Nobody knows in what 3T sources are based on and to be honest at this point I don't really care.
[OnePlus 3 & 3T Cross Device Development] dreinulldrei:
I am aware of this, yes. Hence the smily at the end.
[OnePlus 3 & 3T Cross Device Development] drwazi:
hai dev,

i've started using the v147 since past 2days,i ve noticed that the fingerprint reader is a tad slower than stock kernel,battery is same as or slightly less than stock.cell recption and other stuffs normal.nothing out of ordinary.am i missing something?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
By the looks of it you're missing stock, so you should use it...
[OnePlus 3 & 3T Cross Device Development] cloudx720:
I'm really looking forward to using this kernel, I'm currently on oss 3.5.5 do I just flash latest kernel and I'm good to go? :D
[OnePlus 3 & 3T Cross Device Development] Gugus38:
Isn't this option already in the rom? I mean I disabled the vibration on touch, guess that's the haptic feedback uh?
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Sure.

Nope, it's gestures haptic feedback control (dt2w, flashlight, etc).

You can't disable that in the ROM (unless using CM or the likes)
[OnePlus 3 & 3T Cross Device Development] core_x:
That's an awesome feature! I can't handle the vibration. Thanks [MENTION=3873953]eng.stk[/MENTION]!
[OnePlus 3 & 3T Cross Device Development] immi803:
I was using vibrafix app from play store, Hope i won't be needing it after next release, thanks [MENTION=3873953]eng.stk[/MENTION]
[OnePlus 3 & 3T Cross Device Development] chinmai560621:
Can you add sdcardfs ported from s7 or the one of myfluxi? Idk if this has been discussed already, so if it had just don't mind to type a few words for this idiot.
[OnePlus 3 & 3T Cross Device Development] Antsu:
Hint: Press search button, type sdcardfs, find latest eng.stks post, check what he has written.
[OnePlus 3 & 3T Cross Device Development] jayden2009:
I'm on community build and when flashing this kernel, WiFi stops working?
[OnePlus 3 & 3T Cross Device Development] xanthrax:
This kernel, as stated in countless posts, doesn't support community builds, look at your hands now, you're full of innocent kitten's blood...

Sent from my Darkside of Oneplus 3
[OnePlus 3 & 3T Cross Device Development] jayden2009:
OMG all that blood..... Need to wash my hands :laugh: thanks mate for answering my question :svetius:
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Thread title is for what is available, not what is supported.

I consider custom and CB builds to be beta so I don't support them and it's clear the rules of this thread not only on release posts, but more important, in OP.

The issue is not my thread name, the issue is people not reading the thread and ignoring what I say.

If this is somewhat of an issue I'll just pull everything and start to push builds only compatible with OOS 3.2, less work for me.
[OnePlus 3 & 3T Cross Device Development] Gugus38:
I am using this kernel on 3.5.5 and I never ever had any issues whatsoever. Just saying... :o
[OnePlus 3 & 3T Cross Device Development] Giocarro:
Fair enough, I'm kind of a veteran here at XDA, the issue is and has always been people not reading OP and warning of any shape and colour.
[OnePlus 3 & 3T Cross Device Development] Achu Gowda:
I'm in cb/open beta 7..which I shud flash??... custom or oos kernel??
[OnePlus 3 & 3T Cross Device Development] immi803:
Oos
[OnePlus 3 & 3T Cross Device Development] phil_greg2001:
Try oos :cool:
[OnePlus 3 & 3T Cross Device Development] Achu Gowda:
Xposed having probs with Nov patch...so rolled back oos 3.2.7
[OnePlus 3 & 3T Cross Device Development] immi803:
First this is not proper thread for this

By the way, xposed have no issues with 3.2.7
[OnePlus 3 & 3T Cross Device Development] Tikerz:
That's why he rolled back to 3.2.7. Xposed doesn't work with beta 7 because of November security patch.
[OnePlus 3 & 3T Cross Device Development] Achu Gowda:
I mean in open beta 7,xposed having probs...I kno dis is wrong thread:good:just for info
[OnePlus 3 & 3T Cross Device Development] Pjerisimo:
Just to confirm; i can flash newest version over any older version of bluespark without issues, right?
[OnePlus 3 & 3T Cross Device Development] nmlssit:
I still not get what i am doing wrong when dirty flashing a new CB. WiFi is still missing even with system and ro unticked in twrp.

Any help?

Clean flash > flash supersu > flash kernel > wifi working

Dirty flash > flash supersu > flash kernel > wifi not working

W T F
[OnePlus 3 & 3T Cross Device Development] unease:
Never flash a kernel during the course of flashing a ROM. You may flash SU or Xposed but never a kernel.

Wipe Factory Settings - Flash ROM - Flash SU - Reboot into ROM. Let it settle. Reboot back to recovery and Flash Kernel.
[OnePlus 3 & 3T Cross Device Development] FahrenGrade:
I'd actually wonder why you say this?

I always flash kernel on initial rom flash and never experience issues.

My logic is a kernel has files modules and they initiate upon boot. If you first boot with stock kernel and then flash kernel you may experience conflicts.

If you have some opposing logic to share I'd love to hear.
[OnePlus 3 & 3T Cross Device Development] ritchiedrama:
As the guy above me, I always flash kernel before booting ROM - always works.
[OnePlus 3 & 3T Cross Device Development] nmlssit:
That's what i Always do.

I now tried to flash ROM Supersu and kernel all at once, still no WiFi here.

---------- Post added at 09:06 AM ---------- Previous post was at 08:28 AM ----------

I tried every combination:

Flash ROM > reboot > Flash supersu > reboot > flash kernel > reboot

Flash ROM > flash supersu > reboot > flash kernel > reboot

Flash ROM > flash supersu > flash kernel > reboot

With both custom and oos builds. WiFi only works with only rom and supersu flashed, when i flash both custom or oos builds the wifi stops working.

Ofc system unmounted and ro unticked.
[OnePlus 3 & 3T Cross Device Development] nikhilsnigam:
This kernel works on beta 7? which supersu did you flash?
[OnePlus 3 & 3T Cross Device Development] nmlssit:
I don't know at this point. I flashed SR4.
[OnePlus 3 & 3T Cross Device Development] nikhilsnigam:
In your earlier post you mentioned on clean flash rom-supersu -kernel wifi works.

Are you talking ABOUT BETA 7 OR a different one.
[OnePlus 3 & 3T Cross Device Development] nmlssit:
I was talking about previous CB, 3.5.6. But i won't clean flash at every release, cmon.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
The hassle of using beta sw.

Some people had issues with partition size after upgrading, see if you have enough space on it (I have around 32M free after flash SuperSU SR3).

Yes, you can use my TWRP, flash full OB7 zip and you're good to go.

I upgraded from previous CB, all peachy :)
[OnePlus 3 & 3T Cross Device Development] nikhilsnigam:
Yes i did that and works flawless. But it ends up encrypting my storage which i dont want.

Your storage must be encrypted too right?

Btw saw your screenshot how are you able to run wifi with bluspark kernel?

I cant get it to work even on clean flash
[OnePlus 3 & 3T Cross Device Development] eng.stk:
No, if you flash blu_spark after the ROM and before boot, it will use what you already have.

If it's unencrypted it will remain like that.
[OnePlus 3 & 3T Cross Device Development] nikhilsnigam:
this is what I am doing on twrp 3.0.2.22

Clean flash ob7

flash supersu

flash bluspark

flash twrp 3.0.2.22 again in recovery

reboot recovery reboot system

No wifi :mad:

---------- Post added at 02:50 PM ---------- Previous post was at 02:30 PM ----------

now even tried this

clean flash ob7

flash blupspark reboot

still no wifi.

I am wondering at seeing your screenshot what could have been possibly wrong.

You have wifi working with bluspark. Strange.
[OnePlus 3 & 3T Cross Device Development] lombyzgz:
I have the same problem with all combinations...

Clean flash ob7 reboot flash su reboot flash kernel = no wifi

clean flash ob-flash su- flash kernel = no wifi

Could be something about busybox?
[OnePlus 3 & 3T Cross Device Development] nikhilsnigam:
No no OP clearly has it working. he mentioned straight forward method. But still not working for me.
[OnePlus 3 & 3T Cross Device Development] core_x:
For me this worked coming from beta 6:

1. Flash twrp -22

2. Reboot into twrp

3. Wipe dalvik&cache

4. Flash full beta 7

5. Flash SuperSU v2.78-SR1

6. Flash blu_spark r147

7. Reboot

8. Profit
[OnePlus 3 & 3T Cross Device Development] lombyzgz:
So what can we do? Anybody can make a stock kernel backup.zip for test?
[OnePlus 3 & 3T Cross Device Development] Funk Wizard:
Just dirty flash your stock ROM and ull be back on stock kernel

Sent from Funk Wizard's tuned OnePlus A3003
[OnePlus 3 & 3T Cross Device Development] eng.stk:
So you should have enough space, the module is around 6.8MB.

Check if you have /system/lib/modules and /system/lib/modules_back folders

I am not a psychic, this kind of stuff is exactly why I don't give support to unfinished sw.

If you choose to use it, you're on your own.

This goes for all: this is not a OOS beta thread, enough of ROM troubleshoot already.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Enough is enough.
[OnePlus 3 & 3T Cross Device Development] Stephen:
Moderator Warning,

Thread has been cleaned at OP's request. Please remember this is a development thread. Please keep posts on topic regarding issues etc with this kernel only. The OP has made it clear this is not a support thread for ROM issues or xposed issues etc. If the OP chooses to re-open this thread, please respect his wishes and keep posts on topic.

Many thanks,

Stephen
[OnePlus 3 & 3T Cross Device Development] xNAPx:
I've already have partitions formatted in f2fs do i still need the twrp version .22?
[OnePlus 3 & 3T Cross Device Development] kentexcitebot:
Did you even read what Stephen wrote above?

TWRP has nothing to do with this kernel's development.

Do you really want this thread locked up for good this time? Smh...
[OnePlus 3 & 3T Cross Device Development] immi803:
[MENTION=3873953]eng.stk[/MENTION]

R147 is snappiest one

But since the release of r147 i experienced twice the following:

Rom 3.2.7

Activity : watching video in chrome

Lack of memory or kernel crash(I'm not sure) screen went black, audio was coming through speaker(bluetooth)

Bluetooth was attached at that time

VPN was connected

I know it's a very laggy way to describe something, can [MENTION=3873953]eng.stk[/MENTION] please guide me to how create kernel log so next time i report something with proper log?

Other than just these two incidents, no issue ever recorded, not with gaming etc etc
[OnePlus 3 & 3T Cross Device Development] xanthrax:
You can use several applications to get a log, I would suggest the kernel adiutor, install it and scroll down to the settings section and tap on those 3 log sections when crashes occurs , you'll find the logs on the root of the internal storage, upload the files here as attachments

I personally would blame the ROM, Bluetooth issues occurred several times though on 3.2.7 many had been fixed, this combination, active Bluetooth + VPN + video streaming may lead to crashes, a log may help in this case

As far as I know the dev didn't touch any Bluetooth commits

Sent from my Darkside of Oneplus 3
[OnePlus 3 & 3T Cross Device Development] Explorer23:
It's better to send them privately, logs contain some sensitive data that shouldn't be publicly shared.

You never know ...
[OnePlus 3 & 3T Cross Device Development] xanthrax:
The logs doesn't contain ANY sensitive data the one can be concerned about

Sent from my Darkside of Oneplus 3
[OnePlus 3 & 3T Cross Device Development] immi803:
How to get kernel log?
[OnePlus 3 & 3T Cross Device Development] laupuy:
Hi,

take a look here: http://xdaforums.com/showpost.php?p=69708244&postcount=1751

:cyclops:
[OnePlus 3 & 3T Cross Device Development] Mulayan:
Is Version 147 ready for cm14.1? Because i flashed it and then my sdcard disappeared. It Shows up when booted into twrp but not when Rom is booted. Tried it multiple times. No problems with cm Stock Kernel.
[OnePlus 3 & 3T Cross Device Development] nikhilsnigam:
cm14.1 isnt officially supported yet so refrain yourself from trying it or posting it here for bugs.

and yes it works just fine but don't expect any support if you run into problems.
[OnePlus 3 & 3T Cross Device Development] Mulayan:
Ok, thanks.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
You need to always use my TWRP if using f2fs, or else you'll derp your data.

There's no kernel changes could influence that really, probably something from userspace and from your config.
[OnePlus 3 & 3T Cross Device Development] ungeeked:
[MENTION=3873953]eng.stk[/MENTION] Is there any advantage of formatting cache partition to f2fs? You once said that it was used earlier to store ota etc?

I have noticed few of the apps work better if cache is ext4 and only data is f2fs.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Not really, actually most device s that use f2fs only use it on data partition, that's where all the storage duty is.

It's doesn't make any difference for you apps or anything like that.
[OnePlus 3 & 3T Cross Device Development] Sultan.Alkhuzaie:
can anybody confirm if the kernal is compatible with miui 8 ????
[OnePlus 3 & 3T Cross Device Development] marf28101995:
-> backup

-> flash

-> let us know
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_sp★rk r151

All right crew!

New build is up. Wicked!

Rolled up some goodies, enjoy the vibration toogle for gestures (unzip DisableGestureHapticFeedback.zip and import the DisableGestureHapticFeedback.json on Custom Control tab from Kernel Adiutor).

KCAL should be good on the apps that expect all the sysfs to be available also.

I updated f2fs from the 3T, new twrp-3.0.2-23 with the fixes inside also shipped.

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] Crash:
[MENTION=3873953]eng.stk[/MENTION] thank you very much for your work :good:
[OnePlus 3 & 3T Cross Device Development] otonieru:
Sorry if i might ask in wrong place,

I just read the xda OP3T review that confirm that app opening speed is faster in OP3T by up to 20% due to changes of file system used,

Do you know whether it implemented through the kernel or the rom ? And is it possible to bring those improvement to OP3 users ?

Thx for the good work as always btw!
[OnePlus 3 & 3T Cross Device Development] Roi007leaf:
F2fs..
[OnePlus 3 & 3T Cross Device Development] otonieru:
O ic, so that mean OP3T was actually shipped with F2FS on data partition ?

Ok, am being out of topic,

Thx for the clarification though,

The review should have just stated it, LoL
[OnePlus 3 & 3T Cross Device Development] Roi007leaf:
What's the best app to modify the kernel settings? Kernel auditor modded or exkm?
[OnePlus 3 & 3T Cross Device Development] habylab:
In release notes.
[OnePlus 3 & 3T Cross Device Development] immi803:
R151, can't believe, it's so snappy, that it's slipping from my hand

Huge credits [MENTION=3873953]eng.stk[/MENTION]
[OnePlus 3 & 3T Cross Device Development] otonieru:
Btw,

My gesture still giving a haptic feedback, even when its already toogled in kernel adiutor, hmmm
[OnePlus 3 & 3T Cross Device Development] immi803:
[MENTION=3873953]eng.stk[/MENTION]

Can you please elaborate further how to get control for haptic feedback control? Apology for being noob :rolleyes:
[OnePlus 3 & 3T Cross Device Development] otonieru:
As stated, you can rename the given file from txt to json to further import it to kernel adiutor custom control,

It will become an extra toggle,

But it also confuse me, since even after toggle it on, it still giving me haptic feedback, lol