-
-
Notifications
You must be signed in to change notification settings - Fork 6.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure to Identify Contacts #170
Comments
I can't imagine that this is still a problem after nearly a year. This has been reworked several times. Can you give us feedback if it's still an issue or if it can be closed? |
Also android 2.2 is not supported, going to close this and @JAV4NkfV can reopen if necessary :). |
There was no new version for me to install on Froyo so I can't re-install I mainly use a Nexus 7 2013 tablet for communication now, and was Hope you guys get a multi-platform version out soon, otherwise Wickr is Thanks for checking back in with me. :) On Wed, Apr 16, 2014 at 1:03 PM, Jake McGinty [Masked] <
|
You can sideload via http://apps.evozi.com/apk-downloader/ but it appears that on your specific tablet TS currently crashes for yet to be determined reasons: TextSecure does the WhatsApp-style push messages as well as SMS now. There are also iOS + browser addon versions in development: |
Phone: Motorola Triumph
Android: 2.2.2
Provider: Virgin Mobile
This is not a serious issue but it has been bugging me for a while. TextSecure will fail to identify some of my contacts either by not displaying a picture, their name, or both.
I can not figure out why it identifies some contacts with name and picture but not others. I thought it might be because some contacts are synced from my e-mail account and some are stored locally on the phone but I tested this and the account type did not seem to matter.
However, contacts that do not show picture or name on the list view landing page will sometimes have the picture in the thread conversation view, but no name.
The text was updated successfully, but these errors were encountered: