AT&T retail stores are reportedly being told to send back their first shipments of Google’s Nexus 6 due to a software bug identified by Motorola. The noted issues with this glitch are a blacked out screen and trouble connecting to the carrier’s service. Motorola Mobility is said to be working on restocking Ma Bell’s inventory with replacement devices, however this will likely have an impact on the handset’s availability.
bugs November 21, 2014
bugs May 22, 2014
Apple says it’s resolved an iMessage server issue that was affecting former iPhone users who switched to Android and other mobile operating systems. This is all good and well, but Apple’s text message woes don’t end there. The company is currently working on another SMS intercepting issue, according to Re/code. Apple is struggling to keep track of phone numbers that used to be linked to its iMessage platform. This is causing some ex-iPhone owners’ text messages to be absorbed by the company’s servers before reaching their intended contact.
bugs April 25, 2014
The Samsung Galaxy S5’s camera is a major selling point for the company’s new flagship smartphone, however a newly discovered bug may soon turn would-be buyers away from the device. There have been several reports across the web documenting an issue with the handset’s shooter — most notably its Verizon version — that completely breaks the phone’s camera.
bugs August 13, 2013
bugs November 20, 2012
Those that updated to Android 4.2 might have noticed a bug that prevents users from selecting December for events like birthdays inside of the People app. Google has now officially addressed the issue in a post on the Android Google+ page by confirming that it plans to fix the bug before December:
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.
bugs August 10, 2011
After sending out the usual laundry list of bug fixes for its Flash Player yesterday, Adobe is coming under pressure from Google security engineer Tavis Ormandy who claims the update only listed 13 of the approximately “400 unique vulnerabilities”… A number he describes as “embarrassingly high”.
Ormandy claims he sent the bugs to be fixed “as part of an ongoing security audit” and, according to a report from Computerworld, was “upset that he was not credited for his bug reports”. After noticing he hadn’t received credit in the patch, he took to Twitter to address his concerns, prompting Adobe’s senior manager of corporate communications to tweet the following:
“Tavis, please do not confuse sample files with unique vulnerabilities. What is Google’s agenda here?”
Ormandy responded, also in a tweet, saying:
“I don’t know what Google’s agenda is, but my agenda is getting credit for my work and getting vulnerabilities documented.”
Hours before the patch officially rolled out, Google launched the latest version of Chrome 13 and 14, which included the Flash Player patch in question, and was accompanied by the following statement from Google:
“The Chrome Team would especially like to thank Tavis Ormandy, the Google Security Team, and Google for donating a large amount of time and compute power to identify a significant number of vulnerabilities resolved in this release of Flash Player.”
Adobe did credit 10 other researchers in the report accompanying the update, but had only this to say about Google and Ormandy’s work: