T2 displays wait wheel when playing recorded programs

RayCee · Post by **RayCee** » Sun May 03, 2020 13:30

The latest firmware release displays the rotating wait symbol for sometimes several minutes whilst replaying recorded programs locking out the remote control leaving the user powerless to do anything.
It seems related to the EPG updates and occurs predictably after adding an auto timer, otherwise every 20 ,minutes or so.
Is there any fix otherwise I'd rather have to old firmware back again?
Ray
]

prl · Post by **prl** » Sun May 03, 2020 13:42

Poorly configured AutoTimers can certainly cause this sort of problem.

EPG updates, either from the FTA EPG or from IceTV do not generally cause this sort of problem, though the initial IceTV update after a firmware restart can sometimes cause a short run of the spinner (a few seconds).

How many AutoTimers do you have?

Grumpy_Geoff · Post by **Grumpy_Geoff** » Sun May 03, 2020 14:37

RayCee wrote: ↑
Sun May 03, 2020 13:30
occurs predictably after adding an auto timer, otherwise every 20 ,minutes or so.

That certainly sounds like it's the AutoTimer plugin.
Is the poll interval set to 20 minutes in AutoTimer setup (AutoTimer list, then MENU>>6/Setup)?

Time how long an AutoTimer run takes - bring up the AutoTimer list and simply press GREEN/Save as it'll run the AutoTimer definitions over the EPG.

If you want to see which AutoTimer definition may be slowing the box down, bring up the definitions list and start a run as above, then press BLUE/Extensions list from live TV, then press OK on the AutoTimer background task at the top of the list to open it and watch as it progresses through the definitions one by one. If you do it quick enough then you won't miss too many at the start.

peteru · Post by **peteru** » Sun May 03, 2020 17:13

If it is an autotimer definition (and it most likely is), then the version of the firmware will have no impact. In fact, the older firmware with the same autotimer settings could be a little slower, thus showing the spinner for longer.

Going back to previous firmware is not likely to be the fix here.

RayCee · Post by **RayCee** » Sun May 17, 2020 13:43

Thanks, will try this
Ray

Bodogbodog · Post by **Bodogbodog** » Sun May 24, 2020 21:23

RayCee wrote: ↑
Sun May 17, 2020 13:43
Thanks, will try this
Ray

How did you go? Was this the cause of your issue?

I've started to get the wait wheel popping up on my T2 recently - the only way to stop it is to do a hard power off/on

raymondjpg · Post by **raymondjpg** » Mon May 25, 2020 11:09

Bodogbodog wrote: ↑
Sun May 24, 2020 21:23

RayCee wrote: ↑
Sun May 17, 2020 13:43
Thanks, will try this
Ray
How did you go? Was this the cause of your issue?

I've started to get the wait wheel popping up on my T2 recently - the only way to stop it is to do a hard power off/on

If the issue is not caused by an AutoTimer definition slowing the box down, then it might be worthwhile trying a reboot of the box to see if that fixes it. While the most recent public release firmware is the most stable I've seen so far my T2 still has a tendency to "lock up" now and then, and following advice from someone on this forum (I forget who) as a fix for unresponsiveness to the remote (which also required a hard power off/on) I have a power timer set that reboots the box once a day, which seems to keep the T2 running sweetly.

Bodogbodog · Post by **Bodogbodog** » Mon May 25, 2020 13:49

RaymondJpg
Thanks - sort of good to hear I’m not alone with hangs
I’ll have a bit more of a dig around. I doubt it’s the Timers issue as I never set any as I just use IceTV to setup recordings

Grumpy_Geoff · Post by **Grumpy_Geoff** » Mon May 25, 2020 15:10

Bodogbodog wrote: ↑
Mon May 25, 2020 13:49
I’ll have a bit more of a dig around. I doubt it’s the Timers issue as I never set any as I just use IceTV to setup recordings

Perhaps enable debug logging to see if anything is shown when the Wiz chucks a wobbly -
Setup>>System>>Log settings and restart the GUI (or in OWIF settings, Log settings [but restart the GUI twice if setting it this way]).

raymondjpg · Post by **raymondjpg** » Mon May 25, 2020 15:20

Bodogbodog wrote: ↑
Mon May 25, 2020 13:49
RaymondJpg
Thanks - sort of good to hear I’m not alone with hangs
I’ll have a bit more of a dig around. I doubt it’s the Timers issue as I never set any as I just use IceTV to setup recordings

