Database Users

Shift Slows down and starts vibrating.

I seem to be having a weird behaviour with my phone lately. Once in a while, it just slows down to a crawl, and intermittently vibrates (not the quick haptic vibrations, but maybe 1 to 1.5 second long vibrations). although the phone still responds, it's really slow, and i had to do a battery pull in order to get it property working again. I didn't actually have that problem, so i can't be sure, but the symptoms may match those of a bad temp root. (phone slows down, etc). I never waited long enough to see if the phone reverts to normal after a while, and i've always just pulled the battery.
it seems to be correlated to blutooth connections. it happened once when i was turning on an app (torque) ...and today, happened again while i was exiting from torque. i've been using torque for maybe 2 months now, and everything was fine.
the symptoms also doesn't happen all the time.
anyone know what the problem is?
i have a rooted shift, stock rom, and bc's 1.8 kernel running @ 368-1401 on-demand.
it's also possible that the OBD2 blutooth adapter i'm using with torque is a cheap knock off elm327.

This is a bug with Torque and Pandora. If you uninstall Pandora or turn off the car Bluetooth in the Pandora settings it will fix it.
I use both Torque paid and a cheap knockoff adapter also.
Sent from my HTC EVO SHIFT 4G using XDA App

thanks for the response. are you able to elaborate on the bug? is it the combination of torque and pandora that triggers it? i do have pandora installed, but don't really use it.

finalhit said:
thanks for the response. are you able to elaborate on the bug? is it the combination of torque and pandora that triggers it? i do have pandora installed, but don't really use it.
Click to expand...
Click to collapse
This is from the Torque forum:
There is a good chance that you have another app or bluetooth pairing that is conflicting somehow – with quite a few EVO users (though it wasn’t limited to just the EVO), the ‘Pandora’ app was the culprit, but any app that stays active monitoring bluetooth could be the culprit.
Torque’s bluetooth code is rock solid, and it works on the Tab, so you’ll have some 3rd party app somewhere which is going crazy consuming all the available CPU power.
Click to expand...
Click to collapse
If you go into Pandora and go to Preferences then at the bottom is "Bluetooth for Automotive" turn that off and it fixes the issue. I rarely use Pandora myself and was bummed that I couldn't use both apps, until I found this workaround on the Torque forum.

Interesting. I also have my phone paired to my car...could that be an issue?
Is the fact that I've only experienced this recently inspite of 2+ mos of use, consistent with that thesis?
edit: nm. i went to the torque forums, and learned myself a thing or two. yup, definitely experiencing those symptoms. the dev was saying the newest version should have some workaround, so we'll see tommorow if it takes.
i dont need a signature

[Q] random freezing/crashing when listening to audio

Ever since the Gingerbread update (and subsequent 2 patches) I’ve noticed that my DX will occasionally shut down(?) while listening to audio, it doesn’t matter if it’s streaming or a local file, podcast or music, at some random moment everything stops on my phone and the only way to get it restarted is by pulling/reinserting the battery.
So far it has happened while using Google Listen, Pocket Casts, Pandora, and Winamp
Other audio players where it hasn’t happened it is Google Music (both stock and beta), TuneinPro, SoundCloud, and Scanner Radio, though I don’t know if it hasn’t happened on these by design or it’s just that I haven’t used them as much as the ones were the freeze/crash happens.
The reason why I’m not sure if it’s a freeze or a crash is that it seems like theirs is still power, it’s just that nothing is responding, the screen is black, nothing lights up, and pressing and holding the power button does nothing so I get the impression it’s stuck in some strange loop that clears once I pull the battery.
This is my second DX this is happening to, my 1st DX was replaced by Verizon for dead pixels so this doesn't seem to be related to just a bad phone.
Is anyone else having this problem? Any suggestions of a resolution?

I have had similar issues a well, maybe happens once a week though. Mainly when I have my cassette adapter running and doing other things at the same time. Haven't gotten too bad to try repairing it yet though.
Sent from my DROIDX using XDA App

