Skip to main content

bugs

See All Stories

Android’s Do Not Disturb ‘until next alarm’ option has randomly disappeared

do-not-disturb

When Google released Android 6.0 Marshmallow, it removed one of the most useful Do Not Disturb features, and that was the ‘until next alarm’ option. For those unfamiliar, it allows you to turn off all notifications until your morning alarm goes off and saves you being woken up at a ridiculous time. With 6.0.1, the feature returned, but recently it seems to have vanished again.

A thread on Reddit deals with the issue and claims that even users who aren’t running Android Marshmallow have experienced it. Some claim to have seen it disappear from the options while looking at them. I’ve tried to set Do Not Disturb myself, and like the complainants, I don’t see the ‘until next alarm’ option anymore.

Thankfully, there is a sort-of fix: change your phone’s date to before or after the holidays. If, for instance, you change your phone’s date to January 1st 2016, it seems to reappear, suggesting this is a really weird bug, or Google was trying to make sure you spent less time looking at your phone during the holiday period. You’ll get the same result if you change your phone’s date to before December 25th, according to Android Police.

If you don’t want to mess with your phone’s date, the option should return automatically in the new year, once the phone’s date changes to January 1st on its own.

AT&T’s Nexus 6 stock reportedly being sent back due to software bug (update)

Site default logo image

nexus-6-side-view

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.


Expand
Expanding
Close

Apple working to fix bug that causes ex-iPhone users to lose their text messages

Site default logo image

iMessages

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.


Expand
Expanding
Close

Samsung acknowledges Galaxy S5’s camera killing bug

Site default logo image

Verizon-GS5

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.


Expand
Expanding
Close

Site default logo image

Google increases bug bounties up to fivefold after paying out $2M to date

ImageCache

Google is increasing the bounty it pays to security researchers who discover and report bugs in Chromium by up to 500 percent after announcing that it has paid out a combined total of $2M in bug bounties across Chromium and Google-owned websites in just three years.

Today, the Chromium program is raising reward levels significantly. In a nutshell, bugs previously rewarded at the $1,000 level will now be considered for reward at up to $5,000. In many cases, this will be a 5x increase in reward level! We’ll issue higher rewards for bugs we believe present a more significant threat to user safety, and when the researcher provides an accurate analysis of exploitability and severity. We will continue to pay previously announced bonuses on top, such as those for providing a patch or finding an issue in a critical piece of open source software.

This follows earlier similar increases for reporting website vulnerabilities back in June.

Although the sums of money offered for reporting vulnerabilities are substantially lower than could be made by selling the info on the black market to those who would use it for nefarious reasons, the thinking behind bug bounties is it encourages those who would never dream of misusing the info to file prompt reports. Many large tech companies offer bug bounties, with Microsoft – a long-time hold-out – joining in a month ago.

Google hopes to bring December back to Android 4.2…by December?

Site default logo image

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.

Google engineer claims Adobe hid “embarrassingly high” number of Flash Player bugs

Site default logo image

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:


Expand
Expanding
Close