• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Do you shutdown your phone every night?

A

Aztec12

Newbie
Was wondering if you guys turn off (shutdown) your phone every night or leave it on 25/7 ?
I just got my new Optimus S. I came over from the iPhone 3G and I used to turn it off almost every night.
Should I do the same with my optimus?
 
I was just asking couse I heard somewhere that this smart phones Need to be turned off I guess once in a while becouse it's like a mini computer and it has to be restarted every now or then. 
 
Some people believe in doing that.

I reset my phone enough tinkering around with it (maybe once a week or so) that I haven't had any need to reboot it on any fixed schedule.
 
I try to turn in off in the morning when I go to the gym, or when I'm biking to work, but I usually don't turn it off at night. I have run the phone days on at a time without turning it off, though, and I haven't seen performance suffer. And I use it a lot - to give you an idea, I am pushing 2GB of data usage this billing period, and without tethering.
 
i keep my phone on all day and all night. i also have my screen set to not sleep while charging. i have gone weeks without resetting it without any issues what so ever.
 
I agree with turning it off then back on once a day. Gives it a fresh restart and things do tend to run more smoothly if you consistantly do that.
 
I downloaded the fast reboot app from the marketplace, that way I can "simulate" a reboot without actually having to reboot the phone. It seems to work just fine. Come from the Blackberry world, I do a battery pull every and again out of habit, but it's not really something I have to do.
 
I found this article on a Droid forums, but it talks about the Android OS in general. It's a good article to explain why some programs start up whether you use them or not. It's a quick copy and paste, there is also a video you can watch and some hyperlinks for follow up reading.

Task Killers... The Answer from Google & Developers. - Droid Forum - Verizon Droid & the Motorola Droid Forum

In response to the vast amount of questions regarding Task Killers, I find this to be a valuable article/video in making a determination in whether or not to use a task killer on 'auto-kill' or manually killing apps just because they're open. A task killer is meant to shut down unresponsive apps, not EVERYTHING open.

Good explanation of how the Android OS is designed to handle applications.

Make your decision from there
PLEASE READ THIS!!!

SystemPanel Documentation | android.nextapp.com (smalltowngirl13 posted @ DxF, but I wanted to put it here as well)

*quick cut & paste from the link*
from the developer who designed System Panel.

" Please read this section FIRST. There are a great many misconceptions about how Android works with regard to
starting and stopping applications.

How to Use a Task Manager
Android was designed from the ground up as an operating system (OS) for mobile devices. Its built-in application and memory-management systems were engineered with battery life as one of the most critical concerns.
The Android OS does not work like a desktop operating system. On a desktop OS, like Windows, Mac OS X, or Ubuntu Linux, the user is responsible for closing programs in order to keep a reasonable amount of memory available. On Android, this is not the case. The OS itself automatically removes programs from memory as memory is needed. The OS may also preload applications into memory which it thinks might soon be needed.
Having lots of available empty memory is not a good thing. It takes the same amount of power to hold "nothing" in memory as it does to hold actual data. So, like every other operating system in use today, Android does its best to keep as much important/likely-to-be-used information in memory as possible.
As such, using the task manager feature of SystemPanel to constantly clear memory by killing all apps is strongly NOT RECOMMENDED. This also applies to any other task killer / management program. Generally speaking, you should only "End" applications if you see one which is not working correctly. The "End All" feature can be used if your phone/device is performing poorly and you are uncertain of the cause.

Process Types
The SystemPanel process listing groups applications into three categories: "Active", "Inactive", and "Internal":
Active applications are actually running at the present time on the device. An active application may be running in the background and not have any information currently displayed on the screen.
Inactive applications have been preloaded into memory, but are not actually using up any system resources. Such applications will not consume any battery power whatsoever. The memory used by these applications can be immediately reclaimed should other applications require it. As such, there is no need to manually remove these applications, as you will see no tangible benefit from doing so.
Internal applications are those which are part of the Android operating system itself. Some of these applications may be terminated manually, but they will be immediately restarted afterward by the OS."

I highly recommend people, especially those new to Android, watch the Androidology series of videos put out by Google themselves. In particular, part 2 does a great job of explaining how Android (and really Linux) is different then most people's OS experience.

After watching the whole Androidology series, I decided to let the OS do its thing with killing/running apps and processes. I have a task killer installed only to kill unresponsive apps that the OS can't kill for whatever reason (which by the way, is a fault generally of the app's developer(s). Not the phone or OS). And the Android OS actually comes with it's own "Task Killer" for this purpose, I just prefer to have easy "one-tap" (or close to it) access to such things.

Here's the rest if you're interested (highly recommended. Especially if you're a dev) Videos | Android Developers
Click to expand...


There's a lot of information in the whole thread if you got time to read.

As far as stopping programs from starting up, not sure how to accomplish that.
 
You must log in or register to reply here.
Back
Top Bottom