Nick Owens wrote:
> Oh, so I figured it out.  There is some bug in the emulator I guess.  I ran
> into it once before and at the time, just assumed I had done something
> wrong.
> 
> Basically, I created a new project from your sample Alarm service and ran it
> to see if it would work on my emulator.  Not only did it work, so did mine!
> 
> This happened before when I was having trouble w/ receivers, alarms,
> services, etc.  It's like I have to build and install another totally
> innocuous and unrelated project and then all of a sudden mine will start
> working.  But the alarm is only received and service started when I run the
> other project in the emulator!

I do tend to test that code on hardware, because the emulator never
really falls asleep, so I prefer to use something where I know the
WakeLocks will take effect.

That being said, based on other work, I feel rather strongly that
"receivers, alarms, services, etc." work just fine -- it's only
WakeLocks that I'm worried about in terms of the tech you've been
dealing with on this issue.

You might consider creating a fresh AVD or something.

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com | http://twitter.com/commonsguy

Warescription: Three Android Books, Plus Updates, One Low Price!

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to