tag:blogger.com,1999:blog-8349059454260069992.post1409515963608144673..comments2022-03-26T08:15:53.431-05:00Comments on Techno Detritus: Android "Hello World": a Tale of WoeAnonymoushttp://www.blogger.com/profile/11568514979551543713noreply@blogger.comBlogger13125tag:blogger.com,1999:blog-8349059454260069992.post-85711925813185096292013-06-02T14:42:04.245-05:002013-06-02T14:42:04.245-05:00(Some years later)
Great Job!
I found this artic...(Some years later)<br /><br />Great Job!<br /><br />I found this article via<br />http://stackoverflow.com/questions/2841766/possible-to-change-where-android-virtual-devices-are-saved<br /><br />I have the issue that I have two partitions on my harddrive so the "Android Virtual Device"'s pollute my system partition and I don't like to resize it.<br /><br />Finally there are two solutions to solve this issue. The first one is to create a symbolic link from the path the AVD's are located normally to the path someone likes to store them in realtime. The second one is, how you already mentioned, to set the environment variable "ANDROID_SDK_HOME".<br /><br />I prefer the first one but according to your article here is the Windows solution for the second issue you can store with the installation files together.<br /><br />Use the "SETX" windows command to set a user variable. I found it in the discussion as follows.<br /><br />http://stackoverflow.com/questions/3803581/setting-a-system-environment-variable-from-a-windows-batch-fileAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-8349059454260069992.post-73963067135490904712012-05-11T08:31:17.944-05:002012-05-11T08:31:17.944-05:00Emulator and avd-manager are indeed a pain, althou...Emulator and avd-manager are indeed a pain, although I didn´t have problems installing the full package, creating an avd and starting the emulator at first.<br /><br />The emulator was very slow, but I found something on stackoverflow, that was supposed to make it faster, but didn't work. I tried creating a new avd with different settings. But the tool didn´t react for really long ( > 20 min). Killing the process maybe wasn´t such a good idea, because after I was not able to delete my first avd, mksdcard was still using it, but refused to be killed.<br /><br />However, having the avds under your user account, is not a good solution really. System shut-down takes years with only one avd, if your profile is domain based. But after that I was able to delete the 18Gig big avd, and was really annoid, or was it android.<br /><br />Finally I got the emulator working by changing the android.bat in my android-sdk\tools folder. Replacing "call %java_exe%" with "call %java_exe% c:\somePath" (found that in some other helpful post). Then started the avd-manager again, and believe it or not it created the avd at that place. <br /><br />But then the emulator wouldn´t start it, because that thing still looks for the ini under c:\users\....! So I copied the avd´s ini file to the .android\avd folder under c:\users\myAccount. Not before having tried starting it with all sorts of commandline args, but it never did it properly.<br /><br />Maybe now after a day or so wasted reading unrelated articles and documentation wihtout succes, I can start using the emulator as expected.<br /><br />Really liked Your article and I must agree, commandline tools suck, especially if they require an armfull of arguments.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8349059454260069992.post-56017631066756802272012-04-08T13:46:34.046-05:002012-04-08T13:46:34.046-05:00Grmbl... in my case it picks up my redefined user ...Grmbl... in my case it picks up my redefined user directory fine in the AVD (G:\myusername). Except that when it starts, it starts the correct AVM but at the wrong location: C:\users\myusername\.android and then it returns to forward slashes.<br /><br />Someone did NOT check this.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8349059454260069992.post-38970484030965783002012-03-13T16:25:20.979-05:002012-03-13T16:25:20.979-05:00You make a good point, John.
Curiously, I found a...You make a good point, John.<br /><br />Curiously, I found a lot of the same pain points working with XCode and Objective-C. Apple has improved their deployment (both to devices and to the App Store) significantly since my last attempts a couple years ago.<br /><br />I have to say that Microsoft still wins hands down on the maturity of their development tools, and that I continue to be impressed with Windows Phone 7. (But why the heck don't they have a screen shot function on the device?!?)Anonymoushttps://www.blogger.com/profile/11568514979551543713noreply@blogger.comtag:blogger.com,1999:blog-8349059454260069992.post-80461873224685135032012-03-11T20:46:15.895-05:002012-03-11T20:46:15.895-05:00I can see that you haven't had the displeasure...I can see that you haven't had the displeasure of working with open source tools. In the FOSS world, almost everything is as unfinished and unpolished as that, and an hour or two of googling before being able to get a piece of software running is considered normal.<br /><br />You just have to deal with the fact that it's a different culture. Also, Android is a child of Linux, where the command line is considered the pinnacle of user interface design, but at least Android makes a good job of not exposing end users to the CLI.Johnnoreply@blogger.comtag:blogger.com,1999:blog-8349059454260069992.post-65873779643789604272012-01-13T05:12:03.437-06:002012-01-13T05:12:03.437-06:00I have been fighting with this for several days no...I have been fighting with this for several days now and I FINALLY got my AVD running now it seems. At least it popped up the virtual device, now I just need to figure out why the hello world app isn't running. But thanks... I was starting to give up completely.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8349059454260069992.post-61270328138452143882011-12-31T08:01:00.873-06:002011-12-31T08:01:00.873-06:00Agreed, commandline WTF...Agreed, commandline WTF...Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8349059454260069992.post-50092995870865722662011-10-12T06:41:50.464-05:002011-10-12T06:41:50.464-05:00If anyone is having problems with the Android SDK ...If anyone is having problems with the Android SDK Path. Instead of using <br /><br />C:/Program Files/Android<br /><br />use<br /><br />C:/PROGRA~1/Android<br /><br />Eclipse doesnt like spaces in this folder name, so eclipse cant see the SDK. Just a wee tipAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-8349059454260069992.post-67742081350301545242011-06-24T15:23:14.436-05:002011-06-24T15:23:14.436-05:00Ok everyone,
After some fiddling around I managed...Ok everyone,<br /><br />After some fiddling around I managed to figure it out. Hopefully here is a clear explanations of the issue and what you need to do to solve it.<br /><br />First of all, this happened to me because my folder in windows has non-standard characters (é in my case).<br /><br />What you need to do is first find what is the abbreviated path to your folder in windows. You do this by going in the command line to the parent folder of the folder with the strange characters, then you type dir /x. This will show you the abbreviated name of your folder. Make a note of it.<br /><br />Then you go to and add an environment variable ANDROID_SDK_HOME as mentioned above and its value will be the abbreviated version of your folder. <br /><br />Restart Eclipse if you had it open. Delete any AVDs that don't work. When you open the dialogue to create a new AVD (the Android SDK and AVD manager) you should see that just above the list of AVDs it says: "List of existing Android Virtual Devices located at: ...." and this should show the abbreviated version of your folder. If not, it hasn't worked, so try again.<br /><br />I hope this helps.<br /><br />JoséJoséhttp://josebb.comnoreply@blogger.comtag:blogger.com,1999:blog-8349059454260069992.post-1116025074151338272011-04-05T10:08:12.302-05:002011-04-05T10:08:12.302-05:00I feel your pain I chose an android project for my...I feel your pain I chose an android project for my dissertation and I am about ready to throw both my laptop and phone out the window!!Saint-Emilyhttps://www.blogger.com/profile/09546324442463449123noreply@blogger.comtag:blogger.com,1999:blog-8349059454260069992.post-52889525329935189222011-04-04T09:37:47.542-05:002011-04-04T09:37:47.542-05:00Hi there !
Thanks a lot for your very useful blog...Hi there !<br /><br />Thanks a lot for your very useful blog.<br /><br />Nevertheless, I didn't solve my issue.<br /><br />My problem is that my first name is "Régis" (with an accent) and that the AVDs cannon be found in C:\Users\.android\avd at runtime.<br /><br />So I have got the errors:<br /><br />[2011-04-04 16:10:11 - Emulator] emulator: ERROR: no search paths found in this AVD's configuration.<br />[2011-04-04 16:10:11 - Emulator] Weird, the AVD's config.ini file is malformed. Try re-creating it.<br /><br />I added a new Windows user environment variable:<br /> Variable name: ANDROID_SDK_HOME<br /> Variable value: C:\Users\Régis<br /><br />But still have the error !<br /><br />Actually, I even don't understand how just the addition of this environment variable can solve the issue. Is there another operation to do ?<br /><br />Please answer to regis.andre@2001.ecam.fr<br /><br />Thanks a lot for your answer.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8349059454260069992.post-56637915000496098602011-04-01T02:44:04.890-05:002011-04-01T02:44:04.890-05:00You must not forget about the Android SDK vs. Java...You must not forget about the Android SDK vs. Java JDK issue! When you've got the Java JDK installed (which is obligatory to code for Android) Android SDK still won't install, saying you don't have the JDK installed (that's right!).<br /><br />The workaround is to click the Back button in the very same window and then click the Next button again (that's right!). A miracle happens - the SDK can see the JDK without any problems!Wally QWERTYhttps://www.blogger.com/profile/05009374955076053365noreply@blogger.comtag:blogger.com,1999:blog-8349059454260069992.post-16076651318722483542011-02-21T14:16:25.090-06:002011-02-21T14:16:25.090-06:00Yeah, finally I've gotten it to work. My user ...Yeah, finally I've gotten it to work. My user path contains non-alphanumeric characters, so this shit couldn't find the files when I tried to run the virtual device. It started to work when I moved the virtual devices folder (.android) to another path and created that enviroment variable. Jobs bless you!Jesús V. Garcíahttp://twitter.com/Isotropynoreply@blogger.com