From what I can tell, BlackBerry OS10 does not support the browse
functionality over bluetooth, if I want to actually mount its microcard,
I have to use USB tethering. Not a big deal for me since the only
reason to mount it is for an rsync backup; in most cases the function I
need is to send a few files and receive them. That works between the
Lenovo Yoga (Android), the BlackBerry, and the XPS13 running Debian-
jessie, now that I've installed "blueman-git" (which I believe is the
maintainer's-last-stable-snapshot).
It's possible that OS10 does support the browse function and I just
don't know how to use it. I don't think I've tried it wrt the Android.
I'm also able to use the BlackBerry as a Network Access Point from the
Android or the Linux install, so I'm a happy camper connectivity-wise,
though I am sitting on a single-point-of-failure on the BlackBerry (as I
was reminded yesterday when its SIM wasn't seated just right), but
that's covered by the Pantech UML295 aircard unless I allow a kernel
update, which (until cdc-acm.ko or whichever is fixed) causes it to
constantly reset.
It seems to work better, and if my understanding is correct it's either
in, or soon-to-be-in, the sid version of Debian.
> A way I WAS ABLE to browse the file systems on the droid device
> that did work without using blueman-applet was this: (all was
> connected) In a user term I ran:
>
> obexftp -b -l
>
> after that completed and was back at prompt I ran:
> (Note that A0:91:69:55:8A:26 is the MAC of my phone)
>
> sdptool browse A0:91:69:55:8A:26
>
> Then in a superuser/root term I created a mount point
> for the droid phone:
>
> mkdir /mnt/android
>
> Then ran this next command in same root term:
>
> obexfs -b A0:91:69:55:8A:26 /mnt/android
>
> I then was able to drill along that mount point path (/mnt/android)
> in any filemanager/shell I chose and was able to browse the
> filesystems on the device, both internal and external. Was able to
> copy, delete etc.
>
> Then when done, to unmount the filesystems
> on the device I ran the below in a root term:
>
> fusermount -u /mnt/android
If you want to mess about with the files on an Android, the way to go is
via the adb command, which comes as part of Android Studio (which is
fairly huge imo, a couple GB of added files as I recall). As I recall
adb runs as Android-root, so as long as you don't kill its server out
from under yourself, or otherwise shoot your foot, all's fair.
Your mention of fusermount, gives me a good laugh at myself:
A little more than a year ago I was running Ubuntu 11.10 (oneiric) and
happy as a clam, making progress on my project. Then I got interested
in Android. Pretty soon I was wanting to build phpfuse and found out
that I was missing a lib or two, then I found out that the oneiric
repository was so old it was gone to bit-heaven. At that point I
started looking for a more current distro, and only a couple days ago
have I reached the point again where I have something running that I can
restore onto a fresh drive and in which all the necessary functions seem
to be working on all my systems, which is a different set of systems
than I started out with.
I was going to move to Debian-sid, but instead I'm freezing on jessie
until my hardware gives out (again) and I end up needing a new distro
(again); the jessie repo should be around until 2020 which is good
enough for now and current enough that I can still install a package
from it when I need to, and in most cases not so far behind the
maintainer's version that I can't modify the current code when that
become necessary. Which means (here's the funny part) I've run out of
excuses and will have to get back to writing actual project code. <g>