Mobile Battery & Sustainable Technology Simulator

Active loads

Load level

Screen brightness 60%

CPU / background load 35%

Battery

Capacity 4000 mAh

Time scale 30 sim-min / s

Battery

–

Total draw

–

Runtime left

–

Elapsed

–

How it works

Every phone activity draws its own current, measured in milliamps (mA). Screen backlight, GPS fix acquisition, the cellular/Wi‑Fi radio and CPU background work each pull current independently, and the phone's baseline standby draw never stops. The simulator sums the currents of every active load into one instantaneous draw, then integrates that draw against the battery's rated capacity in milliamp‑hours (mAh) to deplete the charge over simulated time — exactly the accounting a real power‑management IC performs.

draw(mA) = base + screen(bright) + gps + radio + cpu(load)
d(charge_mAh)/dt(h) = −draw(mA)
runtime(h) = charge_mAh / draw(mA)

Screen — OLED backlight current scales roughly linearly with brightness, from ~120 mA dim to ~550 mA at full brightness.
GPS — acquiring and holding a satellite fix costs a steady ~130 mA regardless of brightness or load.
Radio/Network — the cellular or Wi‑Fi modem's transmit/receive cycle adds a fixed ~180 mA while data is flowing.
CPU / background — app refresh, sync and background processing scale from a light ~40 mA idle up to ~400 mA under heavy load.
Time scale — compresses simulated minutes into real seconds so a multi‑hour battery life plays out in view; runtime left is always the true physical estimate, independent of the time‑scale setting.

Real-world relevance: this is the same load‑accounting model behind a phone's battery‑usage breakdown and "time remaining" estimate — sustainable mobile design means trimming exactly these currents (dimmer screens, throttled background sync, coarser location) to stretch the same battery further.

Battery % Screen mA GPS mA Radio mA CPU mA