DX trouble processing "Java/NiO/charbuffer. Class ":

DX trouble processing "Java/NiO/charbuffer. Class ":

Ill-advised or mistaken usage of a core class (Java. * or javax .*)
When not building a core library.

This is often due to inadvertently including a core library file
In your application's project, when using an IDE (such
Eclipse). If you are sure you're not intentionally defining
Core class, then this is the most likely explanation of what's
Going on.

However, you might actually be trying to define a class in a core
Namespace, the source of which you may have taken, for example,
From a non-android Virtual Machine project. This will most
Assuredly not work. At a minimum, it jeopardizes
Compatibility of your app with ure versions of the platform.
It is also often of questionable legality.

If you really intend to build a core library -- which is only
Appropriate as part of creating a full Virtual Machine
Distribution, as opposed to compiling an application -- then use
The "-- Core-library" option to suppress this error message.

If you go ahead and use "-- Core-library" but are in fact
Building an application, then be forewarned that your application
Will still fail to build or run, at some point. Please be
Prepared for angry MERs mers who find, for example, that your
Application ceases to function once they upgrade their operating
System. You will be to blame for this problem.

If you are legitimately using some code that happens to be in
Core Package, then the easiest safe alternative you have is
Repackage that code. That is, move the classes in question
Your own package namespace. This means that they will never be in
Conflict with core system classes. JarJar is a tool that may help
You in this endeavor. If you find that you cannot do this, then
That is an indication that the path you are on will ultimately
Lead to pain, suffering, grief, and lamentation.

[2012-01-03 22:29:53-CLM] dx 1 error; aborting

[2012-01-03 22:29:53-CLM] conversion to Dalvik format failed with error 1

Remove all buildpaths and fix them again. It is caused by references to lower versions of jar on the Internet.