Develop Bugs

[Q] Sound Issues

i have been having issues with no sound coming from the LG nitro , all of a sudden it cut out yesterday and have hard reset numerous times and 1 out of 4 or 5 reboots the sound comes in but if you power off then on the sound disappears .. this is a stock phone with only root , anybody have any ideas or similiar issues ?

This is not any kind of development related topic but I'd suggest that you bring it in for repair or replacement as that sounds like a hardware issue. Maybe try flashing another rom.
Sent from my LG-P930 using XDA App

moved to general

I had a similar issue and ended up returning the phone to bell for a new one.
Here is the long story just in case it helps some one. Like all good Android users I started by rooting my phone, installing ROM Manager and making a nandroid backup. Once this was done I ran rooted stock for a few days. All was well.
Then I started to debloat my phone. After which everything seamed good. Then installed and played with RAM Manager and SD Speed Increase. TBH i did not notice any particular increase in speed on my phone but that might be due to the following issue.
After all this I decided to run a few test by using the phone into the ground. Added a bluetooth headset, while using navigation and making several calls. It was all running very well until I rebooted. Once rebooted whenever I connect my bluetooth headset I was no longer able to make calls. The phone dialer would completely lag out until I de-activated bluetooth. The the 10 or so test calls I tried making would all go through at once. This wasn't the end of the word for me so I continued to use the phone as everything else was working fine. The things started degrading by which time I was on the new CM9 nightly build. The phone had started being really sluggish. I finally decided to return my phone after it would no longer play any sound and whenever it called to any sound related function would lag out and/or reboot. The same behavior happen in stock, cm9 and NO! NO! ROMs. I tried flashing a few roms in a last ditch effort.
I could be wrong by my conclusion is that the audio portion of the snapdargon chip fried and since these phone are basically just 1 chip the phone simply degraded from there.
I would like to know of anyone else has had similar issue or if I just got a lemon and also your take on the cause of the issue.
Hope this can help someone.
Thanks!
Edit: Returned my phone for a new one and I've been flashing CM9 since the first release and no issues. I'm actually really happy with the replacement and would recommend the phone as long as you don't get a lemon ;-)

[Q] No DInc2 Earpiece Audio - Speakerphone works fine

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

[Q] Changing resolution and power issues One X

Hi all
Had the One X (from vodafone uk) for about 6 weeks now - fantastic phone and very happy until yesterday. The phone started doing this on Sunday afternoon and has become progressively worse over the last 24 hours.
Possibly unrelated but the issue first occurred after installing 6 app updates (astro file manager, dropbox, frontline commando and 3 others which escape me)
Display goes from "normal" to ultra low resolution. Seems to coincide with buttons becoming unresponsive (including power). Phone will often not display anything though I can here alerts as messages come in. If I hold in power button to turn phone off the back, menu and recent apps buttons flash briefly but phone display does not come back on.
I tried to link to some images from my public dropbox folder but don't have enough posts on here yet. Attazhed 7z file with png of the display going batsh1t.
Yesterday it was somewhat intermittent today its become progressively worse however. In between bursts of display oddity I managed to get the latest OTA updata from HTC/Vodafone installed 1.29.161.3 but problem persists. I've also done a factory reset to no avail.
Current versions if this is in any way useful:
Android version 4.0.3
HTC sense 4.0
kernel version 2.6.39.4-g1389c4c
I'm guessing as factory reset did not work and neither did the OTA update then I'm looking at hardware issue (GFX or CPU or mainboard?) and most likely back to Vodafone for repair. Just seeking advice if I'm on to the right likely issue here and if anyone else had same/similar issue in case a software update *could* resolve the issue.
Cheers

looks like hardware issue like not all of the data is being sent to the screen, did you drop it or something?
anyway send it back and get it repaired or replaced
this happened to one of my old desire, i dropped it hard and the screen went all low res and weird colours

RESOLVED: Changing resolution and power issues One X
Hi Mox, thanks for that, sort of confirms what I already suspected. Was just hoping a software update or similar could resolve rather than saying goodbye to the phone for 3 weeks while Vodafone sort it.
Don't remember dropping the phone (but I have kids).
Sorting out with Vodafone now. Thanks again.

Inconsistent Playing of Touch Sounds

