yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] farmatito:
@ezterry :

so if understand it correctly it is booting/rebooting with

usb plugged in that still fails?

Do you see the same stuck "android os" entry in battery stats?

If not, than maybe it is a different bug, so more patching is needed.

UPDATE:

test:

plug in usb

reboot

wait a little while phone is charging

unplug usb

go to battery stats:

there you'll see "android os" entry

hit a few times refresh

"android os" %value decreases and after a few more refresh hits it disappears.

I think that if there is battery drain in this case it is not the same bug.

Will check the phone later to see how it behaves:

16.59 84%

18.18 77%

20.42 68%

16 % / 4hrs = 4% /1hrs (in idle state)

Looks not so bad to me... but definitely would not last

48+ hours as my battery usually lasts.

In my opinion this is not the same bug tough, because

what I and other users were experiencing was a very

fast battery drain after disconnecting from a adb

session. The latter bug is indeed fixed.
[G1 Android Development] farmatito:
After more testing with this bug N° 2 triggered the power

consumption with my extended battery is stable at about

4%/hr. I've looked at the most likely candidates

htc_battery.c

msm72k_udc.c

but I've not spotted differences between 2.6.34.8 and 2.6.35.11

that could explain the different behaviour.

Hints and help is welcome.
[G1 Android Development] VAMCAVALO:
Can some one explain that USB drain problem?

I already had change my battery but it hasn't make any difference...

My G1 can only work for 4h and them the battery is over.

That patch can fix it?

How do I flash it?
[G1 Android Development] crypticc:
Check out post for and five on this page.

Sheesh

Lol
[G1 Android Development] Dukenukemx:
There's a few ways to improve you battery life. I went crazy myself, and finally got it working great.

#1 If you're still using the original battery in your G1, it's probably time to replace it.

#2 Some roms do better with battery life, some don't.

#3 Be careful what radio you use. The radio 2.22.27.08 is probably better for USA users, while 2.22.28.25 is better for other countries.

#4 Trying disabling stuff you don't use. Turn off Auto-sync, if you don't need constant updates for E-Mail and contacts backup. You most likely don't. Disabling background data helps, but you'll need to enable it to use any data. Disabling Data under network settings has no effect in how your phone functions, but does decrease battery drain.

#5 Try changing the clock speed of your phone. Most good roms come with built in overclock, and you can change the min CPU frequency to lower then 245 Mhz. Be careful in how much you lower it, cause anything that happens on your phone will kick in the Max CPU frequency, and suck battery power.

#6 Make sure everything is working, like the camera. For months I was going crazy on my battery drain, and just recently discovered my camera wasn't working. Turns out, the camera cable was slightly disconnected. This can easily happen, since the cable sits right under the battery. Took phone apart, plugged it back in, and now battery lasts for 2 days.

#7 Of course, make sure no services are running in the background. Running applications in the background can force your hones CPU to run at max speed.

As for the USB drain bug, basically when you plug your phone in to your PC, it can drain the crap out of your battery. So charging your phone with your PC is a bad idea, and you'll have to reset it to avoid it draining so fast.
[G1 Android Development] VAMCAVALO:
Thank you for the answer!

#1 I already replaced the battery

#2 I am using the Laszlo Froyo and it's know for your not so good battery performance.

#3 I from Brazil but using 2708 radio...should I change it?

#4 Only 2G and all unnecessary stuff its out.

#5 I use the laszlo built-in CPU settings at Extras>Performance at 176-528 ondemand.. it is OK?

#6 I'm sorry but I didn't understand your problem at this point. Which battery

cable? Mine camera it's OK right now..

#7 I'm pretty sure that I know there is no app in background but there is some way to check this out?

a) And I tried to flash today the 2.6.35.11 kernel to see if it help because with laszlo rom, my G1 became really nice again but the battery sometimes make me not that happy.

b) When I charge at PC (often), the only thing I need to do is to reboot after unplug, right?

Thank you very much
[G1 Android Development] Dukenukemx:
#3 You'll have to experiment to see which radio works best for you. I used 2825 before realizing that I never tried 2708. For me, 2708 was way better, but what works best for me might not be best for everyone. Since radios are made for specific regions.

#5 I'm also using Laszlo CPU settings like you are. BTW, same rom but my battery lasts for 2 days.

