yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] juangil:
same here, but I'm assuming this kernel is only for froyo?
[G1 Android Development] Telemaniaka:
Yeap, but so far hasn't been a deal-beaker
[G1 Android Development] farmatito:
If my spare time permits I will try to prepare a kernel with

autogroup patch instead of BFS, maybe this can improve

the touchscreen responsiveness.
[G1 Android Development] farmatito:
Should work on ginger to, but is tested only on froyo.....

until I install ezGinger again
[G1 Android Development] juangil:
thanks Formatito:)
[G1 Android Development] roalex:
Um this build dosn't work proper with the CM vold, been trying to revert what ever he merged with no luck so far, pretty odd since the 3.635-unified works with the new vold.
[G1 Android Development] farmatito:
What files exactly are connected with vold? I don't think that

I have touched something related to it but as my source

is from pershoot's kernel-2635 i suppose it is not ginger

compatible. Try to just copy over the relevant files from the cm-source.

Just pay attention to re-apply the adb-2.6.29 patch to plug BUG n1 battery drain.
[G1 Android Development] roalex:
Its the Android gadget ! for instance the usb tethering isnt working. i did try a sync no luck so far though. And yes is something in pershoot's sourcers not your patchs!
[G1 Android Development] leave:
TESTED that auto-boot-2.6.35.12-farmatito-pershoot-ds+-20110409.zip donot work on Magic 32A (TIM). It stucked on the first boot picture.

But another one compiled by roalex is ok, the file is 2.6.35.12_COS_kernels_05042011.zip

Please check out....

Thanks both of you, farmatito and roalex!
[G1 Android Development] lacus88:
+1, for me it was pretty annoying, bact to stock

And i'm using froyo by laszlo, and as far as I know it's a froyo rom :p
[G1 Android Development] farmatito:
Can you please try the latest autoboot as I think I've fixed

32a install process (the boot.img offset was wrong).
[G1 Android Development] farmatito:
Just out of curiosity did you use the BFS kernel or the autogroup kernel?
[G1 Android Development] lacus88:
I've tried the BFS (this: Latest Kernel with BFS), should I try the other one?
[G1 Android Development] jcarrz1:
its the bfs. it's notorious for that.
[G1 Android Development] leave:
Thanks, I'll try it tonight...
[G1 Android Development] farmatito:
It is worth a try
[G1 Android Development] sada23:
I am using 04092011 for my 32b, gingerbread ROM and it seems to be working good for me. Its about 23hrs since I disconnected from the AC adapter after fully charging it. The battery is now at 78% with occasional use of the phone for phone calls, wifi and Bluetooth. I am turning off the bluetooth and wifi GPS when I dont need them. Will continue to test.

Questions to Farmatito

1. What is BFS?

2. What is autogroup?

Sorry for being a noob.

Thanks a lot for your effort in solving this nagging problem.
[G1 Android Development] farmatito:
BFS http://ck.kolivas.org/patches/bfs/bfs-faq.txt

autogroup http://www.phoronix.com/scan.php?item=linux_2637_video&num=2&page=article
[G1 Android Development] sada23:
Thanks a lot.
[G1 Android Development] crypticc:
Liking 20110410 auto group. very responsive. Swiping, paused scrolling, etc.

So, but erm, pause, pause what's the downside?
[G1 Android Development] sisterchick:
The 20110409 autogroup kernel is a winner for me thus far! I'm currently running Froyo by Laszlo 5.2. Battery life seems good, it's snappy, metamorph/busybox work very well and no touchscreen issues. I'll have a more definitive word on the battery life tomorrow. Good job and thanks for trying to solve the old USB bug problem!
[G1 Android Development] d12unk13astard:
Newest 201104011 farm kernel is working even better then the previous 20110407 kernel i was impressed of. Theres no going back now you have solved the usb drain that has plagued so many of us g1 users.
[G1 Android Development] :
Thanks for fixing touchscreen bug!
[G1 Android Development] beav_35:
What radio is signed-boot-2.6.35.12-farmatito-pershoot-ds+-20110411-froyo.zip for? I flashed it on my 2708+ Dream and it was rebooting shortly after getting to the lockscreen. I then flashed 20110410 autokernel and it works great.

