4 ms·

> In particular it's incredible what the Pebble firmware team was able to accomplish. They built a bespoke OS that's extremely reliable That doesn't match my e

> In particular it's incredible what the Pebble firmware team was able to accomplish. They built a bespoke OS that's extremely reliable That doesn't match my experience at all. A few months ago I was completely ready to jump on the smartwatch bandwagon so got a pebble. First of all, and somewhat unrelated, but the watch band itched and was uncomfortable and seemed to be low quality. More importantly, the Pebble randomly disconnected from my Android phone multiple times a day causing notifications not to show up. The watch would also crash occasionally, resetting to its homescreen and forgetting what I was doing. I am now a happy Moto 360 user (gen 2).

modeless 10y ago
Android Wear may have improved, but in my year or so of wearing a Moto 360 v1 I experienced such various bugs as showing the wrong time on the watch face (yes!), boot loops which were completely unrecoverable without the use of the charging dock, missing notifications due to silly Android permission issues, failure to turn the screen on for notifications, "Unfortunately, Android Wear has stopped", and plenty of bluetooth disconnects. All that among various hardware issues such as general slow performance, touchscreen unreliability that requires you to stare at the watch to confirm the receipt of each swipe, and a heart rate sensor that might as well be replaced with a random number generator. Switching to Pebble Time Round after that was a revelation.
- tokenizerrr 10y ago
  I actually have the 2nd generation Moto 360, and have not experienced any of those issues at all. The only thing I could complain about is how the watch face resets when the watch runs out of power. Not a big deal, the time is still shown correctly, and to set the correct watch face I'd just have to open the Wear app again and tap it. But still annoying. The heart rate sensor also seems consistent at least, though I have nothing to compare it with. Anyway, funny to see how these things go and how our experiences are basically opposites.
- Klathmon 10y ago
  I know it probably doesn't matter to you now, but the M360v1 is widely regarded as one of the worst android wear watches. It was built on a platform that the company making it left the business partially through it's development. It was made with a different screen type (and processor arch IIRC) than other watches, it was significantly slower than other watches, and has had some QC issues where batteries at this point are beginning to swell up and make the watch unusable (it seems to be hitting everyone, the only factor is how long it'll take). I loved my v1 like how I loved my first shitty car, and that might just be a mix of stockholm syndrome and nostalgia (not sure if that's the right word there...), but I currently have a fossil founder that my wife got me as a gift and it clearly improves on the M360v1 in just about every way. Obviously you do you, but if you ever end up wanting to take another look at the landscape, just know that your experience with android wear was probably the worse you could have had, and that things are all around much better now.
wpietri 10y ago
Which Pebble did you have? I had an original Kickstarter Pebble for years, and eventually replaced it with a Pebble Steel. It's been quite reliable for me. (I have had the "mystery disconnection" issue, but not as often as you, and have had it with other Bluetooth devices as well, so I didn't think it was Pebble-specific.)
- tokenizerrr 10y ago
  The Pebble Time Round. I should note the random disconnects never happen for regular headphones or the Moto 360
jazoom 10y ago
> > so got a peddle. Well there's your problem. That's the cheap knockoff brand.
nunez 10y ago
Android phones seem to have issues with Bluetooth LE connections especially when other non-LE Bluetooth devices are connected to it. Listening to music on my Bluetooth headphones was impossible when my Pebble Time Round was paired with my old Galaxy S7 Edge or my Galaxy S6 Edge. Audio quality would degrade significantly. Disabling LE on my Pebble worked (sort of) at the obvious expense of higher battery consumption. This doesn't seem to be the case on the iPhones I've had, though my Pebble is much less useful on iOS than it is on Android. Every smartwatch at the moment has compromises.

modeless 10y ago

Android Wear may have improved, but in my year or so of wearing a Moto 360 v1 I experienced such various bugs as showing the wrong time on the watch face (yes!), boot loops which were completely unrecoverable without the use of the charging dock, missing notifications due to silly Android permission issues, failure to turn the screen on for notifications, "Unfortunately, Android Wear has stopped", and plenty of bluetooth disconnects. All that among various hardware issues such as general slow performance, touchscreen unreliability that requires you to stare at the watch to confirm the receipt of each swipe, and a heart rate sensor that might as well be replaced with a random number generator. Switching to Pebble Time Round after that was a revelation.

tokenizerrr 10y ago
I actually have the 2nd generation Moto 360, and have not experienced any of those issues at all. The only thing I could complain about is how the watch face resets when the watch runs out of power. Not a big deal, the time is still shown correctly, and to set the correct watch face I'd just have to open the Wear app again and tap it. But still annoying. The heart rate sensor also seems consistent at least, though I have nothing to compare it with. Anyway, funny to see how these things go and how our experiences are basically opposites.
Klathmon 10y ago
I know it probably doesn't matter to you now, but the M360v1 is widely regarded as one of the worst android wear watches. It was built on a platform that the company making it left the business partially through it's development. It was made with a different screen type (and processor arch IIRC) than other watches, it was significantly slower than other watches, and has had some QC issues where batteries at this point are beginning to swell up and make the watch unusable (it seems to be hitting everyone, the only factor is how long it'll take). I loved my v1 like how I loved my first shitty car, and that might just be a mix of stockholm syndrome and nostalgia (not sure if that's the right word there...), but I currently have a fossil founder that my wife got me as a gift and it clearly improves on the M360v1 in just about every way. Obviously you do you, but if you ever end up wanting to take another look at the landscape, just know that your experience with android wear was probably the worse you could have had, and that things are all around much better now.

wpietri 10y ago

Which Pebble did you have? I had an original Kickstarter Pebble for years, and eventually replaced it with a Pebble Steel. It's been quite reliable for me. (I have had the "mystery disconnection" issue, but not as often as you, and have had it with other Bluetooth devices as well, so I didn't think it was Pebble-specific.)

tokenizerrr 10y ago
The Pebble Time Round. I should note the random disconnects never happen for regular headphones or the Moto 360

jazoom 10y ago

> > so got a peddle. Well there's your problem. That's the cheap knockoff brand.

nunez 10y ago

Android phones seem to have issues with Bluetooth LE connections especially when other non-LE Bluetooth devices are connected to it. Listening to music on my Bluetooth headphones was impossible when my Pebble Time Round was paired with my old Galaxy S7 Edge or my Galaxy S6 Edge. Audio quality would degrade significantly. Disabling LE on my Pebble worked (sort of) at the obvious expense of higher battery consumption. This doesn't seem to be the case on the iPhones I've had, though my Pebble is much less useful on iOS than it is on Android. Every smartwatch at the moment has compromises.