[Galaxy S I9000 General] pwhooftman:
Update #1

Update 1:

- i have found that disabling "use networks to determine location" reduces the amount of time the cpu is at 30%, but does not prevent it alltogether. This afternoon, the CPU still was at 30+% for about 15 minutes into the 1 hour journey, then settled down.

- as soon as i leave a wifi area, or enter one (without the phone necessarely being connected), the log shows exactly 50 times the following error. This is not the cause however:

[ 09-15 17:58:19.450 4506:0x315e I/System.out ]

1316102299454 - ERROR - Failed to connect to "ssl://null"

[ 09-15 17:58:19.450 4506:0x315e I/System.out ]

java.io.IOException: Invalid url: null -

I did find a clue:

- After a reboot, the cpu usage is very low, hovering between 0% and 1%.

- "DalvikM GC_CONCURRENT freed " log entries are minimal (indicating memory is clean and doesn't need garbage collection)

- "ENTER DORMANCY" log entries are absent

- after some hours of phone use, "ENTER DORMANCY" entries start appearing at a rate of approx. 1-2 per minute.CPU rises to 1-3%

- when starting the journey,the "ENTER DORMANCY" entries rise to a rate of one exactly every 5 seconds

- when the cpu drops, the rate of "ENTER DORMANCY" has reduced to 1-2 per minute also.

The complete log entries every 5 seconds are made up of the lines below. Fast Dormancy is a way to put the data connection to the idle state once data traffic has stopped. Its a technique to reduce data (and battery) usage. So, i'm facing some kind of wake-lock issue. I'm trying to find the cause, so far i have ruled out Google Location Services (which does reduce the problem but does not stop it), Bluetooth, Talk. I seem to be looking for something with a cycle of 5 seconds (wifi- or 3G rescan of some sort?). I'll look into the hints given (Facebook, keeping the phone in a spot with maximum signal while travelling). I have also read many times that this problem has started with Gingerbread.

[ 09-15 17:07:40.640 725:0x2d5 D/FastDormancy ]

before ======= ENTER DORMANCY =======

[ 09-15 17:07:40.640 725:0x2d5 D/FastDormancy ]

[FD] ON default: true

[ 09-15 17:07:40.643 725:0x2d5 D/FastDormancy ]

Before mDormFlag: false in getCapaDormancy()

[ 09-15 17:07:40.646 725:0x2d5 D/FastDormancy ]

After mDormFlag: false in getCapaDormancy()

[ 09-15 17:07:44.619 965:0x3c8 W/ ]

dm_pm_timer expires

[ 09-15 17:07:44.619 965:0x3c8 W/ ]

dm_pm_timer expires 0

[ 09-15 17:07:44.619 965:0x3c8 W/ ]

proc dm_pm_timer expires

Update 2:

---------- Post added at 07:32 PM ---------- Previous post was at 07:23 PM ----------

There are the results of testing with the following settings:

- Left work at 17:15

- Arrived home at 17:50

- Wifi disabled

- 3G enabled

- Automatic sysncing in the background: on

- Location bases on networks or wifi: off

- Bluetooth on, and connected to carset between 17:15 and 17:50

Uploaded with ImageShack.us

The resulst show that the CPU increase is drastically reduced, but still somewhat present (jump from 1% to ca. 5%).

Reducing the wifi scan interval surely seems a good idea (google "increase wifi.supplicant_scan_interval"), but because i couldnt locate build.prop i disabled wifi for now. I'll investigate further how to do this because when in the Wifi settings window, i see the spinning circle pop up every 5 seconds indicating its scanning for wifi networks (even if its connected to my home network just fine).

Update 3:

Interesting...., this morning:

- bluetooth on

- 3G on

- Wifi off

- Background syncing off

- Location determination by network off

- Flashed Galaxian EE kernel last night

- left home 07:15

- arrived around 08:00

So, i would say the kernel is not necesseraly the cause of the drain, but different kernels seem to react differently cpu-wise. Flashing back Semaphore 1.7.0 kernel for now.

URL=http://imageshack.us/photo/my-images/11/snap20110919082924.png/][/URL]