• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Development [KERNEL] [OOS] Omega Kernel OOS11 [September 18, 2021]

Search This thread

avid_droid

Senior Member
Aug 24, 2019
2,154
726
OnePlus 9
OK. So this will be difficult... :)
1. Fix camera issues
2. Still keep the device cool

That being said - since I didn't have any camera issues, I'll need everyone's help here.

Attached is a test build.
- Please check for potential camera issues (especially those who experienced it before)
- Please check for device tempretaures

Thank you all for the help!
I will test and see if temperature changes. I have no camera issues thus far. Downloading and will report back soon. Thank you
 
  • Like
Reactions: PKkeys

avid_droid

Senior Member
Aug 24, 2019
2,154
726
OnePlus 9
So silly me. Don't think the kernel was producing heat. I think my problem was, was having QHD+ on without auto-saver mode which would generally heat up the screen more as it uses more power. Running at FHD and heat isn't prominent anymore.
 
  • Like
Reactions: fromiOS2Android

avid_droid

Senior Member
Aug 24, 2019
2,154
726
OnePlus 9
1.Camera fully functional,as I've never had issues.
2. Heat is subjective when having either FHD or QHD on. FHD draws less power than QHD which cause less heat and power consumption from battery. QHD produces more heat as it draws more power from battery resulting in more heat.

My mistake earlier when leaving QHD on and having heat issues. Placed back to FHD and no more heat.
 

kristofpetho

Senior Member
May 27, 2009
5,190
10,010
Zoetermeer
Everyone, once and for all:

I will not implement wakelock blockers into the kernel. Wakelocks are there for a reason. If you do have wakelocks keeping your phone awake, then figure out what that wakelock is and why it's there, and fix it. 99.99% of the time it's one (or more) of your apps acting up. Either don't use that app (because it's coded badly), or update it to a latest version.
Same thing goes for apps like Naptime, Universal Doze, etc. Don't use these. They do much more harm than good. Android, since version 9, is very intelligent about doze, wakeups, etc. If you put your phone down at night, and you have no crazy apps on your phone, awake-screen-off should not make up more than 4-5% of the total phone time. If it's higher than 10% you need to do some digging and find out which app is misbehaving.
 

avid_droid

Senior Member
Aug 24, 2019
2,154
726
OnePlus 9
Everyone, once and for all:

I will not implement wakelock blockers into the kernel. Wakelocks are there for a reason. If you do have wakelocks keeping your phone awake, then figure out what that wakelock is and why it's there, and fix it. 99.99% of the time it's one (or more) of your apps acting up. Either don't use that app (because it's coded badly), or update it to a latest version.
Same thing goes for apps like Naptime, Universal Doze, etc. Don't use these. They do much more harm than good. Android, since version 9, is very intelligent about doze, wakeups, etc. If you put your phone down at night, and you have no crazy apps on your phone, awake-screen-off should not make up more than 4-5% of the total phone time. If it's higher than 10% you need to do some digging and find out which app is misbehaving.
Agree 100%. Stopped using gmsdoze after about the first hour I had it installed. Thanks for your work
 
  • Like
Reactions: kristofpetho

reffu

Senior Member
Feb 11, 2008
102
36
OnePlus 9
Out of curiousity, what makes it not work on the standard OP9? I see one commit (titled: "hardcode for 9 Pro hardware") that seems specific to the Pro, but most of the others (that I can decipher) seem like they'd work on either device.
 

Flying Fox

Senior Member
Dec 21, 2010
596
779
Vienna
OnePlus 9 Pro
To further get to bottom of the issues:

To anybody who had the camera issues: can you please list here ALL of the Magisk modules you are using?

Thank you
Just for information, here NO issues, everything fine.
My Magisk modules:
Ainur Narsil, Audio Modification Library, Viper4AndroidFX, CyperPunk OnePlus Bootanimation and Systemless Hosts...
At least these modules don´t seem to cause camera issues. (btw, didn´t update to the test versions).
 
  • Like
