yashsingh1/xdaforums huggingface dataset:
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r182 unified

All right crew!

New build is up :highfive:

Newly beta? Enjoy :good:

Because of latest TWRP changes, you'll need to use latest TWRP 3.1.0-1+ or flash my unified TWRP 3.1.1-x blu_spark v43 (recommended).

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

This build features latest OBT24/15 source and new wakelock blocker interface by boeffla, build with latest blu_naro-7.2 :good:

With the new wakelock block system you can add any wakelock source you want, works like this: you can edit /sys/class/misc/boeffla_wakelock_blocker/wakelock_blocker and add the wakelock name in there to block it (list separated by ';')

If you want to survive reboots, you can use a script (check the attached example inside the zip). Just copy your script to /magisk/.core/post-fs-data.d or /su/su.d, depending on su option you use ( don't forget to set the file permission 777)

You can get more info about it here. Because this is powerful and can bring potentially derps if you choose to block unknown stuff, I will give no support if you choose to use any wl blocking (which I didn't before anyway).

blu_spark_r182-oos_op3-op3t_a14e18a

blu_spark_r182-custom_op3-op3t_9746cff

Keep it real, keep it true, keep it blu :highfive:

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

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

I am only interested on debugging stuff in stock and 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.

Custom build isn't compatible with EAS stuff.

Also don't go spam and bug reporting on ROM threads if using this.

If you like my work, donations are always welcome.

Don't forget to hit thanks and rate the thread nicely, it's free ;)
[OnePlus 3 & 3T Cross Device Development] antoniobarros:
Sorry for me this change is a novelty.

after flash on EXMK, wakelock can no longer be selected.

But r182 blocks some ones of the default right? Or now r182 no block anything? and I need block wakelock one to one?

But the WL blocker zip I did not understand what it was for.

an explanation easy to understand for less experienced thanks a lot
[OnePlus 3 & 3T Cross Device Development] habylab:
I agree, could we have more of an explanation? Why would we want wakelocks not blocked by default anymore, as I can see in the changelog? Will look at Git when home.

Edit: apologies, you're right, nothing as default. As you were!
[OnePlus 3 & 3T Cross Device Development] eng.stk:
The explanation is on the release post.

Want to know more follow the link.

The zip as an init.d script inside, you need to extract it obviously.

The new driver allows people to add any wakelock source they want, without me having to add them one by one.

The script allows to do that in a simple way (while there's no tools with controls for it at least).

blu_spark never had any wakelock blocked by default. I don't run any blocks myself, stock behavior.
[OnePlus 3 & 3T Cross Device Development] laupuy:
Hi,

Thanks for this new kernel, as usual good on latest OpenBeta :good:

I think that if the phone is configured properly, the blockers are useless.

They could be useful for newbies, but their usage requires skills ... paradoxical!

PS: I like (pretty much) the new bootanimation :D
[OnePlus 3 & 3T Cross Device Development] 4uperko:
Got no wifi on r182. Back on r181 - all good. OB24.
[OnePlus 3 & 3T Cross Device Development] dugi9991:
You can't blame the kernel just like that without proof. In 99.9% of situations, the order of flashing is to blame - people tend not to flash the kernel last or something else kills the WiFi.
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
No problem here with WIFI using the newest Blu_Spark Kernel and newest Open Beta
[OnePlus 3 & 3T Cross Device Development] rezapatel:
I'll second no wifi issue on latest open beta.
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
Good job on the newest Open Beta OnePlus :good:

Blu_Spark r182 works without any issues here as always :highfive:
[OnePlus 3 & 3T Cross Device Development] maxq1:
tireless & impeccable work as always, blu! you deserved that black cheeseburger! all good here on the stable front..though seriously considering jumping into the betas
[OnePlus 3 & 3T Cross Device Development] bartolinio:
hmmm... I have the same kit, ie beta 24 + bluespark 182, and my blueborne test is negative :rolleyes:
[OnePlus 3 & 3T Cross Device Development] laupuy:
Maybe because of this :

Please note: We have patched the blueborne vulnerability independent of the Android security patch. Therefore, some blueborne vulnerability scanners may not recognize our independent patch.

Source https://forums.oneplus.net/threads/oxygenos-open-beta-24-15-for-the-oneplus-3-and-oneplus-3t.630890/

But OT on kernel thread...
[OnePlus 3 & 3T Cross Device Development] loveuhp:
lost DeepSleep
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Here:

Nothing to do with kernel.
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
Yes but it's weird that he uses the same setup as I do and the BlueBorne scanner shows my device as safe and his not. Pretty weird.
[OnePlus 3 & 3T Cross Device Development] pookybear:
Perhaps, his Bluetooth was turned off when he was checking it.
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
Why should it make a difference if Bluetooth is on or not? I mean your system is either patched or not.

I just tried it with Bluetooth on and off and both times the scanner says I'm safe.
[OnePlus 3 & 3T Cross Device Development] nathanchance:
Are you updated to the September security update? Because Blueborne is a combination of five CVEs for Android:

CVE-2017-0781

CVE-2017-0782

CVE-2017-0783

CVE-2017-0785

CVE-2017-1000251

The first four are fixed via the September security update so that's when you'll show as passing since that's really all the app checks for anyways; people have changed their string via a build.prop editor and they passed lol. The last one is fixed via the kernel patch I linked earlier.
[OnePlus 3 & 3T Cross Device Development] devilth48:
OnePlus have created an own patch for this.
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
A couple of days ago when [MENTION=3873953]eng.stk[/MENTION] updated his Kernel with the BlueBorne fixes on the Kernel side the scanner said I'm still vulnerable which made sense since it also had to be fixed on the ROM side and OOS Open Beta didn't have the fix yet. Yesterday OnePlus posted a new Open Beta and said that they have their own patch for Blueborne and it works even if they haven't updated the Android security patch to September (it's still on August in the settings).

Well apparently they say the truth because once I updated the ROM yesterday the BlueBorne scanner said I'm safe. It's just weird that someone with the same system Setup as me (Blu_Spark Kernel + newest OOS Open Beta) has a failed mark while I pass the BlueBorne scan.
[OnePlus 3 & 3T Cross Device Development] laupuy:
Hi,

did you run the same app bluborne scan?

Because:

Please note: We have patched the blueborne vulnerability independent of the Android security patch. Therefore,

some blueborne vulnerability scanners

may not recognize our independent patch.

source: https://forums.oneplus.net/threads/oxygenos-open-beta-24-15-for-the-oneplus-3-and-oneplus-3t.630890/

;)

