Just received/setup the AM6B+, following the guide:
Did the eMMC-install (CoreELEC-Amlogic-ng.arm-21.2-Omega_nightly_20250205-Generic), and changed to HS400. Managed to get the included (UR-01?) remote to work. Also managed to get my Logitech Harmony to work (MCE).
I can power-off/suspend with the MCE and with the UR-01 (red button), but none of them will power-on/resume. Works with button on the box though.
Have been searching, and it seems it might not be able to power-on/resume using MCE? But should be possible with the UR-01? Am I doing something wrong?
If anyone knows how to fix this, it would be great! Having it running 24/7 seems less than ideal, and having to use the button on the box is an inconvenience.
â systemd-suspend.service - System Suspend
Loaded: loaded (/storage/.config/system.d/systemd-suspend.service; static)
Active: inactive (dead)
Feb 07 12:06:16 Ugoos-media systemd[1]: /storage/.config/system.d/systemd-suspend.service:12: Unbalanced quoting, ignoring: "/bin/sh -c " systemctl mask suspend.target;"
Feb 07 12:06:16 Ugoos-media systemd[1]: systemd-suspend.service: Unit configuration has fatal error, unit will not be started.
Feb 07 12:06:41 Ugoos-media systemd[1]: /storage/.config/system.d/systemd-suspend.service:12: Unbalanced quoting, ignoring: "/bin/sh -c " systemctl mask suspend.target;"
Feb 07 12:06:41 Ugoos-media systemd[1]: systemd-suspend.service: Unit configuration has fatal error, unit will not be started.
Feb 07 12:07:44 Ugoos-media systemd[1]: Starting systemd-suspend.service...
Feb 07 12:07:44 Ugoos-media systemctl[4490]: Created symlink /storage/.config/system.d/suspend.target â /dev/null.
Feb 07 12:09:11 Ugoos-media sh[4587]: Can't open /dev/amremote .
Feb 07 12:09:12 Ugoos-media systemctl[4489]: Removed "/storage/.config/system.d/suspend.target".
Feb 07 12:09:12 Ugoos-media systemd[1]: systemd-suspend.service: Deactivated successfully.
Feb 07 12:09:12 Ugoos-media systemd[1]: Finished systemd-suspend.service.
Specifically pay attention to the script following ExecStart=/bin/sh -c. It starts with a quote " and then even line ends with a backslash . Make sure that each line, even empty lines ends with a backslash, and that there is a close quote at the very end of the script.
The backslashes are line breaks to make the script more readable.
If you still get an error after that, post your suspend service file
Here is the daemon status and the service file.
Still does not work.
Do I need to run the âInject BL301 Blobâ to get this working? Searches tell me that comes with the risk it might brick the device, so to be prepared to perform full restoreâŚ
â systemd-suspend.service - System Suspend
Loaded: loaded (/storage/.config/system.d/systemd-suspend.service; static)
Active: inactive (dead)
Feb 09 12:26:35 Ugoos-media sh[4361]: /bin/sh: line 1: printf: write error: Operation not permitted
Feb 09 12:26:36 Ugoos-media systemd[1]: systemd-suspend.service: Deactivated successfully.
Feb 09 12:26:36 Ugoos-media systemd[1]: Finished systemd-suspend.service.
Feb 09 12:26:51 Ugoos-media systemd[1]: Starting systemd-suspend.service...
Feb 09 12:26:51 Ugoos-media systemctl[4448]: Created symlink /storage/.config/system.d/suspend.target â /dev/null.
Feb 09 12:26:51 Ugoos-media sh[4447]: /bin/sh: line 1: printf: write error: Operation not permitted
Feb 09 12:27:46 Ugoos-media sh[4514]: Can't open /dev/amremote .
Feb 09 12:27:46 Ugoos-media systemctl[4447]: Removed "/storage/.config/system.d/suspend.target".
Feb 09 12:27:51 Ugoos-media systemd[1]: systemd-suspend.service: Deactivated successfully.
Feb 09 12:27:51 Ugoos-media systemd[1]: Finished systemd-suspend.service.
~
~
~
~
~
~
~
~
~
Ugoos-media:~/.config/system.d # cat systemd-suspend.service
[Unit]
Description=System Suspend
[Service]
Type=oneshot
ExecStart=/bin/sh -c "\
systemctl mask suspend.target; \
\
# Disable anything that might wake from suspend early \
# echo disabled > /sys/devices/platform/bt-dev/power/wakeup \
# echo disabled > /sys/devices/platform/ff80023c.aocec/power/wakeup \
echo disabled > /sys/devices/platform/rtc/power/wakeup; \
echo disabled > /sys/devices/platform/rtc/input/input1/power/wakeup; \
echo disabled > /sys/devices/platform/ff3f0000.ethernet/power/wakeup; \
\
# Turn off TV \
printf '\x20\x36' > /dev/aocec; \
\
# Pause Kodi \
pkill -STOP kodi.bin; \
\
# Suspend-to-idle \
echo freeze > /sys/power/state; \
\
# Wakeup \
# Turn on TV \
printf '\x20\x04' > /dev/aocec & \
\
# Reset meson_remote \
modprobe -r meson_remote && modprobe meson_remote; \
remotecfg /storage/.config/remote.conf; \
\
# Unpause Kodi \
pkill -CONT kodi.bin; \
\
systemctl unmask suspend.target; \
"
Ugoos-media:~/.config/system.d #
Broadcast message from root@Ugoos-media (Sun 2025-02-09 12:00:14 CST):
The system will suspend now!
Have not run the âInject BL301 Blobâ since searches tell me: âSome firmware updates for the Ugoos AM6b+ have included encryption on the bootloader, making BL301 injection impossible on those versions. For instance, firmware versions like 0.3.9 and later have this issue, as mentioned in discussions on forums like CoreELEC and Ugoosâs official communications.â
Any changes needed in CoreELEC -Hardware page? The only one I changed was the âeMMC speed Modeâ which was changed to âHS200,HS400â.
For the âstep 7â, I initially did add it, but the Harmony MCE IR would not work at all, as soon as I removed it, everything except for wake-up seems to work fine from IR.
What MCE device do you have on your harmony?
I have tried these 2:
Microsoft MCE-1039
Asrock ION 330HT
The Asrock one since searches tell me thart one can work better for some finicky devices.
The bl301 injection tool isnât needed or used for the suspend service script. Like you said, the AM6+ bootloader has been encrypted for quite some time now, that tool canât be used.
Even though IR wake doesnât work for the AM6+, CEC wake still does. I think itâs common for AM6+ owners to rely on CEC wakeup instead. You may even be able to program the power button on your remote to power your TV on/off. Then setup CE to suspend when TV power is off, and it will wake when you power the TV on (via CEC).
Regarding the suspend service script, is the AM6+ going to sleep and not waking, or is it not going to sleep? Waking from suspend requires using a remote.conf (amremote driver) file, and assigning 116 (power) to one of the remote buttons. The shutdown function should also be changed to suspend if you want to use the same power button to also suspend CE
Settings > System > Power saving > Shutdown function > Suspend
IR power off and resume, via a Harmony, definitely works for the AM6B+ here, multiple times every dayâŚwith a completely vanilla CE 21.2 install. Before I bought one, I asked about Harmony and wake up over in the Kodi forums and others reported it works fine for them too. (I would not have bought it otherwise as I find CEC to be far too unreliable!).
I use âMicrosoft Media Extenderâ as the device in MyHarmony. As a first step, I did boot the Ugoos into Android, and: Device Settings â Power â Disable Auto Power On (to stop it auto booting when first plugged in, so the power switch actually behaves much like a real power switchâŚ).
A while ago I wrote up my Harmony Remote set up here -
That includes the appropriate codes for wake-up etc. in config.ini that I used with Odroid N2/+ machines - however I did not need to do this on the Ugoos - the only change to the vanilla config.ini I have is hdmi_cec='0' actually.
For CEC and the Harmony, it is just too flaky for everyday use, you never know what is on or off!
With kodi set to suspend or shutdown in power ssaving, it does suspend or power off when asked to via IR and Harmony, has worked reliable. It is the wake or power-on that is not working for me.
Will try the trix from bossanova808. Appreciate your suggestions though! Thanks!
Removed the âsystemd-suspend.serviceâ from â/storage/.config/system.dâ.
Boot the Ugoos AM6B+ into Android and in âDevice Settingsâ > âPowerâ > âDisable Auto Power Onâ.
Expected behavior of not powering on when plugging in verified.
Added the âhdmi_cec=â0ââ to the âHDMI CEC OSD Nameâ section:
# HDMI CEC OSD Name
# Set by CoreELEC Settings
#
cec_osd_name='CoreELEC'
hdmi_cec='0'
For the âmake sure ALL CEC stuff is turned off/disabled in Kodi and CoreElec settingsâ, I went to âSettingsâ > âSystemâ > âInputâ > âPeripheralsâ > âStatus: Disabledâ.
Any other places I missed?
Setup my Harmony with the device âMicrosoft Media Centre Extenderâ, and changed settings for the device to: ârepeats and inter-device delays to 0â.
I did NOT add the âremote-repeat.rulesâ, since his is the Ugoos.
Added the âkeymap.xmlâ file to the â/storage/.kodi/userdata/keymapsâ folder.
Changed âPower Savingâ in KODI to âShutdownâ, not âsuspendâ.
Rebooted, and still does not power on!
Poweroff works from Harmony.
In the MyHarmony software, what command do you have set for the power on - I am not at home right now, but I think it should be âPowerToggleâ from memory.
(Also, what Harmony are you actually using? I use 650s)
Yeah beginning to think you must have a hardware issue - the included remote should also definitely work. If neither will, something is definitely not normal.
I have two more AM6B+ machines to set up in a week or two when I have some time for familyâŚI am not crossing my fingers about those!!
Yeah, but it is only the first part of that (hdmi_cec=â0â) which is used, so should still be OK.
Will see if I can get time to do a âfactory reset/Re-imageâ later this week, and try again.
Thanks for input so far!
Ok this is what I did:
Use the OTA firmware upgrade method:
Download the firmware OTA update package (currently 0.4.1) (full OTA and in zip format) and place it on a USB flash drive (FAT32 and MBR needed). https://ugoos.com/downloads
Insert the USB drive into the AM6B+, hold the recovery button and insert the power-plug. Hold recovery button for 5-10 seconds.
In the recovery menu, choose âupdate from extâ and select the update zip file from the USB drive.
Remember to back up your data before re-flashing, as this process will erase all user data and settings on the device.
After recovery is done, go through checking for updates and reboot cycle until it is on latest version (currently 0.5.4).
Here I verified that the included remote now works for powering both on and off!
It did not work for power-on, only power-off previously!
I also made sure while booted into Android, that Auto Power On is disabled: âDevice Settingsâ > âPowerâ > âDisable Auto Power Onâ.
Now follow installation guide as usual:
But skip the remote.conf, since we will use IR with MCE.
After booted into CoreELEC, enable SSH and run the command âceemmc -xâ.
Reboot without external USB inserted.
Setup Harmony Remote:
In Harmony for the device, I use âMicrosoft Media Extenderâ.
It is setup with changed settings for the device to ârepeats" and âinter-device delaysâ to 0 for both.
Added the âhdmi_cec=â0ââ to the âHDMI CEC OSD Nameâ section:
# mount -o remount,rw /flash
# vi /flash/config.ini
Added the keymap.xml file to /storage/.kodi/userdata/keymaps folder.
For the âmake sure ALL CEC stuff is turned off/disabled in Kodi and CoreElec settingsâ step, in KODI I went to âSettingsâ > âSystemâ > âInputâ > âPeripheralsâ > âStatus: Disabledâ.
Disabled all items to get it to state Disabled.
Rebooted into Android.
In Ugoos Android, I went to âSettingsâ > âDevice Preferencesâ > âDisplayâ > âHDMI CECâ > âCEC Controlâ to Off.
Then restarted back to KODI.
Power-off works, but not Power-on.
Implemented workaround, in Android there is an option to add a secondary IR-code to power-on (Needs to be NEC compliant IR code).
âSettingsâ > âDevice Preferencesâ > âPowerâ > âAdditional IR power-on buttonâ. Here I added power-on from an HDMI-switch I no longer use (Amazon.com).
I then configured Harmony to have 2 different buttons for the âMicrosoft Media Extenderâ Device. One is the current default for Power-off, and then the new code learned from the HDMI-switch remote for the Power-on.
Now both power-off and Power-on works with the Harmony MCE remote! Suspend also work.
Then configured from recommendations, with my own tweaks:
That seems, in all, awfully complicated really, but glad it is now basically working for you.
Did you buy it a long time ago? I bought mine around November 24 and it came with 0.5.4n installed, it seems. Iâve never connected the Ugoos side of things to Wi-Fi or done any updates, basically only that adjustment to the power switch and thatâs it. At all times both MCE and Ugoos have worked to power off/resume the system, so I still think itâs definitely odd that you needed all thisâŚ
Yeah, not sure why all this was needed. Bought it Jan 27th this year from the Ugoos store.
Not sure if it came with 0.5.4n or just 0.5.4, however, it is 0.5.4 now, without the ânâ.
Never used Wifi on it, only wired.