[KERNEL] - [Backslash-1.3 KG1] - with [CF-Root v4.1] Initramfs

[saturn_de]

This is a self compiled Kernel from these sources. It's a fork of the kernel source git plus some performance tweaks and minus a bad patch, which turned out to drain the battery.

The initramfs (source) is a modified CF-Root v4.1 of the KG1.
I added some /proc and /sys tweaks in init.rc (github of the initramfs):

+    write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ondemand
+    write /sys/block/mmcblk0/queue/scheduler noop 
+    write /sys/block/mmcblk0/queue/read_ahead_kb 512
+    write /proc/sys/vm/highmem_is_dirtyable 1
+    write /proc/sys/vm/dirty_writeback_centisecs 1500
+    write /proc/sys/vm/laptop_mode 5

This probably works best with Villain ROM 2.0 [2.3.4] and the XXKG1 radio image.


History:

Version 1.1:

• added touchscreen fix suggested by vincenzo91.

Version 1.2 :

• now based on CF-Root 4.1 (was 4.0)
• cherry-pick'ed some fixes from cfs-exp branch of ninphetamine github
• removed "setprop dalvik.vm.execution-mode int:fast", which prevents JIT
• changed touchscreen MOVHYSTI to 5 from 0 (15 original)

Version 1.3 :

• removed bogus /sys, /proc settings
• use /init from KG1/CF-ROOT
• set readahead to 512kb
• enabled fuse, so you can use "ntfs-3g" to mount a NTFS drive
  
  There is also a variant with MOVHYSTI set to "0" (Backslash-1.3-HYST0). Let me know, if you have those touchscreen problems with either "0" (HYST0) or the "5" in the normal kernel.

So how does it look like? See the attached image (FastDormancy was not turned off, because it got better in 2.3.4)

Benchmark CF-Bench Pro v1.1
Interpretation left to the reader...

Stock CF-Root KG1:	      |	Backslash-1.3:
Native:	11256	11478	11172 |	11566	11360	11414
Java:	3155	3235    3071  |	3411	3240	3327
Overall:6395	6532	6311  |	6673	6488	6561

read: 	553	535	540   |	564	571	570
write: 	138	180	176   |	181	181	173

 

[Pume]

This is a self compiled Kernel from this sources. It's a fork of the kernel source git plus some performance tweaks and minus a bad patch, which turned out to drain the battery.

The initramfs is a modified CF-Root v4.0 of the XXKG1.
I added some /proc and /sys tweaks in init.rc.

This probably works best with Villain ROM 2.0 [2.3.4] and the KG1 radio image.

So how does it look like?

So does this also fix the push exchange email battery drain or just some other drain (non-existent to me)?

 

[szav]

This is a self compiled Kernel from this sources. It's a fork of the kernel source git plus some performance tweaks and minus a bad patch, which turned out to drain the battery.

The initramfs is a modified CF-Root v4.0 of the XXKG1.
I added some /proc and /sys tweaks in init.rc.

This probably works best with Villain ROM 2.0 [2.3.4] and the KG1 radio image.

So how does it look like?

This can fix the Android OS draining ?

 

[umair9001]

This can fix the Android OS draining ?

standby battery usage seems quite good, will try on cognition 1.11 and feedback..

 

[cescof]

Hy guys is it possibile have this kernel in a zip flashable version..
I haven' t my pc here but i need to try cause i want my phone for 24 hrs...a day...
Regards

 

[ante0]

Hy guys is it possibile have this kernel in a zip flashable version..
I haven' t my pc here but i need to try cause i want my phone for 24 hrs...a day...
Regards

Just flash in CWM. Open CWM and select Flash Kernel, then select this kernel. It will flash then reboot.

Testing it now. Lets hope it works
Btw, have you noticing it not obeying SetCPU?
In both CF-Root and a testkernel I tried then clock would go above the max I set. I had it set at 800 but it still went to 1ghz, 1.2ghz and 1.6ghz...

 

