OmniRom without Kernel - Omni Q&A

Hi,
Could you generalize a download from OmniRom without kernel ?
A lot of OmniRom users a poweruser and used another kernel

bbk said:
Hi,
Could you generalize a download from OmniRom without kernel ?
A lot of OmniRom users a poweruser and used another kernel
Click to expand...
Click to collapse
No. The included kernel is the only supported configuration, and it will always be this way.
Why? Anything else results in a testing nightmare. It's bad enough when we change out blobs that require a matching kernel change and a maintainer's thread gets flooded with "it's not working with X kernel any more".
Anyone can submit changes to Omni's kernels for review in gerrit, so that leads to the question:
1) Why is the maintainer of an alternate kernel not upstreaming to gerrit? What are they hiding?
2) If a change was submitted to gerrit, why was it rejected? In many cases, some of the "features" of alternate kernels are highly dangerous (such as disabling per-file fsync and allowing devices to pull more than 500 mA from a standard USB host port)

Related

[Q] Modifying Kernel

Hi,
I am trying to modify a kernel for Samsung Galaxy 3. I have successfully compiled stock kernel from Samsung Sources.
I am new to kernel development and want to add new features to it like overclocking etc.
Can any one please suggest me links or give info regarding how to go about it.
For example, how to modify the frequencies supported by kernel or bus speed in the source code?
Thanks,
Abhijeet
Check github for modifications to the base. I don't know about Samsung kernels, but a quick search of github shows plenty, like this:
https://github.com/kangsterizer/android_kernel_samsung
click on the comments to see only files affected by OC/UV mods like this from the above example:
https://github.com/kangsterizer/and...mmit/1817cd02de8165a4f96746d4dddec3ef4347cb2d
See if you can move those changes into your own kernel.

[Q] [Nexus 7 2012 Wifi only] Kernel with nfs support for CarbonROM 4.4.2