Btw, thanks for all your hard work fixing these bugs :D
[G1 Android Development] leave:
TESTED the 0410 version on my 32A. I flashed the BFS version, it is smoothly when play lossless music, and everything is ok now.

But in the "about phone" of settings, the kernel name doesn't contain "BFS" letters in it. Should it be added ?
[G1 Android Development] farmatito:
It could be added. Will see if I find some time to fix the build scripts.
[G1 Android Development] Dukenukemx:
Are these the first kernels with autogroup, bfs, and fixed usb drain bug? Also, can you have bfs + autogroup?

I'm happy to see the 200 line linux performance increase made it to a G1 kernal.
[G1 Android Development] farmatito:
Yes they are. No only BFS or autogroup.
[G1 Android Development] opalhair:
I flashed 20110410 autokernel and it works great,but the vpn is not work for me.
[G1 Android Development] sisterchick:
Draining

Uh oh...I'm afraid I may have spoken too soon. Running Froyo by Lazlo and autogroup 20110409, I'm draining pretty fast. Restarted after overnight charge and have lost 15% in less than 2 hours this morning on standby. 2G only, no wifi, GPS or bluetooth only GMail updating.

EDIT: Just ran same test with Orig Ezterry Biff 2708 2.6.34.7 kernel and lost <5% in 2 hours on standby vs 15%. Of course, not as snappy as 35.12 kernel. At the suggestion of another user, going to try the BFS kernel next.

Again, THANK YOU, FARMATITO for taking your personal time to work on this. I appreciate it.
[G1 Android Development] farmatito:
Some network modules are missing, will post new builds

when I have free time, maybe this evening...... Done.
[G1 Android Development] sada23:
Also, seems like it takes a very long time to charge the battery.
[G1 Android Development] farmatito:
Please test latest, as in a attempt to automatize the builds

I've broken some stuff in the last kernels.
[G1 Android Development] farmatito:
BFS kernel probably is more stable as merging the autogroup

patch with the bfs patch was a pain so there may be some

fallout.
[G1 Android Development] runderekrun:
Trying now. So far so good (17 minutes up).
[G1 Android Development] d12unk13astard:
I've had very nice battery life with the BFS kernel(latest) :)
[G1 Android Development] runderekrun:
Awesome. Unplugged from USB over an hour an hour ago (no restart) still at 100 percent.
[G1 Android Development] sisterchick:
Getting better all the time! BFS battery life was better for me than auto group. All times are far standby, basically.

Auto group 0409: 15% drop in 2 hours

BFS 0407: 8% drop in 2 hours.

Ezterry Biff 2708 2.6.34.7 : 5% in 2 hours (phone doesn't seem as snappy though)

Just saw you posted another update. Will try it next.
[G1 Android Development] runderekrun:
Darn.

3 and half hours in. Down to 91 percent, Android OS number one in battery stats.

This was using: auto-boot-2.6.35.12-farmatito-pershoot-ds+-auto-20110412.zip.
[G1 Android Development] farmatito:
Yes can confirm that the latest autogroup kernel drains battery

again. Think that I have messed up something while trying to tweak it. Will remove the autogroup kernels for now.

Testing a BFS build right now.
[G1 Android Development] :
Left phone on overnight unplugged, 97% after 7 hours. :)
[G1 Android Development] farmatito:
What build are you using BFS , auto and from what day?
[G1 Android Development] jcarrz1:
i've used this for 34 hours, it's been going great and the battery is still in the 40's.

i'm using the autogroup from 4/9. the bfs ones all suck because of the touchscreen.

I love your work, is the newest auto OK to try? which is the latest auto without the bug, is it the one i'm already using?

