Commit 3f003c51 by andrewlewis Committed by Oliver Woodman

Remove documentation on calling startDownloads

-------------
Created by MOE: https://github.com/google/moe
MOE_MIGRATED_REVID=194961264
parent ddeafa4f
...@@ -47,9 +47,6 @@ import java.util.concurrent.CopyOnWriteArraySet; ...@@ -47,9 +47,6 @@ import java.util.concurrent.CopyOnWriteArraySet;
* <p>A download manager instance must be accessed only from the thread that created it, unless that * <p>A download manager instance must be accessed only from the thread that created it, unless that
* thread does not have a {@link Looper}. In that case, it must be accessed only from the * thread does not have a {@link Looper}. In that case, it must be accessed only from the
* application's main thread. Registered listeners will be called on the same thread. * application's main thread. Registered listeners will be called on the same thread.
*
* <p>By default download tasks are stopped, so {@link #startDownloads()} must be called to start
* them.
*/ */
public final class DownloadManager { public final class DownloadManager {
......
...@@ -250,7 +250,9 @@ public abstract class DownloadService extends Service { ...@@ -250,7 +250,9 @@ public abstract class DownloadService extends Service {
/** /**
* Returns a {@link DownloadManager} to be used to downloaded content. Called only once in the * Returns a {@link DownloadManager} to be used to downloaded content. Called only once in the
* life cycle of the service. * life cycle of the service. The service will call {@link DownloadManager#startDownloads()} and
* {@link DownloadManager#stopDownloads} as necessary when requirements returned by {@link
* #getRequirements()} are met or stop being met.
*/ */
protected abstract DownloadManager getDownloadManager(); protected abstract DownloadManager getDownloadManager();
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or sign in to comment