Related
Has anyone had any issue with the G Tablet shutting down after it goes to sleep? Right now I am running virtually stock (rooted with latest VS update). If I leave the tablet for 10 minutes the screen will shut off as expected, but when I try to wake it by hitting the power momentarily the tablet does nothing. If I press power for a few seconds the tablet boots up as it does from being completely shut down.
If I select sleep from the power off menu, I can wake it if I hit the power button or home button, but only if I do it within about 30 seconds. If I wait any longer, it seems to shutdown. I don't see any settings anywhere for this.
Other than this, everything else seems fine. About the only other thing I can think to mention is I did flash to tnt lite 2.02 and had to recover due to boot loops. I've reset, cleared data and cache, etc...
Thanks for any feedback.
Same happens to mine sometime. Currently running TNT 2.02
I've noticed this a few times also. I have no idea what's causing it. Fortunately, boot up is fast!
Same here
Not all the time, but close to half.
Plain vanilla not rooted.
mysterious fix
I had the similar problem where is shuts off half the time after pressing the sleep button. The symptom went away after installing the Miren browser. Can't explain it.
SH
This was happening to me and I tried many nvflashes and every rom so everything you can try. I exchanged mine today after a lot of research online and now for the first time it sleeps and wakes up. I am certain that there are just a few models that can not be fixed.
So happy to be able to hit the power button to have it wake up.
I recommend if you still can then exchange it for another.
My Malata Zpad does this sometimes too. I thought it was movement that did it, or the magnets on the case, but it looks to do it at random (or when something runs in the background?)
It used to do it 5-6 times a day, now that it's a week old it seems to do it maybe once or twice a day.
I am having the same problem. I do not remember this before the last update (3389).
The tablet is stock, not rooted.
I use the volume button to wake mine.
any one else having this problem? just got my g tablet today and it always shuts down when it goes to sleep
any way to fix it?
i was going to root it right away but hesitating now since it will void warranty - the shutdown after sleep is kinda annoying...thanks
Yeah I had similar issues under stock firmware but subsequent patches fixed the issue for me. Have yet tohave it happen on vegan or tnt lite roms.
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
i took the plunge and installed vegan last night - still have the problem (shut down after going to sleep) -
so any suggestions?
DireMerlin said:
i took the plunge and installed vegan last night - still have the problem (shut down after going to sleep) -
so any suggestions?
Click to expand...
Click to collapse
Did you wipe to factory reset before going to vegan? Mine was doing that, but I never did factory wipe for subsequent vegan updates. Since I have done the clean install, never had this problem.
There are also several kernel updates which allows VPN, cifs, ntfs and other enhancement as well as higher fps.
Love my tablet.
well i only have the tablet for a few hours - and that was a problem out of the box
before installing anything i did the "wipe user data" option from the settings menue in the original/stock TnT - then logged in using Family name - and shut down to root (install CM/vegan ect)
i just downloaded and installed this: "1.0.0 Beta5.1 Link" - thats posted on the first post on the vegan thread
so didn't install any kernal updates or anything yet...if you can point me towards them and what to install i would really appreciate it - thanks
also seem to have a problem where no matter where on the homescreen i swipe down it pulls down the notification bar - any way to fix that?
my solution
I had the same problem out of the box as well. I tried using the Vegan rom with the same result. I went ahead and downloaded a free app called hibernate from the market. It puts it to sleep and allows me to wake it up like how its suppose to. As of now, it has yet to shutdown when asleep.
My ghetto fix til someone can truly id the problem with a proper solution. Hope this helps...
dcom222 said:
Has anyone had any issue with the G Tablet shutting down after it goes to sleep? Right now I am running virtually stock (rooted with latest VS update). If I leave the tablet for 10 minutes the screen will shut off as expected, but when I try to wake it by hitting the power momentarily the tablet does nothing. If I press power for a few seconds the tablet boots up as it does from being completely shut down.
If I select sleep from the power off menu, I can wake it if I hit the power button or home button, but only if I do it within about 30 seconds. If I wait any longer, it seems to shutdown. I don't see any settings anywhere for this.
Other than this, everything else seems fine. About the only other thing I can think to mention is I did flash to tnt lite 2.02 and had to recover due to boot loops. I've reset, cleared data and cache, etc...
Thanks for any feedback.
Click to expand...
Click to collapse
Go to settings, application, development, check stay awake.
DireMerlin said:
also seem to have a problem where no matter where on the homescreen i swipe down it pulls down the notification bar - any way to fix that?
Click to expand...
Click to collapse
If you are running ADW launcher it is a "gestures" setting that can be changed in the ADW specific settings.
The ntofication bar problem was caused by adw ex launcher
Still having problems with the sleep mode thing, tried all thedelete user data and cashed deleting still no luck
Other then that I really love this tablet. So should I return it?
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
Mine too
I'm having this same problem....I find it hard to believe this is a "hardware" issue although I guess its possible. I'm running Vegan 5.1beta but it did it with the stock 3389 firmware too before I upgraded.
This issue is the only fatal flaw thus far I've run into, I'd love to get it resolved.
Sean
sjmoreno said:
Go to settings, application, development, check stay awake.
Click to expand...
Click to collapse
This is a "bump".
I just wanted to know if the folks with the original issue on this thread (gTab shutting down after sleep) tried my suggestion and if so did it fix the issue for them?
I had the same problem and it fixed it for me.
My SGS2 (original AT&T version) has started rebooting randomly once every 3 or so days. It doesn't appear to be triggered by any single thing or event. The last time it happened was when I was opening the Market. The device rebooted back to the Samsung Galaxy S II boot screen.
I've been pretty careful with the phone (only installed trustworthy looking apps, etc). The phone never rebooted in the first 30 days of ownership. Sometime after that it started rebooting with increasing frequency.
Has anyone else run into this problem?
I also had this issue. I returned my phone for another one. I havent had the issue on the new phone but I am crossing my fingers that it doesnt start doing it again on this new device.
Thanks for the input. I had an Atrix that also exhibited this problem after 3 weeks of use. Based on the similarities, I figured it must be something in common on both devices.
At first I tried removing the microSD card I had installed (same one I used in both devices). I still had reboot issues after removing the microSD so it probably wasn't the source of the problems.
I finally realized it was the Dolphin HD browser that was always 'involved' in the reboots. I noticed that I could sometimes trigger a reboot by exiting the browser. The device would stop responding and then reboot after a small timeout. Sometimes the reboots would happen after opening another app, but it was always preceded by exiting Dolphin HD.
I found a thread in the international SGS2 forums that talks about this issue: http://forum.xda-developers.com/showthread.php?t=1321612. It seems that it doesn't affect everyone, so it may be just be some combination of settings / installed apps that triggers the reboots.
For now I've uninstalled Dolphin HD and am using the stock browser. I'm going to use the stock browser for a while and see if removing Dolphin HD fixes the issues.
EDIT: To clarify, this only appears to happen if I 'Exit' the browser. Leaving it running in the background doesn't appear to cause reboot issues, which may be why I didn't run into this issue until now.
That looks really strange, dolphin never gave me any issues. However you can try using opera browser that is my main browser and supports all the features.
Soft reboot (back to bootanimation/homescreen) or hard reboot (back to Samsung screen)?
Sent from my GT-P7510 using Tapatalk
Entropy512 said:
Soft reboot (back to bootanimation/homescreen) or hard reboot (back to Samsung screen)?
Click to expand...
Click to collapse
It automatically reboots back to the Samsung Galaxy S II screen. It then proceeds to go through the AT&T boot animation and finally ends up at the home screen. I assume this would mean it's a hard reboot?
I haven't had any reboot issues since I uninstalled Dolphin HD. I'm not sure if it's truly caused by Dolphin so I'm going to try a few more days without Dolphin before reinstalling it.
As a side note, I noticed some other issues which may or may not be related. These occur even with Dolphin uninstalled.
- Menu button sometimes not responding on the homescreen unless I go to 'Applications' and go back to the homescreen. Once I enter / exit the Applications screen the homescreen menu button will work again. Issue seems to be related to enabling/disabling the GPS from the notification bar, but I haven't reliably reproduced the issue.
- GPS not locking for long periods of time, even though it shows 6+ satellites in view. Sometimes it will lock within 10 seconds. My guess is some sort of AGPS download problem (maybe related to how supl is set to use wap.cingular?). A quick search on Google reveals a number of people suffering the same issue on the AT&T SGS2. All posts also indicate that it worked fine for 5+ weeks before GPS issues started to show up.
I'm trying to hold off on resetting my device back to factory defaults. I want to track down the problem instead of just assuming it was some bug that won't happen again. Based on the international forum posts, the Dolphin HD issue will come back eventually even with a reset.
Thanks again for all the input and help!
Yup that's a hard reboot. An app shouldn't be able to cause a hard reboot like this, but it is not possible to debug. Stock kernels don't have ramconsole for crash debugging.
At first I thought my problems stemmed from an update with WidgetLocker. However, I uninstalled that and the problems persist.
Description of problem:
So I boot the device to the lock screen.
I unlock the phone and all I see is my background with the taskbar at the top. No icons. I can't interact with anything. After a few seconds the screen goes dim and times out. Even if I touch the screen to keep this from happening.
I hit the power button to turn the screen back on. No response. I wait 30 seconds or so and it turns back on. I am greeted with "xxxx process/program has stopped responding do you want to force quit, wait, or send a report" (whatever program happens to be up, doesn't seem to matter, all programs cause this to happen). If I hit force quit the program still hangs. If I hit "wait" the program starts working. This isn't a very repeatable event in that sometimes when I turn the screen back on instead of the "force quit" screen I get the background with taskbar.
While all this is going on I am still receiving status updates, emails, texts, etc. Sometimes I can get to the point where icons appear on my homescreen but if I tap a program's icon the screen just freezes.
I have Go Launcher installed but this happens in Go Launcher or Sense.
Any ideas what is going on? So far I've:
restarted
removed battery
restarted without back on
restarted without sim card in
No luck.
I tried "restore" but after being shown green arrows and an icon of the device I immediately get an icon of the device and a red exclamation in a triangle.
Any help is greatly appreciated. I'm trying to avoid a hard reset.
I would run the RUU. I know you don't want to wipe, but I would back up your data as best you can and wipe it.
any recommendations for backing up? I can't really get to any apps right now.
What does RUU mean?
ROM update utility. Stock rom releases from HTC.
http://forum.xda-developers.com/showthread.php?t=1338916
Sent from my ADR6425LVW using XDA
well
I ran the phone down to 0% battery. Restarted it and things seemed ok. But just now it is starting to hang again so going to back it up and run that RUU.
I tried the RUU but was told it could not communicate with my phone even though I had it plugged in via usb.
Instead of installing the RUU I installed one of the leaked ICS updates (official one for the rezound). Now it functions somewhat better. There is still often a long wait between pressing home while in an application and going to the home screen. Also while the screen is off, pressing the power button to turn the screen on I have to wait a good minute for the screen to come back on. Any idea what in the world is going on?
Sounds weird. Anyway, here are a couple thoughts:
When you installed the ICS leak, did you do a complete wipe of everything? If not, do it and reinstall whatever ROM you like.
Otherwise, in recovery, wipe cache and dalvik again. While you're in Recovery, it wouldn't hurt to run Fix Permissions.
HTH - Good luck!
I did a factory reset to the ics rom.
How do I clear cache and what is dalvik.
I'm going to download one of the official rezound 2.3 update toms and flash it. If that doesn't work ill take it to a Verizon store and see what they can do. It is under warranty.
I've noticed that apps function fine the problem is getting to and from the home screens. It's then that the phone freezes up for a minute or so.
Ok was going to reset phone to 2.3 but got the main version error so going to try this trick to get the main version down to where I can "upgrade" to 2.3:
http://forum.xda-developers.com/showthread.php?t=1467099
dsiglin said:
Ok was going to reset phone to 2.3 but got the main version error so going to try this trick to get the main version down to where I can "upgrade" to 2.3:
http://forum.xda-developers.com/showthread.php?t=1467099
Click to expand...
Click to collapse
Everything get worked out?
I can't get temp root to work so I can install superuser. Working on that now.
seems ICS leak has no temp root ability. I've reached the end of my road as I don't know where to go from here.
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
GTMoraes said:
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
Click to expand...
Click to collapse
Try flashing another ROM for S3 and doing a full wipe.
TenKoX said:
Try flashing another ROM for S3 and doing a full wipe.
Click to expand...
Click to collapse
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
GTMoraes said:
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
Click to expand...
Click to collapse
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
TenKoX said:
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
Click to expand...
Click to collapse
Thanks for the reply.
I started doing this the first time, but it still crashes it. And as I was wasting too much time with this, the backup option came as a option to not have to click to download over 200 apps one by one. Also, it once happened during a long holiday, and I was in a friend's ranch with no decent internet connection for downloading. All my apps were gone and I was stuck with a default phone for five days.
The backup is exactly the point where I finish downloading all the apps and they're installed. There are no cracked programs or adapted (e.g. Nexus camera). Every single app is obtainable from Play Store, so it's pretty fresh
Funny (actually sad) thing is that it's a system-wide error that a wipe solves it. If I don't wipe data and reinstall the same ROM (which under normal condition is no big deal), it doesn't get past from boot screen.
The worst is it happens instantly. It's working now, but then it crashes. Bam, gone. Few hours ago I was texting my gf and I left the phone for a while, waiting for her answer. After some time I knew something was off, picked up the phone and it was pretty warm (first signal), with the LED blinking some Facebook notification. Tried to wake up but it is in coma. I force a restart and it hotboot loops like I described on first post
It -only- happens when screen is locked. I disabled the screen lock for now to see if it's a workaround, but I'm not holding my breath
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
WildfireDEV said:
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
Click to expand...
Click to collapse
That's pretty much discarded. Wiping data instantly solves it. It did indeed run for 5 days with no external app without a single problem.
But also it ran over one week with external apps without a problem. I've executed some memory integrity tests and they all reported a-OK.
I'm kinda ruling out the "rogue-app" issue. I thought that recovering "data" from NAND backup was the /sdcard/android/data. But it's deeper than that. Now I don't even have a lead.
Phone already crashed today, without Vine and lockscreen, so that's not the problem. I really need to get some logs out of him. Just need to know how. Only if it could write a realtime log, so I could pull through ADB.
My last resort will be a fresh-fresh android installation, default S3 i9300 ROM, with only essential apps. Already have it triggered for the next crash.
If it goes rogue even this way, I'm running triangleaway and returning it (will be a profit too, the silver border is stripping).
This time around, I'm trying running it without a external sdcard (several files were being corrupted in it, don't know if it's due to force restart by removing battery, or some real issue on the card)
It's a problem within the Facebook social app or Youtube.
I've managed to run the phone flawlessly for weeks without signing in on Facebook, suspecting it might be it.
Today I logged in on Youtube app accidentally, and had to login on Facebook app to retrieve some info. Three hours later, phone went mad again.
I don't know which app caused it, but I think there's some relation to Facebook due to a greater ~involvement~ (couldn't find a proper word.. forgot it) with Android.
I've changed ROMs, launchers, system versions.. but not Kernel. I'll try another kernel and report on Boeffla main thread to see if there's some known bug
So i turned on my phone and strangely this had happened.
The buttons themselves still work as i can long-press to get the settings menu. Back still works (otherwise i wouldn't be able to do anything!)
I also noticed it had turned on bluetooth.
I don't even have the lock screen and the pull-down menu is blank. So i cannot change settings very easily now either, the only way to do it is physically going into the settings app.
Also i cannot go to the normal list of all your applications either. The only way to get to my applications is to manually add them to the home screen "launcher" thing (is this the launcher? i was never clear on terminology).
I am on SmallEUI V18 https://forum.xda-developers.com/t/...eui-5-9-lemax2-aroma-installer-may-1.3524531/
I didn't realise it had been updated.
I cannot use adb, i think maybe i had disabled usb debugging because i heard leaving it on all the time was insecure. However now the developer options won't let me in too, it says "developer options are not available for this user" when i go into the menu. Tried re-enabling them but nothing.
Notifications aren't coming up so I couldn't change the USB connection setting. I was panicking thinking i would be unable to backup anything as i wouldn't be able to put the phone into MTP mode and it would be stuck in charging mode.
Thankfully i can still download and install applications. I found a program called MTP Enabler. I think it was from here but i cannot remember: https://forum.xda-developers.com/t/app-root-r-3-3-marshmallow-mtp-enabler.3263467/
You need root for it but thankfully SuperSU still works.
Aurora store still works so i can get apps there too.
Backed up my applications settings manually (not sure if i did it correctly, i just took copies of the Android/data and Android/obb folders for the apps i wanted, but strangely didn't need root).
Also installed Titanium backup to back them up properly and get some of the Le Eco system apps like camera, IR remote that i might need.
SMS with SMS backup and restore.
Not sure the best way to backup whatsapp, just transferred the folder manually.
So i'm not sure the best way to fix everything.
I cannot remember how to flash roms or do anything since it has been so long since i did it. Anyway I do not even know if it is possible without ADB? Surely it must be, otherwise i might be screwed. At least i have root so i guess that gives me more hope of being able to fix things.
I was really worried at one point because i was trying to run TWRP or something to see if it would recover things but i couldn't remember how and somehow i ended up in Qualcom download mode, with no screen or anything. I had no idea what had happened. If that happens to anyone else, i think you get into it by holding down the power and volume down buttons at the same time. And to get out of it i managed to do it by holding power and volume up buttons. After that i have been too scared to turn off the phone though!
BTW in system analyse, i see something called Le Eco key although it only shows the start and end of it. Is this some kind of encryption key and what is it for? I think i remember it being important when flashing CFW for the first time but i cannot remember...?
After i've managed to sort this i definitely want to wipe my phone and start from scratch though, getting something a lot more up to date on there. At least i have the little i care about backed up now. Will have to re-learn what to do!
I found this thread:
Notification area, "home" and "recent" buttons not working
(I'm running cuoco92 stable release, so I also posted in that thread. But maybe this section here is a better place for my problem) Hi there! Right after charging, the notification area and the "Home" and "Recent" buttons stopped working...
forum.xda-developers.com
However I don't know what Users are on my device. How do i find this out? I have root amaze file manager and i can download any apps. What terminal app would you recommend?
Thanks