Core Apps » Bazaar

BlueFTP can directly send APKs on custom ROMs that have disabled the filter that stock Android ROMs have when sending files via bluetooth. It is possible to rename the file, like foo.apk.jpg and it'll go thru on a stock phone. It is also possible to zip up an APK and it'll go thru, i.e. foo.apk.zip.

If there is a standard location where incoming bluetooth file transfers are put, perhaps in /sdcard/downloads or elsewhere, then this can be used to detect whether F-Droid was just installed via bluetooth. Then it can prompt the user to go thru the p2p repo setup with the person who just send the APK over.

<uses-feature /> will probably have to be setup somehow:
https://developer.android.com/guide/topics/manifest/uses-feature-element.html#bt-permission-handling

Android Beam support for FDroid is included in this merge request, it works well and doesn't disallow sending APKs:
https://gitorious.org/f-droid/fdroidclient/merge_requests/59

Standard bluetooth is a different story. I tested with a CM 10.1 Samsung Note2 and a stock Google Nexus 7. The Nexus 7 would neither send nor receive an APK via standard Bluetooth file transfer. It also failed both ways between Note2/CM10.1 and a Motorola Xoom running TeamEOS ROM, which is based on AOSP.

Made some progress. I got stock Android to send an APK, but it still rejects receiving. CyanogenMod does both just fine. In order to get stock Android to send the APK, I just had to set the MIME type for .zip rather than .apk. I.e.:

intent.setType("application/zip");

Instead of:

intent.setType("application/vnd.android.package-archive");

my working example:
https://stackoverflow.com/questions/16277593/bluetooth-file-transfer-on-androideven-restricted-types/21790899#21790899

    PackageManager pm = getPackageManager();
    ApplicationInfo appInfo;
    try {
        appInfo = pm.getApplicationInfo("org.fdroid.fdroid",
                PackageManager.GET_META_DATA);
        Intent sendBt = new Intent(Intent.ACTION_SEND);
        // NOT THIS! sendBt.setType("application/vnd.android.package-archive");
        sendBt.setType("application/zip");
        sendBt.putExtra(Intent.EXTRA_STREAM,
                Uri.parse("file://" + appInfo.publicSourceDir));
        sendBt.setClassName("com.android.bluetooth",
                "com.android.bluetooth.opp.BluetoothOppLauncherActivity");
        startActivity(sendBt);
    } catch (NameNotFoundException e1) {
        e1.printStackTrace();
    }

But will the receiving end open an APK installer if the mime type is for zip?

Works fine for me, but I've only tested on CM10.1 so far. My guess is that the MIME type info is not sent via Bluetooth.

Works fine for me, but I've only tested on CM10.1 so far. My guess is that the MIME type info is not sent via Bluetooth.

I did a quick test from stock 4.4.2 Nexus 7 to a stock Samsung Galaxy Player 5.0, and the Player 5.0 received the file and installed it! So it seems that even some Samsung ROMs don't include that block.

When I try to send FDroid from a Nexus 7 running stock to a Nexus 4 running CM nightlies I see the transfer fail and the following logcat output on the N7 after selecting the N4 as the transfer endpoint:

othDiscoveryReceiver V Received: android.bluetooth.adapter.action.DISCOVERY_FINISHED
ocalBluetoothManager D setting foreground activity to null
FDroid D Category 'What's New' selected.
BtOppService D insertShare parsed URI: file:///data/app/org.fdroid.fdroid-2.apk
BluetoothOppUtility D getSendFileInfo: uri=file:///data/app/org.fdroid.fdroid-2.apk
BluetoothAdapter W getBluetoothService() called with no BluetoothManagerCallback
BTIF_SOCK D service_uuid: 00001105-0000-1000-8000-00805f9b34fb
BluetoothSocket D connect(), SocketState: INIT, mPfd: {ParcelFileDescriptor: FileDescriptor[97]}
bt-sdp W SDP - Rcvd conn cnf with error: 0x4 CID 0x42
bt-btif E DISCOVERY_COMP_EVT slot id:5, failed to find channle, status:1,scn:0
bt-btif W invalid rfc slot id: 5
BtOppTransfer E Rfcomm socket connect exception
BtOppTransfer E java.io.IOException: read failed, socket might closed or timeout, read ret: -1
BtOppTransfer E at android.bluetooth.BluetoothSocket.readAll(BluetoothSocket.java:505)
BtOppTransfer E at android.bluetooth.BluetoothSocket.readInt(BluetoothSocket.java:516)
BtOppTransfer E at android.bluetooth.BluetoothSocket.connect(BluetoothSocket.java:320)
BtOppTransfer E at com.android.bluetooth.opp.BluetoothOppTransfer$SocketConnectThread.run(BluetoothOppTransfer.java:627)
BtOppTransfer D Mark all ShareInfo in the batch as failed
BluetoothOppUtility D getSendFileInfo: uri=file:///data/app/org.fdroid.fdroid-2.apk
BluetoothOppUtility D closeSendFileInfo: uri=file:///data/app/org.fdroid.fdroid-2.apk

I don't see anything in the N4's logcat. No notifications or messages about an incoming file transfer.

Scratch the above report & stack trace. I selected a hex address as the destination assuming it was the Nexus4 and I hadn't set a Bluetooth name. Turns out I have some neighbours broadcasting bluetooth nearby.

Bluetooth is enabled on the Nexus4 but I had to launch F-Droid, choose the "Bluetooth F-Droid apk" and then click "allow" on the "An app wants to make your device bluetooth visible for the next ..." popup before the N4 would show up in the N7's Bluetooth device scan.

Is there a setting to enable broadcast somewhere else? I'm not sure how I'd have done that on the N4 if I didn't already have the F-Droid app.