I have installed monkey talk IDE to test the android apps and when I try to connect it to android emulator/tethred device, I got a warning
An internal error occurred during: "MonkeyTalk". Error starting adb:
Error running adb: D:\android_sdk (aspire921) on
aspire764\platform-tools\adb.exe forward tcp:16862 tcp:16862 error:
device not found
Your phone must be on the same WiFi network as your PC. The app must be running on the phone in order to connect. About your recording issues, I would have to have more information.
I forgot to check the important thing that both the device and pc would be in same WI-FI Network, while trying to execute monkey-talk enabled apps. Now the connection was set successfully to the device.
Related
My development environment is in ubuntu on wsl2 with vscode as editor running on windows using the remote wsl extension. I am running it on a physical android device using the Expo Go app using the tunnel connection on the same wifi network.
Everything works fine from scanning the QR Code to editing the code and it auto refreshes everytime I make changes on vscode. The problem is when I became idle(not making changes) for a short time, the connection somehow times out giving the error:
Cannot connect to Metro.
Cannot connect to Metro screenshot
What should be done here? How to disable the timeout if there's a way?
I am developing an app using React Native and made my server with node.js. For websocket connections I use socket.io
The thing is if I install the app to my android device and my android emulator, only my android device can connect to my local server. They both run the same code. I checked and the emulator has an active internet connection. Weird thing is I have an other app inside the emulator that connects to the same server without any problems using the same connection methods.
Do you guys have any idea why there is a problem like this?
Android emulators have a built in IP to use when connecting to something on your local machine.
If the socket is running on localhost, you want to connect to using the IP address 10.0.2.2 in the emulator.
I'm not being able to debug a Tizen Web Application in a Smart TV. I followed the steps listed here
When selecting Debug As > Tizen Web Application I get the following error message:
'Launching Basicapplication' has encountered a problem
An internal error occurred during: "Launching Basicapplication".
An internal error occurred during: "Launching Basicapplication".
org.tizen.web.editor.configuration.TizenConfiguratorImpl cannot be cast to org.tizen.web.editor.configuration.IMobileConfigurator
I am using Tizen Studio, and I tried it in both Linux and Windows
Any help on this issue will be appreciated
Regards
I installed the TV-extension "Web app. development" & "Samsung Certificate Extension" from the Package Manager to fix this.
Please check your signature again, It may be you are building the signed copy of Tizen project and using a different signature.
I can run my Blank Cordova apps on any windows simulator.
When I try to deploy on my device Lumia 950XL, I have this error message:
Bootstrapper could not connect to the machine. Did try windows Phone (universal) platform and others Windows Options. Same Error message.
Problem solved. My option for developer was not correctly setup. Used the 3rd option not the second.
I'm having an hard time trying to run my Meteor app on my Android device (LG G2).
I googled for answer and didn't find anything like what I encounter. I followed the instuction and everything went fine, added the Android platform to my project and ran it with meteor run android-device. The device LG G2 is plugged with a USB cable to the machine I'm building and running the app with, and the device has USB debugging enabled. Everything seem to be fine, my terminal indicates:
Started proxy.
Started app on Android Device.
I20150530-16:38:11.280(3)? - waiting for device -
Started MongoDB.
Started your app.
App running at: http://localhost:3000/
No error indication, nothing suspicous, but the app doesn't come up on the device. Nothing happens. Anyone has a clue? I tried to give my own IP and port to the command without a change.
You need to set the USB connexion on your android device as "camera". Whith my s4 mini I had the same symptoms and that was the solution.
I'll list what I've done to solve it, because it's a mix of all the solutions I got here.
I'm using Ubuntu, and LG G2 as device.
I created the /etc/udev/rules.d/51-android.rules. file with
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="1004", GROUP="plugdev" inside. (Detailed instructions here on step 3: http://developer.android.com/tools/device.html#setting-up, thank you #ChristianFritz). Pay attention that "1004" is the vendor
ID of LG.
I realised that for some reason I didn't have the ADB on my machine so I couldn't use adb devices and connect with my device. I followed this guide:
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378 to install the missing ADB (linux section).
I got an error: adb server is out of date. killing... which terminated connection between the device to the machine, but after following #yoh advice, I changed my USB connection from MTP to PTP and tried again. This time worked.
Managed to run my app successfully on physical LG G2 after those steps using Ubuntu.