# Mobile Operating Systems: iOS and Android

> Chapter 30 of the Courseiva A-PLUS-CORE-1 curriculum — https://courseiva.com/learn/a-plus-core-1/mobile-os-types

**Official objective:** 1.2 — Mobile Devices

## Introduction

Supporting diverse mobile environments requires knowledge of both iOS and Android—the two dominant operating systems tested on the CompTIA A+ 220-1101 exam. Mobile devices are a core domain, and knowledge of OS features, security, and management is essential. Approximately 15-20% of exam questions touch on mobile devices, with several specifically addressing OS differences, configuration, and troubleshooting. Mastering this chapter will help you differentiate between iOS and Android for exam scenarios and real-world support.

## iOS and Android as Two Different Operating Systems

Two large office buildings, each with a distinct management philosophy, present a striking contrast. Building A (iOS) is a tightly controlled environment. The building manager (Apple) owns the entire structure, including all the rooms, hallways, and utilities. Tenants (users) can only use approved furniture and appliances that have been pre-tested by the manager. If a tenant wants to install a new coffee machine, they must request it from the manager, who will install it themselves. The manager also has a master key to every room and can remotely disable any appliance that violates policy. This ensures a consistent, secure experience but limits tenant freedom. Building B (Android) is a more open complex. The building owner (Google) provides the basic structure and utilities, but tenants can bring their own furniture, install any appliance, and even modify the walls (within reason). Different floors may have different rules set by the floor manager (device manufacturer). Tenants can install apps from multiple stores, not just the official one. This offers flexibility and choice but can lead to security issues if a tenant installs a faulty appliance. In both buildings, tenants can use apps (like using a room for a specific purpose), but the level of control and customization differs significantly.

## Core explanation

### Introduction to Mobile Operating Systems
Mobile operating systems (OS) are the software platforms that manage hardware resources and provide services for mobile devices like smartphones and tablets. For the CompTIA A+ 220-1101 exam, you need to know the two primary mobile OSes: iOS (developed by Apple) and Android (developed by Google). They share common features—touchscreen interfaces, app ecosystems, wireless connectivity—but differ fundamentally in architecture, security, and customization.

### iOS: Architecture and Key Features
iOS is a Unix-like operating system derived from macOS. It uses a layered architecture with four abstraction layers: Core OS, Core Services, Media, and Cocoa Touch. The Core OS layer contains the kernel (XNU), which manages memory, threads, and file systems. iOS uses a sandboxing model: each app runs in its own sandbox, a directory with restricted access to system resources and other apps' data. This is enforced by the kernel and mandatory access controls. Apps can only access their own container and explicitly granted resources (e.g., photos via user permission).

- **App Store**: The only official source for apps. Apple reviews all apps for malware and policy compliance. Sideloading is not allowed on standard iOS devices (except for enterprise distribution or developer builds).
- **File System**: iOS uses Apple File System (APFS), optimized for flash storage. Users have limited file system access; the Files app provides a unified view of local and cloud files.
- **Security**: iOS includes hardware-backed encryption (AES-256 for data at rest), Secure Enclave for biometric data (Touch ID/Face ID), and code signing to ensure only trusted code runs. Activation Lock ties the device to the owner's Apple ID, preventing unauthorized use if lost.
- **Updates**: iOS updates are pushed by Apple directly to devices. Carriers cannot block updates. Apple typically supports devices for 5-6 years.
- **Management**: iOS supports Mobile Device Management (MDM) via Apple's Device Enrollment Program (DEP) and Volume Purchase Program (VPP). Configuration profiles (XML files) can enforce policies like passcode requirements, VPN settings, and restrictions.

### Android: Architecture and Key Features
Android is a Linux-based operating system. Its architecture includes the Linux kernel (for hardware abstraction and drivers), Hardware Abstraction Layer (HAL), Android Runtime (ART), and application framework. Android uses a sandboxing model based on the Linux user ID (UID) system: each app runs as a separate user with its own UID and permissions. Apps are isolated from each other unless they share a UID (signed with the same certificate).

