Melina Reborn
Melina returns for AOSP Support
If you loved Melina Kernel, you will be happy to hear that Melina Reborn has been developed with new V30A sources (as of rel_r5, Melina is now using more stable sources), with all of the features and performance you loved from Melina Kernel, but now with AOSP support! I did have to disable F2FS, if it is requested, I will try to re-implement it, but AFAIK it was never used on our devices anyway. Aside from F2FS everything else is available. Or should be
Tested on HavocOS-v3.2 on a US997 with BL 21E. (Note: My SD Card slot is broken. I cannot test any SDCard related issues. No issues are foreseen, but if any SDCard related issues happen to arise, please report them in as much detail as possible (dmesg, logcat, etc), as I cannot test SDCard functionality myself.)
Note: There have been reports of missing functionality under Pixel Experience Pie. This may occur on all Pie ROMs, but this is yet unknown. Pie was not tested, so consider this an Android 10 Only kernel for now.
"bootloop" note: Your G6 may reboot itself once after flashing my kernel, before reaching the OS boot animation. Do not panic, this is normal. I believe it is part of the Magisk recovery. If the bootloop occurs more than 1 time, even if it makes it to the OS, please report it here.
Primary Features:
Can now charge while powered off (offline charging) (rel_r5)
clang compiled and optimized kernel with extended armv8-a attributes (rel_r5) (for real this time!)
WiFi Hotspot working with properly configured ROM (rel_r5) (including 5ghz)
USB disconnect issues should be fixed (rel_r5)
Charging issues should be fixed (rel_r5)
Enabled FM Radio (requires supported ROM which currently there is none because it is still in testing, but looking promising)
Switched to more stable kernel sources (rel_r5) (see github readme)
Optimized and DEBUG editions (rel_r4)
Even more debug routines reduced (rel_r4)
Updated CPU optimizations one more time (tune for Kyro) (rel_r4) (this actually failed silently that is why rel_r4 was terrible)
More adjustments to reduce (and hopefully remove) the chance of random reboots (rel_r4)
Updated to AnyKernel 3, allows retaining Magisk when flashing kernel (rel_r3)
Module-less Kernel (rel_r3)
Removed old exFAT driver in favor of new sdfat driver (rel_r3)
Significantly reduce debugging messages/routines for performance enhancements (rel_r2)
Cleaner Kernel code, fixed all compiler warnings (with ubertc 6.x) (rel_r2)
Optimize compiler flags with big.LITTLE optimizations (rel_r2)
Updated AnyKernel Installer to place modules where they should be (rel_r2)
Fixed crashes due to missing 32-bit support (rel_r1.1)
Added maple iosched, enabled tcp westwood congestion sched
New kernel defaults: iosched (now: maple, was: cfq), tcp (now: westwood, was: bic) (Note: These default values may be overridden by the ROM. Be sure to use something like kernel adiutor to verify and set the values as desired.)
Binary releases built with ubertc aarch64-linux-android-6.x
DriveDroid CD-ROM Emulation Support
zzmove and elementalx governors
Various other improvements
Removes /sbin/rctd and related service entry in init.lge.rc if detected (for Stock ROMs, untested)
Remove forceencrypt (for Stock ROMs, untested)
Open source compatible replacement for Tuxera exFAT driver (removed in rel_r3, superseded by sdfat)
The following features from the original Melina Kernel are no longer available due to issues:
Flash Friendly FS (F2FS) Support
Downloads
Note: The difference between optimized and DEBUG is that the optimized version of Melina Kernel has extra debugging removed, which may increase battery life and performance slightly, but at the cost of making it harder to fix problems. The DEBUG kernel is more like most other kernels that are based on LGE official code, where LGE left on a lot of debug routines that aren't needed once the ROM is functional. However, those wanting to help fix issues, or ROM developers working on their ROM may want this extra information. This is why Melina Reborn now offers both kernels as an option.
rel_r5
US997: Optimized - DEBUG
H870 Optimized - DEBUG
H872 Optimized - DEBUG
rel_r4
US997: Optimized - DEBUG
H870 Optimized - DEBUG
H872 Optimized - DEBUG
rel_r3
US997
H870
H872
rel_r2
US997
H870
H872
rel_r1.1
US997
H870
H872
Known Issues
Some users have been reporting "random" reboots with rel_r1.1 and rel_r2. It seems linked to spi8 (fingerprint) and spi12 (touchscreen). An attempt to address this was added to rel_r3.
Attribution
For a full list of credits, please see the Github sources below, and browse the commit log. I try to keep commits as authentic as possible (except my own which I rebase and amend alot lol).
@TheWolfSVK for his work on the V30A sources, as well as for his incredible Havoc ROM
@osm0sis for AnyKernel3
Everyone who used and helped test the original Melina Kernel
When reporting any issues please be as detailed as possible. At a minimum, include your model and bootloader version. Any logs would be appreciated but I know sometimes it's not possible to get them (check for /sys/fs/pstore/console-ramoops). Also try to explain with as much detail as possible what you were doing when the problem happened (What app was active (running and on screen)? Which apps were in the background? Are you rooted? etc)
Github Sources
ROM Developers: You may include this kernel in your ROM so long as you link back to this thread in your release thread. If you modify any of the kernel or config, please also change the name from melinareborn to melinamodified in arch/arm64/configs/melina_common_android_intree_subconfig. This kernel can now be used in-tree while building Android, without clang, although ubertc may be required, untested (I built with ubertc in the tree, see here how to add Melina to a lineage-based G6 device tree.)
clang in-tree building now works and the bluetooth issue was found and addressed (don't ask, it was silly)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Guess who's back! Guess who's back! Haha welcome back! I know you thought about the song! Anyways to the point. Does this support stock as well? Since it uses 30A sources does that mean it can't be used on stock 8.0? It's essentially a pie kennel right? I loved custom ROMs but on TMobile using a phone as phone is hard without volte, vowifi. Still would love you to updateTWRP. It would also be nice if be you did it for v20 too. Since it's been basically the same phone. Although everyone with g5 would get jealous then. Haha! :silly::good::highfive:
Vortell said:
Guess who's back! Guess who's back! Haha welcome back! I know you thought about the song! Anyways to the point. Does this support stock as well? Since it uses 30A sources does that mean it can't be used on stock 8.0? It's essentially a pie kennel right? I loved custom ROMs but on TMobile using a phone as phone is hard without volte, vowifi.:
Click to expand...
Click to collapse
Stock is untested, I could not stand 21E long enough. Though Melina rel_o2 worked well for the 10 minutes I tried to deal with Stock
Have you tried Havoks? I don't have those services to test. If you can snag some logcats on Havoks' Android 10 of you trying to use the services, I will look at it but no promises)
Vortell said:
Still would love you to updateTWRP.
Click to expand...
Click to collapse
TWRP is in planning, since my SD is broken I can't test backups until my USB OTG arrive, should be tomorrow, but I have plans this weekend, and still have to try to fix the issue, so unknown ETA for TWRP.
Vortell said:
It would also be nice if be you did it for v20 too. Since it's been basically the same phone. Although everyone with g5 would get jealous then. Haha! :silly::good::highfive:
Click to expand...
Click to collapse
Depends on how technically it is the same phone. If it has the same hardware, perhaps a device config could be made.
zefie said:
Depends on how technically it is the same phone. If it has the same hardware, perhaps a device config could be made.
Click to expand...
Click to collapse
Both are msm8996 hardware and there is souces for the rest in older trwp page I think. It was just a wish I didn't think you would actually do it.
Vortell said:
Both are msm8996 hardware and there is souces for the rest in older trwp page I think. It was just a wish I didn't think you would actually do it.
Click to expand...
Click to collapse
I mean, if EVERYTHING was the same (except a few unique traits, kinda like the differences between H870, H872 and US997) then it wouldn't really be a problem. But if it even has a different camera, it becomes complicated.
zefie said:
I mean, if EVERYTHING was the same (except a few unique traits, kinda like the differences between H870, H872 and US997) then it wouldn't really be a problem. But if it even has a different camera, it becomes complicated.
Click to expand...
Click to collapse
I see I though blobs were easy, but I have yet to build for Android. If you want to take a look. After this post I promise no more off topic posts.
Here's a link to a kernel kind of like yours for v20:
https://forum.xda-developers.com/v20/development/kernel-gamma-kernel-t394011
Here's modified for stock kernel:
https://forum.xda-developers.com/v20/development/h918-h910-us996-ucl-mk2000-kernel-t3708330
Here's Los 17.1 for it from x86cpu who is same person who builds los for LG G6:
https://forum.xda-developers.com/v20/development/rom-unofficial-lineageos-17-0-lg-v20-t4010893
Here's TWRP for it:
https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
One last thing do you want me to test this on stock 8.0 LG G6 us997? I swear if havoc had volte I would never use anything else. My favorite ROMs are havoc , aicp and crdroid. I had Samsung S5 and it had dozens of ROMs to try. My note 4 had probably a dozen. LG v20 has probably 10, but only 3 current ones.
Vortell said:
I see I though blobs were easy, but I have yet to build for Android. If you want to take a look. After this post I promise no more off topic posts.
Here's a link to a kernel kind of like yours for v20:
https://forum.xda-developers.com/v20/development/kernel-gamma-kernel-t394011
Here's modified for stock kernel:
https://forum.xda-developers.com/v20/development/h918-h910-us996-ucl-mk2000-kernel-t3708330
Here's Los 17.1 for it from x86cpu who is same person who builds los for LG G6:
https://forum.xda-developers.com/v20/development/rom-unofficial-lineageos-17-0-lg-v20-t4010893
Here's TWRP for it:
https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
One last thing do you want me to test this on stock 8.0 LG G6 us997? I swear if havoc had volte I would never use anything else. My favorite ROMs are havoc , aicp and crdroid. I had Samsung S5 and it had dozens of ROMs to try. My note 4 had probably a dozen. LG v20 has probably 10, but only 3 current ones.
Click to expand...
Click to collapse
I'll look into the other device when I get a chance, but I'll be honest its pretty low priority. You can try the kernel on stock. I did score 3 months of Mint Mobile free during their (special american footbal game that has a huge trademark liability on its name) special and apparently they support VoLTE. No promises but I will try to look into it, as I am also working with the developer of Havoc.
Also be on the lookout for rel_r2, r1/r1.1 was kinda rushed, but I am working to further optimize r2, beyond even what the original Melina Kernel had.
zefie said:
I'll look into the other device when I get a chance, but I'll be honest its pretty low priority.
Click to expand...
Click to collapse
Either way always love a extra developer on any phone i own. If you are saying you hope to get volte working on custom ROMs for the g6 that's more impressive and should be a higher priority. I'm almost giddy just thinking about being able to use custom ROM with volte. It would open it up for at least g5 and v20. Assuming you open source it.
Also u will give it a try on stock and let you know.
Hey guys,
On stock pie V30B bluetooth isn't working on my h870 with all modified kernels I tried. Any suggestions? Thank you.
I'm glad that you're back zefie ?
Hi there . it doesn't work for me with the V30B Stock rum either. is there a modified kernel for stock pie?
Rothrex93 said:
Hi there . it doesn't work for me with the V30B Stock rum either. is there a modified kernel for stock pie?
Click to expand...
Click to collapse
It isn't for STOCK Rom this kernel is for AOSP ROMS. Stock kernel has a lot proprietary stuff.
SkylineDiT said:
It isn't for STOCK Rom this kernel is for AOSP ROMS. Stock kernel has a lot proprietary stuff.
Click to expand...
Click to collapse
Sorry you misunderstood. my Stock V30B rom to want a modified kernel. Has anyone done this already?
Rothrex93 said:
Sorry you misunderstood. my Stock V30B rom to want a modified kernel. Has anyone done this already?
Click to expand...
Click to collapse
Sorry, this is for AOSP and there is no plans for a Melina for stock Pie. You can thank LGE for abandoning the US997 Unlocked variant for the fact that I cannot make a Pie Stock kernel
Testing Melina Reborn kernel rel2 on H870 bootloader 20J ROM: PixelExpierence 2019-08-23-2221 (PIE). BT works fine battery is good performace great. Not working: camera, flashlight, NFC, and fastcharging. Will try to test rel3
I am using rl3 with havocOS 3.2 without issues.
I noticed that my device isn't heating as much as it used to.
Battery life is better.
H870.
I agree the melina kernel installation in TWRP preserved all magisk, viper settings in Havoc 3.2 07.02. All works from NFC to kernel adiutor settings e.g. cpu governor zzmove (very quick and more energy safe than performance) - no more powersave which mantained my phone very cool even during games, but was very slow in starting apps. Now my phone is slightly warm all the time, but very quick and responsive. Thank you very much zefie!
Hello, Sir can i install it on H870 with Havoc 2.9 ( Pie) with magisk installed ?
kurogami555 said:
Hello, Sir can i install it on H870 with Havoc 2.9 ( Pie) with magisk installed ?
Click to expand...
Click to collapse
There have been reports of it not working with PE Pie, not sure about Havoc Pie. The kernel may only work on Android 10, not sure yet.. If you do try it, be sure it have a backup of your current kernel.
Vortell said:
Either way always love a extra developer on any phone i own. If you are saying you hope to get volte working on custom ROMs for the g6 that's more impressive and should be a higher priority. I'm almost giddy just thinking about being able to use custom ROM with volte. It would open it up for at least g5 and v20. Assuming you open source it.
Also u will give it a try on stock and let you know.
Click to expand...
Click to collapse
Three things
1) What is the device model code (us996?) for a kernel for you to test
2) it won't work on stock and probably only Android 10 ROMs, if at all lol
3) still no eta
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Base: N7100 KK Sources
Linux 3.0.31
Compiled using latest ArchiToolchain 5.2.0
ArchiDroid Optimizations
Using AnyKernel method (compatible with all ROMs for both AOSP and Samsung)
And many other awesome things I have no time to list
ArchiDroid Optimizations:
- Fully optimized for Samsung Galaxy S3 (-marm -march=armv7-a -mcpu=cortex-a9 -mtune=cortex-a9 -mfpu=neon -mfloat-abi=softfp)
- Compiled with O3 optimization level (-O3)
- Performed interprocedural pointer analysis and interprocedural modification and reference analysis (-fipa-pta)
- Performed loop invariant motion on trees. It also moved operands of conditions that are invariant out of the loop, so that we can use just trivial invariantness analysis in loop unswitching. The pass also includes store motion (-ftree-loop-im)
- Created a canonical counter for number of iterations in loops for which determining number of iterations requires complicated analysis. Later optimizations then may determine the number easily (-ftree-loop-ivcanon)
- Performed induction variable optimizations (strength reduction, induction variable merging and induction variable elimination) on trees (-fivopts)
- Tried to reduce the number of symbolic address calculations by using shared “anchor” symbols to address nearby objects. This transformation can help to reduce the number of GOT entries and GOT accesses on some targets (-fsection-anchors)
- Assumed that loop indices do not overflow, and that loops with nontrivial exit condition are not infinite. This enables a wider range of loop optimizations even if the loop optimizer itself cannot prove that these assumptions are valid (-funsafe-loop-optimizations)
- Moved branches with loop invariant conditions out of the loop (-funswitch-loops)
- Attempted to avoid false dependencies in scheduled code by making use of registers left over after register allocation. This optimization most benefits processors with lots of registers (-frename-registers)
- Re-ran common subexpression elimination after loop optimizations are performed (-frerun-cse-after-loop)
- Didn't keep the frame pointer in a register for functions that don't need one. This avoids the instructions to save, set up and restore frame pointers; it also makes an extra register available in many functions (-fomit-frame-pointer)
- Made a redundant load elimination pass performed after reload. The purpose of this pass is to clean up redundant spilling (-fgcse-after-reload)
- Ran a store motion pass after global common subexpression elimination. This pass attempts to move stores out of loops (-fgcse-sm)
- Eliminated redundant loads that come after stores to the same memory location, both partial and full redundancies (-fgcse-las)
- Constructed webs as commonly used for register allocation purposes and assigned each web individual pseudo register. This allows the register allocation pass to operate on pseudos directly, but also strengthens several other optimization passes, such as CSE, loop optimizer and trivial dead code remover (-fweb)
- Performed tail duplication to enlarge superblock size. This transformation simplifies the control flow of the function allowing other optimizations to do a better job (-ftracer)
Click to expand...
Click to collapse
Download
What to expect:
- Awesome stock battery life on AOSP ROMs (due to Samsung sources and not smdk4x12)
- Blazing fast (Deep advanced optimizations, Linaro toolchain, this is the beast)
- High compatibility (AnyKernel method, the kernel should work on all ROMs)
What to expect in future:
- You tell me
What to NOT expect:
- Many CPU or I/O governors # We don't need overhead, you can achieve nearly the same just by tweaking governor to your needs
- Features I don't like/need
- Dualboot (see above ^)
- F2FS (see above ^, however this one depends on kernel upstreaming, as f2fs is merged)
ArchiKernel is provided in 4 different variants, 2 for AOSP ROMs and 2 for SAMSUNG ROMs.
AOSP -> 29 MALI blobs AOSP variant. Should cover all Lollipops for SGS3.
AOSP_OLD -> 23 MALI blobs AOSP variant. Should cover all KK and pre-KK ROMs for SGS3.
SAMSUNG -> 23 MALI blobs Sammy variant. Should cover all JB ROMs and also some KK ROMs based on N7100 port (such as ArchiPort)
SAMSUNG_NEW -> 29 MALI blobs Sammy variant. Should be used only on KK+ Sammy ROMs based on korean port
ArchiKernel is using my own AnyKernel flashing method, therefore it does not suffer from a need to update it with maintenance ramdisk updates, and that's one of the reason why it should work properly with all ROMs, even those not officially supported, as long as variant matches.
Flashing instructions:
1. Make sure that you have stock kernel already flashed (the one which comes with your ROM), if you're running custom kernel already, reflash your ROM without wipe, this will also flash stock kernel. This is ultimately important, DON'T FLASH ARCHIKERNEL ON ANOTHER CUSTOM KERNEL, you may face various issues you've never seen before.
* This is because ArchiKernel uses AnyKernel method - it pulls ramdisk from your current kernel. If you brick your phone by flashing AK on top of custom kernel, you know who will be responsible for that.
2. Flash ArchiKernel zip.
3. Profit!
Updating instructions:
1. If you arleady have older ArchiKernel version flashed properly with above instructions, and changelog doesn't state otherwise, just flash the .zip with new version of AK.
2. No wipes, cleaning dalvik cache or anything else is required, flashing zip is enough.
3. Profit!
Bugs:
None known
XDA:DevDB Information
[EOL] [KERNEL] [AOSP/Samsung/Ports] [ArchiToolchain 5.2] [01/10/15] ArchiKernel V2.1, Kernel for the Samsung Galaxy S III I9300
Contributors
JustArchi, Moster2
Source Code: https://github.com/ArchiDroid/ArchiKernel
Kernel Special Features:
Version Information
Status: No Longer Updated
Created 2014-06-17
Last Updated 2015-11-12
Reserved
Reserved
Last one.
Great job! Amazing to see a dedicated thread for this beauty.
Will report the experience
V1 uploaded in download section on the top of the thread. It should work with all AOSP ROMs but you tell me if it does. Don't flash it on Sammy (yet). Let me know if I screwed up something, it's late .
will test on omni,thanks
Well, I've been waiting for this thread since I read about "ArchiKernel" =D
I installed the kernel just a few minutes ago and I will test during this days to see how it behaves.
Q: Will you add support to customize it with an app (like TricksterMod, Stweaks or BoefflaConfig)? I'm just asking because I'm curious, I know is to early in development stage already to have this, but I just wanted to know
Thanks!
coto39 said:
Well, I've been waiting for this thread since I read about "ArchiKernel" =D
I installed the kernel just a few minutes ago and I will test during this days to see how it behaves.
Q: Will you add support to customize it with an app (like TricksterMod, Stweaks or BoefflaConfig)? I'm just asking because I'm curious, I know is to early in development stage already to have this, but I just wanted to know
Thanks!
Click to expand...
Click to collapse
At some point I'll definitely consider adding ArchiKernel support in ArchiDroid app, but it won't come too fast.
However, you can still "tweak it' in various ways. SetCPU, TricksterMod and similar apps are only a few examples. Boeffla Sound Control app (not boeffla config) will work as well. But think twice if you want to do, as ArchiKernel is pretty damn tweaked right after booting.
Flashed on Temasek's v98 and works perfectly. Just finished downloading boeffla sound app and I'm ready to rock this new toy :^P
Will report battery life and stuff later!
Keep your fine work up Archi. Cheers!
beeeto said:
Flashed on Temasek's v98 and works perfectly. Just finished downloading boeffla sound app and I'm ready to rock this new toy :^P
Will report battery life and stuff later!
Keep your fine work up Archi. Cheers!
Click to expand...
Click to collapse
If you want to know my opinion - Current smdk4x12 source used in all AOSP kernels is a crap. Somebody screwed up something really hard, I looked at the sources and there are over 7 hundred of different files (comparing to Update13), half of the updates from Update11, Update12 are not even included, while Update13 is not included at all. Whole kernel is one big mess and I have no idea how it even boots. It contains so many merge derps and hacks/workarounds that it hurts. I didn't even want to fix it, too much work to do. I started from clean stable and battery friendly Update13 base.
After flashing first alpha version of my kernel I immediately noticed significantly improved battery life, same as on Sammy ROM. So now I have my perfect combo, ArchiDroid 2.X AOSP speed and ArchiKernel Sammy battery life. Whatever you say, I'm keeping this baby. I love this kernel.
Big credit goes to @Yank555 and @Lord Boeffla because they're true kernel developers, I've made my own kernel based mostly on their commits (but not only, I added my own part as well and I'll add more soon).
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
JustArchi said:
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
Click to expand...
Click to collapse
Add it to the OP!
While not everyone actually reads even the first post, even fewer people would actually bother reading the whole first page.
JustArchi said:
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
Click to expand...
Click to collapse
Do i have to flash the whole r9m again then?
Sent from my GT-I9300 using XDA Free mobile app
skim0322 said:
Do i have to flash the whole r9m again then?
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
If need be, but the stock kernel alone should be enough if you get hands on a .zip.
Awesome
Sent from my GT-I9300 using Tapatalk
JustArchi said:
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
Click to expand...
Click to collapse
May I ask for a flashable zip file of the stock kernel..Thanks.:good: I would like to try this
JustArchi said:
Ah guys, and remember that this kernel uses AnyKernel method, which means that it will PULL ramdisk from your CURRENT kernel so for best results MAKE SURE that you're on STOCK kernel for your rom BEFORE flashing this.
Click to expand...
Click to collapse
i am on archidroid 2.4.6 with boeffla kernel.u mean that i cannot flash your kernel over my current kernel?
Are cam bugs gone since you did not upstream it to the 3.101?
Wysłane z mojego GT-I9300 przy użyciu Tapatalka
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kernel features:
Build with custom toolchain blu_gcc-8.2.0 (cortex-a73.cortex-a53 targeted, build with latest Crosstool-NG from GCC-8.2.0 snapshot)
Full -O2 build with device and target flags enhanced, linaro build improvements, etc
Less is more: stockish builds based on ztemt/NX609J_O_kernel
Systemless installer (doesn't touch system partition, OTA friendly), AnyKernel2 (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 100HZ base timer frequency
msm_performance input boost toggle on/off (enabled by default), tweaked cpu_boost driver (Dynamic stune available)
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
Swap and adaptive LMK off by default
Vibrator Strength tunable and Gesture Haptic Feedback control (touchpanel) [WIP]
KGSL fixes and reworked GPU driver
KCAL - Advanced color control for Qualcomm MDSS v2 (RGB calibration and post-processing features)
USB Fast Charge (USB mode up to 900mA with MTP on)
Battery/Notification LED control [WIP]
FS fsync toggle on/off
Wakelock blockers available
zx2c4's wireguard support
CDROM emulation on mass_storage (compatible with DriveDroid 0.10.36+)
init.d support (put your scripts in /system/su.d or /su.su.d [systemless SuperSU], /magisk/.core/post-fs-data.d [Magisk])
Compatible with Kernel Adiutor and others
DOWNLOAD KERNEL ZIP (No mirrors please)
Warning: If you come from other kernel or have any issues, you should dirty flash your ROM before flashing blu_spark zip to avoid problems.
Reflash ROM -> if you want root flash SuperSU or Magisk (default, no plugins/modules) -> flash blu_spark.
If you are already rooted or upgrading between blu_spark versions, just flash the kernel zip. Also uninstall or clean data of any kernel control app you're using.
About bugs and troubleshoots: 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 ROM with NO mods whatsoever (apart from root). That includes NO support if using xposed, Magisk with modules, etc.
Save the SOT and battery stats/screenshots for general threads, here we deal with development, not personal tastes and results.
Also don't spam this thread with LOS or other ROMs stuff like "this don't work, my app doesn't open, etc" , no OT about OTAs, apps, ROM bugs, Recovery/TWRP troubleshoots and other userspace stuff. There's threads for it, use them.
Going back to stock: This kernel installer doesn't change your filesystem. You can backup your boot.img with TWRP before flashing blu_spark if you want to go back to full stock or just dirty flash your full ROM.
If you like my work, donations are always welcome.
Don't forget to hit thanks and rate the thread nicely, it's free
Red Magic development unit donated by Nubia. Big shouts to them
Special thanks to Adam K. for being such a supportive person.
XDA:DevDB Information
blu_spark kernel for nubia redmagic, Kernel for the ZTE nubia Red Magic
Contributors
eng.stk
Source Code: https://github.com/engstk/redmagic
Kernel Special Features: Powered by sparky
Version Information
Status: Stable
Current Stable Version: r36
Stable Release Date: 2018-09-04
Current Beta Version: r25
Beta Release Date: 2018-07-06
Created 2018-07-06
Last Updated 2019-11-29
blu_spark r25
First blu_spark kernel build is up, go get here
blu_spark extras v8.82
All right crew!
Here's an updated TWRP with all the blu_spark goodies inside and fully synced with TWRP Android-8.1 branch (including more recent upstream than official TWRP) and some specific device fixes.
Fully synced with TWRP 3.2.2+, name changing to reflect base 8.version. decryption, backup & restore, MTP, USB OTG and other basic stuff are working.
Delete your twrp settings or else issues may arise if coming from other version besides blu_spark.
twrp-3.2.2-x_blu_spark_v8.82_redmagic.img
build: TWRP 3.2.2-x | blu_spark v8.82
minuitwrp: Respect TARGET_RECOVERY_PIXEL_FORMAT config in screenshot.
minuitwrp: Add support for QCOM haptics vibrator.
android: release 8.1.0_r32
General cleanup
Device specific changes here
Click to expand...
Click to collapse
Keep it real, keep it true, keep it blu :highfive:
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
blu_spark r28
All right crew!
New build is up :highfive:
Dynamic stune updates, wireguard updates and custom ROM support (use the custom zip, tested on OMNI)
Also checkout latest recommended blu_spark extras with blu_twrp v8.82
blu_spark_r28-redmagic_1903ca3.zip
blu_spark_r28-redmagic-custom_f9dba90.zip
sched/boost: Update functions for newer Dynamic Schedtune Boost changes
cpu-boost: Update functions for newer Dynamic Schedtune Boost changes
sched/tune: Rename dynamic_boost parameter to sched_boost, Switch Dynamic Schedtune Boost to a slot-based tracking system
sched/stune: Rename stune_boost() to do_stune_sched_boost()
wireguard updates (v0.0.20180708)
Anykernel2 updates
synaptics: split wakeup gesture types, cleanup and unify gesture codes with other devices (custom only)
defconfig: disable CONFIG_NUBIA_LCD_BACKLIGHT_CURVE (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 stock based ones).
Meaning, if using anything besides stock don't bother posting about it.
I am only interested on debugging stuff in stock international (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.
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
Man I'd like to try this. Still don't fully understand the process. I did a little messing around with my gs7 edge. Although it was pretty simple. Literally just flashed a custom stock rom with Odin and had SuperSU built it with rom controls and a simple tar img to flash to root and rom control easy unroot button. Was first time I was had a phone I could do something with. New territory for me. Will have to tread lightly lol.
Sent from my nubia Red Magic using XDA Labs
anyone of you have the stock android rom from this phone?
javier211086 said:
anyone of you have the stock android rom from this phone?
Click to expand...
Click to collapse
I have International Stock Rom with Play Store
blu_spark r31
All right crew!
New build is up :highfive:
Also checkout latest recommended blu_spark extras with blu_twrp v8.82
blu_spark_r31-redmagic_a9af12f.zip
blu_spark_r31-redmagic-custom_aa4e2d6.zip
proc: cmdline: remove additional nubia flags (fixes Magisk root factory reset on the Red Magic)
wireguard updates (v0.0.20180718)
Anykernel2 updates
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 stock based ones).
Meaning, if using anything besides stock don't bother posting about it.
I am only interested on debugging stuff in stock international (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.
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
blu_spark extras v8.83
All right crew!
Here's an updated TWRP with all the blu_spark goodies inside and fully synced with TWRP Android-8.1 branch (including more recent upstream than official TWRP) and some specific device fixes.
Fully synced with TWRP 3.2.3+, name changing to reflect base 8.version. decryption, backup & restore, MTP, USB OTG and other basic stuff are working.
Delete your twrp settings or else issues may arise if coming from other version besides blu_spark.
twrp-3.2.3-x_blu_spark_v8.83_redmagic.img
build: TWRP 3.2.3-x | blu_spark v8.83
enable md5sum digest verification
Fix installing OTAs without decrypting
Fix ld.config.txt errors on Android 8.1 system root devices
language: italian: Fix SELinux support label
android: release 8.1.0_r40
Device specific changes here
Click to expand...
Click to collapse
Keep it real, keep it true, keep it blu :highfive:
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
blu_spark r34
All right crew!
New build is up :highfive:
Also checkout latest recommended blu_spark extras with blu_twrp v8.83
blu_spark_r34-redmagic_a137be0.zip
blu_spark_r34-redmagic-custom_56e7374.zip
drivers: misc: implement usb fast charge mode
wireguard updates (v0.0.20180809)
Anykernel2 updates
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 stock based ones).
Meaning, if using anything besides stock don't bother posting about it.
I am only interested on debugging stuff in stock international (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.
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
blu_spark extras v9.85
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.2.3+, name changing to reflect base 9.version, full compatible with upcoming Pie & current Oreo stuff.
Delete your twrp settings or else issues may arise if coming from other version besides blu_spark.
twrp-3.2.3-x_blu_spark_v9.85_redmagic.img
build: TWRP 3.2.3-x | blu_spark v9.85
Fix header file for property_get
Decrypt FBE on 9.0 (backwards compatible)
Merge AOSP android-9.0.0_r3
Device specific changes here
Click to expand...
Click to collapse
Keep it real, keep it true, keep it blu :highfive:
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
blu_spark r36
All right crew!
New build is up :highfive:
Also checkout latest recommended blu_spark extras with blu_twrp v9.85
blu_spark_r36-redmagic_c5448b3.zip
blu_spark_r36-redmagic-custom_cf0b45f.zip
build: use new and improved blu_gcc-8.2.0
makefile: supress some gcc-8 warnings
Makefile: Set KBUILD_OUTPUT to out by default
wireguard updates (v0.0.20180904)
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 stock based ones).
Meaning, if using anything besides stock don't bother posting about it.
I am only interested on debugging stuff in stock international (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.
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
eng.stk said:
All right crew!
New build is up :highfive:
Also checkout latest recommended blu_spark extras with blu_twrp v9.85
blu_spark_r36-redmagic_c5448b3.zip
blu_spark_r36-redmagic-custom_cf0b45f.zip
Keep it real, keep it true, keep it blu :highfive:
Click to expand...
Click to collapse
Thanks for your work. Can I use blu_spark_r36-redmagic_c5448b3.zip with stock rom NX609J-global-v109?
tlgod said:
Thanks for your work. Can I use blu_spark_r36-redmagic_c5448b3.zip with stock rom NX609J-global-v109?
Click to expand...
Click to collapse
Sure, should work fine
Sent from my blu_spark'd OP6
Hi eng.stk
Firstly thanks for your great work, i'm using ur TWRP Blue Spark since release., i'm sure its the best recovery for nubia.
I'm using ominirom, and loving it.
I just wanna know if i can install your kernel on omini rom.
Have someone tested?
unegro said:
Hi eng.stk
Firstly thanks for your great work, i'm using ur TWRP Blue Spark since release., i'm sure its the best recovery for nubia.
I'm using ominirom, and loving it.
I just wanna know if i can install your kernel on omini rom.
Have someone tested?
Click to expand...
Click to collapse
Yes tou can, custom build will work on omni 8.1
Sent from my blu_spark'd OP6
eng.stk said:
Yes tou can, custom build will work on omni 8.1
Sent from my blu_spark'd OP6
Click to expand...
Click to collapse
Flashed blu_spark_r36-redmagic-custom_cf0b45f.zip on ominirom....
Testing it now, thanks.
Hello @eng.stk
We have a common friend that shipped me his nubia. Martinusbe aka the Grumpy Clown it is lol.
I'd like to try to continue his work on red magic with GZR roms but i have a weird issue on it 1st of all...the damn bootloader keeps relocking itself on his own, even after flashing twrp and omni on it.
I know they shipped as tarball the kernel but well...i'll try as well.
Any way to contact you in pm on telegram hangouts or something please? ...to avoid an off topic here.
Thx.
Regards.
Sent from my Poco F1 using Tapatalk
Alx31 said:
Hello @eng.stk
We have a common friend that shipped me his nubia. Martinusbe aka the Grumpy Clown it is lol.
I'd like to try to continue his work on red magic with GZR roms but i have a weird issue on it 1st of all...the damn bootloader keeps relocking itself on his own, even after flashing twrp and omni on it.
I know they shipped as tarball the kernel but well...i'll try as well.
Any way to contact you in pm on telegram hangouts or something please? ...to avoid an off topic here.
Thx.
Regards.
Sent from my Poco F1 using Tapatalk
Click to expand...
Click to collapse
Hit me on tapatalk chat mate, no prob.
Sent from my blu_spark'd Oneplus 6
@eng.stk I know you stopped working on this device long ago since Max stopped making OMNi i guess! i have tried to take someone on-board for development. I was even ready for donating like 5 from my side. NUBIA ditched the international users on Oreo update. even the security patch is october 2018. They gave a update in china for pie. But there are deaf and silent on the pie international updates. The GSI are riddled with sounds issues are there no one who picks this device. Phh is busy man. Even with logs i tried to help him. But he can't. I hope this device is still lying somewhere with you. Can you share and point someone who can start development for this device like lineageOs or something like that. Because Alex's phone doesn't work somehow with anything he tried. So there are no updates from his side. Its not like i have tried to make ROM. I have burnt my laptop motherboard while trying to make ROM. Max said this device killed his two sim cards so he is not willing to work onto this device. I had asked a lot of people in my own country to work onto it. But no one came forward as i said when i tried with money also. Paypal don't work with my bank account. That's the irony and i don't know anyone who can do this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kernel features:
Powered by Ubuntu 18.04.3 x86_64 (sparky VPS @ www.servercore.com.br - thanks @ChristianLetti)
Build with custom toolchain blu_gcc-9.2.0 (cortex-a75.cortex-a55 targeted, build with latest Crosstool-NG from GCC-9.2.0 snapshot)
Full -O2 build with device and target flags enhanced, linaro build improvements, etc
Less is more: stockish OP6T builds based on OnePlusOSS/android_kernel_oneplus_sdm845
Systemless installer (doesn't touch system partition, OTA friendly), AnyKernel2 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_schedutil modded governor merged from latest Pixel 3 patchset)
No OC, use 300HZ kernel timer frequency
msm_performance touchboost toggle on/off (enabled by default), tweaked cpu_boost driver
Enhanced TCP methods (westwood is default), Network tweaks and updated drivers
Several I/O control tweaks, added schedulers FIOPS and ZEN v2 is default, advanced filesystems (F2FS, ExFAT, NTFS, CIFS & NFS)
Patched SafetyNet flags to pass CTS
Stock thermal driver by default
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
adrenoboost enable by default at medium
KCAL - Advanced color control for Qualcomm MDSS v2 (RGB calibration and post-processing features)
KLAPSE support (v5.0)
USB Fast Charge (USB mode up to 900mA with MTP on)
FS fsync toggle on/off
Wakelock blockers available
wireguard support
CDROM emulation on mass_storage (compatible with DriveDroid 0.10.36+)
Compatible with Kernel Adiutor, EXKM, FKM and others
DOWNLOAD KERNEL ZIPExtras download location(No mirrors please)
Warning: If you come from other kernel or have any issues, you should dirty flash your ROM before flashing blu_spark zip to avoid problems.
Reflash ROM -> if you want root flash SuperSU or Magisk (default, no plugins/modules) -> flash blu_spark.
If you are already rooted or upgrading between blu_spark versions, just flash the kernel zip. Also uninstall or clean data of any kernel control app you're using.
About bugs and troubleshoots: 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 with NO mods whatsoever (apart from root). That includes NO support if using xposed, Magisk with modules, etc.
If you're using custom ROMs (including OOS based ones) or Open Betas you're on your own. I'm only interested on debugging stuff in stock and stable OOS.
Save the SOT and battery stats/screenshots for general threads, here we deal with development, not personal tastes and results.
Also don't spam this thread with CM or other ROMs stuff like "this don't work, my app doesn't open, etc" , no OT about OTAs, apps, ROM bugs, Recovery/TWRP troubleshoots and other userspace stuff. There's threads for it, use them.
Going back to stock: This kernel installer doesn't change your filesystem. You can backup your boot.img with TWRP before flashing blu_spark if you want to go back to full stock or just dirty flash your full ROM.
If you like my work, donations are always welcome.
Don't forget to hit thanks and rate the thread nicely, it's free
OnePlus 6T development unit donated by OnePlus. Big shouts to them
Very proud of being on the OnePlus Developer Program, special thanks to Manu J. for being such a supportive person.
XDA:DevDB Information
blu_spark kernel for OnePlus 6T, Kernel for the OnePlus 6T
Contributors
eng.stk
Source Code: https://github.com/engstk/op6
Kernel Special Features: Powered by sparky
Version Information
Status: Stable
Current Stable Version: r103 unified
Stable Release Date: 2019-09-27
Current Beta Version: r108 unified
Beta Release Date: 2019-10-25
Created 2018-10-31
Last Updated 2019-10-25
blu_spark r51 unified
Your favorite kernel for Oneplus devices is here :victory:
I merged in OOS 9.0.4 source drop, so I decided to push OP6/6Tunified beta build (untested, don't have 6T device atm).
Just got on 6T
If you're brave enough, details and downloads here (backup your boot.img so you can go back to stock):
https://forum.xda-developers.com/showpost.php?p=78027996&postcount=963
eng.stk said:
Your favorite kernel for Oneplus devices is here :victory:
I merged in OOS 9.0.4 source drop, so I decided to push OP6/6Tunified beta build (untested, don't have 6T device atm)
If you're brave enough, details and downloads here (backup your boot.img so you can go back to stock):
https://forum.xda-developers.com/showpost.php?p=78027996&postcount=963
Click to expand...
Click to collapse
1st
Best op6 kernel is already available for 6t ?
There is not even a TWRP to flash the kernel and you already made the kernel. Nice work :good: :highfive:
@eng.stk: Thank you buddy for your continued support, we are proud to have you on the developer team
I am suppose to get a device within next 48 hours so i will flash and report.
Keep up the good work.
marf28101995 said:
1st
Best op6 kernel is already available for 6t
Click to expand...
Click to collapse
Bam! Always on the #fastlane
Kir3 said:
There is not even a TWRP to flash the kernel and you already made the kernel. Nice work :good: :highfive:
Click to expand...
Click to collapse
Indeed xD You can try to temp fastboot boot my blu_twrp, maybe it will work.
Funk Wizard said:
@eng.stk: Thank you buddy for your continued support, we are proud to have you on the developer team
I am suppose to get a device within next 48 hours so i will flash and report.
Keep up the good work.
Click to expand...
Click to collapse
Thanks for the kind words my friend. Wouldn't be as much without your support
Yeah test it out and let me know!
OMG its awesome to see u here this soon
That was fastttttt, custom kernel served even before we are seated at the custom recovery table.
My device should be delivered tomorrow.
Its going to be Blusparked ASAP. Switching from oneplus 5T to 6T
I have twrp on my OP6T, but decryption doesn't work so i cant restore my backup. ill try and flash when i fixed that.
How did you get twrp?
meljohnsony2k said:
How did you get twrp?
Click to expand...
Click to collapse
He used OP6 twrp see his tuto in Guide News Discussions section
mingo_mgx said:
I have twrp on my OP6T, but decryption doesn't work so i cant restore my backup. ill try and flash when i fixed that.
Click to expand...
Click to collapse
So to be clear, does the twrp work when no screen lock is set ? Cant test anything as the 6T is yet to be delivered
saiprasadgawde said:
So to be clear, does the twrp work when no screen lock is set ? Cant test anything as the 6T is yet to be delivered
Click to expand...
Click to collapse
TWRP works but decryption does not, regardless of whether screen lock is disabled or not.
I want to try this kernel but a bit too risky at the mo as we have no way to restore a backup and there are no factory images available as yet.
iaTa said:
TWRP works but decryption does not, regardless of whether screen lock is disabled or not.
I want to try this kernel but a bit too risky at the mo as we have no way to restore a backup and there are no factory images available as yet.
Click to expand...
Click to collapse
Oh i see. It is risky no doubt but I am sure it wont be long before working TWRP will be out. Fingers crossed
@eng.stk: Look what's Rocking my Fajita :laugh:
Kernel boots fine, everything works, nothing broken. Used Enchilada 9.86 TWRP, boots fine but has decryption issues so had to sideload the kernel. Thank you once again for your continued support and i look forward to a fully compatible TWRP :highfive:
Edit: Temporary Workaround till we get a fully compatible Blu TWRP :laugh:
Brave! Nice work from all around though
EDIT: Kernel working fine here too!
Funk Wizard said:
@eng.stk: Look what's Rocking my Fajita :laugh:
Kernel boots fine, everything works, nothing broken. Used Enchilada 9.86 TWRP, boots fine but has decryption issues so had to sideload the kernel. Thank you once again for your continued support and i look forward to a fully compatible TWRP :highfive:
Click to expand...
Click to collapse
Oh yeah, awesome stuff my friend, really happy it's all good :highfive:
Seems this phone doesn't have notification light. Does this solve in this kernel as mentioned.
Sent from my [device_name] using XDA-Developers Legacy app
aniesh1114 said:
Seems this phone doesn't have notification light. Does this solve in this kernel as mentioned.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
No it will not add a LED to your phone... it's just a placeholder from the OP6.
Finally rooted and Blusparked my 6T through adb sideload on temporary recovery :laugh:
Device definitely feels more fluid and responsive as expected. The customised vibration is a wonderful addition.
Thanks eng.stk, great work as always
saiprasadgawde said:
Finally rooted and Blusparked my 6T through adb sideload on temporary recovery :laugh:
Device definitely feels more fluid and responsive as expected. The customised vibration is a wonderful addition.
Thanks eng.stk, great work as always
Click to expand...
Click to collapse
Great, but you should hide your IMEI
How is this different to the 'Official' Build?
From October 17th onwards, the Official builds had merged N9 sources which has ridden users the chance of flashing custom kernels due to the new N9 dependency. These builds aim to backtrack that, reverting to S9(+)'s Oreo Vendor, to gain custom kernel support again. Also, the firmware source used in the 'Official' builds have become fairly antique, so it was time for a refresh and use the latest and final Oreo source (BSB1) Samsung had to give, and an upstreamed kernel of latest (almost always) ELS thanks to @Eamo5's Endurance Kernel being baked into the builds.
Aside from these factors and a few more listed below, this is the LineageOS you know and love. Although LineageOS' nightly-build system is great, there is only so much change that can happen over a night. You can expect these builds updating to cover latest Security Patch a.k.a Monthly Builds, but maybe more if a great change is required.
Simple motive: Have a solid daily driver before the Pie Tree sources are dropped.
Screenshots
If you are on the App they may instead be at the bottom of the post
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What's working:
As this build is based on the 'Official' LineageOS build, it complies with the device support requirements, which means including but not limited to these hardwares will work:
Wi-Fi
Bluetooth
Mobile Network (Calling, Data, etc.)
Audio
USB
GPS
NFC
Camera
Fingerprint Sensor - Noticeable speed improvement reverting to an S9(+) Vendor.
Software:
The build has overridden auto-generated fingerprint keys, with an official, whitelisted fingerprint from Samsung, which can also be found in MagiskHideProps. This ensures SafetyNet passes without the need for extra flashing - refer to above screenshot also.
F2FS Support - Instructions to switch from default ext4 to f2fs
Miscellaneous - Overlays:
- Dialer - Call recording enabled. If your country is not blacklisted (for legality reasons) you should see a 'Record' button during your call.
- Trebuchet - Notification Badges
- Files - File Operation Dialog Box, Default Show Internal Storage
- Settings - Default Enable Autobrightness for Night Time flashers; Default Disable Bluetooth and LED
- SystemUI - Button to Expand Notifications; Notifications fade on dismiss
- Snap: api v2 enabled for better quality pictures and remove green artefacts & flashing.
What's not working:
Samsung's own features such as Samsung Pay, KNOX, Theme Center, Game Launcher, etc. won't be ported to LineageOS. They may have their own implementation to similar functions, though.
Iris sensor does not work because AOSP upstream does not support that yet.
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port.
Encryption Support as of now, exploring for a workaround (if there is one).
Bugs:
Lock screen shortcut - Camera: Screen flashes white, and then Camera force closes using shortcut.
Work around: Install another app using Camera action (e.g. SnapChat) and set stock Camera to default for shortcut.
Instructions:
Make sure TWRP has been installed and is functional.
Download the latest build, Vendor and optionally GApps - Links found under the header below.
Reboot to Recovery
Wipe data and cache (required if you are not currently using LOS and are coming from OneUI or SamExp.)
Install Vendor image to Vendor partition.
Flash the latest build (and GApps if you downloaded it)
If you are on and beyond April Patch (OneUI), do not flash a found Oreo Firmware as you will lose Baseband (Sim, Network, RIL). There is also no need to change firmware.
Reboot to System.
If a new build is released, to update:
Downloading and flashing a later build, will automatically replace (wipe & install) the /system partiton and retain your compatible User /data partition and firewall due to LineageOS' addon.d supprort.
You also do not need to flash GApps again, as they too have addon.d support, backing up which GApps you have installed and holding them until after the /system partition wipe has been done.
Same applies to Magisk Root due to (you guessed it) addon.d support too. It holds your currently installed Modules until after the /system partition wipe has been done.
Therefore, due to these addon.d files surviving because of the way LineageOS.zip manipulates the wipe to the /system partition there is no need to wipe partitions manually. Just leave it to the lone flash.
However, do remove any system modified theme overlays (substratum) to ensure no loop on boot, which may then result needing to wipe.
Downloads:
Vendor: Included to the respective Device drives below
Samsung Galaxy S9 (G960F): https://drive.google.com/drive/folders/131WWohHbpeZroYaHISBPpPnhDKYA6kj2
Samsung Galaxy S9+ (G965F): https://drive.google.com/drive/folders/1cr-ivOdTj8lo3p9kYjGcxT1AvgFYy3M9
OpenGApps (Optional): https://opengapps.org/
Contact:
Telegram Group - Handle @invisibazinga2 a.k.a Lil' G-Raf
Contributors:
Big thanks to: @jesec ; @Synt4x.93 ; @Ivan_Meler ; @Eamo5 ; please check GitHub commit history for anybody that I may have missed out, you have all been great!
ROM Information
LineageOS Source: https://github.com/LineageOS
Android Security Patch: May
Android Version: 8.1.0
Kernel Version: ELS - 4.9.xx - Endurance Kernel - Version subjected to change with ELS updates.
Device Source: https://github.com/AzzyC
Thanks for the rom! What would be the best way of installing gcam here? I've tried installing the apk on the official build but the quality wasn't too nice. Tried to flash the libs as well and got a bootloop. Thanks for your work!!
enetzlsg said:
Thanks for the rom! What would be the best way of installing gcam here? I've tried installing the apk on the official build but the quality wasn't too nice. Tried to flash the libs as well and got a bootloop. Thanks for your work!!
Click to expand...
Click to collapse
Hey man! Yeh on the official build as the vendor was N9 based, our modded S9(+) libs wouldn't be compatible. Fortunately, just before writing this reply, I flashed the lib for my device (S9) and then installed GCam and it got going nicely! There is a 4.1_fix.apk (fixed for OneUI lib) and just a regular 4.1.apk (built on Oreo lib).
Let me know how it goes man! And appreciate your compliments ?
the screenshots look like pie roms... clock is on left side ..i thought finally a good lineage 16 build.. yet thanks for the 15.1 build though.. ??
i came from soldier rom pie and after installing the rom according to the instruction.
full wipe, vendor image than rom and gapps and lastly the firmware.
everything boots and works but the phone doesnt detect my sim card nor the latest wifi network i was connected too. it does sees my neighbors wifi, for some reason it doesnt detect mine. i tried to change the baseband for fixing the sim card problem but no luck.
please help me/ im on s9 g960f
kmo1997 said:
i came from soldier rom pie and after installing the rom according to the instruction.
full wipe, vendor image than rom and gapps and lastly the firmware.
everything boots and works but the phone doesnt detect my sim card nor the latest wifi network i was connected too. it does sees my neighbors wifi, for some reason it doesnt detect mine. i tried to change the baseband for fixing the sim card problem but no luck.
please help me/ im on s9 g960f
Click to expand...
Click to collapse
It seems as though you were on and beyond the OneUI April Patch, which in the description of the Firmware zip it clearly indicates a warning to not flash the zip. I can't say anymore than these warnings unfortunately, after that it is up to the User.
A common fix that people do, to get back to normal state, is flash the latest DevBase with all of its complementary files. The April Patch had introduced a version change from U2 to U3 which makes downgrading impossible, without side effects. Please heed to warnings more in the future. Thanks
AzzyC said:
It seems as though you were on and beyond the OneUI April Patch, which in the description of the Firmware zip it clearly indicates a warning to not flash the zip. I can't say anymore than these warnings unfortunately, after that it is up to the User.
A common fix that people do, to get back to normal state, is flash the latest DevBase with all of its complementary files. The April Patch had introduced a version change from U2 to U3 which makes downgrading impossible, without side effects. Please heed to warnings more in the future. Thanks
Click to expand...
Click to collapse
thank you and sorry. i installed back to soldier rom with his firmware and everything works fine. but i really want to try your rom, so what firmware should i install with it?
kmo1997 said:
thank you and sorry. i installed back to soldier rom with his firmware and everything works fine. but i really want to try your rom, so what firmware should i install with it?
Click to expand...
Click to collapse
Glad you're back to normal state!
Users has been able to boot and use the ROM just by installing the provided Vendor image and remaining on the same firmware. Let me know how it goes and if I can recommend other users to do the same, if they are in a similar situation. Thanks
AzzyC said:
Glad you're back to normal state!
If I remember correctly a User has been able to boot and use the ROM just by installing the provided Vendor image and remaining on the same firmware. Let me know how it goes and if I can recommend other users to do the same, if they are in a similar situation. Thanks and hope it works out!
Click to expand...
Click to collapse
yep, works like magic. thank you very much!
AzzyC said:
Hey man! Yeh on the official build as the vendor was N9 based our modded S9(+) libs wouldn't be compatible. Fortunately, just before writing this reply, I flashed the lib for my device (S9) and then installed GCam and it got going nicely! There is a 4.1_fix.apk (fixed for OneUI lib) and just a regular 4.1.apk (built on Oreo lib).
Let me know how it goes man! And appreciate your compliments ?
Click to expand...
Click to collapse
one ui lib didn't work out for me
I always noticed that oreo roms were laggy. I heard somewhere that it was a HWC bug, NOT that HWC was disabled. So... my question... does this unofficial version of lineageos lags like the other oreo roms?
Muntasir Mahmud Saif said:
one ui lib didn't work out for me
Click to expand...
Click to collapse
You tried a OneUI vendor lib, on an Oreo Vendor? Read the post again.
LavaSnake54 said:
I always noticed that oreo roms were laggy. I heard somewhere that it was a HWC bug, NOT that HWC was disabled. So... my question... does this unofficial version of lineageos lags like the other oreo roms?
Click to expand...
Click to collapse
Can assure there is no lag here, but you can find out by trying of course aha! The kernel definitely smoothens out the whole experience and with decent battery (see sceenshot for example result) and HWC is active.
AzzyC said:
Can assure there is no lag here, but you can find out by trying of course aha! The kernel definitely smoothens out the whole experience and with decent battery (see sceenshot for example result) and HWC is active.
Click to expand...
Click to collapse
Looks like a solid daily driver for me. Will definitely try it soon.
AzzyC said:
You tried a OneUI vendor lib, on an Oreo Vendor? Read the post again.
Can assure there is no lag here, but you can find out by trying of course aha! The kernel definitely smoothens out the whole experience and with decent battery (see sceenshot for example result) and HWC is active.
Click to expand...
Click to collapse
one ui lib bro..i am using that lib on my one ui currently for quite a few months..
Muntasir Mahmud Saif said:
one ui lib bro..i am using that lib on my one ui currently for quite a few months..
Click to expand...
Click to collapse
I don't see what is not to grasp here, you are flashing a Pie vendor lib on an Oreo Vendor. How would that work out? Didn't think I'd have to spell it out, but you've spammed this issue across 3 posts now:
Use the Oreo modded lib (not the Pie/OneUI lib), as this ROM is based on an Oreo Vendor, and the 4.1.apk (not the 4.1_fix.apk).
Hey guys!
I was doing a test run for a particular change and I thought I'd do a quick update for both devices. Starlte built just fine but I ran out of disk space when finishing star2lte so the compile failed (at 91% ?)
Not to fret, the May Security Patch has not yet been merged into LineageOS so this would have been just another build on April Patch. However, the included kernel has updated to latest of Endurance, though you can just flash Eamon's latest kernel zip to update and have the same effect.
Both devices will of course get an update when May Patch is out. Gracias bien
For starlte:
https://drive.google.com/drive/mobile/folders/131WWohHbpeZroYaHISBPpPnhDKYA6kj2
Gcam link please?
AzzyC said:
I don't see what is not to grasp here, you are flashing a Pie vendor lib on an Oreo Vendor. How would that work out? Didn't think I'd have to spell it out, but you've spammed this issue across 3 posts now:
Use the Oreo modded lib (not the Pie/OneUI lib), as this ROM is based on an Oreo Vendor, and the 4.1.apk (not the 4.1_fix.apk).
Click to expand...
Click to collapse
sorry if i did wrong or hurt your feelings but can you please provide those two files?
LavaSnake54 said:
Gcam link?
Click to expand...
Click to collapse
Muntasir Mahmud Saif said:
can you please provide those two files?
Click to expand...
Click to collapse
https://f.celsoazevedo.com/file/gcamera/GCam_5.1.018.177470874.41362666_IDan_N6_4.1.apk
AzzyC said:
https://f.celsoazevedo.com/file/gcamera/GCam_5.1.018.177470874.41362666_IDan_N6_4.1.apk
Click to expand...
Click to collapse
you are dope bro .thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kernel features:
Build with custom upstream LLVM 14.x (Clang 14.0.6 + LLD linker + IAS)
Full -O2 build with device and target flags enhanced, build improvements and compiler fixes, etc
Less is more: stockish OP8 builds based on OnePlusOSS/android_kernel_oneplus_sm8250 for max stability
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 for important subsystems
Modded schedutil governor merged from latest CAF sm8250 patchset
No OC, use 250HZ base timer frequency
msm_performance touchboost toggle on/off (enabled by default), tweaked cpu_boost driver
Enhanced TCP methods (westwood is default, BBR available), Network tweaks and updated drivers
Several I/O control tweaks, added schedulers ZEN v2 is default, advanced filesystems enabled (F2FS, ExFAT, NTFS, CIFS & NFS)
ZRAM Swap (LZ4 default) and with file disabled, LZO-RLE and ZSTD are available
Vibrator Strength tunable and Gesture Haptic Feedback control (touchpanel and FPR)
KGSL fixes and general improvements for GPU driver
adrenoboost ready (disabled by default)
Backlight min brightness and backlight scale option
Gamepad support enabled (xbox, ps4, switch)
USB Fast Charge (USB mode up to 900mA with MTP on)
FS fsync toggle on/off
Wakelock blockers available
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
(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.
Source Code: https://github.com/engstk/op8
Don't forget to hit thanks, it's free
OnePlus 8 Pro development unit donated by OnePlus. Big shouts to them
Very proud of being on the OnePlus Developer Program, special thanks to dev relations team.
blu_spark r12 release
All right crew!
It's that time again, 1st build is up :highfive:
This kernel source is unified for OP8/Pro, don't know how it will run in the regular model (can only test in the Pro). Let me know.
At the moment we're maybe at 80% of the usual goodies, get a nice and stable base and go from there.
I'm building with clang currently got some hiccups with gcc. I'll probably revisit this in the future but it will need more TLC.
You can now use FKM download kernel feature, just import the links bellow in the app :highfive:
blu_spark_r12release
FKM download configs: oos | custom
Build with latest Google Clang version 11.0.2 (Android 11) - blu_gcc may come in the future, needs som TLC
Synchronize codes for OnePlus 8 Oxygen OS 10.5.9.IN21AA and OnePlus 8 Pro Oxygen OS 10.5.10.IN11AA
Build errors and warnings fixes
Compiling improving and target optimizations
Goodies: IO and filesystem stuff, priorities and UX, touchboost, zram, wakelock blocker, haptic and gestures level, adrenoboost, etc
wireguard updates (v1.0.20200611)
init adjust for sdm8250
AnyKernel3 latest updates
For root, stable Magisk 20.4 or newer is mandatory
Click to expand...
Click to collapse
Keep in mind: I will give no active support for custom ROMs (including OOS based ones).
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.
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
ur kernel is great for daily use when I have 6t, it's fast, smoot, and stable. do u plan to build one for oneplus 8?
Great to see your blu-spark here! Kudos
Great job! Any list of the best settings to activate for your kernel in FKM? Can't manage to activate westwood TCP method, it gets stuck to reno, for example. Or any config file to have the best settings selected, maybe? Sorry, I'm not too familiar with FKM yet.
Hey there, welcome. Nice to see you here.
Just one question, why are so many features listed in the OP and many or most not in the sources on GitHub? Isn't this a copy paste error?
Sent from my Pixel 4 XL using Tapatalk
orochi9999 said:
ur kernel is great for daily use when I have 6t, it's fast, smoot, and stable. do u plan to build one for oneplus 8?
Click to expand...
Click to collapse
Has it is doesn't work? idk.
At the moment I'm focused on the bringup.
Surfeur-des-Reves said:
Great job! Any list of the best settings to activate for your kernel in FKM? Can't manage to activate westwood TCP method, it gets stuck to reno, for example. Or any config file to have the best settings selected, maybe? Sorry, I'm not too familiar with FKM yet.
Click to expand...
Click to collapse
I already inject settings I see importanton the background. TCP method is westwood by default, that reno situation is a bug from the app, franco is on it :good:
tbalden said:
Hey there, welcome. Nice to see you here.
Just one question, why are so many features listed in the OP and many or most not in the sources on GitHub? Isn't this a copy paste error?
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
Hey. WIP and will come soon after.
eng.stk said:
Hey. WIP and will come soon after.
Click to expand...
Click to collapse
great to see ya here mate... i just got my pro... will teat ince i feel like rooting lol
eng.stk said:
Has it is doesn't work? idk.
At the moment I'm focused on the bringup.
I already inject settings I see importanton the background. TCP method is westwood by default, that reno situation is a bug from the app, franco is on it :good:
Hey. WIP and will come soon after.
Click to expand...
Click to collapse
it's not working on regular 8
After installing this kernel I'm getting an option to boost GPU clock to 900 MHz. This also resulted in a much higher compute score. Is this normal? @eng.stk
On8 not working
Cool to see another old kernel dev from the nexus 5 days xD
orochi9999 said:
it's not working on regular 8
Click to expand...
Click to collapse
Smturbo said:
On8 not working
Click to expand...
Click to collapse
Hum too bad. Seems like there's driver differences between the models, we'll see what can be done ib the future.
For now I'll concentrate on the pro.
akshat207 said:
After installing this kernel I'm getting an option to boost GPU clock to 900 MHz. This also resulted in a much higher compute score. Is this normal? @eng.stk
Click to expand...
Click to collapse
Wait, what? Seem like that app is on acid lol
Sent from my blu_spark'd OnePlus
kevp75 said:
great to see ya here mate... i just got my pro... will teat ince i feel like rooting lol
Click to expand...
Click to collapse
hjjiang said:
Cool to see another old kernel dev from the nexus 5 days xD
Click to expand...
Click to collapse
Welcome guys, nice device choices [emoji16]
Sent from my blu_spark'd OnePlus
eng.stk said:
Wait, what? Seem like that app is on acid lol
Sent from my blu_spark'd OnePlus
Click to expand...
Click to collapse
Then how did I get 4351 OpenCL score on Geekbench lol?
akshat207 said:
Then how did I get 4351 OpenCL score on Geekbench lol?
Click to expand...
Click to collapse
You probably still have custom dtb from the kernel that have gpu oc, since this kernel doesn't replace the dtb and you switched kernels without keeping that in mind you ended up with mixed kernel images and dtbs.
acuicultor said:
You probably still have custom dtb from the kernel that have gpu oc since this kernel doesn't replace the dtb and you switched kernels without keeping that in mind you ended up with mixed kernel images and dtbs.
Click to expand...
Click to collapse
So, how is that much GPU OC possible? that's almost double the stock max frequency!
EDIT: You were right, it was from "Evira Kernel". Now my question is, is that much OC safe? That's insane.
Do note that my device didn't get hot when I was running the benchmark even at 900 MHz.
Smturbo said:
On8 not working
Click to expand...
Click to collapse
what was the problem for the regular OnePlus 8? bootloop and what region was ur phone
hjjiang said:
what was the problem for the regular OnePlus 8? bootloop and what region was ur phone
Click to expand...
Click to collapse
At the bootloader unlock screen, after a few seconds, the text turns green and has black lines through it, when it finishes booting, by the screen goes completely black. Vibration and sound still work though. Have to force power off and back to TWRP to restore stock boot.
blu_spark r18 release
All right crew!
New build is up :highfive:
This kernel is only tested for the Pro variant which I have, regular OP8 support may come in the future.
You can now use FKM download kernel feature, just import the links bellow in the app :highfive:
blu_spark_r18 release
FKM download configs: oos | custom wip
Full LLVM tools build (Clang + LLD), add a couple build fixes/improvements
drivers: misc: power: implement usb2 fast charge mode
power: smb5-lib: reset level on removal
drm-msm-dsi: add backlight min option
fs: exfat: version 2.2.0-3arter97
cpufreq: schedutil: make iowait boost optional
remove and disable some debug and logging
defconfig: enable overlay and disable dtb append
init adjustments
For root, stable Magisk 20.4 or newer is mandatory
Click to expand...
Click to collapse
Keep in mind: I will give no active support for custom ROMs (including OOS based ones).
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.
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