Status Update
Comments
uc...@google.com <uc...@google.com> #2
This is a particularly hard device to come by - do you happen to have access to the device? If so could you provide us with the output of: adb shell dumpsys media.camera > info.txt
Thanks!
vs...@google.com <vs...@google.com> #3
Stacktrace:
Caused by: java.lang.IllegalArgumentException: Can not get supported output size under supported maximum for the format: 34
at androidx.camera.camera2.internal.SupportedSurfaceCombination.getSupportedOutputSizes(SupportedSurfaceCombination.java:355)
at androidx.camera.camera2.internal.SupportedSurfaceCombination.getSuggestedResolutions(SupportedSurfaceCombination.java:197)
at androidx.camera.camera2.internal.Camera2DeviceSurfaceManager.getSuggestedResolutions(Camera2DeviceSurfaceManager.java:198)
at androidx.camera.core.CameraX.calculateSuggestedResolutions(CameraX.java:943)
at androidx.camera.core.CameraX.bindToLifecycle(CameraX.java:293)
at androidx.camera.lifecycle.ProcessCameraProvider.bindToLifecycle(ProcessCameraProvider.java:227)
Below are some findings based on our debugging
When Dex is connected
previewConfig.getMaxResolution() is returning "731x411" as maxSize.
Inside Preview.Builder.build() -> Default_MAX_resolution is set to "CameraX.getSurfaceManager().getPreviewSize()" which is 731x411
this is being picked as maxSize.
While rendering maxSize is 731x411 and minSize is 640x480 and below are available outputSizes
0 = {Size@11860} "4032x3024"
1 = {Size@11861} "3984x2988"
2 = {Size@11862} "4032x2268"
3 = {Size@11863} "3024x3024"
4 = {Size@11864} "2976x2976"
5 = {Size@11865} "3840x2160"
6 = {Size@11866} "3264x2448"
7 = {Size@11867} "4032x1960"
8 = {Size@11868} "2880x2160"
9 = {Size@11869} "3264x1836"
10 = {Size@11870} "2160x2160"
11 = {Size@11871} "2560x1440"
12 = {Size@11872} "2224x1080"
13 = {Size@11873} "2048x1152"
14 = {Size@11874} "1920x1080"
15 = {Size@11875} "1440x1080"
16 = {Size@11876} "1088x1088"
17 = {Size@11877} "1280x720"
18 = {Size@11878} "1024x768"
19 = {Size@11879} "1056x704"
20 = {Size@11880} "960x720"
21 = {Size@11881} "960x540"
22 = {Size@11882} "720x720"
23 = {Size@11883} "800x450"
24 = {Size@11884} "720x480"
25 = {Size@11885} "640x480"
26 = {Size@11886} "352x288"
27 = {Size@11887} "320x240"
28 = {Size@11888} "256x144"
29 = {Size@11889} "176x144"
and couldn't find any size in this range.
When Dex not connected
minsize = 640x480
maxsize = 1920x1080
0 = {Size@11836} "4032x3024"
1 = {Size@11837} "3984x2988"
2 = {Size@11838} "4032x2268"
3 = {Size@11839} "3024x3024"
4 = {Size@11840} "2976x2976"
5 = {Size@11841} "3840x2160"
6 = {Size@11842} "3264x2448"
7 = {Size@11843} "4032x1960"
8 = {Size@11844} "2880x2160"
9 = {Size@11845} "3264x1836"
10 = {Size@11846} "2160x2160"
11 = {Size@11847} "2560x1440"
12 = {Size@11848} "2224x1080"
13 = {Size@11849} "2048x1152"
14 = {Size@11850} "1920x1080"
15 = {Size@11851} "1440x1080"
16 = {Size@11852} "1088x1088"
17 = {Size@11853} "1280x720"
18 = {Size@11854} "1024x768"
19 = {Size@11855} "1056x704"
20 = {Size@11856} "960x720"
21 = {Size@11857} "960x540"
22 = {Size@11858} "720x720"
23 = {Size@11859} "800x450"
24 = {Size@11860} "720x480"
25 = {Size@11861} "640x480"
26 = {Size@11862} "352x288"
27 = {Size@11863} "320x240"
28 = {Size@11864} "256x144"
29 = {Size@11865} "176x144"
and we have 12 available sizes in this range
Camera2DeviceSurfaceManager.java:: getPreviewSize()
mCameraSupportedSurfaceCombinationMap.get(cameraId).getSurfaceDefinition().getPreviewSize() = "1920x1080"
cameraId=0
en...@google.com <en...@google.com> #4
The issue root cause is that CameraX will default filter out sizes smaller than 640x480. For Preview, the max size will be limited to under display size. I checked the HW spec info for the issue related devices. Display size of FUJITSU F-04J/F-05J is 360x640. That will result int that no size exists in the conditions that is larger or equal to 640x480 and smaller or equal to 360x640.
A temporary workaround for this situation is to use Preview.Builder#setTargetResolution() to set a size smaller than 640x480 to bypass the problem.
For device FUJITSU arrowsM04, I checked its HW spec info and its display size I found is 1280x720. It seems that the problem should not exist in the device.
Could you confirm that the problem exist on arrowsM04 device? What will be the returned value when using Display#getRealSize to obtain the display size?
a....@gmail.com <a....@gmail.com> #5
> A temporary workaround for this situation is to use Preview.Builder#setTargetResolution() to set a size smaller than 640x480 to bypass the problem.
OK. I will try it.
> Could you confirm that the problem exist on arrowsM04 device?
We receive the crash report (Crashlytics) that this crash has occurred on arrowsM04.
We don't have this device so we can't confirm that the problem really exist on arrowsM04.
> What will be the returned value when using Display#getRealSize to obtain the display size?
We can't investigate it for the same reason.
Thank you.
ba...@gmail.com <ba...@gmail.com> #6
This issue happened on devices that the display size is smaller than 640x480. In original auto-resolution mechanism, supported sizes smaller than 640x480 will be default filter out.
The auto-resolution mechanism encodes the guaranteed configurations tables in CameraDevice#createCaptureSession(SessionConfiguration). It defines that the PREVIEW size is the small one of the device display size and 1080p. The PREVIEW size will be the maximal size limitation for Preview use case. The reason it limits the size to display size and 1080p is the stream output in display size or 1080p has been able to provide good enough preview quality. Therefore, auto-resolution mechanism will limit the selected size to be smaller than the small one of the device display size and 1080p.
With above two conditions, in this issue, all sizes smaller than 640x480 have been filter out, therefore, there is no size smaller than the display size 320x240 can be selected to use. And cause the exception.
Solution:
When the display size is smaller than 640x480, auto-resolution mechanism won't filter out those small sizes smaller than 640x480. This makes those small size be left and can be selected for the Preview use case on small display devices.
The solution has been merged and will be included in next CameraX release.
zy...@google.com <zy...@google.com> #7
Hello.
This crash still occurs.
- CAMERAX VERSION: 1.0.0-beta4
- ANDROID OS BUILD NUMBER: Android 7.1.1
- DEVICE NAME: FUJITSU F-02H
We receive following crash report from FUJITSU F-02H. So far We have received this crash report only from F-02H.
java.lang.IllegalArgumentException
Can not get supported output size under supported maximum for the format: 34
androidx.camera.camera2.internal.SupportedSurfaceCombination.getSupportedOutputSizes (SupportedSurfaceCombination.java:349)
androidx.camera.camera2.internal.SupportedSurfaceCombination.getSuggestedResolutions (SupportedSurfaceCombination.java:197)
androidx.camera.camera2.internal.Camera2DeviceSurfaceManager.getSuggestedResolutions (Camera2DeviceSurfaceManager.java:198)
androidx.camera.core.CameraX.calculateSuggestedResolutions (CameraX.java:949)
androidx.camera.core.CameraX.bindToLifecycle (CameraX.java:351)
androidx.camera.lifecycle.ProcessCameraProvider.bindToLifecycle (ProcessCameraProvider.java:230)
(our application's package name).CameraFragment.bindCameraUseCases (CameraFragment.java:174)
ba...@gmail.com <ba...@gmail.com> #8
Could you help to provide the following information to clarify the issue?
1. Is the full name of the device Fujitsu Arrows NX F-02H that has a 1440x2560 display?
2. Please help to provide the supported output sizes of ImageFormat.PRIVATE that is obtained by StreamConfigurationMap#getOutputSizes(int).
pa...@google.com <pa...@google.com>
zy...@google.com <zy...@google.com> #9
- Is the full name of the device Fujitsu Arrows NX F-02H that has a 1440x2560 display?
Yes
- Please help to provide the supported output sizes of ImageFormat.PRIVATE that is obtained by StreamConfigurationMap#getOutputSizes(int).
Since we don't have this device, we'll try to collect this information in the next version of our app. The next version will be released later this month.
en...@google.com <en...@google.com> #10
Hello.
- Please help to provide the supported output sizes of ImageFormat.PRIVATE that is obtained by StreamConfigurationMap#getOutputSizes(int).
We have collected the output of the device where the crash occurs.
Device1
- Model : arrows Be F-05J
- Android Version : 7.1.1
- Supported output sizes of ImageFormat.PRIVATE
CameraId 0: 480x480
CameraId 1: 2048x1536 ,1920x1080 ,1280x720 ,960x720 ,640x480 ,320x240 ,176x144
Device2
- Model : Fujitsu arrows M04
- Android Version : 7.1.1
- Supported output sizes of ImageFormat.PRIVATE
CameraId 0: 480x480
CameraId 1: 2048x1536 ,1920x1080 ,1280x720 ,960x720 ,640x480 ,320x240 ,176x144
Additional Information
CameraX version : 1.0.0-beta04
We collect the supported output sizes by following code.
val errorString = buildString {
append("The supported output sizes of ImageFormat.PRIVATE: ")
(requireContext().getSystemService(Context.CAMERA_SERVICE) as CameraManager).apply {
cameraIdList.forEachIndexed { index, cameraId ->
val msg = if (VERSION.SDK_INT >= VERSION_CODES.M) {
val configurationMap =
getCameraCharacteristics(cameraId).get(CameraCharacteristics.SCALER_STREAM_CONFIGURATION_MAP)
val sizes = configurationMap?.getOutputSizes(ImageFormat.PRIVATE)
"CameraId $index: ${sizes?.joinToString(" ,")}"
} else {
"CameraId $index: This device version is under M."
}
append(msg)
}
}
}
a....@gmail.com <a....@gmail.com> #11
ba...@gmail.com <ba...@gmail.com> #12
I tried to find the device specs and both 720x1280
size display. For the camera id 0 device, it is a different case that the display size is larger than 640x480
but the device only supports a 480x480
size. The case also caused the same IllegalArgumentException and was also fixed by 1.0.0-beta04
release. Before 480x480
size would be filtered out and then caused the IllegalArgumentException. After it was merged, the 640x480
size threshold was removed and then the 480x480
size would be kept and selected to use.
It looks like 1.0.0-beta04
release had been used to collect the supported sizes information. But the issue should have been fixed by 1.0.0-beta04
release. Did you only check the device model name to collect the supported sizes information or collect the information when the IllegalArgumentException issue happens again?
CameraX's 1.0.0-beta04
version. Maybe you can also consider to upgrade to the latest 1.0.0-rc01
version for your application. Thanks.
en...@google.com <en...@google.com> #13
Did you only check the device model name to collect the supported sizes information or collect the information when the IllegalArgumentException issue happens again?
We collect informations only from the device on which IllegalArgumentException happened.
Our latest app uses CameraX version 1.0.0-beta10
and this issue still occurres.
However we don't receive crash report from Fujitsu arrows Be F-05J
or Fujitsu arrows M04
so far. (This doesn't mean this issue is fixed on these devices because our app is heavily rely on camera so these device's user wouldn't use our app anymore.)
Instead, we receive crash report from
- Model : Fujitsu F-03K
- Android Version : 7.1.2
- Supported output sizes of ImageFormat.PRIVATE
CameraId 0 : 480x480
CameraId 1 : 2048x1536 ,1920x1080 ,1280x720 ,960x720 ,640x480 ,320x240 ,176x144
pa...@google.com <pa...@google.com>
sm...@google.com <sm...@google.com> #14
I missed some settings when I simulated the issue by robolectric test so that I was not able to reproduce it. Now, I can reproduce the issue if the device only supports one 480x480 resolution. I'm working on the solution and target to make it included in next release.
jm...@google.com <jm...@google.com> #15
Branch: androidx-main
commit 69d15dff7bb857ee33a0f643ff42a0f8bc475ab2
Author: charcoalchen <charcoalchen@google.com>
Date: Fri Jan 08 18:30:03 2021
Fixed IllegalArgumentException issue happened when all preview supported sizes are smaller than 640x480 and display size is larger than 640x480.
Do not filter out sizes smaller than 640x480 when all preview supported sizes are smaller than 640x480 and display size is larger than 640x480.
Relnote:"Fixed IllegalArgumentException issue happened when all preview supported sizes are smaller than 640x480 and display size is larger than 640x480."
Bug: 150506192
Test: SupportedSurfaceCombinationTest
Change-Id: I2a63ce8e2ad42a9cc060c8635ac3603bf440b1ec
M camera/camera-camera2/src/main/java/androidx/camera/camera2/internal/SupportedSurfaceCombination.java
M camera/camera-camera2/src/test/java/androidx/camera/camera2/internal/SupportedSurfaceCombinationTest.java
ba...@gmail.com <ba...@gmail.com> #16
en...@google.com <en...@google.com> #18
separately, for those who're seeing this: are you on IPv6 networks by any chance?
am...@gmail.com <am...@gmail.com> #19
am...@gmail.com <am...@gmail.com> #20
although the command that crashed my adb was adb shell
en...@google.com <en...@google.com> #21
am...@gmail.com <am...@gmail.com> #22
am...@gmail.com <am...@gmail.com> #23
am...@gmail.com <am...@gmail.com> #24
C:\Users\Loise\AppData\Local\Android\sdk\platform-tools>adb2 -s IBAAWC7S5H5HSGNR shell "echo 'ready'"
adb2 I 03-29 08:36:26 8576 6860 adb_trace.cpp:178] Android Debug Bridge version 1.0.39
adb2 I 03-29 08:36:26 8576 6860 adb_trace.cpp:178] Revision 47a91c209b6d-android
adb2 I 03-29 08:36:26 8576 6860 adb_trace.cpp:178]
adb2 I 03-29 08:36:26 8576 6860 adb_client.cpp:271] adb_query: host-serial:IBAAWC7S5H5HSGNR:features
adb2 I 03-29 08:36:26 8576 6860 adb_client.cpp:124] _adb_connect: host:version
adb2 I 03-29 08:36:26 8576 6860 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:101] writex: fd=2048 len=16 30303063686f73743a76657273696f6e 000chost:version
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2 I 03-29 08:36:26 8576 6860 adb_client.cpp:157] _adb_connect: return fd 2048
adb2 I 03-29 08:36:26 8576 6860 adb_client.cpp:165] adb_connect: service host-serial:IBAAWC7S5H5HSGNR:features
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303034 0004
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303237 0027
adb2 I 03-29 08:36:26 8576 6860 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2 I 03-29 08:36:26 8576 6860 adb_client.cpp:124] _adb_connect: host-serial:IBAAWC7S5H5HSGNR:features
adb2 I 03-29 08:36:26 8576 6860 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:101] writex: fd=2048 len=41 30303235686f73742d73657269616c3a 0025host-serial:
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2 I 03-29 08:36:26 8576 6860 adb_client.cpp:157] _adb_connect: return fd 2048
adb2 I 03-29 08:36:26 8576 6860 adb_client.cpp:245] adb_connect: return fd 2048
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303030 0000
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:75] readx: fd=2048 wanted=0
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:91] readx: fd=2048 wanted=0 got=0
adb2 I 03-29 08:36:26 8576 6860 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2 I 03-29 08:36:26 8576 6860 commandline.cpp:762] shell -e 0x7e t=3 use_shell_protocol=false shell_type_arg=pty
adb2 I 03-29 08:36:26 8576 6860 commandline.cpp:762]
adb2 I 03-29 08:36:26 8576 6860 adb_client.cpp:124] _adb_connect: host:version
adb2 I 03-29 08:36:26 8576 6860 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:101] writex: fd=2048 len=16 30303063686f73743a76657273696f6e 000chost:version
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2 I 03-29 08:36:26 8576 6860 adb_client.cpp:157] _adb_connect: return fd 2048
adb2 I 03-29 08:36:26 8576 6860 adb_client.cpp:165] adb_connect: service shell:echo 'ready'
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303034 0004
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303237 0027
adb2 I 03-29 08:36:26 8576 6860 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2 I 03-29 08:36:26 8576 6860 adb_client.cpp:124] _adb_connect: shell:echo 'ready'
adb2 I 03-29 08:36:26 8576 6860 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:101] writex: fd=2048 len=35 30303166686f73743a7472616e73706f 001fhost:transpo
adb2 I 03-29 08:36:26 8576 6860 adb_client.cpp:91] Switch transport in progress
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2 I 03-29 08:36:26 8576 6860 adb_client.cpp:98] Switch transport success
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:101] writex: fd=2048 len=22 303031327368656c6c3a6563686f2027 0012shell:echo '
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2 I 03-29 08:36:26 8576 6860 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2 I 03-29 08:36:26 8576 6860 adb_client.cpp:157] _adb_connect: return fd 2048
adb2 I 03-29 08:36:26 8576 6860 adb_client.cpp:245] adb_connect: return fd 2048
adb2 I 03-29 08:36:26 8576 6860 commandline.cpp:308] read_and_dump(): pre adb_read(fd=2048)
adb2 I 03-29 08:36:26 8576 9236 commandline.cpp:516] stdin_read_thread_loop(): pre unix_read_interruptible(fdi=0,...)
adb2 I 03-29 08:36:26 8576 6860 commandline.cpp:310] read_and_dump(): post adb_read(fd=2048): length=7
ready
adb2 I 03-29 08:36:26 8576 6860 commandline.cpp:308] read_and_dump(): pre adb_read(fd=2048)
adb2 I 03-29 08:36:26 8576 6860 commandline.cpp:310] read_and_dump(): post adb_read(fd=2048): length=0
answering
am...@gmail.com <am...@gmail.com> #25
C:\Users\Loise\AppData\Local\Android\sdk\platform-tools>adb2.exe -s IBAAWC7S5H5HSGNR install "C:\Program Files (x86)\Appium\node_modules\appium\build\settings_apk\settings_apk-debug.apk
adb2.exe I 03-29 08:39:40 5852 9408 adb_trace.cpp:178] Android Debug Bridge version 1.0.39
adb2.exe I 03-29 08:39:40 5852 9408 adb_trace.cpp:178] Revision 47a91c209b6d-android
adb2.exe I 03-29 08:39:40 5852 9408 adb_trace.cpp:178]
adb2.exe I 03-29 08:39:40 5852 9408 adb_client.cpp:271] adb_query: host-serial:IBAAWC7S5H5HSGNR:features
adb2.exe I 03-29 08:39:40 5852 9408 adb_client.cpp:124] _adb_connect: host:version
adb2.exe I 03-29 08:39:40 5852 9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:101] writex: fd=2048 len=16 30303063686f73743a76657273696f6e 000chost:version
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:40 5852 9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:40 5852 9408 adb_client.cpp:165] adb_connect: service host-serial:IBAAWC7S5H5HSGNR:features
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303034 0004
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303237 0027
adb2.exe I 03-29 08:39:40 5852 9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:40 5852 9408 adb_client.cpp:124] _adb_connect: host-serial:IBAAWC7S5H5HSGNR:features
adb2.exe I 03-29 08:39:40 5852 9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:101] writex: fd=2048 len=41 30303235686f73742d73657269616c3a 0025host-serial:
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:40 5852 9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:40 5852 9408 adb_client.cpp:245] adb_connect: return fd 2048
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303030 0000
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=0
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=0 got=0
adb2.exe I 03-29 08:39:40 5852 9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:40 5852 9408 adb_client.cpp:271] adb_query: host-serial:IBAAWC7S5H5HSGNR:features
adb2.exe I 03-29 08:39:40 5852 9408 adb_client.cpp:124] _adb_connect: host:version
adb2.exe I 03-29 08:39:40 5852 9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:101] writex: fd=2048 len=16 30303063686f73743a76657273696f6e 000chost:version
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:40 5852 9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:40 5852 9408 adb_client.cpp:165] adb_connect: service host-serial:IBAAWC7S5H5HSGNR:features
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303034 0004
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303237 0027
adb2.exe I 03-29 08:39:40 5852 9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:40 5852 9408 adb_client.cpp:124] _adb_connect: host-serial:IBAAWC7S5H5HSGNR:features
adb2.exe I 03-29 08:39:40 5852 9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:101] writex: fd=2048 len=41 30303235686f73742d73657269616c3a 0025host-serial:
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:40 5852 9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:40 5852 9408 adb_client.cpp:245] adb_connect: return fd 2048
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303030 0000
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=0
adb2.exe I 03-29 08:39:40 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=0 got=0
adb2.exe I 03-29 08:39:40 5852 9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:40 5852 9408 adb_client.cpp:124] _adb_connect: host:version
adb2.exe I 03-29 08:39:41 5852 9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:101] writex: fd=2048 len=16 30303063686f73743a76657273696f6e 000chost:version
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:41 5852 9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:41 5852 9408 adb_client.cpp:165] adb_connect: service sync:
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303034 0004
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303237 0027
adb2.exe I 03-29 08:39:41 5852 9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:41 5852 9408 adb_client.cpp:124] _adb_connect: sync:
adb2.exe I 03-29 08:39:41 5852 9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:101] writex: fd=2048 len=35 30303166686f73743a7472616e73706f 001fhost:transpo
adb2.exe I 03-29 08:39:41 5852 9408 adb_client.cpp:91] Switch transport in progress
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:41 5852 9408 adb_client.cpp:98] Switch transport success
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:101] writex: fd=2048 len=9 3030303573796e633a 0005sync:
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:41 5852 9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:41 5852 9408 adb_client.cpp:245] adb_connect: return fd 2048
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:101] writex: fd=2048 len=46 53544154260000002f646174612f6c6f STAT&.../data/lo
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=16
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=16 got=16 53544154000000000000000000000000 STAT............
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:101] writex: fd=2048 len=42568 53454e442c0000002f646174612f6c6f SEND,.../data/lo
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=8
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=8 got=8 4f4b415900000000 OKAY....
C:\Program Files (x86)\Appium\node_modules\appium\build\se...debug.apk: 1 file pushed. 1.3 MB/s (42500 bytes in 0.031s)
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:101] writex: fd=2048 len=8 5155495400000000 QUIT....
adb2.exe I 03-29 08:39:41 5852 9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:41 5852 9408 adb_client.cpp:271] adb_query: host-serial:IBAAWC7S5H5HSGNR:features
adb2.exe I 03-29 08:39:41 5852 9408 adb_client.cpp:124] _adb_connect: host:version
adb2.exe I 03-29 08:39:41 5852 9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:101] writex: fd=2048 len=16 30303063686f73743a76657273696f6e 000chost:version
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:41 5852 9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:41 5852 9408 adb_client.cpp:165] adb_connect: service host-serial:IBAAWC7S5H5HSGNR:features
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303034 0004
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303237 0027
adb2.exe I 03-29 08:39:41 5852 9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:41 5852 9408 adb_client.cpp:124] _adb_connect: host-serial:IBAAWC7S5H5HSGNR:features
adb2.exe I 03-29 08:39:41 5852 9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:101] writex: fd=2048 len=41 30303235686f73742d73657269616c3a 0025host-serial:
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:41 5852 9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:41 5852 9408 adb_client.cpp:245] adb_connect: return fd 2048
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303030 0000
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=0
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=0 got=0
adb2.exe I 03-29 08:39:41 5852 9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:41 5852 9408 adb_client.cpp:124] _adb_connect: host:version
adb2.exe I 03-29 08:39:41 5852 9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:101] writex: fd=2048 len=16 30303063686f73743a76657273696f6e 000chost:version
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:41 5852 9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:41 5852 9408 adb_client.cpp:165] adb_connect: service shell:pm 'install' '/data/local/tmp/settings_apk-debug.apk'
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303034 0004
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303237 0027
adb2.exe I 03-29 08:39:41 5852 9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:41 5852 9408 adb_client.cpp:124] _adb_connect: shell:pm 'install' '/data/local/tmp/settings_apk-debug.apk'
adb2.exe I 03-29 08:39:41 5852 9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:101] writex: fd=2048 len=35 30303166686f73743a7472616e73706f 001fhost:transpo
adb2.exe I 03-29 08:39:41 5852 9408 adb_client.cpp:91] Switch transport in progress
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:41 5852 9408 adb_client.cpp:98] Switch transport success
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:101] writex: fd=2048 len=63 303033627368656c6c3a706d2027696e 003bshell:pm 'in
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:41 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:41 5852 9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:41 5852 9408 adb_client.cpp:245] adb_connect: return fd 2048
adb2.exe I 03-29 08:39:41 5852 9408 commandline.cpp:308] read_and_dump(): pre adb_read(fd=2048)
adb2.exe I 03-29 08:39:41 5852 9408 commandline.cpp:310] read_and_dump(): post adb_read(fd=2048): length=46
pkg: /data/local/tmp/settings_apk-debug.apk
adb2.exe I 03-29 08:39:41 5852 9408 commandline.cpp:308] read_and_dump(): pre adb_read(fd=2048)
adb2.exe I 03-29 08:39:42 5852 9408 commandline.cpp:310] read_and_dump(): post adb_read(fd=2048): length=9
Success
adb2.exe I 03-29 08:39:42 5852 9408 commandline.cpp:308] read_and_dump(): pre adb_read(fd=2048)
adb2.exe I 03-29 08:39:42 5852 9408 commandline.cpp:310] read_and_dump(): post adb_read(fd=2048): length=0
adb2.exe I 03-29 08:39:42 5852 9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:42 5852 9408 adb_client.cpp:271] adb_query: host-serial:IBAAWC7S5H5HSGNR:features
adb2.exe I 03-29 08:39:42 5852 9408 adb_client.cpp:124] _adb_connect: host:version
adb2.exe I 03-29 08:39:42 5852 9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:101] writex: fd=2048 len=16 30303063686f73743a76657273696f6e 000chost:version
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:42 5852 9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:42 5852 9408 adb_client.cpp:165] adb_connect: service host-serial:IBAAWC7S5H5HSGNR:features
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303034 0004
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303237 0027
adb2.exe I 03-29 08:39:42 5852 9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:42 5852 9408 adb_client.cpp:124] _adb_connect: host-serial:IBAAWC7S5H5HSGNR:features
adb2.exe I 03-29 08:39:42 5852 9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:101] writex: fd=2048 len=41 30303235686f73742d73657269616c3a 0025host-serial:
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:42 5852 9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:42 5852 9408 adb_client.cpp:245] adb_connect: return fd 2048
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303030 0000
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=0
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=0 got=0
adb2.exe I 03-29 08:39:42 5852 9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:42 5852 9408 adb_client.cpp:124] _adb_connect: host:version
adb2.exe I 03-29 08:39:42 5852 9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:101] writex: fd=2048 len=16 30303063686f73743a76657273696f6e 000chost:version
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:42 5852 9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:42 5852 9408 adb_client.cpp:165] adb_connect: service shell:rm -f '/data/local/tmp/settings_apk-debug.apk'
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303034 0004
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 30303237 0027
adb2.exe I 03-29 08:39:42 5852 9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
adb2.exe I 03-29 08:39:42 5852 9408 adb_client.cpp:124] _adb_connect: shell:rm -f '/data/local/tmp/settings_apk-debug.apk'
adb2.exe I 03-29 08:39:42 5852 9408 sysdeps_win32.cpp:745] port 5037 type tcp => fd 2048
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:101] writex: fd=2048 len=35 30303166686f73743a7472616e73706f 001fhost:transpo
adb2.exe I 03-29 08:39:42 5852 9408 adb_client.cpp:91] Switch transport in progress
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:42 5852 9408 adb_client.cpp:98] Switch transport success
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:101] writex: fd=2048 len=56 303033347368656c6c3a726d202d6620 0034shell:rm -f
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:75] readx: fd=2048 wanted=4
adb2.exe I 03-29 08:39:42 5852 9408 adb_io.cpp:91] readx: fd=2048 wanted=4 got=4 4f4b4159 OKAY
adb2.exe I 03-29 08:39:42 5852 9408 adb_client.cpp:157] _adb_connect: return fd 2048
adb2.exe I 03-29 08:39:42 5852 9408 adb_client.cpp:245] adb_connect: return fd 2048
adb2.exe I 03-29 08:39:42 5852 9408 commandline.cpp:308] read_and_dump(): pre adb_read(fd=2048)
adb2.exe I 03-29 08:39:42 5852 9408 commandline.cpp:310] read_and_dump(): post adb_read(fd=2048): length=0
adb2.exe I 03-29 08:39:42 5852 9408 sysdeps_win32.cpp:472] adb_close: 2048(lo-client:5037)
actually the commands do work as intended, but after the command finishes then the adb crashes, or so windows says "adb.exe has stopped working"
en...@google.com <en...@google.com> #26
a....@gmail.com <a....@gmail.com> #27
I downloaded the adb.exe debug version from #17 comment. Here are results:
for adb start-server
adb I 03-30 09:54:09 3760 9104 adb_trace.cpp:178] Android Debug Bridge version 1.0.39
adb I 03-30 09:54:09 3760 9104 adb_trace.cpp:178] Revision 47a91c209b6d-android
adb I 03-30 09:54:09 3760 9104 adb_trace.cpp:178]
adb I 03-30 09:54:09 3760 9104 adb_client.cpp:124] _adb_connect: host:version
adb I 03-30 09:54:10 3760 9104 sysdeps_win32.cpp:737] could not connect to tcp:5037: cannot connect to
o nie jest pod┼é─ůczone i (podczas wysy┼éania przez gniazdo datagramu przy u┼╝yciu wywo┼éania ÔÇ×wy┼Ťlij doÔÇŁ) nie podano adresu. (10057)
adb I 03-30 09:54:10 3760 9104 adb_client.cpp:165] adb_connect: service host:start-server
* daemon not running. starting it now at tcp:5037 *
adb I 03-30 09:54:10 4928 5472 adb_trace.cpp:178] Android Debug Bridge version 1.0.39
adb I 03-30 09:54:10 4928 5472 adb_trace.cpp:178] Revision 47a91c209b6d-android
adb I 03-30 09:54:10 4928 5472 adb_trace.cpp:178]
adb I 03-30 09:54:10 4928 5472 sysdeps_win32.cpp:822] port 0 type tcp => fd 2048
adb I 03-30 09:54:10 4928 5472 sysdeps_win32.cpp:1061] adb_socketpair: bound on port 62529
adb I 03-30 09:54:10 4928 5472 sysdeps_win32.cpp:745] port 62529 type tcp => fd 2049
adb I 03-30 09:54:10 4928 5472 sysdeps_win32.cpp:946] adb_socket_accept on fd 2048 returns fd 2050
adb I 03-30 09:54:10 4928 5472 sysdeps_win32.cpp:1086] adb_socketpair: peer sockaddr =
adb I 03-30 09:54:10 4928 5472 sysdeps_win32.cpp:1091] adb_socketpair: client sockaddr =
adb I 03-30 09:54:10 4928 5472 sysdeps_win32.cpp:1101] adb_socketpair: client and peer sockaddrs don't match
adb I 03-30 09:54:10 4928 5472 sysdeps_win32.cpp:472] adb_close: 2048(lo-server:0)
adb I 03-30 09:54:10 4928 5472 sysdeps_win32.cpp:472] adb_close: 2049(lo-client:62529)
adb I 03-30 09:54:10 4928 5472 sysdeps_win32.cpp:472] adb_close: 2050(accept:2048(lo-server:0))
error: cannot open transport registration socketpair: Input/output error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
could not read ok from ADB Server
* failed to start daemon *
error: cannot connect to daemon
The polish part is as follows:
"The request of sending or receiving data was blocked, because port/socket(?) is not connected and (in the event of sending datagram via port/socekt using command 'send to') the address was not given."
Mind that I translated it myself.
en...@google.com <en...@google.com> #28
an...@gmail.com <an...@gmail.com> #29
Could you please guide us when fix will be released?
We've faced with same problem with our Win7 machines.
--------------------------------------------------------------------------------
Output of adb from #17 post is:
adb I 04-10 15:24:25 5620 1424 adb_trace.cpp:178] Android Debug Bridge version
1.0.39
adb I 04-10 15:24:25 5620 1424 adb_trace.cpp:178] Revision 47a91c209b6d-androi
d
adb I 04-10 15:24:25 5620 1424 adb_trace.cpp:178]
adb I 04-10 15:24:25 5620 1424 adb_client.cpp:124] _adb_connect: host:version
adb I 04-10 15:24:26 5620 1424 sysdeps_win32.cpp:737] could not connect to tcp
:5037: cannot connect to
╨╕ ╨┐╨╛╨╗╤Г╤З╨╡╨╜╨╕╨╡ ╨┤╨░╨╜╨╜╤Л╤Е (when sending on a datagram socket using a s
endto call) no address was supplied. (10057)
adb I 04-10 15:24:26 5620 1424 adb_client.cpp:165] adb_connect: service host:s
tart-server
* daemon not running. starting it now at tcp:5037 *
adb I 04-10 15:24:26 6056 5044 adb_trace.cpp:178] Android Debug Bridge version
1.0.39
adb I 04-10 15:24:26 6056 5044 adb_trace.cpp:178] Revision 47a91c209b6d-androi
d
adb I 04-10 15:24:26 6056 5044 adb_trace.cpp:178]
adb I 04-10 15:24:26 6056 5044 sysdeps_win32.cpp:822] port 0 type tcp => fd 20
48
adb I 04-10 15:24:26 6056 5044 sysdeps_win32.cpp:1061] adb_socketpair: bound o
n port 64456
adb I 04-10 15:24:26 6056 5044 sysdeps_win32.cpp:745] port 64456 type tcp => f
d 2049
adb I 04-10 15:24:26 6056 5044 sysdeps_win32.cpp:946] adb_socket_accept on fd
2048 returns fd 2050
adb I 04-10 15:24:26 6056 5044 sysdeps_win32.cpp:1086] adb_socketpair: peer so
ckaddr =
adb I 04-10 15:24:26 6056 5044 sysdeps_win32.cpp:1091] adb_socketpair: client
sockaddr =
adb I 04-10 15:24:26 6056 5044 sysdeps_win32.cpp:1101] adb_socketpair: client
and peer sockaddrs don't match
adb I 04-10 15:24:26 6056 5044 sysdeps_win32.cpp:472] adb_close: 2048(lo-serve
r:0)
adb I 04-10 15:24:26 6056 5044 sysdeps_win32.cpp:472] adb_close: 2049(lo-clien
t:64456)
adb I 04-10 15:24:26 6056 5044 sysdeps_win32.cpp:472] adb_close: 2050(accept:2
048(lo-server:0))
error: cannot open transport registration socketpair: Input/output error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
could not read ok from ADB Server
* failed to start daemon *
error: cannot connect to daemon
en...@google.com <en...@google.com> #31
ap...@google.com <ap...@google.com> #32
Branch: sdk-release
commit a017eb19b2ca4d5dc8f3fbae22933ffd579ca739
Author: Josh Gao <jmgao@google.com>
Date: Wed Apr 19 11:32:40 2017
Update platform-tools version to 25.0.5.
Bug:
Bug:
Change-Id: I099f0cf9cde7f5fcefcf92420af3f716b5fd3773
M sdk/plat_tools_source.prop_template
gi...@gmail.com <gi...@gmail.com> #34
ss...@gmail.com <ss...@gmail.com> #35
aa...@gmail.com <aa...@gmail.com> #36
Feedback
ma...@gmail.com <ma...@gmail.com> #37
Sound good
so...@gmail.com <so...@gmail.com> #38
Good
zb...@gmail.com <zb...@gmail.com> #40
Фв
Description
I also downloaded the newest version (25.0.4) from android developers site, to check if it was an Android Studio update issue. The downloaded version crashed too.
All of our computers are using Windows 7 Professional x64 PL Service Pack 1.