A smartphone can turn everyday motion, sound, light, and magnetic fields into measurable data. This practical physics lab tutorial explains which phone sensors are useful, how to collect and export readings, how to check calibration and limitations, and how to turn measurements into graphs, models, and defensible uncertainty estimates.
Overview
Smartphone physics experiments are most useful when the phone is treated as a measuring instrument rather than a magical source of precise answers. A device may contain an accelerometer, gyroscope, microphone, camera, magnetometer, ambient-light sensor, and other components. The exact sensor set, sampling rate, units, and access permissions vary by device and operating system, so check the selected app before designing the activity.
Start with a question that links a measurable quantity to a physics model. Examples include: How does the period of a pendulum depend on its length? Can a phone measure the frequency of a musical note? Does a rolling object have approximately constant acceleration down a slope? How does light intensity change with distance? Is the magnetic field near a small magnet stronger at shorter distances?
Record the phone model, app name and version if shown, sensor used, measurement units, sampling settings, orientation, experimental geometry, and environmental conditions. This information makes the experiment repeatable when a classmate uses a different phone or when an app interface changes.
| Sensor or tool | Experiment and measurable quantity | Physics topic | Likely error sources | Difficulty |
|---|---|---|---|---|
| Accelerometer | Acceleration of a lift, cart, swing, or phone on an incline | Newton’s laws, kinematics | Phone movement, gravity projection, vibration, sampling limits | Beginner to intermediate |
| Gyroscope | Angular speed during rotation or a pendulum’s motion | Rotation, angular kinematics | Sensor bias, drift, axis alignment, mounting movement | Intermediate |
| Microphone | Sound frequency, period, amplitude, or resonance | Waves and sound | Room noise, automatic gain, clipping, reflections | Beginner |
| Camera | Position versus time, wavelength spacing, or image brightness | Motion, optics | Frame rate, perspective, focus, exposure, rolling shutter | Beginner to intermediate |
| Magnetometer | Magnetic-field strength and direction near a magnet or current | Electromagnetism | Nearby metal, electronic interference, orientation, background field | Intermediate |
| Light sensor | Relative light level versus distance, angle, or material | Optics and inverse-square behavior | Room light, sensor range, reflections, automatic display changes | Beginner |
For background on units and scale checks, use the dimensional analysis guide. A smartphone result becomes much more meaningful when its units, expected scale, and physical interpretation are checked before fitting a curve.
Checklist by scenario
Motion with the accelerometer or camera
- Choose a repeatable motion, such as a phone resting on a cart, sliding down a shallow ramp, or moving in an elevator.
- Secure the phone with a case, tape, or a safe holder. Do not hold it loosely during motion.
- Decide whether the app reports raw acceleration, acceleration including gravity, or a processed value. Keep the phone orientation fixed.
- Collect several runs with the same starting position and record distance, mass, slope angle, or another independent variable.
- Plot acceleration against time. For a camera activity, mark the object’s position in successive frames and plot position against time.
- Compare the graph with a model. For approximately constant acceleration, a position-time curve may be fitted with x(t) = x0 + v0t + ½at2.
Keep the phone’s axes in mind: the accelerometer measures components along its device axes, not automatically the acceleration along the ramp. A free-body diagram can clarify which force and acceleration components should appear; see this step-by-step guide to free-body diagrams.
Pendulum timing with the microphone, camera, or accelerometer
- Use a small, safe pendulum with a clearly defined length from pivot to the object’s center of mass.
- Keep the starting angle modest if you want to compare the data with the simple relation T ≈ 2π√(L/g).
- Measure many cycles rather than one. Divide the total time by the number of cycles to reduce start-and-stop timing error.
- Repeat the measurement for several lengths and plot T2 against L. A roughly straight trend supports the model.
- Use the microphone to detect repeated impacts or the camera to track the bob. The accelerometer can work when the phone is securely attached, but its added mass may alter the motion.
Sound frequency with the microphone
- Use a tone source at a controlled distance and avoid loud levels that could overload the microphone.
- Record a short sample in a quiet room. Inspect the waveform or frequency spectrum if the app provides both.
- Estimate the period from repeated peaks, or identify the dominant frequency in the spectrum.
- Repeat with different tones and compare measured frequency with the source setting or a known musical reference.
- Check for harmonics: the strongest visible peak is not always the fundamental frequency.
Optics with the camera or light sensor
- Darken or control the room as much as practical and keep the light source, phone, and target geometry fixed.
- For an inverse-square investigation, measure relative light level at several distances from a small source. Treat the sensor reading as a relative quantity unless the app provides a calibrated unit.
- For diffraction or interference, use the camera to record a pattern and measure distances in pixels or against a scale placed in the same plane.
- Lock focus and exposure when possible. Automatic camera adjustments can change brightness between images.
- Plot the chosen quantity and state which assumptions make the comparison approximate.
For help distinguishing interference, diffraction, and polarization observations, consult this wave-phenomena comparison.
Magnetic-field mapping with the magnetometer
- Remove magnetic cases or accessories and keep the phone away from laptops, speakers, power supplies, steel furniture, and other magnets.
- Record the background reading before bringing the test magnet or current-carrying wire into position.
- Use a ruler or marked grid to measure distance, and keep the phone orientation constant at every point.
- Repeat each position and report the sensor component or magnitude used by the app.
- Compare the pattern qualitatively with the expected field geometry rather than assuming a simple law applies at every distance.
What to double-check
Calibration and sensor limits
Before collecting the main dataset, take a baseline reading while the phone is stationary. Rotate the device slowly and observe whether the displayed axes behave as expected. For timing experiments, compare the app’s timestamps with a known interval or use repeated cycles. Sensor readings may be filtered, rounded, delayed, or sampled at a rate that changes under device load. If the app does not disclose these details, describe the limitation instead of implying laboratory-grade precision.
Permissions also matter. An app may need access to the microphone, camera, motion sensors, or local storage. Grant only the permissions needed for the activity, and confirm that recording is stopped after data collection. Do not use a phone near water, high voltage, extreme heat, moving machinery, or strong equipment that could damage it.
Data export and plotting
Export the original readings before editing them. A comma-separated values file is convenient, but a screenshot can preserve settings and a short written log preserves context. Check the first rows for column names, time units, missing values, decimal separators, and whether the time column starts at zero. Plot raw data first; smoothing should be clearly labeled and should not hide outliers or sudden changes.
A spreadsheet is sufficient for many activities. For larger datasets, a scripting workflow can import the file, calculate averages, fit a model, and generate reproducible plots. The Python data-analysis tutorial provides a useful next step for importing measurements and fitting models.
Uncertainty and conclusions
Separate random variation from systematic effects. Repeated timing may vary because of starting and stopping, while a mismeasured pendulum length affects every trial in the same direction. Report the spread of repeated values, the resolution of rulers or timers, and any important calibration limitation. Do not give more significant figures than the instrument or method supports. For calculations involving several measured quantities, use the guidance in this uncertainty propagation resource.
A strong conclusion answers the original question, gives the measured trend, compares it with the model, and identifies the largest limitation. “The graph looked reasonable” is weaker than “The measured period increased with the square root of length within the uncertainty of the timing and length measurements.”
Common mistakes
- Assuming every phone has the same sensors. Check the device and app before promising a particular activity.
- Ignoring orientation. Accelerometer, gyroscope, and magnetometer components depend on how the phone is held.
- Confusing acceleration with force. An accelerometer reading is not automatically the net force; mass, gravity, and sensor convention must be considered.
- Using one trial. A single reading cannot show repeatability or reveal an accidental disturbance.
- Fitting before inspecting. Look for gaps, clipping, drift, transients, and outliers before choosing a model.
- Overtrusting app labels. “Sound level,” “light,” or “magnetic field” may be processed or relative quantities.
- Changing several variables at once. Keep geometry, distance, orientation, and source settings controlled while testing one relationship.
- Forgetting safety and privacy. Secure the phone, avoid hazardous setups, and stop recordings when the experiment ends.
For a complete write-up, organize the method, raw data, processed data, graphs, uncertainty, and conclusion using this reusable physics lab report template.
When to revisit
Use this checklist again before each new smartphone physics experiment, especially when changing phones, apps, operating systems, sensor settings, or classroom procedures. App menus, export options, permission prompts, supported sensors, and sampling controls can change, so verify them rather than relying on an old screenshot or remembered workflow.
Revisit the setup at the start of each school term or seasonal planning cycle. Confirm that the phone still exports complete timestamps, that the chosen sensor is available, and that any mounting equipment and power supplies are safe. If results suddenly differ from an earlier dataset, repeat the baseline test, check orientation and calibration, compare environmental conditions, and document the change.
Before acting, use this final checklist:
- State the question and predicted relationship.
- Identify the sensor, units, orientation, and sampling settings.
- Control the geometry and record independent variables.
- Collect repeated trials plus a baseline reading.
- Export and preserve the original data.
- Plot raw readings before filtering or fitting.
- Estimate uncertainty and check dimensions and scale.
- Write a conclusion that includes both evidence and limitations.
- Record the device, app, permissions, and workflow so the activity can be repeated or updated.