Related
My wife has a completely stock Droid X and she always has the weirdest issues with her phone with it locking up, freezing or hanging up..
Sometimes the phone recovers, other times it needs to be rebooted manually.
Is this a known issue with this phone?? I have the HTC incredible and have no issues like this.
I havent had a problem or heard of this. Is she under warranty and get it swapped out? If not has she tried to do a wipe/factory reset? While off hold the power and menu key at the same time. A screen will come up. press the search button. Use the volume keys to scroll up and down. Go to wipe/factory reset and press the camera button.
My wife has a stock D2, and it sometimes likes to open up the voice search, or she will be typing a text message, and the g key will open the browser to google.com, or just randomly freeze up..... Maybe women have a different body chemistry that acts like a mini EMP that just destroys all electronics.... Everything electronic she has ever owned has major problems, yet mine last years........
Droid X freezing - having to battery pull.
I've been having similar issues with my Droid X. It will randomly, and often, lock up for a while, then come back to life usually. It's really annoying if your browsing the web and all the sudden the phone freezes for 20-30 seconds.
When it freezes completely, it will just freeze and the screen will remain on. I have to then pull off my protective cover and battery pull to reboot.
Battery pulls happen about once every 2-3 days. Freezes that recover are happening 5 or 6 times a day if not more.
The brief time I had the phone on stock, the issue was occuring. I ignored it and figured surely this won't happen after I root it. I'm now running latest Liberty ROM and it's still happening. Problem definately gets worse if I overclock. I'm wondering if the CPU can't even handle 1000 Mhz and needs to be underclocked just so this thing can run stable.
I'm going to test that out and see if the weird freezing and force closes go away. But it will suck loosing speed.
I unfortunately can't return my phone as I bought it used on Craigslist.
buckweet said:
My wife has a completely stock Droid X and she always has the weirdest issues with her phone with it locking up, freezing or hanging up..
Sometimes the phone recovers, other times it needs to be rebooted manually.
Is this a known issue with this phone?? I have the HTC incredible and have no issues like this.
Click to expand...
Click to collapse
Its likely due to the fact that the stock Droid x firmware sucks a load of ass. The factory blur is perhaps the biggest waste of time I've ever seen. I've had both my dinc and fascinate and x since launch day and the only remedy I've found to stop the x from doing this is flash livery. Only way to fix it at all.
Sent from my DROIDX using XDA App
Yeah man sounds like you have a bad device. If a data wipe/reset wont do it you must have a have bad device . Go back where you got it and ask for an exchange
Sent from my DROIDX using XDA App
deitiphobia said:
I've been having similar issues with my Droid X. It will randomly, and often, lock up for a while, then come back to life usually. It's really annoying if your browsing the web and all the sudden the phone freezes for 20-30 seconds.
When it freezes completely, it will just freeze and the screen will remain on. I have to then pull off my protective cover and battery pull to reboot.
Battery pulls happen about once every 2-3 days. Freezes that recover are happening 5 or 6 times a day if not more.
The brief time I had the phone on stock, the issue was occuring. I ignored it and figured surely this won't happen after I root it. I'm now running latest Liberty ROM and it's still happening. Problem definately gets worse if I overclock. I'm wondering if the CPU can't even handle 1000 Mhz and needs to be underclocked just so this thing can run stable.
I'm going to test that out and see if the weird freezing and force closes go away. But it will suck loosing speed.
I unfortunately can't return my phone as I bought it used on Craigslist.
Click to expand...
Click to collapse
Before reading all of this....note that this is just me providing a POTENTIAL explanation of why some people's phones seem to reboot more than others... this is not a generalization for all... It may not apply to you...
I think that random reboots (especially often) are related to potentially bad hardware, not being on the 2.3.34 OTA update...or user error (don't get mad, please let me explain this part!). I found that after moving off of 2.3.15 OTA that my phone was much more stable.
I notice from back when I first had my Droid X that I went crazy loading up lots of apps, and throwing widgets all over my home screens... I had custom themes flashed and lots of other stuff. While yes, blur does suck up more system resources than custom ROM's without it... you can run a phone with Blur without constant reboots.
The more apps that you have on the phone (even if not running) eat up resources. Along with that, the more widgets or notifications you have on your homescreens, the more resources that the phone is chewing through... With that said, you can SEEM to not be running anything on the phone, but the widgets in the background process' can be using up precious memory that cause the phone to lag or reboot.
Like I said at the beginning, if you don't have a lot of extra widgets and programs loaded, then yes, I would say that really sucks that your phone reboots. Moto's way of handling a resource issue (in most cases RAM)... is to reboot the phone to clear memory.
If you happen to have a lot loaded on your phone...try not to use a lot of widgets, and cut back on some un-needed apps... See if the phone reboots as often. Again, this is not me blaming anyone for their phone rebooting, simply my understanding of technology from personal experience.
My G2 is running the stock ROM, not rooted. I rooted my G1 and ran every ROM I could get my hands on, but with free WiFi tethering and a clean OS, I find no reason to root my G2... yet.
Lately, I've been encountering a really slow boot time - almost 2 minutes from power button to OS up and running. I do have a lot of widgets, but I don't have an excessive amount of apps. Do the widgets slow the bootup? They're not even ready when I unlock the screen (after the network becomes available), and I've already waited 2 minutes.
My wife's G2 takes about 20-30 seconds to boot up. What gives?
It's the widgets. The more you have, the longer the boot time will be in order for everything to load up!
Thanks! I got wise and rooted/installed CM7. Bout damn time. WAY faster than before.
Yeah I noticed the same thing when I tried out CM6 (which I'm using now).
Before it was taking more than a minute, now it's up pretty quick.
I would like to start this out by saying that I have had my Bravo since January 16, and have loved every minute of it. This has been my first Android (Came over from my iPhone 3G). I was extremely excited to finally get the upgrade to 2.2, even though I decided to wait to officially download it OTA.
Since I got my phone, I had no more than three to five apps force close on my using the stock launcher. I rarely noticed much of any lag while working with my phone, and I never once had any issues with the phone rebooting itself on me.
Since I updated my phone on Saturday I've been plagued with all of these issues. Immediately after updating, I noticed my phone was running very hot, and my battery drained to 50% within an hour or two without me even running anything stressful on it. I restarted it twice and since then I haven't noticed any significant issues with my battery, or the phone seeming to run it's processor excessively.
But, I have constant lag, making tasks that were extremely quick and easy before the weekend be significantly more difficult and frustrating. Today I've even noticed that the lag is so bad that I am not even able to use Swype because the phone takes so long to register any touch's it doesn't register anything other than the first and last letter I swyped across. In addition, my phone has rebooted itself 3 times within the last three days I've been using it, an issue that has not happened once in the three months before this weekend.
I will regularly be trying to do things on my phone and it will lag, causing the phone to freeze for 20-30 seconds at a time, and then trying to perform every touch it received in those 20-30 seconds in a scant second after it recovers.
I have noticed some issues not regarding lag, but sometimes it has been difficult for my phone to initiate calls. I have tried to call my wife, and it took 5 times before the call would finally go through, it was immediately ending the call right after I pressed the call button.
I love my phone and the capabilities of the Android system. Until now I haven't had any problems at all with it. Can you help me try to figure out what's happening, and if there are any ways to fix my phone? I haven't gotten around to rooting my phone since I've gotten it, but have been planning on it.
roadkizzle said:
I would like to start this out by saying that I have had my Bravo since January 16, and have loved every minute of it. This has been my first Android (Came over from my iPhone 3G). I was extremely excited to finally get the upgrade to 2.2, even though I decided to wait to officially download it OTA.
Since I got my phone, I had no more than three to five apps force close on my using the stock launcher. I rarely noticed much of any lag while working with my phone, and I never once had any issues with the phone rebooting itself on me.
Since I updated my phone on Saturday I've been plagued with all of these issues. Immediately after updating, I noticed my phone was running very hot, and my battery drained to 50% within an hour or two without me even running anything stressful on it. I restarted it twice and since then I haven't noticed any significant issues with my battery, or the phone seeming to run it's processor excessively.
But, I have constant lag, making tasks that were extremely quick and easy before the weekend be significantly more difficult and frustrating. Today I've even noticed that the lag is so bad that I am not even able to use Swype because the phone takes so long to register any touch's it doesn't register anything other than the first and last letter I swyped across. In addition, my phone has rebooted itself 3 times within the last three days I've been using it, an issue that has not happened once in the three months before this weekend.
I will regularly be trying to do things on my phone and it will lag, causing the phone to freeze for 20-30 seconds at a time, and then trying to perform every touch it received in those 20-30 seconds in a scant second after it recovers.
I have noticed some issues not regarding lag, but sometimes it has been difficult for my phone to initiate calls. I have tried to call my wife, and it took 5 times before the call would finally go through, it was immediately ending the call right after I pressed the call button.
I love my phone and the capabilities of the Android system. Until now I haven't had any problems at all with it. Can you help me try to figure out what's happening, and if there are any ways to fix my phone? I haven't gotten around to rooting my phone since I've gotten it, but have been planning on it.
Click to expand...
Click to collapse
Something probably is messed up in the upgrade process.
Simple solution, flash the 2.2 sbf and you should be good.
roadkizzle, Something doesn't sound right at all with your update. I would try to remove the battery for a minute and reboot. If you still have issues I would try a factory data reset. If that doesn't cure your ills then flashing the 2.2sbf as bandroidx suggested may be in order.
Alright, I flashed the SBF file to the phone through RSDLite, and from what I can see it went through correctly. My only question now is do you think I'll need to try to re-install the full update? Or is that similar to what I did?
roadkizzle said:
Alright, I flashed the SBF file to the phone through RSDLite, and from what I can see it went through correctly. My only question now is do you think I'll need to try to re-install the full update? Or is that similar to what I did?
Click to expand...
Click to collapse
flashing the sbf already updated your phone to 2.2. You don't need to do anything else
I hope reflashing did the trick for you. That experience sounds nasty...
Sent from my MB520 using XDA App
Well, after a couple of hours of playing with my phone it's seeming better. I have been playing a few games of Worms, and my normal surfing the internet and so far I haven't noticed any real lag. The test will be my day through tomorrow.
I was just really confused because I was following the instructions from the Flashing SPRecovery SBF to a Motorola Droid youtube video, and his SBF file really seemed to only change the recovery screen. It looked like he still had to go through the actual update.zip process to make the actual updates to his phone.
Alright it's official, flashing the sbf did not fix the lag issues. My phone hasn't had a critical malfunction and reboot itself yet today, but the lag is unbearable.
roadkizzle, It sounds like you are still having issues. If you look at the system version in "about phone" in settings menu does it say version 37.4.0.MB520??
Yes, it says Version.37.4.0.MB520.ATT.en.US
roadkizzle said:
Alright it's official, flashing the sbf did not fix the lag issues. My phone hasn't had a critical malfunction and reboot itself yet today, but the lag is unbearable.
Click to expand...
Click to collapse
what apps do you have installed?
look in task master and get rid of any auto-ends and reboot and see if that makes a difference
Well, immediately after removing the AT&T apps from the auto-end list and rebooting, I thought I noticed some lag initially, but I've let it run for a few days now doing everything I was before and I've not been having any of those issues recently.
I'm not sure what it was. I wasn't very aggressive adding apps to my auto-end list, really just Maps and the AT&T apps. I added maps after a while because when I would use it once it would stay open and I'd notice later on that it would have been a major consumer of my battery, and I couldn't figure out how to close it fully.
Glad to hear things are going better. I had some issues totally unrelated to the apps I had in auto-end but pulling all of them off of auto-end got rid of the issues. Froyo is supposed to minimise the need for having to add apps to auto-end in task manager. Regards
(SIA for the long post)
roadkizzle - my situation sounds very similar to yours and I wanted see if you are also seeing a couple of other symptoms I've seen beyond what you have indicated. This has been an issue from early on for me. At first it seemed to be associated to when the battery was low, but it is now ever increasingly interrupting my use of the phone. I was hoping 2.2 might resolve some of this, but it hasn't.
Background: Purchased/activated phone early Jan 2011; recently upgraded to the 2.2 sys and used the official channels; all apps I've added are lightweight stuff (ex: notepad-type stuff, weather widget) and I have pushed most unused stuff to the auto-end list.
Similar symptoms: I see the same power drain and high CPU usage when using maps/navigator (really evident on a recent trip). Still monitoring if some of that can be attributed to use of the GPS.
I'm getting a similar lag though I wish it was only for the short period you are seeing. I've only rarely been able to just put the phone down and have it responsive when I get back to it. Maps/Navigator were especially susceptible to this problem, and it seemed consistent with the 90%+ CPU usage often seen when they are running.
I don't use swipe, but the keypad is most often what is being used when the lag kicks in... the entire phone just goes completely unresponsive, including any and all other input such as the hardware home/back keys, etc.
In addition: Better than half the time that the qwerty touchpad becomes unresponsive, I see sporadically entered random keystrokes to my messages... everything from initiating the voice input to entering several dozen spaces or just simple random characters. This happens at a random, often changing rate and I see the keys lighting up and the haptic responses happen as if I were touching the keys, but they are not from any delay in the input. Once ruling out an exorcism, this has started me thinking I might have a hardware issue with the touchpad. The phone has not been dropped or roughed up in any way, so if it is HDWR, it's a manuf issue.
Luckily.... in 99% of the cases where this happens, using the HDWR power button to cycle the screen through a sleep and back resolves the issue. Not a big deal unless you have to do it 3 times to send one text/mail. This has me constantly thinking about items on the auto-end list but I have not unearthed anything to support that.
The other 1% of the time I have had to reboot the phone, but in those cases I can't rule out 'user issues' due to just pure frustration. Task Manager has become my most freq used app, but often I see everything at 0% CPU and/or not running.
I'm wondering if any of these additional symptoms sound familiar...
thx.
humanque said:
(SIA for the long post)
roadkizzle - my situation sounds very similar to yours and I wanted see if you are also seeing a couple of other symptoms I've seen beyond what you have indicated. This has been an issue from early on for me. At first it seemed to be associated to when the battery was low, but it is now ever increasingly interrupting my use of the phone. I was hoping 2.2 might resolve some of this, but it hasn't.
Background: Purchased/activated phone early Jan 2011; recently upgraded to the 2.2 sys and used the official channels; all apps I've added are lightweight stuff (ex: notepad-type stuff, weather widget) and I have pushed most unused stuff to the auto-end list.
Similar symptoms: I see the same power drain and high CPU usage when using maps/navigator (really evident on a recent trip). Still monitoring if some of that can be attributed to use of the GPS.
I'm getting a similar lag though I wish it was only for the short period you are seeing. I've only rarely been able to just put the phone down and have it responsive when I get back to it. Maps/Navigator were especially susceptible to this problem, and it seemed consistent with the 90%+ CPU usage often seen when they are running.
I don't use swipe, but the keypad is most often what is being used when the lag kicks in... the entire phone just goes completely unresponsive, including any and all other input such as the hardware home/back keys, etc.
In addition: Better than half the time that the qwerty touchpad becomes unresponsive, I see sporadically entered random keystrokes to my messages... everything from initiating the voice input to entering several dozen spaces or just simple random characters. This happens at a random, often changing rate and I see the keys lighting up and the haptic responses happen as if I were touching the keys, but they are not from any delay in the input. Once ruling out an exorcism, this has started me thinking I might have a hardware issue with the touchpad. The phone has not been dropped or roughed up in any way, so if it is HDWR, it's a manuf issue.
Luckily.... in 99% of the cases where this happens, using the HDWR power button to cycle the screen through a sleep and back resolves the issue. Not a big deal unless you have to do it 3 times to send one text/mail. This has me constantly thinking about items on the auto-end list but I have not unearthed anything to support that.
The other 1% of the time I have had to reboot the phone, but in those cases I can't rule out 'user issues' due to just pure frustration. Task Manager has become my most freq used app, but often I see everything at 0% CPU and/or not running.
I'm wondering if any of these additional symptoms sound familiar...
thx.
Click to expand...
Click to collapse
Try taking things off of the auto-end list. You shouldn't need the task killer because android manages apps on its own (it's supposed to manage apps better in froyo than in 2.1)
I've also had lag, especially when opening maps (the first time I open maps it often force closes).
Can anyone get the "lock pattern" screen without the slide to unlock? It seems like a common "Motorola 2.2" issue, but I can't figure out if it gets resolved through an update or not
kyngnothing said:
I've also had lag, especially when opening maps (the first time I open maps it often force closes).
Can anyone get the "lock pattern" screen without the slide to unlock? It seems like a common "Motorola 2.2" issue, but I can't figure out if it gets resolved through an update or not
Click to expand...
Click to collapse
it can be fixed through the settings.db in the com.android.providers.settings, but i dont remember what to edit inside.
or you can download No Lock from the Market
https://market.android.com/details?id=org.jraf.android.nolock
jorgonv said:
it can be fixed through the settings.db in the com.android.providers.settings, but i dont remember what to edit inside.
or you can download No Lock from the Market
Click to expand...
Click to collapse
NoLlock just seems to turn the lock screen on and off altogether?
I can get the screen lock on and off, I just can't get the pattern lock without the side-to-side swipe lock at the same time
This is messing with
PS . If you can't get your screen to stop locking all the time with froyo 2.2.1dissable it in the same location ID # 61 screen_lock set to 0. ),
Click to expand...
Click to collapse
and the settings menus.
There are several other seemingly lock-related database settings, but I'm worried about locking myself out
kyngnothing said:
NoLlock just seems to turn the lock screen on and off altogether?
I can get the screen lock on and off, I just can't get the pattern lock without the side-to-side swipe lock at the same time
This is messing with
and the settings menus.
There are several other seemingly lock-related database settings, but I'm worried about locking myself out
Click to expand...
Click to collapse
You can always sbf if you get locked out. your data will also be kept
Hi Guys,
I'm not sure if this is related to 4.4.2 or its a hardware issue, I've only noticed this issue this week.
When I wake my N10 and if I flip the screen around before unlocking it, it will hang and reboot.
It happens every time after putting the N10 to sleep for a few mins.
If I unlock it without rotating then flipping the screen around its fine.
Has anyone else had this issue? Anyway to fix it?
Hi
Just did it and it worked fine for me, I'm also running 4.4.2... You may want to try a factory reset before issuing this as a hardware problem
~Lord
"Time is too short to cry, long enough to try." - March of Time (Helloween)
Sent from my KitKat Nexus 10
on the same boat
Same behavior exactly observed on my tablet, during last week. I suspect something went wrong with the newest updates.
Random crashes with reboots, mainly when rotating on lock screen. Tried a factory reset, however, problem still persists.
Never had a single problem with my Nexus until now, worked like a charm. Also, I have not installed new Apps which to blame for this problem.
At the moment I'm trying things like disabling rotation or pattern unlocking, will see if something works.
I think I've seen this as well, on KOT49H. Not sure exactly how to reproduce it, but it's happened a few times.
Do you have modded/unlocked system? My nex is working like never before. It is twice as smooth and stable as it was on 4.3
I have never rooted/moded this tab and never ever had issues with it...
tapped from my nex
Well, disabling rotation seems to improve the issue a little bit, the random reboots are still there, but just less frequent.
Yesterday I had a couple of hangs-reboots doing simple tasks, like checking GMAIL or interacting with Google Currents widget.
In my opinion, this is not a hardware problem, it is, somehow, related with the 4.4.2. KOT49H update. My N10 worked perfect until this last update.
Ironically, I read somewhere that this update fixes the random reboot problem in a lot of faulty tablets. In my particular case, the "fix" seems to trigger the issue in my tablet
It is worth mentioning that my system is not modded or unlocked.
Updating situation ...
During the last week I have used the N10 With the automatic rotation disabled, in landscape mode. Non a single reboot.
This afternoon I just enabled automatic rotation again and the tablet rebooted itself almost instantly, at the second orientation change.
So, IMHO, This issue is only rotation-based, nothing to do with the lockscreen. It is kind of annoying.
Any help?
ManleyRowe said:
Updating situation ...
During the last week I have used the N10 With the automatic rotation disabled, in landscape mode. Non a single reboot.
This afternoon I just enabled automatic rotation again and the tablet rebooted itself almost instantly, at the second orientation change.
So, IMHO, This issue is only rotation-based, nothing to do with the lockscreen. It is kind of annoying.
Any help?
Click to expand...
Click to collapse
Hi,
Do you mind sharing a logcat when it happens? It would help a lot to see what's causing the problem.
~Lord
"Time is too short to cry, long enough to try." - March of Time (Helloween)
Sent from my KitKat Nexus 10
ManleyRowe said:
Updating situation ...
During the last week I have used the N10 With the automatic rotation disabled, in landscape mode. Non a single reboot.
This afternoon I just enabled automatic rotation again and the tablet rebooted itself almost instantly, at the second orientation change.
Click to expand...
Click to collapse
I never had this problem, but I just tried rotating twice before unlocking, and sure enough that does it.
There are still so many things that cause this device to reboot. I love the hardware, but god is it ever unstable
This is, I hope, my final update regarding this situation..
Well, It is kind of embarrassing to inform that the problem is, apparently, gone. I didn´t do anything to solve it.
So, it looks like some app or widget was causing the instability, and it must be fixed now via a recent update. Honestly I have no clue about who the culprit was..
Thanks, anyway, for your comments and support, and happy new year
Same issue
So it seems I have the same issue too, except I have a Galaxy S4 Touchwiz 4.3. Anytime I go into landscape mode, boom it freezes and reboots. If I disable rotation, then it'll just keep randomly freezing throughout the day. Never happened before, everything was happy go lucky and then I don't know what happened. I reinstalled kernels, took off recent apps I may have installed, tried a different modem, nada... This is a pain. Anyone else with similar issues other than OP?
sefuwl said:
Hi Guys,
I'm not sure if this is related to 4.4.2 or its a hardware issue, I've only noticed this issue this week.
When I wake my N10 and if I flip the screen around before unlocking it, it will hang and reboot.
It happens every time after putting the N10 to sleep for a few mins.
If I unlock it without rotating then flipping the screen around its fine.
Has anyone else had this issue? Anyway to fix it?
Click to expand...
Click to collapse
Ive seen this many times with 4.4.2 and 3. Now with 4 it likely fixed.
I had screen not rotating, I did a dalvik wipe and a cache wipe and haven't had a problem.
Sent from my Nexus 10 using XDA Free mobile app
Running 4.4.4, I just saw the issue again yesterday.
Thought I would share this here - though I believe this is effecting other Moto models as well.
The Moto app "CQATest" seems to be the culprit with major instability issues I've had since the Android Marshmallow update. Before the update, my phone was so smooth and fast. Then the update came, and I blamed it on Marshmallow. Screen response to anything was very slow. Sometimes completely unresponsive. If i tried to touch a notification in my notification bar, it might be 5-10 seconds later before anything would happen, and the app would open. Sometimes it wouldn't ever open at all. Or when Facebook did open, it might take another 10-15 seconds before it went to the item it had notified me about. The camera in particular was slow to respond - with visible lag whenever trying to take a video - or would just crash. The phone itself got into a fairly normal habit of rebooting itself several times a day. And on startup, sometimes it would take 3-5 minutes before it would finally get to the home screen. Simply unacceptable.
So yesterday I started Googling for answers, and ran across a thread on Android Forums talking about issues people were having with CQATest. I immediately went and found the app in the settings>applications menu, under "All Apps" - force stopped and disabled it, then rebooted.
Guess what? The phone boots normally again! And the general responsiveness and functionality are back to what it was prior to the Marshmallow update. I couldn't be more pleased right now - because I was getting very frustrated with what is a relatively new phone.
I'd be interested if others have experienced something similar? Or are having similar lag issues and try this solution to see if it works for you.
Mods - if this CAN be confirmed, it really should be shared with ALL Moto users who've been upgraded to Marshmallow and have similar issues. The Android Forums thread user was originated by someone on the Moto X for instance.
Thanks for your time and feedback.
Do you have any misbehavior since you've disabled CQA Test? Like something doesn't work... Are you getting better battery life? I think you should.
I have Moto X Force, didn't touch app and system is smooth, stable with great battery life. I suppose you have Turbo 2.
No apparent issues with anything else since disabling it that I can see. And yes, I'm on a DT2.
Zeljko1234 said:
Do you have any misbehavior since you've disabled CQA Test? Like something doesn't work... Are you getting better battery life? I think you should.
I have Moto X Force, didn't touch app and system is smooth, stable with great battery life. I suppose you have Turbo 2.
Click to expand...
Click to collapse
I have had CQA Test disabled before and after Marshmallow and notice no misbehavior. I also have been using advanced calling since i got the phone on launch day and have never had a problem with the call quality as others have.
CQATest not causing problems on my Droid Turbo(1)
I just got a refurb Droid Turbo on Marshmallow, and I've had others. I was experiencing some of those same issues that you described.... extremely slow boot and shutdown, and lag on launching apps or other screen clicks.
I just disabled the following and was amazed at the speedy boot time and responsiveness:
CQATest
Amazon (old app.... new one is Amazon Shopping)
Connect
Message+ (verizon sms)
Mobile Hotspot
After that first boot, I re-enabled CQATest and have rebooted several times since. It still seems fast and responsive. I've got a boot time of 35 seconds to the home screen, shutdown time of about 10 seconds.
Just to check, I disabled CQATest again, shutdown and started. The times are the same as above. I was hoping to explore the CQA menu, but haven't been able to so far. I've got USB debugging enabled, but not plugged into a computer. I'll look for answers in other threads.
GeckoDad said:
I just got a refurb Droid Turbo on Marshmallow, and I've had others. I was experiencing some of those same issues that you described.... extremely slow boot and shutdown, and lag on launching apps or other screen clicks.
I just disabled the following and was amazed at the speedy boot time and responsiveness:
CQATest
Amazon (old app.... new one is Amazon Shopping)
Connect
Message+ (verizon sms)
Mobile Hotspot
After that first boot, I re-enabled CQATest and have rebooted several times since. It still seems fast and responsive. I've got a boot time of 35 seconds to the home screen, shutdown time of about 10 seconds.
Just to check, I disabled CQATest again, shutdown and started. The times are the same as above. I was hoping to explore the CQA menu, but haven't been able to so far. I've got USB debugging enabled, but not plugged into a computer. I'll look for answers in other threads.
Click to expand...
Click to collapse
My DT2 was suffering from slow-downs for a couple weeks, then suddenly had the random shutdown and power-only-on-charge scenario yesterday. I was getting ready to do a factory reset.
On one of the reboots, I had a notification about CQA test. When I acknowledged it, I got notifications that "CQATest wants to access this," and "CQATest wants to access that." I denied them all and started hunting up this app I'd never heard of. That's when I came across this thread. I disabled CQATest, but still had the problem. I then remembered that the "old" Amazon app had just updated. I force-closed it, disabled it, and now the phone is back to normal. I see no need for CQATest, so I'm leaving that disabled, but I firmly believe that the Amazon app was culprit.
EDIT: I may have typed to soon. The phone shut off randomly twice today, requiring connection to a power cord to bring it back to life. It does, however, remain powered up upon disconnection (for now?).:-/ I did not clear the cache after deactivating those apps, though, so we'll see if that does the trick.
..
Hi there.
Backstory: My DT2 is almost 3 years old. I already had to send it back to Motorola once for a camera issue, but generally I didn't have any major performance issues for the first year and a half or so. Then it started to decline. Namely OS was taking longer to respond, battery life declining. Then when it was about 2 years old it began the random shutdowns. For the last several months I haven't really had the random shutdowns, however, my battery has been pitifully horrible at holding a charge, and it will usually shut down before the battery indicator hits 0%. First it was around 15%, gradually getting worse. Now it often shuts down between 30-40%, especially if I haven't been on battery saver since disconnecting from the charger.
Now today, I ran down my battery within a few hours to about 30% and it shut off, which was not abnormal. However, upon connecting to charger and attempting restart, the battery indicator jumped from 30 up to 40, then down to 4. Got a weird screen before startup that looked like a system error screen and was afraid it was going into factory reset without my prompting it. Pressed the power key once briefly and the phone went into normal startup, but when it turned on, CommServer was stuck in notifications bar and battery indicator was stuck at 3%, similar story to the others in this thread and others.
I disabled the apps suggested by GeckoDad, and so far the phone can operate, but I've had it plugged in for maybe 30 minutes and it's still hanging out at 3%. Was planning to get a new phone soon, but had hoped to wait another month or two... Probably going to head over to Verizon this afternoon to see if they have any suggestions to keep my DT2 alive until I'm able to replace it.