[Q] i9000M Handset audio issue after upgrade - Galaxy S I9000 Q&A, Help & Troubleshooting

Long time reader, first time poster....
Phone: i9000M from Bell in Canada
Original Firmware: UGJH2
Updated to: XXJW4
After upgrading (flash via ODIN), the handset speaker is VERY quiet (almost silent). Unless the person on the other end screams, it is not audible. I tried flashing several modems, with no change. I have done a hard reset, wiped the device and reflashed with no luck.
I physically opened up the phone to check the connection which was fine. I checked the actual pin holes in the speaker and they were clear. I have tried several apps (Voodoo, Volume+, etc.) and they had zero effect. I tried the service menu as well, no luck.
I am stumped on how audio works fine via all other outputs (rear speaker, headphones, bluetooth) but not via the handset.
Has anyone else encountered this? The only thing I have not tried is flashing the original ROM back. I am searching for it now and hope to test this soon.
Thanks in advance,
Zimzum
*UPDATE 1* I did some further testing with two different headsets: the Samsung headset w/mic that came with the phone as well as a pair of standard earphones. When the standard headphones are plugged in, the in-call volume is normal (similar to any other phone). When the Samsung headset w/mic is plugged in, the call volume is VERY quite (almost impossible to hear the other party), even with volume set to max (100).
*UPDATE 2* When I upgraded the phone XXJW4, it went into a boot loop, so I checked the thread where I grabbed the ROM from and there were several others who had the same issue. The fix was posted by a user that said to flash his attached dbdata file, which was missing and causing the boot loop. I flashes this and it booted fine. Not sure if this could have any impact on in-call audio quality but it the only exception that I could think of from a usual ROM update.

Related

N1 thinks I'm using Headphones

Weirdest thing. I installed recovery-RA-nexus-v1.7.0.1-cyan.img again and immediately loading up my existing OS, I found I couldn't hear out of the phone's ear piece. The back speaker worked.
I eventually got it working by loading up the music app and plugging/unplugging in headphones a few times. Typically the music will pause when you pull out your headphones. It appears this "sense" is broken. So it just thinks my headphones are always plugged in. Sucks because the ear piece is muted thus useless for calls without a headset or using the back speaker.
Well I flashed a Mocado Sense rom, and noticed the headphone icon in the tray. I can't get it to go away. Tried same methods as before.
I've flashed back to Geo411gm's stock FRF91 rom: http://forum.xda-developers.com/showthread.php?t=714184
Same thing. Advice?
[Update]
Wow. I Fixed it but I can replicated it easily. Seems it isn't properly detecting removal of the headset jack. I have to really tweak the jack to get it to start playing through the phones speakers.
Anyone else experience this?
Anyone?
Right now I'm flashing PASSIMG.zip for ERD79 to see if it was something to do with recovery image or custom firmware. I'm thinking it might be a hardware problem though which sucks.
I've used my headphones in the past without problem. I reboot my phone all the time too. Just seemed it started after the recovery image was loaded.
[UPDATE]
No i'm sittin' pretty at ERD79, downloading the FRF91 update as I type this and the headphone jack is still screwed up.
Calling Google.
[UPDATE 2]
Called Google and HTC. Getting an Advanced replacement next week sometime.

[Q] Mic Button No Longer Working - Help !!

Having a weird issue with my Samsung Captivate and I'm seeking the advice of those smarter than myslef . Lately my mic has stopped responding while listening to music. The strange thing is that it still pauses the music but it doesn't pick up any calls. I've tried several music players (even the default) with the same result. I didn't always have this problem. I'm currently running cog 2.2 beta 9, I did a master clear and flashed back to stock but that didn't fix the issue either.
Is it possible my captivate is defective or is something that can be fixed via software. I've also tried multiple headsets.
What was your final outcome? I had a similar problem (no mic OR pause). Tried many things and am now resorting to replacing the unit (warranty). My post: http://forum.xda-developers.com/showthread.php?t=1112729&highlight=mic
Thanks,
DaveCT

[Q] Ear speaker completely mute and black screen during calls