or have you fixed the bfs touchscreen yet (but i don't think it's possible, i remember when all of the hero 1.5 roms used it there was the same problem)
[G1 Android Development] d3vilskid:
I believe the 4/09 kernels where good with battery. I used bfs and don't expericence the issue with the touchscreen. The later build 4/10,4/11 and 4/12 stutters real bad and the same for autogroup except for 04/12. My experience on latest ads rom.
[G1 Android Development] sisterchick:
BFS 0412

Auto group 0409: 15% drop in 2 hours

BFS 0407: 8% drop in 2 hours.

Ezterry Biff 2708 2.6.34.7 : 5% in 2 hours (phone doesn't seem as snappy though)

Auto kernel BFS 0412: 13% in 2 hours
[G1 Android Development] jcarrz1:
something's wrong man. both me and e334 got the same 3%-4% drop overnight. and that's on 0409 autogroup.

awesome kernel, thanks farmatito.
[G1 Android Development] DorianX:
Can you or somebody post the "0409 autogroup" link please? I want to test it
[G1 Android Development] opalhair:
the new update vpn is not work too
[G1 Android Development] jcarrz1:
http://www.mediafire.com/?rqp7phpxk0ao3z2

thats autogroup 409
[G1 Android Development] DorianX:
Thanks man :D
[G1 Android Development] leave:
Where is the 32A version....
[G1 Android Development] leave:
What network modules are missing?

What is the effect?...

Waiting for the new 32A BFS kernel....

EDIT:

I made a mistake.... I forgot it is autogroup...:D

But why the cfs version bug again? and bfs version is ok?:eek:
[G1 Android Development] farmatito:
Try the auto-boot zip it contains eb0/eb1/2708 kernels

so in theory should work on 32a, in case it really boots

please report.
[G1 Android Development] farmatito:
Try auto boot zip.

Why?!? That's a good question....

Latest BFS should be ok.
[G1 Android Development] farmatito:
Can you post a config file of a kernel with working vpn.

Try:

adb pull /proc/config.gz config.gz

and post config.gz.

Will take a look at it if I ever will have enough spare time.
[G1 Android Development] leave:
Someone said this kernel doesn't work on the 32A with 6.35 radio...

And when I flash the kernel, the information is :

...boot.img...

repack boot.img...

flash new boot.img...

Why couldn't flash it once... like another one compiled by roalex, and his is smaller.

Thanks for your hard work!! It works perfect on my phone. I'm not using vpn, so I cannot test network problem now. But there is still no "bfs" word in the "about phone".
[G1 Android Development] farmatito:
Happy to hear installer works on 32a.

There is no BFS word in about phone dialog, so it is ok.

You can run this commands in a terminal after boot to see the BFS version:

dmesg | grep BFS
[G1 Android Development] opalhair:
I use ezBiffTestKernel20110222-2708
[G1 Android Development] runderekrun:
Yep, confirmed.

BFS kernel: up for 3 hours and 15 minutes, @ 99 percent battery (light use). No sign of Display or Android OS in battery stats.

Thank you! This WAS my single biggest annoyance with my G1 as of late.
[G1 Android Development] leave:
Why don't add it into the about information?

I have tried that command, but nothing happened..
[G1 Android Development] farmatito:
OK, will be in next build.
[G1 Android Development] sada23:
auto-boot-2.6.35.12-farmatito-pershoot-ds+-bfs-20110412 Working good on my G1 32b.
[G1 Android Development] farmatito:
Thanks for reporting it. I've uploaded a new build with minor

config changes. Hope it fixes the vpn issues reported (cannot

test it myself).
[G1 Android Development] aaraya1516:
any d/l mirrors?
[G1 Android Development] sada23:
The file for download on MU is not available as of now.
[G1 Android Development] d3vilskid:
mt 1.2

just tried the ebi0 kernel on the mytouch 1.2 and it does not boot, guessing the memory map for mt1.2 32a isn't inputted into the ebi0 kernels yet. so far new kernel update is running strong on my g1
[G1 Android Development] farmatito:
Have you a pointer to a patch so that I can add it?
[G1 Android Development] tom0769:
Having touch issues with auto-boot-2.6.35.12-farmatito-pershoot-ds+-bfs-20110412.zip.

Scrolling/switching between home screens is sluttering.

Pulling down notification bar is difficult.

Switching back to signed-boot-2.6.35.12-farmatito-pershoot-ds-32b-2708+-20110407-froyo.zip and touch is working fine.

Experienced this on BiffMod and Lazlo's rom.

Could bfs cause this?
[G1 Android Development] farmatito:
Could be, nonetheless I have no issues with touchscreen.

If I ever will have enough spare time I will post a version

without BFS just to compare it.

BTW: did you try latest 20110414?
[G1 Android Development] tom0769:
I did:

signed-boot-2.6.35.12-farmatito-pershoot-ds-32b-2708+-20110407-froyo.zip => touch ok

auto-boot-2.6.35.12-farmatito-pershoot-ds+-bfs-20110412.zip => touch issue

auto-boot-2.6.35.12-farmatito-pershoot-ds+-bfs-20110414.zip => touch issue

signed-boot-2.6.35.12-farmatito-pershoot-ds+-20110411-froyo.zip => touch ok

Tested it also on Ofiicial AOSP 2,2 OTA rom, same results.

I think it's the bfs that causes this.
[G1 Android Development] rattking:
I was looking at the updater-script today and I think the auto-kernel is installing to the wrong --base address for the 1.2/fender

I changed this

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"
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","bootloader") == "1.33.0013"
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.sh");
endif;
endif;
endif;

the Fender has a smisize of 32 (not positive about 1.2) and stock hboot of 1.33.0013

then copied mkbootimg.sh changing to --base 10000000 to mkbootimg-12.sh

is this the correct way to detect Fender/1.2 phones?
[G1 Android Development] farmatito:
I don't know as I don't have this hardware, but we will see it soon ;-)

