Home of the Squeezebox™ & Transporter® network music players.
Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 37
  1. #21
    Senior Member
    Join Date
    Mar 2008
    Posts
    496
    Quote Originally Posted by itm View Post
    I'm using Squeezeplayer on an LG G5 (Android 7.0) phone to playback music on LMS 7.9.0 (running on Windows Server 2008). The client app on the phone (I have tried both the Squeezer and Squeeze Commander apps) loses connection to the LMS server every few minutes, which results in the current track being aborted and the next track starting. The wifi connection seems to stay up (but I don't know if it is getting briefly interrupted then resuming).

    I have excluded all of the squeezebox-related apps from Android's battery optimisation features, but it didn't seem to help.

    I don't have the problem if I use a Samsung Galaxy Tab S2 tablet (running exactly the same apps, but on Android 6.0 rather than 7.0).

    I also don't have a problem on the phone if using Google Play Music.

    Can anyone suggest a way of diagnosing or resolving this?
    While I don't want to start a religious war over who makes the best phones, my experience with LG has been 90% good but 10% full of frustrations like this. I love their clothes washers and optical drives, but after the most recent software update completely killed my G Stylo's GPS for good, I had to admit defeat and replace it. Driving for Lyft just doesn't work without GPS...

    More on topic for this forum, I found that using SqueezePlayer while on the road (i.e., using the 4G network and a VPN to stream tracks from home) would consistently result in the volume dropping back to the phone's nannyware low-volume setting about 10 seconds before the end of a track. Every track. Every time. I preferred to keep the output volume on the phone at maximum and control what I heard via the car's stereo, but LG just wouldn't allow it.

    So I could be completely off-base here, but in my experience, LG and SqueezePlayer just don't get along particularly well.

    Of course, now that I have a Samsung, I can't use SqueezePlayer remotely at all because the OpenVPN client refuses to connect. It's always something.

  2. #22
    Senior Member pippin's Avatar
    Join Date
    Oct 2007
    Location
    Berlin
    Posts
    14,141
    Quote Originally Posted by itm View Post
    I thought it interesting that Google Play Music didn't suffer from the same issue. Maybe it handles its data buffering differently?
    It's probably less an issue of data buffering but a question of control.
    Google Play Music is a locally running player that only needs to load the data and then runs independently.

    A Squeezebox (and SqueezePlayer is a Squeezebox) is a streaming client remotely controlled by LMS.
    Even if it downloads all the data it still expects a permanent connection to the server for all of its control.

    What it does if that connection falls away depends a bit on the implementation but at the end of the current track, at latest, it won't know what to do and stop.

    Also, with intermittent connection the server often thinks it needs to reset the playback.
    You can try to work around it but that, again, is an implementation detail.

    There's one point where the phone/OS might play a role: with spotty connections the OS can keep the socket connection all of this is based on "virtually" open in a sense that it doesn't let the higher layers know it had been interrupted.iOS for example is pretty good at this over cellular.
    This might differ from phone model to phone model. I don't know.
    ---
    learn more about iPeng, the iPhone and iPad remote for the Squeezebox and
    Logitech UE Smart Radio as well as iPeng Party, the free Party-App,
    at penguinlovesmusic.com
    New: iPeng 9, the Universal App for iPhone, iPad and Apple Watch

  3. #23
    Senior Member
    Join Date
    May 2008
    Posts
    200
    Sorry - I hadn't realised that one of the other players was still turned on....

    Anyway I'm now trying SB player and getting the same sort of issue. By "same sort of issue" I mean that tracks are now aborting and then either restarting from the beginning or simply stopping mid-track. I stopped LMS, cleared the server log and attach a new one from just after the latest track stopped playing.

    Re. the LG phone - the removable battery is the must-have feature for me. I'm lucky to get more than 8 hours battery life out of my phone, and the spare battery has been a life saver on several occasions.
    Attached Files Attached Files

  4. #24
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    15,254
    There are still two playesrs running (00:04:20:1e:97:d7 and 9e:4d:40:53:84:bc and so many of the message cannot be identified.

    The good news is that at least it is clear a complete file got sent to the player.
    Code:
    17-06-11 15:07:40.9421] Slim::Player::Squeezebox::stream (1030) strm-q
    [17-06-11 15:07:41.1653] Slim::Player::Squeezebox::stream_s (542) stream_s called: format: mp3 url: file:///K:/Music/Steely%20Dan/Katy%20Lied%20Outtakes/04.Daddy%20Don%27t%20Live%20In%20That%20NYC.mp3
    [17-06-11 15:07:41.1657] Slim::Player::Squeezebox::stream_s (978) Starting decoder with format: m flags: 0x0 autostart: 1 buffer threshold: 255 output threshold: 1 samplesize: ? samplerate: ? endian: ? channels: ?
    [17-06-11 15:07:41.2262] Slim::Networking::Slimproto::_stat_handler (785) 00:04:20:07:5d:e3: STAT-STMt: fullness=0, output_fullness=2525560, elapsed=0.000
    [17-06-11 15:07:41.2264] Slim::Networking::Slimproto::_stat_handler (785) 00:04:20:07:5d:e3: STAT-strm: fullness=0, output_fullness=2525560, elapsed=0.000
    [17-06-11 15:07:41.2267] Slim::Networking::Slimproto::_stat_handler (785) 00:04:20:1f:00:c0: STAT-STMt: fullness=0, output_fullness=-1, elapsed=0.000
    [17-06-11 15:07:41.2268] Slim::Networking::Slimproto::_stat_handler (785) 00:04:20:1f:00:c0: STAT-strm: fullness=0, output_fullness=-1, elapsed=0.000
    [17-06-11 15:07:41.2406] Slim::Networking::Slimproto::_stat_handler (785) 00:04:20:1e:97:d7: STAT-STMt: fullness=0, output_fullness=3522376, elapsed=0.000
    [17-06-11 15:07:41.2408] Slim::Networking::Slimproto::_stat_handler (785) 00:04:20:1e:97:d7: STAT-strm: fullness=0, output_fullness=3522376, elapsed=0.000
    [17-06-11 15:07:41.4854] Slim::Networking::Slimproto::_stat_handler (785) 9e:4d:40:53:84:bc: STAT-STMf: fullness=0, output_fullness=-1, elapsed=0.000
    [17-06-11 15:07:41.6959] Slim::Networking::Slimproto::_stat_handler (785) 9e:4d:40:53:84:bc: STAT-audg: fullness=0, output_fullness=-1, elapsed=0.000
    [17-06-11 15:07:41.6961] Slim::Networking::Slimproto::_stat_handler (785) 9e:4d:40:53:84:bc: STAT-STMc: fullness=0, output_fullness=-1, elapsed=0.000
    [17-06-11 15:07:41.6963] Slim::Networking::Slimproto::_stat_handler (785) 9e:4d:40:53:84:bc: STAT-audg: fullness=0, output_fullness=-1, elapsed=0.000
    [17-06-11 15:07:41.6964] Slim::Networking::Slimproto::_stat_handler (785) 9e:4d:40:53:84:bc: STAT-STMt: fullness=0, output_fullness=-1, elapsed=0.000
    [17-06-11 15:07:41.6966] Slim::Networking::Slimproto::_stat_handler (785) 9e:4d:40:53:84:bc: STAT-STMe: fullness=0, output_fullness=-1, elapsed=0.000
    [17-06-11 15:07:41.9580] Slim::Networking::Slimproto::_stat_handler (785) 9e:4d:40:53:84:bc: STAT-STMh: fullness=0, output_fullness=-1, elapsed=0.000
    [17-06-11 15:07:41.9582] Slim::Networking::Slimproto::_http_response_handler (554) Squeezebox got HTTP response:
    HTTP/1.1 200 OK
    
    Server: Logitech Media Server (7.9.0 - 1488878280)
    
    Connection: close
    
    Content-Type: audio/mpeg
    
    
    
    [17-06-11 15:07:42.4498] Slim::Networking::Slimproto::_stat_handler (785) 9e:4d:40:53:84:bc: STAT-STMs: fullness=613376, output_fullness=51226, elapsed=0.000
    [17-06-11 15:07:43.5305] Slim::Networking::Slimproto::_disco_handler (590) Squeezebox got disconnection on the data channel: Connection closed normally
    I think this all points to the network connection going up/down.
    Code:
    17-06-11 15:08:15.8743] Slim::Networking::Slimproto::client_readable (435) Error reading from client: An existing connection was forcibly closed by the remote host.
    [17-06-11 15:08:15.8745] Slim::Networking::Slimproto::slimproto_close (247) connection closed
    and then reconnect after playing only 27 sec of audio.
    Code:
    17-06-11 15:08:16.1023] Slim::Networking::Slimproto::_hello_handler (968) Squeezebox says hello:  Deviceid: 12 revision: 0 mac: 9e:4d:40:53:84:bc uuid: a1e2436fde834ecb9be9ec1ce9003128 bitmapped: 0 reconnect: 0 wlan_channellist: 0000 lang: EN  bytes_received: 0  capabilities: Model=squeezeplay,ModelName=SB Player,alc,aac,ogg,flc,aif,pcm,mp3,MaxSampleRate=44100,AccuratePlayPoints,ImmediateCrossfade,HasDigitalOut
    [17-06-11 15:08:16.1025] Slim::Networking::Slimproto::_hello_handler (1157) Hello from existing client: 9e:4d:40:53:84:bc on ipport: 192.168.1.12:44768
    [17-06-11 15:08:16.1027] Slim::Player::SqueezePlay::updateCapabilities (160) unknown capability: ImmediateCrossfade=1, ignored
    [17-06-11 15:08:16.1028] Slim::Player::SqueezePlay::updateCapabilities (173) formats: alc,aac,ogg,flc,aif,pcm,mp3

  5. #25
    Senior Member
    Join Date
    May 2008
    Posts
    200
    Thanks for that analysis.

    wt0 how would you expect SB Player to behave when the wifi connection is interrupted like that?

  6. #26
    Senior Member
    Join Date
    May 2008
    Posts
    200
    I also notice that I get "Command stream error" or "Command stream broken" messages popping up (I guess from SB Player), then another message saying that it is trying to reconnect to the server.

  7. #27
    Senior Member
    Join Date
    Oct 2005
    Location
    Ireland
    Posts
    15,254
    Ploughing throur LMS code to see what happens on reconnect (i..e "Hello from Existing client" )

    It look like if the player enables reconnect - then LMS will allow player to continue with audio but this player doesn't support "reconnect"
    Code:
    [17-06-11 15:08:16.1023] Slim::Networking::Slimproto::_hello_handler (968) Squeezebox says hello:  Deviceid: 12 revision: 0 mac: 9e:4d:40:53:84:bc uuid: a1e2436fde834ecb9be9ec1ce9003128 bitmapped: 0 reconnect: 0 wlan_channellist: 0000 lang: EN  bytes_received: 0  capabilities: Model=squeezeplay,ModelName=SB Player,alc,aac,ogg,flc,aif,pcm,mp3,MaxSampleRate=44100,AccuratePlayPoints,ImmediateCrossfade,HasDigitalOut
    Since I am just looking at code (sub reconnect in Squeezebox.pm) this is an area I am unsure - perhaps Pippin or wt0 can confirm or explain reconnect capabilities setting.

  8. #28
    Senior Member pippin's Avatar
    Join Date
    Oct 2007
    Location
    Berlin
    Posts
    14,141
    How does a player "enable reconnect"?
    ---
    learn more about iPeng, the iPhone and iPad remote for the Squeezebox and
    Logitech UE Smart Radio as well as iPeng Party, the free Party-App,
    at penguinlovesmusic.com
    New: iPeng 9, the Universal App for iPhone, iPad and Apple Watch

  9. #29
    Senior Member
    Join Date
    Mar 2008
    Posts
    496
    Quote Originally Posted by itm View Post
    Re. the LG phone - the removable battery is the must-have feature for me. I'm lucky to get more than 8 hours battery life out of my phone, and the spare battery has been a life saver on several occasions.
    FWIW, the Samsung battery is (surprisingly!) removable and the somewhat flimsy back cover makes it easy to remove. It seems to last a long time as well, though maybe that's just because it's brand new. Or maybe it really is by design, since the battery is, relatively speaking, enormous.

  10. #30
    Senior Member
    Join Date
    May 2008
    Posts
    200
    Quote Originally Posted by atrocity View Post
    FWIW, the Samsung battery is (surprisingly!) removable and the somewhat flimsy back cover makes it easy to remove. It seems to last a long time as well, though maybe that's just because it's brand new. Or maybe it really is by design, since the battery is, relatively speaking, enormous.
    Which Samsung do you have? I had a Galaxy S4 before the LG and it was good but the camera on the LG is soooo much better, particularly in low light.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •