AppHouseKitchen / AppHouseKitchen/AlDente-Battery_Care_and_Monitoring
macOS 27 Developer Beta
- Linguagem predominante
- Swift
- Estrelas
- 9.2k
- Forks
- 332
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Descrição
**MacBook (please complete the following information):**
- MacBook Model (https://support.apple.com/en-us/HT201608): MacBook Air 13 inch, M3, 2024 (A3113)
- macOS Version (https://support.apple.com/en-us/HT201260): macOS 27 Golden Gate Developer Beta Version 26A5353q
- Charger Model (Apple, Third Party, Wattage,...): Apple 70W USB-C Power Adapter
- Charging Cable (MagSafe 2, MagSafe 3, USB-C, Apple, Third Party,...): Apple MagSafe-3
- AlDente Pro or AlDente Free: AlDente Pro
- AlDente Version: 1.37.3
- List or add screenshots of all enabled/disabled settings in AlDente:
- Charge Limit: 78%
- Automatic Discharge: On
- Sailing Mode: 6%
- Heat Protection: 34C
- Calibration Mode: Not in calibration
- Prevent Overcharging During Sleep: Disable Sleep until Charge Limit
- Low Power Mode: Only On Battery
- Background Dashboard Updates: Off
- Apps Using Significant Energy: Medium Usage
- Hardware Battery Percentage: On
- Magsafe LED: Off During Sleep, Indicate Charge Limit, Blink Orange during Discharge
- Please share a debug file the next time this happens so that we can assess this issue better. You can find a guide on How to generate and share a debug file on our blog(https://apphousekitchen.com/how-to-generate-and-share-a-debug-file/).
- External Monitor connected? No
- MacBook used in Clamshell Mode (with the lid closed)? No
**Describe the bug**
A clear and concise description of what the bug is.
The moment I updated my MacBook to macOS 27 DB I noted that it keeps switching between Low Power Mode and normal mode. I opened AlDente popover, and figured out the problem: the Charging Limit is malfunctioning, but the Automatic Discharge is still functional, leading to the problem that the machine charges over 78% (my set charge limit), and fall into discharging mode (as I turned on Automatic Discharge).
**To Reproduce**
Steps to reproduce the behavior:
1. Charge the battery near Charge Limit;
2. When the Charge Limit is reached and Automatic Discharge is On, the error emerges.
**Expected Behavior**
A clear and concise description of what you expected to happen.
The Charging Limit function is holding the charge instead of letting it pass 78% and triggers the Automatic Discharge function.
**Screenshots and Screen Recordings**
If applicable, add screenshots or screen recordings of the issue to help explain your problem.
The screenshots illustrates the bug loop. (As my battery is currently at 94%, I'll take 94% as an example)
**Additional context**
Add any other context about the problem here.
Guia de contribuição
Nenhum guia de contribuição indexado para este repositório
Avaliação
Esta issue ainda não foi avaliada.