• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[EOL] [KERNEL] [I9300] [Samsung JB] Boeffla-Kernel 5.11/6.9/7.9 (23-10-2015)

Status
Not open for further replies.
Search This thread

i.am.newbie

Senior Member
Jun 9, 2015
157
8
@nik60
As you can see in the screenshot,
last time the cm10.1 developer had built a cm10.1 rom with downgraded mali driver from r3pX to r2p4 with smoother user experience but memory leak.
I have tried to replace all libs in egl folder and libMali.so(s3 lte 4.4.4 rom port) with s3 android 4.0.4 libs but after splash screen my phone ended up with black screen.
So I am curious about driver downgrade only works in cyanogenmod or needs to replace more libs or....
This is because I have flashed paranoid rom(android 4.1.1) with r2p4 mali driver and it booted properly with siyah kernel 1.5.3(android ics kernel) but samsung 4.1.1 leak rom XXDLH8 mali r2p4 driver ended up with black screen.
So, I think you can understand what am I saying haha....
 

Attachments

  • Screenshot_2017-06-07-21-35-15.png
    Screenshot_2017-06-07-21-35-15.png
    109.8 KB · Views: 1,352

ZaneZam

Recognized Contributor
Dec 6, 2010
3,398
16,820
@nik60
As you can see in the screenshot,
last time the cm10.1 developer had built a cm10.1 rom with downgraded mali driver from r3pX to r2p4 with smoother user experience but memory leak.
I have tried to replace all libs in egl folder and libMali.so(s3 lte 4.4.4 rom port) with s3 android 4.0.4 libs but after splash screen my phone ended up with black screen.
So I am curious about driver downgrade only works in cyanogenmod or needs to replace more libs or....
This is because I have flashed paranoid rom(android 4.1.1) with r2p4 mali driver and it booted properly with siyah kernel 1.5.3(android ics kernel) but samsung 4.1.1 leak rom XXDLH8 mali r2p4 driver ended up with black screen.
So, I think you can understand what am I saying haha....

this black screen situation is because a specific driver version does only work with a specific library version from the rom so u have to have the exact combination. the driver is checking what is used and blacks out if it doesn't match. but there were api hacks back then i remember to put that in for my Note 8 https://github.com/zanezam/boeffla-...mmit/49daa638dc7588b0160160411096deb3cef7c791
but anyway no one knows what happens if u are too far away with compatibility so take the commit message caution in braces seriously. they put that checks in for a good reason obviously ;)
 

nik60

Senior Member
Jun 24, 2012
2,432
2,706
arona
@nik60
As you can see in the screenshot,
last time the cm10.1 developer had built a cm10.1 rom with downgraded mali driver from r3pX to r2p4 with smoother user experience but memory leak.
I have tried to replace all libs in egl folder and libMali.so(s3 lte 4.4.4 rom port) with s3 android 4.0.4 libs but after splash screen my phone ended up with black screen.
So I am curious about driver downgrade only works in cyanogenmod or needs to replace more libs or....
This is because I have flashed paranoid rom(android 4.1.1) with r2p4 mali driver and it booted properly with siyah kernel 1.5.3(android ics kernel) but samsung 4.1.1 leak rom XXDLH8 mali r2p4 driver ended up with black screen.
So, I think you can understand what am I saying haha....
Hi
First..cyano rom and Sammy is different
Need appropriate kernel with mali driver that you have
You replace lib Mali. So and egl? OK
But after need Flash boeffla kernel 6.9
You should know which Mali driver have your rom
If you have something wrong ...your device not boot..only black screen
About Sammy. ..
which rom and kernel have you?
Anyway. ...old Mali driver work with boeffla kernel 6.9
New Mali driver work with boeffla kernel 7.9
So you can flash my patch in recovery
Not reboot ...flash appropriate kernel
Nothing will be damaged...if you make a mistake
When you reflash kernel or lib
...phone boot as before..or restore nandroid

