Phone Notification Bug - Why is this taking so long to fix?
Answered
Hammerhead: The phone notification bug has existed now for several release cycles. While some riders don't care about notifications when they ride, others need them due to work, kids, leading group rides etc.
All the bike computer manufactures seem to know this, in fact they all include this function in their software and keep it working. In fact I would go as far to say that it is a standard function for all the major brands including Garmin, Wahoo, Bryton, and others.
So why doesn't Hammerhead fix this important bug? I know Hammerhead is slow to fix bugs, but this getting almost as ridiculous as the time it took to fix the CRITICAL Reboot Issue. Can you give some kind of meaningful update, and not just a worthless "We're working on it."???
-
Well, it has been 4 days since I made the original post, and over 1 month since I posted here asking about this fix in a previous post. Still no fix and no update to this post. The 08/25/22 update just came out and the phone notifications issue hasn't been fixed.
While it is great that HH does bi-weekly updates, hardly any effort goes into fixing Critical and High priority bugs. Most of the effort goes into new features. I know HH is trying to catch up feature-wise with Garmin, but whats the point if the HH user is missing basic functionality?
In short, HH takes as much time to resolve bugs as Garmin, AND while the Garmin bugs are annoying, the HH bugs have impacted my rides much worse than the garmin bugs I experienced. I am seriously considering switching back to Garmin at this point.
-
Thankfully I have stumbled across this thread as I also thought it was just my issue, relaying messages to my head unit was a primary purchasing consideration for me. As Darrell rightly points out above, I need live messaging on my rides due to the nature of my work. I have the exact same scenario as Scott, I need to manually connect the phone again before each ride and a couple of miles in or when the first message lands, it disconnects. I find myself using an old head unit from another manufacturer which is pretty disappointing given I have just bought this Karoo. It needs fixed urgently and can't imagine it's splitting the atom???
-
BUT ... they updated the VALVE STEM configuration???? (Improved Tire Pressure Sensor Configuration)
If you can find me 10 people that benefitted, I will stop thinking that nobody gives a **** about bugs, or anything we say here. They a scrum master randomly picking cards and updating things that might be cool.
-
Well, it has been 11 days since I posted this thread and HH still hasn't responded. Looking at other posts here it looks like HH hasn't responded to hardly any of the posts. Why is this Community section here?
I'm not a big Faceboook fan, but there are 2 Karoo forums there, were there is decent user participation. If folks need help, you can try posting there. It's better than the echo chamber that this area has become.
-
Hey Guys!
We understand that having phone notifications during your rides is an important feature and the Karoo not reconnecting to the phone can be annoying.We would like to inform you that our team is working on a solution for the phone notifications issue and we are expecting the fix to be rolled out in the next update.
-
I am honestly very curious if the problem is really solved now.
I've also been waiting for the messaging fix for months. Reported it some when in April 22 to the support.
In the "Known Bugs and Issues" thread, the entry has disappeared at least once.
( some users are experiencing problems ... some ;-) ;-) )
My Samsung Galaxy S20 FE is always updated with the latest software, including now, and my K2 is also on auto update.
Last week Friday 09/16 it still hadn't worked even though the 08/09 firmware was already installed and activated.
I have now made a hard reset on the K2, deleted my Companion App on the S20 FE, then performed a wipe cache partition, the app reinstalled from the Playstore.
When restarting the K2 came at some point also the connection prompt with the message awaiting connection, have then started the app on my phone and without PIN was now displayed on both devices that the pairing was done.Looks for me first not really promising, but I'm happy to surprise me and will also report further here.
-
The phone notification bug is not fixed for me either. I am running the latest firmware and I can connect my phone, but it disconnects as soon as you walk out of range with the phone or if the Karoo goes to sleep during a coffee break.
This is very disappointing after taking so long for a "fix", to not really have this bug fixed.
-
I agree - not fixed. Works better, but I still watch the white line go from white to grey and back multiple times a ride (and I'm not staring at the computer.)
I fixed the problem - I went back to Garmin. I miss predictive-climber, but don't miss this crap. I'll consider using Hammerhead again when they start fixing broken features and stop upgrading valve stem experience. -
Confirmed! - Notification still doesn't work at all.
- made a hard restet ( newest release was already installed, as described in my former post)
- deleted the Karoo Comanion App
- removed Karoo2 from Bluetooth list
- wiped Cache partition on mobile device
- installed Karoo Companion new from Google Playstore
- connected Karoo2 with Mobile Phone (although only at the second attempt the PIN code was generated and displayed!)
- allowed all permissions
- set the App to "never go to standby"
- started my ride yesterday late afternoon, asked some friends to send me messages in different messengers like Whatsapp, Threema, Signal ..
- received 19 Messages during my ride on my mobile phone
- the line below never changed to grey, was white all the time, phone pairing showed a connected status
- no message was displayed on the Karoo2 and at the End of the ride it still sayed: No phone notofication received on this rideMy Sigma Rox 11.1 which costet a quarter of the Karoo2 does that easily. Maybe HH should hire some developers from
there...
Hey Hammerhead, that's so poor and I feel I am being lied to!!
Please give me my money back and take back your trash!
one thing would still interest me: what says SRAM to such inferior quality -
I would re-phrase what John Hayes said - it's time for Hammerhead to stop advertising - and fix their product.
Wahoo Roam 2 is about to pass them.
Garmin isn't bad.
Both last more than 10 hours.
Both get my notifications.I went from "This is the best "riders" computer" to - it's not worth the frustration. Enhancing fringe features like valve stems while ignoring broken core functionality ... I'm out. If you want a spare, mine's for sale.
-
Well, the Oct 6, 2022 release is now out and there is still no fix for the phone notifications. Hammerhead, this is really poor Product Management. You keep prioritizing critical and high priority bugs very low, which mean important bugs are lingering for months. It is makes your product frustrating on good days and out right unusable on others. YOU WILL NOT BUILD YOUR BUSINESS ON AN UNRELIABLE PRODUCT!!! Features are cool, reliability is a NECESSITY.
I've had a lot of people ask me about my Karoo since I got it and I tell them about the good points, and the critical and high priority bugs that I have I had to deal with. No one has bought a Karoo yet. They refuse to deal with Reboots in the middle of a ride, and no phone notifications. I have at least one of these bugs during the full 6 months months I've owned the product. They have seen the Karoo bugs. They may curse their garmin, but decide the Karoo flaws are showstoppers.
Please sign in to leave a comment.
Comments
16 comments