Hi, I'm the grumpy old guy who was an early complainer about the alarm problems.(I believe that I made the original suggestion involving a $5 alarm clock and duct tape...)
Just checked in after a long absence, to see if the alarm problems had been fixed. I was happy to discover this thread. Sounds like the answer is no. I seem to agree with bluegaspode and jmpage2 on most posts in this thread. Shame on Logitech. I've been an executive for software companies, and own my own company now, so I speak from experience when I say that. Some thoughts: - Why is the alarm clock function implemented as client-server, requiring a 7x24 computer to be running to signal an alarm? (Whether or not one should have a server running 7x24 is an irrelevant question - it shouldn't be required for an alarm clock!) - Why does Logitech not have a software quality assurance function and some regression testing? Use this to reproduce bugs and ensure that they get fixed and stay fixed? - Why does it take months and months to address bugs and issue patches, when there seems to be a fine facility for pushing down software to the radios? - Why does the bug reporting and logging system and process seem so informal and disorganized? Is there a list of reported bugs, showing if they are reproduced, and the planned fix date or version? That said, I still enjoy my SB Radio. I still have my $5 alarm clock taped to the top. Just today, as a test, I enabled by SB Radio alarm, and was jolted awake by the "loud volume burst prior to alarm fade" bug. I was actually happy - the alarm worked today! (Seconds later, my cheap battery alarm clock buzzed....) -- davenva ------------------------------------------------------------------------ davenva's Profile: http://forums.slimdevices.com/member.php?userid=34191 View this thread: http://forums.slimdevices.com/showthread.php?t=75541 _______________________________________________ Radio mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/radio
