Eric Shawn2
2011-03-12 16:15:02
modular747 wrote:
Gotta be a bug, never happened in 4.2Yet it isnt happening to millions of others who updated to 4.3. The problem is in your phone, caused by corruption of data/settings during the update process, not the iOS itself. You need to restore.
Message was edited by: modular747
From how you mention this, stills sounds like an issue for Apple. Updating shouldnt cause considerable bugs like this. Understandable issues like cant complete update (doesnt update and youll have to try again), server overload from too many people trying to update at once, or even updates that just hangs. But successful updates that give no error, or indication anything went wrong until you actually try something youve been successful many times before the update, only to find out the hard way. I will have to disagree. Considering there are others who are experiencing the same issues. Whether its 10 people or 10000000 people, its still an issue that needs to be addressed by Apple. I really hope that Apple doesnt have that mentality that, the lesser people having issues with updates, is less significant than those that havent. They still paid the same amount for their phones, they are still customers who bought their phones because they believed Apple products to be reliable.
Who cares if millions of others havent had the problem. The problem is still there for a lot of people. Their data is lost, all the restoring in the world wont get it back. How do they get compensated for that. Again, no issues prior to their updates. You can give excuses, doll it up however you want, but the fact remains, the update(s) messed up their phones plain and simple.
Yet many other iPhone users who updated to 4.3 are experiencing issues they never had before. How do you answer that?
Mac Pro Intel Xeon Quad 2.8, 6GB ram, Superdrive (internal) Mac OS X (10.6.4) 2x500GB, 1x320GB, 1x1TB SATA (int) HDDs, Radeon HD2600 256MB, LaCie FW burne
Reply