You are doing typical smartphone stuff like surfing, playing a game, etc., when for no unforeseen reason, the phone stops responding. Touch positions are locked in place, hardware buttons don't respond (even the power button), no control at all. Plenty of free ram, no physical damage, no rhyme or reason to it, just happens.
Then, after anywhere from 10 seconds to 16 hours (literally), everything back to normal, and all prior input is now taking effect (destroys my gameplay on Vice City and San Andreas). The best part being that the closest to reproducing this problem is "anytime the device is powered on".
Nothing eliminates the issue. I have done a factory-reset, tried voodoo, prayer, threatening it with a hammer, using The ForceĀ®, even reconfiguring the dual-hetrodyne plasma phase inducer coupling for quantum-warp capabilities while retuning the hysteresis-curve in the matter-transducing earth modulator for hyper-space travel, yet it persists.
I'm pretty sure this is a hardware problem, or perhaps most notably the interaction with the Lollipop OS which, like all Androids, was and never will be bug-fixed because Google is too busy making higher versions that will never be updated.
I want to see if it is just me with all the luck, or if there is a pattern of this happening with other devices as well.
Currently on an Alcatel One-Touch 5020n, Android 4.1.2, soon to be fuel for my fusion reactor core...
Then, after anywhere from 10 seconds to 16 hours (literally), everything back to normal, and all prior input is now taking effect (destroys my gameplay on Vice City and San Andreas). The best part being that the closest to reproducing this problem is "anytime the device is powered on".
Nothing eliminates the issue. I have done a factory-reset, tried voodoo, prayer, threatening it with a hammer, using The ForceĀ®, even reconfiguring the dual-hetrodyne plasma phase inducer coupling for quantum-warp capabilities while retuning the hysteresis-curve in the matter-transducing earth modulator for hyper-space travel, yet it persists.
I'm pretty sure this is a hardware problem, or perhaps most notably the interaction with the Lollipop OS which, like all Androids, was and never will be bug-fixed because Google is too busy making higher versions that will never be updated.
I want to see if it is just me with all the luck, or if there is a pattern of this happening with other devices as well.
Currently on an Alcatel One-Touch 5020n, Android 4.1.2, soon to be fuel for my fusion reactor core...


Comment