Update: 8-26-18 (I was typing this and hit back on my mouse..... Lost a bunch of updating stuff.... So if this is blunt, that is why)
My experience with AutoRCM was going great until I as well started having battery drain issues after turning my switch off from Horizon. This started after I put my switch into the dock and after that, my switch would just reboot into RCM mode after being powered down. To my surprise, after powering off my switch, plugging in the SX Pro Dongle would stop the switch from booting up or rebooting back into RCM mode. Which puzzled me. So as of now, my switch just stays in sleep mode
Info:
My experience with AutoRCM was going great until I as well started having battery drain issues after turning my switch off from Horizon. This started after I put my switch into the dock and after that, my switch would just reboot into RCM mode after being powered down. To my surprise, after powering off my switch, plugging in the SX Pro Dongle would stop the switch from booting up or rebooting back into RCM mode. Which puzzled me. So as of now, my switch just stays in sleep mode
Info:
- To fully turn off your, you will need to power off via Horizon, and boot the CFW you use and hit "Power Off" in that menu. This will fully power the switch off as I have been told.
- I have also seen that holding the power button for 8 seconds or more while in horizon will trigger a force power-off (I have not tested this)
- You can charge your switch with AutoRCM installed. This requires you to charge it with the power brick that powers the dock. I have had to this already and I can say that it does work.
- Since AutoRCM corrupts the BCT (*BCT is the boot configuration table), which results in the switch not being able to charge normally while in RCM mode.
- Switch does not charge normally with AutoRCM, a.k.a corrupt BCT.
- Either it charges very slowly or sometimes with a broken slow/fast/slow/fast charge pattern:
- Or this behavior is current taken from the USB controller or the BPMP (Nvidia's Boot and Power management processor)
- In AutoRCM, the Charge IC probably can't update the battery calibration file and could make the percent fake.
- I have not experienced Battery De-Sync Issued with AutoRCM. This seems to be a misconception that scares people away from installing AutoRCM. Afaik, AutoRCM do not cause De-Syncs.
I think its time to put this to bed once and for all...
In Hekate...
Selecting power-off from Hekate menu turns switch completely off. Just like the PMIC is switched off. (I think it actually is from its I2C lines.)
- Power off from Horizon will take you to RCM after 12 seconds. To get round this, you need your payload injector ready to send.
This has been done to death now.
- Once selecting power-off and you are in RCM after 12 seconds, the next Hekate payload push will look like it is booting (if you have autoboot enabled), but the screen will flash white and console will be off.
- If you don`t have autoboot enabled, it will kick you to the Hekate menu if you have your payload injector plugged in. If you have nothing plugged in and no internal SAMD chip, you will stay in RCM until your battery dies.
- Same applies to SXOS. You need SX pro plugged in until shutdown is complete (after this 12 second delay)
The only way to get round this, is to
- Disable autoRCM or
- Hold power for at least 8 seconds in Horizon or RCM to force power-off
- Fit internal SAMD - (I know of a thread that deals with such issues )
So, Switch charges and does not charges in RCM. xD
The results (battery was 89%):
The switch can charge normally the battery, if the BCT is intact!
In RCM AND in hekate menu.
*BCT is the boot configuration table that autoRCM corrupts.
Tests showed that it was charging with the same current, as in Horison OS.
The current it was drawing with 89% battery, was 800mA - 1000mA, using Switch wall adapter. On PC, it was the max the hub could give.
------------------------------------
The switch cannot charge normally with a corrupt BCT (AutoRCM).
In hekate, it shows similar behavior (read below).
Extra emphasis on the "normally".
With autoRCM, basically a corrupt BCT, the switch behaves differently.
There are 2 behaviors that I saw when connecting to the switch wall charger:
- Common - It was draining 140-250mA.
- Common (in hekate) - 200mA - 400mA
- Rare (normally if you connect charger after powering off from HOS) - Drain of alternating 250mA and 1000mA, with surges of 2.5A.
------------------------------------
Summary - facts:
I don't know for behavior .3 what really happens and what Switch does. This can be easily examined, by connecting a current multimeter between battery and switch and check the readings.
- Switch can charge completely normally in RCM or Hekate with a BCT intact
- The percent % in Horizon OS, after a RCM charge, is not fake.
- Switch does not charge normally with AutoRCM, a.k.a corrupt BCT.
- Either it charges very slowly or sometimes with a broken slow/fast/slow/fast charge pattern:
- Or this behavior is current taken from the USB controller or the BPMP (Nvidia's Boot and Power management processor)
- In AutoRCM, the Charge IC probably can't update the battery calibration file and could make the percent fake.
Last edited by Lumince,