An authorized run applications in Android

[hbelal]

Dear all,

I am using Galaxy Note and I am a new user in Android World.

I noticed that there are a lot of apps will run without my authority, I can understand that some apps will run for system needs but I can see some games, normal applications as well.


is there a way that I can block programs from working background without my authority or at least to ask for my authority first?

I hope that I can find something solve my problem.


thanks.

 

[Unforgiven]

Just let it be. Android is designed to run at near memory capacity as it helps with performance and battery life. As you use your phone more, it will learn what apps you want preloaded and load those. Your phone is new now, so it is loading what it "thinks" you may want. After a few weeks you should start to see it loading primarily apps you frequently use.

And let me warn you that someone will probably recommend a task killer, don't use one. I could give you a link to many threads about this, but they are often long, contentious, and technical.

I hope this helps.

 

[hbelal]

Just let it be. Android is designed to run at near memory capacity as it helps with performance and battery life. As you use your phone more, it will learn what apps you want preloaded and load those. Your phone is new now, so it is loading what it "thinks" you may want. After a few weeks you should start to see it loading primarily apps you frequently use.

And let me warn you that someone will probably recommend a task killer, don't use one. I could give you a link to many threads about this, but they are often long, contentious, and technical.

I hope this helps.

Hi, I really appreciate your reply but it is not clear for me. are you saying that my smartphone will get the experience for running only the frequently apps only? but why not to block this as well since I will run it once I need it? I mean what the use of running it in the background since I won't use it?

 

[chanchan05]

The OS has some sort of database of which apps are known to be used a lot, or it was set when it was created. As you use your phone it will be polling your activity to find out which apps you open/use the most. If your usage of a certain app puts it among say, the top ten most used on your phone, the phone will automatically cache that app in memory everytime there is free space to load that app faster and use less battery. Opening and closing an app from scratch uses up more battery than just loading it from cache, so the most used apps are cached.

Others are background processes for apps that have sync functions. They do not really eat up battery if it is not actively syncing but it sits in the background for faster access and again less battery consumption for the system

A common mistake for new Android users is that they even bother looking at "running tasks" or "available RAM" at all. You shouldn't bother. A lot of people are weaned on Windows where less available RAM = bad. Android is different where more available RAM = waste. Its basically apples and oranges.

 

[hbelal]

The OS has some sort of database of which apps are known to be used a lot, or it was set when it was created. As you use your phone it will be polling your activity to find out which apps you open/use the most. If your usage of a certain app puts it among say, the top ten most used on your phone, the phone will automatically cache that app in memory everytime there is free space to load that app faster and use less battery. Opening and closing an app from scratch uses up more battery than just loading it from cache, so the most used apps are cached.

Others are background processes for apps that have sync functions. They do not really eat up battery if it is not actively syncing but it sits in the background for faster access and again less battery consumption for the system

A common mistake for new Android users is that they even bother looking at "running tasks" or "available RAM" at all. You shouldn't bother. A lot of people are weaned on Windows where less available RAM = bad. Android is different where more available RAM = waste. Its basically apples and oranges.

I got it and it is clear completely for me and really thanks.

I just want to ask you to clear one point please if possible, I raised my query in this thread because I was using Go Launcher in my mobile, I noticed that the mobile got heavy more than before and last week, it was too much heavy and slow ( it was too much slow when I was moving between desktops for example ), during that, I saw the RAM always around 70 m only and there are always around 30 apps working in background.


what was the problem in your view please?


again, many thanks for your kind help.

 

[chanchan05]

I got it and it is clear completely for me and really thanks.

I just want to ask you to clear one point please if possible, I raised my query in this thread because I was using Go Launcher in my mobile, I noticed that the mobile got heavy more than before and last week, it was too much heavy and slow ( it was too much slow when I was moving between desktops for example ), during that, I saw the RAM always around 70 m only and there are always around 30 apps working in background.


what was the problem in your view please?


again, many thanks for your kind help.

It would be entirely dependent on the model of your phone and the nature of your setup. A lower end phone will slow down more noticeably if you try to load too many apps to memory than it can handle. For example, your phone can only handle 15 apps simultaneously due to hardware limitation, but you set up the phone to be running 15 apps simultaneously (lets say 7 homescreens full of widgets + background running services). That's going to lag a bit, and especially when you try to run another app.

For example, I have a Galaxy SL with 1Ghz CPU and north of 512mb RAM. My sister has a Galaxy Fit with 600Mhz CPU and 256MB RAM. On my phone it can handle 5 Go Launcher homescreens full of widgets with several other apps running and syncing in background (onenote, evernote, sugarsync, etc) and still run smooth. If I try that on her phone, it gets laggy as hell.

 

[hbelal]

It would be entirely dependent on the model of your phone and the nature of your setup. A lower end phone will slow down more noticeably if you try to load too many apps to memory than it can handle. For example, your phone can only handle 15 apps simultaneously due to hardware limitation, but you set up the phone to be running 15 apps simultaneously (lets say 7 homescreens full of widgets + background running services). That's going to lag a bit, and especially when you try to run another app.

For example, I have a Galaxy SL with 1Ghz CPU and north of 512mb RAM. My sister has a Galaxy Fit with 600Mhz CPU and 256MB RAM. On my phone it can handle 5 Go Launcher homescreens full of widgets with several other apps running and syncing in background (onenote, evernote, sugarsync, etc) and still run smooth. If I try that on her phone, it gets laggy as hell.

I am using Galaxy Note.

on the other hand, I didn't get the part of " the nature of your setup " do you mean by this that I can control this setup by limiting the number of applications that can be running simultaneously? or you mean by this setup, number of home-screens with the widgets?

 

[chanchan05]

Set up as in the number of widgets or homescreens and other backround services you have. Another thing is the 3D effects you may use which can also cause slowness at times, and the fact that Go Launcher is a third party launcher, so in some instances it will slow down due to being taken off from memory, especially right after you use a memory intensive application, like a game. If Go Launcher was taken off memory, when you close the game it will be loaded from scratch and will behave slowly and a bit laggy for a few moments.

You can try resolving this by enabling "System Persistent" in the Go Launcher preferences. This will make the system not take of Go Launcher from memory unless it absolutely has to.

 

[hbelal]

Set up as in the number of widgets or homescreens and other backround services you have. Another thing is the 3D effects you may use which can also cause slowness at times, and the fact that Go Launcher is a third party launcher, so in some instances it will slow down due to being taken off from memory, especially right after you use a memory intensive application, like a game. If Go Launcher was taken off memory, when you close the game it will be loaded from scratch and will behave slowly and a bit laggy for a few moments.

You can try resolving this by enabling "System Persistent" in the Go Launcher preferences. This will make the system not take of Go Launcher from memory unless it absolutely has to.

again I have to thank you for your kind and clear reply.


it is clear for me. thanks a lot.