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.
Anyone else think the xperia play has the longest ever bootup? It can take up to 5 minutes to load on mine!
how long does your phone take to boot?
Couple of minutes maybe, rooted & some bloatware removed.
My boot up time depends, maybe on the plays mood?, it's between 2-5 min? Never really the same boot up time
Really liked htc fastboot option, took less than 30 secs. Missing that one...
Regards Dousan...
mine takes exactly 4 min.... i never seen an android phone boot so slow....
Little over a minute after removing lots of bloatware.
Its so long that I want to root it just to remove the bloat.
mines is really random, sometimes it takes a minute, sometimes upto 2
when i gotit it took up to 5 lol
ive removed most apps btw
50 seconds. Used this thread to help identify a lot of bloatware:
http://forum.xda-developers.com/showthread.php?t=1046699
the boot time will depend on what you were doing before you switched your device off, for example if you had just installed lots of apps, the dalvik vm will have to rebuilld the DC on bootup so it will take longer ect
Everything was fine until today when I decided to remove the stock recovery reload script, reodined CWM and also flashed the CRT off zip.
CapsLockKey said:
Everything was fine until today when I decided to remove the stock recovery reload script, reodined CWM and also flashed the CRT off zip.
Click to expand...
Click to collapse
Was the CRT script based on the EI22 framework?
I got it from the EI22 CRT off thread in the theme section.
Last night I also had an odd reboot. Not like the old random reboots that would happen when the phone was asleep, this one seemed like it was caused by a GPS crash. I had been using an app that triggered the GPS, (weatherbug I think) and when I closed it, the GPS icon stayed on. Even after I turned off GPS it still stayed on. The phone also started getting pretty warm. GPS itself no longer worked. After a few minutes of trying to shut down GPS the phone locked up. A minute later it did a "partial" reboot, playing the startup sound and eventually giving me the launcher screen. It was still not running right, with the GPS icon stuck on and the phone very sluggish. I did a shutdown and restart. The phone took a long time to start up, sitting on the "big S" for a while just like on it's first startup. Makes me think something got corrupted in the cache and it had to rebuild it.
I don't know if this was just a random event or the sign of problems to come.
This was on Stock EI22, installed as an OTA upgrade over a fresh EC05 install. The only mod was the CRT off / Circular battery mod that I created at the UOT kitchen.
Well fortunately my phone hasn't done it since. Thinking back, it may have been somehow triggered from a WiFi issue as I leave my WiFi toggle on most of the time and I had just pulled into my garage so the phone obviously was switching from 3G to WiFi around that time.
I am still having a weird issue though where Launcher Pro force closes initially every time I reboot the phone ever since then.
CapsLockKey said:
Well fortunately my phone hasn't done it since. Thinking back, it may have been somehow triggered from a WiFi issue as I leave my WiFi toggle on most of the time and I had just pulled into my garage so the phone obviously was switching from 3G to WiFi around that time.
I am still having a weird issue though where Launcher Pro force closes initially every time I reboot the phone ever since then.
Click to expand...
Click to collapse
Perhaps clearing data on LauncherPro and rebuilding the setup from scratch will solve that for you.
poit said:
Perhaps clearing data on LauncherPro and rebuilding the setup from scratch will solve that for you.
Click to expand...
Click to collapse
Tried clearing data, reinstalling, etc. Doesn't matter, still FC's immediately after reboot. Problem must be with Launcher Pro not liking something, because I just flashed CleanGB Rom (which includes the CRT-off and several other tweaks) to try it out and it does the same thing on that.
Update: Seem to have solved it, but not sure why. Had Voodoo Plus set to load module on boot, when I turned that off LP did just fine after rebooting. Decided to flip the load on boot back on to see if it would start FCing again and magically enough it hasn't.
I just had a random reboot and im in stock EI22..... Why?
Sent from my SPH-D700 using XDA App
Been on it since it was released, no reboots here... Working great for me.
ive had this off and on for a few days now. i find it to be caused by having multiple launcher in my case spb shell .had it running stock the first day so i flashed a rom and its still there. also other apps that use alot of resources will cause it. it partail reboots about 3 or 4 times and then runs normal.
CapsLockKey said:
I am still having a weird issue though where Launcher Pro force closes initially every time I reboot the phone ever since then.
Click to expand...
Click to collapse
I have the same issue with Zeam Launcher, clearing defaults doesn't seem to help. I wonder if there's some kind of half-assed check to make sure that TWLauncher is running? I dunno, but it's obnoxious considering how many times a day I'm forced to reboot EI22, added to the fact that they got rid of the deathgrip reboot.
My phone has "Randomly" rebooted on me several times, usually in an area with little signal coverage. Each time, it seems like there's some program (like Spotify or DI.FM) running that's making network calls when the signal craps out.
EI22 has been nothing but problems for me.
Just had my first random reboot. I'm stock EI22 not rooted yet. Imanually installed on the first day and this was my first. Phone was off just sittin on the table and the screen come on showing low battery but was still sittin at 30% and it shut off and the samsung screen come up and went thru the boot up process.
Sent from my SPH-D700 using xda premium
Please see this thread if you get random reboots with WIFI on.
http://forum.xda-developers.com/showthread.php?t=1359315
My Stable setting with no random reboots !!!!
After trying out virtually every rom/kernel out there (started with stock) I finally got a configuration in which I hadn't got any random reboot (or any other silly issues). My current setting are :
ROM : ERA Lagendary RC2
Kernel : Samurai 2.0.1 (inbuilt with Rc2)
Theme : Ei22Ics version 2 (just for fun !!!)
I have used Voltage control to OC it with settings : 400 Mhz minimum(recommended somewhere in dev post), 1340 Mhz maximum(~1400 mv voltage which I think maximum my handset can handle) with ONDEMAND governor.
My Epic is running flawlessly with no random eboots of FC's since last 4 days (while it used to reboot atleast 3-4 times daily earlier).
Hope this helps !!!!
Epic Timezzzzzzzzz !!!!!!
I still get random reboots in EI22, but not as many as I did on the GB leaks. I can cause a reboot by scrolling to fast in Settings, Applications, Manage Applications, All. I have had the phone run for 90 hours without a random reboot so I'm happy.
Had 2 reboots over the past week, where after charging all night I pulled the usb charger cable out and it rebooted. Stock EI22 except rooted, keyboard/CWM flash, and GPS_fix.
rando991 said:
Had 2 reboots over the past week, where after charging all night I pulled the usb charger cable out and it rebooted. Stock EI22 except rooted, keyboard/CWM flash, and GPS_fix.
Click to expand...
Click to collapse
Sounds like your USB port or charger cord is going bad. That is not random. If connections are shorted momentarily it will cause a reboot. Happened once to me on my cheap car charger.
Sent from my SPH-D700 using XDA App
i dont get any with
ROM = ASC AICS 5.5
Kernel : Samurai 2.0.6
Theme = Shake & Bake Mix Up v.5.9
kennyglass123 said:
Sounds like your USB port or charger cord is going bad. That is not random. If connections are shorted momentarily it will cause a reboot. Happened once to me on my cheap car charger.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Well I did notice it only happened on that particular charger (from Walmart)...also, my wife's epic didn't reboot, but had the charging light stuck on all day. I had to power it off and remove the battery to end it. Would that be maybe the same problem?
Been on CleanGB for quite a while. Went out of town this weekend to Chicago and ended up being rebootpalooza on my phone. Probably had almost half a dozen, once it just shut down in the middle of a phone call at the train station after the low battery notice came up, even though after I powered it back on it still had 28%. Another reboot was I unplugged the car charger shortly after the "full" indicator light came on. Others were just amazingly random. I've loved my Epic up until this trip when it turned into the most unreliable thing I've had.
Ok guys. I don't post often since I can usually find my answers by lurking the forums....but I'm at my wits end here. My 2012 Wi-Fi nexus 7 all of a sudden started acting funny one day. It would freeze u randomly, then reboot, then get stuck in a boot loop for about 10-15 minutes, then boot up, then freeze after about 1-2 minutes of use and repeat the whole process. This was on stock 4.4.2. I've since tried using the toolkit to reflash stock, fix bootloop, unlock and root...all of which I was able to do. None of which helped my issue. Although flashing AOKP DID seem to fix it for about an hour.
Anyway, I gave up on it for about a week and came back to it this morning. Although it wasn't even going to te google boot animation, just stuck on the google logo. So I reflashed stock 4.4.2 again. Now I'm back to square 1. So it boots and will function for maybe about a minute or 2 (or less) before freezing and rebooting.
Is this device shot? I'm out of Google AND ASUS warranty now
I posted something in the big help thread yesterday (probably a mistake). Mine is doing exactly what you describe in terms of working for about 2 minutes before freezing, then rebooting. Mine is 100% stock 4.4.2. Never rooted, unlocked, etc. I have the adb stuff, but I haven't even attempted anything, because it seems so unstable. I don't want a partial flash to screw it up even worse. I feel slightly better knowing that someone else is dealing with exactly the same thing in a similar time frame, so maybe it is a software thing, not a totally dead unit.
Well I may have made some progress. Since the warrenty is up anyway, I decided to crack it open. I noticed the GPU was getting extremely hot for just sitting at the home screen. So I enabled developer options and turned on some monitoring options (the fact that it stayed on long enough to do this is a miracle in itself).
Right now I have some overlay monitoring on including cpu usage and gpu rendering (on screen as lines). I also checked the "stay awake" while charging option. It's been on about 2 minutes so far, although graphics performance is horrible atm. Almost like project butter is disabled and it's running at half power....that could just be the monitoring overlay though. We'll see what happens...
*Update*
It made it 21 minutes, but it did reboot again. On restart, the OS smoothness is back to normal, and it does seem like it goes longer stretches without restarting now, however the issue is obviously still there. I should add that the back cover is currently off. which is starting to make me think this has to do with cooling
9629464420
Okay....I just admitted defeat with this issue. Just ordered a replacement board for $30 because the resets are still happening. Upon reset, I can actually hear a part of the main board buzzing for about 5 seconds (not the speakers). Not to mention that prior to this issue, I was having a lot of wifi connectivity issues anyway. Hopefully the board arrives before my long bus ride to new york...
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.