Assigned
Status Update
Comments
eu...@google.com <eu...@google.com> #2
interesting is thread creates for one number or for one contact? (one contact can
have more than one phone number)
have more than one phone number)
[Deleted User] <[Deleted User]> #3
Good question - since the "corrupting MMS" in this case comes from an e-mail address,
the thread is created using the sender's e-mail address. I'm looking through the
code now to understand how the SMS/MMS messages are stored in the SQLite database -
perhaps this sender's e-mail address or the sheer length of the MMS message causes an
mishandled corner case?
Let me know if I need to clarify further here...
the thread is created using the sender's e-mail address. I'm looking through the
code now to understand how the SMS/MMS messages are stored in the SQLite database -
perhaps this sender's e-mail address or the sheer length of the MMS message causes an
mishandled corner case?
Let me know if I need to clarify further here...
jc...@google.com <jc...@google.com> #4
Hello,
I just wanted to comment that I am having the same issue.
I only realized it was happening after I added a few new contacts or responded to
numbers that were not in my contact list before I received the
announcements@t-mobile.delivery.net... (i'm assuming this is the culprit)
As a result, any reply I make to someone that was newly added or not in my contact
list will not actually send to them (it just starts a thread that is listed as
announcements@t-mobile.delivery.net) and instead sends to the first number on my
contact list...(I have changed this to my own number...)
I don't want to hard reset bc then I will have to reinstall all of my progs...
If I don't reset, I will be annoyed with responding to all new recipients as if they
are a new number being entered into an sms, for each individual reply...
Please fix this...
Thanks
Nehemiah Richardson
I just wanted to comment that I am having the same issue.
I only realized it was happening after I added a few new contacts or responded to
numbers that were not in my contact list before I received the
announcements@t-mobile.delivery.net... (i'm assuming this is the culprit)
As a result, any reply I make to someone that was newly added or not in my contact
list will not actually send to them (it just starts a thread that is listed as
announcements@t-mobile.delivery.net) and instead sends to the first number on my
contact list...(I have changed this to my own number...)
I don't want to hard reset bc then I will have to reinstall all of my progs...
If I don't reset, I will be annoyed with responding to all new recipients as if they
are a new number being entered into an sms, for each individual reply...
Please fix this...
Thanks
Nehemiah Richardson
ki...@organizer.com <ki...@organizer.com> #5
This issue is really annoying.
As you can probably tell, it can get you into alot of trouble.
i.e. you texting one of your buddies a joke and your girlfriend ends up getting it
instead. Yeah. Not a happy time.
As you can probably tell, it can get you into alot of trouble.
i.e. you texting one of your buddies a joke and your girlfriend ends up getting it
instead. Yeah. Not a happy time.
jc...@google.com <jc...@google.com> #6
For those of you following this issue:
I need to have some test cases that "break" the phone. If you have experienced the
issue reported above, please copy/paste the entire txt of the "corrupting MMS" to
this thread (please feel free to X out any personal information that you don't want
posted here). Most importantly, we need the exact text of:
* The recipient
* The subject of the MMS (if there was one)
* The body of the MMS
Some of this info is available when you long press on the offending MMS and go to
"View Message Details".
As an example, the one I received was sent by "onlinebanking@alert.bankofamerica.com".
Also, if you or anyone else you know has been affected by this issue, please ask them
to leave their info here. I'm hoping that if enough of us leave messages, this will
get looked at by the Google engineers. Please also mention the link to this bug in
other forums that have been reporting this problem. Thanks.
I need to have some test cases that "break" the phone. If you have experienced the
issue reported above, please copy/paste the entire txt of the "corrupting MMS" to
this thread (please feel free to X out any personal information that you don't want
posted here). Most importantly, we need the exact text of:
* The recipient
* The subject of the MMS (if there was one)
* The body of the MMS
Some of this info is available when you long press on the offending MMS and go to
"View Message Details".
As an example, the one I received was sent by "onlinebanking@alert.bankofamerica.com".
Also, if you or anyone else you know has been affected by this issue, please ask them
to leave their info here. I'm hoping that if enough of us leave messages, this will
get looked at by the Google engineers. Please also mention the link to this bug in
other forums that have been reporting this problem. Thanks.
to...@gmail.com <to...@gmail.com> #7
having same problem
to...@gmail.com <to...@gmail.com> #8
I'm getting the same problem as stated on the post. This happens when I receive MMS from
Innercircle@marketinginnovators.com this is really really annoying, you can't reply, you have to create a
new thread in order for you to reply
Innercircle@marketinginnovators.com this is really really annoying, you can't reply, you have to create a
new thread in order for you to reply
[Deleted User] <[Deleted User]> #9
I'm having the same issue and I think it was caused by an email from Citibank.
I tried T-Mobile's technical support, but they had no idea about this problem.
I tried T-Mobile's technical support, but they had no idea about this problem.
[Deleted User] <[Deleted User]> #10
This is extremely annoying. Is anyone working to fix this problem?
[Deleted User] <[Deleted User]> #11
Bueller? Bueller? Is anyone looking at this or am I going to have to rewrite this
thing?
thing?
bv...@gmail.com <bv...@gmail.com> #12
Happening to me too. It's been like this since I've gotten the phone, and it's
totally annoying. I'm working around it by not"replying" to texts. I'm closing the
text and composing a new message to reply.
I *think* it started when I received a picture message.
totally annoying. I'm working around it by not"replying" to texts. I'm closing the
text and composing a new message to reply.
I *think* it started when I received a picture message.
tv...@gmail.com <tv...@gmail.com> #13
I had the above issue several weeks ago. I performed the hard reset as described by
the author and the issue went away. In my case the source of the mms message was an
alert email from work and I have since disabled it. The problem has not returned.
**** Try this at your own risk ***
There is an application on the market called astro which helps you backup the
applications and thus do not have to document every application before a hard reset.
Astro will backup the applications to the sd card. This will save time from
searching and re-downloading from the market. Astro **does not** backup application
data. You must go into each application and save or export the application data to
the sd card if the option is available. A hard reset has never erased the sd card
for me. After the hard reset, reinstall astro and then start re-loading your apps
direct from the sd card. You can then reload each application data backup if
necessary.
* I did not have astro when I corrected the issue on my g1. I did have astro when I
hard reset the phone a 2nd time for unrelated issue.*
1 drawback is that the apps reinstalled from sd card do not show up in the market
cache. So its a little hard to track application updates unless you eventually
reload from the market or use an application like oi update or atrackdog which track
application updates.
Hopefully a fix comes out soon for this issue.
the author and the issue went away. In my case the source of the mms message was an
alert email from work and I have since disabled it. The problem has not returned.
**** Try this at your own risk ***
There is an application on the market called astro which helps you backup the
applications and thus do not have to document every application before a hard reset.
Astro will backup the applications to the sd card. This will save time from
searching and re-downloading from the market. Astro **does not** backup application
data. You must go into each application and save or export the application data to
the sd card if the option is available. A hard reset has never erased the sd card
for me. After the hard reset, reinstall astro and then start re-loading your apps
direct from the sd card. You can then reload each application data backup if
necessary.
* I did not have astro when I corrected the issue on my g1. I did have astro when I
hard reset the phone a 2nd time for unrelated issue.*
1 drawback is that the apps reinstalled from sd card do not show up in the market
cache. So its a little hard to track application updates unless you eventually
reload from the market or use an application like oi update or atrackdog which track
application updates.
Hopefully a fix comes out soon for this issue.
r....@gmail.com <r....@gmail.com> #14
To anyone who currently has this issue and has not yet performed a hard reset:
Version 1.6 of ChompSMS (an SMS application available in the market) currently does
*not* have support for MMS messages. Please install this application and check to
see if you continue to see the same behavior (threads being merged, SMS's being sent
to wrong recipient). This will help us isolate whether the issue is with Android's
core MMS application itself *or* the way that the SQLite database stores the messages
(I'm suspecting the latter).
I would try this myself, but I'm currently "MMS Clean" and a little weary of
reinstalling apps (tho thanks to fadeng for his suggestions :)
adamcolon: If you are working on this then we'd appreciate any updates here. The
good news is that the Google folks have recently done a code drop from the cupcake
branch 12 days ago (as of this writing) that has numerous updates to Android's core
MMS app. I'm studying the updates now to see if they might have "accidentally" found
and fixed the issue without updating this bug report.
For those interested, the commitdiff for the MMS package is viewable via the web here:
http://android.git.kernel.org/?p=platform/packages/apps/Mms.git;a=commitdiff;h=0f236f55349f070ac94e12cca963847173393da8
Version 1.6 of ChompSMS (an SMS application available in the market) currently does
*not* have support for MMS messages. Please install this application and check to
see if you continue to see the same behavior (threads being merged, SMS's being sent
to wrong recipient). This will help us isolate whether the issue is with Android's
core MMS application itself *or* the way that the SQLite database stores the messages
(I'm suspecting the latter).
I would try this myself, but I'm currently "MMS Clean" and a little weary of
reinstalling apps (tho thanks to fadeng for his suggestions :)
adamcolon: If you are working on this then we'd appreciate any updates here. The
good news is that the Google folks have recently done a code drop from the cupcake
branch 12 days ago (as of this writing) that has numerous updates to Android's core
MMS app. I'm studying the updates now to see if they might have "accidentally" found
and fixed the issue without updating this bug report.
For those interested, the commitdiff for the MMS package is viewable via the web here:
eu...@google.com <eu...@google.com>
bl...@google.com <bl...@google.com>
al...@google.com <al...@google.com>
we...@google.com <we...@google.com>
bw...@google.com <bw...@google.com>
bw...@google.com <bw...@google.com> #15
I have this issue, and installed ChompSMS today, and it has the same problem as the
built in sms/mms client (messages incorrectly threaded, replies go to the wrong
person). It has the same people mis-threaded as the built in client.
It's incredibly frustrating and makes SMS/MMS essentially useless, I hope it gets
fixed soon.
built in sms/mms client (messages incorrectly threaded, replies go to the wrong
person). It has the same people mis-threaded as the built in client.
It's incredibly frustrating and makes SMS/MMS essentially useless, I hope it gets
fixed soon.
Description
Testcase I used:
1. Ran query A that has same subquery repeated 6 times. Time to execute - 195sec
2. Ran subquery first time - Time to execute ~ 30sec
3. Ran subquery second time - Time to execute ~ 2.5sec
4. Created view based on subquery and request data - Time to execute ~ 30sec
5. Ran view request second time - Time to execute ~ 2.5sec
6. Ran initial query with subqueries replaced with view query - Time to execute ~ 160sec
All data were static and was not updated during test.
It seems that there is no optimization of query execution plan based view, which could potentially save a lot of time, CPU and reads. Is it possible to include such kind of optimization in query planner?
Sincerely yours,
Kirill Lebedev
Chief Software engineer at Organizer