Cisco Cisco StadiumVision Mobile Reporter
16
Release Notes for Cisco StadiumVision Mobile Release 2.0
Caveats
CSCup03595—Under rare circumstances fatal exception encountered in Android app
Symptom
A fatal exception occurs in the Android app.
Conditions
Tab to one of the audio only channels in application and encountered fatal exception.
Workaround
There is no workaround.
CSCuw03647—User interface (UI) changes time as per the client time zone
Symptom
The UI changes the time of an event based on the client time zone and is displayed in the
"Upload Event Schedule" page.
Steps
1.
Set up the Reporter server locally in the local time zone.
2.
Upload an event schedule from a different time zone.
3.
Go to the “Upload Event Schedule” page and check the event time on the already uploaded event
schedule.
schedule.
The Reporter UI should not change the time of the event schedule as per the client time zone, however
the Reporter UI changes the time of the event schedule as per the client time zone.
the Reporter UI changes the time of the event schedule as per the client time zone.
Workaround
There is no workaround.
CSCuo50199—When playing a video and home button is pressed sometimes video will stop playing
Symptom
Video stops playing.
Conditions
Bring up the Cisco StadiumVision Mobile application. Play a video. While it is playing the
video, press the home button. Quickly return to the app. It stays on a blank page and the video does not
start. The app is active and you can go back to the channel list. This is observed on:
start. The app is active and you can go back to the channel list. This is observed on:
HTC One 5.5 running Android 4.4.2, Google Nexus, Samsung Galaxy S3
Workaround
Go back to the channel list and select the video channel again.
CSCuo50209—Upgrading the Cisco StadiumVision Mobile Streamer sometimes causes existing configuration to be lost
Symptom
The Cisco StadiumVision Mobile Streamer configuration is lost after performing an upgrade.
Conditions
The “streamer.cfg” file no longer contains any configurations.
Workaround
To safeguard against this issue it is strongly recommended to backup the existing
“streamer.cfg” file before upgrading. If this issue occurs restore the “streamer.cfg” file with the backup
copy.
copy.