-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
Add a "VoIP.ms SMS" connection to Android contacts #110
Comments
Unfortunately VoIP.ms SMS isn't an SMS app from the OS's point of view, so that's not possible. See issue #49 for details. |
Pretty sure any app can add a contact option to a contact. Doesn't have anything to do with SMS...? |
To clarify, you're asking for the ability to click a button in your contact list that opens the conversation window for that contact in VoIP.ms SMS? |
yes |
Yes, that requires that VoIP.ms SMS advertise the SEND_TO intent, which isn't possible for SMS apps unless they're the default. |
but why do you need to say you're an sms app? why not just be the same as any other messaging app that doesn't do sms? |
What other messaging apps let you launch them from your contacts? |
See for example http://stackoverflow.com/questions/28583233/special-case-when-adding-a-custom-connection-action-to-contacts-in-android-kitka and option in screnshot to skype with a username (not phone number) |
Fair enough. This is something different then what I thought you were talking about, and worth investigating. |
Additional related link: https://stackoverflow.com/questions/29846912/adding-new-connection-to-existing-android-contact |
Any further thoughts on this? It is a very minor irritation, as VoIP.ms is my main number. I'm not an android programmer, but if I can contribute in any other way, please let me know. Tarek : ) |
Unfortunately, it looks like a lot of work, so at the moment it's pretty low on my to-do list. |
Similar to "call via whatsapp" buttons and similar. So a new sms conversation can be started in this app via the normal contacts.
The text was updated successfully, but these errors were encountered: