Revert "Corrected strings for Flash SMS"

This reverts commit e00aae5117da0c734c76d154e3b240786c4c10f4.
Revert "Corrected Intent for Flash SMS"

This reverts commit c4d2d6752a50c7e9113f477c02fd8aa2e578e281.
Revert "Corrected values for Flash SMS"

This reverts commit 4385c4751e9de5e17e0d46d16ece808ef7b58028.
Revert "Corrected values for Flash SMS"

This reverts commit 58d926017adadfa2a940988afffd64be788f6842.
Revert "Corrected values for Flash SMS"

This reverts commit 6f3a1d74e7c62e8634767fdd6de16a8e5c0b2832.
Revert "Corrected filenames for Flash SMS"

This reverts commit 204ff4b0de3841eb1705a24ce13dca5475f7fec8.
Revert "Corrected values for Flash SMS"

This reverts commit 4dcf5dfd76bf6d02b7b80c9bd2d7815dbdfb88fc.
Revert "Corrected values for Flash SMS"

This reverts commit 472f6a86a3456c24073f9f9b1220fd2dc5315be8.
Silent Sms Update

Sms Broadcast receiver modified to look for true TYPE 0 Stealth Sms messages,
processing is now done within the PDU checking the first byte value of each received
message. If the first byte == 0x40 then as per 3GPP TS 23.040 9.2.3.9 a TYPE 0 message
has just been intercepted.

Unable to test this function as I have no ability to issue a true TYPE 0 Sms but I
believe other contributes are able to test this fully.

Updated the service to disable the notification alert once the application becomes
visible to address the issue of the alert persisting.
Silent Sms - Check both Type Indicator & TP-PID

Added additional check for Message type indicator & the TP-PID value so if mti == 0
or TP-PID == 0x40 then we have a Silent TYPE 0 Sms.

Additional check added as framework seems to use both in different places.
Merge pull request #78 from xLaMbChOpSx/master

Silent SMS Update