• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Ringer problems after 2.2 update

G

George0211

Android Enthusiast
Has anyone noticed any issues with the ringer after 2.2 update?
On my phone it works if you restart the phone for about half hour to an hour. After that it only vibrates if there is a call coming in or an email notification and so on. If I restart the phone it fixes itself for about an hour and then the same thing happens.
 
After a major update it's a good idea to go through your device as if you're configuring everything for the first time.. Froyo seems to often reset, duplicate and mess with things all through the OS, as reported all over the forums from device to device getting 2.2.
 
Frisco said:
After a major update it's a good idea to go through your device as if you're configuring everything for the first time.. Froyo seems to often reset, duplicate and mess with things all through the OS, as reported all over the forums from device to device getting 2.2.
Click to expand...

I did do that. Right after the update, I went thru all my settings. Once I noticed this issue, I double checked all my settings again, and they are fine.
 
Also, wanted to add that it seems like it's not just the ringer, it's the speaker. I can't get any sounds to come out at all, unless I restart, and then it stops working after a while anyway.
 
Yeah, tech support had no clue. So AT&T ended up replacing the phone. I got a refurbished Captivate from an AT&T store on Saturday night. The phone came with 2.1 JH update installed, so I had to do the 2.2 update again. So far so good.

On a side note, the fact that it was refurbished bothered me at first, but I must say it looks brand new. If they put it in the box and packaged it like a new one, I would never know.
 
Do any of you have a Jawbone ICON or some other Bluetooth headset with AD2P protocols? I was able to replicate the problem by enabling the AD2P and making a call. Somehow that takes over all the audio on the phone itself. By disabling the media playing (AD2P) function in settings and shutting down then restarting the phone the problem goes away. I'm curious to find out if it is for ALL AD2P Bluetooh Devices or just JAWBONE ICON or all JAWBONES.

Please, respond if you have a way of testing this.
 
jcylcruzin said:
Do any of you have a Jawbone ICON or some other Bluetooth headset with AD2P protocols? I was able to replicate the problem by enabling the AD2P and making a call. Somehow that takes over all the audio on the phone itself. By disabling the media playing (AD2P) function in settings and shutting down then restarting the phone the problem goes away. I'm curious to find out if it is for ALL AD2P Bluetooh Devices or just JAWBONE ICON or all JAWBONES.

Please, respond if you have a way of testing this.
Click to expand...

I don't have a Jawbone device but I was using BlueAnt Q2. And yes, when I say all sounds go away, they go away on the phone, but are still working on the bluetooth device.
This is not an issue on my replacement phone.

Have you tried doing a factory reset on your phone? I tried it on mine and it didn't fix the problem, that's when I called AT&T and got a replacement phone.
 
George0211 said:
I don't have a Jawbone device but I was using BlueAnt Q2. And yes, when I say all sounds go away, they go away on the phone, but are still working on the bluetooth device.
This is not an issue on my replacement phone.

Have you tried doing a factory reset on your phone? I tried it on mine and it didn't fix the problem, that's when I called AT&T and got a replacement phone.
Click to expand...

Factory reset did bupkis as suspected. Did your replacement ship with 2.2 Froyo? Ok so your Blueant also has AD2P... and this problem did not happen on your replacement? Must be only on certain handsets then. Unless you are back to 2.1 Eclair?
 
jcylcruzin said:
Factory reset did bupkis as suspected. Did your replacement ship with 2.2 Froyo? Ok so your Blueant also has AD2P... and this problem did not happen on your replacement? Must be only on certain handsets then. Unless you are back to 2.1 Eclair?
Click to expand...

They gave me a choice of shipping the replacement to my house or go to a device support store and pick one up. I chose to go pick it up at a store, because it was only a few miles from my house. The replacement came with 2.1 JH7 firmware, so I had to upgrade it myself.
Yes my bluetooth device does have AD2P and this problem has not occurred with the replacement phone running 2.2
 
George0211 said:
They gave me a choice of shipping the replacement to my house or go to a device support store and pick one up. I chose to go pick it up at a store, because it was only a few miles from my house. The replacement came with 2.1 JH7 firmware, so I had to upgrade it myself.
Yes my bluetooth device does have AD2P and this problem has not occurred with the replacement phone running 2.2
Click to expand...

They let you get warranty replacement from store? Have you had your phone for less than 30days? I'm shocked they are being so helpful. So let me be paranoid -when you receive a call with the bluetooth connected your handset also rings right?
 
jcylcruzin said:
They let you get warranty replacement from store? Have you had your phone for less than 30days? I'm shocked they are being so helpful. So let me be paranoid -when you receive a call with the bluetooth connected your handset also rings right?
Click to expand...

