yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] sada23:
Yes I did overclock my phone to 595.
[G1 Android Development] aaraya1516:
Thanks

I just wanted to say thanks for your work.

Flashed the 5/18 BFS kernel to CM7 experimental and CompCache works like normal. Thanks again!
[G1 Android Development] askrulous:
Battery life didn't seem that good on my magic with gingeryoshi 1.1(shame I haven't really monitored it properly before while on other roms), so I thought I should give your very latest kernel a try. Flashed ok, everything works fine.

Battery just dropped 10% in half hour while testing phone so not looking good.

Wondering if my radio needs changing now, or maybe other settings.

Thanks for all your work!
[G1 Android Development] jonnyj771:
I noticed the same thing...dropped 4% right after flashing...the android system in the battery stats was @ 10% or so an hr ago. Wasn't there with the 05052011 kernel.
[G1 Android Development] darkguy2008:
Well, right now I'm at 89% with:

After unplugging it from work and taking 1hr to get back home and playing some music through bluetooth at max volume :P. I don't consider it too bad, since my battery lasts like 18-20 hrs or so.
[G1 Android Development] Maxamillion:
Has anyone tried this with froyo by lazlo?
[G1 Android Development] jonnyj771:
went back to the 05052011 due to excessive battery drain on my way home looking at facebook and getting major lag issues. when i first flashed it to my phone, my battery drain wasn't so bad, my wife calls and she said she tried 3 times before and got voicemail each time, not a ring first. the kernel lagged bad the entire day. i didn't have these issues with 05052011 though. I will stick with that for now and see what happens.
[G1 Android Development] tom0769:
Actually using for some weeks now the 0428 non-bfs froyo kernel with customized laszlo rom, atm (with light use, most time in standby):

114h up-time (41% Cell standby, 22% Phone idle, 15% Display, 9% Android System, 6%Android OS,...)

45% battery left

still stable without fcs and fast at 537..614MHz ondemand

no taskkiller

customized minfree settings

no cc, swap and jit

So for me it could not be better:D
[G1 Android Development] dilwaladoctor:
20110518 BFS Kernel is extremely superb.

Brilliant Farmatito. You are a genius.

Trillion Thanks.
[G1 Android Development] R3N0V4D0:
can you make a nandroid backup without your personal stuff?
[G1 Android Development] darkguy2008:
Yeah, and what are your customized minfree settings and swap/cc/jit? :O
[G1 Android Development] tom0769:
Hmm, how could I make a nandroid backup without my personal stuff:confused:

Look here: http://xdaforums.com/showpost.php?p=13977709&postcount=1642
[G1 Android Development] askrulous:
So did I jonny, did a restore as well. Battery drain was bad. Apps disappeared, phone froze, lag, the lot. Major probs caused by kernel - weird how its good for some, yet bad for us.
[G1 Android Development] R3N0V4D0:
do a nandroid of your rom currently, then remove all of your contacts and gmail info (master reset) then nandroid that and upload it, then restore your original nandroid :)
[G1 Android Development] OMAKE:
Thanks for the good kernel! But, is it possible to remove 034-10mb_32A.patch from the kernel somehow? Some games is unplayable now.
[G1 Android Development] darkguy2008:
How so? I'm curious about that patch. What does it do to make games be unplayable?

Also, I'm kinda curious... some games which require touchscreen lag really BAD when I touch the screen instead of using the trackball, and doing so makes them really unplayable, is this kernel-related?
[G1 Android Development] ezterry:
unless your game uses the camera in an odd way.. or you are attempting to use this kernel on pre-froyo roms.. I fail to see how the 10MB extra ram can make a game fail to play.. (and I'm not quite sure how a pre-froyo rom is an issue here.. since that is still camera related)

I think you are confusing the old 32b memory hack (for pre-eclair) where vram was removed in favor of extra 8 (ebi1) or 9 (ebi0) megs of ram.. the new "hacks" are actually officially done on the latest OTAs and reclaim some camera ram no longer needed with the newer libcamera.so that moves anything not required to be in the static region to general ram.
[G1 Android Development] tom0769:
With that I will end up in a more or less virgin rom.

Take a look at my sig, that is, I think, what you probably want.;)
[G1 Android Development] robuser007:
wireless thether does work with cos-ds and bfs 18/05 !!!!
[G1 Android Development] ZaneChua:
I tried your ext4, i got a lot of force closes for just the messaging app. No idea why.
[G1 Android Development] tom0769:
Never had any issues with messaging.
[G1 Android Development] azrash:
Try running fix_permissions, or clear messaging data under manage apps
[G1 Android Development] ZaneChua:
Guess i'll try it again. Meh.

