NetBSD-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Bluetooth on current

MLH wrote:
> Manuel Bouyer wrote:
> > On Sat, Jun 09, 2018 at 07:00:50AM -0400, MLH wrote:
> > > Manuel Bouyer wrote:
> > > > On Fri, Jun 08, 2018 at 08:07:45PM -0400, MLH wrote:
> > > > > My old Android phone which allowed writes to the removable sd card
> > > > > was stolen and I had to get a new one, which only allows certain
> > > > > things to be written there (not enough).

> > > [ 297159.8136557] umodem0 at uhub2 port 1 configuration 1 interface 1
> > > [ 297159.8136557] umodem0: SAMSUNG (0x4e8) SAMSUNG_Android (0x6860), rev 2.00/4.00, addr 4, iclass 2/2
> > > [ 297159.8136557] umodem0: data interface 2, has no CM over data, has no break
> > > [ 297159.8136557] umodem0: status change notification available
> > > [ 297159.8136557] ucom0 at umodem0
> The Samsung doesn't work when in either MTP or PTP mode with libmtp,
> but note that the Samsung phone doesn't show a ugen when connected,
> only ucom/umodem, so I suspect that might be the problem with that
> phone.
> Back to bluetooth, I wonder if there isn't some notification client
> that has to connect to sdpd to confirm the transfer. On any other
> bluetooth device when receiving, they pop up a requestor to confirm
> the transfer. I don't see mention of anything in particular though.

Ok, so I gave up and went and bought a cheap used wireless router,
put an s/ftp server on the phone, ftp'ed the ssh key over and now
easily xfer to from the phone using sftp, etc.

However, since I put a fair amount of exercise into attempting USB
MTP and Bluetooth access and think I got pretty close, it would be
nice to go ahead and try to get those working also.

After spending some time with the Samsung Galaxy, I discovered that
in MTP mode it connects to ucom0 and in PTP mode to ugen0! However,
  ugen0: SAMSUNG (0x4e8) SAMSUNG_Android (0x6866), rev 2.00/2.28, addr 3
not as:
  umodem0: SAMSUNG (0x4e8) SAMSUNG_Android (0x6860), rev 2.00/4.00, addr 3, iclass 2/2

Note the 0x6866 instead of 0x6860. libmtp includes entries for the
Samsung 0x6860 devices but not the 0x6866!  Ha.

So I might add the 0x6866 entry and recompile to see if it is
detected in PTP mode though I believe I really want MTP mode. But
not as a umodem/ucom device for libmtp's purposes. On reading the
code, it appears to me that libmtp only can use ugen devices though
I very well might have missed something.

Any thoughts? :^)

Home | Main Index | Thread Index | Old Index