So, I have been using Atmosphere 0.12 running through Hekate w/ Sigpatches on EmuNAND and I have been measuring the boot times through different payloads. The difference in boot times is quite relevant:
Edit: for reference, stock switch (Horizon OS) takes around 10-11 seconds to start.
I am using the following hekate_ipl.ini file
Do I have something incorrectly configured in my setup or can I do something to increase the boot times when using fusee primary as payload?
Any help will be appreciated.
- Payload: Hekate 5.2.1 auto launching CFW emuNAND through fss0= Time to boot: 18.34 seconds
- Payload: Hekate 5.2.1 launching CFW emuNAND through fusee-primary Time to boot: 31.77 seconds
- Payload: fusee-primary auto launching CFW emuNAND Time to boot: 33.47 seconds
Edit: for reference, stock switch (Horizon OS) takes around 10-11 seconds to start.
I am using the following hekate_ipl.ini file
Code:
[config]
autoboot=0
autoboot_list=0
bootwait=0
verification=1
backlight=100
autohosoff=0
autonogc=1
updater2p=1
{------- Launch -------}
[Atmosphere]
payload=bootloader/payloads/fusee-primary.bin
icon=bootloader/res/icon_atmosphere.bmp
[Horizon]
fss0=atmosphere/fusee-secondary.bin
stock=1
icon=bootloader/res/icon_horizon.bmp
[CFW - sysMMC]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp
[CFW - emuMMC]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp
Do I have something incorrectly configured in my setup or can I do something to increase the boot times when using fusee primary as payload?
Any help will be appreciated.
Last edited by Bullseye,