STARFACE Mobile Client for Android, Version 6.7.2.0 (Beta), Release Date: 2615.0809.2020 (Beta)
Beta-Version 6.7.2.0 (Release Date: 2615.0809.2020)Important notesVarious 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.
ImprovementsContent 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.
|