Expand ANT+ light features
Completed
Today's release includes the ANT+ light support, great! It works great, so great job HH!
However, it seems we can now only turn on the lights when we start a ride, and turn them off when we finish the ride. However, I often leave my light on my bike, and I wouldn't want to have it turned on during the day. So maybe that can be a setting?
I was expecting to have a new type of page and have controls like Garmin has, so we can set it to a specific mode with buttons, off/on/high/med/low/flash/flash-daytime, etc. Even at night I never ride with the same light mode. In the city I drive with lowest setting, but in the middle of nowhere where I can't blind people, I tend to have my light at a brighter setting, and when I'm waiting somewhere at an intersection, I would turn it to a low brightness with flash.
It would also be cool if you could set the mode to something else when you stop biking (when the karoo pauses the ride). If I could set it to mode x when I pause, and then continue to mode y when I bike again, that would be epic.
-
Bump. This could really use some improvements, the basic integration is missing some pretty helpful features. Similar to what has already been mentioned:
- Ability to change light mode during a ride, preferably on its own data screen so I don't have to dive into the settings. I want to be able to change the light mode if it gets dark or cloudly, or turn off the lights while I'm at a coffee shop. Garmin has this.
- Proper names of light modes. My Bontrager Ion/Flare lights have Day Flash/Night Flash modes but they just show up as Custom Mode 1 and Custom Mode 2 in the light settings. My Garmin also has this.
- Permanently dismiss the low battery warning. Swiping up to dismiss the notification works as described above, but then I get a new notification and beep something like a minute later. This happens forever so you have no option but to disconnect the light in the sensor settings.
-
One thing about the light controls, and the radar controls , is that burying things in the menu system directly decreases their utility.
I find it is bad design.
More and more systems are doing this, and I find that one has a choice to "engage" or abandon.
I am pushed to abandon more. Maybe that process is just being changed in its focus , to feel more highlighted.
I have begun to feel that trying to "engage" is more and more frustrating, and alienating.
The light controls don't work well, and I doubt that will change, and, fristrated, I just stopped usiung it.
along with many of the other "features" in the system.
If it doesn't work quickly and intuitively , it is just not good design, or a limited design that is not well communicated.
-
Not sure why this is marked as completed, anyways...
Just saw a Facebook post which hints at easier light controls: https://www.facebook.com/HammerheadRides/posts/pfbid02hA3nasmL9iEmtDTK2nVDAvBWgzsCpnaRsXiCxAy6t5gSTpJMiDCnoGapWGSt7kkzl
However, I am very afraid it's one of those nonsense Karoo 2 only features. How can we use this screen in the picture? I really need this.
-
I understand that the Android "kernel" is different between Android 6 and 8., though both are kernel 4. Android 12L is the current non beta version and 9 on use a kernel 5.
Is there a discussion as to why the K1 has to be left with a seven year old Os? Mine is a 3 year old device?
Android 6 came out on October 5, 2015 and 8.0 on August 21, 2017, The K1 in Feb 2018 and K2 Sept 2020, the same month as Android 11.
Are pre-Treble Os's prior to 8, just abandoned as too costly to update, a wrong move or is it a built in obsolescence?
A big part of the attraction of Android was its ability to be updated. @Ali , are you saying the K1 can go to 8, or tops out at its original Android 6 ?
Will the Os in the K2 be updateable under Treble influenced Android 8? Is there a sense as to how long a bike computer should go before being EOL'ed or progressively hobbled, weaned from further features ?
-
As a device whose primary purpose is a GPS bike computer, there are no plans to upgrade the Android version on Karoo 1 or Karoo 2. Upgrading the Android versions will add the complexity of possibly re-working on the many parts of the custom KarooOS. The efforts can be better put on adding more features on the devices instead.
There are currently no plans of ending the support for the Karoo 1 for software updates.
Karoo 1 will continue getting the updates, and will be so unless we reach to a point where it cannot.
-
Thanks very much , Ali. The proprietary elements in the implementation of the light's, radar, and other accessories appear not to follow ANT+ standards completely , preventing the universality in head units, generally. Even when one can cleanly implement them, providing backwards compatibility is at best a headache. This is one of the factors that appears to make Garmin's OS bloat and bug, and has limited sideloading of non HH apps and made them difficult to maintain. Different discussions, but relevant. Controlling feature access and accessories like the remotes, bring this out, as Mikolaj's comment on the Magene notes above.
I don't see HH pulling an Apple and stopping its flagship feature of updates, but I have lost a lot of features on other systems as the 3rd party updates lose compatibility with the primary devices.
Android had substantive changes between 6 and 8, and the things HH has not been able to forward have not substantially affected the utility of the K1 being a good tool.
Please sign in to leave a comment.
Comments
46 comments