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

[i.am.newbie]

@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....

 

[ZaneZam]

@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]

@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

 

[i.am.newbie]

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]

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]

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

 

[Beatray]

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]

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]

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.

 

[sak0071]

Hi Lord Boeffla kernel cm 13 i9300 support F2FS?
Thankyou

 

[andip71]

Hi Lord Boeffla kernel cm 13 i9300 support F2FS?
Thankyou

No, of course not. I hate the F2FS crap.

https://forum.xda-developers.com/showpost.php?p=70498097&postcount=89

Andi

 

[GrayJack]

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]

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

 

[GrayJack]

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.

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?

 

[andip71]

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]

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]

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

 

[funkenwerner]

Nope.

Sorry
Andi

it was in my Head and found it in another Forum, old Thread
( in deutsch: Das Internet vergisst nie da kannst nix ändern )
OK Thanks