Al parecer, cuando tienes varias conversaciones de SMS, cuando envías el mensaje al número A, recibes la confirmación de recibido con el número A, cuando en realidad ha llegado a un número B aleatorio (no es aleatorio en realidad, pero no se ha "descubierto" aún el núcleo dónde reside el error de código que selecciona o confunde el número)...mientras tanto, A estará esperando respuesta. Google ha calificado la prioridad del fallo como media (http://code.google.com/p/android/issues/detail?id=9392) Español: http://kcy.me/1ihp
#1 Yo creo que a la mayoría de gente que hay echando chispas por el bug, tiene que ser por eso..porque a mí, aún habiéndome pasado,no me pondría así... aunque también es verdad que no he mandado mensajes peligrosos, ni tengo ninguna situación susceptible de ello
#5 Justificar un bug de un sistema porque en otro pasa o no pasa, me parece bastante lamentable
#9 A mí y a mi chico tampoco, pero por lo visto, a muchísima gente así y es una vergüenza que hasta que no se le ha dado algo de publicidad, haya estado como prioridad media. A ver si lo arreglan ya de una vez.
----
If anyone is interested, evidently "Darth Mo" has been able to replicate it - found in ACentral Forums - entire post follows;
"It's not user error, or at least it's a combination of user technique and a possible design. It has to do with how the stock messaging app interacts with the Android system notification.
I recreated it this way. Open a text, but only from the notification bar. You will be taken directly to the conversation from that contact. Now, just hit the home button to get back to the home screen. Repeat this four times to let the open conversations build up. We'll call the earliest contact 1, the next 2, etc. for this example. Let's say you converse with these contacts over some time so that messages occur in this chronological order (opened from the notification menu if possible) : 1, you, 2, you, 3, you, 4, you, 1, 3, you, 3.
Now, you've read the message from contact 3, but quickly hit the back button because you need to send a message to contact 4. So you're back at the conversation list and select conversation 4. You compose and send your message and off you go. But, what can actually happen is that your message went to contact 1 because there is a bug that when you use the back button, it will take you to the conversation screen and when you select one, it will take you to the conversation with the last "unreplied" message received before the last conversation you didn't reply to, regardless of the one you actually select from the list. It's easy to miss that it took you to the wrong conversation as the on screen info can take a beat to update and it looks like you've select the right conversation. The kicker is the conversation list does highlight the one you meant to select, but will take you to that other conversation. It's as if it's saying, "Hey, I know you want to go to that one, but you opened this message and jumped out of it without replying. Maybe you didn't see it."
It's pretty easy for people to not have seen this for a few reasons:
1. You open messages directly from the messaging app
2. You close out every conversation using the back button and don't let them build up on top of each other
3. Messages can come in such a sequence that the conditions are never correct
4. It has actually happened, only the last "unreplied" message was from the conversation you actually intended to enter
I was able to create reliably using my Google voice number to send myself text and watched it bounce around conversations seemingly randomly. It was only when I looked at the times of each message with no replies that I saw what it was doing actually had order to it.
About 30 minutes of experimentation to figure it out, but I had to know how this was happening as I could see it leading to an egregious error later. Now to explain it to HTC..."
---------
Comentarios
Vamos, que mandas un sms a la amante y le llega a tu mujer (o al reves...)
Y lo peor de todo es que el bug ya tiene 6 meses y Google le da una prioridad "media"
#1 Yo creo que a la mayoría de gente que hay echando chispas por el bug, tiene que ser por eso..porque a mí, aún habiéndome pasado,no me pondría así... aunque también es verdad que no he mandado mensajes peligrosos, ni tengo ninguna situación susceptible de ello
a la gente le parece muchísimo más grave que el iPhone haya tenido problemas con las alarmas esta mañana 1 de enero
#5 Justificar un bug de un sistema porque en otro pasa o no pasa, me parece bastante lamentable
#9 A mí y a mi chico tampoco, pero por lo visto, a muchísima gente así y es una vergüenza que hasta que no se le ha dado algo de publicidad, haya estado como prioridad media. A ver si lo arreglan ya de una vez.
Debe tener prioridad media porque en Google no se concibe enviar SMS teniendo conexión de datos...
#6 Acaban de subirla a prioridad crítica.
http://code.google.com/p/android/issues/detail?id=9392
#6 bueno, al menos el salir en Engadget ha servido para algo
Yo llevo usando android desde hace año y pico y esto no me pasa, no se cuales serán las condiciones para reproducirlo. ¿A alguien le ha pasado?
#9 A mi tampoco nunca me ha pasado
Buah, me imagino el mismo bug en el iPhone, y me da que el tratamiento no iba a ser tan light
Un usuario ha conseguido reproducir el fallo: copy/paste from http://forum.androidcentral.com/435165-post16.html
----
If anyone is interested, evidently "Darth Mo" has been able to replicate it - found in ACentral Forums - entire post follows;
"It's not user error, or at least it's a combination of user technique and a possible design. It has to do with how the stock messaging app interacts with the Android system notification.
I recreated it this way. Open a text, but only from the notification bar. You will be taken directly to the conversation from that contact. Now, just hit the home button to get back to the home screen. Repeat this four times to let the open conversations build up. We'll call the earliest contact 1, the next 2, etc. for this example. Let's say you converse with these contacts over some time so that messages occur in this chronological order (opened from the notification menu if possible) : 1, you, 2, you, 3, you, 4, you, 1, 3, you, 3.
Now, you've read the message from contact 3, but quickly hit the back button because you need to send a message to contact 4. So you're back at the conversation list and select conversation 4. You compose and send your message and off you go. But, what can actually happen is that your message went to contact 1 because there is a bug that when you use the back button, it will take you to the conversation screen and when you select one, it will take you to the conversation with the last "unreplied" message received before the last conversation you didn't reply to, regardless of the one you actually select from the list. It's easy to miss that it took you to the wrong conversation as the on screen info can take a beat to update and it looks like you've select the right conversation. The kicker is the conversation list does highlight the one you meant to select, but will take you to that other conversation. It's as if it's saying, "Hey, I know you want to go to that one, but you opened this message and jumped out of it without replying. Maybe you didn't see it."
It's pretty easy for people to not have seen this for a few reasons:
1. You open messages directly from the messaging app
2. You close out every conversation using the back button and don't let them build up on top of each other
3. Messages can come in such a sequence that the conditions are never correct
4. It has actually happened, only the last "unreplied" message was from the conversation you actually intended to enter
I was able to create reliably using my Google voice number to send myself text and watched it bounce around conversations seemingly randomly. It was only when I looked at the times of each message with no replies that I saw what it was doing actually had order to it.
About 30 minutes of experimentation to figure it out, but I had to know how this was happening as I could see it leading to an egregious error later. Now to explain it to HTC..."
---------
A este bug hay que sumarle el troyano chino. Android lo está pasando mal últimamente.
Al final parece que la han subido a "Critical"
La madre que los parió. ¿Cómo es posible que lleve semejante bug sin arreglar desde hace tiempo? Y encima sobreviva en Gingerbread!
Joder, no me puedo creer que esto no suba a portada, es gravisimo
Vaya follón que han montado en el hilo de Google Code.