[KERNEL] [DEV] [P31xx] AA-ANYKERNEL- fix the Android 4.4.x drain

AA-ANYKERNEL

Why another Kernel?
A lot of user faced a high Battery-Drain since Android 4.4.x.
It is hard to find the cause of the Problem, because it does not happen to everyone.
The problem seems to be related to the merged commit "apply P3110 JB Update1 from opensource.samsung.com" on our kernel source wich didn´t made Problems before Android 4.4.x.

Who is working on this Kernel?
Since i am still somehow a "Newbie" and don´t understand everything i am not able to sperate the Source of Problem. Our wonderfull Kernel-Dev @ketut.kumajaya is answering my qustions if i run in some trubble.

Why a own Thread for this kernel?
You must know, most of our Roms are using the CM-11.0 Kernel for their Roms - means: a lot of Roms are affected, even if it does not happen to every user. Solveing the issue does not only help fixing CM, also a lot of other Roms wich should be in interest of every user.

Kernel-Source
https://github.com/slimroms/kernel_samsung_espresso10

About the Process:
I took our SlimKat Kernel as base:
1. Applyed the JB Update 1 commit from @ketut.kumajaya
I went back to 3.0.31 kernel and applyed JB Update 1 in 3 parts instead 1 for better changes tracking.
At least i did the upstream from 3.0.31 to 3.0.101 again and added back all other changes wich got applyed on our 3.0.101 kernel before.

@tuxafgmur made huge commit to solve the drain, it was to big to get it merged.
So i made a diff between his changes - 500.000 lines diff - lol.
I worked many days on it to get out the original commits from the diff and found most of them.

So we know JB Update 1 seems to be the source of problem, now lets go ahead:

2. revert some parts from JB Update 1
Only Partially reverted:
arch/arm/mach-omap2/cpuidle44xx.c: (partially) revert JB Update 1 and partially apply "Fix configs & missing log options" from DhollmenKernel by Tuxafgmur
drivers/net/wireless/bcmdhd/dhd_sec_feature.h: partially revert JB Update 1/3

3. Add back missing parts from Upstream 3.0.38 -> 3.0.39

4. some different changes, i´ll list the some times later

DOWNLOAD

XDA:DevDB Information
[P31xx] AA-ANYKERNEL, Kernel for the Samsung Galaxy Tab 2

Contributors
Android-Andi, ketut.kumajaya
Kernel Special Features:

Version Information
Status: Beta

Created 2014-06-29
Last Updated 2014-07-27

Reserved

DOWNLOADS

Vendor-Blobs-update1.zip
(please flash the vendor-blobs DIRECTLY after the kernel)

For SlimKat:
GT-P31XX-Slim-3.0.101-test2.zip

For CyanogenMod 11:
GT-P31XX-CM-3.0.101-test2.zip
(forgot to upload test2 kernel, will do in the evening)

For OmniROM:
GT-P31XX-Omni-3.0.101-test2.zip

For those who don't like Development but need a stable Kernel for Android 4.4 Custom Roms

3.0.101 Kernel based on latest SlimKat Kernel Source for Tab 2
- Xpad support (build as module)
- Boeffla Soundcontroll supported
- DriveDroid Support (host ISO/IMG files to boot your PC from)
- Kernel exFAT (1.2.7)
- LZO compressed Ramdisk
- updated LZO compression
- ZIP contains all needed proprietary vendor files.

-NO FEEDBACK NEEDED-
https://www.androidfilehost.com/?fid=23622183712468548



Online note for myself:
Added
to "export BOOTCLASSPATH" inside "init.environ.rc" to get support for Pac and MoKee.

Tsjoklat said:

I would still include any new dependencies from upstream that are required by the code updates and document the reason why. Not everything new from upstream should be needed

Click to expand...

Click to collapse

I will work on it, but maybe there is a better way, i have seen on sammobile.com samsung released more 4.2.2 updates until July! That means: our kernel-source meight be outdated.


We can fix some bugs like poor battery life and maybe some more, but only with your help - the XDA-Community!

These bugs are caused by OS kernel which is not up-to-date with stock ROM’s and Samsung is refusing to update it. Our previous requests have been ignored by them, and the point is that Samsung have to update it, they are just forced by law and licensing terms of Linux, however they just don’t want to do this because of some unknown reason.

I think that the only way to get an updated source code is to… Show the power of our community and spam them with request messages. That’s the only way to fix Tab 2 bugs wich are still present.
S3 mini and Ace 2 community have done this before with a great success, so we can do this too! It only took 2 or 3 days until Samsung updated the S3 mini kernel source!

It’s a nasty way, but it’s the only thing we can do as a community, because previous requests have been ignored.

I'd be very pleased if you want to help. It’s easy, just send them the message provided below:


Contact form: http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView

Inquiry type: Request for Source Codes

Sample message:

I’d like to request the most recent Linux kernel source code for the whole Samsung Galaxy Tab 2 Family (P3100, P3110, P3113, P5100, P5110 and P5113). Source code already available on Samsung Opensource is outdated and not up-to-date with Samsung internal source code, which can be proved.

According to GNU GPL license you are obliged to publish any source code you had changed in Linux kernel, and you are violating law by not publishing it.

Please, stop pretending that current kernel is up-to-date and just update it. Community have had enough waiting for you to even answer to our requests.

Click to expand...

Click to collapse