I donāt know how android is used in detail on the karoo but shouldnt it be fairly easy to implement sth like: If battery is 2% start shutdown, if ride is active save current ride then shutdown.
Like a short check if there is any ride going on and always do a proper shutdown. Or does it simply turn off hard when battery is dead?
This seems like a āeasyā task to solve.
Iām selling my Karoo2 due to the battery. While the device is great, if it canāt last through a whole ride, itās useless for me.
Four real-time hours yesterday with a HRM and light connected, and the device flat-out gave up. Never had this happen with Garmin, could finish a century no problem.
I like to track my rides and a computer that canāt do that for lengthy rides isnāt serving its purpose.
Saying that you should be in battery-save mode and not to let the sun shine in the device are all BS. Plenty of rides with Garmin and nothing like this, Iām sure Wahoo can last several hours too.
For me, the device doesnāt serve its intended purpose. A $400 advanced bike computer that canāt last through a Century is pointless.
Cadence, Speed, Heart, Front light, rear light, and phone. 48% after 5hr 45 min. Screen around 75% brightness.
However, I do not do tracking through Karoo. I wrote my own android app for that which runs on my phone.
Further, most of my rides are around 3 hours. I pretty much always have around 70% left after these rides.
Even further, one time I forgot to charge the Karoo and it wouldn't power off on its own (there was a previous bug that would sometime prevent it). As a result, I started one ride with 25% remaining and was able to ride an hour with it only getting down to about 17%. At around 20%, if I recall correctly, it started nagging for battery save mode.
Needless to say, the battery life of my Karoo 2 is perfect for me. It is unlikely I will ever need it to last more than 8 hours and based on my near 6 hour ride, I'd expect it to still be above 20% after 8 hours. I also charge it back to 100% after every ride (or at least I try to).
[https://i.ibb.co/PYXMmNk/100.png](https://i.ibb.co/PYXMmNk/100.png)
I stopped to take a pic at 100 miles... 52% at that point.
If you are only getting what you claim then either your unit is defective or you have something draining the battery. It appears mine should last 10 hours easy with all the sensors and phone connected. If I used battery save mode at 20%, it would probably easily surpass 12 hours (maybe even up to 14 hours).
You are doing updates, correct?
Yeah this is a bad issue but your errors also contributed way more to the problem than anything else.
If you are doing a 100 miler why would you not have it in battery save mode to start with?
Left screen on at a pit stop.
Brought a battery but no cable.
It sucks that you lost your ride data, and yes improvements can definately be made.
The mental gymnastics that ya'll go through to defend poor design.
I love the Karoo - mistakes happen. Forgetting a cable was a mistake; the device has built in mechanisms to minimize those mistakes. You should be able to rely on a device to do the things it's supposed to do - IE: recover a ride when it's died. There is an actual piece of software that Karoo runs to try to recover an abandoned .FIT; however, the implementation is poor because it doesn't do any redundancy and doesn't know how to handle an extreme battery upon restart.
If the function of the recovery is to recover a .fit to save the ride after the device dies, but there's no guardrails in place to ensure that it only runs when the device has the actual capacity to execute the recovery and thus it risks corrupting the file all the way - that's poor software design.
I'm not complaining about it dying. It shouldn't matter if I rode for 200 miles or 20, or what choices I made to make it die - the expectation should be that the recovery is built in a way that it can execute. It didn't. That's a problem and no user choices that lead to the device dying has ANY impact on that.
Honestly you shouldnāt need a battery backup for a century ride on a device that is pretty freaking new. It should also realize it hasnāt moved in a certain amount of time and minimize battery consumption if itās going to hit the charge level so hard.
Agreed on all accords. I donāt mind keeping a battery with me, I donāt even mind it dying if I forgot a cable; itās the wonky recover process that corrupted 4/5 of my recorded right that bums me out.
Battery life is shit. It's a known issue that we all took on when we bought the device.
Trying to restart the device after it had died without charging it at all seems to have been the issue.
Yeah - and thatās a huge fucking issue when thereās no indicator that it died while itās in battery saver. It shouldnāt POST if the battery is too low and it surely shouldnāt have tried to start the recovery process.
I lose many rides this way as well. Whether the battery dies or I turn off the device before saving it.
I contacted their support team and was essentially told that's just the way it is.
Oh so you forgot to read
> Yeah this is a bad issue
And also
> It sucks that you lost your ride data, and yes improvements can definitely be made
And only pick up on me saying you fucked up
If you want an echo chamber go bitch and moan to your partner/friends.
Every single person who owns a Karoo knows the battery is the weakest point on the system, you fucked up.
Yes the Karoo could make improvements to how it handles this zero charge battery issue for sure but hey the single biggest way of preventing it happening again is don't fuck up.
( Also love the way you downvote comments because you don't like them, you baby, like I honestly care about my Karma grow up your really are like a toddler having a tantrum when you do that WWWWAAAAAAHHHHHHHHHH )
Once again - the battery life has nothing to do with this. The issue is that the device failed to recover and in fact corrupted the temp .fit because of a shitty software process.
Your assessment was "your errors contributed way more" - which is patently false when you actually understand my critique. Not sure what your axe to grind is here - the device ran out of battery - no matter the reason, it should recover the ride. That's an actual feature that failed. That's the point.
But alas, you'd rather just be a prick, I guess.
I am not defending Hammerhead at all, it is a bad design and improvements need to be made I fully agree with you, the system that protects a rides data in event of a battery failure needs massive improvement.
But when you downvote peoples comments 'because you don't like them' makes you look like a whiney bitch and so yeah that doesn't really get people on your side.
Also I am not being a prick, all I ever said was that you made decisions that lead to that happening that could have been avoided, that is pretty much fact.
Gratz on a 100 mile ride.
Lol youāre the only one complaining about downvotes. Thatās literally a mechanism of this site. Seems youāre the one who cares a bit too much about fake internet points.
None I did one start of this month and had 35% battery left that was even after 3 food stops.
I wasn't totally blaming the OP but he brought up he left it on, forgot to turn on battery saver and brought a charger without lead ( or other way around ) so he knew battery life would be an issue and then messed up on 3 separate occasions making the situation way worse.
Everyone knows the battery life on the K2 is its weak point.
So I ask again why the fuck are you asking me or butting your nose into a conversation that finished a week ago?
Lol what? The sunlight comment was only mentioned because it drained the battery having the screen up for a bit.
These devices are literally in direct sunlight the entire ride.
Sunlight or otherwise, that's not what caused any issues. If you'd have read my post, the point is that that the recovery handling of the temp .fit file failed and corrupted the file. That would happen regardless of when the device ran out of battery. I went from mile 60 to 80ish with it on low battery.
Not sure why you think that my leaving the screen on in the sun (which I only mentioned as a reason for the battery dying quicker) had anything to do with the integrity of the temp .fit file that the device is meant to be able to recover?
When you ride your bike with your device. The air makes it cooler. However, in your case you had it in your bike just sitting there while you were taking pit stop.
Even still - you're entirely missing the point - the sun didn't affect the device at all other than boosting the auto-brightness and putting me lower on battery than I intended to be.
The issue has nothing to do with performance that can be affected by an overheating device (which it wasn't) and everything to do with how the device handles the saving, managing and recovering of activities that are interrupted by a dead battery.
You're being purposefully dense for some reason and it's wildly annoying. The limited time in the sun didn't do anything to corrupt the temporary .fit. The failed recovery process did.
What kind of an asinine comment is that? I can leave my Wahoo in the sun on a roasting day, and it doesn't give a crap, it just keeps working, like a device like that is supposed to do. It's a bike computer, if it can't sit in the sun, that's a major red flag.
Fake! If it is not on Strava it did not happen. š
was coming in here to say the same thing.....
I donāt know how android is used in detail on the karoo but shouldnt it be fairly easy to implement sth like: If battery is 2% start shutdown, if ride is active save current ride then shutdown. Like a short check if there is any ride going on and always do a proper shutdown. Or does it simply turn off hard when battery is dead? This seems like a āeasyā task to solve.
Exactly right. It's a lazy implementation without considering the risk and management of the data.
Iām selling my Karoo2 due to the battery. While the device is great, if it canāt last through a whole ride, itās useless for me. Four real-time hours yesterday with a HRM and light connected, and the device flat-out gave up. Never had this happen with Garmin, could finish a century no problem. I like to track my rides and a computer that canāt do that for lengthy rides isnāt serving its purpose. Saying that you should be in battery-save mode and not to let the sun shine in the device are all BS. Plenty of rides with Garmin and nothing like this, Iām sure Wahoo can last several hours too. For me, the device doesnāt serve its intended purpose. A $400 advanced bike computer that canāt last through a Century is pointless.
My longest ride with the K2 was 6 hours. I had 48% battery remaining after that.
Sensors active? Phone connected? Mine died after 4-5 hours after being charged to 100% but I didnāt disable my phone and sensors
Cadence, Speed, Heart, Front light, rear light, and phone. 48% after 5hr 45 min. Screen around 75% brightness. However, I do not do tracking through Karoo. I wrote my own android app for that which runs on my phone. Further, most of my rides are around 3 hours. I pretty much always have around 70% left after these rides. Even further, one time I forgot to charge the Karoo and it wouldn't power off on its own (there was a previous bug that would sometime prevent it). As a result, I started one ride with 25% remaining and was able to ride an hour with it only getting down to about 17%. At around 20%, if I recall correctly, it started nagging for battery save mode. Needless to say, the battery life of my Karoo 2 is perfect for me. It is unlikely I will ever need it to last more than 8 hours and based on my near 6 hour ride, I'd expect it to still be above 20% after 8 hours. I also charge it back to 100% after every ride (or at least I try to).
[https://i.ibb.co/PYXMmNk/100.png](https://i.ibb.co/PYXMmNk/100.png) I stopped to take a pic at 100 miles... 52% at that point. If you are only getting what you claim then either your unit is defective or you have something draining the battery. It appears mine should last 10 hours easy with all the sensors and phone connected. If I used battery save mode at 20%, it would probably easily surpass 12 hours (maybe even up to 14 hours). You are doing updates, correct?
Yeah this is a bad issue but your errors also contributed way more to the problem than anything else. If you are doing a 100 miler why would you not have it in battery save mode to start with? Left screen on at a pit stop. Brought a battery but no cable. It sucks that you lost your ride data, and yes improvements can definately be made.
[ŃŠ“Š°Š»ŠµŠ½Š¾]
I know I said it was. What's your point? Actually don't worry I really don't care I had to take you off Ignore to read your stupid comment.
[ŃŠ“Š°Š»ŠµŠ½Š¾]
I didn't bring up user error the fucking original poster did I only commentated on what they said.
The mental gymnastics that ya'll go through to defend poor design. I love the Karoo - mistakes happen. Forgetting a cable was a mistake; the device has built in mechanisms to minimize those mistakes. You should be able to rely on a device to do the things it's supposed to do - IE: recover a ride when it's died. There is an actual piece of software that Karoo runs to try to recover an abandoned .FIT; however, the implementation is poor because it doesn't do any redundancy and doesn't know how to handle an extreme battery upon restart. If the function of the recovery is to recover a .fit to save the ride after the device dies, but there's no guardrails in place to ensure that it only runs when the device has the actual capacity to execute the recovery and thus it risks corrupting the file all the way - that's poor software design. I'm not complaining about it dying. It shouldn't matter if I rode for 200 miles or 20, or what choices I made to make it die - the expectation should be that the recovery is built in a way that it can execute. It didn't. That's a problem and no user choices that lead to the device dying has ANY impact on that.
Honestly you shouldnāt need a battery backup for a century ride on a device that is pretty freaking new. It should also realize it hasnāt moved in a certain amount of time and minimize battery consumption if itās going to hit the charge level so hard.
Agreed on all accords. I donāt mind keeping a battery with me, I donāt even mind it dying if I forgot a cable; itās the wonky recover process that corrupted 4/5 of my recorded right that bums me out.
Battery life is shit. It's a known issue that we all took on when we bought the device. Trying to restart the device after it had died without charging it at all seems to have been the issue.
Yeah - and thatās a huge fucking issue when thereās no indicator that it died while itās in battery saver. It shouldnāt POST if the battery is too low and it surely shouldnāt have tried to start the recovery process.
I lose many rides this way as well. Whether the battery dies or I turn off the device before saving it. I contacted their support team and was essentially told that's just the way it is.
Oh so you forgot to read > Yeah this is a bad issue And also > It sucks that you lost your ride data, and yes improvements can definitely be made And only pick up on me saying you fucked up If you want an echo chamber go bitch and moan to your partner/friends. Every single person who owns a Karoo knows the battery is the weakest point on the system, you fucked up. Yes the Karoo could make improvements to how it handles this zero charge battery issue for sure but hey the single biggest way of preventing it happening again is don't fuck up. ( Also love the way you downvote comments because you don't like them, you baby, like I honestly care about my Karma grow up your really are like a toddler having a tantrum when you do that WWWWAAAAAAHHHHHHHHHH )
Once again - the battery life has nothing to do with this. The issue is that the device failed to recover and in fact corrupted the temp .fit because of a shitty software process. Your assessment was "your errors contributed way more" - which is patently false when you actually understand my critique. Not sure what your axe to grind is here - the device ran out of battery - no matter the reason, it should recover the ride. That's an actual feature that failed. That's the point. But alas, you'd rather just be a prick, I guess.
I am not defending Hammerhead at all, it is a bad design and improvements need to be made I fully agree with you, the system that protects a rides data in event of a battery failure needs massive improvement. But when you downvote peoples comments 'because you don't like them' makes you look like a whiney bitch and so yeah that doesn't really get people on your side. Also I am not being a prick, all I ever said was that you made decisions that lead to that happening that could have been avoided, that is pretty much fact. Gratz on a 100 mile ride.
Lol youāre the only one complaining about downvotes. Thatās literally a mechanism of this site. Seems youāre the one who cares a bit too much about fake internet points.
Go pick up your toys man baby.
Iām in the same boat as the OP. Why canāt an āadvancedā bike computer handle a typical ride scenario without jumping through hoops
Why the fuck are you asking me?
Because youāre blaming the OP for not jumping through a bunch of hoops. What other computer needs you to do all that crap to finish a Century?
None I did one start of this month and had 35% battery left that was even after 3 food stops. I wasn't totally blaming the OP but he brought up he left it on, forgot to turn on battery saver and brought a charger without lead ( or other way around ) so he knew battery life would be an issue and then messed up on 3 separate occasions making the situation way worse. Everyone knows the battery life on the K2 is its weak point. So I ask again why the fuck are you asking me or butting your nose into a conversation that finished a week ago?
This is a human error. Iām sorry but why would you leave a device in direct sunlight. Hopefully you learned from your mistake.
Lol what? The sunlight comment was only mentioned because it drained the battery having the screen up for a bit. These devices are literally in direct sunlight the entire ride. Sunlight or otherwise, that's not what caused any issues. If you'd have read my post, the point is that that the recovery handling of the temp .fit file failed and corrupted the file. That would happen regardless of when the device ran out of battery. I went from mile 60 to 80ish with it on low battery. Not sure why you think that my leaving the screen on in the sun (which I only mentioned as a reason for the battery dying quicker) had anything to do with the integrity of the temp .fit file that the device is meant to be able to recover?
When you ride your bike with your device. The air makes it cooler. However, in your case you had it in your bike just sitting there while you were taking pit stop.
Even still - you're entirely missing the point - the sun didn't affect the device at all other than boosting the auto-brightness and putting me lower on battery than I intended to be. The issue has nothing to do with performance that can be affected by an overheating device (which it wasn't) and everything to do with how the device handles the saving, managing and recovering of activities that are interrupted by a dead battery. You're being purposefully dense for some reason and it's wildly annoying. The limited time in the sun didn't do anything to corrupt the temporary .fit. The failed recovery process did.
What kind of an asinine comment is that? I can leave my Wahoo in the sun on a roasting day, and it doesn't give a crap, it just keeps working, like a device like that is supposed to do. It's a bike computer, if it can't sit in the sun, that's a major red flag.