Ticket #1641 (closed defect: fixed)
opkg upgrade blows away custom volume settings
Reported by: | hedora | Owned by: | Nytowl |
---|---|---|---|
Priority: | normal | Milestone: | Om2009 |
Component: | Distro | Version: | |
Severity: | normal | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Estimated Completion (week): | ||
HasPatchForReview: | no | PatchReviewResult: | |
Reproducible: |
Description
The *.state files used to control alsa profiles are stored in /usr, and get overwritten without prompting by opkg upgrade.
This is really irritating, since it makes my headphones really loud, and there's no way practical to change the volume back via the current phone UI. Worse, mediaplayer's volume setting doesn't go low enough to make the default settings usable with my headphones...
Shouldn't these be treated as configuration files (so they're not automatically reverted to default values), and be stored in /etc or ~?
Perhaps it could let people override the defaults by checking for a copy of each *.state file in ~/.openmoko or /etc/openmoko before applying the default state. Then a comment could be added to the files in /usr directing people to create / edit copies elsewhere.
Change History
comment:2 in reply to: ↑ 1 Changed 11 years ago by hedora
Sorry; lost track of this. I just set the headphone volume down a bit, and messed with the mixer settings. I don't want to send a patch, since the changes are specific to the headphones that I bought, and the noise levels during my commute.
For now it is a nice way to make people send patches. Would you mind sharing your changed state files and describe what they fix?