EDIT: And you were talking about integrating that script so you wouldn't have to run it everytime? I'm working on it. Though i need a linux box. I don't have one. fff. It's 3am now so i'm not gonna work on it. Later. Unless you wanna do it for me? Then i won't have to get a linuxbox. ;P.

Add to init.rc at the bottom

# run AMM Memory Sizes Script
service amm /sbin/amm.sh
oneshot

Place your code into a file called amm.sh

#!/system/bin/sh
# Values are given in 4k units!
# Foreground App, Visible App, Secondary Server, Hidden App, Content Provider, Empty App
echo "2048,3072,5120,7680,10192,25600" > /sys/module/lowmemorykiller/parameters/minfree

Place amm.sh into /sbin and init.rc into boot.img?

Repack. :d
[G1 Android Development] darkguy2008:
I made a way to run startup scripts in a generic-ROM way as long as it has init.d functionality. I'll post it shortly once I get back from work :)
[G1 Android Development] ZaneChua:
That should help, since i'm having a hard time to get boot.img to work. -_-
[G1 Android Development] darkguy2008:
Okay, good luck :)

1. Create bash script with this (name it as "90scripts" or something):

#!/system/bin/sh
if [ -e /data/local/scripts ] then
sList=`ls /data/local/scripts/*.sh`
for myScript in $sList
do
sh $myScript
done
fi

2. Push the file:

adb push 90scripts /system/etc/init.d/90scripts

3. Set the right permissions:

adb shell
# chmod 0750 /system/etc/init.d/90scripts
# chown 0:2000 /system/etc/init.d/90scripts

4. ???

5. Profit! xD

Add your startup scripts in /data/local/scripts/, chmod +x them, and you're good to go. I can confirm this is working on my currently running HTC Magic :).

Don't forget to give thanks & credit :D xD
[G1 Android Development] ZaneChua:
Oh wait. But this means i have to have

/system/xbin/busybox run-parts /system/etc/init.d somewhere in the init.rc right? i dont..
[G1 Android Development] darkguy2008:
Actually, yeah, somewhere around 20userinit. Uh, well, add it? o.O I might find a way to add such stuff soon... :P
[G1 Android Development] ZaneChua:
adding it to init.rc means i have to unpack boot.img and repack it. I just mentioned that i have problems with it when i pack it back. When i repack my own boot.img, the phone just fails to boot and is stuck at the splash screen.
[G1 Android Development] VAMCAVALO:
I'm using froyo by laszlo with the 2804 farmatito's kernel

my battery only last a day if I use my phone at standby almost fulltime

one problem that I can see it is when I am charging it takes almost a day to achieve 100% battery; but if I reboot at 35% or more, when it turns on, show 100%.

It's a Battery (hardware) problem or a ROM (software) problem?

Thanks!
[G1 Android Development] darkguy2008:
Hey I've been kinda getting the same thing. I'd like to know too, who to blame? :P - or what to fix! o.o
[G1 Android Development] farmatito:
looks like a battery problem to me.
[G1 Android Development] azrash:
just ordered a new battery, hope it will solve the weird issue
[G1 Android Development] tom0769:
I sometimes observe, that the battery drains (without any usage of the phone) aprox. 10% per hour. Going to setting->info->battery usage I see that the Android OS occupies the cpu with over 60% and not the standby.

This means the phone is not really sleeping.

This happens after fully charging the phone disconnecting power plug (but not everytime I do this).