So I am hoping someone with some real hardware/software knowledge can provide some input...
I recently received my warranty replacement unit because of unresponsive touch and phantom touches. My new unit seems to work perfectly, except now every 10 to 20 touches, the touch will register, but the touch sound "click" doesn't play (if I put my ear close to the speaker, I can hear the speaker activating though). Repeated touches (like repeatedly pressing back) won't reproduce the problem, but more random timing and touches (like in regular use or typing) will. I'm wondering if anyone thinks this is a hardware issue, or some component of the stock software that wouldn't have been overwritten between the update to JSS15Q, and then to JSS15R (it happens in all three versions).
Think I should go for another replacement? Or do you think I should root and unlock, and see if a full installation of a ROM fixes it. It's definitely a sign that something is wrong and it's annoying, I just can't figure out if it's software or hardware related. I'm definitely not going to just ignore it.
(SIDE STORY: When I called nexus help for my first unit, the guy was so helpful and took my word that I had already tried factory resets, and set me up for an RMA. My call on this unit, the woman told me to reboot and toggle touch sounds, and kind of rudely insisted that I was on 4.3 and that Build Version (e.g. JSS15R) had nothing to do with software!! :what: She then told me she'd send me an email with more troubleshooting steps, which never came. I had figured I'd wait for the email, so that I had her name for my next call. Totally unacceptable.)

You come off as just looking for a reason to complain at this point, there doesn't seem to be any real problem with your device other than you being overly picky
Sent from my HTC One using Tapatalk 4

You're completely right. I was so delighted when I managed to find something wrong with my new tablet...
Seriously? You come off as just a worthless ass of a poster at this point. The problem is there, and can be consistently reproduced. I press home and it clicks, and five seconds later I press home and it doesn't click. Your opinion on whether this is a "real problem" or me being overly "picky" is completely irrelevant. It is most certainly real and not normal, and indicates either some software or driver bug on my device, or a strange hardware malfunction. My previous unit (which had very real problems) did not have this problem.
I hope I speak for others here, when I tell you to **** off unless you have something worthwhile to contribute. Just because you don't think something is important, annoying, significant, etc. doesn't make it any less so for someone else.

Do you have this issue with SwiftKey?
Sent from my Nexus 7 using XDA Premium 4 mobile app

Yeah. It's actually everywhere throughout the OS. System settings, stock launcher, Nova launcher, Swiftkey, AOSP keyboard, etc.

I have the opposite problem as you. When muted, every 20 or 30 taps I will get a 'pop' from the speakers, similar to the sound of plugging a guitar into an amp when it's on. Pretty bloody annoying, but I don't want to risk returning it for receiving a unit with worse problems.

GoneTomorrow said:
I have the opposite problem as you. When muted, every 20 or 30 taps I will get a 'pop' from the speakers, similar to the sound of plugging a guitar into an amp when it's on. Pretty bloody annoying, but I don't want to risk returning it for receiving a unit with worse problems.
Click to expand...
Click to collapse
Exactly my thoughts on going through another RMA. But I do feel that it's reasonable to expect a properly functioning tablet on our parts. What you're experiencing is strange. I can tell you that on my Optimus G, when muted, I can hear a faint speaker "activation". Sounds like maybe yours is a hardware issue. Are you stock, or have you tried flashing other ROMs?

Well, I installed CM10.2 last night, and the problem went away. Maybe you might want to try CM, or even just unlocking and reflashing stock JSS15R. You might get lucky with your popping noises.

FYI: I've seen this on multiple tablets (TF101, GTab, Nooks, 2012N7, 2013N7) with different customed ROMs.
So, I wouldn't blame it specially on the Tab. In fact, I see this issue less often on the 2013N7. It usually happens
after I just freshly loaded a new ROM.

spackmanbr said:
Well, I installed CM10.2 last night, and the problem went away. Maybe you might want to try CM, or even just unlocking and reflashing stock JSS15R. You might get lucky with your popping noises.
Click to expand...
Click to collapse
So a couple of nights ago, I decided to try disabling touch sounds in settings. Since doing that I haven't heard a single pop from the speakers. Looks like it was either the touch sounds 'leaking' or the speakers popping from being activated, which they do even when muted (the mute being software)
I'm quite happy with this fix, since the tablet is muted 99.5% of the time, and I don't care for the touch sounds anyway.

