Wait so the droid x isn't locked? I'm so confused.. I was so uninterested in the droidx with its locked bootloader that I never cared to figure out what all the problems were... is it just that you have to run the stock kernel?
Sent from my Droid using Tapatalk
A little app called "autostarts"... disable ANYTHING before or after you open anything. I disable all the nonsense that starts after boot and that's it.
No task killers, no battery profiles. I pull 17-18 hours consistently with the OEM Moto EB, everything on and hard core usage.
I see no benefit to have a app running plus extra services just to "try" and stop other apps from running.
Great app, give it a shot.
Sent from my DROIDX using Tapatalk
Stopping an app from even starting is pointless, if you're on the droid x then it means your nand-locked. So your app that stopps apps from starting is just killing them on boot... since you can't remove the apps or anything like that.
I would just remove the auto app starter thing, it would prbably increase boot time. & I know its probably hard to understand this but android can use 0% cpu when a process is suspended to memory.
Sent from my Droid using Tapatalk
I'm not reffering to stopping the apps... I'm reffering to the multiple services that just run in the background for those "just in case" it needs it type thing. ALL apps I didn't want or use have been removed VIA system mount and Root Explorer including any trace of Verizon garbage not needed.
The point of autostarts is to not allow connecting service to run. ie.. when you turn on or open something it will invoke multiple services they "may" be used. For example, at boot I have no reason for Bluetooth share, market, or the service for endgadet to be running. They can start when I NEED them, not just because. It is not a task or app killer, it is a extended functional arm for managing services.
And its impact on the boot time is "faster" because most of the things that normally start are not.
Sent from my DROIDX using Tapatalk
Stopping an app from even starting is pointless, if you're on the droid x then it means your nand-locked. So your app that stopps apps from starting is just killing them on boot... since you can't remove the apps or anything like that.
I would just remove the auto app starter thing, it would prbably increase boot time. & I know its probably hard to understand this but android can use 0% cpu when a process is suspended to memory.
Sent from my Droid using Tapatalk
I'm not reffering to stopping the apps... I'm reffering to the multiple services that just run in the background for those "just in case" it needs it type thing. ALL apps I didn't want or use have been removed VIA system mount and Root Explorer including any trace of Verizon garbage not needed.
The point of autostarts is to not allow connecting service to run. ie.. when you turn on or open something it will invoke multiple services they "may" be used. For example, at boot I have no reason for Bluetooth share, market, or the service for endgadet to be running. They can start when I NEED them, not just because. It is not a task or app killer, it is a extended functional arm for managing services.
And its impact on the boot time is "faster" because most of the things that normally start are not.
Sent from my DROIDX using Tapatalk
Has no benefit but it has negligble harm, so you can do whatever you want.
Those apps don't "run" in memory, they are loaded into memory and reside there in a fully dormant state until they are called upon to run or are killed and replaced with higher priority processes by androids auto memory management system; dormamt apps in memory do not consume any battery and load faster when they become active, therefore there is no point in stopping them from being there... however, if its an app you never use and then run it once, the difference between it starting from a dormant state in memory vs starting from a first run state not in memory, is negligible. But on android, free memory is wasted memory.. so like I said, there is really no benefit to preventing apps to get loaded into memory to sit their dormantly. Android is not like windows, what your doing is not like typing "msconfig" in run cmd and reducing startup processes because those run actively... big difference. The android memory management system is very sophisticated and requires no user intervention. The best thing you can do is completely eliminate any apps that constantly fetch data or run actively. Any form of task killer, or auto start thing, is either counter-productive or has no real benefit.
{{ WugFresh }}
No problem
I definitely thought the exact same thing you did and use to run the app startup manager, but after researching how android actually manages its memory, I became aware that it was pointless, its hard not to compare android to other computer technology you are familiar with, I totally understand.
{{ WugFresh }}
Also I would recommend downloading a couple apps like Automatic Task Killer (Kills Apps in background)
I admit im a bit of a noob. I cant edit my first post with this app but lets just post things here that do work! When I get on my computer I will edit my first post.
Sent from my DROIDX using DroidForums App
Also I would recommend downloading a couple apps like Automatic Task Killer (Kills Apps in background)
Eer, no..........
~John
Also I would recommend downloading a couple apps like Automatic Task Killer (Kills Apps in background)
Eer, no..........
~John
I know some people don't like Task Killer Apps, but I really haven't had problems with the Automatic one, just the Advanced Task Killer. It does vary on your phone, but it works fine on Motorola Droid 1, 2 and X