Droid 3 Freezing - Motorola Droid 3

I've been having this problem since around the time I first flashed Eclipse 2.2.2 and got on to the .906 update. When I leave my phone idle for about 30min or the screen is just off for prolonged periods of time, it will just freeze. I can't wake it up. Pressing the power button and long pressing the power button both do nothing. I've tried calling the phone but it doesn't answer. The only thing I can do is do a battery pull. It works perfectly fine when it's on, but it's kind of annoying to do a battery pull. This happens on Eclipses 2.2.2, Eclipse 3.0, and Maverick 4.0. Any suggestions?
EDIT: found out the freezing was caused by having 2 CPU apps. I had Voltage Control and SetCPU both installed at the same time so it was causing this. MODs feel free to close thread

Related

Captivate Random Shutdowns - possible reason

I think I found a possible reason for the Captivate random shut down problems.
It seems to me that the battery might be the culprit. My phone starts random shutdowns once my battery reaches below the ~70% mark. When fully charged, or when charge is over 70% it is generally sticking up. I am expecting a new battery (from the warranty dept) on Monday, and will post if I am still seeing random shutdowns.
It might be a good place to start with to see when ur phone is shutting down. Is it like fully charged, or when charge is below a certain point.
I put in Cognition 2.4.1 ROM last night, and ensured my battery is over 80% all the time. My phone current up-time is 15:11:52 as I am typing this.
I hope this helps.
Mine shut down on me 3 times within an hour of taking it off the charger with a full charge yesterday morning, hasn't done it since. That's about 36 hours and another overnight charge. The day before it shut down twice eight after taking it off the charger, the second time it wouldn't start back up. I had to restore with cwm so it would seem to be random.
Sent from my SAMSUNG-SGH-I897 using XDA App
Had the same problem
I had the same problem with my phone randomly shutting down. I re-flashed it and it worked fine, download all my apps again and it started doing it again. So re-flashed a second time and put the apps on one by one with no problems. After I installed Memory Booster it started shutting down again. The app kept killing a system utility and that caused the phone to shutdown on its own. Removed the app and installed the rest and haven't had any trouble since. Hope this helps.
InfiniteImmortal said:
I had the same problem with my phone randomly shutting down. I re-flashed it and it worked fine, download all my apps again and it started doing it again. So re-flashed a second time and put the apps on one by one with no problems. After I installed Memory Booster it started shutting down again. The app kept killing a system utility and that caused the phone to shutdown on its own. Removed the app and installed the rest and haven't had any trouble since. Hope this helps.
Click to expand...
Click to collapse
What app is this, may I ask?
I am thinking of taking off the task manager in 2.2. I think this app is trying to clear out memory at intervals. When I rooted i9000 rom I saw a samsung utility that let me choose the mode of cleanup - normal or aggressive. I have a feeling this has something to do with memory clean up software possibly built-in into the 2.2.
Update:
The issue doesn't seem to be in the battery. I charged it full to 100%, and started a video playback. It went on for like about 4.5 hours, and then when battery reached 15% it came out saying low battery. Since then I have put it in 100% brightness and screen timeout to 10 mins, n moving the screen every once in a while to not let it go to sleep. Didn't die on me once during this process.
I will let it drain all the way down, and then charge fully n see if battery faulty calibration is causing these random shutdowns.
* fingers crossed * hoping this would let me out of these random shutdowns.
There is already an existing thread about random shutdowns, and the possible culprits have been discussed quite a bit. If you need a link I'll gladly supply it.
http://forum.xda-developers.com/showthread.php?t=731560

[Q] Battery discharges when off and slow boot

Hi all,
Just rooted by Nook Color with CM7 and I 2 fairly major problems. I searched threads but could not find anything specific to my specific problems.
First, last night, I turned off the Nook Color by holding down the button on the left and selected "Power Off". When I booted it (after a long wait, see below), it booted but the battery was very low and I checked the battery life settings using Spare Parts app and it said it had been Running 100% of the time since last unplugged. Its as if it didn't power off when I asked it to.
Second, my reboots are super slow....I get the "Read Forever" words when I hold down the left button but it takes several minutes before I have to press the bottom button to get the screen (no indication that its booting or anything).
Any help would be greatly appreciated.
Why are you shutting it down at all? Just let it sleep. Even with the current sleep issues, it will only use 1% or so of the battery that way... try it. I hardly ever power off my nook. As for the slow boot time, there are a lot of reasons...
1. Did you install the OC kernel and forget to wipe dalvik cache?
2. Which version of CM7 are you running? a nightly, or the 7.0 release?
I just did a test.
CM7 cm_encore_full-63
update-CM7-dalingrin-OC-emmc-040411 set at ONDEMAND 300-1100
At 2am battery was at 100%
Standby for 9.5 hrs and it consumed 16% battery.
Not looking good to leave in standby.
Do you leave wifi on? It could be syncing or trying to sync the whole time it is on standby.
xdatoast said:
Hi all,
Just rooted by Nook Color with CM7 and I 2 fairly major problems. I searched threads but could not find anything specific to my specific problems.
First, last night, I turned off the Nook Color by holding down the button on the left and selected "Power Off". When I booted it (after a long wait, see below), it booted but the battery was very low and I checked the battery life settings using Spare Parts app and it said it had been Running 100% of the time since last unplugged. Its as if it didn't power off when I asked it to.
Second, my reboots are super slow....I get the "Read Forever" words when I hold down the left button but it takes several minutes before I have to press the bottom button to get the screen (no indication that its booting or anything).
Any help would be greatly appreciated.
Click to expand...
Click to collapse
If you powered off your NC, it would not be using battery.. Period. Running 100% of the time is normal right now on CM7, but again, it was not running while it was powered off.
Slow boot? Are you using an SD card? If so, get a new one that's faster.

