Hello thanks for reading. I update my Epic to the DK28 2.2.1 on 12/15 and have had a bunch of glitches since (eg. long home screen loads and missing widgets) But a couple days ago I lost all sound from the internal speaker! I can connect something to the headphone jack and hear everything perfectly but as soon as I disconnect... nothing. I have tried so far: wiping all data via recovery mode and all cache, installing audio controller apps but nothing seems to help. No sounds whatsoever even the sprint animation on boot makes no sound. Any ideas? Do you think flashing a custom rom might help?
Re: No Sounds Epic DK28
Sounds more like a hardware problem. Do you use headphones on the phone? I've had a problem on an old LG Chocolate 3 that did the same thing. I had to disassemble the phone and bend a contact point back out. Seems when I unplugged a set of headphones they contact was stuck to the terminal and bent it causing a short.
Try downgrading back to DI19 and seeing what happens. If the audio works again, then you've got a software problem. If it doesn't, you've got a hardware problem.
sauron0101 said:
Try downgrading back to DI19 and seeing what happens. If the audio works again, then you've got a software problem. If it doesn't, you've got a hardware problem.
Click to expand...
Click to collapse
DI18 !
10ch
I did not see any specific mention of the issue I am facing, so I am starting this thread, hoping that folks with this issue would provide their input here and probably we will be able to solve it, if it has not been solved already.
After installing the EB13 update.zip from Samsung, I have noticed the following issues with the sound:
- The maximum volume is less louder than what it was on DI18 (some have reported this issue).
- Sound playing at 70% (rough estimate) or above loses fidelity coming out of the speaker of the phone, which is quite frustrating and disappointing, especially when the issue did not exist on Eclair (DI18).
I have tried flashing twice, although, am not sure if this issue was present the first time. If anyone has found a solution to this problem, please share it, as I do not want to reflash and customize everything yet again. After all, an update should not require two or three flashes to get things right.
Did you flash back to DI18 or just reflash 13? If you flashed back to 18 was it 'resolved'? Did you wipe it completely each time?
NoSoMo said:
Did you flash back to DI18 or just reflash 13? If you flashed back to 18 was it 'resolved'? Did you wipe it completely each time?
Click to expand...
Click to collapse
I had flashed my phone back to DI18 and wiped everything in terms of data and cache on the phone six times.
I have noticed that volume is lot lower as well.
Sent from my Epic 4g Runnin Froyo...rooted for my pleasure!!
Is it possible to go back to pure DI18 Stock ROM, without the ODIN method as I want to rule out the possibility that the issues people are facing could be due to the method of updating? Basically, how do I go back to the state my phone came with without using any of the hack/mod tools?
Sent from my SPH-D700 using XDA App
I've tried pretty much every Froyo ROM that's been released, stock and custom, and have yet to find one that doesn't have Bluetooth issues. It seems to me that the "added Bluetooth functionality" of Froyo has caused problems that have yet to be isolated.
I didn't have any connection issues with any Eclair. It sucks, because I keep bouncing back and forth when a new Froyo ROM is released hoping I won't have these same problems. But I always do!
By the way, the problems are with my hands-free system in my car-- where it will not reconnected without turning on and off Bluetooth. It will also lose it's pairing information, and need to be re-paired on occasion. My wife's Incredible has zero problems in the same car; as does the Epic when it's running Eclair.
The reason I'm hoping for a Froyo release that doesn't have Bluetooth issues is because I do like some of the issues Froyo offers, but having working Bluetooth is more important.
I've had that issue before but SFR 1.1.0 w/ Vision kernel has been flawless for me. I've been running both since the first day of release.
My issue with bluetooth is that unless I hang up with the special 'hang up' button on my dash panel (the other party hangs up first, or the call drops, or etc) then my car thinks it is still on a call and won't release the audio back to music.
The new bonsai rom doesn't seem to have the problem. If you are having the problem then wipe data in cwm. Sometimes you have a corrupt data carryover
Sent From My Evo Killer!!!
JRider said:
I've tried pretty much every Froyo ROM that's been released, stock and custom, and have yet to find one that doesn't have Bluetooth issues. It seems to me that the "added Bluetooth functionality" of Froyo has caused problems that have yet to be isolated.
I didn't have any connection issues with any Eclair. It sucks, because I keep bouncing back and forth when a new Froyo ROM is released hoping I won't have these same problems. But I always do!
By the way, the problems are with my hands-free system in my car-- where it will not reconnected without turning on and off Bluetooth. It will also lose it's pairing information, and need to be re-paired on occasion. My wife's Incredible has zero problems in the same car; as does the Epic when it's running Eclair.
The reason I'm hoping for a Froyo release that doesn't have Bluetooth issues is because I do like some of the issues Froyo offers, but having working Bluetooth is more important.
Click to expand...
Click to collapse
None of the Bluetooth issues currently present in EC05 are ROM related. The problem you are describing occurs usually after ext4 conversion or switching from one ROM to another. I haven't heard anyone report this type of issue that is running stock EC05.
I posted a solution in that has helped several folks and myself who were experiencing similar issues. Try this and let me know how it goes.
http://forum.xda-developers.com/showpost.php?p=12120496&postcount=1392
musclehead84 said:
The new bonsai rom doesn't seem to have the problem. If you are having the problem then wipe data in cwm. Sometimes you have a corrupt data carryover
Sent From My Evo Killer!!!
Click to expand...
Click to collapse
I'm currently running Bonsai 4.0 and it's seem to have been the worst. Are you telling me the they've done something in their latest release that fixes this issue? I don't see anything in their release notes that mentions this.
And trust me, I wipe data in CWM every time I try a new ROM.
mattallica76 said:
None of the Bluetooth issues currently present in EC05 are ROM related. The problem you are describing occurs usually after ext4 conversion or switching from one ROM to another. I haven't heard anyone report this type of issue that is running stock EC05.
I posted a solution in that has helped several folks and myself who were experiencing similar issues. Try this and let me know how it goes.
http://forum.xda-developers.com/showpost.php?p=12120496&postcount=1392
Click to expand...
Click to collapse
Interesting... I seemed to have the problem with stock EC05 as well. I Odin'd to D18, then ran the stock update.zip for EC05. I wiped as well.
I'm going to look at your post right now.
JRider said:
Interesting... I seemed to have the problem with stock EC05 as well. I Odin'd to D18, then ran the stock update.zip for EC05. I wiped as well.
I'm going to look at your post right now.
Click to expand...
Click to collapse
Ok, I just took a look. Wouldn't an Odin to D18 and/or a wipe delete this corrupt data in the data/misc/bluetoothd anyway?
JRider said:
Ok, I just took a look. Wouldn't an Odin to D18 and/or a wipe delete this corrupt data in the data/misc/bluetoothd anyway?
Click to expand...
Click to collapse
Yes, they both would, unless you restored it with Titanium or Nandroid/CWM. If you still have issues after trying the method in my post, you might want to double check your baseband version to make sure it's EC05. The Bluetooth is part of the modem. You might try reflashing the EC05 modem as well.
mattallica76 said:
Yes, they both would, unless you restored it with Titanium or Nandroid/CWM. If you still have issues after trying the method in my post, you might want to double check your baseband version to make sure it's EC05. The Bluetooth is part of the modem. You might try reflashing the EC05 modem as well.
Click to expand...
Click to collapse
I've never restored anything after reflashing. Coming from Windows Mobile ROM flashing taught me it's never a good idea to do.
I'm definitely on EC05 baseband. I've also tried reflashing the EC05 modem with Odin as well. At first I thought that fixed it for me. But a day later, the problems were back.
Again, whenever I flash back to an Eclair ROM, I don't experience any of these problems. So I'm more opt to think the issue lies in Froyo's "updated bluetooth" features.
JRider said:
I've never restored anything after reflashing. Coming from Windows Mobile ROM flashing taught me it's never a good idea to do.
I'm definitely on EC05 baseband. I've also tried reflashing the EC05 modem with Odin as well. At first I thought that fixed it for me. But a day later, the problems were back.
Again, whenever I flash back to an Eclair ROM, I don't experience any of these problems. So I'm more opt to think the issue lies in Froyo's "updated bluetooth" features.
Click to expand...
Click to collapse
EB13/EC05 definitely has a couple BT issues, but the one your describing has not happened on my stock Epic and only happened on my rooted one under the conditions I described in previous posts (and was fixed). We use both phones with several BT devices pretty extensively. If data wipes and reflashes haven't worked for you, and your issue is only with one BT device, you might try clearing the memory of the device. Also you should see if you have issues pairing with other devices.
mattallica76 said:
EB13/EC05 definitely has a couple BT issues, but the one your describing has not happened on my stock Epic and only happened on my rooted one under the conditions I described in previous posts (and was fixed). We use both phones with several BT devices pretty extensively. If data wipes and reflashes haven't worked for you, and your issue is only with one BT device, you might try clearing the memory of the device. Also you should see if you have issues pairing with other devices.
Click to expand...
Click to collapse
Thanks for all of your input!
Like I said in my original post, my wife's Incredible works with the same car without any issues. I've also tried "factory resetting" and erasing all paired devices in the car. And it always ends up with the same issue- any Froyo ROM I run has problems. Like I said, I've tried several, with wipes and Odin to stock, and stock EC05. All of them have the same problems.
I'm definitely not the only person who's experiencing the issues I'm describing. If you read through this other thread at another forum (http://androidforums.com/epic-4g-su...82-bluetooth-problems-after-froyo-update.html) you'll see a couple people describing the exact same problems. One user even talks about the phone showing that it's still connected to the device even after the car is shut off. And the only way to disconnect is turn off bluetooth. Another user talks about the car randomly reporting it as "BCRM Device" instead of what the Bluetooth device name is. Both of these problems, I've had as well.
Trust me, if I can find the cause of this issue, or a ROM that doesn't have it, I'm willing to give it a go. I want the Froyo enhancements, just not the bluetooth issues.
Does your automobiles head unit support Bluetooth phonebook functionality by chance?
Sent from my SPH-D700 using Tapatalk
mattallica76 said:
Does your automobiles head unit support Bluetooth phonebook functionality by chance?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Yes, it does.
Actually, one of the things Froyo does better with handsfree in the car is this feature. Eclair won't sync my Exchange contacts for some reason. It will only sync "Phone Contacts". It also doesn't handle the recent call log as well either. For some reason it will show sent emails and texts in my call history in the car. With Froyo, neither of these problems exist. But that means nothing when there's a fundamental issue with bluetooth itself.
Why do you ask?
JRider said:
Yes, it does.
Actually, one of the things Froyo does better with handsfree in the car is this feature. Eclair won't sync my Exchange contacts for some reason. It will only sync "Phone Contacts". It also doesn't handle the recent call log as well either. For some reason it will show sent emails and texts in my call history in the car. With Froyo, neither of these problems exist. But that means nothing when there's a fundamental issue with bluetooth itself.
Why do you ask?
Click to expand...
Click to collapse
Because I remember reading about the phonebook sync causing the Bluetooth to stop functioning. Try disabling the contacts sync and see if that helps.
Sent from my SPH-D700 using Tapatalk
mattallica76 said:
Because I remember reading about the phonebook sync causing the Bluetooth to stop functioning. Try disabling the contacts sync and see if that helps.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I actually went back to DI18 yesterday, rooted, removed bloatware, and I haven't had a single problem with hands-free Bluetooth in my car.
Again, there's definitely issues with Bluetooth in every version of Froyo. Disabling certain basic features (that other phones have been successfully doing for years) just to get it to work is not an option for me.
For now, I'll run Eclair, and hopefully these issues are resolved at some point.
I will totally agree with the OP Stock 2.1 was fine with my Parrot BT system. Since 2.2 Ive tried a bunch of roms and finally back to bone stock AND i still get a ton of BT issues ( disconnects,missing calls, phone is muted after calls etc etc) I miss my Palm Pre...lol
I have had all of the same issues since updating to Froyo. I had them stock and rooted.
5111 said:
I have had all of the same issues since updating to Froyo. I had them stock and rooted.
Click to expand...
Click to collapse
I've been running DI18 (stock and rooted) for the past two days with literally zero problems with bluetooth. I even loaded the EC05 modem to prove it has nothing to do with the modem (apparently bluetooth is part of the modem tar). So right now, I'm running Eclair DI18 with EC05 modem and bluetooth is working flawlessly.
So I will say it one more time... there is something in Froyo for the Epic that is causing bluetooth issues. It's not the kernel, it's not the modem, it's the Android OS (Froyo 2.2) that is causing the issues with bluetooth.
JRider said:
I've been running DI18 (stock and rooted) for the past two days with literally zero problems with bluetooth. I even loaded the EC05 modem to prove it has nothing to do with the modem (apparently bluetooth is part of the modem tar). So right now, I'm running Eclair DI18 with EC05 modem and bluetooth is working flawlessly.
So I will say it one more time... there is something in Froyo for the Epic that is causing bluetooth issues. It's not the kernel, it's not the modem, it's the Android OS (Froyo 2.2) that is causing the issues with bluetooth.
Click to expand...
Click to collapse
JRider- Just as an FYI, I am having the EXACT same problems you describe with my Moto Roadster. You aren't alone. I've tried most of what you said you've tried with no luck as well. Hope somebody finds a solution.
I've been experiencing the issue of outgoing audio cutting out during phone calls. I'd noticed it first when I tried EF02 and a variety of modems, and now I'm experiencing it still after going back to EC05 with the EC05 modem. Toggling speakerphone "fixes" the problem for that call.
I suppose what I'm trying to figure out is: could having tried EF02 have done something that going back to EC05 didn't resolve? Or perhaps was this happening after EC05 was OTA'd and I just didn't notice it? Is anyone having this on stock EC05?
Before I push to replace what's otherwise a perfect Epic, I want to see if this is a hardware or a firmware issue.
Sent from my Transformer TF101 using Tapatalk
Same issue
I am having the same issue. Tried EF02, which seemed to work great for awhile. Used Odin to return to stock for a completely different issue. Since that time on long calls...in excess of 10 minutes the person on the other end suddenly cannot hear me, and I hear them fine.
Currently ECO5 rooted, but stock otherwise.
Any ideas? I didn't see any answers to the first post, and don't see anything when I searched, prior to this post.
Ok, so I've been using CM nightlies for a very long time. I've never had any major issues unless many others were reporting the same trouble. So now, I've decided to upgrade to 10.2 since it's been a few days already and there are not major issues reported. I upgraded fine except that I do not get any sound at all when on a phone call. The mic isn't working nor can I hear anything from the headset.
The strange thing is that if I put the phone on speaker, I can hear the conversation and the mic is working. If I switch it back, it stops. I've tried the mic and sound in many other apps and everything seems ok except for when making calls. You can see how this is a big issue. If I revert back to CM 10.1, I don't have any problems. As soon as I go back to 10.2, same issue again.
I don't see anyone else reporting the same issue. Here's what I've done so far to try to fix this. I did a complete wipe, lost everything on the phone. I made sure I had the latest gapps. I tried without wiping coming from 10.1 as well. I did all the fix permission in ROM manager. I don't really know what else to do at this point since nothing seems to be working.
Does anyone else have this issue? I'll try stock 4.3 and see what happens but I wanted to share and get some feedback from here as well.
I have you seen s you. Have you found a solution yet? When I use a bluetooth headset it works Fine
You need to update your radio
wrdcndn said:
Ok, so I've been using CM nightlies for a very long time. I've never had any major issues unless many others were reporting the same trouble. So now, I've decided to upgrade to 10.2 since it's been a few days already and there are not major issues reported. I upgraded fine except that I do not get any sound at all when on a phone call. The mic isn't working nor can I hear anything from the headset.
The strange thing is that if I put the phone on speaker, I can hear the conversation and the mic is working. If I switch it back, it stops. I've tried the mic and sound in many other apps and everything seems ok except for when making calls. You can see how this is a big issue. If I revert back to CM 10.1, I don't have any problems. As soon as I go back to 10.2, same issue again.
I don't see anyone else reporting the same issue. Here's what I've done so far to try to fix this. I did a complete wipe, lost everything on the phone. I made sure I had the latest gapps. I tried without wiping coming from 10.1 as well. I did all the fix permission in ROM manager. I don't really know what else to do at this point since nothing seems to be working.
Does anyone else have this issue? I'll try stock 4.3 and see what happens but I wanted to share and get some feedback from here as well.
Click to expand...
Click to collapse
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931
wrdcndn said:
Ok, so I've been using CM nightlies for a very long time. I've never had any major issues unless many others were reporting the same trouble. So now, I've decided to upgrade to 10.2 since it's been a few days already and there are not major issues reported. I upgraded fine except that I do not get any sound at all when on a phone call. The mic isn't working nor can I hear anything from the headset.
The strange thing is that if I put the phone on speaker, I can hear the conversation and the mic is working. If I switch it back, it stops. I've tried the mic and sound in many other apps and everything seems ok except for when making calls. You can see how this is a big issue. If I revert back to CM 10.1, I don't have any problems. As soon as I go back to 10.2, same issue again.
I don't see anyone else reporting the same issue. Here's what I've done so far to try to fix this. I did a complete wipe, lost everything on the phone. I made sure I had the latest gapps. I tried without wiping coming from 10.1 as well. I did all the fix permission in ROM manager. I don't really know what else to do at this point since nothing seems to be working.
Does anyone else have this issue? I'll try stock 4.3 and see what happens but I wanted to share and get some feedback from here as well.
Click to expand...
Click to collapse
Try the app soundabout from the play store. Tell it to send audio to earpiece and under wired headset uncheck everything.
If mic doesn't work check out my thread in general section. Worked for me.
Sent from my Nexus 4 using xda app-developers app
SomeGuyInKc said:
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931
Click to expand...
Click to collapse
I was having this issue as well, and that worked perfectly! Thanks man!
*system error* said:
Try the app soundabout from the play store. Tell it to send audio to earpiece and under wired headset uncheck everything.
If mic doesn't work check out my thread in general section. Worked for me.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I tried that and that app and messed with different settings and it didn't work. I'm gonna try updating the radio and see what that does.
SomeGuyInKc said:
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931
Click to expand...
Click to collapse
That worked actually. Thanks!
SomeGuyInKc said:
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931
Click to expand...
Click to collapse
Huge thanks for this one. I had been searching google for a solution to this one for a week or so now. I will have to say, the most annoying thing I've had to deal with in quite some time. I should have just come to XDA first like an adult.
T-mobile s4
SomeGuyInKc said:
I had the same issue, updating the radio fixed it for me. I chose 33.84. You can get the radio firmware from http://forum.xda-developers.com/showthread.php?t=2358931
Click to expand...
Click to collapse
I have the same issue on T-mobile S4 CM 10.2
can you help me to bring my audio back ?
Try the T-Mobile S4 Forum
ptsite said:
I have the same issue on T-mobile S4 CM 10.2
can you help me to bring my audio back ?
Click to expand...
Click to collapse
Sorry, but I don't know if this applies to the Samsung S4. I would try posting over in the T-Mobile Galaxy S4 forum.