New Phone Setup Audit: Establishing Your Device's Performance Baseline from Day One

There is a window of time, between unboxing a new phone and loading it with apps, accounts, widgets, and data, when the device is in its purest state. No background processes competing for the processor. No accumulated cache taking up storage. No battery wear from months of charge cycles. No forgotten apps holding memory. This is the device's factory-floor performance, and it will never be this fast again.

Most people rush through this window, eager to restore their backup, install their apps, and get back to normal. That is understandable, but it means they miss the single best opportunity to establish a performance baseline: a documented snapshot of the device's capabilities that serves as a reference point for every diagnostic you will ever run on this phone. When the device feels slow six months from now, you will not be guessing whether it was always this way. You will have data.

This guide walks through a setup audit using DeviceLab Spartan's 11 tools. The process takes about 30 minutes and produces a performance profile that works as your device's birth certificate: the reference document against which all future diagnostics are measured.

Before running any benchmarks, put the device in consistent testing conditions. Charge the phone to 100% and make sure Android's power-saving mode is off, since it can hold performance back. Remove any protective case so the device can shed heat freely. Close all open apps (on a new phone, that means finishing the setup wizard) and wait five minutes for the system to settle into idle.

Connect to WiFi and let the device complete any pending system updates. A phone running its initial firmware may not reflect the performance of the patched, updated system you will actually use daily. Once updates are installed and the device has rebooted, let it settle for another five minutes before beginning the audit.

Install DeviceLab Spartan (it is coming to Google Play). On a new device with few other apps, Spartan's own footprint is small, which keeps the testing environment as close to stock as you can get. It asks for no storage, media or 'all apps' permission. For this audit, grant Usage access when Spartan prompts you (Android handles it in Settings, not in a pop-up), so App Manager and Storage Analyzer can show full app sizes.

Open the Performance Suite in DeviceLab Spartan, tap Benchmark, and run it. It times six fixed workloads: SHA-256 hashing on one core, the same hashing on all cores, floating-point matrix math, a memory copy, and a sequential storage write and read. Each result comes back in real units (MB/s, or GFLOPS for the floating-point test) rather than an invented score. This first run is the most important measurement you will take on this device. Record every number: together they describe your hardware under ideal conditions.

Run the benchmark a second time immediately after the first completes, and compare. On a new, thermally stable device, the two runs should land close together. If the second run drops by more than about 10%, your device throttles quickly under load, which tells you how the phone will behave during sustained gaming, video editing, or other heavy tasks. While you're at it, check the Thermal Status line on System Status: it shows Android's own reading of how hard the device is working to manage heat.

Record both sets of results and note the difference. This thermal profile becomes part of your baseline. Six months from now, if the first run matches your original baseline but the second run drops more sharply, you have evidence that the device is handling heat worse than it used to, whether from dust, ageing components, or a case that restricts airflow.

Spartan does not save benchmark results, so take a screenshot of each results screen and keep it somewhere safe, such as cloud storage or an email to yourself. Those screenshots are the foundation of your device's performance record.

A new phone should have a battery in pristine condition, but "should" is not the same as "verified." Devices sometimes sit in warehouses or on retail shelves for months before purchase. If stored somewhere hot, the battery may already have aged before you opened the box. And some refurbished or open-box devices are sold as new with batteries that have already been through charge cycles.

Open DeviceLab Spartan's Battery Analyzer and note the health status Android reports (it should say "Good"), the voltage, and the temperature, which on an idle phone should sit close to room temperature. Then open Analytics: on Android 14 and later, if the battery reports it, you'll also see the charge cycle count. A truly new battery should show very few cycles. If a supposedly new-in-box device shows a meaningful number of cycles, ask the seller whether it was really factory-sealed.

Document these values. They form the battery section of your device's birth certificate. In six months, when you run the same checks, you will be able to compare health status, voltage at a similar charge level, and cycle count against day one, and see whether the battery's ageing looks normal or accelerated.

