I keep running into frustrating smartphone features that feel outdated, unnecessary, or impossible to disable. Which phone feature annoys you the most, and have you found a way to turn it off or replace it?
The hidden cost of “helpful” notification categories is that turning off one type rarely stops the app from finding another way to interrupt you. Shopping and delivery apps are the worst offenders. Disable promotions, and suddenly the same junk arrives as an “account update” or “recommendation.”
I wish phones had a single, permanent “this app may notify me only about things I personally triggered” setting. For now, I disable every notification category except essentials like order status or direct messages. If an app keeps creating new categories after updates, it loses notification access completely. Checking it manually is less annoying than constantly policing it.
Be careful disabling every vibration, because calls and emergency alerts can get caught in the cleanup. My pick is keyboard haptics: that tiny buzz on every tap feels irritating and wastes battery for no real benefit. Turning off “touch feedback” or “keyboard vibration” in sound settings usually gets rid of it without silencing useful notifications.
Keyboard vibration is easy to fix; forced app notifications are the real nuisance. Some apps keep inventing new notification categories after you disable the old ones, so I’d rather phones default to silence until each app earns permission.
Turn off automatic replacement but leave spell-check and the suggestion bar enabled. That middle ground is much better than disabling every keyboard aid or letting the phone rewrite messages after you have already typed the right word.
My pick is aggressive autocorrect. Notifications are louder and more obvious, but at least you can identify which app caused them. Autocorrect creates smaller problems that often go unnoticed until after a message is sent. It is especially bad with names, technical terms, abbreviations, and anyone who switches between languages. The phone acts more confident as its guess gets worse.
I would keep typo highlighting because it waits for you to make the decision. Predictive suggestions are tolerable for the same reason. Automatic replacement crosses the line by changing the text without asking. Most keyboards separate those settings, although the labels vary. Look for options such as auto-correction, auto-replace, predictive text, or text suggestions rather than shutting off the entire keyboard feature set.
Compared with keyboard haptics, this takes a little more trial and error to fix because some apps use their own text fields and saved replacements can still interfere. Checking custom text shortcuts is worth doing too. If the keyboard keeps relearning bad corrections, clearing its learned words is the faster workaround, though that may erase useful vocabulary along with the junk.
Don’t waste time clearing caches or reinstalling apps when they keep opening links in their own cramped little browser. My vote goes to in-app browsers. They hide normal controls, make password managers less reliable, break the back button, and force you to hunt for a menu just to open the page in your actual browser.
Notifications and autocorrect are annoying, but at least phones usually provide settings for them. Link hijacking is worse because every app handles it differently. Some give you an “open externally” option, some bury it, and some pretend their browser is doing you a favor.
On Android, checking the app’s “open by default” or supported-links settings can stop some of this. Clearing its link defaults may help too. On an iPhone, the practical workaround is often using the share menu or choosing “Open in Safari,” assuming the app even offers it. Setting a default browser does not guarantee every app will respect that choice.
There should be a simple system switch: all web links open in my default browser, no exceptions. Apps do not need their own half-functional browser just to keep users trapped inside them for another thirty seconds.
Watch out for turning off adaptive brightness completely, because on some phones that also kills the auto light sensor for other things and you end up manually cranking the slider in every dark room. That said, adaptive brightness is my pick. The screen dimming while I’m reading, then blasting back up when I tilt the phone, drives me up the wall. It second-guesses me constantly and never settles on a level I actually want.
The reason it’s worse than the stuff already mentioned here is that it keeps learning. You set a level, it remembers it for that light condition, then a week later it decides it knows better and drifts again. On most Android phones you can shut it off under Display, and on an iPhone it hides under Accessibility, Display and Text Size, which is a weird place to bury a brightness setting. Even then some models keep a low-level auto-dim tied to heat or battery that you can’t fully touch.
@xdarkstackx nailed the in-app browser thing, and I’d agree that’s the most inconsistent one to fix. But I’ll push back a little on the idea that notifications and autocorrect always give you settings. They give you settings that reset. Every big update I’ve seen tends to re-enable at least one thing you already turned off, and adaptive brightness is a regular offender there too. So half the battle isn’t finding the toggle, it’s noticing when the phone quietly flipped it back.
If you only want to fix one thing today, pick the feature that changes your input or your output, not the one that just annoys you visually. A wrong autocorrect goes out to a real person. A dim screen only bothers you. By that logic @fuzzy_mega_hacker’s autocorrect gripe probably deserves the top spot, even if brightness is the one I personally rage about more.
Don’t start disabling every motion setting when the real culprit is usually just Raise to Wake or Tap to Wake. Automatic screen wake is my pick. A slight movement lights the display, exposes media controls, and makes accidental flashlight or camera presses much more likely.
Search the phone’s settings for “raise,” “lift,” or “tap to wake” and switch those off individually. If the screen still lights up, check whether notifications are allowed to wake the display. Always-on display can be a separate setting too.
I’d leave emergency controls and the normal power-button shortcut alone. The goal is to stop casual movement from waking the screen, not make the phone harder to use when it matters. Compared with @leo82’s adaptive brightness problem, this is less visible but easier to diagnose: if the screen stays dark until you deliberately press a button, you found the right toggle.
Check each paired Bluetooth device for separate “Calls” and “Media audio” switches before deleting the pairing entirely. On phones that expose those controls, disabling the unwanted profile can stop a car stereo from grabbing calls while still letting it play music, or keep a speaker from stealing all phone audio.
My vote is automatic Bluetooth reconnection. The phone remembers a device, detects it nearby, and immediately decides that every sound belongs there. That is especially irritating with shared cars, speakers in another room, and earbuds that are still connected to a second device. Unlike a visible notification, you may not notice the rerouting until a call has already started or a video appears to have no sound.
Android often provides more per-device control, though the exact switches depend on the phone and Bluetooth accessory. iPhones tend to make the choice more blunt: disconnect temporarily, turn Bluetooth off, or forget the device and pair it again later. Some cars and headphones have their own connection-priority settings, so changing the phone alone may not solve it.
I agree with @openloop3531point that unwanted screen waking causes accidental actions, but Bluetooth auto-connect can create a stranger failure because the phone technically works while sending output somewhere unexpected. A system option like “remember this device, but connect only when selected” would fix it without forcing users to repeatedly remove and re-pair hardware.
