android-context

I was wondering when does Context.bindService() return false ? I've tried to make the onBind() return null , but it still returns true when bindService is called and the onServiceConnected does not get executed. I also saw this on Google Groups with no response https://groups.google.com/forum/#!topic/android-developers/ZLl56Mz1jYg I also can't find the implementation of bindService, since it is abstract in Context.java and searching for "public boolean bindService" does not yield any useful results either (closest was ApplicationContext which does not seem to be present in the current API

I've seen this particular technique for launching activities and it seems to me like a bad idea because of static contexts but I was hoping someone might have a legit reason behind this approach. The activity you want to launch implements a static launch(Context context) method that sets up the intent, flags, etc and finally starts the activity. public static void launch(Context context){ Intent i = new Intent(context, SomeOtherActivity.class); // flag stuff context.startActivity(i); } Then a DifferentActivity could go and launch SomeOtherActivity with one line. SomeOtherActivity.launch

So I am trying to get a string resource in my project but when I called context.getResources().getString(...) , I get a NullPointerException . In debug mode, I found out that the context isn't null but looking at its members, I found out that mResources was null. Why are the resources not loaded for the activity context? EDIT Apparently, this is what triggered the Exception public class MyActivity extends Activity { SomeClass someClass = new SomeClass(this); @Override protected void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); } } public class SomeClass { private

If I interpret this article correctly, passing the activity context to AsyncTasks is a potential leak, as the activity might be destroyed while the task is still running. How do you deal with this in AsyncTasks that are not inner clases and need access to resources or to update the UI? Additionally, how can you avoid leaking the context if you need references to progress dialogs to dismiss them? If I understand your question correctly: Java's WeakReference or SoftReference class is a good fit for this type of situation. It will allow you to pass the context to the AsyncTask without preventing

My calling activity: public class Hello extends Activity { public void onCreate(Bundle savedInstanceState) { MyTask mt = new MyTask(this); mt.execute(); } Now In MyTask (an external class): public class MyTask extends AsyncTask<Void, Void, Void> { private Context mContext; public MyTask(Context context) { mContext = context; } //doinbackground, etc protected void onPostExecute() { mContext.finish(); } Other things are working as expected if I remove mContext.finish() above. But if I'm calling mContext.finish() , I'm getting an error: The method finish() is undefined for the type Context

I created a class to retrieve comments from a JSON encoding from a PHP file. This class, extends from AsyncTask: public class RecuperarComentarisFoto extends AsyncTask<String, String, String>{ @Override protected void onPreExecute() { super.onPreExecute(); pDialog = new ProgressDialog(????); pDialog.setMessage("Creating Product.."); pDialog.setIndeterminate(false); pDialog.setCancelable(true); pDialog.show(); } @Override protected String doInBackground(String... arg0) { // TODO Auto-generated method stub return null; } @Override protected void onPostExecute(String result) { // TODO Auto

I have some classes within my application that need to call Android functions that require the Context as a parameter. I don't have it as the class is not a subclass of the Activity class. What is the correct way to tackle this problem? Pass it as a parameter on each call? Pass it at class instantiation and keep it? Maxim It depends on the role of the class. But anyway pass ApplicationContext but not Activity one. If you pass Activity context gc can't remove it from the memory when after you don't need activity anymore. But application context is used while application was not finished by OS