I rooted my phone a month or two ago using odin and TWRP recovery, and I also flashed a new rom (Resurrection Remix 6.0.1). I have since had constant issues with my bluetooth headphones, which are the only bluetooth device i use with this phone. I have searched online and looked at many forums but I couldn't find very much information to help me. My issue is that there are random times where the audio from my headphones gets very choppy and unintelligible, kind of like static. It only occurs for a few seconds though, then everything resumes perfectly fine. Another big issue I have is that when I wake the screen, the same audio choppyness will occur and it will usually stay like that on the lockscreen, and when I unlock my phone, it goes away after a bit. My phone will also randomly show the message "Bluetooth messenger has stopped working" sometimes, usually after my phone is unlocked after a while of not using it. I have turned off my phone's doze function, cleared the cache many times, and factory reset it to no avail. Hope you guys can help.
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
Straight to the problem: sometimes (and in a very unpredictable manner), when i have an incoming call, plenty of problems show their ugly face. First of all, i sometimes can't accept, or decline an incoming call, because the screen isn't responding to input. Sometimes i can go around this by pressing the on/off button twice, and that would enable the screen. But, sometimes even that doesn't work. The phone just keeps ringing until the caller eventually gives up. When that happens, the phone continues to function normally.
Another problem is constant vibrations i noticed in several occasions. Instead of vibrating in "pulses" or "waves", the phone just keeps vibrating constantly, which can be very annoying in combination with the problem mentioned in the first paragraph.
At first i though it's a bug in my ROM (CM9 port for legend), but have heard people experiencing the problem on other stock devices (Galaxy SII on stock ICS, for example). So it is not that rare, but to this day i haven't been able to find a solution.
Did anyone manage to solve this problem, or find any information as to how this can be avoided?
stane37 said:
Straight to the problem: sometimes (and in a very unpredictable manner), when i have an incoming call, plenty of problems show their ugly face. First of all, i sometimes can't accept, or decline an incoming call, because the screen isn't responding to input. Sometimes i can go around this by pressing the on/off button twice, and that would enable the screen. But, sometimes even that doesn't work. The phone just keeps ringing until the caller eventually gives up. When that happens, the phone continues to function normally.
Another problem is constant vibrations i noticed in several occasions. Instead of vibrating in "pulses" or "waves", the phone just keeps vibrating constantly, which can be very annoying in combination with the problem mentioned in the first paragraph.
At first i though it's a bug in my ROM (CM9 port for legend), but have heard people experiencing the problem on other stock devices (Galaxy SII on stock ICS, for example). So it is not that rare, but to this day i haven't been able to find a solution.
Did anyone manage to solve this problem, or find any information as to how this can be avoided?
Click to expand...
Click to collapse
I have the same problem with my phone. Any solution for this problem thx
Reflash, reflash, and if it happens again - reflash. The screen lock/unlock workaround was working about 90% of the time. I gave the phone to my father (clean new flash) and he didn't experience any issues with the rom so far.
Hi Guys,
Always loved loading custom roms on my androids. Never had a problem I had to ask for help with until now. Please bear with me; I'm trying not to be noob-ish.
I'm running Resurrection Remix 4.4.2 on my Galaxy S2 GT-9100. I installed it last night. Had a big problem (after rebooting into recovery and then wipingdata/factory reset) - I couldn't mount my sdcard1 (externalSD) in CWMrecovery > hence I couldn't install the rom.zip from my SD card. I ended up using adb sideload to push the rom and GAPPS onto phone.
ROM working great so far, loving it! Suddenly; I can't adjust the audio slider for my main audio. The ring-volume and alarm volume can both be adjusted - and the speaker works when either of these two are used. My music/audio volume however won't lift up off zero. The speaker has the line through it to say it's muted completely.
I've tried using my hardware buttons, and the touchscreen to adjust it. I've searched Google & XDA. I've looking through all the settings on my phone. No luck. I've tried restarting phone. Can't think of any settings I've adjusted that could cause this. I was playing with contacts all afternoon, syncing FB images & organising Google contacts.
Please can somebody give me a hand - I've got my wedding coming up in 3 weeks and I don't have millions of hours to troubleshoot this alone.
Thanks in advance, let me know if there is anything I can do to help.
****This is strange. Just restarted my phone and it works again. Not sure then what is triggering the issue. Could be something to do with Open Mic for Google Now (it listens actively for "Ok Google"). Could be something to do with USB cable being plugged in and it thinks it is docked? Not sure any more. Working for now.****
****Now lost audio again! Was simply using my phone, using Google now to test the commands etc. Audio level dropped to zero, and I can't lift it up. Why! Perhaps it happened after phone went into standby?**** I've just checked and my WiFi doesn't go to sleep when phone is standby - it's already set to stay on.
I recently restarted my phone after the battery died, and now everytime it gets to the lock screen, I can unlock it, and it'll function seemingly fine for up to 30 seconds (usually more like 5-10), but then it automatically restarts.
The only apps I've installed since last restarting, maybe a week ago, are FolderSync and Tasker. It's possible I haven't restarted since installing AnyConnect and OpenConnect, although I'm pretty sure I did restart at least once after those, and haven't touched them since. OpenConnect did have some permissions fix item in the settings menu that would supposedly attempt to get it to work on devices where it wouldn't (it didn't work on mine), so that has me suspicious, especially since it seems sometimes these boot loops are related to permissions errors.
I'm running Philz recovery, which I can get into fine. I read about a permissions fix in some recoveries, but Philz (at least mine) doesn't seem to have it.
When the battery died, I was connected to a bluetooth speaker, playing music with Spotify. Not sure if something could have gotten corrupted having it die while the bluetooth connection was active.
It's a T-Mobile S5 and the ROM I'm running XtreSoLite 2.1 Lollipop XXU1BOC7.
Any suggestions for things to check to get it to stop restarting? If I have to wipe it, are there any ways to sort of partially wipe it? Are there a series of things I can try that would go from least extreme (not losing anything) to most extreme (fully re-flashing)? I have been able to open an adb shell and pull everything from internal storage that I don't want to lose.
Thanks in advance for any help.
Hi everyone,
My Samsung Galaxy S3 (GT-i9300) is 3.5 years old and is currently running latest Official CM 13 Nightlies ROM. Since last week, it is showing a complaint. My phone restarts at regular intervals. Most of the times, I do not let the phone discharge completely and so the android uptime will show even 15 or more days. But right now, my phone is unable to keep it running up itself for not more than two hours. Whenever I check my phone's uptime, it does not show more than 2 hours. This restarting occurs mainly when the screen is off. But when I work on the phone such as browsing or calling or watching videos, it restarts very rarely. Also sometimes, when I check my phone, it shows no network although full coverage is available in my area. At the same time, my phone will be having no sound at all (no keypad tone, no ear speaker sound, no loud speaker or music sound etc). At that time, sound will not be available even in the head phones also. Network and sound comes back after few minutes, but the issue occurs in regular intervals.. Sometimes the problem will be with network only and sometimes there will be no network and no sound. This network and sound issue started occurring at the same time when the restarting issue began.
Steps Tried :
1. I have completely factory reset my phone. I have erased system, data (including internal storage), cache and dalvik cache partitions and re-flashed most android versions (cm 11, 12 and 13) including my samsung stock jellybean rom. All roms are working in my phone. But this restarting issue occurs in all roms (even when no additional apps are installed, sim card and memory card are removed)
2. I have changed the battery and this issue (restarting and no network/sound) occurs in new battery also.
3. I have removed all connections from mainbaord which can be removed by hand except the display connector. (Removed front camera, back camera, sim/memory card tray connector, speaker/earphone jack connector, volume button connector etc) and kept the phone on. But the restarting issue still occurs.
Can anyone suggest me any solution?