#6 I worded that incorrectly. I meant to say that my camera cable was lose, and the camera wasn't working. I didn't know this, cause I didn't use the camera for months. I fixed it, and now my battery life is 10x better. The cable for the camera sits under the battery, and can easily be pulled lose by dropping the phone.

#7 Aftermarket apps from the market provide the best way to check. Though if you're sure, then don't bother. It's not hard to see if an app is running still.

a) I'm using the kernel that came with Laszlo rom, but I've found that ezBiffTestKernel20110222-2708_S.zip works great for most roms.

b) Yea reboot after you unplug it. My battery has been doing so well lately, that I can wait till I get to my car to charger it. Using my car charger to avoid charging with the PC. [/QUOTE]
[G1 Android Development] VAMCAVALO:
#3 I will try 2825 so!

#5 Holy ****! Two days I can only get leaving the phone on eternal standby...

#6 Now I understand, but my camera and other functions are normal right now.

#7 I'm sorry, but what is aftermarket apps?

a) 2.6.35.11 it's know to be a better kernel on the battery performance. Right now I'm testing 35.10 and I need to wipe my battery stats because I think it can be one of the problems.

b) Ok, that is not a problem because I charge at PC lot of times, so now I will reboot after unplugging.

Well, after all of this, if nothing works, should I change my battery again? I already changed at December 10 but it is a generic one.

TKS
[G1 Android Development] good223:
I just flashed the kernel and I've had good results regarding the battery drain. No more high % "AndroidOS" under the battery stats.

The only thing I found to be weird is the touch screen. It seems like the responsiveness while scrolling through the settings, homescreen, and app drawer is laggy and unresponsive. It sometimes doesn't even scroll when I move my finger across the screen. Also pulling the notification bar is very difficult as I really have to slowly drag it down.

I currently am using the newest kernel released, the 04/03 one, on CyanogenMod nightly 307 on my G1. My old kernel was the "ezBiffTestKernel20101106-2708_S.zip"

Thanks for your work on the battery drain problem.
[G1 Android Development] farmatito:
Could be due to the use of BFS, maybe I'll post a kernel without it in the next days, as I'm testing other changes

right know.
[G1 Android Development] good223:
Ah ok, but what exactly is BFS? I did a quick google search and I came across this article "http://techfreaks4u.com/blog/posts/kernel-linux-kernel-with-bfs/", but I still don't quite understand how it affects our phones.

Could you explain it in a simpler way?
[G1 Android Development] captaincrook:
First two zips froze at the G1 screen using DangerSPL & proper radio, though all of them work fine using the 2.22.27.08/2.22.28.25 radio & appropiate SPL.

The phone doesn't sleep either.

Will test performance more thoroughly tomorrow.
[G1 Android Development] farmatito:
It divides cpu time more or less in equal parts to all running tasks, so all (the more cpu intensive and less intensive) have

the possibility to run in a given time period, the contra is that

the more cpu intensive tasks may slow down a little.
[G1 Android Development] castaway1:
best kernel ever!

i just want to say this is best kernel i ever try (and i try them all ;) ).Its perfect in performance and battery life improved from 16h to 29h. Thank you for this a lot farmatito. Keep up good work :cool:

(using HTC MAGIC 32A / ROM: froyo by laszlo / kernel version auto-boot-2.6.35.12-farmatito-pershoot-ds -20110417.zip)
[G1 Android Development] azrash:
the 0422 patch should be done after i flashed the autokernel right? i tried it and it said verification failed, do i need to sign it using android commander first? im sorry, this is my first time applying a kernel patch, thanks! :)

Edit: i tried to sign them with Android Commander, and when i flashed it, it says update script not found, do i need to merge the patch to the autokernel manually?
[G1 Android Development] farmatito:
No just flash the autokernel. patches.zip contains the source files.
[G1 Android Development] farmatito:
Removed: was a post about a experimental kernel,

so experimental that it didn't work.
[G1 Android Development] dilwaladoctor:
First of all THANKS for all the good work.

I have been trying your kernels but with me its been useful the opposite way.....:eek:

The battery life is much better if I dont reboot the phone after charging.....if I reboot the phone then battery drains much quickly.....dont know why :p

As for the 0422 BFS 1000hz kernel, the screen response has improved alot, though still not perfect....but its usable.

Battery life is best with this kernel. Thanks once again.:D
[G1 Android Development] dilwaladoctor:
Played Raging-Thunder-2 constantly for 1 hour and battery fell only 3 points, using 0422 BFS 1000Hz Kernel.

