This constant was deprecated
in API level 19.
Creating world-readable files is very dangerous, and likely
to cause security holes in applications. It is strongly
discouraged; instead, applications should use more formal
mechanism for interactions such as ContentProvider,
BroadcastReceiver, and Service.
There are no guarantees that this access mode will remain on
a file, such as when it goes through a backup and restore.

This constant was deprecated
in API level 19.
Creating world-writable files is very dangerous, and likely
to cause security holes in applications. It is strongly
discouraged; instead, applications should use more formal
mechanism for interactions such as ContentProvider,
BroadcastReceiver, and Service.
There are no guarantees that this access mode will remain on
a file, such as when it goes through a backup and restore.

Flag for use with writeToParcel(Parcel, int): the object being written
is a return value, that is the result of a function such as
"Parcelable someFunction()",
"void someFunction(out Parcelable)", or
"void someFunction(inout Parcelable)".

Causes the current thread to wait until another thread invokes the
notify() method or the
notifyAll() method for this object, or
some other thread interrupts the current thread, or a certain
amount of real time has elapsed.

MODE_WORLD_READABLE

This constant was deprecated
in API level 19.
Creating world-readable files is very dangerous, and likely
to cause security holes in applications. It is strongly
discouraged; instead, applications should use more formal
mechanism for interactions such as ContentProvider,
BroadcastReceiver, and Service.
There are no guarantees that this access mode will remain on
a file, such as when it goes through a backup and restore.

For use with open(File, int): if MODE_CREATE has been supplied and
this file doesn't already exist, then create the file with permissions
such that any application can read it.

Constant Value:
1
(0x00000001)

MODE_WORLD_WRITEABLE

This constant was deprecated
in API level 19.
Creating world-writable files is very dangerous, and likely
to cause security holes in applications. It is strongly
discouraged; instead, applications should use more formal
mechanism for interactions such as ContentProvider,
BroadcastReceiver, and Service.
There are no guarantees that this access mode will remain on
a file, such as when it goes through a backup and restore.

For use with open(File, int): if MODE_CREATE has been supplied and
this file doesn't already exist, then create the file with permissions
such that any application can write it.

createReliablePipe

Create two ParcelFileDescriptors structured as a data pipe. The first
ParcelFileDescriptor in the returned array is the read side; the second
is the write side.

The write end has the ability to deliver an error message through
closeWithError(String) which can be handled by the read end
calling checkError(), usually after detecting an EOF.
This can also be used to detect remote crashes.

createReliableSocketPair

Create two ParcelFileDescriptors structured as a pair of sockets
connected to each other. The two sockets are indistinguishable.

Both ends have the ability to deliver an error message through
closeWithError(String) which can be detected by the other end
calling checkError(), usually after detecting an EOF.
This can also be used to detect remote crashes.

describeContents

Describe the kinds of special objects contained in this Parcelable
instance's marshaled representation. For example, if the object will
include a file descriptor in the output of writeToParcel(Parcel, int),
the return value of this method must include the
CONTENTS_FILE_DESCRIPTOR bit.

Returns

int

a bitmask indicating the set of special object types marshaled
by this Parcelable object instance.

dup

Create a new ParcelFileDescriptor that is a dup of an existing
FileDescriptor. This obeys standard POSIX semantics, where the
new file descriptor shared state such as file position with the
original file descriptor.

dup

Create a new ParcelFileDescriptor that is a dup of the existing
FileDescriptor. This obeys standard POSIX semantics, where the
new file descriptor shared state such as file position with the
original file descriptor.

fromFd

Create a new ParcelFileDescriptor from a raw native fd. The new
ParcelFileDescriptor holds a dup of the original fd passed in here,
so you must still close that fd as well as the new ParcelFileDescriptor.

fromSocket

Create a new ParcelFileDescriptor from the specified Socket. The new
ParcelFileDescriptor holds a dup of the original FileDescriptor in
the Socket, so you must still close the Socket as well as the new
ParcelFileDescriptor.

Parameters

socket

Socket:
The Socket whose FileDescriptor is used to create
a new ParcelFileDescriptor.

toString

Returns a string representation of the object. In general, the
toString method returns a string that
"textually represents" this object. The result should
be a concise but informative representation that is easy for a
person to read.
It is recommended that all subclasses override this method.

The toString method for class Object
returns a string consisting of the name of the class of which the
object is an instance, the at-sign character `@', and
the unsigned hexadecimal representation of the hash code of the
object. In other words, this method returns a string equal to the
value of:

Protected methods

finalize

Called by the garbage collector on an object when garbage collection
determines that there are no more references to the object.
A subclass overrides the finalize method to dispose of
system resources or to perform other cleanup.

The general contract of finalize is that it is invoked
if and when the JavaTM virtual
machine has determined that there is no longer any
means by which this object can be accessed by any thread that has
not yet died, except as a result of an action taken by the
finalization of some other object or class which is ready to be
finalized. The finalize method may take any action, including
making this object available again to other threads; the usual purpose
of finalize, however, is to perform cleanup actions before
the object is irrevocably discarded. For example, the finalize method
for an object that represents an input/output connection might perform
explicit I/O transactions to break the connection before the object is
permanently discarded.

The finalize method of class Object performs no
special action; it simply returns normally. Subclasses of
Object may override this definition.

The Java programming language does not guarantee which thread will
invoke the finalize method for any given object. It is
guaranteed, however, that the thread that invokes finalize will not
be holding any user-visible synchronization locks when finalize is
invoked. If an uncaught exception is thrown by the finalize method,
the exception is ignored and finalization of that object terminates.

After the finalize method has been invoked for an object, no
further action is taken until the Java virtual machine has again
determined that there is no longer any means by which this object can
be accessed by any thread that has not yet died, including possible
actions by other objects or classes which are ready to be finalized,
at which point the object may be discarded.

The finalize method is never invoked more than once by a Java
virtual machine for any given object.

Any exception thrown by the finalize method causes
the finalization of this object to be halted, but is otherwise
ignored.