|
2011-10-21
, 15:51
|
Posts: 36 |
Thanked: 13 times |
Joined on Oct 2011
@ London
|
#482
|
|
2011-10-21
, 16:02
|
Posts: 50 |
Thanked: 16 times |
Joined on Nov 2009
|
#483
|
you'll have to enable dev mode if you haven't already.
then using the terminal you'll have to find out what process is taking up the cpu (in terminal, landscape so you can see more, type top and press enter, the top process is taking the highest cpu, take note of the highest couple PID's)
then you'll have to kill it.
type: kill <PID>
where <PID> is the number of the process which is the problem.
now you should be able to kill the process, if not try typing in devel-su, and then kill the process, and then type exit (be careful in devel-su).
some processes you won't be able to kill even in devel-su thanks to aegis. in this case i think a reset is best.
as a guide, my top processor users are, sensord, terminal,top,uiserver,xorg,mcompositor,budaemo to mention a few... if your uncertain post your top cpu processors here to make sure your not going to kill anything important (although a simple reboot should fix it if you kill anything important)
|
2011-10-21
, 19:30
|
Posts: 87 |
Thanked: 56 times |
Joined on Nov 2008
|
#484
|
|
2011-10-21
, 20:16
|
Posts: 36 |
Thanked: 13 times |
Joined on Oct 2011
@ London
|
#485
|
|
2011-10-22
, 05:26
|
Posts: 397 |
Thanked: 185 times |
Joined on Oct 2011
|
#486
|
Try "top" on command line. See post #446.
Let me know if you have "smartsearch" running. I'm getting little bit p...ed with that one. Also, "Search" application is not working for me...
|
2011-10-22
, 09:30
|
Posts: 32 |
Thanked: 11 times |
Joined on Oct 2011
|
#487
|
|
2011-10-22
, 11:30
|
|
Posts: 387 |
Thanked: 566 times |
Joined on Dec 2009
@ Dublin
|
#488
|
The Following User Says Thank You to smegheadz For This Useful Post: | ||
|
2011-10-22
, 12:07
|
Banned |
Posts: 706 |
Thanked: 296 times |
Joined on May 2010
|
#489
|
|
2011-10-22
, 12:11
|
Posts: 10 |
Thanked: 4 times |
Joined on Oct 2011
|
#490
|
The Following User Says Thank You to shansp3 For This Useful Post: | ||
then using the terminal you'll have to find out what process is taking up the cpu (in terminal, landscape so you can see more, type top and press enter, the top process is taking the highest cpu, take note of the highest couple PID's)
then you'll have to kill it.
type: kill <PID>
where <PID> is the number of the process which is the problem.
now you should be able to kill the process, if not try typing in devel-su, and then kill the process, and then type exit (be careful in devel-su).
some processes you won't be able to kill even in devel-su thanks to aegis. in this case i think a reset is best.
as a guide, my top processor users are, sensord, terminal,top,uiserver,xorg,mcompositor,budaemo to mention a few... if your uncertain post your top cpu processors here to make sure your not going to kill anything important (although a simple reboot should fix it if you kill anything important)