You are a genius man. Wonderful work. Thanks alot once again
[G1 Android Development] good223:
Wow this kernel is awesome! Been using the 4-21 non-BFS kernel and it's working great. No more "AndroidOS" battery drain.

Thanks for your hard work on this kernel.

Btw any chance of a 710 oc in future kernels?
[G1 Android Development] farmatito:
No 'cause my G1 is unstable over 614 so there is no fun

for me
[G1 Android Development] mat0122:
does this kernel work with gingerbread?
[G1 Android Development] farmatito:
I switched yesterday to ezGinger and the basics work,

there could be some problems with the android gadget

as this originally was a pershoot froyo kernel.
[G1 Android Development] WiseJoeyD:
Installed through Clockwork Recovery on a 32B with CM6.1

Didn't work sadly :(

Extracting EBI0 Kernel files/modules/kernel
Installing kernel
Dumping/Unpacking/Repacking boot.img
mkbootimg 2708
Writing new boot.img
Done!

Maybe the 2708 part is what's wrong. Just have the boring ol' 0006 spl and the 16i radio.
[G1 Android Development] sisterchick:
Fixing to try 0421 kernel.

Been using the non-BFS 0417 with a stripped down CM6.1. With light use (no wifi, GPS or bluetooth), still had 70% at 33 hours. That is fantastic!
[G1 Android Development] mat0122:
i have a question farmatito :)

are u planning to do a stable version for GB?
[G1 Android Development] farmatito:
It should work. I use RA-dream-v1.7.0-cyan.img recovery.
[G1 Android Development] farmatito:
I think ezterry will do it with 2.6.36. I will just play around

with 2.6.35.12 like I've done if spare time and laziness

permits.
[G1 Android Development] farmatito:
Then maybe something is wrong with the installer.

Can you run this script on your phone:

#!/sbin/sh
#
# Find system information based on the kernel command line and populate
# nfo.prop

baseband=`awk '{m=match($0,/androidboot.baseband=([0-9a-zA-Z\.]*)/) ; print(substr($0,RSTART+21,RLENGTH-21))}' < /proc/cmdline`
bootloader=`awk '{m=match($0,/androidboot.bootloader=([0-9a-zA-Z\.]*)/) ; print(substr($0,RSTART+23,RLENGTH-23))}' < /proc/cmdline`
radioseries=`echo $baseband | awk '{print(substr($0,0,4))}'`
custommtd=`awk '/mtdparts/ {print("CustomMTD")}' < /proc/cmdline`
smisize=`awk '{m=match($0,/smisize=([0-9a-zA-Z\.]*)/) ; print(substr($0,RSTART+8,RLENGTH-8))}' < /proc/cmdline`
board=`cat /proc/cpuinfo | grep Hardware | awk '{print $3}'`
modules_sqf=`ls /system/lib/modules/ | grep -c '\.sqf$'`
#write out a prop file for the updater script to read
echo "baseband=$baseband" > /sdcard/nfo.prop
echo "bootloader=$bootloader" >> /sdcard/nfo.prop
echo "radioseries=$radioseries" >> /sdcard/nfo.prop
echo "custommtd=$custommtd" >> /sdcard/nfo.prop
echo "smisize=$smisize" >> /sdcard/nfo.prop
echo "sysboard=$board" >> /sdcard/nfo.prop
echo "modules_sqf=$modules_sqf" >> /sdcard/nfo.prop

and post the results in the /sdcard/nfo.prop file.

and tell me also what you think should be the correct

kernel for you (eb0,eb1,2708)
[G1 Android Development] WiseJoeyD:
baseband=2.22.19.26I

bootloader=1.33.0006

radioseries=2.22

custommtd=

smisize=64

sysboard=sapphire

modules_sqf=0

Just your basic original sapphire

Got the 32B 2.6.35.11 pershoot xtra kernel from February installed fine.

Think it should just be the EB0 kernel, right?

Thanks good sir for your help :)
[G1 Android Development] rattking:
I think there is still some problems with the base address logic.

with the 32b and 16i radio the base address should be 0x10000000 according to Ezterry on page 12 so mkbootimg12.sh should be used

also I have been meaning to mention that I dont think the updater-script is catching 1.2/Fenders with the 1.33.0013d spl.

edit:

