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

Serious Battery Problem - Plus A Few Other Issues

Okay, I have a standard 1040, not the solar model. Up until yesterday's ride, the battery seemed perfectly fine. 2-3 hours on a ride, degraded the battery to about 94-97%, longer rides would degrade it a little further. One five hour ride left me with about 91 or 92%, which is in-line with the predicted 43 hours of total battery life. When I say "predicted" I'm not talking about Garmin's published specs, but what the device predicts I will get when I press on the little battery icon, which is obviously based upon my chosen settings.

But yesterday, without any warning, it all went to total crap! I was on a moderately long ride, totaling about 5 hours. I noticed about 2 hours in that the battery life on the front screen was 67%, which is insane! I have "Battery Life" as one of the fields on my main screen. So I double-checked by swiping down and got to the page with the battery icon on it, and sure enough, it was also 67%. From there it was pretty much all downhill. By the time I was done with a measly 5ish hour ride, I had 39% Battery life left, and the predicted hours was something like 15 hours, if I remember correctly.

Honestly, that's a kind of battery life that my Edge 1000 would laugh at!

Now before anyone asks what my settings are, please remember that I am NOT expecting the 100 advertised hours from my 1040. I am aware that my settings bring my predicted battery life, when fully charged (100%) down to about 43 hours. If you need to know, though, I have the screen set NOT to turn the backlight off. I use the highest GPS settings, which is GPS+ (which includes Glonass, which I know is a battery drain). I use this GPS setting because I live in NY City, and any time I am anywhere near tall buildings, I have intermittent spotty GPS, presumably based on being in a sort of skyscraper-well. The screen brightness is set to "Auto". So as I said, not expecting 100 hours.

Now I am also wondering if yesterday's battery issue was some kind of an arbitration or one-off, so I will try it again today and see what happens. I did find it odd that at the beginning of my ride, yesterday, the device predicted the expected 43 hours, but as the accelerated battery life degradation proceeded, the device remained consistent in the expected battery life for the percentage left. So, it took about 2.5 hours to go from 67% to 39%, but when it as 67% the device was saying I had about 31 hours left, but 2.5 hours later, at 39%, it was saying I had about 15 hours. So I went through supposedly 30 hours of battery life in about 5 hours.

__________________________

Another problem I had yesterday was that my elevation fluctuated between like -160 and -145 feet for the entire ride. This is impossible, since NY City is a coastal city, and I am always very close to water level. LMAO at one point I was riding along bike path along a waterway and I was probably about 3 feet above sea level, but somehow the 1040 thought I was -150 feet, which is physically impossible. However, this I may have resolved when I got home and I manually forced the device to calibrate from my second floor bedroom, and it showed the expected +30 feet.

Another problem is with cell phone functionality, particularly alerts and weather. The phone was connected to the Garminm and yet the weather page thought  there was no connection, and was telling me as much. I tried "forgetting" my phone on the Garmin and "forgetting" my Garmin on the phone and re-synced everything. This didn't work. I also force shut off both the phone and the 1040, which also didn't work. After all of this, though, I was able to get a very poor weather screen with almost no stats by opening the Garmin Connect app on my phone. All it told me was what the temperature was (which was wrong) and had no info on wind or predictions for the coming hours. 

