appium-device-farm: Bluetooth_manager not started

Hello,

im trying to get this plugin to work using Genymotion emulators. The image im using is genymotion-ami-8-1-v13-1. I have a set of scripts that establishes a connection to the emulators, then checks if the init and boot has completed.

After that, the Appium server starts and log says it has connected devices. However there are no devices visible in the device-farm web service. So I checked the logs: image

I tried all the commands separately, turns out the Bluetooth service is the issue: Can't find service: bluetooth_manager. So I wrote a script that while loops to check if the Bluetooth service is running, and if not it uses adb -s "$device" shell dumpsys bluetooth_manager to try to get it running before Appium starts.

However this was unsucessful, even with a timeout of 5 min I cant get it to run. Are there any alternatives to this command?: adb -s "$device" shell dumpsys bluetooth_manager | grep name: | cut -c9- . Is it possible to make this non-mandatory?

Edit: Why not use adb shell getprop ro.product.name instead?

About this issue

  • Original URL
  • State: closed
  • Created 8 months ago
  • Comments: 17 (17 by maintainers)

Commits related to this issue

Most upvoted comments

@ValzRon Sorry too many things in this thread! Is something still blocking you using the plugin with genymotion ??

You need to create a fork and the create a PR

@saikrishna321 So here are some examples to use: From a locally started Emulator in Android Studio:

[ro.serialno]: [EMULATOR31X2X9X0]
[ro.setupwizard.mode]: [EMULATOR]
[ro.product.name]: [sdk_gphone_x86]

And this: adb -s emulator-5554 shell dumpsys bluetooth_manager | grep name: | cut -c9- Returns the error Can't find service: bluetooth_manager I will try it with Genymotion aswell