- **Google Play Store**: The primary app store, but Android allows sideloading (installing APK files from other sources). Users can enable "Install from unknown sources" per app.
- **File System**: Android uses ext4 or F2FS for internal storage. Users have more file system access via the file manager; apps can read/write to shared storage (e.g., SD card) with appropriate permissions.
- **Security**: Android includes encryption (AES-128 or 256, depending on version), Google Play Protect (malware scanning), and app sandboxing. Biometric unlock (fingerprint, face) is common. Android also has a permission model that allows users to grant/deny permissions at runtime (since Android 6.0).
- **Updates**: Android updates are managed by device manufacturers and carriers, leading to fragmentation. Google releases security patches monthly, but adoption depends on the manufacturer. Most devices receive major OS updates for 2-3 years.
- **Management**: Android supports MDM via Android Enterprise (formerly Android for Work). It provides work profiles to separate personal and corporate data. Google Mobile Services (GMS) is required for Play Store access; devices without GMS (e.g., in China) use alternative stores.

### Comparison of Key Features
- **App Installation**: iOS only from App Store; Android from Play Store or sideloading.
- **Customization**: iOS limited (no default app changes, no widgets until iOS 14); Android extensive (launchers, widgets, default apps).
- **File Transfer**: iOS uses iTunes or Finder (macOS) or third-party tools; Android uses MTP (Media Transfer Protocol) for drag-and-drop.
- **Backup**: iOS backs up to iCloud or iTunes; Android backs up to Google Drive or manufacturer cloud.
- **Virtual Assistants**: iOS has Siri; Android has Google Assistant (also available on iOS).
- **Default Browser**: iOS Safari (WebKit-based); Android Chrome (Blink-based). Both support third-party browsers.

### Security and Encryption
- **iOS**: Hardware encryption is enabled by default with AES-256. The Secure Enclave is a dedicated coprocessor that handles cryptographic operations and stores biometric data. Activation Lock prevents reactivation without Apple ID credentials.
- **Android**: Full-disk encryption (FDE) was default from Android 5.0 to 9; file-based encryption (FBE) introduced in Android 7.0 and required from Android 10. Encryption keys are protected by the Trusted Execution Environment (TEE) or dedicated hardware (e.g., Titan M chip on Pixel devices). Google's Find My Device provides similar anti-theft functionality.

### Mobile Device Management (MDM)
MDM allows IT administrators to manage devices remotely. Both iOS and Android support MDM via configuration profiles (iOS) or Android Enterprise (Android). Common MDM features include:
- Enforcing passcode policies (minimum length, complexity, lockout)
- Remote wipe (full or selective)
- Application management (whitelist/blacklist, mandatory install)
- VPN configuration
- Email account setup
- Compliance checks (jailbreak/root detection)

**iOS**: Apple Push Notification service (APNs) is used to send commands to devices. The MDM server communicates with Apple's servers, which then push notifications to devices. Devices poll the MDM server for commands.
**Android**: Google Cloud Messaging (GCM) or Firebase Cloud Messaging (FCM) for push. Android Enterprise provides a dedicated work profile that isolates corporate apps and data.

### Troubleshooting Common Issues
- **Battery Life**: Both OSes have battery optimization features. iOS has Low Power Mode; Android has Doze and App Standby.
- **Connectivity**: Wi-Fi and Bluetooth issues often resolved by forgetting network, rebooting, or resetting network settings.
- **App Crashes**: Force stop (Android) or force quit (iOS) and clear cache/data.
- **Storage Full**: Both offer storage management tools to delete temporary files and offload unused apps.
- **Unresponsive Device**: Force restart methods differ: iOS (press and release Volume Up, then Volume Down, then hold Side button until Apple logo); Android (hold Power + Volume Down for 10-15 seconds).

### Exam Relevance
CompTIA A+ 220-1101 tests your ability to identify OS features, configure email and wireless settings, and implement security measures. Specific objectives include:
- 1.2: Compare and contrast common mobile device features and characteristics.
- 1.3: Given a scenario, set up and configure a mobile device.
- 1.4: Given a scenario, configure mobile device network connectivity and application support.
- 1.5: Given a scenario, implement methods for securing mobile devices.
- 1.6: Given a scenario, troubleshoot common mobile device issues.

You should know the differences between iOS and Android for email configuration (POP3, IMAP, Exchange), wireless settings (Wi-Fi, Bluetooth, NFC), and security features (passcodes, biometrics, remote wipe).

## Real-world context