Hi, The flash ;)

PS. yes I repeat :p
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
Well I don't know what Blueborne scanner he used but I used this one:

https://play.google.com/store/apps/details?id=com.armis.blueborne_detector
[OnePlus 3 & 3T Cross Device Development] fanbogo:
Thanks for another great update:D

Again I feel it's faster
[OnePlus 3 & 3T Cross Device Development] eng.stk:
On the other news: currently testing new f2fs backports updates :fingers-crossed:
[OnePlus 3 & 3T Cross Device Development] andyman_187:
Will this solve performance degradation on f2fs?
[OnePlus 3 & 3T Cross Device Development] bartolinio:
Yes, performance degradation on f2fs is hopeless, very strongly felt
[OnePlus 3 & 3T Cross Device Development] fanbogo:
Hi mate. Could you check background music while screen is off is OK for you? I got problem with sound or someone else?

With fastlane on
[OnePlus 3 & 3T Cross Device Development] marf28101995:
Everything is fine here

Streaming with play music and no problemo
[OnePlus 3 & 3T Cross Device Development] eng.stk:
We'll see. Already found issues with f2fs new extensions and sdcardfs, not all that happy :(
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
No problem here using the latest OOS Open Beta and Blu_Spark r182

I use Poweramp and Spotify as my main music player Apps.
[OnePlus 3 & 3T Cross Device Development] PivotMasterNM:
SultanXDA actually abandoned f2fs because of the many instabilty issues, and forces his ROM users to use ext4.

Do you think that f2fs is still worth it? I'm interested in everybodys opinions and experiences, as I am currently thinking about switching back :/
[OnePlus 3 & 3T Cross Device Development] laupuy:
Hi,

You can use whatever suits your needs. For some it's a dealbreaker, for others it isn't.

If people stopped using someting everytime a bug is found, you would be using paper and pencil still.

Give it some time, I'm sure a solution will come.

source: eng.stk https://xdaforums.com/showpost.php?p=73160142&postcount=5961

