Mobile Tech Today

Guides

  • Hotspot Connects But No Internet? Ask This First

    If every device you connect to your hotspot shows the same “no internet” message, the problem is almost always on the phone’s side — a carrier restriction, Data Saver blocking shared traffic, or a mismatched APN setting. If it’s only happening on one specific device while others connect and browse just fine, the problem is on that device, usually a VPN, a Private DNS setting, or a corrupted network profile. Figuring out which of those two situations you’re in first saves you from troubleshooting the wrong end of the connection entirely.

    Test This Before Anything Else

    If you have access to a second device, whether that’s another laptop, a tablet, or a friend’s phone, connect it to your hotspot and see what happens. (This same swap-and-compare approach is what settles wireless charging problems too — isolating whether an issue follows the device or the connection is one of the fastest ways to diagnose almost anything wireless.) If it also fails to get online, you can be fairly confident the issue lives with your phone. If it connects and works normally while your original device still can’t get online, the problem is isolated to that one device, and no amount of fiddling with your phone’s hotspot settings is going to fix it.

    If you don’t have a second device handy, there’s still a useful clue available: does your phone itself have working internet, either over Wi-Fi or cellular data, right now, separate from the hotspot? If your phone can browse normally on its own but sharing that connection fails for everyone who tries to connect, that also points toward a phone-side sharing setting rather than a carrier outage.

    If It’s Failing for Every Device

    Start with the setting most people don’t even realize exists specifically for this. Many phones include a Data Saver or similar background-data-restriction feature, and depending on how it’s configured, it can allow your own apps to use data normally while quietly blocking data from reaching devices connected through your hotspot. On Android, check Settings > Network & Internet > Data Saver and confirm it’s either off or that your hotspot function is explicitly allowed to bypass it. On iPhone, check Settings > Cellular and scroll down to see if there’s a data-saving mode enabled that might be affecting Personal Hotspot specifically.

    From there, it’s worth confirming your carrier plan actually includes hotspot or tethering data in the first place. Some plans include regular data but charge separately for, or simply don’t include, hotspot usage, and in that case, the hotspot may appear to connect perfectly on the surface while your carrier silently blocks the actual data from flowing through. A quick call or check through your carrier’s app can confirm whether hotspot access is active on your specific plan.

    An outdated or incorrect Access Point Name setting is another common cause, particularly if you’ve recently switched carriers, gotten a new SIM, or your phone recently received a major software update. The APN is essentially the address your phone uses to reach your carrier’s data network, and if it’s misconfigured, regular browsing on the phone itself can sometimes still work while hotspot sharing specifically fails. This setting is usually found under Settings > Network & Internet > Mobile Network > Access Point Names on Android; iPhone typically manages this automatically through carrier settings updates, so checking for a pending carrier settings update under Settings > General > About is the equivalent step there.

    If none of that resolves it, a full restart of the phone is worth doing before moving to anything more involved, since it clears out a meaningful share of temporary networking glitches that build up during normal use. Toggling Airplane Mode on and off, waiting about ten seconds in between, accomplishes something similar and is worth trying if you’d rather not restart the whole phone.

    If It’s Only Failing on One Specific Device

    This is genuinely good news for your phone, since it means the hotspot itself is working correctly, and the fix lives entirely on the other end.

    A VPN active on that specific device is one of the more common causes, since VPNs route traffic through their own servers, and if that VPN service is experiencing an issue or is misconfigured, it can make it look exactly like the hotspot itself has no internet, even though the connection between the device and your phone is perfectly fine. Turning the VPN off completely and testing again quickly rules this in or out.

    A Private DNS or custom DNS setting on that device can cause something similar. If a specific DNS server that device is configured to use is down, slow, or unreachable through your particular carrier’s network, that device may show connected with no internet while every other device using standard DNS settings connects normally. Switching that device’s DNS setting back to automatic, or trying a widely used public DNS service, is worth testing.

    It’s also worth simply forgetting the saved Wi-Fi network on that specific device and reconnecting from scratch, entering the password fresh rather than relying on a saved profile. Saved network profiles occasionally hold onto outdated or corrupted configuration details that a fresh connection clears out entirely.

    A Frequency Detail Worth Checking

    If you’re using an Android phone and the struggling device is a bit older, it’s worth checking which Wi-Fi band your hotspot is broadcasting on. Some older laptops and devices only support the 2.4GHz band and have trouble properly connecting to a 5GHz hotspot signal, sometimes connecting but failing to actually pass data through cleanly. Android hotspot settings typically let you choose or restrict which band is used, and switching to 2.4GHz specifically, even though it’s technically slower, resolves this particular mismatch for older or less capable devices.

    When to Suspect Something Broader

    If you’ve worked through the relevant section above and nothing has changed, it’s worth confirming there isn’t a broader outage or restriction happening on your carrier’s network as a whole, which no amount of settings adjustment on either device will fix. Checking your carrier’s own status page or calling support directly can confirm whether this is a known, wider issue rather than something specific to your phone or the connecting device.

    Frequently Asked Questions

    Why does my hotspot show connected but nothing loads? This almost always means data isn’t actually flowing through the connection, even though the Wi-Fi link itself is established. Common causes include a carrier hotspot restriction, a Data Saver setting blocking shared traffic, an outdated APN configuration, or, if it’s isolated to one device, a VPN or DNS setting on that specific device.

    Does Data Saver mode really block hotspot internet even if my phone has data? Yes, on many phones. Data Saver is designed to restrict background data usage, and depending on how a specific phone implements it, hotspot-shared data can get caught in that restriction even while the phone’s own apps continue working normally.

    Why does my hotspot work for some devices but not others? This pattern points toward something specific to the struggling device rather than your phone, most often an active VPN, a custom DNS setting, or an older device that only supports the 2.4GHz Wi-Fi band rather than 5GHz.

    Do I need a specific plan to use my phone’s hotspot? Often, yes. Many carrier plans separate regular data from hotspot or tethering data, and some don’t include hotspot access at all without an add-on. Checking directly with your carrier is the most reliable way to confirm whether this applies to your specific plan.

  • Phone Volume Buttons Not Working? Start With This One Check

    If your volume button still physically clicks but the volume doesn’t change, the cause is almost always software — a case pressing on it, an accessibility feature intercepting it, or a Bluetooth device taking over audio routing. If the button feels stuck, mushy, or doesn’t click at all, the cause is more likely physical, ranging from trapped debris to actual hardware damage. Checking which one applies to you first saves you from trying fixes aimed at the wrong problem entirely.

    Press the volume button on the side of your phone right now, slowly, and pay attention to whether it actually moves and clicks the way it always has. That one detail decides almost everything about what happens next.

    If the Button Clicks Normally But Nothing Happens

    This is honestly the better outcome, because it almost always means the button itself is fine and something in software is intercepting or overriding it before it reaches the volume system.

    Start by removing your case entirely, even if it’s never seemed to interfere before. Cases can shift slightly over time, especially after a drop or repeated removal and reattachment, and a case that’s even slightly out of alignment can press against the button just enough to block a clean press without it being obvious to the eye. Test the buttons with the case fully off before ruling this out.

    If that’s not it, check whether an accessibility feature is quietly taking over the volume keys. On Android, a feature called TalkBack, built for visually impaired users, has a known history of repurposing the volume buttons for its own shortcuts, which makes them stop controlling volume in the normal way entirely. Head into Settings, then Accessibility, and look for TalkBack specifically, turning it off if it’s enabled and you’re not intentionally using it. On iPhone, a similar thing can happen with certain AssistiveTouch or accessibility shortcut configurations, so it’s worth checking Settings > Accessibility for anything that might have been toggled on by accident.

    It’s also worth confirming which volume you’re actually looking at. On iPhone in particular, there’s a real difference between media volume and ringer volume, and depending on what’s playing or not playing at the moment, the buttons might be adjusting one while you’re watching the other. Try pressing the buttons while music or a video is actively playing, and separately while nothing is playing, to see if the behavior changes between the two.

    If none of that explains it, a Bluetooth device can sometimes take over audio routing in a way that makes it seem like your buttons have stopped working, when really they’re adjusting the volume of a connected device you’re not paying attention to. Turning Bluetooth off completely and testing again is a quick way to rule this out.

    If the Button Feels Stuck, Mushy, or Doesn’t Click At All

    This points more toward something physical, but it’s still often fixable without a repair, so it’s worth working through a few safe steps before assuming the worst.

    Debris is the most common cause by a wide margin. Dust, lint, or small crumbs can wedge into the narrow gap around a volume button over months of being in a pocket or bag, and this often makes a button feel gritty or slightly resistant rather than completely dead. A few short bursts of compressed air, held at an angle so it pushes debris out rather than deeper into the phone, is worth trying first. Holding the phone with the button facing downward while doing this helps gravity work in your favor.

    If compressed air doesn’t loosen it, gently and repeatedly pressing the button, sometimes called the rapid-click method, can occasionally dislodge whatever’s stuck, especially if the button feels mushy rather than completely rigid. This is worth doing gently rather than forcefully, since pressing too hard on a button that’s already under strain risks pushing debris further in or damaging the mechanism underneath.

    It’s worth resisting the urge to use anything sharp, like a pin or a paperclip, to try to dig debris out directly. That approach can easily scratch the phone’s frame or puncture the small membrane underneath the button, turning a simple cleaning job into an actual hardware failure.

    If the phone has been exposed to any moisture recently, even something like humidity, sweat, or a light splash, that’s worth considering as a possible cause too, since dried residue from moisture can leave the area sticky in a way that mimics general debris buildup, but responds better to a light, careful cleaning than to compressed air alone.

    When It’s Likely a Genuine Hardware Issue

    If the button remains stuck, unresponsive, or physically doesn’t move at all after trying the steps above, or if it’s visibly bent or dented, especially following a drop, this points toward internal damage to the button’s mechanism or its connection to the phone’s internal flex cable. This is a real repair situation rather than something to keep working at yourself, since forcing a bent or jammed button can end up causing more damage than it fixes.

    It’s also worth checking whether a software glitch might still be layered on top of a hardware issue. If you’re on Android, booting into Safe Mode briefly disables third-party apps, and if the button suddenly responds normally there, an app is interfering on top of whatever physical wear is present, which is useful information to mention if you do end up taking it in for repair.

    A Practical Workaround in the Meantime

    If you’re waiting to get the button looked at, both iPhone and Android offer on-screen alternatives that let you keep using your phone normally in the meantime. On iPhone, AssistiveTouch under Settings > Accessibility > Touch adds an on-screen button that includes volume control among its options. On Android, most manufacturers include a similar accessibility menu option, or a dedicated on-screen volume control can be added through a widget or accessibility shortcut, depending on your specific phone.

    Weighing the Repair

    A volume button repair is generally on the more affordable end of phone repairs, since it’s a small, self-contained mechanical part rather than something integrated deeply into the rest of the phone. If your phone is a few years old and this isn’t the only issue it’s dealing with, it’s worth thinking through whether a repair still makes sense using our repair vs. replace guide before committing to the cost.

    Frequently Asked Questions

    Can a phone case really cause volume buttons to stop working? Yes, and it’s one of the more common causes. A case that’s shifted slightly, is the wrong fit, or has simply worn down after being removed and reattached many times can press on the button enough to interfere with a clean press, even if it worked fine when it was new.

    Why does TalkBack affect my volume buttons specifically? TalkBack is designed to give visually impaired users an alternative way to navigate their phone, and as part of that, it sometimes repurposes physical buttons, including the volume rocker, for its own gestures and shortcuts. This is intentional behavior for TalkBack users, but it can look exactly like a broken button if it gets turned on accidentally.

    Is it safe to use a paperclip or pin to clean out a stuck volume button? It’s best avoided. Anything sharp risks scratching the phone’s frame or puncturing the small membrane underneath the button itself, which can turn a simple debris problem into an actual hardware failure. Compressed air and gentle repeated pressing are safer first steps.

    How much does it typically cost to repair a volume button? It tends to be on the lower end of phone repair costs, since it’s a small, self-contained mechanical component. Exact pricing varies by phone model, so it’s worth getting a specific quote from a repair shop rather than assuming based on other repairs you may have priced out before.

  • Phone Loses Battery While Completely Turned Off? Here’s What’s Normal

    You charge your phone to 100%, power it all the way off, and set it aside for the night. The next morning, you turn it back on and the battery reads 92%, or 85%, or in some cases, it won’t turn on at all. It feels like it shouldn’t be losing anything while it’s genuinely off, and that confusion is fair, but it’s not quite accurate. A phone that’s powered down still isn’t fully asleep in the way people assume, and knowing where the line sits between normal and concerning makes this much less mysterious.

    Run This Test Before Worrying

    Charge your phone to a full 100%, then power it completely off using the actual shutdown option, not just letting the screen go to sleep. Leave it off and untouched for a set period, eight hours is a good benchmark since it roughly matches an overnight stretch, then turn it back on and check the percentage.

    A drop of somewhere around 1 to 5 percent over that time is generally considered normal and not something to worry about. If you’re seeing a drop in the range of 10 percent or more, or the phone won’t turn back on at all after being off for that stretch, that’s a meaningfully different situation and worth investigating further using the sections below.

    Why a Phone Loses Any Charge at All While Off

    This is the part that trips people up, so it’s worth understanding briefly. Even in its most powered-down state, your phone maintains a small internal clock, similar to the one that’s kept your microwave or car radio showing the correct time even after a power outage. That clock needs a continuous, tiny trickle of power to keep running, and it draws that from the battery regardless of whether the rest of the phone is active.

    Beyond the clock itself, some background hardware components stay in an extremely low-power standby state rather than being entirely disconnected from the battery, partly so the phone can boot back up quickly and partly to preserve certain settings and security features. None of this draws much power individually, but added together over several hours, it accounts for that small, expected single-digit percentage drop.

    If the Drop Is in the Normal Range

    If your test came back showing a small, single-digit drop, there’s genuinely nothing to fix here. This is simply how lithium batteries and modern phone hardware behave, and it’s consistent across both iPhone and Android devices, though the exact percentage can vary slightly by model and by how old the battery is.

    It’s worth knowing that this small drain does tend to increase slightly as a battery ages, since an aging battery becomes somewhat less efficient at holding its charge even in this powered-down state. If your phone is a few years old and the drop has crept up gradually over time but is still in a reasonable single-digit range, that’s expected wear rather than a fault.

    If the Drop Is Unusually Large

    A drop well beyond the single-digit range while genuinely powered off points toward one of a few specific causes, and it’s worth working through them in order.

    The Phone Didn’t Fully Power Off

    This sounds almost too simple, but it’s a genuinely common cause. Some phones, particularly certain Android models, have a fast startup or hybrid shutdown mode that keeps some system processes technically running in a low-power state even after you’ve chosen to power off, rather than performing a true, complete shutdown. Check your settings for anything labeled fast boot, quick start, or a similar feature, and try disabling it, then retest with the phone properly and completely off.

    A Failing Battery

    As lithium batteries age, they become less able to hold a charge steadily, and this shows up not just in shorter battery life while using the phone, but also in a faster-than-normal drain even while it’s sitting completely off. If your phone is more than two to three years old, checking your battery health directly is worth doing before assuming anything else. On iPhone, this is Settings > Battery > Battery Health & Charging; on Android, the exact location varies by manufacturer, but it’s typically found somewhere in Settings > Battery.

    A battery health reading below roughly 80 percent is a reasonable point at which this kind of behavior becomes more likely, and it’s consistent with a battery that’s simply reaching the end of its useful life rather than anything else being wrong with the phone.

    A Manufacturing Defect or Internal Short

    In rarer cases, particularly if this behavior started very suddenly on a phone that was previously completely normal, an internal short circuit or a battery cell issue can cause a genuinely faster drain even while off. This is worth taking seriously, especially if you also notice the phone feeling warm even while powered down, or any swelling in the battery area, both of which are signs to stop using the phone and get it looked at rather than continuing to test it yourself.

    The Phone Won’t Turn Back On At All

    If the battery reads essentially empty after being off for a period where it should have held most of its charge, and it won’t power back on even after being plugged in for a while, try charging it for a full 30 minutes before attempting to turn it on again, since some phones need a small amount of charge restored before the power-on sequence will even begin. If it still won’t respond after that, this points more strongly toward either a battery that’s failed more significantly than gradual wear, or a deeper hardware issue.

    What to Do Next

    If your test consistently shows an unusually large drop and you’ve ruled out a fast-boot or quick-start setting being the cause, checking your battery health is the most useful next step, since that number alone often makes clear whether you’re looking at ordinary battery aging or something else. If the battery health looks fine and the drop is still unusually large, or the phone is showing other symptoms like warmth or swelling, that’s worth getting looked at by a technician rather than continuing to troubleshoot on your own, given the safety considerations involved with battery issues specifically.

    If it does turn out to be a battery replacement, and you’re wondering whether that’s worth doing given the age of your phone, our repair vs. replace guide walks through how to weigh that decision.

    Frequently Asked Questions

    Is it normal for a phone to lose any battery while completely off? Yes. A small single-digit percentage drop over several hours is expected, since the phone’s internal clock and some standby hardware continue drawing a small amount of power even in a fully powered-down state.

    How much battery drop while off is considered abnormal? Generally, anything beyond roughly 10 percent over an eight-hour period is worth investigating further, particularly if it’s a consistent pattern rather than a one-time occurrence.

    Can a software update cause a phone to drain faster while off? It’s less common than other causes, but a settings change during an update, particularly around fast boot or quick start features, can occasionally cause this. Checking and disabling any such setting is worth doing as a first step if the drain started right after an update.

    Does this get worse as a phone gets older? Yes, gradually. Aging batteries become somewhat less efficient at holding charge even while off, so a slight increase in this baseline drain over a few years of normal use is expected. A sudden, significant jump is a different matter and worth checking battery health over.

  • Wireless Charging Not Working But Wired Does? Here’s the Real Test

    Plug in a cable and your phone charges without any fuss. Set it on a wireless pad and nothing happens, or it starts and stops, or the percentage barely moves overnight. That contrast is actually useful information, because it already rules out a dead battery or a fried charging circuit entirely. What’s left comes down to three real possibilities, and there’s a quick way to figure out which one you’re dealing with before you spend money on anything.

    The Swap Test

    Grab a different wireless charger if you can, whether that’s a friend’s, one from a store display, or a second one you happen to own, and remove your phone’s case completely. Set the phone on the new charger and watch what happens for a couple of minutes.

    If it charges normally on the different pad, your original charger or your case was the problem the whole time, and the fix is inexpensive and straightforward. If it still doesn’t charge, even with a different pad and no case in the way, the problem lives with the phone itself, and the next question becomes whether that’s software or something physical.

    If the Swap Test Points to the Charger or Case

    This is the outcome most people are hoping for, and it’s more common than people expect. A phone case, even one that seems reasonably thin, can be enough to interfere with the magnetic connection wireless charging depends on, particularly cases thicker than about 3 to 5 millimeters, or ones with a metal component like a kickstand, credit card holder, or decorative plate. Even a case that’s worked fine for months can suddenly start causing issues if it’s warped slightly or if you’ve added a thick mount or grip to the back of it.

    The charger itself is just as often the culprit. Not every wireless charger sold is genuinely Qi-certified, and uncertified chargers can be inconsistent, work at reduced power, or simply fail intermittently even when they otherwise seem to function. It’s also worth checking the power adapter and cable feeding into the wireless pad, since the pad itself doesn’t generate power, it only passes through whatever the adapter behind it is supplying, and a weak or damaged adapter can make an otherwise fine charging pad behave as if it’s broken.

    Alignment matters more than people assume, too. The coil inside your phone and the coil inside the charging pad need to sit fairly precisely on top of each other, and even being off by a small amount can drop charging speed dramatically or stop it from starting at all. If your pad doesn’t have raised edges or a clear placement guide, it’s worth experimenting with slightly different phone positioning before assuming anything is actually broken.

    If the Problem Persists Even With a Different Charger and No Case

    This is where it’s worth asking one more question: did this start right after a software update, or has it been more of a gradual or sudden hardware-feeling failure?

    If It Started Right After an Update

    This points toward a software glitch rather than anything physical, and it’s a genuinely common pattern. Updates occasionally reset or misconfigure charging-related settings without any obvious warning, and a few steps tend to resolve this reliably. A full restart is worth trying first, since it’s the simplest possible fix and resolves a meaningful share of these cases on its own. If that doesn’t help, check your battery or charging settings for anything related to wireless charging specifically, since some phones have a dedicated toggle for fast wireless charging that can get switched off during an update, or an optimized charging feature that’s being overly conservative about when to actually start delivering power.

    On Android, clearing the system cache through Recovery Mode is worth trying as well, since a corrupted cache after a major software update is a known cause of exactly this kind of charging inconsistency, and it doesn’t touch your personal data.

    If It Wasn’t Tied to an Update

    If nothing about your software changed and this either came on gradually over weeks, or suddenly after a drop or any exposure to water, that leans more toward the phone’s internal charging coil itself. This is a small component that receives the wireless signal and converts it into charging power, and it can be damaged by impact even if the rest of the phone looks and works completely fine otherwise.

    One useful way to get more confidence in this conclusion, if you happen to know someone with the exact same phone model, is to compare the two side by side on the same charger under the same conditions. If an identical phone charges wirelessly without issue while yours doesn’t, that’s a strong, concrete signal the problem is specific to your unit’s hardware rather than something universal to the model or a coincidence of settings.

    When It’s Genuinely a Repair Situation

    If you’ve ruled out the charger, the case, alignment, and any recent software update, and a comparison with an identical phone model confirms the issue is isolated to your device, this points toward the wireless charging coil needing repair or replacement. The good news is that wired charging continuing to work fine means the phone’s main charging circuitry and battery are healthy, which usually keeps this repair more contained and predictable than something like a full charging port or battery replacement. If you’re weighing whether it’s worth the cost, particularly on an older phone, our repair vs. replace guide covers how to think through that decision.

    It’s also worth mentioning that in the meantime, wired charging is a perfectly reliable way to keep using your phone normally while you decide what to do, since it doesn’t rely on the same component at all.

    Frequently Asked Questions

    Can a phone case really stop wireless charging from working? Yes, more often than people expect. Thick cases, cases with metal components like a kickstand or card holder, or even a case that’s shifted slightly out of shape can interfere enough with the magnetic connection to stop charging entirely or make it unreliable.

    Does wireless charging damage the battery faster than wired charging? Wireless charging does tend to generate somewhat more heat than wired charging due to how the energy transfer works, and heat is a real factor in long-term battery wear. This is a gradual effect rather than something that would explain a sudden stop in charging, though.

    Why did my wireless charging stop right after a software update? Updates occasionally reset charging-related settings or leave behind cache issues that interfere with wireless charging specifically, even while wired charging continues working normally. This is usually resolved with a restart or a cache clear rather than pointing to anything physically wrong.

    Is it normal for wireless charging to be slower than wired charging? Yes, this is expected and not a sign of a problem. Wireless charging is inherently less efficient than a direct cable connection, so noticeably slower charging speed on its own isn’t something to be concerned about, only a complete failure to charge at all.

  • Texts Not Going Through to One Person? It’s Not What You Think

    There’s a specific kind of worry that creeps in when one person stops getting your texts, or their texts stop reaching you, while every other conversation on your phone works completely fine. It’s easy to start wondering if you’ve been blocked, if they’re avoiding you, or if something’s genuinely wrong between you two. In the overwhelming majority of cases, none of that is true. What looks like a personal problem is almost always a technical routing problem, and once you know where to look, it’s usually a quick fix rather than a mystery.

    Two Questions That Narrow This Down Fast

    Before trying random fixes, it’s worth answering two things clearly, because the cause and the solution look completely different depending on the answers.

    First: is this a cross-platform conversation, meaning one of you has an iPhone and the other has an Android phone, or are you both on the same type of device? Second: is the problem that your texts aren’t reaching them, or that their texts aren’t reaching you? These aren’t the same question, and mixing them up is exactly why so much generic troubleshooting advice feels like it’s aimed at the wrong problem.

    If It’s an iPhone-to-Android (or Android-to-iPhone) Conversation

    This is, by a wide margin, the most common version of this issue, and it comes down to how these two ecosystems try, and sometimes fail, to hand a conversation back and forth between iMessage, standard SMS, and increasingly RCS.

    When you send a text to another iPhone user, it automatically becomes an iMessage, using data or Wi-Fi rather than your carrier’s texting network, and it should show up in blue rather than green. If the other person switches from iPhone to Android, or their number gets reassigned, or they simply stop using iMessage for some reason, your phone can get stuck trying to route through iMessage and quietly failing rather than falling back to a normal text message the way it’s supposed to.

    The fix that resolves this more often than people expect is toggling iMessage off and back on. Go to Settings, then Messages, and turn iMessage off, wait a few seconds, then turn it back on. This forces your phone to properly re-register which of your contacts can actually receive iMessages, rather than continuing to rely on outdated information about someone who switched phones or carriers.

    If that doesn’t help, and you know specifically that the other person switched away from an iPhone, there’s a known issue where their old number can remain registered with Apple’s servers as an iMessage-capable contact even after they’ve moved to Android, which keeps your phone trying to deliver messages the wrong way. Having them visit Apple’s own deregistration tool at Apple’s iMessage deregistration page can clear this up from their end, even though they no longer use an iPhone.

    On the Android side, if you’re the one not receiving messages from an iPhone user, it’s worth confirming your phone’s default messaging app hasn’t changed recently, since a switch between apps like Google Messages and a manufacturer’s own messaging app can sometimes leave one thread pointed at the wrong app entirely.

    If You’re Both on the Same Type of Phone

    When both people are using iPhones, or both are using Android, and it’s still just this one conversation failing, the cause tends to shift toward something specific to that contact entry or thread rather than a cross-platform handoff issue.

    A corrupted or oddly formatted contact entry is one of the more common and least obvious causes. If the phone number is saved with unusual formatting, missing an area code, or duplicated across multiple contact entries, it can confuse how your messaging app routes texts to that specific person while leaving every other contact completely unaffected. Deleting the contact entirely and creating a fresh one, using a clean, standard phone number format, resolves this more often than it seems like it should.

    It’s also worth checking whether the thread itself has simply gotten stuck. Starting a brand new conversation with that contact, rather than continuing in the existing thread, sometimes clears whatever glitch has built up in that specific conversation over time.

    If the Problem Is Sending (Your Texts Aren’t Reaching Them)

    Beyond the causes above, it’s worth checking whether you’ve accidentally blocked the contact yourself, which is easier to do by mistake than people realize, particularly if you once blocked a number that later got reassigned to someone you know. On iPhone, check Settings > Messages > Blocked Contacts; on Android, check your Messages app’s own blocked list, usually found in its settings menu.

    If you’re on a limited or pay-as-you-go SMS plan, it’s also worth confirming you haven’t hit a balance or plan limit specifically affecting SMS while data-based messaging continues working fine, which can create exactly this kind of one-sided confusion.

    If the Problem Is Receiving (Their Texts Aren’t Reaching You)

    This direction has a few causes of its own worth checking. Some phones and carriers apply spam or unknown-sender filtering that can quietly redirect a specific contact’s messages out of your main inbox, particularly if that number was recently reported as spam by other users for unrelated reasons, an occasional but real false positive. Check your Messages app for any spam, filtered, or “unknown senders” folder that might be catching this specific conversation without your knowledge.

    It’s also technically possible, particularly on Android, for the other person to have been inadvertently added to a spam or block list on your device without you realizing it, especially if you were clearing out unwanted contacts or messages in bulk at some point.

    When None of This Works

    If you’ve worked through the relevant sections above and the issue persists, a full reset of your network settings is a reasonably safe next step, since it clears out accumulated Wi-Fi, Bluetooth, and cellular configuration data that can occasionally interfere with message routing in ways that are hard to pin down otherwise. On iPhone, this is Settings > General > Transfer or Reset iPhone > Reset Network Settings; on Android, it’s typically under Settings > System > Reset options. Note that this does reset saved Wi-Fi passwords, so have those handy afterward.

    It’s also worth restarting the phone entirely before assuming anything more serious is going on, since a simple restart resolves a surprising number of software-level glitches that are hard to diagnose directly but disappear once the phone’s had a fresh start.

    Frequently Asked Questions

    Does this mean the other person blocked me? Almost never, even though that’s usually the first fear people have. The overwhelming majority of one-contact messaging issues come down to iMessage and SMS fallback failures, contact formatting problems, or spam filtering, not an actual block. It’s worth ruling out the technical causes above before assuming anything personal.

    Why does this only happen with one specific contact and nothing else? Because the underlying causes, whether it’s an outdated iMessage registration, a corrupted contact entry, or a spam filter catching one specific number, are all tied to that one contact’s data or messaging history specifically, rather than anything affecting your phone or messaging app as a whole.

    Will deleting and recreating a contact lose my message history with them? No. Your message thread is tied to the phone number itself, not the contact entry, so recreating the contact with a clean, correctly formatted number won’t affect your existing conversation history.

    Is this more common with iPhone-to-Android conversations than same-platform ones? Yes, considerably. The handoff between iMessage and standard SMS or RCS is the single biggest source of this specific issue, which is why it’s worth checking that angle first if the affected contact uses a different type of phone than you do.

  • Cracked Screen Protector or Cracked Screen? A 60-Second Test

    That moment right after you drop your phone and see a spiderweb of cracks looking back at you is genuinely stressful, but before you assume the worst, it’s worth knowing that a huge share of the time, what you’re looking at is a cracked screen protector doing exactly the job it was designed to do, not a cracked phone screen at all. There’s a fast, reliable way to tell the two apart, and it takes less time than it took to panic in the first place.

    Why This Is So Easy to Mix Up

    Screen protectors, especially tempered glass ones, are made to sit almost flush against your actual display, close enough that from a glance, cracks in the protector and cracks in the screen underneath can look nearly identical. That’s not an accident. Tempered glass is specifically engineered to fracture and absorb impact energy the same way a car windshield does, which means when it cracks, it’s often because it successfully protected the screen underneath, not because your phone failed to survive the drop. Knowing this going in helps take some of the panic out of the next few minutes.

    The Three Checks, in Order

    1. The Touch Test

    Run your finger gently across the cracked area and try using the phone normally for a moment. Does everything respond the way it should? Tap an app icon, type a few letters, scroll a page. A cracked screen protector will not affect how your touchscreen responds at all, since the actual sensing layer is beneath it. If typing feels laggy in that specific area, certain spots don’t register your tap, or the screen doesn’t respond consistently near the crack, that’s a meaningful sign the damage has reached the actual display, not just the protector on top of it.

    2. The Edge Check

    Look closely at the very edge of your phone, right where the screen meets the frame. Screen protectors typically sit slightly raised above the true edge of the display, sometimes by just a fraction of a millimeter, but often just enough to notice if you look carefully. If you can see any lifting, a visible gap, or the corner of the protector separating from the phone, that’s a strong indicator the crack is in the protector layer, since actual screen glass is fused directly to the phone and won’t lift away like that.

    3. The Angled Light Test

    Turn your phone’s screen off and hold it at a shallow angle under a bright light, a lamp or even your phone’s flashlight from another device works well. Cracks in a screen protector tend to reflect light differently than cracks in the display glass underneath, often looking more like a surface scratch pattern sitting slightly above the phone itself. If you look closely and can make out two distinct, separate layers of cracking, one appearing to float slightly above the other, that’s a fairly clear sign both the protector and the screen underneath have cracks, which changes what you do next.

    If It’s Just the Protector

    This is genuinely good news, and it means you’re looking at a cheap, quick fix rather than a repair. Removing a cracked protector safely is worth doing carefully, since sharp edges and loose glass fragments are a real (if minor) risk. Power the phone off first, both to reduce the chance of accidental touches and to make any remaining cracks easier to see clearly. With clean, dry hands, find a corner where the protector is already lifted or chipped, and gently work a fingernail or the edge of a plastic card underneath it, lifting at a low angle rather than pulling straight up, which helps keep it from shattering further into smaller pieces as you go. If you notice small glass fragments coming loose during removal, stop and carefully clear them away with the edge of your card before continuing.

    Once it’s off, take a moment to genuinely inspect the screen underneath before assuming everything’s fine. Set your wallpaper to a plain white or black background, which makes any cracks in the display stand out far more clearly than they would over a busy home screen, and look the screen over one more time under good lighting.

    A basic tempered glass replacement typically runs somewhere between $10 and $40, with premium ceramic versions running higher, and this is genuinely one of those repairs worth doing yourself rather than paying a shop $30 to $50 just for installation, unless you’re dealing with an unusually expensive protector or simply prefer not to risk it.

    If the Screen Itself Is Actually Cracked

    If your checks pointed toward real screen damage, whether that’s unresponsive touch areas, visible cracks reaching all the way to the edge of the phone frame, or discoloration and lines appearing on the display, this is a different situation entirely, and it’s worth understanding what you’re actually looking at cost-wise before deciding what to do. Screen repair costs vary quite a bit depending on your specific phone model and whether you go through the manufacturer or a local shop — our full breakdown of screen repair costs by brand covers the specifics for iPhone, Samsung, Pixel, and budget Android models so you’re not guessing at the number.

    If the phone is a few years old or this isn’t the first issue it’s had, it’s also worth pausing to weigh a screen repair against simply replacing the phone altogether, which our repair vs. replace guide walks through in more detail.

    A Habit Worth Building Going Forward

    Once you’ve either removed a cracked protector or dealt with actual screen damage, it’s worth putting a fresh protector on sooner rather than later, even a basic one. The whole reason this situation is often good news rather than bad is that the protector did exactly what it was designed to do, and going without one, even for a short stretch, means your next drop has nothing standing between the impact and your actual screen.

    Frequently Asked Questions

    Can a cracked screen protector make my touchscreen less responsive? Generally, no. Since the touch-sensing layer sits beneath the protector, a cracked protector on its own typically doesn’t affect responsiveness at all. If you’re noticing lag or unresponsive spots, that’s a stronger sign the crack has reached the actual screen.

    Is it safe to keep using my phone with a cracked screen protector? For a short period, yes, though it’s worth being cautious of sharp edges, particularly if pieces have chipped or lifted. It’s not advisable to leave it indefinitely, since a compromised protector offers less protection against your next drop.

    Will removing a screen protector damage my phone’s actual screen? Not if it’s done carefully. Going slowly, working from a lifted corner at a low angle rather than pulling straight up, and using a plastic card rather than anything metal, keeps the risk to the actual screen very low.

    How can I tell if my phone recently got wet and should keep the cracked protector on for now? If your phone has been exposed to water recently, it’s generally better to leave even a cracked protector in place temporarily, since removing it could allow moisture to reach areas it hasn’t gotten to yet. Once you’re confident the phone is fully dry, it’s fine to proceed with removal and inspection.

  • Phone Won’t Charge Unless Cable Is at an Angle

    A phone that only charges when the cable is held at a specific angle almost always comes down to a weak electrical connection inside the charging port, not a dying battery or a broken phone. The two most common causes are debris packed into the port and worn or bent contact points inside it, and one simple test tells you which side of the problem you’re actually dealing with — the cable or the phone itself — before you spend a dime on either one.

    The One Test That Rules Out Your Cable First

    Before touching the phone at all, swap in a cable and wall adapter you know work on another device. Not a spare cable sitting in a drawer that might itself be the problem, but one you’ve watched successfully charge something else recently. Plug that known-good combination into your phone and see if the angle problem disappears entirely.

    If it does, the phone was never the issue — you were dealing with a worn cable, most likely frayed or bent right where the connector meets the cord, which is the single point on any charging cable that takes the most physical stress over time. Replace the cable and you’re done, no repair needed.

    If the same angle-dependent behavior shows up with a cable and adapter you know are good, the problem is inside the phone’s port, and that’s worth confirming with a second pass using yet another cable if you have one, just to rule out an unlucky coincidence of two bad cables in a row.

    If It’s Confirmed to Be the Port: Check for Debris First

    Assuming the port is the culprit, the most common cause by a wide margin is simple buildup — pocket lint, dust, or a bit of fabric fuzz packed into the small opening, which physically prevents the connector pins from making full contact unless you angle the cable just right to compensate. Power the phone off completely, then shine a flashlight directly into the port. You’re looking for a visible fuzzy mass or a shadow where there shouldn’t be one; a clean, empty-looking port rules this out and points toward the next section instead.

    If you do see debris, a wooden toothpick works better than almost anything else for this, since it’s rigid enough to dislodge packed lint but soft enough that it won’t scratch or bend the metal contacts inside if it touches them. Apple’s own guidance on handling charging issues confirms that removing debris from the port is one of the first steps to try before assuming a device needs service, and the same approach applies just as well to USB-C Android phones as it does to Lightning or USB-C iPhones. Work the toothpick gently along the inside walls of the port rather than jabbing straight in, and avoid anything metal like a paperclip or safety pin, since metal tools are far more likely to bend a contact pin than a wooden or plastic one is.

    If the Port Is Clean but the Problem Persists

    A clean port that still only charges at an angle points to physical wear rather than debris — usually the tiny metal contact springs inside the port losing their tension after months or years of cables being plugged and unplugged, or in more severe cases, a pin that’s actually been bent from a cable being forced in at an angle or from a drop. This kind of wear doesn’t reverse itself with cleaning, and it tends to get worse rather than better over the following weeks, since the temporary angle that works today puts uneven pressure on already-weakened contacts.

    If your phone has been dropped recently or been anywhere near water, it’s worth reading through what to do about a water-damaged phone, since moisture corrosion on the contact pins produces this exact angle-dependent symptom and is easy to mistake for simple wear.

    What a Charging Port Repair Actually Costs

    On most phones, the charging port isn’t a large or expensive part on its own, but the labor involved varies a lot by device. On many Android phones the port is a small, separately replaceable module, and repairs tend to run somewhere in the $30 to $70 range. On iPhones and a growing number of Android flagships, the port is often soldered directly to the logic board, which pushes the repair into more specialized microsoldering territory and can run $80 to $150 or more depending on the shop and the model. Given that range, and given that this kind of wear typically shows up on phones that have already seen a few years of daily use, it’s worth taking a moment to think through whether to repair or replace the phone before committing to either option, especially if the device is also starting to show its age in other ways.

    A Quick Software Check Before You Assume It’s Hardware

    It’s a smaller slice of cases, but worth ruling out: if you’re getting a message about an unsupported or uncertified accessory, or the phone seems to charge fine on one outlet but not another, the issue may be a firmware quirk or a genuinely low-quality cable rather than physical damage. A restart clears temporary charging-state glitches on both Android and iOS, and trying a different wall outlet or power bank rules out a weak power source before you go any further with port inspection.

    FAQ

    Q: Why does my phone only charge when the cable is at a certain angle? A: This almost always means the electrical connection between the charging cable and the port isn’t stable, usually because of debris packed inside the port or worn, bent contact pins that need slight pressure from an angled cable to make contact. It’s rarely a sign that the battery itself is failing.

    Q: How do I know if the problem is my cable or my phone’s charging port? A: Test with a cable and wall adapter you know work well on another device. If the angle problem disappears, the original cable was worn and needs replacing. If the same issue happens with a cable you know is good, the charging port itself is the problem.

    Q: How do I clean a phone’s charging port safely? A: Power the phone off completely, shine a flashlight into the port to check for visible lint or debris, and gently work a wooden toothpick along the inside walls to dislodge it. Avoid metal tools like paperclips or pins, since they’re much more likely to bend the delicate contact pins inside.

    Q: Can a worn or damaged charging port be fixed without full replacement? A: If the issue is debris, cleaning fully resolves it with no replacement needed. If the pins themselves are bent or the contact springs have worn out, cleaning won’t help, and the port typically needs to be professionally replaced or, on some devices, repaired via microsoldering.

    Q: How much does it cost to replace a phone’s charging port? A: On phones where the port is a separate replaceable module, typically many Android devices, repair usually costs $30 to $70. On phones where the port is soldered to the logic board, common on iPhones and some flagship Android models, the repair is more specialized and often runs $80 to $150 or more.

  • 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

    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.