It wasn't a regular retail AT&T store, it was a device support store. They don't sell phones, they are there to replace phones under warranty or help you with a problem.
And to answer your question, yes, the phone itself does ring now, with the replacement phone. My old one didn't.
 
George0211 said:
It wasn't a regular retail AT&T store, it was a device support store. They don't sell phones, they are there to replace phones under warranty or help you with a problem.
And to answer your question, yes, the phone itself does ring now, with the replacement phone. My old one didn't.
Click to expand...

Sweet! I'll have to look into that, waiting for my replacement jawbone as it was also giving me problems -just to rule out defective jawbone signals. I'll keep y'all posted on this ongoing saga.
 
jcylcruzin said:
Sweet! I'll have to look into that, waiting for my replacement jawbone as it was also giving me problems -just to rule out defective jawbone signals. I'll keep y'all posted on this ongoing saga.
Click to expand...

@George0211 -thanks for your info, so I strolled into the DSC and wouldn't you know it the phone decides to work 99% of the time they tried to replicate the error while I was there. Thankfully, I was able to make it happen 1 time right in front of the service rep and they replaced me... whew... just like you said I have to do the 2.2 Froyo update myself... wish me luck y'all (chanting -No Brick, No Brick, No Brick, No Brick, No Brick, NO BRICK!!!)
 
And the problem is back even on the replacement phone. Right after using a bluetooth headset, the speaker on the phone stops working unless you restart phone.
Anyone who is using a bluetooth device, have you see this yet?
I'm using BlueAnt Q2 headset.
 
George0211 said:
And the problem is back even on the replacement phone. Right after using a bluetooth headset, the speaker on the phone stops working unless you restart phone.
Anyone who is using a bluetooth device, have you see this yet?
I'm using BlueAnt Q2 headset.
Click to expand...

Here's how I've isolated the problem, seems to be a quirk in how the AT&T 2.2 FROYO handles AD2P.

1) Adjusting the ringer volume just after ending a received call or dialed call through a connected bluetooth with AD2P enabled will cause the audio to go completely to bluetooth AD2P.

2) TEMP FIX 1... call your now silent phone (bluetooth should still sound) and answer the call. Your NEXT call will sound on the phone and keep sounding as long as you don't mess with the ringer volume buttons.

3) TEMP FIX 2... shut down the phone and turn back on. Leave the ringer volume buttons ALONE! And the phone will ring through.

4) WORKAROUND from PHONE... go to your bluetooth settings and hold down the paired bluetooth device, from the option uncheck the media selection. Shutdown your phone and reboot. You will lose the ability to play music... but Calls should work fine 100% now.

5) WORKAROUND from JAWBONE MYTALK UPDATER -turn off AD2P and connect to phone after reboot. result same as (4).

Hope this helps!
 
For the original OP's issue: I found that even though the settings may be correct-such as the ringtone-I had to go into the setting, change it, reboot, then change it back to what I had to begin with, then all is ok. I did this for ringtones, notification tones, etc after 2.2 mucked them. Hopefully that was done before returning the device
 
fldude99 said:
For the original OP's issue: I found that even though the settings may be correct-such as the ringtone-I had to go into the setting, change it, reboot, then change it back to what I had to begin with, then all is ok. I did this for ringtones, notification tones, etc after 2.2 mucked them. Hopefully that was done before returning the device
Click to expand...

Yes, I did all that before I called AT&T.
Just like jcylcruzin posted, this is an issue with AD2P in Froyo.
 
George0211 said:
Yes, I did all that before I called AT&T.
Just like jcylcruzin posted, this is an issue with AD2P in Froyo.
Click to expand...

Y'all there doesn't seem to be many of us yet finding this problem. But I'm hopeful that more people will chime in. Unless there are a lot of complaints we won't be able to get Samsung to fix it. So please do check around with others that have the same phone and make sure to call Samsung and bitch about it!

Thanks guys!
 
jcylcruzin said:
Y'all there doesn't seem to be many of us yet finding this problem. But I'm hopeful that more people will chime in. Unless there are a lot of complaints we won't be able to get Samsung to fix it. So please do check around with others that have the same phone and make sure to call Samsung and bitch about it!

Thanks guys!
Click to expand...


This actually seems to be a problem with Froyo in general, not just Samsung
 
This is DEFINITELY a problem. I've missed some very important calls due to this BS. I'm going to try to uncheck the media option in my BT headsets and see what happens
 
You must log in or register to reply here.
Back
Top Bottom