I am just starting to learn cocos2d-x for Android, and understand how to create a new project (using create-android-project.sh), compiling the native code (using build_native.sh), then importing it into Eclipse as a new Android project (New > Android Project > From source...).
The first time I run the project it works great, but if I run it a second time, nothing shows up on screen and I get a force close after 30 seconds or so. Is the Eclipse import screwing something up? What could I be doing wrong? Do I need to build/clean/etc in a certain order?
I have noticed that on 2.2 if you use the back button, rather than the home button or the 'power' button it will break your emulator. On 2.3.3 and up, it won't even let you use the back button.
If you delete the emulator and remake it, the problem seems to be solved (kinda).
Still trying to figure out how to get around this one for the app I am making, as it needs to support 2.2.
Related
I'm trying to start out with Android programming (I'm running Mac OS X Lion). I had an old version of Eclipse and installed ADT version 20 in it, and code didn't compile properly. Fine; I hadn't done much in there, and after reading some stuff here it sounded like the easiest thing for the long run would be to put together a completely new installation.
So I downloaded the latest version of Android, with the SDK, from the Android developer Getting Started site, and ran it (in its own directory). I loaded one of my previous workspaces and it said that one wouldn't work because the ADT was version 20 and it needs 21. I figured fine, there wasn't much in there and I'd just start a new workspace.
So I started a new workspace, and here's where the real trouble came: It gives me the start screen with newbie welcome instructions but won't go any further than that. When I try to create a new Android Application Project, it goes through the menus but as soon as I click Finish I get a please-wait circular icon, and little happens. There's a line at the bottom that says "66M of 142M" - it increases slowly into the 80s and then drops back down into the 60s, endlessly. And the links provided on the welcome page (Building Your First App, etc.) don't work - I click on them and nothing happens.
Any idea what's going wrong here? Is there some cruft left over in my system from older versions, which I should delete? If so, how should I go about doing that? If not, what else might I try to get it working?
I can't comment beneath yours because of my level, but you can help Eclipse run faster by giving it more memory. Doing this speeds things up quite a bit.
As far as installations go, maybe try Google's packaged version of Eclipse + Android SDK. The whole package is available here. It's already preconfigured to work and provides eclipse with ADT installed by default. Of course, if you already have an existing Eclipse you want to modify this won't help you too much. But if you're new to Eclipse it's a good way to get started with Android development.
Like the question says, no mater what project i try this on, old or brand new, when I right click on the project and go to properties, then select the Android tab (I want to add a library), Eclipse freezes. I have to kill it. Has anyone run into this problem or know how I might fix it?
Thanks
EDIT:
Eclipse SDK
Version: 3.6.2
Build id: M20110210-1200
EDIT:
Or is there another way to add a library. I want to try out ActionbarSherlock :)
Ok, so I don't claim to understand it, but I've tried it more than once and confirmed it. When I'd go to the Android tab in Properties, the window automatically stretches the full height of my monitor and freezes. So, I killed it and went back in, but this time, starting on a different category ("Resource" in this case), I squashed the window height down to almost as small as it could get and clicked on Android. It worked. Didn't freeze. Then I was able to expand the window to see the list of libraries. No idea what it is, but I did it several times...recreating the freeze and then the fix. Hopefully this will save someone else...
i have found the reason ,because the list of available Android sdk is too long ,the window of the property can't be drawn immediately ,so it has no response.
the solution is open the SDK Manager ,delete the old sdk platform ,such as 1.5 1.6 3.0 3.1 3.2
those are not used usualy.then restart the eclipse .it works now .
For these kind of problems you have to try the following (in the same order) and stop when it works.
Play around inside eclipse by closing and opening project, deleting and reimporting projects etc.,
Restart eclipse
Restart system
Upgrade to the latest android SDK
Upgrade to the latest eclipse version
Usually you should stop at 2. Sometimes you need to stop at 3. Occasionally at 4 and Rarely at 5.
Good luck.
I'm a .NET developer but I like JAVA so in my free time I play around with that. I don't normally use Eclipse but I installed the ADT eclipse plugin and Andriod SDK and I started learning and I made a new project with a TableLayout and it kinda looks good, and it runs ok on the emulator.
However... there a few things that drive me absolutely catatonic and perhaps I am doing something wrong so please help me out.
Firstly, if I change the main.xml file in whatever way, even by adding what is supposedly a correct parameter, it will start freaking out and will generate an error that just says "error" without specifying what that is, it will then generate a main.out.xml and then report an error that the main.out.xml is empty. It later won't let me delete that and will start generating a main.out.out.xml and so forth, even after I correct that original xml that caused the error.
The only way to get things going is to delete the bin folder, restart Eclipse, delete all the out xml files and then sometimes it will run the application or some other times it will start generating those 'out' files again and the loop goes on.
That way it takes hours to run a simple app even one without errors that used to run before.
Surely that was NOT how they intended it to work, is it??
Also.. there is no "Rebuild" button that will flush all files out automatically, or is it hidden somewhere? I am tired of manually deleting those automatically generated files and the build folder and all those out.xml files.
Also, while I'm at it, I also want to point out that the designer view sometimes disappears and there is nothing on earth that will bring it back, the only way is to create a new project and copy the main.xml to it and then it shows up again. Another bug?
I have the latest eclipse version:
Version: Indigo Service Release 2
Build id: 20120216-1857
If you have any clues how to get this to work, I will appreciate it!
Many thanks in advance
When you click the Run button with an XML file selected, Eclipse is running an XSL Transformation on that XML and producing the .out.xml file as the result. This is a feature of the Eclipse Web Tools feature, which you'll have if you installed the Eclipse for Java EE Developers package (it may be included in other packages, too).
As others have said above in the comments, to run your Android app, select the Project, right-click, and choose Run As > Android App. Once you've done that once, it will create a Launch Configuration that you can launch from the Run or Debug toolbar buttons (pressing the small down-arrow on the Run or Debug buttons brings up a list of Launch Configurations that you can select from, as well as an option to manage them).
There is a Preference that will make Eclipse always launch the last thing you ran or debugged, instead of trying to be smart about what is currently selected. Open the Preferences and navigate to Run/Debug > Launching; there you'll find the option under Launch Operation at the bottom of the window.
I have troubles compiling my code with eclipse. Each time I click the run button it opens a new AVM.
I am starting to get lost in here any hint or solution please?
The run button in eclipse is designed to launch your code, which has to be done either in the AVM or on hardware connected to your computer. If you are wanting to build the binary without executing you go to the project menu and select Build All. However, it is probably set by default to build automatically, which is also under the project menu. Effectively this means the code you are writing is being built "on the fly" and errors will appear dynamically as you write your code. Is this what you were asking?
I'm having a troubling problem testing some code for and Android app. My app has two parts, and activity where the user changes some settings, and a broadcast receiver that responds to SMS messages, both in the same package.
Here's the problem, I first implemented some simple code to test out the broadcast receiver and the activity, and both worked fine. But then as I tried to refine the code, I noticed the emulator wasn't picking up any of my changes. Event went so far as to uninstall the app from the emulator and try again, no luck. Then I added some extra Toast popups to my receiver, nothing, still running the old code. I know its running the old code because its sending out an SMS using a string constant that is no longer in the current code, so it should be impossible that it respond with that value.
Here's the kicker that has me confused. For fun I made a change to my activity. Ran the project from Eclipse and that change showed up! Tried to test the receiver code again, runs the old code that doesn't even exist anymore!!
How in the world can half the package update, and the other half not?
Can anyone help me out 'cause I'm about ready to lose my mind.
I had a similar problem. Changes made to classes imported from another project didn't get picked up by eclipse, but those made to classes in the current android project were.
Making a change to the current android project (inserting a blank line and deleting it) seemed to make eclipse pick up all the changes made and upload the app to the emulator.
I had this problem too, Now I found a working solution. Just follow these steps:
Run your project normally.
When emulator started, run your project again (DO NOT close the first emulator)
Then the updated application will be uploaded into emulator
I can't really be sure what happened but creating an new emulator image appeared to solve the issue.
I don't know why it happens but it's a problem I have all the time.
What I typically do is
Close the emulator
Close Eclipse
Reopen Eclipse
Clean the projects (in Eclipse, select Project -> Clean... -> Clean all projects)
Rerun the emulator
Annoying as hell but seems to work for me.
I'm having this problem too. It mostly happens when errors are entered into the code. The strange thing is if I go back to the original code, Eclipse doesn't revert to the original code. One thing that seems to help is to temporary delete the contents of a file, save, and rebuild, and then enter the contents back into the file, save, and rebuild.
How is one supposed to debug in such an environment?