Skip to main content

Android: Prevent GPS from stopping



I have an issue with the GPS on Android. I am using the onStatusChanged(int status) with the GPSListener to read the status of the GPS. However, I notice that after some point, the GPS stops since the status returns:





GpsStatus.GPS_EVENT_STOPPED





How can I prevent the GPS from stopping at all? (Eventually I will stop it manually, but having it on when needed is very crucial)


Comments

  1. If you are running your LocationListener in a Service it will be stopped eventually unless you set the wake lock. This has nothing to do with the GPS itself.

    To acquire and release the wake lock I use the following code in my service:

    /**
    * Acquire a wake lock.
    * Ensure the CPU remains on and the screen is at least dim.
    */
    private void aquireWakeLock() {
    final PowerManager pm = (PowerManager) this.getSystemService(Context.POWER_SERVICE);
    this.wakeLock = pm.newWakeLock(PowerManager.SCREEN_DIM_WAKE_LOCK, TAG);
    this.wakeLock.acquire();
    if( DEBUG )
    Log.d( TAG, "Wake lock aquired:" + this.wakeLock);
    }

    /**
    * Release the wake lock.
    */
    private void releaseWakeLock() {
    if( this.wakeLock == null )
    return;
    this.wakeLock.release();
    this.wakeLock = null;
    if( DEBUG )
    Log.d( TAG, "Wake lock release");
    }


    The methods are called in onCreate() resp. onDestroy().

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex