You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to the ESP32S3 causing the USB detection (and other pins) to become "HIGH" on boot for ~500ms, the test to see if the unit is plugged in will always say "1" (True, "HIGH"). Upon deep sleep, the test if the USB was plugged in will ask for the USB detection pin to be "LOW" as a Wake from Deep Sleep signal. When the ESP32S3 enters Deep Sleep, the USB detection pin will be "LOW" and the ESP32S3 will wake up again and repeat this process all over again.
Comment this line out (102 in Watchy.cpp) or expect a ~5 hour battery life:
esp_sleep_enable_ext0_wakeup((gpio_num_t)USB_DET_PIN, USB_PLUGGED_IN ? LOW : HIGH); //// enable deep sleep wake on USB plug in/out
This was a thought I had to check the battery charge indicator, but found out that this caused repeated wake ups non-stop, once I was able to physically test it. This sense line is unusable until after ~500ms from wake up, making it impractical.
The text was updated successfully, but these errors were encountered:
Due to the ESP32S3 causing the USB detection (and other pins) to become "HIGH" on boot for ~500ms, the test to see if the unit is plugged in will always say "1" (True, "HIGH"). Upon deep sleep, the test if the USB was plugged in will ask for the USB detection pin to be "LOW" as a Wake from Deep Sleep signal. When the ESP32S3 enters Deep Sleep, the USB detection pin will be "LOW" and the ESP32S3 will wake up again and repeat this process all over again.
Comment this line out (102 in Watchy.cpp) or expect a ~5 hour battery life:
Watchy/src/Watchy.cpp
Line 102 in 9f3accd
This was a thought I had to check the battery charge indicator, but found out that this caused repeated wake ups non-stop, once I was able to physically test it. This sense line is unusable until after ~500ms from wake up, making it impractical.
The text was updated successfully, but these errors were encountered: