Simple Demo PIC32+Bluetooth Schematic and Android Code -Need bidders from United States

Code and hardware design to allow blue tooth communication from one android application (running on device with Android 4.2.1) to two different circuit boards featuring a PIC32MX450F256L MCU by microchip, including: 1) recommendation and specification of economical but reliable blue tooth components, and circuit schematic including connection to PIC32MX450F256L, in native format for Design Spark PCB v6.0. Avoid use of all analog pins (AN0 to AN27) and USB (host-mode) pins if possible. Exclusions:circuit ICSP, Oscillator and power supply and power supply connections to VDD, AVDD, Vcap, VSS and AVSS. Assume use of 8.0 MHz primary HS oscillator and 60 MHz system clock. 2) java code for Android side application which can a command packet containing two bytes comprising a command byte and a data byte. As this code will be copied and pasted into my code, the code must be very simple including only one \"Send\" button for initiating transmittal of command packet not using any custom classes other than \"MainActivity\" and only two command 0x01, 0x02 and one data 0x01. When a 0x02 command packet is received from the coupled PIC32 hardware accessory, the word \"Hello\" appears on the user interface. Code must be documented in English with explanatory comments and variables must be descriptively named. Code must compile in Eclipse, ADT and use API 16 3) c code in the form of a file \"main.c\" and any supporting files which will compile in MPLABx xc32 v1.70 which receives the command packet with 0x01 command byte and 0x01 data byte and upon receiving the packet returns a command packet including a 0x02 command byte and 0x01 data byte. Again, needs to be the simplest possible code to achieve this purpose. 4) A 1-2 minute video on .avi or .wmv format suitable for viewing on Windows 8.0 discussing the code, demonstrating successful pairing and two-way communication between the android and hardware accessory devices. 5) Concise and clear written email support responses to clarification requests for the purpose of transferring and validating the code in my own application. 6) Review USB schematic attached and provide corrections.