@easytarget Yes, that's exactly what it is. Which is what I disagree with! :)

No other M5 device I'm aware of defaults to turning off. It's a terrible design decision and one that should exclude the Stick from consideration for anything that needs reliable, temporary battery power from the internal battery. You cannot rely on this thing staying on, regardless of how you interact with the "HOLD" pin.

It works fine under any form of external power. The internal battery is useless.

Which is sad because my use case was that when an external power source failed, it would go to the internal battery and software would notice the decline in voltage and alert. If your reboot took 110ms, instead of the normal 90ms (arbitrary, wrong), you are down.

Just my opinion!
M.

I really love the M5 Stack. But then you run across things really hard to understand. Like, I dunno, this:

You must set GPIO4 high within 100ms of the device powering on.
If your code has delays before setting the pin, the device will
shut down.

So if you are powering down with 100% battery, it's BY DESIGN.

Your first two lines in setup() must be:

pinMode(4, OUTPUT);
digitalWrite(4, HIGH);

They are going to protect that battery even if they have to halt your code.

I made a simple audio-to-MIDI trigger using the MIDI Unit. It works surprisingly well!

MIDI-Trigger at Git Hub

This is because UIFlow2.0 sucks with the M5Go. Almost no hardware works. I would abandon all the silly BS and go right to PlatformIO if you want to avoid pulling your hair out.

This ecosystem is so convoluted. I thought I might buy these for presents for kids. No way. Your average parent could not make this shit work ever.

How do you deprecate an API and not have documentation for the new API?

Here's the docs for the button class:

https://docs.m5stack.com/en/arduino/m5unified/touch_class

Where are the docs for the Display class? No one knows.

Where is the comprehensive, definitive documentation for this library? NOWHERE.

It has been 2 years.

I've loaded a small, mono, 16-bit, 44.1kHz audio file into flash in UFlow 2.0. It plays fine within UFlow. No matter what I do, I get an ENOENT error trying to read the file.

Traceback (most recent call last):
File "<stdin>", line 26, in <module>
File "<stdin>", line 18, in loop
OSError: [Errno 2] ENOENT

a snippet of the code from the Python side of things:

def setup():
  global rgb

  M5.begin()
  Widgets.setRotation(1)
  Widgets.fillScreen(0x222222)

  rgb = RGB()
  Speaker.begin()
  Speaker.setVolumePercentage(0.5)


def loop():
  global rgb
  M5.update()
  Speaker.playWavFile('/flash/res/audio/test1.wav')
  if Speaker.isPlaying():
    rgb.fill_color(0xffffff)
  time.sleep(2)

No code I've downloaded from other people works either! I can play tones out of the speaker, I can read images out of flash. I cannot read audio files out of flash.