Can't change "Silence alarm after" in clock settings #646

Closed
duxovni opened this Issue Jun 26, 2017 · 4 comments

Comments

Projects
None yet
3 participants
@duxovni

duxovni commented Jun 26, 2017

When I go into the settings of the built-in clock app on CopperheadOS, and change "Silence alarm after" to "Never", the setting goes back to the default "10 minutes" after closing and reopening the app.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Jun 26, 2017

Contributor

This is an upstream AOSP issue, not a CopperheadOS issue.

Contributor

thestinger commented Jun 26, 2017

This is an upstream AOSP issue, not a CopperheadOS issue.

@regagain

This comment has been minimized.

Show comment Hide comment
@regagain

regagain Jun 26, 2017

I reported this issue on the Android issue tracker some time ago: https://issuetracker.google.com/issues/37138380 (note: sadly, it seems a google account is required to view this page).

I reported this issue on the Android issue tracker some time ago: https://issuetracker.google.com/issues/37138380 (note: sadly, it seems a google account is required to view this page).

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Jun 26, 2017

Contributor

If someone provides a clean patch, I'll apply it.

Contributor

thestinger commented Jun 26, 2017

If someone provides a clean patch, I'll apply it.

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Jul 20, 2017

Contributor

Since it's an upstream issue not caused by or uncovered by a CopperheadOS feature, I'm going to close this issue. It doesn't make sense for us to have an issue filed for every upstream bug. As I said, I'll accept a patch fixing the problem.

Contributor

thestinger commented Jul 20, 2017

Since it's an upstream issue not caused by or uncovered by a CopperheadOS feature, I'm going to close this issue. It doesn't make sense for us to have an issue filed for every upstream bug. As I said, I'll accept a patch fixing the problem.

@thestinger thestinger closed this Jul 20, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment