This has happened twice so far. Phone is locked up and no response except trying to power up the bottom buttons flash like 3 or 4 times. First time it happened I was able to reboot by holding the power button for about a minute. This morning I take my phone off the charger and it's in the same boat except holding the power button didn't seem to help. Luckily I was able to get into recovery and clear cache and that seemed to help.
Where do I even begin to investigate possible causes? Both times it happened I was not even handling the phone.
EDIT:
Forgot to add the occurrences where about a week apart.
Did some digging around and came across the tombstones directory. There was one from last night/this morning around 1:30AM. It appears to be some type of crash dump file. The first section seems to indicate that Chrome caused a SIGSEGV. Perhaps clearing the cache will take care of it. Hopefully...
Code:
pid: 5344, tid: 5344, name: .android.chrome >>> com.android.chrome <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaad
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
Last night I was reading Twitter before going to bed when I noticed that my GPS kept ticking on and off after I'd posted an update (I let my Twitter app access GPS to assign my location to tweets). Thinking that odd, I rebooted.
Talk about the reboot from hell.
Approximately 30 seconds after booting back up, the phone locked: I could tap buttons and feel haptic feedback, but no changes to the screen occurred. I eventually got the bright idea to lock it and unlock it; pressing the lock key blacked the screen, but pressing it again did not bring the screen back. Scared, I eventually pulled the battery and started up again.
It happened again. And again. In the midst of all this, I slowly learned a few things: it wasn't tied to any of the new apps I'd installed (I had enough "functional time" each boot to uninstall a couple of things), it wasn't tied to internet connectivity or GPS (I had time to turn both off), and the SGS3 has a dev option to monitor CPU usage of various apps/threads. That little HUD, which overlayed everything else, would remain updating through a lockup, and I found that a process named "df" was starting up and immediately sucking up the entire CPU and not letting go.
I eventually found that it worked the processor so hard that the phone would overheat if left alone and "soft reboot" (OS restarts, but no Verizon/Samsung loading screens), so I was able to at least stop pulling the battery!
Finally, I turned it off and let it cool down for a few hours whilst Googling: no results anywhere for a similar problem or regarding the "df" process. Turning the phone back on after its reset didn't help at all. The lockup time was so quick that I couldn't even initiate a factory reset--it would lock up in the midst of preparing to perform it!
I eventually restarted it into the bootloader (meant to go for recovery, oops) to poke around and got a really scary image: a "Custom" screen before the bootloader starts that the devs are saying means that system apps/files have been modified. Now, since I don't have root yet (no hacking/voiding warranty JUST yet), I am not ABLE to modify system apps, which means that something got tweaked all by its lonesome, and THAT isn't supposed to happen. It was probably what was causing the lock, though--some driver somewhere that's supposed to say "Processor, don't try to calculate pi to infinity" got hosed or whatever.
I eventually got into stock recovery and was able to initiate the factory reset from there without the use of the actual OS (thus avoiding the hard lock). The phone rebooted fine, let me sign into Google, and spent the rest of the night redownloading apps. It's fine now.
EXTREMELY worrisome. Possibly a hardware fault with the EMMC chips holding my OS or something--there's not a lot that can knock out system files on a non-rooted device. At least it doesn't appear common, insofar as all my Googling leads to no results at all.
Any ideas as to what the heck happened?
Resolved (for now, at least)
The home key on my phone appears to have stopped working. Nothing happens when I press it. Occasionally, if I mash my finger on the area aroud the home key, my lockscreen wallpaper will display for a second or two before returning me to whatever app I was in.
A) Is there any way to tell whether this is a hardware problem (somehow not making a connection when I touch) or software problem (phone detects the touch but doesn't respond)?
B) Any simple fixes I can do to restore functionality?
C) If it is a hardware problem, what are my options? How is Samsung at handling exchanges? I've rooted my phone - if I do need to send it in, should I restore it to factory default first?
__________
10:00 am:
Okay, that's really bizarre.
Phone restart did nothing, using task manager to clear all apps and ram did nothing...
I turned off Tasker to get a clean(er) logcat to share, and then the home button started working again.
I've turned Tasker back on again, and it's still working.
Weird.
A. Have you flashed a kernel recently? Gotten it wet or Left it in a very humid area?
B and C:
You could flash to stock and reset the flash counter if the problem is still present, you are now in a state ready to get a warranty exchange for faulty hardware.
studacris said:
A. Have you flashed a kernel recently? Gotten it wet or Left it in a very humid area?
Click to expand...
Click to collapse
No to all of the above.
Trying to decipher logcat, I do see lines which suggest the system does know something is being touched:
Code:
12-10 09:31:32.768 D/InputReader( 385): Input event: value=1
12-10 09:31:32.778 D/RestrictionPolicy( 385): isHomeKeyEnabled :true
...
12-10 09:31:32.908 D/InputReader( 385): Input event: value=0
12-10 09:31:32.918 D/RestrictionPolicy( 385): isHomeKeyEnabled :true
12-10 09:31:32.928 D/RestrictionPolicy( 385): isHomeKeyEnabled :true
Okay, that's really bizarre.
Phone restart did nothing, using task manager to clear all apps and ram did nothing...
I turned off Tasker to get a clean(er) logcat to share, and then the home button started working again.
I've turned Tasker back on again, and it's still working.
Weird.
Hey guys,
I'm hoping somebody here might have an idea for where I can start to look for this problem, I have had the SGS3 for around a year now, I put CM10 on it initially (from memory), upgraded to CM10.1 when that was released via the nightly releases and I have been running those since.
Recently I updated from a Feb / early March release (cant recall specifically which one) to the next latest (mid to late March I believe) to move from 4.2.1 to 4.2.2. I believe a little after that ( if not that day) I began to very occasionally have small lock up problems with the phone. It would lag out for a short amount of time, or would just completely lock up on the screen its on for a while (if I leave it, it can be between 30 minutes to an hour before it becomes responsive again)
Often I would need to use it so I just end up having to hold the power button in to force a reboot to clear it.
Initially I thought "ok just a bug in a nightly, that's cool, it'll be patched out soon enough", a few days later a nightly came down that fixed a notification bar drop down loop problem I was getting but this other thing has stuck around, depending on how my phone feels its occurring a lot or a little each day, generally seconds / a minute after I start to use it.
I have since jumped around on a few more CM10.1 roms and I have even reverted to the 4.2.1 roms I was using ( I still have them on the phone so I know they are the right ones) to test if its that, but now they are encountering this problem as well.
The phone is completely clear now of user data, I have done a full data clear via CWM and even the original Google "welcome" setup section has locked up more than once in my attempts to set the initial configuration of the phone....
Any thoughts? CWM etc has never had a problem so while it seems to lean toward hardware i'm still thinking its software, maybe a CM10.1 release has updated something else in the phone that's now causing problems, something more firmware related etc?
EDIT: to give some examples, just before I readded my exchange details and started to sync contacts etc, I went into contacts, opened the menu and selected "Settings" to change the first name last name sorting and it just stopped on the settings button, settings was still lit up etc but it was not responsive.
Just now (about 30 minutes later) I have pressed to turn the screen on and its on the lockscreen. Great its back I think, i'll grab the baseband / kernel etc to put in here, I slide it to the unlock and bam, frozen on that now.
more info
I had a play this morning and activated the CPU overlay etc as well as strict mode.
The phone has just done it again in the play store, however the CPU overlay shows nothing out of the ordinary and there was no screen flash to indicate a long run causing a problem.
Interestingly the cursor in the search bar for google play is still blinking, so the phone is still "alive" however i cant control it via the touchscreen or the hardware buttons.
I am trying to dump the log via ADB now however its gotten as far as finding the phone and seems to have stopped (though maybe its still going, i'll see soon hopefully)
Anybody got any ideas? This is driving me crazy and i'm not sure where to go with it now, i guess back to stock is the next option then maybe a warranty claim if thats still possible....
Log collected
Either it was still collecting or it collected after the last event in the log but i've uploaded the log to pastebin here:
http://pastebin.com/Cc20CYZH
The main thing seems to be this:
Code:
W/SQLiteConnectionPool( 6385): Requests in progress:
W/SQLiteConnectionPool( 6385): execute started 646409ms ago - running, sql="COMMIT;"
W/SQLiteConnectionPool( 6385): The connection pool for database '/data/data/com.android.email/databases/EmailProvider.db' has been unable to grant a connection to thread 237 (AsyncTask #2) with flags 0x1 for 646.44104 seconds.
W/SQLiteConnectionPool( 6385): Connections: 1 active, 0 idle, 0 available.
And also this:
Code:
W/InputEventReceiver( 3327): Attempted to finish an input event but the input event receiver has already been disposed.
FYI - that bit at the bottom of the paste about the screen turning off with timeout, the screen has now turned off but i still cant turn it back on etc, soon enough it'll probably reboot (which seems to be what it ends up doing) then it'll be ok again until a problem occurs again.
I'm currently trying a new baseband as recommended here:
http://forum.xda-developers.com/showthread.php?t=2133401
Will post the results after a few days, fingers crossed.
Did you had the same problem on any other aosp or aokp based roms?
Or just try flashing the stock rom
BHARGAV33 said:
Did you had the same problem on any other aosp or aokp based roms?
Or just try flashing the stock rom
Click to expand...
Click to collapse
I actually never ended up changing back, i flashed the new baseband as above, ran the dumm file generator app a few times (letting it lock up as it went), flashed a new rom a few times as well and after all of that it seems to have worked out all the bad sectors.
Definitely seemed like I was a victim of the beginning of the SDS problem, all due to the fact i had flashed this almost immediately after receiving it and had never updated the baseband.
For those with lock up problems, go to http://forum.xda-developers.com/showthread.php?t=2133401 and follow that for installing the baseband, then do the dummy file generator etc, i'm back to a phone that works properly
PS - It took a few weeks after for it to find and remove all the problems, remember your actual ROM install could be written to bad sectors so i would definitely recommend after you run the dummy file generator a few times to update your ROM at least once, it was after 2-3 updates mine had completely settled down.
PPS - If the dummy file gen fills up your storage then crashes, just go to app info (drag from launcher is the easiest way to get here) and clear the data, that'll delete all the dummy data
PPPS - The dummy file gen can make your phone run terribly as it gets close to full, be patient, its not necessarily the lock up problem but even if it is you need to let it sort it out itself, restarting will make it worse not better.
My wife's OnePlus 6 started shutting down randomly, it usually happens up until 3 minutes after turning it on.
- It shuts down without notifying before - it's like someone killed the switch.
- It doesn't happen during the 1 minute boot up.
- Battery is charged to 95% and it still happens.
- It does not happen when connected to the charger (tried 2)
- Cleared up space from storage, she had only 500mb free, cleared 8gb.
- at twrp (it is rooted) wiped the cache partition
- tried logging using log cat, I have a saved log from during the shut down, didn't see and fatal log or something with "fatal", "shut" and "temperature"
- it seems to get quite hot at the top left side of the back side.
My next step is to factory reset, any ideas before I do this? Would like to avoid it obviously
Thanks!
goo day sir!! have you fix this issue? because its really a big problem for me thanks