MrWall said:
Ever since the Gingerbread update (and subsequent 2 patches) I’ve noticed that my DX will occasionally shut down(?) while listening to audio, it doesn’t matter if it’s streaming or a local file, podcast or music, at some random moment everything stops on my phone and the only way to get it restarted is by pulling/reinserting the battery.
So far it has happened while using Google Listen, Pocket Casts, Pandora, and Winamp
Other audio players where it hasn’t happened it is Google Music (both stock and beta), TuneinPro, SoundCloud, and Scanner Radio, though I don’t know if it hasn’t happened on these by design or it’s just that I haven’t used them as much as the ones were the freeze/crash happens.
The reason why I’m not sure if it’s a freeze or a crash is that it seems like theirs is still power, it’s just that nothing is responding, the screen is black, nothing lights up, and pressing and holding the power button does nothing so I get the impression it’s stuck in some strange loop that clears once I pull the battery.
This is my second DX this is happening to, my 1st DX was replaced by Verizon for dead pixels so this doesn't seem to be related to just a bad phone.
Is anyone else having this problem? Any suggestions of a resolution?
Click to expand...
Click to collapse
Only time I ever had an issue like this was one of 2 things happened... either the phone overheated, or I ran the memory out... do you use a task killer? I personally like using a task killer, even though they say GB automatically shuts down background apps when needed, I always found my phone faster and more responsive using a task killer. Just a preference but TaskXP for multitasking works very well for me and it is free on the market. If you have any questions about setting it up you can pm me.
On another note... if you are using so many apps to listen to audio, I'm assuming you probably have it hooked up in your car, maybe on a dash mount... check and see how warm your phone gets, as my DX runs pretty warm too, I had to modify my mount to allow for heat dissipation and I never had a problem after that.
SGT+CM7=:-D

I don't use a task killer mostly as you stated because gb is supposed to manage it well enough but also because it doesn't suppress apps so I kept noticing things restarting right after the app killer did it's thing.
actually I mostly get around on motorcycle and I'm not a fan of using headphones while riding. for the most part, when I'm listening to my dx that's all I'm doing with it because I'm usually preoccupied with something else at the same time.
So in short, when it crashes it's when it's only playing audio
Good suggestions though since I didn't cover what I was doing when it crashes
Sent from my DROIDX using XDA App

A factory reset will cure this.

rocko73 said:
A factory reset will cure this.
Click to expand...
Click to collapse
one would think but I've tried that a few times with the first DX and it didn't resolve the situation.

rocko73 said:
A factory reset will cure this.
Click to expand...
Click to collapse
I'm sure there is more than one issue that could lead to the unexpected reboots, so I doubt there is any easy and universal panacea, much as I wish there were. Factory resets haven't worked for me on either of my 2 DX's, and I can guarantee that overheating is not relevant on mine. It comes and goes, and I thought that perhaps I had it beat, but it's still there.
I've been through a number of SBF's, cache clearing, data clearing, factory data resets, etc., app removals with no resolution. It's most prone to spontaneous reboots while running audio apps, or navigating with Google Maps.

I am not too familiar with some of the acronyms used here but I am having the same problem. The reboots started to happen after I downloaded the latet OS update code. So far Verizon has been unable to help me fix the problem,. I will be going back to Verizon today and will update you with the outcome. So far Verizon has not been all that helpful.

Verizon reloaded the OS yesterday. I will know if that cured the problem after I do an hour on the bike this morning in the gym.

Same issue
I'm having the same issue; it happens when using Google Listen or Audible, more frequently with the latter. I've noticed the problem happens most frequently when I hit the power button to turn off the screen; about a half-second after the screen turns off, the phone crashes. Sometimes it reboots itself, but most of the time I have to remove the battery and then turn it back on. This happens only when listening to audio, and it doesn't matter whether it's through the audio jack, Bluetooth or the speaker. I've formatted the SD card and done multiple hard resets, but the problem continues.