Touchscreen lock-up in CM7

Currently running CM7 7.0.3-encore-signed off of a 8gig c4 sandisk.
I downloaded a free MMO called Pocket Legends and while I was having a good old time killing zombies in one of the dungeons when all of a sudden the touchscreen sensors froze up, but the game animations continued on normally.
I exited the game using the N button. I was unable to do a reboot as the touchscreen still wouldn't respond. Another strange thing is that the NC wouldn't go into automatic sleep mode even after 30 minutes of just letting it sit undisturbed.
After fidding around with it I was got it to power down by pressing and holding the on/off and N buttons. After reboot things appear to be normal, except battery spy and gauge battery widget are reporting the battery at 100%, when it was at 71% before a 2nd reboot.
Anyone else have a similar experience as this?

My phone suddenly shut down

Hello deer XDA friends
My phone suddenly shut down by it self every 3-4 days sometimes when the battery above 50% , when i try to booted up it wont until i remove the battery then it start normally .
what do you think is the problem here?
sorry my English is very bad
Eltoro2010 said:
Hello deer XDA friends
My phone suddenly shut down by it self every 3-4 days sometimes when the battery above 50% , when i try to booted up it wont until i remove the battery then it start normally .
what do you think is the problem here?
sorry my English is very bad
Click to expand...
Click to collapse
You might have some rogue apps running that overheat the cpu. Look in taskmanager which apps are using much power. Download cpu spy free from the market to see if the cpu comes in deep sleep or not.
Good luck
I also have it occasionally. POWER+HOME button to reset. One time need to remove battery. Actually I felt like phone is still open but screen cannot come back. Next time I will call my phone when it happens.
I've had this happen twice. Both times a battery pull fixed it. At first I thought the phone was going dead, completely black and the power button would do nothing, but the second time I hit the volume button several times and it started beeping, so even though it looked completely dead, it was still turned on. I don't know what the problem is, but probably something software.
Which ROM/kernel are you using?
Any special CPU profiles?
How's the temperature?
Sent from my GT-N7000 using XDA App
happened a few times too. So, last time when I found it "dead" I did some test.
1. used my bluetooth headset (MW600) tried to play music, surprisingly music started playing but screen cannot turn on by any keys.
2. I called myself using another phone, Caller can hear ring normally and the call NOT dropped to voice mail, however my Note doesn't ring at all, screen still cannot turn on by any keys.
So it doesn't look like it's auto switched off by overheating, seems like unable to completely wake up after deep sleep.
Phone using Stock Rom(rooted with CWM), with System Power Saving mode turned on. I suspecting it's related to the power saving mode.
I'm also stock 2.3.5 rooted, with CWM, but do not have system power saving turned on. I haven't noticed any heat, but haven't monitored temperatures.
Do you also have the stock kernel?
Are you using setCPU?
Try using cpuspy, from market.
Sent from my GT-N7000 using XDA App
Dead
I also had this case yesterday for the first time. I bought it the 30th november.
Did not want to wakeup, darkscreen. Only way to recover was to remove battery. I am on 2.3.6 french.
I do not use Setcpu.
Mine is unroot. In other words, stock ROM and kernel.
I think it is software problem. And I think it is either Samsung software or Android system. Someone need to run logcat though.
For your information.
When you sure it's sleep dead(not shutdown cause by no battery)
Disconnect any charger/USB connected. Press and hold the power switch for around 10-15 sec,
that will restart the phone, no need remove that inconvenient back cover for battery pull.
alexchan.ccs said:
For your information.
When you sure it's sleep dead(not shutdown cause by no battery)
Disconnect any charger/USB connected. Press and hold the power switch for around 10-15 sec,
that will restart the phone, no need remove that inconvenient back cover for battery pull.
Click to expand...
Click to collapse
The first time it happened to me I tried holding the power button but it didn't work, so I did the battery pull. I haven't tried again since then.
Sudden Shutdown
Mine too i've experience it 3 times, this happen when im opening some applications sudden black screen and restarted cannot access back button, haven't tried the power button. It just restarted thats it!!! Im at stock kernel unrooted 2.3.6 so what do you think guys should i root or just wait for Ice Scream Sandwich upgrade?
maxh said:
The first time it happened to me I tried holding the power button but it didn't work, so I did the battery pull. I haven't tried again since then.
Click to expand...
Click to collapse
See if you hold the button long enough for over 10 seconds, before I would release and think power button not work after 7-8 seconds.
I have experienced "sleep of death" many times on different firmware versions. I has never happened since I flashed KL3. I'm on AbyssNote 2.1 kernel.
update:
since I replaced the stock launcher & locker, no more sleep dead issues. I suspect the problem source is stock locker or some stock widgets. Also, battery last longer too.
now using: widget locker + awd launcher ex + multi-picture live wall paper.
For those wonder why phone can't wake up for some reason, a user at the green power app forum had got the solid evidence.
http://greenpower.pouzerate.com/ind...-s2-freeze--black-screen?limit=6&start=48#465
"And if then it looks like the touchwiz launcher has crashed and changed pid when restarting without telling the InputManagerService about it, so it can't wake up the screen for that reason."
So the culprit is the stock launcher. And this matched with my experience even after I uninstalled green power free, my phone still have "not waking up" problem . But since switched to use 3rd party lock and launcher for a month, the "not waking up" never happens again.
This happened to me for the first time yesterday, when I eventually got it restarted by removing the battery, it was at 88% so don't think it was overheating, otherwise it would be much lower. Also I had Go launcher Ex running so touch wiz unlikely to be the culprit. Maybe some widget, I have loads!
alexchan.ccs said:
For those wonder why phone can't wake up for some reason, a user at the green power app forum had got the solid evidence.
http://greenpower.pouzerate.com/ind...-s2-freeze--black-screen?limit=6&start=48#465
"And if then it looks like the touchwiz launcher has crashed and changed pid when restarting without telling the InputManagerService about it, so it can't wake up the screen for that reason."
So the culprit is the stock launcher. And this matched with my experience even after I uninstalled green power free, my phone still have "not waking up" problem . But since switched to use 3rd party lock and launcher for a month, the "not waking up" never happens again.
Click to expand...
Click to collapse
This actually fits well with my experience. Touchwiz crashes on me occasionally and just last night I was experiencing the sleep of death thing. This time I thought it might have been the battery, so plugged in the charger and that somehow woke the screen back up to show touchwiz in the process of starting up, caught red handed!
This has happened to me as well 3 times, and every time it has been related to using a highres picture on the stock locker. It would lag out on unlock, black screen of death, which i would have to batt pull to fix. Didn't realize i had to hold down the power button for 15 secs to achieve the same thing. Have since switched to a low res pic on lock screen and haven't experienced the issue since. Will try the alternative locker solution if it happens again.

