I’m telling you, it was never fixed. I don’t see a single person here who said it was fixed for them. Can you show where Apple said or did anything about this?
After multiple attempts with Apple support including wiping/reinstalling my phone to factory default settings and no improvement, I gave up and dropped $1,400 for a new iPhone. What could I do? My phone was broken, I needed a working phone, and it’s been 6 months without even an acknowledgement or statement from Apple that I’ve seen.
Support gave me that Apple customer feedback page you gave. That page has got to receive a million messages from crackpots with user errors. It does not look very promising that anyone important enough in Apple would ever see the message, nor would you know if they had or hadn’t. It was disappointing that there didn’t seem to be any route for Apple support to escalate repeated chronic problems to higher tiers that could consider software update flaws.
At least two threads about camera problems and camera “black screens” after IOS 14 updates were created on 9/17/2020 — the day after the release of IOS 14 on 9/16/2020.
Apple threads 251802549 and 251803518, for example, show 6800 and 1400 “Me Too” clicks in those articles. What kind of problem could have caused cameras to become non-responsive (with a black screen) on that many iPhones in such a relatively short period of time, coinciding with IOS 14.x update releases?
On my phone, if you hold any photo button down long enough, it will eventually take the photo, suggesting it’s really a performance problem. I also noticed that once the the haptics — the vibration of the iPhone 7 fake home button — stopped working until the next reboot. It behaves like perhaps an issue with a memory leak or resources being consumed and not released.
For me, these problems started around the time the IOS update changed the setting so that inbound call notifications now appear as a banner instead of full screen. I’ve read that this banner feature was first added with IOS 14, but IOS 14.3 or 14.4 seems to have changed the default setting on my phone to the new banner, coinciding with the problems.
My problems didn’t start until around February-ish, so my hunch is that some people were affected starting with 14.0 and others like me perhaps not until 14.3 or 14.4. If the problem is a coding flaw, perhaps the problem code was added in 14.0 but settings or other variable factors could cause the problem to only become noticeable later.