First off, I'm not an active GNex forum viewer, I use a Galaxy S2S and rarely venture outside of it (except when I was on my HTC Bravo/Desire), I am asking to help a buddy.
I updated his GNex (Maguro) to Google's official Jelly Bean (4.1.1 Deodexed rooted) and he seems to have an issue with low in-call volume. It's rooted, CWM, and all that, using the GNex Tool. Everything works fine except the in-call volume, some calls would be fine, some would be extremely low. I was thinking it's a radio issue OR maybe just an issue with his provider (Mobilicity). He hadn't used the phone prior to upgrading to JB (was on stock ICS) so there was nothing to compare to.
Does anyone know what the problem could be or possible know a fix for it? I've done my homework and I found nothing that relates to this, mostly issues with the speaker.
Thanks in advance.
PS: Is there any modified radios (only) that would work with JB and Maguro?
Related
Hi
I have a HTC Desire and a blueparrot bluetooth headset.
Have tried a few different mods and currently running latest cyanogenmod 7 stable version.
The volume of the microphone is VERY low, so quiet that some people cannot even hear me. If I change to phone mic or speakerphone volume is absolutely fine for them.
Also if I am trying to use the bluetooth headset for voice commands, it is very lucky to get anything correct, no doubt because the volume is so low.
The headset has been tried on other (non Android) devices and works fine. I am pretty sure it is something to do with the Android OS.
I also do not recall having this problem with the stock HTC image that was on the phone, although I only know its a problem if people complain.
I notice that there is a kernel patch for HD2 versions (which I guess mine could not support being a revision 1 desire) that provides for /proc/miclevel control.
Is there any way that I can fix this? Or any roms and kernels that may have this fixed?
I also require the call recording patch in the kernel to be able to record calls without using the speakerphone, so if anyone can incorporate that into suggestions if possible too please?
Thanks for your help.
Regards
Andy
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Using AOSP JellyBean, CM10, and MIUI 4.1, I have experienced an issue where the audio coming through the speakers in the phone is either at max volume (no matter what volume setting I have), or completely silent (turned off).
Is this a known issue with JellyBean on the E4GT (Seen across three separate ROMs), or is this a hardware defect in my device?
Any help is appreciated.
Link3737 said:
Using AOSP JellyBean, CM10, and MIUI 4.1, I have experienced an issue where the audio coming through the speakers in the phone is either at max volume (no matter what volume setting I have), or completely silent (turned off).
Is this a known issue with JellyBean on the E4GT (Seen across three separate ROMs), or is this a hardware defect in my device?
Any help is appreciated.
Click to expand...
Click to collapse
Yes it know to all jelly bean roms .. I use a app from the play store and everything is perfect.. search volume booster or something like that..good luck
Sent from my hand
Hi guys,
In stock Jelly bean touchwiz rom, google plus hangout was working just fine, but when I switched to MIUI or Milestone CM10 Stable, Google plus hangout volume is really low. Others can hear me fine, but I can barely them (can hear very very quietly). And I searched online, and many people have this issue with other devices. But it wasn't evident for me when I was using touchwiz rom. And others who use the same phone are using it fine, as they can hear me, and also my nexus 7 borrowed by a family oversea can hear me fine too with the tablet.
I don't want to use the touchwiz rom though..so could someone possibly help me how to get back the full volume using google plus hangout? Of course I increased all possible volume settings to max.
Would really appreciate your help!!!:fingers-crossed:
I have a Sprint Galaxy Nexus (Toroplus) on the stick 4.2.1 ROM, rooted with the Galaxy Nexus ToolKit V11.0.0. Before I was on 4.2.1 nonrooted, and I had to basically blow away my old ROM to get this running.
Anyway, since getting on 4.2.1 rooted, I've noticed the call volume is super loud, loud enough to use as a speakerphone. The volume is as far down as it can go, which is almost at the far left side of the slider but not all the way (don't remember if this is how it behaved previously). Adjusting the volume louder actually doesn't seem to make it louder.
Do any of you have ideas as to what has caused this, and how to remedy it? Thank you!
Edit: After several reboots this seems to have cleared up on its own. If I encounter this again or find out anything else I'll update this thread.
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!