Either cache the Context object via constructor in your adapter, or get it from your view. Or as a last resort, add – FLAG_ACTIVITY_NEW_TASK flag to your intent: _ myIntent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK); Edit – i would avoid setting flags as it will interfere with normal flow of event and history stack.
An idea is to have a static variable in your main activity, instantiated to be the package name. Then just reference that variable. You will have to initialize it in the main activity’s onCreate() method: Global to the class: public static String PACKAGE_NAME; Then.. @Override public void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.main); PACKAGE_NAME = getApplicationContext().getPackageName(); … Read more
Instead of getApplicationContext(), just use ActivityName.this.
They are both instances of Context, but the application instance is tied to the lifecycle of the application, while the Activity instance is tied to the lifecycle of an Activity. Thus, they have access to different information about the application environment. If you read the docs at getApplicationContext it notes that you should only use … Read more
Very interesting question. I think it’s mainly a semantic meaning, and may also be due to historical reasons. Although in current Android Activity and Service implementations, getApplication() and getApplicationContext() return the same object, there is no guarantee that this will always be the case (for example, in a specific vendor implementation). So if you want … Read more
commit schedules the transaction, i.e. it doesn’t happen straightaway but is scheduled as work on the main thread the next time the main thread is ready. I’d suggest adding an onAttach(Activity activity) method to your Fragment and putting a break point on it and seeing when it is called relative to your call to asd(). … Read more
I agree that documentation is sparse when it comes to Contexts in Android, but you can piece together a few facts from various sources. This blog post on the official Google Android developers blog was written mostly to help address memory leaks, but provides some good information about contexts as well: In a regular Android … Read more
There are a couple of potential problems with this approach, though in a lot of circumstances (such as your example) it will work well. In particular you should be careful when dealing with anything that deals with the GUI that requires a Context. For example, if you pass the application Context into the LayoutInflater you … Read more
View.getContext(): Returns the context the view is currently running in. Usually the currently active Activity. Activity.getApplicationContext(): Returns the context for the entire application (the process all the Activities are running inside of). Use this instead of the current Activity context if you need a context tied to the lifecycle of the entire application, not just … Read more
Using context in a fragment