I am a new linux user and when I installed eclipse and sdk for android in linux.I get below error
when I start emolator and wait for 15 minute. I ran my project.my project run very good and below message is shown.
[2013-05-30 09:53:13 - RamzNegar] Android Launch!
[2013-05-30 09:53:13 - RamzNegar] adb is running normally.
[2013-05-30 09:53:13 - RamzNegar] Performing com.elmos.ramznegar.MainActivity activity launch
[2013-05-30 09:53:13 - RamzNegar] Automatic Target Mode: Unable to detect device compatibility. Please select a target device.
[2013-05-30 09:53:22 - RamzNegar] Uploading RamzNegar.apk onto device 'emulator-5554'
[2013-05-30 09:53:23 - RamzNegar] Installing RamzNegar.apk...
[2013-05-30 09:53:39 - RamzNegar] Success!
[2013-05-30 09:53:39 - RamzNegar] Starting activity com.elmos.ramznegar.MainActivity on device emulator-5554
but i cannot show anything in emolator
I see below image
if answer is ~my emolator not run yet~;why my emolator dont run
how i can solve this problem?
for the first time that you run emulator it will run very slow
and when you run your app ,eclipse didnot get you error
I think this is a bug for google
I hope that speed of emulator will be improve
Related
I found a tutorial that works too.
I have only one problem. The server does not start in autostart.
"V Rising" is a game that unfortunately only runs on Windows Server. My server runs on Linux (Ubuntu 18.04). I have to start it with "Wine" and "xvfb-run". My other game servers run normally with cronjob. V Rising doesn't work with cronjob, or systmctl. "Wine" and "xvfb-run" start as usual. The V Rising Server also starts, but crashes immediately and leaves a log.
FMOD failed to initialize the output device.: "Not enough memory or resources. " (43)
RtlLookupFunctionEntry returned NULL function. Aborting stack walk.
0x000000018050f71c (unityplayer)
0x0000000180514843 (unityplayer)
...
Unable to initalize any audio device (even FMOD nosound device), please check your audio
drivers and/or hardware for malfunction
RtlLookupFunctionEntry returned NULL function. Aborting stack walk.
0x000000018050f71c (unityplayer)
0x0000000180514843 (unityplayer)
...
With this script I start the server.
cd /home/steam/.steam/steamcmd/v-rising
export WINEARCH=win64
xvfb-run --auto-servernum --server-args='-screen 0 640x480x24' wineconsole ./start_server_example.bat
This script works if I start it myself in the terminal. The server starts and works. Unfortunately not in autostart. If I close the terminal (Putty), then the V Rising Server is terminated. Therefore I need the autostart.
Why doesn't this work in autostart?
Using Android Studio 1.5.1 in a win7 ultimate sp1 and in a Mac mini 10.11.3 fully updated.
I have a number of Samsung units for testing my app development incl JNI and this week my private Samsung Galaxy S4mini (Kitkat) died physically so I got a new Samsung Galaxy J5.
However the J5 (lollipop) refuses to be debugged in native mode. Does not matter the app, fails also with Hello-JNI.
The J5 also have some odd java bugs like in a AlertDialog (with stacked linear layouts) linearLayout.addView(anotherLinearLayout); just crashes?? Also I have an odd JNI-bug, I like to debug. And both "bugs" works without crashing in my other devices my old S4mini and a TAB4 Kitkat and a TAB3 and S3mini.
However I found the TAB4 also refuses native debugging. Both the TAB4 and the J5 works fine in (non-native) app-debugging. All other units debugs native no problem, just switching unit on the cable and run, works fine?
Is there something missing in the J5 and TAB4 for making native debugging available?
The debug error message is (I tried everything I could find):
Target device: samsung-sm_j500fn-0af60463
Installing APK: C:\Users\JB\AndroidStudioProjects\HelloJNI\app\build\outputs\apk\app-all-debug.apk
Uploading file to: /data/local/tmp/com.example.hellojni
Installing com.example.hellojni
DEVICE SHELL COMMAND: pm install -r "/data/local/tmp/com.example.hellojni"
pkg: /data/local/tmp/com.example.hellojni
Success
Launching application: com.example.hellojni/com.example.hellojni.HelloJni.
DEVICE SHELL COMMAND: am start -D -n "com.example.hellojni/com.example.hellojni.HelloJni" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER
Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.example.hellojni/.HelloJni }
Warning: debug info can be unavailable. Please close other application using ADB: Monitor, DDMS, Eclipse
Restart ADB integration and try again
Waiting for process: com.example.hellojni
DEVICE SHELL COMMAND: run-as com.example.hellojni mkdir /data/data/com.example.hellojni/lldb
Error while launching debug server on device: com.android.tools.ndk.run.DebuggerContext$StartServerException: java.lang.IllegalStateException: run-as is broken (please see http://b.android.com/187955 for details)
I am trying to deploy my android app from eclipse on to my blackberry Z10 running 10.0.9.422 and i am unsuccessfull at it.
Here is the actual error that i am receiving.
Failed to deploy project XXXX
Info: Sending request: Install
Info: Action: Install
Info: File size: 8659959
Info: Installing ...
Info: Processing 8659959 bytes
Info: Progress 0%...
Info: Progress 49%...
Info: Progress 50%...
Info: Progress 100%...
actual_dname::com.xxx.xxxx.testEPPwDTJahv0UbAeaecXksgI
actual_id::testEPPwDTJahv0UbAeaecXksgI
actual_version::1.0.3.0
result::failure -9
After this error, I could see the app icon on my Z10, but when i try to access it, it says' Initializing. Please wait...' and the app crashes thereafter.
What does failure -9 indicate and any idea on what's the issue/resolution might be?
Any help is greatly appreciated.
I was able to fix my problem after doing little research and finding the unsupported libraries for my app. I figured out the unsupported libraries using the apkbarVerifier tool.
My app was using com.google.android.maps package. So, I edited the android manifest file to reflect the below line.
<uses-library android:name="com.google.android.maps" android:required="false" />
After this change, even though the 'Verify apk' option from eclipse is showing me the same warnings, I was able to deploy the app to my Z10 and had it to work.
Basically, failure -9 on deployment means that the app contains an unsupported library.
I have a web role that I'm trying to run locally using the emulator. I have it working on another computer, but I cannot get it working on a different one, and have gone as far as to reformat it and start from scratch.
When I launch the site from Visual Studio, Chrome shows the following message:
This webpage is not available
The connection to 127.0.0.1 was interrupted.
There is also an error code listed at the bottom:
Error 101 (net::ERR_CONNECTION_RESET): The connection was reset.
One interesting thing from the build output are these lines:
Starting process 'C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Extensions\Microsoft\Windows Azure Tools\v1.8\Debugger\WindowsAzureDebugger.exe' with arguments '"C:\Program Files\IIS Express\iisexpress.exe" /trace:error /config:"C:\Users\brian\AppData\Local\dftmp\Resources\159c7254-b7d0-4076-a4fd-820b00feca5f\temp\temp\RoleTemp\applicationHost.config" /site:"deployment18(27).AzureApp.MyApp.Web_IN_0_Web"'...
Process 'C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Extensions\Microsoft\Windows Azure Tools\v1.8\Debugger\WindowsAzureDebugger.exe' exited with exit code 0.
If I run C:\Program Files\IIS Express\iisexpress.exe" /trace:error /config:"C:\Users\brian\AppData\Local\dftmp\Resources\159c7254-b7d0-4076-a4fd-820b00feca5f\temp\temp\RoleTemp\applicationHost.config" /site:"deployment18(27).AzureApp.MyApp.Web_IN_0_Web" from the command line, I get the following message:
The system cannot find the file specified.
Unable to start IIS Express in background.
I have no idea what file it cannot find, but I've verified that the config file I'm passing does in fact exist. Anyone have a clue what's going on here??
While I can not tell you what could be the actual root cause of your problem I can suggest a few ways to troubleshoot it:
Try changing IIS Express to Full IIS and see if it changes the behavior. You can do it by going to your Windows Azure Application project properties and look at "Web" option.
Try running application without debugging it
Launch CSrun at command prompt with /launchDebugger parameter of the /run option to verify that debugger does run without any issue
Try using IE as default browser
Clean your dftemp folder completely for any residual configuration and then launch Azure Emulator separately to verify there are no issues
Procmon "http://technet.microsoft.com/en-us/sysinternals/bb896645" may help you find the file that is missing...
Hopefully someone stumbles upon this answer with similar symptoms. When removing in role caching the <dataCacheClients> section was removed from . Somehow there was a left over <dataCacheClients> section left in the web.config. Everything and compiled and deployed to the emulator successfully. However, the role would fail to start since applicationHost.config was missing.
The fix was simply remove the unnecessary <dataCacheClients> section from the web.config file.
I've installed REDHAWK 2.0.0 from rpms on CentOS 6.7, run shell scripts as required, configured omniORB as required, updated SDRROOT permissions as required, and run cleanomni from a terminal command line, but cannot get REDHAWK_DEV to launch in the REDHAWK IDE. Right-clicking on Target SDR > Launch Domain... brings up the "Launch Domain Manager" dialog box with: red 'x" over the label 'Domain Manager'; default Device Manager visible and selectable; and "OK" button greyed out.
Attempting to connect via right-clicking REDHAWK_DEV > Connect throws error: 'Connecting Domain' has encountered a problem. Failed to connect to REDHAWK_DEV', and Details>> gives:
org.eclipse.core.runtime.CoreException: Error while executing callable. Caused by org.omg.CORBA.ORBPackage.InvalidName'
Any ideas? Thanks in advance!
You should be able to check the error by hovering over the red x marker in the launch domain dialog. But it's likely one of two problems:
Stale info in the naming service (try cleanns at the command line, then re-open the dialog), or
The naming service isn't running (try stopping it, clearing out /var/log/omniORB, and starting it)
The other issue you mentioned (right-click, "Connect" from context menu) is to connect to an already running domain. It doesn't launch it.
Thanks for that advice. But hovering over the red 'x' does not make visible any dialog box or tooltip.
I removed the files error.log, omninames-avl.bak, and omninames-avl.log from the directory /var/log/omniORB, ran cleanns, cleanes, and cleanomni, stopped and restarted both omniNames and omniEvents.
But none of these procedures had any effect on the symptom; the default domain is still visible and selectable, but not launchable.