Currently, I'm working on a big tablet android like the advertisement board.
I'm trying to use react-native for it and the only port that they have is USB. I'm trying to open the developer menu but have no idea how. I am installing the apps by sending the debug apk using the drive.
Things that I try:-
shake the big tab, might be they do not have the sensor for it
use USB male to male did not detect the USB as adb or anything.
any idea how to open this one? it's pretty hard to not see the console.
Tab Information:
Model number
Quad-Core R18 ads
Android version
android 6.0.1
firmware version
ads_v1.0
kernel version
3.10.65
xiao#yh-Series2 #225
I am having problem after I updated my sdk via intellij updates. my sdk resides in D:/sdk, now after updating when I launch the AVD and click triangular green button to lunch the emulator. Nothing happens no emulator is launching I don't know why.
It probably has something to do with virtualization.
Check if virtualization is enabled in the BIOS setting of your machine. And if you're working on Windows make sure "Hyper-V" options are disabled in "Windows Features".
I'm trying to get my react-native project to run on an android emulator while on a Mac operating system. It worked fine on my windows.
On my Mac, I go to terminal and type react-native run-android and I get the error message:
$ react-native run-android
Scanning 616 folders for symlinks in /Users/John/Documents/myreactnativeproject/node_modules (17ms)
Starting JS server...
Building and installing the app on the device (cd android && ./gradlew installDebug)...
Could not install the app on the device, read the error above for details.
Make sure you have an Android emulator running or a device connected and have
set up your Android development environment:
https://facebook.github.io/react-native/docs/android-setup.html
I type adb devices and I see
List of devices attached
emulator-5554 unauthorized
I go into the settings of my android emulator, I go to Settings Build Number to tap it several times to enable Developer options. In developer options, I enabled USB debugging, disabled Verify apps over USB, and left everything else as default. I shut down my android studio and emulator, restarted it. But still, the same issues mentioned above.
What am I doing wrong?
EDIT
I just connected my android phone to my Mac. When I run adb devices, I see this result
List of devices attached
YLEDU16B18004313 device
But when I run react-native run-android, I get the same error as above. So maybe there is something wrong with my react-native set up instead?
EDIT 2
I was able to deploy the app to my android phone by adding these extra steps
chmod 755 android/gradlew
For some reason, when I type echo $ANDROID_HOME into the terminal, I get the result /Users/John/Library/Android/sdk. But if I add the echo $ANDROID_HOME line to my android/gradlew file, it echoes nothing. And when I run the react-native run-android command, the compiler complains that ANDROID_HOME is not defined. So I have to type export ANDROID_HOME=/Users/John/Library/Android/sdk again, then running the react-native run-android command works and deploys it to my phone.
However, my emulator still doesn't work. The new error message I get is that Skipping device 'emulator-5554' (emulator-5554): Device is UNAUTHORIZED,.
But at least I have a temporary solution, and to debug with my phone.
EDIT 3
I got rid of the emulator 5554 unauthorized error by going into my Android Virtual Devices and deleting the virtual device. Then I re-installed it. And now my adb devices shows emulator 5554 device. And I am not able to deploy the app to my emulator.
In my case, Create a Virtual Device with Google APIs Image, not Google Play Image worked for me.
The problem occurs the only emulator that runs on Android Pie others don't.
In Android Studio
Open an Android Virtual Device Manager.
Create a new Virtual Device.
Select any Hardware you want.
Select any System Image which the Target is "(Google APIs)" not "(Google Play)" (If you don't found. Try to look at "x86 Images" tab or "Other Images" tab)
Done!
Android emulators have by default "Usb Debugging" in settings. You just need to wipe the data of the emulator. Do the following steps. It will work :---
Close the emulator and run the command adb kill-server in the command prompt. If adb is not set in you path then you might run this command from directory where adb is present.
Click on Wipe Data option from avd Actions menu.
Now run the emulator. It should work.
create new Virtual Device, and make sure you choose Google API's.
run the new device!. this should work
In my case, following steps worked
Wipe data from avd manager
Cold boot now
I managed to authenticate the adb on a Pixel 2, Android 9.0 (Google Play), API 28, x86_64 virtual device (Intel HAXM). The problem should be related to the Extended Controls (the 3 dots bottom icon menu, when the virtual device is booted), the Google Play menu, that is checking the version of the Google Play services. When adb is not 'unauthorized', this page is displaying the correct version, and the Update button opens inside the phone the Play Store with the Play Services app, so you can update it.
The steps I took to be able to authenticate are:
Make sure the USB debugging is turned ON in Dev setting
Revoke the USB debugging authorizations
Make sure the Extended Controls > Settings > Advanced > Open GL options are set to the: 'Desktop native OpenGL' and 'Renderer maximum (up to OpenGL ES 3.1)', so the emulator interface, animations, etc, are fast!
Power off the emulator
In 'Your Virtual Devices' in Android Studio, click the down arrow in Actions > Select 'Cold Boot Now'
When the device boot, you have to be fast, the dialog to remember and accept the USB connection will show and disappear for like less than 1 second (again I guess related to some automation scripts kicking, idn).
If you manage to click the 'remember' and 'ok' checkbox and button before the dialog disappears, you are done. Else you have to Power Off and Cold Boot again.
After that, don't wipe your emulator, else you'll have to do that insane race clicking again!
I run adb kill-server and adb devices.
the device will back again.
for Emulator, the default settings is debug enabled
Creating an emulator with graphics set to "Software - GLES 2.0" worked for me (Nexus 6 image).
I was initially using a Nexus 5X image which didn't allow me to select the graphics option.
NOTE: I went through the steps mentioned in EDIT 2 and EDIT 3 by the OP before doing this.
This can happen if USB debugging is not enabled on the emulator device.
Go to the emulated device, enable the Developer options and enable USB debugging.
I had to create a new emulator with Google Api. Wiping data didn't work for me.
2022 answer
What a shame of thread: so many "answers", comments and upvotes and none worked. Nobody simply mentioned that the "adb unauthorized" is caused by the adb keys stored in ~/.android/adbkey and ~/.android/adbkey.pub After deleting and recreating them, the problem was solved.
Credit: Android Emulator Unauthorized
I got my mac system to deploy a react-native build to my physical phone by following Edit 2 in the question.
I got my mac system to deploy a react-native build to my emulator by following Edit 3 in the question.
I think the issue was generally caused by moving my project from a Windows dev area to Mac dev area. Then probably a combination of different issues happened that cause builds to fail for each situation.
Deleting emulator and creating it again helped me on Ubuntu
I solved Problem
add ANDROID_SDK_HOME to environment variable
ANDROID_SDK_HOME = D:\sdk
and unplug device
and use new cmd
The emulator used to run fine, but as of late whenever i try to launch it, whether directly from the programs list or by running code in Visual Studio, the emulator will launch, stop responding and crash, then when I hit "close program" it will launch itself again, stop responding and crash again. I've looked everywhere and cannot get an answer to this issue.
Thanks
The only way i think is by reinstalling the product.
Just so you know, make sure that you're using the right version of the SDK for your OS (on PC) and using just the right emulator supported by your OS (pc).
Like for SDK 8.0, if you're developing Win8 app, use 'Device' for direct app deployment onto your phone or "Emulator WVGA 512MB" for optimized, memory-constrained output on your PC itself.
This might be esoteric but here goes.
I'm developing a program in WPF for use on a multitouch screen. I'm using the Surface 2.0 SDK and trying to get the Toolkit to simulate inputs and run the stress test. However SurfaceStress.exe is throwing an error:
Error 0: Cannot get reference to virtual digitizer controller.
and Input Simulator is giving me a timeout error looking for the controller.
I've read up about it on MSDN http://msdn.microsoft.com/en-us/library/ff727911.aspx
I know it can't run two controllers at the same time and it's not on a SUR40. It says "Tablet PC Settings" would only appear if the Input Simulator is running. But it's running anyway and its Setup button is grayed out. I don't have a touchscreen but I do have a Wacom Bamboo tablet connected. Has anyone else had interference between a tablet and Surface Input Simulator?
It was in Device Manager. Bamboo touch drivers disabled the Virtual Digitizer Controller which was also listed as a device. Flip the switches and rode off into the sunset. good job, me! o/