Guo-Rong

Are you able to confirm GPS is functioning as expected? It is very possible that tweaks may be needed to ensure `furble` is using the correct UART port and/or pins.

> PWR button hack does not work on the M5Tough or the Core2 to lockout the touchscreen This is a Core2 and not a Core2 v1.1? Unfortunately I only have...

> In Gold inside its written as **M5 Core II** OK, thank you. It's quite messy with the way the M5Unified library handles these devices. There's 2 Core2 devices, v1.0...

What I will do is to merge the existing changes and issue a new release with the known working feature set. This allows us to baseline the functionality whilst we...

I have just tagged v3.3.0 so we have a release with basic M5Tough working: https://github.com/gkoh/furble/releases/tag/v3.3.0 > The current you expect, is that on the 5V USB supply or actual load...

There's some commentary in the M5Unified code for configuring the PMIC on Core2: ``` Axp192.setChargeCurrent(390); // Core2 battery = 390mAh ``` and ``` void AXP192_Class::setChargeCurrent(std::uint16_t max_mA) { max_mA /= 10;...

Apologies for spam commenting. I noticed furble's M5 libraries are quite outdated, so I've updated and spun a test release: https://github.com/gkoh/furble/releases/tag/v3.3.1-rc0 Nothing in the changes suggests it will fix the...

@Grumpytech4 Wow, thank you for expending the effort in obtaining actual traces. These are roughly inline with the values I obtained from the PMIC itself, which is great. > Some...

Just revisiting this. >> Biggest savings could be made by putting the GPS into idle for a period and not continuously polling for a camera on auto > reconnect. >...

Interesting. This appears to occur only if the GPS unit is attached and enabled. If I just switch off GPS, I cannot reproduce. Still investigating.