elgatodetexas
Lurker
I've been looking to see if I can find a built in task manager for the myTouch 4G phone. No luck so far, just wondering if there is one that is built in or not. I've search the forums, but no luck.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Help myTouch 4g task manager
- Thread starter elgatodetexas
- Start date
-
- Tags
- t-mobile mytouch 4g
As android is running linux based variant by default it shares few similarities. As one of them includes superior memory management which is not same as WinMo. In our world UNIX world (long before this POS Android newbie stuff was even born) we have a saying that unused memory is wasted memory. So when anything is allocated it is cached and its not released until anything requires it to be reallocated. Now this can happen from few things as memory is still cached if user were to access it by rerunning it then it will still be available but if the resource is unused based on the access recalls its relased based on chronologically.
Now anyone who thinks task management is not required even on UNIX/Linux much less on Android is simply a fool who shouldn't do anything as they are harm to the system. With that being said if you are required to shut something down forcefully due to memory leak or other factors you should do it only if you know what you are doing as it will not be fully released until you do warm boot.
If you need greater access to system resource then I suggest you take control of service and disable things that you do not need. Once again if you don't know what you are doing then leave it alone. As you can disable service at boot and some service do restart in that case you can also setup policies to shut it down if its restarted.
^ now tell me I don't know about memory efficiency.
Now anyone who thinks task management is not required even on UNIX/Linux much less on Android is simply a fool who shouldn't do anything as they are harm to the system. With that being said if you are required to shut something down forcefully due to memory leak or other factors you should do it only if you know what you are doing as it will not be fully released until you do warm boot.
If you need greater access to system resource then I suggest you take control of service and disable things that you do not need. Once again if you don't know what you are doing then leave it alone. As you can disable service at boot and some service do restart in that case you can also setup policies to shut it down if its restarted.
^ now tell me I don't know about memory efficiency.