I've used 2 different ROMS, AOSP extended and Pure Nexus. I've tried using custom kernels and with the default one that comes with the ROM. I've tried going into safe mode. But my phone still randomly reboots. I found that it restarts much more often when I open the Google Maps App, and sometimes camera app too.
Unlike other people, the phone can stay on for a long time if I don't touch it and just keep it in my pocket; it doesn't reboot.
Is it a software or hardware problem? Is it because I am trying to use Android 7 on it?
My phone rebooted during two consecutive nights, a few days ago. It happened between 6 and 7 in the morning, while the phone was lying on my desk, in flight mode. I always put my phone (and previous phones) in flight mode when I go to sleep. Battery usage showed how long ago the reboot took place. The first time my battery was drained from 50% to 20%, second time it didn't (stayed around 80%). I made a TWRP backup, and planned to restore a backup from a few weeks back. Due to lack of time I didn't do that. The reboots didn't happen after that.
The first reboot was after I installed GlassWIre in the afternoon. I uninstalled it after the first reboot. So far I have no idea what caused the reboots.
My phone is on stock 6.1 with january 2017 security patches, and is rooted.
This is a weird one.
No problems until I switched my SIM out (went to a different carrier) and since then any app that tried to access the GPS causes a reboot.
Read that I should change my APN type to "default,mms" so I did so and rebooted, have not had any issue since.
Related
Anyone have any idea what may have happened here?
I was unexpectedly away from home, but using the device quite heavily, and didn't have a method to charge the battery.
Once the battery had drained to about 3%, I switched the phone off but I ended up needing to make another call. The phone booted, but all core apps returned a force close message. Phone, Maps, Google Account, all the main stuff... Other apps would launch and function with no problem though.
Thinking it may have just been a glitch, I rebooted the phone again thinking there would still be just enough juice to allow a phone call, but while booting, the battery totally failed.
Once I had a chance to plug in the charger, all core apps continued to fail, even though the phone now had plenty of power.
Even after a battery pull, the same issues continued, rendering the phone pretty much useless. No link to Sprint, no WiFi network, nothing...
The phone is rooted with v1.5.2 RC and Fresh ROM v1.0, so lacking anything else to do, I performed a Nandroid restore from a backup made about 2 days ago and that seems to have fixed up the problem. (whew.. I did not want to resort to the RUU)
But, I just can't figure out what may have caused this odd behavior in the first place....
Are you using apps2sd?
No, I'm not using the apps2sd feature.
The lockscreen text showed "No service" and the notification bar icon showed the same. The "phone" application was the only one that would attempt to restart after being forced closed. After a second fc though, it would apparently give up.
Oh, and just remembered one other oddity.. Once booted and all force close messages removed, attempting to turn on the mobile network resulted in a hard reboot. I really didn't expect anything since there was no service link, but I was just clicking various shortcuts to see what did or didn't work.
Good part is that a Nandroid restore saved the day, so it's more of a curiosity at this point to what the root cause might have been.
I wouldn't have thought that a battery drain could have corrupted the apps or prevented the root filesystem from mounting.
You probably had too many apps installed. It's a known issue with the Hero, where having too many apps installed causes a bunch of core apps to fail to load for no apparent reason. The phone losing power just caused it to reboot, which triggers the issue.
mkhopper said:
Anyone have any idea what may have happened here?
I was unexpectedly away from home, but using the device quite heavily, and didn't have a method to charge the battery.
Once the battery had drained to about 3%, I switched the phone off but I ended up needing to make another call. The phone booted, but all core apps returned a force close message. Phone, Maps, Google Account, all the main stuff... Other apps would launch and function with no problem though.
Thinking it may have just been a glitch, I rebooted the phone again thinking there would still be just enough juice to allow a phone call, but while booting, the battery totally failed.
Once I had a chance to plug in the charger, all core apps continued to fail, even though the phone now had plenty of power.
Even after a battery pull, the same issues continued, rendering the phone pretty much useless. No link to Sprint, no WiFi network, nothing...
The phone is rooted with v1.5.2 RC and Fresh ROM v1.0, so lacking anything else to do, I performed a Nandroid restore from a backup made about 2 days ago and that seems to have fixed up the problem. (whew.. I did not want to resort to the RUU)
But, I just can't figure out what may have caused this odd behavior in the first place....
Click to expand...
Click to collapse
oddly enough I've had a similar experience. it was 2 days before christmas and i was doing all my last minute shopping. heavy use of the phone caused the battery to die, so i just threw it on my car charger. it booted, but REFUSED to get any data at all (i didn't run into any fc's, however). I rebooted it 3 times and each time the issue persisted.
I was running the AOSP 2.0 build at the time, so i flashed my backup of 2.1 and everything was fine from there...
patches11 said:
You probably had too many apps installed. It's a known issue with the Hero, where having too many apps installed causes a bunch of core apps to fail to load for no apparent reason. The phone losing power just caused it to reboot, which triggers the issue.
Click to expand...
Click to collapse
Hmm, good possibility there. Just did a count and I do have 85 apps installed.
(whoof, I had no idea the number had gotten that high. just too many useful apps for this phone.
Hey guys, so this has happened the last two nights -- at exactly 2:02am my Droid X locks hard. Just did it again. I have no idea what is going on here but I have to pull the battery.
Last night it was on the charger (And the screen was on) so when I picked it up this morning it said 2:02 on the lock screen. Just now I was listening to music and dead stop -- screen was off but I looked at the clock on my computer and sure enough: 2:02.
Just set the clock manually to 2:01 and started a song -- let us see what happens in one minute.
*SIGH*
My phone has been working generally well..... but then I had a strange issue last night where the phone became super unresponsive accessing the SD, so I rebooted. Then the 2:02 lockup .. and then today the battery drained really quickly. A check of CPU spy and the phone never entered deep sleep. Battery manager showed the phone never going to sleep as the "awake" bar went across the whole screen even though Screen on was less than 1 hour total.
Manual clock set to 2:01 did not result in a freeze as I let it go to 2:03... I just set it to 1:59 to see if that makes a difference.
Stock latest GB, root, debloat done myself (fresh install and debloat a couple weeks ago) .... really at my wit's end with Motorola phones. I have a Droid X2 but find that phone generally unusable due to the extremely lackluster performance including the constant audio dropouts, even with the latest GB release.
Anyone else ever seen this 2:02 thing? Or have any idea where I can even begin to look to fix it? I don't see a crontab file on here. I haven't installed any new apps other than the usual updates that seem to happen every day.
....Manual clock is now at 2:04 (from 1:59) with no freeze. So I don't know WTF is happening. I had rebooted the phone around 8pm tonight .. actually had to pull the battery. Did a "reboot" from the Terminal Emulator and the phone went black and never started rebooting.
I'm so fed up with this damn phone!!
That's not happening to mines
Hard reset your phone n back up SMS, files, etc.
Try different battery!
Sent from my DROIDX
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.
This is an ongoing, intermittent and devastating problem I have. My phone will be working perfectly fine, then all of a sudden it will randomly reboot. Then it will work for a few minutes or hours, then randomly reboot again. Then for a shorter time and reboot again until the phone basically can't even get through the bootup process without rebooting. It will be essentially bricked for anywhere from 1/2 a day to nearly a week (though it usually manages to get to working for 15 minutes at a time for most of the week. Then, all of a sudden and for no reason I can tell, it will just start working fine again for anywhere from several days to a month. This has been going on for at least 6 months.
It reboots during any manner of activities with the most common being phone calls, texting (I usually use Handcent Next SMS), anything with the keyboard (stock), browsing, swiping on the home screen, etc.. Really anything causes it, including it just sleeping with the screen off. The same problem occurs when in Safe mode, with or without the SD card (using as just extra storage, not phone memory), and with or without the SIM. It doesn't matter if it's plugged in or not. I have noticed what seems to be a greater tendency for rebooting to occur when the battery is low.
I am on T-Mobile (if that matters in any way for OTAs and such) and running the stock ROM without root. I'm about to try a factory reset but that has not been a permanent solution in the past.
so I just did the factory reset and it rebooted during the initial phone info setup (select your language, etc.)... I think it's toast... Does anyone know if this is the sort of thing that can be repaired for <$100 or should I just buy a new phone from ebay?
So, here is my problem. I've got an almost four years old Note4. I flashed some custom ROM's after i bought it but then I found an old X-note 4.4.4 based custom ROM and i was using that for more than 2 years. Yesterday around noon i noticed that if I try to use Viber, it takes seconds till it opens, and lags badly. (Before that the phone was working perfectly for years). I deleted it, reinstalled, but the problem stayed the same. After a few hours all the other apps started to do the same, the phone became really laggy. As time went by it got worse and worse, around 8pm it started to freeze, reboot, became almost completely useless. I thought maybe a factory reset and a new flash would help. I did a factory reset, and flashed a completely stock ROM on it. It started well, was working good for an hour or so, and then the same problems occured again. Lag, freeze, reboot.... And then nothing. Did not even restart. I can switch it on every now and then, (like in every 20 minutes), but it boots into odin mode. I thought maybe the battery, but that is less then 2 months old. Anyone any idea what happened? I mean the phone is almost 4 years old, so I'm not really pissed off, the only reason why I wanna keep using the Note4 cuz it's removable battery. I don't like phones with built-in battery, this is why i did not upgrade to Note8 for instance. Any help would be much appreciated. By the way, my device is an SM-N910F.
Well, things got even weirder later. I found my old battery which i replaced 2 months ago, still had some juice in it, i put it in, and the phone started!!! Worked perfectly, for about an hour and a bit, then the same problems occured again, lag freeze reboot, and now it boots itself into recovery if i can start it up at all... All the same story. Anyway, i threw it in the drawer and bought a new phone.