es1011defaultproject for Android Publisher's description
This is the android project for the "embedded system 10/11" course of the Department of Information Engineering of the University of Padua
This is the android project for the "embedded system 10/11" course of the Department of Information Engineering of the University of Padua.
Default Course Project Design and implement an application that records and charts data coming from the accelerometer built into your device. The application should manage and store multiple recording sessions. The application should provide at least the following 5 user interfaces (UIs).
A UI that lists all the recording sessions stored on the device and makes it possible to visualize (see UI #2) and delete any of the sessions. To better understand how a list may look like, consult this page. A UI that shows a single recording session in detail. Data from the session must be displayed in graphical form as a run chart. Some form of support for panning and zooming is mandatory; however, support for data exploration through gestures (e.g., pinch to zoom) is optional. Further optional features for the UI are: support for multiple visualization scales (e.g., linear and logarithmic); display of the current recording session with real-time update; display of data in the frequency domain. A UI that shows the details (exact values of the readings, date and time, ...) of a single record. It is suggested that this UI is entered from UI #2 by touching a data sample. A UI that allows the user to start a new recording session after having set the appropriate parameters (sampling time, duration, axes to record, ...) for the session. A UI that is displayed while recording is in progress. The UI should display some summary information about the session (e.g., number of samples recorded so far) and offer the possibility of stopping the recording process.
All UIs must be correctly displayed in both portrait and landscape mode with the exception of UI #2, where support for portrait mode is optional. Error messages should be presented to the user when appropriate (e.g., when no more space is available for recording data). Be aware that quality will be rewarded more than quantity. For instance, an application that provides only basic functionalities but is "rock solid" will get higher grades than an application that offers a lot of optional functions but does not respect the UI guidelines for the chosen platform, does not properly handle error conditions, stops recording data when it is moved to the background, and so forth. The quality of the source code will be also considered in the grading process. For instance, source code that is properly commented and highly modular will be favored over code that lacks comments, uses cut-and-paste instead of inheritance, and so forth.
System Requirements:No special requirements.
Program Release Status: New Release
Program Install Support: Install and Uninstall