[Q] Silverneedle and custom kernals - HTC EVO 3D

So I'm new to android and have some questions about replacement kernals. I'm just not sure about some of the terminology being used. I was looking at the thread for Silverneedle http://forum.xda-developers.com/showthread.php?t=1194190
Current things of interest:
- CIFS
- TUN
- Overclock up to 1.7ghz currently (this will be expanded in future builds)
- JHash3
- The usual assortment of build tweaks that those familiar with my previous work have come to expect
Click to expand...
Click to collapse
Specifically can anybody expand on the terms CIFS, TUN and JHash3. Also what other tweaks is he referring to? I'm not familiar with his other work or other kernals in general.
I'm coming from webos, so I know that custom kernals can offer all sorts of different advantages over stock ones. What benefits can I expect if I use silverneedle?
Thanks in advance

Related

TELUS [KERNEL]05.12.2011 test-kernels [CM7/MIUI] platypus;SECURITY,VOODOO,OC/UV,more

Hi guys,
BIG FAT WARNING
WARNING: TELUS ONLY
this is my first modded kernel for the [ Telus Fascinate ]
T E L U S FASCINATE edition of the Platypus Revolutions kernel
This Project is inactive/low activity for a longer period of time
Kernel
CM7 & MIUI only
NEO series
(since May 24th '11)
Do you want to discuss on this kernel, get the news on the current state of development, or test kernels even fresher than fresh ?
connect via webchat from your browser:
http://webchat.quakenet.org/
and join #platypus-kernel
(recommended)
Fire up your IRC client, and join via client
the server (for now is) : irc.quakenet.org
port : 6667
Channel : #platypus-kernel​
(thanks to Tk for the layout idea )
before you ask for any ETAs:
The first rule of CyanogenMod [and this project]: DO NOT ASK FOR AN ETA!
First step before install & kernel switch:
Always have this cleaning script on your internal SD card ready
If you're switching kernels, have issues with auto-rotation, the cam, bootloops or other sorts of problem (failed overclock attempt),
please use lippol94's updated cleaning script (apply via CWM recovery) :http://www.multiupload.com/XFH1GCK4MB
Introduction:
Hi guys,
this is my first modded kernel for the SGS/Telus Fascinate (CM7/MIUI only)
I first needed to test it to make sure that it'll be stable & boot at the first place
so far it's very fast & responsive & smooth
This thread shall serve as the center for my testing kernels (stability & functionality-wise)
DISCLAIMER: the kernel (binary) and driver modules are provided as is. If problems occcur they most probably are from upstream and can be fixed with the newest version. Since I'm doing this in my free spare time as a hobby (quenching my thirst for tweaks & performance) updates will occur irregularly as time permits and I see fit (most probably when new features & bugfixes arrive). YOU are responsible for the actions that you take (such as over- or underclocking), etc. You agree that I can not be held liable for any potential damage that arises from your actions in combination with or the usage of this kernel and other related parts.
Kudos:
* Google, Andy Rubin & the whole Android crew
* Linus Torvalds & the kernel hackers for upstream Linux
* cyanogen & all the devs out there hacking on this
* Supercurio for enriching our media experience of this smartphone
* codeworkx, coolya, guiper, atinm - the whole teamhacksung|cmsgsteam crew and all other hackers working on CM7
* laststufo, hardcore, nikademus, existz and all the other kernel hackers on the SGS forum
* zen-kernel team for inspiration to create a kernel, too
* all other contributors (devs, users, etc.) who make this possible
The purpose of these kernels is extensive stability testing addressing the following sticking points:
- overall stability & functioning of the kernel and phone
- call drops, missed calls, etc.
- lags (suggestions for improvements are welcome)
- auto-rotation, sensors, etc.
- Voodoo Control Plus [any crashes ? compatibility problems ?]
- working on CM7 or MIUI ?
- scheduler, sound, video synchronisation & lags: Tap Tap Revenge 4 (especially at the beginning of songs)
- scheduler, sound, video synchronisation and any other issues: doodle dash (while shooting & sound activated)
- proper pmem memory layout & settings: proper functioning of Google Googles
for those who love SAUCE (Source):
old source:
ALL MY SAUCE for QUORRA KernalZ ^^
new source:
android_kernel_samsung_aries
(fork and 1:1 update to upstream kernel source - changes in different branches)
(latest changes sometimes might not be in [yet] but in the whole repo everything should be available)
current UV & OC stable values:
Recommended apps for OC/UV:
- Pimp my CPU (also available here on XDA for those who don't have a credit card, etc.)
- Xan's VoltageControl
on stability testing:
http://forum.xda-developers.com/showpost.php?p=13255871&postcount=5
(start with "Q: I'm new in OC/OV operations so please could you explain to me how to set it in the best way?")
the following OC/UV values are only applicable for kernels with the old OC/UV implementation (max. 1.3 GHz)
my current UV (undervolt) stable Values :
old OC/UV implementation (morfic, bilboa1/kang, TheEscapist):
1300000 0 (haven't tested 1.3 GHz much yet)
1200000 -25
1000000 -50
800000 -75
600000 -100
400000 -100
200000 -125
100000 -150
edit:
1200000 -50
1000000 -75
800000 -75
600000 -225
400000 -125
200000 -150
100000 -175
thanks jetcz !
new OC/UV implementation (morfic, bilboa1/kang, TheEscapist - Tk-Glitch):
Tk-Glitch said:
Note that these UV settings will be unstable on many devices. It's only informative.
1600 MHz - 1.500v / -> That's high and many devices will fail on this frequency. Find working UV for you if any.
1500 MHz - 1.500v / -> That's high and many devices will fail on this frequency. Find working UV for you if any.
1440 MHz - 1.475v / -75mv
1400 MHz - 1.450v / -75mv
1300 MHz - 1.400v / -75mv
1200 MHz - 1.350v / -75mv
1000 MHz - 1.250v / -50mv - If you have stability issues, try to let this one by default.
800 MHz - 1.200v / -75mv
400 MHz - 1.050v / -100mv
200 MHz - 0.950v / -150mv
100 MHz - 0.950v / -200mv - (can be very different between two devices)
More volts is not always equal to more stability. Try to add more UV (less volts) if the frequency you're trying to achieve is unstable.
Considering all phones will respond differently to OC/UV, to tweak the values to suit your device will be required.
By default, no overclock/undervolt is applied. You'll need to use one of the tools below to adjust the frequencies and voltages.
Note : Never ever use SetCPU with this kernel. You could encounter many stability problems like random reboots or bootloops.
Click to expand...
Click to collapse
3D performance and games:
recommended apps:
[root] Chainfire3D
Currently there's no CM7, but MIUI(Not Fully Functioning).
old stuff removed ...
latest kernels:
NEO 17 -r18 codename: Butterfly
http://forum.xda-developers.com/showpost.php?p=18281665&postcount=62
NEO 18-update1 codename: funky fish
NEO XX.1-update1 codename: mighty rhino
http://forum.xda-developers.com/showpost.php?p=20000152&postcount=71
ALL USERS MUST UPDATE (this fixes yet another potential data loss trigger)
xHoLyx said:
Currently there's no CM7, but MIUI(Not Fully Functioning).
Click to expand...
Click to collapse
I see
what is broken besides the keymappings ?
thanks !
zacharias.maladroit said:
I see
what is broken besides the keymappings ?
thanks !
Click to expand...
Click to collapse
If you are asking what is broken with MIUI/AOSP/CM6 for the fascinate VZW it is MMS, in call Bluetooth and camcorder
kidserious said:
If you are asking what is broken with MIUI/AOSP/CM6 for the fascinate VZW it is MMS, in call Bluetooth and camcorder
Click to expand...
Click to collapse
ok, well so hopefully
harimgs can shed light on what he did to get CM7 and/or MIUI to work on his Telus Fascinate
repost from the SGS kernel thread:
harimgs please comment on the
CM7/MIUI platypus kernel thread at the Fascinate development forums
on how you got your phone working with CM7 and/or MIUI
[KERNEL][CM7/MIUI] 18/04,platypus,Voodoo SOUND&COLOR,OC/UV,SLQB,LED notif,NODEBUG,...
it probably includes:
- creating a tar initial kernel for flashing with Odin
- replacing the kernel in an initial update-package from the SGS with my kernel (for the telus fascinate)
- then following the steps codeworkx posted at [All Models] CyanogenMod 7 for Samsung Galaxy S Phones - EXPERIMENTAL
I'm not sure though
thanks !
zacharias.maladroit said:
ok, well so hopefully
harimgs can shed light on what he did to get CM7 and/or MIUI to work on his Telus Fascinate
Click to expand...
Click to collapse
I hope so, cuz sammy and verizon have left us fascinate folks on the back burner. Any ideas would be awesome. I commend our devs for what they have done with so little official sources or support.
zacharias.maladroit said:
ok, well so hopefully
harimgs can shed light on what he did to get CM7 and/or MIUI to work on his Telus Fascinate
Click to expand...
Click to collapse
If this is Telus Fascinate only you should consider putting that in the title. That would make it easier for us Verizon users to not clog up your thread. Thanks and good work none the less.
Sent from my SCH-I500 using Tapatalk
zacharias.maladroit said:
repost from the SGS kernel thread:
harimgs please comment on the
CM7/MIUI platypus kernel thread at the Fascinate development forums
on how you got your phone working with CM7 and/or MIUI
[KERNEL][CM7/MIUI] 18/04,platypus,Voodoo SOUND&COLOR,OC/UV,SLQB,LED notif,NODEBUG,...
it probably includes:
- creating a tar initial kernel for flashing with Odin
- replacing the kernel in an initial update-package from the SGS with my kernel (for the telus fascinate)
- then following the steps codeworkx posted at [All Models] CyanogenMod 7 for Samsung Galaxy S Phones - EXPERIMENTAL
I'm not sure though
thanks !
Click to expand...
Click to collapse
I'm not sure any of this will work for our phone. Sounds like just the telus fascinate.
You may want to put a note that this is for Telus in the OP in bold/red so there aren't VZW Fascinate users flashing this and wondering why nothing works.
zacharias.maladroit said:
repost from the SGS kernel thread:
harimgs please comment on the
CM7/MIUI platypus kernel thread at the Fascinate development forums
on how you got your phone working with CM7 and/or MIUI
[KERNEL][CM7/MIUI] 18/04,platypus,Voodoo SOUND&COLOR,OC/UV,SLQB,LED notif,NODEBUG,...
it probably includes:
- creating a tar initial kernel for flashing with Odin
- replacing the kernel in an initial update-package from the SGS with my kernel (for the telus fascinate)
- then following the steps codeworkx posted at [All Models] CyanogenMod 7 for Samsung Galaxy S Phones - EXPERIMENTAL
I'm not sure though
thanks !
Click to expand...
Click to collapse
i doubt it would work... but always better to have more brain.
He can visit IRC anytime
#Samsung-Fascinate
There are about 8 devs who can help.
evilhunter101 said:
If this is Telus Fascinate only you should consider putting that in the title. That would make it easier for us Verizon users to not clog up your thread. Thanks and good work none the less.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
kidserious said:
I'm not sure any of this will work for our phone. Sounds like just the telus fascinate.
Click to expand...
Click to collapse
imnuts said:
You may want to put a note that this is for Telus in the OP in bold/red so there aren't VZW Fascinate users flashing this and wondering why nothing works.
Click to expand...
Click to collapse
ok, I clarified it in the thread title (TELUS FASCInate) - more room isn't there so hopefully that makes it clear
sorry any (potential) breakage
due to flashing this on an Fascinate
thanks !
First of all, I want to thank you for every second you put in this kernel. As stated, you should put TELUS ONLY in big red letter on the first post. as we dont have our own thread, people don't read enough and say "Hey, its for fascinate, i'll try it".I'll test it as soon as i'll be able and i'll tell you if there is problem. But i didn't saw much problem on your i9000 kernel so i don't think there will be more with this one. Thanks again fellas, keep your good work going ^^.
@chadouming:
done
hope that's BIG enough
Big thanks for building this for the Telus Fascinate
I didn't find it stated in your post, but does this kernel include any lagfix as well?
Is it compatible with any other custom roms or only MIUI and CM7??
Sent from my T959D on Trigger 2.9.2.
daoom said:
Big thanks for building this for the Telus Fascinate
I didn't find it stated in your post, but does this kernel include any lagfix as well?
Click to expand...
Click to collapse
no lagfix needed (it's using yaffs2 for all partitions, ext4 for /data)
once you've tried it - you'll see that it's literally flying
cowvun said:
Is it compatible with any other custom roms or only MIUI and CM7??
Sent from my T959D on Trigger 2.9.2.
Click to expand...
Click to collapse
nope since the partition layout is different from that of Samsung ROMs
CM7 which MIUI is also based on tries to stay as close to AOSP (android open source project) as possible
so it'll only work with that
besides that Samsung ROMs include a lot of proprietary stuff that only works with Touchwiz
some more info:
harimgs said:
Sorry for my bad english
So I finally compiled cm7 platypus kernel for Telus Fascinate GSM PHONE(not verizon(CDMA))
changing little bit of mach-s5pv210/mach-aries.c(see attached changed keymapping part )
Telus fasinate is same as galaxys i9000 except softkey(same softkey with captivate)
so I changed the keymapping for glaxys with captivate in mach-aries.c
and than compiled it with using galaxys config
I flashed it into my phone and everything is working fine except WI-FI
It gives me error when i try to turn it on.
I also swapped bcm4329.ko and tun.ko ,but still it gives me error
If i use i9000 kernel it works fine
I tried many times comping new kernel, but still no kernel works.
also tried reboot my phone,but still not working
any solution? or can anyone compile for me?
cm7 telus fasinate platypus kernel.zip <---- click here to download
Click to expand...
Click to collapse
daoom said:
I didn't find it stated in your post, but does this kernel include any lagfix as well?
Click to expand...
Click to collapse
CM7 is ext4-only. No RFS.
zacharias.maladroit said:
@chadouming:
done
hope that's BIG enough
Click to expand...
Click to collapse
Yeah, really obvious now, which is just perfect for fast reader. thx

[Q] The Only Thing I'm Not New To, Is Flashing ROMs

Okay, I am a noob. Glad to be on XDA, but a noob nonetheless.
I know the basic in's and out's of flashing, backing up ROMs, etc.
Well, I want to learn how to start writing my own custom ROMs.
I have (at least I think) most of the necessary software, SDK Tools, Microsoft Basic and C++ 2010. But I don't have anything but basic knowledge of code. Anybody willing to help a noob out and get me kick-started in making ROMs and coding in general?
The only device I have to work with is a PC and my HTC DInc. It's been a great phone
I'd much appreciate the help.
Thanks in advance,
TheSmashippy
The kernel is in C
Android is mostly java (if its open source = Cyanogenmod).
But most Roms just and and replace apps. Maybe add some themes and stuff. Have a modded kernel for OC and stuff. And thats mostly it.
Smasher816 said:
The kernel is in C
Android is mostly java (if its open source = Cyanogenmod).
But most Roms just and and replace apps. Maybe add some themes and stuff. Have a modded kernel for OC and stuff. And thats mostly it.
Click to expand...
Click to collapse
Well, see I don't really get most of that. I don't understand the differences between C and C++ and Basic, I know they're separate languages, but I don't really notice any differences.
And I have never flashed a new kernel before, just new ROMs I'm actually pretty sure I still have the Stock DInc kernel, unless a few of the ROMs I've flashed came with kernels specifically for them... Not really sure how kernels effect the ROM :/ Like I said, noob. Hard.
Well, until you have flashing down, then I would stick there. Once you do it a few times, it is no big deal. The first time might have you on the edge of your seat.
thesmashippy said:
Not really sure how kernels affect the ROM :/.
Click to expand...
Click to collapse
The Kernel has a major effect on the rom. Changing a kernel can make a rom much better or far worst. Kernels allow many customizations in the rom like overclocking. Here's an example of this: Kernel A may allow your device to be overclocked to 1.2Ghz and Kernel B may allow your device to be overclocked to 1.9Ghz. See here: http://en.wikipedia.org/wiki/Kernel_(computing) . It's basically the same in Android.
Theonew said:
The Kernel has a major effect on the rom. Changing a kernel can make a rom much better or far worst. Kernels allow many customizations in the rom like overclocking. Here's an example of this: Kernel A may allow your device to be overclocked to 1.2Ghz and Kernel B may allow your device to be overclocked to 1.9Ghz. See here: "could not quote this url due to noobiness" . It's basically the same in Android.
Click to expand...
Click to collapse
Thanks for the description man that really specified it for me.
Ok, learning a bit at a time is good Anyone want to take me under their wing and teach me about writing code and creating my own ROMs?

[Q] Resurrection Remix install dude - Solved

My question is when u install resurrection remix there are 3 types of kernetl i want to know what are the differences between them.
why dont you ask this question in Resurrection Remix thread?, just use siyah kernel or go to the kernel threads and read the differences between them.
Just to give you a brief overview,
Siyah: This kernel allows you to tweak many things, including overclocking, undervolting and having the largest array of governors to choose from. It would probably be best to use try to take full advantage of this kernel only if you know what you're doing....
CM10: This kernel is CyanogenMod 10's kernel as its name suggests. It is reported by many users to feature excellent battery life.
Fluxi: This is a custom kernel that is also reported by many users to have excellent battery life.
If you want to know more, do as republicano suggests and go look into their threads (Fluxi and Siyah). For CM10 you'll have to google it because as far as I can see it does not have a thread in the SGSII section of this forum.
Will2000 said:
Just to give you a brief overview,
Siyah: This kernel allows you to tweak many things, including overclocking, undervolting and having the largest array of governors to choose from. It would probably be best to use try to take full advantage of this kernel only if you know what you're doing....
CM10: This kernel is CyanogenMod 10's kernel as its name suggests. It is reported by many users to feature excellent battery life.
Fluxi: This is a custom kernel that is also reported by many users to have excellent battery life.
If you want to know more, do as republicano suggests and go look into their threads (Fluxi and Siyah). For CM10 you'll have to google it because as far as I can see it does not have a thread in the SGSII section of this forum.
Click to expand...
Click to collapse
Good overview bro but you missed the info under CM10 kernel.
Stock CM10 kernel unlike CM9 (which give great battery life), eats/kill battery life like hell. That's why most people flash another kernel right after flashing CM10 / CM10-based Roms
Swyped from my Samsung Galaxy SII
hebyo1990 said:
My question is when u install resurrection remix there are 3 types of kernetl i want to know what are the differences between them.
Click to expand...
Click to collapse
Just go for the Siyah, its the best IMO...
U can try Dorimanx too
Thanks
Will2000 said:
Just to give you a brief overview,
Siyah: This kernel allows you to tweak many things, including overclocking, undervolting and having the largest array of governors to choose from. It would probably be best to use try to take full advantage of this kernel only if you know what you're doing....
CM10: This kernel is CyanogenMod 10's kernel as its name suggests. It is reported by many users to feature excellent battery life.
Fluxi: This is a custom kernel that is also reported by many users to have excellent battery life.
If you want to know more, do as republicano suggests and go look into their threads (Fluxi and Siyah). For CM10 you'll have to google it because as far as I can see it does not have a thread in the SGSII section of this forum.
Click to expand...
Click to collapse
thanks very much for answering my question

[Q] General question regarding kernels and android releases

Hi! This is maybe a general dev question, but I'd like to get an answer anyway:
what is exactly the link between an Android release and the kernel it works upon?
I noticed most recent releases use 3.0+ Linux kernels, and others (like the DSCs) use the Phoenix Universal Kernel, which is based on a 2.6.35... So I wonder: is ICS/JB in any way dependant on "newer" kernels?
I understand the answer must be closer to "no", since the pre-alpha build also uses a fork of the PUK, but the fact that it uses a *different version* makes me wonder how much work does it take to get a kernel ready for a newer release, and most importantly... why?
Thanks a lot! Total n00b here, but eager to know more.
Newer kernel not required at least for ICS.
All GB/ICS kernels are based on this kernel (and it's a Dell's lie about using same sources for 407 release as SoD was fixed there without switching timer source):
http://opensource.dell.com/releases/streak/4.05_and_4.07/
kibuuka successfully applied kgsl/genlock patch and it's the only thing actually needed for ICS.
List (a bit old) of changes in Phoenix kernel and later derivatives:
http://forum.xda-developers.com/showpost.php?p=25291276&postcount=3812

[EOL] [KERNEL] [SM-G900F] [Lineage14/CM13/12.1/12/11] Boeffla-Kernel (28-03-2018)

** Note: This kernel is end-of-life and will no more be maintained. There will be no LineageOS 15.1 or newer kernel be available anymore **
Hi all,
some of you know me from the Samsung devices area, where I provide my kernels already for more than two years to Galaxy S3 and Note 10.1 users for all sort of platforms (Samsung, Cyanogenmod, Omnirom etc.).
Maybe you also know me from my OnePlus One kernels I added in winter last year to my portfolio.
Finally I got a Samsung Galaxy S5 afew weeks ago and decided to port my kernel also to this device. This is a sponsored device, so I want to say a big thank you to the people that made it possible, namely the ones in the German Smartphone Forum www.hubo.in !!!
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).
For the Samsung Stock Boeffla-Kernel, please go HERE.
Important notes
When using new anykernel concept Boeffla-Kernel: Flash stock kernel of rom first !
Compatibility
Important: This kernel is only meant to be compatible with official LineageOS/Cyanogenmod 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 !!
Support
First read the FAQ section on the Homepage !!!
Click here to learn about all possible kernel settings in the config app.
Click here to learn about using the config app.
I will refuse to give support if you do any undervolting 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.
Change logs
(you can also access them directly in Boeffla-Config V2 by pressing menu and selecting "change log...")
Change log for CM14 kernels: CLICK HERE
Change log for CM13 kernels: CLICK HERE
Change log for CM12 kernels: CLICK HERE
Change log for CM11 kernels: CLICK HERE
Features
Support of anykernel concept (only latest kernels) - flash stock kernel before flashing Boeffla
Full integration with Boeffla-Config V2 configuration app (get it from http://www.boeffla.de) to configure all kernel settings
Additional governors: zzmoove (Note: not considered stable at the moment, you might face reboots!!!), intelliactive, intellidemand, wheatley, smartmax, slim, intellimm, nightmare, lionheart, pegasusq
Zzmoove supporting native hotplugging profiles
Additional schedulers: fiops, bfq, sio, tripndroid, zen
Many Hotplug tweak profiles (Default, Optimized, 1 core max, 2 cores max, 3 cores max, 2 cores min, 3 cores min, 4 cores min, 2 cores exact, 3 cores exact)
Wake up gestures implemented (double-tap-to-wake, swipe to wake)
Boeffla-Sound engine (Headphones and speaker volume configurable)
Configurable vnswap
True dynamic FSync (activated if screen on, deactived if screen off), configurable
Touch boost frequency configurable, touch boost switch (all boosts removed by Lineage team in December 2016)
CPU Overclocking up to 2.84 GHz
CPU Voltages interface for undervolting/overvolting
GPU idle frequency 27 Mhz added
GPU governor selection support
Show GPU frequency usage per frequency in Boeffla-Config
Color control to adjust RGB color space + inverted mode
SD card read ahead buffer configurable (default increased to 1024 kB)
Ext4 File system tweaks (default to on, can be disabled)
System Tweaks predefined supported (default is off)
Android logger (logcat) configurable
Kernel logger (dmesg) configurable
Charge rates for AC charger, USB and wireless charging separately configurable (set charge rate to 0 to have stock charge logic back)
Charge information display support via Boeffla-Config V2 app
CIFS support (module, do not mount inside /data)
NFS support (module)
NTFS support (module)
XBox support (module)
OTG-Ethernet support (module)
TCP Congestion changed to Westwood
Swap supported (but not recommended, use zRam instead)
init.d support (in /system/etc/init.d - set correct permissions!)
Default entropies increased
Insecure kernel (adb has root privileges)
Automatic EFS backup
Kernel survival mode by Boeffla-Config app to survive CM rom flashes
Full support for mpdecision for best compatibility and smoothness
(Important: use Boeffla-Config to configure min/max CPU frequencies + governors + schedulers only - or explicitely allow other apps/processes to overwrite this in Boeffla-Config settings, but expect weird side effects)
Integrated full busybox 1.23.1 (own compilation)
Auto-Root by kernel possible by request, not recommended for CM however (latest su included)
Kernel initialisation log file (with history of 3 log files)
Emergency reset script automatically placed into /boeffla-kernel-data folder of your internal memory
Presets supported in Boeffla-Config by kernel (Extreme power, power, normal, battery friendly and battery saving)
Google gcc 4.8 toolchain used for best stability
Always using latest Initramfs
Always based on latest Galaxy S5 sm-g900f kernel sources by CM
Kernel runs with SELinux enforcing by default, just as CM12 stock kernel for S5 - but can be configured to work in permissive mode in Boeffla-Config settings
Note: I do NOT upstream the kernel to higher Linux kernel versions anymore as this usually has zero benefit but likely introduces new issues + is a waste of effort in the end
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 Galaxy S5 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 correct kernel depending on whether you are on Samsung Stock, CM12 or CM11 !!!
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.1.72 or higher for the Galaxy S5 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
* Yank555
* ktoonsez
* Hardcore
* Chainfire
* AndreiLux
* Netarchy
* Gokhanmoral
* Entropy512
* Faux
* Ak
... 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 logs:
LineageOS 14.1
http://kernel.boeffla.de/sgs5/boeffla-kernel-cm/cm14.0/changelog.htm
CM13.0
http://kernel.boeffla.de/sgs5/boeffla-kernel-cm/cm13.0/changelog.htm
Configuration and profile thread
http://forum.xda-developers.com/galaxy-s5/general/unofficial-boeffla-kernel-profile-t3139530
*** 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
Hi all,
Great kernel
Works very fine
Check this out..
Thanxxxx to the Lord for the hard work in the last week's
Now i love my S5 G900F
[emoji7]
Ive installed on Teamsek CM12 v9.0 and geting self reboot ...
Im waiting for new ver. Always big fan of your krenels
gravis_jg said:
Ive installed on Teamsek CM12 v9.0 and geting self reboot ...
Im waiting for new ver. Always big fan of your krenels
Click to expand...
Click to collapse
Cannot comment for Temasek, as written.. it is for official CM12. And it is only tested by me with official CM12.
If it runs with Temasek - fine. If not, you need to search why it reboots for you. Then Temasek seems not 100% compatible.
Andi
Flashed fine on AICP.
Only heard good things about your kernel!
superleeds27 said:
Flashed fine on AICP.
Only heard good things about your kernel!
Click to expand...
Click to collapse
Thanks.
But also let's be realistic. It is version 1.0-beta1. So for sure some more way to go
Andi
@Lord Boeffla
Hi Andi, a big neverending thanks for providing us with an S5 (G900F/klte) kernel.
Coming from my i9300 which ran the whole time with your wellknown and imho best kernel for the i9300 I am familiar with your fine app and highly appreciate your new work for the S5.
And btw: Due to so far not working TRDS for LP/cm12 I still run kitkat for s5 (same with my i9300) using FusionRom which is mostly based on cm11.
Now with Boeffla-cm11 for G900F based on FusionRom 4.4.4 I feel happy again - fast-stable-easy to handle 1A+++
gravis_jg said:
Ive installed on Teamsek CM12 v9.0 and geting self reboot ...
Im waiting for new ver. Always big fan of your krenels
Click to expand...
Click to collapse
Quick question: Are you coming from another custom kernel?
It might be, some cleanup work is required first.
Just had a user that came from KT kernel and he had to deinstall the two KT apps manually, wipe dalvik and cache. Then it started working.
Andi
CM12 kernel seems to work fine on bliss-pop. At least so far. ?
vulfgar said:
CM12 kernel seems to work fine on bliss-pop. At least so far. ?
Click to expand...
Click to collapse
Fingers crossed it will stay like that
Andi
Lord Boeffla said:
Fingers crossed it will stay like that
Andi
Click to expand...
Click to collapse
Me too. If not I'll have to change rom.
Lord Boeffla said:
Fingers crossed it will stay like that
Andi
Click to expand...
Click to collapse
Just to be tested, my friend thanks for everything
Lord Boeffla said:
Quick question: Are you coming from another custom kernel?
It might be, some cleanup work is required first.
Just had a user that came from KT kernel and he had to deinstall the two KT apps manually, wipe dalvik and cache. Then it started working.
Andi
Click to expand...
Click to collapse
I was the user
You must delete in root/system/app/com.ktoonsez.KTmonitor.apk and com.ktoonsez.KTweaker.apk.
Additionally, in Int SDcard the KTKernel Folder with profiles and scripts.
First, install the Boeffla Config, then go into recovery and flash the kernel. Wipe cash and Dalvik and reboot.
For Viper4android user, first deactivate Viper4Android or use the Beoffla Kernel without Boeffla sound settings.
Sorry for my bad English, with this kernel for lollipop tw viper4android work or not? Now i have flashed this kernel and boeffla apk
gravis_jg said:
Ive installed on Teamsek CM12 v9.0 and geting self reboot ...
Im waiting for new ver. Always big fan of your krenels
Click to expand...
Click to collapse
Hi, I've tested the kernel on Temasek and on a few different Rome.
Bliss Pop Rome, Fusion, Darko ... CM12 unofficial
It's like Horsti G says everything must be deleted from the kernel KT otherwise there are problems. but I have only the KT monitor at run without problems
Especially on the Temasek Rome had 2 people tested the kernel for quite some time without any problems.
Unfortunately the support for other roms is not possible because there are always errors and differences with other roms.
a Idde would make a thread for all other roms. since one could then afford support?
@ cranio84
For Viper4android user, first deactivate Viper4Android or use the Beoffla Kernel without Boeffla sound settings.
sorry for the translation with the googel translator
kind regards
Jakkomo 77
Ok i deactive boeffla sound setting, but where is a guide to install viper4android, because I have tried with more kernel on tw rom and don't work
For sure there are specialised threads for viper4android.
But wrong in this thread to discuss that...
Andi
Ok, i discute un this 3d because your kernel is correlate for me

Categories

Resources