What is the reason for the error “Device supports x86, but APK only supports armeabi-v7a”
I am playing around with Android Studio by testing some projects out from GitHub and when I try to emulate the apk, it does not let me choose an emulator.
It tells me:
Device supports x86, but APK only supports armeabi-v7a
Why does it do this?
android android-studio
|
show 4 more comments
I am playing around with Android Studio by testing some projects out from GitHub and when I try to emulate the apk, it does not let me choose an emulator.
It tells me:
Device supports x86, but APK only supports armeabi-v7a
Why does it do this?
android android-studio
What AVD did you use? What System Image? What GitHub project?
– cricket_007
Jan 21 '17 at 5:23
In other words, the Intel x86 images aren't going to run ARM code.
– cricket_007
Jan 21 '17 at 5:25
github.com/jreyes/mirror
– Alexander Ibarra
Jan 21 '17 at 5:31
I wanted to use a Nexus 10 running android 5.1
– Alexander Ibarra
Jan 21 '17 at 5:32
Okay, and did you use the ARM eabi v7 system image or an Intel Atom x86 image? Check your SDK manager what you have installed.
– cricket_007
Jan 21 '17 at 5:34
|
show 4 more comments
I am playing around with Android Studio by testing some projects out from GitHub and when I try to emulate the apk, it does not let me choose an emulator.
It tells me:
Device supports x86, but APK only supports armeabi-v7a
Why does it do this?
android android-studio
I am playing around with Android Studio by testing some projects out from GitHub and when I try to emulate the apk, it does not let me choose an emulator.
It tells me:
Device supports x86, but APK only supports armeabi-v7a
Why does it do this?
android android-studio
android android-studio
edited Jun 6 '17 at 22:37
halfer
14.6k758113
14.6k758113
asked Jan 21 '17 at 5:17
Alexander IbarraAlexander Ibarra
3631310
3631310
What AVD did you use? What System Image? What GitHub project?
– cricket_007
Jan 21 '17 at 5:23
In other words, the Intel x86 images aren't going to run ARM code.
– cricket_007
Jan 21 '17 at 5:25
github.com/jreyes/mirror
– Alexander Ibarra
Jan 21 '17 at 5:31
I wanted to use a Nexus 10 running android 5.1
– Alexander Ibarra
Jan 21 '17 at 5:32
Okay, and did you use the ARM eabi v7 system image or an Intel Atom x86 image? Check your SDK manager what you have installed.
– cricket_007
Jan 21 '17 at 5:34
|
show 4 more comments
What AVD did you use? What System Image? What GitHub project?
– cricket_007
Jan 21 '17 at 5:23
In other words, the Intel x86 images aren't going to run ARM code.
– cricket_007
Jan 21 '17 at 5:25
github.com/jreyes/mirror
– Alexander Ibarra
Jan 21 '17 at 5:31
I wanted to use a Nexus 10 running android 5.1
– Alexander Ibarra
Jan 21 '17 at 5:32
Okay, and did you use the ARM eabi v7 system image or an Intel Atom x86 image? Check your SDK manager what you have installed.
– cricket_007
Jan 21 '17 at 5:34
What AVD did you use? What System Image? What GitHub project?
– cricket_007
Jan 21 '17 at 5:23
What AVD did you use? What System Image? What GitHub project?
– cricket_007
Jan 21 '17 at 5:23
In other words, the Intel x86 images aren't going to run ARM code.
– cricket_007
Jan 21 '17 at 5:25
In other words, the Intel x86 images aren't going to run ARM code.
– cricket_007
Jan 21 '17 at 5:25
github.com/jreyes/mirror
– Alexander Ibarra
Jan 21 '17 at 5:31
github.com/jreyes/mirror
– Alexander Ibarra
Jan 21 '17 at 5:31
I wanted to use a Nexus 10 running android 5.1
– Alexander Ibarra
Jan 21 '17 at 5:32
I wanted to use a Nexus 10 running android 5.1
– Alexander Ibarra
Jan 21 '17 at 5:32
Okay, and did you use the ARM eabi v7 system image or an Intel Atom x86 image? Check your SDK manager what you have installed.
– cricket_007
Jan 21 '17 at 5:34
Okay, and did you use the ARM eabi v7 system image or an Intel Atom x86 image? Check your SDK manager what you have installed.
– cricket_007
Jan 21 '17 at 5:34
|
show 4 more comments
20 Answers
20
active
oldest
votes
I had the same problem, I checkout the build.gradle from module:app. It turns out that there's a such config:
ndk {
abiFilters "armeabi-v7a", "x86"
}
when I commented all out, everything worked fine.
I was trying to deal with the React Native Android project.
1
I think you meant build.gradle ;)
– Ryan Pfister
Mar 31 '17 at 17:50
1
@RyanPfister you're right
– Bruce Lee
Apr 1 '17 at 10:38
2
I had the same problem and for me "x86" was just missing there
– thomas
Jun 6 '17 at 8:51
1
This worked for me - however all I had to do was allow debug on my actual device and I could uncomment this line again.
– Boomer Rogers
May 7 '18 at 21:51
Restarting device solved problem for me
– O. Borcuhin
Feb 11 at 5:18
add a comment |
Turn off USB debugging and turn it back on the hardware device.
5
Those comments I would normally downvote, but actually, it works!
– Ahmed Hegazy
Jul 26 '18 at 14:00
Wow, really it works!
– kientux
Aug 8 '18 at 7:51
It did work, perfect. Thanks
– Ayoub
Oct 8 '18 at 7:34
add a comment |
In Android Studio, select the Build menu,
then click Select Build Variant... and in 'Build Variants' window select x86Debug(or release)
PS: Im using Android Studio 2.3 on Mac
Saved me !!! Thanks
– Jay Thakkar
Jul 28 '17 at 11:25
This worked perfectly - my gradle setup defined both ARM and x86 builds, but I had to instruct Android Studio to build the x86 variant as opposed to the ARM variant (likely for iOS). Thanks!
– jevon
Aug 1 '18 at 5:09
thanks, its work for me.
– MD.Riyaz
Aug 13 '18 at 20:50
add a comment |
On Linux:
File > Invalidate Cache / Restart
On phone:
Instead Charge this device change to Transfer photos (PTP)
1
None of the above answers were working. This worked. Thanks a lot.
– thedarkpassenger
Aug 21 '18 at 9:27
add a comment |
Device supports x86, but APK only supports armeabi-v7a)
Sounds like you used an x86
image in the emulator.
Create a separate one. Choose "other images" tab to find arm devices, if you have to.
Or, run on an actual device. The repo you listed is meant to run on a Raspberry Pi 3 / ODroid, I think.
add a comment |
I had the similar issue and I've resolved it by adding "x86" value to the "abiFilters" list like below -
[Open build.gradle(Module: app) file ]
and search for "ndk" in deafultSection and add "x86" to it!
ndk {
abiFilters "armeabi", "armeabi-v7a", "x86"
}
Hope it helps!!!
You should probably droparmeabi
if you're targeting SDK 19 and above. Android itself doesn't support it starting 4.4
– mradzinski
Mar 17 '18 at 21:04
add a comment |
In my case of Linux machine adb devices
showed
List of devices attached
44b194f5 no permissions
Then restarted the adb server
sudo adb kill-server
and then
sudo adb start-server
then connect your device turn Debugging on and type
adb devices
List of devices attached
44b194f5 device
Finally was able to run on the device
add a comment |
Can confirm, toggling USB debugging off/on in Developer Options resolved the issue. Maybe even cancel the "Select Deployment Target" window in Android Studio and try to run the app again after toggling USB debugging.
add a comment |
Just go to device Settings >> Developer Options >> Restore Default Settings
then enable USB debugging
add a comment |
In my case my app use some native libraries. Each platform requires the corresponding libs to be built.
So the native lib of x86(or any other) platform is not generated.You must have add an abifilter somewhere:
There are several places where abi filters can be specified:
Application.mk
add the platform you need like this:
APP_ABI := armeabi armeabi-v7a x86
build.gradle
find abiFilters, and add platform you need like this:
abiFilters "armeabi","armeabi-v7a","x86"
add a comment |
On my physical device, I started getting this. The fix was to go into Developer Settings and turn off and on USB debugging.
add a comment |
For me it worked my changing the cable option from
-> Charge Only.
To
-> Transfer file.
add a comment |
adb kill-server
adb start-server
Its working for me on windows OS.
add a comment |
If you use Ubuntu:
- make sure that usb debugging is ON
- check your cable connection
- on notification bar check android system notification and touch it for change charging state to file transfer
- now go terminal and type:
adb devices
after run this command adb restart and your device show in list
add a comment |
Test your code on real phone. If you have still same issue,then import your code again and before this you should update your SDK and create a new emulator with ARM system image.
add a comment |
Many times this means that you have not granted your laptop/computer access to your device. Take a look at your device and click the "Allow Access" button as well as the debugging permissions.
add a comment |
Running an AVD using the x86 processor is 10x faster than using the ARM emulator, but most of the time you are only compiling your APK for ARM. To have faster emulation runs using an x86 AVD I had to do the following (for a Cocos2d-x project):
app/jni/Android.mk
APP_ABI := armeabi-v7a:x86
gradle.properties
PROP_APP_ABI=armeabi-v7a:x86
app/build.gradle
android {
...
defaultConfig {
...
ndk {
abiFilters =
abiFilters.addAll(PROP_APP_ABI.split(':').collect{it as String})
}
}
}
add a comment |
Restarting device solved problem for me (React-native)
add a comment |
You need to reconnect your device and try to turn off/on the developer options.
See Enable developer options and debugging
add a comment |
It happened to me to after updating the Android Studio. In my case, it happened because of the build setting is not automatically configured into x86Debug-x86.
Just change it by opening Build>>Select Build Variant>> Change the build variant option from armeabi-v7a into x86Debug-x86 or whatever you need in the emulator.
New contributor
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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%2fstackoverflow.com%2fquestions%2f41775988%2fwhat-is-the-reason-for-the-error-device-supports-x86-but-apk-only-supports-arm%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
20 Answers
20
active
oldest
votes
20 Answers
20
active
oldest
votes
active
oldest
votes
active
oldest
votes
I had the same problem, I checkout the build.gradle from module:app. It turns out that there's a such config:
ndk {
abiFilters "armeabi-v7a", "x86"
}
when I commented all out, everything worked fine.
I was trying to deal with the React Native Android project.
1
I think you meant build.gradle ;)
– Ryan Pfister
Mar 31 '17 at 17:50
1
@RyanPfister you're right
– Bruce Lee
Apr 1 '17 at 10:38
2
I had the same problem and for me "x86" was just missing there
– thomas
Jun 6 '17 at 8:51
1
This worked for me - however all I had to do was allow debug on my actual device and I could uncomment this line again.
– Boomer Rogers
May 7 '18 at 21:51
Restarting device solved problem for me
– O. Borcuhin
Feb 11 at 5:18
add a comment |
I had the same problem, I checkout the build.gradle from module:app. It turns out that there's a such config:
ndk {
abiFilters "armeabi-v7a", "x86"
}
when I commented all out, everything worked fine.
I was trying to deal with the React Native Android project.
1
I think you meant build.gradle ;)
– Ryan Pfister
Mar 31 '17 at 17:50
1
@RyanPfister you're right
– Bruce Lee
Apr 1 '17 at 10:38
2
I had the same problem and for me "x86" was just missing there
– thomas
Jun 6 '17 at 8:51
1
This worked for me - however all I had to do was allow debug on my actual device and I could uncomment this line again.
– Boomer Rogers
May 7 '18 at 21:51
Restarting device solved problem for me
– O. Borcuhin
Feb 11 at 5:18
add a comment |
I had the same problem, I checkout the build.gradle from module:app. It turns out that there's a such config:
ndk {
abiFilters "armeabi-v7a", "x86"
}
when I commented all out, everything worked fine.
I was trying to deal with the React Native Android project.
I had the same problem, I checkout the build.gradle from module:app. It turns out that there's a such config:
ndk {
abiFilters "armeabi-v7a", "x86"
}
when I commented all out, everything worked fine.
I was trying to deal with the React Native Android project.
edited Oct 14 '17 at 11:36
ishandutta2007
4,78164260
4,78164260
answered Mar 4 '17 at 3:08
Bruce LeeBruce Lee
1,9841823
1,9841823
1
I think you meant build.gradle ;)
– Ryan Pfister
Mar 31 '17 at 17:50
1
@RyanPfister you're right
– Bruce Lee
Apr 1 '17 at 10:38
2
I had the same problem and for me "x86" was just missing there
– thomas
Jun 6 '17 at 8:51
1
This worked for me - however all I had to do was allow debug on my actual device and I could uncomment this line again.
– Boomer Rogers
May 7 '18 at 21:51
Restarting device solved problem for me
– O. Borcuhin
Feb 11 at 5:18
add a comment |
1
I think you meant build.gradle ;)
– Ryan Pfister
Mar 31 '17 at 17:50
1
@RyanPfister you're right
– Bruce Lee
Apr 1 '17 at 10:38
2
I had the same problem and for me "x86" was just missing there
– thomas
Jun 6 '17 at 8:51
1
This worked for me - however all I had to do was allow debug on my actual device and I could uncomment this line again.
– Boomer Rogers
May 7 '18 at 21:51
Restarting device solved problem for me
– O. Borcuhin
Feb 11 at 5:18
1
1
I think you meant build.gradle ;)
– Ryan Pfister
Mar 31 '17 at 17:50
I think you meant build.gradle ;)
– Ryan Pfister
Mar 31 '17 at 17:50
1
1
@RyanPfister you're right
– Bruce Lee
Apr 1 '17 at 10:38
@RyanPfister you're right
– Bruce Lee
Apr 1 '17 at 10:38
2
2
I had the same problem and for me "x86" was just missing there
– thomas
Jun 6 '17 at 8:51
I had the same problem and for me "x86" was just missing there
– thomas
Jun 6 '17 at 8:51
1
1
This worked for me - however all I had to do was allow debug on my actual device and I could uncomment this line again.
– Boomer Rogers
May 7 '18 at 21:51
This worked for me - however all I had to do was allow debug on my actual device and I could uncomment this line again.
– Boomer Rogers
May 7 '18 at 21:51
Restarting device solved problem for me
– O. Borcuhin
Feb 11 at 5:18
Restarting device solved problem for me
– O. Borcuhin
Feb 11 at 5:18
add a comment |
Turn off USB debugging and turn it back on the hardware device.
5
Those comments I would normally downvote, but actually, it works!
– Ahmed Hegazy
Jul 26 '18 at 14:00
Wow, really it works!
– kientux
Aug 8 '18 at 7:51
It did work, perfect. Thanks
– Ayoub
Oct 8 '18 at 7:34
add a comment |
Turn off USB debugging and turn it back on the hardware device.
5
Those comments I would normally downvote, but actually, it works!
– Ahmed Hegazy
Jul 26 '18 at 14:00
Wow, really it works!
– kientux
Aug 8 '18 at 7:51
It did work, perfect. Thanks
– Ayoub
Oct 8 '18 at 7:34
add a comment |
Turn off USB debugging and turn it back on the hardware device.
Turn off USB debugging and turn it back on the hardware device.
answered Mar 8 '18 at 22:31
user3157940user3157940
685711
685711
5
Those comments I would normally downvote, but actually, it works!
– Ahmed Hegazy
Jul 26 '18 at 14:00
Wow, really it works!
– kientux
Aug 8 '18 at 7:51
It did work, perfect. Thanks
– Ayoub
Oct 8 '18 at 7:34
add a comment |
5
Those comments I would normally downvote, but actually, it works!
– Ahmed Hegazy
Jul 26 '18 at 14:00
Wow, really it works!
– kientux
Aug 8 '18 at 7:51
It did work, perfect. Thanks
– Ayoub
Oct 8 '18 at 7:34
5
5
Those comments I would normally downvote, but actually, it works!
– Ahmed Hegazy
Jul 26 '18 at 14:00
Those comments I would normally downvote, but actually, it works!
– Ahmed Hegazy
Jul 26 '18 at 14:00
Wow, really it works!
– kientux
Aug 8 '18 at 7:51
Wow, really it works!
– kientux
Aug 8 '18 at 7:51
It did work, perfect. Thanks
– Ayoub
Oct 8 '18 at 7:34
It did work, perfect. Thanks
– Ayoub
Oct 8 '18 at 7:34
add a comment |
In Android Studio, select the Build menu,
then click Select Build Variant... and in 'Build Variants' window select x86Debug(or release)
PS: Im using Android Studio 2.3 on Mac
Saved me !!! Thanks
– Jay Thakkar
Jul 28 '17 at 11:25
This worked perfectly - my gradle setup defined both ARM and x86 builds, but I had to instruct Android Studio to build the x86 variant as opposed to the ARM variant (likely for iOS). Thanks!
– jevon
Aug 1 '18 at 5:09
thanks, its work for me.
– MD.Riyaz
Aug 13 '18 at 20:50
add a comment |
In Android Studio, select the Build menu,
then click Select Build Variant... and in 'Build Variants' window select x86Debug(or release)
PS: Im using Android Studio 2.3 on Mac
Saved me !!! Thanks
– Jay Thakkar
Jul 28 '17 at 11:25
This worked perfectly - my gradle setup defined both ARM and x86 builds, but I had to instruct Android Studio to build the x86 variant as opposed to the ARM variant (likely for iOS). Thanks!
– jevon
Aug 1 '18 at 5:09
thanks, its work for me.
– MD.Riyaz
Aug 13 '18 at 20:50
add a comment |
In Android Studio, select the Build menu,
then click Select Build Variant... and in 'Build Variants' window select x86Debug(or release)
PS: Im using Android Studio 2.3 on Mac
In Android Studio, select the Build menu,
then click Select Build Variant... and in 'Build Variants' window select x86Debug(or release)
PS: Im using Android Studio 2.3 on Mac
answered May 2 '17 at 15:46
rafahororafahoro
871917
871917
Saved me !!! Thanks
– Jay Thakkar
Jul 28 '17 at 11:25
This worked perfectly - my gradle setup defined both ARM and x86 builds, but I had to instruct Android Studio to build the x86 variant as opposed to the ARM variant (likely for iOS). Thanks!
– jevon
Aug 1 '18 at 5:09
thanks, its work for me.
– MD.Riyaz
Aug 13 '18 at 20:50
add a comment |
Saved me !!! Thanks
– Jay Thakkar
Jul 28 '17 at 11:25
This worked perfectly - my gradle setup defined both ARM and x86 builds, but I had to instruct Android Studio to build the x86 variant as opposed to the ARM variant (likely for iOS). Thanks!
– jevon
Aug 1 '18 at 5:09
thanks, its work for me.
– MD.Riyaz
Aug 13 '18 at 20:50
Saved me !!! Thanks
– Jay Thakkar
Jul 28 '17 at 11:25
Saved me !!! Thanks
– Jay Thakkar
Jul 28 '17 at 11:25
This worked perfectly - my gradle setup defined both ARM and x86 builds, but I had to instruct Android Studio to build the x86 variant as opposed to the ARM variant (likely for iOS). Thanks!
– jevon
Aug 1 '18 at 5:09
This worked perfectly - my gradle setup defined both ARM and x86 builds, but I had to instruct Android Studio to build the x86 variant as opposed to the ARM variant (likely for iOS). Thanks!
– jevon
Aug 1 '18 at 5:09
thanks, its work for me.
– MD.Riyaz
Aug 13 '18 at 20:50
thanks, its work for me.
– MD.Riyaz
Aug 13 '18 at 20:50
add a comment |
On Linux:
File > Invalidate Cache / Restart
On phone:
Instead Charge this device change to Transfer photos (PTP)
1
None of the above answers were working. This worked. Thanks a lot.
– thedarkpassenger
Aug 21 '18 at 9:27
add a comment |
On Linux:
File > Invalidate Cache / Restart
On phone:
Instead Charge this device change to Transfer photos (PTP)
1
None of the above answers were working. This worked. Thanks a lot.
– thedarkpassenger
Aug 21 '18 at 9:27
add a comment |
On Linux:
File > Invalidate Cache / Restart
On phone:
Instead Charge this device change to Transfer photos (PTP)
On Linux:
File > Invalidate Cache / Restart
On phone:
Instead Charge this device change to Transfer photos (PTP)
answered Apr 20 '17 at 11:56
JRdevJRdev
12313
12313
1
None of the above answers were working. This worked. Thanks a lot.
– thedarkpassenger
Aug 21 '18 at 9:27
add a comment |
1
None of the above answers were working. This worked. Thanks a lot.
– thedarkpassenger
Aug 21 '18 at 9:27
1
1
None of the above answers were working. This worked. Thanks a lot.
– thedarkpassenger
Aug 21 '18 at 9:27
None of the above answers were working. This worked. Thanks a lot.
– thedarkpassenger
Aug 21 '18 at 9:27
add a comment |
Device supports x86, but APK only supports armeabi-v7a)
Sounds like you used an x86
image in the emulator.
Create a separate one. Choose "other images" tab to find arm devices, if you have to.
Or, run on an actual device. The repo you listed is meant to run on a Raspberry Pi 3 / ODroid, I think.
add a comment |
Device supports x86, but APK only supports armeabi-v7a)
Sounds like you used an x86
image in the emulator.
Create a separate one. Choose "other images" tab to find arm devices, if you have to.
Or, run on an actual device. The repo you listed is meant to run on a Raspberry Pi 3 / ODroid, I think.
add a comment |
Device supports x86, but APK only supports armeabi-v7a)
Sounds like you used an x86
image in the emulator.
Create a separate one. Choose "other images" tab to find arm devices, if you have to.
Or, run on an actual device. The repo you listed is meant to run on a Raspberry Pi 3 / ODroid, I think.
Device supports x86, but APK only supports armeabi-v7a)
Sounds like you used an x86
image in the emulator.
Create a separate one. Choose "other images" tab to find arm devices, if you have to.
Or, run on an actual device. The repo you listed is meant to run on a Raspberry Pi 3 / ODroid, I think.
answered Jan 21 '17 at 5:39
cricket_007cricket_007
82.6k1144112
82.6k1144112
add a comment |
add a comment |
I had the similar issue and I've resolved it by adding "x86" value to the "abiFilters" list like below -
[Open build.gradle(Module: app) file ]
and search for "ndk" in deafultSection and add "x86" to it!
ndk {
abiFilters "armeabi", "armeabi-v7a", "x86"
}
Hope it helps!!!
You should probably droparmeabi
if you're targeting SDK 19 and above. Android itself doesn't support it starting 4.4
– mradzinski
Mar 17 '18 at 21:04
add a comment |
I had the similar issue and I've resolved it by adding "x86" value to the "abiFilters" list like below -
[Open build.gradle(Module: app) file ]
and search for "ndk" in deafultSection and add "x86" to it!
ndk {
abiFilters "armeabi", "armeabi-v7a", "x86"
}
Hope it helps!!!
You should probably droparmeabi
if you're targeting SDK 19 and above. Android itself doesn't support it starting 4.4
– mradzinski
Mar 17 '18 at 21:04
add a comment |
I had the similar issue and I've resolved it by adding "x86" value to the "abiFilters" list like below -
[Open build.gradle(Module: app) file ]
and search for "ndk" in deafultSection and add "x86" to it!
ndk {
abiFilters "armeabi", "armeabi-v7a", "x86"
}
Hope it helps!!!
I had the similar issue and I've resolved it by adding "x86" value to the "abiFilters" list like below -
[Open build.gradle(Module: app) file ]
and search for "ndk" in deafultSection and add "x86" to it!
ndk {
abiFilters "armeabi", "armeabi-v7a", "x86"
}
Hope it helps!!!
answered Jun 28 '17 at 17:44
Roopesh ReddyRoopesh Reddy
566167
566167
You should probably droparmeabi
if you're targeting SDK 19 and above. Android itself doesn't support it starting 4.4
– mradzinski
Mar 17 '18 at 21:04
add a comment |
You should probably droparmeabi
if you're targeting SDK 19 and above. Android itself doesn't support it starting 4.4
– mradzinski
Mar 17 '18 at 21:04
You should probably drop
armeabi
if you're targeting SDK 19 and above. Android itself doesn't support it starting 4.4– mradzinski
Mar 17 '18 at 21:04
You should probably drop
armeabi
if you're targeting SDK 19 and above. Android itself doesn't support it starting 4.4– mradzinski
Mar 17 '18 at 21:04
add a comment |
In my case of Linux machine adb devices
showed
List of devices attached
44b194f5 no permissions
Then restarted the adb server
sudo adb kill-server
and then
sudo adb start-server
then connect your device turn Debugging on and type
adb devices
List of devices attached
44b194f5 device
Finally was able to run on the device
add a comment |
In my case of Linux machine adb devices
showed
List of devices attached
44b194f5 no permissions
Then restarted the adb server
sudo adb kill-server
and then
sudo adb start-server
then connect your device turn Debugging on and type
adb devices
List of devices attached
44b194f5 device
Finally was able to run on the device
add a comment |
In my case of Linux machine adb devices
showed
List of devices attached
44b194f5 no permissions
Then restarted the adb server
sudo adb kill-server
and then
sudo adb start-server
then connect your device turn Debugging on and type
adb devices
List of devices attached
44b194f5 device
Finally was able to run on the device
In my case of Linux machine adb devices
showed
List of devices attached
44b194f5 no permissions
Then restarted the adb server
sudo adb kill-server
and then
sudo adb start-server
then connect your device turn Debugging on and type
adb devices
List of devices attached
44b194f5 device
Finally was able to run on the device
answered Nov 15 '18 at 7:32
Sachin KSachin K
385816
385816
add a comment |
add a comment |
Can confirm, toggling USB debugging off/on in Developer Options resolved the issue. Maybe even cancel the "Select Deployment Target" window in Android Studio and try to run the app again after toggling USB debugging.
add a comment |
Can confirm, toggling USB debugging off/on in Developer Options resolved the issue. Maybe even cancel the "Select Deployment Target" window in Android Studio and try to run the app again after toggling USB debugging.
add a comment |
Can confirm, toggling USB debugging off/on in Developer Options resolved the issue. Maybe even cancel the "Select Deployment Target" window in Android Studio and try to run the app again after toggling USB debugging.
Can confirm, toggling USB debugging off/on in Developer Options resolved the issue. Maybe even cancel the "Select Deployment Target" window in Android Studio and try to run the app again after toggling USB debugging.
answered May 1 '18 at 20:53
Val GeyvandovVal Geyvandov
8514
8514
add a comment |
add a comment |
Just go to device Settings >> Developer Options >> Restore Default Settings
then enable USB debugging
add a comment |
Just go to device Settings >> Developer Options >> Restore Default Settings
then enable USB debugging
add a comment |
Just go to device Settings >> Developer Options >> Restore Default Settings
then enable USB debugging
Just go to device Settings >> Developer Options >> Restore Default Settings
then enable USB debugging
answered Oct 25 '17 at 17:06
Iman MarashiIman Marashi
2,4102031
2,4102031
add a comment |
add a comment |
In my case my app use some native libraries. Each platform requires the corresponding libs to be built.
So the native lib of x86(or any other) platform is not generated.You must have add an abifilter somewhere:
There are several places where abi filters can be specified:
Application.mk
add the platform you need like this:
APP_ABI := armeabi armeabi-v7a x86
build.gradle
find abiFilters, and add platform you need like this:
abiFilters "armeabi","armeabi-v7a","x86"
add a comment |
In my case my app use some native libraries. Each platform requires the corresponding libs to be built.
So the native lib of x86(or any other) platform is not generated.You must have add an abifilter somewhere:
There are several places where abi filters can be specified:
Application.mk
add the platform you need like this:
APP_ABI := armeabi armeabi-v7a x86
build.gradle
find abiFilters, and add platform you need like this:
abiFilters "armeabi","armeabi-v7a","x86"
add a comment |
In my case my app use some native libraries. Each platform requires the corresponding libs to be built.
So the native lib of x86(or any other) platform is not generated.You must have add an abifilter somewhere:
There are several places where abi filters can be specified:
Application.mk
add the platform you need like this:
APP_ABI := armeabi armeabi-v7a x86
build.gradle
find abiFilters, and add platform you need like this:
abiFilters "armeabi","armeabi-v7a","x86"
In my case my app use some native libraries. Each platform requires the corresponding libs to be built.
So the native lib of x86(or any other) platform is not generated.You must have add an abifilter somewhere:
There are several places where abi filters can be specified:
Application.mk
add the platform you need like this:
APP_ABI := armeabi armeabi-v7a x86
build.gradle
find abiFilters, and add platform you need like this:
abiFilters "armeabi","armeabi-v7a","x86"
edited Feb 6 at 20:45
answered Apr 17 '17 at 3:21
yaoyao
969
969
add a comment |
add a comment |
On my physical device, I started getting this. The fix was to go into Developer Settings and turn off and on USB debugging.
add a comment |
On my physical device, I started getting this. The fix was to go into Developer Settings and turn off and on USB debugging.
add a comment |
On my physical device, I started getting this. The fix was to go into Developer Settings and turn off and on USB debugging.
On my physical device, I started getting this. The fix was to go into Developer Settings and turn off and on USB debugging.
answered Apr 16 '18 at 20:13
svguerin3svguerin3
1,12531737
1,12531737
add a comment |
add a comment |
For me it worked my changing the cable option from
-> Charge Only.
To
-> Transfer file.
add a comment |
For me it worked my changing the cable option from
-> Charge Only.
To
-> Transfer file.
add a comment |
For me it worked my changing the cable option from
-> Charge Only.
To
-> Transfer file.
For me it worked my changing the cable option from
-> Charge Only.
To
-> Transfer file.
answered Oct 26 '18 at 4:37
Sushil ChaudharySushil Chaudhary
1036
1036
add a comment |
add a comment |
adb kill-server
adb start-server
Its working for me on windows OS.
add a comment |
adb kill-server
adb start-server
Its working for me on windows OS.
add a comment |
adb kill-server
adb start-server
Its working for me on windows OS.
adb kill-server
adb start-server
Its working for me on windows OS.
answered Jan 11 at 4:19
siddhartha shankarsiddhartha shankar
67189
67189
add a comment |
add a comment |
If you use Ubuntu:
- make sure that usb debugging is ON
- check your cable connection
- on notification bar check android system notification and touch it for change charging state to file transfer
- now go terminal and type:
adb devices
after run this command adb restart and your device show in list
add a comment |
If you use Ubuntu:
- make sure that usb debugging is ON
- check your cable connection
- on notification bar check android system notification and touch it for change charging state to file transfer
- now go terminal and type:
adb devices
after run this command adb restart and your device show in list
add a comment |
If you use Ubuntu:
- make sure that usb debugging is ON
- check your cable connection
- on notification bar check android system notification and touch it for change charging state to file transfer
- now go terminal and type:
adb devices
after run this command adb restart and your device show in list
If you use Ubuntu:
- make sure that usb debugging is ON
- check your cable connection
- on notification bar check android system notification and touch it for change charging state to file transfer
- now go terminal and type:
adb devices
after run this command adb restart and your device show in list
edited Jan 23 at 1:05
Pang
6,9391664102
6,9391664102
answered Dec 30 '18 at 5:28
mohsen khalilimohsen khalili
1113
1113
add a comment |
add a comment |
Test your code on real phone. If you have still same issue,then import your code again and before this you should update your SDK and create a new emulator with ARM system image.
add a comment |
Test your code on real phone. If you have still same issue,then import your code again and before this you should update your SDK and create a new emulator with ARM system image.
add a comment |
Test your code on real phone. If you have still same issue,then import your code again and before this you should update your SDK and create a new emulator with ARM system image.
Test your code on real phone. If you have still same issue,then import your code again and before this you should update your SDK and create a new emulator with ARM system image.
answered Jan 21 '17 at 5:39
AdiAdi
152217
152217
add a comment |
add a comment |
Many times this means that you have not granted your laptop/computer access to your device. Take a look at your device and click the "Allow Access" button as well as the debugging permissions.
add a comment |
Many times this means that you have not granted your laptop/computer access to your device. Take a look at your device and click the "Allow Access" button as well as the debugging permissions.
add a comment |
Many times this means that you have not granted your laptop/computer access to your device. Take a look at your device and click the "Allow Access" button as well as the debugging permissions.
Many times this means that you have not granted your laptop/computer access to your device. Take a look at your device and click the "Allow Access" button as well as the debugging permissions.
answered Jul 27 '18 at 18:58
NVANVA
5772919
5772919
add a comment |
add a comment |
Running an AVD using the x86 processor is 10x faster than using the ARM emulator, but most of the time you are only compiling your APK for ARM. To have faster emulation runs using an x86 AVD I had to do the following (for a Cocos2d-x project):
app/jni/Android.mk
APP_ABI := armeabi-v7a:x86
gradle.properties
PROP_APP_ABI=armeabi-v7a:x86
app/build.gradle
android {
...
defaultConfig {
...
ndk {
abiFilters =
abiFilters.addAll(PROP_APP_ABI.split(':').collect{it as String})
}
}
}
add a comment |
Running an AVD using the x86 processor is 10x faster than using the ARM emulator, but most of the time you are only compiling your APK for ARM. To have faster emulation runs using an x86 AVD I had to do the following (for a Cocos2d-x project):
app/jni/Android.mk
APP_ABI := armeabi-v7a:x86
gradle.properties
PROP_APP_ABI=armeabi-v7a:x86
app/build.gradle
android {
...
defaultConfig {
...
ndk {
abiFilters =
abiFilters.addAll(PROP_APP_ABI.split(':').collect{it as String})
}
}
}
add a comment |
Running an AVD using the x86 processor is 10x faster than using the ARM emulator, but most of the time you are only compiling your APK for ARM. To have faster emulation runs using an x86 AVD I had to do the following (for a Cocos2d-x project):
app/jni/Android.mk
APP_ABI := armeabi-v7a:x86
gradle.properties
PROP_APP_ABI=armeabi-v7a:x86
app/build.gradle
android {
...
defaultConfig {
...
ndk {
abiFilters =
abiFilters.addAll(PROP_APP_ABI.split(':').collect{it as String})
}
}
}
Running an AVD using the x86 processor is 10x faster than using the ARM emulator, but most of the time you are only compiling your APK for ARM. To have faster emulation runs using an x86 AVD I had to do the following (for a Cocos2d-x project):
app/jni/Android.mk
APP_ABI := armeabi-v7a:x86
gradle.properties
PROP_APP_ABI=armeabi-v7a:x86
app/build.gradle
android {
...
defaultConfig {
...
ndk {
abiFilters =
abiFilters.addAll(PROP_APP_ABI.split(':').collect{it as String})
}
}
}
answered Dec 24 '18 at 16:19
nikcnikc
1,6241416
1,6241416
add a comment |
add a comment |
Restarting device solved problem for me (React-native)
add a comment |
Restarting device solved problem for me (React-native)
add a comment |
Restarting device solved problem for me (React-native)
Restarting device solved problem for me (React-native)
answered Feb 11 at 5:20
O. BorcuhinO. Borcuhin
20625
20625
add a comment |
add a comment |
You need to reconnect your device and try to turn off/on the developer options.
See Enable developer options and debugging
add a comment |
You need to reconnect your device and try to turn off/on the developer options.
See Enable developer options and debugging
add a comment |
You need to reconnect your device and try to turn off/on the developer options.
See Enable developer options and debugging
You need to reconnect your device and try to turn off/on the developer options.
See Enable developer options and debugging
answered Feb 11 at 5:25
shizhenshizhen
3,59841233
3,59841233
add a comment |
add a comment |
It happened to me to after updating the Android Studio. In my case, it happened because of the build setting is not automatically configured into x86Debug-x86.
Just change it by opening Build>>Select Build Variant>> Change the build variant option from armeabi-v7a into x86Debug-x86 or whatever you need in the emulator.
New contributor
add a comment |
It happened to me to after updating the Android Studio. In my case, it happened because of the build setting is not automatically configured into x86Debug-x86.
Just change it by opening Build>>Select Build Variant>> Change the build variant option from armeabi-v7a into x86Debug-x86 or whatever you need in the emulator.
New contributor
add a comment |
It happened to me to after updating the Android Studio. In my case, it happened because of the build setting is not automatically configured into x86Debug-x86.
Just change it by opening Build>>Select Build Variant>> Change the build variant option from armeabi-v7a into x86Debug-x86 or whatever you need in the emulator.
New contributor
It happened to me to after updating the Android Studio. In my case, it happened because of the build setting is not automatically configured into x86Debug-x86.
Just change it by opening Build>>Select Build Variant>> Change the build variant option from armeabi-v7a into x86Debug-x86 or whatever you need in the emulator.
New contributor
New contributor
answered yesterday
Rico ValentinoRico Valentino
1
1
New contributor
New contributor
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- 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%2fstackoverflow.com%2fquestions%2f41775988%2fwhat-is-the-reason-for-the-error-device-supports-x86-but-apk-only-supports-arm%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
What AVD did you use? What System Image? What GitHub project?
– cricket_007
Jan 21 '17 at 5:23
In other words, the Intel x86 images aren't going to run ARM code.
– cricket_007
Jan 21 '17 at 5:25
github.com/jreyes/mirror
– Alexander Ibarra
Jan 21 '17 at 5:31
I wanted to use a Nexus 10 running android 5.1
– Alexander Ibarra
Jan 21 '17 at 5:32
Okay, and did you use the ARM eabi v7 system image or an Intel Atom x86 image? Check your SDK manager what you have installed.
– cricket_007
Jan 21 '17 at 5:34