My experience with these things is that it is usually a bug in the firmware, and they usually show up after some automatic upgrade. Instead of committing to have their programmers take a deep look into the issue after a bunch of similar complaints, they have us try this, and try that, restart this, reset that. Companies NEVER admit (or even consider) that it would be a bug. One day, it will mysteriously be fixed, after a programmer discovers an issue. Nothing will ever be admitted though. A few more updates later, it will be some new issue that gets introduced.
I don't mean to be so cynical, but all complex devices have bugs of some kind. Some companies admit it and strive to fix them promptly, and some pretend it's at our end. All of us. The ones just using it.
In the old days, Steve Jobs himself thoroughly used the devices his company made. Strangely, the major bugs in their technology got fixed promptly. (Ok, there was that one time he said "you're holding it wrong...").
This is a fairly major bug, obviously affecting multiple people. We are just the ones that bother to come here. Most just restart it and put up with it. Just once I would like to hear this particular company to admit something and make a decision to get to the bottom of it.
Again, not trying to be cynical, but I have used a lot of technology form this company over the years, and have been through this before.
It's like the people with a bug in their website code. They ask you to delete your cookies (thus losing all your logons to every site), which actually does nothing to solve a bug on their side - but is on their list of things to say. Oh, and clear your cache too while you're at it.
It's always on the end of the customer, not the end of the company creating the product and the software within, right?
I get that you are fed up. I am too. We have learned that if we change the channel when this happens, then change back, it works for a while. I restart the device from time to time. I know that there will be a secret update one day.
We get that it can be difficult to track these issues down, but these companies need to take a proactive approach, and work to solve the issue, rather than work around it. Yes, restarting things often does get around a bug. But if programmers rely on this, then bugs won't get fixed.
If you doubt anything I say, remember that a programmer built some error-handling code, and assigned an error number to this particular situation, so that we would be able to report something. The programmer themself would probably be glad to have a look at fixing it - if they ever actually heard about it.