;)
[OnePlus 3 & 3T Cross Device Development] PivotMasterNM:
thx for the quote, but I am also interested in other peoples opinions :)
[OnePlus 3 & 3T Cross Device Development] eng.stk:
OP3 came back from expensive 100€ forced vacations...
[OnePlus 3 & 3T Cross Device Development] Crazy_Oni:
Gone is the spiderapp [emoji106]

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] zarocks:
Delete

---------- Post added at 03:43 AM ---------- Previous post was at 03:42 AM ----------

Magisk?
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
Yes I use Magisk
[OnePlus 3 & 3T Cross Device Development] fanbogo:
Cracked screen? I cracked mine, I dropped it from about 2-3 cm :) lucky me I had insurance
[OnePlus 3 & 3T Cross Device Development] pxrave:
I switched back to ext4 much more Stäbe and no slow down... Look at op5 there is no f2fs anymore... They learned Form op3... So be a clever user and use ext4 will be very stable in all Linux kernel since years +faster boot +nobug +better battery
[OnePlus 3 & 3T Cross Device Development] :
Awesome!!
[OnePlus 3 & 3T Cross Device Development] 4uperko:
Think it's because of Xposed framework. Without it got no Wifi problems.
[OnePlus 3 & 3T Cross Device Development] marf28101995:
So you came here reporting wifi problems with Xposed installed

Tell me more about you Einstein
[OnePlus 3 & 3T Cross Device Development] fbf2201:
As I told you, about 100€. :) Actually, for a screen repair, including material, it's not that bad.

Where was yours shipped to for repair? Mine went from Germany to Poland with UPS.
[OnePlus 3 & 3T Cross Device Development] PivotMasterNM:
that's actually pretty inexpensive for a screen repair. most retailers here in Germany are asking up to 200€:crying:
[OnePlus 3 & 3T Cross Device Development] vatsal8286:
voice calls is taking too much of battery...what is the solution for this.
[OnePlus 3 & 3T Cross Device Development] laupuy:
Hi,

try sms...

Sorry but not kernel related so better to open a new tread here: https://xdaforums.com/oneplus-3/help
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
I do use Xposed but I don't have any WiFi problems whatsoever
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Yeah, I don't call it a bargain by the retail price of the device, but still a lot cheaper than those 3rd party fixers.

Yep, european repair center is in Poland.

UPS worked very fast with free accurate service and next day deliverys, but 2 weeks to change a screen seems a bit too much.

Not a bad after sale service, but hope they can improve speed in the future.
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
Anybody here who has probelms with a system process called "mm-qcamera-daemon"? It drains my battery if I don't force stop it and it seems to go crazy out of nowhere.
[OnePlus 3 & 3T Cross Device Development] BIGWORM:
Too hard to replace the screen yourself? Though, I will admit, I don't know the availability of replacement parts in EU...especially since the 3/3T isn't being produced anymore. =(
[OnePlus 3 & 3T Cross Device Development] dreinulldrei:
I was wondering if the F2FS garbage collection issue has been resolved. Last time I tested this my write speeds were rather slow.

I am asking because Paranoid Android claims their latest release has a workaround for it:

"Included workaround for F2FS GC which makes F2FS usable without concerns again"

https://www.xda-developers.com/para...mization-features-blueborne-patches-and-more/
[OnePlus 3 & 3T Cross Device Development] abhaykelkar:
Does anyone know how to update blu_spark twrp recovery. I am currently having v39 and i want to update to v43. Please does anybody knows about that?

Will everything work as usual after the update? I mean its password dialog box and how to skip that. Thanks in advance.
[OnePlus 3 & 3T Cross Device Development] mabor01:
Just download the .img-file and reboot your device to recovery. Then choose install and the option of image files, you will see the downloaded file and flash it. Afterwards reboot to recovery, not sytem, and you will see the updated twrp version. Check if Everything is okay and then restart to system....
[OnePlus 3 & 3T Cross Device Development] marf28101995:
If you read the last few pages you would see that we are currently test the new patches, it take some time to see if the GC attacks again so we are testing it, anyway a beta will be released soon

Just flash the update in TWRP , instead of flashing zip pick flash IMG and flash it to recovery partition and reboot
[OnePlus 3 & 3T Cross Device Development] dreinulldrei:
I must have missed that so thanks for letting me know.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
Userspace camera stuff, nothing to do with kernel.

The fixes are present in the latest f2fs-stable backport I had merged for testing, I didn't released it yet because of some issues I found with sdcardfs.
[OnePlus 3 & 3T Cross Device Development] eng.stk:
No point of doing stuff on your own and actually pay more and lose the warranty...
[OnePlus 3 & 3T Cross Device Development] BIGWORM:
Forgot about the warranty thing. That's different over in EU, right? More consumer-friendly? On OOS, my E-Warranty Card said it expired on 1/23. I'm assuming that's the day I unlocked my bootloader lol!
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r186 unified

All right crew!

New build is up :highfive:

Because of latest TWRP changes, you'll need to use latest TWRP 3.1.0-1+ or flash my unified TWRP 3.1.1-x blu_spark v44 (recommended).

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

Although all went fine in testing, backups are recommended because of f2fs changes.

This build features latest wifi updates, blu_active goodies and f2fs fixes.

I decided not to merge full f2fs-stable backport v4.14-rc1-3.18 because of sdcardfs derps. I will look into ii in the future if I can, for now I decided to merge the gc cherry picks (which also features in aospa), to tackle the most important.

blu_spark_r186-oos_op3-op3t_62483ec.zip

blu_spark_r186-custom_op3-op3t_248540e.zip

Keep it real, keep it true, keep it blu :highfive:

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

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

I am only interested on debugging stuff in stock and 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.

Custom build isn't compatible with EAS stuff.

Also don't go spam and bug reporting on ROM threads if using this.

If you like my work, donations are always welcome.

Don't forget to hit thanks and rate the thread nicely, it's free ;)
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark extras v44

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) and some specific device fixes.

