Closed GoogleCodeExporter closed 8 years ago
Check with osmonitor if mediaserver is in loop (100% of cpu use)
--
Azhad
Original comment by colaiann...@gmail.com
on 19 Sep 2010 at 6:58
No, thats not the problem.
'Android System' is the problem.
Original comment by sleibfa...@gmail.com
on 19 Sep 2010 at 8:18
Yup, need some optimization. Android system takes second after display on
battery use
Original comment by superbiji
on 20 Sep 2010 at 3:15
Cyanogenmod for Milestone by default overclocks the CPU to 900Mhz. That could
be the cause.
Original comment by bounce...@gmail.com
on 20 Sep 2010 at 5:44
No it's not the overclock...
Before (with GOT 2.36) i was using the overclock in 1000MHz with 60 vsel max
and i had almost twice battery life...
Original comment by kalagas.YS
on 20 Sep 2010 at 5:49
[deleted comment]
Maybe the new "interactive" cpufreq governor?
Original comment by bounce...@gmail.com
on 20 Sep 2010 at 5:51
I was using the interactive governor before too...
My 71_overclock.sh in GOT 2.36 was like this:
/system/bin/insmod /system/lib/modules/overclock.ko
omap2_clk_init_cpufreq_table_addr=0xc004e4b0
echo 0xc0295704 > /proc/overclock/cpufreq_stats_update_addr
echo 60 > /proc/overclock/max_vsel
echo 1000000 > /proc/overclock/max_rate
echo "1 125000000 28" > /proc/overclock/mpu_opps
echo "2 250000000 28" > /proc/overclock/mpu_opps
echo "3 500000000 36" > /proc/overclock/mpu_opps
echo "4 750000000 56" > /proc/overclock/mpu_opps
echo "0 1000000" > proc/overclock/freq_table
echo "1 500000" > proc/overclock/freq_table
echo "2 250000" > proc/overclock/freq_table
echo "3 125000" > proc/overclock/freq_table
system/bin/insmod /system/lib/modules/cpufreq_interactive.ko
echo interactive > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
And I had no problems with battery....
I think in this ROM (Cyanogen Port) the problem may be in sleep mode or in
display...
Original comment by kalagas.YS
on 20 Sep 2010 at 6:12
Any idea how to debug battery use? I will try on my device
Original comment by superbiji
on 20 Sep 2010 at 10:45
Hi,
I just realized that my WLAN will not disconnect when I turn the display off.
For example my download continues. I set the extended WLAN options to "Do not
disconnect, while charging". This definitivly is a reason for the high battery
drain in "Standby".
GMAEDZL
Original comment by gmae...@gmail.com
on 20 Sep 2010 at 10:55
yes, it is a fact, that MS does not switch in deep sleep with CM...you can try
for yourself as follows:
- connect to WLAN
- start any download from your MS
- switch to standby and stay there for a few minutes
- switch back from standby
--> you will recognise, that download continued though it usually stops WLAN,
when you switch to standby
Original comment by eybee1970@googlemail.com
on 20 Sep 2010 at 10:59
+ I do not have to reconnect to my access point when I unlock the phone. With
2.36. it took a while befor the WiFi connection was established. Now its
instantly connected.
GMAEDZL
Original comment by gmae...@gmail.com
on 20 Sep 2010 at 10:59
Froyo itself is coming normally with a new kernel. The kernel is optimized a
bit more for battery use. So, i think, if we don't get a new kernel, the
battery drain will still be there. I THINK it is only a kernel related problem,
as we all use 2.1.29 kernel, although 2.1.32 (?) is the kernel for Froyo.
BUT battery drain is much better, than in frenzy release.
Original comment by kniff...@gmail.com
on 20 Sep 2010 at 11:00
i lost 10% with Frenzy over night, now I lose 30%....so I don't think, it is a
kernel problem, but a prob with not not switching to deep sleep in standby (see
gmaedzl's and my commet above)
Original comment by eybee1970@googlemail.com
on 20 Sep 2010 at 11:16
Found it, using testing menu- batt history
Android system takes high for sensor usage.
Original comment by superbiji
on 20 Sep 2010 at 11:24
I've lost 40% in 7 hours. The phone has been mostly idle, and is set to
downclock when the screen is off. According the battery history, Android System
is the source of the drain.
Original comment by Adam.Hus...@gmail.com
on 20 Sep 2010 at 1:52
Thanks for the reports.
Original comment by kabal...@gmail.com
on 20 Sep 2010 at 2:16
Having run DMesg via ADB, I notice the following entries:
Powerdomain (core_pwrdm) didn't enter target state 1
<3>[31808.092529] Could not enter target state in pm_suspend
<3>[31808.093750] cpcap_batt_resume: Wakeup!
<6>[31808.157135] suspend: exit suspend, ret = 0 (2010-09-20 15:25:08.562500008
UTC)
<6>[31808.157348] suspend: abort suspend
<6>[31808.657867] suspend: enter suspend
<6>[31808.710113] power_suspend_late return 0
It then loops repeatedly. I've attached the full logfile.
Original comment by Adam.Hus...@gmail.com
on 20 Sep 2010 at 5:22
Attachments:
Please read here
http://forum.xda-developers.com/showpost.php?p=8232076&postcount=185
what I wrote. Might be helpful...
Original comment by kalagas.YS
on 20 Sep 2010 at 5:57
I disabled network location and android system dosn't use as much battery as
before (55% versus 5%)
Original comment by colaiann...@gmail.com
on 20 Sep 2010 at 10:24
reenabled network location and after 1 hour android system was consuming more
battery than the display
Original comment by colaiann...@gmail.com
on 20 Sep 2010 at 11:27
As soon as the (anyway only temporarily used) dext3r's usb fix is disabled, the
board goes to standby very nicely. Including the wifi. So it's hopefully all
about the initialy declared 'To do' item "- make some non polling usb fix".
Thanks for the reports, I'm working on it.
Original comment by kabal...@gmail.com
on 21 Sep 2010 at 1:27
Great... i hope included in hotfix.
btw disabling auto rotate and auto brightness save some battery.
Original comment by superbiji
on 21 Sep 2010 at 3:14
How do we disable dext3r's usb fix in the mean time? What is the consequence of
that?
Original comment by bounce...@gmail.com
on 22 Sep 2010 at 6:44
Edit /etc/rootfs/init.mapphone_umts.rc and remove or comment :
service dexter_usbfix /system/bin/usb_mass_storage_fix
class pre-zygote_services
oneshot
I have made it but continue same problem.
Original comment by alexandr...@gmail.com
on 22 Sep 2010 at 11:16
Thanks!
Same problem meaning still having battery drain problem?
Original comment by bounce...@gmail.com
on 22 Sep 2010 at 11:40
Yep, in dmesg phone can't sleep.
But it have saved some battery.
Original comment by alexandr...@gmail.com
on 22 Sep 2010 at 11:59
In my phone when I comment those lines as described, when it boots up the phone
becomes laggy. I checked and there is some kind of significant constant load on
the cpu. Maybe there's something that is missing.
Original comment by bounce...@gmail.com
on 22 Sep 2010 at 2:24
Please report, whether the usb solution in 0.01c update helped.
Original comment by kabal...@gmail.com
on 22 Sep 2010 at 6:41
Currently disconnected from power/usb for 11 hours, WiFi, Bluetooth, GPS, data
and sync on, battery at 80%.
I really hope that we can close this issue as fixed in 0.01c.
Original comment by kabal...@gmail.com
on 23 Sep 2010 at 10:54
Hi,
for me the battery drain seems to be gone. Thank you for your work!
Original comment by jan.rin...@gmail.com
on 23 Sep 2010 at 12:26
Hi! My battery lasts much longer now.
What I'm concerned is the use of Motorola's proprietary drivers and parts for
this fix.
But maybe this is the best for now.
Thanks for your hardwork!
Original comment by bounce...@gmail.com
on 23 Sep 2010 at 1:06
look at all the proprietary files that are being used by the official CM6 for
droid:
http://github.com/koush/proprietary_vendor_motorola/tree/froyo/sholes/proprietar
y/
We will always have to use some proprietary files in the binary form, unless
the sources magically emerge. As we also have the locked kernel, some
proprietary daemons matching the drivers already compiled in the kernel are
inevitable.
I agree that the goal should be to keep the number of such files and direct
changes of the platform files at minimum as possible.
Original comment by kabal...@gmail.com
on 23 Sep 2010 at 2:27
Confirmed. Work! Thanks nadlabak
Original comment by superbiji
on 23 Sep 2010 at 11:33
Seems like it has vastly improved when idling, but music player is eating a lot
of battery (there is another issue for it).
Thanks! :)
Original comment by nicolas....@gmail.com
on 24 Sep 2010 at 2:09
Hmm i having trouble, android system acting strange again. Using 1 second cpu
time every second, using battery use.
After turn on data and run imo.im
Original comment by superbiji
on 25 Sep 2010 at 1:51
Installed 0.01c, OSMonitor still shows regular activity of Android System.
Status says "Sleep", but Im not in Sleep Mode. Seems like Android starts a loop
to activate the sleep mode but always fails or something.
In Battery Info the "Android System" still goes pretty high, almost always
right next to the Display...
Is there a Fix or something in the works?
Original comment by Try4Ce...@gmail.com
on 29 Sep 2010 at 1:35
I also have abnormal (compared to 2.1-update1) battery consumption using 0.01c.
Specifically, after being idle for about 13 hours, the battery level went from
100% to 50%. The battery statistics are as follows:
34% Phone Idle
26% Cell Standby
11% Android OS
10% Android System
6% PowerTutor
(Unfortunately, even though I had killed everything killable before this test,
PowerTutor apparently decided to restart itself.)
I can't really say exactly how long the battery would have lasted with my
previous Android in the same conditions, but leaving it on overnight generally
resulted in a 10% level drop at worst.
Original comment by ljl...@gmail.com
on 30 Sep 2010 at 1:17
I have a lot of battery drain in standby and 'workong mode' (v0.02)
I detected, that AndroidSystem shows up with 12% CPU-Load in standby (checked
with WatchDog from market), in Android System VPN was one of the tasks though I
don't use it - removed VPN in /system/app for now and testing, if this was
cause of drain...
Original comment by eybee1970@googlemail.com
on 1 Oct 2010 at 11:11
Suggestion: please, install the Toggle 2G/3G application from XDA, mentioned
here: http://code.google.com/p/cyanogenmod4milestone/issues/detail?id=41#c2, it
works very well and really helps the battery life.
I'm waiting for a permission of its author to include it in the next release as
a prebuilt apk.
Original comment by kabal...@gmail.com
on 1 Oct 2010 at 3:03
thx, nadlabak
but that does not solve the issue - my mobile connections are disabled in
standby but battery drain has doubled compared to 0.01c
Original comment by eybee1970@googlemail.com
on 1 Oct 2010 at 3:53
IMHO that app will make things worse. everytime switching to 3G/2G , Network
location will run more often and suck more battery.
Original comment by superbiji
on 1 Oct 2010 at 3:58
I thing battery with 0.02 is worst than 0.01c...
With same usage in 0.01c lasted about 30-32 hours and now with 0.02 lasts about
20 hours...
Original comment by kalagas.YS
on 2 Oct 2010 at 6:43
the new 0.02 is worst than 0.01b and c for sure! My device get 10% down after
an hour.
Original comment by nguyensh...@gmail.com
on 3 Oct 2010 at 3:49
The cell standby mode seems to be over 35% in battery use. Also phone idle
drains a lot of battery... all these in 0.02 10.02.10
Original comment by kalagas.YS
on 3 Oct 2010 at 7:25
@Kabaldan
I use the app Autostart to exclude some apps from starting... in the menu
"After Startup" of the Autostart app, I noticed that the only that can't be
disabled is "Google Service Framework". I think this is the app that the drains
the battery in sleep mode. In properties of Google Service Framework I noticed
that it's something about gtalkservice, online services etc. Please correct me
if I'm wrong but I think that Google Service Framework is responsible for drain
battery, cause always trying make nothing, I don't know what but I thing its
working hard in background all the time. So maybe you can check this if my
thoughts are correct...
Original comment by kalagas.YS
on 3 Oct 2010 at 8:42
@kalagas.YS are you crazy :) still complaining battery for 20 hours of use?
I only get 7 hours max of full use.
Original comment by superbiji
on 3 Oct 2010 at 2:39
No now with 0.02 02Oct I have maximum 10-12hours with normal use...
That's why I started to search what is that drains my battery, and as I told I
thing it's Google Service Framework...
Original comment by kalagas.YS
on 3 Oct 2010 at 3:39
You know that Google Service Framework is the entire Android framework, right ?
Are you sure you don't have a problem with some sync, like Picasa Web Albums
trying to sync something you don't have (check in Settings > Syncing and
Accounts (or somethings like that) > then open your Google Account > Uncheck
unnecessary functions).
Original comment by feron.ga...@gmail.com
on 3 Oct 2010 at 5:44
I said that Autostart can't disable the Google Settings Framework, so I don't
have problems with synchronization. I was thinking if this app don't let the
phone to go into sleep mode and that's why there is so much battery drain...
Original comment by kalagas.YS
on 3 Oct 2010 at 6:33
Original issue reported on code.google.com by
sleibfa...@gmail.com
on 19 Sep 2010 at 9:15