[FTF] Sony Xperia Z Lollipop Release

Sony rolled out a Lollipop update for Xperia Z just yesterday. If you still haven’t gotten … more

Original Moto G Receives Lollipop, OTA Captured

The original Moto G was released almost two years ago. Motorola still continues to … more

Device Review: No.1 X1 Rugged Smartphone

We are almost at the end of Q2 for 2015, and we have seen most of the flagship phones for the … more

When a Friend or Family Member Asks for a Phone Recommendation, What Do You Tell Them?

The majority of us here at XDA would consider … more
Post Reply Subscribe to Thread Email Thread

Delay when answering/placing calls post 4.3

14th February 2014, 06:39 PM |#31  
decimalman's Avatar
Senior Member
Thanks Meter: 3,290
Donate to Me
Originally Posted by metalfan78

So what you're basically saying is that Samsung screwed the pooch?

Not at all. I'm saying that Samsung is playing fast and loose with the GPL. The MK3 kernel source contains any number of tricks to keep it from building correctly unless Samsung is building it themselves. Without patching it, exFAT support is (silently) skipped, the a2220 driver uses AT&T's firmware instead of Sprint's, and there's likely a few more bugs affecting the a2220 and video drivers (and possibly others as well).

EDIT: To clarify, some of the source code uses magic #define macros and directory layouts in order to change how it's built. Without being built by Samsung's build tree, that magic is missing and the resulting kernel isn't functionally equivalent to the kernel Samsung provided. GPLv2 doesn't explicitly forbid this, so they're technically compliant.
Last edited by decimalman; 14th February 2014 at 06:47 PM.
The Following 2 Users Say Thank You to decimalman For This Useful Post: [ View ]
14th February 2014, 08:06 PM |#32  
metalfan78's Avatar
Senior Member
Flag Lakewood, CO
Thanks Meter: 2,003
14th February 2014, 08:19 PM |#33  
CNexus's Avatar
Recognized Contributor
Flag ~/android
Thanks Meter: 13,828
Donate to Me
Yup, what he said could not be more spot on...

For example, take a look at my commit here:

That line that I removed was originally only pulling in exfat if some folder way up in Samsung build tree exists. And so, since we don't have the same build setup as Samsung, exfat gets skipped unless you remove that
The Following 2 Users Say Thank You to CNexus For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes