Android Studio not communicating with adb GLIBC .... not found error - android

Android studio was communicating with adb normally. Right after updating platform-tools to version 23, android studio stopped communicating with adb.
It displays the message:
Unable to create Debug Bridge: Unable to start adb server: Unable to
detect adb version, adb output:
/data/programs/android-sdk/platform-tools/adb: /lib64/libc.so.6:
version 'GLIBC_2.14' not found (required by
/data/programs/android-sdk/platform-tools/adb)
/data/programs/android-sdk/platform-tools/adb: /lib64/libc.so.6:
version 'GLIBC_2.15' not found (required by
/data/programs/android-sdk/platform-tools/adb)
I have Centos 6.5 (final) Kernel
Linux 2.6.32.431.el6.x86_64
Gnome 2.28.2

I think the only solution to this problem is to upgrade the distribution because one can't simply upgrade GLIBC on the dist
A temporary workaround is to rollback to a previous version of the platform tools.
The version introduced this is platform-tools_r23.1.0.
The last working version is platform-tools_r23.0.1.
You can download the last working version from
http://dl-ssl.google.com/android/repository/platform-tools_r23.0.1-linux.zip
Just extract it and replace the platform-tools folder inside your sdk folder.

I found a temporary solution:
I have a copy of the previous version of platform-tools folder. I replaced the new folder with the older one. back to normal.
But I still wish someone finds a solution to make platform-tools v23 works on Centos machine.

Related

Xamarin Ui Test -> Compatible with Android target version 9.0 (28)

I've got an Android project with the target to Android 9 (PI) -> SDK Platform 28.
I would like to write Xamarin UI tests to my project, but unfortunatelly I get the error:
System.Exception: 'The running adb server is incompatible with the Android SDK version in use by UITest:
C:\Users\User\AppData\Local\Android\Sdk
You probably have multiple installations of the Android SDK and should update them or ensure that your IDE, simulator and shell all use the same instance. The ANDROID_HOME environment variable can effect this.'
I use following versions:
Target Platform: Android 9
Xamarin.UITest 3.0.0 (currently the latest)
ADB 1.0.41
Before I used the ADB 1.0.39, but I replaced it by the version 1.0.41 after the error occurred.
Does Xamarin UI Test currently works with the target platform Android 9 at all?
What are compatible versions?
I found the solution :)
It was really a problem with different ADB versions...
The concrete problem was, that the ADB version within Visual Studio was different from my version in C:\Users\User\AppData\Local\Android\Sdk.
Following solution helped:
Open the "Package Manager Console" within Visual Studio.
Update ADB to the latest version (within the console): dotnet tool update --global AndroidSDK.PlatformTools.ADB
Download the same version as updated from the ADB git-hub project
Rename the old "platforms-tools" folder within C:\Users\User\AppData\Local\Android\Sdk\ and copy the downloaded "platforms-tools" folder into the Sdk directory.
Restart the computer.
The tests started after these steps successfully.
PS: The "platforms-tools" folder can be found using the "adb version" command within the windows console.

Error Initializing ADB: Android Debug Bridge not found [duplicate]

After updating Android Studio to 2.0 l am getting this error unable to obtain debug bridge and Android Device Monitor does not open. Anyone faced this error before?
I just open sdk manager and installed all android sdk tools and done.
Check whether you need to install "Android Sdk Platform Tools" in the Android SDK Manager.
Somehow, after installing Android Studio from the bundle (for Linux) I lacked the "platform-tools" directory in "Android/Sdk", where the adb executable resides. Installing the platform tools helped. It was easier to find in the standalone sdk manager.
This is because you deleted the adb.exe (it might be your antivirus who deleted it),that resided in the platform tools in the android sdk folder.
What you need to do is to delete the current platform-tools in the sdk manager program and re install it all over again.
I installed the right sdk version that matched my virtual device android version
I am also running the same problem when update android studio from 1.4 to 1.5 stable version. When I run adb command from terminal then i found following error :
bash: ./adb: cannot execute binary file: Exec format error
After R&d I found that this error occurs due to unsupported architecture. In my case:
I am using ubuntu14.04 LTS 32-bit. I observed that after updation, lib folder under platform-tools converted to lib64. I think above error occurs due to 32-bit architecture because after updation 32-bit support removed.
For permanent solution upgrade you system to 64-bit architecture.
Quick solution is to replace the updated platform-tools folder with old one that containing the lib folder instead of lib64.
I think 32-bit architecture support for android development stopped by google for future releases. But I am not sure.
I am phase these error when updating Android-SDK Plateform-Tools 23.1 in Android SDK Manager
i am worked on ubuntu 14.04 [32bit] that is not supporting with Plateform-Tools 23.1 it is only supporting in 64bit Operating System architecture that's why downgrade my Plateform-tools 23.0
it works perfect...!!!
Go to: Android Studio Settings > Appearance & Behavior > System Settings > Android SDK:
If path for SDK are text in red, change to your SDK folder and click ***APPLY***
Open the standalone SDK manager and install the platform tools package.

Unable to create Debug Bridge Unable to detect adb version. Syntax error: ")" Upgrading Platform-tools 23.0.1 to 23.1.0 Linux-32 bit causes Issue [duplicate]

This question already has answers here:
android studio adb Syntax error: ")" unexpected
(4 answers)
Closed 5 years ago.
I updated Platform-tools from 23.0.1 to 23.1.0 and found some of the Android integration broke.
I'm running Ubuntu 14.04 32-bit with android-sdk_r24.4.1, with both android-studio (141.2456560) installed.
While executing adb command it keeps on saying below message :
Unable to create Debug Bridge: Unable to start adb server: Unable to
detect adb version, adb output:
/home/bhavesh/android-sdk-linux/platform-tools/adb: 1:
/home/bhavesh/android-sdk-linux/platform-tools/adb: Syntax error: ")"
unexpected
Any help would be appreciated.
Thanks
OK. after some research found that reason for this is because
android-sdk-linux/platform-tools content is 32-bit
ELF in 23.0.1 but 64-bit ELF in 23.1_rc1 and 23.1.0. So, several
functions in android-studio (and I assume eclipse+ADT as well) fail
because of the attempt to run 64-bit executables.
This issue has already been raised HERE
Also, as per the official comment given by google project member parts of the platform-tools will support 64 bit Ubuntu OS only from 23.1.0 onwards.
Platform-tools 23.1.0 OR onwards will not work on Ubuntu 32-bit OS. Developer needs to upgrade Ubuntu OS to 64-bit to make it work.
That eventually means we only have possible two workarounds now :
1. Stick with Platform-tool 23.0.1 as of now. and DO NOT UPGRADE platform-tools to 23.1.0 or above
2. Change your Ubuntu OS to 64-bit instead of 32-bit.
I hope this would help someone.
download sdk platform-tool 23.0.1 from this link
I filed that bug 8-) If you updated to 23.1.0 already (or install a fresh android-sdk, which will insist on installing newest platform-tools), you have two solutions:
1) Get platform-tools 23.0.1 from https://dl-ssl.google.com/android/repository/platform-tools_r23.0.1-linux.zip . Go to android-sdk-linux directory, delete the "platform-tools" directory (may not be necessary) and unzip the platform-tools_r23.0.1-linux.zip there. SDK updater correctly shows 23.0.1 is installed next time you run it.
2) I found although qemu-2.0.0 will not run 64-bit "adb start-server", qemu-2.4.0 will! I posted to the bug report linked above, please see my post for more info. Long story short, I built qemu-2.4.0 source package (for Ubuntu Xxxxx Xaros -- I forget what Ubuntu 16.04's animal name is...) and installed a single extra binfmt file to enable qemu-x86_64 seamless support. I ran "dpkg --add-architecture amd64" and "apt-get install libc6:amd64" to install base 64-bit libraries. Done, x86-64 seamless emulation is a go!
This sounds like a recipe for the world's slowest SDK install... but actually, Java itself uses the VAST majority of CPU time running eclipse+ADT or Android Studio. As important as the native binaries are to having a working SDK, the CPU usage of those binaries is nearly 0 (other than the phone/table emulator itself, which is needless to say quite CPU-intensive.)
This error arrived i have in case of updated platform-tools from 23.0.1 to 23.2.0, i have solved by downloading platform-tools for 23.0.1 and start its working,
because 23.2.0 is not supported in 32 bit os version its nee 64 bit os

android studio adb Syntax error: ")" unexpected

this morning when I start doing my daily routine(opening android studio 1.5.1 in my PC - lubuntu 32 bit) I encounter an error after I try to run my application to my device. This is the android studio error:
Error running app: Unable to obtain debug bridge
Unable to detect adb version, adb output: /root/Android/Sdk/platform-tools/adb: 1: /root/Android/Sdk/platform-tools/adb: Syntax error: ")" unexpected
I was looking for possible solution for hours now through internet but can't find same error as this. I already try some other remedies but still no luck of solving it. Can you help me guy? Thanks in advance.
for 32bit users... Don't update "platform-tools" to version 23.1.
foremost version you can use is 23.0.1 which you can download here
If you are on 64bit machine and having trouble using the latest version of the plateform-tools.. check instructions here.
thanks for the working link- #Tyler
OK. after some research found that reason for this is because
android-sdk-linux/platform-tools content is 32-bit
ELF in 23.0.1 but 64-bit ELF in 23.1_rc1 and 23.1.0. So, several
functions in android-studio (and I assume eclipse+ADT as well) fail
because of the attempt to run 64-bit executables.
This issue has already been raised HERE
Also, as per the official comment given by google project member parts of the platform-tools will support 64 bit Ubuntu OS only from 23.1.0 onwards.
Platform-tools 23.1.0 OR onwards will not work on Ubuntu 32-bit OS. Developer needs to upgrade Ubuntu OS to 64-bit to make it work.
That eventually means we only have possible two workarounds now :
1. Stick with Platform-tool 23.0.1 as of now. and DO NOT UPGRADE platform-tools to 23.1.0 or above
2. Change your Ubuntu OS to 64-bit instead of 32-bit.
I hope this would help someone.
download sdk platform-tool 23.0.1 from this link
As Arnav M. said, for Ubuntu 32bit users, stick to 23.0.1 or install a 64bit Ubuntu. For more details see this:
https://stackoverflow.com/a/34239600/3032209
What you actually need to do is downgrade your platform-tool, which contains Android Debug Bridge, to lower version.
Download the platform-tool package from following link
platform-tools_r23.0.1-linux
Unzip the package and replace the platform-tool folder, in android-sdk folder, with the downloaded platform-tool folder.
After restarting android studio, it may ask you to upgrade platform-tool. Ignore it.

Error:Unable to obtain debug bridge in android studio

After updating Android Studio to 2.0 l am getting this error unable to obtain debug bridge and Android Device Monitor does not open. Anyone faced this error before?
I just open sdk manager and installed all android sdk tools and done.
Check whether you need to install "Android Sdk Platform Tools" in the Android SDK Manager.
Somehow, after installing Android Studio from the bundle (for Linux) I lacked the "platform-tools" directory in "Android/Sdk", where the adb executable resides. Installing the platform tools helped. It was easier to find in the standalone sdk manager.
This is because you deleted the adb.exe (it might be your antivirus who deleted it),that resided in the platform tools in the android sdk folder.
What you need to do is to delete the current platform-tools in the sdk manager program and re install it all over again.
I installed the right sdk version that matched my virtual device android version
I am also running the same problem when update android studio from 1.4 to 1.5 stable version. When I run adb command from terminal then i found following error :
bash: ./adb: cannot execute binary file: Exec format error
After R&d I found that this error occurs due to unsupported architecture. In my case:
I am using ubuntu14.04 LTS 32-bit. I observed that after updation, lib folder under platform-tools converted to lib64. I think above error occurs due to 32-bit architecture because after updation 32-bit support removed.
For permanent solution upgrade you system to 64-bit architecture.
Quick solution is to replace the updated platform-tools folder with old one that containing the lib folder instead of lib64.
I think 32-bit architecture support for android development stopped by google for future releases. But I am not sure.
I am phase these error when updating Android-SDK Plateform-Tools 23.1 in Android SDK Manager
i am worked on ubuntu 14.04 [32bit] that is not supporting with Plateform-Tools 23.1 it is only supporting in 64bit Operating System architecture that's why downgrade my Plateform-tools 23.0
it works perfect...!!!
Go to: Android Studio Settings > Appearance & Behavior > System Settings > Android SDK:
If path for SDK are text in red, change to your SDK folder and click ***APPLY***
Open the standalone SDK manager and install the platform tools package.

Categories

Resources