"Why do you want to do this?" is a better response than "this is a
totally stupid design and is not possible!" If someone asks about the
use of a certain feature for a use which it's not designed, it usually
is because they are trying to do something that could be accomplished
by another method fo
Glad to have been able to point you in the right direction. If you want to
test between devices and don't happen to have 2 physical devices handy you
can use 2 emulator instances!
On Apr 1, 2015 12:25 PM, "Daniel Chacon" wrote:
> I appreciate the feedback and suggestions, i was able to find some
I appreciate the feedback and suggestions, i was able to find something
that seems to be working.. Since this was not going to be a messaging app,
but an app that had a small messaging feature in it, i was looking for the
easiest way to implement something. After the comments above, i was able to
g
I am fed up with the answers ("why do you want to do this", etc) that one often
gets on a question like this. The simple answer is that this is no longer
possible, from Android version 4.4.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
So with gcm it mentions going thru our servers, so does that mean we
have to host something?
On Mar 31, 2015 9:02 PM, "Kristopher Micinski"
wrote:
> The usual way to do this sort of communication between apps on
> different devices is to use a push notification. An example would be
> Go
So found this example for data sms
http://stackoverflow.com/questions/3757229/how-to-send-and-receive-data-sms-messages
On Mar 31, 2015 8:40 PM, "Steve Gabrilowitz" wrote:
> So basically, you are trying to build a messenger app that uses SMS as a
> transport layer but doesn't affect other SM
The usual way to do this sort of communication between apps on
different devices is to use a push notification. An example would be
Google Cloud Messaging, or Parse.
SMS would be possible, but just seems like a suboptimal solution when
things like GCM were designed to do exactly this: there are a
So basically, you are trying to build a messenger app that uses SMS as a
transport layer but doesn't affect other SMS apps? Try investigating the
use of a data SMS rather than the usual text.
On Mar 31, 2015 5:50 PM, "Dan Cha" wrote:
> So im working or playing around with sending text/sms from w
Well it's company phones with unlimited texting as well as
tablets. How would aidl, content providers or intent work between
them and office's miles apart?
This is a internal office app , if sms is not the way, then we
need a more optimal method.
On Mar 31, 2015 7:01
Using SMS to communicate *between* apps on the phone!?
You should 100% *not* be doing that. It's bad design, and it could
potentially cost your users money (if they pay for their texts).
You can use an intent, content provider, or AIDL, and it will be way
easier and much more obvious how to deal
First it seemed easier to use sms to communicate between the apps. This
will only be used internally, so no public version. If there is another way
to communicate only within the app that will work also, basically don't
need to have the messages in 2 places, right now when I send a message it's
in
What's the motivation for doing this?
It seems kind of counterintuitive that you'd want to do this, because
presumably if the user *does* send a text, they want a record of it.
It's easy to imagine a spam app which sends tons of texts and leaves
no trace of it for the user to see!
But I'm a littl
So im working or playing around with sending text/sms from within our app
as well as receiving replies. We will have the app on both ends(sender and
receiver devices)
But right now just prelim testing the messages are sent but they are
showing up as text within the default text app on the phone.
13 matches
Mail list logo