Reactions: kristofpetho

Ben19799

New member
Nov 11, 2018
2
2
To further get to bottom of the issues:

To anybody who had the camera issues: can you please list here ALL of the Magisk modules you are using?

Thank you
I had issue with camera app freezing with black screen in photo mode. (video mode was ok). Updating to the 0517 build resolved the issue.
Magisk module: Debloater, Font Manager, Oneplus Dialer Contact & Messages, Riru, Riru - Clipboard Whitelist, Riru - EdXposed, Systemless Hosts.
EdXposed: AFWall+, Gravity Box (R), WA Tweaker
 
  • Like
Reactions: kristofpetho

Levi4cyber

Senior Member
Apr 26, 2018
132
33
OnePlus 9 Pro
Sorry for asking a newb question.

How do I Flash this kernel from my phone?

I have downloaded Smart Pack kernel manager but I get this error when flashing.
Screenshot_20210519-143853.jpg



Thanks.
 
Last edited:

terlynn4

Senior Member
Aug 18, 2012
277
135
Fort Worth, TX
Nexus 9
OnePlus 9 Pro
I have installed BusyBox still get this error.

What do you mean require a specific version?

The app may be designed to work with a particular release version of busybox. Looks like that dev has his own busybox installer in the play store (here), so you might try that. Otherwise, I don't know. I use exkm and I've never had any issues.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 12
    I think that sentiment is a bit extreme, man. I also used to test Omega, and never took it to heart when things, as they do eventually, slowed down and eventually stopped for the 6t.

    KTP is stability focused and doesn't tend to push release after release just for the sake of doing it. Omega is always a good stable kernel for that exact reason.

    A guy that has a full time day job, who happens to understand more than most peeps about kernels, makes his own, then shares it with the community, gratis with no expectations is not on the hook to dash titty sprinkles on the kernel and re-release it constantly. If he was asking for $$ (which he does not) or something in return (which he does not) it would be different.

    Of course, you can choose to not use Omega as well, if you feel there's something better or are super committed to the Cartman mantra of [screw you guys, I'm going home], that, much like installing Omega in the first place, is your choice.

    Let's not act like the dev owes anyone anything, bc he doesn't owe us anything whatsoever. We are the privileged in the equation.
    There has been no source update for the device since 11.2.8.8...
    I'm waiting for updated sources, and dont want to break anything in the meantime.
    10
    I think that sentiment is a bit extreme, man. I also used to test Omega, and never took it to heart when things, as they do eventually, slowed down and eventually stopped for the 6t.

    KTP is stability focused and doesn't tend to push release after release just for the sake of doing it. Omega is always a good stable kernel for that exact reason.

    A guy that has a full time day job, who happens to understand more than most peeps about kernels, makes his own, then shares it with the community, gratis with no expectations is not on the hook to dash titty sprinkles on the kernel and re-release it constantly. If he was asking for $$ (which he does not) or something in return (which he does not) it would be different.

    Of course, you can choose to not use Omega as well, if you feel there's something better or are super committed to the Cartman mantra of [screw you guys, I'm going home], that, much like installing Omega in the first place, is your choice.

    Let's not act like the dev owes anyone anything, bc he doesn't owe us anything whatsoever. We are the privileged in the equation.
    4
    I just recently flashed this kernel again because I was running stock kernel but omega is really cpu hungry in your last update it said less cpu hungry while overnight it eats like 20% away when the screen is on you can spend like 5 to 6 hours on the screen but not even last a day on lock screen where you can spend like 2 or 3 tops then your phone dies

    Stock kernel seems not to be cpu hungry
    lol this kernel is anything but cpu hungry. once again need to point out that idle/active drain is directly related to what apps you use and how you use your phone, not the kernel, especially this one that is the polar opposite of cpu hungry
    3
    Sorry about my comment @kristofpetho . Your work is still amazing. I apologize to everyone here on the forum for my stupid comments. No more from me. Sorry and thank you
    3
    at first when I read your post I was thinking no way it's been abandoned, but then I looked at github and there has been no new commits since 9/17 (the last update he released) so I'm not sure now. perhaps he's just busy with other things? either way I hope it's not.

    Willing to bet if @kristofpetho was stopping, he would have said so. Sometimes, there isn't anything to update.
    I imagine until source is out for a12, there probably won't be any big changes needed. Only my guess, though. ;). Thank you for what you do @kristofpetho !!
  • 54
    Introduction

    Hello everyone, this is my personal kernel for the OnePlus 9 Pro.
    My philosophy on the kernel is pretty simple, intended to replace the stock kernel, but with a lot of under-the-hood tweaks.

    Hopefully you will all enjoy!

    Important thread information!

    I refuse to acknowledge/respond to bug reports that do not include clear steps to reproduce, a logcat, and a console ramoops (if random rebooting) or a dmesg (any other issues). Follow this guide to do this.
    Keep things civil, no flaming in the forums!

    Features

    • Up to date with OxygenOS 11 source
    • Compiled with Google's Clang toolchain for maximum stability, with all warnings and errors fixed
    • Compiled with Clang's cortex-a55 optimizations
    • Many tweaks under the hood for smoother UX, lower battery drain, etc.
    • Westwood as the default congestion algorithm (BBR is also available)
    • Available to flash with AnyKernel3

    Latest kernel release on GitHub

    LINK

    Source

    Omega GitHub: https://github.com/kristofpetho/kernel_oneplus_sm8350
    Omega originally sourced from: OnePlusOSS

    Thanks where it's due

    @pyry666 for all his help getting me logs after logs after logs. Without him this wouldn't have been possible!
    @Burt Squirtz and @crashazz3 and @TheKnux for helping to test
    Kerneltoast for his extreme patience and guidance
    osm0sis (for AnyKernel3)
    @eng.stk for finding a way to have proper hardware detection working
    28
    New kernel release!

    Changelog:
    - Pulled in patch from Google to make cpufreq stat collection less CPU-hungry (smoothness)
    - Pulled in 3 Clang/LLVM stability fixes from upstream Linux
    - Pulled in a patch for better power consumption when vibrations are enabled (from arter's source)

    While this kernel works on latest 11.2.9.9, please note that OnePlus hasn't released sources yet for 11.2.9.9.

    Enjoy!
    25
    New release!

    Changelog:
    - Build with Google's Clang 13.0.1, updated Binutils to 2.37
    - Pulled in 5 code fixes from CAF for display driver
    - Pulled in 2 logic fixes from CAF for display driver
    - Pulled in 3 various CAF stability fixes
    - Fixed a dmesg error message with a commit from upstream Linux
    - Removed all android_fs tracing from the ext4 and f2fs filesystem drivers
    24
    New kernel release!

    This is a huge one in terms of stability and smoothness.

    Changelog:
    - GCC LTO implemented
    - GCC O3 optimization (together with LTO results in significant improvement of hackbench scores)
    - Wireguard added
    - Anykernel 3 updated
    - Critical and stability fixes from CAF
    - More code fixes based on GCC's diagnostics
    - Significant improvement to ZRAM speed

    Enjoy!
    24
    New kernel release!

    The test team has been crazy busy, flashing sometimes 5 builds a day to pressure test, and come up with this new kernel.
    After tons of performance tests, we found that Clang (with the included optimizations) outperforms even the best GCC builds, so I'm now moving to using Clang by Google to compile the kernel.

    Changelog:
    - Fixed major network error where userspace was trying to modify network settings but the kernel wasn't allowing it (this issue is also present on stock kernel)
    - Pulled in a fix from CAF to improve/lower battery drain
    - Updated Wireguard module to latest version
    - Built using Google's latest Clang (12.0.6)
    - Enabled all Clang internal optimizations (reverted a crazy CAF patch disabling them), and fixed all subsequent code errors
    - Fixed an IRQ saving issue found via lockdep (upstream)

    Enjoy!