If I observe such a battery drain, I go to seetings->application->services and kill all services once. After that, the battery drain in standby decreases to almost nothing.

Could not figure out which app or service is responsible for this so far.

Normally I'm getting up to 6 days up time (most in standby) out of my phone.
[G1 Android Development] farmatito:
That's what I get to, about 6-7 days in standby. Would be nice to know what is causing

this other drain, try to run top in a terminal next time or try to kill the services one at a time.
[G1 Android Development] xillius200:
hey formattio lol how long do you think before we will get android kernel 3.0?? lol seeing linux kernel 3.0rc1 is out xD
[G1 Android Development] farmatito:
I think I will stick with 2.6.35.xx longterm for now and eventually

backport some cherrypicked patches at least as long as 2.6.36

has battery drain problems. You know: "New kernel, new bugs"
[G1 Android Development] darkguy2008:
Aw, but man, I'm dying for a new kernel with better speed and such.

Also, not being able to mount an .img file in /dev/block/loopX or /dev/loop failing with Invalid Argument or No Such File or Directory is the Kernel's fault?

Or, to rephrase my question: Does this kernel have loop support & ext2/3? It might be a dumb question, but I wanna make sure, too, because I've been having some problems and that's what stuff on google suggest, but I don't think this kernel is missing such features, right?
[G1 Android Development] houlalajaimal:
ssl connection

Hi,

I use the 2.6.35.13-farmatito-pershoot-ds-BFS kernel with 2.3.4 Yoshi ROM and I have some trouble with ssl on smtp.

Is there some people with same trouble here ?
[G1 Android Development] tvall:
3.0? O.o

Now I know what my computer will be doing while I'm in school today lol.
[G1 Android Development] farmatito:
No it has loop dev support:

CONFIG_BLK_DEV=y

# CONFIG_BLK_DEV_COW_COMMON is not set

CONFIG_BLK_DEV_LOOP=y

Have you tried this:

# Device compatibility
for i in 0 1 2 3 4 5 6 7;
do
busybox ln -s /dev/block/loop$i /dev/loop$i;
done;

as busybox's mount expects /dev/loopX to be there.
[G1 Android Development] farmatito:
Looks to me that it is nothing more than a renumbered 2.6.40

so there is no need to hurry ;)
[G1 Android Development] tvall:
I know. I usually run the rc kernels at rc2 or 3. but I like the idea of running linux 3.0 So I'm gonna jump in at rc1. How hard would it be to build this for the g1/magic? Lol
[G1 Android Development] darkguy2008:
Well, turns out the .img got damaged while unzipping it from the very terminal itself. I had to copy it manually instead :(.

Still, that script could prove useful, since you're right, busybox expects those links to be there and there's a lot of disaster being caused by some scripts made for other phones which have (or don't) those symlinks :) Thanks!
[G1 Android Development] VAMCAVALO:
It could be a battery problem?

Unfortunately but thankfully there are more people with the same problem

My drain it is about 15%/hour at standby until the battery reachs something about 25%. After this, it drain so quickly that I can't do nothing; it happens on 15 minutes to drain the 25% remaining.

I don't know what to do, I suppose changing every thing (rom, kernel) but I like so much this ROM and it runs so smooth that I can't uninstall..

What should I do? I tried to kill the services, but I didn't see any difference.

Thank you!
[G1 Android Development] tom0769:
Which rom do you use?
[G1 Android Development] tom0769:
Deleted Google Maps and now it seems that the drain is gone (so far).

I noticed that NetworLocationService keeps running, even when maps is closed.

Could not kill the service, always restarting immediately.

With deleting maps the service does not restart.

I think this came with the latest versions of maps.
[G1 Android Development] VAMCAVALO:
Froyo by Laszlo

Why?
[G1 Android Development] tom0769:
I'm using froyo by laszlo too.

I've got an uptime of 3..6 days, depending on usage.

I dont' use ext, cc, swap or jit.

I dont' use a task killer, just customized the minfree settings to my needs.

I recently deleted google maps since it permanently keeps running network location service in background.

Just see my sig for more info;)
[G1 Android Development] darkguy2008:
Hey, is it possible to add this patch to the kernel?

http://xdaforums.com/showthread.php?t=929941

I know, it isn't very detailed (I'd like to know the changes he made, too), but I tried to get a diff from this kernel and that kernel and found that HTC Magic 32A's use the synaptics touchscreen driver (synaptics_i2c_rmi.c) and the patched one over there is the mcs6000_ts.c one. Both located at /drivers/input/touchscreen.