I noticed that my DroidX only seems to do it when the screen is off. As far as I can tell if you keep the screen on it should not crash.
Nobody seems to know what to do about it. Verizon knows about it but Motorola seems to be clueless. Their crappy tech support only said it was a problem with the phone, but didn't know if it was a hardware or software bug. I have has the issue across 2 Droid X devices so I figure it is more likely just Motorolas crappy software.
I have installed the latest revnumbers daily build and it hasn't conked out yet.
Verizon is of course happy to keep swapping them out under extended warranty coverage at no cost. Not that it actually helps much.

Does GasBuddy still cause a battery drain problem for nexus 6p users?

So I noticed that the newest version of GasBuddy says they fixed the battery drain problem that was affecting certain phone models. I decided to test this the last two nights. I Uninstalled GasBuddy and left my phone unplugged while I slept. I lost 2 percent from 100 percent. Then last night I tried with GasBuddy installed. I lost 20 percent and the keep awake time for android os was more than 8 hours. Is this still an issue for other people? I love GasBuddy and I hate to keep it off my phone.
Sent from my Nexus 6P using Tapatalk

same - the update didn't fix it.

it did cause mad wakes for me, uninstalled it last week, i will wait longer until i know its fixed for sure

going to mobile version of the site from chrome and adding to homescreen for the time being seems to be better option instead of installing the app. Also this seems to be fast.

I haven't seen any battery drain at all, I read somewhere that it had something to do with bluetooth, which I don't use

Well I sent then an email hopefully they can fix the 2nd time around
Sent from my Nexus 6P using Tapatalk

Yes, problem still here, had to uninstall GasBuddy. Strange that it needs bluetooth and then GB doesn't even show up in BBS as holding a wakelock.

Just Greenify it.

jejb said:
Just Greenify it.
Click to expand...
Click to collapse
Does that fix it? Have you tried it? I'm afraid that once it triggers bluetooth to keep the phone awake it may not go away even if you Greenify it. It feels like something wrong in the bluetooth stack that GB may trigger. I can't explain why GB doesn't show up in BBS or the Android battery monitor.

sirxdroid said:
Does that fix it? Have you tried it? I'm afraid that once it triggers bluetooth to keep the phone awake it may not go away even if you Greenify it. It feels like something wrong in the bluetooth stack that GB may trigger. I can't explain why GB doesn't show up in BBS or the Android battery monitor.
Click to expand...
Click to collapse
No, apparently not. After reading this thread, I started GasBuddy for the first time on my new phone and put it right on the Greenify list. Constant wakelocks anyway, and battery took a steep downhill trend for the next few hours.

jejb said:
No, apparently not. After reading this thread, I started GasBuddy for the first time on my new phone and put it right on the Greenify list. Constant wakelocks anyway, and battery took a steep downhill trend for the next few hours.
Click to expand...
Click to collapse
Yeah, this may point to a Bluetooth stack problem and not really a GasBuddy problem, though the app triggers it. I'm sure there are other apps out there that trigger the same.

Wow thank you people... I noticed in the last weeks that, as soon as I use the bluetooth and then stop using it (I disconnect my device), if I let the bluetooth activated, my phone was awake all the time. I couldn't find WHY !!
Then I saw a post from someone who said that the fix was to remove gasbuddy. I couldn't believe it, but I did the test and it's true !!
Gasbuddy is the culprit

It seems to be fixed now, in the latest release. I'm running it and have actually uninstalled Greenify. I never turn BT off. Battery life is excellent.

jejb said:
It seems to be fixed now, in the latest release. I'm running it and have actually uninstalled Greenify. I never turn BT off. Battery life is excellent.
Click to expand...
Click to collapse
I did the test this morning and it's not fixed

All I can say is that is working great for me. Stock Rom, Kylo Kernel, system level root, 6.0.1.

jejb said:
All I can say is that is working great for me. Stock Rom, Kylo Kernel, system level root, 6.0.1.
Click to expand...
Click to collapse
Stock only for me.
I just did it again :
I installed GasBuddy, I turn bluetooth ON, I connect my headphone.
I start TuneIn and start playing anything for a few seconds. Then I stop it and I disconnect my headphone and I let the bluetooth on
here is the wakelock again.

