I am having a Phone Audio issue. I am using PPCKitchen ROM 19588/Radio 3.42.30
After a soft-reset, the phone works fine & calls are okay. After a few hours, sometimes as long as 2 days later, the No-Audio issue repeats.
No audio is passed in or out during a phone conversation.
So if someone calls me, the phone rings, but when I answer, no audio is heard on either end. The same goes with Outgoing calls. I tried Speakerphone and the same issue is there.
I'm thinking its a Radio issue rather than ROM issue. Can I use another Radio without having to-flash the ROM?
Any suggestions?
Thanks
It's not a radio issue. No one using 3.42.30 has seen this issue. It's either the rom, or defective hardware.
Related
Newbie question.
I've successfully connected a Moto hs850 BT headset to my O2 XDA 2s. Problem is, I can make outgoing calls no problem but when others call my phone, neither the XDA 2s nor the headset rings... the caller goes straight through to my voicemail.
Phone works fine when the bluetooth is off.
I must be missing something. Consulted the manual and trawled this site but cannot find the answer.
Any help out there?
ROM 1.12.62 WWE
Radio 1.02.00
Protocol 1337.32
ExtROM 1.12.178 WWE
What version of BT Manager are you running? i think 3900 is the latest and can be found here. Also the Radio Rom 1.02 is pretty old as well; I would upgrade to the latest BT manager and go from there.
Moto HS850
Thanks for that.
I've upgraded the radio to 1.13 and the BT to 3900. Now I can call out and receive calls no problem except for one MAJOR pain in the ass...
When the device goes into standby mode, a received call will not wake up the device and reconnect the BT headset in time to answer the call - I have to answer it via the device green button. I've looked through the forum and found that a few people have had this problem. I realise that not going into standby mode burns up the battery more quickly but I'm hoping for a way to get a compromise... i.e. standby for the screen and the processor, but bluetooth and the headset connection still active.
I've yet to upgrade my ROM to 1.31 (from O2 UK/IRL) or 1.40 if I figure out how to rejig the iMate ROM for my XDA. Has anyone had any experience of a ROM upgrade helping (or worsening!) this problem.
Better yet - anyone have a workaround?
Your advice is much appreciated...
Hi all
Am I the only one experiencing microfone problems on my new galaxy S3?? Im on my third I9300, because of this issue...
People complaining about that the mic vol goes up and down...
I'm also facing similar issues. I'm going to get mine replaced also.
First of all guys make sure 100% it's not the mic. Record some song and see if you still have the problem. I was facing similar issues with the mic going up and down durring calls.
In my case it was the simcard. Don't ask me why, because the same simcard was working fine in another phone, but after getting a replacement everybody said that they can hear me a whole lot better.
mikesoftwiz said:
First of all guys make sure 100% it's not the mic. Record some song and see if you still have the problem. I was facing similar issues with the mic going up and down durring calls.
In my case it was the simcard. Don't ask me why, because the same simcard was working fine in another phone, but after getting a replacement everybody said that they can hear me a whole lot better.
Click to expand...
Click to collapse
I am going through the very same issues.
I had a mic problem with my first S3 during phone calls. It was really annoying me because I couldn't do anything about it everyone was saying they couldn't hear me etc.
The sim I am using is an British UK O2 micro simcard that I used in a iphone 4, cheap samsung, and samsung S2 previously with no problems at all.
I then returned the phone to the T-mobile shop retailers, they said it was rare and not a common fault.
My new one is doing the exact same thing, I didn't update it nor is there a new update.
Can someone please help. Thank you.
I am getting the same issue but not everytime. I am sure that it is not the fault in mic that is causing this problem, as i recorded my voice (using both mics, the one at the top and at the bottom) and it was crytal clear.
turn off Noise Cancelling... fixed my problems
same problem
Had the same issue ,also with the s 2 , but the trick then (witch also worked now ) was to turn off the noise cancellation .
During a call just take the phone away from your ear and under the callers picture there u will find the option to do so
I have literally just started having the same issue today.
Am on FoxHound Rom 1.4 with Siyah Kernel. Had no problems, even made calls last night, perfect.
Then I tried switching Fast Dormancy on, flashed stock kernel and this morning I find when I made calls to Orange customer services, they were saying they couldn't hear me.
Tried testing it myself, and no matter who I call no-one can hear me.
I've tried:
re-flashing rom, kernel
Tried latest stock roms such as I9300XXBLG8_I9300OXABLG8_I9300XXLG8_HOME.tar.md5, none have made a difference. Even Roms I had backed up in clockworkmod that were working perfectly, like CM10 preview and CM9 have stopped working.
I've tried disabling Noise reduction, which has had no effect. Tried factory reset, flashing modems, kernels, roms, stock roms, nothing has made a difference. I can record video, google talk, anything else fine, just not get anything from the mic when making phone calls.
Tried putting a friends 3 SIM in, and the same thing, so it's definitely not network related either. I definately hope it isn't a hardware fault, as I bought mine on ebay and it isn't insured. Was kinda hoping for more than 2 mores usage out of a phone :crying:
HI all,
I can't post in the Dev section yet so I will ask here. I installed this ROM last night and it all went well except for today in the car while testing bluetooth I have no audio unless I switch the source away from Bluetooth and back (say, set it to Speaker then back to BT). I did a full wipe again and re-loaded the ROM and still have the same problem. I am using the .19 radio if that makes a difference and my car has the older (2008) Ford Sync system (2.1).
Is anyone else having a similar issue?
rpoitras said:
HI all,
I can't post in the Dev section yet so I will ask here. I installed this ROM last night and it all went well except for today in the car while testing bluetooth I have no audio unless I switch the source away from Bluetooth and back (say, set it to Speaker then back to BT). I did a full wipe again and re-loaded the ROM and still have the same problem. I am using the .19 radio if that makes a difference and my car has the older (2008) Ford Sync system (2.1).
Is anyone else having a similar issue?
Click to expand...
Click to collapse
This seems to happen quite a bit. It's a semi known issue from a number of cusom ROMs. Have never seen a solid fix for it except what you just described. Some people have this problem and need to competely turn it off and back on to get it to work! If it truely is a dealbreaker for you (it shouldn't be...not that big of a glitch), best bet is to stick to a ROM closer to the original tbolt software.
Its not that its a dealbreaker but it kind of defeats the purpose of using handsfree in the car when I would have to pick the phone up and switch BT inputs to get it working. I had a low Bluetooth volume problem with a rom before which was fixed with, I think, a different radio but I never had this one before. I noticed someone else posted the problem in the official thread so hopefully comes out if it. Thanks.
So this happens every time u get a call, or only every time you connect to the car?
I haven't received any calls yet while connected to BT but it happened when making calls and it seems once I do the toggle to get things working then it "sticks" and works thereafter. I haven't tried reconnecting while in the car to see if the fix would stick afterwards but this morning when I got into my car I tried making a call and it worked great first time and I know I rebooted the phone multiple times last night with doing backups of the rom, etc. Maybe it somehow worked itself out or maybe it's just an intermittent thing. I didn't change anything since the install.
***** started working again after 2 hours... *****
So this happened once before back in November, started working again the after a day or two but wasn't a huge issue as was on holiday so not making calls anyway. It's just happened now, but I need to use my phone. It's not a hardware issue as they can hear me fine and my speakers are working fine as I'm listening to music and it's working in other apps. Any ideas? When I make a call I get the little beep to say the call is initialised, but never hear the ringing or them talking when they answer, I also get the beep when the call is ended. Already tried cache wipe/restart.
I've read every thread I could find on google and most just say either heat up the sound chip (lose connection), or send to Samsung, which is fine if it's a hardware issue but mine isn't.
I'd prefer not to factory reset tbh. Any idea of a fix? AS it's done it before and sorted itself there must be a way to do something?
And not working again?
Did u try flashing latest boeffla kernel. Someone solved in this way
sent from Neatrom'd i9300
My phone has root, S-off, and I just updated it with the latest radio from Captain_Throwback (3.17.651.4). Right after doing that I flashed a new rom. I don't do many phone calls but after a couple days I realized people could hardly hear me. I restored the backup I had done before switching roms but I have the same issue there now. I'm guessing the problem came up from the radio update. If I yell the mic picks it up and passes it along. If I turn on speaker phone or plug in headphones the mic works perfect. Any idea on this one?
*I figured out this is the noise cancellation feature not working correctly. I blocked off the mic at the top and it works just fine. I thought it was strange that it was feeding my voice back to me, that's why. Any thoughts on disabling the noise cancellation? I took a quick look but didn't see any help.
**Got tired of waiting for help so I ran the 4.3 RUU. Working just fine now.