Recent content by Moguledyouth

I am looking for those icons as well, could you post them to this thread please.

If you are asking me, notifications are enabled in the Voice app and I even have Lightflow set up with a custom led notification.

That's strange, I'm on Sprint and the *28xxxxxxxxxx, worked for me perfectly. I may try busy *74 number, but as for me all my voicemails are being forwarded to Google Voice and the Google Voice app is notifying me accordingly.

Also make sure you are using the latest adb and fastboot files from Google.

Read up on Android Wear 2.0, that's one of the main features. You install the apps you want directly to the watch from the Play Store app on the watch. They even list what apps you have installed on the phone that have watch counterparts for easy installation.

I'm on a Nexus 6 and everything went smooth, one thing you might want to do is make sure you are using the latest versions of ADB and Fastboot. I initially had problems flashing etc. because I had an older version of Fastboot etc. Below is a link to just the core sdk files (around 4mb). The link...

You could always head over to the WatchMaker G+ community and ask someone if they could recreate it from the included photo...

Just make sure to update all apps (both Google app and Android Wear app had updates) on DP4 once you have it set up, after that it was smooth sailing for me.

Day after update... after I made sure that all the app updates were done on DP4 (both android wear and google app needed updating) as well as I believe a new Google (beta) app update last night, I have not had the problem of my bluetooth turning off after a reboot. I am still on the early Jan...

If you could add OrderedChaos too, it sounds amazing!

Work Around As a work around and since I already have and use Tasker, I have it set up that Bluetooth is always on, if it is disabled it will automatically re-enable it. **Update** so I decided to install the AW 2.0 DP4 on my Huawei watch, and just had my bluetooth disable itself on my phone...

What I'm hoping is that the glitch may correct itself once AW 2.0 is released for our watches if it is indeed the culprit. I feel like it might be a some kind of BT communications glitch (memory leak?) that causes BT to choke and kill itself. I know for a fact that I have only been experiencing...

Just a thought, but I didn't seem to have this issue with Bluetooth until recently, like around the same time as the Android Wear app was updated in preparation for AW 2.0... Just curious if that is a commonality among users with this issue?

I know right, I'm going to check and see if there is a new radio/bootloader included with the Feb. security updates as I do update both of those when they are updated. The only other thing is that I have multiple bluetooth devices including (2) "always on" type devices a Huawei Watch and a...

I've been having this issue as well, I am running the PN version before the current 1/21/17 version. I'm just waiting for the Feb. updates to do a complete fresh install, however these issues just started popping up for me within the last couple weeks and I've been on this rom since it was released.