Fixed
Status Update
Comments
er...@google.com <er...@google.com> #2
Forgot to mention running platform-tools 26.0.0. And Android "O" public beta
er...@google.com <er...@google.com> #3
Not to be "that guy" but is there any update on this? Any additional information needed?
ch...@google.com <ch...@google.com>
ch...@google.com <ch...@google.com> #4
Project: platform/system/core
Branch: master
commit f806a3c303028014eec43894386fbfb117667684
Author: Josh Gao <jmgao@google.com>
Date: Fri Aug 18 18:25:44 2017
fastboot: gracefully handle failure to open a USB device on OS X.
High Sierra restricts opening some USB devices (e.g. the touchbar)
to processes that have specific entitlements. Ignore devices that we
can't open.
Bug:http://b/64292422
Test: manual
Change-Id: I6074b53a365b8d936610bafea60244f8bba1a33f
M fastboot/usb_osx.cpp
https://android-review.googlesource.com/461857
https://goto.google.com/android-sha1/f806a3c303028014eec43894386fbfb117667684
Branch: master
commit f806a3c303028014eec43894386fbfb117667684
Author: Josh Gao <jmgao@google.com>
Date: Fri Aug 18 18:25:44 2017
fastboot: gracefully handle failure to open a USB device on OS X.
High Sierra restricts opening some USB devices (e.g. the touchbar)
to processes that have specific entitlements. Ignore devices that we
can't open.
Bug:
Test: manual
Change-Id: I6074b53a365b8d936610bafea60244f8bba1a33f
M fastboot/usb_osx.cpp
ch...@google.com <ch...@google.com>
vi...@gmail.com <vi...@gmail.com> #5
Since OSX 10.13 is being released the 25th of September (in 5 days as of writing), is it possible to create a new Android Platform Tools release, so the impact can be as low as possible?
ch...@google.com <ch...@google.com> #6
Project: platform/system/core
Branch: sdk-release
commit 73f4670f380679ba5e6081968ba7ea992edf51b9
Author: Josh Gao <jmgao@google.com>
Date: Fri Aug 18 18:25:44 2017
fastboot: gracefully handle failure to open a USB device on OS X.
High Sierra restricts opening some USB devices (e.g. the touchbar)
to processes that have specific entitlements. Ignore devices that we
can't open.
Bug:http://b/64292422
Test: manual
Change-Id: I6074b53a365b8d936610bafea60244f8bba1a33f
(cherry picked from commit f806a3c303028014eec43894386fbfb117667684)
M fastboot/usb_osx.cpp
https://android-review.googlesource.com/489920
https://goto.google.com/android-sha1/73f4670f380679ba5e6081968ba7ea992edf51b9
Branch: sdk-release
commit 73f4670f380679ba5e6081968ba7ea992edf51b9
Author: Josh Gao <jmgao@google.com>
Date: Fri Aug 18 18:25:44 2017
fastboot: gracefully handle failure to open a USB device on OS X.
High Sierra restricts opening some USB devices (e.g. the touchbar)
to processes that have specific entitlements. Ignore devices that we
can't open.
Bug:
Test: manual
Change-Id: I6074b53a365b8d936610bafea60244f8bba1a33f
(cherry picked from commit f806a3c303028014eec43894386fbfb117667684)
M fastboot/usb_osx.cpp
vi...@gmail.com <vi...@gmail.com> #7
Thanks for the reminder, I'm kicking off the process now.
ch...@google.com <ch...@google.com> #8
Release process is still churning along, until then I've attached the binary we're planning to release that should work on 10.13.
vi...@gmail.com <vi...@gmail.com> #10
Sweet, thanks a bunch!
vi...@gmail.com <vi...@gmail.com> #11
I think i still have this issue
MacBookPro13,3 (late 16" touchbar)
macOS 10.13 (17A405)
fastboot version 4022467
bnaya@bmbp ~ $ fastboot --version
fastboot version -4022467
Installed as /Users/bnaya/Library/Android/sdk/platform-tools/fastboot
bnaya@bmbp ~ $ fastboot devices
ERROR: Unable to create a plug-in (e00002be)
Sudo didn't help
MacBookPro13,3 (late 16" touchbar)
macOS 10.13 (17A405)
fastboot version 4022467
bnaya@bmbp ~ $ fastboot --version
fastboot version -4022467
Installed as /Users/bnaya/Library/Android/sdk/platform-tools/fastboot
bnaya@bmbp ~ $ fastboot devices
ERROR: Unable to create a plug-in (e00002be)
Sudo didn't help
ch...@google.com <ch...@google.com> #12
More info:
when starting adb i see this message
bnaya@bmbp platform-tools $ adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
adb E 10-28 17:42:35 1657 37964 usb_osx.cpp:152] Unable to create an interface plug-in (e00002be)
* daemon started successfully *
LGH815*** device
when starting adb i see this message
bnaya@bmbp platform-tools $ adb devices
List of devices attached
* daemon not running. starting it now at tcp:5037 *
adb E 10-28 17:42:35 1657 37964 usb_osx.cpp:152] Unable to create an interface plug-in (e00002be)
* daemon started successfully *
LGH815*** device
vi...@gmail.com <vi...@gmail.com> #13
it not yet fix
ch...@google.com <ch...@google.com> #14
Same error message for me. MacOS 10.13, Platform-tools 26.0.2
ap...@google.com <ap...@google.com> #15
it seems the version attached in comment#8 actually works on MacOSHighSierra,
(./fastboot version 9dc0875966c0-android ) , but the one (version -4022467) included in 26.0.2 tools release, does not work (it reports the same bug)
I've just flashed fine with the provided version (9dc0875966c0).
(./fastboot version 9dc0875966c0-android ) , but the one (version -4022467) included in 26.0.2 tools release, does not work (it reports the same bug)
I've just flashed fine with the provided version (9dc0875966c0).
ch...@google.com <ch...@google.com> #16
jmgao: did we somehow lose this patch when we fixed the Pixel 2 support bug?
Description
1.0.0-alpha07
DEVICE NAME: (Nexus 5X, Samsung S6, etc)
name : FUJITSU arrowsM04
Android OS version : 7.1.1
name: FUJITSU F-04J
Android OS version : 6.0.1
name: FUJITSU F-05J
Android OS version : 7.1.1
DESCRIPTION:
We receive following crash report from our app user.
Fatal Exception: java.lang.IllegalArgumentException: Can not get supported output size under supported maximum for the format: 34
at a.c.a.b.k0.a + 98(SupportedSurfaceCombination.java:98)
at a.c.a.b.k0.a + 30(SupportedSurfaceCombination.java:30)
at a.c.a.b.t.a + 22(Camera2DeviceSurfaceManager.java:22)
at androidx.camera.core.k1.a + 98(CameraX.java:98)
at androidx.camera.core.k1.a + 22(CameraX.java:22)
at a.c.b.c.a + 6(ProcessCameraProvider.java:6)
at <out app package name>.CameraFragment.a + 33(CameraFragment.kt:33)
at <out app package name>.CameraFragment.a + 1(CameraFragment.kt:1)
at <out app package name>.CameraFragment$m.run + 1(CameraFragment.kt:1)
at android.os.Handler.handleCallback + 751(Handler.java:751)
at android.os.Handler.dispatchMessage + 95(Handler.java:95)
at android.os.Looper.loop + 154(Looper.java:154)
at android.app.ActivityThread.main + 6262(ActivityThread.java:6262)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run + 890(ZygoteInit.java:890)
at com.android.internal.os.ZygoteInit.main + 780(ZygoteInit.java:780)
REPRODUCIBILITY: (5 of out 5, 1 out of 100, etc)
We receive this crash report from only three devices. And these devices's manufacturer is FUJITSU.
ADDITIONAL INFORMATION:
CODE FRAGMENTS (this will help us troubleshoot your issues):
Our app bind usecases by following code.
private fun bindCameraUseCases(processCameraProvider: ProcessCameraProvider) {
preview = Preview.Builder().apply {
setTargetAspectRatio(AspectRatio.RATIO_4_3)
}.build().apply {
previewSurfaceProvider = binding.previewViewCamera.previewSurfaceProvider
}
imageCapture = ImageCapture.Builder().apply {
setCaptureMode(ImageCapture.CaptureMode.MINIMIZE_LATENCY)
setTargetAspectRatio(AspectRatio.RATIO_4_3)
setFlashMode(FlashMode.OFF)
}.build()
val cameraSelector = CameraSelector.Builder().requireLensFacing(LensFacing.BACK).build()
processCameraProvider.bindToLifecycle(viewLifecycleOwner, cameraSelector, preview, imageCapture)
}