|
The extended timeframe that this has been happening is starting to make things lean away from it being an "issue that needs to be solved" and lean towards being "intentional behavior implemented by Amazon".
Has Amazon even acknowledged the problem yet, or have they remained silent on it? I would assume that someone has reported it to them. This is not something that I keep up with routinely, other than occasionally scanning this thread to see if there have been any updates. It's interesting to read about, but it doesn't affect me personally (100% in airplane mode, always).
|