ParandroidMessaging icon indicating copy to clipboard operation
ParandroidMessaging copied to clipboard

Error sending public key

Open n8fr8 opened this issue 15 years ago • 3 comments

When I try to send my public key on T-Mobile USA using a Nexus One (with Cyanogen), I get the following error message back from the carrier:

"Unable to send message to 1917xxxxxx. Please try again without a symbol in the text"

Perhaps you need to Base64 encode the data you are sending?

n8fr8 avatar Apr 27 '10 04:04 n8fr8

Hi Nathan,

thanks for submitting the issue. We used to sent messages base64 encoded, however we were able to send binary messages, so we skipped the base64 encoding and decoding part (also since base64 comes with some overhead).

We will look into this quickly.

jklardie avatar Apr 27 '10 07:04 jklardie

I searched around a bit, and it seems a known issue for the Nexus One (and other devices). For some, the SMSC number was wrong, might be in the Cyanogen APN list.

Can you try this, Nathan? I found it here: http://www.google.com/support/forum/p/android/thread?tid=3f4ad5ffac46bf92&hl=en

  • Dial ##4636##
  • Go to 'Phone information'
  • Scroll all the way down on the page that opens and type in your SMSC number.
  • T-Mobile's SMSC is +12063130004
  • Hit UPDATE.

Also, can you e-mail me your Nexus One phone number so I can send my public key, see if that works. Thanks for testing!

erikwt avatar Apr 27 '10 08:04 erikwt

Erik, At #guardianhackday, three people tried to send public keys over the T-mobile network. Was tested on N1, MyTouch and G1 phones, all normal builds. None worked. The fix you pointed to seems to be for sending normal SMSs; all these phones can send unecrypted SMSs. It seems to be an issue of sending binary SMS that are not base-64 encoded (discussed further on IRC)..

prabhasp avatar Apr 27 '10 17:04 prabhasp