Each system seems to have it's own algorithm. Three examples from my last short ride:
Garmin 93 W; RunwithGPS 96 W; Strava 78 W; BLEvo 80 W
So this values are only for a kind of orientation, not for an exact measure.
As i said before, it is not a big problem for me. But it would be interesting, if @PaoloBLEvo finds a solution. And i mean, that i have not seen this behavior with older versions of BLEvo.
I have a 2018 Levo with the green leds at the battery. So the mode change is only visible via BLevo.
But it is not such a problem. BLevo is the best app for my LEvo.
I use the original remote. It must be a difference, if i use Smart Power, because BLevo must interact with the TCU. Smart Power modi are not stored permanently, only in BLevo. Without BLevo i have only the stored modi, but without delay after button press.
On my last longer rides (80-90 km) i made the same observation (but with Smart Power). And i feel that the longer the ride the more often there is the delay between button-press and level change.
@PaoloBLEvo It is not so an important issue. I only was a little bit confused about the different amount of data saved by BLEvo and Garmin. BLEvo works fine and on my Turbo Levo i only use it. The Garmin is now on my Bosch CX bike.
I think, it is not necessary to save data every second. 1 Mb for a 8 km ride will be 10 Mb for 80 km. And an upload with Mobile Data rate will reduce my mobile credit to fast. The best solution would be to choose the data rate in BLevo.
The tcx-files from BLevo are 5-6 times bigger then the one of my Garmin Edge. (See the pictures). The first is from my Garmin, the second from BLevo. Both show the speed-diagramm of the same track. It seems, that BLevo measures speed and other datas much more often than my Edge. If so, it would...
I have found a good workaround for me. My settings for long press on the buttons are: 1) down button - screen goes off after timeout ( 60 sec ); 2) up button - enable screen on level change.
So a long push on the down button and the screen goes off after 60 sec. If i want to switch the screen...
Testride was ok. It works as decribed by @PaoloBLEvo .But eventually the function to turn off and on the screen with a button push on the remote can be implemented?
Hello, i have a problem with the "action to turn off / on screen". A long push on the middle button will turn on the screen forever (screen message). But with which action i can turn off the screen? Or will this only be realized with the button of my phone?