Troubleshooting and Security Hardware

Methodology and Physical Safeguards

Applying the A+ troubleshooting methodology to common mobile device issues and identifying the physical and biometric hardware features that keep them secure.
Author

Chuck Nelson

Published

November 16, 2025

1 Purpose

When a mobile device fails, a technician needs a logical and repeatable process to find the root cause. This document introduces how to apply the standard A+ troubleshooting methodology to common mobile device symptoms. It also covers the physical and biometric hardware features designed to protect the device and its data from unauthorized access.

2 What You’ll Accomplish

By the end of this reading, you will be able to:

  • List the six steps of the CompTIA A+ troubleshooting methodology.
  • Apply the troubleshooting methodology to common mobile device symptoms like poor battery life or failed connectivity.
  • Identify common hardware security features, such as biometric scanners and physical lock slots.

This reading maps to the following program and course learning outcomes:

  • Course Learning Outcomes (CLOs):
    • 3. Troubleshoot hardware and basic network components: This document is focused on the core process of troubleshooting and identifying security-related hardware.

This exercise develops the following skills, which align with the O*NET SOC Code 15-1232.00 for Computer User Support Specialists.

Learning Objective O*NET KSAs Technologies Used
Apply the A+ troubleshooting methodology. Knowledge: Customer and Personal Service
Skills: Troubleshooting, Critical Thinking		 A+ Methodology
Diagnose common mobile device symptoms. Knowledge: Computers & Electronics, Telecommunications
Skills: Systems Analysis		 upower, nmcli
Identify hardware security features. Knowledge: Public Safety and Security
Abilities: None		 Biometrics, Kensington Lock

3 The A+ Troubleshooting Methodology

A structured approach is always more effective than random guessing. The CompTIA A+ methodology provides a six-step framework for any IT problem.

  1. Identify the problem: Question the user and gather information. Identify all symptoms.
  2. Establish a theory of probable cause: Start with the simplest and most obvious potential causes.
  3. Test the theory to determine cause: If the theory is confirmed, move to the next step. If not, establish a new theory.
  4. Establish a plan of action to resolve the problem and implement the solution.
  5. Verify full system functionality and, if applicable, implement preventative measures.
  6. Document findings, actions, and outcomes.

4 Applying the Methodology to Mobile Issues

Let’s apply this framework to a couple of common scenarios that can be diagnosed using the tools in your Fedora VM.

4.1 Scenario 1: “My battery drains too fast.”

  • 1. Identify: A user reports their laptop battery life has recently become much shorter.
  • 2. Theory:
    • Theory A: The battery is old and has degraded.
    • Theory B: A software process is stuck and using excessive CPU.
    • Theory C: The system is stuck in the “Performance” power profile.
  • 3. Test:
    • Test A: Use upower -i /org/freedesktop/UPower/devices/battery_BAT0 and check the capacity percentage. A low value (e.g., below 80%) indicates significant degradation.
    • Test B: Use the top command to see if any process is consistently using a high percentage of the CPU.
    • Test C: Use powerprofilesctl get to see if the active profile is performance.
  • 4. Plan:
    • If Test A is the cause, the plan is to recommend a battery replacement.
    • If Test B is the cause, the plan is to kill the rogue process and investigate why it got stuck.
    • If Test C is the cause, the plan is to use powerprofilesctl set balanced to return to a normal power profile.
  • 5. Verify: After implementing the fix, use the device and see if battery life improves.
  • 6. Document: Note the cause (e.g., “High CPU usage from ‘stuck_process’”) and the solution.

4.2 Scenario 2: “I can’t connect to the Wi-Fi.”

  • 1. Identify: A user’s laptop cannot access any websites. The Wi-Fi icon indicates it is disconnected.
  • 2. Theory:
    • Theory A: The Wi-Fi radio has been accidentally turned off by a physical switch or software setting.
    • Theory B: The device is out of range of any known access points.
  • 3. Test:
    • Test A: Run nmcli radio wifi to see if the hardware is enabled.
    • Test B: Run nmcli device wifi list to see if any networks are visible and what their signal strength is.
  • 4. Plan:
    • If Test A is the cause, the plan is to run nmcli radio wifi on.
    • If Test B is the cause, the plan is to advise the user to move closer to their router.
  • 5. Verify: Attempt to connect to the network.
  • 6. Document: Note the cause (e.g., “Wi-Fi radio was disabled in software”) and the solution.

5 Hardware Security Features

Beyond software, mobile devices have physical features to protect them.

  • Biometric Authentication:
    • Fingerprint Readers: Scanners (often on the power button or under the screen) that grant access based on a unique fingerprint.
    • Facial Recognition: Uses infrared cameras and dot projectors (like Apple’s Face ID) to create a 3D map of a face for secure authentication.
  • Physical Security:
    • Kensington Lock Slot: A small, reinforced hole found on most laptops. A special cable lock can be attached to secure the laptop to a desk, preventing physical theft.
    • Privacy Shutters: A small physical slider that covers the webcam, providing a guaranteed way to know the camera is not active.
    • Microphone Mute Keys: A dedicated key on some laptops that electronically disconnects the microphone at the hardware level.

6 Reflect and Review

ImportantReflection: 3-2-1

Now that you have reviewed this document, take a moment to reflect on your learning in your Microsoft Teams Student Notebook:

  • 3 of the six steps in the A+ troubleshooting methodology.
  • 2 different hardware security features you might find on a laptop.
  • 1 question you still have about diagnosing mobile device issues.
TipCheck on Learning

Answer these questions in your notebook to solidify your understanding:

  1. What is the first step in the A+ troubleshooting methodology?
  2. A user reports their laptop feels “puffy” and the keyboard is bulging. What is the most likely and most dangerous cause?
  3. You suspect a rogue application is draining your battery. What command-line tool could you use to check for processes with high CPU usage?
  4. What is the purpose of a Kensington Lock slot?
  5. You run nmcli device wifi list and see no networks listed. What are two possible theories for the cause of this problem?
Back to top