Hey, it seems like I didn't receive any video of the issue's process? In this case, please provide these: 1. Record the process in a video. 2. During the process recording, please also capture the log(Settings-General-Log report, click it before operation) Then upload the report and send me the name and time of it. Thx.
Hello. You can hear in 17th and 32th second of the video the lag. After that lagging 5 minutes later the player performed a fast type rebooting. I didn't expecting that and i did not capture this. T8.mp4
TBH, at the 17th second I can hear some kind of glitch (but there seems to be background noise too), while I cannot discern anything at the 32nd second.
In this video you going to hear very clearly the lag and also the behavior that i was talking about. The quick restart behavior. And at the beginning of the video you will see the delay of the cover art. T8_2.mp4
Here is the link that shows clearly the lagging and the buggy behavior. My opinion is that the hardware it's limited to the software and most of all the heavy loaded software with more than 100k of tracks. T8_2.mp4
Now yes. It's evident. What I can see, anyway, is that the sound lags while you are searching the library. Is your library local, or are you browsing some external USB, or some network share / NAS ?
My library is on a NAS with NFS protocol through network. I have also the Hifi Rose RS130 and i don't have issues with the network and the NAS. It's clearly the T8's hardware-software limitation. Too many resources from android 12 based software and the cpu-ram combination runs to the limit. I hope they prove me wrong.
For what may concern the Android (pseudo) OS I totally agree, it's a resource-hungry hog compared to other native / proprietary OSs. I would try to increase some buffers, especially incoming ones. One more thing that comes to mind: if you are over wi-fi, try to switch to 5GHz channels, as they usually are less congested; this might improve the transfer quality (aka: less packet-loss => less packet retransmission => less glitches, as a rule of thumb...) Give it a try, might work, as it might not... HTH Cheers, Al.
@Zidoo Support-Kim Hi Kim,with 1.5.30 on the T8 I observe the following .... My T8 is playing 24/7 (for various burn-in purposes). Every couple of days I seem to - partially - lose connection to the T8. It is still playing and I can operate ithe T8 from the screen ... I can also see it in the app. The issue however is that I can no longer access the main menu on the iOS app to operate it. The only thing I can still do from within the iOS app is power off/reboot etc ... A simple reboot of the T8 restores connectivity and everything starts working fine again ... Is this a known issue by any chance? (My T8 is connected via SFP to LHY AS6, behaviour occurs both on Finisar and TP-Link modules)
It may well be a LAN lease timeout. Some routers have it off, some 24h, some a week. The router's settings to change the behavior change from brand/model to brand/model.
It remains accessible on its regular IP address and I can still shutdown/reboot etc the T8 … It rather appears to be some partial saturation of the interface? Because it can still be accessed remotely, just not completely …
Maybe then some session connection(s) do not get closed properly, causing newer to either fail (ERR_MAX_CONN or the like), or being linked / redirected to expired old ones.| In other words, I am more keen to consider it a bug. :-(
Not yet .. I will do that also as step 2 after your recommended step 1 ... I do however doubt it will make a difference. So far my T8 has been testplaying to support burn-in elsewhere in the chain and as a result has kept the allocated IP address in use permanently. So an expired lease should not even happen because the T8 remained active at all times. The logs in the Unifi console (I have a 100% Unifi based network with the entire audio section on the wired segment) also prove that even when this happens, traffic to and form the T8 continues to flow.
i just realized i got this bug too. the lag lasts only for a short time when the app is connecting with the eversolo, so i don't mind that much. but it only occured after the larest firmware-update...
It can be caused by the overwhelming of library. If your library contains more than 20K, please try reduce it to see if it helps.
If fear that's not an option as i think the whole purpose of a library to contain your complete library. i think i'll just live with the lags. i have to point out though, the problem only occured after the latest firmware-update!
