The in call audio doesnt work through the normal call speaker or speakerphone. However when i connect to earphones it does work. I have tried rebooting, battery pulling and cache&dalvik wiping. I feel like I read this being a CM issue but i cant find the source. Im running the PAC man Rom, its kernel, and the team acid audio engine mod and clear audio add ons. Does anyone have a solution? Thanks.
Update: So I found and flashed the CM workaround, but that didn't work. I flashed it a few more times and every time i tried to call someone the screen temporarily froze and the call screen failed to show up. I suspected it was a hardware problem. I then wiped and flashed a touchwiz and the problem was gone. So its seems that the problem was of CM origin. Idk why the problem persisted. Im attempting to find a fix in the CM thread and S4 noob faq, so i guess this thread can be closed down.
Related
So I've been browsing the forums trying to look for anyone with a similar issue but to no avail. Now I'm not sure if this issue pertains to CM9 but I've noticed that ever since I've flashed RC1 or a later nightly, every app that uses the microphone reverts the phone speaker to call speaker. This is highly irritating as I have to put my ear to the phone every time I want to hear say, music, notifications etc. I usually reset this by plugging in a pair of headphones and then taking it back out, however the problem still persists every time I use the mic. This does not happen during calls so that's fine.
I am quite certain that this isn't hardware related because it only happens after using the microphone through some app and resets itself using the headphone workaround or a reboot. Again, I don't know if this is a singled out issue or if it pertains to the phone or the latest CM9 ROM.
Any help would be appreciated.
So after updating to RC2 and then again to the latest Nightly (20120802) I still have no luck with my loud speaker and my call speaker. To test this I usually use the Tune Me app and mess around with it and record some things but after using the app, instead of playing through the loud speaker like its supposed to, it plays audio through the call speaker.
Also, when I previewed CM10 and was playing around with Google Now with voice the same thing occurred. I don't know if there's a conflicting issue with some apps I've installed or something that installing the ROM did but any form of support would be appreciated.
Thanks.
So after searching around the web and installing different ROMs I cannot seem to fix an issue with my Verizon Galaxy Nexus. My volume on speaker will just go real low by itself when listening to music/spotify/tunein. Sometimes if I wait a few minutes it will come back on by itself. Other times it takes a battery pull to get volume back. Even just a reboot doesn't fix it. I've tried the tricks that have been posted in the forums but nothing seems to work. This is only with the speakerphone. Headphone jack works great all day long. Here are the ROMS I've tried with no help.
MmuzzyROM, CM10.1, paranoidandroid, AOKP
Is there a specific kernel that fixes this?
Thanks for the help.
Hello and thanks in advance for any help that can be offered. This is my first post on XDA so I hope I'm doing things right!
I've searched (on this forum and others) and found no answers to my issue. I've flashed JellyBam 9.1.2 onto my Samsung Galaxy S3 (SGH-I747). All is well and I love the options/interface but when I make or receive calls I can hear others but they can't hear me at all. Initially I flashed back to pure stock touchwiz and the mic started working fine again so I know it isn't hardware related. Upon flashing JellyBam again the mic worked initially! But the next day (and after a reboot) the mic once again won't pick up my voice on calls. I have to yell into the mic on speakerphone to be heard at all.
This is very frustrating as I've flashed other baseband/modem versions on the phone (from stock to the most current) and nothing is working with JellyBam. I've also tried other kernels to no avail. I'm stumped and beginning to think I may have to go back to basic touchwiz for this to work.
What else could i be overlooking? Are there any other custom roms that will work fine with the mics on Galaxy S3 att? Some other fix I'm not catching or doing properly. Any help at all would be great. Thanks again.
Sorry, but Jellybam is not supported on these forums, for not releasing kernel source and kanging features that are not theirs. I advise you to flash a ROM here on XDA and see if you can reproduce the problem. This is not the right place to be posting this, there is a Q&A section for questions. Welcome to XDA!
Is there any kikkat rom available for lg-g-pro without "speaker issue" ?
Let me explain: when i make a call and bring the phone to my ear the speaker mutes. Also there are some posts with the same issue in Viber.
I've tried several CM-bases roms (10.2, 11) and all of them have the speaker problem in Skype.
Any suggestions ? Stock looks awful after glossy KK =(
plz suggest me a perfect custom rom kitkat based im doing it for the first time i need advice
Have you tried the CandyKat rom? Its very good.. and I dont see it has any problem with sound..
mandarjoshiin said:
Have you tried the CandyKat rom? Its very good.. and I dont see it has any problem with sound..
Click to expand...
Click to collapse
that's odd because skype runs with no problems, but i'm getting speaker/mic problems with regular calls when headphones plugged in, and with CSipSimple app.
Thanks for help anyway.
UvarovG said:
that's odd because skype runs with no problems, but i'm getting speaker/mic problems with regular calls when headphones plugged in, and with CSipSimple app.
Thanks for help anyway.
Click to expand...
Click to collapse
I'm still fighting the in call low-volume mic problem as well. Apparently is not uncommon among other cm11 builds. I have yet to find a rom where its working properly. I tried downloading a few sound recorder apps and they record mic volume just fine - so it appears to be constrained to in call usage.
I also tried modifying an xml doc at the system level, as some had success on the nexus 4 with the same issue, but no luck for me.
I've got a head scratcher that I can't fix. I can't hear anything in calls and the other end can't hear me. My speaker and mic work perfectly in all other applications - I can record video and hear the audio in that, I can make and receive calls in Skype and Viber and the speaker and mic work flawlessly in both but the standard phone just doesn't work. I hear the rising been after dialling and then nothing - I can't hear it ringing and can't hear anything once it is answere and the other end don't hear me.
Phone was totally stock (not even rooted) when this first happened and I figured I'd fix it through a new rom so I rooted and first one I tried was an old familiar ARHD (I'd used the equivalent on my last phone) and it was odd as I think that seemed to fix it for the first test call and then stopped again. This seemed to be an oddity as no other rom I've tried even worked once.
I figured something Samsung was still updating after the install and causing the problem so next I tried Cyanogen 11 - didn't work even once. Tried Cyanogen 10.1.3, same thing. Just tried the AOSB rom and still the same thing...
Really not sure what to do now - any ideas?
Thanks,
DF
Hi,
Custom ROMs can be difficult and might be a source of the issue itself. Since your issue was present before installing the custom ROM, we might be able to assist. Please open a support ticket at this link: http://bit.ly/1aOwGy2 and a support agent will be in touch.
dannyfranks76 said:
I've got a head scratcher that I can't fix. I can't hear anything in calls and the other end can't hear me. My speaker and mic work perfectly in all other applications - I can record video and hear the audio in that, I can make and receive calls in Skype and Viber and the speaker and mic work flawlessly in both but the standard phone just doesn't work. I hear the rising been after dialling and then nothing - I can't hear it ringing and can't hear anything once it is answere and the other end don't hear me.
Phone was totally stock (not even rooted) when this first happened and I figured I'd fix it through a new rom so I rooted and first one I tried was an old familiar ARHD (I'd used the equivalent on my last phone) and it was odd as I think that seemed to fix it for the first test call and then stopped again. This seemed to be an oddity as no other rom I've tried even worked once.
I figured something Samsung was still updating after the install and causing the problem so next I tried Cyanogen 11 - didn't work even once. Tried Cyanogen 10.1.3, same thing. Just tried the AOSB rom and still the same thing...
Really not sure what to do now - any ideas?
Thanks,
DF
Click to expand...
Click to collapse
Viber Team said:
Hi,
Custom ROMs can be difficult and might be a source of the issue itself. Since your issue was present before installing the custom ROM, we might be able to assist. Please open a support ticket at this link: http://bit.ly/1aOwGy2 and a support agent will be in touch.
Click to expand...
Click to collapse
Hi,
Thanks for the offer of help but Viber actually works perfectly - it's just the built in phone that stopped working. Unfortunately GiffGaff don't seem to support Viber In for all calls otherwise I would just enable that and not worry about the normal phone not working...
Thanks,
DF