Android apps that launch a browser (native) to do authentication, don't communicate back, eg TapKey

[sebix]

The realistic option for you is to install an Android Browser and use that as suggested in this thread.

@AL13N

what would be a realistic expectation of this next update (whether BT would be in it or not)

are we talking like next month or more like 6 months?

This is not known.

If you have some spare time, you can try this hack on your own (and at your own risk!) and share your experience and feedback in that thread:

Potential Bluetooth Support in the Android App Support (AAS)

Enable Developer Tools enable SSH remote access and connect to C2 via SSH: Go to root: $ devel-su Stop AAS if running from SFOS settings menu. Stop bluetooth and bluebinder services: [root@JollaC2 defaultuser]# systemctl stop bluetooth [root@JollaC2 defaultuser]# systemctl stop bluebinder [root@JollaC2 defaultuser]# systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; disabled; vendor preset: enabled) Active: i…

@AL13N

what about the NFC? is that also not in the android subsystem?

There are no known plans for NFC support in the Android subsystem.