Example...( I don't understood ..your device?..S3 Lte?..It is i9305...not i9300)
1 if you are in 4.4.4 port ...and you want old driver
2 reboot to recovery
3 flash my patch "return to 6.9 boeffla(have old Mali inside)
4 flash boeffla kernel 6.9 that have old Mali driver support
I THINK THERE ISNT ANY DIFFERENCE IF YOU CHANGE MALI DRIVER....
Ps
Many years ago. .I made rom modified for dual boot ...first rom Sammy. .second rom cyano
For dual boot with the same kernel logically need change mali lib
Because are different..in cyano we have new mali

Sent from my SM-G925F using XDA Labs
 
Last edited:

i.am.newbie

Senior Member
Jun 9, 2015
157
8
no i mean paranoid android 4.1.1 with siyah 1.5.3 ics kernel booted properly but samsung jb 4.1.1 leak with siyah 1.5.3 ics kernel ended up with black screen
both rom are using r2p4 mali driver
and the cm10.1 rom can downgrade mali driver from r3pX to r2p4 but s3 lte i9305 kitkat rom for s3 i9300 after i replace egl libs and libMali.so my phone also ended up with black screen.
Why cm10.1 can downgrade mali driver but s3 lte 4.4.4 rom port for s3 i9300 cannot?
Another question: Does android kernel works on any android version? This is because siyah 1.5.3 ics kernel works with paranoid jb 4.1.1 so i also flash this kernel on s3 lte kitkat rom for i9300 but ended up with black screen :(
 

andip71

Recognized Developer
Apr 22, 2008
17,095
67,644
Potsdam
Another question: Does android kernel works on any android version? This is because siyah 1.5.3 ics kernel works with paranoid jb 4.1.1 so i also flash this kernel on s3 lte kitkat rom for i9300 but ended up with black screen :(

No, the kernel is usually strongly changed for every Android version.
Even if it seems to run, many things (also in the background) can be broken and can lead to all sort of weird side effects.

Andi
 

nik60

Senior Member
Jun 24, 2012
2,432
2,706
arona
no i mean paranoid android 4.1.1 with siyah 1.5.3 ics kernel booted properly but samsung jb 4.1.1 leak with siyah 1.5.3 ics kernel ended up with black screen
both rom are using r2p4 mali driver
and the cm10.1 rom can downgrade mali driver from r3pX to r2p4 but s3 lte i9305 kitkat rom for s3 i9300 after i replace egl libs and libMali.so my phone also ended up with black screen.
Why cm10.1 can downgrade mali driver but s3 lte 4.4.4 rom port for s3 i9300 cannot?
Another question: Does android kernel works on any android version? This is because siyah 1.5.3 ics kernel works with paranoid jb 4.1.1 so i also flash this kernel on s3 lte kitkat rom for i9300 but ended up with black screen :(
Hi
You can see that rom from i9305 to i9300 4.4.4 port is my rom
I tried many time change mali driver and it work
How i said ...if you use old Mali on s3 i9300 4.4.4 port ....need boeffla 6.9

Anyway latest version siyah kernel by gokhanmoral is 1.9.1..
Have support samsung jelly bean and CM 10.1
With support dual boot
2.if i remember firmware leak samsung is 4.2.2

look changelog
◾tested only on Samsung 4.1.2 latest official ROM and CM-10.1 nightly (30/3/2013). Samsung 4.2 leaks are not supported. Also CM10 support is dropped as I don’t want to keep 3 different mali drivers in the kernel
http://www.gokhanmoral.com/

Sent from my SM-G925F using XDA Labs
 
Last edited:

Beatray

Member
Jul 1, 2012
29
3
Do you guys encounter problems with proximity sensor while using boeffla kernel? During call proximity sensor causes hang up. I have used it on different roms and still the same. Without boeffla kernel i have not noticed that issue.
 

andip71

Recognized Developer
Apr 22, 2008
17,095
67,644
Potsdam
Do you guys encounter problems with proximity sensor while using boeffla kernel? During call proximity sensor causes hang up. I have used it on different roms and still the same. Without boeffla kernel i have not noticed that issue.

Maybe others can comment on that.
I think I have not used my S3 anymore for calling for more than 3 years...
But I would be surprised if that would be a general issue as this for sure would have been reported already.
At least when I still used it last time, I had no such issues with latest kernel (but on official Samsung roms, nothing else).

Let's see.

Andi
 

ExTrEmEe

Senior Member
Oct 22, 2014
507
247
Novi Sad
Do you guys encounter problems with proximity sensor while using boeffla kernel? During call proximity sensor causes hang up. I have used it on different roms and still the same. Without boeffla kernel i have not noticed that issue.

I'm using this kernel since it got support for back to n00t rom, so 2-3 years, and now v7.9 with Blekota Note4 ROM. Never had that problem. And i'm really supprised how good 5 years old phone is keeping up with latest apps, running just fine. Also, i still have original battery, that came with phone and im getting around 3 hours of screen on time, without any modifications, with standard pegasusq preset.
 
Last edited:
  • Like
Reactions: andip71

GrayJack

Senior Member
Sep 16, 2012
521
207
Silent Hill
Is there any way to disable automatic busybox installation at /sbin?
I have newer 1.27.1 version in /system/xbin and I don't want to see outdated 1.23.2 that appears with every reboot.
 

andip71

Recognized Developer
Apr 22, 2008
17,095
67,644
Potsdam
Is there any way to disable automatic busybox installation at /sbin?
I have newer 1.27.1 version in /system/xbin and I don't want to see outdated 1.23.2 that appears with every reboot.

No, this is elementar part of my kernel.

You can, by a script, delete busybox from /sbin after start. However this would probably mean some things in my kernel do not work properly anymore. So I do not advice it.

As this kernel is EOL for ages, I do not have another solution for you.
People still using such an old rom have to live with the busybox that was state-of-the art during that time.

Sorry
Andi
 

andip71

Recognized Developer
Apr 22, 2008
17,095
67,644
Potsdam
What is newer version will be properly installed in /system/xbin?
Will the kernel find it and use it normally?
Or /sbin path is hardcoded?

Nowadays with modern kernels it would work (as long as the busybox has all required features compiled in, which is not always the case and the reason I bring an onwn busybox).

But for such an old kernel, I cannot guarantee. You can try. The busybox shows up anyways after every start again in /sbin. So you can delete it and check if all is fine.
But you need to script it to remove it after every boot again.

Andi
 

funkenwerner

Member
Apr 28, 2016
6
4
hello

sorry my english is bad, very little

i seek this ( ich suche diese Einstellung) "Kernel vor Rom Flash schützen" ( i dont no in english)

please help, is that never in Config app?
 

andip71

Recognized Developer
Apr 22, 2008
17,095
67,644
Potsdam
hello

sorry my english is bad, very little

i seek this ( ich suche diese Einstellung) "Kernel vor Rom Flash schützen" ( i dont no in english)

please help, is that never in Config app?

Nope. It is not in the config app anymore, as this setting technically does not work with a kernel that uses anykernel concept.

To be a bit more technical:
In the anykernel world, flashing a custom kernel reuses part of the currently installed stock kernel.
If now we prevent the stock kernel to be installed with a rom update, the custom kernel would never get refreshed by new stock kernel parts.

So I had to remove this for all kernels using anykernel. And also latest Samsung Kernel is using anykernel.

Where did you read about the setting? I would like to correct it and take it out or put a note in, explaining this is not possible with anykernel.

Sorry
Andi
 
  • Like
Reactions: MysteryIII
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 638
    *** NOTE: All kernels are now officially end-of-life (EOL).
    Please do not expect any more updates for them in future, no maintenance and no bugfixing. ***


    Hi all,

    this is the thread about the well-known Boeffla-Kernel for the Samsung Galaxy S3 international.

    Compatibility

    Important: This kernel is only meant to be compatible with official Samsung Stock firmware 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 !!



    Notes:
    Never install it on CM or AOSP based roms!!!

    • Kernel version 5.x are only for Samsung based Jelly Bean 4.3.x roms!!!

    • Kernel version 6.x is only for ported Samsung based Kitkat 4.4.2 roms (e.g. Archiport) !!!

    • Kernel version 7.x is only for ported Samsung based Kitkat 4.4.4 roms (e.g. back-to-n00t) !!!

    • Kernel versions 1-4 are only for Samsung based Jelly Bean 4.1.x roms!!! (no development anymore)

    For the CM Boeffla-Kernel, please go HERE.

    If you have questions to settings, presets, others configuration and wanna share your configuration, head over to the unofficial Boeffla-Config App Config sharing thread:
    http://forum.xda-developers.com/showthread.php?t=2621308

    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.


    Change logs

    (you can also access them directly in Boeffla-Config V2 by pressing menu and selecting "change log...")

    Change log for Android 4.3 kernels: KLICK HERE
    Change log for Android 4.4.2 kernels: KLICK HERE
    Change log for Android 4.4.4 kernels: KLICK HERE


    Features

    * To tweak and configure the kernel, manually load and install the app "Boeffla-Config V2" from here: DOWNLOAD
    * Upstreamed to Linux 3.0.101 (www.kernel.org)
    * Based on Samsung source code GT-I9300_JB_Opensource_Update13
    * Initramfs from xxugml2 kernel
    * CPU "soft" overclocking to 1500 or 1600 MHz
    * CPU undervolting interface
    * GPU frequencies configurable (underclocking, overclocking up to 700 MHz)
    * GPU voltages configurable (undervolting, overvolting)
    * Configurable zRam (Turbo zRam with up to 4 devices)
    * Configurable touch-to-wake
    * Configurable touch boost frequency
    * Configurable early suspend time (for screen off animations, 100ms default)
    * Configurable LED for fading mode, speed and brightness
    * Configurable charger rate for AC, USB and wireless (default increased to 1100 mA for ac charging)
    * Charging logic supports ignore unstable power and remove safety margin
    * Charge information display support via Boeffla-Config V2 app
    * Boeffla-Sound engine V1.6.5 to unleash the power of the Galaxy S3 audio chip
    * Additional governors: zzmoove 0.7d, pegasusqplus, smartassv2 and lulzactiveq
    * Governor profiles for pegasusq, pegasusqplus and zzmoove for performance, battery saving etc.
    * Additional schedulers: ROW, ZEN, BFQ (v6r2) and SIO
    * Schedulers configurable separate for internal and external SD memory
    * Hardcore speedmod sharpness fix implemented (default is off)
    * Black crush fix for better balanced display
    * SD card read ahead buffer configurable separate for internal and external SD memory (default increased to 256 kB)
    * Ext4 File system tweaks (default to on, can be disabled)
    * System Tweaks predefined supported (default is off, new Mattiadj tweak set included)
    * WIFI Multicast filter for better battery life
    * WIFI wakelock times reduction
    * Proportional rate reduction for TCP
    * TCP congestion changed from Cubic to Westwood
    * Wifi mac address change support
    * Dynamic fsync 1.2 implemented
    * Timeout for external SD card changed to improve handling of crappy SD cards
    * Custom boot animation support
    * Swap supported (but not recommended, use zRam instead)
    * init.d support (in /system/etc/init.d - set correct permissions!)
    * exFat opensource (Samsung OSRC) instead of proprietory modules
    * NTFS (read-only access only!) compiled as a module
    * CIFS compiled as a module
    * NFS compiled as a module
    * XBox controller support as module
    * exFat support switchable (switch it off if you do not need it)
    * Battery monitor wakelocks reduced
    * Kernel can root if required (create file "autoroot" on internal sd and reboot)
    * Android logger can be disabled
    * Kernel logger can be disabled
    * Disabled various debug logs and traces
    * Frandom compiled as a module (for mods like Crossbreeder)
    * Triangle away supported
    * Automatic EFS backup to external (priority) or internal SD Card (fallback) - now compatible with tools like kTool
    * Kernel initialisation log file (with history of 3 log files)
    * Exynos vulnerability and sudden dead issue fixed
    * Emergency reset script automatically placed into /boeffla-kernel-data folder of your internal memory
    * Compatibility to common standard apps (Voltage Control, SetCPU, System tuner etc.)
    * EFS V1 modem supported (also on Android 4.3)
    * Compiled with Google arm 4.7 toolchain
    * Internal kernel busybox version 1.21.1

    Download

    For all information and downloads (stable AND testing versions), visit the Boeffla-Kernel homepage:
    www.boeffla.de


    History

    Basically I created Boeffla-Kernel 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. 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 !!!

    This said, I will definitely NEVER implement:

    • dual boot (I do not need it)
    • color "calibration" (I do not like it, but I like the crispy stock colours)
    • real hard overclocking higher than 1600 MHz as this is outside of Exynos specs
    • f2fs - it is known to cause various issues and compatibility problems
    • anything that requires upstreaming of kernel parts to a higher kernel major version
    So do not even ask for it. Everything else I am happy to check and decide.

    Compatibility

    To reiterate it again: This kernel is only for Samsung based Jelly Bean (Android 4.1.x) firmwares. It is not designed to run on AOSP based roms!


    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.


    Donation

    If you like my work, feel free to donate: Donation-Link

    You will receive a personal donation code which unlocks some nice 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:

    * Yank555
    * ZaneZam
    * Hardcore
    * Chainfire
    * Harunjo
    * AndreiLux
    * Netarchy
    * Gokhanmoral
    * Simone201
    * Supercurio
    * Mialwe
    * Entropy512
    * Faux

    ... 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 CWM recovery and safely store your personal data before you flash a new kernel.


    Cheers and enjoy
    Andi
    89
    reserved1

    --- reserved for future usage ---
    73
    reserved2

    --- reserved for future usage 2 ---
    56
    Away...

    Ladies and Gents,

    I will say good-bye to you for the next few days. We are travelling for our new year's eve party tomorrow and will return on Thursday throughout the day.

    But I wish a happy new year 2014 to everyone. Let's see what it brings for the Android world.

    CU soon
    Andi
    53
    Final round up

    Hi guys,

    also a final round for my S3 Samsung kernels today, which are now considered final.

    Change log is the same for the Samsung JB 4.3, Kitkat 4.4.2 (Archiport) and KitKat 4.4.4 (back-to-n00t).

    Samsung 4.3 -- Version 5.9 stable -- Final
    Samsung 4.4.2 -- Version 6.7 stable -- Final
    Samsung 4.4.4 -- Version 7.7 stable -- Final
    13.08.2015

    • zzmoove governor updated to version 1.0-beta8 - bugfix and cleanup release (credits to ZaneZam)
    • zzmoove governor profile "relax" added (aiming to avoid audio stutters during screen off)
    • TCP optimisation (initial TCP window size)
    • Enabled a bunch additional tcp congestion algorithms that can be selected in Boeffla-Config app (click here and here for more information)
    • Support for latest Boeffla-Config apps to have a better stock settings determination
    • Kernel build process now able to use ccache
    • Internal build script enhancements
    • Internal async kernel start script reverted back to previous approach
    • Replaced kernel-internal busybox by a new version

    Have fun (hopefully)
    Andi