• State Not Answered
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 7 replies
  • Subscribers 4 subscribers
  • Views 1483 views
  • Users 0 members are here
Options
Related
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

Battery drain/calibration issue from 35% to 25%

shrijith1
over 4 years ago

I have been using my Solar for nearly 4 months and in the last 4 discharge cycles have given me closer to 25 days battery life with following profile.

1. Average 1 hour Non-GPS activity.

2. Pulse Ox turned off.

3. HR, Sleep, Steps tracking ON.

So there is nothing much to complain about this however I noticed this peculiar behaviour. On an average I notice 4% battery drain per day with above profile. However once the battery reaches 35%, there is a rapid battery drain of 10-12% on the following day. It becomes normal at around 24-25% again. I have checked this 4 times and it happened every single time even without any activity. There was a battery drain of 5% overnight during this time compared to 1% average.

Has anybody noticed this ? I have not yet contacted support since I am getting advertised battery life.

  • 0 over 4 years ago

    You are not the only one! It happened twice with mine as well. From around 32% in the evening, I woke up with only 24%.
    Pulse Ox is off.
    HR, Sleep and Steps traking are on. 

  • 0 over 4 years ago in reply to 8990965
    8990965 said:
    From around 32% in the evening, I woke up with only 24%.

    There may be many reasons for that. First of all the discharge curve of a battery is not linear. Then, the watch might consume more than usually for some reason - for example you accidentally and repeateadly pressed against the light button, or perhaps another one, or the watch might have downloaded (or repeatedly tried downloading) a firmware or the ephemers file update, or the phone was on the edge of the BT range, hence there were some permanent hadshakes between the devices, etc., etc. It could be also due to a temperature change - that will impact the battery voltage too. There are certainly many other possibilities I did not name.

    To test the discharging rate, it would be safer keeping the watch on the table, without touching it, and disabling also the BT, to avoid at least some of the possible reasons I listed.

  • 0 over 4 years ago in reply to trux

    That's the reason I tested it over 4 discharge cycles to rule out if it's a one off issue. All the 4 times the usage profile was exactly same. I keep Bluetooth off. Also noticed that at around 10% the battery discharge is very minimal. It stays in the same percentage for almost a day. Due to this the total battery life doesn't get hit but wanted to bring into light this peculiar behaviour. I will write to support with all the details.

  • 0 over 3 years ago

    Can this be checked by engineers ? I would be happy to help with any logs. Using the watch since almost an year and the battery always depletes from 35 to 25% quickly.

  • 0 over 3 years ago in reply to shrijith1

    Owning an Instinct Solar for more than a year, I can confirm. I thought the faster discharge begins at 40%, but it could be 35%, as well. I don't look at it so often, so I am not sure. Either way, I've never thought it may be a problem. As trux mentioned, batteries do not discharge in a linear fashion, so I have always assumed the range from 40% down to 25% is "the weak" on of this battery.

    Have you gotten any feedback from the tech support?

  • +1 over 3 years ago in reply to shrijith1

    In general, when concerned if your battery is potentially defective, it is best to observe your total charge time from beginning to end. Take into account how much Pulse OX is used, GPS, and if you are receive a large number of smart notifications. For  battery impact, PulseOX is #1, then GPS, then Bluetooth for draining your battery.

  • 0 over 3 years ago

    Total battery life is fine. I am just pointing to a potential software/battery calibration bug which others are also facing as is evident from the thread. Can you please pass on the message in this thread to your engineers to fix it ?