Hidden carrier features on Android are the privacy tool I never thought to audit

Published Nov 10, 2026, 6:30 AM EST Aggy is a veteran writer and editor in the technology and gaming space. Having served as a Managing Editor for high-traffic digital publications, alongside being an editor and consultant for over a dozen sites. Aggy's published work spans a wide and respected array of tech and gaming outlets, including WePC, Screen Rant, How-To Geek, Android Police, PC Invasion, and Try Hard Guides. Beyond editorial work, Aggy's direct experience in the tech sphere extends to app development. Aggy has published two games under Tales and is always eager to learn and do more. He also likes working on computers and researching in his spare time. He knows about Windows, Linux, Audio, Video, and much more. I never thought about auditing my carrier's software because I never knew how easy it was. I'd checked app permissions, turned off ad tracking, and cleaned out old apps, but the preloaded packages that came with my Galaxy stayed untouched because I assumed they were just part of the phone. I spent an afternoon looking into what T-Mobile and Samsung put on my device, what it can actually do, and what happens when you turn it off. It's easy enough to try yourself. Carrier software doesn't follow normal app rules Four packages show how much access it has Your carrier's software doesn't get installed onto your phone the way a regular app does. It's built right into the phone's read-only system storage. That comes from how Google, Samsung, and carriers like T-Mobile split up the work, since it's easier than building separate software for every carrier. Android divides things into partitions. It has a partition for the core OS, one for device-specific stuff, and one for hardware drivers. Carrier apps land in protected folders inside those partitions, and that hands them privileges normal apps don't get unless you go out of your way to grant them. If you're on T-Mobile like me, these four packages show how far this preloaded software can reach. The first, com.tmobile.pr.adapt, is a background diagnostic tool that's been around for a while. It's allowed to read Android's system log buffers, so it can pull in debug messages, connection events, and crash data, then bundle all that up and ship it to T-Mobile's servers. The package working alongside it is com.tmobile.pr.mytmodules. This one acts like a background job runner. T-Mobile can send it remote instructions to run network tests and check your connection speed, and none of that needs a system update. The third package, com.tmobile.services, handles carrier security features like T-Mobile Scam Shield and NameID. It watches incoming calls in real time and scores how likely they are to be spam. It also manages stuff like visual voicemail and carrier network policies. Then there's Samsung's own com.sec.android.app.omcagent, the Open Market Customization Agent. When you drop in a SIM card, this app reads the card's carrier info and loads the matching settings profile for that network, including APN configurations, network preferences, and any carrier apps that need to be installed automatically. This all sounds shady, but a system app being on your phone doesn't mean it's snooping on you. These apps live on read-only partitions, so their files are always there no matter what, and each one is built for a specific job. Whether they're actually collecting and sending data depends on what services are running, what triggers them, and whether the phone is connected to a network. Just because com.tmobile.pr.adapt can read system logs doesn't automatically mean it's logging everything all the time. You'd need to verify that through official documentation or by actually capturing your network traffic. You can audit and disable these packages yourself Here's how to do it on your phone This is a little more complicated than a menu option, but I was able to check it out on my own T-Mobile phone pretty easily. I get nervous trying new things and like to do a lot of research first, but it's not as bad as it sounds. I got it done in a few minutes. On One UI, go to Settings, open Apps, tap the menu icon in the corner, and select Show system apps. That shows you all the preloaded system components that are normally hidden. There's no Uninstall button for these, so you need the Android Debug Bridge (ADB) on a computer. To get ADB working, you need to enable Developer Options on the phone. Go to Settings, tap About Phone, go to Software Information, then tap Build Number seven times until you see a confirmation message. Then go back to the main Settings screen, open Developer Options, and turn on USB Debugging. When you connect the phone to your computer with a USB cable, the phone shows a prompt asking you to authorize the connection. Approve it, then open a terminal on your computer and run adb devices to confirm everything is hooked up properly. Once you're connected, you can uninstall each of the four packages for your user profile with these commands: adb shell pm uninstall -k --user 0 com.tmobile.pr.adapt adb shell pm uninstall -k --user 0 com.tmobile.pr.mytmodules adb shell pm uninstall -k --user 0 com.tmobile.services adb shell pm uninstall -k --user 0 com.sec.android.app.omcagent If you break this down, the --user 0 part means these changes only apply to the main user account on the phone. The -k flag tells Android to keep the app's saved data instead of wiping it. Android just marks these packages as uninstalled for user 0, so they can't run in the background, receive broadcasts, or show up in the launcher. The files will still sit in the read-only partition. They just can't do anything. To confirm it worked, you can run adb shell pm list packages -f | grep -E "tmobile|omcagent" or check a specific package with adb shell dumpsys package followed by the package name. For other carriers, the process is the same on any Android device. The only thing that changes is the package name at the end of the command. Verizon bloatware packages usually start with com.vzw, AT&T apps tend to use com.att, and older Sprint packages use com.sprint. Since carriers rename these apps pretty often, the easiest way to find your carrier's packages is to connect your phone to your computer and run adb shell pm list packages | grep "carriername" in the terminal, swapping in your carrier's prefix, like vzw or att. From there, just grab the exact package names from the list and remove them using the same ADB uninstall command. Disabling these packages has limits Removing them can break things Disabling these packages through ADB can be risky. Turning off com.tmobile.services can break Wi-Fi Calling since that feature depends on background authentication tied to your emergency address registration. It'll also stop visual voicemail notifications and Scam Shield call scoring. Disabling Samsung's omcagent means your phone won't automatically reconfigure itself when you swap SIM cards, so APN settings, VoLTE profiles, and regional network configurations may stop working correctly. If you do a factory reset or install a major OS update, they'll come back because the packages are still on the system partition, so this isn't permanent. You can also re-enable any of them by running adb shell cmd package install-existing followed by the package name, without wiping or reflashing anything. There's also a bigger issue to keep in mind if you care about privacy. Even if you remove every carrier app from your phone, T-Mobile still logs everything at the network level. That's how cellular networks work. Carriers record which towers your phone connects to, your general location, call records, SMS metadata, data usage, and billing activity. All of that gets captured on the carrier's side, not on your phone. No app removal changes that. And some of these packages aren't tracking tools at all. They handle things like APN configuration and IMS encryption tunnels that your phone needs to work. There's a good reason to audit and remove what you can Even if the carrier sees everything at the network level, disabling something like com.tmobile.pr.adapt stops it from reading your system logs on the device, scraping app crash reports, sending periodic data uploads, or waking up your processor and modem. It won't make you invisible to your carrier, but at least it will reduce what's happening locally on your device. Keep in mind this isn't a full fix, and if you want to know exactly what a package is collecting, check the carrier's official privacy documentation or run your own packet analysis instead of taking anyone's word for it.