axp192 VS u8g2

There is also a platform agnostic I2C driver for AXP192. For most sensors etc drivers only thing that changes between platforms are the io functions. I have been using this with M5Stack Core2 for a while. It is a bit annoying board to initialize. Especially because you need to initialize the AXP192 first before you can initialize the display.

Try the https://github.com/olikraus/u8g2/wiki library.

If you want to stick with the u8g2 library, be sure to check out the u8g2 wiki for some more information. There's a lot of info on the setup page and I find the u8g2 reference especially useful in practice.

Check out the U8G2 library if you're going to work with OLED displays. It's really the best one out there and it does it all, supporting multiple OLED displays with the one library. It also has excellent support for numerous fonts in different sizes.

I have been considering two different methods for achieving this. The first method is the one that Olikraus uses with the u8x8 library, which implements a callback system that handles the hardware abstraction layer. The second method that I have been contemplating is using i2cdev, which allows for sharing the i2c port with other threads.

I use the u8x8 library (https://github.com/olikraus/u8g2/wiki/u8x8reference) for the display. I like this library a lot!

Use u8g2, awesome library, very flexible, works with everything.

Try U8G2. It works with both these OLEDs and many more.

For displays like this, I strongly recommend the U8G2 (https://github.com/olikraus/u8g2) library. It has support for pretty much everything. However, you might need to find/write/tweak your own "hal" later, which is just a couple of simple callback functions that bridge it to the I2C or SPI ports of your MCU.