You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Akitaishi (@ironmanfpv) who did Question-Visualizer-for-Monocle suggested in the chat that Noa could put the Monocle to sleep when not in use.
This would allow to save a lot of battery, and remove the need to put the Monocle back in the charging case between use.
One way this could be implemented is keep the Monocle sleeping all of the time, when woken up by a touch, immediately take a capture, transfer it, then immediately go back to sleep.
This means Noa would need to constantly scan for the Monocle presence, but this uses battery on the phone (larger battery) rather than the Monocle (small battery).
Quoting Akitaishi on advantages this could have:
a preset x seconds wait before the monocle goes to sleep when working with NOA
an option in NOA which allow user to set the x seconds (wait before hibernate,) because that everyone’s sweet spot is different.
a touch sequence or hold touch sequence which will be prompt Monocle ; one that is understood by device to be a “hibernate” call.
a voice command : Eg “Monocle sleep” , when translated or picked up, will put Monocle to sleep.
another way is a “user customisable voice command”, to call the device to go to sleep. Isn’t that fun ?! I could think of so many ways to do it. It’s a much needed feature for the 1 hour limit monocle batt time.
I personally would love No. 5) as it’s elegant and customisable.
Would that make sense? It sounded reasonable to implement as long as connecting back to the Monocle can be done reasonably fast. Worth trying?
Thanks to everyone!
The text was updated successfully, but these errors were encountered:
Akitaishi (@ironmanfpv) who did Question-Visualizer-for-Monocle suggested in the chat that Noa could put the Monocle to sleep when not in use.
This would allow to save a lot of battery, and remove the need to put the Monocle back in the charging case between use.
One way this could be implemented is keep the Monocle sleeping all of the time, when woken up by a touch, immediately take a capture, transfer it, then immediately go back to sleep.
This means Noa would need to constantly scan for the Monocle presence, but this uses battery on the phone (larger battery) rather than the Monocle (small battery).
Quoting Akitaishi on advantages this could have:
Would that make sense? It sounded reasonable to implement as long as connecting back to the Monocle can be done reasonably fast. Worth trying?
Thanks to everyone!
The text was updated successfully, but these errors were encountered: