Hello everyone.
Is there anyone here with multiple Wear watches (preferably with different Wear versions) paired to a single phone?
I am wondering it it is just me, or anyone else too, that have such problems with watches.
I suspect that since the Wear app v. 2.0 started rolling out, having multiple watches (with different OSs) paired to my phone just started an armageddon.
Before official 2.0, I had devprev on huawei and 1.5 on zw3 and Gwatch. I had ZERO issues, ever. Then, Wear app v. 2.0 update came and it slowly began:
Wear app is going haywire almost every week. I shot few videos, hopefully I will be able to throw them on youtube tonight to showcase what is happening. But basically: I choose a watch and connect it in wear app. App shows connected. I leave for work. At work I notice I dont get notifications. I check the app, and it shows one of few possible screens: trying to connect.. or "Have a watch? set it up" (that is the most hilarious for me ) Or shows a page that would normally show your chosen watch, but it is blank. Everytime I close and open Wear app, it can show something different. It can also be showing "Connected" for a long time, but nothing works. You cant see battery stats, change watchface, nothing...
The last time, I even lost all my paired watches in BT settings. Wear app says "reconnect", ok, it reconnects, but actually isnt connected. Well, I am not sure about that to be honest.. Smart lock works Sometimes, watch says connected too (in Settings-About) The most faulty watches are those with 2.0. But it happened to 1.4 and 1.5 too.
As of right now, only zenwatch3 on 1.5 is working, but, I did a FR yesterday because it wasnt working
I am really f**king fed up with resetting every god damn watch every god damn week so that it can work for a week and then god damn break again!
I am so glad I still keep my Sony SW2 as a backup, this watch works just AWESOME! Wear watches are still nowhere near the ease of usability and reliability of SW2.
EDIT: I uploaded videos of said behaving:
NOone with issues with multiple watches??
Yes, only 1.5 watches still, but I get best results with only one watch powered on at a time, and only one manually chosen to be connected via BT in the phone app. Otherwise, there are frequent connect/disconnect notifications, mysterious quick battery drain, and often conflict between what the phone app says is connected, and what the icons on the watch say about the connection. I occasionally get the "set up your watch" on the phone app as well. I just back out of it, and it's ok.
sirrelevant said:
Yes, only 1.5 watches still, but I get best results with only one watch powered on at a time, and only one manually chosen to be connected via BT in the phone app. Otherwise, there are frequent connect/disconnect notifications, mysterious quick battery drain, and often conflict between what the phone app says is connected, and what the icons on the watch say about the connection. I occasionally get the "set up your watch" on the phone app as well. I just back out of it, and it's ok.
Click to expand...
Click to collapse
Thanks, the symptoms are the same. But it is happening to me even when I have only one watch powered on and only one watch connected to phone. But, 7 watches total are paired. I am starting to think if it is something with BT 4.0 hardware limitations.
Related
I recently purchased the LG watch R. I am using it with the Samsung Galaxy S5. Here is the watch info
Software version 4.4W.2
Build no. KNX01R
Unfortunately, "nothing" seems to work well on the watch.
I'm wondering if I have the most recent firmware but I can't confirm that mine is most recent. When I read about watch operation, the settings, etc seem to be different and offer less that what is described.
I'll describe the problems that I notice with this watch:
1) phone calls only occasionally cause a message and vibrate on the watch - random as to whether it will notify or not - about 10% of calls cause the watch to notify me.
2) texts do not appear on the watch. (I use Textra and my Textra says ver 2.3 although the web says 2.4 is most recent and has android wear support. When I upload the recent version, still says ver 2.3) This lack of text messages on watch is a major defect!! That is one convenience I really wanted. I'm not sure if it is the app itself of the android OS that sends the message. That is, I thought that perhaps anything that would show up as a notification might show up on the watch but maybe not. Maybe it is Textra. My version seems to have nothing about android wear in the its settings.
3) "Try out notifications" on the android wear app only works with "incoming phone call". All the others either do nothing or will send a notice an hour or so later. This is in spite of the app saying "notification sent" after I select a notification.
4) "Disconnected" with the 'no cloud' icon shows up about 30% of the time when I try and use Google voice operation. This is supposed to mean that the phone has not data connection. I always have a good cell and WiFi connection whenever I have received this message. It pretty much makes the watch worthless for voice commands.
5) Does not tolerate any ambient noise with voice commands as compared to talking directly to the phone. When I try and use the watch in the car, even low level road noise seems to keep the watch from ever realizing that I am talking to it as it just waits and waits and then times out. As mentioned, the same attempts directly to the phone work pretty well in the car or in the car on bluetooth device. Maybe that is just related to the microphone and that is the way it is, but it really diminishes the value of the watch.
Well, any thoughts on this?
Thanks for reading . . .
You may do better asking in the G Watch R Q&A forum. Or maybe you can ask a mod to move this thread for you.
Just an odd thought question here... is it possible to connect two different watches to the same phone at the same time?
I recently got a new Moto360 and still have my Samsung Gear Live around. I had this really weird vision of mounting the two together either side-by-side or top and bottom of my wrist to be able to display additional information.
Probably wouldn't work, but thought I'd ask the question...
Never tried it myself, but from what I read here on XDA it should be possible.
But it's not possible to pair your watch with 2 phones (not very easy at least)
I have 3 connected, working just fine.
PolishPoet said:
I have 3 connected, working just fine.
Click to expand...
Click to collapse
How does it handle things like notifications? Can you load/run different programs on them at different times?
Usually only one is connected at time, but they all get synced with the same apps. When they are all connected they all get the same notifications.
Yeah You can do this easily
fwiw the gear live makes an excellent sleeping watch with sleep as android.
that's pretty much all that one gets used for anymore, but I have it paired to my tablet. My gwatchR and moto 360 both turn on when you put them on the charger (another reason the sw3 is awesome, it'll charge while off) and SAA doesn't let you select which watch to use.
it is possible, I have three watches paired to a S6 Edge for development. In terms of developping though, you can only debug one device at a time and you have to manually assign the device to use through the Android Wear companion app.
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.
Last night I got one of those cheap Chinese smartwatches for $40 locally. (Amazon seems to have some for $20 at amzn.to/2qpSftK) Yeah I know, I know, but I work at a job that is anal about cell phones (a major gripe of mine the way places can be that way) and I need to know if my child's ride at school doesn't show up or if school lets out early due to a power outage etc, if that happens then I HAVE to pause what I'm doing and make a call or two to make pickup arrangements or else it's a legal issue of child abandonment. Such may only happen 2-3 times an entire school year, but it has happened a few times--my mother-in-law's battery was dead and she was running late, or she couldn't find her keys etc--in such cases I had to track down someone locally and get them to step-in, last minute.
Thus, I need a smartwatch which can relay calls which have come in so I can see them and it also needs to push SMS messages and let me reply to them, that way without even pulling my phone out of my pocket I will know if this has occurred (and can quickly reply to SMS) but I can otherwise keep my phone in my pocket knowing beyond any shadow of a doubt that if a call or SMS has come in, this watch WILL pick it up and I WILL be able to reply to them.
This watch I got, it is fine with relaying phone calls and it even relayed the audio from a YouTube video I was watching on the phone itself, but it WILL NOT WORK with relaying SMS. At first it did, such requires installing a "BT Notifier" on the phone (which is the best?) but even then it was hit or miss, and then it just stopped. I've done EVERYTHING in terms of different BT Notifier apps, I even scanned the "OCR Code" or whatever to point to the BT Notifier specific to that model (it appears to be a GT08 type, with the "fan" style of icons, menu/phone on the bottom left and names/text on the right, this YouTube video Ksy0pd-12BI shows one like it), I set that app up--no matter, IT WILL NOT push SMS to this smartwatch, no way/no how.
Is this a common occurrence with such smartwatches? Is this a case of that I'm going to have to just accept this model CANNOT handle SMS no matter what and get something else, vs being able to actually fix this? One model I had read good things about in an article (BIT and 2lTVoxg) called the OUMAX Bluetooth Smart Watch S6 for around $50, this model looked like a good one because it downplays "fitness" features I do not at all need and instead stresses pushing smartphone notifications and being able to replay to them, which is what I DO need. I started to get it on Amazon but then it would've required several days to get here and I need something up & running quickly but without spending $250. Maybe I should've just gotten that and waited?
Tips in general?
If anyone has any tips please do reply, I am only say this because I have an update but that doesn't mean I am not still looking for help.
I've somehow got it working just fine, no timing out of connectivity or any such thing. I had saved the downloaded BT Notifier .apk file from the app it referenced in the barcode I scanned, and I tried again but this time I disabled an app I've used on the phone for a long time--NoLED, which displays a moving dot on the LCD when notifications arrive, making it unnecessary to "wake up" the phone to see missed calls etc. I've used that app for forever, it's a long-time staple of mine, but I wondered if it was possibly interfering with this process.
I'm not sure if that is the case, but since disabling it (but also turning the watch off and letting it charge to full overnight) it's working great today. I possibly could get beyond that eventually but for now I'll take it, I mean having a smartwatch does somewhat make it less necessary anyway. The only issue now--the band, it won't attach and it's apparently a permanent part of the watch's structure, not easily swapped out. I'm not sure how I'll get around that, maybe stitching another watch band on top of it using a sewing kit?
Ultimate Fix: Watch-Specific App/Disable/Install 3rd Party
I'm somewhat disappointed in the lack of replies. Is this because this watch is now perhaps an older model, or what is the reason?
In any case, I now have the ultimate fix.
It's 3 things:
(1) Install the watch-specific app by scanning the QR code and "sideloading" the app
(2) "Force Stop" this app in Google settings but DO NOT uninstall it, leave it installed.
(3) Install the 3rd party app by "Shenznen Fan Yun Technology Co, Ltd" (green background, white circle with exclamation point) then under the "Accessibility" enable the second "BT Notifications" entry, leave the 1st one at OFF
When I got this watch, the first thing I did was download that 3rd party app, it worked some but not consistently, then it totally stopped. I then stumbled across the QR code in the watch, scanned it, installed that app, and that worked--but that app was FULL of adware, constantly bugging me to install this app or that, launching a new tab and page in my Chrome browser, and just being a total pain. I was glad the watch worked, but hated that behavior--so much I disabled the app, figuring I'd just have to re-enable it when the watch was being used.
On a hunch, eager to try again, with the watch-specific app still disabled, I downloaded the 3rd party "Shenznen Fan Yun Technology Co, Ltd" app and, just totally guessing, under "accessibility" enabled the 2nd entry (both entries have identical names so you can't tell which is which), but didn't uninstall the watch-specific app only because I figured that I would end up having to revert back to it anyway.
To my surprise, this has worked. It seems to require me turning the watch off and connecting through the watch initially, but however I get a connection and the SMS message log on the phone populates on the watch, at that point it is stable and reliable from that point on. I had it running today all-day and was receiving texts and the inbox was coming up reliably.
I hope this helps somebody. (Note: this watch is still being sold as eBay item #381686066028.)
Sorry for the crosspost - hoped I can get more eyes here...
Searched and searched so posting here and will try in general thread in case it's not tied to the watch itself.
Background: IOS user for phone, have to - developer, had Apple Watch (hated it). Got myself a Huawei Watch 2 on a deal and loved everything about it except the useless bezel and tiny screen size. Seeing as I had a great experience, I started a hunt for an LGWS. Hunt because not a single store sold one and I'm in Chicago with LOTS of stores. So online we go. There too - few resellers. Finally found one. New. Manufacture date of May 2017.
The Watch 2 worked flawlessly as functions go. Sycn'd, stayed connected, battery life of full use (all functions on - obviously no LTE), brightness at 8, raise to view on, always on display on... end of the day going to bed around 10:30 still had 50% of battery left at worst! The only issue other than cosmetic that it had was WIFI would not connect so "automatically" so to speak. So when I sent a watchmaker face, I always had to go to settings, connectivity, wifi and wait until the SSID showed connected. Then all is fine. Transferred over and enjoyed.
So the LGWS shows up. I unpair the Watch 2, connect up the LGWS and love it. The display I expected, size is great for me and off to the races. Within an hour it went from 95% to 60%. I figured - setup blues. Ignore it. Let it fully bake and see what happens. Another hour later I'm at 30%... ok onto the charger we go. Did a full charge at 6pm, by 9pm it was flat.
LGWS background: GW 2.8 loaded, Watch 2 was still running 2.0. LGWS - cellular off, raise to view on, display brightness 4, wifi connected...
But here's what I noticed: on my phone, it consistently says disconnected - tap card to connect. I tried that about 20 times, no joy. Rebooted watch and phone... no joy. Reset watch, deleted app on phone and deleted Bluetooth pairing. Re-installed Wear app, re-paired watch, left all at stock settings except shut-off cellular and OK Google listening.
That last bit is the 6-9pm going totally flat.
So. Any ideas here? Things I see - 8 vs 2 OS... obviously IOS (I get it, but why did the Huawei work so well?) and there is nothing I can do about that. Don't know if I can downgrade to 2 to see if that makes a difference... if I do, will it self-update back to 8 when it gets a chance?
I really want to keep this watch - it's exactly what I wanted (short of strap change capability). I sure hope Google doesn't give up on Wear. As a Mac/IOS dev, I can easily say this is a superior platform for the user. Truly great stuff and I want it to improve and keep improving. The iWatch bigots are really missing out!
Thanks in advance for your tips.
Cheers!
P.S. One thing I cannot do on IOS AW app is see battery usage by app. Sadly if I paired up to my old Galaxy S5 test phone, I suspect the problems may go away as it would be a first pairing of a watch to that phone plus it's not the same as the use environment.
wig said:
Sorry for the crosspost - hoped I can get more eyes here...
Searched and searched so posting here and will try in general thread in case it's not tied to the watch itself.
Background: IOS user for phone, have to - developer, had Apple Watch (hated it). Got myself a Huawei Watch 2 on a deal and loved everything about it except the useless bezel and tiny screen size. Seeing as I had a great experience, I started a hunt for an LGWS. Hunt because not a single store sold one and I'm in Chicago with LOTS of stores. So online we go. There too - few resellers. Finally found one. New. Manufacture date of May 2017.
The Watch 2 worked flawlessly as functions go. Sycn'd, stayed connected, battery life of full use (all functions on - obviously no LTE), brightness at 8, raise to view on, always on display on... end of the day going to bed around 10:30 still had 50% of battery left at worst! The only issue other than cosmetic that it had was WIFI would not connect so "automatically" so to speak. So when I sent a watchmaker face, I always had to go to settings, connectivity, wifi and wait until the SSID showed connected. Then all is fine. Transferred over and enjoyed.
So the LGWS shows up. I unpair the Watch 2, connect up the LGWS and love it. The display I expected, size is great for me and off to the races. Within an hour it went from 95% to 60%. I figured - setup blues. Ignore it. Let it fully bake and see what happens. Another hour later I'm at 30%... ok onto the charger we go. Did a full charge at 6pm, by 9pm it was flat.
LGWS background: GW 2.8 loaded, Watch 2 was still running 2.0. LGWS - cellular off, raise to view on, display brightness 4, wifi connected...
But here's what I noticed: on my phone, it consistently says disconnected - tap card to connect. I tried that about 20 times, no joy. Rebooted watch and phone... no joy. Reset watch, deleted app on phone and deleted Bluetooth pairing. Re-installed Wear app, re-paired watch, left all at stock settings except shut-off cellular and OK Google listening.
That last bit is the 6-9pm going totally flat.
So. Any ideas here? Things I see - 8 vs 2 OS... obviously IOS (I get it, but why did the Huawei work so well?) and there is nothing I can do about that. Don't know if I can downgrade to 2 to see if that makes a difference... if I do, will it self-update back to 8 when it gets a chance?
I really want to keep this watch - it's exactly what I wanted (short of strap change capability). I sure hope Google doesn't give up on Wear. As a Mac/IOS dev, I can easily say this is a superior platform for the user. Truly great stuff and I want it to improve and keep improving. The iWatch bigots are really missing out!
Thanks in advance for your tips.
Cheers!
P.S. One thing I cannot do on IOS AW app is see battery usage by app. Sadly if I paired up to my old Galaxy S5 test phone, I suspect the problems may go away as it would be a first pairing of a watch to that phone plus it's not the same as the use environment.
Click to expand...
Click to collapse
Man, as I was reading this I was like.. is this guy a mind reader.. I swear to you I have the exact same issues, and the same reason for switching from Apple watch Series 3 to Android Wear (watches should be round darnit).. I almost bought the HW2 classic and for the same reason (smaller screen, giant bezel, etc.) bought the LGWS.. I sure hope someone has some advice for both of us recent converts!
Day 2... full delete of app IOS, reboot phone. Full restore of watch. Remove from bluetooth pairings. Start over from scratch.
left it mostly stock... only OK Google and Cellular turned off (no sim in there anyhow, but to be safe since technically all phones are supposed to allow 911 calls regardless of sim status)... in that stock vanilla flavor - battery held up all day. Ended the day with about 30%. WIFI was not linked to any network, so just Bluetooth to my phone. All worked great.
Day two of grand experiment.. added WIFI set to auto on. Loaded the main app I really want, Watchmaker. five hours of use 44% of battery gone - roughly 8ish percent per hour. Not terrible, but compared to vanilla. MUCH worse. Will keep playing. The mix is in there somewhere.
The shocker is that the HW2 has a slightly smaller battery (10mAh smaller) but also a MUCH smaller face. That would account for it.
I had exactly the opposite experiences with the Huawei and LGWS. I tried out a Huawei watch 2 classic for about a week, and I had TERRIBLE battery life. Like, fully charged to DEAD in 12 hours. The LG lasted me 18 - 25+ hours (the lesser on workout days). I had all connections turned off except Bluetooth, although I turned on GPS on the LG and didn't notice any battery life change. I had assistant on, fit with everything on, always on, basically most of the apps and such.
Unfortunately, it seems like the battery life you get depends on the watch, and what you have on with AW. With LTE and WiFi on, I'm sure I would have been charging the LG once at least during the day.