[Q] Galaxy Note becomes unresponsive, heats up, and drains battery when idle

Hey Everyone! Want to share with all about this problem i have been facing.
This GT-N7000 of mine has a very strange problem that has been bugging me since the beginning.
Be it using stock ROM (the days of being in totally stock ICS and jellybean ROM) or now, when i use CM11 4.4.4 (Created by the nice people here on XDA and cyanogen), if i leave the phone idle (e.g screen locked and turn off, when i don't use it and place it in my jeans pocket or lying on the table), once every few days (basically whenever the phone feels like it), when not connected to the charger, it will:
1) randomly decide to become unresponsive (means you can't wake the phone up when pressing any physical buttons or touching the screen)
2) Phone becomes hot while in this unresponsive state (I assume the processor is fully utilized, but doing something totally irrelevant and silly)
3) Need to do a battery pull before you can turn on the phone again
4) Notice upon boot that x% of battery was used up. The battery stats would indicate a break, and sudden drop from 72% of battery to 48% battery.. In other words, it seems the phone does not know what it was doing when it was unresponsive. The faster you catch the phone in this state, the more battery you'll have left. if this happens and you didn't catch the phone in this state, the phone would happily guzzle all the life out of your battery, to 0%.
Now that i am rooted and running CM11, i Digged a little deeper, and it seems that after each unresponsive state reboot, setCPU will indicate that there was alot of CPU usage at 1.4Ghz. At first i didn't bother about it, until i remembered my CPU settings was only supposed to run at 500mhz Maximum when my screen is off, or at 1Ghz when battery is below 80% and screen is on. My CM11 kernal is standard kernel and has NO overclock/underclock.
This means the phone somehow managed to overide setCPU while being in unresponsive state and remain clocked at 1.4 ghz even though the screen is off, thus draining the battery extremely quickly and becoming hot
I have tried multiple factory resets with Stock rom, then Re-flash stock rom with ODIN, to changing to CM11 ROM, and i still have this issue. I do not have a sim card Or SD Card plugged into this phone. (Even with sim card/sd card connected, it still has this issue)
Any other users that encounter this? And has anyone found a way to solve this? Thanks for your inputs!

Categories

Resources