Like a lot of people, the Froyo update completely destroyed my battery life. I see there are a thousand posts on that topic, so I'll try to read through them to see if there are any suggestions. Another extremely irritating issue though, that I can't find anything on, is that I am having all kinds of trouble with the bluetooth pairing with my Kia Sorento since the update. I've had the car less than a month, but was easily able to pair my phone and have been happily using hands-free up until I updated my phone on Friday. Prior to the update, my phone was paired with the car, my contact list was synched, and I was able to dial and use speed dial from the touch-screen in the car. Following the update, the car was unable to connect to the phone, so I had to reconnect from the phone. Once I did that, my contact list was no longer synched and I was not able to dial using the touch-screen in the car. I deleted the pairing and recreated it, and was once again able to sync my contact list, but still no dialing from the car. Also, my phone still says it is using bluetooth audio even after the car is shut off and I'm in the house. I have to disable bluetooth in order to fix that issue, but it hangs for five minutes or so before shutting off. I have actually had to power off the phone in order to get bluetooth to shut down. Anyone else experiencing this problem or have any ideas?
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Help Bluetooth problems after Froyo update
- Thread starter cjstl
- Start date
-
- Tags
- samsung epic 4g
Still have bluetooth problems here. Seems to work with dialing out with froyo but when you disconnect the sound is muffled like it is coming from the earpiece jack instead of the regular speaker. The only way to get the normal sound to work is to reboot phone.
I have tried turning off BT on phone first then device, tried turning of device then BT on the phone. Neither works. Still have to reboot.
I have tried turning off BT on phone first then device, tried turning of device then BT on the phone. Neither works. Still have to reboot.
I am having the same problem with the Bluetooth showing that it is still connected to my car, even after I turn the car off and go inside. The only way to correct it is to manually turn the Bluetooth off. My phone hangs up at this point to, sometimes eventually turning the Bluetooth off, but sometimes requires rebooting the phone. I also tried un-pairing and re-pairing my phone, before I realized the Bluetooth feature was never closing when I shut off the car. Curious thing happened...when I went to pair the phone, it automatically connected without requiring a passkey to my car Bluetooth...it showed up as BRCM Device, rather than "My Device" All of this has happened since the 2.2 upgrade. Sprint tech support recommended a hard reset...I have not done that yet, since I have files to save before trying that. Has a hard reset worked for anyone else??? Or is it a problem with the 2.2 upgrade???
IT WORKS TODAY!!!...Follow up to my post from yesterday...I paired a Samsung Instinct s30 to my car Bluetooth. This phone had no problems signing off, but my Epic continued to be in Bluetooth mode even after the car was turned off, until I manually disabled the phone Bluetooth. I noticed that the Epic gets stuck in "Synch" mode...it NEVER stops trying to synch with the car Bluetooth. Even after the car is turned off, my phone was still trying to synch with the Bluetooth. After verifying that the Bluetooth firmware was up to date, I did the hard reset of my phone, and now, for the FIRST time since the EC05 update, my Epic is behaving as it should. Granted, it is only one day, but it is a start, and time will tell if it continues to work correctly.
I've been having these same exact issue with every Froyo rom I've tried (stock or custom roms). I have a 2011 Kia Optima, and used to use my bluetooth flawlessly with Eclair 2.1.
I'm currently using Bonsai 4.0 (Froyo) and still have the issues. I'm considering trying to find a good custom 2.1 ROM to switch to, because I've decided it just doesn't work right with Froyo, and it's too important for me to have a steady bluetooth connection.
I'm currently using Bonsai 4.0 (Froyo) and still have the issues. I'm considering trying to find a good custom 2.1 ROM to switch to, because I've decided it just doesn't work right with Froyo, and it's too important for me to have a steady bluetooth connection.
queteacher
Lurker
I have had to resych at least four times since the update. Additionally, my phone freezes up and the touchscreen does nothing, nor does the power button.. I have to take the battery out and power up. This happens at least two times a day. I have an appointment to take my phone in today. Everything was fine until the update. This never happened with my Palm Centro.
My wife and I got new Samsung Epics two weeks ago. Just after buying the phones, we installed the Froyo update after getting the update message on each phone. I paired both phones to each of our cars and headsets. At first, we could use bluetooth just after pairing, but on the next use, we had to pair again. So our phones were basically useless for Bluetooth. Even my wife's Samsung headset had to be re-paired with each use (enter PIN).
Then I flashed both phones back to EClair. Now our bluetooth has been perfect on both phones - no issues whatsoever. I even tried to update my phone to Froyo again - but the same issues occurred, so I flashed back to EClair.
To turn off the update nag, I rooted the phones and renamed /system/app/SystemUpdater.apk.
Now both phones are working great! No more bluetooth problems.
Hopefully they will make Froyo 2.2.2 or something to fix these Bluetooth problems. For now, we will happily stay with Eclair.
Then I flashed both phones back to EClair. Now our bluetooth has been perfect on both phones - no issues whatsoever. I even tried to update my phone to Froyo again - but the same issues occurred, so I flashed back to EClair.
To turn off the update nag, I rooted the phones and renamed /system/app/SystemUpdater.apk.
Now both phones are working great! No more bluetooth problems.
Hopefully they will make Froyo 2.2.2 or something to fix these Bluetooth problems. For now, we will happily stay with Eclair.
I may end up doing this same exact thing in a few minutes. My bluetooth in my car works perfectly with 2.1. Well, almost perfectly. The only issue I have is my contacts do not sync over unless they are "Phone Contacts". My Exchange contacts (which is what all of them are) don't sync. So what I have to do is copy them to the "Phone Contacts" then sync, then delete them so I don't have duplicates. I also find that with 2.1, my call history (my call will sync my recent calls) will also show recent emails and texts- so that's kind of weird. I don't have these issues with Froyo, but at least with 2.1 my phone will connect every time I get into my car.
Similar issues here. Bluetooth worked fabulous for over 1 year, after FROYO update, not so much. My issues are similar. Often my car (VW Jetta) can't drop a call connection. I've had it fail to drop when disconnecting from phone, and disconnecting from steering wheel control. When I walk away from my car (in my office), about 50% of the time, the phone will ring thru my ear speaker, not the usual speaker. So it's so faint, I rarely hear it ring. It's make my bluetooth useless. The only way to get things back to normal is power cycle. So now, everytime I walk away from my car I power cycle my phone to get the ringer back. Kind of silly don't you think. Just for grins, I tryed the exact same drill with my motorcycle (Chatterbox). Exact same result, so it's definitely a phone issue.
I tried a factory reset after the FROYO update, just to see if anything was left over from my settings that might be causing it. After factory reset, no other apps installed, etc. Same result.
I tried a factory reset after the FROYO update, just to see if anything was left over from my settings that might be causing it. After factory reset, no other apps installed, etc. Same result.
I have an Epic and 2011 Kia Sportage. I haven't updated my phone since I purchased the car a few weeks ago, but I think I did an update shortly before. When I connect the phone to the car's Bluetooth, it normally works for one call. Seems to work flawlessly, but one call is all I get. From then on, even though the car and phone both say they're still connected, and I can use the voice dial feature - it really doesn't work. The command doesn't reach the phone. Another problem I have is that sometimes it gets stuck in the phone book download phase and I can't do anything. HELP!!!! I'm not a phone techie, so I'm not sure what all the Froyo / Eclair talk is about but I would really like to get this fixed. Any advice or help (remember I'm no phone tech guru) would be appreciated.... 
I have an Epic and 2011 Kia Sportage. I haven't updated my phone since I purchased the car a few weeks ago, but I think I did an update shortly before. When I connect the phone to the car's Bluetooth, it normally works for one call. Seems to work flawlessly, but one call is all I get. From then on, even though the car and phone both say they're still connected, and I can use the voice dial feature - it really doesn't work. The command doesn't reach the phone. Another problem I have is that sometimes it gets stuck in the phone book download phase and I can't do anything. HELP!!!! I'm not a phone techie, so I'm not sure what all the Froyo / Eclair talk is about but I would really like to get this fixed. Any advice or help (remember I'm no phone tech guru) would be appreciated....
I'm having the EXACT same issue in my VW. I got a replacement the other day (was under 30-day trial) and the other one worked fine. This one is performing the exact same was you described. It works for one call, but then it comes straight to my phone, not the bluetooth, even though the phone shows it's paired. If I try to make a call through the car's BT functions, it shows "Dial Up Failed" - then I have to turn off bluetooth on both, reconnect - but then only works for the first phone call. What is going on? I thought it was just me. I don't want to have to get a third refurbished phone....
MarsThunder
Lurker
I was hoping it wasn't going to be the same, but it is. I updated my Vibrant (Galaxy) this weekend to Froyo using Kies (T-Mobile method, not OTA like Sprint & Verizon). My phone worked perfectly at 2.1 with my new Hyundai Genesis: voice dialing, phonebook (phone contacts only, not gmail, SIM, or Exchange) all worked as they should. So I knew the phone physically can do it. I will have to try the hard reset. What happens now: phone is recognized and pairs fine (even makes the email noise which it didn't before), can re-download contacts fine, disconnects when car turned off fine (also with email noise). It just won't place call. Either by voice or using phonebook manually, the number shows on driver info system screen and says 'dialing...' but it never dials - just ends. I even see the number on my phone screen which also says 'dialing...', so the communication with car seems to be right on the money. Just wanted to share my version of the issue.
MarsThunder
Lurker
Ok. Without doing much of anything, I think it is working as it should. What I did: I had bluetooth on my phone off (usually I keep it on). Car screen showed 'not connected' - good. Turned blutooth on phone back on. Got the email noise and paired up showing on both screens. Dialed a call on car joystick - worked. Chose 'voicemail' on my phonebook and called thru to voicemail - worked. Called by name with voice control - dialed and worked! All seems to be well. Interesting, I noticed duplicate contacts on my phonebook in the car. Perhaps (and I hope it is true) it is actually retrieving from my 'phone' contacts as well as my 'exchange' contacts! I know 2.2 beefed up much in the Exchange connectivity side of things. Will investigate further....
Lady Shiloh
Lurker
I have an Epic and 2011 Kia Sportage. I haven't updated my phone since I purchased the car a few weeks ago, but I think I did an update shortly before. When I connect the phone to the car's Bluetooth, it normally works for one call. Seems to work flawlessly, but one call is all I get. From then on, even though the car and phone both say they're still connected, and I can use the voice dial feature - it really doesn't work. The command doesn't reach the phone. Another problem I have is that sometimes it gets stuck in the phone book download phase and I can't do anything. HELP!!!! I'm not a phone techie, so I'm not sure what all the Froyo / Eclair talk is about but I would really like to get this fixed. Any advice or help (remember I'm no phone tech guru) would be appreciated....
I'm with you guys. Samsung Epic and a 2011 Hyundai Elantra. I've re-paired this phone a dozen times trying to get this to work. I get one call, then even though it shows as connected, it isn't working. I even got stuck in "Phonebook Downloading" mode for several days! So we just have to wait for a new Froyo update and hope for the best? That sucks! Guess it's time to write to Google and let them know that, while 2.2 might be GREAT for a lot of things, their bluetooth connectivity SUCKS!!!
But what's weird about all of this is that my husband has the exact same phone I have, but he has no problems making multiple calls. He also has the 2.2 operating system. So I really don't get it.
D
Deleted User
Guest
Chiming in...
I have a 2008 Acura MDX and until a week ago my Epic 4G has been working flawlessly since I've paired it months ago. I went to the Acura corporate website and found out the Samsung Epic 4G is NOT compatible with the 2008 Acura MDX. What gives? It was working fine.
Digging deeper: I've recently tried one of these voice fancy dialing apps (Vlingo? Forgot the name, deleted it from my phone) and I have a strong suspicion that is the culprit to why my phone no longer pairs with my car. After I deleted the app, the phone stopped pairing and working with my car.
Any thoughts or input would be appreciated.
Thanks in advance.
I have a 2008 Acura MDX and until a week ago my Epic 4G has been working flawlessly since I've paired it months ago. I went to the Acura corporate website and found out the Samsung Epic 4G is NOT compatible with the 2008 Acura MDX. What gives? It was working fine.
Digging deeper: I've recently tried one of these voice fancy dialing apps (Vlingo? Forgot the name, deleted it from my phone) and I have a strong suspicion that is the culprit to why my phone no longer pairs with my car. After I deleted the app, the phone stopped pairing and working with my car.
Any thoughts or input would be appreciated.
Thanks in advance.
I updated my vibrant to 2.2 Froyo and the next morning I had an update for Bluetooth in the market. So Updated and now it is hit or miss when I can use it in my car (2012 Passat). It seems like it worked fine after the Froyo, but after the market update it just does it's own thing. Does not disconnect once vehicle turns off. If it does work, it is only good for one call and then it still registers that it is on, but it rings through headset. I have to either shut off the whole bluetooth or the whole phone. I don't want to do a reset because I have already read that people seem to experience similar problems still. I hope Samsung will fix this issue QUICKLY! We shouldn't have to reset our phones because of a problem they created! I am also hoping that everyone posts so Samsung will fix.