Hey, good catch! I'm pretty sure I know exactly when this behavior started -- anduril2 branch r594. I'm not entirely sure if it should be categorized as a bug or not though.
If I enable the manual memory timer (a.k.a. hybrid memory), this is what I see:
- Ramp to the desired brightness.
- Turn the light off.
- Go to beacon mode.
- Turn light off, then wait more than than N minutes, where N is the duration of the manual memory timer.
- Go to beacon mode again.
Result: Beacon mode uses the last-ramped level the first time, and the manual memory level the second time.
The question is... if the memory timer is set to zero (i.e. reset brightness to manually-saved level immediately after turning light off), what is the correct behavior? Is returning memory to the manual level immediately correct, or a bug?
For anyone else who runs into this, it may help to give the timer a non-zero value so it will remember the ramp level long enough to reach beacon mode.
Hey, good catch! I'm pretty sure I know exactly when this behavior started -- anduril2 branch r594. I'm not entirely sure if it should be categorized as a bug or not though.
https:/ /bazaar. launchpad. net/~toykeeper/ flashlight- firmware/ anduril2/ revision/ 594
If I enable the manual memory timer (a.k.a. hybrid memory), this is what I see:
- Ramp to the desired brightness.
- Turn the light off.
- Go to beacon mode.
- Turn light off, then wait more than than N minutes, where N is the duration of the manual memory timer.
- Go to beacon mode again.
Result: Beacon mode uses the last-ramped level the first time, and the manual memory level the second time.
The question is... if the memory timer is set to zero (i.e. reset brightness to manually-saved level immediately after turning light off), what is the correct behavior? Is returning memory to the manual level immediately correct, or a bug?
For anyone else who runs into this, it may help to give the timer a non-zero value so it will remember the ramp level long enough to reach beacon mode.