Originally created by @adayush on GitHub (May 4, 2021).
My Mac (Air M1) doesn't charge without AlDente. I removed the app by setting the limit to 100% and then moved it to trash. It doesn't even charge now. Please help
Originally created by @adayush on GitHub (May 4, 2021).
My Mac (Air M1) doesn't charge without AlDente. I removed the app by setting the limit to 100% and then moved it to trash. It doesn't even charge now. Please help
I'm experiencing this issue, on an Intel Mac. Please help? I removed the app after uninstalling the helper, set "Optimize battery charging" back on, and moved it to trash.
@ThatXliner commented on GitHub (Jul 12, 2021):
I'm experiencing this issue, on an Intel Mac. Please help? I removed the app after uninstalling the helper, set "Optimize battery charging" back on, and moved it to trash.
Sorry about this, this was probably caused by something else. Using another port for charging worked perfectly. It probably just got dirty.
@ThatXliner commented on GitHub (Jul 13, 2021):
Sorry about this, this was probably caused by something else. Using another port for charging worked perfectly. It probably just got dirty.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @adayush on GitHub (May 4, 2021).
My Mac (Air M1) doesn't charge without AlDente. I removed the app by setting the limit to 100% and then moved it to trash. It doesn't even charge now. Please help
@adayush commented on GitHub (May 4, 2021):
Nvm, after system update everything works nicely. Though the reboot didn't work when I tried it.
@ThatXliner commented on GitHub (Jul 12, 2021):
I'm experiencing this issue, on an Intel Mac. Please help? I removed the app after uninstalling the helper, set "Optimize battery charging" back on, and moved it to trash.
@MatthiasKerbl commented on GitHub (Jul 13, 2021):
Hi @ThatXliner,
did you try an SMC reset? https://support.apple.com/en-us/HT201295
@ThatXliner commented on GitHub (Jul 13, 2021):
Sorry about this, this was probably caused by something else. Using another port for charging worked perfectly. It probably just got dirty.