Mega888 Works Until I Receive a Phone Call—Why Does Mobile Multitasking Change Things?

The session that was going exactly right

There is a particular kind of focus that happens about twenty minutes into a session. The interface stops being something you read and becomes something you feel. Your thumb knows where it is going before your eye does. The pacing settles. You are not thinking about the phone at all any more, which is precisely the point — the device has disappeared and only the game is left.

Then the screen changes owner.

A name appears across the top. The audio cuts. The whole surface you were working on slides away and something else takes its place. Ten seconds later you are back, and something is subtly wrong. The round did not resume where you left it. The balance took a moment to reappear. Sometimes you are looking at a login screen that you were not looking at before.

It is tempting to read that as the app failing you. It is a more useful story than that, and a more hopeful one, because what actually happened in those ten seconds was not one failure. It was three separate systems all reacting correctly at the same moment — and once you can see all three, most of what frustrated you turns out to be something you can design around.

Then the screen changes owner

The first thing that happens is the one you can see, and it is governed by rules that are written down publicly.

When a call arrives, Android does not ask the app's permission. It tells it. The system calls onPause, which Google's own documentation describes as "the first indication that the user is leaving your activity, though it does not always mean the activity is being destroyed." Moments later, when the call screen has fully covered the app, onStop fires — the documentation puts it plainly: "When your activity is no longer visible to the user, it enters the Stopped state."

So far, so recoverable. In the Stopped state the app is still sitting in memory with everything intact. But this is where the exposure begins, and the documentation is unusually direct about it. "The system kills processes when it needs to free up RAM," it says — and critically, "the system never kills an activity directly to free up memory. Instead, it kills the process the activity runs in, destroying not only the activity but everything else running in the process as well."

Android publishes a ranking of what gets killed first. An app in the foreground has the lowest likelihood. An app that is visible but unfocused is low. An app that is in the background and invisible — exactly where your session goes the moment the call screen covers it — is rated higher. The documentation states the consequence without softening it: "the system can destroy your application's process while the user is away and your activity is stopped."

That is the first handover. Your session did not crash. It was moved to the back of a queue, and on a phone that is already short on memory, the back of the queue is not a safe place to stand.

The second handover happens where you cannot see it at all

Here is the part almost nobody accounts for, and it is the reason two people on the same app in the same room can have completely different experiences of the same interruption.

Your voice call and your data do not necessarily share a lane.

On networks using Circuit-Switched Fallback — the arrangement where a 4G phone drops to an older network to carry a voice call — researchers measuring operational LTE networks found that the data session does not merely slow down. It stops. In their measurements, transmission was suspended for an average of 6.4 seconds on TCP and 5.4 seconds on UDP, with one logged example showing a 6.4-second gap followed by a second 1.5-second gap as the handover completed. Throughput during calls fell by around a third in typical runs — 14 Mbps down to 9 Mbps on one operator — and in the worst case they recorded a drop of 83.4%.

Recovery is not instant either, and the reason is almost poetic. TCP interprets silence as congestion, so during the outage its retransmission timeout doubled repeatedly, climbing from 0.436 seconds to 6.976 seconds. By the time the data path came back, the connection had taught itself to wait. The network was ready before the protocol was.

And occasionally the phone simply does not come home. The same study found cases where a handset stayed on the older network after the call ended — in one test, for more than ten hours.

This matters enormously in Malaysia specifically, because of where our networks are. Under the JENDELA programme the 3G network has been sunset, and reporting at the time noted the practical consequence for subscribers: a 4G phone without VoLTE enabled has to fall back to 2G to carry a voice call. On 2G, data is not slow. It is effectively gone for the duration.

So the question "why does my session break when someone calls me" has a different answer depending on one setting buried in your phone. If VoLTE is on and your carrier supports it, voice and data ride together and the interruption is mostly cosmetic. If it is off, your data takes a trip to a slower network and back, and the app has to survive the silence.

The third handover: something on the other side has been counting

While the operating system is reshuffling and the radio is renegotiating, there is a third party in this story that has no idea a call is happening: the server.

A live session is a conversation with an expectation of rhythm. The server holds your session open on the assumption that you are still there, and it knows you are still there because your device keeps saying so. When the device goes quiet — because the app was backgrounded, or because the radio handed off, or both — the server is left listening to nothing. It cannot distinguish a ten-second phone call from a phone that fell in a drain.

