DanGeiger

The accelerometer is a BMA423. You can download the specs from the internet. It is a pretty standard accelerometer with some special features like step detection and detection of single and double taps. The response is nice too. I am not sure what you mean by "how much more features would it have and what would I lose?" If you look at the framework, you can get rid of anything you don't want and add any features that you program in.

It is the symbol key and the "i" key. You can check the mapping of all the keys in the SmartResponseSE.cpp file. It shows the normal, shifted, and symbol key map there.

The Power button only turns the unit on. Use the command "Bye" to shut down.I also started to have issues compiling the code. I think it is something to do with the board definition file.

They are 1 inch long nd about 1mm in diameter.

Thanks so much. And thanks for all of your work. Developers like you just make people want to make.

The most probable is that you don't have all the files in the same directory. Make sure you put all of them in one directory and then open the main file and the others should load as tabs.If that doesn't work, load the main one in the Arduino IDE, click on the drop down box in the upper right of the IDE and select "Add Tab". Then copy and paste one of the files into it. Repeat that for the others.

If I understand you right, you can get rid of the loopy. The code I have is the complete code, so if you just paste it into a new program, you will have my setup() and loop() and your setup() and loop() that you start with when you select NEW in the menu. Since I provide the setup and loop routines, delete the other ones. Setup() is run once and loop() repeats forever. If nothing is calling your loopy() routine, it is not executing at all.

The temperature is a value that is returned from the getTemp() routine. To get the temperature to display under my temperature scale, I had to use the temperature value - 20. This is the x-axis value of the small oval that will be printed under the temperature scale. If your run the program and your rectangle is far off to the right or left, add or subtract a value to the -20 in the term int(temp) - 20 to get it under the temperature scale. This is going to vary from watch to watch so I don't know what it is for yours. I would suggest changing the value and see it's effect on the display.

The sleep function is a hardware function of the switch and set from the factory. Some in the comments have posted code to better control the power to the watch.

The keyboard code I wrote is really bad. I just through something together to allow people to set the time. I would download the code with the internet time routine. It sets the time from the internet.

A long press on the button (6 sec) puts it to sleep and a 2 second press wakes it up.

There were a couple of problems with the original software and people in the comments have offered code to fix them. The time set function was one of them.I never figured out why the power sometimes reads right and not.For the temperature, the code prints a small icon under the color block. If you look in the code, there is a comment that you need to set one of the variables based on the temperature reading of your specific watch.

Hold the button for 6 seconds and the watch will go to sleep. There is a discussion of how to sleep the watch in the writeup and others have developed code to automatically sleep after a time period. Thanks for the comment.

Ecellent. That would be the thing I would have looked for.

Thanks so much!

Very Nice. This is what you hope for when you post on Instructables. Someone to go and write the code you really wanted. Well done.

Are all of the files in the same directory and do they all show up as tabs in the Arduino IDE when you open the main file? This is the only reason I can see that the main program wouldn't see the other files.

That's a great reminder. Anytime you program the ESP32 in Arduino, there is a substantial library that needs to compile. My initial compile isn't as bad as yours, but it is at least 3 minutes.

Creative Commons. It is the small banner at the top of the Instructable page next to the published date. If you click on that, it gives you a description. Thanks for expanding on this.

Great catch on the menu touch issue. Micropython would be nice except the first person has to figure out all of the drivers and pins from the documentation. Pretty big task, but I bet someone will take it on.

The power management is pretty complicated. The easiest way would be to call the power shutdown routine after your timeout and then use the button hold for 2 seconds to wake it up.If you wanted full control, you would want to look at the shutdown() routine in the axp20x.cpp file. You can call this to have the watch shutdown as if you held the button for 6 seconds. If you want to wake it with a screen tap, you would have to look at a lot of the libraries and even a bunch of the datasheets to figure out the pin connections and functions since LilyGo didn't release the schematic. You would want to keep the touch screen running during shutdown and set it to generate an interrupt when touched. The esp32 would then need to set the interrupt pin to wake the chip on the interrupt. You would then …

The power management is pretty complicated. The easiest way would be to call the power shutdown routine after your timeout and then use the button hold for 2 seconds to wake it up.If you wanted full control, you would want to look at the shutdown() routine in the axp20x.cpp file. You can call this to have the watch shutdown as if you held the button for 6 seconds. If you want to wake it with a screen tap, you would have to look at a lot of the libraries and even a bunch of the datasheets to figure out the pin connections and functions since LilyGo didn't release the schematic. You would want to keep the touch screen running during shutdown and set it to generate an interrupt when touched. The esp32 would then need to set the interrupt pin to wake the chip on the interrupt. You would then need to power up the rest of the watch.I find it easier to just hold the button for 2 seconds when I want to do something on the watch.

I have 11 apps right now and they all work as they should. I would check:1) Do you have the correct number set in the maxApp variable in the menu routine?2) Do you have the appName variable updated with the name of each app?3) In the case statement, is there a case value for each app (ex. your app #9 should correspond to the #9 app in your appName variable and should call that particular routine.)4) Do you do any processing in your case statement besides call the associated function? If you do, you may have brackets (like for a for loop or if statement) that are causing the compiler to think that it is at the end of the switch function and it ignores the rest of the cases. 5) Did you do what I often do; copy the previous case statement to save time and then not change the value of the cas…

I have 11 apps right now and they all work as they should. I would check:1) Do you have the correct number set in the maxApp variable in the menu routine?2) Do you have the appName variable updated with the name of each app?3) In the case statement, is there a case value for each app (ex. your app #9 should correspond to the #9 app in your appName variable and should call that particular routine.)4) Do you do any processing in your case statement besides call the associated function? If you do, you may have brackets (like for a for loop or if statement) that are causing the compiler to think that it is at the end of the switch function and it ignores the rest of the cases. 5) Did you do what I often do; copy the previous case statement to save time and then not change the value of the case?Take a look at these possibilities.

Thanks for the feedback. One of the problems with using esp32 is the extensive libraries it has to include and compile. Even a bare bones program would still take a long time to compile if you have the esp32 and the Twatch object. You should post that link in your own Instructable so you can continue to add to it as you find useful tools.

I just added a line to my write up. It looks like calling the shutdown() function from the axp202 library does the same thing as a long press. So that would be the way to go.Thanks for loading up and sharing the picture of the working watch. There is always a chance it works for me but everyone will have difficulty with getting it to work so it is good to see you got it going on your watch. Thanks.