It is true that I do not use an OLED screen on a motorcycle, but when I export videos from the Insta360 application on a tablet with OLED, I turn off the screen using this application:
It is effective, working, configurable and free (although I decided to support the developer by buying PRO).
I don’t consider pixel-shift a solution as is doesn’t prevent burn-in, it just makes the edges of burnt-in areas blurry so that they appear a bit less obvious. As @Hobbyfahrer said, the displays with variable content already do some sort of pixel shifting just by the content changing and these are still burnt in. These burn-ins just appear like dark clouds on the display but the damage is clearly visible.
I just took this picture to complain about the new outlines causing burn-in in this thread, but I thought this is a good illustration why some sort of screensaver is neccessary.
This is my phone display showing nothing but full screen white at max brightness.
I manually turn off the display as often as safely possible but it still burned in like this.
I tested the screensaver mode this afternoon going home.
It works fine, just some things that can enhance the feature.
As I know the route, there’s no problem, but sometimes could be useful to turn on the screen not just when you need to turn or take exits, also when kurviger announces it (for example at 2 km, 1 km, 500 meters as you can select). When there are a lot of lanes, sometimes you need some time to see which one you need to take.
When route is missed (I tried many times), kurviger screen is on (good for me), and when you return to route again, screen turns off again. I was on a parallel route and GPS position is nearly the same, so kurviger assume that you are on route again. Maybe in that situation, screen coud be turned on more time.
Just 2 ideas, not demands. As I use the phone charging, I usually don’t have power problems, but I’ve found this feature very interesting.
This could be done. However users can select the distances of voice guidance.
I started with a simple implementation and see which workflow is more needed.
(also avoiding to load the app with many options)
What timeout have you selected?
When return on route, the screen turns black again after the selected timeout.
I’ve see that respects the selected timeout. I’ve selected 5 seconds. I assumed that this timeout is used after a turn, but maybe is just used when screen is turned on after user touched and returned to route?
Currently the screen saver is available in navigation (Pro) in app version 2.1.2 (beta). It would be helpfull too in follow mode (Free and Pro). Then burn-in at the screen would be reduced when using follow mode for hours.
Then screen saver should be available at application (Free and Pro) instead of navigation (Pro).
In navigation mode same functionality as currently used (copied from Kurviger 2.1.2 (Beta) announcement):
Screen turns on before the turns
Screen turns black after the turns
Screen stays on when being off route
Screen turns on (with timeout) when touching the screen
In follow mode the functionality of screen saver could be:
Screen turns on (with timeout) when touching the screen
I do not know if this is possible. I have set the voice instructions for 2km before the turn. Would it be possible to get the screen displayed from this announcement until the turn?
P.S.have not tested the screen saver yet.