Follow

Viggo Mobile

============31.05.2016 ========
-----Viggo iOS version: v.2.16.22.1(build number x.xx)--------------------------
Task #4291, #4292, #4293, #4300

============05.04.2016 ========
-----Viggo apk version: v.2.16.14.1(build number x.xx)--------------------------
BFV #4157, #4168
============23.03.2016 ========
-----Viggo apk version: v.2.16.12.3(build number x.xx)--------------------------
BFV #4035
============23.03.2016 ========
-----Viggo iOS version: v.2.16.12.3(build number x.xx)--------------------------
BFV #4083
============13.03.2016 ========
-----Viggo iOS version: v.2.16.10.5(build number x.xx)--------------------------
Completed Task  4083 FIXED
============06.03.2016 ========
-----Viggo iOS version: v.2.16.09.5(build number x.xx)--------------------------
Task  4083 FIXED
The app checks flat JSON data for Explore-Catigories and uses backend.viggo-sntv.com
============29.02.2016 ========
-----Viggo iOS version: v.2.16.08.7(build number x.xx)--------------------------
bug 3859 - "IOS Long movies (90min) ..." is fixed

============28.02.2016 ========
-----Viggo iOS version: v.2.16.08.4(build number x.xx)--------------------------
- Regarding the Chat: please show alert BEFORE you ask user for room/name
- Task 4080: About templates list for the chat.
If you don't get values in other languages (french, german), just show the english
============25.02.2016 ========
-----Viggo iOS version: v.2.16.07.4(build number x.xx)--------------------------

============04-07.02.2016 ========
-----Viggo iOS version: v.2.16.05.3(build number x.xx)--------------------------
-----Viggo apk version: v.2.16.05.4(build number x.xx)--------------------------
FIX #2624
============06-10.01.2016 ========
-----Viggo iOS version: v.2.16.01.2(build number x.xx)--------------------------
-----Viggo iOS version: v.2.16.01.5(build number x.xx)--------------------------
- FIX #2817, #3249, #3249
- FIX #3959 - "added time interval 0.75 sec between pictures sharing to prevent the bug
"If the user scroll the some pictures quickly ...". We have discussed about it via Skype."
- FIX #3879, #3918
============20.12.2015========
-----Viggo iOS version: v.2.15.xx.x (build number x.xx)--------------------------
- The new UI Dialog about connection state for Media Share
- Now UI Dialogs of the MediaShare reads description from assets/ui/.XML files instead of hardcoded description
- Localisation Strings of the Media Share is loaded from assets/ui/strings.XML instead of hardcoded strings,

============13.12.2015========
-----Viggo iOS version: v.2.15.50.5 (build number x.xx)--------------------------

============09.12.2015========
------Viggo iOS version: v.2.15.50.3 (build number 2.26)--------------------------
- Wording should be: "Your Viggo App is connected to Viggo TV <ServiceName>"- Done
- The ViggoClient IOS  ProgressDialog bug is fixed:
If the ProgressDialog is showed and user exits from the MediaShare to the Landing and returns back to
the MediaShare, then ProgressDialog is showed before "Kindly" dialog is closed.

============05.12.2015========
------Viggo iOS version: v.2.15.50.2--------------------------
- The task 3890 is done.
- The ViggoClient uses AJ servicename tv.viggo.byod._<SSID> to search BYOD
- The AJ Client are started after closing the Dialog "Kindly..." in the MediaShare
- If the AJ Client finds BYOD and user press "Yes" on the ConfirmDialog of BYOD then the Client shows popup about connection with BYOD's device.

============26.11.2015========
------Viggo iOS version: v.2.15.48.2--------------------------
- New tiles on Home Page
- Task 3857 is done

============17.11.2015========
------Viggo iOS version: v.2.15.46.3--------------------------
===============================

============05.11.2015========
------Viggo iOS version: v.2.15.45.3--------------------------
===============================
1. Task #3823- Mobile - new 1st page design

============29.10.2015========
Viggo iOS version: v.2.15.42.4
===============================
1. Bug Fix #3806
2. The Viggo Client sends "command:exit" command after back from the Media Share

============22.10.2015========
Viggo iOS version: v.2.15.42.4
===============================
If the the connection is not established then the alert message shows additional debug information about AllJoyn state

============20.10.2015========
Viggo iOS version: v.2.15.42.3
===============================
Increased time for searching of AllJoyn connection to 25 seconds.
If the the connection is not established then the alert message shows additional debug information about AllJoyn state

============18.10.2015========
Viggo iOS version: v.2.15.41.7
===============================
1) If user logs out then the Alljoyn will disconnected. So if user will login again then the Alljoyn will connect again with checking new room number. (Alljoyn is not disconnected after the logout in the previous version).
2)The font size of progress dialog was increased. (See please Alljoyn connection process)
3)The bug with background of the Settings Dialog  is fixed. Now if the "Settings Dialog" is showed then user can not click behind of the "Settings Dialog" . For example user can not press "Settings button" again.
4)The sensitivity of the "home" and "settings" buttons in the Media Share are improved
============15.10.2015========
Viggo iOS version: v.2.15.40.4
===============================
BFV #
============29.07.2015========
Viggo iOS version: v.2.15.30.3
===============================
BFV #3583
==============================
Installation-
Select City and Hotel
Front Desk
TV Media Share
View Bill
My Hotel
Settings > Hotel Address Navigation
The Apple map View has “Direction” button to show Apple Map Application with Route
About v.2.15.30.3
============16.07.2015========
Viggo iOS version: v.2.15.29.4
==============================
Installation-
Select City and Hotel
Front Desk
TV Media Share
View Bill
My Hotel
Settings > Hotel Address Navigation
The Apple map View has “Direction” button to show Apple Map Application with Route
About v.2.15.29.2
==============================

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk