adb not recognizing one of my pairs of Google Glass - google-gdk

I had two pairs of Google glasses. One is black(original version) and the other white(new version). I had done a lot of development using the black pair. We sent the black one back to exchange for the new version. I tried to continue developing using the white pair but can not get adb to recognize it.
OS: Mac 10.8.5
Eclipse 4.2.1
Glass Firmware: XE16.11
ADT Package 2.3
Android SDK Tools 22.6.2
Android SDK Platform-tools 19.0.1
Both pairs were set to debug mode.
Thanks,
Mark

Related

Android Studio very laggy on M1 Apple Silicon chip

I've upgraded to the M1 chip 2020 Macbook Air from a 7th gen. Intel chip pc. Overall, I'm very happy and content with it but when it comes to Android Studio performance, which I use quite often, it is very disappointing I'm sorry to say. When will an Apple Silicon compatible version be available? Are any of you guys have any clue?
I had the exact problem and the solution was as follows:
Open Android Studio, go to Help -> Edit Custom VM Options and add the following lines:
-Dsun.java2d.opengl=true
-Dsun.java2d.opengl.fbobject=false
Restart the IDE and wait for the files to sync. Done, IDE running smooth again.
Starting from Android Studio Artic Fox version, they not only changed versioning number style (replaced number system with Year-styling Version names), but also introduced Android Studio for M1/Apple Silicon (arm arch 64bits).
To check if you'r using right Android Studio for your M1, click on 'About Android Studio' and check the runtime, it should show as aarch64 (ie. Arm architecture 64bits). If not, mostly you might be having x86_64 if you installed regular Mac's Android Studio.
To switch to M1's Android Studio,
first exit already installed Android Studio, if it's open.
Go to Finder and under 'Applications', rename 'Android Studio' to preferably 'Android Studio_x86_64'.
Go to Android Studio downloads page (https://developer.android.com/studio#downloads), and download the one tagged as 'Mac (64-bit, ARM)' and unzip and move to 'Applications'.
Click to open 'Android Studio' from the Finder/Applications. You may drag and add it as a Dock shortcut option.
Good thing is that there is no extra installation required and the existing project, (at least for me), opened without any issues.
Android-SDK based and Flutter projects should be good right after switch, NDK not yet there.
AS is now faster again as you are using it as intended on Apple M1's chipset. !
Now Android Studio Bumblebee (2021.1.1) is available in Stable Channel. If your version is older than Bumblebee, download it for more performance.
I find out that the link shown by default is for intel architectures.
Automatic update performed by android studio also downloads the intel version even if this download occurs on a Mac with an ARM architecture (M1) .
You should navigate to the download options and choose ARM architecture manually.
You can download version 2021.1.1.22 Bumblebee for MAC ARM (M1) here (Link updated on Mar 7 2022 )
Check Android Studio Arctic Fox (2020.3.1) Beta 3 (have apple silicon support)
https://developer.android.com/studio/archive
use Intellij CE the latest version released on April 6th has native support for m1 and its very fast and intuitive, i've been using it and it's not very different from android studio
Edit: September 21
Download m1 native supported Android studio through https://developer.android.com/studio/archive
Download Mac (Apple silicon)
All the above did not work and my emulator was completely unusable but in my case the following fixed my issues:
Android studio Preferences > Tools > Emulator
Make sure 'Launch in a tool window' is checked
'Wipe Data' on emulator and then relaunch
Having the emulator launch as a separate window caused a huge slowdown but this fixed it immediately

Android Studio 4.0 doesn't recognize any previous virtual devices

First post--be gentle. Can't find any posts on Android Studio 4.0, so I hope this isn't a repeat. I updated Android Studio from 3.6.3 to 4.0 on Windows 10 (1909). Had created a couple of virtual devices in 3.6.3 (a Pixel 2 running API 28 and a Pixel 3 running API 29)--both worked great in AS-3.6.3 and I could develop apps, compile, load, and run them with no problem.
After the update to AS-4.0, the virtual devices no longer appear in the devices box at the top of the GUI--it just says "No Devices". When I open the AVD Manager, I can see them, and I can start them (although when I start them I get a pop-up saying "AVD Manager: Unable to locate adb"), but I can't get any code to download and execute on it. On the Pixel 3 emulator, I also get another pop-up saying "Detected ADB: Could not automatically detect an ADB binary.", and it gives instructions to resolve it, which don't make any difference (jump into extended controls and toggle "Use detected ADB location").
When I try to open a past project and run it, I get the same behavior--no devices found.
I've also tried making new emulators, hoping the new setup would recognize them, but to no avail. Tried starting and restarting AS, as well as the computer, also to no avail. I have Android SDK Build-Tools 30-rc4, the latest Android SDK Command-line Tools, Android Emulator 30.0.12 Android SDK Platform-Tools 30.0.1, and the Intel x86 Emulator Accelerator all installed.
I've Googled and spoken words of fierce power over this for several days now. Any suggestions for how to get AS-4.0 to recognize the emulators? I've resisted uninstalling everything and starting over--was hoping it was just a configuration thing.
Thanks in advance,
Uber
After some more Googling, I found the answer here (I think my constraint of wanting an answer for AS-4.0 specifically kept me from finding it):
Could not automatically detect an ADB binary - Android Studio
I had to redownload the SDK platform-tools zip file and reinstall it. I don't know why the old one got messed up with the migration from AS-3.6.3 to 4.0, but there you go--such is life with complicated software.
As soon as I replaced the old platform-tools directory with the new one, all my old emulators showed up and I was back in business.
Thanks anyway!
Uber

Problem running the Android Studio emulator on AMD CPU

Recently I decided to learn android dev with Kotlin, I installed JDK, the latest Android Studio release and other stuff but my CPU is AMD so I cannot install intel's HAXM which is required to launch the emulator . I want to know if an equivalent for pc with AMD exist
For your problem there are several ways to fix the issue.
Android Studio with Android Emulator Hypervisor Driver for AMD Processors Tools(Recommended)
Here's the full document
Go to Android SDK -> SDK Tools -> Check Android Emulator Hypervisor Driver for AMD Processors also make sure if they're installed they're updated, since this solution got a problem with using NOX player at same time, and causing Blue Screen of Death
Then go to App & Features -> Turn windows features on or off -> make sure Hyper-V and Windows Hypervisor Platform are disabled. All Windows features enabling Hyper-V either explicitly or silently must be turned off.
Other solution is to use Nox or Bluestack emulator. i prefer nox since idk why but bluestack using so many resource, and also nox multi-instance is also working very well for using several emulators and it's got 3 version of android (4, 5, 7).
Common issues while using nox when trying to develop flutter app or etc is sometime emulator won't appear in your emulator list in android studio which the solution is that you should copy your adb nox file to your android sdk folder. or address the PATH VARIABLES to use nox adb.
Good Luck.

Android wear and Android TV in Android studio

What's the function Android TV and Android Wear in Android SDK manager in Android studio. Do I need to install these for all Api
Those two components provide you a way to develop for Wear and TV apps, respectively. If you only want to develop a phone app, you are not needed to install those.
You can see more about the Android Wear SDK here and Android TV SDK here.
Android TV is for Android TV. If you don't need your app to run on an Android TV (which has a tiny marketshare anyway), then don't worry about it.
The same goes for Android Wear. If you don't need your app to run on an Android watch (which has a tiny marketshare anyway), then don't worry about it.
Also, you seem to misunderstand how Android versioning works. If you want to develop on a phone or a tablet, just download the latest version, you do not need to download the previous versions (except may be for one compatibility library that you might need).
In other words, if you're just a beginner, download as little as you can. Most beginners download almost everything and that's just a waste of space.

Google maps does not run on emulator and asks for Google play services update

I use:
Android studio 1.5
Java JDK 1.7
windows 7
Intel HAXM driver
I created a default google map activity with studio and I tried to run with but I get a message to upgrade my google servies.
As I read to documentation of android studio I have to set
compile 'com.google.android.gms:play-services:8.3.0'
on gradle in section dependencies. This was set by default.
I don't think that the problem is on my code but in emulator's configuration.
I strongly believe that the problem start from my android sdk packages but it is not possible to make any mistake. I test the same project in Linux OS that I have install android Dev environment and there is no problem at all. Google maps works.
I installed next packages
From tools:
Android SDK Tools
Android SDK platform-tools
Android SDK Build-tools
From Android 6.0(API 23)
Everything except ARM, Wear and TV packages.
From Extra:
Android Support Repository
Android Support Library
Google Play services
Google Repository
Google USB Driver
Intel x86 Emulator Accelerator(HAXM installer)
Next I create AVD from android studio:
I choose a device definition one from default
Then system image API level 23 with ABI x86 and target Android 6.0 (with Google APIs)
but automatically selects android 6.0 without Google APIs
Your problem may well be the same as mine, see AVD Error - Update Google Play Services. Sorry no solutions but perhaps you are correct that the fault lies with the current packages

Resources