th a fresh Android treat comes new tools new rules for those that make Android-powered phones, tablets, other gadgets. 

That’s because with each version of Android, updates its Compatibility Definition document. This tells hardware partners (OEMs) what they can can’t do in order to make an Android device that earns the blessing of .

thout passing the requirements getting the go from the Compatibility Test Site, the device won’t get ay services. That means no apps or ay Store access for you.

There are quite a number of new hardware capabilities requirements with Marshmallow. In all, it shows that is trying to push ahead with an effort it made in llipop to provide a framework for more attractive devices, while dangling enough carrots to keep OEMs in line. ft to their own devices, too many Android manufacturers stray far from the vision of building a phone that taps into the power of Android. Or, they provide similar capabilities while trying to keep the technology proprietary to their own phones, making it hard for developers to support all devices throughout the Android ecosystem.

Here’s a brief rundown of the most important new rules for Android manufacturers, what it might mean for your next Android device.

Doze Mode for most, but not all

is requiring that OEMs put Doze Mode into place let you know which apps are exempted from it. In stock Marshmallow you’ll only see ay Services Android Device Manager as opted out. However, expect Samsung, , others to exclude some of their preinstalled apps from this feature. The upside for you is that you should get significantly better battery life with your next phone. However, don’t be surprised if manufacturers mess with this by opting out carrier bloatware.

Full-disc encryption is a needed security feature

This one deserves a big, “finally.” Full-disk encryption secure boot are now matory for Marshmallow devices. This was the plan with llipop, but it was pushed aside due to performance issues. This brings a much-needed level of security to your device, especially since you’re likely to sell it off in a year get a new one. en you wipe it, your old data is encrypted non-recoverable.

Devices that flag themselves as low-memory (less than 512MB) don’t have a secure lock screen can still opt out of this. Those requirements preclude basically all modern phones tablets—it seems like an out for those making other Android-based devices (smart network players, robots, internet-of-things devices, so on).

Fingerprint sensor requirements

This is an area where is playing much-needed catch-up to Apple’s Touch ID. There’s a long list of requirements for those OEMs that want to include a fingerprint sensor. The devices must limit a user to five attempts limit third-party access to merely authenticating prints, not identifying which particular prints are used. ile Samsung others have fingerprint sensors in its devices for a couple of generations, this enables the rest of Android OEMs to include this feature without developing their own custom software. And it builds a stard interface that app developers can use to authenticate you using your fingerprint. For example, a password manager might auto-fill forms after you authenticate with your fingerprint.

You can check out the lengthy list of requirements from here.

More professional audio

Android has struggled in the past with audio latency problems, ceding a huge advantage to Apple. attempts to fix this with more requirements for how devices perform when paired with speakers or other hardware, how quickly the operating system audio software stack respond to playback sounds from inputs. has added a professional audio package manager, which dictates the details for audio latency support of B audio connections. Devices that meet strict requirements can make themselves available for As that should bring far better audio performance to certain apps.

at it all means

If you follow Android you know it’s incredibly fragmented that the developer user experience varies sharply. is trying to repair this without turning into an autocrat banishing others from making Android devices. th llipop arguably tightened the screws, but perhaps not nearly enough.

If you want to find out all the specifics underst the complex details surrounding hardware requirements, then check out the Android Compatibility Definition document. That will give you a full picture of what you can expect with Marshmallow, which should come with the next wave of Android devices.