The ServiceStartArguments API demo is one example of associating a
thread with a service:
http://code.google.com/android/samples/ApiDemos/src/com/google/android/samples/app/ServiceStartArguments.html
On Apr 26, 9:46 pm, "Dan U." <[EMAIL PROTECTED]> wrote:
> I think what Hielko said still applies
I think what Hielko said still applies. Try experimenting a bit with
it. If you get stuck, just post another message.
On Apr 26, 2:35 pm, WildLuka <[EMAIL PROTECTED]> wrote:
> follow the thread link at the beginning of my first post ... it's all
> there
>
> On Apr 26, 11:14 pm, Hielko <[EMAIL PRO
follow the thread link at the beginning of my first post ... it's all
there
On Apr 26, 11:14 pm, Hielko <[EMAIL PROTECTED]> wrote:
> I'm not sure what problem you exactly want to solve. If you want a
> service that is running in it's own thread you can simple create a
> class that extends Service
I'm not sure what problem you exactly want to solve. If you want a
service that is running in it's own thread you can simple create a
class that extends Service and implements runnable (and in the
onCreate of the service you create the thread): so what's the problem?
On 26 apr, 22:49, WildLuka <[
supposing you have a service with an certain number of methods and the
service is to run in its own thread ... how would you do it ?
On Apr 26, 10:41 pm, "Dan U." <[EMAIL PROTECTED]> wrote:
> If you notice the api docs say that creating a Handler associates it
> with the current thread. Probably
If you notice the api docs say that creating a Handler associates it
with the current thread. Probably you create your Handler instance
while setting up the UI? That should mean the UI thread is what it
uses when you use your Handler. That would explain why you have a
frozen UI. Quite often a Hand
6 matches
Mail list logo
