Is anyone experiencing a problem with the Gtablet where apps are randomly exiting or closing ( but not FC's) and it's like you're hitting the back button? Sometimes windows of previously closed apps are randomly popping up? Doesn't happen all the time but very annoying when it happens. This thing happened even when I had the stock rom build 4349 , branch 1.2 and now flashed with CM7.03 pershoot. After a while without doing anything, and it's like it finished hitting the back button several times, then it settles and works fine again. I'm tempted of sending it to Viewsonic for repair but maybe someone had this issue before and had some solution or answer to what's going on. Thanks.
This has happened to me several times before, but it usually fixes it self, usually I clean the screen and the capacitive buttons. And i think that stops it. Or sometimes it may just be the app, I was having problems exactly like the ones you are describing with Opera Mobile Browser. You should also try to wipe all data/cache and format your sd card if it doesn't stop.
Thanks for the reply. I decided to send it to Viewsonic. It needed fixing of the charging connector anyways. I told viewsonic support about the problem, he seemed to know about it. So far I have not received it yet. I thought about the screen and tried cleaning it but not sure if it fixed the problem. Tried formatting the SD card too.
Related
My audio randomly drops out and requires a reboot to clear. All audio is silenced. For example, pressing the volume buttons do not beep. It happens randomly, but most often after a reboot.
Tonight I was able to reproduce the problem fairly consistently so I was able to get a logcat (attached) of the issue. I was using Rockplayer v1.5.5 with hardware decoding. I don't think Rockplayer is the issue because the problem has happened with other programs, like Angry Birds.
I am not an expert but I see lines like "[FONT="]W/AudioTrack( 927): obtainBuffer timed out (is the CPU pegged?) 0x21a528 user=00033b2a," [/FONT]when the issue occurs. When everything is working normally, these entries are not there. I trimmed the log file to meet the size limitations. I have the whole file if needed. Please help!!![FONT="]
[/FONT]
Moved to general
I will try and post a logcat the next time mine does it.
I'm having the same problem. I can hear sound whenever i startup the tablet, but after a while (sometimes it can be less than 1 min sometimes after 5 hours) the sound stops and i only get static noise or no sound at all. Whenever that happens, in the android log appears the following lines repeatedly (with a frequency of 1 sec):
W/AudioTrack( ####): obtainBuffer timed out (is the CPU pegged?) 0x##### user=00######, server=00######
I've tried changing ROMs without success in solving this problem, now i'm using TNTL v4.4.0.
The bug triggers while i'm using sound (games/watching videos on youtube/playng music on winamp/ pressing the battery button on the status bar, triggering that "click" noise).
When this bug is triggered, i get FC from some apps that use sound (Youtube / Winamp / some games)...
Rebooting the tablet fixes the problem untill it triggers again
i've been using adb logcat several times with this problem and the only correlation between the logs is the line described above, i've tried searching on google, but the results i get are for cellphones or pre 2.2 devices... in one of them, they interpret it as a kernel problem (http://forum.xda-developers.com/showthread.php?p=6280968)...
Any help is appreciated.
Same thing here on one of the woot tablets running Vegan 5.1. 1. Usually happens after coming back from sleep. I asked for a replacement and the new tablet will be here tomorrow.
I really hope this is a hardware problem and not caused by a rom or app. Still interested in finding out what causes this, so I won't have this happen again with my new tab. Did anyone have this issue with the stock rom? Are these all recently bought tablets? I didn't spend enough time with stock to encounter sound problems.
I've been toying around with my tablet to see what is causing the problem, so i started by Flashing all over to stock to find out if at some point the sound problem stops... well... here are my results untill now:
Started at TNTL 4.4.0, Many apps installed and the sound problem appears constantly and is triggered easily. Before starting I backed up everything using Titanium Backup xD.
Part 1: Format + NVFlash to "belkit 1105" + Factory Reset: Problem Still Arround, took me about 3 reboots and 7 minutes to reproduce it by playing a song and randomly click on the battery/wifi/notification buttons with the sound of those buttons turned on.
Part 2: Updated to "stock 3588" (couldn't do it through OTA because it sayed that my tablet was up to date... so I downloaded the update from the NVFlash guide and installed using this guide from the internal SD. It didn't work, it took me about 5 minutes to reproduce the error, no rebooting .
Part 3: Settings > Security > Factory Reset: ... still haven't been able to reproduce the error, i've rebooted it about 7 times and listened music for 3 hours, eventually clicking on the notification/battery/wifi buttons and it seems to work fine... at least this is a checkpoint for me
It would be great if someone with the same problem could confirm that this works, i'm going to leave my tablet playing music during the night just to be sure :9.
Oh, JIC I bought my tablet on 27 Feb from J&R Electronics Inc through Amazon.
I'm having the same problem with mine in fact I have the tablet sitting next to me and the thing just went all static and freaked the cat out and woke my wife up not exactly cool when your in bed! I may have to look into exchanging or return it! I would hate to be at work or somewhere else and have it freak out like that! It's annoying!
I'm having the same problem, I lost all sound once I upgraded to Vegan Tab Ginger. Downgrading, or any changes doesn't do anything
I have a similar issue. I installed Cyanogenmod 7.0.3 and my sound mysteriously goes away. I can easily repeat it by putting the table to sleep and then waking it up. Sometimes, you can hear some static before it goes out.
I discussed this with Gojimi long time ago, but, I dont remember, I think the issue got lost with time. Still happens though
Hi everyone,
I've been lurking for the past year or so, but now I got a problem of my own and I hope I can solve it with your help.
For a while now, almost every time, I picked up the phone, tried to check mail, or do something, and it wouldn't do anything. It seemed like it was turned off, except I couldn't turn it on by pressing the power key. It wouldn't react to touching the screen, menu button, plugging in headphones, the USB cable, pressing hardware buttons, sending myself a mail/sms, or calling myself, the alarm didn't go off (especially troublesome), it was, for all intents and purposes, completely frozen, until I removed and reinserted the battery. Then, I could normally turn it on and it seemed like everything was in order and a new message or email (in the account that triggers a notification) was waiting for me.
This started after I upgraded to ICS (official). I also rooted the phone with CF-Root. Everything was working fine, except for these freezes.
Last week, I had enough and I did a factory reset. After that, it seemed to be ok, until 2 days ago, when I flashed it with ICS 4.0.4 and rooted it again. It was fine for 2 days, today it started freezing again. I did not install any new apps - all the apps were (re)installed immediately after the flashing.
I *did* have some problems with the camera (I couldn't see what I was shooting, I found out that it's probably a wrong version of CF-root, so I reflashed that, problem persisted, I reflashed just the kernel of official 4.0.4 and the problem disappeared. This is all I did before I noticed the problem again.
I would think that it might be because of the SD card, some app or something else, but to the best of my observing, it ONLY happens, when a notification should be triggered - instead, the phone freezes.
Any ideas?
Thanks,
Ben
i think your RAM is on its maximum level, try cleaning your RAM once in a while.. go to your Task Manager (if you're on a stock firmware)
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
Hi,
I'm looking for some general advice and troubleshooting for my phone's issues. My phone started crashing very often, sometimes at complete random, as well as when I was using it fairly heavily (any app that froze my phone for a second before loading before the crashing would now crash my phone). Sometimes it would reboot fine, other times it would bootloop once or twice before reloading fine. I previously tried doing a factory reset, removing my external microSD card, and updating everything via Kies and nothing worked.
I got bored and rooted my phone, did a full wipe, and flashed the latest Infamous update. The problem was still there but it wouldn't crash as often while using it because my phone could handle higher app activity but it's still there. Oddly enough, after flashing Infamous, it often fails to reboot and so I have to do a battery pull before turning it back on, otherwise it won't even vibrate after holding the power button.
I'm just wondering if you guys have any idea what the issue could be. Is it likely still something I can fix? Is this potentially a battery issue or is it a hardware issue?
Thanks so much!
jasonale said:
Hi,
I'm looking for some general advice and troubleshooting for my phone's issues. My phone started crashing very often, sometimes at complete random, as well as when I was using it fairly heavily (any app that froze my phone for a second before loading before the crashing would now crash my phone). Sometimes it would reboot fine, other times it would bootloop once or twice before reloading fine. I previously tried doing a factory reset, removing my external microSD card, and updating everything via Kies and nothing worked.
I got bored and rooted my phone, did a full wipe, and flashed the latest Infamous update. The problem was still there but it wouldn't crash as often while using it because my phone could handle higher app activity but it's still there. Oddly enough, after flashing Infamous, it often fails to reboot and so I have to do a battery pull before turning it back on, otherwise it won't even vibrate after holding the power button.
I'm just wondering if you guys have any idea what the issue could be. Is it likely still something I can fix? Is this potentially a battery issue or is it a hardware issue?
Thanks so much!
Click to expand...
Click to collapse
So when your phone have become unstable , in what condition it was ? did you ever flash it before ... so my s2x did the same thing afer a update with odin on 4.2 ... so i have reflashed it and evrything was working good after
I've been having this problem for a while, but can't shake it. No matter what ROM I try (including stock!) The phone reboots several times per day. I'll have it just sitting on my desk doing nothing when it suddenly reboots.
Also, if I try using just the phone itself to make a call the person on the other end hears their own voice echoed back to them. The only way to avoid this is to not use the phones mic/speaker. If I plug into the phones audio jack, or connect via blutooth the echo goes away.
At first I thought it was the roms I was using, blaming it on the call record function. But even the stock rom has this issue. I thought maybe upgrading the bootloader/modem would fix it, so I flash NK2, but still have the issues.
What else can I try here? Anyone else experience this? I've search but found nothing but a thread suggesting it might be a corrupt SD card causing the reboots. Pulled the SD card, still reboots. I'm out of ideas.
timekillerj said:
I've been having this problem for a while, but can't shake it. No matter what ROM I try (including stock!) The phone reboots several times per day. I'll have it just sitting on my desk doing nothing when it suddenly reboots.
Also, if I try using just the phone itself to make a call the person on the other end hears their own voice echoed back to them. The only way to avoid this is to not use the phones mic/speaker. If I plug into the phones audio jack, or connect via blutooth the echo goes away.
At first I thought it was the roms I was using, blaming it on the call record function. But even the stock rom has this issue. I thought maybe upgrading the bootloader/modem would fix it, so I flash NK2, but still have the issues.
What else can I try here? Anyone else experience this? I've search but found nothing but a thread suggesting it might be a corrupt SD card causing the reboots. Pulled the SD card, still reboots. I'm out of ideas.
Click to expand...
Click to collapse
I do have the echo problem but it doesn't happen often and usually goes away if I just call them back which I think might just be a signal problem.
As far as the rebooting issue, your phone will reboot itself if there is low memory for the phone to function meaning there is something running in the background that you don't necessarily see when you open the recent apps to close. That's why I got task killing apps that help close apps that you don't want running (Clean Master App does it pretty well). As for me the only time I get reboots is when I'm running multiple apps that's a bit intensive causing my phone's memory to drop down to like 300MB +/- 100MB like games plus some messenger apps to talk to people I play with. Worst case scenario is that you going to have to contact Tmo or Samsung for warranty and best case scenario is you just figure out whats running background or clear cache now and then.
timekillerj said:
I've been having this problem for a while, but can't shake it. No matter what ROM I try (including stock!) The phone reboots several times per day. I'll have it just sitting on my desk doing nothing when it suddenly reboots.
Also, if I try using just the phone itself to make a call the person on the other end hears their own voice echoed back to them. The only way to avoid this is to not use the phones mic/speaker. If I plug into the phones audio jack, or connect via blutooth the echo goes away.
At first I thought it was the roms I was using, blaming it on the call record function. But even the stock rom has this issue. I thought maybe upgrading the bootloader/modem would fix it, so I flash NK2, but still have the issues.
What else can I try here? Anyone else experience this? I've search but found nothing but a thread suggesting it might be a corrupt SD card causing the reboots. Pulled the SD card, still reboots. I'm out of ideas.
Click to expand...
Click to collapse
Do a full Wipe (Wipe Data, System, Dalvik Cache and Cache) and go back to stock. That's how I solved all of my problems
timekillerj said:
What else can I try here? Anyone else experience this? I'm out of ideas.
Click to expand...
Click to collapse
I think I've read in a couple of threads that if you let it sit for 5 minutes after it comes back up after a full wipe and then just cancel out of all the automatic setup screens, then reboot and set it up manually it seems to fix this. I haven't had the problem so I can't verify this, but hey, anything is worth a try.
Good luck.