Same here. I don't see any hangs with my U4 and the only difference in setup between my U4 and T2 is that the U4 uses FTA EPG and autotimers, and the T2 IceTV. I don't know if IceTV has anything to do with the hangs with the T2, I haven't seen any reports of that here. and I haven't run the T2 with FTA EPG and autotimers long enough to observe if it hangs with that setup. Conversely I haven't run the U4 with IceTV for long enough to observe if the U4 has any tendency to hang with that setup.

I'm inclined to think it is a T2 issue rather than anything to do with IceTV.

Bodogbodog · Post by **Bodogbodog** » Mon May 25, 2020 17:55

Grumpy Geoff - I looked for that option under Setup/Swttings and it’s not there - would this be a post 17.5 FW option?

I might also update to the latest version of the firmware - currently onn17.5

prl · Post by **prl** » Mon May 25, 2020 18:04

Bodogbodog wrote: ↑
Mon May 25, 2020 17:55
I might also update to the latest version of the firmware - currently onn17.5

I think you'd need to upgrade to a 19.3 release to get that option.

Bodogbodog · Post by **Bodogbodog** » Mon May 25, 2020 18:41

Thanks - I’ve downloaded that version and will do the upgrade tomorrow - maybe that in itself will solve the stability issue?

Grumpy_Geoff · Post by **Grumpy_Geoff** » Mon May 25, 2020 19:10

Bodogbodog wrote: ↑
Mon May 25, 2020 17:55
Grumpy Geoff - I looked for that option under Setup/Swttings and it’s not there - would this be a post 17.5 FW option?

Yep, the GUI setting is in 19.3's 20191106. But you can still use OWIF to set it, as that was the original old school method (before adoxa's change).

Bodogbodog · Post by **Bodogbodog** » Fri Jun 05, 2020 15:11

I've now upgraded to 19.3 and I still get the "revolving wheel" coming up - I've enabled logging but have no idea how to view let along interpret the logs

