[BOUNTY] Custom kernel SM-G935F/FD

Status
Not open for further replies.

Neemac

Senior Member
Sep 6, 2012
108
87
0
Bergen
Okay. So apparently Samsung have made some changes to the kernel in S7 compared to other Samsung's.

In order to make the kernel boot, you have too disable tima_rkp. But disabling tima_rkp makes the kernel unstable.
We can make the Kenrel stabel, by disabling the FP lock. But then again. A very used feature of the phone is useless :(

I figured out by putting out a bounty, maybe some developers are willing too have a look at it, and see if it's a way too make this work. Currently Samsung have 4 kernel sources out here




Anyway. Don't let me disturb you any more, and let's start this bounty tread.

I'll start with pledging $50 for the one who can make a stable custom kernel for our beloved S7 edge. (935F/fd)
Please notice, there is no minimum pledge. You are free to pledge what ever amount you want too.

Current status : $396 bounty
 
Last edited:

lost_

Senior Member
Jan 29, 2010
949
491
0
DC
USD 75

I'm an S7 930F user, but Edge 935F development is more active, and there is little to no difference anyway. I'm sure , if needed, it can be recompiled for 930F.
 
  • Like
Reactions: Okarina26
F

Faspaiso

Guest
Out of curiosity, why is a bounty needed for making a custom kernel for the S7? The rom development was quite active on the S6, so why is it so "dead" at least from a kernel perspective here? I mean, is a custom kernel just not happening for the S7 or will we set some in the near future?
 

Neemac

Senior Member
Sep 6, 2012
108
87
0
Bergen
Out of curiosity, why is a bounty needed for making a custom kernel for the S7? The rom development was quite active on the S6, so why is it so "dead" at least from a kernel perspective here? I mean, is a custom kernel just not happening for the S7 or will we set some in the near future?
As its my understanding, the major problem with a custom kernel, is the implementation of tima_rkp, Samsung have been using on this kernel. Just in order too have the kernel boot, you have to disable it, but then again, you will have a unstable kernel. It can be some stable, if you don't use any hard-coded security features, like fingerprint unlock and so on.

Swipe to wake works, with very few too none reboots. But still it isn't stable.

That's why it's a little bounty out, too trigger the willingness of other developers too take some of their free time and have a look at it.

As you prob noticed, there isn't any custom kernel out yet, tho the S6 hade a few kernels out just a week after release.
 

dave7802

Senior Member
Jan 23, 2007
1,041
510
143
Liverpool
Out of curiosity, why is a bounty needed for making a custom kernel for the S7? The rom development was quite active on the S6, so why is it so "dead" at least from a kernel perspective here? I mean, is a custom kernel just not happening for the S7 or will we set some in the near future?
To make it simple, its as simple as
Open Source
and No Source.

exynos = closed source (Making development very difficult)
Snapdragon = Open Source (Everyone can have a go)

I can only assume the S6 had both a Snapdragon and exynos variant and the exynos being less popular
 

NonXtreme

Senior Member
Oct 23, 2013
388
152
0
To make it simple, its as simple as
Open Source
and No Source.

exynos = closed source (Making development very difficult)
Snapdragon = Open Source (Everyone can have a go)

I can only assume the S6 had both a Snapdragon and exynos variant and the exynos being less popular
Nope
Samsung's already release KERNEL source for exynos S7 or else this thread won't even exist.
This thread is here because of the new change samsung had made to S7 kernel (mostly security stuff) make modifying the kernel without too much trouble hard
Also S6 had only Exynos version because of the underperforming sd810.

Sent from my SM-G935F using Tapatalk
 
  • Like
Reactions: lost_
F

Faspaiso

Guest
To make it simple, its as simple as
Open Source
and No Source.

exynos = closed source (Making development very difficult)
Snapdragon = Open Source (Everyone can have a go)

I can only assume the S6 had both a Snapdragon and exynos variant and the exynos being less popular
That's only for custom roms, which is the reason we *might* never see a stable AOSP Rom. There are sources out for the kernel.
 

dave7802

Senior Member
Jan 23, 2007
1,041
510
143
Liverpool
Bla cba with the response, I was more down the lines of AOSP
as i dont see any other real benefit to a custom kernel.

Its not like the S7 suffers from Lag / Performance issues or battery draining.

(My original replay was much longer going into detail, stupid page timeout)
 

pigmich

Senior Member
May 15, 2011
294
88
0
To make it simple, its as simple as
Open Source
and No Source.

exynos = closed source (Making development very difficult)
Snapdragon = Open Source (Everyone can have a go)

I can only assume the S6 had both a Snapdragon and exynos variant and the exynos being less popular
s7/ s7edge also got its own Snapdragon Version
 

Beefheart

Senior Member
Dec 5, 2007
4,331
1,215
0
England
Bla cba with the response, I was more down the lines of AOSP
as i dont see any other real benefit to a custom kernel.

Its not like the S7 suffers from Lag / Performance issues or battery draining.
Indeed. The main reason for a custom kernel for me has always been for permissive, which V4A requires to work. But there is now a work around for this on enforcing kernels so I'm really not that bothered. It's not as if Exynos S7/S7E devices suffer from battery life issues or overheat problems which underclocking and/or undervolting could fix. It works very well as is, I get between 6 and 7 hours SOT on average and it's very stable in all other departments. In short, the need for a custom kernel has greatly diminished on this device, especially in comparison to the S6/S6E/S6E+ which all had terrible battery life. But if it's important to some people then good luck in getting one sorted.
 
Last edited:

jesec

Inactive Recognized Developer / Inactive Recognize
Jan 29, 2015
804
6,170
133
SF Bay Area
Here are the temporary solutions.

Way A:
Remove /system/lib/libbauth* , /system/lib64/libbauth*

Way B: (If you want to completely disable (or bypass) TEE)
Remove /system/lib/libbauth* , /system/lib64/libbauth*
Replace /system/lib64/hw/gatekeeper.exynos8890.so,/system/lib64/hw/keystore.exynos8890.so with these i uploaded.

Both of them will make your FP Sensor not working.
(Lock Screen will work)

But,at least,you get a stable custom kernel.

I am trying to re-implement FP sensor support to system with TEE disabled.
Here is some files from somewhere confidential and a simple kernel compiled by me and my build.prop.
 

Attachments

Last edited:
Status
Not open for further replies.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone