These are the APIs that Google has so far left out of the Android echosystem for easily sending any type of message without digging through source code and what not.
[...]
I feel like this should be an important part of the Android APIs, yet it is all missing so this is my go at it!
No, this is something different from the purpose of the library. It will make the message database more consistently available across devices, but really makes no difference for anything this library does as far as I can tell for sending messages.Here you go: http://android-developers.blogspot.de/2013/10/getting-your-sms-apps-ready-for-kitkat.html
It will be included in Android 4.4 Kitkat.
Settings sendSettings = new Settings();
sendSettings.setMmsc("http://mmsc.cingular.com");
sendSettings.setProxy("66.209.11.33");
sendSettings.setPort("80");
sendSettings.setGroup(true);
sendSettings.setWifiMmsFix(true);
sendSettings.setPreferVoice(false);
sendSettings.setDeliveryReports(false);
sendSettings.setSplit(false);
sendSettings.setSplitCounter(false);
sendSettings.setStripUnicode(false);
sendSettings.setSignature("");
sendSettings.setSendLongAsMms(true);
sendSettings.setSendLongAsMmsAfter(3);
sendSettings.setAccount("jklinker1@gmail.com");
sendSettings.setRnrSe(null);Transaction sendTransaction = new Transaction(mContext, sendSettings);Message mMessage = new Message(textToSend, addressToSendTo);
mMessage.setImage(mBitmap);sendTransaction.sendNewMessage(message, threadId)<receiver android:name="com.klinker.android.send_message.SentReceiver" >
<intent-filter>
<action android:name="com.klinker.android.send_message.SMS_SENT" />
</intent-filter>
</receiver>
<receiver android:name="com.klinker.android.send_message.DeliveredReceiver" >
<intent-filter>
<action android:name="com.klinker.android.send_message.SMS_DELIVERED" />
</intent-filter>
</receiver><uses-permission android:name="android.permission.SEND_SMS"/>
<uses-permission android:name="android.permission.READ_SMS" />
<uses-permission android:name="android.permission.WRITE_SMS"/>
<uses-permission android:name="android.permission.RECEIVE_SMS"/>
<uses-permission android:name="android.permission.RECEIVE_MMS"/>
<uses-permission android:name="android.permission.VIBRATE"/>
<uses-permission android:name="android.provider.Telephony.SMS_RECEIVED" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.CHANGE_WIFI_STATE" />
<uses-permission android:name="android.permission.CHANGE_NETWORK_STATE" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.MANAGE_ACCOUNTS" />
<uses-permission android:name="android.permission.USE_CREDENTIALS" />
<uses-permission android:name="android.permission.GET_ACCOUNTS" />ArrayList<Account> accounts = new ArrayList<Account>();
for (Account account : AccountManager.get(context).getAccountsByType("com.google")) {
accounts.add(account);
}if (sendSettings.getAccount() != null && sendSettings.getRnrSe() == null) {
BroadcastReceiver receiver = new BroadcastReceiver() {
[user=439709]@override[/user]
public void onReceive(Context context, Intent intent) {
sharedPrefs.edit().putString("voice_rnrse", intent.getStringExtra("_rnr_se")).commit();
}
};
context.registerReceiver(receiver, new IntentFilter("com.klinker.android.send_message.RNRSE"));
}Haha no, I built sliding from the ground up off of nothing, just referenced stock source when I needed to. Before I made this library, you had to download and import all kinds of internal classes not in the APIs, both from the stock app and just android source in general. This library brings all of those together so that you don't have to download hundreds of files to get the imports all sorted out (that took me days itself to do) and then it just allows you to use all those classes in a much easier way, really by only creating a message object and sending it through the transaction class.
Basically, it does everything exactly the same as what you will see from the stock source, but it encapsulates all that so third party developers have much easier access to it and can worry about more important things in their app then sifting through source code to find out how to send a stupid MMS message ha. All of the MMS source can be sooooo confusing, especially if you're just starting out like I was.
We in the UK don't use MMS at all hardy, costs too much 
<receiver android:name="com.klinker.android.send_message.SentReceiver" >
<intent-filter>
<action android:name="com.klinker.android.send_message.SMS_SENT" />
</intent-filter>
</receiver>
