![]() |
2010-08-03
, 09:41
|
|
Posts: 70 |
Thanked: 410 times |
Joined on Sep 2009
@ Fife, Scotland.
|
#32
|
I have titans kernel and got about 90% on C4 and 1,5-2% on C0 so i am not sure it is the oc-kernel. Though i can confirm that tick_nohz_restart_sched_tick is one with the most wakeups.
The Following 6 Users Say Thank You to SpeedEvil For This Useful Post: | ||
![]() |
2010-08-03
, 09:48
|
Posts: 1,751 |
Thanked: 844 times |
Joined on Feb 2010
@ Sweden
|
#33
|
![]() |
2010-08-03
, 11:19
|
Posts: 69 |
Thanked: 18 times |
Joined on Apr 2010
|
#34
|
I have titans kernel and got about 90% on C4 and 1,5-2% on C0 so i am not sure it is the oc-kernel. Though i can confirm that tick_nohz_restart_sched_tick is one with the most wakeups.
Have never seen the scim-panel-gtk causing problems.. but that process must be pretty deep and if turned of cause instability.. thus it starts up again. Maybe if you remove it from init.d but that would probably cause even bigger problems.
Ohh.. and i forgot to say that powertop needs to be run with root or it segfaults.
![]() |
2010-08-03
, 12:55
|
Posts: 1,751 |
Thanked: 844 times |
Joined on Feb 2010
@ Sweden
|
#35
|
On the occasion that things behave nicely. I can get up to 97% on C4 on a complete idle system. As I have said previously, it was randomly keeping the device out of C4 and into C0. Will have another try on a completely flashed system on the weekend and see if what SpeedEvil describles will happen on a fresh system.
The scim-panel-gtk is not really that integral to the system. On a fresh boot it doesnt kick in. only when I click on the screen for the virtual keyboard the scim input box then pops up and the process stays. So I don't see why it can't be killed.
@SpeedEvil, can't wait for the full article
![]() |
2010-08-03
, 13:01
|
Posts: 1,224 |
Thanked: 1,763 times |
Joined on Jul 2007
|
#36
|
All apps that do something when not started drain. battery-eye, e.g. is one. As is battery-graph. To log battery, one needs to run. Also, shotcutd, camkeyd, etc are all daemons. All servers.
![]() |
2010-08-03
, 14:24
|
|
Posts: 365 |
Thanked: 98 times |
Joined on Nov 2009
|
#37
|
The fact that a program is a daemon does not mean that it causes any battery drain. Take camkeyd, for example. All it does is sleep, waiting for a specific d-bus event. It does not run and therefore does not consume battery except for very short time when the camera key is pressed. Unless you spend all time pressing and releasing the camera key, it has absolutely no effect on battery life.
Shortcutd, on the other hand, might activate the proximity sensor which does draw non negligible amount of power, but it's CPU consumption is meaningless.
![]() |
2010-08-03
, 20:48
|
Posts: 1,258 |
Thanked: 672 times |
Joined on Mar 2009
|
#38
|
Good point. But still even as it sleeps isn't it still pulling power? An app not recieving any processing power will not be able to tell the event occured. At least not in any computer architecture I'm aware of. While the power I'm talking about to make this happen is negligible it is still power being drawn. I'm not sure how the operating memory of the N900 functions in comparison to desktop RAM, (I know how the my documents and sd card portion work) but I'm assuming even being loaded into this space still requires power to keep it there.
The only way an app can claim it doesn't use power, is when it's not being reported in your list of processes.
![]() |
2010-08-03
, 21:33
|
|
Posts: 186 |
Thanked: 192 times |
Joined on Jan 2010
@ Finland
|
#39
|
But battery eye & battery graph doesnt record the battery activity when its idle right?
these two apps only use cpu when they are opened.it takes 5-8secs to load since it needs to get the details so that the graph/percentage left can be shown.
so i think they dont drain battery unless you use them
![]() |
2010-08-03
, 23:09
|
Posts: 142 |
Thanked: 8 times |
Joined on Jul 2010
|
#40
|
Both of the battery logging apps mentioned come with a background process that is "on" whenever the phone is. They do listen for changes in the values they record, and when they do, they write the do some very infrequent polling, maybe 10min interval, in order to record system load). I've been running both of these apps for about 5 months now, and dare to claim that neither of them should be causing measureable idle drain.
That said, if one doesn't want or need battery stats recording, there's no reason to keep these apps installed.
Have never seen the scim-panel-gtk causing problems.. but that process must be pretty deep and if turned of cause instability.. thus it starts up again. Maybe if you remove it from init.d but that would probably cause even bigger problems.
Ohh.. and i forgot to say that powertop needs to be run with root or it segfaults.