Badapple59 wrote:
Thank you, rbrylawski. I and most others are not here to bash apple but are here out of continued frustration. If apple would have been honest and told me that it is a known issue and to sit tight while they come up with a fix i would be fine with that. For them to turn their head on me while under warranty, force me to purchase applecare, etc is no way to treat a loyal customer. Im quickly starting to feel as though i had bought it from a shady street vendor in Hong Hong. Just be honest.
Very few (if any) companies will publicly admit a flaw with their product. Nikon introduced the full frame D600 a year ago. Immediately, people began getting oil spots on their sensors, which translated to spots on pictures. Nikon never admited an issue, but for anyone who had the oil sensor issue and their camera was sent in for service/cleaning, Nikon quietly replaced the mechanism that caused the issue. And a year later, which is not typical for the life-cycle of a full frame camera, the D610 was released.
I'm a Nikon fan. I've had Nikon DSLR's since the year 2000. Had that happened to me, I'd have been disappointed, but at least Nikon took care of the effected customers, while never admitting blame.
Apple has a storied reputation for being very quiet about new releases and very quiet about fixes for products already released. The only reason Apple had to admit there was an antenna issue on iPhone 4 was because it was so widespread, it had become comedy material for Jay Leno and had grown to become well documented by the press.
Compare that with Proximity sensor issues. It was never publicly acknowledged by Apple. BUT, it was fixed in a software update.
I think people here are expecting something Apple is not going to do. They're not going to say iPad Air or iOS 7 has an issue. But everyone should know that while Apple does not participate in these forums (except for moderators who delete or edit posts that violate the terms of use we all agree to when we joined Apple's Hosted Forum) Apple is most certainly reading these posts and is hard at work on a major software upgrade, which I'm sure everyone on this thread hopes will solve this issue.