[saturn_de]

Just flash in CWM. Open CWM and select Flash Kernel, then select this kernel. It will flash then reboot.

Testing it now. Lets hope it works
Btw, have you noticing it not obeying SetCPU?
In both CF-Root and a testkernel I tried then clock would go above the max I set. I had it set at 800 but it still went to 1ghz, 1.2ghz and 1.6ghz...

Just don't use SetCPU... it's useless. "Race to idle" is the key. Don't be smarter than the kernel and add more load with an app.

 

[dr3minem]

Just flash in CWM. Open CWM and select Flash Kernel, then select this kernel. It will flash then reboot.

Testing it now. Lets hope it works
Btw, have you noticing it not obeying SetCPU?
In both CF-Root and a testkernel I tried then clock would go above the max I set. I had it set at 800 but it still went to 1ghz, 1.2ghz and 1.6ghz...

Really? Where did you check your real clock speed? In the Battery statistics in setCPU it tells me 0% for 1200 Mhz if i set it to 500-1000Mhz, using CF-Root for now.

@saturn_de: Isn't CF-Root 4.1 out? I have no idea whats changed but im one of those "the newer the better guys" even though i know thats not always true haha

EDIT: Ill stop using setCPU for today and see how it goes

 

[umair9001]

Just flash in CWM. Open CWM and select Flash Kernel, then select this kernel. It will flash then reboot.

Testing it now. Lets hope it works
Btw, have you noticing it not obeying SetCPU?
In both CF-Root and a testkernel I tried then clock would go above the max I set. I had it set at 800 but it still went to 1ghz, 1.2ghz and 1.6ghz...

it is not an overclocked kernel..and it obeys setcpu profiles..i am using them..

Removing setcpu as per saturn.. lets see..

 

[saturn_de]

@saturn_de: Isn't CF-Root 4.1 out? I have no idea whats changed but im one of those "the newer the better guys" even though i know thats not always true haha

I will have a look what changed in CF-Root 4.1 ...

 

[kalpik]

So anyone here can confirm/deny the battery drain fix?

 

[H377]

I cannot see any change yet. Just flashed KG1 and the kernel and the Android OS is still 20%.

We will see in a long-term.

Fingers crossed.

 

[Pume]

I cannot see any change yet. Just flashed KG1 and the kernel and the Android OS is still 20%.

We will see in a long-term.

Fingers crossed.

Email is still draining... Don't know about anything else as I haven't had any other processes / apps draining my power source aka battery.

 

[H377]

Email is still draining... Don't know about anything else as I haven't had any other processes / apps draining my power source aka battery.

I have Gmail and Exchange all set up to PUSH but I don't have a problem with them. Only the Android OS's battery usage is high.

 

[Pume]

I have Gmail and Exchange all set up to PUSH but I don't have a problem with them. Only the Android OS's battery usage is high.

If your awake bar is not blue when the screen is off then you don't have anything to worry about. Android OS percentage does not mean a thing if the phone stays asleep when it should.

 

[H377]

If your awake bar is not blue when the screen is off then you don't have anything to worry about. Android OS percentage does not mean a thing if the phone stays asleep when it should.

Thanks!

In fact after 12 or 14 hours I got 50% of the battery with normal usage. I don't know if it's normal or not but my HD2 and Desire also last almost the same.

I always had to charge them at night every day if I didn't want them to run of fuel during next business day.

 

[Nuja]

Hi,
can you tell us what tweaks you applied ?

thx

 

[Sonic7]

from my side the kernel looks good so far good idle batterie atm

 

[scanie]

Flashed via CWM without problems. Will be using this kernel and post results tomorrow night.

I'm on Exynos 2.0.

 

[H377]

After 1h2m almost always in idle with screen off (GMail&Exchange Push, 3G on) 1% has gone. The phone was charged to 100% and the battery stats were also wiped.


EDIT: GPS was/is also on