Recently, probably with one of the major releases, my phone stopped displaying the Subject: line on email-to-sms messages.
I use my phone for monitoring servers at work, and our nagios-like system sends out important information in the Subject line. An email that is sent to the <number>@tmomail.net gateway that looks like
Subject: Server WEB-123
Ping result: down
...used to come across in an sms like
"<Subject: Server WEB-123> - Ping result: down"
...but now comes across in an sms like
"Ping result: down"
The "subject line" is being stripped or omitted somehow. I called tmobile and spent a long time with one of the technicians who finally declared it an android "app" problem, and closed the case.
I even swapped out SIM cards with a friend and tested -- the subject stripping stayed with the android/G1 and not with the SIM card/number.
<pause for troubleshooting>
Ok, I just sent a lot of tests with different length messages. I sent emails with a 27 byte subject, and each email had a body length increasing 10 bytes in length. When I hit 120 bytes in the body, the subject started showing up again.
Additionally, with shorter messages, the g1 sms application would just pop up the body of the message, but when longer messages, it would show the subject with italicized message "loading message..." with the size of the message ... that loading message would then be replaced with the actual message.
My initial guess would be that if it can send the entire body/content as one packet, one message, one whatever ... then the subject is erroneously OMITTED by the android sms application.. where if it has to go back and wait for the rest of the message to load, get the next packet, etc, then, it DOES show the subject.
Using my phone to receive server notifications via email-to-sms gateway is fairly critical. Has anyone else experienced this, and is there any viability of this to the android dev team? IE, is it a known issue, perhaps being worked on?
Thanks so much for any help/insight !!
mrHua
Phone: T-mobile G1, firmware version 1.6
ps. I'm not sure if there is a "tech support" thread, or if this belongs in a developer thread...
I use my phone for monitoring servers at work, and our nagios-like system sends out important information in the Subject line. An email that is sent to the <number>@tmomail.net gateway that looks like
Subject: Server WEB-123
Ping result: down
...used to come across in an sms like
"<Subject: Server WEB-123> - Ping result: down"
...but now comes across in an sms like
"Ping result: down"
The "subject line" is being stripped or omitted somehow. I called tmobile and spent a long time with one of the technicians who finally declared it an android "app" problem, and closed the case.
I even swapped out SIM cards with a friend and tested -- the subject stripping stayed with the android/G1 and not with the SIM card/number.
<pause for troubleshooting>
Ok, I just sent a lot of tests with different length messages. I sent emails with a 27 byte subject, and each email had a body length increasing 10 bytes in length. When I hit 120 bytes in the body, the subject started showing up again.
Additionally, with shorter messages, the g1 sms application would just pop up the body of the message, but when longer messages, it would show the subject with italicized message "loading message..." with the size of the message ... that loading message would then be replaced with the actual message.
My initial guess would be that if it can send the entire body/content as one packet, one message, one whatever ... then the subject is erroneously OMITTED by the android sms application.. where if it has to go back and wait for the rest of the message to load, get the next packet, etc, then, it DOES show the subject.
Using my phone to receive server notifications via email-to-sms gateway is fairly critical. Has anyone else experienced this, and is there any viability of this to the android dev team? IE, is it a known issue, perhaps being worked on?
Thanks so much for any help/insight !!
mrHua
Phone: T-mobile G1, firmware version 1.6
ps. I'm not sure if there is a "tech support" thread, or if this belongs in a developer thread...