Skip to content
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

Closed
6 of 7 tasks
RokeJulianLockhart opened this issue Feb 20, 2024 · 5 comments
Closed
6 of 7 tasks
Labels
wontfix This will not be worked on

Comments

@RokeJulianLockhart
Copy link

RokeJulianLockhart commented Feb 20, 2024

Checklist

  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
  • I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
  • This issue contains only one feature request.
  • I have read and understood the contribution guidelines.
  • I optionally donated to support the Fossify mission.

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.

@RokeJulianLockhart RokeJulianLockhart added feature request Issue is about a new feature in the app needs triage Issue is not yet ready for PR authors to take up labels Feb 20, 2024
@Aga-C
Copy link
Member

Aga-C commented Feb 20, 2024

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.

@Aga-C Aga-C closed this as not planned Won't fix, can't repro, duplicate, stale Feb 20, 2024
@Aga-C Aga-C added wontfix This will not be worked on and removed feature request Issue is about a new feature in the app needs triage Issue is not yet ready for PR authors to take up labels Feb 20, 2024
@RokeJulianLockhart
Copy link
Author

#109 (comment)

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.

@inson1
Copy link

inson1 commented Feb 20, 2024

@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)"

@RokeJulianLockhart
Copy link
Author

RokeJulianLockhart commented Feb 21, 2024

#109 (comment)

@inson1, I'm aware. It's depressing.

@MulverineX
Copy link

MulverineX commented Jun 21, 2024

actions that can be considered malicious

@Aga-C

Otherwise known as, trying to break Google's monopolistic behavior. Gotta love when corporations label proconsumer monopoly breaking attempts as malicious behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

4 participants