I only connect to my vehicles and laptop with BT, which I've done several times since loading GasBuddy's fixed release. No issues. Ended the day yesterday with 92%, including a couple of BT phone calls from my truck.
I'm also using NapTime, using the Aggressive mode.

jejb said:
I only connect to my vehicles and laptop with BT, which I've done several times since loading GasBuddy's fixed release. No issues. Ended the day yesterday with 92%, including a couple of BT phone calls from my truck.
I'm also using NapTime, using the Aggressive mode.
Click to expand...
Click to collapse
Are you stock rooted with the stock kernel as well?

geoff5093 said:
Are you stock rooted with the stock kernel as well?
Click to expand...
Click to collapse
See post #15

Nougat just ruined bluetooth on this phone

So I guess I was spoiled with last version of android because for me with that last version, I could reasonably easily install android auto, have it start playing when I got into my truck, have it stop as soon as bluetooth disconnected etc. Predictable in other words.
Since the upgrade... bluetooth is... just bad. Selects one of many music apps at random apparently to open when I connect to bluetooth... And apparently likes to just sit and lag like 5 seconds before it realizes its no longer connected... so I have music blasting out of my phone when I get out of the car.
Removing all pairing information and resetting wireless connection info and re-pairing didnt resolve anything at all for me.
Any one else experiencing the same thing?

I had wacky issues with multiple 3rd party music apps (rocket player, amp) and found that only Samsung Music and Play Music were at all reliable when interoperating with my car via BT or my various BT headphones.
Same behavior KK/MM, haven't bothered trying the 3rd party stuff since getting N.
Currently I only have Play Music on my phone and it works fine in all use-cases.
So, I don't so much think it's the BT so much as it's the other apps and how well they do or do not integrate and behave with the system.
I"d advise paring your system down to one music player and testing and working up from there. PITA, to be sure.

I use power amp with no issues

I typically use Android auto and Pandora... But it's definitely considerably less predictable. I manually installed qa6 prior to being officially available. Is it possible that this could be the reasoning?
Earlier today turning off the car the music playing didn't ever stop when what I've noticed is I get like 5-10 seconds after car shuts off.

There have been issues with Bluetooth on some devices after the update. Sometimes a factory reset fixes the issue, but not always.

My Bluetooth has always been stupid when it comes to Android in general, I'll be last listening to Spotify and when I hop in my car my phone will start playing the last podcast I was listening too instead (even though that app was killed and not running anymore) or it will start up Play Music which I haven't used for days instead, sometimes it will connect right back to what I was last using but most of the time, even before this update, it would randomly pick some other app that streams over Bluetooth instead. Needless to say, I never had this happen with my iPhone when I had it, no idea why Android is so wonky when it comes to this stuff

I have no issues with BT and connect to about a half-dozen devices regularly including AA in my car. If you use Smart Switch or other method of restoring apps used by AA they won't work. You have to uninstall them and reinstall them manually. That isn't Nougat related it was the same way with Marshmallow. I learned the hard way when I went through two Note7's to end up with a S7 Edge.

ronnyek said:
I typically use Android auto and Pandora... But it's definitely considerably less predictable. I manually installed qa6 prior to being officially available. Is it possible that this could be the reasoning?
Earlier today turning off the car the music playing didn't ever stop when what I've noticed is I get like 5-10 seconds after car shuts off.
Click to expand...
Click to collapse
I use Spotify with Adroid Auto with no issues since getting N. I have connected to two BT 4.0 devices and a 4.1. As another poster mentioned, it could be the apps you are using, but I think it has more to do with qa6. If you manually updated, there is always a risk. I love hacking my phone, but there is always an accepted risk. Best bet is probably a factory reset and/or rolling back your update (if possible) to allow the automatic update take effect.

When I am talking in my truck via Blue Tooth since the update it will randomly drop the connection. It seems to work fine with my Earbud (PLT_E50) though.