Reason is: some games (such as Gun Bros, Angry Birds, etc) that require touchscreen input lag heavily when touching the screen. I thought it was the game's fault, so I made a simple app to try, which purpose was to clear the screen setting the screen color based on the touchscreen X&Y position using GLSurfaceView.

Testing on the device turns out that I get around 40-60 FPS with the app doing nothing, and when I touch the screen it goes down to 20-30 FPS. No wonder why the games lag really bad.

I'm greatly interested in getting that modification applied and I'm willing to test and develop (if I find a good android kernel-building guide for Win/Linux, which I haven't yet), because, man, this is really bad for us game developers :(
[G1 Android Development] ichijin:
This seems really interesting.
[G1 Android Development] farmatito:
Upadated Experimental Standard Autokernel for Gingerbread

with autogroup patches and memory compaction:

V 20110612

* Compensate for rounding on odd-frequency clocksources

* zImage fixes

* Enable Memory Compaction

* wifi - Don't make disabled irqs wake the device

* cache-l2x0: Correct l2x0 initialization

* autogroup patches

NO WARRANTY. USE AT YOUR OWN RISK.

Enjoy.
[G1 Android Development] darkguy2008:
Awesome!

Does that kernel include BFS 404 too? In my case it's very important since it makes my phone like 100 times more responsive :)

Also, did you read what I posted about the touchscreen lag fix?
[G1 Android Development] Maxamillion:
Has anyone used the new kernel with cos-ds? Is it better than than the stock cosds kernel?
[G1 Android Development] d3vilskid:
I'm using the new kernel on ads magpie and I must say it speed everything up greatly. My wife phones mt3g has it and is running the 2.3.3 gb with 2.1 sense beta and the kernel improved its speed.
[G1 Android Development] farmatito:
No, autogroup and BFS don't play well together.

I read it, but it seems to me that it refers to a different driver.
[G1 Android Development] darkguy2008:
Oh okay, so autogroup is some kind of different BFS? or are they unrelated altogether?

True, it's for a different driver. The core idea was to see if the msleep() implementations could be done in the same way for the synaptics driver, or at least see what's wrong or what can we do to avoid such massive lag when touching the screen.
[G1 Android Development] robuser007:
Could you also solve the bluetooth drain issues ?

I don't think I can use this kernel on cos-ds.
[G1 Android Development] darkguy2008:
Is there a bluetooth drain issue? :/ I'm using this on GY...
[G1 Android Development] farmatito:
Will take a look at it, but I cannot test it as I use 2708 radio myself.

In my tests I get a a constant power draw of 4% (of a 2300 mAh

battery) per hour if rebooting while connected to a usb port.

The phone wakes up for an irq 109 call and a SMD_RPCCALL.

IRQ 109 in my findings maybe is related to msm_serial_hs

but i don't know why it is triggered (have to test yet if it is

also triggered if rebooting without usb connected).

