Skip to content
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

Support for wifi-only devices (f. e. tablets) #1153

Closed
NeXXor opened this issue Mar 14, 2014 · 14 comments
Closed

Support for wifi-only devices (f. e. tablets) #1153

NeXXor opened this issue Mar 14, 2014 · 14 comments

Comments

@NeXXor
Copy link

NeXXor commented Mar 14, 2014

It would be a nice feature, if TextSecure would run wifi-only devices like tablets.

@JavaJens
Copy link

This should work, if not now then in a few releases.

Have you tried registering? You can use your phone and type in the code, that's how the browser plugin works.

But I don't know if the live server supports multiple devices yet...

@NeXXor
Copy link
Author

NeXXor commented Mar 14, 2014

The problem is, that I cannot download TextSecure via the Playstore.I get a message that my "device is not supported". I don't know how Google decides which app is supported and which is not; I have not tried to compile the source on my own or copy the .apk from a 3G device yet to check if it works.

@JavaJens
Copy link

Ah okay. I would suggest you grab a copy of the code, remove some logic that you can directly input the code received via SMS on your regular phone and compile for your self.

But I don't know if you can follow. Maybe there is official support planned, but I don't know.

Sorry for raising your hopes.

@generalmanager
Copy link

You can try sideloading the app via http://apps.evozi.com/apk-downloader/
And then you can activate it, using the number of a phone, similar to using google voice:
http://support.whispersystems.org/customer/portal/articles/1468990-how-can-i-get-textsecure-working-with-my-google-voice-number-

@NeXXor
Copy link
Author

NeXXor commented Mar 14, 2014

Nice idea. I'll check that and report my results later.

@NeXXor
Copy link
Author

NeXXor commented Mar 15, 2014

Worked. Thank you very much!

@generalmanager
Copy link

You're welcome ;)

@JavaJens
Copy link

As you resolved this locally, maybe you can close the issue?
@moxie0 I've got two questions: are you planning on supporting wifi-only
devices? Wouldn't a method for directly inputting the code, ie. skip the
send+call buttons, save you money? I don't think it would be much, but
maybe somewhat considerable for Google Voice and Wifi-only users?

@NeXXor NeXXor closed this as completed Mar 15, 2014
@moxie0
Copy link
Contributor

moxie0 commented Mar 15, 2014

multi-device support is on the roadmap

@stiltgit
Copy link

@NeXXor
can you send messages on your wifi-only device?
#614 states that on Nexus 7 wifi the app crashes when trying to do so after successfull sideloading and registering as explained above (I can replicate this behavior in #614 on my 2012 Nexus 7 Wifi Kitkat)

@bobobo1618
Copy link

Sorry to revive a dead thread but I searched and couldn't find any updates.

@moxie0 are there any updates on multi-device support? Is there an issue I couldn't find tracking the feature? Is there any kind of public area where we can follow progress?

@ChaoticMind
Copy link

@bobobo1618 You can watch the development of the browser extension. I would assume that Its release is a strong indication that a version of multi-device support is ready at least in some form.

@tildelowengrimm
Copy link

Why is multi-device support being conflated with wifi-only device support?

The version of TextSecure in the Play Store is still not marked as compatible with wifi-only devices. Since the Play Store is the recommended way to install TextSecure, I'd suggest that this issue is not actually resolved — people with wifi-only devices can't install TextSecure the recommend way.

@agerwick
Copy link

agerwick commented Apr 6, 2016

Why is this issue closed? I can't see it having been resolved. I just installed Signal on an Android phone without a sim card, using the verification by phone (to my dumb-phone, where I keep my sim card), but in Google Play store any device in our household that are designed to not have a sim card (i.e. tablets) are considered as incompatible.

I don't see why:

  1. using a phone number as an ID can be the cause of this issue, as I might as well use a tablet and receive a verification call on another phone, just like I did on my sim-less android phone.
  2. there is a need to use phone number as the only form of ID, why not use email addresses, or a used generated string for that mater?
  3. the UI not being designed for tablets can be a significant problem. I've used lots of other apps that were "designed for phones", and they work just fine. Not optimal perhaps but better than nothing!

@signalapp signalapp locked and limited conversation to collaborators Apr 6, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

9 participants