This features seems a little buggy if used with autoboot. Am I wrong? I set Auto HOS Power Off as enabled and Autoboot of Atmosphere enabled with 0s boot delay.That is the Auto HOS Power Off feature you are experiencing. When a console with AutoRCM enabled enters RCM from Horizon, such as when turning the console off or rebooting it, sending the Hekate payload with this feature causes the console to shut down (and you will see the Hekate logo as well). More explanation and instructions can be found on the Hekate GitHub page.
That's expected. Shutting down the console from Horizon with AutoRCM enabled causes it to reboot into RCM and with Autoboot, the console will automatically boot the CFW when the payload is sent.This features seems a little buggy if used with autoboot. Am I wrong? I set Auto HOS Power Off as enabled and Autoboot of Atmosphere enabled with 0s boot delay.
When I turn off the console from Atmosphere it correctly goes in RCM, but when I inject Hekate payload again, it just launches Atmosphere again.
Inviato dal mio Nexus 5X utilizzando Tapatalk
So the two features can't be used together in any way? I'm sad [emoji3525]That's expected. Shutting down the console from Horizon with AutoRCM enabled causes it to reboot into RCM and with Autoboot, the console will automatically boot the CFW when the payload is sent.
I believe Hekate will default to Auto HOS Power Off before Autoboot since Auto HOS Power Off is designed to turn off the console when you enter RCM from Horizon not a powered off state. Autoboot doesn't care how you entered RCM, just that the Switch is currently in RCM and a payload was pushed.So the two features can't be used together in any way? I'm sad [emoji3525]
Inviato dal mio Nexus 5X utilizzando Tapatalk
I believe Hekate will default to Auto HOS Power Off before Autoboot since Auto HOS Power Off is designed to turn off the console when you enter RCM from Horizon not a powered off state. Autoboot doesn't care how you entered RCM, just that the Switch is currently in RCM and a payload was pushed.
I believe Hekate will default to Auto HOS Power Off before Autoboot since Auto HOS Power Off is designed to turn off the console when you enter RCM from Horizon not a powered off state. Autoboot doesn't care how you entered RCM, just that the Switch is currently in RCM and a payload was pushed.
Auto HOS off is useful for people who have Auto RCM enabled. In fact, when you turn off your console from Horizon (Ninendo Switch OS) using the power off menu, the console automatically reboots to RCM. So, thanks to Auto HOS off, if you re-inject Hekate's payload, it will truly turn your console off.Can I disable auto HOS? What it does?
Auto HOS off is useful for people who have Auto RCM enabled. In fact, when you turn off your console from Horizon (Ninendo Switch OS) using the power off menu, the console automatically reboots to RCM. So, thanks to Auto HOS off, if you re-inject Hekate's payload, it will truly turn your console off.
Inviato dal mio Nexus 5X utilizzando Tapatalk
You are telling that I had to inject payload twice because the first time (after i turned off my switch) hekate turned my switch off for real?