So yesterday my N1 was working fine, I put it to charge and today it's acting all strange:
I can make calls, but when I take the phone to the ear it goes black and doesn't come back. Sometimes if I press trackball or power it does, but normally it should show me the in call screen when I move away.
I can't hear anything from the ear speaker. I don't hear the calling tone, and when the other side picks up (I feel the vibration that tells me that) I can't hear anything. Speaker works fine, only the ear speaker that don't.
I've tried wiping everything twice, removing the battery and putting it back again, downgrading CM to 7.0, and nothing works. The question is: is this a hardware problem (speaker dead) that is making the call screen bug, or is it a software bug that is causing the ear speaker to be mute?
I accept suggestions on how to test it.
UPDATE 1: connecting an external headset on the 3.5 mm plug doesn't work either, I tried to place a call and no sound came of the headset, and neither media apps like youtube redirected the sound to it.
Have you tried doing a full wipe, plus while your at it you might as well reflash your ROM with a system wipe. That should fix you up.
I flashed a whole new stack of stock stuff (boot, recovery, system), going back even to 2.1, and still no game.
Then I opened it and changed the top circuit board for one I had here (I replaced it with a new one because of the power button), and still no game.
So I can't think of anything else short of a total loss of this phone, maybe some circuitry on the bottom board fried or something like this.
I don't see any solution for my poor nexus

Very strange (temporary) audio bug

Hi guys/gals,
Yesterday was a very strange day for my new (ATT branded) Nexus 6. It was working fine in the morning with no issues. It sat on my desk next to me for a few hours and I noticed no problems. (Tangent: I spilled some water near the phone and the bottom of the case got wet, however none got on the actual phone - but it made what happened next much more terrifying!)
I pick up the phone to listen to a podcast while walking my dog, and no sound. Adjust volume, reset phone, still no sound.
After a bit of investigation, only SOME of the sound functions worked.
Worked:
Volume rocker beep (ringer volume only)
In-call speakerphone
Ringtones in-menu (no one called me, didn't test that)
Did not work:
All media playback
Touch sounds
In-call handset non-speakerphone
Dial buttons sounds
I suspected it was a problem with the system, so I reinstalled my ROM.... didn't work. (ressurection remix from Feb.08)
I suspected it was a problem with the ROM, so I installed a different one.... didn't work. (Chroma current version)
This morning, I re-installed my original ROM with a new GApps package (but booted without GApps first) and everything was back to normal. I Still have no idea what happened.
What happened here? My first guess was some app updated and somehow broke the audio stack, but the problem persisted over a new ROM. I'm stumped.
deleted
I had nearly the exact same experience today. I am stock though.
On a hunch i plugged in headphones, which worked. Then when I unplugged them the problem was gone.

Speaker and Earpiece NOT WORKING

So I encountered this problem today. Was watching a YouTube video and then paused it, spoke to my dad for a few seconds, resumed the video and BAM! The sound was gone. First I thought there's some problem with the video or the app. Replayed the video and also restarted the app, none worked. Rebooted the phone, the Nokia jingle didn't come at the boot screen. Starting to freak out, I booted into safe mode, this time the jingle did come and speakers and Earpiece both were working just fine. So it seemed a software issue and in the hopes that now everything would be fine, rebooted the phone into the normal mode. Rebooted into normal mode and NOPE! No audio via the speakers or the Earpiece. Tried calling and it worked on the speakerphone however when I'd disable the speakerphone, I couldn't hear anything nor the person on the other end. Although, when I get a call, the speakers are working just fine. As of writing this, the problem still persists where Audio through Earpiece and speakerphone is not coming. Tried the following : 1. Reboot 2. Reboot into safe mode. 3. Plug in/out earphones for atleast 10-20 times. 4. Dial some *#*# number to check the Earpiece. Nothing seems to work. Please help if anyone of you have encountered this issue. Seems a software issue though.
Well, booted into safe mode once again( Nokia jingle came this time) and played a song.(sound through the speakers came nice and clear). Powered off the phone and then powered it back on(Nokia jingle did come) and, VOILA! Everything has started working although afraid to put the earphones into the jack. Let's see, will keep you all updated.
Update
Hi.any update in regard to this? Im facing the same issue right now
Memi88105 said:
Hi.any update in regard to this? Im facing the same issue right now
Click to expand...
Click to collapse
hey i would just suggest that you don't panic and do what i did (read the above two posts). it should start working without any problems.
hehe. yeah. I have contacted their customer support and they suggest me to do a soft reset. however I failed to do so-I guess, for theres a red warning sign in my android that showed up while im doing the reset with stated "no command" below.
Will try the above procedures when I encounter it again.(its working fine now. after constant restart.lol)
I haven't tried inserting earphones tho.
thanks a lot'
Same problem , any solutions?
Try doing what's written in the second post. It could've been a fluke in my case but fortunately it did work and that issue has never come up ever since.

Categories

Resources