For reasons unknown, Google disabled the Nexus 6's tap-to-wake feature

Not the end of the world, we suppose

The Nexus 6 comes with Android 5.0 Lollipop, Google's latest mobile operating system that brings a number of cool new features to any device running it. However it appears that on the Nexus 6 Google has disabled the tap-to-wake function.

This feature would have allowed Nexus 6 owners to double tap the screen to wake the device up rather than having to press the power button.

The Nexus 6 initially had the feature, however in a code commit on Google's website it appears that Google has disabled the feature.

There hasn't been an official explanation about why Google has taken the feature out of the Nexus 6. The Nexus 9 includes the feature without any problems.

A potential reason for Google disabling the tap to wake feature was mentioned by PhoneArena. As the Nexus 6 is manufactured by Motorola it comes with an Ambient Display, which is similar to the active display found in the Moto X.

Motorola's unique display might be causing issues with the tap-to-wake feature, but until it's officially confirmed this is all speculation. What we do know is that sadly the Nexus 6 will be shipping with one less feature.

Via PhoneArena

See more phone and communications news Sign up to receive our free weekly newsletter with the week's hottest news, reviews and offers.

View the original article here

Apple lists the top 10 reasons apps get rejected

Screenshot by Michelle Starr/CNET

When a developer submits an app to the iTunes App Store, Apple runs it through a manual review process to make sure everything is up to scratch. This is a time of tenterhooks: Apple's standards are high, and it's not uncommon for an app to be sent back to the developer for tweaking.

But why are apps sent back? We've all heard about the occasional app that gets pulled or rejected for content, but surely that's not the case with every app that gets sent back to the drawing board.

And, as it turns out, it's not: Apple has published a post on its developer site that clearly outlines its review criteria, with a breakdown of the most common reasons that an app will get rejected.

"Before you develop your app, it's important to become familiar with the technical, content, and design criteria that we use to review all apps," Apple wrote. "We've highlighted some of the most common issues that cause apps to get rejected to help you better prepare your apps before submitting them for review."

Most of the reasons for rejection seem to be technical in nature: an app that crashes frequently or is buggy, for instance, or contains broken links, or incomplete forms. Other reasons include terrible UIs, apps that aren't considered "engaging and useful", misleading information, and trying to submit too many apps that are similar to each other.

But by far and away the highest rate of rejection at 14 percent falls under "More information needed" -- which simply means that the review submission form -- the form developers need to fill out when submitting their app for review -- is incomplete.

This is followed by bugginess at 8 percent, and non-compliance with the Developer Program License Agreement and terrible user interfaces in equal third at 6 percent. In all, the top 10 reasons for app rejections account for 58 percent of all app rejections.

Apple did not go into detail about the remaining 42 percent, nor state what percentage of apps get rejected in the first place. As of June 2014, Apple had 1.2 million apps in the iTunes app store, and had seen over 75 billion app downloads.

View the original article here