Week 5: Laptops and Mobile Devices

A laptop is still a computer.

It still has processing, memory, storage, power, networking, input, and display systems.

What changes is how tightly those systems are integrated.

A desktop may let you replace the GPU, power supply, RAM, storage, wireless adapter, keyboard, and display as separate parts. A laptop may integrate several of those functions into the motherboard, display assembly, top case, or battery-powered chassis.

So the mobile technician question is not only:

What component is failing?

It is also:

On this exact model, where does that function live, what else shares the assembly, and can it be serviced independently?

That model-specific thinking matters even more with phones and tablets, where hardware, radios, accounts, policy, carrier service, and cloud synchronization can all produce similar user-visible symptoms.

The system question

The question for Week 5 is:

How do we locate a mobile-device failure when hardware, accessories, radios, policy, accounts, and synchronization all overlap?

Use this model:

power / battery
      ↓
main board + integrated hardware
      ↓
display / touch / camera / input
      ↓
ports / accessories
      ↓
Wi-Fi / Bluetooth / cellular / location
      ↓
OS permissions + device policy
      ↓
accounts / apps / cloud sync

A failure near the bottom can look like a hardware problem at the top if you do not separate the layers.

How the chapter moves

Lesson 1 focuses on serviceability. You will compare batteries, keyboards, RAM, storage, wireless cards and antenna leads, cameras, microphones, biometrics, and other model-specific replacement boundaries.

Lesson 2 follows the portable power, display, digitizer, camera, microphone, keyboard, trackpad, and stylus paths. One lid can contain several systems, and they do not all fail together.

Lesson 3 moves outside the chassis into USB-C and legacy connectors, docks, Bluetooth, NFC, cellular, hotspots, location services, MDM, BYOD, corporate applications, and synchronization.

Lesson 4 is the support lab. You will use what already works to eliminate large parts of the stack instead of resetting everything.

Lesson 5 turns the full Core 1 mobile symptom set into bounded diagnosis: poor battery health, swelling, broken screens, charging failures, connectivity, liquid damage, overheating, digitizer problems, damaged ports, suspicious software behavior, cursor drift, app-install failures, stylus issues, and degraded performance.

What you should be able to defend

By the end of the week, you should be able to explain:

• whether a laptop component is replaceable, integrated, or model-dependent;
• why service documentation matters before opening a portable system;
• how charging, battery, display, touch, camera, microphone, keyboard, and pointing-device paths differ;
• what USB-C, microUSB, miniUSB, Lightning, NFC, Bluetooth, docks, and port replicators actually provide;
• how hotspots, Wi-Fi, 3G/4G/5G, SIM/eSIM, GPS, and location permissions form separate boundaries;
• why MDM and BYOD policy can intentionally block a function;
• how mail, calendar, contacts, corporate apps, and cloud storage can synchronize independently; and
• how to troubleshoot a mobile complaint without turning a factory reset into the first move.

The safety line

A swollen or damaged battery is a stop-work condition. Do not puncture, bend, crush, squeeze, pry open, or continue charging a damaged pack.

Do not repeatedly power a liquid-exposed device to see whether it still works.

No personal mobile device needs to be disassembled or enrolled into MDM for this course.

Portable hardware is smaller. The consequences are not.