Venu 2/2s Battery Drain After sw 9.17

I am already doing that currently with my watch now after this update 

Hey Kevin, 

I tried all of that and still experiencing the same drain. The battery makes it roughly 30 hours before needing to be fully charged again. Last night when I went to bed (11pm) the battery was at 49 and this morning when waking up (6am) the battery was at 14%. I would say that’s pretty unacceptable considering I was asleep during that time period in which the only function running on my watch is HR and Spo2 (never had an issue before 9.17 update running that constantly) Yes you have permission to email me, yes you can view my Garmon account, I live in the United Staes. 

My only question is will there be and update to resolve this issue that everyone is seeing to have with 9.17 firmware update? It seems that update is causing more issues for people rather than updating the ability to utilize the watch itself. It seems every watch face I have tried to install to use to get the same functionally of the SHN EDO face comes with the same drain. Before the update of 9.17 I would get about 7-9 days on a single charge with the same settings I am running currently post 9.17 update. Now I get 30 hours of battery life off one charge. Just want to know what in the new update is causing this and what the solution is going to be seeing that the above ones provided are not creating one. 

hi Garmin-Kevin,  

 until the independent developer is able to update their app/watch face to function correctly (without causing a battery drain) with the new firmware version on your watch.

As a dev, I'm very curious about that, What we have to do?! I mean if no battery drain on app before a Garmin update that means the code was correct, and should not be wrong?

Garmin-Kevin I'm sorry, but there is no way a CIQ WF can cause that kind of battery drain.  If it is, it's still a problem with the fw, not with the CIQ WF.  As a CIQ developer, there is absolutely nothing I could do to cause that kind of drain.

I don't know... I write CIQ code too but never a WF... but I'm guessing there are examples of stupid coding that continuously run logic every second that could drain the battery over a 30-hour period (over 100,000 iterations). It would have to be a really poor design and incompetent coding. But Garmin is just trying to eliminate unknowns and things out of their control. If removing the 3rd party WF solves the issue... then bingo... that WF caused it. Likely that WON'T solve the issue and then it is on Garmin.

Hey all. I did not mean to stir up any drama when referencing the watch face I am currently using. I’ve tried multiple ones that share the same data that I usually have on the face and revived the same results across the board. Last night when I went to bed at 11pm the watch was at 45% and then when waking up at 6:40 it was at 18%. The only thing that I have constantly running is the HR tracking, but have never experienced battery drain like that up until this last weekend. I’m losing roughly 1/3 of my battery every 8 or so hours. I’ve tried all of the things garmin has suggested but still getting the same results of significant battery loss no matter the watch face used. Again, didn’t mean to cause any issue between dev and garmin from referencing the face used. Just trying to find a solution to this so It can go back to lasting me 7-9 days with all of the things I would run on my watch before my watch was updated to the new FW. If not I’ll have to return. Have only had for 6 months as well. 

Connect IQ put limits on how long WF's can take to redraw the screen, and will crash the WF if you take too long.  It also prevents you from doing continuous every  second updates.  If your WF is causing that kind of drain, it means the system isn't limiting the WF like it should.

You also can't do a whole bunch of operations like web requests in the main WF code.  You need to use background processes that can only run at most every 5 minutes.

Connect IQ has been designed to limit the battery drain.

Perhaps it is a hardware issue and has nothing to do with the firmware updates. 

I started experiencing this drain issue last weekend when I connected my watch to my computer to update. It was fully charged Saturday and then I got a notification Sunday that my batter was at 10% around 6pm. Before the update the watch would last me about 7-9 days fully running HR and Spo2 all day with no issue 

Oh nice!! Then yeah, no way a CIQ WF can drain like that. thx!