Ticket #1649 (assigned defect)

Opened 9 years ago

Last modified 9 years ago

SMS messages show up as MIME attachment

Reported by: kenrestivo Owned by:
Priority: normal Milestone:
Component: Qtopia Version: GTA02v5
Severity: normal Keywords:
Cc: Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: PatchReviewResult:
Reproducible:

Description

In the ASU Messages application, some SMS messages show up as Attachment: application/x-qtopia-sms-1, and the phone doesn't appear to have any way to read those. They also show the sending number as "50", so perhaps they come from the cell carrier.

Other messages from friends look fine.

I also can't find where these attachments are stored, so I'm unable to copy them to my desktop or otherwise open them in the terminal as a workaround either.

Change History

comment:1 Changed 9 years ago by zecke

  • Owner zecke deleted
  • Status changed from new to assigned
  • Milestone ASU deleted

Removing myself as the owner of the bug. Removing the ASU milestone as it is used by the PM and his delegates.

comment:2 Changed 9 years ago by zecke

Same procedure as with #1647. Would you mind sharing the PDU (message) with us? If you don't please attach it to the bugtracker. On startup Qtopia should query the SMS (AT+CMGL) and the message should get listed, you should be able to identify it.

comment:3 Changed 9 years ago by kenrestivo

I would love to attach the actual message to the bug report, but I can't figure out where it is stored in the FR filesystem. Is it in a SQLite database somewhere? If so, which? Is it in a flat file somewhere? I haven't been able to find it yet.

For the record, I did not assign this bug to anyone. I did list it as ASU because this is related to the ASU distribution, but I guess I'm not supposed to do that, so I won't.

comment:4 Changed 9 years ago by zecke

You have to enable logging, I described that in #1647 and then after startup execute logread. Then search for AT+CMGL. This command will list the stored messages. One message per line, you should be able to identify the message by the "service number" (50).

Note: See TracTickets for help on using tickets.