So it does the responsible thing and closes the session. That is not the platform being difficult with you. A session that stayed open indefinitely on an unresponsive device would be a genuine security problem, and the same timeout that occasionally re-prompts you for a login is the one protecting your account when you leave your phone on a mamak table.

This is also the natural point to say the quiet thing out loud: an interruption is information. If a call pulls you out and you find yourself irritated at a ten-second gap, that irritation is worth noticing more than it is worth solving. The strongest sessions are the ones you can walk away from. Set a time before you start, treat the interruption as the end of a stretch rather than an obstacle to it, and come back later with the same clear head you had twenty minutes in. Playing within a budget you decided in advance is not a limitation on the experience. It is the thing that keeps it an experience.

The turning point: it was never one failure

Once you can name all three handovers, the frustration reorganises itself into something far more manageable.

It was never the app being unreliable. It was the operating system correctly deprioritising an invisible process, the radio correctly carrying your voice at the expense of your data, and the server correctly protecting an account it could no longer hear from. Three systems, three reasonable decisions, one bad ten seconds.

And every one of those three has a lever on it.

Building a session that survives the interruption

Start with the radio, because it is the single highest-leverage fix and it takes under a minute. Find VoLTE in your phone's network settings and turn it on. If the option is missing, check with your carrier whether your plan and handset support it. This is the difference between a call that costs you a flicker and a call that costs you the connection entirely.

Then take pressure off the memory ranking. The reason Android reaches for background processes is that it needs RAM, so the fewer apps stacked up behind yours, the less likely yours is the one that gets reclaimed. Clear the recents list before a session rather than after. On devices with aggressive battery management, exempt the app from the most restrictive power-saving modes, because those settings exist specifically to make backgrounded apps easier to kill.

Then give the connection the best ground to stand on. A stable Wi-Fi connection behaves very differently from a cellular one during a voice call, because on Wi-Fi the call and the data are not competing for the same radio path at all. If you know a call is likely — you are expecting one, or it is the hour when they come — that choice alone removes the second handover from the story entirely.

And then stop fighting the third one. Treat the login prompt as a feature rather than an insult. Keep your credentials somewhere you can retrieve them in five seconds instead of fifty, so that a timeout costs you a moment rather than a mood.

What changes when you stop fighting the interruption

The interesting shift here is not technical. It is that a phone call stops feeling like something being taken from you.

Your phone is not a console. It is a device whose entire design assumes that the most important thing happening on it might arrive at any second from someone else, and every behaviour described above — the backgrounding, the radio handover, the session timeout — exists because the phone is doing what a phone is for. The call is not interrupting the device's real job. The call is the device's real job.

Once you set it up with that in mind, the ten seconds stop being a break in the session and become a pause in it. You come back, the state is where you left it, and the focus you had twenty minutes in is still waiting for you.

That is a better place to play from anyway.

Why does Mega888 ask me to log in again after a phone call?

Because the server stopped hearing from your device. While the app is backgrounded and the radio is handing off, nothing is reaching the session from your side, and a live session that goes silent is closed as a security measure. It is the same protection that secures your account if you leave your phone somewhere.

Will turning on VoLTE actually fix this?

It fixes the radio half of the problem, which is often the biggest half. VoLTE lets voice and data run together rather than forcing your phone onto an older network for the duration of the call. Without it, a 4G phone in Malaysia falls back to 2G to carry voice, where data effectively stops. It will not stop Android from backgrounding the app, but it removes the data outage underneath it.

Why does it work fine for my friend but not for me?

Almost always a difference in one of three things: whether VoLTE is enabled on that handset and plan, how much free RAM the device has when the call lands, and whether the connection is Wi-Fi or cellular. Same app, same call, three different sets of conditions.

Does Wi-Fi really make a difference during a call?

Yes, and for a structural reason rather than a speed one. On Wi-Fi your data is not travelling over the cellular radio that the voice call needs, so the two never compete. The handover that causes the multi-second data gap simply does not happen.

How long should the interruption actually last?

On a network using circuit-switched fallback, measurements on live LTE networks found data suspensions averaging around five to six seconds, with recovery typically another two to four seconds after the call ends. If yours regularly runs far longer than that, the problem is more likely memory pressure on the device or an unstable connection than the call itself.