The linux config changed and you might have something not compatible installed (kernel module).
Make a clean fresh install and try again. The reboot loop can come up again when restore a backup including non compatible items again.
I’ve got the same issue and all I have is a skin and jellyfin for Kodi plugin installed
First make a fresh & clean install and check without any addon/plugin
“just a skin” could be the issue
Well I did a clean install and still got a bootloop
Figured the issue out, remove the sdcard
Mensur
21 August 2026 10:49
376
I probably missed something - can CE on AM9 pro be booted only from a USB stick, without using an SD card?
vpeter
21 August 2026 10:52
377
It can boot from USB or SD.
Mensur
21 August 2026 11:36
378
sorry if this has been explained somewhere before, but this is quite confusing to me: after removing the sd card, as @RoninByte wrote, and unplugging the power, the system next time actually boots my coreelec (while only a USB stick is plugged in). When selecting the restart option while in coreelec, the device reverts to android. Now how do I go back to coreelec if the SD card is removed all the time?
vpeter
21 August 2026 11:38
379
Reboot from CE doesn’t work reliably and will be fixed in next Android release from Ugoos.
You need to shutdown from CE.
I’m having this weird issue where my ugoos included remote control stopped suddenly adjusting volume on my soundbar. It used to work fine a few weeks ago. Now I have to grab my TV remote control to change volume.
I tried unplugging all devices from power and the issue was not fixed.
I’m using the latest version of CoreELEC.
Is this a know issue or something wrong in my setup?
master ← opdenkamp:cec-tv-volume-control
opened 09:52AM - 09 Aug 26 UTC
## Description
Lets Kodi's volume keys control the TV over CEC when there is no… amplifier on the bus, instead of falling back to Kodi's own mixer.
`HasAudioControl()` no longer means "an amp is connected" but "some CEC device takes volume", backed by a new `m_volumeTarget` holding `CECDEVICE_AUDIOSYSTEM`, `CECDEVICE_TV` or `CECDEVICE_UNKNOWN`. Every existing caller — `CPeripherals::OnAction`, `ToggleMute`, `IsMuted` — keeps working unchanged, so no new action IDs and nothing outside the CEC adapter had to move.
The target is picked in `UpdateAudioSystemStatus()`, which already runs on the initial configuration and on every configuration update, so changing the setting re-evaluates it through the existing `OnSettingChanged` path.
New setting `volume_control`, default *Automatic*:
| Value | Behaviour |
| --- | --- |
| None | Never send volume over CEC — Kodi's own mixer, as today without an amp |
| Automatic | The amp if one is present, otherwise the TV if it reports CEC 2.0 |
| Always | The amp if one is present, otherwise the TV regardless of the version it reports |
CEC 2.0 is the first version that requires a TV to act on `<User Control Pressed>` volume commands, so the version the TV reports is what the default keys off. It is discovered with `GetDeviceCecVersion()`, which uses `<Get CEC Version>` — a CEC 1.4 opcode, so no CEC 2.0 support is needed in libCEC. *Always* covers TVs that honour volume commands without reporting 2.0.
Unmuting Kodi and pinning its volume to maximum, which previously happened only when an amp was found, now happens for whichever target is chosen and is skipped when volume stays with Kodi.
## Motivation and Context
Implements the request in https://forum.kodi.tv/showthread.php?tid=211527.
Supersedes #18521, which took a different approach: it added dedicated `ACTION_CEC_VOLUME_UP` / `ACTION_CEC_VOLUME_DOWN` actions. Those are not needed — `ACTION_VOLUME_UP` already reaches `CPeripherals::OnAction()` ahead of Kodi's global volume handling — and that PR kept the `HasAudioControl()` gate, so it did not change anything for the setup the forum request is about.
## How Has This Been Tested?
Not yet runtime tested; it compiles clean. Testing wanted on:
- an amp on the bus — behaviour should be unchanged
- a TV reporting CEC 2.0, no amp — volume keys should reach the TV
- a TV reporting CEC 1.4, no amp — volume keys should stay with Kodi on *Automatic* and reach the TV on *Always*
## Types of change
- [ ] **Bug fix** (non-breaking change which fixes an issue)
- [ ] **Clean up** (non-breaking change which removes non-working, unmaintained functionality)
- [x] **Improvement** (non-breaking change which improves existing functionality)
- [x] **New feature** (non-breaking change which adds functionality)
- [ ] **Breaking change** (fix or feature that will cause existing functionality to change)
- [ ] **Cosmetic change** (non-breaking change that doesn't touch code)
- [ ] **None of the above** (please explain below)
## Notes for reviewers
- The default changes behaviour for existing users with no amp and a CEC 2.0 TV: volume moves from Kodi's mixer to the TV, and Kodi is pinned to 100%. Happy to default to *None* if opt-in is preferred.
- Audio on a non-HDMI output (S/PDIF, USB) with HDMI video is the case this does not handle: volume keys drive a TV that is not rendering the audio, and *None* is the only way out. The amp path has always had the same flaw, so I kept the two consistent rather than fixing one half.
- Mute state is tracked locally and flipped on send. Nothing reconciles it with a TV that disagrees.
- #28855 reworks the same functions and conflicts with this; whichever lands first, the other gets rebased on top.
- New strings take 36055/36056. #28892 claims the same IDs, so one of the two will need renumbering.
So find last working version and make cec kodi log before and after and create a issue at https://github.com/xbmc/xbmc/issues:
Index of /Amlogic-no/CE-22/
Same problem here, after CE updates. An extra box restart fixed the CEC sound control problem.
In the HDMI settings. I think it was called CEC adapter? There is an option to send CEC command and the default was automatic. Setting this to Always fixed the issue for me. I think it used to work like this anyway.
New Firmware:
Android 14 Ugoos AM9 Pro Firmware v. 2.2.0
1. Fixed system crashes
2. Fixed storage unmounting issues
3. Audio passthrough fixes
4. Added automatic system bars hiding option
5. Added Samba server status to Hardware Monitor
6. Added an option to disable Hardware Monitor in the status bar
7. Added Processes window
8. Added new Power Menu
9. Added new features to Update Service
10. Updated UPlayer to version 0.6.3
11. Fixed Gallery2 photo editor crash
12. Many other system changes
2026-09-07
anyone got any issues with CE after updating to latest Android firmware?
ugoos am9 pro update 2.2.0 fw, take care - it’s breaks CE, probs need new dtb
Screen Zoomed and stretched, then cursor appears in left up corner and picture totally freezes. RC not working.
Don’t update to 2.2.0 !!!
Waiting for info from Ugoos about their changes, because they break graphical part fully