CHANGELOG.md

Version History:

• v1.0.0
  • initial release
• v1.1.0
  • Preference Sender changed to Sender must end with
    • in v1.0.0:
      • exact match
    • in v1.1.0:
      • value entered in whitelist rule only needs to occur at the end of the SMS sender
      • the purpose for this change is to ignore optional country codes, and such
        • example:
          • field value: 9876543210
          • SMS sender: +19876543210
          • is match?:
            • v1.0.0: no
            • v1.1.0: yes
• v1.2.0
  • Preference Sender must end with
    • adds support for a match-all glob pattern
      • when the value for this field in a rule is exactly: *
      • then the field will match the SMS sender for all incoming SMS text messages
• v2.0.0
  • the idea was borrowed from: Silent Ping SMS for Android
  • details:
    • uses: SmsManager.sendDataMessage()
    • port: 9200
  • usage:
    • to send:
      • open app from launcher
      • click 'silent' menu icon
      • enter phone number of recipient (who must also have 'SMS my GPS' installed and its service enabled)
      • click 'send'
    • on receiving end:
      • the SMS does not trigger any notification or sound alert
      • the SMS does not register in the normal text SMS app
      • the SMS does reach 'SMS my GPS'
        • if the phone number of the sender matches the (non-glob) value of the sender field in any whitelist rule, then a match occurs and a reply text SMS is sent with GPS data.
  • limitations:
    • SmsManager.sendDataMessage() does not work on CDMA phones
      • GSM only
  • status:
    • normal functionality has been tested, and works the same as v1.2.0
    • silent data-only functionality is untested
      • I only own CDMA phones
      • I have no idea if message.getUserData() in SMSReceiver returns the same byte[] out as was originally passed in to sendDataMessage() in SilentSMSSender
      • feedback is welcome
• v2.0.1
  • minor fix
    • persist Preference data after deletion of each whitelist rule
• v2.1.0
  • add 'Direction' to GPS data in SMS text reply
    • only included when value is valid
• v2.1.1
  • minor fix
    • if 'Direction' includes a bearing containing a range of degree values, format each degree value to stay within: 0.0 to 360.0
• v2.1.2
  • minor tweak
    • truncate SMS reply if it were to exceeds the max length
• v2.1.3
  • minor tweak
    • change format of URL for Google Maps
      • old: https://www.google.com/maps/search/?api=1&query={lat},{lon}
      • new: https://maps.google.com/?q={lat},{lon}
      • why:
        • old:
          • works in: web browser, Google Maps app
          • fails in: OsmAnd app
            => "could not parse geo intent"
        • new:
          • works in all
• v2.1.4
  • minor tweak
    • prioritize broacast receiver intent filters
      • only important before: Android 4.4 (API 19)
• v2.1.5
  • add runtime permission checks
    • applies to: Android 6.0+ (API 23)