Accueil / Tech News / 10 things you should never do on your Android phone

10 things you should never do on your Android phone

Avoid major mistakes that make your Android phone less secure and less convenient to use.

If you've used Android for a while, you probably know some of its most important rules. But even with an OS that's been around for more than 15 years, myths and outdated assumptions still persist. Or you might be new to Android and not totally sure how to best take care of your device.

Either way, Android doesn't come with a complete user manual, so we've compiled some of the mistakes you shouldn't make on an Android phone. They include ignoring security features and trying advanced functions without understanding them. Follow these, and your Android phone should last years in good condition.

Why it's bad: Software updates fix known vulnerabilities. Patches in a software update are often responsive, meaning they protect against attacks that are happening, not just theoretical threats. Also, if you use high-security apps like banking and wallet tools, those services won't work if your phone gets too behind on security updates.

Who says so: Security vulnerabilities in Android are reported to Google, and Google shares this information confidentially with Android device makers. You can read about what threats Google considers critical on its Android Security page.

Google doesn't share this information publicly for 90 days, giving vendors time to create proper patches and preventing would-be attackers from taking advantage of the details before people have a chance to install patches. There are a lot of players here: Google is responsible for Android software, then every phone maker adds software to Android devices that needs to be patched. Chip makers like MediaTek and Qualcomm also need to patch the drivers that allow those chips to function properly.

What's the best practice: Install every security update as soon as it appears. Also, open the Google Play Store and make sure to update apps regularly — automatic updates are best.

Why it's bad: When your phone is running too many processes at once, it slows down. That seems obvious, but what's actually happening is your phone is shuttling apps between three internal components: storage, RAM and a special partition of RAM called ZRAM made to quickly store and recall active processes.

When your RAM fills up, it starts compressing processes so it can cram them into the ZRAM partition. When there's no more room in ZRAM for compressed data, your phone enters a state called memory thrashing, where it repeatedly loads data from the ZRAM and then compresses it back in an ongoing cycle. This causes your phone to slow down and heat up as the CPU drains power.

Who says so: The Android Open Source Project offers technical details on the so-called "low memory killer daemon" (the software process that stuffs data into ZRAM), and the problems caused when you let that memory fill up with extraneous data pages.

What's the best practice: Restart your phone regularly to clear the RAM and ZRAM. When you're done with a heavy app like a game, swipe to close it from the app switcher menu (though you don't need to do this constantly for all apps). Finally, uninstall apps that you no longer use to make sure they aren't running processes you don't need. On Android, even if you don't open an app, it may still run and use your RAM in the background.

As another part of core maintenance, make sure to keep enough space free on your Android phone. Running it with maxed-out storage means it has no room for temporary caches and other "helper" data.

Why it's bad: There is no easier way for bad actors to take advantage of security flaws than from apps that come from outside Google's Play Store garden. One common practice is for bad apps to take advantage of your phone's Accessibility controls, which grant privileges for copying your phone's screen and running apps in the background. Google is cautious about approving accessibility access on the Play Store, which is why bad apps are often found on third-party sites.

Who says so: According to Google's security blog, Google Play Protect identified more than 13 million malicious apps from outside the Play Store in 2024 — and those are just the ones the service was able to detect. The standards for Android app security are set by the App Defense Alliance, part of Linux, which forms the foundation of Android's code.

What's the best practice: If you must install apps from outside Google Play, make sure you 100 percent trust the source. A first-party developer you trust, or a security-conscious third-party app market like F-Droid, is better than a random forum or Reddit page. Always use caution outside the Google Play Store.

Why it's bad: If you're asked to disable Google Play Protect for any reason, that's a major red flag. Usually, a scammer will try to convince you to download a phony app by pretending to be your bank or another trusted source. When you try to install the new app, you get a warning from Play Protect, which the scammer tells you to disregard. Never ignore this warning.

Who says so: Play Protect has been a part of Android for almost 10 years, and it gets constant updates that make it more stringent. It's the primary line of defense against dangerous apps you try to install.

What's the best practice: Never disable Google Play Protect, but don't trust it blindly either. Researchers like Bitdefender claim to have found apps that made it to the Play Store and still pose a risk, so you still need to be careful about what you install.

Why it's bad: In the early days of Android, there were good reasons to obtain root access to your phone. You could enable features that were inexplicably turned off, like network tethering on Verizon's early Android devices. It allows you to remove bloatware installed by your mobile carrier, or even load an OS like CyanogenMod that was better than what Samsung or Google provided. Those days are over.

Rooting a phone triggers failures in Google's Play Integrity API, and that's a break that can't heal. You won't be able to use banking or financial apps or any apps that rely on your phone's Strong integrity, a tag that disappears when you obtain root access to your system. Having root access means mistakes or malicious apps can cause much more damage.

Who says so: Even the US government says this is a bad idea. The National Institute of Standards and Technology (NIST) warns against rooting your mobile device, listing rooting and jailbreaking a phone as a threat in its Mobile Threat Catalogue.

What's the best practice: There is not enough reason to root your primary Android phone today if you aren't a software developer. Phone features are no longer restricted based on which carrier sold you the phone. And phone makers let you remove (or at least hide) the bloat — you can even remove Google apps that used to be permanently stuck in your app drawer.

If you have an old device that no longer gets updates, rooting and installing a custom ROM can bring new life to it, but the trade-offs aren't worth it on an in-support daily phone.

Why it's bad: Say your new Android phone came with a bunch of apps you don't want. The Settings menu lets you disable them so they disappear, but they're still taking up space and you can't let it go.

So, you found a YouTube video that shows you how to turn on USB Debugging, which lets you manage your phone's files from your PC. You figure this isn't a problem, since you aren't installing anything from a third party or handing your phone to a stranger.

Except those instructions often skip an important final step: remember to turn USB Debugging off. Otherwise, your phone is more vulnerable to attacks using a computer. While Android requires you to authorize the connection when you connect to any PC for the first time, you might not realize what you're doing, or someone could trick you into handing over access. That's why it's important to watch the prompts when connecting to an unknown USB port (more on this below).

There are lots of features on Android that can give you advanced access to your system without being dangerous, as long as you're careful to turn them off when you're done.

Who says so: Google is enthusiastic about Android users trying Developer Mode, but admits "it's essential to understand the implications of each setting." That's a massive understatement, since these options can cause problems if you don't know what they do.

Origine de l’article : lire l’article original

Traduction