CompTIA A+ mobile device hardware: what Core 1 actually tests

Why batteries matter more than any other mobile component

Battery chemistry is on the blueprint because failure modes matter. The two you need to recognize are lithium-ion and lithium-polymer. Both can swell, both can vent, both can catch fire if punctured. The differences are packaging and shape, not behavior under failure.

• Lithium-ion (Li-ion). Cylindrical or prismatic cells in a rigid case. Common in laptops and older phones. Energy dense. Will swell when the electrolyte breaks down.
• Lithium-polymer (LiPo). Flexible pouch cells. Common in modern thin phones, tablets, ultrabooks. Same chemistry, different package. Pouches bulge dramatically when failing.

The symptoms worth recognizing on sight: a device that will not seat in its case, a screen lifting away from the frame, a bowed back panel, a laptop that rocks on a flat desk, a trackpad that stopped clicking. Those all point at a swollen cell.

The safe response is the same every time. Stop charging it. Power it down. Isolate it from heat, metal, and anything flammable. Then hand it to the manufacturer or a shop equipped for battery service. Spent and damaged cells leave through hazardous-waste or e-waste handling, not the trash. A swollen pouch is under pressure and the internals are already failing, so puncturing or heating one is how people end up with a fire on the bench. That is not a scare tactic, it is the reason the referral is the answer.

What screen technology shows up on Core 1

The three families you need to know are LCD (including IPS as a panel type), OLED, and the older TN you will still occasionally see on cheap laptops. Each has trade-offs the exam can ask about by symptom or use case.

• LCD / IPS. Uses a backlight behind a liquid crystal layer. IPS is an LCD variant with better viewing angles and color. If a user reports "the bottom of the screen has a dim bar but the image is still there," that is usually backlight failure on an LCD. The pixels are fine, the light is not.
• OLED. Each pixel emits its own light. No backlight. True blacks. Susceptible to burn-in when static images sit on screen too long. If a user reports "I can see the keyboard outline on my dark wallpaper," that is OLED burn-in.
• TN. Cheap, fast, poor viewing angles. Mostly gone from new devices but still in budget displays. Color shifts off-axis.

The pattern: a backlight problem points to LCD, a burn-in problem points to OLED, a viewing-angle complaint points to TN or low-end LCD. Match the symptom to the panel.

Which connectors does the exam expect you to recognize

Mobile ports on the current blueprint center on USB-C, Lightning, and the legacy connectors you still see in the wild. The trick is knowing which device family uses which and what the user will hand you.

• USB-C. Reversible, carries USB data, DisplayPort, Thunderbolt, and up to 240 W of power on the latest spec. Standard on most current Android phones, recent iPhones, modern laptops, and tablets.
• Lightning. Apple's proprietary connector on older iPhones and accessories. Reversible. Being phased out. Still common enough to know on sight.
• microUSB. Legacy. Still on cheap accessories, e-readers, older controllers. Not reversible. If a user hands you a cable from a drawer and it has the trapezoid shape, that is microUSB.

A delivery company with a fleet of older Samsung phones might still have microUSB chargers in every truck. The newer fleet has USB-C. The mismatch is the question, not the spec sheet.

What does a safe replacement workflow look like

On the job, mobile repair is mostly screen assemblies, back glass, and battery swaps. Where you draw the line matters more than the sequence, so start with the line: this workflow assumes an intact battery. If the cell is swollen, vented, hot, leaking, or physically damaged, none of the steps below apply. That device gets powered down, isolated, and referred out. Techs get hurt at the moment they decide a bulging pouch is close enough to normal.

1. Inspect the battery before anything else. Look for swelling, lifting panels, or heat. Any of those and you stop here and refer the device out.
2. Set the bench up first. Ventilated space, eye protection, nitrile gloves, no clutter, nothing flammable on the surface, and a way to smother a lithium fire within reach. Cheap habits, cheap insurance.
3. Power down and discharge. Never open a device with a live battery if you can avoid it. Drain to under 25 percent if possible.
4. Heat the adhesive, on an intact battery only. Most modern phones and tablets are sealed with adhesive strips or perimeter glue, and a heating pad or iOpener softens it. Keep the heat low and away from the cell. Do not apply heat to a swollen battery at all.
5. Open with the right tools. Suction cup, plastic pry tools, opening picks. Never a metal blade against a battery pouch.
6. Disconnect the battery first. Before any other connector. This prevents accidental shorts during the rest of the work.
7. Swap the part. Replace adhesive. Reassemble. Old adhesive rarely reseals well. Use fresh strips.
8. Test before declaring done. Cellular, Wi-Fi, cameras, Face ID or fingerprint, charging, speaker. Each of those can be the thing that breaks during reassembly.
9. Route the old cell to e-waste. Tape the contacts, keep it out of the trash, and hand it to a battery recycling stream.

What about MDM enrollment and pairing

Mobile device management sits in objective 1.3 with mobile accessories and configuration, and the scenarios usually focus on what enrollment does rather than on any one vendor console. For the delivery company with a Samsung fleet, MDM means each device is registered to the company, policies push down (passcode required, remote wipe enabled, app whitelist), and the company can recover the device if it walks off.

Pairing gotchas show up too. Bluetooth pairing needs both devices in discovery mode at the same time. A common exam-style scenario has a user who cannot pair new headphones, and the first thing to check is discovery mode on both ends before you go looking for a driver or a firmware bug. The boring check is usually the one that closes the ticket.

What this looks like in our platform

Our Study Mode decks for objectives 1.1 through 1.3 cover each component family with diagrams and the symptom-to-part match. The Help Desk Simulator has tickets for the swollen battery, the burn-in OLED, the worn USB-C port, and the failed MDM enrollment. Each ticket grades you on whether you ran the six-step methodology and whether you reached the right cause.

If you are tracking toward the A+, the A+ track page has the full objective map. Mobile devices is the first domain on Core 1 for a reason. Get it solid and the rest of Core 1 gets easier.

Where to go next

Mobile leans into networking next. Objective 2.x on Core 1 covers wireless standards, cellular generations, and the protocols mobile devices use. The pattern stays the same. Match symptom to spec. Match user complaint to component. The exam rewards the match, not the memorization.

About the authors

Nick Miller

Founder and Lead Author

IT Service Center Manager and former CTE / IT teacher. Owner of Revtek IT Solutions. Writes everything that ships under his name and reviews every line of Revy-assisted drafting before publish.

LinkedIn ↗

R

Revy

Study buddy · AI co-author

Revy helps draft and structure these posts. Every piece is reviewed, edited, and fact-checked by Nick before publish. We disclose this here because it is the right thing to do. See the AI Policy for the full stance.