Study guide

Mobile OS & Application Troubleshooting

CompTIA A+ 220-1201 & 220-1202

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

About the CompTIA A+ Certification Exam Domains & Study Strategy

2 Core 1 Domain 1: Mobile Devices (13%)

Laptop Hardware & Components Laptop Features & Display Types Mobile Device Connectivity & Accessories Mobile Operating System Features Mobile Device Synchronization & Data Transfer

3 Core 1 Domain 2: Networking (23%)

TCP/IP Fundamentals & the OSI Model Common Ports & Protocols Wireless Networking Standards Network Hardware & Devices Network Configuration & Internet Connections Network Types & Topologies

4 Core 1 Domain 3: Hardware (25%)

Cables & Connectors RAM Types & Storage Devices Motherboards, CPUs & Power Supplies Printers & Multifunction Devices Peripheral Devices & Expansion Cards Network Cable Tools & Testing

5 Core 1 Domain 4: Virtualization & Cloud Computing (11%)

Virtualization Concepts Cloud Computing Models & Services Client-Side Virtualization in Practice

6 Core 1 Domain 5: Hardware & Network Troubleshooting (28%)

CompTIA Troubleshooting Methodology Hardware Troubleshooting Network Troubleshooting Printer Troubleshooting Display & Mobile Device Troubleshooting

7 Core 2 Domain 1: Operating Systems (28%)

Windows Editions & Features Windows Administrative Tools & Utilities Windows Command Line & PowerShell macOS & Linux Basics Windows Networking & File Sharing Windows Installation & Upgrade Methods

8 Core 2 Domain 2: Security (28%)

Physical & Logical Security Measures Malware Types & Threat Mitigation Wireless & Network Security Encryption & Data Protection

9 Core 2 Domain 3: Software Troubleshooting (23%)

Windows OS Troubleshooting Mobile OS & Application Troubleshooting Browser & Application Troubleshooting

10 Core 2 Domain 4: Operational Procedures (21%)

Documentation & Change Management Backup & Recovery Methods Safety & Environmental Procedures Scripting & Remote Access Technologies Privacy, Licensing & Organizational Policies

Mobile OS & Application Troubleshooting

Key Takeaways Explain This Topic AI

Diagnose short battery life by reading per-app battery usage in Settings before replacing anything; rogue apps, max brightness, weak signal, and a degraded battery (health below ~80%) are the usual culprits.

App crashes follow an escalating order: force stop → clear cache → update → clear data → reinstall → update OS ; only escalate to factory reset after a backup.

A swollen or extremely hot battery is a fire hazard — stop charging, power down, and replace it; never puncture a lithium-ion battery.

Mobile connectivity fixes escalate from toggling airplane mode , to forget/re-add network , to reset network settings , then check APN and carrier status for cellular.

A lost or stolen managed device is contained through Mobile Device Management (MDM) or Find My to remotely lock or wipe — speed matters because data exposure grows every minute.

Last updated: October 2026

  • Battery, Heat, and Storage
  • Battery Drain

CompTIA wants a diagnose-before-replace mindset. Both iOS ( Settings → Battery ) and Android ( Settings → Battery → Battery usage ) break consumption down per app over 24 hours or several days — read that screen first. A single app at the top of the list is the lead suspect.

  • Cause Fix
  • Screen brightness maxed Enable auto-brightness, lower manual level
  • Rogue/background app Force stop or uninstall the top battery consumer
  • Background App Refresh / push sync Disable for non-essential apps, lengthen fetch interval
  • Weak cellular signal Phone burns power hunting for signal — connect to Wi-Fi
  • Location "Always" Set most apps to "While Using"
  • Degraded battery Check Battery Health; replace if maximum capacity is below ~80%
  • Overheating and Battery Safety

Lithium-ion cells should operate roughly 0–35 °C (32–95 °F) . Sustained heat both drains and ages the battery. Causes: resource-heavy apps (3D games, AR, sustained 4K recording), charging during heavy use, direct sun, or malware running hidden background processes.

