I thought my Droid was bricked this morning

My phone is two weeks old and it just happened to me. I had it on the table next to me as I watched TV... When I went to go to bed my phone was blank. Nothing I did made a difference... I pulled the battery and put it back in and bingo the phone fired right up with 80% charge.... I dunno
 
I'm starting to think now that this is a software issue. Anyone agree, disagree? I figure, the phone probably didn't go dead, rather it's being unresponsive to input from the keys. I guess this doesn't explain my alarm not going off again, or having no affect when being plugged into the charger.
 
I had this happen once with my first droid that I got on launch day. I had to exchange it this past weekend, and had a chance to talk with a some sort of outside techspecialist stationed at the store. I know...I should have paid better attention to the company name below the verizon badge.

Anyway...I told him about this happening to my droid and he said that it was indeed a software issue. He said that while the android system is supposed to handle multiple programs running in the background...on occasion something can get stuck in a loop, or can continue to drain memory even though it should not be active.

This he claimed is what ultimately leads to the "dead phone". It is not actually dead...just stuck. Hence why the battery pull resets it with no after effects at all. He then recommended I download a task killer program and get in the habit of doing at least once a day.

I cannot guarantee he was not full of ****...but it sounded reasonable to me.
 
Yeah, a software error makes most sense to me. So, what app do we all have in common that is causing this issue? :)

I can make that an easy answer, since I just got my phone I only have put two apps on it, task killer and missed call...... see if you guys have any of those two.
 
This has happened to me twice, the second time just happened in the middle of the night last night.

Maybe 2 weeks ago, I picked my phone up from my desk to check the time, and it was on the red "droid eye" screen rebooting. Didn't notice any problems after that, so really thought nothing of it.

Then last night, I just happened to wake up in the middle of the night and went to check the time. The screen was black, and couldn't turn it on using the power button or the slider. Had to pull the battery. Worked fine after that, but now this has me worried. I'm actually not too worried about the phone itself, but about what would have happened if i didn't see that the phone was off. My alarm clock wouldn't have gone off, and I would have been in lot of trouble at work.

Could it be a loose battery connection? maybe if the phone gets jarred or shaken the battery comes loose? but the phone was just sitting on my nightstand both times it went dead?

I dunno....
 
Yeah, a software error makes most sense to me. So, what app do we all have in common that is causing this issue? :)

I can make that an easy answer, since I just got my phone I only have put two apps on it, task killer and missed call...... see if you guys have any of those two.

It's task killer. Happened to me once, uninstalled task killer never happened again. Trust me...it's task killer. Completely unnecessary for this phone.
 
I thought the same thing happened to my phone this morning. My alarm didn't go off, missed a class I really can't miss.

I've done everything I can think of, this phone isn't turning back on. :(

Taken the battery out, placed it back in, still nothing. Taken battery out and connected to phone to the charger, still nothing. With battery in and connected to the charger, still nothing.

I cannot get my phone to turn on. And no, I didn't brick it... I haven't gotten around to rooting the phone yet. I have 2.0.1 and all basic apps. It was on the cradle last night.

I have a feeling I need to go to Verizon, don't I?
 
So it appears for my case, it too was not dead. For some reason, even though the phone was on the charging cradle (and yes, connected properly with the mini-usb pins making a connection), the phone decided not to charge. I've seen the Motorola M logo quite a few times, on occasion getting the phone to boot.

I don't know why I couldn't get the phone to boot with the battery removed and power connection made, that typically can work regardless of battery condition since it is not there.
But right now the phone is showing charging, and 5%. Actually the case or not, no idea. Just glad to see the phone staying on this time.
 
Attention anyone who thinks they know what a 'bricked' device is:
Brick (electronics) - Wikipedia, the free encyclopedia

For the record, I am one to argue the validity of wikipedia entries for the simple reason that it's maintained by a subset of the same masses that are incorrect in their definition of bricked, but here's an excerpt:
"In the strictest sense of the term, bricking must imply that software error has rendered the device completely unrecoverable without some hardware replacement."

Please stop saying 'bricked' until your device is actually worthless.
 
OK, for one, I was immediately under the impression that my device was useless. Hence, my thread title "I thought my Droid was bricked". Did you even read my original post? After further investigation, my device was in fact operational and from then on out I never used the term "brick" again.

Secondly, why make a new thread reiterating your post? :icon_ nono2:
 
I also have experienced my Droid shutting off at least twice since I have had it for approx. 2 weeks. I took it back to Verizon and they swapped it out with a new one since I was still within my 30 day grace period. I have not had any shutdowns with my new phone but its only been 5-6 days, and this time I did remove Task Killer so will see. It would be nice to have some idea of the cause.
 
Back
Top