This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Venu 2 battery 60% to 1%, and overheating

Hi all.  I've been using my Venu 2 for about 3 weeks.  So far I generally only need to charge it while showering each day, so 1 or 2 showers, total time not wearing the watch is probably less than 15-30 minutes a day.  Pretty incredible.  I run frequently enough that I'm in GPS mode between 1-2 hours every 3-6 days a week.  Pulse Ox tracking is On.  I've been playing around with sync'ing a few songs from Spotify, so far, mixed results with the user experience but no issues on battery.  

Today however, I tried getting the music controls to download a 2.5 hour podcast through Spotify.  I've noticed that larger files have a seriously poor time sync'ing to the Venu 2, if they ever do.  Usually they fail.  

At lunch I was sitting there trying to get this 2.5 hour episode to sync - it seemed to get started.  I allowed the watch to do its thing while I ate.  A few minutes later, my watch started buzzing at me that the watch was at 1% battery, asking if I want the watch to go to power saver mode.  While playing around with Spotify sync, I had noticed the battery was dropping a bit more than usual, like from 64% to 60% in a shorter time than usual, but figured the higher data transfer rate perhaps.  

And then down to 1%.  I took the watch off, and it was VERY warm.  I work in IT, and am very familiar with scenarios where they get super warm, or hot even, and how that affects the immediate battery charge level, plus the longevity of the battery.  So I'm not liking this situation and wonder if in a few months I'll have a dead watch on my hands (almost literally, nyuk nyuk).  

It's currently charging at what I imagine is a normal rate, up to 67% so far in about 45 minutes so far.  Doesn't feel as warm.  

AFter it's at 100% I will re-do this Spotify stuff and see what behaviour I get.  Anyone else have similar?  .  

side notes:  the Spotify experience could use some real improvement.  It makes so much more sense to select and configure things in Garmin Connect on the phone app, or website, and have that push things to the watch, than try to work with the watch interface, which itself isn't too bad for this, except that it just does a terrible job of syncing stuff reliably.  Like a real data management section in Connect would make so much more sense than this very ambiguous, no-idea-what's-happening interface situation currently.  

{edited to fix up some times where I said "phone" instead of "watch" - habits!}

Top Replies

All Replies

  • Looks like probably a faulty watch.  Charged to 100% is under an hour, worked ok sitting at my desk, then a few minutes later _buzz buzz), and battery was at 1% again.  To ensure it wasn't a Spotify sync causing the issue, I had deleted all Spotify items from the watch.  

  • Update again:  read several forum threads here about the latest update, 4.67.  Overall there are no clear answers yet, on anything really, but in general I gather that this latest update has thrown the balance of things off big time.  Anyway, via Garmin Express on the PC here, I got rid of 4 third-party apps/glances.  I was not actually using any of them.  In any case, now that there is no Spotify music stored (thus no attempts to sync), and no 3rd party stuff, the watch is more or less back to default.  Let's see what happens.  If the watch today behaves like yesterday, while it's at 99% right now, it should drop to nearly zero in the span of a few minutes, at some random point.  

  • Have you done a forced restart yet by holding down the top button. A few of us have to do that after update 4.67 which caused problems with battery usage. Mine went from charging every 7 or 8 days (with 4 or 5 hours of GPS activity) to needing charged every 3 days - if that. Doing the forced restart solved my problem and it’s back to charging every 7 or 8 days. 

  • Hello .  Regarding your mention of the watch getting warm/hot, we take these types of complaints very seriously, but cannot address these over the forums as we will require some personal information we would not request publicly.

    Please reach out to your local Garmin support team by going to www.support.garmin.com, scrolling down to the bottom of your screen and selecting your location (see the red arrow in the screenshot below).

    Your local Garmin support team will work directly with you to resolve this.

  • I didn't know about the force restart option so I'll keep that in mind.  Since my last post, my watch has been behaving completely normally again.  However, I have not (yet) attempted anything that seemed to trigger that last issue, such as sync Spotify content.  So I'll be trying that out soon.  I wanted to establish a reliable baseline of reliable function again.  So I'll probably try the Spotify sync again this weekend and put my results back here.  

  • Hi @Garmin-kevin  I'm still in the testing phase for this problem so unless you suggest otherwise, I was thinking to hold off on contacting support until I can reproducer the problem again.  Provided the warranty on this watch hasn't expired, I have no idea what the warranty duration is.  I only bought it a month ago via the Garmin Amazon store.  

    So far, the watch has been good again for the past week, since my last post above mentioning the issue.  But I haven't done anything new with it, just using it with Pulse Ox on 24/7, standard stuff otherwise, running 1-2 hours for a few days at a time with a break in between, etc.  The watch hasn't had any issues.  The last time I had problems was either just coincidence, or happened to be due to using Spotify sync'ing.  And with that, it was only when I tired to sync a 2 hour podcast, but had not been an issue when sync'ing some smaller songs the day before.  So who knows, maybe the watch can't handle larger file sizes and goes into overdrive, attempting to sync so rapidly (fail, retry, fail, retry) that it overheats the device because the activity isn't regulated - something the coders can address perhaps..  So I'll try to reproduce this situation soon, probably this weekend.  

    But again just to be clear for anyone else reading, though it seems there are battery-related issues with the 4.67 update, my issue was that my battery went from about 60% down to 1% in a matter of seconds (and it only got to 60% due to the excessive try/fail with the Spotify sync - otherwise the watch has never been below around 74% since I charge it for about 20 minutes each day and wear it the other ~23h:30m).  

    We'll see!  

  • Haven't tried the Spotify sync yet, will be doing that soon.  Missed my chance last weekend.  

  • Still haven't tested, but the device has since updated to 5.xx firmware.  It, so far, has had zero issues, so I'll give that sync thing a try soon and we'll see.