FILE MANAGMENT AND MEMORY STORAGE
Parnell Davis
POS/355
December 22, 2014
Professor, Eric Godat

FILE MANAGMENT AND MEMORY STORAGE

FILE MANAGEMENT, MINIMUM MEMORY AND STORAGE
The memory accessible to the kernel and consumer space must be at least 340MB at device implementation. Hardware machinery such as broadcasting systems, video, and other devices as that are not under the kernel's control are excluded from the 340MB designated memory. The absolute value "true" for ActivityManager.isLowRamDevice occurs when the implementation memory accessible to the kernel and user space is less than 512MB. A minimum of 1GB of non-volatile storage space available is required for application confidential data Device implementation. In addition 1GB is required for the datapartition. Android systems are futuristic, although it’s not mandatory; its best have at least 2GB of non-volatile storage available for application personal data as the user may desire to upgrade to the future releases.
Application Shared Storage
Storage is a major component within implementation as shared storage applications are a requirement for applications and must be 1GB or more available. Configuration with storage mounted by default is an additional requirement. It is necessary that the device include a Linux symbolic link from /sdcard to the actual mount point. It is even more crucial if the If the shared storage is not mounted on the Linux path /sdcard. In addition, system implementations are required to enforce mandatory rules as documented within the various systems for example: android.permission.WRITE_EXTERNAL_STORAGE permission on this shared storage. Communal storage space is obligated to be writable by any application which obtains an authorization. System hardware for user-accessible detachable storage space, such as a Secure Digital is contained in some implementation cards. On the contrary, some implementations allot internal (non-removable) storage as shared storage for apps.
Not considering the form of shared storage used, device implementations are mandated to make available some apparatus to make contact with the contents of joint storage from a host computer, such as USB mass storage (UMS) or Media Transfer Protocol (MTP). USB mass storage can be used however; Media Transfer Protocol is a better choice if the device implementation supports Media Transfer
Protocol:
It is best for Device implementations to incorporate a USB client port as well as a USB host port. The USB client port typically connects to a USB host with a standard USB-A port and uses the micro USB form factor on the device side. It is extremely necessary that existing and new Android devices meet the requirement to aide in desired upgrades. In order for the display to draw correctly when the device is oriented, it is best to locate the port underneath or allow software display rotary motion for all applications. Another requirement for applications is to have host linked to the device to allow the contents of the common storage capacity using either USB mass storage or Media Transfer Protocol. The Android Open Accessory API is required to support for the hardware feature and USB audio class as specified and documented in the Android SDK documentation. It is also desirable that there is support for USB battery charging specification as well.
If a device implementation includes a USB host port it usually contains a non-standard port form factor and ship with a cable or cables adapting the port to standard USB-A. It is also mandatory that the Android USB host API and indicate ample support for the hardware feature android. Hardware, usb, hosts [Resources, 53] and should take into consideration the Android Debug Bridge. Metric Performance Threshold Comments Application
Launch Time
The following applications should launch within the specified time.
Browser: less than 1300ms
Contacts: less than 700ms
Settings: less than 700ms
The launch time is measured as the total time to complete loading the default activity for the application, including the time it takes to start the Linux process, load the Android package into the Dalvik VM, and call on Create. Simultaneous Applications When multiple applications have been launched, re-launching an already-running