Is there anyone out there who can help me do some further troubleshooting (given 19.3 is pretty much a fresh install I'm wondering what could be causing it)

Thanks

Grumpy_Geoff · Post by **Grumpy_Geoff** » Fri Jun 05, 2020 16:49

Bodogbodog wrote: ↑
Fri Jun 05, 2020 15:11
Is there anyone out there who can help me do some further troubleshooting (given 19.3 is pretty much a fresh install I'm wondering what could be causing it)

Use File Commander to retrieve the debug log from wherever it's being written to (the default, if you didn't change the destination, is /home/root/logs, and you can get to it using the 'Logs' Samba share), plus these other two files from /var/log:
dmesg
messages

Attach them here (you may have to add a .txt suffix to allow them to attach to the forum).

Bodogbodog · Post by **Bodogbodog** » Mon Jul 20, 2020 12:30

I'm back - and still with the same issue - I have reloaded the T2 with the latest firmware and believe the hanging is being caused by IceTV - so I've asked IceTV if there is anything in my logs with them that shows an issue

Any suggestions on how I can find out on the T2 side of things what is going on with these periodic hangs - which sometimes even result in the T2 rebooting

I'm happy to send logs to anyone - but I don't really know how to get them off my T2 so would need help setting up the logs and then downloading them

It's so frustrating to have this happening irregularly so of course I'd like to try and resolve it

prl · Post by **prl** » Mon Jul 20, 2020 13:35

Which "latest" firmware: latest official (20191106), latest beta USB (20200328) or the latest online beta update (20200405)?

and when you have "periodic hangs - which sometimes even result in the T2 rebooting", is it a full reboot, showing the big Beyonwiz button, or is it a UI crash, showing a black screen with white text, then the "blue bubbles" splash screen without the big Beyonwiz button first?

I'm inclined to think that it's unrelated to IceTV, and even if it is that may not be much of use in the IceTV-side logs.

If you're seeing the GUI crash that I described above, there will be crash logs on the T2 that I can describe how you can fetch. Otherwise, there are only debugging logs if you have enabled them.

If you want to get debug logs, I can describe how you can enable them and then fetch them when they show something "interesting".

Grumpy_Geoff · Post by **Grumpy_Geoff** » Mon Jul 20, 2020 14:03

prl wrote: ↑
Mon Jul 20, 2020 13:35
If you want to get debug logs, I can describe how you can enable them and then fetch them when they show something "interesting".

Didn't I show that in viewtopic.php?p=188354#p187409
?

Bodogbodog · Post by **Bodogbodog** » Mon Jul 20, 2020 17:39

prl wrote: ↑
Mon Jul 20, 2020 13:35
Which "latest" firmware: latest official (20191106), latest beta USB (20200328) or the latest online beta update (20200405)?

1. Ive upgraded (fresh install) to the latest release software (didn't think it wise to go to beta given I'm already having issues)
2. The reboot results in the big Beyonwiz button - note the spinning wheel often reappears when it reboots

I would really appreciate assistance with getting the logs and then analyzing them

I have just enabled the debug logs in the options on the T2 - so they will be being created

So I guess at this point I standby waiting for it to crash again

Thanks

prl · Post by **prl** » Mon Jul 20, 2020 17:46

Bodogbodog wrote: ↑
Mon Jul 20, 2020 17:39
2. The reboot results in the big Beyonwiz button - note the spinning wheel often reappears when it reboots

It's most likely an operating system crash, and may be a hardware issue.

Bodogbodog wrote: ↑
Mon Jul 20, 2020 17:39
I have just enabled the debug logs in the options on the T2 - so they will be being created

If it is an OS crash, there may not be much of use in the debug logs, but it's worth having a look. Unfortunately, the OS log files are deleted if the OS crashes.

Bodogbodog · Post by **Bodogbodog** » Mon Jul 20, 2020 17:46

Grumpy_Geoff wrote: ↑
Mon Jul 20, 2020 14:03
Didn't I show that in viewtopic.php?p=188354#p187409
?

Geoff - I'm reasonably technical but I don't know Linux and don't know how to access or use the file commander - so I didn't pursue that - and like any normal user just put up with the crashes and hoped they'd go away (not much of a strategy is it!)

I can follow step by step guidance - and access the T2 from my Windows 10 PC on the same network although when I click on the Wiz icon under networking it is asking for a Username and Password - so any idea what that would be (I don't believe we've set one for the T2 (I'll check that with my son who "manages" our network

Bodogbodog · Post by **Bodogbodog** » Mon Jul 20, 2020 17:49

prl wrote: ↑
Mon Jul 20, 2020 17:46

It's most likely an operating system crash, and may be a hardware issue.

If it is an OS crash, there may not be much of use in the debug logs, but it's worth having a look. Unfortunately, the OS log files are deleted if the OS crashes.

The interesting thing is that the wheel can appear and spin for ages but the system doesn't reboot and it eventually resolves - so it doesn't always cause a reboot - so would that still indicate a hardware fault?

Bodogbodog · Post by **Bodogbodog** » Mon Jul 20, 2020 17:50

peteru wrote: ↑
Sun May 03, 2020 17:13
If it is an autotimer definition (and it most likely is), then the version of the firmware will have no impact

If it's this then what would I need to do to clear that issue?

Bodogbodog · Post by **Bodogbodog** » Mon Jul 20, 2020 17:54

prl wrote: ↑
Mon Jul 20, 2020 13:35
I'm inclined to think that it's unrelated to IceTV, and even if it is that may not be much of use in the IceTV-side logs.

I just heard from Daniel at IceTV

"I can't see anything out of the ordinary in your logs, or on your account.
The only anomaly is that your Beyonwiz is only updating every 30 minutes, but that wouldn't cause this to happen.
There may be more information available in the debug logs on the Beyonwiz but I can't confirm that, if you are talking about it on the Beyonwiz forum then I am sure that prl would be able to give some better advice as to the cause.
Regards,
Daniel Hall
CTO
TV TV Australia Pty Ltd trading as IceTV"

I set the IceTV update out to 30 minutes from the 15 minute default trying to delay the crash - but it still fails eventually and certainly doesnt hang every 30 minutes so it's probably not the update process causing the revolving wheel/hang

prl · Post by **prl** » Mon Jul 20, 2020 18:05

Bodogbodog wrote: ↑
Mon Jul 20, 2020 17:50

peteru wrote: ↑
Sun May 03, 2020 17:13
If it is an autotimer definition (and it most likely is), then the version of the firmware will have no impact
If it's this then what would I need to do to clear that issue?

Do you use AutoTimers?

Bodogbodog · Post by **Bodogbodog** » Mon Jul 20, 2020 18:12

prl wrote: ↑
Mon Jul 20, 2020 18:05
Do you use AutoTimers?

I use IceTV to set all my Timers - so I assume that means no I don't?

prl · Post by **prl** » Mon Jul 20, 2020 18:19

Bodogbodog wrote: ↑
Mon Jul 20, 2020 18:12

prl wrote: ↑
Mon Jul 20, 2020 18:05
Do you use AutoTimers?
I use IceTV to set all my Timers - so I assume that means no I don't?

There are IceTV users who also use AutoTimers. Since you say you use IceTV to set all timers, then presumably you don't use AutoTimers. You can check by looking in MENU>AutoTimer, and seeing if any are listed.

Bodogbodog · Post by **Bodogbodog** » Mon Jul 20, 2020 18:40

prl wrote: ↑
Mon Jul 20, 2020 18:19
You can check by looking in MENU>AutoTimer, and seeing if any are listed.

Just checked and can confirm that there is nothing listed under Auto Timers

No hangs since I enabled logging (although the T2 has hung since reinstalling) - so the "patient" is under observation

Grumpy_Geoff · Post by **Grumpy_Geoff** » Mon Jul 20, 2020 19:01

Bodogbodog wrote: ↑
Mon Jul 20, 2020 17:46

Grumpy_Geoff wrote: ↑
Mon Jul 20, 2020 14:03
Didn't I show that in viewtopic.php?p=188354#p187409
?
Geoff - I'm reasonably technical but I don't know Linux and don't know how to access or use the file commander - so I didn't pursue that - and like any normal user just put up with the crashes and hoped they'd go away (not much of a strategy is it!)

I mentioned to use File Commander. That's a plugin on your Wiz, and you get to it from MENU>>Sources / Files.
Navigate through Internal Flash / then 'home', then 'root', then 'logs' (/home/root/logs/).
If a crash log is present, copy the log to a USB drive -
Have the log directory open in one File Commander panel/pane and the USB drive open in the other pane (you can use PREV/NEXT to switch panes).
Then select a crash log from the "log" pane and copy it to the "USB" pane using YELLOW/Copy (the active panel is the source).
Pressing MEDIA will allow multiple files to be selected (OK to toggle file selection).
Exit back to live TV.
To eject/unmount the USB, use the 'SimpleUmount' plugin, which is located towards the bottom of the plugins column of the main menu.

I mentioned another option of using the 'Logs' Samba share - that is accessing the same default logs directory by using Windows File Explorer from your computer, exploring the network connection to the Wiz, where the 'Logs' share should show (in addition to the 'Movie' share).

Bodogbodog · Post by **Bodogbodog** » Mon Jul 20, 2020 19:37

Grumpy_Geoff wrote: ↑
Mon Jul 20, 2020 19:01
I mentioned to use File Commander. That's a plugin on your Wiz, and you get to it from MENU>>Sources / Files.

Perfect instructions and I managed to follow them to access the logs - here's the crash from yesterday evening

MrQuade · Post by **MrQuade** » Mon Jul 20, 2020 19:54

It looks like you tried to delete something called "192_TVShows" with the RED button and it crashed. Is that a shared folder somewhere on your network? Trying to delete a mounted filesystem probably wouldn't end well.

Also, it looks like you are navigating down from your movie folder into the /media directory to get to network mount points? That's a bit of a messy way of navigating around the Wiz. You are better off (IMHO) using the "Locations" shortcut which is hotkeyed to YELLOW by default.

You can also set your Media Player "root directory" to hide all directories below "movie" so that you don't accidentally navigate away from your recordings and into the guts of the T2's filesystem.

Bodogbodog · Post by **Bodogbodog** » Mon Jul 20, 2020 20:21

MrQuade wrote: ↑
Mon Jul 20, 2020 19:54
It looks like you tried to delete something called "192_TVShows" with the RED button and it crashed. Is that a shared folder somewhere on your network? Trying to delete a mounted filesystem probably wouldn't end well.

Thanks for the shortcuts and navigation tips

Yes - Busted on trying to delete the Network Mount as I don't like the name it assigned to it - so I'll try Unmounting it before deleting it

Yes - I never realised that shortcut using the Yellow button was there - will look to use that moving forward

So basically I'll wait for the return to the "wheel of death" - until then it's humming along normally - so will this log file "trap" what happens? - Hope so

MrQuade · Post by **MrQuade** » Mon Jul 20, 2020 20:36

Bodogbodog wrote: ↑
Mon Jul 20, 2020 20:21
Yes - Busted on trying to delete the Network Mount as I don't like the name it assigned to it - so I'll try Unmounting it before deleting it

Once the mount point is removed via the network mount manager, the directory will be automatically removed as well

. You can name the new mount point anything you like

.

And yep, you can grab the log files again the next time something bad happens.

Grumpy_Geoff · Post by **Grumpy_Geoff** » Mon Jul 20, 2020 21:15

Bodogbodog wrote: ↑
Mon Jul 20, 2020 20:21
Yes - Busted on trying to delete the Network Mount as I don't like the name it assigned to it - so I'll try Unmounting it before deleting it

You can use the Mount viewer screen to edit the local share name (Setup>>Network>>Mount manager>>Mountpoints management).
Select the '192_TVShows' mount entry and press OK to open the Mounts editor screen for that mount. Cursor down to the Local share name field, press TEXT to bring up the virtual keyboard and edit the name.
GREEN/Save, reply 'yes' to the prompt, wait for the update, then wait out the prompt or OK it. I always reboot after a mount change.

peteru · Post by **peteru** » Mon Jul 20, 2020 23:00

With autotimers out of the equation, the most likely culprit would be an intermittent hard disk or unreliable network.

The spinning wheel is an indication that the Beyonwiz is waiting on "something" to complete and that "something" is taking way too long. A HDD that is experiencing issues or a network mount from a file server that is not responding, are two good examples.

The third potential source of problems could be a failing power supply, but that would most likely exhibit as unrecoverable crashes, rather than delays that can come good.

Bodogbodog · Post by **Bodogbodog** » Mon Jul 20, 2020 23:28

peteru wrote: ↑
Mon Jul 20, 2020 23:00
With autotimers out of the equation, the most likely culprit would be an intermittent hard disk or unreliable network.

OK - I have spare 1gb drive - ex my Skippa (now there’s a blast from the past!) - so that’s easy to try - although then I’ll lose our current recordings won’t I? Btw What’s the max size internal HDD the T2 can accomodate?

I think the network is good - Cat 6 cabled LAN and a nice healthy 100/40 NBN connection for the updates (at long last - we only got that a few weeks ago)

First I’m going to wait for the spinning wheel and/or a crash and I’ll post the logs for review to see if it’s telling us anything - if nothing then I’ll start on the hardware

MrQuade · Post by **MrQuade** » Mon Jul 20, 2020 23:34

Bodogbodog wrote: ↑
Mon Jul 20, 2020 23:28
OK - I have spare 1gb drive - ex my Skippa (now there’s a blast from the past!) - so that’s easy to try - although then I’ll lose our current recordings won’t I? Btw What’s the max size internal HDD the T2 can accomodate?

No practical size limit.

Grumpy_Geoff · Post by **Grumpy_Geoff** » Mon Jul 20, 2020 23:51

peteru wrote: ↑
Mon Jul 20, 2020 23:00
The spinning wheel is an indication that the Beyonwiz is waiting on "something" to complete and that "something" is taking way too long.

The crash log shows the oom-killer being invoked in the dmesg dump.
I'm not smart enough to know if it's related to the crash.

Code: Select all

<3>Out of memory: Kill process 713 (enigma2) score 629 or sacrifice child
<3>Killed process 713 (enigma2) total-vm:264844kB, anon-rss:150024kB, file-rss:8kB

peteru · Post by **peteru** » Tue Jul 21, 2020 04:40

If enigma2 is killed because of oom, that won't give a crash with an error log like we see. So, those two are separate incidents.

Looking at the memory usage numbers in the oom-killer report, there's nothing that sticks out as being way too obvious in terms of runaway memory use. Comparing the figures to a T4 with 24 days uptime, samba uses about 20% more memory and enigma2 about 30% more memory. I guess those two might add up to push the T2 to the limit.

If you are not using DLNA (and you probably should not be), you could save some memory by disabling minidlnad and djmount.

Based on the evidence collected so far, I'd say that your issues are network related. What are you connecting to? An old NAS?

Try a test: Unplug the Ethernet cable and reboot. Use your T2 for a few hours without network - did the spinner stop appearing as a result?

Bodogbodog · Post by **Bodogbodog** » Tue Jul 21, 2020 06:50

Thanks to all of you for assisting me troubleshoot this - at this point I wait for a new crash so we can hopefully capture something in the logs

Of course as you all know they inevitably don’t occur when the patient is under observation...but I’m sure they’ll show themselves soon enough

I’ll update as soon as I have something captured

Peter - how do I disable those DLNA processes?

Grumpy_Geoff · Post by **Grumpy_Geoff** » Tue Jul 21, 2020 09:14

Bodogbodog wrote: ↑
Tue Jul 21, 2020 06:50
how do I disable those DLNA processes?

Setup>>Network>>DLNA server. Press GREEN/Stop, then YELLOW/Autostart - Autostart and Current status indicators should show 'Disabled' and 'Stopped'.
It's not permanent though, as it can autostart after an online update, and will autostart after a USB firmware flash.

Bodogbodog · Post by **Bodogbodog** » Sun Jul 26, 2020 18:52

I'm back after an uneventful week in terms of crashes - which was very pleasant

I did have one crash during the week but that happened when I tried to watch You Tube via the T2 - that just crashed it repeatedly and produced lots of log files - I didn't post them though as I wondered if that You Tube option might be a bit flaky

But just now we were watching a movie from our Server (cabled to the same network as the T2 sits on with it via a cabled connection) and after about 90 minutes into it the revolving wheel appeared - after several minutes the T2 returned to responsiveness (the News was recording in the background and appears to have stayed recording)

Anyway here's the Log that was generated. Does it tell us anything interesting/useful?

Grumpy_Geoff · Post by **Grumpy_Geoff** » Sun Jul 26, 2020 19:15

Bodogbodog wrote: ↑
Sun Jul 26, 2020 18:52
Anyway here's the Log that was generated. Does it tell us anything interesting/useful?

Possibly the hard drive isn't keeping up:

Code: Select all

{13828}<362006.855> [gRC] main thread is non-idle! display spinner!
{14567}<362264.030> [eFilePushThreadRecorder] OVERFLOW while recording
... repeats 25 more times, then the last at
{14567}<362445.155> [eFilePushThreadRecorder] OVERFLOW while recording

I think that means the data can't be written fast enough, so the buffer space isn't being freed fast enough.
Perhaps a dicky SATA cable connection?

Bodogbodog · Post by **Bodogbodog** » Sun Jul 26, 2020 19:49

Thanks and really do appreciate the review of the log and ideas as to the cause

Is there an option in a setting somewhere to increase the buffer space allocated at all?

Re the SATA connection cable option - it seems strange it would be so intermittent- given its run for several days without an issue and then hangs and this time actually recovers

If someone can tell me what I need to look for in the log I'm happy to search them myself

Grumpy_Geoff · Post by **Grumpy_Geoff** » Sun Jul 26, 2020 20:51

Bodogbodog wrote: ↑
Sun Jul 26, 2020 19:49
Re the SATA connection cable option - it seems strange it would be so intermittent- given its run for several days without an issue and then hangs and this time actually recovers

The issues may not be related though.

Bodogbodog · Post by **Bodogbodog** » Mon Jul 27, 2020 14:42

Todays hang log - the hang occurred while watching a movie streamed from our server (all units on a cabled LAN) - I was eventually able to get it to "stop" by hitting stop a number of times. So it does seem like a buffer limit was reached which caused it to hang
But appreciate advice from someone who can interpret the log file to see what happened - and suggest a solution?

prl · Post by **prl** » Mon Jul 27, 2020 16:25

I can't see anything obvious in the logs around when you had the long hang followed by multiple presses of STOP (at about 2554389 25540007).

An odd thing is that about 5 minutes elapses between the last time the log shows the spinner running and when you pressed STOP (or at least when it was processed).

Grumpy_Geoff · Post by **Grumpy_Geoff** » Mon Jul 27, 2020 17:13

Bodogbodog wrote: ↑
Mon Jul 27, 2020 14:42
But appreciate advice from someone who can interpret the log file to see what happened - and suggest a solution?

Perhaps it's the online update check, as it took 867 secs on that occasion.
Turn the automatic check off and monitor.
More likely though either your router or your NAS/file server is crappy. Do you only get the spinner when playing from that source?

Code: Select all

{13825}<434017.510> [IPKG] executing opkg list-upgradable
{13825}<434017.511> [eConsoleAppContainer] Starting /bin/sh
{13828}<434045.187> [gRC] main thread is non-idle! display spinner!
{13828}<434050.897> [gRC] main thread is non-idle! display spinner!
{13828}<434060.753> [gRC] main thread is non-idle! display spinner!
{13828}<434078.118> [gRC] main thread is non-idle! display spinner!
{13828}<434096.764> [gRC] main thread is non-idle! display spinner!
{13828}<434105.091> [gRC] main thread is non-idle! display spinner!
{13828}<434438.393> [gRC] main thread is non-idle! display spinner!
{13828}<434464.095> [gRC] main thread is non-idle! display spinner!
... STOP pressed multiple times
{13825}<434884.327> [OnlineVersionCheck] 0 updates available

About the Forum

Join us