DELTA++: Reducing the Size of Android Application Updates android project |Reducing the Size of Android Application Updates android project free download | Reducing the Size of Android Application Updates android project source code free download
DELTA++: Reducing the Size of Android Application Updates
ABSTRACT:
This method of creating and deploying update patches improves on Google Smart Application Update by first unpacking the Android Application Package and then compressing its elements individually. The smartphone user can then download a smaller patch. Experiments show that performance yields 49 percent more reduction relative to Google’s solution, increasing the savings in cellular network bandwidth use and resulting in lighter application server loads. This reduction in Android application-update traffic could translate to a 1.7 percent decrease in annual US cellular traffic. Similar methods applied to iPhone application updates could yield even greater savings.
EXISTING SYSTEM:
To reduce application update traffic, Google developed Google Smart Application Update, which uses a compression method transparent to application developers and Android users. Modifications to the Google Play application and the server software enable Google Play to construct new versions of updated applications by applying a patch to the application version installed on the user’s Android device. Although this solution has made inroads into traffic reduction, its compression methods are not optimal.
DISADVANTAGES OF EXISTING SYSTEM:
DELTA could successfully decrease application update traffic and enable savings in the cellular network and data centers but we want much more.
PROPOSED SYSTEM:
Notably, delta encoding is at the Android Application Package (APK) level only, which limits the possible reduction in patch size. To address this shortcoming and reduce update traffic even more, we extended our Delta Encoding for Less Traffic for Apps (DELTA), an update mechanism based on the bsdiff delta encoding tool.
We have implemented DELTA++ as server side software, which constructs update patches and serves them by request, and as an Android application that deploys the received patches and updates the installed applications.
ADVANTAGES OF PROPOSED SYSTEM:
ü Unlike Google Smart Application Update, DELTA++ unpacks the A PK and then compresses its individual modules. Our experimental results show that DELTA++ can reduce application update size by 77 percent on average, relative to a 55 percent average size reduction possible with Google Smart Application Update.
ü Our experiments show that additional battery use is negligible.
ü Although DELTA++ is clearly superior to Google Smart Application Update in patch size and traffic reduction, its advantage in deployment time is less straightforward.
MODULES:
] Patch Generation
] Construction
] Deployment
] Battery Discharge
MODULES DESCRIPTION:
Patch Generation
The size of the patch that the delta differencing algorithm computes depends primarily on the extent to which the old and new file versions differ, but compression can also affect that size. If two files have only a few differences, the compressed file versions might differ considerably on a binary level because of how they were processed during compression. The same is true of the APK, which, as the sidebar “Inside an Android Application Package File” makes clear, is basically a compressed archive of all the files comprising an Android application. DELTA++ aims to determine the difference between the application files within an APK, as opposed to the APKs themselves. DELTA generated a patch as a delta difference between the application’s old and new APK versions. The bsdiff delta encoding tool produces this delta patch in the server, and the bspatch tool deploys the patch in the smartphone. DELTA works generally like Google Smart Application Update in that both use delta encoding and neither unpacks the APK. DELTA++ improves on both methods by decompressing the APK and exploiting its specific structure. The result is a much smaller patch.
Construction
DELTA++ patch construction consists of eight steps: DELTA++ first decompresses the old and new APK versions and traverses the manifest files to get the names, paths, and SHA-1 hash digests for all the files in two APKs. It then marks the files in the new version. If the file is in the new version but not in the old one, it is marked NEW. If the file is in both versions but its SHA-1 sums differ, it is marked UPDATED. If the file is in both versions, and the SHA-1 digests are the same, it is marked SAME. Finally, if the file is in the old version but deleted in the new one, it is marked DELETED. After marking is complete, DELTA++ copies the files marked NEW into the constructed patch. To compute differences between the old and new APK versions, DELTA++ inputs the files marked as UPDATED to the bsdiff delta encoding algorithm and copies this difference into the constructed patch. Because of the overhead in creating the delta file, the difference between small files can sometimes exceed the size of the
Deployment
Deployment begins by decompressing the received patch into a temporary directory. DELTA++ then uses the ApplicationInfo class to load the APK of the current application version and uses the PatchManifest.xml file in the patch to delete all the files that are no longer required. By applying all the differences in the patch to the proper files, DELTA++ updates them. It then copies all the NEW files from the patch to the old application version. At this point, the old and new application versions contain exactly the same files. The next step is to construct the APK by compressing all the files into a zip archive with a .apk extension. Finally, DELTA++ uses the Android PackageInstaller built into the application to install the resulting APK.
Battery Discharge
Although DELTA++ is clearly superior to Google Smart Application Update in patch size and traffic reduction, its advantage in deployment time is less straightforward. Both methods use the Android PackageInstaller application to install the update, but it takes DELTA++ approximately 50 seconds longer on average to deploy the patch. To determine the effect of this longer deployment on the smartphone battery discharge, we created another Android application, DELTA Energy Profiler, and made it free through Google Play. The application enables every Android user to see how much power the device components (CPU, 4G, screen, and so on) are consuming. The application provides a first-order estimate by maintaining certain conditions (for example, screen turned on) and measuring battery level every 30 seconds during a long period. For our purposes, we set that period to 40 minutes for experiments with 4G radio and 60 minutes for all other experiments. Energy Profiler measured power consumption as the percentage of battery consumed per second during four activities: • Idle. Device is awake with its screen turned off and only background routines running. • Screen. Device is idle, but its screen is turned on (maximum brightness). • 4G. Device is downloading a file using 4G radio. • Patch deployment. Device is applying the delta encoded patch (includes patch construction and installing the newly constructed version).
SYSTEM REQUIREMENTS:
HARDWARE REQUIREMENTS:
Ø System : Pentium IV 2.4 GHz.
Ø Hard Disk : 40 GB.
Ø Floppy Drive : 1.44 Mb.
Ø Monitor : 15 VGA Colour.
Ø Mouse : Logitech.
Ø Ram : 512 Mb.
Ø MOBILE : ANDROID
SOFTWARE REQUIREMENTS:
Ø Operating system : Windows XP/7.
Ø Coding Language : Java 1.7
Ø Tool Kit : Android 2.3 ABOVE
Ø IDE : Eclipse
REFERENCE:
Nikolai Samteladze and Ken Christensen University of South Florida “DELTA++:REDUCING THE SIZE OF ANDROID APPLICATION UPDATES ”IEEE 2014.
VIDEO OUTPUT
thank you for your comment
pls call me on 8125424511