You believe the problem is in the code you posted. You cannot find and fix the problem yourself. Therefore there is a 50% or greater chance that the problem is not in the code you think it's in.
Its unlikely there is a magic wand type command that will fix your code, especially as is often said on here, the problem is probably the code you did not post.
With any project it makes sense to have simple programs that test a particular function or bit of hardware. Its possible you have a hardware issue with the display.
If I had that problem your seeing I load up simple program that keeps writing to and clearing the display only. Leave it run for a while, do you see the same problem ?
This is a valid question, personally I could share the code, but that's not so easy when I have agreed to not publish it. Maybe I can take out part of it, due to 'secret code' is only math, nothing with display function. But then again, not all code available for revision.
Mentioning many problems will not result in a working project, but I can try to write down a few problems.
We don't have enough information.
Is that a I2C OLED display ? Does the project recover from that ? What happens if the LoRa is turned off ? and so on.
I assume that the timing of the display together with the library is no problem. Those OLED displays can handle fast timing.
Possible problems:
Voltage dip or voltage too low. This would be my first guess. Measure the voltage, add a large capacitor.
Memory problem. A stack or array problem can create this. If the bug only influences the OLED library, then the OLED might even recover from such a bug.
1: I use a original Samsung Charger, no extra cap. I can try another charger, or use my bench power supply. I can try to add a cap. Is it possible to add it to pin 3.3 and GND?
2: I did not think about mem problems. In code I don't use the memory (Preferences), but the code of course use mem. Libraries I use is:
Eh? People sell out their country for less. Good ethics, tho.
Those extra characters are not in your code (you do not use card suits, graphics, or most of the accent characters). That is from a comms issue (I2C).
If you connected three boards incorrectly, you will have the same error. Make a drawing of your classified project. Are you posting from work? They have eyes.
[edit] You are working with radio/radar... your I2C lines need to be very short. Maybe your radio/radar equipment is inducting the its noise onto the I2C lines.
Its not super advanced. I reseive weight, temp, humidity and alarm on LoRa. This I present on Grafana. Display not so important, but my wife like to se the data live.
This is a private project, monitoring bee hives. When finished I will monitor 10 pcs.
Since yesterday I i have not worked on this issue, maybe this weekend.