Android Mobile Data Draining Fast: Find the Cause

This is for the reader whose bundle disappears faster than their own habits explain, built on one cycle of readings off a Tecno Spark 40 running HiOS on Android 15. By the end you can read a per-app ranking, tell a live leak from an old record, and read a carrier's depletion rules instead of guessing. It does not cover Wi-Fi that drops, a battery that empties early, or storage that fills up.

Those exclusions live elsewhere: why an Android phone keeps dropping Wi-Fi, why an Android battery drains faster than you expect, and our Android fixes hub. How we test a phone carries the method behind each reading below.

What one cycle of readings looks like

Start with the ranking screen. Its dropdown prints the window as Sep 7 to Oct 6, and that window is one billing cycle.

A user entry sits above the apps at 6.25 MB, and the rows below it descend from Termux at 1.64 GB. The last row, X, is cut off at the bottom of the frame and shows no figure, so no number is claimed for it.

Open the top entry and the split appears. Termux reads Total 1.64 GB, Foreground 1.64 GB and Background 3.27 kB across the same window. Background data is switched on, Unrestricted data usage is switched on, and the status bar reads 0.00 KB/s while nothing is moving.

That split is what this post rests on. The drain was not a background sync, and no background switch was quietly blocking one either. A guide that opens by telling you to close background apps is describing a figure this phone never produced.

Sort the ranking, then open the top entry

Google's step list for stock Android reads Settings, then Network and internet, then SIMs, then App data usage. The same page warns that carriers measure usage differently and recommends checking with the carrier.

My Spark 40 reaches the same screen with the same fields. The search box inside Settings is the fallback when a skin renames the menus: search for data usage and open the result it returns.

One row then deserves its own sentence. Hotspot and tethering reads 420 MB, running to about a quarter of the top app's total. That bucket holds traffic shared with a tethered device, and no screen splits my browsing from a second device's downloads.

Data Saver does not touch the foreground

Data Saver is a background restriction, not a foreground throttle. Google's own documentation defines it as the control that decides which apps can access data in the background and which can access data only while in the foreground.

That page carries a last-updated stamp of 17 June 2026, dates the feature to Android 7.0, and tells makers not to whitelist apps. The exception list is therefore mine to choose.

The Data Saver screen on my Spark 40 states the same contract in its own words: Data Saver prevents some apps from sending or receiving data in the background, while an app I am using can still reach the network, though less often.

Battery Saver is the second switch that reads like a data control. The Power Saving screen on my Spark 40 says that background network status, location access and refresh rate will be restricted while it is on.

Auto-enable is also on at 30 percent, beside a 60Hz refresh-rate cap. Neither switch explains those figures, because the app that held the cycle held it with both on.

The switches that change real numbers

The switches below sit inside apps rather than inside Settings, and the paths are the ones their own vendors print.

Switch	Path	What it stops
WhatsApp auto-download	Settings, then Chats, then Media auto-download	Group media arriving on data. It fills storage too, so the storage guide covers that half
Google Photos backup	Photos settings, then Backup, then Mobile data usage	Uploads over data, including the Back up videos over data toggle
Instagram and Facebook	Account settings, then Data usage, then Use less cellular data; Settings & Privacy, then Media	Autoplay starting on a mobile connection
Play Store updates	Search Settings for Play Store	Unverified: no current Google help page prints this path

Airtel's FAQ prints the two social paths above. Google help pages for that row returned errors when checked, so the search is printed instead of a route.

The half of the bundle no app touches

The ranking explains the app side only. The rest runs on rules published on MTN's bundles page, which the phone never prints.

Rule	What the carrier's page prints
Bonus data	Unused bonus does not roll over, even when the bundle auto-renews
Order of use	With several bundles active, the one with the least validity is used first
Grace period	A bundle cannot be used in the grace period until it is renewed
Running out	Browsing continues from airtime at N3.07 per MB
Balance check	Text 2 to 323, or dial *323*4# for main and bonus, or *310#

That page carries a 2023 publication date and was modified in July 2026, so the rate above came from a maintained page. Opt-in for pay-as-you-go browsing is *312*200#, and the opt-out is *312*201#.

The arithmetic is worth doing once. N3.07 per MB is N3,143.68 per GB at 1,024 MB, while the 10 GB monthly bundle costs N4,500, which is N450 per GB. Browsing on airtime therefore costs just under seven times the bundle rate.

Airtel runs the same shape of rules. Its FAQ prints grace periods of 7 days for monthly plans, 3 days for weekly plans and 1 day for daily plans. Expired data cannot be used in the grace period unless the bundle is renewed.

Airtel also prints *323# for the expiry date beside the balance, and *400*1# to opt out of pay-as-you-go browsing.

If the audit and the bundle both add up

If the ranking looks clean and the rules above explain the rest, the next move is a complaint rather than a setting. The regulator's own FAQ sets the order.

Contact the provider first on its free short code: 9mobile reads 200, Airtel 111, Globacom 121 and MTN 180. Ask for a trouble ticket, because it records the time, date and nature of the complaint.

If the complaint misses the stated timeline, the same page gives the regulator's toll-free number as 622 and asks for the ticket number.

One caveat belongs with the ranking. Settings counts what the handset sent, while the carrier bills what its network counted.

The 40% figure, and the codes to avoid

A Nigerian tips page built around the NaijaVPN Data Saver app claims ad blocking saves up to 40 percent of a bundle. A quoted search for that claim returned two results, both the vendor's own pages, with no review, listing or method.

The same page prints balance codes that contradict both carriers: *131*1# for MTN and *140# for Airtel. Dial neither; the current channels are the ones above. Its Glo and 9mobile codes were dropped, since no carrier page was fetched to check them.

Seeing live use, which Settings cannot do

The ranking records the window; it is not a live view. It cannot say which app is pulling data right now, which is why a clean ranking still feels like a leak.

The status bar carries the live rate: 0.00 KB/s while idle, 253 KB/s on the Data Saver shot and 31.3 KB/s on the ranking shot. It covers the whole phone at once, so it names no app.

NetGuard is the on-device answer to that gap. It needs no root, it blocks each app on Wi-Fi and mobile separately, and its free tier records usage per application per address and can notify you when an app reaches the internet.

The traffic log is not free: NetGuard lists View traffic log under its Pro features, so per-connection inspection is a paid addition. Two costs stay visible: the app takes this phone's VPN slot, so no second VPN runs beside it, and it needs a battery optimisation exemption.

Any app you block should be opened and checked afterwards, because a blocked app fails quietly.

What I could not measure on the Tecno Spark 40

The negative result is the useful part: I could not reproduce an overnight drain on this phone. Data Saver was on, Battery Saver was on, background traffic for the app that dominated the cycle was 3.27 kB, and the drain still ran to 1.64 GB in the foreground. If your bundle empties overnight with nothing open, this phone does not show you the mechanism: read the carrier rules first.

Three limits stay stated rather than smoothed over. The HiOS build number was never photographed with these screens, so none is claimed. The 420 MB tethering row cannot be split between my traffic and a tethered device. No other skin was tested, so no other path is printed here.