I'm struggling with Android emulator version 26.0.0.0. The tools are managed by the Android Studio (2.3.1). All this running on Fedora FC25 with latest updates.
I can't seem to get the ARM emulator to have network access. Same works fine with x86/x64, but not arm (or arm64).
It looks like I ran to the end of my abilities to debug what's going on, and on where to continue digging.
On arm : no ability to resolve names, no ability to connect to the outside network. I'm running nc from adb shell to check the connectivity. On an arm emulator, I get timeout on host lookup when using host name, and no route to host when attempting to connect by IP. Browser application also can't connect. I run strace on the emulator and I don't even see attempts to connect to the DNS server.
On x86 : everything works. However I did have to add -dns-server option before it started working.
Debugging The most I did was running strace for both the emulators and examining the difference. AFAIU, there is an I/O thread that gets to make the requests, and it looks like it's not picking up the requests in arm case. Or the requests are not properly deposited. The thread seems to be OK otherwise, it iterates between polls and futex locks.
Of course, my whole point is to run ARM emulators (needed to debug certain ARM native code).
Debug outputs (I did remove multi-touch connection errors from the output):
arm
x86
Any pointers on where to dig, or what I may be doing wrong is greatly appreciated. I can post full trace files from running both as well.
update your Android emulator to v26.1.0, it will work fine.
Related
I'm trying to flash my code to NUCLEO-L432KC(STM32L432KC) by TrueStudio. It was failed.
[
It looks tool cannot detect ST-Link probe. I just connected it by USB cable from PC (Windows10). Code and project file are generated by STM32CubeMX.
What is the missing? What should I do?
I have confirmed following.
From STM32CubeProgrammer GUI, it cannot detect ST-Link connection.
From STM32CubeProgrammer CLI, it can detect S/N of ST-Link. But cannot connect.
From STLinkUpgrade 3.3.0, it can detect device and S/N. Also can update to V2J33M25.
From IAR Embedded Workbench, it can build and flash code and debug. No problem at all.
It looks same result using by STM32F4 Discovery kit for STM32F429 MCU.
Make sure you don't have another program such as ST-LINK utility running while you use the debugger. Some versions of the ST-LINK "hogs" the debug pod access and other programs then would have trouble connecting to it.
Install the drivers https://www.st.com/en/development-tools/stsw-link009.html
Choose the correct micro in the debug configuration window
I have been running CTS tests (Android L, CTS v7) on Intel Baytrail based devices.
Host side setup is:
1.Ubuntu Linux 14.04 LTS.
2.Open JDK 1.6/1.7
While running CTS tests I face below frequent issues:
Tests get stopped after the device gets rebooted after 200 tests as per CTS tradefed framework.
I see a huge number of pseudo failures (generally not seen by other team when run at other location).
ADB does not work with super speed ports.
Here are the possible reasons for the issues you are facing:
Device Presettings should be done in accordance to Google Recommendations:
https://source.android.com/compatibility/cts/setup
Check with the wifi connected to device is consistent during execution
Check out the display doesn't turn off during execution.
I'm trying to deploy my first Windows Phone 8 app to my brand new Lumia 920, after getting everything up and running on the emulator, but I'm running into the following error during deployment:
1>------ Deploy started: Project: AudioFilteringPhone, Configuration: Debug ARM ------
1>Deploying C:\Users\<username>\Documents\Visual Studio 2012\Projects\AudioFiltering\AudioFiltering\Bin\ARM\Debug\AudioFiltering_Debug_ARM.xap...
1>Connecting to Device...
1>Optimizing for device...
1>Installing the application...
1>Deployment of application to device failed.
1>Error writing file '%FOLDERID_SharedData%\PhoneTools\11.0\Install\{29b31259-9af9-47a5-9891-c3098315d3d8}\AudioFiltering_Debug_ARM.xap'. Error 0x80070003: The system cannot find the path specified.
If I manually try to deploy using the Deployment tool, I get the same error. Does anyone know what the cause of this is and how to alleviate it? This happens even if I just start a new WP8 app and immediately try to deploy it, so it's something wrong with my environment, not my application configuration.
I had exactly the same problem, but solved it by simply rebooting the phone. No software updates were required.
It turns out that there were software updates that needed to be installed. If anyone knows a way to find out the names of the updates applied, I will post them here, otherwise all I can say is that I had to update to OS version 8.0.10211.204.
This also can be because of wrong USB cable or port. I have a long cable for charging which works with android devices, but doesn't with WP.
Or maybe using another USB port helped.
I have set up the board according to the RX cpu example in eclipse, and everything seemed to be working fine till I wanted to get the example running on the board. When I click the option to hardware debug, I get an error saying "Error launching GDB server. Check installation".
Am I to re install eclipse, or the GCC toolchain for the RX cpu, or anything else?
I don't know anything about your specifics (that is Renesas or the RX62N). I do use eclipse for embedded work. Typically on a new platform I would make sure I can build and download a release version first. Once you have that working then see if you can get a Debug build and the debugger running. On the platforms I am used to, you have to put in hooks (typically just a single call) to enable the debugger. For exmple on the NetBurner the debugger can run over the serial port or Ethernet so the call has to specify which version you want to use. I know other platforms use JTAG debuggers etc, Typically a dev kit for the board comes with a manual that details how to get the debugger working. I doubt that you need to reinstall anything you just need to get the configuration set up correctly.
I am new to both the android and android development so I'm not on familiar ground here.
When I start the emulator I have no service. Therefore I have no internet connection on the emulator.
I am running Windows 7 and I generally run the emulator via eclipse.
My host machine is connected to the internet via the Local Area Network. There is no proxy.
I have tried:
Disabling all network adapters except for the Local Area Network [link]
Running the emulator from cmd line with: emulator -avd -dns-server 8.8.8.8
Reinstalling the SDK Tools 9 and Platform Tools (rev 2).
Restarting the machine! :P
Is there a setup needed to specify to simulate a 3G connection? Or could this be a Windows 7 permissions issue? Or am I doomed like these folks: link link
Ah! found the solution.. I uninstalled the entire SDK and reinstalled it to C:/Android. I deleted the C:/Users/[your-name]/.android folder and recreated an avd. Voila.. Something in there worked!
[edit]
Actually it looks like you have to keep restarting the emulator until it connects. I will often get no service so I restart a bunch of times till it works.
I found that 'Airplane Mode' was enabled by default in the standalone android emulator - this may also be the cause in the sdk version. Turning this off (by holding down the red power button until the menu came up, and then toggling the airplane mode button/section) allowed the emulator to 'find service' and connect properly through the LAN.