Battery pull vs power off/on
OK, so I came from a blackberry and the only way to actually have the phone turn off 100% was to pull the battery. On the Droid X, if you power down and turn off the phone it 100% turns off the phone.
My question/debate is why does everyone here say to pull the battery on the droid. It's my understanding that the only time the battery should need to be pulled is if the device completely locks up and doesnt allow you to power down the phone using the power button. Pulling the battery seems to potentially lead to more problems, like breaking the battery door, ripping the pull tab off etc.
so is there really any difference between pulling the battery and powering the device off and back on that would make the phone more "magical" when it turns back on?
- 10-20-2010, 08:43 AM #2
I believe when you pull the battery it is similar to unplugging a modem completely from a power source when troubleshooting bad connections.
That lack of a power source is more like a, "Well not sure that it will help the situation but it certainly cant hurt it!" kind of thing.
Things just tend to work when you do that I think because when the battery is removed for a certain period of time it helps the device to reboot in a fresh active state.
- 10-20-2010, 08:46 AM #3
All modern cell phones are potentially on with the battery installed.
The only true way to kill potential tracking or spying access is to pull the battery in any cell phone.
However, the Androids are nothing like dingleberrys and shouldn't ever need a battery
pull, usually a simple reboot will work if you experience a problem.
You won't need to be pulling the battery all the time because of lockups like with a
- 10-20-2010, 09:58 AM #4
- 10-20-2010, 11:01 AM #5
- 10-20-2010, 11:26 AM #6
Reason? My brother also has a DX. Ever since he did the OTA upgrade from 2.1 to 2.2 his X will occasionally hang up on the Moto logo when he powers on from a turned off device. He has tried a factory reset (which eliminated about 90% of the hang ups with powering on) but still has an occasional Moto screen freeze. If he does a battery pull when stuck in Moto logo, it tends to boot up just fine after that.
So I assumed, perhaps incorrectly, that doing a battery pull was more of a complete restart based upon his experience. Thoughts?
As an aside, I also did the OTA upgrade with my DX and it's been fine in every way. Strange...
- 10-20-2010, 08:48 PM #7
- 10-20-2010, 10:29 PM #8
Android os is like a computer os, there are temp files and other system files in use. Just as you dont want to pull the plug on your computer unless you absolutely have to, you shouldn't pull the battery on your Android device. You will end up with orphaned files like the temp files that were in use at the time, but after the reboot, the os wont know what that file was for. So the file sits there taking up space unless it is removed.
- 10-21-2010, 05:16 AM #9
- 10-21-2010, 02:26 PM #10
I don't know enough about the chipset on the DX, but is it possible that with the battery still in, the SRAM on the phone used for running applications stays possibly active through a shutdown (at least for a while). While a battery pull ensures that the SRAM loses the resident image (and any currupted bits) and refreshes the OS from the non-volitile memory?
Just thinking out loud... Of course I would power-off before pulling the battery to avoid the previous posters orphaned files issues...
- 10-21-2010, 02:34 PM #11
- 10-21-2010, 03:04 PM #12
- 10-21-2010, 03:07 PM #13
This is why i started this thread. It sorta drives me nuts that a lot of people in this forums solution is to pull the battery rather than power cycle the device. For all the little/big issues that Ive had with froyo, all have been resolved just by powering the device off and then back on. I like a good debate every now and then though in case someone has some more insight that i might not understand.
This is kinda in that same area of task killer vs no task killer and how big red installs them on your phone even though they shouldnt be used.
- 10-21-2010, 04:10 PM #15
- 10-21-2010, 04:20 PM #16
I still don't think you can ignore the cold boot vs. warm boot possibilities...
I don't do Android programming, but from my experience, the bootloader of an embedded system will take different paths to restoring the OS depending on the state of internal registers telling them if they lost power or not... Whether that is attempting to reload a resident image or assuming a driver is already initialized... these are time/settings saving activities the bootloader will attempt... if there was issues with curruption in those images, a battery pull could force the bootloader to reload from scratch....
- 10-21-2010, 05:33 PM #17
- 1,064 Posts
Ok I just want to say, if the device is powered OFF, its OFF. There's no physically-possible way for a powered off device to transmit any signal whatsoever.
All those phony warnings about how your phone can be tracked, even while "off" are bull just to scare lesser tech savvy individuals. When they say off, they mean when you have the screen off, but the phone is still powered on, but in a standby state. In this case yes its possible for your phone to "transmit a signal" while "off" but this is totally different then holding the power button down for 3 seconds, and pressing "Power Off." This is the equivalent to pressing Start -> Shut down on your computer. Its off. Period. I dunno about you guys but when my computers off it can't transmit me any porn so I guess it can't transmit anything else either well guess what the same applies to your phone.
Now as for the debate of whether to pull the battery or power cycle through the OS, its the same end result only the means of getting there are different. Sometimes you NEED to pull the battery, point in case stuck at the M logo. Other times you just want to get a fresh boot. In that case it is not necessary to pull the battery.
For the sake of curing temporary bugs in the system, a power cycle via the OS is more than sufficient.
So glad some others out there share my resent for those who live by these false beliefs (powered off transmitting signals, battery pull doing something more than just turning off the device) lol. Thanks and hope this helps clear things up for anyone still confused.
- 10-21-2010, 06:26 PM #18
Please just take this as a heathy discussion...
Using your PC analogy, if you turn off your pc, it CAN still get a signal... Think power on LAN... but it would behave much differently if you also pulled the plug. I agree this is limited, and much different from consperacy "tracking" that people seem to worry about.
And before I go on, I want to make it clear I do NOT believe when a phone is off it still sends signals. In fact I do think that the phone is off and the OS will boot fresh, by just powerring off.
But, my point is that when hardware retains power, it retains settings, that the bootloader will sometimes NOT refresh if it too finds that the power was maintained... In the PC example this is the LAN card staying on and active and on the OMAP chipset this could be the SDIO controller chip that had a register bit flip causing issues writing to the SD card properly. http://www.linuxfordevices.com/files...3640_block.jpg
I do think the power down will solve 99% of issues with what's ailing the phone, as most issues will be with poor software development. But don't 100% discount the healing possibilities of a cold boot.
- 10-21-2010, 07:14 PM #19
- 10-21-2010, 07:38 PM #20
Unfortunately my phone is one if the unlucky phones that seems to always get stuck on the Motorola logo whenever I power the phone off and back on. Pulling the battery always lets me reboot. This is of course, after the froyo update.
Sent from my DROIDX using Tapatalk
- 10-21-2010, 10:09 PM #21
Wanna give out your......Nevermind.
Within 5 minutes, anyone's phone Mic , camera and GPS can be monitored on any modern cell phone.
Please don't mislead people into false "security", this has been proven wrong too many times.
Anyway, the battery has to be out to truly power off a cell phone and it only needs pulled
if the phone locks up and you cannot soft reboot.
- 10-21-2010, 10:49 PM #22
- 363 Posts
I saw this on Eagle Eye, they were able to track cell phones while powered off. And on CSI they were able to triangulate the exact location of a powered off cell phone. And in The Matrix Agent Smith was able to find a cell phone that was thrown in the trash, well that one was still on, and in a virtual world, but still.
[tapatalk - droidx]
- 10-22-2010, 12:20 PM #23
So... I was wanting to know if by pulling my battery once in a while I was creating a vast army of orphaned files on my device and if so, how I could perform a "search and destroy" on said files.
If a rare battery pull is no big deal on a Droid X, I will just put up with it. Honestly battery pulls were a way of life with all of my prior BB's. This is a huge improvement over a Berry.
My X has been stellar otherwise. Nonetheless, VZW has told me that they would issue me a brand new device if the occasional stuck Moto is driving me nuts. It's not and I thought I'd simply wait for the Froyo patch update to fix this. OK, guys I've got 2 days left on my 30 day return window. What say you?
- 10-22-2010, 12:55 PM #24
My understanding was that in order to get a completely clean restart, free of and residual "stuff" sitting on the DX's memory you should power the device off, pull the battery, then (with the battery out) hold the power button for 3-5 seconds. I read this in a "how to get a clean factory reset" thread that I think was stickied and noted to be most accurate... But my memory sucks so it may have just been a random thread I stumbled across. Can anyone (who is not just guessing because they haven't heard of it before) verify this or debunk it?
- 06-16-2011, 02:51 PM #25
Within the first week, I've had 3 times where I went to use my phone and it was frozen solid. Pushing and/or holding the Power or Home buttons did absolutely nothing and the only way to fix the problem was to pull the battery, which reminds me of the Blackberry days.
I called Verizon today and they said this is not an issue (to them) on the Droid X2.
Anyone know what the problem is and how I might fix it? I'm a complete Android nyoob at this point and am clueless as to how to proceed.