I've added your changes to the script. Thanks for your time and effort.
[G1 Android Development] farmatito:
A new kernel without BFS for you to test. Enjoy
[G1 Android Development] farmatito:
Could you please test latest as I've added some installer fixes from rattking. Enjoy.
[G1 Android Development] ezterry:
32b = smi size 64

32a = smi size 32

Here is the logic from the ezGingerbread script:

#determine if we need to patch a boot image
#This will work for all known cases besides the new radio with
#an old SPL on a 32b phone.. where none of our 3 common kernels work
if file_getprop("/tmp/nfo.prop","radioseries") == "3.22"
then
#EBI1 kernel needed
ui_print("Extracting EBI1 patch");
#Install EBI1 kernel (both 32a/32b)
else
#EBI0/2708 kernel needed
if file_getprop("/tmp/nfo.prop","smisize") == "64" &&
( file_getprop("/tmp/nfo.prop","bootloader") == "1.33.0011" ||
file_getprop("/tmp/nfo.prop","bootloader") == "1.33.2011" ||
file_getprop("/tmp/nfo.prop","bootloader") == "1.33.3011" ||
file_getprop("/tmp/nfo.prop","bootloader") == "1.33.0013" ||
file_getprop("/tmp/nfo.prop","bootloader") == "1.33.2013" ||
file_getprop("/tmp/nfo.prop","bootloader") == "1.33.3013" ||
file_getprop("/tmp/nfo.prop","bootloader") == "1.33.0013d" ) &&
( file_getprop("/tmp/nfo.prop","baseband") == "2.22.27.08" ||
file_getprop("/tmp/nfo.prop","baseband") == "2.22.28.25" )
then
#2708 kernel (unless the user has the fake Crios SPL 1.33.2013 ENG)
# if the fake version they will fail to boot since its really
# 1.33.2005...
if file_getprop("/tmp/nfo.prop","bootloader") == "1.33.2013"
then
ui_print("1.33.2013 detected, please ensure this is not Crios SPL 1.33.2013 ENG; as its really 1.33.2005");
endif;
ui_print("Extracting 2708+ patch");
#install 2708+ kernel (32b only with both new radio and SPL)
else
#EBI0 kernel
ui_print("Extracting EBI0 patch");
#install EBI0 kernel (includes all fender and MT2.1 even with new SPL 1.33.0013d)
endif;
endif;

