Last edited by ChanseyIsTheBest,
Still no proof it was CTCaer that asked for it. Also why remove the whole repo and not just fix the issue? Sounds like nuclear option is a bit extreme.A new charging mode was added to OC-Suite to charge at a default of 3000mAh based on the L4T default of 3000mAh. (In actuality the L4T default is not 3000mAh and charging at that level is unsafe). One of the people associated with L4T got upset about it because of the misinformation and the damage potential. This person also did not also like the unsafe OC in Switch-OC Suite because of its hardware damage potential and requested for the project to be taken down (the charging thing being the power keg moment) going by was written in the readme file being the only thing left in the repo.
If you go on the front page of the GitHub it now says this
View attachment 357689
I have same feeling about this, but this is not the way, because all the users are harmedYeah there's no definitive proof. I have a feeling the whole repo was requested to be removed because that person also did not like fools blindly copying and changing stuff in the repo, getting rid of warnings and making it unsafe and malfunctional. If the repo goes away no one will have the skill to update it therefore cutting off those people.
Why no sleep mode?That sucks, it should be your own decision to risk your own hardware.
Especially in the OC Suite you could adjust everything so it fits your own needs.
Seems i'm stuck with Atmosphere 1.4.1 without sleep mode.
My sysnand is already on HOS 16 and my emunand on HOS 15.Why no sleep mode?
I have the exact same setup, my sleep mode works fine on emummc.My sysnand is already on HOS 16 and my emunand on HOS 15.
Sleep mode no longer works on emunand, because of the fuse mismatch.
The switch will not wake up again and i have to hold the power button 10 seconds to reset the switch if i accidentally put it to sleep.
I thought it's not a problem i'll wait a few weeks until OC Suit it updatet and the new Online kip configurator is online, but yeay.
The right loader kip is more important to me than the sleep mode, so I'll stay on 15.
when i boot emummc via hekate:I have the exact same setup, my sleep mode works fine on emummc.
What is the error you receive?
Thanks, good to know. I read about it on rentry, but was not sure if it messes my clean stock nand.I ran the wormboot fix when I updated my emummc to 15.0 like 2 weeks ago and it fixed this issue.
It does not mess anything on sysnand, its essentially one click in Hekate and then reboot.Thanks, good to know. I read about it on rentry, but was not sure if it messes my clean stock nand.
WRONG
Yea i mean if it was really about some bricked switches he will write about it i guess and if it was something in a new firmware that is causing some issues he will also write about it and hold the new version not deleting the whole project...Maybe it was the drop that filled the glass fo Kazu, I hate this things, why one dev say other what to do? Everyone can do what he/she want, like we do as user, no one can say me what to do, can warning me about danger, but if I want to do anyway, is my responsability, I don't understand why a few think they have the right to do things like that
https://gbatemp.net/threads/switch-oc-suite.625066/post-10093858 this is not form dev?No one asked for it to be cancelled. If you have proof that someone did, then post it.