View Full Version : My 7.5.1 experience so far.....
.... is not very pleasant.
1. The device occasionally makes a 3-beep tone, seems totally random to me. It can happen 2 times within 10 min or not happen for a couple of hours.
2. It wakes up from sleepmode by itself, often it wakes up 4-5 sec right after i press the off button.
3. ALARM!! is totally broken after the new firmware.
a) Sometimes the alarm dont go off at all
b) If it do go off, 50% of the times it sounds for 5 sec then shuts itself off (tested with both streaming radio and the effects sounds)
c) sometimes the snooze window dont pop up so i have no way to turn off the alarm other than turn on the device and then off again.
I dont run a server myself so im only connected to MySB
From what i understood they should have made improvements to the alarm when connected to a local server, but it seems they broke it even more when u are only connected to MySB server.
As the alarm now is broken i had to revert back to 7.5.0 where it atleast works 95% of the times.
With the help of this nice forum i found out you can revert back to the previous firmware by holding "REW" while starting the device. That helped me so i atleast can use the device, thing is i have to do this everytime i start it now, is there a way to permananently go back to the previous one without running your own server and patching it that way?
On the positive side streaming radio seems to still work without problem with the new firmware :)
Regards
Dolph
p.s this is not meant as a whining post, just wanted to report the bugs i found so far :o
fullkoll
2010-06-19, 13:47
I have about the same experiences as Dolph with my Squeezebox Radio delivered today.
It occasionally makes that 3-beep tone and it sometimes also wakes up from sleepmode by itself.
What I find most irritating is that the alarm shuts itself off after a few seconds!!!
/Kjell
diannabill
2010-06-19, 17:49
I am using Squeezebox Server and don't use the alarm function, so my troubles with 7.5.1 are different from yours. But I did have trouble even using the Squeezebox Server.
Radio would just freeze up and no presets would work. Then the radio kept prompting me to "upgrade" to 7.5.0 when I already had 7.5.1 installed (along with that version on the Squeezebox Server). So I finally gave up and let it upgrade to "7.5.0" After it was done with that, my radio showed I was on version 7.5.1.
After continuing to have problems with the radio freezing up, I uninstalled Squeezebox Server, downloaded version 7.5.0 again, and was prompted on my radio to go back to 7.5.0. No problems since.
I think 7.5.1 was a bone tossed our way! I fetched!
bluegaspode
2010-06-20, 01:49
3. ALARM!! is totally broken after the new firmware.
Just a guess: I am thinking that maybe because the whole world is downloading a new firmware releases this mysb.com-network is not stable enough for alarms :( ? So maybe this situation 'fixes' itself after a couple of weeks (but this wouldn't help you right now of course).
a) Sometimes the alarm dont go off at all
Are you configuring your alarm always and exclusivly on the Radio ?
If you do it via MySB.com thats the first thing you should stop be doing (as you can never be sure, that the alarm gets synced to the Radio in time).
If you configure alarms on the Radio and it still fails to sound the alarm completly see my point b)
b) If it do go off, 50% of the times it sounds for 5 sec then shuts itself
Out of interest for you point b)
I'd be interested if you can provide logs from the Radio.
For this you have to enable remote access (in the advanced settings), connect with the program 'WinSCP' and download the file '/var/log/messages' right after you experienced the alarm just stops.
If I find more time I might even look into the source to see if logitech changed something to the bad.
Thats the only help I can provide at the time.
(Please don't use my attempt to help for ranting about alarms or the architechture because then I'm very fast off this thread.)
Hi,
I am using my squeezebox radio as an alarm clock in my bedroom and I am experiencing the following issues (connected to MySB server):
1. The alarm clock screen shows only a very small clock that you cannot read even if you are only 1m away.
--> This has been mentioned already many times in the forum but it seems that this is not fixed. Unfortunately, the patch installer seems not to work any more so for me there is currently no solution for this.
--> This is a real bug for me and one reason why I think about returning the squeezebox radio. For me reading the clock while the alarm is on is a basic requirement!
2. No auto play at startup:
If you listen to a internet radio station and then switch off the radio (standby mode) and then wake up in the morning (by yourself and not through an alarm) and you want to listen to the radio again you have to switch on the SB radio and then hit the play button.
--> This is almost not possible in a dark bedroom and this is a basic feature for me! Every radio starts playing, if you switch it on! If this is not fixed soon, I will sell the radio because it cannot be used as a bedroom radio this way!!!
It seems that logitech puts a lot of effort into the apps and other fancy stuff but does not implement the basic features of an alarm clock/bedroom radio.
Hi,
If you listen to a internet radio station and then switch off the radio (standby mode) and then wake up in the morning (by yourself and not through an alarm) and you want to listen to the radio again you have to switch on the SB radio and then hit the play button.
If you set your presets to different stations/streams, all you need to do is press a preset in the morning and the radio turns on automatically and starts to play that station/stream.
If you set your presets to different stations/streams, all you need to do is press a preset in the morning and the radio turns on automatically and starts to play that station/stream.
Thanks for your reply.
I just checked this and it doesn't work!
After pressing the preset, the radio wakes up from standby and shows the internet station but it switches from stop to pause! You have to hit the play button afterwards in order to start the audio stream.
This is really annoying because you cannot find the play button easily when it is dark.
Any other solutions?
Any other solutions?
Try rebooting the radio. You won't lose your presets. Turn the radio on. Press and hold the power button. It should reboot the next time you press the power button.
Then try the preset method.
bluegaspode
2010-06-20, 04:33
After pressing the preset, the radio wakes up from standby and shows the internet station but it switches from stop to pause!
This is strange. When my Radio is off (i.e. Soft Off = Showing the Clock Screensafer) I can press a preset, it connects to the stream and instantly starts playing.
I'd give Logitech Support a try, maybe they can find the reason why its not working for you ?
Or you think about installing a local server, to get a lot more options/possibilities than mysqueezebox.com will ever be giving you.
2. No auto play at startup:
If you listen to a internet radio station and then switch off the radio (standby mode) and then wake up in the morning (by yourself and not through an alarm) and you want to listen to the radio again you have to switch on the SB radio and then hit the play button.
--> This is almost not possible in a dark bedroom and this is a basic feature for me! Every radio starts playing, if you switch it on! If this is not fixed soon, I will sell the radio because it cannot be used as a bedroom radio this way!!!
Also on my (local) server on the WebUI I have an option to configure the starting behaviour with the options:
"Pause at Power Off/Remain Paused at Power On" or
"Pause at Power Off/Resume at Power On"
which seems to be exactly what you are searching for.
Unfortunately I couldn't find this option on the MySqueezebox.com Website.
Maybe you should contact official support to ask whether there is some hidden way for MySqueezebox.com users to activate this option ?
1. The alarm clock screen shows only a very small clock that you cannot read even if you are only 1m away.
--> This has been mentioned already many times in the forum but it seems that this is not fixed.
This is not a bug, but an enhancement request. I guess it will only be changed, if enough users voted on an enhancements request in bugzilla (bugs.slimdevices.com).
With a quick search I couldn't find an enhancement request there so you might create one and start a new topic here on the forum to get some followers/voters.
I don't use alarms, but my Radio on MySB or SBS ...
- correctly maintains Power state (Off or Standby), does not turn itself on nor go from Off to Standby by itself.
I wonder if Alarms are causing these odd Power state changes?
- pressing Play or any Preset from Standby state correctly and instantly plays what it is supposed too
- no *3-beep* tones here (though I do have all audio beeps turned off in Settings > Sound Effects)
- I do still get the Radio self reboot whether playing or just in Standby (now very rare, maybe once per week as far as I can tell)
- station art is still dodgy and completely random
Playing same stream:
--- sometimes shows, sometimes not
--- sometimes will show on initial play but then disappears after 5 seconds
--- sometimes will show for hours
WinXP & SBS 7.5.1 & US MySB servers
Suggestions & tips:
- always reboot Radio after any FW update (press and hold OFF)
- if switching between SBS and MySB upgrade prompts should not display if SBS and MySB are the same FW version
- you can dismiss Radio FW update prompts (annoying, I know) by selecting Help from the update prompt then hitting the Home button
Thanks to all for the feedback.
1. Preset does not autoplay
Rebooting did not help. But I played around a little bit more and stored the preset again.
And now it works! Weired...
2. No autoplay after pressing the power button
This is for me, and my wife :-), still not logic.
If a stream was playing and I go into standby, I would expect that the stream would autoplay if the power button is pressed again.
Also, through a local SB server this option seems to be available (to your explanations). However, I don't want to run a local server.
--> I will write to the logitech support to find out, if this option can also be activated on the MySB server.
3. Font size of the clock in the alarm window
For me this is still a bug or lets say false spec because if you cannot read the clock from 1m away it is useless to display it.
--> However, I will open a new request on bugs.slimdevices.com
--> EDIT: Bug 16312
Hopefully this is changed because otherwise I am quite happy with the radio.
Thanks to all.
Yeah, starting playback via Power from Standby is just as you are experiencing:
SBS = works
MySB = does not work (stream enters Pause state)
Just press Play from Standby instead of Power for both SBS and MySB.
bluegaspode
2010-06-20, 05:57
--> EDIT: Bug 16312
I voted for it :D (though I wake up every day to the same time and actually don't need it in the display ;) )
http://bugs.slimdevices.com/show_bug.cgi?id=16312
Thanks for responding bluegaspode, have been away over the weekend so havnt been able to comeback with a log until today.
Out of interest for you point b)
I'd be interested if you can provide logs from the Radio.
If I find more time I might even look into the source to see if logitech changed something to the bad.
Here is the log from the time i set the alarm to when it went off and then turned it off by itself.
Jun 20 22:34:51 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:131 notify_playerAlarmState received for LocalPlayer {Squeezebox Radio} with alarmState of set
Jun 20 22:34:51 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:133 **************************** notify_playerAlarmState received: set 1277066280
Jun 20 22:34:51 squeezeplay: INFO applet.AlarmSnooze - AlarmSnoozeApplet.lua:210 storing epochseconds of next alarm: 1277066280
Jun 20 22:34:51 squeezeplay: INFO squeezeplay.applets - AppletManager.lua:708 store settings: AlarmSnooze
Jun 20 22:34:51 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:626 _stopTimer: stopping RTC fallback alarm timer
Jun 20 22:34:51 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:631 _stopTimer: stopping WOL timer
Jun 20 22:34:51 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:693 _startTimer: starting RTC fallback alarm timer (209000)
Jun 20 22:34:51 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:718 SEND WOL NOW
Jun 20 22:34:51 squeezeplay: WARN squeezebox.server - SlimServer.lua:606 wakeOnLan(): SKIPPING WOL, self.mac: nil, self:isSqueezeNetwork(): true
Jun 20 22:34:59 squeezeplay: INFO squeezeplay - JiveMain.lua:200 Turn soft power off
Jun 20 22:35:00 squeezeplay: INFO applet.ScreenSavers - ScreenSaversApplet.lua:280 activating Clock screensaver
Jun 20 22:35:00 squeezeplay: INFO applet.SlimMenus - SlimMenusApplet.lua:441 _menuSink(1) nil menuDirective: add isCurrentServer:true
Jun 20 22:35:00 squeezeplay: INFO applet.SlimMenus - SlimMenusApplet.lua:713 hiding any 'connecting to server' popup after menu response from current server, SlimServer {mysqueezebox.com}
Jun 20 22:35:00 squeezeplay: INFO applet.AlarmSnooze - AlarmSnoozeApplet.lua:255 notify_playerLoaded(LocalPlayer {Squeezebox Radio})
Jun 20 22:35:00 squeezeplay: INFO applet.ChooseMusicSource - ChooseMusicSourceApplet.lua:543 Hiding popup, exists?: nil
Jun 20 22:35:00 squeezeplay: INFO applet.SlimDiscovery - SlimDiscoveryApplet.lua:517 notify_playerPower: false
Jun 20 22:35:00 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:292 notify_playerModeChange: player (LocalPlayer {Squeezebox Radio}) mode has been changed to stop
Jun 20 22:35:00 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:294 notify_playerModeChange: - audioState is 0
Jun 20 22:35:05 squeezeplay: INFO squeezeplay.applets - AppletManager.lua:708 store settings: Playback
Jun 20 22:35:18 squeezeplay: INFO applet.SlimDiscovery - SlimDiscoveryApplet.lua:517 notify_playerPower: true
Jun 20 22:35:18 squeezeplay: INFO squeezeplay - JiveMain.lua:207 Turn soft power on
Jun 20 22:35:18 squeezeplay: WARN squeezebox.server - SlimServer.lua:606 wakeOnLan(): SKIPPING WOL, self.mac: nil, self:isSqueezeNetwork(): true
Jun 20 22:35:25 squeezeplay: INFO squeezeplay.applets - AppletManager.lua:708 store settings: Playback
Jun 20 22:35:48 squeezeplay: INFO applet.ScreenSavers - ScreenSaversApplet.lua:280 activating Clock screensaver
Jun 20 22:36:00 squeezeplay: WARN net.thread - NetworkThread.lua:146 network thread timeout for Task(SocketHttp {mysqueezebox.com_Request}(R))
Jun 20 22:36:18 squeezeplay: INFO applet.SlimDiscovery - SlimDiscoveryApplet.lua:517 notify_playerPower: false
Jun 20 22:36:18 squeezeplay: INFO squeezeplay - JiveMain.lua:200 Turn soft power off
Jun 20 22:36:18 squeezeplay: INFO applet.ScreenSavers - ScreenSaversApplet.lua:280 activating Clock screensaver
Jun 20 22:36:25 squeezeplay: INFO squeezeplay.applets - AppletManager.lua:708 store settings: Playback
Jun 20 22:38:00 squeezeplay: INFO applet.SlimMenus - SlimMenusApplet.lua:441 _menuSink(1) nil menuDirective: add isCurrentServer:true
Jun 20 22:38:00 squeezeplay: INFO applet.SlimMenus - SlimMenusApplet.lua:713 hiding any 'connecting to server' popup after menu response from current server, SlimServer {mysqueezebox.com}
Jun 20 22:38:00 squeezeplay: INFO applet.AlarmSnooze - AlarmSnoozeApplet.lua:255 notify_playerLoaded(LocalPlayer {Squeezebox Radio})
Jun 20 22:38:00 squeezeplay: INFO applet.ChooseMusicSource - ChooseMusicSourceApplet.lua:543 Hiding popup, exists?: nil
Jun 20 22:38:01 squeezeplay: INFO applet.SlimMenus - SlimMenusApplet.lua:441 _menuSink(1) nil menuDirective: add isCurrentServer:true
Jun 20 22:38:01 squeezeplay: INFO applet.SlimMenus - SlimMenusApplet.lua:713 hiding any 'connecting to server' popup after menu response from current server, SlimServer {mysqueezebox.com}
Jun 20 22:38:01 squeezeplay: INFO applet.AlarmSnooze - AlarmSnoozeApplet.lua:255 notify_playerLoaded(LocalPlayer {Squeezebox Radio})
Jun 20 22:38:01 squeezeplay: INFO applet.ChooseMusicSource - ChooseMusicSourceApplet.lua:543 Hiding popup, exists?: nil
Jun 20 22:38:01 squeezeplay: INFO applet.SlimDiscovery - SlimDiscoveryApplet.lua:517 notify_playerPower: true
Jun 20 22:38:01 squeezeplay: INFO squeezeplay - JiveMain.lua:207 Turn soft power on
Jun 20 22:38:01 squeezeplay: WARN squeezebox.server - SlimServer.lua:606 wakeOnLan(): SKIPPING WOL, self.mac: nil, self:isSqueezeNetwork(): true
Jun 20 22:38:01 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:292 notify_playerModeChange: player (LocalPlayer {Squeezebox Radio}) mode has been changed to play
Jun 20 22:38:01 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:294 notify_playerModeChange: - audioState is 1
Jun 20 22:38:01 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:131 notify_playerAlarmState received for LocalPlayer {Squeezebox Radio} with alarmState of active
Jun 20 22:38:01 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:133 **************************** notify_playerAlarmState received: active 0
Jun 20 22:38:01 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:626 _stopTimer: stopping RTC fallback alarm timer
Jun 20 22:38:01 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:426 openAlarmWindow()server true
Jun 20 22:38:01 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:466 openAlarmWindow: called with `server` - audioState is 1
Jun 20 22:38:05 squeezeplay: INFO squeezeplay.applets - AppletManager.lua:708 store settings: Playback
Jun 20 22:38:11 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:396 _pollDecodeState(server): audioState is 1
Jun 20 22:38:11 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:235 alarm_sledgehammerRearm(_pollDecodeState): server alarm in progress - audioState is 1
Jun 20 22:38:18 squeezeplay: INFO applet.SlimDiscovery - SlimDiscoveryApplet.lua:517 notify_playerPower: false
Jun 20 22:38:18 squeezeplay: INFO squeezeplay - JiveMain.lua:200 Turn soft power off
Jun 20 22:38:18 squeezeplay: INFO applet.ScreenSavers - ScreenSaversApplet.lua:280 activating Clock screensaver
Jun 20 22:38:18 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:276 Power turned off while alarm in progress. By design, turn the alarm off
Jun 20 22:38:18 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:604 _alarmOff: server alarm canceled - alarmInProgress state (server)
Jun 20 22:38:18 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:639 stopping decodeStatePoller
Jun 20 22:38:18 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:618 _alarmOff: send stopAlarm to connected server
Jun 20 22:38:19 squeezeplay: INFO applet.SlimMenus - SlimMenusApplet.lua:441 _menuSink(1) nil menuDirective: add isCurrentServer:true
Jun 20 22:38:19 squeezeplay: INFO applet.SlimMenus - SlimMenusApplet.lua:713 hiding any 'connecting to server' popup after menu response from current server, SlimServer {mysqueezebox.com}
Jun 20 22:38:19 squeezeplay: INFO applet.AlarmSnooze - AlarmSnoozeApplet.lua:255 notify_playerLoaded(LocalPlayer {Squeezebox Radio})
Jun 20 22:38:19 squeezeplay: INFO applet.ChooseMusicSource - ChooseMusicSourceApplet.lua:543 Hiding popup, exists?: nil
Jun 20 22:38:19 squeezeplay: INFO applet.SlimDiscovery - SlimDiscoveryApplet.lua:517 notify_playerPower: true
Jun 20 22:38:19 squeezeplay: INFO squeezeplay - JiveMain.lua:207 Turn soft power on
Jun 20 22:38:19 squeezeplay: WARN squeezebox.server - SlimServer.lua:606 wakeOnLan(): SKIPPING WOL, self.mac: nil, self:isSqueezeNetwork(): true
Jun 20 22:38:20 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:292 notify_playerModeChange: player (LocalPlayer {Squeezebox Radio}) mode has been changed to pause
Jun 20 22:38:20 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:294 notify_playerModeChange: - audioState is 0
Jun 20 22:38:20 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:131 notify_playerAlarmState received for LocalPlayer {Squeezebox Radio} with alarmState of set
Jun 20 22:38:20 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:133 **************************** notify_playerAlarmState received: set 1277152680
Jun 20 22:38:20 squeezeplay: INFO applet.AlarmSnooze - AlarmSnoozeApplet.lua:210 storing epochseconds of next alarm: 1277152680
Jun 20 22:38:20 squeezeplay: INFO squeezeplay.applets - AppletManager.lua:708 store settings: AlarmSnooze
Jun 20 22:38:20 squeezeplay: WARN applet.AlarmSnooze - AlarmSnoozeApplet.lua:693 _startTimer: starting RTC fallback alarm timer (86400000)
Regards
/Dolphe
bluegaspode
2010-06-20, 14:44
Dolph,
thanks for this log.
I cannot find anything special in it ... except that 18seconds after the alarm sounds the Radio gets a signal to turn itself off:
Jun 20 22:38:18 squeezeplay: INFO applet.SlimDiscovery - SlimDiscoveryApplet.lua:517 notify_playerPower: false
Jun 20 22:38:18 squeezeplay: INFO squeezeplay - JiveMain.lua:200 Turn soft power off
When you are on MySqueezebox.com - do you see any devices that don't belong to you (I'm thinking of some strange scenarios, where maybe this alarms triggers another Radio and another person gets upset and turns his Radio off) ?
Also I think this log is very valuable information for official Logitech support as it proves that your Radio gets a wrong signal from the mysqueezebox.com server.
At least it might give you the fast lane to the second tier (without having to do factory resets, network checks or support-people that don't believe you). I hope that this can be resolved very fast for you - please keep us updated !
I cannot find anything special in it ... except that 18seconds after the alarm sounds the Radio gets a signal to turn itself off:
Ya now when i check i can see the "off" screen flashing and then the "now playing" screen comes back and the alarm is off.
So sequence is: Alarm activates-> snooze screen->off screen->now playing screen
When you are on MySqueezebox.com - do you see any devices that don't belong to you (I'm thinking of some strange scenarios, where maybe this alarms triggers another Radio and another person gets upset and turns his Radio off) ?
Ohhh that would be really awsome making alarms go off at other ppl *evil grin*
But no i cant see anything strange in the MySB its only my device with my ip and my mac adress.
Also I think this log is very valuable information for official Logitech support as it proves that your Radio gets a wrong signal from the mysqueezebox.com server.
At least it might give you the fast lane to the second tier (without having to do factory resets, network checks or support-people that don't believe you). I hope that this can be resolved very fast for you - please keep us updated !
Will make a post on the logitech support forum tomorrow, and post back any answer i get.
Thanks again for your help
Regards
/Dolphe
bluegaspode
2010-06-20, 17:37
Will make a post on the logitech support forum tomorrow, and post back any answer i get.
Rather write them a mail (http://logitech-en-amr.custhelp.com/cgi-bin/logitech_en_amr.cfg/php/enduser/ask.php?section=contact&tabs=1,3,2,4,5).
You get a ticket and they are 'forced' to answer in reasonable time *evil grin*.
Philip Meyer
2010-06-21, 15:52
>2. No autoplay after pressing the power button
I disagree that it should autoplay; I have many other devices that don't resume when I turn them back on, but do resume if I hit play.
e.g. DVD player, Video Player, Sky+, iPod.
However, I think there's an option (in local SBS) to change the functionality to do what you want. In web UI Player preferences > Audio, there's a "Power On Resume" option, from which you can choose "Pause at power off / Resume at power on".
I don't use MySB.com, so I can't remember if there's a way of choosing this option there. But rather than suggest that it should do X instead of Y, if there is a change it should be configurable like SBS is.
Phil
Philip Meyer
2010-06-21, 15:58
>3. Font size of the clock in the alarm window
>For me this is still a bug or lets say false spec because if you cannot
>read the clock from 1m away it is useless to display it.
>
I've said before, but not repeated myself for some time, so here goes again ;-)
Many people have different views on what should happen when an alarm starts. Some people only want a screen with snooze/off options; some only want a clock; some don't want anything special (standard Now Playing screen).
I think the best compromise would be for an Alarm Screensaver setting, for the user to choose the option that suits them best.
I believe that Erland produced a plugin/addon/patch to achieve this, but I use my trusty SB3 for bedroom alarm clock, with MusicInfoScreensaver defining what gets displayed, which is perfect for me.
gcparris
2010-06-22, 02:59
Hi there, just to confirm that I am getting exactly the same problems with the alarm as Dolph. The alarm comes on for a few seconds and then turns off.
This makes the radio completely useless for me as the only reason I purchased it was for the flexible alarm system.
Regards,
Gareth.
Ya now when i check i can see the "off" screen flashing and then the "now playing" screen comes back and the alarm is off.
So sequence is: Alarm activates-> snooze screen->off screen->now playing screen
Ohhh that would be really awsome making alarms go off at other ppl *evil grin*
But no i cant see anything strange in the MySB its only my device with my ip and my mac adress.
Will make a post on the logitech support forum tomorrow, and post back any answer i get.
Thanks again for your help
Regards
/Dolphe
First let me say that I love this radio (not as much as my two booms and my two receivers and my controller, but I love this radio). I have very bad radio reception on my regular radios, so now I can listen to all my local stations. I can also listen to podcasts and I also am a Sirius radio subscriber. Plus, lots of other stuff like Pandora, Slacker, etc.
But, the 7.5.1 update was a total flop. I don't know that anything changed.
1. When I first turn the radio on, it plays for less than 30 seconds and then turns off (same behavior as pre-upgrade).
2. The alarm turns on but shuts off after a few seconds (no matter if it is set on Sirius or Pandora - have not tried other stuff).
3. Once alarm turns off by itself, it never sounds a snooze alarm.
4. Sometimes, the "art" doesn't update when I change from one radio station to another or from one Sirius channel to another. When that happens, the radio must be rebooted (if that's the right term - hold power button and let it shut down then press the power and let it boot up again).
I wonder what the upgrade fixed? Didn't they do any testing before they released this thing?
I use Mysqueezebox.com almost exclusively. From what I've read here, perhaps the behavior would be better if i used squeezebox server but the fact is, my computer is normally off.
In summary, I think the radio is great. It would be really wonderful if they got some of the bugs out of it.
You are not alone. I have the all the same issues. The problems not going away from 7.42 to 750 to 7.51. Logitech hired cheap programmers I guess,
First let me say that I love this radio (not as much as my two booms and my two receivers and my controller, but I love this radio). I have very bad radio reception on my regular radios, so now I can listen to all my local stations. I can also listen to podcasts and I also am a Sirius radio subscriber. Plus, lots of other stuff like Pandora, Slacker, etc.
But, the 7.5.1 update was a total flop. I don't know that anything changed.
1. When I first turn the radio on, it plays for less than 30 seconds and then turns off (same behavior as pre-upgrade).
2. The alarm turns on but shuts off after a few seconds (no matter if it is set on Sirius or Pandora - have not tried other stuff).
3. Once alarm turns off by itself, it never sounds a snooze alarm.
4. Sometimes, the "art" doesn't update when I change from one radio station to another or from one Sirius channel to another. When that happens, the radio must be rebooted (if that's the right term - hold power button and let it shut down then press the power and let it boot up again).
I wonder what the upgrade fixed? Didn't they do any testing before they released this thing?
I use Mysqueezebox.com almost exclusively. From what I've read here, perhaps the behavior would be better if i used squeezebox server but the fact is, my computer is normally off.
In summary, I think the radio is great. It would be really wonderful if they got some of the bugs out of it.
With the risk of sounding totally dim witted...
Have you tried a factory reset of the thing (just note the email used for your mysb.com account ) .
My experience with the controller (almost same software) beta testing dozens of version, have taught me that sometimes even the *working* version of the fw will not behave well until a factory reset is done.
Hopefully I have not sent yall on a run around wasting some time.
vdeknock
2010-06-24, 22:53
I never use MySB as I have a vortexbox running 24/7. Radio has been rock solid and has woken me up each morning without fail. (Fallback alarm has gone off once in the last 2-3months).
I use a number of plugins and patches to fix issues that have been raised in the thread. The Patch for the Alarm to make it display a large clock is great, and fixes what I agree is an issue.
I sometimes have issues with radio streams, but this is normally an issue with my net connection of the wireless network in my house. ie the kids are moving large files or watching youtube on the network at the same time.
I have set the alarm to play a playlist called alarm with a single track, which I change. Once awake I then push the preset to get the radio stream working. While not what everyone wants is works and stops all the issues with the fallback alarm starting because of the bufferring of the stream.
The radio does work with a dedicated server running, but like most things can always be improved.
With the risk of sounding totally dim witted...
Have you tried a factory reset of the thing (just note the email used for your mysb.com account ) .
My experience with the controller (almost same software) beta testing dozens of version, have taught me that sometimes even the *working* version of the fw will not behave well until a factory reset is done.
Hopefully I have not sent yall on a run around wasting some time.
Thanks for the input. However, I just did a full factory reset. The behavior is exactly the same. as described in my 6-23-10 post.
You are not alone. I have the all the same issues. The problems not going away from 7.42 to 750 to 7.51. Logitech hired cheap programmers I guess,
I have the same problem too since firmware 7.5.0
0xdeadbeef
2010-06-25, 10:06
Indeed some things have changed from 7.5.0 to 7.5.1. E.g. the Radio doesn't lose its default screensaver/background settings any more all the time. Also with 7.5.0, in like 6 of 10 cases, the backup alarm came up either at once or after a few seconds. Since 7.5.1, there are less backup alarms and much more cases where no alarm is started at all.
Now really, this is ridiculous. In the 8 months that I own the Radio, not one of the main issues has been fixed by Logitech. Instead things are getting rather worse than any better.
If I was somehow involved in the design or development process of this piece of crap software, I'd start to think of a different career. In a professional company, this time would be sufficient to develop a large software project from scratch and they don't even manage to get an alarm clock to work. There is simply no word for how pathetic this is.
1. The alarm clock screen shows only a very small clock that you cannot read even if you are only 1m away.
--> This has been mentioned already many times in the forum but it seems that this is not fixed. Unfortunately, the patch installer seems not to work any more so for me there is currently no solution for this.
--> This is a real bug for me and one reason why I think about returning the squeezebox radio. For me reading the clock while the alarm is on is a basic requirement!
This is not a bug, as it works as designed. So what one need to do is to create an enhancement request.
2. No auto play at startup:
If you listen to a internet radio station and then switch off the radio (standby mode) and then wake up in the morning (by yourself and not through an alarm) and you want to listen to the radio again you have to switch on the SB radio and then hit the play button.
--> This is almost not possible in a dark bedroom and this is a basic feature for me! Every radio starts playing, if you switch it on! If this is not fixed soon, I will sell the radio because it cannot be used as a bedroom radio this way!!!
This is a configuration item under
Player -> Audio -> Power on Resume
where you can choose
"Pause at power off / resume at power on"
If that does not work. Then I would consider it as bug.
Regards, Torsten
...........
"Pause at power off / resume at power on"
This option is only available when running SBS on the computer.
This is not an option when using MySB.com as Jukebox is doing.
firegrip
2010-06-27, 09:00
I am also a new owner with a few problems / complaints. 1st, my scroll will stop after a few songs, and will not display the current song or station info. Even if i change preset stations.
2nd, why is it that when I power the unit on from standby I have to hit play? Thats stupid if its an upgrade... why whould I want to do that?? Turn the unit on, music plays... just like a regular radio. I have rebooted the unit several times and the screen problem goes away, for now.
I sent a message to Logitech Customer Support expressing my displeasure at the fact that the 7.5.1 firmware updated did not fix the key issues that many people are having - radio turns off by itself after turn on, alarm functions do not work properly when using MSB.com and the artwork not updating properly.
The response was surprising - it is below in QUOTES. Please let me know what you think about this.....
"At this point we are actually replacing Radios for this reason. We believe it is not a firmware bug that we can fix, but actually a hardware issue with overheating.
Our Engineers monitor the forums, but our support staff does not, to answer your question there.
Can you supply me with your shipping address and phone number so I can setup a replacement Radio?"
I sent a message to Logitech Customer Support expressing my displeasure at the fact that the 7.5.1 firmware updated did not fix the key issues that many people are having - radio turns off by itself after turn on, alarm functions do not work properly when using MSB.com and the artwork not updating properly.
The response was surprising - it is below in QUOTES. Please let me know what you think about this.....
"At this point we are actually replacing Radios for this reason. We believe it is not a firmware bug that we can fix, but actually a hardware issue with overheating.
The hardware on the Radio is pretty limited, so if you do something that push it over the limit it can reboot spontaneously, I've seen this several times myself when using third party stuff. If we have an overheating issue, it could cause all kinds of strange problems.
I would say that you should take their offer to get a replacement, I'm pretty sure it won't solve all the problems you mention but it might solve some of them. They wouldn't offer a replacement unless they know it might solve some of the problems.
If you choose to get a replacement, please report if it solved some of your problems.
Before you return it, on your Radio go to Settings > Advanced > Diagnostics
The second item is Hardware Version.
I'd be curious to know if your replacement is a different version. ;)
Before you return it, on your Radio go to Settings > Advanced > Diagnostics
The second item is Hardware Version.
I'd be curious to know if your replacement is a different version. ;)
I'll be sending it back in the morning. For the record, the hardware version of the unit being returned is "5".
I'll let you know what the version number of the new one is. And I'll report back on whether the new unit clears up the issues.
I'll be sending it back in the morning. For the record, the hardware version of the unit being returned is "5".
I'll let you know what the version number of the new one is. And I'll report back on whether the new unit clears up the issues.
Please let us know if the new unit work better.
Mine also hardware version 5 and has the same problems. Updating firmware from 7.4.2 to 7.5.0 to 7.5.1 not fixing the problems. I feel the display is warm after turn on for a while. I don't know if this is the source of the problem. The temporarily fix is rebooting the radio then it will work properly for a day or two. Now I just power it off every morning and turn it on when I come back from work. I hope there is a better solution.
Please let us know if the new unit work better.
Mine also hardware version 5 and has the same problems. Updating firmware from 7.4.2 to 7.5.0 to 7.5.1 not fixing the problems. I feel the display is warm after turn on for a while. I don't know if this is the source of the problem. The temporarily fix is rebooting the radio then it will work properly for a day or two. Now I just power it off every morning and turn it on when I come back from work. I hope there is a better solution.
I will post when I receive the new Radio.
I moved one of my two Squeezebox Booms to the nightstand and used it for my alarm this morning. It worked flawlessly. Both booms have warm screens. In the words of another forum poster, the Squeezebox Boom is a pleasure to own.
Often when listening to radio, the alarm will stop the radio, but no alarm is played. When manually pressing play, the radio will continue, but now at Alarm volume level.
Hardware version is 4
No local server
Wired lan connection
/MF
CorePrime
2010-06-30, 05:42
"We believe it is not a firmware bug that we can fix, but actually a hardware issue with overheating"
How is this possible? The radio didn't automatically shutoff until the last couple firmware updates. After it shuts off, I can turn it on and it stays on. So why doesn't it overheat and turn off again? I don't think Logitech knows what they are doing. I only bought this radio because it supported Shoutcast, what a mistake. Nothing but trouble. I have a Harmony remote that is junk. No more Logitech for me.
"We believe it is not a firmware bug that we can fix, but actually a hardware issue with overheating"
How is this possible? The radio didn't automatically shutoff until the last couple firmware updates.
Exactly. Do they STILL not grasp that these drop-offs didn't occur until 7.5.0?? I'm not a programmer, but doesn't basic diagnostic logic suggest that you go looking for the problem in code that changed between 7.4 and 7.5? Honestly, if were me, I would start over with version 7.4.2, then (carefully) try to build from scratch whatever new functionality was introduced in 7.5 - TESTING ALL THE WAY. If the problem lies with MySqueezebox.com, same approach - throw out the enhancements since February and start again.
Just wanted to post and say that I am also having the same alarm issue as others. This is pretty frustrating because I set two alarms in the morning (one being the Squeezebox) to basically safeguard each other in case one doesn't go off. Unfortunately, if my other alarm craps out now, I'll be SOL since the Squeezebox has been more silent than not in the morning.
Some might say that you shouldn't rely on a Squeezebox alarm since it wasn't specifically made to be an alarm clock, but personally I bought the Squeezebox partially because of its alarm clock feature and I expected it to work -- and if it didn't, a backup sound would wake me up. Hearing nothing at all which could cause me to miss getting up for work is just unacceptable.
bluegaspode
2010-06-30, 17:40
Some might say that you shouldn't rely on a Squeezebox alarm since it wasn't specifically made to be an alarm clock, but personally I bought the Squeezebox partially because of its alarm clock feature and I expected it to work -- and if it didn't, a backup sound would wake me up. Hearing nothing at all which could cause me to miss getting up for work is just unacceptable.
Could you confirm, that you schedule your alarm ONLY directly on the Radio (instead of via the web-interface) ?
I never had a failing backup alarm since 7.4.2 version where the backup-alarm code was fixed.
Could you also write if you use a local server or mysqueezebox.com ?
There are several tweaks for both scenarious to make the alarm play the wanted sound instead of the backup-alarm (which should always sound, regardless of your server type)
After numerous complaints to customer support and no relief from the 7.5.1 upgrade, I was told that Logitech was now replacing radios as they believe that the streaming issue (and others that I have) are caused by a hardware issue. They mentioned "overheating" They asked me to send my radio in for replacement. New radio arrived yesterday. The hardware version is "5". This is the same hardware version as the previous one. I set up the new radio. It downloaded firmware 7.5.1. I turned the radio on using a preset. The streaming stopped within 10 seconds. Same exact problem as I had before.
Waste of my time. But at least we know it is not a hardware issue. (But we all knew that before).
Is there any word on when these bugs will actually be fixed?
Do they actually test these firmware releases before they are released?
New radio arrived yesterday. The hardware version is "5". This is the same hardware version as the previous one. I set up the new radio. It downloaded firmware 7.5.1. I turned the radio on using a preset. The streaming stopped within 10 seconds. Same exact problem as I had before.
Please make sure to inform the support that it didn't help, just to avoid that other users have to waste time the same way as you had to.
Is there any word on when these bugs will actually be fixed?
I think you will get the best answer through the official support channels, you are only going to get guesses on these forums. Bugging the support about it will make them aware of the problem and it will hopefully also make them improve their internal communication channels so the support staff knows when a new release is planned, this doesn't currently always seem to be the case based on some forum posts here.
If you find the bug in the bug database at bugs.slimdevices.com, you can look at the "Target Milestone" field to get an indication which release it's planned for. If it's "7.5.x" it's planned for the next 7.5 release although some 7.5.x bugs might probably be postponed to a future 7.5 release since there are a lot of them now.
Do they actually test these firmware releases before they are released?
Yes and it works good for a lot of people. The problem is that most of these bugs depends on the environment, typically some network problem or server problem, it might be your local network or it might be your ISP network connection to MySB.com or it might be internet radio station providing the stream or the MySB.com servers. It's often hard to tell exactly which one is causing the problems.
They are still bugs that needs to be fixed so this is no excuse, I'm just saying that it can be pretty hard to find some of these things when running tests in a test facility prior to the release. We don't have much information about how Logitech performs the testing, so it's hard to tell if they have done as much as they realistically can do prior to the release. Still, it's really not our responsibility to tell them how to test things, we should only make sure to tell them through the official support channels when the quality is insufficient. Or in the "Beta" section of this forum if we are participating in official beta testing of the software prior to a release. Yes, I know it might feel like we are beta testing the official release also but I think it's better to report those problem through the official support channels.
Hopefully someone at Logitech is working to solve these issues as soon as possible, but it's hard to tell with the current level of communication they have with the community.
I kinda suspected you would end up with the same hardware exhibiting the same issues. :(
As erlend suggests your issues are not a universal problem for all users, which would indicate not being a hardware problem.
My Radio does not turn itself ON or OFF under any conditions including selecting a Preset from Standby. For me this works as expected.
How/what/why it works for some and not others I haven't a clue.
If you provide the station details (name, url, format, etc..) I can save the same station as a Preset and try to duplicate your issue.
But I'm betting it will function fine for me.
This is in response to Erland and Toby10. Thanks for your posts.
First I’d like to clarify that I’m not complaining. If I were to complain, my posts would be a lot longer. My complaints have been expressed through the appropriate channels – customer support. And my experiences and assistance have been expressed in bug reports. I’ve had an open back and forth email dialogue with tech support.
Once I received the new radio and set it up, it became apparent that nothing had changed. My first stop was not to come to the forums. My first action was to report back to tech support. My second action was to post an update to one of the bug reports. My last action was to come here and simply report back since someone had expressed curiosity about what the hardware version number was. Sorry if some of my frustration emerged.
With respect to the installed environment for this radio, I can tell you that my too Booms work flawlessly. My two receivers and my controller also work flawlessly. I know that doesn’t mean anything but given that as a foundation, I’d expect the radio to work also.
With respect to the radio turning off after start up, it is a problem no matter what is playing when I’m connected to MSB. This includes Sirius Radio, Pandora, any radio stream through RadioTime and anything I listen to through the Podcast Player. With respect to it turning on after I shut it off, I don’t think it matters what it was playing when I last turned it off. With respect to the alarm, it is simply unreliable no matter what it is set to play when it triggers. I have a strong impression that the device becomes far more stable when connected to SBS rather than MSB. I know that I can avoid much of this by just running SBS.
I enjoy being a beta tester. I’ve beta tested software. I like looking for issues and solutions. I’m not a programmer but I enjoy this stuff. Unfortunately, I didn’t sign up to be a beta tester on this device. I realized a long time ago, however, that I am beta testing.
The only thing that threw me a bit here is I simply have the feeling they asked me to send my radio in because they are at a loss. If they still believe this is a hardware problem it means their current level of communication with the community is not great. While I have not tried it myself, it seems pretty clear based on what I've read that many of my problems did not exist prior to 7.5. Doesn't sound like a hardware problem, but I don't know enough to make a firm statement.
I’m hoping they solve this also.
If I hear anything productive from tech support, I'll post it here in the hope that it helps someone.
This is in response to Erland and Toby10. Thanks for your posts.
Once I received the new radio and set it up, it became apparent that nothing had changed. My first stop was not to come to the forums. My first action was to report back to tech support. My second action was to post an update to one of the bug reports. My last action was to come here and simply report back since someone had expressed curiosity about what the hardware version number was.
Thanks, this is exactly how users with problems should make Logitech aware of them. I wish more users would follow your example.
Sorry if some of my frustration emerged.
No problem, it's just that we are as frustrated as you are because we have no idea if Logitech is working on this or not. We hope they are but we don't really have any proof.
With respect to the installed environment for this radio, I can tell you that my too Booms work flawlessly. My two receivers and my controller also work flawlessly. I know that doesn’t mean anything but given that as a foundation, I’d expect the radio to work also.
From what I've seen I think the Receiver and Boom are a bit less dependent on mysqueezebox.com so that might explain why they work better.
Some questions, just to try to help you, sorry if I'm asking questions about something you have posted somewhere else where I could have read it.
Are you playing audio directly on the Controller or is it just used for controlling the other players ?
Is the alarm unreliable because it doesn't play anything and just stays silent, or is it unreliable because you sometimes get the loud fallback alarm ?
If the problem is the fallback alarm, I have the same problem in my setup. In my setup it's caused by a brief disconnection with the server, probably due to local network problems as I'm playing local music.
Could you think of anything that happens when it's turned on after you have shut it down ?
- An SBS installation on local network is started or restarted or shut down ?
- Some computer on local network is going out of hibernate/suspend mode ?
- Some computer on local network is started or restarted ?
- You change what's playing on some of the other players ?
- Some network connection problem with mysqueezebox com ?
Do you shut it down completely by holding power for a while, or do you just switch it to the off screen saver ?
...........
First I’d like to clarify that I’m not complaining....
I sure didn't think you were. :)
Let me know if you want me to try something on my end for comparison.
Some questions, just to try to help you, sorry if I'm asking questions about something you have posted somewhere else where I could have read it.
Are you playing audio directly on the Controller or is it just used for controlling the other players ?
I welcome all of your questions – thanks.
Is the alarm unreliable because it doesn't play anything and just stays silent, or is it unreliable because you sometimes get the loud fallback alarm ?
It varies. Sometimes it works fine but when “snoozed” it does not re-trigger. Sometimes it gives the fall back alarm. Sometimes it triggers properly but shuts off after a few seconds.
If the problem is the fallback alarm, I have the same problem in my setup. In my setup it's caused by a brief disconnection with the server, probably due to local network problems as I'm playing local music.
Could you think of anything that happens when it's turned on after you have shut it down ?
- An SBS installation on local network is started or restarted or shut down ?
- Some computer on local network is going out of hibernate/suspend mode ?
- Some computer on local network is started or restarted ?
- You change what's playing on some of the other players ?
- Some network connection problem with mysqueezebox com ?
All of the issues I have are when connected to MSB.com. I rarely am connected to SBS. And SBS is rarely running. When the alarm triggers in the morning, there is no computer on. The radio is connected directly to MSB.com No other players are up and running when this happens. Not sure if it is a network connection problem. I’ve often done testing of the alarm when the radio is within five feet of the wireless modem and the reception is listed as 100%. I have not tried it with an Ethernet cable.
When it turns on by itself, it is usually within just a few seconds of being turned off (switched off to screen saver). That’s at a point where there are no other players on and no computer on.
Do you shut it down completely by holding power for a while, or do you just switch it to the off screen saver ?
I don’t shut it down completely unless I have to (which frequently I must since the “art” gets frozen on the last thing that has played – which is one of the other bugs). Should I be shutting it down completely whenever I shut the radio off?
It varies. Sometimes it works fine but when “snoozed” it does not re-trigger. Sometimes it gives the fall back alarm. Sometimes it triggers properly but shuts off after a few seconds.
Do you have the same problem if you play the same music stream normally and not through the alarm ?
Do you have the same problem independent which type of internet radio station you configure to be played when the alarm triggers ?
What does the display indicate after you have snoozed it ? If I remember correctly there is some indication that the alarm is snoozed and not turned off. I need to check to know exactly how it looks like since I'm not using snooze myself, maybe someone else knows ?
All of the issues I have are when connected to MSB.com. I rarely am connected to SBS. And SBS is rarely running. When the alarm triggers in the morning, there is no computer on. The radio is connected directly to MSB.com No other players are up and running when this happens. Not sure if it is a network connection problem. I’ve often done testing of the alarm when the radio is within five feet of the wireless modem and the reception is listed as 100%. I have not tried it with an Ethernet cable.
Try with an ethernet cable to see if the local network causes the problems.
When it turns on by itself, it is usually within just a few seconds of being turned off (switched off to screen saver). That’s at a point where there are no other players on and no computer on.
Do you only see the problem when you turn it off when something is playing or do you have the same problem if it's stopped before you turn it off ?
I don’t shut it down completely unless I have to (which frequently I must since the “art” gets frozen on the last thing that has played – which is one of the other bugs). Should I be shutting it down completely whenever I shut the radio off?
I'm guessing it won't turn on spontaneously if you shut it down completely ?
So the problem where the Radio is turned on after a few seconds only happens when you activate the off screen saver ?
Which screen saver do you use as the off screen saver ?
Questions from Erland
Erland - thanks so much for taking the time to help with this. The responses might take a little bit of time. I want to make sure that I give you accurate responses. Some issues happen only frequently rather than all the time. Give me a few days.
Also, I received a reply from tech support on my expression of frustration about why they made me swap the hardware. Their response was they were trying to eliminate the hardware as an issue. They have also asked me a number of questions about readings from the diagnostic screens such as Power readings, MAC address, etc. I'll keep you posted on this as well.
Thanks again!
Questions from Erland
Erland:
I’ve spent some time observing the behavior of the Radio over the last several days. The alarm function seems to have stabilized a bit. To keep it as uncomplicated as possible, I’ll focus on the radio turning on and off by itself in this post.
First, some foundational comments:
The behaviors described here happen whether it is connected to wireless network or to Ethernet cable.
Radio is connected to MSB.com. Not connected to SBS. SBS is off (as is the computer which has SBS loaded).
There are no other computers on either hard wired or wireless. The computers are off.
In my descriptions below, when I say “off” or “turn off” I mean just a short push of the power button, not a full shut down. When I say shut down, I mean a press and hold of the power button.
My screensavers are as follows – Off (Digital clock – Black); Stop – Analog Clock; When playing – Now Playing; Screensaver delay is 30 seconds
Normally, when I turn the radio off, I do a short press of the power button. I don’t do a shut down unless I am looking to reset the radio.
If I do a shut down, it doesn’t normally come back on by itself (but sometimes it does – not often).
The following sequence can be duplicated more than 90% of the time.
1. The radio is off (Off screensaver displayed)
2. I turn it on using the power button – It has a “pause” indicator showing in the lower left hand corner
3. It turns off by itself within about 15 seconds
4. It turns on by itself in a minute. Displays the last stream’s art. Shows a “Pause” icon in the lower left hand corner.
5. It goes into the “Stop” screensaver (digital clock) after 30 seconds
6. It remains in this state until I intervene
7. I press the Power button – it goes to a screen showing the last thing that played (with a pause indicator in lower left hand corner)
8. I press the power button again – it turns off
9. It turns on by itself in about a minute with a stop indicator in lower left hand corner
10. It goes to the “Off” screensaver in about 30 seconds
11. It goes off by itself in about 30 seconds
12. It stays off.
The following sequence can also be duplicated more than 75% of the time:
1. Turn the radio on with a preset or turn it on with the power button and then hit a preset. Radio streams (stream can be either a radio station, Pandora or Sirius station).
2. Radio turns off within about 15 seconds
3. Radio turns itself back on usually with the “Play” icon in the lower left hand corner
4. I press the pause button; icon changes to “Pause”
5. I press the play button and then stream restarts
6. At this point, it usually continues to play
7. I turn the radio off
8. Unit turns itself on within a minute (with stop icon in lower left hand corner)
9. After 30 seconds it goes to the “Stop” screensaver
10. Unit turns itself off (and stays off)
Very strange, but very consistent.
The only "event" that disrupted the above behavior today was a power outage that lasted 2 hours. Once the power came back, all of the above behavior disappeared and the radio worked like it is supposed to. After a while, it was back to the "odd" behavior above.
Any ideas or questions are welcome.
snarlydwarf
2010-07-13, 15:23
Radio is connected to MSB.com. Not connected to SBS. SBS is off (as is the computer which has SBS loaded).
My guess is that this is actually a bug on MSB since I haven't seen a report of the "I think I will turn off" with SBS. For some mysterious reason MySB is deciding the radio needs to be off.
It could be something such as an alarm state being incorrectly tracked ("oh, wait you're playing and the alarm period is over, so off you go!").
VERY good information in that post: have you filed a bug report with that over on bugs.slimdevices.com? That information and perhaps pulling logs for your account ("what the heck, why does the server log that it's turning your radio off")... no clue how spammy their debugging logs are, should help narrow it down a ton.
Again, kudos for such a detailed report (including noting the different screensavers, since 'off' is just a state of mind, knowing which off is meant is useful info).
VERY good information in that post: have you filed a bug report with that over on bugs.slimdevices.com?
There are just so many open posts there related to this or similar issues.
I'm thinking about logging my post, as is, to the trail on bug 16170. What do you think?
........
The following sequence can be duplicated more than 90% of the time.
1. The radio is off (Off screensaver displayed)
2. I turn it on using the power button – It has a “pause” indicator showing in the lower left hand corner
3. It turns off by itself within about 15 seconds
4. It turns on by itself in a minute. Displays the last stream’s art. Shows a “Pause” icon in the lower left hand corner.
5. It goes into the “Stop” screensaver (digital clock) after 30 seconds
6. It remains in this state until I intervene
7. I press the Power button – it goes to a screen showing the last thing that played (with a pause indicator in lower left hand corner)
8. I press the power button again – it turns off
9. It turns on by itself in about a minute with a stop indicator in lower left hand corner
10. It goes to the “Off” screensaver in about 30 seconds
11. It goes off by itself in about 30 seconds
12. It stays off.
.............
Any ideas or questions are welcome.
For my Radio on Mysb:
1, 2, 3 = same (I'm guessing it enters "off" mode because nothing is playing)
4 = does not turn itself on
5 = does not apply cuz #4 did not occur
6, 7, 8 = same
9 = does not turn itself on
10, 11 = does not apply cuz #9 did not occur
12 = same
Let me know if you want me to try some different settings etc.. to try to duplicate your issue.
Radio 7.5.1 r8837
note: I do not use any alarms
snarlydwarf
2010-07-13, 16:28
There are just so many open posts there related to this or similar issues.
I'm thinking about logging my post, as is, to the trail on bug 16170. What do you think?
Ugh, towards the end of the comments it becomes This Problem, but it sure doesn't start out that way.
I'd guess 16170 would be the right place to put that, but 16295 looks close, too.
...........
The following sequence can also be duplicated more than 75% of the time:
1. Turn the radio on with a preset or turn it on with the power button and then hit a preset. Radio streams (stream can be either a radio station, Pandora or Sirius station).
2. Radio turns off within about 15 seconds
3. Radio turns itself back on usually with the “Play” icon in the lower left hand corner
4. I press the pause button; icon changes to “Pause”
5. I press the play button and then stream restarts
6. At this point, it usually continues to play
7. I turn the radio off
8. Unit turns itself on within a minute (with stop icon in lower left hand corner)
9. After 30 seconds it goes to the “Stop” screensaver
10. Unit turns itself off (and stays off)
...............
Any ideas or questions are welcome.
On my Radio on MySB:
1 = same (Radio correctly streams from Preset from standby state or already turned on)
2 = mine does not turn itself off
3, 4, 5, 6 = does not apply cuz #2 did not occur
7 = same (it correctly turns off on command)
8, 9, 10 = does not occur on my Radio
Again, let me know if you want me to try some different settings to attempt to reproduce.
Radio 7.5.1 r8837
note: I do not use any alarms
6. At this point, it usually continues to play
7. I turn the radio off
8. Unit turns itself on within a minute (with stop icon in lower left hand corner)
9. After 30 seconds it goes to the “Stop” screensaver
10. Unit turns itself off (and stays off)
I get this part all the time. (It's the won't-stay-off issue I mentioned in the other thread.) However, during steps 7 thru 10, the content is still streaming over WiFi; that worries me because I don't want it to do that forever.
I observed one final step:
11. Unit finally turns itself "more off" after several more minutes - no longer streaming content via WiFi. Screen remains as in step 10, the clock.
Ugh, towards the end of the comments it becomes This Problem, but it sure doesn't start out that way.
I'd guess 16170 would be the right place to put that, but 16295 looks close, too.
I posted in both bugs. I think it is a bit of each of them.
Turns on by itself.
Turns off by itself.
I won't get into the alarm problems just yet.
Thanks!
Again, let me know if you want me to try some different settings to attempt to reproduce.
I was going to ask if you had any alarms "enabled" but I see that specifically said you don't use alarms.
I just tried disabling my alarm. No change but interestingly, the alarm icon still appeared on the off screensaver. I then turned on SBS and switched to it. I disabled the alarm there (I don't have MSB and SBS synchronized). Only then did the alarm icon disappear. Then, I switched back to MSB.com and turned SBS off. I know that makes no sense at all. I'm just describing what happens.
The most interesting thing is now I cannot reproduce the behaviors in my post. In other words, when I turn on with a present, it stays on. When I turn it off, it stays off. How frustrating. Are enabled alarms creating these issues? If so, what a mess. Are the bugs with MSB.com and not the radio?
snarlydwarf
2010-07-13, 18:01
The most interesting thing is now I cannot reproduce the behaviors in my post. In other words, when I turn on with a present, it stays on. When I turn it off, it stays off. How frustrating. Are enabled alarms creating these issues? If so, what a mess. Are the bugs with MSB.com and not the radio?
That's my guess, some sort of synchronization of alarms: the Radio plays, MySB sees it playing but decides 'oh crud, you started playing hours ago from that alarm, you need to stop now' and turns it off.
I think it's a MySB bug: since it only seems to affect people using MySB, not SBS.
I just tried disabling my alarm. No change but interestingly, the alarm icon still appeared on the off screensaver. I then turned on SBS and switched to it. I disabled the alarm there (I don't have MSB and SBS synchronized). Only then did the alarm icon disappear. Then, I switched back to MSB.com and turned SBS off. I know that makes no sense at all. I'm just describing what happens.
Did you disable the alarm directly on the Radio or through SBS/MySB web interfaces ?
I think it takes effect immediately (hiding alarm icon) if you do it directly on the Radio but if you do it on SBS/MySB it's updated the next time you play something on the Radio. Possibly it might also be triggered by doing other things than playing music. I've only tried this with SBS so it might work differently with MySB.
1. The radio is off (Off screensaver displayed)
2. I turn it on using the power button – It has a “pause” indicator showing in the lower left hand corner
3. It turns off by itself within about 15 seconds
Do you have a battery pack installed in your Radio ?
Does it also turn off after 15 seconds if you after point 2 starts to navigate through the menu and actually do something with it ?
I'm guessing there might be some timeout that triggers if you leave it on with a battery but isn't using it. Possibly there might be something similar on MySB to save server resources for players that aren't used. Still, 15 seconds feels a bit short if this is caused by an intentional timeout.
Philip Meyer
2010-07-14, 00:34
Do you have an alarm timeout configured, or is the timeout=0. This can be configured in SBS, not sure about MySB as I don't use that service.
I'm thinking that if the timeout isn't 0, that it might cause the audio to stop thinking that an alarm had previously been started. If it is 0, it might avoid that.
Do you have a battery pack installed in your Radio ?
No battery installed.
Does it also turn off after 15 seconds if you after point 2 starts to navigate through the menu and actually do something with it ?
Yes. Often it will actually turn off if I'm in the middle of tuning to a favorite or changing the alarm set time.
..... Are enabled alarms creating these issues?....
That has long been my suspicion that Alarms are either creating or aggravating these issues.
I don't want to speak too soon, but I now have had 24 hours of flawless listening to my Radio. No automatic turn offs; no turning on by itself. All of the odd behavior that I reported in my prior posts has been eliminated.
How?
The only thing I did was delete any alarms that were programmed (not just disable - DELETE). My radio now contains no alarms. There are no alarms set on MSB.com. I also redirected the radio to SBS and made sure there were not stray alarms there. Then I redirected the radio back to MSB.com
Once alarms were deleted, I made sure that the "All Alarms" setting was set to "off".
Then I did a power down by pulling the plug and re-plugging.
No more auto turn offs, etc.
Why? I have no idea but I'm convinced (for today) that the alarms were causing my problems. Who knows, tomorrow I may retract my statements.
I don't want to speak too soon, but I now have had 24 hours of flawless listening to my Radio. Who knows, tomorrow I may retract my statements.
I retract my last post. After 36 hours of flawless listening, the radio is back to its auto off, auto on behavior, exactly as I posted in my step by step details. I give up for now.
sheriff1972
2010-07-16, 03:12
Ciamer,
There is an ever growing number of us stuck in this SB Radio firmware hell.
(Don't tell Snarlydwarf though as he does not like people posting negative comments about their own user experience.)
Should have bough another Boom, to go with my Duet...
Ciamer,
There is an ever growing number of us stuck in this SB Radio firmware hell.
(Don't tell Snarlydwarf though as he does not like people posting negative comments about their own user experience.)
Should have bough another Boom, to go with my Duet...
Progress and a workaround!
See http://bugs.slimdevices.com/show_bug.cgi?id=16170 Comment 95.
Powered by vBulletin® Version 4.1.12 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.