the main issue I've seen... music playing does not stop when my head unit turns off anymore. Thinking the early released OTA nougat qa6 was what I was running and that may somehow be different than what att actually sent out, I fully wiped, reverted back to pk1, let it do the att upgrade to qa6.
This morning, I noticed the exact same thing... its pretty good about start playing when I get in the truck and it connects to bluetooth etc... it just doesnt turn off for a LONG time after blue tooth device is turned off.

Lemfo Y3 issues

Notifications sometimes don't work, especially for calls. It stays connected fine with Nougat, though I can't figure out how to track sleep. The specs state that it can.
Until today. I added the watch as one of my "trusted devices" so the phone stays unlocked when they're in range of each other, and it disconnected. Now when I try to reconnect in WiiWear, it crashes and disconnects again. I've forgotten the watch, removed it from "trusted devices," wiped cache, reinstalled WiiWear, etc, and it still crashes. HELP!

The Bluetooth stack in all these MTK 6580 watches are very unreliable
Sent from my HTC 2PS6200 using Tapatalk

pablo11 said:
The Bluetooth stack in all these MTK 6580 watches are very unreliable
Click to expand...
Click to collapse
Seems that way. Hopefully an update comes soon that helps.

I've had it. Constantly disconnecting, having to reset the watch to get it to connect again, and crashing assistant "SinWear" app. Pissing me off. I'm returning this.

GuyInDogSuit said:
I've had it. Constantly disconnecting, having to reset the watch to get it to connect again, and crashing assistant "SinWear" app. Pissing me off. I'm returning this.
Click to expand...
Click to collapse
Sorry to hear about your issues. I'm considering buying one myself. Do you think this is mostly a problem with the watch (i.e. hardware) or something with the connection between the phone app and the watch software?
Also, if you don't mind taking a minute to tell me, what did you think of the build quality and general usability of the Y3?

Techngro said:
Sorry to hear about your issues. I'm considering buying one myself. Do you think this is mostly a problem with the watch (i.e. hardware) or something with the connection between the phone app and the watch software?
Also, if you don't mind taking a minute to tell me, what did you think of the build quality and general usability of the Y3?
Click to expand...
Click to collapse
I have the Y3, and the connection problem is very real. Until yesterday, I could not maintain any reliable connection between the watch and my phone. The Bluetooth would continually connect and disconnect, and the m2d manager and receiver were very quickly being killed after the the screen turned off. Then I stumbled on the cause. I was checking the app notification log using Google gesture and noticed an app called Battery Master posting silent notifications. This app does not show in the app list and is not accessible in any other settings screen. However, when I tapped on one of the notifications in the notification log, it took me to the info screen for Battery Master and gave me the option to disable the app, which I did. Bluetooth, m2d, and notifications have worked perfectly ever since. So far I have not noticed any significant difference in battery drain but it will probably take a few days to know for sure.
Build quality of the watch is excellent. I love the watch now that the connection issue is fixed. The display is awesome since there is no black band around the outside and no flat tire. I've installed the ClockSkin launcher which provides a better looking interface and allows installation of all the excellent LEM5 watch faces available from the G+ user group. Battery life for me (after disabling Battery Master) seems to be about 10 hours.

