[Development]Kernel

---

Hei there.

The idea of this thread is to develop a better kernel for the I9001 in the community. I have compiled my own one for using it in the cwm recovery mod. I've only changed the following so far:
Patched pm2.c file in the samsung kernel sources, see here for the patch:
https://github.com/PabloPL/android_k...a47329371fff44

through menuconfig I've changed the default cpu governor from performance to ondemand.

What we should implement first is init.d support.

I've uploaded my boot.img file for further use here:
http://www.mediafire.com/?6p91s5knka0e0py

It also contains the CWM Recovery

This is great idea bro. Its great to have you here.
Thanks again!!!

Sent from my GT-I9001 using Tapatalk

I would love to see a overclock able kernel! Great idea!

Joost

Sent from my GT-I9001 using XDA App

overclocking module

---

Hi guys,

coolbho3000 posted source of an overclocking module for HTC Vision. As far I know, it can be used with the SetCPU App together.
http://forum.xda-developers.com/showthread.php?t=813681

Since S+ has a similar Qualcomm chip, it should work as well.

I compiled the overclocking module with the S+ Kernel and packed it into the zImage. The device doesn't boot. Maybe it would be better to follow what coolbho3000 says and adapt the settings :)

ädu

PS: it needs definitively some adaptions.

Shouldn't we create our own github/bitbucket repositories for kernel and CWM? I'm trying to get my feet wet in generic Android kernel development now, it would be cool to have repository to sync with.

Originally Posted by YardE

Shouldn't we create our own github/bitbucket repositories for kernel and CWM? I'm trying to get my feet wet in generic Android kernel development now, it would be cool to have repository to sync with.

yep of course. I've already opened an account on github. But right now I ain't got time to read the instructions on how to upload repos because I'm busy with applying some changes to FeaMod Recovery and testing them.

I would be happy if a lot of kernel developers would join us!

Edit: The sources for FeaMod recovery 1.1 are on github:
https://github.com/manveru0/FeaMod-R...-CWM-Recovery-

Samsung kernel sources with patched pm2.c:
https://github.com/manveru0/kernel_I9001_samsung

Later I'll try to add "run-parts /system/etc/init.d/" to init.rc, but I'm highly confused from examining ramdisk, because I couldn't find any bash-scripts interpreter (possibly embedded into init executable?) and don't have enough time to continue examining init.rc now. I think, we can add busybox to system image and call it from there. Also, please, modify these lines in default.prop in your future builds:

ro.secure=0
ro.debuggable=1

As far as I understood, these allow us to use "adb root".

Also, thanks for your awesome work!

Originally Posted by YardE

Later I'll try to add "run-parts /system/etc/init.d/" to init.rc, but I'm highly confused from examining ramdisk, because I couldn't find any bash-scripts interpreter (possibly embedded into init executable?) and don't have enough time to continue examining init.rc now. I think, we can add busybox to system image and call it from there. Also, please, modify these lines in default.prop in your future builds:

ro.secure=0
ro.debuggable=1

As far as I understood, these allow us to use "adb root".

Also, thanks for your awesome work!

sounds good. I haven't seen a script interpreter either and I'm not quite sure if there is one included in the init. I think it's better we include busybox. Take a look at this thread by the way:

http://forum.xda-developers.com/show....php?t=1152740

I'll try to do that testwise.

Here's the adress for my uploaded boot.img-ramdisk without the samsung pictures (we can easily add them again when building a new boot.img):
https://github.com/manveru0/bootimage_ramdisk_I9001

I've already included the changes in default.prop

EDIT: some useful links
http://www.kandroid.org/online-pdk/guide/bring_up.html
http://www.androidenea.com/2009/08/i...nd-initrc.html

After some init.rd learning I've inserted a service here which should get the job's done, but I have no idea how to test it. Anyway, here is the diff from the normal one:

[abbradar@abbradarbook boot]$ diff -u3 init.rc ../boot_mod/init.rc
--- init.rc	2011-11-05 22:35:33.194680288 +0400
+++ ../boot_mod/init.rc	2011-11-05 22:24:40.000000000 +0400
@@ -566,7 +566,7 @@
     
     # ihryu 2010.07.19
     setprop ro.rfkilldisabled 0
-    class_start default
+    #class_start default
 # +++++++++++++++++++++++++++++++++++++++++++
 
     # for silent reset
@@ -714,6 +714,10 @@
     onrestart restart netd
     onrestart restart sensor-daemon
 
+service initd /system/bin/logwrapper /system/xbin/busybox run-parts /system/etc/init.d
+    oneshot
+
 service media /system/bin/mediaserver
     user media
     group system audio camera graphics inet net_bt net_bt_admin net_raw radio  qcom_oncrpc
[abbradar@abbradarbook boot]$

Have also commented "class_start default" which runs twice for some reason. To have this working in theory, you should have busybox installed in /system/xbin with run-parts support. For me, it boots at least ^_^
P.S. It also works if I call command line from adb. Also, adb root works after changing default.prop, good.
P.P.S. You can also remove "charging.rle" from repo, as it is image, too, but why not just keep all the files in repo? git is loyal to binary files as long as you don't try to create a patch. ~_^ Also, you can use .gitignore to exclude some files from git's view at all.

Found excellent reference on init.rd:
http://www.kandroid.org/online-pdk/guide/bring_up.html
Fixed previous post (removed "disabled"), so it should really work now. Going to test it, but not really sure if my test are correct (I'll try to write something to sdcard, but is it mounted r/w at the moment of script running?)
Test failed, thinking of some other, more accurate tests now.
Tried to create file in /cache, and it worked! Here is boot.img with working init.rd and adb root. Flash it via dd (dd if=boot.img of=/dev/block/mmcblk0p8). You should have busybox installed into /system/xbin for this to work.