adb can't detect Genymotion device
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I create an Android device in Genymotion : Custom Phone Android 4.4-API 19, and the device run well.
But when I try 'adb devices , it is empty below 'List of devices attached'
enter image description here
'Use custom Android SDK tools' is already set
enter image description here
the device's Developer Options and USB debugging is enabled.
I have tried
- adb kill-server adb start-server adb devices
but the adb still can not detect the Genymotion device.
virtualbox as follow
enter image description here
Runing on Ubuntu 16.04 LTS
Does anybody has the same problem ? Please help, many thanks!
virtualbox android adb genymotion
add a comment |
I create an Android device in Genymotion : Custom Phone Android 4.4-API 19, and the device run well.
But when I try 'adb devices , it is empty below 'List of devices attached'
enter image description here
'Use custom Android SDK tools' is already set
enter image description here
the device's Developer Options and USB debugging is enabled.
I have tried
- adb kill-server adb start-server adb devices
but the adb still can not detect the Genymotion device.
virtualbox as follow
enter image description here
Runing on Ubuntu 16.04 LTS
Does anybody has the same problem ? Please help, many thanks!
virtualbox android adb genymotion
add a comment |
I create an Android device in Genymotion : Custom Phone Android 4.4-API 19, and the device run well.
But when I try 'adb devices , it is empty below 'List of devices attached'
enter image description here
'Use custom Android SDK tools' is already set
enter image description here
the device's Developer Options and USB debugging is enabled.
I have tried
- adb kill-server adb start-server adb devices
but the adb still can not detect the Genymotion device.
virtualbox as follow
enter image description here
Runing on Ubuntu 16.04 LTS
Does anybody has the same problem ? Please help, many thanks!
virtualbox android adb genymotion
I create an Android device in Genymotion : Custom Phone Android 4.4-API 19, and the device run well.
But when I try 'adb devices , it is empty below 'List of devices attached'
enter image description here
'Use custom Android SDK tools' is already set
enter image description here
the device's Developer Options and USB debugging is enabled.
I have tried
- adb kill-server adb start-server adb devices
but the adb still can not detect the Genymotion device.
virtualbox as follow
enter image description here
Runing on Ubuntu 16.04 LTS
Does anybody has the same problem ? Please help, many thanks!
virtualbox android adb genymotion
virtualbox android adb genymotion
edited Apr 3 at 10:19
luckin
asked Apr 3 at 8:37
luckinluckin
12
12
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I found this answer to be helpful for a similar situation. I'm not really sure what the underlying bug is (either in adb or Genymotion), but until it gets fixed this is a suitable workaround. Essentially you're explicitly pointing adb to the device with adb connect ...
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1130840%2fadb-cant-detect-genymotion-device%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I found this answer to be helpful for a similar situation. I'm not really sure what the underlying bug is (either in adb or Genymotion), but until it gets fixed this is a suitable workaround. Essentially you're explicitly pointing adb to the device with adb connect ...
add a comment |
I found this answer to be helpful for a similar situation. I'm not really sure what the underlying bug is (either in adb or Genymotion), but until it gets fixed this is a suitable workaround. Essentially you're explicitly pointing adb to the device with adb connect ...
add a comment |
I found this answer to be helpful for a similar situation. I'm not really sure what the underlying bug is (either in adb or Genymotion), but until it gets fixed this is a suitable workaround. Essentially you're explicitly pointing adb to the device with adb connect ...
I found this answer to be helpful for a similar situation. I'm not really sure what the underlying bug is (either in adb or Genymotion), but until it gets fixed this is a suitable workaround. Essentially you're explicitly pointing adb to the device with adb connect ...
answered Apr 8 at 23:10
SoutherneerSoutherneer
1013
1013
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1130840%2fadb-cant-detect-genymotion-device%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown