From owner-freebsd-hackers@freebsd.org Tue Feb 5 18:13:23 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A057F14C39E6 for ; Tue, 5 Feb 2019 18:13:23 +0000 (UTC) (envelope-from waitman@waitman.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E627F87AC4 for ; Tue, 5 Feb 2019 18:13:22 +0000 (UTC) (envelope-from waitman@waitman.net) Received: by mailman.ysv.freebsd.org (Postfix) id A55C314C39E5; Tue, 5 Feb 2019 18:13:22 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 802E714C39E3 for ; Tue, 5 Feb 2019 18:13:22 +0000 (UTC) (envelope-from waitman@waitman.net) Received: from mail-40132.protonmail.ch (mail-40132.protonmail.ch [185.70.40.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.protonmail.ch", Issuer "SwissSign Server Silver CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0FC6387AC3 for ; Tue, 5 Feb 2019 18:13:21 +0000 (UTC) (envelope-from waitman@waitman.net) Date: Tue, 05 Feb 2019 18:13:09 +0000 To: "hackers@freebsd.org" From: Waitman Gobble Reply-To: Waitman Gobble Subject: Re: bsd android tethering using USB cable - intermittent failure Message-ID: In-Reply-To: <201902051634.x15GYg7l077811@fire.js.berklix.net> References: <201902051634.x15GYg7l077811@fire.js.berklix.net> Feedback-ID: a9EiCCViSiSHQ6Bx5OnM7zSE3j9mdPjjMltovBgA7v_vv_C4nKI9vbMXvmk_xW33cGmibh2zGAa2Co0Llrno4A==:Ext:ProtonMail MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.protonmail.ch X-Rspamd-Queue-Id: 0FC6387AC3 X-Spamd-Bar: ------ X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.991,0] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2019 18:13:23 -0000 =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On Tuesday, February 5, 2019 12:34 PM, Julian H. Stacey w= rote: > Matthias Apitz wrote: > > > El d=C3=ADa Tuesday, February 05, 2019 a las 02:36:59PM +0100, Julian H= . Stacey escribi=C3=B3: > > > > > Hi hackers@, > > > I tether Androids to FreeBSDs using USB cables, Using > > > ports/devel/android-tools-adb Mostly it works, but sometimes fails to > > > connect, I've no idea why. > > > I've tried: different physical androids, different versions of androi= d (4 & 5), > > > different physical ports (once I had a cable hanging down didnt conne= ct on > > > laptop socket), via hub & direct avoiding usb hub, different FreeBSDs > > > (all of 10.4-RELEASE 11.2-RELEASE 13.0-CURRENT), 2 different FreeBSD = PCs > > > Could someone please please take a look at > > > http://www.berklix.org/android/#adb > > > & perhaps spot what I'm forgetting to initialise ? > > > > With my Ubuntu Phone (which has as well an Android kernel behind the > > scenes), I learned that one must enable developer mode and even with > > this on connect the display must be unlocked and a pop up answered > > about the permission. > > Thanks , Yes I've got developer mode on (7 taps on build version) > & dont know how to lock display so always on, & yes I do always > touch screen to tether. > > Ive tried rebooting BSD today didnt help. Dont think ive tried > rebooting the Androids today. I wondered if I had some hidden > faulty initialiser file so just removed a bunch of ~/.[a-zA-Z]* > that I didnt recognise or didnt want. > > Weirdly, adb shell has now just connected on the phone I want to > move data on. > > & also weirdly ifconfig -a > does Not display a ue0: eg from past: > ue0: flags=3D8802 metric 0 mtu 1500 > > =09ether xx:xx:xx:xx:xx:xx > > > though I thought I needed ue to tether with, > ifconfig -a just shows ether & local bge0: & lo0: > > Unfortunately my background devd set up the connection before I > killed it & switched to foreground /sbin/devd -d so xterm scroll > back does not show what device, but I grabbed a tar copy of /dev > to look at later > > My Android popped up with a less often seen screen: USB PC Connection > Connect as > Media device (MTP) which shows pre-ticked Green > Camera (PTP) which shows blank, un-checked. > > Well I wont disturb that pair of devs that are ready to talk, > I'll start long transfer of data I need, > > but I will contine to experiment on another pair of devs, > > Cheers, > Julian > I've done the android connect on FreeBSD quite often without any trouble, f= or years, however one time it acted the way you described I decided it was = a crappy cable. I threw the cable in the trash and totally stopped having t= hat problem. (just in case you didn't try different cables) Waitman Gobble