Having severely scratchy, distorted music audio that usually starts after a few hours of regular use of stock music player, Doubletwist and Pandora. Also happens when automatically going back to music after answering an incoming call through my BT mono. Really strange. And when it kicks in, even my notification tones begin to sound scratchy (but oddly my ringtone sounds fine). A reboot fully corrects the issue... for a while, at least... but that's a pain and drops my battery between ~2% - 8% each time.
I clean my cache automatically daily. Thought it was a rouge app and monitored for a while through SP, but still coming up empty. And of course, I've changed up my ringtones with the thought that my regular one was blowing my speakers (I'm a child of the 80's and lost my hearing to death metal concerts in my youth, so I have to have my ringer just a notch above blaring )
Tried Timat's (same issue), now back on Sav's kernal. Tried full wipe & Calks format, flashed back to Sense, a fresh download of the ROM I'm using, did all this twice. Tried to disable stagefright in the build.prop using GScript so I could re-able when necessary (didn't work either).
Has anyone come across this? Many thanks.
jedijackie said:
Having severely scratchy, distorted music audio that usually starts after a few hours of regular use of stock music player, Doubletwist and Pandora. Also happens when automatically going back to music after answering an incoming call through my BT mono. Really strange. And when it kicks in, even my notification tones begin to sound scratchy (but oddly my ringtone sounds fine). A reboot fully corrects the issue... for a while, at least... but that's a pain and drops my battery between ~2% - 8% each time.
I clean my cache automatically daily. Thought it was a rouge app and monitored for a while through SP, but still coming up empty. And of course, I've changed up my ringtones with the thought that my regular one was blowing my speakers (I'm a child of the 80's and lost my hearing to death metal concerts in my youth, so I have to have my ringer just a notch above blaring )
Tried Timat's (same issue), now back on Sav's kernal. Tried full wipe & Calks format, flashed back to Sense, a fresh download of the ROM I'm using, did all this twice. Tried to disable stagefright in the build.prop using GScript so I could re-able when necessary (didn't work either).
Has anyone come across this? Many thanks.
Click to expand...
Click to collapse
Well, you've tried everything I would've suggested...tried different kernels, flashed backed to sense, performed a full wipe, etc. I would think that flashing back to stock would've alleviated the issue if it was software related. Perhaps your speaker is starting to fail? I've seen many people reporting needing to replace the speaker. However, it is indeed odd that its intermittent, you'd think that if the speaker was failing, it'd be consistent, and a reboot wouldn't clear it up. Odd, but I don't know what else to suggest. Have you tried tweaking the settings using DSP manager at all? If all fails, and being on stock sense doesn't fix it, I'd unroot and have it looked at by Sprint probably.
Crap, I was afraid someone would say return to store (which isn't the end of the world cuz I got it through BB and they REALLY don't care if it's rooted or not. They'll just hand me a new one). Sigh... too bad too, because I got everything else running perfectly (finally) with no fc, reboots, smooth as butter save for my music.
And yeah I played around with DSP also.
Many thanks, K2. I appreciate your response.
jedijackie said:
Crap, I was afraid someone would say return to store (which isn't the end of the world cuz I got it through BB and they REALLY don't care if it's rooted or not. They'll just hand me a new one). Sigh... too bad too, because I got everything else running perfectly (finally) with no fc, reboots, smooth as butter save for my music.
And yeah I played around with DSP also.
Many thanks, K2. I appreciate your response.
Click to expand...
Click to collapse
You definitely seemed to try just about everything but did you flash a Stock RUU? I'd nandroid backup and flash it to see if the problem still exists, if you've tried that then you would only have one option left, take it to BB. Best of luck either way.
Huh... haven't tried a Stock RUU. Good call! I'll try now and report back. Thanks Blake.
jedijackie said:
Crap, I was afraid someone would say return to store (which isn't the end of the world cuz I got it through BB and they REALLY don't care if it's rooted or not. They'll just hand me a new one). Sigh... too bad too, because I got everything else running perfectly (finally) with no fc, reboots, smooth as butter save for my music.
And yeah I played around with DSP also.
Many thanks, K2. I appreciate your response.
Click to expand...
Click to collapse
You're welcome, sorry there isn't more I can suggest. As Blake said, run RUU to unroot, which I would do before you take it in anyways. (What I meant when I said "unroot and take it in). If its still out of wack then, take it in.
Sent from my PC36100 using XDA App
I attached the Stock rooted RUU but visiting HERE should return you to unrooted stock evo.
Related
OK so this has been an issue for several months now and its gotten worse.
The ear speaker has been working intermittently and will usually not come on at all.
This seems specific to CM7 because flashing back to CM6 it works fine.
Problem is: Speaker works randomly, at first i thought it was hardware issue but every time a loud sound or voice was played through it would come on.
I would use a saved voicemail and play it a couple times and that would usually kick the speaker to work. But as of recently its doesnt come on at all, only when it wants to.
I have no idea if this would help, but using OSMonitor's log, whenever i tried to play a sound through the ear speaker it would always log audio_disable().
Sometimes reboot works, mostly it doesn't. Ive done clean wipes, fresh installs, and reverting back to previous nightlies and stables. it only has gotten worse with newer updates.
I've looked everywhere for an answer. I dont mind uploading a log, just dont no what to exactly copy for the speaker.
it happpened to me too.
Called tmobile.. pretended to run the test they told me to run.. they then agreen that it was broken internally, and sent me a replacement.
Then I un-rooted my phone, sent it to them, and life is good now
lol
do it..
any other ideas on whats causing this??any solutions besides the return?? ha
I dont know if this is a coincidence or not.. but my speaker died as soon as I flashed the Salsa Slide ROM.
I have had no issues previously.... and I am not trying to pin the blame, it just seems coincidental.
I do have a slide that I bought right at launch, so I dont know if that has anything to do with it...
Either way, I will be calling today to get it replaced because when I flashed back to NB-mod I still could not hear from the internal speaker.
I finally decided to root/s-off/ROM last week, and after following the many excellent guides around I got to a place where I liked the features and speed of the ROM I settled on (Incredible 2 HD 4.something).
Here's a breakdown of what I passed through to downgrade/s-off/root/recovery/ROM:
Friday
Downgraded from 2.3.4/Hboot0.98. Successful.
Installed CWR, su, busybox. All well.
Boot once into stock VZW GB 2.3.3.
Grab full nandroid backup of "stock" 2.3.3 as a failsafe.
Back to CWR 5.0.2.0. Installed CM7 / gapps. All still well. I wanted Sense back, so hunted for a good candidate ROM.
Settled on Incredible 2 HD from themikmik.com
Initial flash acted like I wasn't rooted (CWR .zip install said (bad) when I selected the ZIP. md5sum is perfect, so it's not a bad copy. Battery pull later and a few full wipes, install is fine.
Saturday
Inc2HD ROM is really sluggish so I decide to nuke it from orbit and start over again.
I grab the Super Wipe script and run.
Reinstall DInc2HD ROM.
Rom is very responsive, acting much better.
Start reinstalling all my apps again.
Deal with the stupid problem of sms messages from VZW (http://www.droid-life.com/2011/06/2...age-from-vzwnmn-here-is-how-to-stop-them/]fix detailed here[/URL]).
Receive and place several calls as normal throughout the day.
Gradually reinstall apps only as I need them. Keeps down the clutter
Sunday
Receive and place several calls as normal throughout the day.
Gradually reinstall more apps only as I need them.
Getting to a good state with apps re-authed and reinstalled. Decide to grab another nandroid checkpoint backup.
Backup is fine, resume normal daily use.
Monday (today)
[*]Alarm goes off as intended (yay - I have 'Clock' back after being missing on my phone since 2.3.3!)
[*]Listen to some spotify paired to my car on the drive into work
[*]Colleague calls me .. and I can't hear him. I figure it's a bad connection so I call him back. Still can't hear him through the earpiece. As a quick test I switch to speakerphone, I can now hear him.
I figured this was a one-time thing, but start test calls to DInc2 from my desk.
Damn - earpiece isn't passing any audio. Speakerphone toggle gets me audio, as does plugging in my 3.5mm earphones.
I then test other apps I know I can toggle to playback through earpiece, and no dice (Google Voice, etc). All I can hear is a very very faint buzz while a call or playback should be coming from the earpiece. When I hang up, the faint buzz in the earpiece goes dead again.
Made sure bluetooth radio was off to rule out pairing to other devices (though I haven't re-paired since wiping anyway). No wifi radio on either. All alone with the mobile network radio.
Now I know I've done a lot to the phone over the weekend, but I can't find any common cause of what might have happened between the last good call I placed on Sunday evening and today (Monday). Phone sat all night charging on my nightstand. No physical damage or anything like that.
Thinking this may be a ROM or app issue, I bounce back to my known-good snapshot of the 2.3.3 stock ROM. Problem persists - crap.
To further rule out, I full wipe and install CM7.1.0.1 from scratch just to get another baseline. Still no earpiece audio - getting frustrated!
Whatever it is, it isn't exhibiting signs of being a ROM or app issue because it persists full wipes (wipe/cache clear/dalvik wipe, and another pass even with the super-wipe script).
Yes, I've checked basics like making sure In-Call Volume is not muted. I've also installed Audio Manager to make sure there's not some lurking audio volume problem. All sliders maxed before, during and after test calls.
Uninstalled any audio-related app to attempt to remove any hold on audio output. But recall here - it's following across ROMs and wipes, so this is just busy work.
Logic says then that either
I hit some rare bug?
The process of mucking around with recoveries, ROMs, and other lower-level items has flipped a bit somewhere that will persist full user-space wipes/partitions/formats.
it's faulty hardware (which I have a hard time believing, but stranger things have happened!) This would just have to be horrible timing.
Searches on here and other sites don't bring up too much for the Incredible 2 and this kind of earpiece issue. There's a passing mention of a "silent audio bug" here, but doesn't seem relevant (nor much detail given).
I've grabbed output 'c:\> adb logcat -v time -b radio > alogcat.radio.txt' while making a call and switching between earpiece (default) and speakerphone. No really good clues there. Changes in logging verbosity didn't show too much of interest. I'll pastebin it after I scrub my phone number out if anyone's interested.
So after the wall of text ... anyone have any ideas?
I'm in it to win it with this, so I'm not unrooting and warrantying this pig I'm due for a new phone but there's nothing I want other than to just have my DInc2 back working.
I'm off to keep searching. Wondering if there are other debug-level tools/switches via adb that'd let me poke at devices, but I'm guessing those interfaces may not be as readily exposed as I'd like.
Thanks in advance all.
tl;dr - Incredible 2 earpiece randomly stopped working, but speakerphone and headphones still output phone call audio fine. Follows across wipes/ROM installs. LOLWTFBBQ?
I hate to say it, but your earpiece is probably broken... U may have smashed it with your keys in your pocket (did that on og dinc)...
Sent from my Incredible 2 using xda premium
If speakerphone and headphones work, but you cannot get sound at all from the earpiece then that would lead to me to be hardware issue... Electronics break man.. unfortunately.. and when you try to think that there is nooo way possible that you could've broken it, that's usually when you do.
Sent from my Incredible 2 using xda premium
faehsemc said:
If speakerphone and headphones work, but you cannot get sound at all from the earpiece then that would lead to me to be hardware issue... Electronics break man.. unfortunately.. and when you try to think that there is nooo way possible that you could've broken it, that's usually when you do.
Click to expand...
Click to collapse
Fair enough. I hadn't ruled out full-on hardware failure I just found it to be the least-likely of the candidates.
I had to replace the speaker in my original Incredible, so I figure it can't be too much tougher to do in this one. I'm going to exhaust some other troubleshooting first (my wife has a functional stock DInc2 that I want to compare some logcat output from, see if anything stands out when making a standard voice call).
I'm always careful to change ONE thing at a time then test to make sure my variables are where I expect them to be, so this one threw me. I'll post back with results, and hopefully get my earpiece back .
OK, I ordered a replacement earpiece and replaced it. This did not fix the audio. I tested both the original earpiece and the new earpiece before installation by using a low speaker-level source and confirmed that BOTH actually work fine and produce sound as expected.
While the phone was disassembled, I made sure all contact points were good for the earpiece. This isn't a physical problem.
So, this takes me back into the software/firmware/radio arena.
And more specifically, in order to persist all wipes and reinstalls, this has to be something below.
I'm going to use adb to flash a radio (I think there's one newer than the one I have installed, something.622? Not down at bootloader to check right now).
If this doesn't do it, anyone want to buy a DInc2 for parts and dev?
The newest radio is .1111 before that .722
Sent from my Incredible 2 using xda premium
Good call on the 1.09.01.1111 firmware. I found and flashed that instead of .722.
No effect unfortunately.
So next I'm thinking that perhaps whatever kernel I brought with me from the first ROM flash could have jacked something up in terms of audio modules or packages. It's a long shot, but I'm going to grab something like nc2_2.6.35.14#21-2.3.4.zip (non-AOSP) and flash that.
Now that I have ruled out actual hardware failure, I'm just too stubborn to give up on this .. open to productive ideas on things to check, methods to troubleshoot or rule out, etc. TIA.
What about Tue hardware connection from the speaker to phone itself? I don't know much of the board on the phone so I can't give you ideas of where to test, but if you can see where the leads go I would say follow it
Sent from my Incredible 2 using xda premium
Right. I disassembled the phone again late last night and traced back to the extent I could follow. I didn't find anything glaringly obvious or bad.
Also of note, if I'm in a super-quiet room and keep the earpiece near me with no call in progress, I hear literally nothing. As soon as a call is initiated, I hear a very faint "sputtering" sound from the earpiece (original or new earpiece), which means the symptom here clearly impacts either speaker.
So something upstream from it ... whatever pathway sends audio to this device isn't getting instantiated properly? That'd make me look to the kernel or driver to understand what pathway does work when routing audio output to the rear speaker that doesn't properly route it to the earpiece for the same call.
Recapping for my own sanity:
- Physical causes == none seen, mostly ruled out via disassembly and inspection, earpiece replacement with known-good part and known-good reassembly.
- Radio == upgrade to .722, .1111 and back to .622, no change.
- ROM == not likely culprit (problem persists any ROM replacement)
Can't fight off the nagging feeling that the act of starting down the road to S-Off + su + rooting did something here.
Given that there are guides to un-rooting (don't think you can un-S-off per se though, right) I may give that a shot since this phone is essentially a guinea pig now. Going to see how far down this rabbit hole I can go.
While I'm stewing on that does anyone have links to android filesystem reference material? I'm thinking the high-level relation between things like bootloader, recovery partition, user-space filesystem and on which levels I can address these with tools like adb. I want to try to understand if some bit could have been flipped at a layer lower than what flashing a ROM or kernel can recover, but perhaps higher than a baseband radio flash. Knowing where all these live and how they interrelate sounds interesting to me. Then I can form a better working theory on what could cause the stupid problem I'm having and if it's plausible to be in software/firmware somewhere.
There is an unrooting guide on YouTube. I find it hard to believe its software, but I work on a radar weapon system that has proven me wrong many times... But if you have flashed multiple roms then the kernel would've been reflashed atleast once and if you are doing a full boot and system wipe, whatever drivers previously installed would have been overwritten... I'm leading to believe there is a shorted componant on your board and because the voltage is so low on these, there moght not be any visual evidence. Unless u have schematics of what voltage is applied where, there isn't a way to test most of them. Especially if the gates are set to be low when applied, vice highs. I would s-on factory reset and of that doesn't work, its hardware
Sent from my Incredible 2 using xda premium
Agreed. I work with enterprise hardware/storage/cluster systems, so I'm driven by nature to root cause this silly thing - but yeah, occam's razor seems to say here that it's just a really stupid coincidence that some random component failed just at the time I began making other changes. And I can't let it go
This is even more frustrating to me because I always make a point to introduce only one change at a time then test the outcome!
After poking through the SDK/reference guide about AudioManager, I was reminded that GV has access to the earpiece audio path. While I could just make test calls in/out, this saves me from burning minutes in the process.
As a quick-and-dirty workaround (for anyone who may stumble on this in the future), you can use Google Voice to act as an internal earpiece playback test tool.
Install and then go to settings and tell it to play back via the earpiece by default and not the speaker. Then (assuming you have voicemails to play), attempt playback. You can toggle between the two audio outs in a much quicker way than I've seen in any other app. Works close enough for me to serve as a test tool as I make discrete changes as I go through troubleshooting.
Maybe there are other media playback apps that'd offer a toggle to the earpiece for playback (but why?), though I didn't look. Seems like the AudioManager reference guide implied that the earpiece was a more "protected" audio path than the speaker (but that's likely just for actual carrier network voice calls).
Cheers,
I'm really getting a kick troubleshooting.. I've been recruiting for a year and a half now.. miss working on gear.. one and a half years left and back to my ship... Can't wait
Sent from my Incredible 2 using xda premium
I actually doubt it's your ROMs --- I'm running latest unmodified vz gingerbread and all of a sudden about 5 days ago I could no longer get earpiece to function - my only guess is something shorted out because of an off-market USB charger that I got 3 of for 7 dollars off Amazon...
Anyways, I had the same sorta flutter that you seem to hear when on a call and there should be sound... and otherwise silence when silence is expected... anyways I replaced it with a brand new earpiece and EXACT same issue is happening still.
Not sure whats up but this may be the world telling me to use my Bluetooth headset more anyways... I'll post if I find anything that fixes it, but I ain't gonna hold my breath given how few ppl seem to be experiencing this issue.
Good luck
I am starting to hate this phone more and more everyday. It works different every time, sometimes it works great, sometimes it's bad.
Currently, i am having a problem that started appearing few days ago. So, i'm listening to music, and i notice the quality of the songs have gotten worse. I go over to settings, in walkman, and click on Sound enhancements, and this is what pops up: Sound effects currently not available
I am like, okaaaay, ill try another music player (poweramp).. the equalizer settings just disappeared from the options restarted my phone, and everything is okay again. So later that day, i plug in my headphones again, and i notice the quality is bad again, so i check the equalizer, "sound effects currently not available" what the hell, again? and everyday is like that. i restart my phone two times each day for the equalizer. why has this started happening? my phone is really smooth, no junk in it, not a lot of installed apps, everything works fine. and it can't be a jelly bean bug, because this started happening few days ago.
i swear, i am so trying to not mess with my phone, took a really good care of it from day one, i always do the clean up, never did i drop it once on the ground, so it's in the best stage, and the problems just keep appearing by itself...
anyone have this problem?
That's where problem starts,you didn't messed up with your phone .Just try a few roms out there or flash stock rom with flashtool & you'll start to love ur phone again
Sent from my LT26ii using xda premium
I think u should flash the original firmware with flashtool
(most people use clearaudio+ now, not sound enhancement lol )
torimatorima said:
I am starting to hate this phone more and more everyday. It works different every time, sometimes it works great, sometimes it's bad.
Currently, i am having a problem that started appearing few days ago. So, i'm listening to music, and i notice the quality of the songs have gotten worse. I go over to settings, in walkman, and click on Sound enhancements, and this is what pops up: Sound effects currently not available
I am like, okaaaay, ill try another music player (poweramp).. the equalizer settings just disappeared from the options restarted my phone, and everything is okay again. So later that day, i plug in my headphones again, and i notice the quality is bad again, so i check the equalizer, "sound effects currently not available" what the hell, again? and everyday is like that. i restart my phone two times each day for the equalizer. why has this started happening? my phone is really smooth, no junk in it, not a lot of installed apps, everything works fine. and it can't be a jelly bean bug, because this started happening few days ago.
i swear, i am so trying to not mess with my phone, took a really good care of it from day one, i always do the clean up, never did i drop it once on the ground, so it's in the best stage, and the problems just keep appearing by itself...
anyone have this problem?
Click to expand...
Click to collapse
make a backup and do a factory reset and if it doesnt helps go for a different rom
You probably mean sound enhancements? Try to uncheck clearaudio+
Sent from my heart
You hate this phone? LOL Well this phone must hate you too. If you don't like this phone, get another one. You are *****ing and moaning about this phone but you still keep it.
This problem just started for me and I have experienced nothing like it. I'm running the LG p930 with CM10.1.3 RC2. Yesterday, the phone began restarting whenever it tries playing a sound. This happens in Netflix/ Youtube once a video starts, Pandora when it attempts to start playing a song, even the sound panel when I use the volume rocker to try changing my volume and it attempts to play the little beep. It also happens no matter what speaker it tries using - headphones, speakerphone or earpiece, meaning I can't actually use the telephone functionality of the device either..
As far as fixing- I've tried clearing the cache and dalvik, fixing permissions, and even flashed several other ROMs. Everything seemed to have the same problem. Does anyone know what could be going on?
This exact thing happened to me. I couldn't find any information on it.
I had to completely format and un-brick the phone. I'm not even sure that it worked the first time. But after completely wiping and un-bricking a couple of times, it was back to normal. I think this is the guide that I have always used for that.
http://forum.xda-developers.com/showthread.php?t=1597488
Hope this works for you. I know that problem can really suck.
Thank you so much! I'll try this. I can't believe someone else had this issue, it seems incredibly rare. Can you tell me more about it? What ROM were you running? could you play any sounds at all?
Thanks again
I know what you mean. I was surprised to stumble across this post about it. I feel like I have had a few issues that just seemed very strange with this phone.
Mine was just like you described. I couldn't even change the volume without it crashing. If my phone was on vibrate, I could see the call come through. When I answered the call, the phone crashed.
I was probably on a PAC-ROM or CM10 Nightly. But like you, I probably went through every available ROM, stables and nightlies at that time. I think I even tried to flash a stock ROM.
Thank you so much. Actually, you don't have to follow the whole guide. All you need to do is download the image files, and skip to step 4 in the section "Restoring the original Nitro HD images:" Then get cwm working, and move on from there with whatever ROM you want. I would never have thought to try this. Thanks again.
For about a day now my m8 has been having some strange audio issues, and since I haven't found any other discussions surrounding it, I thought I'd drop in here as a last hope.
Essentially, almost any audio that plays from the internal speakers freezes the phone and forces me to soft reset it. Any games/music/videos locks it up, but notification/ringtones play without issue. When I try to play music, the boomsound icon appears in the notification bar, and I can change the volume for about a second before the phone freezes, though no music actually plays.
It seems to have started after I downloaded Sherlock: The Network(which I have since uninstalled), but that may be coincidental. I have a Verizon m8, rooted with S-OFF but stock ROM. I'm backing up things right now in preparation of a factory reset to hopefully resolve the issue, but if anyone has any solutions or suggestions, I'd be more than happy to hear them - can provide more info if needed.
Another edit since I'm now remembering info I was going to originally add: I did an audio test via HTC's Diagnostic Tool - which was hard enough to reach because touch tones would freeze it all up - and could not hear any of the sounds it was apparently making.
Use Titanium to freeze the suspected app, and see if the issue persists.
redpoint73 said:
Use Titanium to freeze the suspected app, and see if the issue persists.
Click to expand...
Click to collapse
I should have noted in the OP (in fact, I'll edit it in now) that I uninstalled said app as soon as the issues began. I've also checked through the running processes in hopes of finding some sound driver that wasn't responding, to no avail.
This started happening to me after installing/uninstalling Hungry Shark. Did you end up doing a factory rest? 3-4 resets a day are quite annoying...
davidwnbrgr said:
This started happening to me after installing/uninstalling Hungry Shark. Did you end up doing a factory rest? 3-4 resets a day are quite annoying...
Click to expand...
Click to collapse
Yup, in the end I had to do a factory reset and didn't reinstall the app (though I'm not sure that was entirely the source of the issue). I've had no problems with the audio since, but I know how aggravating it is to deal with.