This is wireless network scanning
I assume here you refer to Library Scanning.
I suggest you open a new thread with full debug enabled logs upload via MyOSMC as I doubt this issue is related to your original post of Display Frozen
This isn’t an error - it’s just a message when WiFi scan occurs.
Will reduce verbosity in next update.
I suspect my Vero4k+ is toast.
Note, the installs were performed with the Vero connected directly to the display, eliminating the Oppo in the chain.
A fresh install of OSMC_TGT_vero3_20211129 did not resolve the issues.
With a fresh install of OSMC_TGT_vero3_20201227 the scraping speed went back to normal but there were other issues and after upgrading the scraping speed tanked. Also before upgrading the video playback start/stop worked fine.
Just tried a fresh install of OSMC_TGT_vero3_20210808 and there issues, the video came up in 1920x1080i instead of 1920x1280p, and timezone would not set (could do it later via ssh).
When I say scraping speed tanked, it literally goes from a clean start of something like 10-20 minutes for my 123 TV shows, to several hours. Granted the newer python based scraper is slower, but even the old scraper is very slow.
Could it possibly some bad ram? Is there a bootable diagnostic disk available?
Thanks,
Chris
Without logging enabled there seems to be a lot activity in the journal:
– Logs begin at Mon 2021-12-27 11:38:36 EST, end at Mon 2021-12-27 12:40:23 EST. –
Dec 27 12:40:23 zapfap su[4120]: pam_unix(su-l:session): session opened for user root by osmc(uid=1000)
Dec 27 12:40:23 zapfap su[4120]: (to root) osmc on pts/0
Dec 27 12:39:06 zapfap kernel: wl_run_escan: LEGACY_SCAN sync ID: 12, bssidx: 0
Dec 27 12:38:55 zapfap kernel: hdmitx: audio: hdmi_ch: 0 speaker_layout: 0
Dec 27 12:38:55 zapfap kernel: hdmitx: audio: aout notify size 32
Dec 27 12:38:55 zapfap kernel: hdmitx: audio: aout notify rate 44100
Dec 27 12:38:55 zapfap kernel: snd_spdif_dai: aml_hw_iec958_init,runtime->rate=44100, runtime->channels=2
same source mode(1), stream format=2 CH PCM
Dec 27 12:38:54 zapfap kernel: hdmitx: audio: hdmi_ch: 0 speaker_layout: 0
Dec 27 12:38:54 zapfap kernel: hdmitx: audio: aout notify size 32
Dec 27 12:38:54 zapfap kernel: hdmitx: audio: aout notify rate 44100
Dec 27 12:38:54 zapfap kernel: snd_spdif_dai: aml_hw_iec958_init,runtime->rate=44100, runtime->channels=2
same source mode(1), stream format=2 CH PCM
Dec 27 12:38:52 zapfap kernel: hdmitx: audio: hdmi_ch: 0 speaker_layout: 0
Dec 27 12:38:52 zapfap kernel: hdmitx: audio: aout notify size 32
Dec 27 12:38:52 zapfap kernel: hdmitx: audio: aout notify rate 44100
Dec 27 12:38:52 zapfap kernel: snd_spdif_dai: aml_hw_iec958_init,runtime->rate=44100, runtime->channels=2
same source mode(1), stream format=2 CH PCM
Dec 27 12:38:51 zapfap kernel: hdmitx: audio: hdmi_ch: 0 speaker_layout: 0
Dec 27 12:38:51 zapfap kernel: hdmitx: audio: aout notify size 32
Dec 27 12:38:51 zapfap kernel: hdmitx: audio: aout notify rate 44100
Dec 27 12:38:51 zapfap kernel: snd_spdif_dai: aml_hw_iec958_init,runtime->rate=44100, runtime->channels=2
same source mode(1), stream format=2 CH PCM
Dec 27 12:38:45 zapfap kernel: hdmitx: audio: hdmi_ch: 0 speaker_layout: 0
Dec 27 12:38:45 zapfap kernel: hdmitx: audio: aout notify size 32
Dec 27 12:38:45 zapfap kernel: hdmitx: audio: aout notify rate 44100
Dec 27 12:38:45 zapfap kernel: snd_spdif_dai: aml_hw_iec958_init,runtime->rate=44100, runtime->channels=2
same source mode(1), stream format=2 CH PCM
Dec 27 12:38:43 zapfap kernel: hdmitx: audio: hdmi_ch: 0 speaker_layout: 0
Dec 27 12:38:43 zapfap kernel: hdmitx: audio: aout notify size 32
Dec 27 12:38:43 zapfap kernel: hdmitx: audio: aout notify rate 44100
Dec 27 12:38:43 zapfap kernel: snd_spdif_dai: aml_hw_iec958_init,runtime->rate=44100, runtime->channels=2
same source mode(1), stream format=2 CH PCM
Dec 27 12:38:42 zapfap kernel: hdmitx: audio: hdmi_ch: 0 speaker_layout: 0
Dec 27 12:38:42 zapfap kernel: hdmitx: audio: aout notify size 32
Dec 27 12:38:42 zapfap kernel: hdmitx: audio: aout notify rate 44100
Dec 27 12:38:42 zapfap kernel: snd_spdif_dai: aml_hw_iec958_init,runtime->rate=44100, runtime->channels=2
same source mode(1), stream format=2 CH PCM
Dec 27 12:38:41 zapfap kernel: hdmitx: audio: hdmi_ch: 0 speaker_layout: 0
Dec 27 12:38:41 zapfap kernel: hdmitx: audio: aout notify size 32
Dec 27 12:38:41 zapfap kernel: hdmitx: audio: aout notify rate 44100
Dec 27 12:38:41 zapfap kernel: snd_spdif_dai: aml_hw_iec958_init,runtime->rate=44100, runtime->channels=2
same source mode(1), stream format=2 CH PCM
Dec 27 12:38:39 zapfap kernel: hdmitx: audio: hdmi_ch: 0 speaker_layout: 0
Dec 27 12:38:39 zapfap kernel: hdmitx: audio: aout notify size 32
Dec 27 12:38:39 zapfap kernel: hdmitx: audio: aout notify rate 44100
Dec 27 12:38:39 zapfap kernel: snd_spdif_dai: aml_hw_iec958_init,runtime->rate=44100, runtime->channels=2
same source mode(1), stream format=2 CH PCM
Seems a bit busy to me, more activity than my Gentoo desktop logs.
That’s fine – and is likely just caused by GUI sounds being enabled on your device. So the sound sink is opened and closed regularly.
That was an issue with older images.
If an older version of Kodi works OK, it’s not going to be an issue with the RAM on your device. Scraping performance will depend on the amount of content being scraped, the implementation and the speed of the network.
How big is your library?
The TV show library is 123 shows. I started a a fresh scan 3 hours ago and it’s still running.
A quick search (I don’t use Library Mode) shows that scraping is indeed slower on Kodi v19. This could be because of the new scraper architecture.
I think that the default scraper also changed between versions, which may have an impact.
Of course some show have multiple seasons, but previously a scan from scratch would be less than 1/2 hour.
Vero is connected via 5G wireless, wireless access point connected to a gigabit switch, Internet bandwidth is 200/10 Mbits down/up respectively.
I’m having doubts that the video playback stop issues are necessarily the fault of the Vero, as if I connect it to the display those issues do not occur. Maybe something going sideways in the Oppo, maybe it’s an incompatibility with the new code in the Vero.
I did order another Vero today, if it ends up not solving the issue I’ll know to look elsewhere for a solution. At the least I’ll have a backup Vero. And finding a replacement for the Oppo is in a whole different expense category.
Thanks for all your help.
Chris
I’ve been meaning to try to resolve recent issues too (frequent crashes, some freezes, slow starting play), some of them similar on a similar configuration (content via nfs), and also seemingly having started around the same time (nov update). also other issues like backup failing to copy .tar file to SD card. Away until after NY and plan to troubleshoot more after that, but just chiming in in the hopes there are some known issues to be fixed in an update coming soon.
This doesn’t sound related. It seems Chris’ issue is primarily with playback.
Feel free to start a new post with logs when you get a chance
Cheers
Sam