fireguy_6364 wrote:
magenta6440033 wrote:
fireguy_6364 wrote:
https://rcs.developer.samsung.com/develop/Introduction/overview.html
a grab from the link above
hatbots are the central component of Samsung RCS MaaP. They enable user functionality through conversational interfaces that simulate human conversation and allow brands to interact with their customers in new ways. For example, a travel company can provide its customers with a chatbot that lets their customers easily book an airline flight using conversational language
TMO however did need to agree with this however (as did OP wanting to get on the bandwagon with Sammy)
lots of info there to go through
it is/was supposed t be able to be turned off...not deleted..if you are unable to turn it off say so and i can try and see whats up with that.
Can you provide instructions on how to disable this on a OnePlus 8T? It just appeared on my OnePlus 8T and my search for how to remove it brought me to this thread. I do not see a way to disable in the stock messenger app
I am using a T Mobile OnePlus 8T
Stock Messenger app version 6.0.0.4.210225164113.91f57a8
Android 11 10/1/2021 security update
Build number 11.0.13.15.KB09CB
the option SHOULD be under the texts settings..then again the instructions on how to remove it are also in the link i provided above..since its a Samsung link but OP is also doing it im not sure if the same instructions will work on a OP as it is supposed to work on the Samsung side.
Maybe I misunderstood something but I am not sure how the fact that there SHOULD be some way to disable it helps if there is no way to ACTUALLY disable it. If there ACTUALLY is a way to disable it, would appreciate any help you can provide for the more technically challenged people like me. If you do not know, that is fine too but would rather you have just said that. I do not see any way to disable it on the phone.
This seems like an issue with T Mobile branded phones. This may be one more reason for me to stat buying unlocked (did just that with the Z Flip3).
As the other poster said, this issue definitely still exists, is NOT resolved, and just started happening again recently.