Droid Shut Off and Required Battery Pull This MorningSupport


Last Updated:

  1. PearlMikeJam

    PearlMikeJam Member This Topic's Starter

    Joined:
    Nov 23, 2009
    Messages:
    9
    Likes Received:
    0
    I got up this morning and check a couple of emails. About a half hour later, I went to check my phone and it was unresponsive. I could not get it to do anything. I tried holding down the power button and got nothing. I finally had to pull the battery and wait 30 seconds to get it to boot.

    Has anyone else experienced this? Was this a fluke or is my Droid dying after a month?
     

    Advertisement
  2. spiritskeeper

    spiritskeeper New Member

    Joined:
    Mar 3, 2010
    Messages:
    4
    Likes Received:
    0

    I also have had the same issue twice now. I just got my droid 3 weeks ago. It only happened after I rooted and I am thinking of unrooting. Any answers to this would be helpful.

    Thoughts?
     
  3. johnlgalt

    johnlgalt Antidisestablishmentarian VIP Member

    Joined:
    Oct 28, 2009
    Messages:
    9,416
    Likes Received:
    1,919
    This can happen whether you're rooted or not. Personally, with as many different ROMs as I try on my phones, I expect this daily, and experience it weekly.

    However, if you have not rooted (OP) then watch your phone carefully - if it happens again, you need to start looking at your apps, b/c one of them might be doing something stupid on your phone.

    If you are rooted, then double what I just said - root access allows you to do things that you normally cannot do - and that means messing with system files and such, which can have dire consequences.

    I am not saying this is a direct cause of rooting - I always prefer to test a system first and then make a determination, and 99% of the time it is some app or another being stupid. A lot of the apps in Market, although they don't actually say it, are, in fact, Beta-level apps, meaning there are bugs, inconsistencies, and flaws that need to be worked out.

    Comes with the territory.

    basically, if it doesn't happen again, you're cool. If it happens very occasionally, you'll need to dig deeper and see if it is an app. If it happens frequently, you need to look now and figure out if it is an app or if it is your phone. And if you just got your DROID and are still within the 30 window, forget troubleshooting, go get a new in-warranty replacement and be done with it.

    (If you're within 30 days of purchase and they offer you a refurb, DO NOT TAKE IT - demand a new one.
     
  4. spiritskeeper

    spiritskeeper New Member

    Joined:
    Mar 3, 2010
    Messages:
    4
    Likes Received:
    0
    Thanks for the fast response. Unforunately it did it a 3rd time about 30 minutes after I posted last. I charged my droid and unrooted. I am now completely stock again. Seems to be running just fine now.

    It was probably a conflict in two apps that do basically the same thing. I am not used to dead phone and doing battery pulls. I came from an omnia i910 windows phone running custom software so the droid and android is a new learning curve for me.

    I think I will say stock for a few days to see if I can make it repeat. Again thank you for the fast response. I think I like it here.
     
  5. johnlgalt

    johnlgalt Antidisestablishmentarian VIP Member

    Joined:
    Oct 28, 2009
    Messages:
    9,416
    Likes Received:
    1,919
    Glad you like it here, this place really is a great source of all sorts of knowledge.

    Your surmise is probably correct, in that a pair of apps were conflicting and causing some sort of instability. Since you lost root and the issue went away, I'd look hard at the apps you have installed.

    BTW, I did not realize wen I first replied that that was your first post, so welcome to the forums!
     
  6. Shadowtech

    Shadowtech Well-Known Member

    Joined:
    Dec 29, 2009
    Messages:
    434
    Likes Received:
    36
    This can happen pretty easily with rooting, I have had it happen to mine quite a few times after a rom flash. For some reason the phone could just not like the kernel, or anything else for that matter. Unless you do a complete wipe before each flash, there's always a chance of some files not working well together.

    Since you are already rooted anyway, I would try out a couple different roms and see how they do. The performance gain you'd get from some of the new ESE53 roms is quite nice over stock.
     
  7. Phases

    Phases Community Manager Administrator

    Joined:
    Sep 9, 2008
    Messages:
    8,498
    Likes Received:
    18,871
    This happens to me somewhat regularly. Including again a couple minutes ago. Not rooted. Don't have tooo many apps installed, either. Just removed five or six though, just in case.
     
  8. Shadowtech

    Shadowtech Well-Known Member

    Joined:
    Dec 29, 2009
    Messages:
    434
    Likes Received:
    36
    As I seen someone state elsewhere in this forum.. it's probably due to the fact that a lot of apps are essentially "beta" programs. That's the problem with these phone app markets.. people rush apps to get in on the quick money, then worry about making their stuff stable.
     
  9. johnlgalt

    johnlgalt Antidisestablishmentarian VIP Member

    Joined:
    Oct 28, 2009
    Messages:
    9,416
    Likes Received:
    1,919
    Lol - actually, I mentioned it above in my first reply....

    But, yeah, I have been seeing more and more phones non-rooted phones go stupid in the last week or so, and it is mind boggling.

    Or, could it be that there is some sort of update being pushed to non-rooted (and therefore non-OTA-blocking) phones?
     

Share This Page

Loading...