Rockbox mail archiveSubject: Re: sleep timer
Re: sleep timer
From: Joseph Jones <joe_at_bumpycarrot.cjb.net>
Date: Mon, 14 Jun 2004 07:45:15 +0100
On a slightly different branch from this, I thought it might be a good
idea to kill the music the instant that the off button is pressed,
whilst on the WPS screen. As it is currently, I have to wait for the
unit to power down if I hit the power to shut it off, and *then* I can
ask the bus driver for a ticket ;)
PS. This sounds like a good idea, if it's workable, but perhaps the
"Off" could just be replaced by a simple, distinct "beep" in the
headphones? If you've hit the power button, you'll be expecting it
anyways. Are there any beep sounds that can be generated on the fly, if
you know what I mean, by just piecing tother the bits to feed to the
MAS? I'm trying to think of a way of cutting down the memory footprint here.
Linus Nielsen Feltzing wrote:
> BlueChip wrote:
>> My best thought on this is to trap the power-off request long enough
>> before the hardware sees it, to affect any shut-down protocols that
>> may be appropriate.
> That works very well for the FM/V2, but the hardware timeout on the
> older models may be very short, less than a second on my recorder.
>> Trap OFF at 2S, get the voice to say "off" to let the user know the
>> trap has happened; they can then release the OFF button before the
>> hardware takes control and trust that Rockbox will finish the process.
> That's exactly how it works for the FM/V2 in the original firmware, but
> I don't think it'll work on the older models, since the user isn't
> likely to let go of the OFF button that fast. ANd as I said above, my
> recorder shuts off in about 1 second.
> We should still implement it on the FM/V2 platforms, though.
>> The biggest drawback I can see with this, is that the speech "off"
>> would need to be ready in RAM at all times; as loading it off disk may
>> take too long and all is lost.
>> Perhaps we could register bash the MAS volume or something and create
>> some form of beep?
> Perhaps. I don't think it's *that* important, as long as the shutdown
> sequence is long enough to allow the user to release the button in time.
Received on 2004-06-14