• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [DEVELOPMENT] SickleKernels For the SV

Thank you, figured out it was my internet causing issues for me...is this compatible with the new .6. Jb update fron boost?
 
ModdingMyMind said:
Where is it lol... GCC.... :-)

First time using your kernel. Always held on to the stock.
Click to expand...

Well I was using the code fire tool chain, but now I am going to build my own :) I have a lot of plans for this kernel now. It only happens on weekends though
 
simonsimons34 said:
Well I was using the code fire tool chain, but now I am going to build my own :) I have a lot of plans for this kernel now. It only happens on weekends though
Click to expand...

So is gcc implemented in the kernel? Cuz I saw your post and it appeared that way so I flashed your kernel to check it out haha.
 
simonsimons34 said:
I have a lot of plans for this kernel now. It only happens on weekends though
Click to expand...

Hey man, a question pertaining to the bcmdhd.ko file which you have located in './lib/modules/' when boot.img is unpacked?

I was looking at init.target.rc file and you have as follows:
Code: 
# Load bcmdhd.ko while booting
chmod 0444 /lib/modules/bcmdhd.ko
insmod /lib/modules/bcmdhd.ko

Yet, when the kernel is flashed on the device (K2_CL) and then booted, there is still also the original bcmdhd.ko file located in 'system/lib/modules/bcmdhd.ko.

In other words, there are two....

Would this cause conflict?

I'm about to adjust this by dragging the lib folder in the unpacked ramdisk over to the system folder and then adjust the command within the init.target.rc file. Will rebuild, and flash.

I'm curious needless to say and it seems controversy so I thought I would ask. :-)
 
Yea, made no difference from what I can tell lol. Boots up fine, results appear the same either way.
 
Benchmark
 

Attachments

  • uploadfromtaptalk1390317149331.jpg
    uploadfromtaptalk1390317149331.jpg
    27.7 KB · Views: 69
Alright so time to clear some stuff up. Firstly GCC is what you use to build the Linux kernel... Or clang (but that is different and in my opinion, not worth the changes to get to c99 right now.) the GCC 4.8 tool chain at the time was the newest. Latest optimization and such.

Modules I put them in lib so that I could just flash the kernel and be done with it. At that time security was on and kernels had to be written by fast boot. Now I will start any kernel releases :) just flash in recovery. Location of module doesn't matter though. As long as it gets installed
 
Yea, I'm aware of gcc. Your choice of words threw me in a loop so I had to see for myself :-).

Been running your kernel for about a day now. Not too bad. I like it.

But thanks for the clarification ;-)
 
ModdingMyMind said:
Yea, I'm aware of gcc. Your choice of words threw me in a loop so I had to see for myself :-).

Been running your kernel for about a day now. Not too bad. I like it.

But thanks for the clarification ;-)
Click to expand...

This one has s2w as well. You can use s2w apps to enable it. I'm also going to add lz4 to the kernel. This allows for faster boot times
 
simonsimons34 said:
This one has s2w as well. You can use s2w apps to enable it. I'm also going to add lz4 to the kernel. This allows for faster boot times
Click to expand...

Some tweaks I added along with your kernel. Helps dramatically :-).

Code: 
 * Kernel & VM Tweaks *

busybox sysctl -w vm.min_free_kbytes=27648;
busybox sysctl -w vm.oom_kill_allocating_task=0;
busybox sysctl -w vm.panic_on_oom=0;
busybox sysctl -w vm.overcommit_memory=1;
busybox sysctl -w vm.swappiness=20;
busybox sysctl -w kernel.panic_on_oops=0;
busybox sysctl -w kernel.panic=0;
busybox sysctl -w kernel.random.read_wakeup_threshold=1376;  
  
 *  3G Enhancement *

busybox sysctl -w net.core.wmem_max=1048576;
busybox sysctl -w net.core.rmem_max=1048576;
busybox sysctl -w net.core.optmem_max=20480;
busybox sysctl -w net.ipv4.tcp_moderate_rcvbuf=1;    
    busybox sysctl -w net.ipv4.route.flush=1;
busybox sysctl -w net.ipv4.udp_rmem_min=6144;
busybox sysctl -w net.ipv4.udp_wmem_min=6144;
busybox sysctl -w net.ipv4.tcp_rmem='6144 87380 1048576';
busybox sysctl -w net.ipv4.tcp_wmem='6144 87380 1048576';
 
In all honesty a kernel.panic and kernel.panic_on_oops should be 1
 
Still no 4.2.2 update for the Boost ONE SV? I haven't noticed a thread in ATR section. Been absent for a while, sorry to get off topic I don't normally do that.
 
ModdingMyMind said:
Typo lol. 10 and 1. Oops :-)

Had dinner being prepped at the time.
Click to expand...

10 on oops should be fine. Generally I got rid of any causes of it though. So that shouldn't be an issue anyways. Next chance I get, there will be one major update
 
You must log in or register to reply here.
Back
Top Bottom