would this work to be extra sure that you actually have a 2708+

if file_getprop("/tmp/nfo.prop","radioseries") == "3.22"
then
ui_print("mkbootimg eb1");
set_perm(0, 0, 0777, "/tmp/mkbootimg-eb1.sh");
run_program("/tmp/mkbootimg-eb1.sh");
else
if file_getprop("/tmp/nfo.prop","smisize") == "64" &&
( file_getprop("/tmp/nfo.prop","baseband") == "2.22.27.08" ||
file_getprop("/tmp/nfo.prop","baseband") == "2.22.28.25" )
then
ui_print("mkbootimg 2708");
set_perm(0, 0, 0777, "/tmp/mkbootimg.sh");
run_program("/tmp/mkbootimg.sh");
else
if file_getprop("/tmp/nfo.prop","smisize") == "32" &&
( file_getprop("/tmp/nfo.prop","bootloader") == "1.33.3013" ||
file_getprop("/tmp/nfo.prop","bootloader") == "1.33.0013d")
then
ui_print("mkbootimg 1.2");
set_perm(0, 0, 0777, "/tmp/mkbootimg-12.sh");
run_program("/tmp/mkbootimg-12.sh");
else
ui_print("mkbootimg 32b");
set_perm(0, 0, 0777, "/tmp/mkbootimg.sh");
run_program("/tmp/mkbootimg-12.sh");
endif;
endif;
endif;
[G1 Android Development] farmatito:
I'm thinking about removing this completely and use:

#!/sbin/sh
echo \#!/sbin/sh > /tmp/createnewboot.sh
echo /tmp/mkbootimg --kernel /tmp/zImage --ramdisk /tmp/boot.img-ramdisk.gz --cmdline \"$(cat /tmp/boot.img-cmdline)\" --base $(cat /tmp/boot.img-base) --output /tmp/newboot.img >> /tmp/createnewboot.sh
chmod 777 /tmp/createnewboot.sh
/tmp/createnewboot.sh
return $?

in mkbootimg.sh as pershoot does.

Am I wrong with this?
[G1 Android Development] rattking:
the problem with that in the past was that if the rom wrote the kernel to the wrong address initially then the updater would also get it wrong.. 1.2/Fenders users had a lot of problems with that after 2708 kernels became the default for roms
[G1 Android Development] WiseJoeyD:
A problem with the base address? Any way to 'force' it to use 0x10000000 as a starting address using the scripts?
[G1 Android Development] farmatito:
Could you please try one of the kernels linked

here to see if the simplified installer works for you

as it did for me. If it does tomorrow I will move them

to the first post.

auto-boot-2.6.35.12-farmatito-pershoot-ds+-20110425.zip

http://www.multiupload.com/UB7VYV4Z8P

auto-boot-2.6.35.12-farmatito-pershoot-ds-BFS+-20110425.zip

http://www.multiupload.com/Q667O2GG1N

Other 32A/32b/2708/MT1.2 users are encouraged to test and report if the installer works for them.

Enjoy and USE AT YOUR OWN RISK.
[G1 Android Development] farmatito:
I see...., then maybe your solution is better, but that way

this will get a mess more and more with time.

Isn't there a way to get the base address as the installing Kernel(?) expects it?

In reality we already know it as it is hardcoded in the kernel.

in Makefile.boot

ifeq ($(CONFIG_MSM_AMSS_SUPPORT_256MB_EBI1),y)
zreladdr-y := 0x19208000
params_phys-y := 0x19200100
initrd_phys-y := 0x19A00000
else
ifeq ($(CONFIG_MSM_AMSS_RADIO2708_MEMMAP),y)
zreladdr-y := 0x02008000
params_phys-y := 0x02000100
initrd_phys-y := 0x02800000
else
zreladdr-y := 0x10008000
params_phys-y := 0x10000100
initrd_phys-y := 0x10800000
endif
endif

# for now, override for QSD8x50
zreladdr-$(CONFIG_ARCH_QSD8X50) := 0x20008000
params_phys-$(CONFIG_ARCH_QSD8X50) := 0x20000100
initrd_phys-$(CONFIG_ARCH_QSD8X50) := 0x21000000

zreladdr-$(CONFIG_ARCH_MSM7X30) := 0x00208000
params_phys-$(CONFIG_ARCH_MSM7X30) := 0x00200100
initrd_phys-$(CONFIG_ARCH_MSM7X30) := 0x01200000

