Am6b+ buffering issues

Hello, Ive got the Ugoos Am6b+ with Coreelec Stable installed on emmc but I have 1 issue:

I sometimes have buffering issues (video cache goes down to 0% for few seconds) and video stops playing. I am using PM4K with SMB path mapping (because I wanted to try if this resolves that issue). This happens pretty randomly, on high and also low-bitrate files. When I close the player and I start playing again from the same spot it plays like nothing happened.

I have Plex running on Unraid with an i3 8100. The strange thing is, the moment this happens I also have increasing CPU I/O wait up to 80%. I’ve never had this issue with other plex player, like LG’s Plex app, Plex for Android or with Jellyfin. I first thought it was an HDD issue but it happens with files from different HDDs. Right now I have a SATA extension card but already ordered a Lsi 9300-8i, just to be sure its not a hardware bottleneck.

I followed the recommended settings (especially for caching), also tried other caching settings (4x speed factor, etc.), without success.

Ugoos is conected via ethernet (CAT7 cables), TP Link Gigabit Switch. Also tried Wifi only, same results.

Also tried Nightly.

Would really be nice if anyone could help me resolve this as this is really frustrating and besides from that i really love that thing.

Log files will follow…

No log, no problem.

Use CE-22, CE-NO.

Yes I’m sorry, provide log files as soon as I can.
Currently I have 21.2 NG installed, guess thats my first mistake. Can I just update from NG to NO? (Copy to Update folder, restart device)?

log_21.2.txt (122.8 KB)

OK so here’s the log file from when the error happened, note that this is still 21.2 NG.

Will update to CE-22 NO now and see what happens, and provide a log file from that too if error still persists.

I would suggest you supply the complete debug file per the instructions here:

https://wiki.coreelec.org/coreelec:debuglogs

Ok, so I’ve updated to CE-22 NO, but after first start I got the info message that Dolby Vision kernel module is not compatible with the kernel (minimum Linux kernel version 5.15.137). I’ve checked if there are any updates for the AM6b+ but I’m on the latest 0.5.4n firmware. Also had PM4K crash a few times.

So I’ve decided to do a fresh 21.2 NG Stable install on emmc (ofc. i followed recommended settings from here again). I was hoping maybe the fresh install would solve it, but unfortunately not.

Here is my complete log file. As you can see there, it took a bit to reproduce the error, but error startet at time ~ 11:33.

At the exact same time I had I/O-wait on my server (see below). But again: This only happens when using this player!

Read forum and try again with CE-NO!!!
CE-NG is EOL!

Did you copy coreect one to device? I assume not.

I think you need to read few threds on forum because helping with same issues again and again sucks.

I’m sorry, just trying my best to get this working. I can understand this might be a bit frustrating for you.
I now did the following:

  • Freshly install CE 22 NG on emmc
  • Used this dovi.ko *

Was able to catch the error one time again. Here is the log file, it happened at ~ 16:42.

*@vpeter you mentioned here that we must use a dovi-dummy. With that DV didn’t work obviously. Why would I need the file then? Did I use the correct one?
And sorry, if this is too much off-topic: Will there be FEL support at anytime for the AM6b+ on CE22 NO?

EDIT: I found it, FEL won’t be supported

This question was answered many times

1 Like

Here’s another log file, error was more consistant here.

For me it looks like a addon or network issue:
https://paste.kodi.tv/voxutulugu

You see it goes up and then down again to 0, so no data got added from file to buffer. After a while data start to come in again.

Thanks for looking into it.
Given that I also have I/O wait on the server when it happens I guess it’s a hardware issue then. Just strange it seems that its only happening with my Ugoos.

just an fyi. Spinning disks have very limited iops. (io operations per second). In practice, if one is doing something else io intensive on the disk at the same time, it can exhaust the by default very small buffer that the kodi is configured to have (which is generally sufficient for local LAN access). For those with SSDs, This is less likely to be seen.

You can try making the buffer relatively large (i.e. measured in MBs vs KBs). The negative of this is that it will take longer for things to load (especially if using addons to provide internet based streams).

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.