I am new both as Android developer as posting a question in this forum.
It is my first Android project and I am getting a lot of warnnings with FD_SETSIZE issue when running my simple application throw emulator.
I guess the solution may be increase FD_SETSIZE but I didn't find where neither what exactly is the reason for such need.
My question was originally posted in https://stackoverflow.com/questions...e-descriptor-amount-raised-by-android-emulato and has some relationship with this question https://stackoverflow.com/questions...ntfor-error-fd-52396-above-fd-setsize-32768-b
Has anyone faced similar logs when emulating the app with Android Studio? Mine is the recent version 4.0.
31/05/2020
18:55 Emulator: Process finished with exit code 0
18:55 Executing tasks: [:app:assembleDebug] in project C:\WSs\FireStoreDemos\AppFirestore
18:55 Gradle build finished in 752 ms
18:55 Emulator: socketTcpLoopbackClientFor: error: fd 52380 above FD_SETSIZE (32768)
18:55 Emulator: socketTcpLoopbackClientFor: error: fd 52380 above FD_SETSIZE (32768)
18:55 Emulator: socketTcpLoopbackClientFor: error: fd 52396 above FD_SETSIZE (32768)
18:55 Emulator: socketTcpLoopbackClientFor: error: fd 52396 above FD_SETSIZE (32768)
18:55 Install successfully finished in 142 ms.: App restart successful without requiring a re-install.
The Virtual Device I am using
Name: Pixel_3a_API_28
CPU/ABI: Google Play Intel Atom (x86)
Path: C:\Users\Cast\.android\avd\Pixel_3a_API_28.avd
Target: google_apis_playstore [Google Play] (API level 28)
Skin: pixel_3a
SD Card: 512M
fastboot.chosenSnapshotFile:
runtime.network.speed: full
hw.accelerometer: yes
hw.device.name: pixel_3a
hw.lcd.width: 1080
hw.initialOrientation: Portrait
image.androidVersion.api: 28
tag.id: google_apis_playstore
hw.mainKeys: no
hw.camera.front: emulated
avd.ini.displayname: Pixel 3a API 28
hw.gpu.mode: auto
hw.ramSize: 1536
PlayStore.enabled: true
fastboot.forceColdBoot: no
hw.cpu.ncore: 4
hw.keyboard: yes
hw.sensors.proximity: yes
hw.dPad: no
hw.lcd.height: 2220
vm.heapSize: 256
skin.dynamic: yes
hw.device.manufacturer: Google
hw.gps: yes
hw.audioInput: yes
image.sysdir.1: system-images\android-28\google_apis_playstore\x86\
showDeviceFrame: yes
hw.camera.back: virtualscene
AvdId: Pixel_3a_API_28
hw.lcd.density: 440
hw.arc: false
hw.device.hash2: MD5:0e6953ebf01bdc6b33a2f54746629c50
fastboot.forceChosenSnapshotBoot: no
fastboot.forceFastBoot: yes
hw.trackBall: no
hw.battery: yes
hw.sdCard: yes
tag.display: Google Play
runtime.network.latency: none
disk.dataPartition.size: 6442450944
hw.sensors.orientation: yes
avd.ini.encoding: UTF-8
hw.gpu.enabled: yes
And finally, as far as I understand, all emulator ports:
C:\Users>netstat -ano | findstr "5037"
TCP 127.0.0.1:5037 0.0.0.0:0 LISTENING 7892
TCP 127.0.0.1:5037 127.0.0.1:49735 ESTABLISHED 7892
TCP 127.0.0.1:5037 127.0.0.1:51843 ESTABLISHED 7892
TCP 127.0.0.1:5037 127.0.0.1:51855 ESTABLISHED 7892
TCP 127.0.0.1:5037 127.0.0.1:51859 ESTABLISHED 7892
TCP 127.0.0.1:5037 127.0.0.1:51867 ESTABLISHED 7892
TCP 127.0.0.1:49735 127.0.0.1:5037 ESTABLISHED 9604
TCP 127.0.0.1:51843 127.0.0.1:5037 ESTABLISHED 13184
TCP 127.0.0.1:51855 127.0.0.1:5037 ESTABLISHED 9604
TCP 127.0.0.1:51859 127.0.0.1:5037 ESTABLISHED 9604
TCP 127.0.0.1:51867 127.0.0.1:5037 ESTABLISHED 9604
Honestly, I don't understand why so many ESTABLISHED connections related to port 5037 but I guess it is normal
It is my first Android project and I am getting a lot of warnnings with FD_SETSIZE issue when running my simple application throw emulator.
I guess the solution may be increase FD_SETSIZE but I didn't find where neither what exactly is the reason for such need.
My question was originally posted in https://stackoverflow.com/questions...e-descriptor-amount-raised-by-android-emulato and has some relationship with this question https://stackoverflow.com/questions...ntfor-error-fd-52396-above-fd-setsize-32768-b
Has anyone faced similar logs when emulating the app with Android Studio? Mine is the recent version 4.0.
31/05/2020
18:55 Emulator: Process finished with exit code 0
18:55 Executing tasks: [:app:assembleDebug] in project C:\WSs\FireStoreDemos\AppFirestore
18:55 Gradle build finished in 752 ms
18:55 Emulator: socketTcpLoopbackClientFor: error: fd 52380 above FD_SETSIZE (32768)
18:55 Emulator: socketTcpLoopbackClientFor: error: fd 52380 above FD_SETSIZE (32768)
18:55 Emulator: socketTcpLoopbackClientFor: error: fd 52396 above FD_SETSIZE (32768)
18:55 Emulator: socketTcpLoopbackClientFor: error: fd 52396 above FD_SETSIZE (32768)
18:55 Install successfully finished in 142 ms.: App restart successful without requiring a re-install.
The Virtual Device I am using
Name: Pixel_3a_API_28
CPU/ABI: Google Play Intel Atom (x86)
Path: C:\Users\Cast\.android\avd\Pixel_3a_API_28.avd
Target: google_apis_playstore [Google Play] (API level 28)
Skin: pixel_3a
SD Card: 512M
fastboot.chosenSnapshotFile:
runtime.network.speed: full
hw.accelerometer: yes
hw.device.name: pixel_3a
hw.lcd.width: 1080
hw.initialOrientation: Portrait
image.androidVersion.api: 28
tag.id: google_apis_playstore
hw.mainKeys: no
hw.camera.front: emulated
avd.ini.displayname: Pixel 3a API 28
hw.gpu.mode: auto
hw.ramSize: 1536
PlayStore.enabled: true
fastboot.forceColdBoot: no
hw.cpu.ncore: 4
hw.keyboard: yes
hw.sensors.proximity: yes
hw.dPad: no
hw.lcd.height: 2220
vm.heapSize: 256
skin.dynamic: yes
hw.device.manufacturer: Google
hw.gps: yes
hw.audioInput: yes
image.sysdir.1: system-images\android-28\google_apis_playstore\x86\
showDeviceFrame: yes
hw.camera.back: virtualscene
AvdId: Pixel_3a_API_28
hw.lcd.density: 440
hw.arc: false
hw.device.hash2: MD5:0e6953ebf01bdc6b33a2f54746629c50
fastboot.forceChosenSnapshotBoot: no
fastboot.forceFastBoot: yes
hw.trackBall: no
hw.battery: yes
hw.sdCard: yes
tag.display: Google Play
runtime.network.latency: none
disk.dataPartition.size: 6442450944
hw.sensors.orientation: yes
avd.ini.encoding: UTF-8
hw.gpu.enabled: yes
And finally, as far as I understand, all emulator ports:
C:\Users>netstat -ano | findstr "5037"
TCP 127.0.0.1:5037 0.0.0.0:0 LISTENING 7892
TCP 127.0.0.1:5037 127.0.0.1:49735 ESTABLISHED 7892
TCP 127.0.0.1:5037 127.0.0.1:51843 ESTABLISHED 7892
TCP 127.0.0.1:5037 127.0.0.1:51855 ESTABLISHED 7892
TCP 127.0.0.1:5037 127.0.0.1:51859 ESTABLISHED 7892
TCP 127.0.0.1:5037 127.0.0.1:51867 ESTABLISHED 7892
TCP 127.0.0.1:49735 127.0.0.1:5037 ESTABLISHED 9604
TCP 127.0.0.1:51843 127.0.0.1:5037 ESTABLISHED 13184
TCP 127.0.0.1:51855 127.0.0.1:5037 ESTABLISHED 9604
TCP 127.0.0.1:51859 127.0.0.1:5037 ESTABLISHED 9604
TCP 127.0.0.1:51867 127.0.0.1:5037 ESTABLISHED 9604
Honestly, I don't understand why so many ESTABLISHED connections related to port 5037 but I guess it is normal