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.

  • Auto turns the backlight up further the brighter it is. This means the battery level is negatively affected especially in sunshine.

  • Of course it is possible that your unit is defective, but try it without auto function.

  • I definitely will try it, thanks. But I won't lie, if that's the cause of the battery issue, then WOW, that is some piss-poor engineering right there.

    The new Edge 1040 advertising slogan:

    "Buy the 1040, it's battery will be ALMOST as good as your 8 year old Edge 1000 with an aging, decrepit, old battery that's one step away from leaking the acid out onto your stem!"

    I think that's a real winner.

  • 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%

    When I have the backlight on manual and on high, my burn rate is 15-17% per hour. Install the burn rate connect IQ data field.

  • Auto turns the backlight up further the brighter it is. This means the battery level is negatively affected especially in sunshine.

    That is not the behavior I observe when I go to the screen to adjust the brightness and select auto, and watch the slider move around in various lighting conditions. I’m seeing the opposite. Have you tried this 

  • Not just the auto brightness function, there is also the backlight timeout (system - display). I have that turning off after 30s. The backlight is the biggest single consumer of power for the device (same with phones, tv’s, basically anything with a screen).  I doubt much can be done in efficiency since the 1000 (or even the older ones).  If it’s left on permanently try putting it onto a timeout and see what difference it makes.

  • So you're saying that it works the other way around for you? The darker, the brighter? That doesn't make much sense, does it?

    Of course, I tried Auto myself and turned off the automatic afterwards, because it consumes too much battery on sunny days.

    By the way, the automatic function also works on all smartphones (at least on iPhones) exactly as I described - when the sun shines on the display, the iPhone turns the brightness to maximum.

    Even MacBooks work like this - if you work in the sun and there is no automatic brightness control, you have to increase the display brightness yourself. Can't think of your device doing otherwise! Are you sure about your observation?

  • I’ve got backlight permanently on and auto brightness on. And right now I’m at 83% after a 2:14min ride and a 4:11min ride in the full blasting sun. And that’s moving time. So I’m not sure where the backlight-panic in this thread is coming from? I should easily do 40 hours.

    For reference: Got a non-solar 1040. Garmin HRM, Shimano power sensor, Di2, and an IPhone connected with the app on. I use navigation and Multi GNSS/Multi Band. Not exactly economical mode.

  • So you're saying that it works the other way around for you? The darker, the brighter? That doesn't make much sense, does it?

    Yes, it makes sense, because the display of a smartphone works not like the Edge display.

    Edge devices have a transflective display. The more sun the less backlight is needed!
    In bright sunlight no backlight is needed!
    https://www.szmaclight.com/new/How-to-choose-Sunlight-readable-tft.html

    Smartphones have LCD, AMOLED or OLED diplays: the more sunlight the more (back)light is needed!
    https://www.nextpit.com/smartphone-displays-explained

  • I’ve got backlight permanently on and auto brightness on. And right now I’m at 83% after a 2:14min ride and a 4:11min ride in the full blasting sun. And that’s moving time. So I’m not sure where the backlight-panic in this thread is coming from? I should easily do 40 hours.

    Your setup is similar to mine only you have more devices than I do. I have a speed sensor, cadence, my iPhone, Edge Remote, and my Garmin chest HRM. So I would expect out battery life to be roughly the same. But to your point, this is kind of what I'm saying. Don't get me wrong, it costs me nothing to experiment with turning the auto off and setting the brightness to about 33%, because Garmin tech support and customer service aren't even open now. So if I do decide I need to send it back for a refund, or if it is defective and Garmin replaces it, waiting till tomorrow for the former won't change my refund period, and it's not like Garmin can help me now anyway. But I will say this. If it turns out that my unit isn't defective, and that just turning ONE setting on like Auto, causes this state-of-the-art computer to go from 100 hours to a laughable 8 hours, then I have a decision to make. Because I can max out the setting on my OLD Edge 1000 with an aging battery, and get more than that.

    So if this is a feature and not a bug, then that would be a huge problem for me. Enough to cause me to wonder why I spent all this money on a brand new device that has a bunch of spiffy features and all, but what I really wanted was the huge battery, while my 1000 works perfectly fine.

    One more thing: I have had Auto turned on since I started using this thing. Why, only after several weeks, am I getting this ridiculous battery draining, when nothing has changed? Like you, I was getting 43 hour predictions with 100% charge, and like you, only after about 7 hours of constantly being on, did my 1040 go down to 85ish%. Now it takes an hour, with literally NO settings changed?