In enterprise environments, organizations often deploy both iOS and Android devices. A typical scenario: a company issues iPhones to executives and Android phones to field workers. The IT team uses MDM solutions like VMware Workspace ONE or Microsoft Intune to manage both platforms. For iOS, they enroll devices via Apple Business Manager (ABM) using Automated Device Enrollment (ADE), which forces supervised mode and allows configuration profiles to be installed without user interaction. For Android, they use Android Enterprise with work profiles, separating corporate apps and data from personal ones. Common issues: users forgetting to install MDM profiles, device encryption not enabled, or apps not deploying due to OS version incompatibility. Performance considerations: iOS devices have uniform hardware, simplifying management; Android fragmentation requires testing on multiple models. Misconfiguration: failing to set a passcode policy can lead to data breach if a device is lost. Another scenario: BYOD (Bring Your Own Device) policy. Employees use personal phones for work email and apps. IT deploys containerization: iOS uses managed open-in and per-app VPN; Android uses work profile. Challenges: users may resist installing management profiles, and remote wipe of a personal device could erase personal data. Best practice: use selective wipe (remove corporate data only) and educate users on privacy. A third scenario: kiosk mode for point-of-sale or digital signage. iOS uses Guided Access (restricts device to a single app). Android uses Lock Task mode (kiosk app). Both require MDM to configure. Common failure: devices not exiting kiosk mode due to incorrect configuration, requiring factory reset.

## Exam focus

The CompTIA A+ 220-1101 exam tests mobile OS knowledge primarily in the Mobile Devices domain (15% of exam). Specific objectives: 1.2 (Compare and contrast common mobile device features), 1.3 (Set up and configure), 1.4 (Network connectivity), 1.5 (Security), 1.6 (Troubleshooting). The most common wrong answers on exam questions: (1) Thinking that Android updates are pushed by Google like iOS – reality: updates depend on manufacturers/carriers. (2) Believing iOS allows sideloading – it does not for standard devices. (3) Confusing encryption: iOS uses hardware AES-256; Android uses file-based encryption (FBE) since 7.0, not full-disk encryption (FDE) on newer versions. (4) Assuming both OSes use the same app store – iOS only App Store; Android can have multiple stores. Exam loves edge cases: (1) Activation Lock: requires Apple ID password to disable, even after factory reset. (2) Android Enterprise work profile: corporate data is encrypted separately. (3) iOS supervised mode: required for some MDM policies like disabling iMessage. To eliminate wrong answers, focus on the underlying mechanism: if an answer says 'Android updates are timely and universal' it's wrong; if it says 'iOS only installs apps from App Store' it's correct. Memorize specific numbers: iOS passcode default is 6 digits; Android can be any length. Encryption strength: iOS AES-256; Android AES-128 or 256. For email ports: IMAP 993, POP3 995, SMTP 465/587. For MDM: iOS uses APNs; Android uses FCM.

## Step by step

1. **Device Initial Setup** — When a new device is powered on, the OS initializes. For iOS, the setup assistant guides through language, Wi-Fi, Apple ID sign-in, Touch ID/Face ID, and passcode creation. For Android, the setup wizard asks for language, Wi-Fi, Google account sign-in, fingerprint/pin setup, and data restoration options. Both download system updates if connected to Wi-Fi. The exam may ask about initial configuration steps, especially for enterprise devices that use zero-touch enrollment (Android) or Apple Business Manager (iOS).
2. **App Installation and Permissions** — Users install apps from the App Store (iOS) or Play Store (Android). On iOS, permissions are requested at first use of a feature (e.g., camera access). On Android, permissions are granted at install time (pre-6.0) or runtime (post-6.0). iOS apps are sandboxed and cannot access other apps' data. Android apps are isolated by UID but can share data via content providers. The exam tests understanding of permission models and how to revoke permissions.
3. **Email Configuration** — Both OSes support POP3, IMAP, and Exchange ActiveSync. On iOS, go to Settings > Mail > Accounts > Add Account. On Android, open Email or Gmail app > Add account. IMAP leaves emails on server; POP3 downloads and deletes. Exchange uses Microsoft's protocol for push email, contacts, and calendar. For exam, know how to configure server settings (incoming/outgoing server, SSL/TLS, port numbers: IMAP 993, POP3 995, SMTP 465/587).
4. **Wireless Connectivity Setup** — Wi-Fi: Both OSes scan for networks; user selects SSID and enters passphrase (WPA2/WPA3). Bluetooth: Pairing involves making device discoverable, selecting it, and confirming PIN. NFC: Used for Apple Pay (iOS) and Google Pay (Android). Hotspot: Both can share cellular data via Wi-Fi, Bluetooth, or USB. The exam may ask about configuring Wi-Fi (static IP, proxy) and Bluetooth (pairing, file transfer).
5. **Security Configuration** — Set passcode/pin (iOS: 6-digit default; Android: variable length). Enable biometrics (Touch ID/Face ID on iOS; fingerprint/face on Android). For enterprise, enforce passcode policies via MDM. Enable encryption: iOS encrypts by default; Android requires encryption to be turned on (usually default on modern devices). Remote wipe: via iCloud (iOS) or Find My Device (Android). The exam tests understanding of these security features and their limitations.

