Dear Iphone4_925:
I have always thought it was a software issue. Hardware can be designed in such a way to have a hysteresis effect. So it is possible that it could be hardware, but I doubt it. Even if the hardware is somewhat at fault I still think and have always thought it can be fixed via software. I really think that it is software.
Look at the post I did on this page:
http://discussions.apple.com/message.jspa?messageID=11920701#11920701
The prox sensor is not a ruler. It only needs to know that a face is within a certain distance of the face. It doe not need to know that the face is .25", .5" or etc from the face. Yet, it appears that is what they are trying to do.
Dear Rapstone:
Apple is great company, but slow it seems to acknowledge a problem. They may not have thought it was a wide spread problem. Maybe they are still not sure. Steve did use the word "tracking". Maybe our posts and the little press coverage of late is at least making them look into it. I guess we don't know. I read that someone said the next OS update would be toward the end of September. I do not know if that is true. I guess the real question is can the users that currently have this problem put up with it until then. Can the users that will experience this problem be able to endure it?
It is bad in my phone. However, I think I have figured out a way to lessen effect of this prox issue. I am trying to answer this question myself before my Genius bar apt. today. I really like the rest if the phone. The signal issue has not been an issue for me.
I agree that all users with this problem should call Apple Support and report it. Apple is made up of engineers and people that love numbers. These types love data. I know, because I am an engineer. I have often said "the data does not lie". That is the engineer in me. However, data does not always reflect reality.
I have to decide which bugs (software and hardware) are fixed first or last at my company. I decide based mostly upon the numbers. If a bug will be experienced by a lower percentage of users, then it is lower on the list. If it is experienced by a larger percentage, then it gets fixed more quickly. Bugs that corrupt or delete data or crashes always get the highest priority. So I base these decisions on my understanding of the numbers. You have no choice.
The more people that report this as an issue will increase the numbers. That is why I tried to get coverage for the problem, because it increases the numbers in a way.
Look at some of my previous posts. The testing I did shows a memory effect and this average like method to create a new trigger point. I have no idea why they would do that. I do agree that the prox issue may be better or worse depending on the users habits.