Android Police

Articles Tagged:

android CDD

53

After years, Google to force Android device OEMs to support [some] standard headphone inline controls

After years, Google to force Android device OEMs to support [some] standard headphone inline controls

The Android CDD is a tedious document to pick over, largely because very small changes in wording can have very big consequences. While I would hardly call this one "very big," it's still significant: Google has changed the support of standard impedance-based inline headphones controls from a suggestion to a hard requirement. Now, devices with 4-conductor 3.5mm audio jacks must recognize the impedance range and corresponding action it must produce when used on an inline controller.

MUST support the detection and mapping to the keycodes for the following 3 ranges of equivalent impedance between the microphone and ground conductors on the audio plug:

  • 70 ohm or less : KEYCODE_HEADSETHOOK
  • 210-290 Ohm : KEYCODE_VOLUME_UP
  • 360-680 Ohm : KEYCODE_VOLUME_DOWN

Inline headphone controls are a rather...

Read More
147

Android 7.0 CDD says Google may soon require OEMs to stop screwing with USB-C charging standards

Android 7.0 CDD says Google may soon require OEMs to stop screwing with USB-C charging standards

In its latest revision of the Android Compatibility Definition Document, Google has laid down some rather interesting rules not related to Android itself, but rather common device hardware. In the CDD, a new section has appeared that specifically relates to the USB Type C standard and charging - a subject that has become increasingly thorny with the proliferation of numerous proprietary fast charging standards.

While the section for now is labeled as "STRONGLY RECOMMENDED," Google is signaling clearly that it could become mandatory: "in future Android versions we might REQUIRE all type-C devices to support full interoperability with standard type-C chargers."

Read More
199

Android 6.0 Will Finally Require Manufacturers To Enable Full-Disk Encryption By Default On New Devices

Android 6.0 Will Finally Require Manufacturers To Enable Full-Disk Encryption By Default On New Devices

With every major Android release comes a new version of Google's not-so-famous Android Compatibility Definition Document. As reading goes, it is roughly between the excitement level of "doing your taxes" and "doing somebody else's taxes." Which is to say, I am well-caffeinated this morning. Anyway, the newest version of the CDD for Android 6.0 contains a change we've been on the lookout for since Lollipop was announced last year: mandatory full-disk encryption.

Since the announcement of encryption being enabled by default of the Nexus 6 and Nexus 9, Google has been on the encryption warpath (rightfully so!), and did in fact attempt to make this change in the initial Lollipop CDD back in January.

Read More
Mastodon