-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow usage without being the default SMS/MMS/RCS application. #109
Comments
On Android, only one app can have permission to access SMS at the time. Even if there were any hacks to avoid it, we don't want to do this, to not perform any actions that can be considered malicious, what may lead to get banned on e.g. Google Play. |
I understand. That's reasonable. In which case, @Aga-C, https://issuetracker.google.com/issues/36982356#comment1 may be worth following if you're not already. |
@RokeJulianLockhart the newest comment there is 1,25 year old and second newest comment is 4,25 year old and it has status "Won't fix (Obsolete)" |
@inson1, I'm aware. It's depressing. |
Otherwise known as, trying to break Google's monopolistic behavior. Gotta love when corporations label proconsumer monopoly breaking attempts as malicious behavior. |
Checklist
Feature description
I'd like to be able to use this alongside other SMS/MMS/RCS applications.
Why do you want this feature?
In order to evaluate its abilities and more importantly, use some of its functionality to supplement others' and vice versa.
Additional information
See https://xdaforums.com/t/how-to-write-to-sms-content-provider-in-android-kitkat-without-being-default-sms-app.2551072/post-48032696 per https://stackoverflow.com/a/20434604/9731176.
The text was updated successfully, but these errors were encountered: