ralphy wrote:
>
> Yes the radio actually pauses the stream, until the output buffer fills
> a bit then resumes. Occasionally, this pause/unpause happens several
> times before the stream stabilizes, which could sound similar to
> stuttering when you first start a stream. I've not had it
slartibartfast wrote:
> One of the users that reported it posted in this thread that he was in
> the USA so wasn't even listening to the 320kbps stream.
>
> Sent from my Pixel 3a using Tapatalk
Indeed. It's a mystery. I've also tried to recreate the issue on the
international streams.
expectingtofly wrote:
> Ah yes, excellent, that probably explains the improvement.
> I've now tried very hard to recreate the reported issue, and can't at
> all.One of the users that reported it posted in this thread that he was in
the USA so wasn't even listening to the 320kbps stream.
ralphy wrote:
> I did fix a problem with 'reported number of decoded samples available
> in the AAC decoder'
> (https://github.com/ralph-irving/squeezeos-squeezeplay/commit/a6ced8195144bbc64cfdc57def9c12634ed78bae)
> back in March 2021. That might explain why the behaviour is different.
Ah
expectingtofly wrote:
> Interestingly, I remember when I implemented the throttling that the
> problem was easily reproducible. The odd thing now is, with this
> latest release of the firmware, I can't reproduce the problem at all,
> even if I set the throttling to zero, effectively turning
mrw wrote:
> Right, I've just experienced this. Playback stops within a very short
> time after the stream is started, and the stream needs to be started
> again. It is not 'the norm', but has happened a few times, now I think
> about it.
>
> I wouldn't describe it as stuttering.
>
> I
christianhunt wrote:
> Hi all. I am one of the two 'bug reporters' mentioned by expectingtofly.
>
> In case it's helpful, the 'stuttering' sounds to me like momentary
> disruption to the audio stream - as if the audio is glitching or
> skipping slightly. It's not regular, it's more random.
Hi all. I am one of the two 'bug reporters' mentioned by
expectingtofly.
In case it's helpful, the 'stuttering' sounds to me like momentary
disruption to the audio stream - as if the audio is glitching or
skipping slightly. It's not regular, it's more random. It's a little
hard to describe but
mrw wrote:
> This post would suggest that it was before the Community Firmware:
>
> https://forums.slimdevices.com/showthread.php?113479-Announce-Community-Firmware-for-Squeezebox-Radio-Touch-Controller-and-LMS-8=1002965=1#post1002965I
> found it back in June 2020 when I was getting frequent
slartibartfast wrote:
> I remember that and I also disabled native aac at the time. Was that
> before or after the community firmware?
This post would suggest that it was before the Community Firmware:
For info, this is how the 2 reporters describe the issue
https://github.com/expectingtofly/LMS_BBC_Sounds_Plugin/issues/134 :
>
> Symptoms
> Stuttering - I can happily listen for days without a problem and then,
> like today, it becomes almost unlistenable. At worst the stutters can
> become
mrw wrote:
> Right, I've just experienced this. Playback stops within a very short
> time after the stream is started, and the stream needs to be started
> again. It is not 'the norm', but has happened a few times, now I think
> about it.
>
> I wouldn't describe it as stuttering.
>
> I
mrw wrote:
> Right, I've just experienced this. Playback stops within a very short
> time after the stream is started, and the stream needs to be started
> again. It is not 'the norm', but has happened a few times, now I think
> about it.
>
> I wouldn't describe it as stuttering.
>
> I
ralphy wrote:
> I implemented the AAC decoder for squeezeplay and later the community
> firmware as Logitech never released the code as they used the closed
> source fdk-aac library in the official firmware.
>
> I have spent some time investigating this issue but had to setup a local
> server
ralphy wrote:
> What's happening is the aac decoder can't push enough decoded PCM data
> to the output buffer at the start of the high rate streams and jive_alsa
> throws an underrun error.
Right, I've just experienced this. Playback stops within a very short
time after the stream is started,
slartibartfast wrote:
> Can this stuttering occur any time or just at the beginning of a
> stream?
>
> Sent from my Pixel 3a using Tapatalk
For me, it only happens at the beginning of the stream.
Ralphy
*1*-Touch, *5*-Classics, *3*-Booms, *2*-UE Radio
'Squeezebox client builds'
ralphy wrote:
> I implemented the AAC decoder for squeezeplay and later the community
> firmware as Logitech never released the code as they used the closed
> source fdk-aac library in the official firmware.
>
> I have spent some time investigating this issue but had to setup a local
> server
I implemented the AAC decoder for squeezeplay and later the community
firmware as Logitech never released the code as they used the closed
source fdk-aac library in the official firmware.
I have spent some time investigating this issue but had to setup a local
server that streams AAC 320Kbps at
mrw wrote:
> I have two Radios running with the latest community firmware, and am a
> regular/prolific user of BBC Sounds. I have not noted any instances of
> audio stuttering on either Radio. But Ill keep an ear open.
>
> Perhaps worth noting that I do use the native playback option, so any
expectingtofly wrote:
> I have had a couple of bugs raised on the BBC Sounds Plugin repository
> relating to audio stuttering :
> https://github.com/expectingtofly/LMS_BBC_Sounds_Plugin/issues/134
>
> Both reports are using Squeezebox radio's with the community firmware.
> The BBC Streams are
I have had a couple of bugs raised on the BBC Sounds Plugin repository
relating to audio stuttering :
https://github.com/expectingtofly/LMS_BBC_Sounds_Plugin/issues/134
Both reports are using Squeezebox radio's with the community firmware.
The BBC Streams are AAC 320kbs@48000, so quite high
Nice work. A Touch and four radios updated. On the Radios I had to
reinstall the CustomClock in the Applet installer.
Paytheprice's Profile: http://forums.slimdevices.com/member.php?userid=63737
View this thread:
did a successful reset.
It seems the weather info broke the upgrade..
seth_space's Profile: http://forums.slimdevices.com/member.php?userid=37717
View this thread: http://forums.slimdevices.com/showthread.php?t=113479
seth_space wrote:
> updated three radios successful and the logitech touch.
> But now the touch does not wants to switch off anymore,
> Any thoughts?
I've been running the firmware on my touch for a month and have not
experienced this issue.
I'd suggest you first perform a factory reset on
updated three radios successful and the logitech touch.
But now the touch does not wants to switch off anymore,
Any thoughts?
seth_space's Profile: http://forums.slimdevices.com/member.php?userid=37717
View this thread:
Michael and Ralphy, thanks for explaining codec. I hope now get it.
The encoding ability (which was never used in the hardware) was removed,
but the decoding ACC was retained and updated.
Thanks again!
Paul
P
Thanks for the work on this. Updated Radio, Touch, and Controller this
morning.
*Home:* Pi4B-8GB/pCP8.x/4TB>LMS 8.2.x>Transporter, Touch, Boom, Radio
(all ethernet)
*Cottage:* rPi4B-4GB/pCP8.x/4TB>LMS 8.2.x>Touch>Benchmark DAC I, Boom,
Radio w/Battery (Radio WIFI)
*Office:*
ralphy wrote:
> Release 8.0.1_r16907 is now available via the plugin.
Thank you! Five SB devices updated this morning.
Apesbrain's Profile: http://forums.slimdevices.com/member.php?userid=738
View this thread:
P Nelson wrote:
> from the change log:
>
Update Fraunhofer FDK AAC Codec Library v2.0.3 and remove
> encoder support.
>
> Due to my lack of technical knowledge, I am interpreting the above as it
> was updated and then removed. Of course, that conclusion does not any
> make sense. Please add
Updated my 2 Sb radio and my 2 Sb Touch
/Patrik
Insomniacx's Profile: http://forums.slimdevices.com/member.php?userid=71872
View this thread: http://forums.slimdevices.com/showthread.php?t=113479
Update Fraunhofer FDK AAC Codec Library v2.0.3 and remove
encoder support.
Due to my lack of technical knowledge, I am interpreting the above as it
was updated and then removed. Of course, that conclusion does not any
make sense.
"Codec" stands for "code/decode". I assume the first part was
ralphy wrote:
> Release 8.0.1_r16907 is now available via the plugin.
>
> See the ' community firmware plugin changelog'
> (https://ralph_irving.gitlab.io/lms-community-firmware/changelog.html)
> for details.
from the change log:
Update Fraunhofer FDK AAC Codec Library v2.0.3 and remove
slartibartfast wrote:
> OK. One more thought. I have added a Cron job to reboot my Touch every 2
> weeks. Will I need to redo it?
I think not. The cron table is, I think, stored in the etc hierarchy,
which is left untouched by firmware updates. And I think it takes a
factory reset to wipe
mrw wrote:
> No.OK. One more thought. I have added a Cron job to reboot my Touch every 2
weeks. Will I need to redo it?
Sent from my Pixel 3a using Tapatalk
slartibartfast's Profile:
slartibartfast wrote:
> Do we need to take any notice of the items under Build failure
> mitigations?
No.
mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299
View this thread:
ralphy wrote:
> Release 8.0.1_r16907 is now available via the plugin.
>
> See the ' community firmware plugin changelog'
> (https://ralph_irving.gitlab.io/lms-community-firmware/changelog.html)
> for details.Do we need to take any notice of the items under Build failure
mitigations?
Sent from
Release 8.0.1_r16907 is now available via the plugin.
See the ' community firmware plugin changelog'
(https://ralph_irving.gitlab.io/lms-community-firmware/changelog.html)
for details.
Ralphy
*1*-Touch, *5*-Classics, *3*-Booms, *2*-UE Radio
'Squeezebox client builds'
ralphy wrote:
>
>
> I usually wait a few weeks for the early adopters to have a bang at it
> just in case something is broken.
Nice... Good old fashioned development cycle :D
As ever, thanks for all your work in the SB ecosystem Ralphy.
Kev
Apesbrain wrote:
> Maybe I've jumped the gun? Is the 'r16907;10/4/22 firmware'
> (https://sourceforge.net/projects/lmsclients/files/squeezeos/) released
> for the plugin to download?
No. I haven't released it through the plugin yet.
I usually wait a few weeks for the early adopters to have a
Apesbrain wrote:
> Maybe I've jumped the gun? Is the 'r16907;10/4/22 firmware'
> (https://sourceforge.net/projects/lmsclients/files/squeezeos/) released
> for the plugin to download?Probably not released yet. I am on r16881.
Sent from my Pixel 3a using Tapatalk
bengaldave wrote:
> First let me say I have been running community firmware and it is
> working fine! So thanks for the effort!
>
> The question, is the project for the firmware setup differently than lms
> such that it had to renamed community firmware?
>
> What was the last official
bengaldave wrote:
>
> The question, is the project for the firmware setup differently than lms
> such that it had to renamed community firmware?
>
LMS is not a firmware, so I'm not sure what you mean by "renamed"?
First let me say I have been running community firmware and it is
working fine! So thanks for the effort!
The question, is the project for the firmware setup differently than lms
such that it had to renamed community firmware?
What was the last official firmware for the touch and radio?
Maybe I've jumped the gun? Is the 'r16907;10/4/22 firmware'
(https://sourceforge.net/projects/lmsclients/files/squeezeos/) released
for the plugin to download?
Apesbrain's Profile:
Apesbrain wrote:
> Yes, both. :( Plugins box is checked. I've updated Touch firmware via
> USB in the past, but thought there was a "manual" way to do it via LMS
> for both Touch and Radio.I've never tried it but I believe firmware can be
> installed on the Touch
via SD card.
Sent from my
slartibartfast wrote:
> Have you checked for a software update on the players or rebooted the
> players?
Yes, both. :( Plugins box is checked. I've updated Touch firmware via
USB in the past, but thought there was a "manual" way to do it via LMS
for both Touch and Radio.
Apesbrain wrote:
> I've updated the plugin, but I'm impatient. If I've downloaded the
> latest firmware (r16907), is there a location on LMS-Windows where I can
> copy the unzipped files and they will upload to my Squeezeboxes?I have never
> had to wait to get the update. Have you checked for
I've updated the plugin, but I'm impatient. If I've downloaded the
latest firmware (r16907), is there a location on LMS-Windows where I can
copy the unzipped files and they will upload to my Squeezeboxes?
Apesbrain's
Rasputin_GY wrote:
> As a workaround you could ssh onto your pi and do the following:
>
> >
Code:
> > cd Downloads
> wget
https://downloads.sourceforge.net/project/lmsclients/squeezeos/baby_8.0.1_r16855.zip
> unzip baby_8.0.1_r16855.zip
> mv
JJZolx wrote:
> Someone remind me again...
>
> What does the community firmware fix, add or subtract from the standard
> firmware?
https://ralph_irving.gitlab.io/lms-community-firmware/changelog.html
*Home:* Pi4B-8GB/pCP8.x/4TB>LMS 8.2.x>Transporter, Touch, Boom, Radio
(all ethernet)
See the first post in this thread - and in particular the link to the
change log
Paul Webster
author of \"now playing\" plugins covering radio france (fip etc),
planetradio (bauer - kiss, absolute, scala, jazzfm etc), kcrw, abc
australia and cbc/radio-canada
and, via the extra \"radio now
Someone remind me again...
What does the community firmware fix, add or subtract from the standard
firmware?
JJZolx's Profile: http://forums.slimdevices.com/member.php?userid=10
View this thread:
Syco54645 wrote:
> Apparently my post was removed somehow so let's try again.
>
> I am quite new to LMS and am trying to install the community firmware
> but my player is not seeing it. I am running LMS 8.3.0 - 66147463 and
> have installed the plugin and then went to the settings to to enable
Im about 24 hours youll get a notice to install on your radio or
touch. Nothing to set to reduce that wait.
*Home:* Pi4B-8GB/pCP8.x/4TB>LMS 8.2.x>Transporter, Touch, Boom, Radio
(all ethernet)
*Cottage:* rPi4B-4GB/pCP8.x/4TB>LMS 8.2.x>Touch>Benchmark DAC I, Boom,
Radio w/Battery (Radio WIFI)
Apparently my post was removed somehow so let's try again.
I am quite new to LMS and am trying to install the community firmware
but my player is not seeing it. I am running LMS 8.3.0 - 66147463 and
have installed the plugin and then went to the settings to to enable the
plugin. I have changed
So I am very new to LMS and squeezebox in general but am unable to see
the community firmware update. I installed the plugin and went to the
plugin settings to enable it after install. I changed player.firmware to
debug but I do not see the radio checking for it. The first post
mentions that we
mherger wrote:
> >[22-04-02 12:27:21.8333] Slim::Utils::Firmware::downloadAsyncError
> (574) Warning: Firmware: Failed to download
> https://ralph_irving.gitlab.io/lms-community-firmware/update/firmware/8.2.0/fab4_8.0.1_r16862.bin.sha
> (Validation of firmware
[22-04-02 12:27:21.8333] Slim::Utils::Firmware::downloadAsyncError (574)
Warning: Firmware: Failed to download
https://ralph_irving.gitlab.io/lms-community-firmware/update/firmware/8.2.0/fab4_8.0.1_r16862.bin.sha
(Validation of firmware /tmp/slimupdate/fab4_8.0.1_r16862.bin failed, SHA1
First: Thanks to Ralphy, Michael and this community for keeping those
old devices alive.
I am having problems with LMS downloading the community firmware (SHA1
checksum did not match).
Any ideas?
Code:
[22-04-02 12:27:07.4584]
Hi!
Long-time lurker here; I had to factory reset my Touch, so I took the
opportunity to switch to this firmware, and it just works perfectly,
thanks a lot!
I was wondering about the busybox version in it, would it be possible to
build it with ntp support, and also the kernel with the iptables
Paytheprice wrote:
> It seems to be an issue with the update. I got a new radio with the
> update installed. It had the problem from the beginning. After updating
> the other three radios to the community firmware, there is only one
> Radio left without the issue. It is the only one with an
I have a problem with lost wifi connection after upgrading this
firmware. The current fix right now for me is to unplug my squeezebox
radio and plug back. have you had any similar problem?
hatng's Profile:
I have turned on an alarm clock on an other Radio now. I will see, if
there is an connection to the WiFi on the device tomorrow. Nevertheless
I do not know where to begin the search. It might be a problem with my
Unif APs, too.
I can't be of any help here, but just reporting that I'm running
community firmware on everything, and I have only one RADIO WIFI
connected RADIO, and it does not exhibit this problem. This RADIO is
at a weekend place, and the internet is OFF when not there. But the
RADIO always automatically
It seems to be an issue with the update. I got a new radio with the
update installed. It had the problem from the beginning. After updating
the other three radios to the community firmware, there is only one
Radio left without the issue. It is the only one with an alarm
activated. It seems not
Paytheprice wrote:
> As noticed before, just two of four radios seem to be affected. And it
> just happens if WiFi was turned off during the night. The third one did
> loose connection today and showed the blue WiFi icon while it was not
> connedted. Here a restart was necessary.
>
If you
Dear all,
I would like to come back to my thread.
I am running LMS 8.2 on a PiCorePlayer. I updated my four radios to
Firmware 8.0.1-r16867. I have a similar problem as descibed before. My
WiFi turns off during the night and turns on in the early morning again.
Two of my radios do not
slartibartfast wrote:
> If you restart LMS that warning should disappear.
Nope. Perhaps it's a PCP idiosyncrasy. The warning has been there for
years, even after applying the old Version Comparison Fix patch. Anyhoo,
I shall focus not on that but on enjoying the superior AAC sound :D!
RPi
beneix wrote:
> OK, I took the plunge. Exciting! :)
>
> Interestingly, I still get the following on the Information tab in LMS,
> but the firmware is definitely updated. No matter.
> >
Code:
> > You seem to be using a Squeezebox with an outdated firmware, not
slartibartfast wrote:
> Michael added a change to LMS to allow Radios with old firmware to
> connect. I don't know if a warning about the firmware still appears
> somewhere.
>
> Sent from my Pixel 3a using Tapatalk
OK, I took the plunge. Exciting!
Interestingly, I still get the following on
beneix wrote:
> Thanks, that is helpful. My Radio on 7.7.3-r16676 seems to be playing
> fine with my 8.2 LMS, but perhaps there are things I am not aware of
> that would work better, or that I am missing, based on what you wrote
> above. Is it the case that compatibility issues between the
slartibartfast wrote:
> The new firmware includes the same fix as AlsaBufferSize I think. It
> also includes the patch to allow the Radio to work with LMS 8.x.
>
Thanks, that is helpful. My Radio on 7.7.3-r16676 seems to be playing
fine with my 8.2 LMS, but perhaps there are things I am not
Dear all,
I am running LMS 8.2 on a PiCorePlayer. I updated my four radios to
Firmware 8.0.1-r16867. I have a similar problem as descibed before. My
WiFi turns off during the night and turns on in the early morning again.
Two of my radios do not reconnect to the WiFi automatically. I have to
beneix wrote:
> I'm using a Radio. I recall having a bass drop-out issue a few years
> ago; I think I resolved it with a 3rd party app called AlsaBufferSize.
> Is that the same issue?
>
> In any case, it sounds like this firmware is aimed more at fixing issues
> for people than at offering new
beneix wrote:
> I'm using a Radio. I recall having a bass drop-out issue a few years
> ago; I think I resolved it with a 3rd party app called AlsaBufferSize.
> Is that the same issue?
>
> In any case, it sounds like this firmware is aimed more at fixing issues
> for people than at offering new
slartibartfast wrote:
> Are you using a Touch or a Radio? There is more reason to use it on the
> Radio where sometimes the bass speaker can stop working and the new
> firmware contains a fix for this.
>
> Sent from my Pixel 3a using Tapatalk
I'm using a Radio. I recall having a bass drop-out
beneix wrote:
> I am sorry, but I read that and more, and it only tells me that a lot of
> changes have been made to the first version of the community firmware,
> but not the original reason to create it. From the changelog, I can sort
> of deduce that a lot is around AAC and WiFi issues - is
slartibartfast wrote:
> You can find all the info in the first post of this thread including a
> changelog.
>
> Sent from my Pixel 3a using Tapatalk
I am sorry, but I read that and more, and it only tells me that a lot of
changes have been made to the first version of the community firmware,
slartibartfast wrote:
> You can find all the info in the first post of this thread including a
> changelog.
>
> Sent from my Pixel 3a using Tapatalk
I am sorry, but I read that and more, and it only tells me that a lot of
changes have been made to the first version of the community firmware,
beneix wrote:
> I have just discovered that a community firmware exists. I went looking
> for a summary of what it offers above the last official firmware, but I
> came up short. Where can I find a summary?You can find all the info in the
> first post of this thread including a
changelog.
I have just discovered that a community firmware exists. I went looking
for a summary of what it offers above the last official firmware, but I
came up short. Where can I find a summary?
beneix's Profile:
slartibartfast wrote:
> Maybe contact Bluegaspode to see if he can change the maximum version to
> 8.*. At the moment it is 7.*. If you can find the applet file you might
> be able to edit the file yourself. I have installed applets manually
> before but can't remember how I did it. It will be
ThomH wrote:
> Thanks for the quick answer. But - unfortunately not. I knew this
> address and post, and that was exactly what worked until now.
> Now I can´t find this plugin in my lms list anymore (lms 8), however
> having "third parties plugins" engaged and the bluegaspode url correctly
>
Man in a van wrote:
> This any good ?
>
> https://forums.slimdevices.com/showthread.php?67139-Announce-Headphone-Switcher-for-Squeezebox-Duet
>
> ronnie :)
Thanks for the quick answer. But - unfortunately not. I knew this
address and post, and that was exactly what worked until now.
Now I
ThomH wrote:
> Hello Ralphy, Michael and all the others,
> Many thanks for doing this and keeping the sytem updated! It´s still the
> best system on the market to me and I enjoy it everyday.
> The firmware installed and run without problems on all my devices.
> However I miss one item on the
Hello Ralphy, Michael and all the others,
Many thanks for doing this and keeping the sytem updated! It´s still the
best system on the market to me and I enjoy it everyday.
The firmware installed and run without problems on all my devices.
However I miss one item on the controllers: I had the
Dear all,
community firmware is working great. I noticed one issue yesterday when
setting up the alarm clocks the first time.
Configuration/setup:
- SB Radio, community firmware 8.0.1 r16867
- Radio timezone set to GMT+1
- Alarm clock setup at 6:00 in the display
-> the alarm rings at 7:00. So
mhhd wrote:
> Dear Paul, dear Gary,
>
> Thank you very much for your response! It was the network connection!!
> Checking for networks with a wifi analyzer app, I got somehow shocked,
> as there were 25-30 overlapping access points in my tiny neighbourhood
> (3 years ago about 8). Interfearing
garym wrote:
> And note that simply plugging in ethernet does not automatically switch
> the radio to ethernet. You need to go into the "networking" menu on the
> Radio.
Dear Paul, dear Gary,
Thank you very much for your response! It was the network connection!!
Checking for networks with a
P Nelson wrote:
> Try connecting using Ethernet to see if problem goes away. If yes, then
> you might have wifi network issues.
>
> As for my reported problem, it happened two times, but it has not
> occurred recently.
>
> Paul
And note that simply plugging in ethernet does not
mhhd wrote:
> Sorry for missleading you :-(
> After about a day the radios disconnected from LMS 8.1.2 as well.
> So no solution yet and unfortunatelly no music...
>
> Would love if someone with more knowledge could dig into this...
> Thanks and regards,
> Martin
Try connecting using Ethernet
mhhd wrote:
> Hello,
>
> Maybe in line with some others here I experienced issues with both of my
> radios connected to LMS 8.2 (docker communityserver).
> Both radio firmwares 8.0.1 r16867 and 8.0.1 r16862 in combination with
> LMS 8.2 showed the same issues P Nelson described:
> - Message on
P Nelson wrote:
> The SB Radio at my office has been exhibiting strange behavior since,
> yesterday, when I installed the recent firmware Version 8.0.1 r16867. I
> typically use mysqueezebox.com instead of running LMS on the work
> computer as I mostly listen to a jazz radio station.
>
>
tommyz wrote:
> Are the experimental kernels still available?
Some of them I was able to recover and they are listed from within the
EDO app on the touch.
Please move further discussions of EDO to that 'thread'
Are the experimental kernels still available?
tommyz's Profile: http://forums.slimdevices.com/member.php?userid=5457
View this thread: http://forums.slimdevices.com/showthread.php?t=113479
tommyz wrote:
> Hi, I have two Touchs using Triodes EDO patch conncted to TEAC UD 301 &
> 501, using Triodes experimantal kernals (#11 & #12).
>
> Will these still be needed / available after the update?
>
> br, Thomas
community firmware doesn't change the need for EDO, if one needs EDO
Hi, I have two Touchs using Triodes EDO patch conncted to TEAC UD 301 &
501, using Triodes experimantal kernals (#11 & #12).
Will these still be needed / available after the update?
br, Thomas
tommyz's Profile:
mrw wrote:
> I have encountered something similar, but perhaps not identical.
>
> See issue: https://github.com/ralph-irving/squeezeos/issues/11
>
> In this case, it appears to be triggered by perhaps high overall
> memory usage in the Radio.
> I am presently monitoring that, to see if any
P Nelson wrote:
> I have noticed unpredictable behavior trying to reconnect to the WiFi
> network. Not sure if I could recreate the problem. If there are logs
> that could help, let me know.
>
I have encountered something similar, but perhaps not identical.
See issue:
At my office, the WiFi router was turned off for several days while I
was away. After turning the router back on, the SB Radio would not
reconnect to my WiFi network. Attempts to use repair network failed.
Attempts to select and connect to the WiFi network failed. I rebooted
the radio. It
1 - 100 of 611 matches
Mail list logo
