Optimization Tip for Android Wear in Android M

If you are using Android Wear in Android M, check your optimizations

You may not be aware that Android M thinks your Android Wear app needs to take a nap every once in a while.

It should be no surprise to anyone out there that the Android M Developer Preview is not 100% ready for public consumption even it’s not stable to use. A few folks — including our TWIT friend Jason Howell — noticed Android Wear didn’t always behave as expected when connected to the preview, there are many things which make it behave differently from what expected.

Android M’s new App standby functionality and the Wear app not being ready for M than anything else. It also means there’s an easy way to stop this from being in a problem.

android-m-wears

There is a App standby function in Android M sets apps up for auto-shutdown when the system feels there’s no need for the app to continue running in the background and no one is using in any way.

Maximum of us thinks Android Wear is specifically designed to constantly run in the background so you can sync with your phone, this is when these problems rise.


There is a very simple way to To fix this, hop into the Battery Optimizations section of the battery manager in Android M and set the Android Wear app to ignore optimizations. This will keep the watch connected to your phone, and let you get back to totally not using a Developer Preview as your daily driver.


Thanks for visiting the blog