Am i right with the assumption:

2708 base 0x02000000

ebi0 base 0x10000000

ebi1 base 0x19200000
[G1 Android Development] WiseJoeyD:
Thanks sir!

Booted up and works perfect. The tweaks did the job :D
[G1 Android Development] farmatito:
Could you please try one of the kernels linked

here to see if the simplified installer V2 works for you

as it did for me. If it does tomorrow I will move them

to the first post.

auto-boot-2.6.35.12-farmatito-pershoot-ds+-20110425.zip

http://www.multiupload.com/J1GEPOK6EY

auto-boot-2.6.35.12-farmatito-pershoot-ds-BFS+-20110425.zip

http://www.multiupload.com/IPSIIXUCAB

Other 32A/32b/2708/MT1.2 users are encouraged to test and report if the installer works for them.

Enjoy and USE AT YOUR OWN RISK.

Going to bed now.
[G1 Android Development] d3vilskid:
auto-boot-2.6.35.12-farmatito-pershoot-ds-BFS+-20110425.zip

http://www.multiupload.com/IPSIIXUCAB

is the 1000hz in this bfs version?

both kernels flash and booted up just fine on the dream with 2708 kernel and mt3g 1.2/fender booted up fine also. so far no ill effects noted
[G1 Android Development] farmatito:
Thanks for your report. I removed 1000hz for now as in some

circumstances it was unstable on my phone.
[G1 Android Development] Brut.all:
94h on a battery O_O Thanks farmatito!

BFS 20110417
[G1 Android Development] WiseJoeyD:
The new v2 installer worked perfect on my old 32b with the 2.xx.16i radio

A friend tried the installer on his 2708 port CM 6.1, with the 2.xx.28S and it worked great as well.

Looks like your sleuthing and hard work paid off!

Thanks again dude
[G1 Android Development] castaway1:
auto-boot-2.6.35.12-farmatito-pershoot-ds+-20110425.zip

works fine on magic 32A good job farmatito.

One suggestion - can you please explain BFS version? what it can bring to our phones? i read some guides about it but i dont fully understand..I need simply explanation :p
[G1 Android Development] farmatito:
No stuttering when you listen to music , for example....that's the main reason I like it.
[G1 Android Development] farmatito:
Could people with BFS touchscreen lag issue please run this script on their phone to see if there are any improvements,

as I cannot trigger this lag whatever I do, so I think that maybe

it is a matter of my personal settings.

#!/system/bin/sh
POWERSAVE_BIAS=200; # default: 0
SAMPLING_RATE=2000000;
CPU_UP_THRESHOLD=45; # default 40, percent cpu usage before going up a speed step
IGNORE_NICE_LOAD=0;
PAGE_CLUSTER=0; # default: 3 Changes Page clustering from 8 to 2
LAPTOP_MODE=5; # default: 0 Helps keep SSD from getting worn
DIRTY_EXPIRE_CENTISECS=5000; # default: 3000
DIRTY_WRITEBACK_CENTISECS=800; # default: 500
DIRTY_BACKGROUND_RATIO=10; # default: 5
DIRTY_RATIO=16; # default: 10

echo $POWERSAVE_BIAS > /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias;
echo $SAMPLING_RATE > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate;
echo $CPU_UP_THRESHOLD > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold;
echo $IGNORE_NICE_LOAD > /sys/devices/system/cpu/cpufreq/ondemand/ignore_nice_load;
echo $PAGE_CLUSTER > /proc/sys/vm/page-cluster;
echo $LAPTOP_MODE > /proc/sys/vm/laptop_mode;
echo $DIRTY_EXPIRE_CENTISECS > /proc/sys/vm/dirty_expire_centisecs;
echo $DIRTY_WRITEBACK_CENTISECS > /proc/sys/vm/dirty_writeback_centisecs;
echo $DIRTY_BACKGROUND_RATIO > /proc/sys/vm/dirty_background_ratio;
echo $DIRTY_RATIO > /proc/sys/vm/dirty_ratio;

Just an experiment.

Enjoy and use at your own risk.

PS.: my oc settings are SCALING_MIN=122880 SCALING_MAX=528000
[G1 Android Development] azrash:
nice, new kernels! :D been getting good battery life with your kernel

