I have Samsung Galaxy Y. I think that when I use wireless and installing apps, not immediately but after a while the phone slows down considerably.

When it happens I must restart and when it turn on, then continues to operate normally.

I don't know if this is caused by some applications I have installed or some other problem. When it occurs I try to free RAM memory with Samsung's task manager or fast reboot, but it doesn't help.

After I read some of your topics, I don't use task killer anymore. It happens to me two or three times a day!

Why my phone slows down, and only turning it off/on seems to solve the issue?

  • Sounds like it could be a memory leak. Jan 30, 2012 at 18:04
  • How do I resolve the problem without rebooting?!
    – Dule
    Jan 30, 2012 at 18:15
  • Don't be impatient, we don't even know what the problem is. When you try to free memory with samsungs task manager, does free memory increase? How much do you have free before and after the samsung freeing?
    – Mihic
    Sep 3, 2012 at 13:06

1 Answer 1


"Getting slow" can be caused by a couple of different things -- separately or combined. It could be an app hogging your CPU, or the system running low on free RAM. It's even possible that some service runs havoc, blocking resources (though this one would be a bit harder to track).

Easy tracking for beginners (and for free)

There are several possibilities to find out what's going on. The easiest is to install e.g. OS Monitor and, when the device gets slow, starting this app and taking a look at the running processes. First order them by CPU usage: Is there any app constantly using 50% or more CPU? If so, you probably found the evil-doer. Next order them by RAM usage: Any app "eating" extra-ordinarily much?

Don't worry to much about how much RAM is free. There's no such thing as "unused RAM being a good thing" -- neither on Android nor on Linux. Free RAM will be used to speed things up, e.g. by caching files. Of course, if more RAM is used, those caches get freed.

Monitoring the system

If the easy approach does not help, you need heavier armament -- and a little background knowledge to use such. There's e.g. SystemPanel which can monitor your system. More useful is the paid version, which can do so in the background, and also saves its monitored data -- so you could even check after a reboot. An alternative helper-app is System Tuner (here again the paid app is more useful). Also, Tracing Memory might be worth a look (can't hurt, it's free).

Found it?

When you found out the bad app, actions depend on what it is. Is it an app that came pre-installed, or even belongs to the Android system, you e.g. could not simply remove it. Check the app's configuration, contact the developer, or search the web for known trouble with the evil-doer are always good steps to take. Of course, once you found the culprit, you can always come back here and ask a more specific question -- and with the background information you collected, we probably can give you better hints to solve the issue.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .