5

Would this be correct code for Android:
calling init from MyApplication.onCreate()

public class Connectivity {
    static ConnectivityManager cm;

    public static void init(Context context){
        cm = (ConnectivityManager) context.getSystemService(Context.CONNECTIVITY_SERVICE);      
    }

    public static boolean isConnected(){
        activeNetwork = cm.getActiveNetworkInfo();
        boolean isConnected = activeNetwork != null &&
                              activeNetwork.isConnected();
        return isConnected;
    }

Is using static way to go for Android?
Will those static values stay longer than any activity or launched service (that will finish in an hour)?

There was related question Android Application Class Lifecycle but discussion went to Activities lifecycle.

Community
  • 1
  • 1
Paul Verest
  • 60,022
  • 51
  • 208
  • 332
  • Maybe this topic answer your question? http://stackoverflow.com/questions/1944369/android-static-object-lifecycle – Anh-Tuan Mai Apr 19 '16 at 13:38
  • Should we inject our Application class in AndroidManifest by adding android:name="MyApplication", then in onCreate() we do an initialization for all needed singleton? – Anh-Tuan Mai Apr 19 '16 at 13:45

0 Answers0