Manufacturers advertise storage and memory specifications, but the usable values are always lower than the headline numbers. Part of every phone's storage goes to the operating system, pre-installed apps and system partitions before you save a single photo. Part of its RAM goes to the kernel, system services and the manufacturer's own software before your apps get any.

DeviceLab Spartan shows the real numbers. Open System Status and record Storage Used and the space available on internal storage on the factory-fresh device, then open Storage Analyzer for the breakdown by category. This tells you how much space the system and pre-installed software take before you have installed anything. If a device advertises 128GB but shows only 100GB available at factory state, you know about 28GB is already spoken for, which is useful when choosing a storage tier on your next phone.

Do the same for memory. Device Info shows total RAM, and System Status shows memory in use and available memory. The gap on an idle, freshly set-up phone is the baseline overhead of the operating system and the manufacturer's customizations. Two phones with the same RAM on the spec sheet can leave you very different headroom depending on how heavy the manufacturer's skin is. No spec sheet tells you that, but it affects your daily experience.

The benchmark's storage results belong here too. Spartan measures sequential write and read speeds (the read can be helped by Android's file cache, and the app says so). Compare them with what reviews report for the same model. Spartan does not measure random I/O, so treat this as a rough check rather than a full storage test. If your sequential write speed is far below what other owners see, it is worth asking why.

Every Android manufacturer and carrier pre-installs applications, some useful, many not. These apps take storage, may run background services that use memory and processor time, and in some cases collect and transmit data. On a new device, before you have installed your own apps, App Manager gives a clear view of what the manufacturer put on your home screen.

Open DeviceLab Spartan's App Manager. It lists the apps you can open from your home screen with their size, version and install date, sorts by size, and filters system apps from user apps. Note which pre-installed apps are system apps (usually they can only be disabled, not uninstalled) and which you can remove. Tap any app to open its Android settings page, where you can disable or uninstall it. Disabled apps can't run in the background, so they stop costing you anything without needing root access. Pre-installed packages with no home-screen icon won't appear in App Manager; to see those, open Android Settings, go to Apps, and choose to show system apps.

Permissions are the second half of the audit, and Android handles that part itself. Open Settings and find the Permission manager (usually under Privacy, or Security and privacy). Pick a sensitive permission such as Contacts, Location, Camera or Microphone and look at which pre-installed apps are allowed to use it. Does the pre-installed weather widget really need your contacts? Does the manufacturer's file manager need the camera? Revoking permissions that pre-installed apps don't need is a privacy step most people never take, because they never look at what came on the device.

Write down or screenshot the list of pre-installed apps, their sizes, and the permissions you changed. That record shows what your device shipped with and helps if a manufacturer app misbehaves later. If a system update re-enables an app you disabled, which does happen, your original audit makes it easy to spot and disable again.

With benchmarks run, battery checked, storage and memory documented, and pre-installed apps reviewed, you now have a performance baseline. Gather your screenshots and notes into a single record. It should include: device model and Android version (from Device Info), benchmark results from both runs, battery readings (health status, voltage, temperature, and cycle count if your device reports it), storage used and available, total and available memory, sequential storage write and read speeds, and the pre-installed app list.

Store this record somewhere durable, such as cloud storage, email, or a folder on your computer. Label it with the device model and the date. This is the reference point for every future diagnostic. When your phone feels slow in eight months, run the same benchmarks and compare. A consistent drop in the CPU results, especially on the second run, points to heat. A large drop in storage write speed is worth investigating, starting with how full the storage is. A battery that has lost health faster than its cycle count would suggest may have been run hot.

This baseline also helps if you ever need warranty service. Day-one measurements next to current ones that show a clear decline give a service technician something concrete, far more persuasive than saying the phone "feels slower than it used to." Data replaces anecdotes, and DeviceLab Spartan provides the data.

Finally, set a calendar reminder to repeat this audit (minus the pre-installed app review) at three months, six months, and twelve months. Each checkpoint adds a data point. Over time, you build a long-term performance record that turns device ownership from reactive troubleshooting into informed, proactive care.