universal-android-debloater
universal-android-debloater copied to clipboard
0x192
Update uad_lists.json
Your phone: Xiaomi 11T
Packages documentation to update:
com.google.android.apps.messaging
Documentation chage
Current description
Google Messages (SMS+RCS) https://play.google.com/store/apps/details?id=com.google.android.appls.messaging)
Runs in the background.
QKSMS is a good FOSS replacement.
Proposed description
Google Messages (SMS+RCS) https://play.google.com/store/apps/details?id=com.google.android.appls.messaging)
Runs in the background.
QKSMS is a good FOSS replacement.
Removing this may cause issues with receiving verification text messages and calls.
Notes
Further investigation is probably needed, but until I have reenabled this, I was unable to get any calls or texts from Google verification (2FA). Just having this reenabled (while using my FOSS texting app) instantly fixed this issue.
Thank you for your report. Sorry for the late reply.
That so weird. How could Google know that you have this application on your phone? When you say calls or text from Google is it for 2FA? Where you on a computer or on your phone when you "activated" the sending of the message/call?
Yes, I should have been more clear, it is for 2FA, and it was requested from a desktop computer. I never accessed anything Google-related from the phone in question, only using it for 2FA in regards to Google services.
This is crazy. I don't understand how it's possible to receive everything but 2FA SMS from Google. It should be all or nothing. Only the default SMS application can receive SMS.
It really smells like a bug. Are 100% sure about this one? You didn't forget to reboot your phone after the debloat? Can you retry just in case? This app is preinstalled on a lot of phones and I've never encountered this issue.
I should also update the description with this: Android's Messages, Dialer apps quietly sent text, call info to Google
Sorry for the late response! Yes I am 100% certain, and have had my phone (and my partner's) like this for weeks, so several reboots happened after the debloat. I was trying to single out which app was causing this problem once I noticed I can receive calls but not texts from Google and this app was very suspicious. I reenabled it and texts worked immediately.
I'm so slow at merging stuff. It's awful! Thanks again for your response!
@TheEmbracedOne
and... good luck with your game! I really hope it will be successful. I love the aesthetic and the atmosphere! :slightly_smiling_face:
Hello. I just recently got s21 ultra (SM-G9980) and i can confirm that once you remove this google messaging app you will have problems in some app that sends device registration.
I was once had SM-G998U (s21 ultra US variant) and i don't have this app.
Android 13 TKQ1.220807.001 MIUI Global 14.0.5.0 (TLCEUXM) Xiaomi 12
Just uninstalled Google Messages yesterday with UAD and found no problems so far. Also tried 2FA with my Google Account and received SMS code on my Facebook Messenger App. Until now, no issues with receiving any type of SMS, malfunction of system or unwanted reboots.
Android 13 TKQ1.220807.001 MIUI Global 14.0.5.0 (TLCEUXM) Xiaomi 12
Just uninstalled Google Messages yesterday with UAD and found no problems so far. Also tried 2FA with my Google Account and received SMS code on my Facebook Messenger App. Until now, no issues with receiving any type of SMS, malfunction of system or unwanted reboots.
The 2fa we are talking about is not just a sms type that will give you a code to be input somewhere.
This is automation of lodging the OTP or the device unique key to be registered into the certain app.
Xiaomi Redmi Note 9S (Miui 14.0.3 stable) When I remove it, I could sent message anymore (even with the QKSMS)
Xiaomi Redmi Note 9S (Miui 14.0.3 stable) When I remove it, I could sent message anymore (even with the QKSMS)
Could or couldn't?
Sorry about my english (I speak portuguese), "couldn't".
If you can't send text messages anymore, it means you should use an alternative SMS application from the Play Store.
@0x192
Phone: Samsung Flip 5 System: Android 14 (One UI 6)
Conflict with app: Garmin Connect
Removal of com.google.android.apps.messaging prevents the app from pairing and synchronizing with Garmin watches. The Connect app logs NullPointerException:
02-24 12:48:28.876 12298 12404 E AbstractFuture: RuntimeException while executing runnable CallbackListener{l71.h$d@bec6aef} with executor MoreExecutors.directExecutor()
02-24 12:48:28.876 12298 12404 E AbstractFuture: java.lang.NullPointerException: Attempt to invoke virtual method 'long android.os.BaseBundle.getLong(java.lang.String, long)' on a null object reference
02-24 12:48:28.876 12298 12404 E AbstractFuture: at l71.h$d.onFailure(SourceFile:36)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at com.google.common.util.concurrent.Futures$CallbackListener.run(SourceFile:38)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at com.google.common.util.concurrent.DirectExecutor.execute(Unknown Source:0)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at com.google.common.util.concurrent.AbstractFuture.executeListener(SourceFile:1)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at com.google.common.util.concurrent.AbstractFuture.complete(SourceFile:57)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at com.google.common.util.concurrent.AbstractFuture.setFuture(SourceFile:29)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at com.google.common.util.concurrent.AbstractTransformFuture.run(SourceFile:34)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at com.google.common.util.concurrent.DirectExecutor.execute(Unknown Source:0)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at com.google.common.util.concurrent.AbstractFuture.executeListener(SourceFile:1)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at com.google.common.util.concurrent.AbstractFuture.complete(SourceFile:57)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at com.google.common.util.concurrent.AbstractFuture.setFuture(SourceFile:29)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at com.google.common.util.concurrent.AbstractTransformFuture.run(SourceFile:34)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at com.google.common.util.concurrent.DirectExecutor.execute(Unknown Source:0)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at com.google.common.util.concurrent.AbstractFuture.executeListener(SourceFile:1)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at com.google.common.util.concurrent.AbstractFuture.complete(SourceFile:57)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at com.google.common.util.concurrent.AbstractFuture.setFuture(SourceFile:29)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at com.google.common.util.concurrent.AbstractTransformFuture.run(SourceFile:34)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at com.google.common.util.concurrent.DirectExecutor.execute(Unknown Source:0)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at com.google.common.util.concurrent.AbstractFuture.executeListener(SourceFile:1)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at com.google.common.util.concurrent.AbstractFuture.complete(SourceFile:57)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at com.google.common.util.concurrent.AbstractFuture.cancel(SourceFile:57)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at com.google.common.util.concurrent.AbstractFuture$TrustedFuture.cancel(Unknown Source:0)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at l71.h.onDeviceDisconnect(SourceFile:4)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at m31.f.onDeviceDisconnect(SourceFile:40)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at mz0.b.onDeviceConnectingFailure(SourceFile:13)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at lz0.e$b.f(SourceFile:50)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at dz0.g.c(SourceFile:30)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at com.garmin.android.gfdi.framework.GfdiServiceSubscriber.startCommunication$suspendImpl(SourceFile:358)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at com.garmin.android.gfdi.framework.GfdiServiceSubscriber$startCommunication$1.invokeSuspend(Unknown Source:12)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at il1.a.resumeWith(SourceFile:9)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at to1.q.z(Unknown Source:6)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at no1.a.resumeWith(SourceFile:23)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at il1.a.resumeWith(SourceFile:32)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at no1.q0.run(SourceFile:112)
02-24 12:48:28.876 12298 12404 E AbstractFuture: at vo1.a$a.run(SourceFile:96)
02-24 12:48:28.885 3804 15052 D BtGatt.GattService: unregisterClient(com.garmin.android.apps.connectmobile) - clientIf=12
02-24 12:48:29.906 3804 3967 I bt : bluetooth_core::gatt::arbiter: processing disconnection on transport TransportIndex(0)
02-24 12:48:29.913 3804 4380 D BtGatt.GattService: onClientConnected() uid_not_found=android.uid.bluetooth
02-24 12:48:29.915 3804 4380 D BtGatt.GattService: onClientConnected() uid_not_found=android.uid.bluetooth
02-24 12:48:29.916 3804 4380 D BtGatt.GattService: onClientConnected() uid_not_found=android.uid.bluetooth
Reinstalling the package fixes the issue.
