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.
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:2829747
Android smartphone devices that are supported for use with Lync 2013 for AndroidInstall 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:
- Whether a user’s Session Initiation Protocol (SIP) address is the same as the user’s user principal name (UPN)
- Whether users are hosted on an on-premises Lync server or on Lync Online
The following table describes the sign-in fields required for Android users:
Collapse this tableExpand this table
|User is hosted by||SIP address and UPN||Required fields|
|On-premises Lync server||SIP address and UPN are the same||Sign-in address: SIP address|
User name: Blank
|On-premises Lync server||SIP address and UPN are different||Sign-in address: SIP address|
User name: UPN or domain\username
|Office 365||SIP address and UPN are the same||Sign-in address: SIP address|
User Name: Blank
|Office 365||SIP address and UPN are different||Sign-in address: SIP address|
User name: UPN
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:
*These addresses are valid only for Office 365 users and will be different for On-premises Lync server deployments.Note
: The Sign-in address
fields are displayed on the sign-in screen. To access the User name
, Internal discovery address
, and External discovery address
fields, select Server Settings
on the sign-in screen.Troubleshoot Auto-Detect
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:
Collapse this tableExpand this table
|<Your web directory location>Example: Webdir.online.lync.com|
To troubleshoot, use one or more of the following methods, as appropriate for your situation:
Connecting over Wi-Fi through an authenticating proxy
- Use the nslookup command and a public DNS server to determine whether the DNS CNAME record is configured correctly.
- If the user has the option, have the user switch between Wi-Fi and 3G to determine whether the issue can be scoped to one kind of connection. If sign in continues to fail on a 3G data connection, although the CNAME DNS records are configured, it may be an issue with the cellular service provider’s data connection.
- The user receives the following error message:
Cannot connect to the server. It might be unavailable. Also please check your network connection, sign-in address and server addresses.
This error message usually indicates one of the following conditions:
- A DNS lookup issue exists.
- The Auto-Detect CNAME records are configured incorrectly or aren't configured at all.
- The user receives the following error message when the user tries to sign in:
Can’t sign in. Please check your account information and try again.
This error message indicates one of the following conditions:
- The Lync 2013 mobile client for Google Android can discover the correct Lync Online server. However, it can't find the sign-in address that was entered by the user.
- The password is incorrect.
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.Contact lists
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
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.Security
The Lync client supports only digest authentication and does not support integrated/ SPNEGO for authenticated proxy.Notifications
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:
- On the Android device, after a user is signed in, press the hardware menu button and tap Options in the menu. On the Options screen, check if the Logging option is turned on. If not, turn on the Logging option, sign out, and then sign in again.
- Reproduce the issue, return to the Options screen, and then tap Send Log Files.
- Select a configured email account.
- In the To box, enter the recipient's email address. In the Subject box, enter a subject, and then tap Send. Logs are attached as a .zip file.