My question was actually about why you are using multiple processes for your
receiver components.  Nothing in what you describe indicates that you need
that.  Keep in mind that each process currently requires about 2MB of
overhead, and slows down your app if it needs to be launched.

On Tue, Jan 6, 2009 at 2:23 PM, ArtJin <ajin...@gmail.com> wrote:

>
> Got it thanks.
>
> To answer your question let me describe what I am trying to do.
> I have an AlarmManager that runs a service, which connects to web
> server and gets some data.
> Everything works fine, but battery drains quickly since AlarmManager
> stops running only when CPU stops.
> So I wanted to reschedule the AlarmManager according to screen's on/
> off situation, since I do not really need it running when user is not
> looking at the screen.
> I guess I need to re-think the design approach.
> What would you recommend?
> Thanks again for quick response! :-)
>
>
> On Jan 6, 5:02 pm, "Dianne Hackborn" <hack...@android.com> wrote:
> > These are currently only delivered to receivers actively registered with
> > registerReceiver().
> >
> > On a side note...  why are you running your receivers in a separate
> > process??
> >
> >
> >
> > On Tue, Jan 6, 2009 at 1:57 PM, ArtJin <ajin...@gmail.com> wrote:
> >
> > > Hello everybody.
> > > Carter, did you find out what was the problem?
> > > I am having exact same issue.
> > > the receivers are installed with no problems, however they do not
> > > receive SCREEN_ON or SCREEN_OFF broadcasts for some reason, unless I
> > > do everything programatically.
> > > Here is the receiver snippet from my manifest:
> > > <receiver android:name=".ScreenOnBroadcastReceiver"
> > > android:process=":remote">
> > >  <intent-filter>
> > >   <action android:name="android.intent.action.SCREEN_ON"></action>
> > >  </intent-filter>
> > > </receiver>
> > > <receiver android:name=".ScreenOffBroadcastReceiver"
> > > android:process=":remote">
> > >  <intent-filter>
> > >    <action android:name="android.intent.action.SCREEN_OFF"></action>
> > >  </intent-filter>
> > > </receiver>
> >
> > > Ideas are appreciated!
> > > Thanks :-)
> >
> > > On Dec 4 2008, 1:22 pm, Carter <ccjerni...@gmail.com> wrote:
> > > > I'm trying to detect when the phone's screen turns on and off with
> the
> > > > SCREEN_ON andSCREEN_OFFIntents.  A BroadcastReceiver declared in the
> > > > AndroidManifest doesn't work with these screen on/off Intents, but
> > > > instantiating a BroadcastReceiver programatically at runtime does
> > > > work.
> >
> > > > As far as troubleshooting goes: my AndroidManifest BroadcastReceiver
> > > > is properly receiving other Intents, such as for phone boot.  There
> is
> > > > no helpful information in LogCat.  And this isn't a permissions
> issue,
> > > > since it works when declared programatically.
> >
> > > > There are no explanations in the JavaDocs (e.g. its not like the
> > > > battery changed Intent which cannot be declared in the Manifest),
> > > > although when searching through the Android source I discovered that
> > > > none of the Android OS services declare interest this particular
> > > > Intent in XML either.
> >
> > > > So any ideas why I can't declare SCREEN_ON andSCREEN_OFFin the
> > > > AndroidManifest?
> >
> > --
> > Dianne Hackborn
> > Android framework engineer
> > hack...@android.com
> >
> > Note: please don't send private questions to me, as I don't have time to
> > provide private support.  All such questions should be posted on public
> > forums, where I and others can see and answer them.
> >
>


-- 
Dianne Hackborn
Android framework engineer
hack...@android.com

Note: please don't send private questions to me, as I don't have time to
provide private support.  All such questions should be posted on public
forums, where I and others can see and answer them.

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

Reply via email to