Related
Anybody else having problems with keeping Bluetooth audio working after the DI07 update?
I'm on a replacement phone and my A2DP headset seems to lose sound after a while of inactivity and needs to be re-paired. The previous phone was on DG27 and didn't have this issue, so I'm guessing the update had something to do with it.
lordsandwich said:
Anybody else having problems with keeping Bluetooth audio working after the DI07 update?
I'm on a replacement phone and my A2DP headset seems to lose sound after a while of inactivity and needs to be re-paired. The previous phone was on DG27 and didn't have this issue, so I'm guessing the update had something to do with it.
Click to expand...
Click to collapse
I have noticed this also. Cuts out during calls also.
Yep have this problem as well. Very very annoying.
Sent from my SPH-D700 using XDA App
Crap, guess that justifies trying an overclocked DG27 kernel to see if it fixes the issue. Not like GPS was resolved with the update anyway.
I also have the problem. Hope it gets addressed soon.
Sent from my Epic 4g
Flashing a rooted kernel didn't help, I think it's the DI07 baseband that's screwing up. May revert to DG27 stock later to see what happens.
lordsandwich said:
Flashing a rooted kernel didn't help, I think it's the DI07 baseband that's screwing up. May revert to DG27 stock later to see what happens.
Click to expand...
Click to collapse
I'm still running DG27 and this issue is present here also. Except when I was running DI07, I would also get soft re-boots while connecting or disconnecting to and from Bluetooth devices.
Restored to stock DG27, applied one-click ClockworkMod and flashed Mixup kernel. So far things seem stable unless I start restoring the system and data images from my DI07 Nandroid backup.
I'm going to test my user apps one at a time to see if any of them was affecting the Bluetooth audio, however unlikely that may be.
EDIT: Looks like stock DG27 solved it, music apps are all running fine.
Has anyone with this problem tried upgrading to DI18 to see if Bluetooth is fixed? I'm a little hesitant to try now that I've got everything working again.
I am running D118 with MixUp nonvodoo kernel. I just install a bt headunit tonight and tried bt audio. I have audio drop out but I also restored apps and data with Titanium Backup. I dont't know if that makes any difference. I tried a call with bt and that seemed fine.
I only have a couple days left, to return this phone.
Im having two huge bugs.
1. When I call people sometimes the phone calls them but the speakers never turn on, I cant hear them and they cant hear me... I cant even hear it ring...
2. Sometimes the proximity sensor goes ape bananas during a phone call and turns the screen off and on even when the sensor is next to my head.
Im using a custom rom but, Ive had both of these problems on the shipped rom as well. Is anyone else having these problems? If not Im assuming I have faulty hardware and will be returning my phone.
edit: Im pretty sure Ive gotten to the bottom of both of these issuses.
1. not being able to hear caller. This is a problem with all dk28 based roms. If you wait until you see the call is connected and the counter has started for a few seconds it should happen alot less often. If the problem still does happen usually turning on speaker phone and then back off again will remedy the situation.
2. proximity sensor freaking out. The proximity sensor works fine if you put your hand in front of it. The problem I was having is on occasion a small lock of my hair would be in between the proximity sensor and my head, this caused the sensor to bug out and turn the screen off and on. So if this happens to you just make sure the sensor located just to the right of the ear piece is point towards skin w/o hair in between it.
Most of the people on this forum, prolly have short hair and thats why they havent noticed it.
Go get it replaced before your time is up. Say that you are having issues that aren't being resolved through reloading di18
It is most likely hardware issue.
Sent from my SPH-D700 using XDA App
What android version are you on?
had the phone for a week and notice this problems, so i think i was on di18, which is 2.1 update
and currently im on 2.2.1 froyo
if no one else is having these problems, Im going to call them in an hour.
That isn't a common issue with the epic. Exchange it, remember to flash back to di18
Sent from my SPH-D700 using XDA App
What are you guys talking about? The speaker issue is a known issue in DK28, and I have the proximity sensor issue quite a bit (though only in Cyanogenmod).
Try toggling Speakerphone and/or Mute at the start of the call and see if it fixes that problem.
AndrewZorn said:
What are you guys talking about? The speaker issue is a known issue in DK28, and I have the proximity sensor issue quite a bit (though only in Cyanogenmod).
Try toggling Speakerphone and/or Mute at the start of the call and see if it fixes that problem.
Click to expand...
Click to collapse
hmm I guess Ill hold off another day before I return it, see if anyone else can confirm or deny these are software issues....
thx for the feedback so far.
AndrewZorn said:
What are you guys talking about? The speaker issue is a known issue in DK28, and I have the proximity sensor issue quite a bit (though only in Cyanogenmod).
Try toggling Speakerphone and/or Mute at the start of the call and see if it fixes that problem.
Click to expand...
Click to collapse
This doesn't happen for me...what hardware version are you guys?
Sent from my SPH-D700 using XDA App
I have the issue with the phone calls not being able to hear them, or them hearing me.. Running 2.2.1. Did not have this problem before the upgrade to DK28.
I have not noticed any problems with the proximity switch, although every once in awhile my screen will not turn off like it is supposed too.
mrhocuspocus said:
had the phone for a week and notice this problems, so i think i was on di18, which is 2.1 update
and currently im on 2.2.1 froyo
if no one else is having these problems, Im going to call them in an hour.
Click to expand...
Click to collapse
I don't know if I am too late "chiming in" in here, but I can confirm that the call issue did not happen to me on the stock, out of the box, rom. However, every dk28 rom I have flashed has given me that issue. It is a "bug" in the leaked dk28.
The proximity sensor seems to be a hardware/software issue. That has never happened to me (the way you described it) For that - you should take the phone back before your time is up!
As someone posted earlier - flash/odin back to stock before you take it back!!
Got the same thing happening, using DK28 nebula rom, it happens like every other call.
I have experienced the call issue once after switching to 2.2 DK28, only once, and I have been running it since leaked.
as for the proximity sensor, I've heard of issues, but only seem to have an issue myself if I'm holding the phone at a odd angle.
If you have any concern at all, take it back and make them give you a new one, assuming your still in your buyers remorse period there shouldn't be any issues.
It's already been mentioned, but I'll repeat it again, flash back to DI18 before returning.
FWIW, I love this phone, very few glitches, very stable even running leaked DK28. There is not a better phone available through sprint at the moment.
Also wanted to add that the ROM I am currently using is Epic Experience 2.0.07
I think I have solutions to both of my problems, I have updated the op to reflect these events, and hopefully help other people.
Glad to hear you figured it out, I guess I just haven't noticed the first issue all that much.
I wish more people would update their posts like you did.
Sent from my SPH-D700 using XDA App
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 have this problem for long time.
I have great reception at my office and home, and I do not hold the phone all the time, so its not death grip thing.
Many people complained that I did not answer the phone....
I would, if it rings..... My phone is always charged and out of blue, I got few voice mails. I tried make a phone call, my vibrant says calling and call ended.
I had to reboot my phone and its fine again.
I called CS many times and changed my phone twice. I still have this problem.
I tried almost all roms and modems, and I still have this damn problem.
I have been with t-mobile when they were voice stream, never had this problem until I got vibrant.
If anyone know any solution about this, please let me know.
I hate to leave t-mobile, but I think I have to if I do not find solution for this.
Help!
how often do you flash things? i had very similar issues that resulted from something getting corrupted. i odin'd to stock and reflashed and havent had issues since, tho i never tried flashing an alternative modem. I would give that a shot but chances are that odin will be your best bet.
Cheers
peekapoo said:
I have this problem for long time.
I have great reception at my office and home, and I do not hold the phone all the time, so its not death grip thing.
Many people complained that I did not answer the phone....
I would, if it rings..... My phone is always charged and out of blue, I got few voice mails. I tried make a phone call, my vibrant says calling and call ended.
I had to reboot my phone and its fine again.
I called CS many times and changed my phone twice. I still have this problem.
I tried almost all roms and modems, and I still have this damn problem.
I have been with t-mobile when they were voice stream, never had this problem until I got vibrant.
If anyone know any solution about this, please let me know.
I hate to leave t-mobile, but I think I have to if I do not find solution for this.
Help!
Click to expand...
Click to collapse
I have this exact same problem, I'm fact I was going to post here just now
Sent from my SGH-T959 using Tapatalk
I used to have that same problem when I was on stock rom. Haven't had that since I rooted and flashed to bionix v by tw.
Sent from my SGH-T959 using XDA App
Yes, I did odined back to stock, and reflashed. I still have that issue.
try a differnt modem
Pls post more infos:
Rom, Kernel, Modem? Apps?
I tried many, if not all modems and roms, so I can't provide specific rom or modems.
I've tried all modems kb5, ka6, ka7 no luck. I've tried bionix trigger stock toxic and sgs2 clone rom and still see the issue
Sent from my SGH-T959 using Tapatalk
I have the same problem. on bionix v1.3.1 modem kb1.
I generally have the problem in lower reception areas, but others phones i have don't have the problem. You'd think a great phone like the vibrant would be able to handle lower bar reception...