Hi Folk's,
Sorry to drag up an old post, but I've noticed my N7 shows this behaviour on KitKat as well.
It misses the touch sound if you pause for about 5 secs during input. Does it every time and it's very annoying. I've tried a couple of different KK roms and it does the same on all of them.
Just tried going back to CM10.2 (JB 4.3) and it works fine!
Does anyone know the cure for this, apart from going back to JB, please? Would really like to be running KK, but this bug is bugging me!
Thanks for any info.
Cheers

I have bought one nexus 7 2013 32gb recently and im experiente this strange beahvior ...im on lolipop 5.1.1! What i have to do to solucionate?

Petermira said:
I have bought one nexus 7 2013 32gb recently and im experiente this strange beahvior ...im on lolipop 5.1.1! What i have to do to solucionate?
Click to expand...
Click to collapse
@Petermira @Xi2or @spackmanbr
I have this same behavior on a stock 4.4.2 S3.
After 5 seconds, if I click anything UI (keyboard, Soft buttons, shortcuts, toggles) there is no sound. If I quickly click again and keep clicking, the sounds work as normal. It's definitely ROM related but is there a fix???
UPDATE: Issue does not happen with headphones plugged in. STRANGE!!!
UPDATE: Issue does not happen if I keep a song playing in Power Amp or similar.
Affected UI items include:
- keyboard
- shortcuts
- toggles
- capacitive buttons
- dialer pad
- etc.

Help with CM11 no sound on calls

Hello,
First I apologize for opening a new thread instead of posting in the CM11 thread, but till now I don't have write privileges there.
I recently unlocked and permrooted my Desire HD then installed Mustaavalkosta's CM11, but as a newbie, I have some issues I require assistance with. To note that I did an extensive reading before I did any rooting and installing a new rom.
1- I find myself not hearing anything during calls. It's sort of like my internal speaker got muted somehow after installing CM11. I tried multiple apps to no avail. I read somewhere that if u fail to flash the boot.img in the rom u might get this issue, but thing is I did flash the boot.img after I installed the rom and the recovery and wiped the cache. I can hear the calls with the external speaker turned on and with the headphone, so I think it's not a hardware issue but a software one. Any fix to this?
2- After each restart, the UI somehow resets itself. I mean many of the settings and widgets I use either get reset or vanish like the sleep option in seetings for example (I put the screen to turn off after a 1 min and it resets to 15 sec after each reboot which is annoying as hell). Also, many apps like Dolphin and GoSMSPro shortcuts vanish from the home screen after each reboot, while whatsapp for example doesn't. I'm not able to figure why some app shortcuts vanish while others don't.
3- I tried to use ART instead of dalvik, but yet again after each reboot, dalvik is back. So effectively, I can't benefit from ART.
4- other minor bugs which I will not mention for now till I solve the 3 main ones.
If someone can provide some assistance (mainly for the first issue which is the major one), I will be very grateful. It's becoming increasingly annoying and embarrassing to turn the speaker on every time I receive a call, bc most of the times I am in a room with other individuals or in a meeting, and I am forced to have them hear the conversations bc not always I can excuse myself.

No one has any input on this?

After wiping data, dalvik cache, android secure, etc... and reinstalling the stock rooted 2.3.5 Rom, I still had the same internal speaker issue on calls. The heaphone icon was on even though there were no headphones plugged. I installed 2 widgets (togggleheadset 2 and headphone fix) and the issue was fixed. To note I had this problem back on my unrooted stock Desire HD before I rooted it and upgraded to CM11 BR3 thinking the new rom will fix this problem.
So after I made the calls work on Gingerbread stock rooted rom, I did a clean wipe once more and installed CM11 BR4. The problem reemerged. And the 2 widgets couldn't be redownloaded bc they are not compatible with kitkat. The other issues mentioned in the OP disappeared, only the incall volume issue remained.
I need to mention that many Desire HD owners have had this problem on their Froyo and Gingerbread stock builds, and usually the 2 widgets I mentioned above helped fix the issue. On 4.4.2, it seems some android users have complained of in-speaker audio volume being very low, so maybe this worsens the issue I had instead of fixing it.
I'm leaning to think that it's mostly a software/code issue, otherwise why would the widgets fix the problem on an earlier version if it's hardware related? hence, there could be a workaround for it on Kitkat if someone knowledgeable cares to look at it. Maybe the code turns off the internal speaker or lowers the volume so much it becomes unhearable. The headphone and external speaker are just fine, I can hear the other person in the call without any problem. It's when I rely on the internal speaker that I hear nothing.
Hope someone can offer some assistance here.