Viewing a single comment thread. View all comments

celebratedrecluse wrote

I know. This shit is so fucking obnoxious, i developed a workaround.

What i do is grab a copy of androidx86, verify it then use the install media to setup a virtual machine. Even then, you have to fiddle a bit because androidx86 has its own issues, i have to boot "nomodeset" or it freezes on a startup command line.

At this point, upon boot i disable all the google bullshit i can from within the vm. Fortunately u dont need to do this everytime. I like to do this with the vm manager having blocked the internet, microphone, camera.

After this, you can use a usb stick to transfer the signal apk onto the guest OS and install/configure it, without having to trust the guest OS. I recommend enabling a really secure registration lock.

I then restart, enabling the vm's internet connection. You then register your # with signal. If you want a throwaway #, just get a burner phone and use it to register a google voice/onsip/some similar voip ahead of time over vpn, then log into the vpn and voip on your host OS once youve setup the vm, and use that to register the #. Give away the physical burner phone to someone who needs it, for example lots of houseless people need cell service so just ask around.

This gives you the actual signal app, plus a disposable #, for about $30. And it lasts for life if u keep your voip active (google is free, although obviously sketch)

4

avbeav wrote (edited )

If you want a throwaway #, just get a burner phone and use it to register a google voice/onsip/some similar voip ahead of time over vpn, then log into the vpn and voip on your host OS once youve setup the vm, and use that to register the #.

That's a clever way of dealing with not being able to access a SIM-card from the Android vm!

I used signal-cli with a burner phone for initial registration and that worked fine as well.

What i do is grab a copy of androidx86, verify it then use the install media to setup a virtual machine.

Sounds like a good hack! 🛠

Pros:

  • edit groups
  • initiate conversations

Cons:

  • attaching files? (They'd have to be transferred to the vm)
  • clicking on links? (They'd open in the Android browser, no?)
  • now Signal needs a full separate OS rather than "just" a full separate browser 😨

Edit: Just found this, Signal-curses. Looks promising.

2

celebratedrecluse wrote

Files can be transferred in and out of the vm thru a physical usb stick pretty easy, and you could theoretically force the vm to use vpn or tor if you want to be able to click on links, however both are clunky ur right. And yes, it's absurd to run a 2gb OS just to have one signal app lmao

2

celebratedrecluse wrote

Btw, i highly reccommend 2gb per vm for androidx86. Otherwise the interface will be p slow, ime

1