ART Android runtime

Introducing ART

ART is a new Android runtime being introduced experimentally in the 4.4 release. This is a preview of work in progress in KitKat that can be turned on in Settings > developer options. This is available for the purpose of obtaining early developer and partner feedback.

Important: Dalvik must remain the default runtime or you risk breaking your Android implementations and third-party applications.

Most existing apps should just work when running with ART. However, some techniques that work on Dalvik do not work on ART. For information about the most important issues, see Verifying App Behavior on the Android Runtime (ART).

ART Features

---

Here are some of the major new features implemented by ART.

Ahead-of-time (AOT) compilation

ART introduces ahead-of-time (AOT) compilation, which can improve app performance. ART also has tighter install-time verification than Dalvik.

At install time, ART compiles apps using the on-device dex2oat tool. This utility accepts DEX files as input and generates a compiled app executable for the target device. The utility should be able to compile all valid DEX files without difficulty. However, some post-processing tools produce invalid files that may be tolerated by Dalvik but cannot be compiled by ART. For more information, see Addressing Garbage Collection Issues.

Improved garbage collection

Garbage collection (GC) can impair an app's performance, resulting in choppy display, poor UI responsiveness, and other problems. ART improves garbage collection in several ways:

• One GC pause instead of two
• Parallelized processing during the remaining GC pause
• Collector with lower pause time for the special case of cleaning up recently-allocated, short-lived objects
• Improved garbage collection ergonomics, making concurrent garbage collections more timely, which makesGC_FOR_ALLOC events extremely rare in typical use cases

ART currently does not use compacting GC, but this feature is under development in the Android Open Source Project (AOSP). In the meantime, don't perform operations that are incompatible with compacting GC, such as storing pointers to object fields. For more information, see Addressing Garbage Collection Issues.

Development and debugging improvements

ART offers a number of features to improve app development and debugging.

Support for sampling profiler

Historically, developers have used the Traceview tool (designed for tracing application execution) as a profiler. While Traceview gives useful information, its results on Dalvik have been skewed by the per-method-call overhead, and use of the tool noticeably affects run time performance.

ART adds support for a dedicated sampling profiler that does not have these limitations. This gives a more accurate view of app execution without significant slowdown. Sampling support has also been added to Traceview for Dalvik.

Support for more debugging features

ART supports a number of new debugging options, particularly in monitor- and garbage collection-related functionality. For example, you can:

• See what locks are held in stack traces, then jump to the thread that holds a lock.
• Ask how many live instances there are of a given class, ask to see the instances, and see what references are keeping an object live.
• Filter events (like breakpoint) for a specific instance.
• See the value returned by a method when it exits (using “method-exit” events).
• Set field watchpoint to suspend the execution of a program when a specific field is accessed and/or modified.

Improved diagnostic detail in exceptions and crash reports

ART gives you as much context and detail as possible when runtime exceptions occur. ART provides expanded exception detail for java.lang.ClassCastException, java.lang.ClassNotFoundException, andjava.lang.NullPointerException. (Later versions of Dalvik provided expanded exception detail forjava.lang.ArrayIndexOutOfBoundsException and java.lang.ArrayStoreException, which now include the size of the array and the out-of-bounds offset, and ART does this as well.)

For example, java.lang.NullPointerException now shows information about what the app was trying to do with the null pointer, such as the field the app was trying to write to, or the method it was trying to call. Here are some typical examples:

java.lang.NullPointerException: Attempt to write to field 'int
android.accessibilityservice.AccessibilityServiceInfo.flags' on a null object
reference

java.lang.NullPointerException: Attempt to invoke virtual method
'java.lang.String java.lang.Object.toString()' on a null object reference

ART also provides improved context information in app native crash reports, by including both Java and native stack information.

Android Bluetooth Connection

Bluetooth:The Android platform supports Bluetooth connection, which allows exchanging data with other Bluetooth devices. The application framework provides access to the Bluetooth functionality through the Android Bluetooth APIs connect to other Bluetooth devices.

All of the Bluetooth APIs is available in the Android Bluetooth package. Here is a summary of the classes you will need to create as below.

BluetoothAdapter: Represents the local Bluetooth adapter (Bluetooth radio)
BluetoothDevice: Represents a remote Bluetooth device, query information such as its name, address, class, and bonding state.
BluetoothSocket: Represents the interface for a Bluetooth socket (similar to a TCP Socket).
BluetoothServerSocket: Represents an open server socket that listens for incoming requests (similar to a TCP ServerSocket).
BluetoothClass: Describes the general characteristics and capabilities of a Bluetooth device.

In our example we are going to create an application which get the information about the Bluetooth connections is activates and deactivates Bluetooth.

FREE DOWNLOAD FULL SOURCE CODE !!!!

Final Output:

Please check the screenshots attached.

  

Step 1. First we need check Bluetooth connection. So Create new class named “Connections”.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

public class Connections {       private static boolean state = false;       public static boolean blueTooth() {           BluetoothAdapter bluetooth = BluetoothAdapter.getDefaultAdapter();         if (!bluetooth.isEnabled()) {             System.out.println("Bluetooth is Disable...");             state = true;         } else if (bluetooth.isEnabled()) {             String address = bluetooth.getAddress();             String name = bluetooth.getName();             System.out.println(name + " : " + address);             state = false;         }         return state;     }   }

Step 2. Now when we got the response from the Connections class in our Main Activity with BT in Off state we get dialog for On BT.

Then we create new method into main activity class for the setting up all the Bluetooth information into Text View.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59

public class MainActivity extends Activity {       private static final int REQUEST_ENABLE_BT = 12;     private TextView out;     private BluetoothAdapter adapter;       @Override     public void onCreate(Bundle savedInstanceState) {         super.onCreate(savedInstanceState);         setContentView(R.layout.main);           out = (TextView) findViewById(R.id.tvBluetoothInfo);         setBluetoothData();           if (Connections.blueTooth()) {             Intent enableBtIntent = new Intent(                     BluetoothAdapter.ACTION_REQUEST_ENABLE);             startActivityForResult(enableBtIntent, REQUEST_ENABLE_BT);         }     }       @Override     protected void onActivityResult(int requestCode, int resultCode, Intent data) {         // TODO Auto-generated method stub         super.onActivityResult(requestCode, resultCode, data);         out.setText("");         setBluetoothData();     }       private void setBluetoothData() {           // Getting the Bluetooth adapter         adapter = BluetoothAdapter.getDefaultAdapter();         out.append("\nAdapter: " + adapter.toString() + "\n\nName: "                 + adapter.getName() + "\nAddress: " + adapter.getAddress());           // Check for Bluetooth support in the first place         // Emulator doesn't support Bluetooth and will return null           if (adapter == null) {             Toast.makeText(this, "Bluetooth NOT supported. Aborting.",                     Toast.LENGTH_LONG).show();         }           // Starting the device discovery         out.append("\n\nStarting discovery...");         adapter.startDiscovery();         out.append("\nDone with discovery...\n");           // Listing paired devices         out.append("\nDevices Pared:");         Set<BluetoothDevice> devices = adapter.getBondedDevices();         for (BluetoothDevice device : devices) {             out.append("\nFound device: " + device.getName() + " Add: "                     + device.getAddress());         }     }   }

For More Details visit following links.

• http://developer.android.com/reference/android/bluetooth/BluetoothAdapter.html

I hope you enjoy this tutorial and it would be helpful to you.