Chances are you heard about the Gmail outage that took place on Friday. But there is something else that happened aside from it. A glitch in Google search is causing David S. Peck, a Hotmail user, to receive thousands of emails from people he does not even know. During the outage, people were frantically searching ”Gmail” and when they clicked on the first sublink, they were sent to a window that had Peck’s email address in the “To” input box. Of course, people decided to press Send. » Read the rest
Google announced it will correct the bug which prohibited the entry of December events into the updated People app in Android 4.2. The good news came via a Google+ post for the official Android account. While no specific date was given we’re hopeful “soon” means sometime before December arrives.
Some people I still think this may have been Google’s attempt to prevent the end of the world by not allowing 12/21/2012 to come. Read the full statement below.
“We discovered a bug in the Android 4.2 update, which makes it impossible to enter December events in optional fields of the People app (this bug did not affect Calendar). Rest assured, this will be fixed soon so that those of you with December birthdays and anniversaries won’t be forgotten by your friends and family.”
Source: Android Google+
The newest iteration of Android, version 4.2 Jelly Bean, seems to think there are just 11 months in a year, effectively leaving out December altogether. No presents? No Santa? What ever shall we do?
The updated People application found in the stock AOSP version of the software doesn’t allow users to select the 12th month of the year, meaning people who have birthdays, anniversaries or any other sort of special event around Christmas time aren’t able to have it recognized.
The issue has been reported to the official bug tracker and has already been acknowledged by Google. We’re expecting an update to Android 4.1.2 soon. Perhaps, before non-existent December rolls around?
Samsung’s Galaxy Tab 10.1 has released a 63.12MB update to users which brings the device to Android 3.2 and, oh yeah, it has a serious glitch which is causing all kinds of WiFi connection problems. Since the Android tablet is WiFi-only, users that have already completed their update are left with a relatively useless device.
Of the problems reported, users say their tablet would no longer connect to WiFi with DHCP dynamic IP and rather only through static IP. Also, it will no longer connect to Kies, displays “Firmware update failed” upon reboot and even ceases auto rotation. As for a solution to the glitch, hard resets have proven ineffective and Samsung has offered only the following statement to their customers:
“Samsung is aware of an issue that some Galaxy Tab 10.1 customers have experienced with today’s software update. We are working on a resolution and will provide more information shortly. In the interim we have chosen to discontinue availability of the update.”
You may have read last week about the SMS bug that has been plaguing some Android users. Or maybe you heard us talk about it on our InfoByte podcast this week. Maybe you’ve even experienced the SMS bug yourself, and found your texts going to random, unintended recipients.
We were on the fence about whether we believed it was actually a bug, or whether it was just user error. Apparently Google was able to reproduce the issue consistently enough that they were able to determine that it was, in fact, a legitimate problem, but only affecting a very small subset of users in very specific circumstances. They have been able to track it down, however, and have created a fix. They issued the following statement:
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.
They have not yet made a statement as to how or when the fix will be deployed, but if we learn anything more we will let you know.
[via Google's Code Blog]
During Google’s I\O Conference, they handed out around 5,000 EVO 4G’s to attendees. How does that benefit them? A whole lot of hardcore testing. Well low and behold, something popped up.
The lucky ones who got their hands on the EVO a few weeks early have been reporting issues with not being able to write data to the included 8GB microSD card. (Yes I know my image above shows 4GB, gimme a break) Apparently it’s an intermittent issue, but when it occurs it can cause hang ups, or even total crashes. Obviously this isn’t a good thing, but a simple reboot fixes the problem.
Not one to stand around and ignore the problem, HTC is aware of the problem and will be pushing out a software update to the phone as soon as a solution is available (which they expect to be very soon).