Phone Notification Failure: Bug Status?
AnsweredHH, what is the status of the Phone Notification Bug?
BTW, it is really great that you fixed the Critical Bug - Reboots due to beeper/audio alerts. I hope this one is really fixed. The reboots really make the K2 unusable.
-
yeah, would be very interesting for me too, cause since I opened a ticket at the and of april/beginning of may where I sent several informations/screenshot etc etc and I was promised, that the issue will be given to the developers, I have the feeling that the behavior has gotten worse instead of better.
Despite new pairing, I often get no notifications, neither for messages nor for calls.
Is there a way, we can see the progress of that issue?
thx
Henryk -
Well, it appears the Phone Notification bug is still here. On today's ride, notifications were active during the early part of the ride. After a 15 minute coffee/pee break, I noticed that Phone Notifications were no longer working. They didn't work for the rest of the ride.
After I got home and uploaded my ride, I powered off the K2, then powered it back on to see if the K2 would reconnect to my phone on it's own. It wouldn't. I had to go into my phone's bluetooth setting, and reselect the K2.
So HH, can you give us an update and ETA for this bug?
-
Hi All,
Thanks for posting and sharing your insights here! We are aware of the concerns around the phone notifications. Our team is currently investigating the reports and since the number of reports around this concern is sporadic and linked with different phone manufacturers it is taking longer than expected!
I do apologize that we do not have an exact timeline for the solution but I will be sure to share your sentiments and observations with my team for their reference!
Please sign in to leave a comment.
Comments
6 comments