Article ID: 2834018 - View products that this article applies to.
Users can download the Lync 2013 mobile client for Google Android for free from Google Play. Users can use the client to connect to Lync Online if they're assigned a Lync Online license. This article describes how to troubleshoot some common issues that you may encounter when you use the Lync 2013 mobile client for Google Android.
Note The current release of Lync 2013 for Android smartphones isn't supported on Android media tablets or on other non-phone Android form factors (hardware models). For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2829747/en-us)Android smartphone devices that are supported for use with Lync 2013 for Android
Install the app
The Lync 2013 mobile client for Google Android is available for free from Google Play. Users should install the app directly to their device and use their user ID to sign in.
If users experience issues when they download or install the Lync 2013 mobile client, they should change their connection type from 3G to Wi-Fi or from Wi-Fi to 3G and try downloading again. If the users still can't install the client, they should contact their cellular service provider or contact:
Google Play Support
Sign-in requirements for Google Android
When users sign in to the Lync Mobile app, the sign-in information that's required to successfully authenticate depends on the following scenarios:
If automatic discovery for mobile clients hasn't been configured, users have to enter the following internal and external discovery addresses in addition to the fields that are listed in the table:
Collapse this tableExpand this table
Note : The Sign-in address and Password fields are displayed on the sign-in screen. To access the User name, Domain, Internal discovery address, and External discovery address fields, select Server Settings on the sign-in screen.
The Lync 2013 mobile client for Google Android looks for different DNS records than the Lync 2013 desktop client. For the Auto-Detect process to discover the correct Lync Online service, a CNAME record that meets the following criteria must be created for the SIP domain that's being used:
To troubleshoot, use one or more of the following methods, as appropriate for your situation:
Collapse this tableExpand this table
If the Wi-Fi connection that's used requires authentication before connecting, Lync may not connect because it can't use the credentials to connect through a proxy. To work around this, connect through the mobile carrier’s data connection instead of Wi-Fi.
The contact list that's displayed in the Lync 2013 mobile client for Google Android is read-only and can't be changed from the mobile device. If a user wants to add or remove a contact from the list, the user must use the Lync 2013 desktop client or Outlook Web App (OWA) Instant Messaging (IM).
Contact photos are displayed only if they're stored in the global address list (GAL). A contact who specified images through web URLs on the desktop client won't have a photo displayed for the contact.
Chats tab and conversation history
The Chats tab on the Lync mobile client for Google Android only keeps track of the conversations that occurred on the mobile device. It won't display chats from desktop clients. Chats on mobile devices aren't displayed in the conversation history folder in the user’s Exchange mailbox.
The Lync client supports only digest authentication and does not support integrated/ SPNEGO for authenticated proxy.
Some users may repeatedly see a notification with information that their calls are not set up to ring a mobile device. This is a known issue.
Comparison with other mobile clients
For a feature comparison of Lync 2013 mobile clients, go to the following Microsoft TechNet website:
Mobile Client Comparison Tables
When users experience an issue with the Lync 2013 mobile client for Google Android, they can send logs by email to the technical support engineer. To do this, follow these steps:
Article ID: 2834018 - Last Review: September 4, 2013 - Revision: 3.0