From owner-freebsd-current@FreeBSD.ORG Thu Aug 14 06:32:02 2014 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 576B8AEE; Thu, 14 Aug 2014 06:32:02 +0000 (UTC) Received: from mail-we0-x230.google.com (mail-we0-x230.google.com [IPv6:2a00:1450:400c:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BE2072891; Thu, 14 Aug 2014 06:32:01 +0000 (UTC) Received: by mail-we0-f176.google.com with SMTP id q58so643934wes.21 for ; Wed, 13 Aug 2014 23:32:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-type:content-transfer-encoding; bh=iTBpXdQkBcyRrKQFLzlFzJxSIaO6uFyhQYc7dMlrKeo=; b=XSNU8OdaaN6IaxQ01ThTRLoIUISGW+FNtypPfMjMBBNpUFI0+RZ7F3sPMcyQ8pEJOC FH5lYzrzK9UjDCrfEuQ3/8MYVHYjS7NZA4iBQcGNZeRXNLRxFw/zHWIk1bqFJbm1FJha 7BofZAcspYkAJkSBNskXTSbDw4H/49jtxVt/eoZwJSqKntAbrutlpAUBiug15O5LmYYj yz3rpPD97hWXfTV2/CL9+LefcFJwhxG3Mz7SpN6tCFc8IjBN2FpMIzqRkWM2F9zzi/0y 1u5hklisC70L/PaC89+72CdWd+vTs3aYF/KcQ4bXNFSbKPK70gbcmxVPHF8otQvsdp+9 kPRQ== X-Received: by 10.194.170.227 with SMTP id ap3mr9244681wjc.30.1407997920040; Wed, 13 Aug 2014 23:32:00 -0700 (PDT) Received: from ernst.home (p4FCA71FE.dip0.t-ipconnect.de. [79.202.113.254]) by mx.google.com with ESMTPSA id a4sm76115459wie.21.2014.08.13.23.31.58 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Wed, 13 Aug 2014 23:31:59 -0700 (PDT) Date: Thu, 14 Aug 2014 08:31:56 +0200 From: Gary Jennejohn To: Shane Ambler Subject: Re: android bsd connectivity tools etc ? Message-ID: <20140814083156.394fc06a@ernst.home> In-Reply-To: <53EC3930.6060604@ShaneWare.Biz> References: <201408132347.s7DNlcHU013055@fire.js.berklix.net> <53EC3930.6060604@ShaneWare.Biz> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.17; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 14 Aug 2014 11:36:54 +0000 Cc: Gary Jennejohn , "Julian H. Stacey" , current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Aug 2014 06:32:02 -0000 On Thu, 14 Aug 2014 13:51:04 +0930 Shane Ambler wrote: > On 14/08/2014 09:17, Julian H. Stacey wrote: > > Hi, > > Any tips for Android / FreeBSD BSD tools for connectivity etc ? > > > > I just got a Samsung Galaxy Note 3, with Android 4.4.2 kernel 3.4.0 > > > I'll build a current from a 10.0-RELEASE partition, > > but now looking with 9.2-RELEASE I see: > > > > /dev/ > > lrwxr-xr-x 1 root wheel 9 Aug 14 00:01 ugen1.5@ -> usb/1.5.0 > > crw------- 1 root operator 0x7a Aug 14 00:00 usb/1.5.0 > > crw------- 1 root operator 0x8f Aug 14 00:00 usb/1.5.1 > > crw------- 1 root operator 0x90 Aug 14 00:00 usb/1.5.2 > > > > I have a cheap Huawei phone running 2.3.6 > When I plug in the usb cable to charge it, it shows up as 3 devices > > da0 at umass-sim1 bus 1 scbus5 target 0 lun 0 > da0: < Android Adapter 0100> Removable Direct Access SCSI-2 device > cd1 at umass-sim1 bus 1 scbus5 target 0 lun 1 > cd1: < Android Adapter 0100> Removable CD-ROM SCSI-2 device > da1 at umass-sim1 bus 1 scbus5 target 0 lun 2 > da1: < Android Adapter 0100> Removable Direct Access SCSI-2 device > > On the phone I get a message to turn on usb mass storage after which I > can mount_msdosfs /dev/da0s1 and get access to the sdcard in the phone. > > It looks like mass storage was hidden in 4.0 and maybe removed after 4.2. > Try searching the android app store for usb mass storage. > > Online storage like google drive? > Running HEAD-11. I have a Zopo Z980+ running 4.2.2. I see this when I plug it in: Aug 14 08:19:44 ernst kernel: ugen6.2: at usbus6 Aug 14 08:19:44 ernst kernel: umass0: on usbus6 Aug 14 08:19:44 ernst kernel: da0 at umass-sim0 bus 0 scbus8 target 0 lun 0 Aug 14 08:19:44 ernst kernel: da0: Removable Direct Access SCSI-2 device Aug 14 08:19:44 ernst kernel: da0: 40.000MB/s transfers Aug 14 08:19:44 ernst kernel: da0: Attempt to query device size failed: NOT READY, Medium not present Aug 14 08:19:44 ernst kernel: da0: quirks=0x2 Aug 14 08:19:44 ernst kernel: da1 at umass-sim0 bus 0 scbus8 target 0 lun 1 Aug 14 08:19:44 ernst kernel: da1: Removable Direct Access SCSI-2 device Aug 14 08:19:44 ernst kernel: da1: 40.000MB/s transfers Aug 14 08:19:44 ernst kernel: da1: Attempt to query device size failed: NOT READY, Medium not present Aug 14 08:19:44 ernst kernel: da1: quirks=0x2 This trace corresponds to the internal and external storage. After enabling USB storage on the phone I can mount the internal storage, but not the external storage. You have to be sure that USB debugging is turned off in the developer options. These may not even be visible on your device because Google hid them at around 4.2. I suspect that you just need some quirks to support the device. -- Gary Jennejohn