So I pull the phone out of my pocket, I hit the "phone" icon. And I can hear the damn crickets. Nothing for a few seconds. Then the phone appears. And it's a bit laggy. I push a number and it hesitates, and so on.
I understand this is a robust operating system, and it's often busy doing things in the background, not to mention the apps and widgets that may be downloading stuff at any given moment.
I'm not an expert, but I think if I were the one who designed the Android system, I would have establish some app precedence/priority system. For instance, if I try to start a game, the system might say, "Get in line. I'm in the middle of something," and put that in the queue.
But if I press the phone icon, it would recognize it as an essential app and important request, HALT everything else and interrupt all updates, and make sure the damn phone app is up and running, and impose a temporary freeze on all resources to go on standby.
Same goes for when I'm receiving a call. It takes a second sometimes to respond to the unlock swipe.
I understand this is a robust operating system, and it's often busy doing things in the background, not to mention the apps and widgets that may be downloading stuff at any given moment.
I'm not an expert, but I think if I were the one who designed the Android system, I would have establish some app precedence/priority system. For instance, if I try to start a game, the system might say, "Get in line. I'm in the middle of something," and put that in the queue.
But if I press the phone icon, it would recognize it as an essential app and important request, HALT everything else and interrupt all updates, and make sure the damn phone app is up and running, and impose a temporary freeze on all resources to go on standby.
Same goes for when I'm receiving a call. It takes a second sometimes to respond to the unlock swipe.
