If you have already used Eclipse with Android SDK, you probably have some experience with known and unknown bugs. I'd like to show you some of these, and help you how to solve them.
First of all, if you got the following message from the running Emulator, except that the process is your Project, then you have to open up DDMS.
You can find DDMS button in the upper-right corner of Eclipse. Once you are in DDMS, Select your running Emulator from the left, and see what is happening by Clicking on LogCat tab (bottom of the screen).
Scroll all the way down, then start scrolling upwards, until red-colored lines show up. Probably you have NullPointer Exception or something like that, so I can't help you on that one, but I try my best to solve some other problems that you may have had.
When I first tried to manage an sqlite database on an android device I was not sure about where I fail in it. Can I even insert the records into the database, or I fail only to read the data from it? So I started to search for possibilities to debug the database lifecycle.
The system stores databases in the /data/data/package_name/databases folder by default.
In a command line using the adb (Android Debug Bridge - found in the android sdk tools library) you can access the databases on a running emulator like below:
Would you like to disable a button on an appwidget?
As far as I know it can not be done, since the appwiget UI manipulation is limited by the methods of the RemoteViews class.
But if you insist to do that there is a way to make it look like the button were disabled!
RemoteViews can't manipulate a buttons enabled/disabled state, but it can modify its visibility. So the trick is to have two buttons, the real one, and an other which is designed to look like the real one in disabled state, and change witch one is visible.
Lets see a simple example:
We want to have two buttons on the widget, a stop and a start button in order to stop and start some kind of functionality. Once we have started it, we can not start it agin, until we stopped it and vica versa, so we want to disable the button which can not be used right now.
The XML definition of the buttons can be like this:
The emulator available in the Android SDK is not just a tool that allows you to easily test applications without having to install it to a real device, or even having one. With the proper configuration it is possible to test situations which are hardly reproduced on a physical one.
Recently I had a chance to try out my first Android device. It's called the "T-Mobile Pulse / Huawei U8220". Previously I tried an HTC Diamond, which was running on Windows Mobile, both platforms have a very nice UI.
At first, when the boot-up screen showed up, I thought to myself that these devices are just like PC-s from now on, rather than mobile-phones. Not to speak about those very high DPI values. It is also very comfortable and useful that you can rotate the mobile by 90 degrees both direction, the display is going to be rearranged.
The Pulse has a version 1.5 of Android, and it features aGPS, 3.2mp camera, g-sensor, Wifi, etc...
About Andoid
just take a quick look at this chart...
android (blue) |windows mobile (red) |symbian (orange)
At last I found a companion for my Fallout3 BobbleHead that sits on my desk. He is so lonely, being alone all the time. He was very happy as my kids started to play with him but after a while it did hurt him.
Now he will get some friends. I hope that he won't have any problem with the fact that the friends will be non-biological. In any case they are more friendly then super mutants
If you were ever wondering, how you could see if someone is using Google Talk from an Android device, here is the solution. In your Google Mail web interface go to Settings, select the Labs tab, and turn on the "Green Robot" extension: this will display a robot icon for the users from an Android device, while the coloring indicates the availability of the person.
It really makes sense: your friends can see, that you are logged in from your phone, so they know if you are available and do not answer, this is maybe because you do not have a free hand at the moment.