Remember however you must always set the base address properly both when building your kernel and generating the boot.img from that kernel:

EBI0 = 0x10000000

EBI1 = 0x19200000

2708+ = 0x02000000
[G1 Android Development] farmatito:
I've merged koush's anykernel with the logic in your script,

so it should work, but as rattking pointed out I've forgotten to set the base address for the initrd correctly.

I suppose the kernel build system should do this automagically depending on the selected config options,

at least this is my guess by looking at this code in

arch/mach-msm/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
[G1 Android Development] opalhair:
Are you fix the vpn bug?
[G1 Android Development] leave:
Yes, it exists in 32A kernel too..

I have noticed it, but I thought it was my finger having sth wrong...

I'll test the 0415 version of BFS..
[G1 Android Development] farmatito:
I hope but I cannot test it so please try latest and report if it

works for you.
[G1 Android Development] sisterchick:
Good job! Thank you!

auto-boot-2.6.35.12-farmatito-pershoot-ds+-20110415.zip is running very well on my G1. No stutter on screen and dropped less than 1% an hour overnight on standby. Good job and thank you!

PS: Running Froyo by Laszlo 5.2
[G1 Android Development] ThdDude:
BFS from 0415 scrolling is laggy on Ginger Yoshi and COS D/S other 0415 kernel is smooth. Testing it today
[G1 Android Development] mzmo:
Is it the "2.6.35.12-patches-20110415" attachment?
[G1 Android Development] crypticc:
nope - those are patches for devs. you need one of the megaupload links just above that.
[G1 Android Development] mzmo:
Oooh! Cant believe I missed that. Thanks.
[G1 Android Development] sisterchick:
This one:

Latest Autokernel without BFS:

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

http://www.megaupload.com/?d=0LNDSTY6
[G1 Android Development] d3vilskid:
just flashed kernal on mt3g 1.2 and it booted fine, thanks farm. Oh one quick question does the kernel for mt3g 1.2/fender comes with the 10mb hack?
[G1 Android Development] leave:
Yes it is laggy too on my 32A.

a touch issue caused by BFS...
[G1 Android Development] :
Lol.. I just found out what "BFS" actually stood for...
[G1 Android Development] mezner:
auto-boot-2.6.35.12-farmatito-pershoot-ds+-20110415.zip

