Seitenhistorie

STARFACE Mobile Client for Android, Version 6.7.7 (Build 348), Release Date: 16.02.2021

Version 6.7.7 (Release Date: 16.02.2021)

Important notes

• Various manufacturers (including Huawei, Xiaomi and OnePlus) have recently tightened their battery management policies for many devices in the course of optimizing battery consumption. This prevents the background activity of apps in certain constellations if the user does not explicitly allow it for an app. It is possible that this stricter policy for handling background activity of apps may also have an impact on the STARFACE Mobile Client. We therefore recommend checking the settings on the device side with regard to prioritized background activity and adjusting the settings if necessary. Important settings are 1. "Deactivate battery optimization for the app" and 2. "Set the respective app to 'Manually manage' under App-Start". In addition, it may be necessary to adjust the settings for prioritizing the notifications of the STARFACE app on some devices to ensure that the app notifications (e.g. for incoming calls) are still displayed as usual. These settings may differ slightly depending on manufacturer, device and Android version.

• The following link provides a brief guide to this (with some device-specific examples): Error Guide - Calls are not displayed in the Mobile Client.

Bugfixes

• Bugfixes to improve stability.

STARFACE Mobile Client for Android, Version 6.7.6 (Build 347), Release Date: 12.02.2021

Version 6.7.6 (Release Date: 12.02.2021)

Important notes

• Various manufacturers (including Huawei, Xiaomi and OnePlus) have recently tightened their battery management policies for many devices in the course of optimizing battery consumption. This prevents the background activity of apps in certain constellations if the user does not explicitly allow it for an app. It is possible that this stricter policy for handling background activity of apps may also have an impact on the STARFACE Mobile Client. We therefore recommend checking the settings on the device side with regard to prioritized background activity and adjusting the settings if necessary. Important settings are 1. "Deactivate battery optimization for the app" and 2. "Set the respective app to 'Manually manage' under App-Start". In addition, it may be necessary to adjust the settings for prioritizing the notifications of the STARFACE app on some devices to ensure that the app notifications (e.g. for incoming calls) are still displayed as usual. These settings may differ slightly depending on manufacturer, device and Android version.

• The following link provides a brief guide to this (with some device-specific examples): Error Guide - Calls are not displayed in the Mobile Client.

Bugfixes