This matches latest f2fs fixes, it will be the last build for N :good:

edit 25/09/2017: v44 was refreshed, download and flash it again

twrp-3.1.1-x_blu_spark_v44-op3_op3t.img

Keep it real, keep it true, keep it blu :highfive:

You should also take a look to the systemless Magisk modules, if you need those:

Disable sdcardfs Magisk module (not needed on OOS 4.1.5+)

Touchscreen FW update Magisk module (not needed on OOS 4.1.7+)

Wakelock blocker info and example script

I'm just sharing my personal mods since people asked, meaning no support will be given (don't bother post about it).

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.

Don't forget to hit thanks and rate the thread nicely, it's free ;)
[OnePlus 3 & 3T Cross Device Development] Skinpipe:
i did a fresh f2fs install today on 182 and v43 blu_twrp, would i benefit from another clean flash using your updated v44 blu_twrp?

thanks
[OnePlus 3 & 3T Cross Device Development] habylab:
Just to be clear, the GC fixes won't help those that have suffered already? It will just help if we reformat?
[OnePlus 3 & 3T Cross Device Development] marf28101995:
I will say yes but it's not like day and night if you don't have time right now do it when you have time no problem ;)
[OnePlus 3 & 3T Cross Device Development] Skinpipe:
If I nandroid to my computer, reformat using v44 then restore my nandroid, will I then have the benefits for f2fs?

I appreciate your advice.
[OnePlus 3 & 3T Cross Device Development] marf28101995:
Yes mate you can also do it that way
[OnePlus 3 & 3T Cross Device Development] Flasher8:
Btw Oos stable 4.5.0 been released. ;)
[OnePlus 3 & 3T Cross Device Development] avalx:
And blu_spark r186 works with it! :cool:
[OnePlus 3 & 3T Cross Device Development] eng.stk:
blu_spark r188 unified

All right crew!

New build is up, fastlane speed style :highfive:

Because of latest TWRP changes, you'll need to use latest TWRP 3.1.0-1+ or flash my unified TWRP 3.1.1-x blu_spark v44 (recommended).

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

Although all went fine in testing, backups are recommended because of f2fs changes. TWRP 3.1.1-x blu_spark v44 was refreshed with new kernel, download and flash it again.

This kernel build features latest OOS 4.5.0 source, wifi updates and further f2fs fixes.

blu_spark_r188-oos_op3-op3t_2cff7f0.zip

blu_spark_r188-custom_op3-op3t_ed5b2fd.zip

Keep it real, keep it true, keep it blu :highfive:

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

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

I am only interested on debugging stuff in stock and 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.

Custom build isn't compatible with EAS stuff.

