No information about Android

by [EMAIL PROTECTED] » Tue, 24 Jun 2008 22:24:21 GMT

Sponsored Links

I just knew the Android project ... there is a lack of information ...
Google should post news in the magazines once a Week or two about

As a programmer, people only will go with Android if there is a
business to be exploited. Google should go for professionals, offer
professional advice, tools and make learn how enterprises can gain
money with its product.



Other Threads

1. Inter-process communication with a Service and Notifications issue

You can set android:launchMode to singleTop to avoid having multiple
instances of the activity created on top of each other.  However, you
probably want to sit down and think about how this notification should
interact with the application in all of its states -- both while the user is
in it, and when they are elsewhere.  This is probably one of most
challenging areas of Android app design, and still has some issues with even
some of the standard apps.

Anyway, there are two main approaches I would recommend taking:

(1) If your app consists of a single main activity that the user naturally
wants to return to, then have the notification intent launch that with the
standard intent (MAIN action, LAUNCHER category), with
FLAG_ACTIVITY_CLEAR_TOP so that the user will return to this instead of
whatever other activity was on top of it.  The Gmail application is mostly a
good example of this, where the notification brings you to the main inbox
activity, regardless of whether you were last viewing a message.

(2) Otherwise, have the notification launch a special activity that tells
the user the full information associated with it, with facilities to launch
in to the actual application in whatever state is appropriate.  This special
activity, once the user selects something in its UI, will launch the desired
regular app activity with FLAG_ACTIVITY_NEW_TASK, allowing it to be placed
on top of the app in whatever state it currently is in, or use other flags
or such to control how the user enters the current app state.  The Calendar
application is a good example of this -- note how selecting its notification
brings you to a summary of all of the unhandled notifications, allowing you
to tap on one to view it in the app.

One of the goals of this is that you really want to design things so that
when the user selects your notification, they can press BACK to return to
whatever they were previously doing -- NOT to have that go back through your
app's old history stack however they last left it.

Btw, one more thing, I notice in your app manifest that you are not using
multiple processes, so you are not really doing "IPC" with the service.
 This is good.  In fact you don't actually need that .aidl interface at all
-- you can use the method shown in the LocalService sample code to simplify
your app a fair amount in this area:
On Sun, Dec 13, 2009 at 8:40 AM, Christophe Vandeplas <


2. IRC office hours Thursday 5:00-6:00 pm PST

You can subscribe to developer events calendar here, it includes our IRC
office hours.

Please submit your questions for today's office hours at :

Let me know if you have other office hours related questions.


2009/12/17 Bill Michaelson <>


3. how to send an IM?

4. URLconnection.setConnectTimeout doesn't work?

5. In what folder do you put a bitmap xml resource in your Android project?

6. How to use clasess on android device

7. how to change Menu background color?