Just updated to 2.1, everything seems to work well except voicemail playback. The audio quality of voicemail playback is suddenly terrible, as if the data is being heavily compressed on playback. Never a problem with 2.0.2. I've tested and replicated this problem with EDGE and 3G, the problem is consistent.
Audio quality during calls seems fine, only voicemails sound awful.
Has anyone else encountered this issue with 2.1? Any solutions?
Okay, I've tested this problem from multiple land lines as well as other cell phones from AT&T and Verizon. Every voicemail played back on the 2.1 iPhone 3G sounds very tinny, like badly compressed AM radio. Regular call quality is fine, only voicemails are affected.
Anyone else experiencing this with the 2.1 update?
exact same here. I am in the UK with O2. To my ears its a new lesser quality codec being used at their (O2's) end.. Probably to save bandwidth etc.
Anyway, the quality is NOT acceptable.. It sounds like a $5.99 bargain bin kids toy that records voice notes...
Please restore the back end codec to the original high quality one..
Having the same issue here. All my voicemails are sounding tinny. I remember this being an issue with the 1.0 software from the original iPhone. I'm going to try to do a restore and see if this improves the issue. Has anyone tried this? It sounds like it's not happening to everyone, so it makes me wonder if it's just a bad install of the Firmware update.
same here.. I haven't been able to find much info at all on this. Seems like it would be getting more attention/traction on the websites/forums than it appears to be.
So I tried restoring with the 2.1 software but still have the same issue, with the voicemail quality now being tinny. It's not too bad, but definitely a step down from the quality we used to have. I guess we'll have to add that in to the list of issues to resolve for 2.1.1 or 2.1.2.
Ugh...but on the flip side...this one did fix some major issues..so I would put this in the medium issue category. As long as I can understand the voicemail its cool. But if we can't, that's when it becomes an issue, and that was the case with the first iPhone with 1.0 software.
Guys, you are not alone with the no SIM error message after 2.1 update.
I'm in Australia and I have the same problem. Apparently, 2.1 fries some SIM cards and you have to go to your service provider to get a replacement SIM card.
The funny thing is, the 2.1 update worked perfectly in my personal Iphone 3g but fried my work Iphone! Both phones uses SIM cards from the same provider. Don't understand why this is happening. Hope this help sort your problems.
My experience with voicemail quality is similar to yours. It sounded great on 2.0.1 and 2.0.2. With 2.1, it sounds somewhat tinny as you've described. Audio quality on calls is fine.
I tested on several voicemail messages (some from cellphone users, others from landline) - they all sound just as bad. Hopefully, this is corrected in the next update.
FWIW... If you call into your voicemail and listen to them, the quality is perfect -- as it use to be on the Visual Voice mail side of things. Apple support said the phone physically downloads the voicemails to the phone. So I suspect that v2.1 is compressing them down MUCH more than before. If they are going to do that, it should be an option we get to choose (save space or get better quality), IMO!
Glad I'm not alone on this. I've also confirmed that voicemails sound fine if I check them directly from AT&T. The bad audio quality only happens when I listen to them on the iPhone, which indicates bad audio compression.
You'd think Apple would test to ensure old features didn't get broken. But this kind of problem is common with patches. The list of new bugs is often as long as the list of bug fixes!
I am experiencing the same degradation in quality after upgrading to 2.1. This bug appears to affect all visual voicemail playback, as messages that were downloaded prior to upgrade display the same 'tinny' sound.
I've only received one voicemail since I updated and I did notice the audio quality was poor. Didn't think much of it until I read this thread. I just assumed it was a one-off problem because the call was placed from a mobile as well...