This question was somewhat asked previously but it doesn't appear there was a resolution.
For testing purposes, I am trying to use an app on the Android emulator that records from the mic. I believe this is possible -- but correct me if I'm wrong.
Using the following combinations, I have been unsuccessful in running the Speech Recognition app (app closes when I hit record with Sorry! message):
host os - OSX lion / Fedora
android os - 2.0, 4.3
My mic is working on the host machine. I have enabled audio recording and playback in the AVD.
Related
I activated virtual microphone on Android emulator by enabling toggles at the Extended Controls > Microphone path in emulator settings but when I start recording audio by Google Assistant and other recording apps to test it, the emulator receives no audio signal from the machine inputs. My operating system is macOS Catalina 10.15.4 and the Android Studio version is 3.6. Also, my laptop microphone works correctly and I checked it with an external Headset and other MacBooks but the problem didn't solve. How could I fix it?
I am writing an Android App which needs to use the devices microphone.
To test my app, I installed various virtual devices using the AVD Manager of Android Studio.
However, I realise that for none of the virtual devices that I installed, the microphone was working.
I am using Android Studio 3.6.2 on MacOS Version 10.15.4 (Catalina).
I'd like to deploy my code on any virtual device in Android Studio and record sound via my MacBookPro's microphone.
Can anybody please let me know how I can install such virtual device and link the emulated microphone to my MacBookPro's microphone?
Every android emulator has the option of MicroPhone which can be found in the running emulator's setting. You can configure your emulator and setup the microphone there:
I recently enrolled my Pixel XL for Android Beta program. After the update to Nougat 7.1.2 my device is not detected properly in Android Studio Linux.
I get something like this in AVD monitor
HT6A70201284 [null]
But it was working on my windows desktop, I tried it on other linux devices and got the same issue. I came across a post mentioning about the driver support, so I updated my SDK to Android O preview, but it had no use.
Another strange behavior is when I turn of the debug mode in phone, it gets detected by my linux system, other posts state the same driver issues, but I am not able to figure out exactly which driver and from where I am supposed to install.
Just a simple solution (Working on Nexus 5X, 7.1.2),
Developer options
Select USB configurations
Choose MTP (Media Transfer Protocol)
OR
If notification panel shows "USB charging this device"
Tap on it and just select "Transfer files"
Device detected.
I am not sure if anyone else faced this issue, but after trying several stuffs, the problem seems to be solved temporarily.
Generally I use my device in charging mode while developing the apps, but after the update Android studio detects the device in Data Transfer Mode only, somehow, USB mode charging has some bugs in preview release and couldn't be detected by Android Studio.
I am trying to run "unity remote 4" test project (http://u3d.as/content/unity-technologies/unity-remote-4/7PZ) on Unity Free for Mac.
I have "Unity Remote 4" installed on Samsung galaxy.
I have android SDK installed, adb devices command returns 0019e6197e378e device.
I have turned on all necessary developer options on the phone.
When I press Play in Unity, it says accepted incoming socket.
But nothing shows up on app but the welcome screen asking me to press Play in Unity.
Here are the steps you might be missing
Go to Edit Menu:- Project Setting:- Editor.
Under Unity Remote: Device choose "Any Android Device".
Connect your android device through usb cable.
Run unity Remote on your android device.
Now press play button in unity.
It will launch your game in android device.
Make sure no android emulator (bluestack, genimotion etc) is running in background. Sometimes priority of emulator gets higher than device and operations like "Build & run" or debugging etc starts producing their outputs on emulator rather than device :)
I have just started playing around with Android development and looking to use PhoneGap.
Using their getting started guide (http://phonegap.com/start#android) I have got to the final step, which is running the app in an Android Virtual Device.
I have set some up and all of which cause a BSOD when ever I try to run it. I am using Windows 7.
The error message displayed on the BSOD is:
STOP: 0X0000008E
emBDA.sys - Address 8EB5320C base at 8EB50000
Thanks!
I had the same problem with file emBDA64.sys. Probably it is the same problem that I had, but you have 32-bit driver not 64-bit. This file is part of probably PVR-TV USB device. I had to turn off this device and emulator started to work well. Check, what device is this file a part of and turn off this device when using emulator. Probably it is extrnal TV tuner too.
Confirming kzez1986's suggestion that the BSOD might have to do, or always has to do (?) with a(n internal) USB TV tuner.
My Win7-64 system suffered from the same BSOD after a brand new install of the Android SDK and starting a new AVD.
When disabling a USB device, in my case called 'DVBT Hybrid TV Device' in the 'Sound, video and game controllers' section of the windows Device Manager I could now start the Android AVD without problems.
Note: Because I'm on a 64bit machine, in my case the BSOD error was pointing to emBDA64.sys.