I see that this thread has become inactive for a while, at least by the standards of the frequency of other posts. I'm curious if others have found a solution, or we have all just resigned ourselves to wait for a firmware update to address this issue, which Apple has not acknowledged. This begs the question, if an issue is raised and apple publicly ignores it, is it an issue?...
