whenever I start any virtual device, it gives this error
invalid command-line parameter: Files\Android\android-sdk\tools/emulator-arm.exe.
Hint: use '#foo' to launch a virtual device named 'foo'.
please use -help for more information
Platform in android 2.3.3, windows xp ....
Main problem is with eclipse IDE, it would not recognise your sdk until you sets path which don't have any spaces, e.g., if your Android home is something like, c:\program files\android, your AVD will not launch, it will through error which you have in your cause, to overcome this move whole Android home folder to single directory path like, c:\android\ , it worked for me.
Related
Prior to today, everything was working fine and I was able to deploy from Unity to specifically an APK. I wasn't able to operate in "Play" mode so I tried updating the Oculus Platform SDK, which proceeded to hang in "Installing..." forever, leading to my current predicament.
What happens:
I hit "download" on anything inside the Downloads section of the Oculus Developer Hub
It hangs saying "Installing..." for hours and does nothing.
Also, when I try to change my ADB Path in Oculus Developer Hub, it "fails" and asks me to try again, but the new value is present every time.
I've tried installing/uninstalling both ODH and Oculus software. I've tried changing the ADB path. I've tried installing and adding JRE and NDK to the path. I'm running out of options here. Does anyone have any advice? This is blocking me from doing development work in Unity.
To avoid issues, ODH (Oculus Developer Hub) must reference the same adb.exe as the one referenced by your Unity Editor.
If, for instance, you are using the Unity Editor 2021.3.1f1 with the standard settings (you didn't changed the default installation path and also installed the Android Build Support module and the corresponding sub-modules), then Unity will use the adb.exe found in:
C:\Program Files\Unity\Hub\Editor\2021.3.1f1\Editor\Data\PlaybackEngines\AndroidPlayer\SDK\platform-tools\adb.exe
ODH has a buggy behavior when trying to change the ADB path (ODH > Settings > General > ADB Path > Edit): when you select the desired adb path from the Detected ADB Clients drop down and click Restart ODH, you get the following error message:
"Unable to change ADB path and restart ODH. Please try again."
Just ignore the error message. Dont' click Cancel, just close ODH and start it again. Then navigate again to the menu where you changed the ADB path, i.e. ODH > Settings > General > ADB Path > Edit. You should now have the path you chose before manually restarting ODH.
My flutter project is run smoothly in my old laptop. But when I use my new laptop, my flutter project can't run in debug mode.
This error
FAILURE: Build failed with an exception.
* What went wrong:
Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the User Manual chapter on the daemon at https://docs.gradle.org/5.6.2/userguide/gradle_daemon.html
Process command line: C:\Program Files (x86)\Java\jre1.8.0_221\bin\java.exe -Xmx1536M -Dfile.encoding=windows-1252 -Duser.country=US -Duser.language=en -Duser.variant -cp C:\Users\ajoris\.gradle\wrapper\dists\gradle-5.6.2-all\9st6wgf78h16so49nn74lgtbb\gradle-5.6.2\lib\gradle-launcher-5.6.2.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 5.6.2
Please read the following process output to find out more:
-----------------------
Error occurred during initialization of VM
Could not reserve enough space for 1572864KB object heap
Picked up JAVA_TOOL_OPTIONS: -Djava.vendor="Sun Microsystems Inc."
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
Is there something missing in the settings on my new laptop? I tried to clean project, upgrade flutter but always fail. Sorry for new
What actually worked for me is, In windows 10 just turn off your mobile hotspot and run the app again. I think it's a glitch/bug in windows 10.
The solution to this problem is deactivating windows hotspot before running build or app compilation.
Don't delete anything or file, just build the app with mobile hotspot turned off.'
its a windows 10 bug that start without any reason. i refreshed my windows and this started
Flutter or Android Applications
The general steps I would use are:
run flutter doctor in terminal
if you are using an emulator make sure it has enough space (often it needs a restart to clear junk files created upon consecutive deploys)
if the gradle files have been modified it is recommended to open them with Android Studio (Android folder of the application). If anything is missing the IDE will prompt you to install the missing dependencies.
Hope it helps
I tried all the above methods but sadly none of them worked. What eventually worked for me was too simple.
first try all the suggested solutions here and if it doesn't work
try to disable mobile firewall, actually I discovered that it's a windows 10 bug because disabling mobile hotspot just until you build or compile your project then you can reenable it without any problem .
Step 1: Open the Registry Editor on your Windows 10 computer. To do this, just press the Windows + R keys on your keyboard. In the Run dialog box, type “Regedit” and hit enter. This will open the Registry Editor window.
Step 2: In the Registry Editor, navigate to the following location:
HKEY_LOCAL_MACHINE SOFTWARE Policies Microsoft WindowsNetwork Connections
Step 3: In the Network Connections key, on the right-side pane, right-click anywhere in the empty area and select New > DWORD (32-bit) Value.
Step 4: Name the newly created registry “NC_ShowSharedAccessUI” and keep its value as “0” to disable the Mobile Hotspot feature on your laptop.
Step 5: To enable the feature, just change the value of the NC_ShowSharedAccessUI registry from 0 to 1 and the feature will be enabled again.
When the functionality has been disabled, the feature will still appear in the Network & Internet settings but it cannot be enabled or configured. To use the feature, the registry needs to be edited again and enable the functionality.
It looks like a memory problem.
In your project folder, Go to android/gradle.properties.
Change the line
From:
org.gradle.jvmargs=-Xmx1536M
To:
org.gradle.jvmargs=-Xmx1024M
Save the gradle.properties file and try to run debugging again.
That Worked for me :)
Usually it Is bcoz of the .gradle file in C:drive.
1.Locate to the .gradle folder (usually in C:\users\your_username)
2.Delete the .gradle folder once located.
2.Locate to your flutter project folder
2.Locate to android
3.Run gradlew clean
4.Run gradlew build
5.now run your app...It worked for me
I tried all the above methods but sadly none of them worked. What eventually worked for me was simple.
There has been a lot of problem with emulator configuration and sometimes it crashes for a lot of reasons. For the above problem what I recommend is, delete the current emulator but remember the settings like API version and all and make a new emulator.
This worked for me fine!
I'll post what solved for me.
flutter clean
flutter run
Close Android studio
Delete your ".gradle" folder
Open android studio as administrator and allow project to build.
For my case i had --no-sound-null-safety in the Dart: Flutter Additional Args ( go to vscode settings under extensions dart ). I deleted it, deleted the web folder in the project ( i was working on the app only ) then reloaded vscode. the error was gone afterwards
go to C:\Program Files\nodejs
Open npm, npm.cmd, npx, npx.cmd
then change the prefix -g to prefix --location=global
still if this did not work,
go to android studio click on build, then click clear project.
I also faced this issue and this step resolved problem. Still if this did not work out let me know.
Non of the solution in here worked for me. running my vscode or android studio as an administrator solved the problem.
Go to file/setting/build,execution,deployment/gradle, and there where Gradle user home: pass static address.
For example, my address is C:/Users/Admin/.gradle.
After applying if runs OK.
There is a simple solution.
Uninstall the app from your device .
Then restart the PC .
First of all Uninstall the application from emulator.
then wipe all data from the emulator.
Sometimes turning off mobile hotspot will do the work.
After turning off if not work then restart the pc or a laptop. Don't turn on mobile hotspot and run flutter run.
First of all, I'm a total newbie to all of this stuff and I was pushed into it.
Acording to these two topics:
Starting the Android emulator in SDK tools, revision 12, and
Invalid command line parameter when Android executes the solution to "invalid command line parameter when android execution" problem is adjusting the spaces in the path, but I don't know how.
I have Windows 7, Eclipse IDE for Parallel Application Developers with ADT Plugin.
The path to emulator.exe is: C:\Program Files (x86)\Android\android-sdk\tools
You have an option to change the SDK path. The SDK gets installed in C:\Program Files\Android by default. Now launch Eclipse -> Window-> Prefrences -> Android. Here you can browse to your android sdk location. I was successfully able to go through installation by doing this step and my sdk is installed in Program Files.
The above step is applicable to Android SDK version 15.
Instead of re-installing, you can use the subst dos command to create a local drive alias.
Subst z: "c:\program files (x86)\android"
You need to reinstall Android SDK to shorter path with no spaces. I remember reading the Android SDK recommendation, where the path with spaces is described as wrongdoing.
You can not even have it there in Program Files in first place, because the installer (not zip, but recommended installer) picks the C:\AndroidSDK as suggested location.
I think there is no workaround for this other that reinstall
I'm just starting to use Eclipse and ADT and I have some issues, the Android Emulator don't start :
[2011-07-10 15:32:25 - Android_FirstApp] ------------------------------
[2011-07-10 15:32:25 - Android_FirstApp] Android Launch!
[2011-07-10 15:32:25 - Android_FirstApp] adb is running normally.
[2011-07-10 15:32:25 - Android_FirstApp] Performing samr1.Android_FirstApp.Android_FirstAppActivity activity launch
[2011-07-10 15:32:25 - Android_FirstApp] Automatic Target Mode: launching new emulator with compatible AVD 'Android2.1'
[2011-07-10 15:32:25 - Android_FirstApp] Launching a new emulator with Virtual Device 'Android2.1'
[2011-07-10 15:32:26 - Emulator] PANIC: Could not open: C:\Users\Sam\.android/avd/Android2.1.ini
The path isn't correct, though the path in Android2.1.ini is correct. The User folder is located in an another disk.
How can I modify the start path of Android Emulator ? I can't find where.
Thanks
EDIT :
I found that graphical AVD Manager creates AVD directory inside C:\Users\.android\ on Windows 7 :
Default location of AVD files
But using Command Line doesn't work.
So i moved my AVD files in C:\Users\Sam\ and now it works.
This is a bug in the ADT Plugin. For a workaround until it is fixed use a NTFS symbolic link.
I have a C: drive for windows 7 and a D: drive for all my work and data. After installing windows 7 I relocate all my special folders from C:\Users\John Doe to D:\John Doe. The ADT Plugin is trying to load the emulator from C: when it and the configure files are on D: (PANIC: Could not open etc.). NTFS can get the ADT Plugin to read from D: using a NTFS symbolic link. Open a command prompt in C:\Users\John Doe (obviously use your user name), use the mklink command.
mklink /J "C:\Users\John Doe\.android" "D:\John Doe\.android"
Now when the ADT plugin is trying to reference .android on C:, NTFS sends the request to D: and the emulator starts correctly.
Create a environment variable called: ANDROID_SDK_HOME and set it to C:\Users\Administrator
Open Eclipse > Window > Preferences and click in Run/Debug and String Substitution
Add a new variable called: user.home and set it to C:\Users\Administrator
Create an AVD and run it.
It should work now.
The configuration files for your emulator might have been saved by AndroidSDK and AVD Manager some where else in your hard drive.
Do the following:
First search for the .android folder on you harddisk.
After you find that, move the .android folder to your user root directory - which may be "C:\Users\hallo\" in your case.
These type of project creation errors(with cause and solution) is described here.
The configuration files for your emulator might have been saved by AndroidSDK and AVD Manager some where else in your hard drive.
Do the following:
First search for the .android folder on you harddisk.
After you find that, move the .android folder to your user root directory - which may be "C:\Users\something\" in your case.
Other Method
Check the location of old folder you can open eclipse Navigate to Windows--> Preferences-->Android-->Expand it and Select Build
Find the Value of Default Debug keystore and you will know your .android folder location.
Then mklink /J "old folder location" "C:\Users\Something\"
if anyone is interested on the same problem in Linux (Ubuntu 11.10) the solution is NOT run Android SDK Manager as root. Aparently, SDK expects to be runned by a regular user, and it tries to work with the main user folder, that's why the error. This is what I suspect.
This worked for me by running eclipse as root ( in Ubuntu ), my be run as administrator will work
i am having the same problem described in the following post "Android emulator reports unknown virtual device" Why does the Android emulator report "unknown virtual device", when the device is in my user directory? and have followed all of the instructions in an attempt to resolve but still i cannot run my AVD.
I only have one drive on my Windows 7 machine (C:) and the AVD is being created in the correct location -> C:\Users\MyUser\.android
Ive also tried to setup an environment variable "ANDROID_SDK_HOME"
The actual error is:
emulator: ERROR: unknown virtual device name: 'my_AVD'
emulator: could not find virtual device named 'my_AVD'
Can someone please help me?
For another reason i had to re-format my pc. After a quick rebuild its working fine now. I think the problem happened because in the previous installation of windows, i was playing around with HDD's. Somehow this had caused problems..
Solution: you should have a copy od .android in C:\<your user name>\.
Please try the below steps to solve the above issue -
in task manager kill adb in process
in android sdk folder .. /tools/ run adb kill-server in command line
Check the avd folder name in " ../.adroid/avd/" - say it is "avd1"
run command "emulator -avd avd1 " under android folder "../tool/" in command line
it will start the avd1 device
Now start the eclipse and run your project with setting the "manula" option in configuration.
It will ask for choosing the avd between "avd1" and the existing list of avd's in eclipse if any. You choose "avd1" as it is already running.