GuyInDogSuit said:
I've had it. Constantly disconnecting, having to reset the watch to get it to connect again, and crashing assistant "SinWear" app. Pissing me off. I'm returning this.
Click to expand...
Click to collapse
mattbren said:
I have the Y3, and the connection problem is very real. Until yesterday, I could not maintain any reliable connection between the watch and my phone. The Bluetooth would continually connect and disconnect, and the m2d manager and receiver were very quickly being killed after the the screen turned off. Then I stumbled on the cause. I was checking the app notification log using Google gesture and noticed an app called Battery Master posting silent notifications. This app does not show in the app list and is not accessible in any other settings screen. However, when I tapped on one of the notifications in the notification log, it took me to the info screen for Battery Master and gave me the option to disable the app, which I did. Bluetooth, m2d, and notifications have worked perfectly ever since. So far I have not noticed any significant difference in battery drain but it will probably take a few days to know for sure.
Build quality of the watch is excellent. I love the watch now that the connection issue is fixed. The display is awesome since there is no black band around the outside and no flat tire. I've installed the ClockSkin launcher which provides a better looking interface and allows installation of all the excellent LEM5 watch faces available from the G+ user group. Battery life for me (after disabling Battery Master) seems to be about 10 hours.
Click to expand...
Click to collapse
That's good to hear. You should definitely make a quick Youtube video about the fix, or even just a thread here on XDA. I bet a lot of people never discovered what was the cause of their connection issues and just returned the watch. One question though, does that fix persist through a reboot, or do you have to disable the Battery Master app each time you start the watch?
Please update us if your connection issues continue to be resolved with that fix (or not).

Techngro said:
Sorry to hear about your issues. I'm considering buying one myself. Do you think this is mostly a problem with the watch (i.e. hardware) or something with the connection between the phone app and the watch software?
Click to expand...
Click to collapse
Definitely the phone app. The phone app crashes when trying to connect.
Techngro said:
Also, if you don't mind taking a minute to tell me, what did you think of the build quality and general usability of the Y3?
Click to expand...
Click to collapse
It's actually really good. It's a solid watch, and it has a lot of good uses. I wish it did work with apps like Google Fit and Sleep as Android though, but it's not really necessary as those work fine with just the phone as is. It is supposedly IP67-rated water proof, but I don't recommend testing that by completely submerging it, or showering with it on. It likely is OK with washing hands, though. Or sweat. Never had a problem even with my original Moto 360 in that regard.

One thing these will never do is make or receive calls over Bluetooth. None of them will.
They are a stand alone watch phone. Never made to call through Bluetooth.
Cheers
Sent from my HTC 2PS6200 using Tapatalk

Techngro said:
That's good to hear. You should definitely make a quick Youtube video about the fix, or even just a thread here on XDA. I bet a lot of people never discovered what was the cause of their connection issues and just returned the watch. One question though, does that fix persist through a reboot, or do you have to disable the Battery Master app each time you start the watch?
Please update us if your connection issues continue to be resolved with that fix (or not).
Click to expand...
Click to collapse
The fix is still working, and yes, it does survive a reboot.

mattbren said:
I have the Y3, and the connection problem is very real. Until yesterday, I could not maintain any reliable connection between the watch and my phone. The Bluetooth would continually connect and disconnect, and the m2d manager and receiver were very quickly being killed after the the screen turned off. Then I stumbled on the cause. I was checking the app notification log using Google gesture and noticed an app called Battery Master posting silent notifications. This app does not show in the app list and is not accessible in any other settings screen. However, when I tapped on one of the notifications in the notification log, it took me to the info screen for Battery Master and gave me the option to disable the app, which I did. Bluetooth, m2d, and notifications have worked perfectly ever since. So far I have not noticed any significant difference in battery drain but it will probably take a few days to know for sure.
Build quality of the watch is excellent. I love the watch now that the connection issue is fixed. The display is awesome since there is no black band around the outside and no flat tire. I've installed the ClockSkin launcher which provides a better looking interface and allows installation of all the excellent LEM5 watch faces available from the G+ user group. Battery life for me (after disabling Battery Master) seems to be about 10 hours.
Click to expand...
Click to collapse
How exactly did you access those settings? What if you walked too far from the phone, does it reconnect?

GuyInDogSuit said:
How exactly did you access those settings? What if you walked too far from the phone, does it reconnect?
Click to expand...
Click to collapse
Download the app Google Gesture Search from the play store onto your watch. This will allow you to easily search for settings options that are not accessible through the watch's launcher. Search for Notification Log. In the log, tap on any line that says Battery Master. This will take you to the app info page for Battery Master. You can't uninstall the app but you can disable it. This will allow Bluetooth to stay connected and will allow the m2d manager and receiver to stay running.
Using m2d, the phone will reconnect with the watch automatically if you come back into Bluetooth range.
Be aware that once you disable Battery Master, there is no way to re-enable it because it won't show up in the logs. I'm guessing that a firmware update or a factory reset would re-enable it.

