Mobile Tech Today

Guides

  • Phone Screen Goes Black During Calls

    Your phone screen going black during calls is usually the proximity sensor doing exactly what it was designed to do — shutting the display off the moment the handset gets close to your face, mainly to save battery and stop your cheek from muting the call or hanging up by accident. This only turns into an actual problem when the screen refuses to come back once you pull the phone away, or when it blacks out immediately even while the phone is sitting flat on a table, nowhere near your face. There’s one short test that tells you which situation you’re actually dealing with, and it takes less than a minute to run.

    When the Black Screen Is Completely Normal

    Almost every phone made in the last decade has a small proximity sensor tucked near the earpiece, usually hidden behind the glass right above the front camera. Its whole job during a call is to detect when something — your face, your ear, the side of your head — comes within a few centimeters of the top of the phone, and to kill the display the instant that happens. The moment you move the phone away again, the sensor should report clear space and the screen should light back up on its own.

    If that’s exactly what’s happening to you — screen goes dark against your face, comes right back the second you pull away — nothing is wrong. On some Android phones you can soften this behavior slightly through a setting like “keep screen on while viewing” or a motion-and-gestures toggle buried in the display settings, which uses face detection through the front camera instead of relying purely on the proximity sensor. iPhones don’t offer a user-facing switch for this at all; the screen-off-during-calls behavior is built into iOS and isn’t something you can turn off through Settings, so if you’re on an iPhone and the sensor is behaving consistently, there’s genuinely nothing to fix.

    The One Test That Actually Tells You What’s Wrong

    The question that matters here isn’t “why does my screen go black,” because the answer to that is almost always “the proximity sensor.” The question that matters is whether the sensor is reporting the truth or lying to your phone — and that’s a testable, binary thing, not a guessing game.

    If you’re on a Samsung phone, or most Android devices, open the dialer and enter #0#, which drops you into a hidden hardware diagnostics menu most manufacturers build in for exactly this kind of troubleshooting. Look for a tile labeled “Sensor” or “Proximity Sensor,” tap it, then wave your hand slowly toward and away from the top edge of the screen where the sensor sits. A working sensor will register clean pass and fail states in near real time, no lag, no getting stuck. If it fails to register your hand approaching, fails to register it leaving, or the readout freezes on one state, that’s your answer.

    iPhones don’t have an equivalent hidden menu, so the test has to happen live. Place a call — voicemail works fine for this — hold the phone to your ear until the screen goes black, then pull it away sharply and repeat that motion five or six times in a row at different speeds. A sensor that’s actually failing will show a pattern: either the screen never comes back no matter how far you move the phone, or it flickers on and off unpredictably even when the phone is held steady against your ear.

    If the Sensor Fails the Test

    A sensor that consistently fails this test almost never fixes itself, and the cause is usually one of three things. The most common is a case or screen protector sitting slightly too close to the sensor cutout, effectively covering it and permanently reporting “something is near” even when nothing is. Pulling the case off and running the test again costs nothing and rules this out in ten seconds. The second is simple debris — pocket lint, dust, a bit of adhesive residue from a previous screen protector — sitting directly over the sensor opening, which a gentle wipe with a dry microfiber cloth usually clears.

    The third cause is physical damage, and it’s the one that actually needs a repair. A drop that jars the sensor loose from its connector, or moisture that gets into that area of the phone, can both cause exactly this symptom. If your phone has taken a fall recently or been anywhere near water, it’s worth reading through what to do after a water-damaged phone before assuming this is a standalone sensor issue, since the two often show up together.

    Ruling Out Software Before You Assume It’s Hardware

    Before writing this off as a hardware failure, it’s worth spending five minutes on the software side, because a surprising number of proximity sensor complaints trace back to a bad update rather than a broken part. A full restart clears temporary sensor calibration glitches more often than people expect. If you’ve recently installed a third-party dialer, call recorder, or call-blocking app, disable it and test again — these apps sometimes hook into the same system permissions the proximity sensor uses and can interfere with how quickly it reports state changes. And if there’s a pending OS update sitting in your settings, installing it is worth doing before you spend any money, since manufacturers occasionally patch exactly this kind of sensor bug.

    What Repair Actually Costs

    On most modern phones, the proximity sensor isn’t a cheap standalone part you can swap in isolation — it’s usually built into the same assembly as the display itself, which means a genuine hardware failure typically means replacing the screen assembly rather than just “the sensor.” Depending on the phone model and whether you go through a third-party repair shop or the manufacturer, that repair tends to land anywhere from roughly $50 on older or budget Android devices up toward $150 or more on newer flagships. If your screen is also cracked or damaged from the same drop that knocked the sensor loose, it’s worth checking realistic pricing for a cracked screen repair before you commit, since you may be paying for the same part either way. And if the phone is older or already showing other wear, it’s worth weighing that cost against simply deciding whether to repair or replace the phone rather than sinking money into a single component.

    It’s also worth mentioning that a malfunctioning proximity sensor sometimes shows up alongside other call-quality complaints rather than on its own. If you’re also noticing that you can’t hear the other person during calls, that they can’t hear you clearly, or sound that’s crackling and distorted only during calls, those are separate components with their own failure patterns, but a phone that’s taken a drop or water exposure can easily affect more than one part at once.

    FAQ (SEOPress FAQ Schema Block – Option A)

    Q: Why does my phone screen go black during calls? A: A small proximity sensor near the earpiece detects when the phone is close to your face and turns the screen off automatically, mainly to save battery and prevent accidental touches. This is normal behavior on virtually every smartphone and only becomes a problem if the screen fails to turn back on when the phone is pulled away.

    Q: Is it normal for the screen to turn off during a phone call? A: Yes, screens turning off during calls is standard, intentional behavior on both Android and iPhone devices. It’s only a fault if the screen stays black after the phone is moved away from your face, or if it goes black even when the phone isn’t near your face at all.

    Q: How can I test if my phone’s proximity sensor is broken? A: On Samsung and most Android phones, dial #0# to open the hidden hardware diagnostics menu, select the proximity sensor test, and wave your hand toward and away from the top of the screen to see if it registers each state correctly. On iPhone, make a test call and repeatedly move the phone to and away from your ear; a failing sensor will either keep the screen permanently black or flicker unpredictably.

    Q: Can a phone case or screen protector cause the screen to go black during calls even when nothing is near it? A: Yes. A case or screen protector positioned too close to the sensor cutout can physically block it, causing the phone to permanently register something as nearby even when it isn’t. Removing the case or protector and retesting the sensor usually confirms this immediately.

    Q: How much does it cost to fix a broken proximity sensor? A: On most modern phones the proximity sensor is built into the display assembly rather than sold as a separate part, so repair typically means replacing the screen assembly. Costs generally range from around $50 on older or budget Android phones to $150 or more on newer flagship models, depending on the device and repair provider.

  • Phone Flashlight Not Working? Check This Before Anything Else

    Before you try anything else, open your Camera app and switch the flash to on, then take a photo or just watch what happens in the viewfinder. That one check tells you more than almost any other troubleshooting step, because whether the flashlight works from inside the Camera app but not from your Control Center or Quick Settings, or whether it fails to come on no matter where you try it, points you toward two very different kinds of problems.

    Why This Test Matters

    Here’s something that surprises a lot of people: your flashlight isn’t actually its own separate part inside the phone. It’s the same LED flash that’s built into your rear camera module, the one used for photos. That single fact explains almost everything else about why flashlights fail in the specific patterns they do.

    When you tap the flashlight icon from Control Center or your Quick Settings panel, your phone’s operating system is essentially sending a stripped-down instruction to the camera hardware: turn on the LED, but don’t bother opening the full camera app behind it. That’s a slightly different, lighter-weight pathway than the one used when you open the actual Camera app and turn the flash on there. Because of that, it’s entirely possible for one pathway to break while the other keeps working perfectly, and which one is broken tells you a lot about what’s actually going wrong.

    If It Works in the Camera App but Not from Control Center

    This is genuinely good news, because it means your camera hardware and the LED itself are both functioning fine. The problem is isolated to the lighter software pathway that Control Center uses, which is usually one of a small handful of causes.

    The most common one by far is a background app holding onto the camera. Since the flashlight and the camera share the same hardware, if another app, particularly something like Snapchat, Instagram, or a video calling app, is running in the background and still has a claim on the camera, it can block the Control Center flashlight from turning it on even while leaving the full Camera app free to use it directly. Close out of any recently used apps completely, not just switch away from them, and try the flashlight again.

    Battery Saver or Low Power Mode is another common culprit, since many phones deliberately restrict Control Center features like the flashlight shortcut when battery saving is active, even though the same LED remains fully available inside the Camera app itself. Turning off battery saver, even temporarily, is worth testing.

    A simple restart resolves a surprising number of these cases too, since it’s often nothing more than a temporary glitch in how the Control Center shortcut is communicating with the camera hardware, rather than anything actually broken.

    If It Doesn’t Work Anywhere, Including the Camera App

    This points toward something closer to the hardware itself, or a more fundamental restriction, so it’s worth working through a slightly different set of checks.

    Heat is one of the most common causes here and one people rarely suspect. The LED flash generates real heat concentrated in a very small area, and phones are built with a safety feature that disables the flash entirely if the phone has gotten too warm, often showing a message like “Flash is Disabled” or simply refusing to activate without much explanation. This tends to happen after extended gaming, recording video for a long stretch, or leaving the phone in direct sunlight or a hot car. If your phone feels warm to the touch, let it cool down somewhere shaded for fifteen to twenty minutes and test again before assuming anything is actually broken.

    Low battery can trigger a similar restriction on some phones, particularly once the battery drops below a certain percentage, since the flash draws a meaningful burst of power that the phone may not want to commit if it’s trying to preserve what’s left. Charging the phone for a while before testing again rules this out quickly.

    If the camera app itself is behaving oddly in other ways too, crashing, showing a black screen, or displaying an error like “camera in use” or “flash unavailable,” that’s worth noting, since it suggests the underlying issue is with the camera system as a whole rather than the flashlight specifically. Clearing your Camera app’s cache and data, or on Android, checking whether the auto-flash setting inside the Camera app itself has gotten stuck, are both worth trying at this point.

    The Safe Mode Test

    If none of the causes above seem to apply, it’s worth checking whether a third-party app is interfering at a deeper level than just holding onto the camera in the background. Booting into Safe Mode on Android disables third-party apps entirely, and it’s the same technique that’s useful for tracking down apps causing a phone to restart unexpectedly if you’ve run into that issue too. If the flashlight works normally in Safe Mode, something you’ve installed is the cause, and uninstalling whatever was added most recently usually solves it.

    When It’s Genuinely a Hardware Problem

    If you’ve ruled out heat, low battery, background apps, and confirmed it’s not a Safe Mode issue, and the flashlight still won’t activate in the Camera app itself while the rest of the camera otherwise functions normally, that points toward the LED component itself having failed or a connection issue inside the camera module. This is more likely if the flashlight stopped working suddenly after a drop, or if you’ve noticed any other new issues with your camera around the same time, like blurry photos or the camera app crashing unexpectedly.

    The LED flash is a relatively small, self-contained part of the camera module, so a genuine hardware repair here tends to be more affordable than something like a full camera replacement, though pricing does vary depending on whether it can be replaced on its own or requires swapping the entire camera assembly. If you’re weighing whether that repair is worth it, our repair vs. replace guide walks through how to think about that decision based on your phone’s age and condition.

    Frequently Asked Questions

    Why does my flashlight work in the Camera app but not from Control Center? This usually means a background app is holding onto the camera, or Battery Saver mode is restricting the Control Center shortcut specifically. Since both features use the same LED, this pattern almost always points to a software conflict rather than anything hardware-related.

    Can low battery really stop my flashlight from working? Yes, on many phones. The flash requires a noticeable burst of power, and some phones restrict it once the battery drops below a certain level to help preserve what charge remains. Charging the phone for a bit before testing again is a quick way to rule this out.

    Does an overheating phone actually disable the flashlight? Yes, and it’s more common than most people expect. The LED flash generates concentrated heat, and phones have a built-in safety feature that disables it if the phone is already running warm, often after gaming, recording video, or sitting in direct sunlight.

    Is a broken flashlight always a sign the whole camera is damaged? Not necessarily. Since the flash is one specific component within the camera module, it’s possible for it to fail while the rest of your camera continues taking normal photos and video. If you’re also noticing other camera issues at the same time, that’s a stronger sign the problem is more widespread.

  • Phone Speaker Crackling or Distorted? Ask This One Question First

    Before you go digging through a long list of possible causes, there’s one question that narrows this down faster than almost anything else: does the crackling happen only when the volume is turned up high, or does it happen at every volume level, even low? That single distinction splits this problem into two very different situations, and knowing which one you’re in tells you almost immediately whether you’re looking at a five-minute fix or something that needs a technician.

    Why This Question Matters So Much

    A tiny phone speaker is, physically, a small diaphragm being pushed and pulled by an electrical signal, and at high volume that diaphragm is working close to its limit even when everything is functioning normally. If a small amount of dust, a case pressing against the grille, or an aggressive equalizer setting is adding even a little extra resistance, it often only becomes audible as crackling once you’re pushing the speaker hard — meaning at low-to-medium volume, everything sounds fine, and the problem only shows up once you crank it up. This pattern points toward something external interfering with the speaker’s ability to move freely, not the speaker itself being damaged.

    Crackling that happens at every volume level, including quiet, tells a different story. If the speaker distorts even at a whisper of volume, that generally means the diaphragm or voice coil itself isn’t moving cleanly, which points more toward internal damage — often from a drop, water exposure, or general wear over time. This doesn’t automatically mean the news is bad, since even this can sometimes be fixed with a clean, but it does mean you should treat this more seriously than the high-volume-only version.

    Take thirty seconds now, before reading further, and test this on your own phone: play something at low volume, then gradually raise it, and note exactly where the crackling starts. That answer will tell you which section below to focus on.

    If It Only Happens at High Volume

    Start with the two most common physical causes, since these solve the problem most often. Take off your case and, if you have one, your screen protector, and test again — a case that fits slightly wrong, or a screen protector that extends further than it should, can partially cover the speaker grille and create exactly this high-volume-only distortion. If that’s not it, look closely at the speaker grille itself, usually along the bottom edge or back of the phone, for visible dust, lint, or grime, and clean it gently with a soft, dry brush or a few short bursts of compressed air held a few inches away — never anything sharp or metal, and never liquid.

    If cleaning doesn’t resolve it, check your audio settings next. Aggressive equalizer settings, particularly boosted bass, ask more of a small phone speaker than it’s built to handle, and can cause exactly this kind of high-volume crackling even on a completely healthy speaker. Look in your Sound settings for any equalizer or “sound enhancement” features and try turning them off or resetting them to default, then test again.

    It’s also worth ruling out the source of the audio itself before blaming the phone. Play the exact same clip through a different app, or through headphones, to see if the crackling follows the audio or stays with the speaker. If it disappears with headphones but persists through the speaker across multiple different apps and files, that confirms it’s genuinely the speaker rather than a single corrupted file or a buggy app.

    If It Happens at Every Volume Level, Even Low

    This pattern is more likely to point toward the speaker itself, so the checks here are a bit more targeted. Still start with Bluetooth, since it’s an easy thing to overlook: if your phone has ever paired with a Bluetooth device, even briefly, audio can sometimes route strangely and produce distortion that feels like it’s coming from the main speaker but is actually a routing issue. Turn Bluetooth off entirely and test again before assuming anything about the hardware.

    From there, restart the phone, since a surprising number of persistent, low-level audio glitches clear up with nothing more than that. If the crackling survives a restart, try booting into Safe Mode on Android, which disables third-party apps temporarily — if the sound is clean there, a recently installed app is interfering with audio processing system-wide, and uninstalling the most recent addition usually resolves it.

    If none of that changes anything, and the phone has been dropped recently, or has had any contact with water even if it seemed to survive fine at the time, that timing is a strong clue. Moisture sitting on the speaker diaphragm, even a small amount from humidity, sweat, or being caught in light rain, can cause exactly this kind of persistent distortion, and it sometimes clears up entirely once the moisture fully evaporates over a day or two in a dry space. If there’s been no drop and no moisture exposure, and the crackling has been getting gradually worse over weeks or months rather than appearing suddenly, that pattern points more toward ordinary wear on an aging speaker component.

    A Few Other Things Worth Ruling Out Either Way

    Do Not Disturb and certain audio profile settings have, in rare cases, been reported to interfere with normal audio output on some phones — it’s a quick check to confirm this is fully turned off. And if you’re only hearing the distortion within one specific app, that’s actually good news: it points to a corrupted file or a bug in that particular app rather than your speaker at all, and reinstalling the app or trying different audio content is worth doing before you assume anything hardware-related.

    When to See a Repair Technician

    If you’ve worked through the relevant section above based on your volume-level answer, and the crackling persists across multiple apps, multiple audio files, and after a restart and Safe Mode test, this is a reasonable point to stop troubleshooting and get it looked at. It’s worth noting this is a similar but distinct issue from a speaker going completely silent during calls — that’s usually the earpiece specifically, while crackling and distortion more often involves the main speaker. If a repair does turn out to be needed, it’s worth weighing the cost against our repair vs. replace guide, especially if the phone is a few years old and this isn’t its first issue.

    Frequently Asked Questions

    Why does my phone speaker only crackle at high volume? This is most often caused by dust or debris in the speaker grille, a case or screen protector partially covering it, or an aggressive equalizer setting asking more of the speaker than it can cleanly handle. All three are common and usually fixable without any repair.

    Can water damage cause speaker crackling without breaking the phone entirely? Yes. Even a small amount of moisture on the speaker diaphragm can cause persistent distortion while the rest of the phone continues working completely normally. This sometimes resolves on its own once the moisture fully evaporates, though it’s worth monitoring in case it points to broader water exposure.

    Does a software update ever cause speaker crackling? It can, though it’s less common than physical causes. A buggy update can occasionally interfere with how audio is processed system-wide, and this typically resolves with the next patch or by checking your audio and equalizer settings for anything that changed after the update.

    Is speaker crackling always a sign I need a repair? No — in a large share of cases, the cause is dust, a case, or a software setting, all of which cost nothing to fix. Persistent crackling that happens at every volume level and survives cleaning, restarting, and a Safe Mode test is the pattern that more reliably points toward an actual repair being needed.

  • Phone Microphone Not Working During Calls? Here’s Why (It’s Not Necessarily Broken)

    If you’ve tested your microphone with a voice memo, or watched Siri or Google Assistant understand you perfectly, and it still doesn’t work the moment you’re on an actual phone call, you’ve probably already run into the most confusing part of this problem: everything you tested says the microphone works, yet callers can’t hear a word you say. The reason this feels like a contradiction is that it isn’t actually a contradiction at all — your phone almost certainly has more than one microphone, and the one used specifically for calls is a different physical component from the one picking up your voice for recordings, Siri, or video.

    Once you know that, the whole troubleshooting process gets much more targeted, because you’re no longer treating this as one vague “microphone problem.” You’re isolating which microphone failed, and why.

    Why Your Phone Has More Than One Microphone

    Most modern smartphones have between two and four microphones, and each serves a specific purpose. There’s typically a primary microphone near the bottom of the phone, close to where your mouth sits during a call, which is the one actually used for regular voice calls. There’s usually a second microphone near the top or front, primarily used for video recording, FaceTime-style video calls, and noise cancellation. Some phones add a third microphone specifically for active noise cancellation on speakerphone or when using earbuds.

    This is exactly why voice memos, Siri, and Google Assistant can all work flawlessly while regular calls stay silent — those features often rely on a different microphone than the one dedicated to calls. A caller-can’t-hear-you problem isolated specifically to calls is telling you something precise: the call-specific microphone or its connection has failed, while the others remain completely fine. That’s a much smaller, more fixable problem than “my microphone is broken” sounds like at first.

    Step One: Confirm It’s Genuinely Call-Specific

    Before anything else, it’s worth deliberately separating what’s actually broken from what still works. Record a voice memo and play it back to confirm general microphone function. Try a voice assistant command and see if it understands you accurately. Then make a test call, ideally to a voicemail line or a friend who can tell you honestly whether they can hear you, and try both with the phone held normally and on speakerphone.

    If voice memos and voice assistant work but calls are silent regardless of speaker or earpiece mode, this confirms the issue lives specifically in the call-audio pathway rather than the microphone hardware generally — which points you toward the causes below rather than a full hardware failure.

    The Most Common Cause: A Recently Installed App

    Just as with speaker issues, a third-party app that requests microphone access, particularly call recorders, translation apps, or anything that hooks into call audio, can interfere with how the phone routes microphone input during calls specifically, without affecting voice memos or other microphone uses at all.

    The cleanest way to test this is booting into Safe Mode on Android, which temporarily disables third-party apps entirely. (This is the same technique that’s useful for the phone-restarts-by-itself problem if you’re dealing with more than one issue at once.) Make a test call while in Safe Mode — if the microphone works normally there, a recently installed app is almost certainly the cause, and uninstalling the most recently added one usually resolves it. On iPhone, since there’s no Safe Mode equivalent, the practical approach is offloading recently installed apps one at a time and re-testing after each.

    Check Your Dialer App’s Own Settings

    This one is easy to overlook because it feels unrelated to a hardware problem. Many Android phones include call-specific audio processing — noise reduction, voice clarity enhancement, or noise suppression — built directly into the Phone or Dialer app’s settings, separate from any general sound settings. Occasionally, a software bug in these features causes them to suppress your voice too aggressively, effectively muting you without any hardware fault at all.

    Check inside your Phone or Dialer app’s own settings menu, not just the phone’s general sound settings, for anything labeled noise reduction, voice clarity, or similar, and try temporarily disabling it as a test.

    Check App Permissions

    If a specific app you use for calling, whether that’s your default dialer or something like WhatsApp, doesn’t have microphone permission enabled, it will behave exactly like a hardware failure from the caller’s side while every other microphone use continues working fine. On Android, this is worth checking directly in Settings > Privacy > Permission manager > Microphone, confirming your calling app appears under the allowed list. On iPhone, check Settings > Privacy & Security > Microphone for the same thing.

    A Blocked or Damaged Microphone Port

    If everything above checks out and you’re still not being heard, it’s worth a physical inspection. The microphone used for calls is usually a very small hole, often near the charging port at the bottom of the phone, and it’s easy for lint, dust, or a poorly fitted case to partially or fully block it without being obvious at a glance.

    Gently inspect this opening with a flashlight and clean it carefully with a soft, dry brush or a short burst of compressed air, avoiding anything sharp or metal. It’s worth removing your case temporarily as well, since some cases can partially cover this specific microphone opening even when they fit everything else properly.

    When It’s Genuinely Hardware

    If you’ve confirmed the issue is isolated to calls, ruled out third-party apps through Safe Mode, checked dialer-specific settings and permissions, and cleaned the microphone opening with no change, this points toward the call microphone itself having failed, or its internal connector coming loose. This is more likely if the issue appeared suddenly after a drop, or followed any water exposure, even if the phone otherwise seemed to survive that exposure fine.

    The reasonably good news is that, similar to the earpiece speaker, the call microphone is typically a small, self-contained component rather than something deeply integrated into the rest of the phone, which usually keeps the repair cost and complexity on the lower end compared to something like a full display or battery replacement.

    Frequently Asked Questions

    Why can Siri hear me but callers can’t?
    Because Siri and Google Assistant typically use a different microphone than the one dedicated to regular phone calls. A fault isolated to the call microphone won’t affect voice assistants or voice recording at all, which is exactly why this symptom pattern is so useful for narrowing down the cause.

    Can a software update fix a microphone that doesn’t work on calls?
    Sometimes, yes, if the cause is a bug in call-specific audio processing or a permissions glitch rather than physical blockage or hardware failure. It’s worth installing any pending updates as a quick, no-cost step before assuming hardware is at fault.

    Does switching to speakerphone use a different microphone?
    On many phones, yes — speakerphone mode sometimes activates a secondary microphone designed to pick up voice from a distance, which is why some people notice they can be heard on speakerphone but not when holding the phone normally to their ear, or vice versa. This distinction is useful information for a repair technician if you do need professional help.

    Is a call microphone repair expensive?
    Generally not among the pricier phone repairs. Since it’s typically a small, self-contained component similar to the earpiece speaker, it tends to be one of the more affordable and quicker fixes compared to display or battery work.

  • Phone Speaker Not Working During Calls? Here’s the Real Cause

    Here’s the detail that most troubleshooting guides skip right past: if your phone plays music, videos, and alarms just fine, but goes silent the moment you’re on an actual call, that’s not one problem with several possible fixes — it’s almost always one of three completely different, specific issues. Treating it as a single generic “speaker problem” is exactly why so much advice out there doesn’t work: half of it targets the wrong cause.

    The three real possibilities are a Bluetooth device quietly routing your call audio somewhere else, physical debris blocking the small earpiece speaker specifically, or an actual hardware fault in the earpiece itself, which is a completely different, smaller component than your main speaker. Figuring out which one you’re dealing with takes about two minutes, and it changes everything about what to do next.

    Why This Distinction Matters So Much

    Your phone actually has two entirely separate speakers, and that’s the root of most of the confusion. The main speaker, the one used for music, videos, and speakerphone mode, sits on the bottom or back of the phone and is a relatively large, robust component. The earpiece, on the other hand, is a small, narrow, low-volume speaker near the top of the screen, purpose-built specifically for holding the phone against your ear during a normal call. If your main speaker works perfectly for everything except calls, the main speaker was never the problem to begin with — you’ve been troubleshooting the wrong component the entire time.

    First: Rule Out Bluetooth

    This is the cause people miss most often, because it doesn’t feel like it should be related. If your phone has ever paired with a Bluetooth headset, car system, smartwatch, or earbuds, even briefly, your phone can quietly decide to route call audio to that device instead of the earpiece, even if the device isn’t nearby, isn’t turned on, or isn’t in your ear at the moment.

    To check, open Bluetooth settings during an active call and look at what’s currently connected — on both iPhone and Android, the call screen itself usually shows an audio source icon indicating where sound is being routed. If anything is listed as connected, disconnect it or simply turn Bluetooth off entirely, then make a test call. If the earpiece suddenly works, you’ve solved it, and the long-term fix is either remembering to disconnect that device before calls or removing it from your paired devices list if you rarely use it.

    Second: Check for Physical Blockage

    If Bluetooth isn’t the culprit, the next most common cause is simple: dust, lint, or oily residue sitting directly in the earpiece grille, which is easy to overlook because it’s such a small, narrow slot compared to the main speaker.

    Look closely at the top of your phone’s screen, just above the display, for a thin horizontal slot — that’s the earpiece. Gently clean it with a soft, dry brush (an old, clean toothbrush works well) or a few short bursts of compressed air held a few inches away. Avoid anything sharp or metal, and avoid liquids entirely. It’s also worth removing any case and screen protector temporarily, since a poorly fitted case lip or a screen protector that extends too far can partially cover the earpiece slot without being obvious at a glance.

    If sound comes back clearly after cleaning, that confirms this was the issue, and it’s worth building a habit of an occasional gentle clean, especially if you carry your phone in a pocket with lint-prone fabric.

    Third: A Genuine Earpiece Hardware Fault

    If you’ve ruled out Bluetooth and confirmed the earpiece is clean, and it’s still silent specifically during calls while everything else works fine, this points toward the earpiece itself having failed — a connector coming loose, or the small speaker component wearing out. This is more likely if the problem appeared suddenly after a drop, or gradually got quieter over weeks or months before going silent entirely, or followed any water exposure.

    The good news here is that this is one of the more affordable and straightforward phone repairs, since it’s a small, self-contained component rather than something tied deeply into the motherboard on most models.

    A Quick Way to Confirm Which One You’re Dealing With

    Before assuming the worst, run this simple sequence: turn off Bluetooth completely, clean the earpiece area gently, then make a test call to a friend or use a voicemail test line. If sound returns at any point, you’ve found and fixed your cause. If it’s still silent after both of those steps, and you’ve confirmed the main speaker works fine for everything else, you’re very likely looking at a hardware repair rather than something you can resolve yourself.

    What About Software?

    Software is a real but smaller factor here, usually showing up as a temporary glitch rather than the root cause. A simple restart clears out a surprising number of one-off audio routing errors, and it’s worth trying before anything else simply because it costs nothing. If restarts don’t help and you’re on Android, booting into Safe Mode can reveal whether a third-party app is interfering with audio routing — if the earpiece works normally there, a recently installed app is worth investigating and possibly uninstalling. (This is the same Safe Mode technique covered in more depth in our guide on a phone that keeps restarting by itself, if you’re dealing with both issues at once.)

    When to See a Repair Technician

    If Bluetooth is off, the earpiece is visibly clean, a restart hasn’t helped, and the problem is isolated specifically to calls while music and video audio work normally through the main speaker, this is a genuine hardware repair situation rather than something to keep troubleshooting at home. It’s a relatively minor, well-understood repair, and getting it looked at sooner rather than later is worthwhile, since a partially failing earpiece connector can sometimes be a sign of other internal wear worth catching early. If you’re weighing whether it’s worth fixing given your phone’s age, our repair vs. replace guide walks through how to think about that.

    Frequently Asked Questions

    Why does my speaker work for music but not calls? Because your phone has two separate speakers for these purposes. Music and videos use the main speaker; calls default to the earpiece unless you switch to speakerphone. A fault or blockage isolated to the earpiece won’t affect music at all, which is exactly why this symptom pattern is so specific and useful for diagnosis.

    Can a software update fix a silent earpiece? Occasionally, if the cause is a software routing bug rather than physical blockage or hardware failure. It’s worth checking for and installing any pending updates as a low-effort step, but if the earpiece is physically blocked or has failed, no software update will resolve it.

    Does this happen more after a phone has been dropped? Yes. A drop can loosen the earpiece connector internally even without any visible external damage, which is one of the more common reasons this issue appears somewhat suddenly rather than gradually.

    Is fixing an earpiece speaker expensive? Generally, no — it’s typically one of the more affordable phone repairs, since the earpiece is a small, self-contained component rather than something integrated deeply with the rest of the phone’s internals on most models.

  • Should You Repair Your Phone or Just Replace It?

    There’s a specific kind of hesitation that sets in when your phone breaks and you’re standing at the crossroads of paying for a repair or just biting the bullet on a new one. It’s rarely a purely financial decision either — there’s the hassle of setting up a new phone, the sentimental pull of a device you’ve had for years, and the nagging worry that fixing it now just means it breaks again in six months. A simple rule of thumb cuts through a lot of that noise: if the repair costs more than about half of what a comparable replacement would run you, replacement is usually the better move. If it’s under that threshold, repair tends to make more sense, especially if the phone is otherwise working well and isn’t too old. But like most rules of thumb, it works best with a bit of context around it.

    Start With a Real Number, Not a Guess

    The first step is getting an actual repair quote rather than estimating. Prices vary more than people expect, so it’s worth knowing roughly what you’re dealing with. A screen replacement typically runs anywhere from $79 to $399 depending on the phone. Battery replacement tends to be more modest, usually $49 to $99. A charging port repair often lands between $59 and $129, back glass replacement between $89 and $199, and a camera module repair somewhere around $79 to $249. Water damage is trickier — cleaning and repair attempts run $99 to $249, but it’s also one of the more common cases where repair simply isn’t possible, depending on how much corrosion has set in.

    Then Compare It Against What Replacement Actually Costs

    Once you have a real repair number, look up two things: the price of a new equivalent or upgraded model, and the price of a certified refurbished version of your exact phone. Refurbished units, particularly certified ones, often run 30% to 50% cheaper than buying new, and they usually come with their own warranty, which makes them a genuinely underrated middle option that a lot of people forget to consider.

    Where the 50% Rule Bends

    The straightforward math doesn’t always tell the full story, and there are situations where it makes sense to lean one way or the other even outside the strict 50% threshold.

    Repair tends to be worth it even above that halfway mark if the phone is less than two years old, if this is the only real problem it has, if you’d genuinely rather avoid the hassle of migrating everything to a new device, or if the battery is still healthy — above roughly 85% capacity — meaning the phone has real life left in it once the current issue is fixed.

    Replacement starts to look better even below the 50% mark if the phone is four or more years old and no longer receiving security updates, if this is the second or third repair on the same device within a year (a pattern that suggests you’re really paying for a phone that’s simply wearing out), if the battery is already degraded below 80%, meaning you’re effectively signing up for two repairs instead of one, or if the phone already feels sluggish for reasons that have nothing to do with the current problem — an aging processor or not enough RAM for how you use it today.

    Thinking About It by Age

    For a phone under a year old, repair is almost always the right call, even for something as pricey as a full screen replacement, since there’s so much useful life left ahead of it — and if it’s still under warranty, plenty of issues may not cost you anything at all.

    Between one and three years old, repair is generally still the smart move unless the cost creeps up toward 60% or more of what replacement would cost, or the same problem keeps recurring.

    Three to five years old is really where the decision gets genuinely difficult. It’s worth checking whether the phone is still receiving security updates at all — this matters more than people give it credit for, since an unsupported phone is a real security risk regardless of how it’s holding up physically. It’s also worth checking battery health directly, since anything under 80% suggests you should be budgeting for a battery replacement in the near future regardless of what else is going on, and thinking honestly about whether the current repair addresses everything wrong with the phone or just one symptom of general wear.

    Past five years, replacement usually makes more sense unless the phone holds specific value to you — genuine sentimental attachment, a feature you rely on that newer phones dropped, like a headphone jack, or a size that simply isn’t made anymore. Security update support has very likely ended by this point, and that’s a real risk rather than just an inconvenience worth brushing off.

    The Cost People Tend to Forget

    Replacing a phone isn’t just the sticker price. It’s the hours spent transferring photos, logging back into every app, re-pairing headphones and watches, and adjusting to a new layout or gesture system. For a lot of people, that adds up to something like $50 to $150 worth of their own time and patience, and it’s a real cost even if it never shows up on a receipt. Factoring that in tends to nudge borderline decisions back toward repair.

    When Repair Genuinely Isn’t an Option

    Occasionally the decision gets made for you. Water damage with visible corrosion on the logic board often isn’t economically repairable. A failure at the motherboard level, rather than a single component, tends to push repair costs high enough that replacement becomes the obvious choice. And on phones five years or older, the specific part you need may simply be discontinued, which is becoming more common as manufacturers move on to newer models.

    Frequently Asked Questions

    Is it worth repairing a phone that’s out of warranty?
    Yes, as long as the repair cost stays under the roughly 50% threshold and the phone is otherwise in decent shape. Warranty status affects how much you’ll pay, not whether the repair itself makes sense.

    Does repairing my phone lower its future resale value?
    A professional repair using quality parts typically has minimal impact on resale value. In fact, an unrepaired crack tends to hurt resale value far more than a properly documented repair does.

    Should I repair my phone if I’m planning to upgrade in six months anyway?
    If it’s an inexpensive fix, under $100 or so, and it keeps the phone fully functional in the meantime, it’s usually worth doing, since it also protects your trade-in or resale value until then. For a more expensive repair, it’s often better to just hold out for the planned upgrade.

    Is a refurbished phone a good alternative to repairing?
    Yes, particularly if it’s certified refurbished through the manufacturer or a major retailer. You get warranty coverage and effectively a fresh battery, often for less than what a repair on an aging device would cost you anyway.

  • Your Phone Fell in Water. Here’s What to Actually Do

    There’s a specific jolt of panic that comes with watching your phone disappear into a puddle, a sink, or a pool, and it’s usually followed almost immediately by the instinct to grab it, dry it off, and check if it still works. That instinct, understandably, is the exact thing that causes the most damage. The single most important thing you can do is turn the phone off immediately and resist the urge to check it — powering on a wet phone is what causes permanent short-circuit damage, far more often than the water exposure itself does. And while we’re at it: skip the rice. It’s one of the most persistent myths in phone care, and it doesn’t actually do what people think.

    What to Do in the First Few Minutes

    Get the phone out of the water and power it off right away. If it’s already off on its own, don’t turn it on to see if it’s fine — that single decision is the biggest cause of permanent damage in water incidents. Remove the case along with the SIM card and tray, since trapped water sitting under a case speeds up corrosion. Gently dry the outside with a soft cloth, but avoid shaking the phone, which can push water deeper into ports and speakers rather than out. And don’t plug it in to charge, even if you’re worried about the battery — charging a wet phone risks an internal short circuit.

    Why Rice Doesn’t Really Work

    Rice became folk wisdom for a reasonable-sounding reason: it’s porous, it’s usually sitting in the kitchen, and it feels like it should absorb moisture. In practice, though, it’s a fairly weak desiccant compared to materials actually designed for the job, and more importantly, it doesn’t pull moisture out of the tight spaces that actually matter — the charging port, the speaker grille, the seams around buttons. Rice also tends to leave dust and starch behind, which can work its way into those same ports and create a second problem on top of the first. The reason rice has such a good reputation is mostly survivorship bias: plenty of phones survive water exposure regardless of what happens afterward, and rice ends up getting credit it didn’t really earn.

    What Actually Helps

    If you happen to have silica gel packets around — the ones that come tucked into shoe boxes or vitamin bottles — this is your best option. Sealing the phone in an airtight container with several packets for 24 to 48 hours gives it a real chance, since silica gel is genuinely designed to pull moisture out of the air, unlike rice.

    If you don’t have any on hand, simply leaving the phone in a dry, room-temperature space for a full 48 hours works reasonably well too. Patience matters more here than any clever trick. What you want to avoid is any kind of heat — no hairdryers, no ovens, no leaving it in direct sun, and definitely no microwaves. Heat can warp internal components or damage the battery, occasionally causing it to swell, which in rare cases becomes a genuine fire risk. It’s also worth gently angling the phone so the charging port and headphone jack, if it has one, face downward, which encourages any remaining water to drain out rather than pool inside.

    Checking If It’s Safe to Turn Back On

    After the waiting period, look closely at the camera lenses for any internal fogging — if you see it, the phone is still holding moisture and needs more time. If your phone has a liquid contact indicator, usually visible inside the SIM tray slot, check whether it’s fully triggered to red or pink; this is mainly something manufacturers use to determine warranty eligibility rather than a precise diagnostic tool, but it’s still useful information. And simply feel the phone all over, including the ports, to confirm it’s completely dry to the touch.

    If everything checks out, go ahead and power it on. If it doesn’t respond, try plugging it into a charger and waiting thirty minutes before attempting again — sometimes the issue is simply that the battery needs a charge, not that anything is actually damaged.

    Signs That Call for a Professional

    If you open the phone up, or a technician does, and there’s visible corrosion — a greenish or white residue around the ports or battery — that’s a clear sign professional repair is needed. The same goes for any discoloration, dark spots, or lines appearing on the screen, or if the phone powers on but the speaker, microphone, or charging port stop working properly. And if the battery looks swollen at any point in this process, stop using the phone immediately; that’s a safety concern that needs attention right away, not something to wait out.

    A Few Things Worth Avoiding Entirely

    Skip the hairdryer or heat gun, no matter how tempting it is to speed things up. Don’t shake or tap the phone trying to dislodge water. Don’t blow into the charging port either — it tends to push moisture deeper rather than out. Don’t charge the phone while there’s any chance moisture remains inside. And try not to cut the waiting period short just because the outside looks dry, since the parts that matter most are the ones you can’t see.

    Frequently Asked Questions

    How long should I wait before turning on a water-damaged phone?
    A minimum of 24 hours, though 48 hours is safer, ideally using silica gel or a genuinely dry environment. Turning the phone on too early is, by a wide margin, the most common mistake people make.

    Is a phone water damage warranty claim ever covered?
    Standard manufacturer warranties almost always exclude water damage explicitly. Extended plans like AppleCare+ or carrier insurance are a different story and often do cover it, typically with a deductible attached.

    Can salt water damage be fixed the same way as fresh water?
    Salt water is considerably more corrosive and far more time-sensitive than fresh water. If that’s what your phone was exposed to, getting it to a professional for ultrasonic cleaning of the internals within 24 hours gives you a meaningfully better chance than relying on home drying alone.

    My phone is IP68 water resistant — can it still get water damaged?
    Yes, it can. Water resistance ratings are based on specific lab conditions — still water, limited depth, limited time — and that resistance naturally degrades over the life of the phone, especially after drops or any repair work that disturbs the internal seals. It’s a meaningful layer of protection, not an absolute guarantee.

  • Phone Stuck on the Logo Screen? Here’s How to Get It Moving Again

    You press the power button, the familiar logo pops up like it’s about to boot normally, and then… nothing. It just sits there. Maybe it flickers and tries again a minute later, looping back to the same screen. It’s an unsettling moment, mostly because a frozen logo screen looks a lot like a dead phone, when in reality it’s usually something far more fixable: the operating system is failing partway through loading, caught in what’s commonly called a boot loop.

    The good news is that in the vast majority of cases, this resolves without losing any of your data, and the steps differ a little depending on whether you’re dealing with an iPhone or an Android device.

    First, Figure Out How Long It’s Actually Been Stuck

    This matters more than people realize. If it’s been under ten minutes, this might just be a slow, normal boot after a recent update — the best thing to do is leave it alone rather than interrupting it. If it’s been ten to thirty minutes with occasional flickering or restarting, that’s more likely a genuine soft boot loop, and the steps below are worth trying. If it’s been hours with total silence — no vibration, no response to anything — that leans more toward a hardware issue, which we’ll get to.

    If You’re on an iPhone

    The first thing worth trying is a force restart, and the exact button sequence depends on your model. On an iPhone 8 or later, quickly press Volume Up, then Volume Down, then hold the Side button until the Apple logo appears. On a 7 or 7 Plus, it’s Volume Down held together with the Side button. On a 6s or earlier, it’s Home and the Side (or Top) button held together. This single step resolves the majority of logo-loop situations and doesn’t touch your data at all.

    If that doesn’t do it, the next step is Recovery Mode. Connect the phone to a computer, open Finder on a Mac or iTunes on Windows, and use the same button combination as above — but this time, instead of letting go when the Apple logo appears, keep holding until you see a screen prompting you to connect to a computer. From there, choose Update rather than Restore. Update reinstalls the operating system while keeping your data intact; Restore wipes everything, so it’s worth treating as a genuine last resort rather than a first move.

    One thing worth checking before you do any of this: look closely at the edges of the screen. If it looks slightly lifted or separated from the frame, that can indicate a swollen battery, and in that case, stop trying to power it on and get it to a technician — it’s a safety issue, not just a technical one.

    If You’re on Android

    Start the same way, with a force restart — usually Power and Volume Down held together for ten to twenty seconds, though some models just need the Power button alone held for a similar length of time.

    If that gets it moving but it seems unstable, try booting into Safe Mode. This temporarily disables third-party apps, and if the phone runs fine there, you’ve likely found your problem: something you installed recently is the culprit, and uninstalling the most recent addition usually solves it. The exact way to reach Safe Mode varies a bit by brand, but on most phones it involves holding the Power button, then long-pressing the on-screen Power Off option until a “Reboot to Safe Mode” prompt appears.

    If Safe Mode isn’t the fix, wiping the cache partition is the next reasonable step, and importantly, this is different from a factory reset — it clears out corrupted temporary files without touching your photos, messages, or app data. You’ll need to power the phone off completely, then hold a specific button combination (commonly Power and Volume Up, though this varies by brand) to enter Recovery Mode, navigate using the volume buttons, and select the option to wipe the cache partition before rebooting.

    If none of that works and you’re still stuck, a full factory reset from Recovery Mode will almost always get the phone booting again, but it does erase everything on the device. This is genuinely a last resort — only worth doing if you have a backup, or if the alternative is a phone that simply won’t start at all.

    When It’s Probably Not a Software Problem

    Some signs point more clearly toward hardware rather than something you can fix yourself. If the phone doesn’t respond to any force-restart combination at all, if the issue appeared suddenly after a drop or water exposure, if you notice any discoloration or lines on the screen, or if even Recovery Mode won’t load, these all suggest something physical is going on — often a loose display connector or a damaged component on the motherboard. These are usually fixable by a technician, just not through software steps on your end.

    A Couple of Habits That Prevent This

    Keeping at least 15% of your storage free helps avoid failed updates mid-installation, which is one of the more common triggers for a boot loop in the first place. And it’s worth resisting the urge to interrupt a software update once it’s started, even if it seems to be taking a while — interrupting partway through is one of the more reliable ways to end up stuck on a logo screen. Regular backups, whether to the cloud or a computer, also mean that if a factory reset ever does become necessary, it’s a minor inconvenience rather than a genuine data-loss emergency.

    Frequently Asked Questions

    Will I lose my data if my phone is stuck on the logo screen?
    Not necessarily. Force restarting and clearing the cache both preserve your data completely. It’s only a full factory reset or Restore that wipes everything, and that’s meant to be a last resort rather than a default step.

    How long is too long for a phone to be stuck on the logo screen?
    Somewhere past fifteen to twenty minutes without any progress, especially if you’re seeing repeated restart loops, is a reasonable point to stop waiting and start troubleshooting.

    Can a low battery cause a boot loop?
    Yes, it can. If the battery is critically low or beginning to fail, some phones will loop on the logo screen rather than booting normally. It’s worth plugging in and letting it charge for at least thirty minutes before assuming it’s a deeper issue.

    Is this covered under warranty?
    If the cause turns out to be software-related rather than physical damage, and the phone is still within its warranty period, this is typically covered at no cost by the manufacturer.

  • What It Actually Costs to Fix a Cracked Phone Screen

    That sinking feeling when your phone slips out of your hand and you hear the crack before you even look down — everyone who’s owned a smartphone for more than a couple of years knows it. The first question after “how bad is it” is almost always “how much is this going to cost me.” The honest answer is that it depends a lot on your phone, and the range is wider than most people expect: anywhere from about $79 to nearly $600.

    Why the Price Swings So Much

    A screen repair isn’t one standardized job — it varies based on your phone’s make and model, whether you go through the manufacturer or a local repair shop, and the display technology inside your particular phone. Newer flagship phones with AMOLED or OLED displays cost noticeably more to repair than older or budget models with simpler LCD screens, mostly because the parts themselves are more expensive and more delicate to install correctly.

    iPhone Screen Repairs

    If you’re an iPhone owner, Apple’s own repair pricing for a base model like the SE tends to sit between $129 and $169, climbing to somewhere around $229 to $279 for a standard iPhone 13 through 15, and up to $329 to $399 for the Pro and Pro Max models. Third-party shops usually undercut all of these by a meaningful margin — often $69 to $99 for older models and $149 to $229 for Pro-tier phones — but the tradeoff is worth understanding. Apple uses genuine parts and preserves things like True Tone display calibration and Face ID accuracy without any extra steps; a third-party shop’s quality really depends on whether they’re using OEM or aftermarket glass, which is worth asking about directly before you book anything.

    Samsung Galaxy Screen Repairs

    Samsung’s pricing follows a similar shape. Budget A-series phones run about $99 to $149 through Samsung directly, or $69 to $110 through a third-party shop. Standard Galaxy S phones land around $229 to $279 officially, or $129 to $189 elsewhere. The real jump comes with the Ultra and Fold models, where official repairs can run $299 all the way to $599 — foldables in particular are expensive because of the flexible display and hinge mechanism, which is genuinely worth factoring in before buying one if you’re someone who drops phones occasionally.

    Google Pixel Screen Repairs

    Pixel repairs tend to be a bit gentler on the wallet. The budget-friendly a-series models run roughly $99 to $139 through Google, or $79 to $120 through independent shops, while the standard and Pro Pixel models land around $199 to $279 officially and $109 to $179 through third parties.

    Budget and Mid-Range Android Phones

    If you’re using a Motorola, OnePlus, Nothing phone, or similar mid-range Android device, you’ll generally find the most affordable repairs here — typically $59 to $149 through a local repair shop, since these brands often don’t have the same widespread official repair network that Apple and Samsung do in most regions. The parts themselves also tend to be cheaper, since they’re not premium flagship glass.

    What’s Really Driving the Final Number

    A few specific factors tend to make the biggest difference in what you’ll actually pay. Whether the repair replaces just the outer glass or the full display assembly matters a lot — on most modern phones, the glass is fused directly to the display, so a full assembly replacement is usually required even for a surface-level crack, and that’s pricier than the simple glass swap that older phones sometimes allowed. Genuine versus aftermarket parts is another big one: genuine parts cost more upfront but tend to hold up better over time in terms of brightness, color accuracy, and touch responsiveness. And if there’s damage beyond the glass — the display itself, the frame, or the battery — the price climbs accordingly. If you’re covered by something like AppleCare+, Samsung Care+, or carrier insurance, all of this might be moot anyway, since you’d likely just be paying a flat deductible somewhere between $29 and $99 instead of the full retail price.

    Choosing Between Official and Third-Party Repair

    Going through the manufacturer makes the most sense if your phone is still under warranty or covered by insurance, if you need Face ID or another biometric system calibrated precisely, or if resale value matters enough to you that a documented, genuine-parts repair is worth paying for. Third-party repair tends to be the better call when cost is the priority on an older phone, when you need it fixed same-day without waiting for a mail-in service, or when there’s simply no official repair location nearby. If you do go the third-party route, look specifically for shops that state upfront they use OEM-quality parts and back their work with a warranty — ideally 90 days or longer.

    A Few Ways to Avoid Overpaying

    Getting at least two quotes before committing, especially at independent shops, tends to reveal a surprising amount of price variation for the exact same repair. It’s also worth explicitly asking whether a quote covers just the glass or the full display assembly, since that distinction is where most of the price confusion comes from. Some credit cards include phone protection as a card benefit, which is easy to forget about and worth checking before you pay out of pocket. And if your phone is already three years old or more, it’s worth pausing to weigh the repair cost against simply replacing the phone — a decision that deserves its own dedicated thinking, which is exactly what our repair-versus-replace guide walks through.

    Frequently Asked Questions

    Is it cheaper to fix a phone screen myself with a DIY kit?
    DIY kits, usually $20 to $60, are cheaper upfront, but they carry real risk. A slip during installation can damage the display, the battery connector, or the phone’s water-resistance seal, turning what should have been a $100 repair into something closer to $300. It’s really only worth attempting if you already have some experience with electronics repair.

    Does a cracked screen affect phone resale value?
    Yes, and often more than people expect — trade-in and resale value can drop by 30% to 50% with visible screen damage. In most cases, paying for the repair before selling actually nets you more money overall than selling the phone as-is.

    How long does a screen repair take?
    Third-party shops can often turn a repair around same-day, sometimes in 30 to 90 minutes. Manufacturer service is also same-day if done in a physical store, but mail-in service through the manufacturer can take anywhere from three to seven business days.

    Will a screen replacement void my warranty?
    Using an authorized repair provider won’t void your warranty. Going through an unauthorized third-party shop can void what’s left of your manufacturer warranty on some brands, so it’s worth checking your specific terms before booking if warranty coverage still matters to you.

  • Phone Keeps Restarting By Itself? Here’s What’s Actually Going On

    There’s a particular kind of annoyance that comes from your phone restarting itself in the middle of something — a text you were typing, a call, a photo you were about to take. It vanishes, the screen goes black, and thirty seconds later you’re staring at your lock screen wondering what just happened. If this is becoming a pattern rather than a one-off, the good news is that it’s usually solvable, and it rarely means your phone is dying.

    Most random restarts come down to one of five things: a misbehaving app, a buildup of corrupted system files, a battery that’s starting to wear out, the phone overheating, or, less commonly, an actual hardware fault. The trick is narrowing down which one you’re dealing with, because the fix looks different depending on the cause.

    Start Here Before You Panic

    Before assuming the worst, run through this short sequence. It resolves the issue for a surprising number of people.

    Restart the phone manually first — it sounds almost too simple, but a manual restart clears out temporary glitches that a forced, unplanned restart doesn’t. Then check for pending updates, both for the operating system and your apps, since an outdated app is one of the most common triggers. Take a look at your battery usage in Settings and see if anything is behaving strangely — one app eating far more power than it should is often the smoking gun. If storage is running low, under about 10% free space, clear some out, because a nearly-full phone can become unstable during background tasks. And if none of that helps, try booting into Safe Mode on Android, which temporarily disables third-party apps — if the restarts stop, you’ve found your culprit.

    If you’ve already tried all of that and the restarts are still happening, the cause is probably a bit deeper, so let’s go through the possibilities properly.

    The Most Likely Culprit: A Problem App

    By far the most common cause of random restarts is a single app that’s crashing in a way that takes the whole operating system down with it, rather than just closing on its own. This tends to happen right after installing something new or after an app update, so if you can remember when the restarts started, think back to what you installed or updated around that time.

    Safe Mode on Android is the cleanest way to test this — it temporarily shuts off everything except built-in apps, so if the phone behaves normally there, a third-party app is almost certainly responsible. On iPhone, since there’s no direct equivalent, the more practical approach is offloading apps one at a time, starting with anything installed or updated recently, and watching whether the restarts stop.

    Corrupted System Files

    Sometimes it’s not an app at all — it’s leftover corrupted data sitting in the system cache, often left behind by a software update that didn’t fully complete. This is more common than people realize, especially if the update happened while the phone had low battery or unstable Wi-Fi.

    Clearing the cache partition on Android through Recovery Mode, or resetting all settings on an iPhone (which doesn’t erase your data, just preferences and configurations), tends to clear this up. It sounds like a bigger step than it is — neither of these touches your photos, messages, or app data.

    Overheating Is More Common Than You’d Think

    Phones are built to protect themselves, and one of the ways they do that is by forcing a restart when internal temperatures climb too high. If your phone tends to restart specifically during gaming sessions, while navigating with GPS running, or when it’s charging in direct sunlight, overheating is very likely the explanation rather than anything more serious.

    The fix here is almost embarrassingly simple: take the case off (cases trap heat more than people expect), stop charging if it’s plugged in, and let it sit somewhere shaded for ten to fifteen minutes. If the pattern only shows up during specific heavy use, that consistency is itself the confirmation you need.

    When It’s the Battery

    A battery that’s starting to fail doesn’t always announce itself with obviously short battery life. Sometimes the first sign is instability — the phone restarting because the battery can’t deliver steady power under load, or because it’s misreporting its own charge level, dying suddenly at 30% when it claims to have plenty left.

    You can check this directly. On an iPhone, Settings > Battery > Battery Health & Charging will show you a percentage — anything meaningfully below 80% is worth taking seriously. On Android, the exact path varies by manufacturer, but Settings > Battery > Battery usage history showing sudden, unexplained drops is a similar red flag.

    A Power Button That’s Not Quite Right

    This one’s easy to overlook. If your restarts happen more often when the phone’s been in your pocket or bag, it’s worth checking whether the power button itself feels different than it used to — stickier, looser, slower to spring back. A button that’s getting physically pressed by fabric or pressure inside a bag can trigger restarts that have nothing to do with software at all.

    Malware, Though It’s Rarer Than People Assume

    This is genuinely uncommon, especially on iPhone, and even on Android it usually only becomes a factor if you’ve installed apps from outside the Play Store. But if the restarts started after installing something from an unfamiliar source, it’s worth running a scan with a reputable security app and checking your installed apps list for anything you don’t recognize.

    Storage Running Low

    When a phone’s storage gets critically full, background processes — photo backups, automatic updates, cache management — can start behaving erratically, and on some devices this manifests as instability severe enough to cause a restart. Freeing up roughly 10% of total storage usually settles this down.

    A Software Update That Didn’t Land Well

    If the restarts started right after your phone updated itself, this is very likely your answer, even though manufacturers rarely acknowledge it outright. It happens more than you’d think. Check whether a follow-up patch has been released — often there’s a fix within a week or two. Android phones sometimes allow rolling back to a previous version if the update is causing serious problems; iPhones generally don’t offer that option, so in that case you’re mostly waiting for Apple to release a fix.

    And Sometimes, It’s Genuinely Hardware

    If you’ve worked through everything above and the restarts are still happening, especially if the phone feels warm even sitting idle, or if you notice any swelling around the battery area, this points toward a hardware issue rather than software. A swollen battery in particular is worth taking seriously as a safety matter, not just an inconvenience — stop using the phone and get it looked at.

    Frequently Asked Questions

    Will a factory reset fix random restarts?
    Often, yes, if the underlying cause is software-related. Back up your data first, since a factory reset wipes everything on the device — but for a stubborn software issue, it’s usually effective.

    Can a cracked screen cause my phone to restart?
    Not directly in most cases, but if the crack came with internal damage to a connector or affected the battery compartment, that kind of physical damage absolutely can cause instability, restarts included.

    Is it normal for a phone to restart once a month?
    An occasional, isolated restart — particularly right after an update — isn’t unusual. What’s worth investigating is a pattern: several restarts a week with no obvious trigger.

    Does restarting a phone reduce battery life over time?
    No. A manual restart is completely safe for the battery and is actually a healthy habit, not something to avoid.