I got disgusted yesterday, early in my ride, seeing very limited weather info, so while pedaling, I shut the 1040 off (Garmin Connect open and running on my phone), which was difficult since the unit doesn't want to let you while an activity is running. But I held the On/off button, while pedaling for 10 seconds, which forced it to shut off, and I immediately turned it back on. After all this, the weather was fine, with the "coming hours" predicted below the current weather, and all the right stats working properly.

  • Any chance you may have turned the backlight on continuously (or it did it itself somehow). That’s just the sort of thing to cause this rapid drain.

  • It’s a computer. Same as the Garmin watches, sometimes a process seems to produce a high CPU load. Happens from time to time. 
    do a restart and everything should be fine. 

  • Even if I did, which I am sure I didn't, the Garmin makes its battery predictions based on the settings. When I started the ride, it said 100% with 43 hours left. TWO HOURS later it was down to 67% with a mere 29ish hours left; and 2-3 hours later, it was down to 39% with about 15 hours left. So my point is even if there was some magical setting to make this thing drain battery WORSE than my Edge 1000, why was the device essentially "lying to me" at every percentage. The device calculated certain hours left, and it was totally wrong in a huge, catastrophic way. No setting I could put on would cause that.

  • This is what I hope, that it as a one-off or momentary glitch. I will see a little later today when I ride.

  • I suspect it is the automatic lighting. i just tested it on my 1040 (non solar) (battery still has just under 80%).
    Settings: GPS max (multi) + backlight to 30% always on, but AUTO turned off.
    Prediction: about 45 hrs.


    Turned automatic on -> prediction down to 33 hrs.


    Then moved under a very bright light source with automatic on -> prediction: 7 hrs !!!!


    Turn off the auto, it sucks your battery faster than you can watch, especially in the sun and during the day.

  • I understand everything you’re saying, and I said in my original post, that I am not expecting maximum battery life on this thing. With the Settings I’m choosing, I don’t expect 100 hours, and I’m more than happy with 43-ish hours. Which is what I was getting up until yesterday, with the exact same settings. And I’m about to go on a ride so I just double checked. I think the problem you’re not grasping that I am having is that there seems to be a consistency problem. If the unit is reacting to the settings I already have, and telling me that I have 43 hours at the beginning of my ride which it’s saying I do now, then that is based upon the settings that I am using. 

    on the other hand, when it goes from 99% claiming 43 hours of battery life all the way down to 67% claiming 30 hours of bad life, and this takes place in the span of two hours, and then on top of that, going from 67 to 39% in another two hours, now estimating 15 hours of battery life, that is a problem with the device. Because I assume that the 1040 should have the ability to extrapolate battery data and keep it consistent and it’s predictions. So it starts out saying 43 hours, but five hours later it’s saying 15 hours? Where did all those hours go?

    moreover, this is the first time that happened. Even with the setting is precisely the same, and as I said I just checked them, I was getting consistent battery predictions for the last 15 or so rides I’ve done. Meaning in two or three hours the better we would go from 100% to say 93% or 94%. In five hours it might go from 100% to 90 or 91%. But in five hours it is never gone from 100 to 39%. That’s getting into the territory of my Edge 1000, by the way with the same settings lol! 

  • Then return the 1040 and get back to 1000

  • I had a prediction margin between 7hrs and 33hrs with the SAME setting!

    the only thing that changed was the environment (light/sun)....

    The prediction with backlight setting to AUTO depends on the brightness of daylight - im my test it was a margin of 26hrs!!! (7-33).

  • Yeah there is definitely something wrong with this unit. I did another ride today, and within about an hour it went from 100% all the way down to 85%. Nobody is going to convince me that this brand-spanking newfangled Garmin, representing the pinnacle of Edge technology should be behaving this way. I wanted to try the same settings as I did yesterday, in case this was a one-off glitch. Tomorrow I will try taking Auto off, but I really don't see how that's going to make a difference. I can say for certain that my aging 1000, with a battery that has definitely lost some of its juice, would do better than losing a full 15% in about an hour.

    If "Auto" is the culprit here, then that is indefensible. Particularly since the unit tells me straight out when I turn it on at 100% that I have 43 hours of battery life! I would be inclined to believe that the settings really could make my unit go from 100 hours at a full charge to lol 8 hours on a full charge, IF the damned thing didn't tell me that I have 43 hours, with my current settings only to lose not only 15 full percent BUT like 5 additional hours off the prediction indicator. I mean, if I started my ride and it said 100% Battery and predicted 8 hours on that full charge, then maybe. But nobody can convince me that the battery life predictor algorithm on this brand new unit is SO BAD that it thinks I will get 43 hours with the settings I have on and then only really gets 8.

  • By the way, I forgot to mention in my post a few minutes ago, both days I was riding in the middle of the day, blazing hot sun. If Auto was the culprit, as some are suggestion, I would imagine that this would only come into play on a dark night, not the middle of the day with the sun as brights as it could be, not behind any clouds.