-
Notifications
You must be signed in to change notification settings - Fork 297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sleep timer #157
Comments
Thinking about it, i feel like this should be the default anyway: I often find myself having the idle-timeout active by mistake. So i'll have the idle-timeout automatically disable itself if there are no objections |
It could just disable itself after it reaches the timeout. That would be a sleep timer already. Then the checkbox would be "Always Timeout" and greyed out,that would maintain current behaviour |
Looks good to me, it should at least disable itself automatically once it reaches the timeout. |
Any news on this one? I tried to play in the code but hmmm. Haven't touched programming since almost 10 years, let alone Android programming. I do somewhat understand how it works, but can't reset the idle_timeout preference. |
No, sorry: i did not have time to work on this.
The code should get an instance of the SharedPreferencesEditor after the idle timeout was hit, eg:
|
Yes, please add a real sleep timer. The timeout option is too limited. Other players have option like
Please improve the sleep timer. |
Yes, please add a a real sleep timer, with (some of) the options mentioned above. :-) |
Is this a planned feature still? |
Any plans on adding a simple sleep timer in Vanilla Music (Menu > Sleep timer)?
I know it can be achieved with the "Idle Timeout" option in Settings > Miscellaneous.
However, once activated, the "Idle Timeout" stays active forever, unless unchecked. I think that adding an option that would deactivate the "Idle Timeout" once done would make sense. The checkbox could be name something like "Disable once done" and grayed out unless "Idle Timeout" is checked.
Thanks :)
The text was updated successfully, but these errors were encountered: