Thank you for the questions.
And yes, the answers do point to needing a service with IPC, though
the IPC can be loosely coupled via a Pending Result.
In reference to question #3: We are using an IntentService, so the
service should shut down when it does not have work to do as well as
provide th
I'm posting this to share the lessons I learned while working with
IntentService.
IntentService has a single constructor that takes a string argument
"name". The documentation has no description of what name is used for.
In looking at the sources, I found that its only use is in naming the
worker
On May 6, 5:33 pm, jseghers wrote:
> On May 6, 2:49 pm, Dianne Hackborn wrote:
>
> > [B]e aware that if you do this by sending to a registered broadcast
> > receiver,
> > you can cause security holes because other people can also register for the
> > broadcas
On May 6, 2:49 pm, Dianne Hackborn wrote:
> [B]e aware that if you do this by sending to a registered broadcast receiver,
> you can cause security holes because other people can also register for the
> broadcast and send a broadcast to your client.
Am I safe by doing the following:
Caller has a
On further investigation, I see that the PendingIntent can be
cancelled, and such can work in the way I need by using a
BroadcastReceiver (probably dynamically registered).
- John
On May 6, 12:59 pm, jseghers wrote:
> Thank you for your quick reply.
>
> I thought about the PendingIn
Thank you for your quick reply.
I thought about the PendingIntent, but in this application the
information is only useful to the Caller if it is received while the
Caller is active that time. So if the information arrives later,
we'll still process it in the Service and store it for later use, b
I've been researching how to best implement a service which performs a
network transaction and returns data to the caller.
Clearly, this needs to happen on its own thread which means some form
of async response. I can see at least three ways of doing this--some
more complex than others. In the
On Apr 14, 4:58 pm, Rob Shortt wrote:
> I'm looking for any documentation on the call flow including any
> notifications and intents fired.
Look at android.telephony.PhoneStateListener
- John
--~--~-~--~~~---~--~~
You received this message because you are subsc
I've seen with the onscreen keypad, the application does not seem to
be notified that the OSK has been brought in front of it.
I would like to be able to change the layout of my screen so that
relevant information is visible when the keypad is brought to the
fore. I have information onscreen tha
My company has a team of developers and testers working on product for
Andriod phones. The normal developer account can only order a single
ADP1. We would like to get a couple more of them.
Is there a corporate developer account that would give us access to
more of them? Or do we need to create m
ed, in which case the system will restart it automatically.
>
>
>
>
>
> On Wed, Mar 25, 2009 at 11:12 AM, jseghers wrote:
>
> > Thank you for your reply!
>
> > I am seeing am_task_to_front followed by am_finish_activity.
> > I found the event-log-tags file
;
>
>
>
> On Tue, Mar 24, 2009 at 7:24 PM, jseghers wrote:
>
> > I am just starting on an Android app and I am puzzled about why my
> > Task activity stack is being reset any time the application is
> > launched from the Home screen.
>
> > I used
I am just starting on an Android app and I am puzzled about why my
Task activity stack is being reset any time the application is
launched from the Home screen.
I used the ADT tools to create the application in Eclipse.
The main activity is ".UserLaunch" and it starts the activity ".About"
when t
13 matches
Mail list logo
