Develop Bugs

[DEV] Kernel 2.6.27-community (Version 1.4 - 03/11/09)

Disclaimer: For devs only. Updating to it will wipe your device. I am not responsible of any damage of any sort or data loss or anything. Alway do a nandroid backup before updating
Kernel android-msm-2.6.27-hero-community
The purpose of that community project is to have an optimized hero kernel based on HTC kernel sources.
Current release: 1.4 [download]
Features:
- compcache with ramzswap enabled
- /system/etc/init.d init scripts support
- some init script (firstboot, userinit)
- CIFS support
- Ext4 full support
- Removed DEBUG options
- All bluetooth options (don't know if needed ??)
- Droidwall support
- Pptp support (need testing)
- IP Gre tunnel module
- SquashFS 3.4
Links:
Git
Wiki
Issues tracker
Note: devs, as a community project, you patches or configuration corrections are welcomed. Feel free to submit.
Note: if anyone needs it, in the downloads section of the git there is the patch to apply to android-msm-2.6.27 sources so they compile for Hero.
Note: this kernel does not support modaco roms, the reason is that modaco rom is dependant of scripts called from kernel ramdisk, witch is not good. If you use Modaco rom, use teknologist kernel (http://ow.ly/yCxu) witch have similar tweaks

Changelog
Version 1.4 - Nov 3rd 2009
- added ext4 full support
- some init.d scripts (firstboot, userinit)
- squashfs 3.4
Version 1.3 - Nov 3rd 2009 (test build)
Version 1.2 - Nov 3rd 2009
- added ext4dev support (ext4 support in git, update.zip coming soon)
- added pptp support
- removed kernel debuging options
- added ramzswap init.d script
Version 1.1 - Oct 29th 2009
- added support for /data/init.sh script
- added support for /system/etc/init.d/* scripts
Version 1.0.1 - Oct 29th 2009
- fixed wlan.ko
Version 1.0 - Oct 28th 2009
- compcache 0.5.4 patch
- optimized config by Teknologist

Thanks for the hard work and more importantly sharing!..... this will be very useful once Ive got my oven sorted

Lox could you also post the version number of compcache that is integrated ? (and version numbers for future addons) cant wait to test the next release
Edit: Do i need to wipe the data before i update to this kernel? because i cant turn on wifi

whats the diff between AOSF CUPCAKE thread and this? these two projects do diff jobs? which will give us a basic android rom withot sense thing?

dying4004 said:
whats the diff between AOSF CUPCAKE thread and this? these two projects do diff jobs? which will give us a basic android rom withot sense thing?
Click to expand...
Click to collapse
This is the an optimized kernel to run any rom.

Lox_Dev said:
This is the an optimized kernel to run any rom.
Click to expand...
Click to collapse
WHOA!!!
LOX u have got really close in getting those nice roms and fancy stuffs in hero. so this is the base of all roms and fancy things.
CONGRATS BRO

New version 1.1.
Now you can have init scripts in /system/etc/init.d. /data/init.sh supported too.
To run Compache and have a really faster kernel, follow this how to. Busybox is needed (here is an update.zip to install it)

Lox_Dev said:
New version 1.1.
Now you can have init scripts in /system/etc/init.d. /data/init.sh supported too.
To run Compache and have a really faster kernel, follow this how to. Busybox is needed (here is an update.zip to install it)
Click to expand...
Click to collapse
could you also add little adb how-to for adding @ moving 05ramzswap file to init.d ?

i read all the references printed in first post, but there is nowhere a description of what has been optimized.. can someone please inform ;-)

felikz said:
i read all the references printed in first post, but there is nowhere a description of what has been optimized.. can someone please inform ;-)
Click to expand...
Click to collapse
second post maybe?

jaapschaap said:
second post maybe?
Click to expand...
Click to collapse
thats just the CHANGE LOG?

@ Lox_Dev
Thanks
This 05ramzswap script is correct?
#!/system/bin/sh
insmod /system/lib/modules/lzo_decompress.ko
insmod /system/lib/modules/lzo_compress.ko
insmod /system/lib/modules/compcache/xvmalloc.ko
/system/xbin/insmod /system/lib/modules/compcache/ramzswap.ko memlimit_kb=64200 backing_swap=/dev/block/mmcblk0p3
swapon /dev/block/ramzswap0
fi;
For building the rom, is correct added this line in update-script?
show_progress 0.5 0
show_progress 0.2 0
write_raw_image PACKAGE:boot.img BOOT:
show_progress 0.2 10
Thank you and sorry my english.

MACH_SAPPHIRE=y
Click to expand...
Click to collapse
Does this option is really necessary ?

thx lox, thread sticky

I managed to use nandroid's restoring method and put new boot.img back without any data wipe. Here is how I did it: Make a nandroid backup first, and copy the latest backup files to your computer, replace original boot.img to the new one(community version). Then edit the value of boot.img in nandroid.md5 to the proper content and match your new boot.img. Finally just restore it in recovery mode.
If the wireless function isn't working after boot, you may also need to push it via adb:
adb push wlan.ko /system/lib/modules/wlan.ko
adb shell sync
(reboot again)

foxfair said:
I managed to use nandroid's restoring method and put new boot.img back without any data wipe. Here is how I did it: Make a nandroid backup first, and copy the latest backup files to your computer, replace original boot.img to the new one(community version). Then edit the value of boot.img in nandroid.md5 to the proper content and match your new boot.img. Finally just restore it in recovery mode.
Click to expand...
Click to collapse
# adb push ./boot.img /sdcard
# adb shell flash_image boot /sdcard/boot.img
I little bit more fast... (but you should make a backup before)

Poischack said:
# adb push ./boot.img /sdcard
# adb shell flash_image boot /sdcard/boot.img
I little bit more fast... (but you should make a backup before)
Click to expand...
Click to collapse
i'm on RUU 2.73.x version, for some reason fastboot and adb push won't work... anyway I just provide an alternative way.

Lox did you try to upgrade to 2.6.29?

foxfair said:
Lox did you try to upgrade to 2.6.29?
Click to expand...
Click to collapse
Clone this git if you want to play:
git://android.git.kernel.org/kernel/msm.git branch android-msm-2.6.29
You WILL need to port over some of the drivers from the Hero kernel HTC released a while back (which was 2.6.27 btw).

[KERNEL][GPL][SECURITY][I9000] FuguMod (Gingerbread) VoodooSndV10

Included in the image are:
- Superuser
- own busybox 1.18.4
- TUN support
- No more RFS at all (if you want)
- JVB source based
- CWM 3.0.0.5
- security fixes
- low latency
- filesystems: jfs, ext2/3/4 (using ext4 driver), reiserfs, rfs (not on Ultra)
- CIFS support
- Voodoo SoundV10
- Voodoo color (sharpness fix)
- BLN (enabled by default)
- Preemptive RCU (only on Ultra)
- 10 fingers support (on roms that support it)
It has been tested on JVB/JVH/JVO/JV9
Read the whole post (except the changelog) before attempting to install
Thanks to Neldar for BLN
Thanks to Supercurio for voodoo additions
Thanks to zurchpet and js8 for dedicated testing
Thanks to Andro1d for ideas
Thanks to mothatt for the vectorized picture
Thanks to virnik for the new boot logo
For safety purposes /dev/block/stl3 is not mounted anymore but /efs is copied to /dbdata.
Quick table on the versions:
Two branches: Stable (which is stable) and Bleeding Edge (includes latest changes, in testing, consult the changelog)
Two versions in each branch: Normal (without preemptive RCU) and Ultra (with preemptive RCU)
Video
http://www.youtube.com/watch?v=mO-MiKVAzD8
You must flash a normal kernel before Ultra or you will not have phone/modem
Ultra does NOT support RFS filesystem
This kernel can now also be flashed from DOC rom in http://romkitchen.org thanks to Stefunel, choose a non wipe rom.
You can get it at . Normal version is named zImage-rXXX and Ultra is named zImage-ultra-rXXX.
Logs are in /fugumod.log
You can get support on #romkitchen on irc.freenode.net
Unless some unexpected changes occur, I am not going to produce any overclocked kernel anytime in the future as they have proven multiple times to be too unstable.
- All versions are upgradeable to the latest one without any data loss.
- You must have at least 400Mb free on your internal SD card storage for conversions. If you don't have any apps installed. If you have apps already installed, you must ensure that you have at least the same size as you data storage free on the sdcard. Note that upgrades don't really need space on your external storage.
- It is only known to work with international GT-I9000 and the Bell 9000M.
- The cleanest way to revert the mod is to reflash a complete ROM. But now supports reverting to RFS as well.
- If you use another custom kernel, you don't need anymore to revert the lagfix before applying. But it is always a good idea to start from a clean ROM.
Locale/timezone reset when using some filesystems
Some people may see that time zone sometimes reset at boot or even language reset, the easy solution is to edit /system/default.prop with something like:
persist.sys.timezone=Europe/Brussels
persist.sys.language=en
persist.sys.country=BE
Click to expand...
Click to collapse
Chances are that those settings are not in your /system/default.prop, it is safe to append them after the already defined ones.
See [url]http://en.wikipedia.org/wiki/List_of_zoneinfo_timezones for your timezone
How to convert filesystems:
Use FuguApp or FuguAppFree or create a /sdcard/fugumod/fs.convert file. If you don't see the paid version in the market and only see the free one, it may be due to your ROM build prop, just change it with SGS tools (in SGS tools -> prop editor -> build.prop -> Unlock -> ro.build.fingerprint=samsung/GT-I9000/GT-I9000:2.3.3/GINGERBREAD/XWJVB:user/release-keys and leave the rest as is. save, Apply script -> clear market cache, reboot...)
You can also create a /sdcard/fugumod/fs.convert which has the same syntax as /sdcard/fugumod/fs.current
How to specify custom filesystem mount options:
Create a file called /sdcard/fugumod/fs.options
It should contain the FS options like shown below (not specify a fs is equivalent to no option). Options "noexec nodiratime nosuid nodev nosuid" are "enforced".
stl9 noatime,barrier=0
stl10 noatime,barrier=1
stl11 noatime,notail
mmcblk0p2 relatime,barrier=0
Click to expand...
Click to collapse
Root bug with some applications:
Some applications don't properly detect if the phone is rooted, generally because they expect su to be in /system/xbin
Solution: type the following commands as root using adb shell or connectbot or any other shell console:
mount -o remount,rw /system
mkdir -p /system/xbin
cp /sbin/su /system/xbin/
mount -o remount,ro /system
Click to expand...
Click to collapse
What is Ultra version
Ultra version is a version with a preemptive RCU which brings an impressive user experience by having a near realtime response. Interestingly, it also seem to boost quadrant scores by ~15%.
Bleeding Edge can be found here
But it is not compatible with RFS filesystem, so don't flash if
- you still use RFS in any of /system, /data, /dbdata , /cache
- you haven't at last booted once a normal FuguMod edition
- you don't have basic skills of recovering from soft bricking (generally, flashing a normal edition will solve soft brick with Ultra)
Start adbd as root
If you want to start adbd as root and in recovery, you need to create a file called /sdcard/fugumod/debug
The change will only take place on next reboot.
Why is quadrant score so low ~1000 in ext4 but I still feel my phone is really fast?
- Quadrant does no measure latency, but user does it. You could have a completely unresponsive phone with very high quadrant score.
- I use safe mounts for ext4, but if you feel brave enough, you can tweak them using fs.options explained earlier or switch to JFS.
- Some ROMs/kernels set "media.stagefright.enable-player=true" in build.prop, in general this will give you 500+ supplementary quadrant score but but will break playing some videos. This won't make your phone faster or more responsive or whatever, it will only boost your quadrant score and break some videos.
Which filesystem is the best?
This all depends on your perception. I general, having /system on reiserfs and all others on jfs seems to be the fastest.
Random reboots
They are known to happen if:
- you force switch the radio band for example using "band selection" in diagnostic menu from wcdma 1900/2100 to 850 or 900 gsm.
Wifi not working
If your wifi is not working anymore, you probably use a JVH based ROM and have restored your wifi settings via titanium backup (or possibly other backup utilities). Wifi configuration from pre-JVH is not compatible with JVH ROMs. You should be able to restore without reflashing a full ROM by stopping wifi, then doing the following commands in a root shell.
cd /data/wifi
cp bcm_supp.conf bcm_supp.conf.bak
cp wpa_supplicant.conf wpa_supplicant.conf.bak
rm bcm_supp.conf
ln -s wpa_supplicant.conf bcm_supp.conf
cat bcm_supp.conf.bak | head -n5 > wpa_supplicant.conf
cat wpa_supplicant.conf.bak >> wpa_supplicant.conf
rm wpa_supplicant.conf.bak bcm_supp.conf.bak
Click to expand...
Click to collapse
And enable wifi again
WARNING: This may brick your phone, kill your cat or destroy your house (although in theory it should not).
If you like it, remember there are donations which may help me getting a development phone
Repository: http://github.com/renaudallard
Source of other GPL utilities I use: http://faramir.eriador.org/r/
Download
http://faramir.eriador.org/r/Samsung_galaxys/, it is called zImage-rXXX or zImage-ultra-rXXX. Bigger XXX number means it's the most recent version.
Changelog:
https://github.com/renaudallard/kernel-GB-GTI9000/commits/fugumod

sounds interesting, I'm keen to hear more about your project

A bit more info would be nice: quadrant score, are apps like newsrob fast.

Install it yourself, and play its the only way to get a feeling on how it preforms.
However:
JPM - Clean
Quadrant Score: 981
default slice_sync (97), slice_async (39)
Write: 12800000 bytes (12.2MB) copied, 2.836737 seconds, 4.3MB/s
Read: 12800000 bytes (12.2MB) copied, 0.222411 seconds, 54.9MB/s
JPM - with jfs
Quadrant Score: 1658
Write: 12800000 bytes (12.2MB) copied, 1.311856 seconds, 9.3MB/s
Read: 12800000 bytes (12.2MB) copied, 0.221596 seconds, 55.1MB/s
Tests done with:
dd if=/dev/zero of=/data/test count=25000
dd if=/data/test of=/dev/null

erased for better timeline

Have you tried with ReiserFS and XFS ?? Because I wanted to test with those even if they might use more cpu they should be faster, but I didn't had the time to,

Yeah this is interesting.
I must admit I hesitated between Ext4 and JFS during original choice for Voodoo and after a lot of reading (and head scratching) I chose Ext4 mostrly because of the ease to get e2fsprogs working, and their maturity.

Hey guys I love the developers society I'm glad to see that our phone has such hard working developers! Looking forward to good news from you

nikademus said:
Hello,
I was not intending to post this at first, but it seems some people are interested in my works on the Galaxy S.
I made a very raw script to convert /data to jfs on the external SD (at the moment).
I am open to all suggestions, so feel free to post
Click to expand...
Click to collapse
By the way, if you want to avoid creating new script (conversion, etc) I suppose you can "port" Voodoo to JFS in a few minutes.
Don't hesitate to ask for details if you're interested in.
I'm curious about this, I feel like I could have underestimate JFS for mobile (about the low CPU utilization part), like, you know, the general underestimation of this filesystem.
On my tests, the battery really used by the filesystem itself is really minimal, but still

supercurio said:
By the way, if you want to avoid creating new script (conversion, etc) I suppose you can "port" Voodoo to JFS in a few minutes.
Don't hesitate to ask for details if you're interested in.
I'm curious about this, I feel like I could have underestimate JFS for mobile (about the low CPU utilization part), like, you know, the general underestimation of this filesystem.
On my tests, the battery really used by the filesystem itself is really minimal, but still
Click to expand...
Click to collapse
I would like to see Voodoo using JFS, I think that it will only be better.

Will be interesting to compare only recently updated to JPM so will have to give this a look..

exadeci said:
Have you tried with ReiserFS and XFS ?? Because I wanted to test with those even if they might use more cpu they should be faster, but I didn't had the time to,
Click to expand...
Click to collapse
I did not try xfs, but reiserfs did quadrant scores of about 1200.
XFS overhead is higher than many others, so battery wise, it may not be a good idea. If you wish to test, I made an xfs.ko module on my site (even a btrfs one).

This page is an interesting read, what's your opinion about this?
http://wiki.archlinux.org/index.php/JFS
btw this remark is very bad for Android usage: http://wiki.archlinux.org/index.php/JFS#JFS_losing_files
I don't how valid it is.

nikademus said:
I did not try xfs, but reiserfs did quadrant scores of about 1200.
XFS overhead is higher than many others, so battery wise, it may not be a good idea. If you wish to test, I made an xfs.ko module on my site (even a btrfs one).
Click to expand...
Click to collapse
I experienced a bad habit that XFS has, it tend to produce garbage in files when not powered down cleanly
XFS was mostly designed to work efficiently with big files.
JFS looks like a more sensible choice

btw this remark is very bad for Android usage: #JFS_losing_files
I don't how valid it is.
Click to expand...
Click to collapse
I know about this, but under android, memory pressure should be sufficient to force writes.
Also it's not very clear how this affects the filesystem. If someones first job is to power the system unproperly, then with whatever filesystem, you will have problems at some point. Also, there is a "discussion" about this here too:
http://wiki.archlinux.org/index.php/Talk:JFS_Filesystem
(this link posting is a little bit annoying, if someon knows how to bypass that, I would be happy to hear)

nikademus said:
...(this link posting is a little bit annoying, if someon knows how to bypass that, I would be happy to hear)
Click to expand...
Click to collapse
You need at least ten (or twelve, don't remember well) posts. Since your posts are particular interesting, I hope you will break that limit very soon...
Thank you very much for your contribution.

daigoro64 said:
You need at least ten (or twelve, don't remember well) posts. Since your posts are particular interesting, I hope you will break that limit very soon...
Thank you very much for your contribution.
Click to expand...
Click to collapse
Thanks for finding my work interesting, hopefully, I will break the post barrier soon.

I think you should work with the z4mod team so they can provide a jfs update.zip

http://llorien.org/samsung_galaxys/
i'll help you hyperlink it lol. you can quote it or something idk. go spam some posts in Q&A and you can post links yourself ;p

Adevem said:
llorien.org samsung_galaxys
i'll help you hyperlink it lol. you can quote it or something idk. go spam some posts in Q&A and you can post links yourself ;p
Click to expand...
Click to collapse
Thanks for linking (even if I cannot qupote you correctly)

dcd's intercept kernel 0.4.0 [root/ext2/ext4/5.4mflops]

Here is a kernel for Froyo intercept.
Features:
root
busybox
ext2/ext4 support
FUSE support
CIFS support
branch prediction
ARM V6k processor extensions
FASTFPE floating point emulation
To be real honest, this kernel offers nothing that CrapKernel doesn't already offer. I am posting this early version to announce that I am working on intercept, and also track my own progress. Any feedback is appreciated.
Huge thanks to JosephMother, who all but built it for me. Also thanks to rxaaron for help along the way, joeykrim for the moment guides and .config references, and to everyone in #sdx-developers.
Changelog:
0.2.4:
first beta release
add ext2/ext4 support
0.2.5:
add FUSE support
add CIFS support
move to gcc 4.4.5
gcc flags -O3
optimize for arm1176jzf-s
0.3.0:
reduce kernel log buffer size
remove parallel port
include my busybox binary
0.4.0:
enable ARM V6k processor extensions
replace NWFPE with FASTFPE
Download:
0.2.4: http://www.megaupload.com/?d=VMGMB9WV
0.2.5: http://www.megaupload.com/?d=C7WGZ1M6
0.4.0: http://www.megaupload.com/?d=KI29NSTX

question
How to install? This affects me some funsion the phone? I have to have custom recovery? A prerequisite?

henrydcc said:
How to install? This affects me some funsion the phone? I have to have custom recovery? A prerequisite?
Click to expand...
Click to collapse
Copy the zip to your sd card and install using a custom recovery. Will not work without custom recovery.

dcd1182 said:
Copy the zip to your sd card and install using a custom recovery. Will not work without custom recovery.
Click to expand...
Click to collapse
I beg to differ, you can pull the zimage from the zip file, place it on your sd card, and use terminal, connectbot, or adb to run:
flash_image boot /sdcard/zImage
But since you're an intercept rookie you're forgiven dcd

yes
i'm rookie intecept user, but my first cel. was a htc hero and i now fully management it.

[24.APR.2011][KERNEL] AA 0.6 OC [ext2/3/4,cifs,reiserfs,btrfs,nilfs,utf8][MAGLDR/cLK]

Use at your own risk, overclock at your own risk - I'm not responsible for damage to your device​
The kernel used in this ROM is based on MDJ S9.2, and have ported it, and have patched to the latest upstream with the relevant fixes
The git is available here, check logs and diffs for the changes made. There is a neat build script to get it compiled for yourself if you want as well in Linux or cygwin. I am using the test branch at the moment.
Howto cLK (kernel_aa_X.X.zip)
Click to expand...
Click to collapse
Download kernel
Unzip archive
run script.sh (linux) or script.bat (windows) to copy over the kernel modules to your phone (make sure adb is in your path)
grab the initrd.gz from your current rom
then, either
reboot phone into fastboot by holding the back key
run "fastboot -c "" -b 0x11800000 flash:raw boot zImage initrd.gz"
or
make boot.img by using "mkbootimg --kernel zImage --ramdisk initrd.gz --cmdline "console=null" --base 0x11800000 -o boot.img"
adb push boot.img /sdcard/
adb shell flash_image boot /sdcard/boot.img
reboot your phone
Howto MAGLDR CWM (kernel_aa_X.X.zip) & Howto cLK (kernel_aa_X.X_clk_ppp.zip)
Click to expand...
Click to collapse
Download kernel
copy archive onto the FAT partition of your SD card
reboot phone into CWM
Select Install zip from sdcard
Select choose zip from sdcard
Select the kernel from the SD
Select Yes to install the zip
reboot your phone
Differences between kernel_aa_X.X.zip and kernel_aa_X.X_clk_ppp.zip
Click to expand...
Click to collapse
my initrd (so has boot.img which will only work with cLK)
Added ppp specific stuff
Added 02recov, which allows to get ROM Manager working (works for me)
NOTE: The initrd may or may not work for everyone please report your problems with dmesg and logcat files
Thanks/credits
Click to expand...
Click to collapse
m-deejay
Cotulla (MAGLDR)
RaiderX303 (ClockworkMod)
cedesmith (cLK)
#htc-linux and #htc-linux-chat
All ROM users

Changelog
v0.6 (24/04/2011)
Add reiserfs support
Add NILFS support
Add btrfs support
v0.5 (21/03/2011)
Removed SMARTASS
Merged with master git
v0.4 (18/03/2011)
kernel patch to save reboot reason so is available on bootloader (credits to cedesmith)
v0.3 (01/03/2011)
Add back PPP support (to work with cLK)
Add cLK patches (credits to cedesmith)
more MDJ stuff config
v0.2 (14/02/2011)
re-cloned MDJ S9.2
Created branch test
Removed squashfs
Removed unnecessary PPP
Merged with master git
v0.1 (12/02/2011)
cloned MDJ S9.2
merged with master git
Previous Changelog from MDJ
Code:
S9.2:
- fixed wifi mac addresses ( http://www.gitorious.com/linux-on-wince-htc/linux_on_wince_htc/commit/4c31f2fb265ae68b82ed5e8ea4bec91208837011 )
S9.1:
- Initial Release

reserved another

Trying now
Sent from my HTC HD2 using XDA Premium App

Nice, thanks.....if i'm not wrong Mdj's kernel wasnt UV, right?

is it UV? afaik no
af974 said:
Nice, thanks.....if i'm not wrong Mdj's kernel wasnt UV, right?
Click to expand...
Click to collapse
afaik, it is not UV, I cannot see it in his changelogs

updated kernel see OP, changelog and git logs for details

Thanks so much. It's said that MDJ's kernel is extraordinary power-saving and low battery drainage. We have not seen Mr MDJ on the forum for quite a long time. We just hope you great guys to carry on the goodness of MDJ's kernel.

about time someone made a proper kernel for cLk ..thanks arif-ali

arif-ali said:
Use at your own risk, overclock at your own risk - I'm not responsible for damage to your device​
The kernel used in this ROM is based on MDJ S9.2, and have ported it, and have patched to the latest upstream with the relevant fixes
The git is available here, check logs and diffs for the changes made. There is a neat build script to get it compiled for yourself if you want as well in Linux or cygwin. I am using the test branch at the moment.
Download kernel
Unzip archive
run script.sh (linux) or script.bat (windows) to copy over the kernel modules to your phone (make sure adb is in your path)
grab the initrd.gz from your current rom
then, either
reboot phone into fastboot by holding the back key
run "fastboot -c "" -b 0x11800000 flash:raw boot zImage initrd.gz"
or
make boot.img by using "mkbootimg --kernel zImage --ramdisk initrd.gz --cmdline "console=null" --base 0x11800000 -o boot.img"
adb push boot.img /sdcard/
adb shell flash_image boot /sdcard/boot.img
reboot your phone
Download kernel
copy archive onto the FAT partition of your SD card
reboot phone into CWM
Select Install zip from sdcard
Select choose zip from sdcard
Select the kernel from the SD
Select Yes to install the zip
reboot your phone
my initrd (so has boot.img which will only work with cLK)
Added ppp specific stuff
Added 02recov, which allows to get ROM Manager working (works for me)
NOTE: The initrd may or may not work for everyone please report your problems with dmesg and logcat files
m-deejay
Cotulla (MAGLDR)
RaiderX303 (ClockworkMod)
cedesmith (cLK)
#htc-linux and #htc-linux-chat
All ROM users
Click to expand...
Click to collapse
Can you please make a cLK CWM Kernel of your to use with Typhoons build...
I have tried it this way and is not working and I think that the file structure for Typhoon builds is different that common build.
I would like to try this kernel. Is it possible plz?

zach.antre said:
Can you please make a cLK CWM Kernel of your to use with Typhoons build...
I have tried it this way and is not working and I think that the file structure for Typhoon builds is different that common build.
I would like to try this kernel. Is it possible plz?
Click to expand...
Click to collapse
what problems are you getting, any logcats or dmesg output

arif-ali said:
what problems are you getting, any logcats or dmesg output
Click to expand...
Click to collapse
it was stuck in bootscreen, i will try to send later.
Till then you can check the GL_Core kernel thread that had same issue
he made a Kernel for Typhoon builds and a kernel for all others.
you can see the differencies

arif-ali said:
what problems are you getting, any logcats or dmesg output
Click to expand...
Click to collapse
here is the logcat

@zach.antre
I have added the 0.5 kernel with wpa in OP, This is the only difference I see between my kernel and the GL kernel.
I haven't tested it, so not sure if it will work.
If you do test it, let me know how it goes.
thanks

arif-ali said:
@zach.antre
I have added the 0.5 kernel with wpa in OP, This is the only difference I see between my kernel and the GL kernel.
I haven't tested it, so not sure if it will work.
If you do test it, let me know how it goes.
thanks
Click to expand...
Click to collapse
I'll test it know, give 5 minutes and i'll report back
------------------EDIT---------------------------
After testing your kernel again i get the same issues.
System will not start, it is stuck in bootscreen.
You will find attached the logcat
I should mention that TyphooNs build is nonSense, it is CM7

Not many use this, but hey, might as well release it
updated kernel to
* Add reiserfs support
* Add NILFS support
* Add btrfs support

arif-ali said:
Not many use this, but hey, might as well release it
updated kernel to
* Add reiserfs support
* Add NILFS support
* Add btrfs support
Click to expand...
Click to collapse
Hey Arif, what exactly is reiserfs, nilfs, btrfs?

mattfmartin said:
Hey Arif, what exactly is reiserfs, nilfs, btrfs?
Click to expand...
Click to collapse
they are all file systems, similar to ext2/3/4, but some people prefer these instead
plus this is the basis for the recovery kernel as well that is available on RM, so more I can support, the better

arif-ali said:
Not many use this, but hey, might as well release it
updated kernel to
* Add reiserfs support
* Add NILFS support
* Add btrfs support
Click to expand...
Click to collapse
Hi Arif, thanks for all the good work!
1) Does this kernel work for GB, or only Froyo?
2) Does cLK version incorporate any of the new ppp wrapper stuff discussed in cedesmith's thread?
Thanks!

lukedunk said:
Hi Arif, thanks for all the good work!
1) Does this kernel work for GB, or only Froyo?
2) Does cLK version incorporate any of the new ppp wrapper stuff discussed in cedesmith's thread?
Thanks!
Click to expand...
Click to collapse
1a) personally, haven't tested this in GB, so not sure. zach.antre tested it with one of the GB roms, and didn't quite work. I still need to do some testing, to see exactly what is different to make it work. (but you can still test if you want the challenge)
1b) This kernel is used as a basis for CWR that is on RM, so the fact it works there, and the basis there is GB, I would have thought that it would work with GB, but I could be wrong
2) No, as the wrapper is still beta at the moment (and several people are still having problems). Once we know that is working effectively with no problems, I will have no problems in adding it in.

Nook Touch kernel hacking

So i have downloaded the nook touch kernel source and have gotten it to build using the gossamer defconfig. (as described somewhere by jesusfreke)
then as a test i enabled ext4 support and recompiled
then converted my system partition to ext4 while booted into noogie on the sdcard.
i also edited the init.rc to mount /system as ext4 and enable adb over usb support
and it seems like it works as shown in the code below.
Code:
[email protected]: nook_touch$ adb shell cat /proc/version
Linux version 2.6.29-omap1 ([email protected]) (gcc version 4.4.1 (Sourcery G++ Lite 2009q3-67) ) #3 PREEMPT Tue Oct 4 14:37:59 CDT 2011
[email protected]: nook_touch$ adb shell cat /proc/mounts
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mmcblk0p2 /rom vfat rw,sync,noatime,nodiratime,uid=1000,gid=1000,fmask=0117,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,errors=remount-ro 0 0
/dev/block/mmcblk0p5 /system ext4 ro,barrier=1,data=writeback 0 0
/dev/block/mmcblk0p8 /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,data=ordered 0 0
so where do i go from here? how do i start forward porting the kernel to .32 or .35 or do i even need to do that? in general what needs to change to get a cyanogenmod compatible kernel?
also how can we get a serial or UART output from the nook touch. I have been testing some cm builds from the nook color but it doesnt boot far enough for abd to give any output. ive looked at the back of the board but there doesnt seem to be any blatantly obvious serial port connections on it like the nook color has.
ps. uImage and uRamdisk are attached for reference. i try them if you want. but backup yours first!

Help this guy and include a Bitcoin address and I'll send you a coin

This the config you used?
--*removed*--
Edit: nvm, figured it out, and ty!
I ended up in a serious bootloop trying my compiled kernel and I got to test my recovery image in a new setting, it worked

ros87 said:
This the config you used?
omap3621_gossamer_defconfig
Click to expand...
Click to collapse
omap3621_gossamer_evt1c_defconfig

texasice said:
also how can we get a serial or UART output from the nook touch. I have been testing some cm builds from the nook color but it doesnt boot far enough for abd to give any output. ive looked at the back of the board but there doesnt seem to be any blatantly obvious serial port connections on it like the nook color has.
Click to expand...
Click to collapse
Can't find the link but someone thought there was serial pins under/near the sd card. Here is back of NT http://www.zdnet.com/photos/crackin...6244759?seq=32&tag=photo-frame;get-photo-roto
GL with this. I need to get GPS signals into my NT so subscribed

BTW, the memory is sadly only 256MB, not 512 as written in that article,
the K4X2G323PC-8G part number is mentioned here www .samsung .com /global/business/semiconductor/support/brochures/downloads/memory/SamsungPSG_july2010_final.pdf on page 10 as
2Gb MDDR 64Mx32 K4X2G323PC-8G(1) 90-FBGA 1.8V
That explains why the device reports MemTotal: 233024 kB in /proc/meminfo :-(

texasice said:
so where do i go from here? how do i start forward porting the kernel to .32 or .35 or do i even need to do that? in general what needs to change to get a cyanogenmod compatible kernel?
Click to expand...
Click to collapse
Hi,
nice to see that someone tries to get CM to the N2E.
I'm not really familiar with the process of porting CM, but I think the next step would be trying to build a working kernel from the Nook Color CM kernel sources.
It looks like most are in the /arch/arm/configs directory where a lot of definitions for the gossamer-board are missing.
Whats also missing is the touchscreen-driver drivers/input/touchscreen/zforce.c (and the according headers/configs), and the GPU/Epaper-driver (i think it is in drivers/video/omap3ep/, headers and configs have to be added too).
A good way to see what differences between the two kernels exist, is to get the version 1.1 original source for the nookcolor (Kernel version 2.6.29, same as the N2E kernel) and make a diff. http://images.barnesandnoble.com/PResources/download/Nook/source-code/nookcolor_1.1.tgz
At least thats what I will try, as soon as I find some time and get my nook.

CM should be possible. As the nook color and nook touch shares the similar hardware (at least same CPU board).
But at least we need some developer to build ClockworkMod for Nook Touch so we can copy the CM build to the device.
The bad side of the CM build is... we can't use the default Nook application anymore (unless we are going to modify the CM framework).
I guess Nook Touch is just a Android device running the "Nook" launcher, which the device should only run default book software. I wonder if it's possible to put a Nook Touch default reading software shortcut to "Go Launcher"?
mali100 said:
Hi,
nice to see that someone tries to get CM to the N2E.
I'm not really familiar with the process of porting CM, but I think the next step would be trying to build a working kernel from the Nook Color CM kernel sources.
It looks like most are in the /arch/arm/configs directory where a lot of definitions for the gossamer-board are missing.
Whats also missing is the touchscreen-driver drivers/input/touchscreen/zforce.c (and the according headers/configs), and the GPU/Epaper-driver (i think it is in drivers/video/omap3ep/, headers and configs have to be added too).
A good way to see what differences between the two kernels exist, is to get the version 1.1 original source for the nookcolor (Kernel version 2.6.29, same as the N2E kernel) and make a diff. http://images.barnesandnoble.com/PResources/download/Nook/source-code/nookcolor_1.1.tgz
At least thats what I will try, as soon as I find some time and get my nook.
Click to expand...
Click to collapse

winstonma said:
CM should be possible. As the nook color and nook touch shares the similar hardware (at least same CPU board).
Click to expand...
Click to collapse
I described in my last post what hardware is different, and what has to be changed in the kernel. But now I think we could also try the standard Nook-Touch kernel, but we have to put all the userland files in place.
But at least we need some developer to build ClockworkMod for Nook Touch so we can copy the CM build to the device.
Click to expand...
Click to collapse
CWM-Recovery would be nice, but isn't necessary for CM. We could start with a bootable SD like it was done with CM for the Nook Color.
I guess Nook Touch is just a Android device running the "Nook" launcher, which the device should only run default book software. I wonder if it's possible to put a Nook Touch default reading software shortcut to "Go Launcher"?
Click to expand...
Click to collapse
Take a look at XorZones work http://forum.xda-developers.com/showthread.php?t=1289894

As we have the full source of Nook Touch, is it possible to get Nook Touch as Official CM port?
I have the gut feeling to follow the Nook Color: Full Update Guide and install CM. So I believe it's nice to have ClockworkMod Recovery on Nook Touch.
By the way this is the Nook Touch 1.1 Source from B&N.
I am still waiting for my Nook Touch. It'll arrive 2 weeks later.
To be honest I don't need the B&N service. I just treat this device as e-ink Android Tablet. So I really enthusiastic to make CM port as official.
Is it possible to join as a team and work together?

Is it only me thinking that undervolting this overpowered ebook, would make us get that extra inch in battery life we all (I) want?
I'll look into making this kernel overclockable when I have a bit of free time.
If someone looks into it before I do better

Now, before we go on about kernel hacking, can someone actually provide a fully working kernel compiled from sources?
I spent a few hours on it (1.1.0 sources) tonight and this is how far I got:
dmesg:
http://pastebin.com/VUv74LFV
logcat:
http://pastebin.com/cGpkAz3n
Basically it's running and I can access it, but I have some trouble with the SGX (no graphics)
This is omap3621_gossamer_evt1_defconfig btw.

Wikipedia tells me NST uses an OMAP3611, there's very little diference between the two (OMAP3621) but something must screw up the output.
http://en.wikipedia.org/wiki/Texas_Instruments_OMAP#OMAP_3
---------- Post added at 01:25 AM ---------- Previous post was at 01:19 AM ----------
Allthough our NST works at 800mhz, so maybe wiki is wrong.
Here it's reported as an OMAP3621 so forget what I said.
http://forum.xda-developers.com/showthread.php?t=1251209

eded333 said:
Wikipedia tells me NST uses an OMAP3611, there's very little diference between the two (OMAP3621) but something must screw up the output.
Click to expand...
Click to collapse
NST uses Omap3621 as I can tell you from my opened NST laying in front of me
If you need more proof:
http://www.techrepublic.com/photos/...34&tag=thumbnail-view-selector;get-photo-roto
Most likely the gossamer evt1 config is the wrong one, but the edp1 (epson digital paper) config doesn't compile at all..
Weekend and GF-time is coming up so I won't be continuing this until Sunday evening.
---------- Post added at 01:36 AM ---------- Previous post was at 01:32 AM ----------
Anyway, it's close as everything is running, including Dalvik
Will figure it out next week

f*****g wiki, they must allways have something wrong.
Good work! It'll be done when it's done but didn't expect to see so much progress in so little time

ros87 said:
Now, before we go on about kernel hacking, can someone actually provide a fully working kernel compiled from sources?
I spent a few hours on it (1.1.0 sources) tonight and this is how far I got:
dmesg:
http://pastebin.com/VUv74LFV
logcat:
http://pastebin.com/cGpkAz3n
Basically it's running and I can access it, but I have some trouble with the SGX (no graphics)
This is omap3621_gossamer_evt1_defconfig btw.
Click to expand...
Click to collapse
Hi,
building from the 1.1 source with the omap3621_gossamer_evt1_defconfig configuration works great for me. The kernel runs perfectly, no problems with the display, touchscreen or wifi. Can't notice a difference between the stock and self-built-kernel.
I used arm-eabi-4.4.0 to build it.

Great! Which means we can build CM and get official build-bot.
But back to the point. But it'll be great if we can load the new Android ROM into our device.
So back to the basic question. Should we build recovery like CWM?
Sent from my Liquid using Tapatalk

winstonma said:
Great! Which means we can build CM and get official build-bot.
Click to expand...
Click to collapse
No it doesn't! Thats just the kernel. Getting CM running is a much harder task.
So back to the basic question. Should we build recovery like CWM?
Click to expand...
Click to collapse
If you can build CWM for the N2E than please do it. I tried, but had no success.

mali100 said:
No it doesn't! Thats just the kernel. Getting CM running is a much harder task.
Click to expand...
Click to collapse
I agree that CM would be tougher than building a kernel. But there are guides. Teaching us how to grab a built CM, swap the kernel, and it boots. So we can try that. But still, we need the recovery to "install" our build.
If you can build CWM for the N2E than please do it. I tried, but had no success.
Click to expand...
Click to collapse
I know it's not easy. But we have no choice but to get this step done if we need full access (like installing custom ROM). I will start trying once I grab my N2E.

mali100 said:
Hi,
building from the 1.1 source with the omap3621_gossamer_evt1_defconfig configuration works great for me. The kernel runs perfectly, no problems with the display, touchscreen or wifi. Can't notice a difference between the stock and self-built-kernel.
I used arm-eabi-4.4.0 to build it.
Click to expand...
Click to collapse
Hi
That post got outdated quite quickly as I managed to figure it out the day after posting it.
There was no problem with my build, but there's something really important missing in the Kernel sources, kernel modules for the PowerVR graphics.
So yes, you can build that config and push the kernel to a working NST and it will work as expected, but as we don't have the source code for the modules there's a limit to what we can actually do.
From my experience there only so much you can change in the Kernel before having to recompile the modules..
To be continued..