View Single Post
Posts: 230 | Thanked: 302 times | Joined on Oct 2009 @ Helsinki, Suomi (Finland)
#21
Originally Posted by tortoisedoc View Post
Might also depend on the battery level of each device - and / or battery qualiy?
Battery in slower testing one is in better shape and was at full charge. Faster results are from my main phone, so battery might have degraded a bit (not much though as it still charges nearly to the max.)

@Yisroel

Good. Nothing out of ordinary in CPU usage, but something seems to be hogging your RAM. Try to hit "m" key while running top and it will sort processes by highest memory usage. Maybe some app has a memory leak or has crashed and is still reserving RAM for itself.

You are also running some daemon called theshaketorchd in the background, which is using some CPU and RAM. Though if you find the app useful and haven't experienced too much of battery drain t's probably not a problem.

PS. While looking at this I also ran top on my own phone ane noticed that cutetube had crashed (I didn't have it open and I have disabled the cutetubed daemon) and hogging over 200MB of RAM.

To kill processes you have two ways. Using PID (process ID), which you can see from top or ps output. Or by using the name of the process.

Former is done with command "kill [PID]" and latter by command killall [name]. Both take flag -9 to force kill if the process doesn't respond. So for example:
Code:
$ killall -9 cutetube