Got the ICS update the other day on my totally stock US wi-fi Xoom.
So far, reliability has taken a step backwards.
1. The thing wakes up at random. As in, just sitting there on the nightstand sleeping, and all of a sudden it wakes up as if I had tapped the power button.
2. It's happened at least once so far where it just spontaneously rebooted. It was just sitting on the nightstand, and all of a sudden the screen turns on and the unit is (re-)booting. Might be an evil incidence of issue #1.
3. Tapping the power button sometimes doesn't work and I have to tap it multiple times or tap and hold it in order to get the tablet to wake up.
WTF? I understand that glitches are inevitable with new software but wow, this is pretty basic reliability stuff... the final Honeycomb version on this tablet was rock solid for me.
Also, in contrast to others' reports, I think browsing has also taken a step backwards. It takes longer to load pages, and sometimes I just wind up with an empty white screen instead of a rendered page.
I suppose I could try resetting to shake out any demons but I would very much like to avoid doing that unless it's really known that it fixes some of these issues.
Any thoughts?
Are you using a dock?
I upgraded and it's running way better. No bugs that I can find so far. Wake up lag is nonexistant. No reboots or wakes. Battery is lasting about a day longer than before.
I'm having this problem. I thought it was dock related but looks like I was wrong.
I left it undocked all night and woke up in the morning and found it was at the "enter your password" screen for encrypted tablets.
I also get the problem where it doesn't wake up from sleep, have to force reboot it. Am gonna do a full wipe today and see if that helps, will report back.
I recently GED-ified mine, wonder if that makes a difference, it was originally on the UK/EU honeycomb firmware.
zer0day said:
I'm having this problem. I thought it was dock related but looks like I was wrong.
I left it undocked all night and woke up in the morning and found it was at the "enter your password" screen for encrypted tablets.
I also get the problem where it doesn't wake up from sleep, have to force reboot it. Am gonna do a full wipe today and see if that helps, will report back.
I recently GED-ified mine, wonder if that makes a difference, it was originally on the UK/EU honeycomb firmware.
Click to expand...
Click to collapse
Seems like the only people having the issues use a dock. Maybe it has something to do with being charged by the dock if its happening off the dock too?
Do a little testing. Don't use the dock for a few, two or three days after your reset to see if you have any issues. Then dock it and see if the issues come back?
I have no issues but have never docked it once. Don't own a dock.
Sent from my Xoom using xda premium
crisisinthecity said:
Seems like the only people having the issues use a dock. Maybe it has something to do with being charged by the dock if its happening off the dock too?
Do a little testing. Don't use the dock for a few, two or three days after your reset to see if you have any issues. Then dock it and see if the issues come back?
I have no issues but have never docked it once. Don't own a dock.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
I doubt it is related to the dock. Sometimes you just get a bad download...like a slight power surge while downloading, or whatever. I'm not on stock, but from my experience on ICS, the issues you report are related to your own software install and not the OS or dock hardware.
I am using the standard dock and no issues here at all.
I wiped via Android settings and booted in, signed in, etc. Was changing some settings and it just rebooted :| Have wired it up to adb, hoping it happens again so I can see why.
The dock doesn't work right either. Putting the tablet on the dock doesn't cause it to sleep automatically after a time, and taking it off the dock does not cause it to automatically wake up.
ICS is a definite step backwards, at least for some of us. Hopefully there will be occasional updates like there were for Honeycomb. By the end of Honeycomb, things were nice and stable.
tai4de2 said:
Got the ICS update the other day on my totally stock US wi-fi Xoom.
So far, reliability has taken a step backwards.
1. The thing wakes up at random. As in, just sitting there on the nightstand sleeping, and all of a sudden it wakes up as if I had tapped the power button.
2. It's happened at least once so far where it just spontaneously rebooted. It was just sitting on the nightstand, and all of a sudden the screen turns on and the unit is (re-)booting. Might be an evil incidence of issue #1.
3. Tapping the power button sometimes doesn't work and I have to tap it multiple times or tap and hold it in order to get the tablet to wake up.
WTF? I understand that glitches are inevitable with new software but wow, this is pretty basic reliability stuff... the final Honeycomb version on this tablet was rock solid for me.
Also, in contrast to others' reports, I think browsing has also taken a step backwards. It takes longer to load pages, and sometimes I just wind up with an empty white screen instead of a rendered page.
I suppose I could try resetting to shake out any demons but I would very much like to avoid doing that unless it's really known that it fixes some of these issues.
Any thoughts?
Click to expand...
Click to collapse
Try wiping your Tablet and then reinstalling all your apps. That might help you out.
I reset the tablet. This does in fact seem to have made things better.
Maybe there's some apps, or settings or whatever that don't carry over well into ICS.
The tablet has not turned itself on by itself and it's behaving about as I expect with the dock. I still think something is a bit 'off' in terms of how the tablet sleeps and resumes automatically when docked and undocked, but it's at least not behaving like there's a ghost in it.
My one is still doing random reboots, came back home from work and found it had a mere 1 hr of uptime, I left it in my drawer undocked.
when I upgraded I noticed certain apps that weren't ics ready needed to be reinstalled. Try uninstalling everything that isn't a stock app then slowly add those apps back. Ideally if you can identify the app you can let the developer know so they can fix their app.
Sent from my Galaxy Nexus using XDA App
Mine turns on randomly I think it may be from another reason.. I am on team EOS rom.
Xoom Master said:
Mine turns on randomly I think it may be from another reason.. I am on team EOS rom.
Click to expand...
Click to collapse
Could be overclocked at to high a speed for your CPU, or you're using the wrong governor. Or some other combination of settings, or needing to do a wipe before flashing a new GApps version...
Hmm its on lag free and at 1408mhz could that be the issue?
Thanks
zer0day said:
I wiped via Android settings and booted in, signed in, etc. Was changing some settings and it just rebooted :| Have wired it up to adb, hoping it happens again so I can see why.
Click to expand...
Click to collapse
I have the same problem. Random reboots and freezes while the tablet is idle. I deleted all downloaded apps and wiped the tablet - to no avail. This is what I found out so far:
The reboots/freezes only happen when the tablet is idle, never when I'm working.
No reboots when USB is connected (so you can't use adb to find out the cause)
No reboots in Airplane Mode
Any ideas? Before the ICS update my tablet was fine
Xoom Master said:
Hmm its on lag free and at 1408mhz could that be the issue?
Thanks
Click to expand...
Click to collapse
try interactive.
u do a full wipe (factory reset)
I'm on eos and have not had a random reboot since 5
Mine is also having problems. I put the stock rom on there via CWM recovery with the modified file that got rid of the device check.
If I leave it sitting around for a while even in airplane mode the performance of the whole tablet just plummets. There is literally nothing happening to it when I'm not using it either. Random reboots (almost on cue when I stop using it), etc.
My device history was that I had Honeycomb stock and a locked bootloader, then unlocked (and wiped obviously) and loaded ICS. I then wanted to see if I could get the official OTA update so I flashed back to 3.2.1, and then flashed ICS again.
Edit: On second thought, maybe I should try eliminating apps before I say anything
I'd suggest a Factory Reset for those having consistent random reboots. More than likely it is an app or app related that didn't move over well during the upgrade/update. Especially if you weren't having these problems before the update/upgrade.
I personally always Factory Reset whenever my device goes from one OS version to the next OS version and then re-download the apps as needed (this usually makes for a good cleanup as well, I find a few apps I downloaded I never end up using).
My Xoom has been up 267 hours and would be longer if I hadn't turned it off while away from my charger(s) for an extended time. It has never rebooted on it's own or locked up since getting the ICS update.
With the eos rom i do not have random reboots but sometime my xoom wont wake up. I have to reboot it manually with power-volume up.
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!!
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
Has anyone else goten a ton of random reboots? It tends to happen when I am not using the dvice, and it's docked with the screen open and turned off. About every few hours, I see the EEE Pad restart. Even when I do not have it near me, I often come back to it only to find that AndChat/my other running programs have stopped running, which suggests the device reboot itself.
Hi,
I can't say that have seen lots of them, but last weekend as I was putting it down, as usual I switched off the screen by pressing the On/Off button... and it rebooted!?!??!?!
There is no way that I have held down the button for over 4 sec, and it should ask me whether to shut down first, and finally I have never seen an option on the TF for rebooting the device.
Any ideas guys?
rio
I have the same trouble I have noticed this today.
MP3 player on pause, tablet docked and open on my desk and after a while (like 5 or 10 min) I look at it and it's rebooting...
Quite strange.
Sounds like a power management trouble.
Would really love to know what's wrong with it.
Fandaor
If you have an sdcard plugged in the dock, you can try to remove it.
It worked for me.
more details -> http://forum.xda-developers.com/showthread.php?t=1120185
reppad said:
If you have an sdcard plugged in the dock, you can try to remove it.
It worked for me.
more details -> http://forum.xda-developers.com/showthread.php?t=1120185
Click to expand...
Click to collapse
What about that don't have dock & this happens?
Yes mine does it fairly often and I had never seen it happen undocked before until this weekend. I started undocking it at night due to the battery drain issue and both Sat and Sunday when I undocked it and sat the tablet aside, the tablet auto reboot. Previously I had seen this happen only when docked and sleeping and when the screen was open. Very annoying, wish they'd fix this.
I had it wake up a few times when it notified me I had mail..of those times...it rebooted on me.
Turning off background sync did the trick for me. It really is annoying..sometimes come from work and power level dropped dramatically...now when I go anywhere..airplane mode helps...pia but it gets the job done.
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
I just had a scare. I updated my GN 8013 to JB 4.12 several days ago and haven't had any real issues. I let my Note go into hibernate to take a break and do some chores in between trying to finish an ebook checked out from my local library. The battery was at 68 per cent and I planned to be back to reading within 10 minutes. When I did get back to read and picked up my Note it wouldn't turn on. This is the first time this has happened. Jumping onto Google, it appears this has happened to other Samsung tablets in the past, usually after a software update. Here's a link I used and following the steps outlined in I then was able to reboot (keep finger on screen while holding down power button then reboot once battery icon appears on screen). http://mojocode.com/content/samsung-galaxy-tablet-101s-wont-boot My battery is still at 68 percent, but I'm leaving it plugged in while I do some other chores. I hope this isn't a new problem brought about by the update. If anyone else has this issue, I'd suggest we keep track so we can report to Samsung.
Yeah I think they call it the sleep of death. Happened to my recently updated wifi (8013)note also.
IF it is happening then only 8013 devices as none from other devices have reported so far. If two devices then it is a cause of worry
samir_a said:
IF it is happening then only 8013 devices as none from other devices have reported so far. If two devices then it is a cause of worry
Click to expand...
Click to collapse
I started the thread so we can see if it's happening to multiple units and what models and firmare seem to be affected. If more report the same issue, maybe this thread can be stickied. From what I read when looking for solutions, it seems to occur after firmware updates and has occurred on many of Samsung's tablets.
I have a N8000 and it's happened to mine three or four times since August; once on ICS. It would infrequently happen to my GT-P7500 on HC also. You can be in the middle of something and the screen goes black. No warnings or pop-ups, it just goes black. Nothing happens when you hit the power button normally like you would to wake it up. You have to hold the power button down for a looong time (maybe more than once) and the tablet boots. The first time it happens it's stroke inducing because you think your tablet's dead. After that it's just an annoyance. I have no idea what causes it but it does no harm (other than potentially losing unsaved work) when it happens. Between my OG G-Tab and the Note it's probably happened half a dozen times in eighteen months.
BarryH_GEG said:
I have a N8000 and it's happened to mine three or four times since August; once on ICS. It would infrequently happen to my GT-P7500 on HC also. You can be in the middle of something and the screen goes black. No warnings or pop-ups, it just goes black. Nothing happens when you hit the power button normally like you would to wake it up. You have to hold the power button down for a looong time (maybe more than once) and the tablet boots. The first time it happens it's stroke inducing because you think your tablet's dead. After that it's just an annoyance. I have no idea what causes it but it does no harm (other than potentially losing unsaved work) when it happens. Between my OG G-Tab and the Note it's probably happened half a dozen times in eighteen months.
Click to expand...
Click to collapse
On my GN 8013, I had to keep a finger on my screen while holding down the power button; that brought up the battery icon screen and from there I could reboot. Holding down the power button alone did not reboot and triggered my panic that drove me to a Google search and a solution to enable rebooting. This seems to be a long standing issue across versions of Android and manufacturers and seems to be a result of manufacturer code tweaking having unexpected consequences.
mke1973 said:
This seems to be a long standing issue across versions of Android and manufacturers and seems to be a result of manufacturer code tweaking having unexpected consequences.
Click to expand...
Click to collapse
I kind of look at it as the equivalent of the "blue screen of death" in Windows. My desktop PC throws a shoe every once in a while and it's usually tied to either graphics or memory conflicts based on the dump message. I'm guessing what we're experiencing is the Android version. As a pure guess I'd say it's something to do with memory reads/writes/buffers caused by either a management issue with the OS or an app (or combination of apps) doing something it shouldn't at an inappropriate time. And after playing with the power button I've gotten what you did (the giant battery icon showing up) and other times the Samsung boot logo. And I've had it happen twice in a week and other times once in six months; all without changing anything with the OS or apps. It's just one of life's little mysteries.
P.S. - My N2's done it but it behaves differently. It shows up a spontaneous reboot.
I had same issue frequently since last upgrade to 4.1.2 . I thought the problem is from Mobile VOIP. So I un installed it.
But today, another freeze happened. Ok, today just once. But, what's the problem?
N.b I recover it just by holding power button for 8 seconds.
Sent from my GT-I9100 using Tapatalk 2
mohammedsarhan said:
I had same issue frequently since last upgrade to 4.1.2
Click to expand...
Click to collapse
If it's happening frequently it may be something other than the random event some of us are talking about. A lot of you that upgraded from ICS to JB with all your apps intact could be having compatibility issues as not all apps have been updated/optimized yet. Older apps that are a little less mainstream and/or popular would be a good place to start to troubleshoot. Unless there's something specific to U.S. JB a lot of us have been on it since October and there haven't been any reports of frequent freezes or reboots. That is outside the random one discussed above that's not specific to JB.
mke1973 said:
I just had a scare. I updated my GN 8013 to JB 4.12 several days ago and haven't had any real issues. I let my Note go into hibernate to take a break and do some chores in between trying to finish an ebook checked out from my local library. The battery was at 68 per cent and I planned to be back to reading within 10 minutes. When I did get back to read and picked up my Note it wouldn't turn on. This is the first time this has happened. Jumping onto Google, it appears this has happened to other Samsung tablets in the past, usually after a software update. Here's a link I used and following the steps outlined in I then was able to reboot (keep finger on screen while holding down power button then reboot once battery icon appears on screen). http://mojocode.com/content/samsung-galaxy-tablet-101s-wont-boot My battery is still at 68 percent, but I'm leaving it plugged in while I do some other chores. I hope this isn't a new problem brought about by the update. If anyone else has this issue, I'd suggest we keep track so we can report to Samsung.
Click to expand...
Click to collapse
Pretty much exact same thing happened to me last night, for the first time ever. Took me about 30 seconds to get any response, by holding down the power button for a LONG time. Rebooted, saw the battery was below 20%, which was also odd since I had charged it overnight and had consistently been getting 2-3 days on a charge.
If it happens again, I'll go with Barry's suggestion and try a clean install, then adding apps one by one. Little disappointing though, as I've had no real problems at all with the GNote until this JB update.
Thanks,
JC
Sleep of Death...
I have the 16gb wifi GT8013 model and I am having the sleep issue too. Mine isn't "deathly" that requires the finger on the screen while powering up, or standing on your head and spinning three times while chanting "sleep of death" or any craziness like that, but every once and a while, for no rhyme or reason, I have to start it from a cold boot when I attempt to wake it with the power button. I press and hold the power button for 3-4 seconds and here comes the Samsung boot logo. Once it gets booted and connects to the wifi, I am good to go.
This happens so intermittently, with it not doing it for a couple days, or it might be within the next hour. I think I have narrowed it down to the wifi radio. Reason being...I have done a factory reset and tried running it naked and it still happened. But I have noticed the issue seems to happen when I have left the house and it drops the home wifi and then negotiates a new connection with my SIII hotspot, which I turn on before leaving the house for work, or anything that I will need connectivity for the tablet while away from the house. I don't know if it is due to roaming outside the home wife and dropping the connection, or if it is the combination of dropping the home wifi and then locking into the phone hotspot. I am so busy that I haven't been able to get that far in my troubleshooting. However, I am leaning to just the fact of it leaving a wifi signal and, I guess, it doesn't want to and gets jumbled and kills itself all together. I say that because it has happened when I have forgotten to turn on the hotspot until I got to work and then I open the tablet and its dead.
This has been happening from day one, when I bought the tablet towards the end of January. Unfortunately the Samsung warranty absolutely sucks, due to them wanting me to ship it in and do without it for 3wks and then to boil my blood even more, they want to give me a refurb unit if they can't fix this one. To make matters worse, its been almost a week now and they can't even get the shipping arrangements made yet! Needless to say, with this thing only being barely two months old, I am a little on edge with Samsung and I would love to figure it out and fix it myself. If it were something I knew, without a doubt, would be fixed with rooting and dropping CM on there, then I would. But I see there are still stability issues with most custom ROMs and I really would like to keep the functionality of the S-pen.
I have attempted to pull a log file with aLogCat and they are blank. It appears that the log files disappear when rebooted, which does me no good in figuring out what shut it down, if I can't recall the log from pre-shutdown. I have also tried aLogrec in hopes of accomplishing this, however, something isn't right because I left it recording for hours and days and the log file was only 1kb. Although, it doesn't much matter since the log recorder running in the background keeps it from sleeping to the point of shutdown, so I am assuming it is a sleep issue, due to that discovery.
If anyone has any thoughts that might help me, I am definitely all ears! This tablet is for work and school so it is next to impossible for me to do without it for 3wks...provided Samsung can get their crap in gear enough to even arrange the shipping for the service request. And I sure as hell don't want a refurb!!
Later,
Roger
I had periodic issues with the sleep-of-death once I updated to JB. It turned out that a VOIP program that worked fine on ICS (Sipdroid) crashed JB. I installed a different VOIP program that users said worked with JB (C-SipSimple) and my tablet stabilized. If you have non-stock apps that you use a lot, I would begin doing Google searches on them, starting with those that you use most frequently to see if anyone is reporting issues with JB (I wouldn't only rely on comments in playstore since users are more likely to engage in a discussin in a forum like this one). Good luck.
mke1973 said:
I had periodic issues with the sleep-of-death once I updated to JB. It turned out that a VOIP program that worked fine on ICS (Sipdroid) crashed JB. I installed a different VOIP program that users said worked with JB (C-SipSimple) and my tablet stabilized. If you have non-stock apps that you use a lot, I would begin doing Google searches on them, starting with those that you use most frequently to see if anyone is reporting issues with JB (I wouldn't only rely on comments in playstore since users are more likely to engage in a discussin in a forum like this one). Good luck.
Click to expand...
Click to collapse
Unfortunately, I have come to the conclusion it isn't an app issue. I have never used any VOIP service, of any kind, and I have done a factory reset and it happened before I installed any apps. Unless, of course, it is an app or service that is included in the Touchwiz junk and/or bloatware that comes with it. It happened on ICS, which is what came on it, and it happens after being update to JB. However, I only had it on ICS for a couple days and I would like to go back to it for further troubleshooting, but since it has been updated to JB, that isn't possible without rooting and I haven't decided if I want to do that yet.
--Roger
After further observation, it appears my sleep-of-death issues arise when I leave the comforts of my home Wifi. When doing so, apparently losing the Wifi signal causes the tablet to shut down completely... When asleep. If I have LogCatRec running, that keeps the tablet from falling into hibernate and the issue never happens, thus resulting in nothing interesting being logged, aside from the typical tablet activity.
Now the question arises, is it my home Wifi, or just leaving a Wifi range in general? I cannot get it to recreate the issue by simply turning off the Wifi signal it is currently connected to. However, I am now on a new Netgear router, due to the Belkin shooting craps on me, and it happened then, on the Belkin, and it happens now, on the Netgear. So, my presumption is that it has to drop a Wifi connection due to signal degredation, versus simply cutting a decent signal off at the source.
Has anyone else gotten this far with their sleep of death issue? Or is there another thread, that I've missed that I am just repeating? I am curious to see what's out there, before I send this thing off and its gone for three weeks!
-Roger
Sent from my GT-N8013 using xda app-developers app
I have no issues any longer after finding the offending app on my note and uninstalling it. I don't think there's one cause for this issue. Most often, Android OS updates seem to create program instability in some apps that then trigger the sleep of death. It gets hard to track down issues for individuals experiencing the sleep of death on their devices because we all have different apps installed. You might look at apps on your note that require WIFI to sync and are allowed to sync periodically since one of those may be the culprit. Check comments on Google Play to see if any are known to be buggy under JB. Good luck.
Mke1973, with all due respect, I dont think you are reading my post thoroughly.
As I have already said, this is not an app issue. I have done a reset and the issue still happens when I run it without any apps downloaded and installed. Unless it is an issue with a Samsung app that is preloaded, in which case the fix is still out of my hands, since the owner of the tablet can't uninstall crapware at their will, without rooting it.
Sent from my GT-N8013 using xda app-developers app
Actually, I wasn't ignoring your facts it's just that there are 3rd party apps installed by default that, if you decide to use them, require sync. Specifically I'm thinking of Evernote. Once device makers began pushing out upgrades to JB, some Android users began reporting incidents of the sleep of death when using or after closing Evernote in various Android forums. It wasn't a majority of people, but more than a smattering, but that is standard with the sleep of death. Again good luck on your hunt.