Bug 16415 – 8977 MP candidate has different initial setup behavior current version

Bug 16415 - 8977 MP candidate has different initial setup behavior current version

Summary:

8977 MP candidate has different initial setup behavior current version

Status:	NEW

Product:	SB Radio
Classification:	Unclassified
Component:	Setup
Version:	Include FW version in comment
Platform:	PC Windows XP

Importance:	-- normal (vote)
Target Milestone:	---
Assigned To:	Unassigned bug - please assign me!

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-07-29 16:24 UTC by Ryan
Modified:	2011-11-06 23:23 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 Ryan 2010-07-29 16:24:35 UTC

Current MP firmware 7.4 r7525

When a new unit is set up for the first time once the unit has been connected to the network via WiFi or Ethernet the unit will "phone home" to MSB.com to get an update to the current customer FW, if a connection to MSB.com is not available but there is a connection to a local server  the unit will phone home to the local server and perform an update.
 In this case the customer will then be able to play his/her private content without registering on MSB.com.

The behavior with 7.5.1 r8977 the potential MP version 

When a "new" unit is set up for the first time, once attached to the network if it fails to connect to MSB.com there is then no way to continue on and update to the latest FW that is available on the local server. 

Once connection to MSB.com is available then an update can be initialized manually. Navigate to my music> select your local server> then navigate to software update and go. 

I am not absolutely sure this is unwanted behavior but it is different than what a customer would currently experience.

Comment 1 Alan Young 2011-11-06 23:23:00 UTC

Unassigned bugs cannot have a priority.