java.lang.Object | |
↳ | android.os.StrictMode.ThreadPolicy.Builder |
Creates
StrictMode.ThreadPolicy
instances. Methods whose names start
with
detect
specify what problems we should look
for. Methods whose names start with
penalty
specify what
we should do when we detect a problem.
You can call as many
detect
and
penalty
methods as you like. Currently order is insignificant: all
penalties apply to all detected problems.
For example, detect everything and log anything that's found:
StrictMode.ThreadPolicy policy = new StrictMode.ThreadPolicy.Builder() .detectAll() .penaltyLog() .build(); StrictMode.setThreadPolicy(policy);
Public Constructors | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
|
Create a Builder that detects nothing and has no
violations.
|
||||||||||
|
Initialize a Builder from an existing ThreadPolicy.
|
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
|
Construct the ThreadPolicy instance.
|
||||||||||
|
Detect everything that's potentially suspect.
|
||||||||||
|
Enable detection of slow calls.
|
||||||||||
|
Enable detection of disk reads.
|
||||||||||
|
Enable detection of disk writes.
|
||||||||||
|
Enable detection of network operations.
|
||||||||||
|
Crash the whole process on violation.
|
||||||||||
|
Crash the whole process on any network usage.
|
||||||||||
|
Show an annoying dialog to the developer on detected
violations, rate-limited to be only a little annoying.
|
||||||||||
|
Enable detected violations log a stacktrace and timing data
to the
DropBox
on policy
violation.
|
||||||||||
|
Flash the screen during a violation.
|
||||||||||
|
Log detected violations to the system log.
|
||||||||||
|
Disable the detection of everything.
|
||||||||||
|
Disable detection of slow calls.
|
||||||||||
|
Disable detection of disk reads.
|
||||||||||
|
Disable detection of disk writes.
|
||||||||||
|
Disable detection of network operations.
|
[Expand]
Inherited Methods
|
|||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From class
java.lang.Object
|
Create a Builder that detects nothing and has no
violations. (but note that
build()
will default
to enabling
penaltyLog()
if no other penalties
are specified)
Initialize a Builder from an existing ThreadPolicy.
Construct the ThreadPolicy instance.
Note: if no penalties are enabled before calling
build
,
penaltyLog()
is implicitly
set.
Detect everything that's potentially suspect.
As of the Gingerbread release this includes network and disk operations but will likely expand in future releases.
Enable detection of slow calls.
Enable detection of disk reads.
Enable detection of disk writes.
Enable detection of network operations.
Crash the whole process on violation. This penalty runs at the end of all enabled penalties so you'll still get see logging or other violations before the process dies.
Unlike
penaltyDeathOnNetwork()
, this applies
to disk reads, disk writes, and network usage if their
corresponding detect flags are set.
Crash the whole process on any network usage. Unlike
penaltyDeath()
, this penalty runs
before
anything else. You must still have
called
detectNetwork()
to enable this.
In the Honeycomb or later SDKs, this is on by default.
Show an annoying dialog to the developer on detected violations, rate-limited to be only a little annoying.
Enable detected violations log a stacktrace and timing data
to the
DropBox
on policy
violation. Intended mostly for platform integrators doing
beta user field data collection.
Flash the screen during a violation.
Log detected violations to the system log.
Disable the detection of everything.
Disable detection of slow calls.
Disable detection of disk reads.
Disable detection of disk writes.
Disable detection of network operations.