Hello there,
I'm looking for a way to mount nfs shares of my NAS and (debian wheezy) server in the filesystem for access of my media files.
I thought for long that it would be the most natural thing to do for my (linux based) mobile devices in a linux server environment, but it seems I'm far off.
So far I have been unable to mount these nfs shares of mine to the Nexus 7 (grouper) device running a Carbon ROM 4.4.2 Nightly Build from march this year (CARBON...20140302-0433.zip) with CifsManager, most likely due to its lack of kernel support (version 3.1.10--g90cc2cb1 bigshotrob...).
May one of you recommend a kernel that supports nfs, cifs and utf-8 for this build? I restrain from updating it as it is running smoothly and without problems (Remember? Never change a...) and I don't like to invest much time for the reconfiguration and other related stuff.
I know there is M-Kernel (http://forum.xda-developers.com/showthread.php?t=2168787) out there that claims to have exactly the requested support and compliance to the CarbonROM series. But I'm unable to sort out what version of the kernel would match my build of the ROM.
I understand that the most actual release is for versions 4.4.4, but the changelog and >200 posts I've browsed do give no hint which release was compiled for 4.4.2 ROMs.
Please note, I would ask directly in that respective thread in the development section if I could, but owing to the (imho pretty stupid) 10 post restriction of newcomers I am unable to post there.
Edit: Not necessary anymore, got my postings ...
Accordingly, my second question would be, if someone with more than 10 posts would be so kind and ask the following questions for me in the given thread?
Namely:
What version of the kernel would fit my 4.4.2 CarbonROM Build and where could I obtain it?
Does anyone had success to mount nfs shares with it (or cifs, if not) ?
Edit end
That and any alternative ways/hints to get nfs going would be highly appreciated!
Thank you very much,
Nix
Specs Summary:
Nexus 7 2012 Wifi only
Carbon ROM 4.4.2 Nightly Build (CARBON...20140302-0433.zip)
Kernel 3.1.10--g90cc2cb1 bigshotrob...
Simple. Give my kernel a shot. It uses an AnyKernel installer, which then works with both ext4/f2fs ROMs. If you don't want experimental dt2w/s2w, flash 1.6.1.
Edit
http://vp-zp.com/snuzzo/kernels/grouper/
Forgot my link lol
Snuzzo said:
Simple. Give my kernel a shot. It uses an AnyKernel installer, which then works with both ext4/f2fs ROMs. If you don't want experimental dt2w/s2w, flash 1.6.1.
Click to expand...
Click to collapse
Thank you for the reply snuzzo,
would you mind to give some details where to learn more of its features and where to find it?
Then I'll have a look at it.
EDIT:
Thanks for the link! But exactly what version do I have download for my Carbon ROM build above, if I'd decide to use it that is?
Presumably .../kitkat/Funky...??
BTW, are there some feature lists or such things? I'll probably browse the forum a bit, I suppose?
Cheers, Nix
Anykernel Installer. You can flash it on either an ext4/f2fs rom for /data compatibility
Overclock with 1.3Ghz max default
Under/overvolt
IO Scheduler additions: SIO BFQ ROW
CPU Governor additions: Lazy Lagfree Scary Lulzactive Wheatley (could be few more but thats from memory)
DoubleTap2Wake/Sweep2Wake in 1.6.2, disabled in 1.6.1(experimental)
Kexec Hardboot for MultiRom
Dynamic Fsync Control
Stock Google 4.7GCC prebuilt toolchain.
CIFS.
Theres a few other tweaks I made for overall UI performance other than that it follows CM-11.0 source. I build these for my own personal use but upload to share them for those who want what I run. You will want 1.6.2 or 1.6.1.
Snuzzo said:
Anykernel Installer. You can flash it on either an ext4/f2fs rom for /data compatibility
Overclock with 1.3Ghz max default
Under/overvolt
IO Scheduler additions: SIO BFQ ROW
CPU Governor additions: Lazy Lagfree Scary Lulzactive Wheatley (could be few more but thats from memory)
DoubleTap2Wake/Sweep2Wake in 1.6.2, disabled in 1.6.1(experimental)
Kexec Hardboot for MultiRom
Dynamic Fsync Control
Stock Google 4.7GCC prebuilt toolchain.
CIFS.
Theres a few other tweaks I made for overall UI performance other than that it follows CM-11.0 source. I build these for my own personal use but upload to share them for those who want what I run.
Click to expand...
Click to collapse
Sounds great, although most of it are books with seven seals for me
What about nfs support? And its definitely for 4.4.2 based ROMs?
Thx again,
Nix
Yes to both. It has NFS and CIFS support.
And v.1.6 is the one you'd suggest?
Nixblicker said:
And v.1.6 is the one you'd suggest?
Click to expand...
Click to collapse
Yes.
Snuzzo said:
Yes.
Click to expand...
Click to collapse
One more question, please - do I have to activate or load those modules manually or will they be loaded at bootup by default?
Where may I find them to insmod/modprobe them manually, if not?
Thanks for the help once more,
Cheerio,
Nix
They will load by default.

[Dev Info] [Deathly Kernel] [AOSP] [Lollipop 5.1.1]

This thread will be about changes i have made to the device trees for the t700,t705,t800,t805 which should in the long run make maintaining the variants a lot easier the primary changes i have done are combine all 4 of the variants into 1 kernel source as well as make a common device tree so they can inherit everything that is the same across devices.
Kernel Changes:
The Base kernel from Cyanogenmod supports klimtwifi (T700) and klimtlte (T705) to add support for chagallwifi (T800) all that is needed is to add its defconfig which is this file
https://github.com/LiquidSmooth-Dev...arch/arm/configs/deathly_chagalllte_defconfig
To add support for the Chagallte (T805) it was a little more complicated for to do but very simple for you guys for a little background T805 is exactly the same chipset as the other Galaxy Tab S's except for whatever reason Samsung decided to put a different gpu (Midgard_wk04) everyone else uses a mali_t6xx.
The stuff developers actually need to support Chagalllte are the following:
Defconfig:
https://github.com/LiquidSmooth-Dev...arch/arm/configs/deathly_chagalllte_defconfig
The GPU addition commit:
https://github.com/LiquidSmooth-Dev...mmit/c8e96e86c902cbc2b13d34e7e7158623eacf5d84
Bam that was easy now any kernel can support all 4 main variants of the Tab S
Device tree and vendor repos
First part i want to place links to all of the stuff that's needed to make a rom for each device in one place.
(Disclaimer the trees will be LiquidSmooth but it is very easy to convert them to any rom)
Klimtwifi (T700):
https://github.com/LiquidSmooth-Devices/android_device_samsung_klimtwifi
https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-12.1/klimtwifi
Klimtlte (T705)
https://github.com/LiquidSmooth-Devices/android_device_samsung_klimtlte
https://github.com/schwabe93/vendor_samsung_klimtlte
Chagallwifi (T800)
https://github.com/LiquidSmooth-Devices/android_device_samsung_chagallwifi
https://github.com/diego-cr/android_vendor_samsung_chagallwifi
Chagalllte (T805)
https://github.com/LiquidSmooth-Devices/android_device_samsung_chagalllte
https://github.com/Andrewt12/android_vendor_samsung_chagalllte
WIP Common Device Tree:
When bringing up support for LiquidSmooth for these devices i noticed that they are all pretty much copied each other (which makes sense) but because of it there was tons of duplicated code between the devices so i decided to make a common device tree so any future code changes could be placed in one place instead of over 4 device trees. This is still a WIP because i do not have all the devices so i can not test them all in my eyes they should all work fine. The common device tree will also hopefully will be rom independent so no changes would be needed on a per rom basis. I can for sure say klimtwifi and chagallwifi work with my common tree, Chagalllte and klimtlte need to be tested still.
Common Device tree repo:
https://github.com/LiquidSmooth-Devices/android_device_samsung_exynos5420-common
Common device tree migration commits
Klimtwifi:
https://github.com/LiquidSmooth-Dev...mmit/444b4fc08f82eeeabe8e0a533539fe0c2fadd723
https://github.com/LiquidSmooth-Dev...mmit/cdf5f06c8a29bb237b964d5ee602d151c6323677
Klimtlte:
https://github.com/LiquidSmooth-Dev...mmit/8570d466e2b5b88c316c7f1576bf8ea9051c5e2a
Chagallwifi:
https://github.com/LiquidSmooth-Dev...mmit/5be51eb30283355109c65513ea209dd1d6855ff2
Chagalllte:
https://github.com/LiquidSmooth-Dev...mmit/5ff21d73a9cad3f7f9cf7f79b29bdbab0d8b2b1e
One more improvement that myself and @diegocr made was finally made a pernament fix to Chagallwifi's (T800) wifi issue he made a custom release tool in the device tree to make it so you would not have to manually patch it every time. I then took that and fixed the root of the issue which was that the vendor repo was not putting the files in the right spot. (My orig commit also did egl but that was not needed) the commit that did it is this:
https://github.com/diego-cr/android...mmit/1fc5135eda985ddc159f8465ee114e67aa5dfcae
Now into the features of my Deathly kernel
XDA:DevDB Information
[Dev Info] [Deathly Kernel] [AOSP] [Lollipop 5.1.1], Kernel for the Samsung Galaxy Tab S
Contributors
deadman96385
Kernel Special Features:
Version Information
Status: Testing
Created 2015-06-22
Last Updated 2015-06-21
Deathly Kernel
I have had a deathly kernel on most devices i own the goal of it is to get as many options and features into a kernel but still be stable. For the Tab S i took the aosp cm base and have updated it against kernel.org from 3.4.105 too 3.4.108 along with pull in a bunch of features from other exynos 5420 devices
As you read above i have made a common tree which changes the ramdisk so i have to provide two zips one with the new format one with old format currently the only rom that i personally have built with the new version is the latest klimtwifi and chagawifi all other roms will boot loop with it so use the old version
Currently i only have flashable for Klimtwifi (T700) i will generate the others once i get back from my trip.
New Ramdisk option:
http://www.drdevs.com/devs/teamliquid/Kernels/klimtwifi/New_format/
Old Ramdisk option:
http://www.drdevs.com/devs/teamliquid/Kernels/klimtwifi/Old_format/
Features of the Deathly kernel:
Will support all 4 main tab s devices (will add support for the US carrier variants if aosp is brought up)
CPU Voltage Control
CPU OverClock/UnderClock
GPU Voltage Control
GPU OverClock/UnderClock
MIF/INT Voltage Control (I will not show how to configure this if you know how too then you can)
Wolfson Sound Control Thanks to oloendithas for fixing it for stereo out
UKSM instead of KSM
Added the following IO Schedulers: fifo, fiops, sioplus, tripndroid, vr, zen, bfq (Default)
Full f2fs support updated off the mainline (Stock cm kernel has limited support)
Modified Thermal Throttling temperatures for all devices so hopefully they won't get as hot (WIP)
Android Logger disabled by default can be enabled over sysfs
Exynos thermal exposed to sysfs
WQ power efficient workqueues (Still need to apply in more places)
Frandom Support
Readahead bumped to 256 from 128
Details how to configure all of the features i will add the rest once i come back
GPU Configuration:
To configure the max or min gpu frequency you would go to either of the following files in a root enabled file browser and change the value inside
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq_gpu
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq_gpu
The allowed values for the files are as followed:
667, 600, 533, 480, 420, 350, 266, 177, 100
T800 owners the default min gpu freq is 100 on all roms if that causes issues raise the min freq to 266 you will probably not notice a battery decreases if that still does not work let me know i'll take a look at the code.
Reserved
Reserved
Thanks, working great on CM12.
Thank you man.. Im glad someone finely separated the device tree... And specially Happy about a new kernel that I can use in my Project Roms.
With all Credits going to you of course.. thanks again.
Hey mate, thanks for this!
I'm a little unsure about the new and old ramdisk thingy.
Running aicp on my klmitwifi, new ramdisk is cool?
Will try anyway, but let me know please!
Edit :
just checked, didn't stupidly before, Looks like the kernel is baked in your AICP rom.
Thanks again for your hard work!
Edit edit:
tried the v02 on the rom mentioned, had to revert cause I was having many ui fc.
Used new ramdisk version, could be that or I should have done a clean flash maybe?
Thanks for this, hopefully if fixes the lag issue for me on CM12 with the T800.
Thanks for all the hard work, grid .1 and .2 both worked perfect on bliss rom
Thanks, I will use your kernel on my chagallwifi SlimLP builds
Wait, does the Deathly kernel already in CarbonROM for T700 have F2FS support already? Or is that for the New Version and not yet built for klimtwifi? Thanks
SkOrPn said:
Wait, does the Deathly kernel already in CarbonROM for T700 have F2FS support already? Or is that for the New Version and not yet built for klimtwifi? Thanks
Click to expand...
Click to collapse
The f2fs version in the carbon build is not updated like it is now so i can not guarantee it works the next build will work though
deadman96385 said:
The f2fs version in the carbon build is not updated like it is now so i can not guarantee it works the next build will work though
Click to expand...
Click to collapse
OK, thanks. Hope your enjoying your time off... :good:
I'm going to backup your kernel and try ashyx's new build released today. Its closer to stock but has F2FS support also. Then I will test yours once its updated. Loving this new tab of mine, almost forgot how much fun it was trying to find the sweet spot on a device, lol. My Nexus 7 found its sweet spot a long time ago and now its just a plain ole boring tablet. hehe
diegocr said:
Thanks, I will use your kernel on my chagallwifi SlimLP builds
Click to expand...
Click to collapse
...Slim LP, for t800 maybe, where to find it?
m.
meduza2 said:
...Slim LP, for t800 maybe, where to find it?
m.
Click to expand...
Click to collapse
In SlimRoms Builders Collective
diegocr said:
In SlimRoms Builders Collective
Click to expand...
Click to collapse
...nice Do you intend to make an own SLIM LP thread?
m.
meduza2 said:
...nice Do you intend to make an own SLIM LP thread?
m.
Click to expand...
Click to collapse
Great idea, but now I have no time to keep updated
diegocr said:
Great idea, but now I have no time to keep you updated
Click to expand...
Click to collapse
Would be really great!!
I would like to see SLIM LP on my tab s A platform to exchange user experience for our specific device would be very helpful for you and us
m.
meduza2 said:
Would be really great!!
I would like to see SLIM LP on my tab s A platform to exchange user experience for our specific device would be very helpful for you and us
m.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-tab-s/development/rom-ezio84-slimlp-t3146025

[KERNEL] [EOL] [OnePlus3] [OOS 5, 4, 3] Boeffla-Kernel (15-01-2019)

*** This kernel is now end-of-life, not supported and developed anymore !!! ***
Hi all,
some of you know me from the other OnePlus or Samsung devices areas, where I provide my kernels already for more than three years to OnePlus One, OnePlus Two, OnePlus X, Galaxy S5, S3 and Note 10.1 users for all sort of platforms (Samsung, Cyanogenmod, Omnirom etc.)
Please note:
I am not heading to have as many features as possible implemented, this is not my design goal. If you are more into that, move on to other, good existing kernels. If you are searching for a good mix of improvements and new functions while not sacrificing stability, you are welcome here (see below the history section for more info).
Compatibility
Important: This kernel is only meant to be compatible with official OnePlus OOS and nothing else.
So when the kernel does not run on custom rom XYZ, do not even bother me with it or ask hundred times in the thread for compatibility.
I could not care less about it !!
To add: An open beta (aka community build) is NOT an official build supported here. If you use a community build and have issues, don't complain or even report. I am not merging any kernel changes from open betas into my kernels !!
Important notes
When using new anykernel concept Boeffla-Kernel: Flash stock kernel of rom first !
This kernel is ONLY compatible to OxygenOs stock, nothing else !!!
If you are using a custom rom that bases on OxygenOs, it might work. However, if it does not work, do not expect me to do tweak to make the kernel running with your favorite rom. I would not do it - my one and only reference is OxygenOs stock.
It is not supposed to be compatible to CM, HydrogenOS etc.
Also note: You have to use Boeffla-Config app which I provide on my homepage to tweak the kernel. 3rd party apps will not be able to unleash the full power of the kernel.
Installation
Read the install instructions in the support section on the Boeffla Site.
Support
First read the FAQ section on the Homepage !!!
Click here to learn about all possible kernel settings in the config app (outdated at the moment).
Click here to learn about using the config app (outdated at the moment).
I will refuse to give support if you do any undervolting/overclocking and experience freezes or hot reboots.
I will also not provide any support if you do not use Boeffla-Config app to tweak the kernel, other 3rd party tweaking apps are known (and intended) to cause issues.
I will refuse to give support if you have xposed framework installed and reporting any kind of weird issues. My opinion to xposed it quite clear: too powerful for >90% of the users that just mess up their system with it.
Otherwise, you can get in touch with me via the support e-mail address: [email protected]
Please provide kernel version, rom version, a detailed issue description and ideally supporting screenshots or log files.
Change logs
(you can also access them directly in Boeffla-Config V2 by pressing menu and selecting "change log...")
Change log for OxygenOS 4.x.x kernel - Click here
Change log for OxygenOS 3.x.x kernel - Click here
Features
Note: This kernel only runs on OOS 3.x.x for the OnePlus 3 - nothing else !!!
Support of anykernel concept (only latest kernels) - flash stock kernel before flashing Boeffla
Full integration with Boeffla-Config V2 (you need at least version 2.4.02 or higher !!!) configuration app (get it from http://www.boeffla.de) to configure all kernel settings
Dash charging fully supported
The two CPU clusters (big and little cpu) can be configured completely separate in terms of min/max frequencies, governors and CPU core profiles
Additional governors: Impulse, zzmoove, elementalx, conservative, ondemand, blu_active
Additional schedulers: fiops, bfq, sio, sioplus, fifo, vr, tripndroid, zen, maple
CPU overclocking - one additional overclocking step for both clusters (1,72 GHz for little CPU / 2,26 GHz for big CPU)
No GPU overclocking, no CPU and GPU voltage interface
USB charge rate bumped up to 900 mA
Boeffla charge analysis (display of charger type and charge current in Boeffla-Config app in real time)
Boeffla touchkey LED control (LEDs fully off, LED on screen touch, configurable duration)
CPU core profiles to restrict number of CPU cores being used (the OP3 does not hotplug based on load)
Notification LED control (effect + speed for blinking/fading, brightness for continuous notification like battery charging etc.)
Boeffla-Sound engine: Headphone volume and speaker volume (only lowering volumes for speaker)
Dynamic FSync (activated if screen on, deactived if screen off), configurable
Input boost frequencies and duration configurable per CPU cluster, input boost switch
Show CPU frequency usage per CPU and frequency in Boeffla-Config
Show GPU frequency usage per frequency in Boeffla-Config
KCal V2 Color control
Display backlight limits configurable (to avoid display brightness gets too low in some situations)
Display backlight dimmer
Swipe2wake gestures
Control haptic feedback of gestures (except fingerprint)
Haptic feedback intensity control
Swipe2sleep gestures
Boeffla generic wakelock blocker V1.1.0 (documentation)
SD card read ahead buffer configurable (default increased to 1024 kB)
Ext4 File system tweaks (default to on, can be disabled)
Kernel logger (dmesg) configurable
CIFS support (module, do not mount inside /data, if you rooted with Chainfire SuperSu, make sure you uncheck the namespace separation in SuperSu app)
NFS support (module)
NTFS support (module)
XBox support (module)
OTG-Ethernet support (module)
TCP Congestion changed to Westwood
Many additional TCP congestion algorithms available
Entropy values configurable
Hardware touch keys are locked as long as screen is in use (touched) for better usability
Swap supported
Various minor kernel tweaks
Doze mode configurable in Boeffla-Config
Full selinux strict support (switchable to permissive on demand)
Show speedbin information (PVS level) in Boeffla-Config app
init.d support (in /system/etc/init.d - set correct permissions!)
Automatic EFS backup
Integrated full busybox 1.27.2 (own compilation)
Kernel initialisation log file (with history of 3 log files)
Emergency reset script automatically placed into /boeffla-kernel-data folder of your internal memory
Google gcc 4.9 toolchain (64 bit) used for best stability
Always based on latest OOS kernel sources (https://github.com/OnePlusOSS/android_kernel_oneplus_msm8996)
Download
For all information and downloads (stable AND testing versions), visit the Boeffla-Kernel homepage:
www.boeffla.de
History and design targets
Basically I created my first Boeffla-Kernel in 2012 as there was no kernel for the Samsung Galaxy S3 around that had exactly the mix of functionalities that I wanted. I wanted to have full flexibility in undervolting and charge rates for instance, but did not like the sharpness and/or brightness tweaks many kernels have implemented as per default.
Hence, I began to create my own kernel after a while, adding all the features I like. This is the result of my work, which in the end I decided to share with you. I hope you like it as much as I do.
The objective of this kernel is to have a kernel for daily use. It does not aim for best battery life, or best smoothness or best benchmark scores. Also it does not aim to have the broadest feature set available everywhere.
It aims more for a good mix of all, not sacrificing stability and functionality in the end.
And - most important: It aims to stay quite close to stock !!!
These design targets are also valid for the OnePlus kernel here!!!
This said, I will definitely NEVER implement:
things I do personally not need
things I do not like
things that are in any way dangerous
anything which is highly experimental
f2fs - it is known to cause various issues and compatibility problems
a CAF based kernel
anything that requires upstreaming of kernel parts to a higher kernel major version
So do not even ask for it if it falls into the listed categories. Everything else I am happy to check and decide.
And: I do not really care about benchmark numbers, they say almost nothing as long as something is not completely wrong. Important for me is the feel-good factor.
I am also not interested in gaming at all, so never expect a gamer kernel. It will just not happen...
Compatibility
To reiterate it again: Flash the kernel only if you are running a compatible rom !!!
Configuration of the kernel
To tweak and configure the kernel, manually load and install the app "Boeffla-Config V2" from the downloads section on www.boeffla.de.
You need at least version 2.4.02 or higher for the OnePlus 3 Boeffla Kernels.
Donation
If you like my work, feel free to donate: Donation-Link
If you donate at least 2,49 EUR (to be in line with the donation app prices on Google Play store), you will receive a personal donation code which unlocks some nice little comfort functions in Boeffla-Config V2 on top.
Source code
All sources can be found in my Github repository: http://github.com/andip71
Credits to developers
Of course, I had never been able to create all that by my own. So I want to give credits to the really good developers around, that have given me all the inspiration and from which I cherry picked lots of the implemented functionalities:
* ZaneZam
* Grarak
* Yank555
* Hardcore
* Chainfire
* AndreiLux
* Netarchy
* Gokhanmoral
* Simone201
* Mialwe
* Entropy512
* Faux
* Harunjo
* FranciscoFranco
* Ak
* Osm0sis
... I just hope I did not forget someone. If so, please let me know and I will add you of course.
Thanks to all of you for your great work !!!
Disclaimer
*** As always - Flash on our own risk! ***
Make sure you flash the correct version depending on your firmware version!
I can and will not take any responsibility for bricked phones or lost data.
It is generally recommended to run a complete Nandroid backup in your custom recovery and safely store your personal data before you flash a new kernel.
Cheers and enjoy
Andi
Latest change log:
OOS4
http://kernel.boeffla.de/oneplus3/boeffla-kernel-oos/oos4xx/changelog.htm
OOS3
http://kernel.boeffla.de/oneplus3/boeffla-kernel-oos/oos3xx/changelog.htm
Configuration and profile thread
http://forum.xda-developers.com/oneplus-3/how-to/profiles-boeffla-kernel-profiles-t3455503
*** You want my support? Then stick to my rules ***
Guys, I am receiving more and more completely useless support requests in different threads. Useless because people provide nothing to be able to help, not even the minimal possible information they could give.
Hence, I will now remind anyone again on the support guide lines stated here:
http://boeffla.de/index.php/support/support
Also you need to ensure you follow the installation guide lines incl. trouble-shooting stated here:
http://boeffla.de/index.php/support/installation-how-to
And to cut a long story short: If you do not at least provide what I request in the support guide lines, I will IGNORE YOUR REQUESTS IN FUTURE.
Straight and simple. I have enough of people wasting my time just because they are too lazy to write details.
Period.
Also as a reminder:
you use xposed? -> no support, everything is your own issue
you use a custom rom and not the official stock or CM one? -> good luck, you are on your own
you undervolt or overclock? -> have fun, but without my support
Sorry, this might sound harsh (and it is meant to sound harsh), but you cannot imagine about how crappy support requests can be. Stating something does not work is just not enough.
Please consider that!!!
Andi
Allright folks, thread is open. Kernel is available for download.
Before you start, please make sure you read the following information at least:
http://boeffla.de/index.php/support/installation-how-to
http://boeffla.de/index.php/support/support
If you have trouble, I ask you to also scan for your issue in the OnePlus 2 thread, as major parts are the same on both devices (http://forum.xda-developers.com/oneplus-2/orig-development/kernel-boeffla-kernel-05-10-2015-t3218164)
Enjoy
Andi
It's going to be legen. Wait for it. Dary
Thanks Dev for supporting OP3
Downloading rn
Awesome ... Thanks for this ....
Great work..
To restore old kernel stock..is it possible to have it too??
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
isoladisegnata said:
Great work..
To restore old kernel stock..is it possible to have it too??
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Click to expand...
Click to collapse
Let me create a stock kernel section for it on www.boeffla.de, then yes. But this can take till tomorrow, I am out very soon today.
Apart from that, you can always flash OOS dirty over, this brings you stock kernel back.
Andi
Lord Boeffla said:
Let me create a stock kernel section for it quickly on www.boeffla.de, then yes.
Apart from that, you can always flash OOS dirty over, this brings you stock kernel back.
Andi
Click to expand...
Click to collapse
Yes..
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
isoladisegnata said:
Yes..
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Click to expand...
Click to collapse
Just corrected my statement, will not be before tomorrow as I have to leave very early today for an appointment.
Andi
hail to the lord of kernels
isoladisegnata said:
Great work..
To restore old kernel stock..is it possible to have it too??
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Click to expand...
Click to collapse
With Flashify you can backup and restore the stock kernel.
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Der-Knuffi said:
With Flashify you can backup and restore the stock kernel.
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
Yeees, but... not 100%.
IMHO it backups the kernel image, but not the kernel modules too.
And OnePlus is using kernel modules on OOS.
Just to be very precise.
Andi
its not yet available to download?
tatuboy said:
its not yet available to download?
Click to expand...
Click to collapse
What?
And why should it be not?
Be more specific pls.
Andi
Download of OOS kernel working here.
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
It finally happened
OMG.
Now I have no excuses anymore to not buy a Oneplus 3.
So it was a short interruption without Boeffla on LG G4 (5 months)
Many, many thanks for this.
Hail to Lord Boeffla. I can not live without your kernels
Greetings and keep calm.
Some got the app working on 3.5.1?
C.H.T.J. said:
Some got the app working on 3.5.1?
Click to expand...
Click to collapse
Same here, not working boeffla config in OSS 3.5.1... The kernel is very good, smooth, but the apk isn't working yet...
Good job bro, your kernel is awesome..
Sent from my ONEPLUS A3003 using Tapatalk
What is your webpages
Code:
http://kernel.boeffla.de/oneplus3/boeffla-kernel-oos/oos3xx_download/Stable
wrong with the ESET antivirus selectively alert immediately and does not reach the website.
Indicates that the page is harmful.

[KERNEL] Neon Kernel [4.14.195] [Nethunter] [MIUI 12/STOCK]

NEON KERNEL
Disclaimer:
Use this kernel at your own risk. Flashing it may brick your device. I'm not responsible for any software/hardware and any kind of damages/losses.​
Changelog v1.01
Upstreamed To Latest CAF With Linux Stable Merged.
Full Nethunter Support.
Supports Internal Monitor Mode.
Lots Of Under The Hood Bug Fixes.
Download
Click Me
How to flash:
- reboot into recovery
- make a backup of your original boot.img
- flash zip
- flash magisk if needed
- wipe dalvik (mandatory!)
XDA:DevDB Information
Neon Kernel, Kernel for the Xiaomi Mi A3
Contributors
arunbiju969, paul89rulez
Source Code: [url]https://github.com/ArunBiju/Neon-Kernel[/url]
Version Information
Status: Stable
Current Stable Version: v1.01
Stable Release Date: 2020-09-01
Created 2020-08-31
Last Updated 2020-08-31
Reserved1
Reserved2
Hi,
1- Can you add patching kernel so flashing magisk is not necessary.
2- Can this kernel be used in Custom Roms?
3- Whats the point of this kernel battery,performance,balanced or only for Nethunter?
sasukeob said:
Hi,
1- Can you add patching kernel so flashing magisk is not necessary.
2- Can this kernel be used in Custom Roms?
3- Whats the point of this kernel battery,performance,balanced or only for Nethunter?
Click to expand...
Click to collapse
Patching is already present, this kernel was also tested on crDroid basically any rom with stock vendor and MIUI, Finally this kernel is made for balanced use with Good performance and Battery with the latest bug fixes from ALS and nethunter is bonus.
bad news for me. Because i have OSS vendor and Pixel Experience Rom. so i cant flash it.. Sad..
sasukeob said:
bad news for me. Because i have OSS vendor and Pixel Experience Rom. so i cant flash it.. Sad..
Click to expand...
Click to collapse
I am planning an OSS release.
if it has flashing kernel and magisk flashing not necessary again, and if it has for OSS vendor, i will definetly try this kernel
Does packet injection work to do Deauth attacks, I would like to do deauth attacks without the need for a wifi adapter, by the way does it support all kinds of wifi adapters?
Charly737 said:
Does packet injection work to do Deauth attacks, I would like to do deauth attacks without the need for a wifi adapter, by the way does it support all kinds of wifi adapters?
Click to expand...
Click to collapse
Internal packet injection is not present as of now and yes it supports all the adapter supported by Kali Nethunter.
Friend since I installed this kernel I cannot use my phone as a universal remote control every time I try it restarts my phone I checked it and it is the friend kernel.
Also quick bug report
Face unlock doesn't work with this kernel.
Don't use it that much so it's not a big deal for me but have since switched to a different oss ROM and never got a log of the issue, my apologies
arunbiju969 said:
Patching is already present, this kernel was also tested on crDroid basically any rom with stock vendor and MIUI, Finally this kernel is made for balanced use with Good performance and Battery with the latest bug fixes from ALS and nethunter is bonus.
Click to expand...
Click to collapse
Well this may sound stupid or dumb but i had to, so how was the battery backup on crDroid? because i am trying find a perfect kernel to get the best battery backup i could from a 4000 mah and i have the CrDroid.
thanks for making this ( THANKED )
Regards.
Are you guys using Kali Nethunter or X-Tools via Termux?
nice effort,
is it better than perf+?
Hello. I cannot start a covert attack with your kernel, that is, I connect the phone to the computer, click on Execute attack, for 1 second the inscription: attack launched appears, and then the inscription: attack execution appears
ended. Tested on Windows 10. Internal monitor mode works and duckHunter Hid works too. Firmware: android 10 stock
Hey, airmon-ng working??? I need this kernel to get wifi handshakes using built-in wifi, if its already working please let me know.
Charly737 said:
Friend since I installed this kernel I cannot use my phone as a universal remote control every time I try it restarts my phone I checked it and it is the friend kernel.
Click to expand...
Click to collapse
Which phone you have
Is for Stock a10 or A11?
Gauravnoob said:
Which phone you have
Click to expand...
Click to collapse
Mia A3 Android 11

Categories

Resources