Ugoos SK1 (S928X) - Hard lockup when using USB Microphone (G20S Pro)

Subject: Ugoos SK1 (S928X) - Hard lockup when using USB Microphone (G20S Pro)

Device: Ugoos SK1 (S928X)
Version: CoreELEC 22.0-Piers_alpha3 (Amlogic-no)
Remote: G20S Pro (USB Dongle)

Issue:
The system completely freezes (hard lockup) as soon as the microphone button is pressed or any attempt is made to record audio via the USB dongle. The only way to recover is a hard power cycle.

Technical details:
The remote is detected as card 1: Device [USB Composite Device], device 0: USB Audio.
When trying to capture audio (arecord -D hw:1,0 -f S16_LE -r 16000), the system hangs immediately.

Relevant dmesg output before the crash:

PHL: this wp is tx fail (LIFETIME_DROP)
aml_audio_reset, reg 0xa, shift 9, use_vadtop 0
[WARNING] polling Rx Tag fail, tag = 0, target_tag = 65

Additional info:

  • Bluetooth is also not working on this build for SK1.

  • Tried different USB ports (2.0 and 3.0), the result is the same.

  • On v21.3 (Omega), the UI is glitchy in 4K, which is why I’m testing v22-alpha3.

It seems like a kernel/driver issue with the USB controller on S928X regarding isochronous transfers for USB Audio. Any help or a test build would be appreciated!

Just an update: I noticed that exactly when I press the mic button, the audio signal to my AVR (Receiver) drops/disconnects for a split second, and then the whole system freezes. It looks like a direct resource conflict between HDMI-audio and USB-audio in the S928X SoC.

Disable this audio device somehow?

ā€œI don’t want to disable the microphone permanently. My goal is to make voice search work via the VoiceSST (service.voice.assistant) plugin on my Ugoos SK1. Right now, it’s the only thing causing these hard lockups. I am ready to provide any logs or test new builds to help fix this driver conflict between HDMI-audio and USB-audio.ā€

Got it.
Hard to fix such issues without hw. I think you are on your own for now.

Effort might be better spent getting bluetooth working then you can try to use a bluetooth voice remote like every other platform.

"I’ve updated to the latest build, but Bluetooth is still not working on Ugoos SK1. I’m getting a ā€˜Bluetooth error: Page Timeout’ (see screenshot). Since Bluetooth is unavailable, I have to use the 2.4G USB dongle, which continues to cause hard lockups with the polling Rx Tag fail error in dmesg. It seems both USB-audio and Bluetooth drivers for the Unisoc/S928X SoC are still unstable in this alpha."

PR welcome :frowning:

For reliable BT use USB dongle. I’m making one seting in CE Kodi addon to select the adapter. It is annoying to test all possible combinations that’s why it took longer than I though.

Yea I got that, you would have used bluetooth but it doesn’t work so you went with USB.

Now USB doesn’t work either so you’re trying to put effort into fixing the USB rather than fixing the real initial issue of fixing bluetooth.

Therefor my comment that it would likely be better to spend effort on fixing the real issue instead of fixing the workaround.

Side question, would a bluetooth USB dongle work or is bluetooth in general broken?

I think those things are cheap, at least used to be.

Apologies but I think your making some incorrect assumptions. The hardware I believe that was being mentioned was not only the usb mike or dongle but also the Ugoos SK1.

Also, again aplogies, but your presumption that they are trying to fix some peripheral issue instead of a core problem does not bear out and you unfortunatley phrase it in a way that, to my ears, is rather insulting.

What? The thread title is ā€œHard lockup when using USB Microphone (G20S Pro)ā€ so there is no presumption, that is exactly what they posted about to fix.

Then take your wokeness to your settings and put me on ignore.

I have no reason to even be responding here except I feel bad for users who can’t get answers.

Your lack of appreciation that I took time out of my day to even post here is insulting.

I’m far from woke. I do try and be polite. That you use woke couched in terms means you mean to be it insulting. I really think, so what…

But since you project an aura of busy success it would behoove you to offer a copy of your hardware to these developers so that they can actually focus on your specific issue and provide benefit to other users.

Update on testing with config.ini (Ugoos SK1 / S928X):

I tried to stabilize the USB bus by adding usbcore.autosuspend=-1 and setting usbpower=1 in config.ini.

Results:

On the first attempt after reboot, the microphone button worked and the system did NOT freeze immediately. However, during the second attempt or after a few seconds of recording, the system hit a hard lockup again.

This suggests that while disabling USB power management helps with the initial handshake, there is still a critical IRQ / Buffer overflow issue in the S928X USB-audio driver (the polling Rx Tag fail error we saw earlier).

It seems the kernel can’t handle the high polling rate (bInterval 1) of the G20S Pro remote under the current alpha3 build.

ā€œThanks for the suggestion, but the issue is that the VoiceSST plugin I use is specifically designed to work with USB-audio (ALSA) devices. Fixing Bluetooth is great, but it doesn’t solve the core problem: a hard lockup caused by the USB-audio driver on the S928X SoC. I’d rather help developers fix the underlying USB issue (the Rx Tag fail error), as it’s a critical system bug.ā€

1 Like

Currently for you only.
And as I wrote: only you have this remote which means you can’t expect must to be fixed by devs if they don’t even has the device. CE is not some big crew of 100 people to be able address every single issue it pops up. Sadly that’s the truth.