Skip to main content

Broadcast receiver not getting extra



I have an app using a tab bar host api that I found and I am trying to use it to change activities when I receive a Sms message.





The receiver that was build into this tab host is the following:







public class ChangeTabBroadcastReceiver extends BroadcastReceiver

{

@Override

public void onReceive(Context context, Intent intent)

{

int index = intent.getExtras().getInt(CURRENT_TAB_INDEX);

setCurrentTab(index);

}

}







This is defined in the ScrollableTabActivity.java, then the ScrollableTabHost extends this and is called in the bellow method when a Sms is reveived:







Intent intent2 = new Intent(context,ScrollableTabHost.class);

intent2.putExtra("CURRENT_TAB_INDEX", index);

intent2.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK);

context.startActivity(intent2);







There is also an OnTabChanged listener build in which prints the index of the tab to the log. When i send a text from the emulator I shows that the tab was changed to index 0 twice, no matter which index I try to set it to. I have been looking for a while and cant find why I am getting 0 instead of the index that I send.


Comments

  1. It sounds like a similar issue to this : Android keeps caching my intents Extras, how to declare a pending intent that keeps fresh extras?

    So you can maybe try to give some unique id to your intents when you are setting the action:

    intent.setAction("smsaction" + System.currentTimeMillis());


    to make sure the latest one is the valid one (hence the extras and the ids)

    On the other hand... you are not using PendingIntents so this may be all irrelevant. If so please ignore.

    ReplyDelete

Post a Comment

Popular posts from this blog

Slow Android emulator

I have a 2.67 GHz Celeron processor, 1.21 GB of RAM on a x86 Windows XP Professional machine. My understanding is that the Android emulator should start fairly quickly on such a machine, but for me it does not. I have followed all instructions in setting up the IDE, SDKs, JDKs and such and have had some success in staring the emulator quickly but is very particulary. How can I, if possible, fix this problem?