• On STARFACE systems with a global line configuration for Austria, outgoing calls caused a crash [Call#6981319] [Call#6981443].
• Bugfixes to improve stability.

STARFACE Mobile Client for Android, Version 6.7.5.0 (Build 345), Release Date: 01.02.2021

Version 6.7.5.0 (Release Date: 01.02.2021)

Important notes

• Various manufacturers (including Huawei, Xiaomi and OnePlus) have recently tightened their battery management policies for many devices in the course of optimizing battery consumption. This prevents the background activity of apps in certain constellations if the user does not explicitly allow it for an app. It is possible that this stricter policy for handling background activity of apps may also have an impact on the STARFACE Mobile Client. We therefore recommend checking the settings on the device side with regard to prioritized background activity and adjusting the settings if necessary. Important settings are 1. "Deactivate battery optimization for the app" and 2. "Set the respective app to 'Manually manage' under App-Start". In addition, it may be necessary to adjust the settings for prioritizing the notifications of the STARFACE app on some devices to ensure that the app notifications (e.g. for incoming calls) are still displayed as usual. These settings may differ slightly depending on manufacturer, device and Android version.

• The following link provides a brief guide to this (with some device-specific examples): Error Guide - Calls are not displayed in the Mobile Client.

Improvements

• If the public access prefix is activated, outgoing calls without the specified prefix are executed correctly.

Bugfixes

• If the public access prefix was activated, a call from the call list could not be started correctly without the specified prefix [Call#6949830][Call#6952879][Call#6953288][Call#6956810][Call#6970988][Call#6945246][Call#6962780][Call#6963131].
• If the public access prefix was activated, calling a fully qualified external number from the Numpad without the specified prefix failed.
• If the public access prefix was activated, the callback of an external number via the call symbol in the Voicemail tab of the journal did not work correctly.
• In some cases, it took a long time to display the search results when searching in the Keys tab of the Contacts screen.
• Bugfixes to improve stability.

STARFACE Mobile Client for Android, Version 6.7.4.0 (Build 342), Release Date: 15.12.2020

Version 6.7.4.0 (Release Date: 15.12.2020)

Important notes

• Various manufacturers (including Huawei, Xiaomi and OnePlus) have recently tightened their battery management policies for many devices in the course of optimizing battery consumption. This prevents the background activity of apps in certain constellations if the user does not explicitly allow it for an app. It is possible that this stricter policy for handling background activity of apps may also have an impact on the STARFACE Mobile Client. We therefore recommend checking the settings on the device side with regard to prioritized background activity and adjusting the settings if necessary. Important settings are 1. "Deactivate battery optimization for the app" and 2. "Set the respective app to 'Manually manage' under App-Start". In addition, it may be necessary to adjust the settings for prioritizing the notifications of the STARFACE app on some devices to ensure that the app notifications (e.g. for incoming calls) are still displayed as usual. These settings may differ slightly depending on manufacturer, device and Android version.
  
  The following link provides a brief guide to this (with some device-specific examples): Error Guide - Calls are not displayed in the Mobile Client.

Improvements

• Compatibility with STARFACE 7

• Open and copy links in chat messages.

• Improved display of links in chat messages.

Bugfixes

• Bugfixes to ensure compatibility with STARFACE 7.
• Bugfixes to improve stability.
• It was not possible to start a call for the Mobile Client for Android correctly via the UCC client (a black empty call screen was shown).
• A link from a chat message could not be opened or copied.
• Users could change their name via the app while Active Directory was active.
• For journal entries of the call list, fax list and voicemail sent from a different time zone, the wrong time was specified (according to German time zone).
• In the journal, missed calls, voicemail messages and fax messages were always signaled as new (using the orange counter).
• Direct dial keys were not displayed if you opened the Keys tab from an active call when starting a consultation call.
• Empty call screen was shown after a call attempt during an active GSM Call was ended from the other party.
• Chat status icons were not displayed on the mini-BLFs in the chat view.
• From the "Contact details" of a user's BLF (Contacts --> Buttons --> Open contact), it was not possible to start a chat using the "Start chat" button.
• App crashed when a user who doesn't have softphone license opened the settings menu.
• If you entered a non-existent server address / hostname in the login screen, then the login attempt took a very long time until it failed.
• In some cases, a newly received chat message was displayed twice after starting the client.
• In certain constellations the device was still in silent mode after a finished phone call instead of being in loud mode as before.
• In certain constellations the name of the called party was not displayed in the call screen of the STARFACE Mobile Client for Android (if the called party was using a STARFACE Mobile Client for iPhone and his client was in the background during the call).
• In rare cases a logout was not possible and an error message was displayed.

STARFACE Mobile Client for Android, Version 6.7.3.0, Release Date: 18.09.2020

Version 6.7.3.0 (Release Date: 18.09.2020)

Important notes

• Various manufacturers (including Huawei, Xiaomi and OnePlus) have recently tightened their battery management policies for many devices in the course of optimizing battery consumption. This prevents the background activity of apps in certain constellations if the user does not explicitly allow it for an app. It is possible that this stricter policy for handling background activity of apps may also have an impact on the STARFACE Mobile Client. We therefore recommend checking the settings on the device side with regard to prioritized background activity and adjusting the settings if necessary. Important settings are 1. "Deactivate battery optimization for the app" and 2. "Set the respective app to 'Manually manage' under App-Start". In addition, it may be necessary to adjust the settings for prioritizing the notifications of the STARFACE app on some devices to ensure that the app notifications (e.g. for incoming calls) are still displayed as usual. These settings may differ slightly depending on manufacturer, device and Android version.

Bugfixes

• On STARFACE cloud systems without a fixed IP address, telephony (audio transmission) did not work [Call#6967589].

STARFACE Mobile Client for Android, Version 6.7.2.0, Release Date: 15.09.2020

Version 6.7.2.0 (Release Date: 15.09.2020)

Important notes

• Various manufacturers (including Huawei, Xiaomi and OnePlus) have recently tightened their battery management policies for many devices in the course of optimizing battery consumption. This prevents the background activity of apps in certain constellations if the user does not explicitly allow it for an app. It is possible that this stricter policy for handling background activity of apps may also have an impact on the STARFACE Mobile Client. We therefore recommend checking the settings on the device side with regard to prioritized background activity and adjusting the settings if necessary. Important settings are 1. "Deactivate battery optimization for the app" and 2. "Set the respective app to 'Manually manage' under App-Start". In addition, it may be necessary to adjust the settings for prioritizing the notifications of the STARFACE app on some devices to ensure that the app notifications (e.g. for incoming calls) are still displayed as usual. These settings may differ slightly depending on manufacturer, device and Android version.

Improvements

• Content improvement of the log files.

• In the case of a spontaneous conference, a consultation call is first made to the selected participant, while the original party is put on hold.

Bugfixes

• The call quality deteriorated on Samsung devices with Android 10 when the system back button was clicked during an active call [Call#6962948][Call#6957862].
• When a spontaneous conference was initiated, the original call partner was not put on hold for the duration of the call from the 3rd subscriber.
• Call was sometimes not hung up correctly when the user was logged out during a call.
• When clicking the Back button in the Settings menu item, a crash occurred in some cases.
• After an invited person rejected the invitation to a spontaneous conference, the conference button was inactive and no alternative participant could be invited.
• In some cases an empty call screen was displayed on the Mobile Client after the call was answered on another device.
• At the beginning of a call, in some cases the other party could only be heard after a delay of a few seconds.
• After the device was unused for some time before, in some cases incoming calls were not correctly signalled.
• In some cases, a call was not terminated correctly if one party had network problems during an active call and the call was subsequently terminated by the other party.
• Newly created chat status messages were not retained if you logged out, changed servers in the meantime and then logged in again.
• In some cases it took a very long time after login to load the chat entries in the journal and their contents.
• If the user previously deactivated and reactivated the softphone on the Mobile Client, in some cases the subsequent call could not be ended correctly and the call was still shown on the display as an active call.
• Bugfixes to improve stability.