Also don't go spam and bug reporting on ROM threads if using this.

If you like my work, donations are always welcome.

Don't forget to hit thanks and rate the thread nicely, it's free ;)
[OnePlus 3 & 3T Cross Device Development] sasa.kljucaric@yahoo.de:
Thank you very much for the awesome kernel. The best Kernel for our device. Great and superb work.
[OnePlus 3 & 3T Cross Device Development] Hatshipuh:
Now all the f2fs fixes are there literally 2 days after I reformatted and returned to ext4...

Well this kernel works great with ext4, so I won't change again...for now. Pushing all the data back and forth was too much a hassle.
[OnePlus 3 & 3T Cross Device Development] marf28101995:
That was fast !!!
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
Anybody tried r188 with the newest Open Beta? as I wait for the FreedomOS dev to update to the newest stable version of OOS.
[OnePlus 3 & 3T Cross Device Development] Crazy_Oni:
Runs and makes no problems so far.

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[OnePlus 3 & 3T Cross Device Development] habylab:
How much of a difference have you noticed between the two filesystems on Blu Spark?
[OnePlus 3 & 3T Cross Device Development] bartolinio:
so far? massive
[OnePlus 3 & 3T Cross Device Development] GeloFight:
With r188 I lost soft calibration on last open beta
[OnePlus 3 & 3T Cross Device Development] laupuy:
Hi,

Yes, it's normal.

-> cf changelog:

Synchronize codes for OxygenOS 4.5.0

Revert all OB code
[OnePlus 3 & 3T Cross Device Development] GeloFight:
Yes I saw the changeling but last point is "incremental update" so for that reason I thought that was for open beta as well :p
[OnePlus 3 & 3T Cross Device Development] deepongi:
anyone with the cpu frequencies always at the highest step of the cluster? and lag.

latest build, #188

ill try a clean install of OOS 4.5 meanwhile.

edit: cpu governor was set to performance, despite not having any app to control kernel.

edit #2: and it returns to performance, even after reboot.

edit #3: seems solved, after a full wipe, and reflashing 4.5 boot img.. :)
[OnePlus 3 & 3T Cross Device Development] habylab:
In what sense? I know the tests initially were being faked by OP.

Also, does anyone know an answer to the above?
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
So the new colour calibration from the last 2 previous Open Betas is gone after flashing r188 and there is no way of getting it back besides downgrading?

I'm actually one of the few persons who liked the new calibration.
[OnePlus 3 & 3T Cross Device Development] edukastillo:
That new calibration is a ROM feature, so, yes, you will need to downgrade to get it working.
[OnePlus 3 & 3T Cross Device Development] Hatshipuh:
I had reformatted with f2fs once before after I got hit with the performance degration. Performance was back up for a while, but then it hit me again. Even with that zero file workaround it never really went back up.

Then I read that OP5 returned to ext4 too, so I decided to revert back to ext4.

The benchmark results were pretty much the same as with f2fs after a fresh reformat, and in daily use it doesn't feel any different than before.

I'm playing a demanding game and while on f2fs I was lagging heavily. That lag was there independent from kernel and clean flashes, and I thought it's just lack of optimization from the game developer's side or serversided. But that lag is instantly gone after going back to ext4, but that might as well be from the reformat resulting factory reset, though on f2fs even clean flashes never made a difference.

But that's all with the f2fs before the fixes, since I don't feel any real disadvantage on ext4, I'm in no rush to change again, maybe sometime when I have more time at hand and feel so bored that I want to push all the on storage photos back and forth. (No not using cloud :rolleyes:)
[OnePlus 3 & 3T Cross Device Development] laupuy:
Hi,

I think DCI-P3 can be enabled by a terminal, but I can't see soft calibration...

Or stick on r182 or 186

;)
[OnePlus 3 & 3T Cross Device Development] laupuy:
Hi, not only rom but also kernel ;)
[OnePlus 3 & 3T Cross Device Development] Scarface1991:
Ok I see so I won't update to r188 then because the soft calibration kinda really grew on me. [MENTION=3873953]eng.stk[/MENTION] would it be possible to bring it back on the Kernel side?
[OnePlus 3 & 3T Cross Device Development] laupuy:
Hi,

Yes, this is a known "issue" to some users, but only because of bad settings / flash / root.

I remember reading this (but when and where?) so a quick search should answer you ;)