Android 2.2 Messaging Bug(s) Is (Are) Getting Fixed

#Android22 #MessagingBug is not a #Messagegate http://snapvoip.blogspot.com/
The Android Messaging bug reported on the Google Android Forum is getting fixed, Google says. A user posted  the problem on Google Android Forum, (Issue 9392) complained about SMS or TXT messages being sent to wrong people. The thread continued with various other users joining in with threats, begs and sometimes funny notes like

Comment xxxx by xxxxxxx, Jan 02 (4 days ago)

oh   come on   that's horrible   the message which is supposed to my girlfriend went to my boss      please fix it as soon as you guys can

But it continued with many "fix it", "FIX IT", "WTF FIX IT", occasionally peppered with messages from a user who insisted that the thread is the work of Trolls. Thankfully I did not experience problem and most my work SMS goes out of Google Voice in any case.
But the best part is Google Android Team discovering the problem, actually two according to the post which are being fixed. The fixes will be deployed shortly.

Comment 1460 by project member n...@google.com, Yesterday (20 hours ago)

Thanks to everyone for your patience while we've been investigating these reports. As it turns out, we believe there are two distinct situations being discussed on this issue chain. Fortunately, we have fixes for both of them. When some users tap to open a message in the Messaging application, they're seeing a different message appear instead. We don't believe this issue is affecting many users, but we've developed a fix that we're preparing to deploy.

Of course, double-checking the displayed message before hitting "Send" will prevent any messages from being sent to the wrong recipients. We've found in testing this issue, it is more likely to occur if you tap on a message before the Messaging app is fully loaded, so we recommend waiting for all the elements to load before clicking on the message you want to display.
Separately, some users have reported that their SMS messages are being delivered to the wrong people. It took us some time to reproduce this issue, as it appears that it's only occurring very rarely. Even so, we've now managed to both reproduce it and develop a fix that we will deploy.
While we don't anticipate any persistent problems, we'll continue to investigate in case we come up with additional ways to trigger these bugs. Thanks again for helping us improve Android.

Very lucky for Google it did not become a Messagegate like rival Apple's Alarmgate or Antennagate! But it almost did, with the section below the high lighted area, saying users do not know how to use the phone, like Steve Jobs saying users do not know how to hold the iPhone.

How To Fix iPhone Alarm Bug! Alarmgate.

#iPhone #Alarmgate http://snapvoip.blogspot.com/
Just like the Antennagate, aka "You Do NOT Know How To Hold The iPhone 4!", Apple left a new year gift on our desk tops. Many people who were relying on iPhone to wake up found them missing flights, being late for work and having so many troubles. Well my alarm is on a Droid!  and it worked fine, even woke me up to read the news about iPhone alarm bug. But my partners iPhone alarm, which was also running iOS 4.1 went off without a hitch. Perhaps because of the new year rituals, she had to set the alarms anew.
So if you have an iPhone running iOS 4.0.2, iOS 4.2 or iOS 4.2, you can follow the simple procedudure below to fix the alarm or just wait till Monday as Apple suggests.
Run the Clock set an alarm by tapping "+" and set your alarm as you want. Select "Repeat" and set the desired repeat interval and "Save". You are done.

Hope you guys wake up on time and catch that plane or bus.