README.md

Advanced Sms Manager

AdvancedSmsManager is library for sending sms for single and two sim-card phones. it is very handy and usefull. It's two-sim mode works on Android.SDK > 21. For lower SDKs it send sms from default sim. For using in android studio add this to your dependency:

gradle

compile 'ir.mtajik.android:advancedsmsmanager:1.1.0'                    

Permissions

Before using SmsHandler you had to permit user with Manifest.permission.SEND_SMS and Manifest.permission.READ_PHONE_STATE .

Usage

After that simply call sendSms that have a Interface for all callbacks. smsId is a random unique auto generated Id that generated for every single sms that created by your app. In version 1.0.5 , i implement Builder design pattern. All the with parameters are optional.

SmsHandler.builder(context, "+989120000000")
                .withCarrierNameFilter("MCI")
                .withCustomDialogForSendSms(R.layout.my_sms_dialog)
                .withCustomDialogForChoseSim(R.layout.simcard_choosing_dialog)
                .needToShowSendSmsDialog(false)
                .build().sendSms(DIALOG_MESSAGE, SMS_BODY, new MySmsManager.SMSManagerCallBack() {
            @Override
            public void afterSuccessfulSMS(int smsId) {

            }

            @Override
            public void afterDelivered(int smsId) {

            }

            @Override
            public void afterUnSuccessfulSMS(int smsId, String message) {

            }

            @Override
            public void onCarrierNameNotMatch(int smsId, String message) {

            }
        });

If you do not want to ask user for send sms after premitted, put .needToShowSendSmsDialog(false) or else leave it and sms confirem dialog will be displayed.

Sim-card carrier name filter

You can set carrier name filter that works for SDK>22 with .withCarrierNameFilter("MCI") If user going to send sms from carrier that not match your filter ( in one or two sim card phones), the call-back :onCarrierNameNotMatch() will be call.

In new version there is a new feature that you can send Sms from specific carrier and do not show sim-card chosing dialog to user. Mention that sim chose dialog on two sim phones will always diplayed in pre 1.1.0 versions.

.needSendSmsFromSpecificCarrierWithOutAskingUser("MTN")

This will be check phone sim-cards carrier names in lower-case that contains "mtn". If one exists then sms will send from that carrier without asking from user. If there is no carrier name that matches this filter onCarrierNameNotMatch() will be call. When you use this option no need for using .withCarrierNameFilter() option. But if you use both of them the last used properties will override carrierNameFilter.

Custom Parameters

You can pass custom Layoutparameters for sendSmsDialog

WindowManager.LayoutParams layoutParams = new WindowManager.LayoutParams();
layoutParams.width = WindowManager.LayoutParams.MATCH_PARENT;
layoutParams.height = WindowManager.LayoutParams.WRAP_CONTENT;
layoutParams.flags = WindowManager.LayoutParams.FLAG_DIM_BEHIND;
layoutParams.dimAmount = 0.6f;

And add with .withLayoutParams(layoutParams)

You can also pass widht or height in dp for sendSmsDialog and they will ovveride LayoutParams.

.withHeight(200) // 200dp
.withHeight(800) // 800dp

Custom Layouts

You can inflate you custom view for both sendSmsDialog and simChoseDialog if they are going to shown. Mention that they must have these component and ids. ( Extended components from these components are acceptable)

for sendSmsDialog:

<Button
	android:id="@+id/send_button"
	...
           />
            
<Button
	android:id="@+id/cancel_button"
	...
           />

<TextView
        android:id="@+id/dialog_title"
        ...
          />

<ProgressBar
        android:id="@+id/progressBar_total"
	...
	   />

and for simChoseDialog :

<Button
	android:id="@+id/sim1_button"
	...
           />
            
<Button
	android:id="@+id/sim2_button"
	...
           />

<TextView
        android:id="@+id/dialog_title"
        ...
          />

Dependencies

This library created with MVP architecture and Uses Dagger2 as DI container with these dependencies:

compile 'com.google.dagger:dagger:2.7'
annotationProcessor 'com.google.dagger:dagger-compiler:2.7'

So if you use dagger2 make sure that use compatible dependencies. I hope this library would be useful and wait for your comments.

This is my weblog: http://www.mahditajik.ir