[Fascinate Android Development] comradesven:
You're welcome of course. I do it for me, though!

The one I'm thinking of is indeed the one people pointed you to. It looks like the ROMs have the proper firmware for the phone's wifi (the Wireless Tether for Android app uses it by default) because it worked for me as I said. I hope you have had success.

Your problem is pretty vague but I have some ideas if you haven't gotten things working by now. I talked about some things that you need to make the Samsung source compile into a working kernel but those are all included in the source you downloaded, which is the right repo.

I've actually never tried it but it looks like there's a way to dump Linux's boot messages to the framebuffer on the phone. I refer you to this commit in djp952's git: https://github.com/djp952/sch-i500-gingerbread/commit/43c5609f8f25ea7138a834290b9726396faa8052

I compared sch-i500_defconfig and sch-i500-debug_defconfig in my fork of his kernel (the old TKSGB source) and here's what looks important. You can do it yourself, too, by downloading the individual files as of a certain commit from github's web interface and running a diff, to see what else changed.

429,430c429,430
< CONFIG_CMDLINE="console=ttySAC2,115200 init=/linuxrc"
< # CONFIG_CMDLINE_FORCE is not set
---
> CONFIG_CMDLINE="console=tty0,115200 fbcon=rotate:1 fbcon=font:VGA8x8"
> CONFIG_CMDLINE_FORCE=y
1467c1467
< # CONFIG_FRAMEBUFFER_CONSOLE is not set
---
> CONFIG_FRAMEBUFFER_CONSOLE=y
1469c1469,1474
< # CONFIG_LOGO is not set
---
> CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
> CONFIG_FONTS=y
> CONFIG_FONT_8x8=y
> CONFIG_FONT_8x16=y
> CONFIG_LOGO=y
> CONFIG_LOGO_LINUX_MONO=y
1956c1961
< # CONFIG_PRINTK_TIME is not set
---
> CONFIG_PRINTK_TIME=y
1992c1997
< # CONFIG_DEBUG_INFO is not set
---
> CONFIG_DEBUG_INFO=y

So in theory you should be able to open up arch/arm/configs/tksgb_defconfig, change the lines prefixed with < with those prefixed with > , build the kernel again, and see the boot messages.

Before that you can try adb shell while your kernel is loading and getting stuck on the Samsung logo. For example, I used to only vaguely understood why this was important. Without the changes to include/scripts/setlocalversion or if CONFIG_LOCALVERSION_AUTO was =y in the defconfig my phone hung at the Samsung logo too. adb shell said something like "/system/bin/sh: no such file", which led me to the Voodoo logs at /sdcard/Voodoo (also something you should try), from which I discovered there were no bml or stl devices in /dev/block, which was bad because most internal partitions including /system are /dev/block/bmlsomething or stlsomething. Turns out that the FSR driver that creates those devices and the RFS filesystem driver among others are built as modules and so getting the "version magic" correct is pretty damn important.

Make sure you really do have all the prerequisites on your x86 build machine to build an Android kernel. The CyanogenMod wiki has some great articles like this one that you should look through even if things like getting proprietary files from a stock ROM and the Java SDK don't apply to you to make sure you have the packages.

Still, all the necessary things appear to have made it onto my github. Maybe if you don't make the /home/vb/toolchain symlink and set the toolchain paths correctly in build.sh and Makefile? I was going for builds that just worked with only minimal hassle as long as the build machine has all the prerequisites.

No idea. I appreciate that you seem to have made finding that kind of thing out something you do, though :P

Apparently dvfs_lock doesn't respect those settings, so for example Bluetooth usage may lock your phone at 200MHz. This behavior is in the original Samsung source.

It does still eventually slow down over time. Can't have that. :)