mattbren said:
Download the app Google Gesture Search from the play store onto your watch. This will allow you to easily search for settings options that are not accessible through the watch's launcher. Search for Notification Log. In the log, tap on any line that says Battery Master. This will take you to the app info page for Battery Master. You can't uninstall the app but you can disable it. This will allow Bluetooth to stay connected and will allow the m2d manager and receiver to stay running.
Using m2d, the phone will reconnect with the watch automatically if you come back into Bluetooth range.
Be aware that once you disable Battery Master, there is no way to re-enable it because it won't show up in the logs. I'm guessing that a firmware update or a factory reset would re-enable it.
Click to expand...
Click to collapse
Sweet!

GuyInDogSuit said:
Definitely the phone app. The phone app crashes when trying to connect.
It's actually really good. It's a solid watch, and it has a lot of good uses. I wish it did work with apps like Google Fit and Sleep as Android though, but it's not really necessary as those work fine with just the phone as is. It is supposedly IP67-rated water proof, but I don't recommend testing that by completely submerging it, or showering with it on. It likely is OK with washing hands, though. Or sweat. Never had a problem even with my original Moto 360 in that regard.
Click to expand...
Click to collapse
The IP67 rating is a misprint, on the official LEMFO store at AliExpress, the listing for the Y3 states that it is IP65 rated. I took a screenshot because I know a lot of people were confused about that.

pablo11 said:
One thing these will never do is make or receive calls over Bluetooth. None of them will.
They are a stand alone watch phone. Never made to call through Bluetooth.
Cheers
Sent from my HTC 2PS6200 using Tapatalk
Click to expand...
Click to collapse
That's really too bad. I really would like a watch like my Gear S (which also allows you to use a SIM card) that can simply pass the call through the watch. For driving it is great to keep your hands on the wheel. I wonder why the feature isn't on more watches. It seems like a no-brainer.

Yeah, these are literally a phone watch. A miniature android phone on your wrist....
Sent from my HTC 2PS6200 using Tapatalk

mattbren said:
Download the app Google Gesture Search from the play store onto your watch. This will allow you to easily search for settings options that are not accessible through the watch's launcher. Search for Notification Log. In the log, tap on any line that says Battery Master. This will take you to the app info page for Battery Master. You can't uninstall the app but you can disable it. This will allow Bluetooth to stay connected and will allow the m2d manager and receiver to stay running.
Using m2d, the phone will reconnect with the watch automatically if you come back into Bluetooth range.
Be aware that once you disable Battery Master, there is no way to re-enable it because it won't show up in the logs. I'm guessing that a firmware update or a factory reset would re-enable it.
Click to expand...
Click to collapse
Are you sure it's called "Google Gesture Search"? I can't seem to find it.

pablo11 said:
https://play.google.com/store/apps/details?id=com.google.android.apps.gesturesearch&hl=en Settings search is also good
Click to expand...
Click to collapse
Not available in my country. I got it from APKMirror though.

I still have issues connecting after doing this. It worked fine and stayed connected the first time but once I rebooted both devices, wiiwear now force closes. I'm on Nexus 6p dirty unicorns 7.1 and the firmware on the watch is from Dec 16 any ideas
Sent from this Nexus "Pure" 6P!!!

Ultraman666 said:
I still have issues connecting after doing this. It worked fine and stayed connected the first time but once I rebooted both devices, wiiwear now force closes. I'm on Nexus 6p dirty unicorns 7.1 and the firmware on the watch is from Dec 16 any ideas
Sent from this Nexus "Pure" 6P!!!
Click to expand...
Click to collapse
Neither Wiiwear or Sinwear will run on my Nexus 5x. I think it's an incompatibility with Android 7+. You can sync notifications to the Y3 using m2d once you fix the Bluetooth problem by disabling Battery Master.