I have a Nexus S on Android 4.04. This version of Android has a SMS messaging delete bug. The bug happens when you try to delete a message other than the first message in the "thread". Android 4.04 will delete the first message instead of the message that you want to delete.
For example, suppose you have a thread with 5 messages. You want to delete the 5th message and keep the first four messages. When you select the 5th message in the "thread" to delete, Android will delete the first message instead of the 5th message. This only happens the first time you have Messaging "launched". If you try to delete the 5th message (which is the 4th message now) after the initial delete, Android will delete the 5th message correctly. But if you quit Messaging and relaunch Messaging, the bug will reoccur the first time you delete a message.
I tried googling to see if this bug has been fixed but there is very little info on this bug. I want to keep using this Nexus S phone. According to Wikipedia, the Nexus S phone is upgradable to 4.1.2 Jelly Bean.
My question is anyone aware of this Android 4.04 messaging delete bug and does Android 4.1.2 Jelly Bean fixes the issue?
For example, suppose you have a thread with 5 messages. You want to delete the 5th message and keep the first four messages. When you select the 5th message in the "thread" to delete, Android will delete the first message instead of the 5th message. This only happens the first time you have Messaging "launched". If you try to delete the 5th message (which is the 4th message now) after the initial delete, Android will delete the 5th message correctly. But if you quit Messaging and relaunch Messaging, the bug will reoccur the first time you delete a message.
I tried googling to see if this bug has been fixed but there is very little info on this bug. I want to keep using this Nexus S phone. According to Wikipedia, the Nexus S phone is upgradable to 4.1.2 Jelly Bean.
My question is anyone aware of this Android 4.04 messaging delete bug and does Android 4.1.2 Jelly Bean fixes the issue?