This issue was mentioned before, but there isn't any recent or working solution. So...
My lower microphone doesn't work, neither in calls nor in recording applications It's very very quiet. Changing ROM, kernel, nuking the rom doesn't fix this, however sometimes the microphone works fine. Upper microphone also works fine (could be checked by switching to loadspeaker).
Does changing the charging board will fix this or the issue is elsewhere (on MB ie)? What board should I buy (new china one, used original)? What revision is best (2.2, 2.3 (this one I currently have). Or maybe the problem lays somewhere deep in the software (audio menu is ofcourse blocked)?
Is this problem even exist on the official rom?
Zile995 said:
Is this problem even exist on the official rom?
Click to expand...
Click to collapse
Actually I didn't try one. But I tried:
- CM 10.1
- AOSP Neatrom 5.0
- Neatrom from 5.9 to 6.3 (problem first occured sometime after updating to 6.0, but I could have nothing in common)
Also tested serval Dorimanx kernel, Apolo 4.13 and 4.14, latest Philz and nothing...
Try to flash stock firmware over odin. First do the full wipe in recovery and then boot phone to download mode.
Related
So basically, I installed Foxhound ROM 1.4.1 (XXALE8) with Siyah kernel and from then I have had no sound on outgoing calls (from my mic) and no sound either way on incoming calls.
After reflashing, wiping, restoring Nandroids, flashing different ROMs and everything else I could think of. There was no fix apart from going back to Stock.
If i go back to the Stock ROM then sound works 100%. I can root and install a custom recovery (via gs3 tools) with no problem and audio works perfect. But as soon as i install a custom ROM it no longer works (even ROMs which i could previously install fine).
I would really really appreciate any help at all that people can give or if anyone else has this issue if they can post so we can try to find the cause of the problem. I have found a few mentions of this here and there on different ROM threads but by posting here someone more knowledgeable may see it and be able to post a resolution.
Any help would be massively appreciated!!
boarder.2k9 said:
So basically, I installed Foxhound ROM 1.4.1 (XXALE8) with Siyah kernel and from then I have had no sound on outgoing calls (from my mic) and no sound either way on incoming calls.
After reflashing, wiping, restoring Nandroids, flashing different ROMs and everything else I could think of. There was no fix apart from going back to Stock.
If i go back to the Stock ROM then sound works 100%. I can root and install a custom recovery (via gs3 tools) with no problem and audio works perfect. But as soon as i install a custom ROM it no longer works (even ROMs which i could previously install fine).
I would really really appreciate any help at all that people can give or if anyone else has this issue if they can post so we can try to find the cause of the problem. I have found a few mentions of this here and there on different ROM threads but by posting here someone more knowledgeable may see it and be able to post a resolution.
Any help would be massively appreciated!!
Click to expand...
Click to collapse
I have the same problem, however I was on stock when it happened. And it JUST happened for no reason after a call. Nothing helps. Really nothing. I've flashed custom, different stock roms, reset etc etc. The modem must be damaged some how as KIES says there is a software update available, I download and install it and then upon reboot it says the same again. The phone looks as if it's connecting but after 10-30 seconds it says out or range or similar and disconnects from the network for about 10 seconds and then reconnects.
Sometimes I can hear a crack sound for a second before it fails to connect a call.
Everything else works perfectly.
Are you on 3 UK by any chance? Apparently an ota with new modem was released yesterday that fixes it. Look in the foxhound thread (I'm just relaying what I've read, I know no more than that)
Good luck guys
Sent from my GT-I9300 using xda app-developers app
bump.
someone managed to fix this?
anyone figure is one out yet?
Hi guys
i have galaxy S3 with the same problem when you try or make a call there is no sound even if you will used the speaker headset there is no sound and when i end the call the signal bar becomes circle void but it will came back again the signal. i try to make a software and reheat the audio ic and it is the same still no sound on call
iam live in ksa
i send it back to samsung to solve the problem and iam waitting for them
Same problem here, had no problems flashing different modems on Omega 27 until I moved from siyah kernel to Franco kernel. Now got no sound problem during call. Can get call sound back sometimes by playing wth clearing caches, fixing permissions etc. I do always get sound back by restoring nandroid. Drives me nuts! Wish I knew what causes it
Sent via TCP/IP
i am also having same problem
stock rom no modification
any solution ?
this video well describes : youtube.com/watch?v=fo46OXWEcX0
Problem with audio
MonsterMMORPG said:
i am also having same problem
stock rom no modification
any solution ?
this video well describes : youtube.com/watch?v=fo46OXWEcX0
Click to expand...
Click to collapse
Hi guys, i'm from Portugal, and i have installed omni rom 4.4.2 into my Samsung Galaxy S3 LTE ( GT-I9305). I installed properly using full wipe and cleaning the cache but, after a week using this rom, the sound into my device was death. Don't have sound into notifications, calls, even using headphones, don't have sound. Already reinstall the room making all the process again, but i have the same problem all the time. Someone can help me please?
Info:
Model : GT-I9305
Android Version: 4.4.2
Omni Version: 4.4.2-20140220-i9305-NIGHTLY
BaseBand Version: I9305XXBLL5
Kernel Version : 3.0.64-CM-g659c99f
[email protected] #1
Thu Feb 20 02:07:18 CET 2014
Compilation number: omni_i9305-userbug 4.4.2 KVT49L 149 test-keys
Thnks for the assist
Whenever I make a call, the person on the other side reports low audio from my end. Its the same when recording audio, the volume is very low. I am using a 4.1.1 rom with latest Siyah kernel. I have tried several different roms (even aosp) and the problem still persists. I doubt it a jelly bean issue since everything was working fine until the past few days when I decided to experiment with a plethora of different roms. I have tried all the basic fixes (wipe cache, fix permission, flash different kernel) and am out of ideas. Could you guys please recommend some solutions? Thanks.
Firstly try to clean your microphone with a pin (bottom and top). If it is software it could be kernel related. Try reverting back to stock ics and that try to make a call
I've started getting a situation when I install a MIUI based ROM in my I9300T, and any call to or from a mobile has extremely distorted audio (sounds like an amplifier trying to run at 150%) in both directions.
The audio is fine to landlines, so it sounds like it might be CODEC based.
I've done factory resets, Dalvik, Cache, reflash, new modem, reduced volume, and everything else I can think of. Flashing back to a non-MIUI resolves the problem, and re-flashing MIUI brings it back every time.
I've found a couple of threads asking about this problem, but nobody has every given a suggested solution (other than reset, reflash, modem).
Has anyone here experienced this or found a solutions?
Cheers,
Jason
AW: [Q] Badly clipped voice audio running MIUI based roms
Had exactlythe same problem, tried different MIUI versions, different modems etc. Call audio on ALL Samsung based MIUI was terrible, it worked only well on MIUI polimorph (which is AOSP/CM based). But on this MIUI I had issues with Bluetooth...
I read somewhere that this problem may occur when you come from stock Samsung Jellybean ROM and then flash a Jeallybean MIUI. So I tried following:
1. Download a ICS Stock Samsung ROM (for example 4.0.4) - important: complete ROM with PDA, Modem & CSC)
2. Flash ICS ROM with ODIN -- warning: all your data on internal SD will be erased!
3. Boot into your ICS Stock Samsung ROM (just to check call audio, should be fine...)
4. Flash CWM
5. Restart phone into CWM and flash your MIUI
6. Wipe data/factory reset
7. Restart & boot your MIUI. In case you got stuck while booting into MIUI do another full wipe data/cache in CWM. Then booting into MIUI should work fine.
!!! Attention: ALL YOUR DATA ON INTERNAL SD ARE ERASED WITH THIS METHOD !!! Be sure to copy your data, backups etc. to external SD or to your PC/laptop !!!
This was the solution I found after 1,5 weeks trying and reading and trying etc... Hope this works for you also!
Btw: be very careful doing this - there is always a risk of bricking your phone! Read carefully all about flashing with ODIN! Good luck...
Brilliant, thanks for the lengthy response!
The main thing I was wanting was an acknowledgement that someone had experienced and been able to overcome the problem, and you've included a description of exactly how you did it too.
Thank you very much for the help, and I'll post back in here if this works for me too in case others have the same problem.
I'd love to know which part of this process actually resolves the issue. I wonder what aspect of the JB ROM is not erased or overwritten by the MIUI installer.
AW: [Q] Badly clipped voice audio running MIUI based roms
You're welcome mate!
I'm also wondering WHY this helped, but it did... I only read somewhere in the forums that all the Bluetooth and WiFi issues on CM 10.1 only happen when flashing from a JB Samsung ROM, and everything is ok when coming from an ICS ROM. So I thought it is worth the try...
And I'm really happy now that I can use my beloved MIUI (Sammy-based MIUI-India) on my SGS3
Wow, what a grind this was to implement.
OK, so I...
1. Odin installed 4.0.4 and reset
2. Flashed MIUI m0, same problem
3. Odin installed 4.0.4 again, reset
4. Made a call, no audio at all
5. Factory reset again
6. Made a call, receive audio only, no send
7. Factory reset again
8. Reflashed MIUI m0
9. Made a call, no audio
10. Flashed modem DUELL2
11. Audio works!
12. FlashedMIUI India
Finally, MIUI and working audio!
You'd think from this list that flashing the new modem would have fixed the original issue, but I'd already tried this several times with no luck.
I'm guessing there is something in the 4.0.4 roms that is set in the flash related to a hardware codec. It may be that in JB the values are modified, and once it's been changed MIUI doesn't have any means of resetting it, during installation or subsequent booting.
Now I've wasted many hours on this, but at least I can go home happy
AW: [Q] Badly clipped voice audio running MIUI based roms
Really much work, but finally you got it working! Congrats!
Yes, I know, only flashing different modems without flashing ICS before won't help with this weird MIUI audio issue... Can't remember all the modems I tried, but tried many...
Hi,
If phone is on stock samsung rom (latest 4.1.2 or experimental samsung 4.3) it can not go to sleep (turn of screen). If I install custom 4.3 or 4.2.2 or 4.4 rom phone go to sleep nicely but there is no sound in media. Phone have sound in call but no sound playing video or audio. When I put back stock or any other 4.1.2 rom, with sound there is no problem. But screen does not turn off. What could be wrong with phone? Where I have to look for problems?
If you´re in stock (4.1.2) There your dont get into "sleep"? Or only on experimental Android?
tiebiex said:
If you´re in stock (4.1.2) There your dont get into "sleep"? Or only on experimental Android?
Click to expand...
Click to collapse
On stock 4.1.2 phone does not turn screen off (but everything else works). Also if I update to Open Europe test 4.3 firmware from here
http://www.sammobile.com/2013/12/13/open-europe-test-firmwares-available-for-galaxy-s-iii-gt-i9300-and-galaxy-note-ii-gt-n7100/
phone does not turn off screen.
If I put some custom 4.3 or 4.4 firmware (I have tried few) phone turns the screen off as it should, but then there is no multimedia sound. I can not play any video or mp3 file with sound... but there is sound when calling.
Do a full wipe, format internal sd card then use odin to flash the latest 4.3 official stock rom.
Test before you install/restore anything, if still the same then you have a hardware fault.
I was using slimkat 4.4.2 and restored the official samsung rom 4.3 to try a mhl cable. The result as you may know is that I couldn't install any custom rom that wasn't based on samsung's after that.
Searching here in the forums I found some people saying that it was because of a layout change on partitions, others because of knox, or the update in bootloader...
I installed the twrp-2.7.1.0 recovery and tried to install omni rom with pa_gapps, cm11 etc and I always get an error for gapps (couldn't find build.prop or something...). Tried Omega v58 (based on sam) and it worked, then I tried slimkat 4.4.3 weekly and slim_AIO_gapps (advanced wipe, everything but extsd, format data) and it installed everything fine.
It's almost perfect but now I have only a small problem... when I plug the headset the audio is really bad and sometimes I can't hear anything ... I tried another kernel with the same result. Tried slimkat 4.4.2 stable, same.
Does it make any sense to anyone here? any sugestions on how to fix? flash something somewhere maybe :x
and what is the real problem after the 4.3 official update? if slimkat is working maybe we can make other roms work too.
Thank you in advance
Do a full wipe, all your previous issues were due to files left over from other firmware.
On the headset, go back to stock firmware after a full wipe. If still the same then it is hardware.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Do a full wipe, all your previous issues were due to files left over from other firmware.
Click to expand...
Click to collapse
I still can't install most roms even with full wipe (gapps error) after the 4.3 official update but I'm happy with slimkat. I think maybe it works because it just copies the gapps files to android without doing other checks, maybe editing the scripts we can "force" the install of other roms too. If anyone have any info, please tell me.
boomboomer said:
On the headset, go back to stock firmware after a full wipe. If still the same then it is hardware.
Click to expand...
Click to collapse
Oh, I think it was just a series of bad coincidences. Tried the stock firmware and the headset did not work. Seems like my headset broke the same day all that stuff happened, and I tried the one I use on PC but it didn't connect firmly on s3 so the sound was bad too... just tried a new phone headset and it's working fine.. thank you