Massive battery drain since Firmware 25.00

So in the end I made a few more attempts and reduced sw 23.xx to 20.50, 20.00, 19.20,16.70,15.20 up to version 13.30. Still the consumption on the first day was 0.3%per hour which was great, but from the second day it always hung to 0.4% and more.Interestingly, it dropped 100% to 98% each time and then it stabilized at 0.3% on the first day, but from the second day the consumption picked up again! Finally, I managed to get to consumption in the range of 0.1% for 1h to 0.3% for 1h in version 24.00. I have been testing for the fourth day and it still holds these values . And it was interesting that this time it did not drop from 100% to 98% as fast as before .

Maybe it helped that I also read somewhere that it is important to do a soft restart after updating the sw when the battery is charged to 100%! I do not know if I have not done those soft restarts before when the battery is not recharged to 100%. It was mentioned to charge for sure to 100% and then do a soft restart! And also because of the altimeter I preferred to leave the sensor hub at 8.00 , so I do not know if it can also be the reason that the sw 24.00 may be well understood with this version of the sensor hub . GPS and everything works well so far

25.10 seems to have addressed the issue for me. 

Have you had problems with the battery before? On what sw ?

Before v25.0 it was fine. 

After v25.0, noticeable battery drain. 

After v25.10, it seems fine again

It's definitely these 3rd party watch faces, esp those that have the 'run in the background' permission. I've recreated this multiple times.

No matter how simple the watch face, as soon as I delete them and do a soft reset (push light button until shutdown and then turn ON after 5 sec) the batter consumption goes as expected.
The native WF are really OK, even if they display the seconds or heart rate etc.

Please, really, how difficult is it to add the stress level and body battery to native watch faces so that others won't have to rely on these 3rd party faces. It's not that they drain battery, they also cause the watch to lag.

It's that simple a solution for those who use the other wf only because of the data (not design necessarily).

Not always iWerry. I am using a 3rd party WF with the software version before 25.00 and never noticed any battery draining problem. After installation, It consumed a significant amount of power after only a few hours, enough for me to realise the difference.

I tried soft reset many times, same condition so I gave up worrying about it and decided to wait for a new version. 

A few days ago, version 25.10 was released on my watch, The battery-draining issue appears to have gone away without me doing anything additional to the watch. And, I have not installed anything new nor did I change the WF.  

I also use the 3rd part of WF and now at sw 24.00 problm with battery I do not consume 0.1-0.3% per hour and for several previous sw verses I had a problem with the battery. Good consumption was with versions 13.30, 16.70, 20.01 and 20.30, but from 23.xx I started to have problems with the battery. Now I have probably the best battery consumption results at 24.00 where I prefer to stay for some time. Each time I had the same 3rd part WF on my watch. Therefore, I would not say that in my case the higher consumption was caused by WF . I have WF SC8  where many data fields are also used .

Hi For your information.

25.xx introduce System IQ 6 with CIQ API 3.4.0.

So third party software need to be updated for a good support of this important change.

SC8 WF seems to support CIQ system 5, including F7/E1 FRx55.

Not System 6, for FRx65, Instinct 2, etc.

It's an old WF, for sure the developer will update it with the latest API support.