Bug 11594 – Info page in web ui fails to show updated fw version

Bug 11594 - Info page in web ui fails to show updated fw version

Summary:

Info page in web ui fails to show updated fw version

Status:	RESOLVED DUPLICATE of bug 12908

Product:	SqueezePlay
Classification:	Unclassified
Component:	SB Server
Version:	unspecified
Platform:	All All

Importance:	-- minor (vote)
Target Milestone:	7.4.0
Assigned To:	Michael Herger

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-04-01 10:39 UTC by Jim McAtee
Modified:	2009-09-08 09:18 UTC (History)
CC List:	3 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 Jim McAtee 2009-04-01 10:39:19 UTC

I'm guessing this must only be updated when the player first connects.  Maybe the player needs to send a message to the server telling it about the new version whenever it updates itself.

Comment 1 James Richardson 2009-04-01 10:58:48 UTC

Andy: would that be a function of SN or the firmware?

Comment 2 Andy Grundman 2009-04-01 11:17:48 UTC

I don't believe Fab4 reports the firmware version to SC.

Comment 3 Blackketter Dean 2009-04-01 14:00:07 UTC

It does.  I see this:

Player Model: fab4
Firmware: 7.4-r5069

the info tab under settings.

It does not, however, update until you restart SC.  Upgrading, reconnecting or rebooting the player are not enough.

Comment 4 Michael Herger 2009-04-08 03:15:13 UTC

Ben/Richard - is SP sending that information out to SC when it's reconnecting?

Comment 5 Jim McAtee 2009-04-09 13:15:36 UTC

Another effect of the server not knowing the correct firmware version is that on the Fab4 itself, if you go to

Settings > Advanced > Information > Player Information > <Fab4>

you see the old firmware version there, which conflicts with what you see under Settings > Advanced > About.

Comment 6 Richard Titmuss 2009-07-23 08:24:01 UTC


*** This bug has been marked as a duplicate of bug 12908 ***