Hello,
By explicit component do you mean data android scheme=custom/
data in the intent filter or code in the broadcast receiver? Is that
all i'd need?
Thanks,
George
On Apr 23, 1:29 am, Dianne Hackborn hack...@android.com wrote:
You didn't include all of your code, but you definitely what
I've added the scheme to my intent filter as following.
proxBroadcastReceiver = new MyIntentReceiver();
proxIntentFilter = new IntentFilter
(android.intent.action.PROXIMITY_ALERT);
proxIntentFilter.addDataScheme(custom);
registerReceiver(proxBroadcastReceiver, proxIntentFilter);
I'm now
I've fixed this now. Rather embarrassingly, in my intent receiver i
never actually retrieved the mgoal from the extras. So the info i was
getting was just the number i initialized the variable with! Thanks
for all your help!
George
On Apr 23, 1:17 pm, Fuzzmonkey she...@gmail.com wrote:
I've
I've fixed this now. Rather embarrassingly, in my intent receiver i
never actually retrieved the mgoal from the extras. So the info i was
getting was just the number i initialized the variable with! Thanks
for all your help!
George
On Apr 23, 1:17 pm, Fuzzmonkey she...@gmail.com wrote:
I've
info+fram Use different request codes each time in
PendingIntent.getActivity, the documentation is bugged and say this is
not in use but they DO work. There is an old discussion on this one:
No, I mean setting the explicit component to your broadcast receiver
component on the Intent class. I strongly strongly recommend this for this
kind of situation where you want someone to deliver some specific thing to a
component in your app. Please read the Intent java doc for more info.
On
So with all the input from this thread, what's the proper way to send x
number of pending intents that are unique?
I guess I'm doing it not 100% correctly (even though it seems to work for me
and the intents are spaced out enough not to interfere with each other). I
was doing it
as
Cool, will look into that then. Thanks all.
On Thu, Apr 23, 2009 at 1:52 PM, Dianne Hackborn hack...@android.comwrote:
Different request codes is a perfectly fine way to do it.
On Thu, Apr 23, 2009 at 9:48 AM, Rob Franz rob.fr...@gmail.com wrote:
So with all the input from this thread,
That said... I would be -very- suspicious about the code you posted where
you are effectively creating random identities for your pending intents. In
most of the places where one uses a pending intent, you give it to something
that holds on to it indefinitely, so you need to be able to recover
Hi guys,
I seem to be having a similar problem when i add proximity alerts via
the location manager. It seems only the pending intent for the last
alert i enter into the location manager is 'saved'. I've been trying
to make the intents 'unique' but what ever i try stops the proximity
alert
Hi,If you have an intent like
Intent i = new Intent(YourActivity.this, YourBroadcastReceiver.class);
Make it unique by:
i.setData((Uri.parse(custom://+SystemClock.elapsedRealtime(;
-Rob
On Wed, Apr 22, 2009 at 12:04 PM, Fuzzmonkey she...@gmail.com wrote:
Hi guys,
I seem to be having
I hope you aren't writing constants into real code like that. :}
For changing the extras -- you need to use cancel, and this will result in a
new PendingIntent that you need to send to the notification manager. As of
cupcake you can alternatively use the new FLAG_UPDATE_CURRENT.
On Thu, Mar 26,
Hi Dianne,I thought that the goal was to create unique pendingIntents...
i.e. don't cancel or change the currently pending one.
For me, changing the extras didn't work - doing the setData() with the
random value made the intent 'unique' in the eyes of the notification
manager...i wanted the
Setting the data uniquely in this way is a bit ugly - and what if you post
two intents within the granularity of the clock?
I use unique request codes. I can't claim that this is the intended use for
them (the documentation is a bit sparse) but it seems to work well.
Tom.
2009/4/22 Rob Franz
Yeah I agree - it is ugly, but for my purposes it worked... the intents
wouldn't be fired one right after the other for me.
On Wed, Apr 22, 2009 at 4:02 PM, Tom Gibara m...@tomgibara.com wrote:
Setting the data uniquely in this way is a bit ugly - and what if you post
two intents within the
Hmm.
I'm currently using unique request codes and i'm still getting this
problem. I'm trying to add multiple proximity alerts, with each alert
containing different information. For example, i have 4 gps co-
ordinates belong to the same group. I want the intent to contain the
extra information
Done a bit more digging.
proxIntent.setData((Uri.parse(custom://+SystemClock.elapsedRealtime
(;
If i add this line, the proximity alert is still triggered but the
intent is never received. That is I assume it's still being fired but
not received. I just get..
I/LocationManagerService(
You didn't include all of your code, but you definitely what to set an
explicit component for your receiver, and then the rest of the intent data
doesn't matter for deciding where or whether it will be delivered.
On Wed, Apr 22, 2009 at 5:19 PM, Fuzzmonkey she...@gmail.com wrote:
Done a bit
Thank you for your detailed answer Blake B.,
First of all I understood that different Extras are not act as a
difference on PendingIntent comparison.
In the first option assigning a stub data element seems reasonable but
I did not like the approach to put not only irrelevant but also not
I'm running into the same thing - sending multiple PIs with the extras
data changing each time. If I send two PIs, I get the first PI extra
data. I'm glad someone else ran into this, because I was going crazy
trying to find out why my stuff wasn't working.
Seeing a couple of different opinions
Actually it looks like
PendingIntent pendingIntent = PendingIntent.getBroadcast(context, 0, intent,
0x1000);
...works for me (0x1000 represents FLAG_CANCEL_CURRENT). I can verify
that the appropriate extras data makes it to the intent. Hope this helps.
-Rob
On Thu, Mar 26, 2009 at
Intents are cached by the system, and two Intents are not
differentiated by their Extras. So your two intents look like the
same Intent and the second one is being tossed out. You must differ
Intents by their Action/Data/Category. I will sometimes use the Data
field to hold a simple ID that is
To correct my previous statement, PendingIntents are cached by the
system, not Intents. The note about how to differentiate Intents
still holds though, so if you need to replace a current PendingIntent
with a new PI that has a new Intent that only differs by its Extras,
be sure to use the flag
Hello Mr. Murphy,
I searched for it before sending my post and looked at
http://groups.google.com/group/android-developers/browse_thread/thread/6c0d72904ab4234e/9cc2ad4d8795e9a6?lnk=gstq=PendingIntent#9cc2ad4d8795e9a6
and
Dear all,
Am I the only one who is having this problem?
Actually, I am going to find a workaround for this problem, but I
would like to know what I am doing wrong.
Any help would be appreciated.
Regards,
info+farm
info+farm wrote:
Hello all,
I have more than one notification in
info+farm wrote:
Am I the only one who is having this problem?
Actually, I am going to find a workaround for this problem, but I
would like to know what I am doing wrong.
I do not remember the answer, but I do know this was discussed on this
list within the past few months. Search the list
26 matches
Mail list logo
