Posts tagged Blackbook

Shady SMS – Mblware Cease and Desist – Open Source Declaration of Various Code Elements

At the request of Mblware I have changed the name of Android Blackbook to Shady SMS. To completely and unilaterally comply with the cease and desist request the name was immediately changed as to not further infringe on the copyright of Mblware.

I have also adjusted the description of the application, and various instructions as to not use the same semantic terminology as Mblware. This is also to the effect of not infringing on potentially additional copyrights of Mblware.

As a sign of good faith I will be publicly disclosing various code elements to the general public.

To process outgoing calls on the Android operating system several elements are required in the manifest file:

<uses-permission android:name=”android.permission.PROCESS_OUTGOING_CALLS” />

Particularly in the application section, of the manifest, you create a filter associating a particular class with a particular broadcast:

<receiver android:name=”.OutgoingCallReceiver”>
<intent-filter android:priority=”0″>
<action android:name=”android.intent.action.NEW_OUTGOING_CALL”></action>
</intent-filter>
</receiver>

Then in the class you extend BroadcastReceiver and override the onReceive method:

@Override
public void onReceive(final Context context, final Intent intent)

You can then process the outgoing call a variety of ways. I know several of my associates are aborting the outgoing call to change the telephone number to something more economical. You can also abort the outgoing call, for instance, if the screen is off; this can be part of an application to enhance “butt dialing” prevention.

To abort an outgoing call you can use:

setResultData(null);

After the call is aborted you can dial another number using:

Intent intent = new Intent(Intent.ACTION_CALL, Uri.parse(“tel: xxxxxxxx”));
context.startActivity(intent);

The previous code is an intent, which can also be used to launch an application activity as follows:

Intent intent = new Intent(context, newActivity.class);
context.startActivity(intent);

All of the above code is part of the Android SDK a publication of predominantly open source code. It is freely searchable, viewable, and downloadable directly from the internet.

All code in Shady SMS is completely unique and derived of novel copyright. The sole reference used to generate the code was and is:

http://developer.android.com/guide/index.html

and:

http://developer.android.com/reference/packages.html

While the vast majority of code in Shady SMS is not open source I have no problem sharing most elements. Any requests for example algorithms can be sent directly to me via the contact tab at the top of this website. Email or call anytime, I’m always around :)

Android BlackBook – MMS Support Coming Real Soon

A sorely lacked feature has been MMS photo support. I am happy to report it is relatively close to being released. After this feature is stable, and released, its on to T-Mobile support. Then 2.2 support; I may need to wait for 2.2 on the Incredible, or actually purchase  the Nexus 1 with a prepaid T-Mobile sim.

T-Mobile has proven tricky. The incoming telephone number has a 1 in it. I have compensated for this manually, but I want the process to be automatic. As of now BlackBook works with T-Mobile when the T-Mobile option in the main settings is checked. The option allows for a 1 to be stored in the contacts telephone number. For some reason even with the 1 in the contacts telephone number SMS filtering is not working.

SMS delivers a bundle. In the bundle is the message and the senders address(telephone). I have a feeling the senders telephone number does not have a 1 for SMS messages. This means T-Mobile is all over the place. There is definitely a 1 in the incoming telephone number, but most likley not a 1 in the incoming SMS message? Strange, where is the consistency?

If I cannot make T-Mobile detect automated I am going to make the T-Mobile option more obvious. I will also make it so when the option is disable and enabled the telephone numbers of all the contacts are re-adjusted automatically.

Android Blackbook Pro – Full Support & New Features

Blackbook now supports two themes in the SMS client (Bubbles and Stock). You can toggle the them via the menu option (nice and easy). I fixed a couple of bugs last night, and completely removed the kill pill that is in the BETA version. The pro version will receive all updates from now on. There are many things on my list of todos. Two are from a recent comment on a previous blog post.

1) Photo support

2) Group sms sending

3) SMS auto responder

4) Message linkify (ex. hyperlinks)

5) I want to try send to voicemail using a clever hack to work around lack of such a feature in the sdk (this may prove to be a waste of time)

6) MMS support, which is not high priority because although it is an important feature it is used substantially less than SMS. Also it is remarkably more difficult.

And as always more code cleanup for efficiency.

Please comment if there are features you want me to add to the list of todos.

Android Blackbook – Motorola Droid Milestone

Blackbook now is confirmed to work on the Motorola Droid Milestone. This is of great importance because it extends its reach tremendously.

There is still a lot of work to be done with the application. I will be completely revamping the entire user interface. The main page will predominantly remain the same, for now, as it is based on some coding from my previous app that I think looks appealing. The contact settings menu will take on a more traditional look, along with the main settings menu. As of now sms filtering works basically flawlessly, call filtering works fine with the most frustrating drawback being the missed call notification that is programatically unavoidable. Silence mode works as expected, and notification vibrations have been added with some more options added to the main settings menu. MMS support still needs to be implemented.

Blackbook will remain in Beta for some time. At least until the 15th of July. There is a kill pill in the code and as of right now the app will no longer function after the 1st of July. I will modify this code to allow it to function till the 15th, but please note this requires you to upgrade your software from the marketplace. I most likely will keep Blackbook in Beta until I get MMS working, which I will start working on after I revamp the UI.

Android Blackbook – Fully Functional on Droid Incredible

I have made a comprehensive Blackbook application for the Droid Incredible. It will be available soon, and I may publish it on the Market in a beta version with date expiration; to get some feedback. It was built and tested on the Incredible, and should work on all other devices with 2.1. I want to publish to beta to see what other devices it works on.

It is comprehensive. It filters incoming and outgoing text messages. When a contact is in the blackbook receives an incoming messages it is not shown in the regular message inbox. It can only be viewed in the blackbook application. There are two options associated with text messages; notifications and dummy text messages. Dummy messages will replace the deleted message with a message saying Spam Filter has removed unwanted content. The notification  also has similar content. These features can be disabled.

Notifications will replace the default notification for your text message app. Notifications are handled for regular text messages as well as blacklisted contacts. Notifications for regular text messages are similar to the notifications produced by your default text message application. They will include the contact, and the message and link to the messaging application. Notifications for blacklisted contacts will say Spam has been detected and removed successfully. When you get a notification like this it should signify that you have a new discrete text message that can be viewed in the Android Blackbook.

Android Blackbook has no icon. It does not show in the recent applications quick launch dialog that shows when you hold the home button. It is completely hidden and can only be accessed by entering your secret code into the dialer, and pressing call. The default secret code is 123 and can be configured in the application. The only way to see that the app is installed in the applications menu in settings. In their The icon is a warning sign and the title of the app is  System Error. It is for all practical purposes discrete!!!

I will continue to work on this app aggressively. I will post again as I get more done.