[KERNEL] [blu_spark r226 unified OP5/5T] [A10 unified]

Search This thread
By:
Advanced…
brmbjn

brmbjn

Senior Member
Mar 17, 2015
1,009
155
Bojonegoro
OnePlus 8
OnePlus 8 Pro
eng.stk said:
All right crew!

New Oreo build is up :highfive:
Oreo builds are unified, also good to go on 5T Oreo stuff :good:

Because of latest TWRP and Oreo changes, you'll need to use TWRP 3.2+ or my unified TWRP 3.2.1-x blu_spark v8.69 (recommended).
Any other versions may not have full support for the kernel and the installer.

Also mind that for now on builds will touch system partition (Oreo stuff).
So, if you want to go back to stock, just backup boot and system beforehand or dirty flash you ROM zip.
If coming from other kernel always dirty flash your ROM (and root if that's the case) beforehand.

@Gentilsatan PM'ed this commit today https://github.com/EAS-Project/AnyKernel2/commit/ce662605bef9432f0d9dc9efc28556b23f6e221a, it seems that this userspace change (disable filtering that is) could make wifi connections not dropping, etc.
I went ahead and tried to fix it properly on the kernel, from internal testing seems like it's all good :)
Tagged it beta for the time being, test it out and let me know :fingers-crossed:

This is for Oreo only.


blu_spark_r100-oos-oreo_op5-op5t_f875f3d.zip
blu_spark_r100-custom_oreo_op5-op5t_4cfcc60.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).
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.


No mirrors please

If you like my work, donations are always welcome.
Don't forget to hit thanks and rate the thread nicely, it's free ;)
Click to expand...
Click to collapse
Nice
 
  • Like
Reactions: Dieppy, Chaplan, eng.stk and 1 other person
dajumper

dajumper

Senior Member
Jun 28, 2008
1,954
311
44
1518555934069.jpg

That qril is this related to the kernel ? Because in stock kernel I don't have that.

Sent from my ONEPLUS A5000 using XDA-Developers Legacy app
 
Chaplan

Chaplan

Senior Member
Jan 8, 2008
1,334
2,243
No Place
Xiaomi Mi Pad 4
Google Pixel 4a
Sc4r3Crow said:
Try this:

- Deactivate trust agent
- Reboot your device
- Activate trust agent

After that face unlocker should (hopefully) work again...
Click to expand...
Click to collapse
You quoted the wrong user ?.
I'm using face unlock (the real deal on OOS) without a problem.

You guys are again talking about trusted face and calling it face unlock.
When asking for help out or reporting something even if OT, and I'm not saying you should report OT stuff, for the very least share the setup you are on.

ROM, kernel build... We do guess a lot but with mixing feature names come judgment errors.
Your solution seems solid, although I can't see how kernel would break trust agent upon being flashed.
 
Last edited:
  • Like
Reactions: eng.stk and Dieppy
S

Sc4r3Crow

Senior Member
May 18, 2017
1,163
211
Chaplan said:
You quoted the wrong user .
I'm using face unlock (the real deal on OOS) without a problem.

You guys are again talking about trusted face and calling it face unlock.
When asking for help out or reporting something even if OT, and I'm not saying you should report OT stuff, for the very least share the setup you are on.

ROM, kernel build... We do guess a lot but with mixing feature names come judgement errors.
Your solution seems solid, although I can't see how kernel would break trust agent upon being flashed.
Click to expand...
Click to collapse

