Related
Most of us here love our Nexus S phones. We love Android 2.3's speed and the neat little TV effect when we lock our screens. Since Friday morning, (Feb. 11th) my Nexus S seems to be having another TV effect: nightly "sign offs."
It does not matter if I was charging the phone or not, the phone would just stop working. The strip of touch buttons along the bottom of the phone could be lit or unlit, but the screen would just turn off and no button presses would wake the phone. If I plugged it in to a computer, you could hear a "device connect" noise and see the Android hard drive appear under the Device Manager in Windows.
All of this means that the Nexus S was powered, but not responding. It would not reboot itself, and yes, I have experienced the reboot issue. This seems to be a separate issue. This only seems to happen after midnight.
The only solution is to pull out the battery and reboot it manually.
If my Nexus S is still on when this silent crash occurs overnight, my battery could be completely drained by the time I wake up, making me plug it in AND requiring a battery pull.
Has anyone else had this issue occur? According to the Android Market, I've only updated a few programs recently, one of them being Twitter.
Some Recently Updated Programs: (most recent first)
T-Mobile My Account (to 5.0.15)
Google Authenticator (installed, 0.54)
Google Goggles (to 1.3.1)
Twitter (to 2.0.0)
Amazon MP3 (to 1.8.30)
Google Books (to 1.1.4)
System Info:
Stock, unrooted Nexus S
Launch day unit
T-Mobile USA
Android 2.3.2
Baseband I9020XXJK8
Kernel 2.6.35.7-g7f1638a [email protected] #1
Build GRH78C
When I woke up on Friday, I called Samsung and they did note the issue under my phone number. I will call them again Monday and let them know I'm still having issues.
Any help/suggestions from the XDA community would be appreciated.
Thank you!
Just checked this morning, (Monday) and I had to pop out the battery to turn the phone back on. Before I went to sleep, my battery was at 100%. When I woke up and booted the phone up, it was around 30%. A 70% drop in 8 hours. Time to call Samsung again.
No one else is having this issue?
Sent from my Nexus S using XDA App
Sounds like either a defective unit, or messed up software.
Try doing a factory reset and use don't install many apps and see if that resolves for problems for a day or 2.
Well I had a strange issue that I had never seen before... at around midnight last night both my NS and my gf's went into bootloop at the same time, it was freaky. We're both on CM7 but hers is an older build and mine has netarchy's but it's never happened before... pulling the battery and powering back on fixed both phones but it's still very weird.
I have never actually called the manufacturer before about any issues with a device. Do they do anything for you? Or help you in any way?
Sent from my Nexus S using XDA App
Samsung suggested that I do a factory reset and then if that does not fix the issue, then I'll have to send the phone into them. The tech I got on Friday was more knowledgeable than the one I got today. I'm going to backup my data and then do a factory reset, making sure not to "pull" my data from Google's servers.
Man, not doing that is going to suck.
I am also using Google Voice for my voicemail. Just wanted to throw that out there in case any running services or something is causing all of this. I'm thinking that the new version of Twitter is causing this, as it's baked into Android now and there was an update recently. Thoughts?
Here's a small update on my issue: it seems to be software-related. My Nexus S crashes during the day as well, requiring a battery pull as described above. Disabling sync does not solve the issue, so it doesn't seem like it's coming from that area. What would you guys suggest my next place to look be?
Thanks!
Well, have been having almost the same issue for the past two days. Go to bed with 57 & 63%. Get up in the morning and the phone is dead. Not sure of the exact time it.passes away, but yeah.
Can't understand why the phone has to drink while I sleep.
Sent from my Nexus S using XDA App
Same prob, only intermitant though. Im using rc1 now, with no custom kernel.
Sent from my Nexus S using XDA App
I've been having the same issue since the 13th of Feb. At first it would freeze only overnight. Now, since the 14th it freezes while asleep 4-5 times a day, and the only way to get it working is to do a battery pull. I've tried to remove recently installed apps and widgets, but that has made no difference. I really don't want to have to do a factory reset, especially after I've been reading on google forums about other users not noticing a difference after a factory reset. This is getting ridiculous.
Unrooted Nexus S
Android 2.3.2
Baseband I9020XXJK8
Kernel 2.6.35.7-g7f1638a [email protected] #1
Build GRH78C
T-Mobile US
Agreed. Mine started to freeze during the day as well, requiring a battery pull. Do you have the new Twitter installed? Do you use Google Voice for voicemail? I'm trying to pull together some common threads. It's definitely software related.
Edit: OK, now this is just stupid. It seems like I'm freezing up every half an hour by now. I pull the phone from my pocket to check on something and I push the power button. The lockscreen shows, but the screen and touch buttons don't respond. Battery pull is the only option.
Yes, I do have the new Twitter installed, and yes, I do use Google Voice.
It seems to be happening more often now for me as well. Sometimes it takes two to three times for it to fully restart and get to the home screen, or the lock screen, and sometimes it will wake and then freeze on my pattern lock which also requires a battery pull.
I've starred a few forums on this same issue on the Google support forums, I hope others do the same to show support for a quick fix.
Last night I had the battery at 90. Switched of Wifi, Data and Sync.
Got up this morning and ... no probs The battery dropped to just 88!
BTW. I have got a stock unrooted phone with no Google Voice or twitter so, could not really be a problem related to that.
I use the app addin timer to run stuff at particular times. Other apps that I downloaded are calcbuddy, barcode scanner (which I think is pointless and going to remove), pure messenger, calwidget, appbrain (again, did not like the new updated one), aTakephone, Flip4Silence, CoPilot, Fast Reboot, Docs to Go, Skype, Remote Desktop, StockIndia, Tunein Radio and Widgetsoid.
Thanks for letting me know the apps you have installed. The only common ones between us are:
Barcode Scanner
Skype
Barcode scanner is actually useful. (QR Codes, etc.) Skype may have something to do with it as it does integrate itself with data sync. Thoughts?
In order for this theory to hold water, your phone must:
Crash and require a battery pull to be responsive
Have Skype installed
Edit: My phone was crashing so much that the "first time/welcome" wizard was coming up. Swype, Facebook and GMail were crashing left and right. Time for another Factory Reset....
Edit 2: The phone has SOMEHOW survived a Factory Reset from the normal phone menu AND the Recovery menu! WHAT?!
My Nexus S is going back to Samsung for repair. *sigh* I wonder what they'll say caused the issues?
Sent from my Nexus One using XDA App
Now, today, the phone doesn't get passed the initial "Google" screen. No matter how many times I pull the battery, plug it into a charger or usb port, it does not go past the first google screen. Very disappointing.
Can you get into the bootloader menu? (Volume Up + Power)
Yes, that allowed me to get to the bootloader menu, but I couldn't do a factory reset, it just sat at the screen with the android and an exclamation point inside a triangle. I then did a battery pull, tried a normal restart and got to my home screen.
Glad to hear that you got in. By the way, once you get to the exclamation point screen, you can push Power while holding the Volume Up button to bring up a menu.
Cool, thanks for the help!!
Had my Verizon 7.7 i815 since 4-30 and love it except for one issue - it reboots at least
once a day usually when its connected to the charger.
I need help figuring out if this is a hardware issue so I can just exchange it or if is
software/other issue that I can resolve myself.
When it reboots it goes to a black screen with a single white dot in the center.
It is playing the reboot jingle when this happens.
Sometimes it will bootloop and I have to press the power button for a few seconds to
reset the tab.
Honeybar is installed and AdwLauncherEx is the launcher.
I have tried booting to stock recovery and clearing the cache and did a factory reset - didnt help.
The tab is rooted.
I also removed the Sandisk 16gb microsdhc card after a reboot at 5 am because I had read about users who were having issues with their tabs until removing or switching out their sd cards. The tab went without rebooting after that for 19 hours until I installed
Hidebar. After installing hidebar the tab rebooted twice within a minute so these two instances may be because of that app. I uninstalled it after that and went back to
Honeybar.
I have only experiened a white dot reboot when trying to swap the phone.apk (it was a never ending reboot). I otherwise haven't had it reboot on me. I don't use any bar hiding apps.
Sent from my SCH-I815 using xda premium
Just to be clear my tab was having the reboot issue long before
I installed hidebar - I only installed hidebar tonight and have
owned the tab for a week.
I am however able to cause the reboot consistently with hidebar.
Well the reboots started again after almost an entire weekend reboot free.
Going to exchange it at Verizon for another 7.7 tonight.
Good luck! hopefully the new one is error free.
I've had the same issue with mine, also a vz 7.7.
It was happening in a loop the other day and I managed to capture a video of the entire sequence.
I don't actually think this is a reboot but instead seems to be more of a screen and radio lockup.
I get the little dot in the middle of the screen. After 20 seconds or so the tab goes back to the lock screen. Once unlocked it has to re-connect to either Verizon or Wifi.
I tried disabling the wifi and 3g/4g networks and this seemed to improve the situation but yesterday I was able to get it to do the same thing with the radio's disabled so probably not chip related.
I'm still within my return window I think. Seriously considering returning the thing mainly due to this problem and the lack of ICS.
Had a GT8.9 previously and even though the screen isn't quite as nice it was a pretty great tab and cost half as much *and* can access the awesome AOKP ICS rom.
--tr
Yep, development for this tab is non-existent at the moment.
I'm stickin' it out tho and hoping for CM9 sooner or later.
Same here. I can't find a pattern to what triggers it. The first time i was installing a bunch of apps from my computer via Google Play (not tethered to PC). I pull my microsd and sim and it continues for several cycles. Did a bunch of the stuff you did also w/ clearing the cache and actually the first time i couldn't get it out of the loop (it would actually get into the desktop where it looks like it would be ok, then suddenly screen w/ the white dot in the middle and looping again). Never got close to depleting the built-in storage, so that's not the factor.
Sometimes I can get it to stop by turning it off by holding power down and turning it back on again. It doesn't happen a lot, but it's freakin annoying when it starts.
I don't have honeybar, but am running ADW.
Wow, good to know others who are going through the same issue...I thought I was the only one! I still have the reboot loop issue even after performing a hard reset. For me, the reboot loop only occurs when I'm on a cellular connection. If I'm on wifi or on airplane mode, it doesn't happen. I'm well past the exchange/return policy so this is extremely irritating.
Personally, the most frustrating thing is that my tab will be fully charged at the start of my day, then in my bag for the morning while I'm at work and then, when I take it out to use it, the battery is completely drained because of the reboot loop!!!
I'm hoping an update (ICS?) will fix the issue but I'm not holding my breath for it...
Same issue here. I am rooted, and originally thought the reboot was from Gesture Control app (awesome app!) when hiding navi bar. But after reading this thread, I'm not so sure.
I've only had the reboot loop once, here is my setup when it happened....
-had just unplugged from charger after full charge
-Mobile data was off, Wifi was set to sleep....never when plugged in..
-The device kept rebooting, so I powered off, went into recovery, wiped cache. I also turned off Gesture Control app functions (not sure if this was necessary however). This seemed to stop the reboot loop.
Would be nice if we could keep gathering info on the conditions that cause this, and potentially find a solution. It sucks having a dead tablet because of this issue.
My 7.7 does the same thing. I don't use the tab constantly, but I do notice the reboot on a fairly regular basis. Same symptoms as everyone above, except for me it doesn't go into a loop, it just reboots once with the white dot and then comes back fairly quickly, so not really a full reboot. I don't see the Verizon & Samsung splash screens, just the white dot then the login screen.
Mine is not rooted, has the stock ROM, and does not have any UI enhancing apps or mods. It's pretty much stock other than having applications installed, and nothing that really runs in the background because I have Advanced Task Killer kill auto kill every 30 minutes.
Not that big of an issue for me right now, but would definitely like to see it resolved.
gawd! It doesn't happen a lot, but when it does it's friggin annoying. Yes, it's the white dot and doesn't show the full bootup splash, kinda just goes to the desktop again seems ok for a minute and then boom- black screen w/ dot in the middle and it starts over again.
This last bout was pretty bad and it didn't respond to shutting it completely down by holding the power button and letting it boot again, which has sometimes fixed this in the past when it's looping like this.
Can't tell what is causing it, at first i thought maybe a live wallpaper, the 64GB sandisk microsd card, or a faulty sim (sometimes my tablet says SIM not inserted, even if it is). I tried changing all of those but it still happens. I haven't found a pattern of usage or other type of trigger to make it do this though.
I've only ever experienced this when I tried adding in the mms and dialer app from the GSM 7.7. Otherwise my tab has been rock solid.
Sent from my SCH-I815 using xda premium
It's bone stock. I haven't even bothered to root it yet. Recently in the last week or two, sometimes after I updated to the most recent update the phone has become sluggish. The keyboard will sometimes take a long time to pop up and then when it does it will be laggy to type. It reminds me of how the stock messaging app was which is why I installed Textra.
Hitting the home or power button doesn't always take it up, I've tried holding the home button and still doesn't seem to work, still just a black screen. Holding the power button down it will eventually bring up the menu with "power off, reboot" etc on it and then I can use the home button but still sluggish.
I tried booting into Safe Mode and that seems to make it work normally.
I can't remember installing anything new recently so I'm wondering what could have caused the issues I'm experiencing? I know the boards are mostly geared towards people that root their phone and install custom roms but this is driving me crazy.
I uninstalled Yahoo Weather. It had been acting weird lately anyway and it seems to have fixed things... no idea why. Very strange.
wow--weird, but glad you got it--:good:
if you reinstall yahoo weather try clearing data and cache for app in settings/apps and see if that helps
Why is this thread re-posted?
So I finally got the notification that I could update my Nexus 4 to Lollipop; I was aware of some issues regarding performance/wifi etc but nothing prepared me for this;
I installed Lollipop last night and left my phone optimising its apps etc overnight. In the morning I had a couple of messages saying the launcher was not responding, I also noticed I had no wifi or mobile data connection.
I restarted and my wifi connected but the phone promptly froze and needed another reboot. After reboot it took a long time for even the 'no signal' triangle to come up and much longer for it to show any service, but still no data connection. Various apps are causing popups asking me to close, wait or report. Normally it won't respond to any of these options. I've not even tried to use most of the apps, such as Google Docs which has come up a few times.
Within a couple of hours all I had managed to do was let Gmail steal my emails and get a quick glance of the 'new look' (which I like).
A bit more careful handling got Spotify running for my drive to work but it froze and needed a reboot after removing the aux lead from the port.
Then it stopped responding and I left it for the day as I was working, when I came back it still said 9am on the screen. I cleared the cache via the recovery boot process, performance has improved but its still freezing and the data/mobile reception is very flaky. In 24hrs I still haven't managed to use the phone for anything except Spotify. Not even loaded a web page. Its probably had 20 restarts today.
Help!
Just done the following and there has been a marginal improvement i.e. I can actually open an app (occasionally) without freezing the phone but its still largely unresponsive and no mobile reception at all.
Go into the developer options as above. There are three options under "Drawing" in Developer Options :
-Window animation scale
-Transition animation scale
-Animator duration scale
Turn all three to 'Animation off'.
then, under the 'Apps' subheading (in developer options still), set Background Process Limit to "at most, 2 processes".
My N4 and N7 have been flying along since I did that.
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.