I'm using CarbonRom is both HD and HD+ and this problem is the same for both. Today, I made a phone call and the person wasn't getting enough volume and the words were garbled. I tried the headset with Google Voice search and VoiceToText in other apps. It is evident that the mic isn't working correctly. I tried a different wired headset and the result was the same. For reference the headsets are a Klipsh S4A and stock that comes with Galaxy S3. The onboard mic works as expected. I paired a Bluetooth headset and, surprisingly, that worked the best of all.
Sometimes this is a kernel issue. I reflashed the rom without the fstrim kernel and that made no difference.
I am thinking that this is a bug that may be in the various Android, custom roms and that's why I didn't post only in CarbonRom thread. It may even be a problem with stock. I don't think there are many people that use a wired headset with mic. I make phone calls with MagicJack.
Maybe a few people that have a headset with mic can try and report back if this is a problem for the particular rom they are using.
someone here http://forum.xda-developers.com/showthread.php?t=2388088 mentioned it worked with cm 10.1, maybe that one would work for you
king200 said:
I'm using CarbonRom is both HD and HD+ and this problem is the same for both. Today, I made a phone call and the person wasn't getting enough volume and the words were garbled. I tried the headset with Google Voice search and VoiceToText in other apps. It is evident that the mic isn't working correctly. I tried a different wired headset and the result was the same. For reference the headsets are a Klipsh S4A and stock that comes with Galaxy S3. The onboard mic works as expected. I paired a Bluetooth headset and, surprisingly, that worked the best of all.
Sometimes this is a kernel issue. I reflashed the rom without the fstrim kernel and that made no difference.
I am thinking that this is a bug that may be in the various Android, custom roms and that's why I didn't post only in CarbonRom thread. It may even be a problem with stock. I don't think there are many people that use a wired headset with mic. I make phone calls with MagicJack.
Maybe a few people that have a headset with mic can try and report back if this is a problem for the particular rom they are using.
Click to expand...
Click to collapse
Yes, I can confirm this issue, apparently.
I'll try to see what could be done.
Related
All of the 2.2 based ROMs don't have the headset functionality I'm looking for, and it appears it's a 2.2 issue.
Is anyone still working on 2.1 based ROM's?
Whether it's still under development or not, where can I find a couple of good simple bloatware free 2.1 based ROMs?
I tried searching the development forum, but there's so much about current ROMs (2.2 based) that I can't filter through them and find a 2.1 based ROM.
Thanks, alabamaroping
what headset functionality do you think is broken on all 2.2 roms? those issues have all been resolved unless you have some random new one
I'm looking to have the call output routed through a standard headset connection, NOT the headset that came with the phone that supports mic, and stereo audio out.
A standard headphone connection only has the audio out, no mic. (as I'm sure you know). I'll be listening to music in my truck, and a call will come in and i'll have to unjack the 3.5mm jack and grab the phone instead of the call just routing through the speakers.
I've tried the following: (Cognition 2.3b7, AXURA 2.4, eSPyeL's ROM Beta3.4.1). None of them work.
alabamaroping said:
I'm looking to have the call output routed through a standard headset connection, NOT the headset that came with the phone that supports mic, and stereo audio out.
A standard headphone connection only has the audio out, no mic. (as I'm sure you know). I'll be listening to music in my truck, and a call will come in and i'll have to unjack the 3.5mm jack and grab the phone instead of the call just routing through the speakers.
I've tried the following: (Cognition 2.3b7, AXURA 2.4, eSPyeL's ROM Beta3.4.1). None of them work.
Click to expand...
Click to collapse
AS far as I know no one is still working on 2.1 roms anymore. To tell the truth from all the roms I have have seen the "issue" with the headset without a mic may not be a clitch. I will have to ask a few people that got the 2.2 official update to make sure but I think it was changed on purpose by google. (could be wrong though, will have to wait till I talk to some people)
The car dock allows call output to standard headphones, just got mine yesterday and it works. But, you know it's against the law almost everywhere to wear headphones and drive right?
Captivate Froyo / Perception Build 9 - Cog Kernel 4
Sent via XDA through the ether that is.
no headphones
Actually, I don't drive with headphones. I have a 3.5mm jack run into my truck stereo system. It's the same as a headphone jack, so I just use that as an example.
I've been using headphones to test functionality when sitting in my office, and the jack is the same, so I've been using the two interchangeably.
However, you are correct: it's unsafe to drive with headphones, but I see the iPeople doing it with their iPhones & iPods all the time.
The only 2.1 ROM out there still that should be available is Cognition. Lord knows though I haven't tried to download it... buyer beware.
Might just be easier to keep your "stock" 2.1 - Root it and get an application like Titanium Backup that will uninstall the bloat on your phone.
And.. I thought the issue for 2.2 custom ROMS were due to the use of i9000 modems/kernels? Or was that only Bluetooth?
avgjoegeek said:
And.. I thought the issue for 2.2 custom ROMS were due to the use of i9000 modems/kernels? Or was that only Bluetooth?
Click to expand...
Click to collapse
Also, does the bluetooth issue still exist on the never versions? I haven't used my bluetooth earpiece in along time so I haven't bothered to try on these newer roms.
I believe I have found an issue with the latest (stable + nightlies) cyanogen mod rom with Bluetooth headset audio, and before I go about posting to the Dev thread I wanted to get some help with understanding how or what info a need to gather.
I have a car stereo that has support for Bluetooth (both media and voice), and whilst the phone syncs to the unit and plays music just fine, when trying to place a call, all that can be heard is a loud buzzing when the call is connected (@ both ends).
The stereo is functioning correctly, and works fine for both voice and media with my SGS2 (also running cyanogen). I also have the same model stereo in another car, and the problem manifests on this unit too.
Prior to flashing cyanogen I was using other roms (both standard and mod's) and never had any issues with voice calls.
I have tried changing the baseband, and ril but this had not made any difference. I have also paired with other headsets and they work fine, so this is down to some compatibility issue with the stereo and Cyanogen's Bluetooth stack settings, I think.
Before posting this as a bug, is there anything else I should try, and if not what info do I need to gather (other than version numbers etc) to ensure I give the dev's enough info to work with?
Thanks
If it's in stable, use the issue tracker.
I have a HTC one. Have tried various tons and it seems every time I use my Bluetooth headset the caller on the other end hears screeching and buzzing. Any ideas how this can be fixed or which ROM works best. As well if possible am I able to return to stock ROM without an original nand backup. Thanks
Hi all..
I have a minor problem for most that is important enough for me and keeps me away from all those wonderful custom ROMs..
That is:
The phone is set to "vibrate mode", I stream music through A2DP and it works great until someone calls me. Then the headset notifies about the call and the music I used to listen to is now played back loudly through the phone's speaker. That is very annoying, given that I discovered it when I was in my university's library trollolol.
I tried all versions, CM10.1, AOSP, AOKP and this happens in every single one of them. Only in stock based ROMs everything is working as it should..
This also happens with the apollo player and also with player pro.
Also tried Optimus Prime kernel by demetris_l, still the same.
Lastly, I also tried it with 2 different A2DP bluetooth headsets (Sony Ericsson MW-600 and Scosche tuneStreamII), both act the same.
Any help would be greatly appreciated...
Thanks for your time!
Update.. I managed to work around it by changing the applications I have been using.. Mortplayer works great and doesn't act like that, for instance.
Thing is, why did the apps like PlayerPro and Apollo worked ok and paused music playback during a call on the stock ROM but not on any of the custom ones?
Is it maybe that they can't use the READ_PHONE_STATE permission properly?
Thanks for providing a workaround atleast
thre was a guy saying that this doesnt happen to him, so dont you think it could be your BT headset?
profyler said:
thre was a guy saying that this doesnt happen to him, so dont you think it could be your BT headset?
Click to expand...
Click to collapse
Both of them?
Just acquired one of these phones today and seem to be having a slightly strange issue and hoping someone might know the resolution.
When on a call, the other person cannot hear me at all (they can hear nothing as-if the microphone is muted, it's not!), however if I switch to speakerphone they can hear me fine.
This is happening on any ROM, except unofficial CM10.1 where the microphone does not work at all.
In external apps the mic does not work either (so if I record a video, I get no sound).
I'm having trouble seeing this as a mic hardware issue as it works OK on speakerphone, any ideas on this?
Cheers!
tral1z said:
Just acquired one of these phones today and seem to be having a slightly strange issue and hoping someone might know the resolution.
When on a call, the other person cannot hear me at all (they can hear nothing as-if the microphone is muted, it's not!), however if I switch to speakerphone they can hear me fine.
This is happening on any ROM, except unofficial CM10.1 where the microphone does not work at all.
In external apps the mic does not work either (so if I record a video, I get no sound).
I'm having trouble seeing this as a mic hardware issue as it works OK on speakerphone, any ideas on this?
Cheers!
Click to expand...
Click to collapse
Does this happen on stock rom as well?
Yeah I've put it back to the Samsung firmware (Carphone Warehouse UK, 2.3.6) and still doing the same thing.
Interestingly, on stock-based ROMs the Mic works on speakerphone (Still nothing anywhere else), but on CM-based or ported ROMs, the mic does not work at all!
Just to confirm, the Galaxy Mini does have just a single mic right? Haha!