FAU Android

FAU's local android experts!

RIFL Update T-Minus: One Week

Posted by Charles Norona April - 15 - 2010 - Thursday

Here, I have compiled a collection of updates given that I have been busy managing our team in wrapping up our Engineering Design II project:

  • Power Metrics: In order to incorporate more electrical engineering aspects I have uploaded a couple of creenshots of some power consumption metrics acquired by the University of Michigan’s PowerTutor (http://powertutor.org/) application while the RIFL client application was running on the phone. Unfortunately, it only tells us about LCD and CPU power consumption (GPS and WIFI were not being used by the app). We still need to find out how much power was being consumed by the sensors and the Bluetooth radio. Both I think can be estimated based off of the information from the appended datasheets:

    AK8973 3-axis Electronic Compass:
    BMA150 3-axis Accelerometer:

    We still need to find out more about the Bluetooth radio and how much power it consumes during an RFCOMM streaming transmission.

  • Base Station Application: I have cooked up a little applet to test out the tracking of the RIFL system as well as output an excel compatible table of sensor values. It performs fairly well but as expected there are some inaccuracies. Allan is currently working on an the front end which will add many features to the RIFL system and take advantage of the capabilities of this applet. The test applet is available at http://engineering-design-ii-group-6-spring-2010.googlegroups.com/web….


  • Bluetooth Connectivity: In the past week we have successfully managed to connect the PC to one of the Nexus Ones we will be using as a prototype. After having implemented the RFCOMM server-client programming into the base station and the mobile device it was simply a matter of pairing the two devices together and matching their universally unique IDs (UUIDs) before they would server application on the base station would connect via Bluetooth to the client application on the mobile device.

Comments are closed.