<6>[15203.500457] wakeup wake lock: SMD_RPCCALL
<6>[15203.503936] PM: resume of devices complete after 4.512 msecs
<4>[15203.505340] Restarting tasks ... done.
<6>[15203.522094] suspend: exit suspend, ret = 0 (2011-04-03 18:30:45.408658537 UTC)
<6>[15203.557952] PM: Syncing filesystems ... done.
<4>[15203.560485] Freezing user space processes ... (elapsed 0.03 seconds) done.
<4>[15203.594360] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
<6>[15203.626281] PM: suspend of devices complete after 11.250 msecs
<6>[15203.627685] PM: late suspend of devices complete after 0.579 msecs
<6>[15203.628173] Wakeup IRQ 109 pending, suspend aborted
<6>[15203.629180] PM: early resume of devices complete after 0.243 msecs
<6>[15203.632446] wakeup wake lock: SMD_RPCCALL
<6>[15203.636260] PM: resume of devices complete after 6.432 msecs
<4>[15203.637298] Restarting tasks ... done.
<6>[15203.654815] suspend: exit suspend, ret = 0 (2011-04-03 18:30:45.541219512 UTC)
<6>[15203.698059] PM: Syncing filesystems ... done.
<4>[15203.700958] Freezing user space processes ... (elapsed 0.03 seconds) done.
<4>[15203.734191] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
<6>[15203.766174] PM: suspend of devices complete after 10.975 msecs
<6>[15203.767211] PM: late suspend of devices complete after 0.548 msecs
<6>[15203.768035] Wakeup IRQ 109 pending, suspend aborted
<6>[15203.768737] PM: early resume of devices complete after 0.243 msecs
<6>[15203.772399] wakeup wake lock: SMD_RPCCALL
<6>[15203.775909] PM: resume of devices complete after 6.189 msecs
<4>[15203.777282] Restarting tasks ... done.
<6>[15203.793701] suspend: exit suspend, ret = 0 (2011-04-03 18:30:45.679969512 UTC)
<6>[15203.838195] PM: Syncing filesystems ... done.
<4>[15203.840759] Freezing user space processes ... (elapsed 0.03 seconds) done.
<4>[15203.874664] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
<6>[15203.905975] PM: suspend of devices complete after 10.609 msecs
<6>[15203.907348] PM: late suspend of devices complete after 0.548 msecs
<6>[15203.907836] Wakeup IRQ 109 pending, suspend aborted
<6>[15203.908874] PM: early resume of devices complete after 0.243 msecs
<6>[15203.912139] wakeup wake lock: SMD_RPCCALL
[G1 Android Development] farmatito:
Preliminary diagnosis of usb battery drain bug n2:

by comparing the dmesg of a battery draining and non draining kernel:

WITH DRAINING

<6>[15203.217590] Wakeup IRQ 109 pending, suspend aborted
<6>[15203.218292] PM: early resume of devices complete after 0.243 msecs
<6>[15203.221923] wakeup wake lock: SMD_RPCCALL
<6>[15203.225494] PM: resume of devices complete after 6.219 msecs
<4>[15203.226867] Restarting tasks ... done.
<6>[15203.243438] suspend: exit suspend, ret = 0 (2011-04-03 18:30:45.130274391 UTC)
<6>[15203.287658] PM: Syncing filesystems ... done.
<4>[15203.290222] Freezing user space processes ... (elapsed 0.03 seconds) done.
<4>[15203.324127] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
<6>[15203.355773] PM: suspend of devices complete after 10.975 msecs

WITHOUT DRAINING

<6>[ 334.138092] [R] resume start
<6>[ 334.138580] PM: early resume of devices complete after 0.457 msecs
<6>[ 334.139404] wakeup wake lock: SMD_DS
<6>[ 334.144897] PM: resume of devices complete after 4.756 msecs
<4>[ 334.146331] Restarting tasks ... done.
<6>[ 334.187255] suspend: exit suspend, ret = 0 (2011-04-04 10:23:03.542530327 UTC)
<6>[ 334.636169] PM: Syncing filesystems ... done.
<4>[ 334.638671] Freezing user space processes ... (elapsed 0.02 seconds) done.
<4>[ 334.664062] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
<6>[ 334.695495] PM: suspend of devices complete after 10.609 msecs
<6>[ 334.696868] PM: late suspend of devices complete after 0.548 msecs
<6>[ 334.696868] [R] suspend end

The shown messages repeat themselves for most of the log.

In the first case I get a draining of about 4%/hr of a 2300mAh

battery, in the latter more or less 1%/hr.

By looking at snippet 1 I've tried to identify where this

