@gachapo Thanks for persevering with this as I got my M5 to day and was getting confused lol. Without this link I would never have got it up and running so thanks for the link as that has kept me from throwing it out of the window.

For anybody else looking at fixing the issue with multiple simultaneous button presses it seems it can't be done. Having dived into the M5Core2 source the events generated for two button presses, e.g. A & C, are press for A and move for A. This looked like a deeper bug (since the second should have been identified as C), so going further in I found that an else branch wasn't refreshing the currently identified touched button on second press (C) in the method "doEvents" in touch.cpp (it doesn't help the code isn't documented, isn't single responsibility and has an arrow antipattern too). Fixing that bug, so the correct button is refreshed, showed that two events together did not produce presses for A & C but instead (I assume - I'm fed up at this point) the hardware averages the presses' coordinates and declares it's button B(!) that is pressed. If you have old Core 1 code you're porting that uses two simultaneous button presses I'd suggest changing the code to double taps of a single button instead which is the workaround I'm about to use - to remain consistent this behaviour is both on Core 1 and Core 2 More formally, I should have read the file header in touch.h earlier: the M5Stack Core2 touch display is only multi-touch in one dimension. What that means is that it can detect two separate touches only if they occur on different vertical positions. This has to do with the way the touch screen is wired, it's not something that can be changed in software. So you will only ever see two points if they do not occur side-by-side. Touches that do happen side-by-side blend into one touch that is detected somewhere between the actual touches.

Hi Calin, thanks for this amazing work. How I can add my own code/Application? Tks in advance for any help you can provide. brgds.

Hello I have exactely the same problem with my M5STack I have resolved this by remove the battery part (Bottom ) Amigapocket

Hi Guys, ihm new with M5Stack. I have a MCore2 and try compile this in visual code with plattform.io. How i must use the code in Plattform.io ? If i compile the code, the device showing black screen. Can anyone help me ?

@ajb2k3 Thank you, very helpful information!

@foxhound Best wish to you !

@felmue that definitely sounds like a massive design issue - I wonder, maybe that's why the M5EPD library doesn't have any touchscreen power-off calls? There was also a post on the M5Stack twitter recently, showing a blurred out image of upcoming devices, with a device eerily similar to the M5Paper taking up a large chunk of the photo: https://twitter.com/M5Stack/status/1357559621389479940/photo/1 I wonder if the design team realised these small issues and made a new board that is more fit for general usage purposes. It happened with the M5Cores (the Basic model had no PSRAM and the first units only had 4MB storage, which later got expanded to 16MB, then the Grey kit came with an MPU, then the Fire kit also included a microphone and PSRAM, among other changes), though the speed is much faster - I think there was almost a year between the Basic and Grey M5Cores, whereas the M5Paper was only recently released. It does feel like a slap in the face for us who already bought multiple M5Paper units though - we've received a device that has a handful of obvious faulty design choices, and now we have to buy the new, updated model to get functionality that should've been working in the first iteration. Don't get me wrong, I'm happy for the updated design, I just hope there will be some discount for those who've already got units on their hands.

For those who have 'battery issue' with their M5Stack; please, use the 'contact now' button on any product page of our Aliexpress store to contact with our after-sale team. We will try our best to bring you a satisfying purchase experience.

@akshaypatil Here are the blocks for uiflow, http://s000.tinyupload.com/index.php?file_id=08084396321658982238 and don't forget to use it together with the one uploaded by @world101 (https://www.dropbox.com/s/xosetw0qzin722l/Blynk.m5b?dl=0) Cheers! :)

@dpharris in the FS root path has already had main.py file you could modify it. when you select the app mode(purple) main.py will be exec. if you are use UIFlow, you need to download the program, not just exec it. then it will auto setting this program for auto-start running. if still not work, pls check the serial log

Thank you Calin!

@m5stack Thank you! The solution 2 (as describe in link) is fully functional.

@watson 在 Ideas, helping M5Stack document stuff... 中说： Please read this doc. I updated it just now. It is better to see once than read 100 times bla-bla-bla

Hello @AndyT hmm, strange, if anything I'd expected the M5Stack Gray to work with low brightness level and the M5Stack Black to not behave due to the fact that the M5Stack Gray has additional hardware (e.g. IMU) consuming power to keep the device powered on. That said, I suspect the IP5306 switching off due to too light load. Try to add the following statement before going into deep sleep. It should prevent the IP5306 from shutting down under light load. M5.Power.setPowerBoostKeepOn(true); Happy Stacking! Felix

@world101 said in How to control lots of Neopixel: @osc, WLED (https://github.com/Aircoookie/WLED) is a really great and easy way to control lots of neopixels. The author has done an awesome job and there are so many features supported now. I used it this past Christmas season to control 800 of the WS2811 string LEDs on the exterior of my home. It runs on the ESP8266 and ESP32, but I haven’t seen anyone using an m5stack product as a controller yet. The most common platform used is the nodeMCU which is based on the ESP8266. I only started trying to port WLED to the m5stack yesterday (I was inspired by this thread), but since I’m new to PlatformIO and I’m a weak programmer, I’m running into build/compile issues. I’ll let you know if I make any progress, but you could also look into the nodeMCU if you want something running quickly. If there was a Micropython lib then i would be interested in testing.

@Pepsi Thanks, I could not find the call to decrease the speed. Not very much, but it helps.