Oh, sorry bro...I tapped on the wrong post in my xda app (maybe my fingers are too big for the device's screen ;) )
I know the difference between trusted face and face unlock, and just reffered to the used designation in the other post :good:
 
Chaplan

Chaplan

Senior Member
Jan 8, 2008
1,334
2,243
No Place
Xiaomi Mi Pad 4
Google Pixel 4a
Sc4r3Crow said:
Oh, sorry bro...I tapped on the wrong post in my xda app (maybe my fingers are too big for the device's screen ;) )
I know the difference between trusted face and face unlock, and just reffered to the used designation in the other post :good:
Click to expand...
Click to collapse
No problem. I just got notified, through Wi-Fi, no delays ? and thought I would tell you because the user in need didn't get quoted. LOL

About the designation, I know you do, we have been through that 3 days back on the same coffee table.
I didn't remember you by name at first though.
That part wasn't specifically for you but for the
general user base that like myself participate on XDA actively.

I flashed this and that doesn't work is clearly laziness postage habits. I report stuff that I find strange here and there, I always post my setup, and I make sure it's inline with what's supported.
Steps to reproduce and most of the times logs.
Simple, straight forward and crystal clear.

Again, this is not specifically for you. Keep up. :good:
 
  • Like
Reactions: ixor00
S

Sc4r3Crow

Senior Member
May 18, 2017
1,163
211
Chaplan said:
No problem. I just got notified, through Wi-Fi, no delays ? and thought I would tell you because the user in need didn't get quoted. LOL

About the designation, I know you do, we have been through that 3 days back on the same coffee table.
I didn't remember you by name at first though.
That part wasn't specifically for you but for the
general user base that like myself participate on XDA actively.

I flashed this and that doesn't work is clearly laziness postage habits. I report stuff that I find strange here and there, I always post my setup, and I make sure it's inline with what's supported.
Steps to reproduce and most of the times logs.
Simple, straight forward and crystal clear.

Again, this is not specifically for you. Keep up. :good:
Click to expand...
Click to collapse

I don't feel offended, don't worry and thanks for the hint quoting the wrong post ?

For anti-spamming purposes I won't quote a 2nd time, if the other user is interested in an answer, s/he will hopefully read some posts and see my quotation and maybe other ones.

Referring to the details you mentioned which a request should contain (rom, kernel etc.)...I fully agree, makes it easier to answer adequatelly ?
 
  • Like
Reactions: ixor00, marf28101995, eng.stk and 1 other person
You must log in or register to reply here.

Similar threads

D
[EOL][11.0][OFFICIAL] LineageOS 18.1 for Oneplus 5 & 5T
Replies
899
Views
183K
Fostel
Fostel
P
[ROM][UNOFFICIAL][BETA][10.0] NitrogenOS [Op5/5t][24-08-2020]
Replies
625
Views
86K
R
Raideep
mukesh22584
[ROM][A12][GAPPS] XTENDED XS-Tribute To Vladimir [Oneplus 5 & 5T][ 19 Feb 2022 ]
Replies
1K
Views
151K
K
kirknado18
P
[ROM][11.0] Yet another AOSP project [OP5/5T][ALPHA][26-10-2020]
Replies
175
Views
62K
thaidroid
thaidroid
D
[12.1][OFFICIAL] LineageOS 19 for Oneplus 5 & 5T
Replies
472
Views
92K
K
KatayHan

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 248
    eng.stk
    eng.stk
    DWHxIK

    Kernel features:
    • Build with custom toolchain blu_gcc-11.2 (cortex-a73.cortex-a53 targeted, build from gcc-11.1.0 snapshot with latest bleeding edge components)
    • Full -O2 build with device and target flags enhanced, linaro build improvements, etc
    • Less is more: stockish OP5 builds based on OnePlusOSS/android_kernel_oneplus_msm8998
    • Systemless installer (doesn't touch system partition, OTA friendly), AnyKernel3 backend (compatible with autoflash apps)
    • Removed some debug and logging options
    • ARM enhanced performance and battery patches
    • CVE security patches, general upstream and CAF fixes
    • Several CPU Governors (blu_active modded own governor by default - fastlane mode available!)
    • No OC, use 250HZ kernel timer frequency
    • msm_performance input boost toggle on/off (enabled by default), tweaked cpu_boost driver
    • Enhanced TCP methods (westwood is default), Network and Wifi tweaks and updated drivers
    • Several I/O control tweaks, added schedulers FIOPS and ZEN v2 is default, tweaked and upstreamed filesystems (F2FS, ExFAT, NTFS, CIFS & NFS)
    • Removed verify and doesn't force encryption, patched SafetyNet flags to pass CTS
    • Stock thermal driver by default (custom tunables available for ROMs with no thermal daemon)
    • Disabled hotplug, also on low battery levels (CTL and BCL)
    • Optimized crypto routines
    • ZRAM Swap (LZ4) and adaptive LMK on by default
    • Vibrator Strength tunable and Gesture Haptic Feedback control (touchpanel and FPR)
    • KGSL fixes and reworked GPU driver (goes to idle @ 180MHz)
    • adrenoboost enabled by default at low level
    • KCAL - Advanced color control for Qualcomm MDSS v2 (RGB calibration and post-processing features)
    • KLAPSE support (v5.0)
    • Backlight min brightness option
    • USB Fast Charge (USB mode up to 900mA with MTP on)
    • Battery/Notification LED control
    • FS fsync toggle on/off
    • Wakelock blockers available
    • zx2c4's wireguard support
    • CDROM emulation on mass_storage (compatible with DriveDroid 0.10.36+)
    • Compatible with Kernel Adiutor, EXKM, FKM and others


    DOWNLOAD KERNEL ZIP
    FKM download configs: oos | custom
    Extras download location
    (No mirrors please)​


    Setup and troubleshoot: To install just flash the zip on a stock setup with either TWRP or autoflash kernel app.
    If you come from other kernel or have any issues, you should restore your stock boot.img or dirty flash your ROM before flashing blu_spark zip to avoid problems. Also uninstall or clean data of any kernel control app you're using.
    If you are upgrading between blu_spark versions, just flash the kernel zip.

    About bugs and reports: don't bother to post if a log isn't ready or without steps so the behavior can be replicated. I only active support stock OOS ROM with NO mods whatsoever (apart from root). That includes NO support if using xposed, Magisk with added modules, etc.
    If you're using custom ROMs (including stock based ones) and OOS Open Betas you're much on your own. I'm mostly interested on debugging stuff in stock and stable OOS.
    Also try not to spam the thread with OT. There's threads for all kind of stuff, use them.

    Going back to stock: This kernel installer doesn't change your filesystem. You can backup your boot.img with TWRP or kernel app before flashing blu_spark if you want to go back to full stock or just dirty flash your full ROM.


    OnePlus 5 development unit donated by OnePlus. Big shouts to them :)
    Very proud of being on the OnePlus Developer Program, special thanks to Adam K. for being such a supportive person.


    Contributors
    eng.stk
    Source Code: https://github.com/engstk/op5
    View
    100
    eng.stk
    eng.stk
    blu_spark r8

    All right crew!

    First build of your favorite kernel is up. Wicked!

    Just got an OP5 developer unit yesterday from Oneplus, so today you already have a fully featured blu_spark build.
    Most of the features you are used to from blu_spark on OP3/3T and others are in, this first build was compiled with Linaro GCC 5.4 (blu_naro 7.1 build still need some work).
    Pretty happy with the stable and smooth base, next weeks will bring more of the usual goodies, there's still lot's of room for improvements :fingers-crossed:

    blu_spark_r8-oos_op5_49e4692.zip

    • First public build (check OP and github for details)
    Click to expand...
    Click to collapse

    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.


    pp-acceptance-small.png

    If you like my work, donations are always welcome.
    Don't forget to hit thanks and rate the thread nicely, it's free ;)
    View
    57
    eng.stk
    eng.stk
    blu_spark extras v9.110

    All right crew!

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

    Fully synced with TWRP 3.3.1+, name changing to reflect base 9.version, full compatible with Pie stuff (you need Pie fw also) and A10 custom ROMs will work also (OMNI tested)
    TWRP blu_spark edition is unified, works for both OP5/5T.
    Delete your twrp settings or else issues may arise if coming from other version besides blu_spark.
    This build is treble ready, allowing /vendor partition operations. If you don't use treble enabled ROMs, ignore any vendor errors that may appear, TWRP will work just fine.


    twrp-3.3.1-x_blu_spark_v9.110_treble-op5_op5t

    • build: TWRP 3.31-x | blu_spark v9.110
    • Supports Android 10
    • /sbin should come first in the linker search path
    • Move decryption error from logerror to loginfo
    • Encryption: don't try wrapped key if not needed
    • Removing fake error: E: recv error on uevent
    • bootable: read all asserts in case there are more than one.
    • Prevent errors caused by /data/per_boot/
    • crypto: add some missing newlines
    • Complete overhaul of Dutch translation:
    • recovery: wipe bootloader message from index 0 when using custom offsets
    • android-5.1: use char constructor for default on c++ streams
    • recovery: Move bldrmsg offset symbols to bootloader_message.cpp
    • Encryption: try wrapped key also for device without metadata support
    • ldconfig: add /sbin to search.paths
    • Device specific changes here
    Click to expand...
    Click to collapse




    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 please
    If you like my work, donations are always welcome.
    Don't forget to hit thanks and rate the thread nicely, it's free ;)
    View
    56
    eng.stk
    eng.stk
    blu_spark r30

    All right crew!

    New build is up :highfive:
    Also take a look to the rest of blu_spark v43 extras to get some nice and useful additions to the kernel.

    This build features latest blu goodies 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 root 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_r30-oos_op5_28565f7.zip
    blu_spark_r30-custom_op5_28aae04.zip

    • build: use newest and improved blu_naro-7.2, build from developer snapshot Linaro GCC 7.2-2017.09, with updated components and improvements/fixes
    • blu_active: handle error for module load fail
    • defconfig: enable boeffla wakelock blocker
    • boeffla_wl_blocker: add generic wakelock blocker driver v1.0.0, update to wakelock blocker driver v1.0.1, update to wakelock blocker driver v1.1.0
    • boeffla_wl_blocker: don't block wakelocks by default
    • Revert singular wakelock block
    • Revert su expose workarounds
    • DASH: spoof normal usb fastcharge into android-7.1 (custom only)
    Click to expand...
    Click to collapse

    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).
    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 LOS 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.


    pp-acceptance-small.png

    If you like my work, donations are always welcome.
    Don't forget to hit thanks and rate the thread nicely, it's free ;)
    View
    48
    eng.stk
    eng.stk
    Merry Christmas for all the blu_crew :highfive:
    View

New posts