Safety rule: A swollen battery or a phone that becomes painfully hot is a genuine fire and rupture hazard . Stop using it, unplug it, power it down, and replace the battery. Never puncture, bend, or keep charging a swollen lithium-ion battery.

Storage Exhaustion

  • Symptom Fix
  • "Storage full" warning Settings → Storage to find the largest apps/files
  • Cannot install or update apps Clear app caches, delete unused apps
  • Photos/videos dominate space Enable cloud backup (iCloud/Google Photos), remove local copies
  • App data ballooning Clear cache (Android: App info → Storage → Clear cache)

Clearing cache keeps your logins and settings; clearing data resets the app to first-launch state, so try cache first.

Application Troubleshooting Ladder

When a mobile app crashes, freezes, or refuses to open, follow a least-disruptive-first escalation. Memorize this order — the exam frequently asks for the next step after one you have already done.

  • Step Action Why / Cost
  • 1 Force stop the app Clears a hung process; zero data loss
  • 2 Clear cache Removes corrupt temp files; keeps settings/logins
  • 3 Update the app A known bug may already be patched
  • 4 Clear data Resets app to fresh state; loses in-app settings
  • 5 Uninstall and reinstall Replaces corrupt program files
  • 6 Update the OS App may require a newer iOS/Android version
  • 7 Factory reset Last resort — back up first
  • App Will Not Install

Confirm free storage (a download plus install needs roughly double the app's size).

Verify connectivity — switch between Wi-Fi and cellular to isolate a network block.

Check the OS version meets the app's minimum requirement.

Clear the App Store / Play Store cache and retry.

On Android, sideloading requires "Install unknown apps" to be enabled per source — but enabling it broadly is a security risk and a common exam "wrong" answer.

Performance and "App Spell" Symptoms

Random reboots, rapid battery drain, surprise pop-up ads, and unexpected data usage frequently signal malware rather than a hardware fault. Check per-app data usage , review recently installed apps, remove anything unfamiliar, and run a reputable mobile security scan before suspecting the hardware.

  • Connectivity and Mobile Security
  • Wi-Fi, Bluetooth, and Cellular

Most wireless faults resolve with an escalation from quick toggles to a full network reset.

  • Layer Problem Fix
  • Wi-Fi "Connected, no internet" Forget the network and reconnect; verify the router works for other devices
  • Wi-Fi Slow or dropping Move closer to the access point, switch to the 5 GHz band, avoid 2.4 GHz interference
  • Bluetooth Paired but won't connect Remove the pairing and re-pair; restart Bluetooth on both ends
  • Bluetooth Audio cutting out Reduce distance/obstacles; 2.4 GHz Wi-Fi and microwaves cause interference
  • Cellular No signal Check airplane mode, reseat the SIM/eSIM, restart
  • Cellular No mobile data Verify cellular data is on and the Access Point Name (APN) is correct

The universal escalation for stubborn wireless issues is: toggle airplane mode → forget/re-add the network → Reset Network Settings (which clears saved Wi-Fi passwords, VPNs, and APN, so warn the user first).

Mobile Security Triage

  • Issue Response
  • Device lost or stolen Use MDM or Find My to remotely lock then wipe ; act immediately
  • Apps you did not install Scan for malware; remove unknown apps; disable "install unknown apps"
  • Constant pop-up ads Uninstall recently added apps; check browser extensions
  • Unexpected data usage Inspect per-app data; restrict background data on suspicious apps
  • Account compromised Change passwords, enable multi-factor authentication (MFA) , review active sessions

High-security mobile signs (exam-named): leaked files/data, unauthorized account or location access , excessive resource consumption , signal/data anomalies, and high (unexpected) network traffic . A managed (BYOD or corporate) device is contained through MDM enforcement of encryption, screen lock, and remote wipe — not by waiting for the user to find it.