irq 109 comes from and by looking at the sources:

in arch/arm/mach-msm/include/mach/irqs.h

#define MSM_GPIO_TO_INT(n) (FIRST_GPIO_IRQ + (n))

#define FIRST_GPIO_IRQ (NR_MSM_IRQS + NR_SIRC_IRQS)

in arch/arm/mach-msm/include/mach/irqs7x00.h

#define NR_MSM_IRQS 64

#define NR_SIRC_IRQS 0

so:

109 = ((64 + 0) + n)

n = 45;

and in board-trout.c

#ifdef CONFIG_SERIAL_MSM_HS

static struct msm_serial_hs_platform_data msm_uart_dm1_pdata = {

.rx_wakeup_irq = MSM_GPIO_TO_INT(45),

.inject_rx_on_wakeup = 1,

.rx_to_inject = 0x32,

};

#endif

It seems to me that the "serial_msm_hs" gets somehow

activated when booting with a usb cable plugged.

I've tried to compile serial_msms_hs as a module but it

breaks bluetooth so it is not a viable solution, I've also

applied some updates from the htc vivo sources with no luck.

If there is somebody more experienced in this kernel

stuff hints or help is appreciated as I'm already far beyond

my skills. These findings are obviously speculative so

I may be totally wrong, also in this case hints or help is appreciated.
[G1 Android Development] VAMCAVALO:
I think my battery problem happens because the system cannot see the amount of charge is in it. When the phone shuts off by itself, the LED keeps blinking in red and if I take off the battery and put in again the cell phone starts to vibrate and only stops if I try to turn on by pressing the red button. I let it vibrate for a while until it stops but that is a sign of some charge remaining at the battery
[G1 Android Development] roalex:
Wouldn't it be better to focus (as in submit patches and so on) to ezgb-2636 at ezterry/kernel-biff-testing (github.com/ezterry) ? Doesn't look like we have anything else going on at this point :) from there its probably pretty easy to go for .37 and .38.
[G1 Android Development] farmatito:
Yes of course, but if the drain is also in .36 in the meanwhile

I can learn a little more. At the moment I messed it up

completely my battery/charger is not even recognized.
[G1 Android Development] rattking:
Hi, First of all let me say thanks to all that are working on this drain bug!

I have been able to reliably trigger this (and hopefully not another) `Wakeup IRQ 109 pending, suspend aborted` bug using my stereo bluetooth headset..

By enabling bluetooth and connecting the headset then disabling bluetooth on the phone. hit the end button (set to sleep in cm parts) dmesg fills with Wakeup IRQ 109 warnings.. when I re-enable bluetooth they stop.. and this is without connecting a usb cable at all.

i tested this on my kernel build 2.6.35.12 and auto-boot-2.6.35.12-farmatito-pershoot-ds+-20110403. but It doesn't seem to happen in ezterry's ezgb-2636 (dang green tint bug)
[G1 Android Development] ezterry:
I keep trying to change any logic change from the screen setup in that patch (there is not supposed to be any.. just adding support for other phones) and none of it seems to fix the green... of course I have the problem of not being able to test it myself.. not having the green issue..

the non working wifi is my top priority on 2.6.36.* however

(The other odd bug is a camera JPEG encoding error when you take a picture as a zoom > 1.0)
[G1 Android Development] rattking:
Yea I see that.

tiwlan_module_init: Timed out waiting for device detect

well if there is anything I can do to help with then green tint bug let me know.. feel free to e-mail or pm me
[G1 Android Development] d3vilskid:
I know its trivial stuff, but lately with the .35 kernels the home, menu and end button doesn't soft reboot the phone, like the previous kernel.
[G1 Android Development] mercenaryhmster:
the 3 finger salute still works, you just need to hold the buttons down longer.
[G1 Android Development] farmatito:
So far after 20h 22m battery charge is still 99%

the latest kernel looks pretty good to me. Phone

sleeps well and lasts long.
[G1 Android Development] sada23:
That's pretty impressive. You mean the test kernel with Bug2 fixed?