one quick question though, to use the BFS version, do we need to disable setcpu? and we run your personal setting as a script in gscript right? thanks!
[G1 Android Development] farmatito:
Don't think you need to disable setcpu.

Gscript is ok or copy it userinit.sh or put it in init.d/ dir

if your rom has one.
[G1 Android Development] Patrick@sw:
Also have the lag :/ will try this script tomorrow and post my result then
[G1 Android Development] Patrick@sw:
script doesn't seem to change anything. the lag still remains for me! :/
[G1 Android Development] farmatito:
Just out of curiosity: there are 2 touchscreen drivers enabled in dream sapphire kernels

elan and synaptics, could you take a look at dmesg to see wich one is used by your hardware?
[G1 Android Development] azrash:
i have noticeable scrolling lag as well, happens in bfs+your personal setting, not sure why though :p

pastebin of dmesg here http://j.mp/idCnk4

logcat here http://j.mp/gUXrIp

im using froyo by laszlo's, tell me if you need more details, thanks! :)
[G1 Android Development] farmatito:
The dmesg starts to late in the boot process, try instead:

cat /proc/last_kmsg > /sdcard/boot.txt

and post the generated boot.txt file or just the relevant lines like:

[ 6.998840] ekt8232_probe enter.
[ 6.999114] elan-touch 0-0010: without platform data??!!
[ 7.199584] elan-touch 0-0010: __hello_packet_handler: failed!
[ 7.199829] looks like it's not Elan, so..i'll quit
[ 7.221313] msm_hsusb_phy_reset: success
[ 7.261535] msm_i2c msm_i2c.0: error, status 43c8
[ 7.262481] msm_i2c msm_i2c.0: Error during data xfer 20 (-5)
[ 7.371643] synaptics_ts_probe: Product Major Version 1
[ 7.373260] synaptics_ts_probe: Product Minor Version c
[ 7.375488] synaptics_ts_probe: product property 2
[ 7.377044] synaptics_ts_probe: device control 81
[ 7.379241] synaptics_ts_probe: interrupt enable 3
[ 7.382141] synaptics_ts_probe: 0xe0: 1 1 1 2 1 c 0 0
[ 7.384124] synaptics_ts_probe: Sensor properties 601
[ 7.389099] synaptics_ts_probe: max_x 3480, max_y 5368
[ 7.389892] synaptics_ts_probe: inactive_x -80 -80, inactive_y -32 -32
[ 7.391510] synaptics_ts_probe: snap_x 240-248 240-248, snap_y 80-88 80-88
[ 7.394348] input: synaptics-rmi-touchscreen as /devices/virtual/input/input2
[ 7.396850] synaptics_ts_probe: Start touchscreen synaptics-rmi-touchscreen in interrupt mode
[G1 Android Development] ra100x:
any idea why am I stuck in bootloop when flashing last kernel update (2011/04/25) over COS-DS ROM (04/26/2011)? it worked with older version of kernel (2011/04/24) and (04/21/2011) COS-DS ROM (http://xdaforums.com/showthread.php?t=950765)
[G1 Android Development] farmatito:
There were some changes to improve the installer.

Would you please tell me what phone, what kernel

(eb0, eb1, 2708+) was intended to be installed.

Output of:

cat /proc/cmdline

without serialno.

Output of the flashing process.
[G1 Android Development] ra100x:
sorry, I've forgotten to include info about device :)

HTC Dream/G1, 2708+ kernel

I hope this is output you needed, I ran that command after flashing kernel

board_trout.disable_uart3=0
board_trout.usb_h2w_sw=0
board_trout.disable_sdcard=0
smisize=64
androidboot.baseband=2.22.28.25
androidboot.cid=T-MOB005
androidboot.carrier=TMUK
androidboot.keycaps=qwerty
androidboot.mode=recovery
androidboot.bootloader=1.33.0013d
no_console_suspend=1
console=null

Dream/Sapphire
...
Extracting tools...
Checking system information...
Remove old kernel modules..
Extracting 2708+ Kernel files...
Extracting 2708+ modules.sqf
Extracting 2708+ kernel
Installing kernel...
Dumping boot.img...
Unpacking boot.img...
Writing new boot.img...

Done!

Install from sdcard complete.
[G1 Android Development] farmatito:
Really don't know as I have the same phone, the same Spl, the same radio and flashed the same kernel and it worked for me.

Did you flash the BFS or non-BFS kernel?