New Controller Arrival Check: Drift, Buttons, Sticks & Battery Before the Return Window Closes

Disclosure: As an Amazon Associate, we earn from qualifying purchases.

A new controller can be faulty out of the box — drift from the factory, a sticky button, a trigger that does not reach full press, a battery that will not hold charge. The tragedy is not the fault; it is discovering it after the return window closes, when a free replacement becomes a warranty claim or a repair bill. This guide is the arrival checklist: what to test, in what order, on day one, so a fault is caught while returning it is still easy. It is arrival-led, not fault-led — the diagnose and fix guides own controllers that are already known to be faulty; this guide owns controllers that seem fine and might not be.

Step 1: unboxing inspection

Before powering on, inspect the box and controller: seals intact (or, for refurbished/open-box, condition as described), shell free of cracks and scratches, sticks straight and centred at rest (not visibly tilted or off-centre), buttons seated evenly, triggers moving freely, charging port clean and undamaged, and included accessories present (cable, dongle, caps, case as listed). Photograph anything unusual now — a photo taken on arrival day is far more persuasive for a return than a description written weeks later. Keep the box and receipt until the check is complete.

Step 2: the dead-zone drift check

Connect the controller, open a dead-zone viewer or the platform’s calibration display, and leave both sticks untouched. Either stick reporting off-centre at rest is drift — on a brand-new controller, that is a return, not a repair project. Do not “fix” new-controller drift with a larger dead zone and keep the pad: a dead zone masks drift, and masked drift on day one is drift you have accepted as your problem. Rotate each stick slowly through its full range and watch for jumps, spikes, or sections where the reported position jumps rather than moving smoothly. Flick each stick and confirm it snaps back to centre cleanly. The dead-zone guide explains what the viewer shows and what a drift reading detects. A clean arrival check is not a drift-free guarantee — drift can develop later, especially on potentiometer sticks — but a failed arrival check is a certain return, and that certainty is worth having on day one.

Step 3: button, trigger, and paddle sweep

Press every input once and confirm each registers and releases cleanly in a game or input viewer: face buttons, D-pad (including diagonals), bumpers, triggers (slow pull for smooth analogue rise, fast pulls for consistent full press), stick clicks, and any paddles or back buttons. Test trigger stops in both positions if fitted. Test rumble in a game that uses it, and confirm both motors (where fitted) respond. Test the headphone jack if you use one, and any mute or function buttons. A single dead input on arrival day is a return — do not accept “it might loosen up” for an electronic fault.

Step 4: wireless, range, and battery first-charge behaviour

Pair the controller by its intended wireless method (Bluetooth or dongle) and play wirelessly at your normal play distance, including through whatever furniture sits between you and the console or PC. Note any drops, stutter, or pairing difficulty — a controller that only works at short range on day one will not improve. Then check first-charge behaviour: charge fully, note whether charging completes normally and the indicator behaves as documented, then play wirelessly and note whether battery behaviour seems plausible for a session (you are checking for a gross fault — dying in minutes — not measuring exact battery life, which needs controlled conditions). For AA pads, check the battery compartment for clean contacts and a secure door. For dock-charged pads, check the dock seats the controller correctly and charges reliably.

Step 5: record and decide

Write down the check date, the results (pass, or which check failed and how), and the return deadline. If everything passes, keep the record anyway — it establishes a baseline if drift or faults develop later, and it supports a warranty claim with a dated “was fine on arrival” note. If anything fails, return or exchange now, with the check evidence (viewer screenshot, fault description, arrival photos) included. Do not start a DIY repair on a new controller inside its return window: a repair attempt can complicate a return that would otherwise be simple, and a new controller’s fault is the seller’s problem, not yours.

If a check fails and you are unsure whether it is a fault or a settings issue, the DualSense diagnosis guide (for DualSense pads) or the general diagnose guidance will help you distinguish — but do not let diagnosis eat the return window. When in doubt on a new pad, exchange first and diagnose later: an exchange costs nothing, and a missed window costs a controller.

The checks people skip (and regret skipping)

Three checks cause the most post-window regret. The second-day check: some faults — a stick that drifts only after warming up, a battery that fades faster than expected, a button that sticks only occasionally — do not show in a first-hour test. Repeat the dead-zone check and the button sweep after a few real play sessions, still inside the return window, not just on arrival day. The game check: a controller can pass an input viewer yet misbehave in a specific game (a trigger range a game reads differently, a vibration pattern that rattles). Play at least one real game from each genre you actually play before the window closes, not just a viewer. The accessory check: if you bought a dock, case, or caps with the controller, test them with this controller now — a dock that does not seat this exact variant, or caps that interfere with stick travel, are return-window discoveries too, and they are easy to miss when the controller itself passes. A return window is a testing period, not an unboxing period: use all of it.

[AFFILIATE LINK: controller carrying case] · [AFFILIATE LINK: thumbstick caps set]

Related: Dead-zone calibration guide · DualSense drift diagnosis guide · Community Drift Tracker