## Comparisons

### iOS vs Android

**iOS:**
- Closed ecosystem: only App Store
- Hardware encryption AES-256
- Updates pushed by Apple directly
- Limited user customization
- Supervised mode for enterprise

**Android:**
- Open ecosystem: sideloading allowed
- File-based encryption (AES-128/256)
- Updates depend on manufacturer/carrier
- Extensive customization (launchers, widgets)
- Android Enterprise work profile

## Common misconceptions

- **Misconception:** Android devices receive OS updates directly from Google. **Reality:** Only Pixel devices get direct updates from Google. Most Android devices receive updates from the manufacturer (Samsung, LG, etc.) and carrier, causing delays and fragmentation.
- **Misconception:** iOS allows installing apps from any source, like Android. **Reality:** iOS only allows app installation from the App Store. Sideloading is not possible on standard devices without jailbreaking or enterprise certificates.
- **Misconception:** Both iOS and Android use the same encryption method. **Reality:** iOS uses hardware-backed AES-256 encryption with Secure Enclave. Android uses file-based encryption (AES-128/256) with TEE or dedicated security chip.
- **Misconception:** iOS and Android have identical file system access for users. **Reality:** iOS restricts file system access; users interact mainly through apps. Android provides more file system access via file managers and MTP.
- **Misconception:** MDM works the same way on both platforms. **Reality:** iOS uses Apple Push Notification service (APNs) and configuration profiles. Android uses Google Cloud Messaging/Firebase and Android Enterprise. Implementation details differ.

## Key takeaways

- iOS uses a sandboxed, closed ecosystem; Android uses a Linux-based, open ecosystem.
- iOS encryption is hardware-based AES-256; Android uses file-based encryption since 7.0.
- iOS updates are universal; Android updates are fragmented due to manufacturer/carrier control.
- MDM for iOS uses APNs; for Android uses FCM.
- Email configuration: IMAP port 993, POP3 port 995, SMTP port 465/587.
- Activation Lock is unique to iOS; Find My Device is Android's equivalent.
- Android allows runtime permissions since 6.0; iOS requests permissions at first use.

## FAQ

**Can I install apps from outside the App Store on iOS?**

No, standard iOS devices cannot install apps from outside the App Store. Sideloading is not allowed. Only enterprise deployments can distribute apps via MDM, and developers can sideload via Xcode (limited to 100 devices). Jailbreaking removes this restriction but voids warranty and security.

**How do I update Android OS on my device?**

Android updates are pushed by the device manufacturer and carrier, not Google (except Pixel phones). Go to Settings > System > System Update to check. Updates may be delayed weeks or months. Security patches are released monthly by Google, but adoption depends on the manufacturer.

**What is the difference between full-disk encryption and file-based encryption on Android?**

Full-disk encryption (FDE) encrypts the entire storage partition, requiring a single password at boot. File-based encryption (FBE) encrypts files individually with different keys, allowing the device to start without decrypting all files. FBE was introduced in Android 7.0 and is required from Android 10.

**How does Activation Lock work on iOS?**

Activation Lock is tied to the Apple ID. When Find My iPhone is enabled, the device cannot be erased or reactivated without the Apple ID password. Even after a factory reset, the device remains locked. This deters theft. To disable, the owner must sign out of iCloud or remove the device from their account.

**What are the default passcode lengths for iOS and Android?**

iOS default passcode is 6 digits (4-digit option available). Android has no fixed default; it can be a PIN, pattern, or password of varying length. Android may enforce minimum length via policy.

**Can I use the same MDM for both iOS and Android?**

Yes, most MDM solutions (e.g., Intune, Workspace ONE) support both iOS and Android. However, the enrollment methods differ: iOS uses Apple Business Manager and APNs; Android uses Android Enterprise and FCM. The MDM server must be configured for each platform separately.

**What is the difference between a work profile on Android and supervised mode on iOS?**

Android work profile creates a separate, encrypted container for corporate apps and data on a personal device. It isolates work apps from personal apps. iOS supervised mode gives the MDM more control, such as disabling iMessage, AirDrop, and restricting app installation. Supervised mode requires device enrollment via Apple Business Manager.

---

Interactive version with quiz and diagrams: https://courseiva.com/learn/a-plus-core-1/mobile-os-types