VPN (PPTP) works. Feels a little more responsive too, rom is FroyoByLaszlo 5.2, awesome job, thumbs up.
[G1 Android Development] farmatito:
I guess not.
[G1 Android Development] fooby_sjz:
hello,you are very good.but i cannot download it from the site (http://www.megaupload.com),beacause i am in China.can you put it on another site for us in China.thanks !!
[G1 Android Development] farmatito:
What site is best for China?
[G1 Android Development] Brut.all:
I suggest you to use multiupload.com . I had a lot of problems with hosting Google Maps mod, because some services remove files, others aren't accessible worldwide, etc. Multiupload has solved my problems :-)
[G1 Android Development] opalhair:
vpn is work,thanks!
[G1 Android Development] d3vilskid:
heres the link to the patches ezterry did for the classic 32a and mt3g 1.2/fender

http://xdaforums.com/showpost.php?p=11565574&postcount=670
[G1 Android Development] farmatito:
Thanks, the patch for Magic Plus (32a) was missing even if contained in the patches zip.The other patch was correctly applied. Will post a new build asap.
[G1 Android Development] fooby_sjz:
it is ok for the http://www.multiupload.com in China to download.300kb/s,it is very fast,but also need foxyproxy in firefox.very good!thanks!!!
[G1 Android Development] fooby_sjz:
hello.my MT1.2 is

can i use it ?
[G1 Android Development] d3vilskid:
Yea the kernel will work on the mt3g 1.2
[G1 Android Development] Namit1994:
Hey thanks for this kernel. Saves a LOT of battery juice. I have one problem, I am using Artifexed Legend and when I open the camera app, the camera stays black. Can you fix this? Thanks.
[G1 Android Development] farmatito:
No I don't think I can fix it. Sorry about that.

Maybe you can try to push the camera.apk from

some know to work rom (e.g. enomther).

Make a backup first.

PS.: you could also post a kernel config of a working kernel just out of curiosity

to see what is different.
[G1 Android Development] Namit1994:
How do I do that?
[G1 Android Development] :
That would ruin the point of having a HTC Camera App... I think it is driver issue, not the app itself but I could be wrong.. wouldn't hurt trying
[G1 Android Development] Namit1994:
The app worked with ezterry's 2708 kernel but not with this one. Does that make it a driver issue or is it the kernel?
[G1 Android Development] farmatito:
The only difference I can see in the config files is:

# Qualcomm MSM Camera And Video
#
CONFIG_MSM_CAMERA=y
-# CONFIG_MSM_CAMERA_DEBUG is not set
-CONFIG_MSM_CAMERA_OLD=y
# CONFIG_720P_CAMERA is not set
+# CONFIG_MSM_CAMERA_DEBUG is not set

that ezterry uses OLD camera, but as my camera

worked with his kernel and works also with mine

I suppose it is some form of bad interaction with

the userspace files. I recall having solved a similar

problem (black screen after installing a new rom)

by wiping the camera data (I guess in

/data/data/com.android.camera ).

Hope this helps.
[G1 Android Development] hrk:
Unless it's too much OT, what is the difference between the "old" and "new" camera drivers?
[G1 Android Development] Namit1994:
It didn't work. No other suggestions?
[G1 Android Development] farmatito:
Don't know yet, maybe HTC camera vs Aosp camera, with userspace that needs different libs or sys/ dev/ files because my camera worked with both kernels.

Sadly at the moment no time to look at it. Maybe ezterry knows the difference...
[G1 Android Development] leave:
Hi farm..

the BFS version have some touch issue on 32A too...

I flashed the CFS(is this name right?) version now... this one don't lag when scrolling screen.
[G1 Android Development] farmatito:
I think I will discontinue the BFS version, as it is easier to maintain only one version.
[G1 Android Development] cellsafemode:
Hi Farmatito, Can you submit these kernels to the kernel manager site so they can be retrieved and dealt with through that app? It would be nice to finally get some Magic kernels on there. My 1.2 just experienced some nasty battery draining after being plugged into usb over night and as far as i've seen this is the only option to fix the issue.

Also, is it normal to have excessive battery drain for a couple reboots after unplugging from USB ? If so, how? I had to reboot my phone 3-4 times before i started seeing battery drain look somewhat normal. By then though it was down to 49% from 80% 30 min prior.
[G1 Android Development] farmatito:
One reboot usually is enough for the usb drain, but there was

other factors that prevented the phone to sleep correctly and

contributed to drain. Do you have a link to this kernel manager site?

To be honest I've no spare time to support all roms out there

as each one has it subtle incompatibilities. I would prefer the

that rom cooks add the relevant patches to their kernel repositories.
[G1 Android Development] cellsafemode:
(link removed)

It basically allows people testing your kernel to do so (and switch and manager other kernels) right from the app in a simple streamlined process. There is no real need to try to support various mods and such. Other than some basic things like describing what hardware your kernel is for and maybe a changelog ....users are expected to know what they're doing.
[G1 Android Development] farmatito:
I took a look at it, but I don't think I will support it.

Sorry about that.
[G1 Android Development] leave:
Oh....what a pity.

I like BFS because it could play APE smoothly..
[G1 Android Development] djmeistro:
thank you

Thanks for the work farm...using your latest kernel along with setcpu on 122 122 when screen is off...good battery life with moderate use