Bug 14151 – power_toggle fails after power_off sent to Baby/Radio, Fab4/Touch

Bug 14151 - power_toggle fails after power_off sent to Baby/Radio, Fab4/Touch

Summary:

power_toggle fails after power_off sent to Baby/Radio, Fab4/Touch

Status:	RESOLVED WORKSFORME

Product:	SqueezePlay
Classification:	Unclassified
Component:	UI
Version:	7.4.x
Platform:	All All

Importance:	P4 normal (vote)
Target Milestone:	7.5.0
Assigned To:	Felix Mueller

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-09-19 18:23 UTC by Peter Watkins
Modified:	2009-10-21 09:48 UTC (History)
CC List:	2 users (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Peter Watkins 2009-09-19 18:23:29 UTC

Baby at 7.4.0r7656 and Fab4 at 7.4.0r7649: if the player is turned off with the power_off discrete IR code, the player cannot be turned on with the old power_tggle IR code. On both players, power_toggle causes a normal screen to briefly appear, but the player quickly switches off again (the off screensaver takes over again).

On Baby/Radio, the front panel power button has the same effect as the power_toggle IR code.

Both seem to behave normally again only after sending a discrete power_on IR code.

Comment 1 James Richardson 2009-09-19 19:11:24 UTC

this appears to be app related.  Please target appropriately.

Comment 2 Felix Mueller 2009-10-16 02:30:36 UTC

Works for me with Baby 7.4.0 r7790 and Fab4 7.5.0 r7859. Used IR Blaster to send discrete power on and off commands.

Could you please re-test with the latest firmware and reopen the bug if you still see the issue.

Thanks
Felix

Comment 3 Chris Owens 2009-10-21 09:48:04 UTC

Moving these bugs to P4 to make room for moving P1.5 bugs to P2