Hi
This is really a warning to anyone who has an Android wear (or probably any other kind of smartwatch)
My Gear LIve and LG Watch R worked perfectly with KK and Lollipop but with MM 522 it just would not work properly at all
i worked with a dev of one of the apps and it was only the Huawei with MM that caused any problems and notifications were just not getting to the watch
MM on a samsung worked no trouble and going back to 5.1.1 on the M7 again worked perfect
I liked MM but i didnt see that much difference to being worth keeping without the watch
So if you are planning on Upgrading and have a smartwatch then you will have issues
I am now back on 5.1.1 and rooted and all works fine
I have Asus ZenWatch 2 and it works with B522 properly. Only issue I have noticed is infrequent unconnecting, about twice a week. But I just run Android Wear app and watch is connected again.
I must admit I'm surprised that's is working OK for you add the tests we got when trying to resolve the issues were all down to huawei and the non standard calls they make and the permissions issues that were occurring
The doze feature in mm seemed to be conflicting with huawei's own features and stopping a lot of the notifications getting through even though those apps were set to protected.
It also seemed to be an issue with 1 app calling another appointment and again even though that permission was granted it still gave us issues.
But I suppose in the end every setup is different and in all honesty I don't think mm was a great step up grim lollipop anyway or at least not on the huawei
Sent from my SM-N920C using XDA-Developers mobile app
I have a Samsung Gear S2 Classic and since I installed MM on my MT7-L09, Samsung Gear app will not not load, it just opens and closes in a flash.
The only way to make it work is to switch off the Bluetooth on the phone, then open the Samsung Gear App, and press connect from the app. This will switch the Bluetooth back on, connects to the watch and the app works.
Weird and very frustrating until I figured out a workaround!
Sent using Tapatalk
I have a moto 360 2nd gen and works with no issues what so ever with MM, if anything it has become more reliable so it may just be a conflict with particular manufacturers?
sthentic said:
I have a moto 360 2nd gen and works with no issues what so ever with MM, if anything it has become more reliable so it may just be a conflict with particular manufacturers?
Click to expand...
Click to collapse
I've got the first gen Moto 360. when I updated to MM my watch at didn't receive any notifications (even the test ones). I did a factory reset and everything works fine now. The only issue I have is that sometimes the Gmail app pushes a ton of notifications for the same email.
Related
I gather many people are having connection issues with their Android Wear devices.
Is this just a Note 3 issue?
Has anyone managed to get a stable connection using Lollipop?
Yes, my Note 3 with Lollipop (tested many ROMs, even the Note 4 ports) has this issue, and it's not only with Android Wear, but with several other Bluetooth LE devices. I've heard mixed explanations: some say it's something with Lollipop itself, affecting many phones (unless the manufacturer added patches to solve the issue), and Google solved it with Lollipop 5.1; others say it's something only with Samsung's Lollipop ROMs. The latter may be true, as @civato apparently solved the issue tweaking the kernel.
Some people say their phones don't have this issue, but I suspect it's because they haven't put their BTLE devices under the failing scenarios. I have a very easy test case:
1) Pair your Android Wear watch with your phone, using the Android Wear app. Make sure the watch is communicating with the phone.
2) Create a situation where your watch loses connection with your phone (e.g. walk away with the watch, put it in a Faraday cage etc.). But make sure it stays that way for some time, say 10-30 minutes (sometimes it happens as soon as it's out of range).
3) Notice that even though the watch is disconnected (the "no cloud" icon is shown), the Android Wear app on the phone will show it as "connected". Now even if you bring the watch close to the phone again, it will not reconnect automatically.
The same thing happens with other BTLE devices. Other symptoms include frequently disconnects / reconnects, even when the device is in range.
Mine has paired but refuses to connect now. I'll try Civ kernel.
Is there a Lollipop Civ kernel lol
Some problem here with my Sony Smartwatch. The new XEO Update don't fix the Bluetooth problems complete. Is any fix released to fix the Bluetooth Connection problems?
I had all sorts of problems on both the leaked Lollipop and the official Lollipop. It was driving me insane with its constant disconnections/reconnections and then just disconnecting until Bluetooth was cycled. It made the watch useless!!!
I then tried Dark Lords N4 port (v1.5). Boom! All working perfectly. No more issues at all and reconnects if i move out of range seamlessly.
Same problem, Note 3 XEO with Sony SW3. So maybe for now there is only way - root with knox 0x1 and N4 port ROM...
Had a few issues after getting Lollipop but nothing compared to the issues I got when Android Wear updated (on Friday I think it was).
My Moto 360 just wasn't wanting to connect, tried rebooting phone, then the watch, but didn't help. In the end I factory rest my watch and its been fine since.
Vince
Yep, bluetooth all over the shop...Headset and Moto 360.
I also have a lot of problems with Sony SW3 and Note 3. Not only I have inconstant BT connection, but also weird management of incoming phone calls: watch notifies phone calls that appear on the teleohone only 3 or 4 seconds later (that's a huge time).
Anaother issue: I have also tried to decline a phone call with the Smartwatch but the telephone went on ringing.
Inviato dal mio SM-N9005 utilizzando Tapatalk
My Moto360 has started not displaying a card notification when receiving a message via WhatsApp. All other notifications are vibrating and switching on the display with card, but WhatsApp it just vibrates.
I have tried uninstalling and re-installting whatsapp, tried re-syncing the apps, but WhatsApp continues not to switch the screen on ... any ideas?
You haven't blocked whatsapp from showing notifications on your 360? Its easily done by accident. You might have swiped then clicked on block this app. If you go into your wear settings, then blocked apps, check to see whatsapp isnt there.
Sent from my SM-G920F using Tapatalk
Nope, checked that .. nothing in the Blocked Apps. The phone vibrates, so it is getting the notification, but unlike all the other apps which vibrate and switch the screen on, this just vibrates. When I wake the screen, the notification is shown
Yeh, sorry, when I re-read your post I realised you couldn't have whatsapp in the blocked list if you are getting the vibration. #facepalm ?.
I had a similar issue with not receiving cards for my outlook work emails on a different device to my 360 a while back, it turned out to be an app I had used to set a custom vibration pattern for my outlook notifications. Im guessing that if you had a similar app installed you would have checked that.. also Im sure you would have tried a restart of your 360..
I think the problem is with your 360 as your phone is clearly pushing the notification to your 360 if you are getting the vibration. I know an app resync usually fixes most issues but as you've tried that what about a factory reset of your moto 360? I know its a bit drastic but I don't know what else to suggest.
Sent from my SM-G920F using Tapatalk
Tried a reset as well ... the funny (annoying part), is that the screen on notification did work for a while, and then just suddenly stopped, withouth me installing anything, so not so sure it is an issue with the Moto 360, as all other notifications pop up ..... WhatsApp is the only one that does not
Yeh thats really odd. Maybe someone else will have a suggestion that can fix it. What version of the 360 do you have? Ive got the smaller mens 2015 version. I'm at the end of my tether with it tbh for other reasons. The lag on the the device is so bad for me its virtually unusable by the end of my working day. Im gonna sell it and get the watch urbane instead.
Sent from my SM-G920F using Tapatalk
I have the 1st Gen, and to be honest I am more than happy with it, even with the outdated processor in there, don't really get that much lag with it .... and taking it off charge at 7 in the morning, and putting back on around 10pm ... still gettng about 40%+ battery left.
Surprised the 2nd gen (2015) version that you are having lags with it, have heard it was supposed to be rock solid
What other issues you having?
I get "android wear has stopped working" at least twice a day. Which means it can crash without me knowing so i miss notifications and calls throughout the day. Thats my biggest gripe at the moment. Then the lag progressively gets worse throughout the day, the only way i can fix it is to do a reboot but at its worst it can take 2-3 minutes for me to get into settings then another few minutes for each option in settings to load before i can choose restart device. I tried a factory restore last night but its already crashed 3 times today..
When i compare it to my other smart watch my 360 doesn't have that 60fps smoothness when navigating the interface. I did read that if you disable ambient then the lag isnt so bad but i like having ambient on.
I'm planning on making a YouTube video of how bad it is over weekend.
Sent from my SM-G920F using Tapatalk
I initially had the android wear stopping issue with mine, what I tried was a reset of the watch, removed all pairing with the phone, and then installed an older version of Android Wear .. think it was 1.1 (do a search on google, you will find a load of links). Then reset my watch up to the phone .... but .... tried running on Android Wear 1.1 for a few days, and it was stable. I then upgraded the Android Wear 1.4 through the Play Store (make sure to disable auto update, whilst testing, otherwise off it will go), and mine has been rock solid
albie999 said:
I initially had the android wear stopping issue with mine, what I tried was a reset of the watch, removed all pairing with the phone, and then installed an older version of Android Wear .. think it was 1.1 (do a search on google, you will find a load of links). Then reset my watch up to the phone .... but .... tried running on Android Wear 1.1 for a few days, and it was stable. I then upgraded the Android Wear 1.4 through the Play Store (make sure to disable auto update, whilst testing, otherwise off it will go), and mine has been rock solid
Click to expand...
Click to collapse
Thanks for the reply. I think I'll try out your suggestion now. Need my watch working, I've come to really rely on my watch for notifications as I can't have my phone on during working hours. It got so bad today with the lag and crashes I had to use my Razer Nabu instead of my Moto360.
Fingers crossed, I'll let you know how it goes [emoji106]
Sent from my SM-G920F using Tapatalk
The 2nd Gen really should not be that bad, as said, I have the 1st Gen and to be honest, hardly any lag, so hope this workaround works for you
albie999 said:
The 2nd Gen really should not be that bad, as said, I have the 1st Gen and to be honest, hardly any lag, so hope this workaround works for you
Click to expand...
Click to collapse
As the moto 360 2015 doesn't have a cable, its wireless charging only, how would you reflash a previous version of wear? Im kinda stumped lol
Last night I did another factory reset and i uninstalled a lot of apps that i didn't want running on my moto. Some apps seem to have a companion wear app for their mobile equivalent that automatically install.. Well ive taken a lot of crap off and i have seemed to have fixed the stability issue. Also i can use my device albeit with a small amount of lag. This i can live with for now, it seems that moto knows about "always on" causing lag on some devices. I'll hold out for an update to fix it [emoji106] [emoji3]
Sent from my SM-G920F using Tapatalk
Ah, should have said .. it is not Android Wear on the watch, but the companion android wear on the phone that I installed an older version. Don't believe you can actually change the version on the actual watch
I have ambient mode off, wifi off (dont really see the point) and tilt to wake off ... as it kept coming on when I changed gear in the car lol
install quick for wear
i know it's an old thread, but i still have the problem in android wear 2.0.
whatsapp notifications are extremely unreliable. it's like the developers do every single thing their own way.
i set my watch to show notifications until i swipe it away or down, the very few times whatsapp actually shows the notification it goes away after a few seconds.
the notifications do work, as i can manually swipe to the notifications and they're there. they just refuse to show automatically.
i'm not a heavy user, so i get few notifications of which most of them are from whatsapp. so my watch functions more like a normal watch.
Whattsapp issues wear 2.0
I too get a buzz but no card till I manually swipe up anyone managed to fix this whattsapp support are useless auto gen email each time
Anyone else having problems with bluetooth on the Moto X Pure? I'm using a Verizon SIM, on 6.0 with the February 2016 patch, fully stock (although using Nova). Having to constantly power off and back the phone to get bluetooth to work with audio in mine and my wife's car (audio cutting in and out, skipping, jumbling), and with Android Wear, constant disconnects (and this is my second android wear device).
Just wondering if this is pandemic or worth wiping and giving it a fresh load. Thanks!
Dan76 said:
Anyone else having problems with bluetooth on the Moto X Pure? I'm using a Verizon SIM, on 6.0 with the February 2016 patch, fully stock (although using Nova). Having to constantly power off and back the phone to get bluetooth to work with audio in mine and my wife's car (audio cutting in and out, skipping, jumbling), and with Android Wear, constant disconnects (and this is my second android wear device).
Just wondering if this is pandemic or worth wiping and giving it a fresh load. Thanks!
Click to expand...
Click to collapse
I sometimes have issues reconnecting to my bluetooth headset (fixed by repairing) but no issues when it is connected. And I have a moto 360 always connected that has no disconnection problems. I would go with a factory reset!
Dan76 said:
Anyone else having problems with bluetooth on the Moto X Pure? I'm using a Verizon SIM, on 6.0 with the February 2016 patch, fully stock (although using Nova). Having to constantly power off and back the phone to get bluetooth to work with audio in mine and my wife's car (audio cutting in and out, skipping, jumbling), and with Android Wear, constant disconnects (and this is my second android wear device).
Just wondering if this is pandemic or worth wiping and giving it a fresh load. Thanks!
Click to expand...
Click to collapse
I know this is several weeks old, but yes I have this issue, and have done everything imaginable to get rid of it, to no avail.
My phone pretty reliably connects to my 360 (or, currently, Pebble), but is almost useless in my car. Fine for phone calls, but audio works 1 time out of 5 at best, otherwise it just does thta jumpy skip thing.
I initially thought it was because of Android Wear -- connecting to the watch was using too much bandwidth and interfering with the ability to talk stream audio -- but a) it's ONLY aproblem in my car (and my wife's car, so it's not JUST my car), never to, like, a standalone bluetooth speaker, and b) I completely wiped my phone and didn't install Android Wear or pear with a watch at all, and the problem resurfaced. A clean wipe almost always results in reliable bluetooth for 2 or 3 days, and then it gets jumpy, which HAS to be a clue (some state or buffer being corrupted / filled?) but I haven't been able to figure out what it's clueing me into.
This thread dives into the potential Android Wear connection, but no real solution.
If anyone who HAS experienced this figures out a solution, I'd really love to hear it.
Not sure if this applies. However, I experienced this EXACT problem when streaming music over bluetooth. This problem only happened AFTER I made or received a call. Reboot is the only cure. This is with 6.0 stock with Feb update. I tried 2 phones with the same problem. Both were new out of the box. This FW is obviously defective. I'm not sure why others aren't reporting this issue. My search for a phone continues....
insanedc said:
Not sure if this applies. However, I experienced this EXACT problem when streaming music over bluetooth. This problem only happened AFTER I made or received a call. Reboot is the only cure. This is with 6.0 stock with Feb update. I tried 2 phones with the same problem. Both were new out of the box. This FW is obviously defective. I'm not sure why others aren't reporting this issue. My search for a phone continues....
Click to expand...
Click to collapse
I can usually toggle off Bluetooth then back on and it's okay, but sometimes it does require a restart. SUPER frustrating when you're driving! I'm glad I'm not the only one, I just wish we'd get more info on this and maybe someday a patch.
Hi,
I have actually been having this problem for roughly 1 year on multiple devices from lollipop to marshmallow. I have a LG G watch R and this issue started happening around the same time i started using my galaxy note 4 on lollipop. It has persisted through to a Galaxy S6 edge plus and now my S7 edge on stock and custom roms.
So the Issue is when ever i install android wear all my notifications sounds disappear after i use my watch for voice commands to make a call or send a sms. My ringtone still works but all sms and application sounds do not. I reboot my phone and sounds come back until i use my voice commands on my watch. Also if i uninstall android wear all sounds are restored and all is perfect again.
I contacted google support and they said they are going to try and help me to correct this problem with android wear, after 45 min they transferred me to LG without telling me and LG was like well what do you want us to do call Samsung.
Has anyone else experienced anything like this or maybe knows of a fix?
Anyways thanks for reading.
Since official Nougat update, i get no notificiatons on my pebble, IT runs,wenn i install both Apps Android wear, and pebble App,for half an hour, but then nothing comes to pebble, expect incoming and outgoing Calls, that Shows my pebble and i have tried all in the setting of my Phone.
Anyone Here who has similiar Problems with smartwatches?
With my Sony SmartWatch 2 sometimes Android kill the watch process :/
Sent from my HUAWEI CAN-L11 using XDA-Developers Legacy app
I've gad similiar issue on my Nova with B340 firmware, but I've unchecked Pebble app in battery optimalisation and clicked the lock button in recent screen which I suppose forces app to not being killer and so far Pebble seem to receive notifications properly.
I've had troubles too with my Pebble Steel paired on Huawei EMUI 5.1. It seems that disabling battery optimization doesn't do the trick there, although it's working on vanilla android.
I have decided to give gadgetbridge a shot. It is available via f-droid.
Since then the watch only disconnects when i'm out of range. Perfect. Hence the issue seems to be related to the pebble app I'm only using it for uploading watchfaces since then...
Gadgetbridge
To solve the problems with Emui and Pebble notifications try to install Gadgetbridge app instead of Pebble official app.