Related
This has been happening on my Epic 4G for awhile now and it's really frustrating. I'm pretty sure this hasn't been happening the whole time I've owned the phone, but at this point it's hard to really remmber.
Basically, when I make or receive a call, within a couple\few minutes of the phone call the caller suddenly can't hear me - this happens whether it's using the phone normally, in speakerphone mode, or even a headset. As soon as it happens and the other caller starts the "Hello? Are you still there?" I can fix it by toggling the speaker on and off (or off and on) and it fixes it - but it can suddenly start again at anytime...couple of minutes later, five minutes later, etc.
Right now I'm slowly removing apps from my phone after every call this happens on - my goal is to determine if a particualr app is confusing my phone. I don't think it's the ROM or modem I'm using (Frozen 1.2, EC05) as I did a stock flash and flashed to those just recently and others aren't having the same problem. I DID restore some data so if I can't narrow down an app that's causing it, not restoring any data is my next option (but even more time consuming to figure out specifically which data is causing issues).
I'm pretty sure the phone hasn't always done this so I don't want to exchange the phone considering I don't have any other issues and I think this is software, not hardware related. Has anyone experienced anything similar to this?
Have you tried switching Roms, I have this same problem on EC05 when I moved to gingerbread it stopped happening.......
Do you voodoo installed?
Sent from my SPH-D700 using XDA App
I was having the same problem with EF02 and the EF02/EF10 modems. I switched back to the EC05 modem and haven't had the problem since (knocking on wood)...
Sent from my Transformer TF101 using Tapatalk
Try ee03 modem..
Sent from my SPH-D700 using Tapatalk
masaidjet said:
Have you tried switching Roms, I have this same problem on EC05 when I moved to gingerbread it stopped happening.......
Do you voodoo installed?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I do have Voodoo installed (since it comes with Frozen 1.2). I haven't tried switching ROMs yet but I have started looking again (I was pretty content with Frozen but if no one had a similar issue and changing the modem doesn't work then a ROM switch is my next try).
Thanks to others who suggested changing modems - I'm going to do that now and see if EE03 fixes this....*crosses fingers*
evancg said:
I do have Voodoo installed (since it comes with Frozen 1.2). I haven't tried switching ROMs yet but I have started looking again (I was pretty content with Frozen but if no one had a similar issue and changing the modem doesn't work then a ROM switch is my next try).
Thanks to others who suggested changing modems - I'm going to do that now and see if EE03 fixes this....*crosses fingers*
Click to expand...
Click to collapse
Go into you Voodoo sound settings and change recording setting to Original. Shoul fix your issue.
Sent from my SPH-D700 using XDA App
Sure you are not hitting the mute button by accident? Sounds dumb but I've done that before.
Blankrubber said:
Go into you Voodoo sound settings and change recording setting to Original. Shoul fix your issue.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I have the SAME EXACT PROBLEM and just like the OP it hasn't always been like that, did this work for you?
Sent from my rooted, suited, & booted Epic 4G kno dat!
I was having the same issues so I just applied this. People couldn't hear me on speakerphone at all...seriously. hopefully this helps. Thanks for the tip
Sent from my SPH-D700 using XDA App
evancg said:
Basically, when I make or receive a call, within a couple\few minutes of the phone call the caller suddenly can't hear me - this happens whether it's using the phone normally, in speakerphone mode, or even a headset. As soon as it happens and the other caller starts the "Hello? Are you still there?" I can fix it by toggling the speaker on and off (or off and on) and it fixes it - but it can suddenly start again at anytime...couple of minutes later, five minutes later, etc.
Click to expand...
Click to collapse
Yes! Mine started doing this a couple months ago, and I resolve it exactly the same way (though I have to hit the volume button once, either up or down, then toggle speaker on then off). It's definitely not the ROM because I've had it with both Froyo and GB ROMs. Unfortunately, I haven't found any other solution, yet. I'm hoping it will go away with official GB, but I have no real reason to think it will work. I'm going to play around with the Voodoo sound.
edonnelly said:
Yes! Mine started doing this a couple months ago, and I resolve it exactly the same way (though I have to hit the volume button once, either up or down, then toggle speaker on then off). It's definitely not the ROM because I've had it with both Froyo and GB ROMs. Unfortunately, I haven't found any other solution, yet. I'm hoping it will go away with official GB, but I have no real reason to think it will work. I'm going to play around with the Voodoo sound.
Click to expand...
Click to collapse
you guys shouldn't be having this problem make a backup then odin to ec05 stock and check if you still have the issue if you do just take it to sprint and show the tech your problem they should fix it or get you a replacement phone.
I have the same issue. I am completely stock. It usually happens 10 to 15 minutes into a phone call. I've already called sprint, taken it to a store but only reflashed the os, and I just recently spoke to someone on chat, who said the problem has been solved. If it happens again should I get a replacement phone?
Blankrubbers fix actually worked for me
Sent from my SPH-D700 using XDA App
steviee7 said:
you guys shouldn't be having this problem make a backup then odin to ec05 stock and check if you still have the issue if you do just take it to sprint and show the tech your problem they should fix it or get you a replacement phone.
Click to expand...
Click to collapse
I had this problem as well. I odinned stock and problem solved. Now I'm back on bonsai with no problems.
Edit: I just noticed that I don't have voodoo sound installed, I know that I used to, maybe deleting that solved my problem and not odinning back to stock.
Sent from my SPH-D700 using Tapatalk
evancg said:
This has been happening on my Epic 4G for awhile now and it's really frustrating. I'm pretty sure this hasn't been happening the whole time I've owned the phone, but at this point it's hard to really remmber.
Basically, when I make or receive a call, within a couple\few minutes of the phone call the caller suddenly can't hear me - this happens whether it's using the phone normally, in speakerphone mode, or even a headset. As soon as it happens and the other caller starts the "Hello? Are you still there?" I can fix it by toggling the speaker on and off (or off and on) and it fixes it - but it can suddenly start again at anytime...couple of minutes later, five minutes later, etc.
Right now I'm slowly removing apps from my phone after every call this happens on - my goal is to determine if a particualr app is confusing my phone. I don't think it's the ROM or modem I'm using (Frozen 1.2, EC05) as I did a stock flash and flashed to those just recently and others aren't having the same problem. I DID restore some data so if I can't narrow down an app that's causing it, not restoring any data is my next option (but even more time consuming to figure out specifically which data is causing issues).
I'm pretty sure the phone hasn't always done this so I don't want to exchange the phone considering I don't have any other issues and I think this is software, not hardware related. Has anyone experienced anything similar to this?
Click to expand...
Click to collapse
speak up i can't hear you
Sadly even after changing modems and making the adjustment in Voodoo Control I still have the same problem. Going to uninstall Voodoo all together and see if that resolves anything.
I just discovered that I'm having the same problem after I Odin'd back to stock EC05 for a different reason. So, EC05 and EC05 modem, and I'm having a problem that I didn't think I was having before I tried EF02.
Could something have been changed that going back to EC05/EC05 modem didn't resolve?
Sent from my Transformer TF101 using Tapatalk
evancg said:
Sadly even after changing modems and making the adjustment in Voodoo Control I still have the same problem. Going to uninstall Voodoo all together and see if that resolves anything.
Click to expand...
Click to collapse
This problem is not generated by Voodoo. I have a stock Epic (rooted) and have never had Voodoo installed on my device and I have intermittently had this problem in the past (haven't seen it for a while, though). My friend has an Epic (never rooted) and also has this problem.
About the only thing I've heard that people have said fixes this is to wipe cache and dalvik and then flash something using Odin. Stock or custom I don't think matters.
As others have noted, uninstalling Voodoo didn't fix it for me. I think what must be causing this is everytime I wipe and install a clean ROM I restore some data through TiBackup and SOMETHING I'm restoring is causing this. Guess I'll just have to wipe and be very careful about what I'm restoring.
This might be completely random, but by chance did other people that experience this problem happen to install NZBAir?
My led isn't flashing when I receive a text, it stays on solid with a quick off then back on for a split second, every so often. It happens kind of randomly. Anybody else have this problem or find a fix? I'm running starburst 1.9 with the lost kernel. I've tried more than one rom and. Kernel and I still have the issue even after factory wiping. Any help is greatly appreciated..
Sent from my SPH-D710 using xda premium
no issues here. running viper 2.2
no issue here either viper 2.2 also. You can try no led from the market.
Thanks for the feedback guys... Seems like such a simple fix but I just can't figure it out..
Sent from my SPH-D710 using xda premium
Not to resurrect this thread (well, yes actually.. that is my intent )
But I seem to be having the same issues. The LED only seems to work when I'm charging the unit. It doesn't work for any other type of notification.
I'm running Calkulin's FC18 ROM. However, it hasn't really worked before then as well. I'm not sure if it worked with the stock ROM when I first bought it as I didn't have the stock ROM on it but for maybe 30 mins after I bought the phone .
Any ideas?
cshoffie said:
Not to resurrect this thread (well, yes actually.. that is my intent )
But I seem to be having the same issues. The LED only seems to work when I'm charging the unit. It doesn't work for any other type of notification.
I'm running Calkulin's FC18 ROM. However, it hasn't really worked before then as well. I'm not sure if it worked with the stock ROM when I first bought it as I didn't have the stock ROM on it but for maybe 30 mins after I bought the phone .
Any ideas?
Click to expand...
Click to collapse
Pretty sure it's an ICS problem with FC18 in general because tons of people are getting it. Try upgrading to FC22 (not sure if its been fixrd) or just wait
Edit: Ignore what I said, since you said the LED ONLY works when it's charging. For me, the LED works only when it isn't charging .
Sent from my SPH-D710 using XDA
Hey everyone,
Just flashed the newest CM7 RC2 and the in-call volume (from the earpiece) is just way too loud, even at the lowest volume setting. Not sure if it's something with this ROM (I've tried a bunch of the TW varieties and don't remember noticing it) or maybe just my phone?
Any advice or suggestions?
Thanks,
Do u use voodoo sound? And you mean bluetooth right? Or headphones..?
Sent from my SPH-D700 using XDA App
I tried installing voodoo but the CM7 kernel doesn't support it (or viceversa).
And bluetooth is fine, I'm having a problem with the earpiece on the phone itself. Just noticed it on a call today when my bluetooth died.
Same Issue
I am having the same issue with in call volume. Has anyone found a solution? Have reflashed onto the most recent nightly 06/03 of CM7 and have even done a factory reset with no change. Love this ROM as I can get almost 2 days of battery life with it, but the call volume is making my ears bleed.
trent1w said:
I am having the same issue with in call volume. Has anyone found a solution? Have reflashed onto the most recent nightly 06/03 of CM7 and have even done a factory reset with no change. Love this ROM as I can get almost 2 days of battery life with it, but the call volume is making my ears bleed.
Click to expand...
Click to collapse
Not sure if the new nightlies have the fix but according to the change log RC3 had the fix.
http://cm-7-nightlies.appspot.com/?device=epicmtd
http://forum.cyanogenmod.com/forum-545/announcement-23-cyanogenmod-72-rc3-released-2012-may-26/
Running the latest nightly, still same issue. Am I missing anything? I have wiped all and started over hoping that might solve it, but no change.
trent1w said:
Running the latest nightly, still same issue. Am I missing anything? I have wiped all and started over hoping that might solve it, but no change.
Click to expand...
Click to collapse
just try rc3 then you will know if they fixed it or not. my understanding is the nightly might not have the rc3 kernel. not sure how to tell.
tazfanatic said:
Not sure if the new nightlies have the fix but according to the change log RC3 had the fix.
http://cm-7-nightlies.appspot.com/?device=epicmtd
It didn't.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Click to expand...
Click to collapse
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
wbexpress said:
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
Click to expand...
Click to collapse
it turns on with pac 20.0 not sure if it stays on though. I'm on the latest twrp. full wiped, adsk and nos script. give that a try?
wbexpress said:
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
Click to expand...
Click to collapse
I works on the 2/26/13 Nightly of CM10.1. You wanna try and clean flash it? If it doesn't work then it's just a problem with your phone hardware instead of the software. Might be a buddy bluetooth adapter or such.
zxstyle07 said:
it turns on with pac 20.0 not sure if it stays on though. I'm on the latest twrp. full wiped, adsk and nos script. give that a try?
Click to expand...
Click to collapse
Fingers crossed, so far so good. I reinstalled Rootbox which is awesome. I changed from CWM back to TWRP and also installed Cerux 1.42 which in the thread made mention of the bluetooth issue being fixed, and being kernel, not ROM related. I am using crossbreeder which makes things crazy fast. I saw the "nos script" in some thread but couldn't find it with a Google search. Do you have a link for it and what exactly does it do?
Edit: Crap. it went away. Oh well, back to 4.1. Hellybean it is. I just don't get it. BT works fine on any 4.1 or ICS ROM. Only thing with 4.1 is music skips in my music player but I can live with that, I can't live with no BT. Thanks for your help. Maybe when source drops it will be all good.
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
joeyrey said:
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Yup, this helped for my JB-MR build 4!
no more having to reboot to enable bluetooth
wbexpress said:
Fingers crossed, so far so good. I reinstalled Rootbox which is awesome. I changed from CWM back to TWRP and also installed Cerux 1.42 which in the thread made mention of the bluetooth issue being fixed, and being kernel, not ROM related. I am using crossbreeder which makes things crazy fast. I saw the "nos script" in some thread but couldn't find it with a Google search. Do you have a link for it and what exactly does it do?
Edit: Crap. it went away. Oh well, back to 4.1. Hellybean it is. I just don't get it. BT works fine on any 4.1 or ICS ROM. Only thing with 4.1 is music skips in my music player but I can live with that, I can't live with no BT. Thanks for your help. Maybe when source drops it will be all good.
Click to expand...
Click to collapse
http:// http://forum.xda-developers.com/showthread.php?t=2158329
joeyrey said:
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Well, what seems to happen is it is fine for 15-30 minutes after I've freshly installed the ROM, then it just turns off. When I then try to turn it back on it hangs at "turning on" and then goes back to off. At that point when I click "turn on", it doesn't even move. I'm a gonna try the fix, nothing to lose at this point...
Nuts. It fast moves to on and immediately goes back to off. White flag, thanks to all.
Apply the fix and delete all you devices then try turning it on and off with nothing on it...if it works then add devices one by one...if you have devices married to it the patch might not work also I think my computer dongle was the culprit
Sent from my SAMSUNG-SGH-T989 using xda premium
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
djtheraven said:
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yeah, how about that. I can't see that it's hardware-related, it's perfect on 4.1.
wbexpress said:
Yeah, how about that. I can't see that it's hardware-related, it's perfect on 4.1.
Click to expand...
Click to collapse
Your exactly right...
Sent from my SAMSUNG-SGH-T989 using xda premium
djtheraven said:
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
If you ever figure it out, please put something here. I keep looking every so often, I have to believe enough folks are having the issue that eventually someone is gonna fix it. Thanks...
wbexpress said:
If you ever figure it out, please put something here. I keep looking every so often, I have to believe enough folks are having the issue that eventually someone is gonna fix it. Thanks...
Click to expand...
Click to collapse
I'm posting to a couple of devs hope they can get it...the problem was people were commenting that it worked when they had no Bluetooth device hooked up...if you uninstall all devices then bt will toggle on and off...so they thought it was working when it wasn't...
Sent from my SAMSUNG-SGH-T989 using xda premium
bluetooth issues
djtheraven said:
I'm posting to a couple of devs hope they can get it...the problem was people were commenting that it worked when they had no Bluetooth device hooked up...if you uninstall all devices then bt will toggle on and off...so they thought it was working when it wasn't...
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Has anyone had any luck with this? I've tried various combinations of different 4.2.2 roms and kernels and have the same issues described in this thread with all of them.
Not a perfect answer...
RandyToe said:
Has anyone had any luck with this? I've tried various combinations of different 4.2.2 roms and kernels and have the same issues described in this thread with all of them.
Click to expand...
Click to collapse
I found one thing that at least gets it working again without rebooting is to activate airplane mode. Its faster than rebooting. Wish I had a better answer...
I've been ignoring custom roms for about 6 months after I tried one previously and found the bluetooth bug. Just curious if this has found a fix at this point? I'd love to run a CM10.1 rom, but bluetooth audio is a must have for me.
cegna09 said:
I've been ignoring custom roms for about 6 months after I tried one previously and found the bluetooth bug. Just curious if this has found a fix at this point? I'd love to run a CM10.1 rom, but bluetooth audio is a must have for me.
Click to expand...
Click to collapse
the issues from 6 months ago have been gone for sometime now.
fantastic, thank you.
Life's been pretty crazy so i'm out of the loop on where everything has progressed. Once i get AT&T to warranty my phone for the GPS issues i'm having i'll try out one of the new builds.
Bluetooth audio has been working fine
But from my experience there have been problems with Bluetooth dialing.
A recent update of slimbean (version 6) seems to have corrected the problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I don't know that the issue really is fixed in 4.2.2. Doesn't seem to matter what ROM I run (I've tried CM, Carbon, AOKP), I can't get Bluetooth to work at all. It won't scan/find any of my devices or even turn on. I've resorted going back to stock rooted.
Has anyone found a work around or fix?
If bluetooth worked, it wont be 4.2.2. Best to go back to 4.1.x.
Sent from my SAMSUNG-SGH-I747 using xda premium
kt314 said:
I don't know that the issue really is fixed in 4.2.2. Doesn't seem to matter what ROM I run (I've tried CM, Carbon, AOKP), I can't get Bluetooth to work at all. It won't scan/find any of my devices or even turn on. I've resorted going back to stock rooted.
Has anyone found a work around or fix?
Click to expand...
Click to collapse
once in the past, when the CM roms were having bluetooth problems, I tried a different kernel and that fixed issues. The BMS Kernel is pretty stable and great performance/battery. you might give that a try.