messaging

Is there a free API or some other way to determine what carrier a cell phone number is registered with? I'd like my application to broadcast text messages without them picking their carrier from a list. UPDATE: Interestingly, a coworker found the answer: http://developer.whitepages.com/ UPDATE2: Well the whitepages license agreement is so restrictive that you can't build an app for it. Any other ideas? UPDATE3: At some point, someone removed my Update 2. This puts it back. More importantly as of 10/19/2015 the Terms of Service is still in a state that it should be impossible to legally utilize

I need 2 variables from an incoming text message, the sender and the message body. How do I access them? Here is step by step description for how to read incoming sms in android You need to use broadcast receiver for that Declare receiver in AndroidManifest <receiver android:name=".IncomingSms"> <intent-filter> <action android:name="android.provider.Telephony.SMS_RECEIVED" /> </intent-filter> Give read SMS permission in AndroidManifest <uses-permission android:name="android.permission.RECEIVE_SMS"></uses-permission> <uses-permission android:name="android.permission.READ_SMS" /> <uses

(or set multiple objects with one value) Is there a way to send multiple objects one message in one line. So like [someObject, otherObject reset]; like in LUA scripts (which I believe is C?) you can set mutliple objects: someThing, otherThing = 1 , 0 In short, no, neither Objective-C nor C support this feature. As an extreme measure, you can use -[NSArray makeObjectsPerformSelector:] and -[NSArray makeObjectsPerformSelector:withObject:] , such as [[NSArray arrayWithObjects:someObject, otherObject, nil] makeObjectsPerformSelector:@selector(reset)]; I would probably use an NSNotification. You

I would like to pass a string to an Activity easily. Something like callback would be needed because when the string has to be passed then the Activity has to do something. public class MyHostApduService extends HostApduService { @Override public byte[] processCommandApdu(byte[] apdu, Bundle extras) { if (selectAidApdu(apdu)) { Log.i("HCEDEMO", "Application selected"); return getWelcomeMessage(); } else { if (exchangeDataApdu(apdu)) { Log.i("HCEDEMO", "Data exchanged"); // int _len_ = apdu[4]; String _data_ = new String(apdu).substring(5, apdu.length - 1); // TODO: Send _data_ to an activity..

I'm using a Messenger class in order to send data between view models. There is an AppView that hosts two main views in a content control, and up until now have had no issue with sending/receiving data this way. Issue: Now I added a ProductView that shows a separate dialog to the AppView. But when I call Messenger.Default.Send<ProductModel>(SelectedProduct); after calling .ShowDetailDialog() this blocks the Send code call, until the dialog is closed. I tried the other way around, calling the Send code first, then opening the dialog. But this means that the message handler in the receiving VM

ActiveMQ / JMS has a built in-mechanism for ensuring that messages that share a common header (namely, the JMSXGroupID header) are always consumed by the same consumer of a queue when using a competing consumers pattern. The consumers of a queue are completely agnostic of the actual header values, as the guarantee of messages with a common header is performed server-side and not consumer-side. For more details on how this works, see http://activemq.apache.org/message-groups.html . Is doing such a thing possible with AMQP or with something RabbitMQ specific? As of the time this answer is

I need to send MMS. Into my hero this code looks ugly but works: Intent sendIntent = new Intent("android.intent.action.SEND_MSG"); sendIntent.putExtra("address", toText); sendIntent.putExtra(Intent.EXTRA_SUBJECT, "subject"); sendIntent.putExtra("sms_body", textMessage); sendIntent.putExtra(Intent.EXTRA_STREAM, Uri.parse(url)); sendIntent.setType("image/jpeg"); startActivity(sendIntent); But it seems to me that on the other devices it doesn't work at all. I want to send directly to main messaging app without any choices(the better solution of course - direct from my app). Because not sure that