Improve Application in Android Devices

Improve Application in Android Devices 
Even after the introduction of Android Runtime (ART) in the latest release of Android Lollipop, Android Operating System still struggles in areas such as application launch time, especially during sluggish or memory crunch situations. When a new application is launched in a sluggish condition, low memory killer (LMK) gets initiated in order to free some memory by killing the already running applications. The current LMK approach kills application based on how recently it was used. This approach does not consider various other user scenarios such as how frequently the application was launched or how important that application is to user. In our proposed solution, we aim to improve user experience by reducing or removing the delay at memory crunch situations with efficient use of LMK.https://codeshoppy.in/
Market share for android smartphones have been increasing exponentially day by day. With this increase in numbers of phones sold every year, even the demands for a better quality of the android phones are increasing in the competitive market. To meet the high expectations of users, companies are putting good amount of efforts in the improvement of hardware as well as software. While smartphone hardware market is already saturating to an extent, there is a lot of scope for improvement on software design on top of Google’s stock Android for better user experience. As far as user experience is concerned, application launch time is one of the most important performance parameter for any smartphone device. In general, due to the usage of many applications, a good amount of RAM gets consumed resulting in phone sluggishness. This sluggishness is very much visible to the user especially when a particular application, which user wanted to re-use, is already killed by LMK. In our proposed solution, we intend to provide a better user experience by improving LMK’s algorithm based on user’s usage of various applications. Thereby, enhance user experience by decreasing application launch time of favorite applications.
Android operating system has an in-built task killer, called low memory killer (LMK). The LMK keeps an eye on the real time RAM usage of all applications. Whenever excess of RAM is consumed, the LMK starts killing applications to free-upsome memory [4][5]. For the killing of applications, LMK has defined some set of priorities through oom_adj value. This oom_adj is set by android kernel for each process on the Android system. It ranges from -17 at the highest to +15 at the lowest. Therefore, in memory crunch situation, LMK is called and it starts killing applications from the lowest oom_adj i.e. oom_adj value of +15. For this paper, we target only the cached applications that range from +9 to +15 [5]. As important applications and services have higher priority than cached applications.
 
Most users are expected to have some favorite applications which they keep on re-launching. For the solution proposed .we target on improving the launch time of such 4 most frequently used applications. We keep these 4 most important applications to be always running in the background. A stack of frequently used applications is maintained which is created through learning the user’s usage. These four applications keeps getting updated according to the change in the usage of the user after every half an hour when phone is left in idle state for a little while. Mostly the update happens when the phone is kept in idle state to lower the overhead. These applications are then launched and kept at the background killing them only as a last resort. When the stack is updated, the application that gets removed from the stack becomes normal application running at the background just like others. Another advantage of DCA algorithm over DSPO algorithm is that since the boot complete it keeps basic 4 applications opened. As those basic applications are already opened, user can see a good amount of performance improvement in launch of those 4 applications after boot .
https://codeshoppy.com/shop/product/agri-shop-for-farmers/
https://codeshoppy.com/shop/product/toll-gate-app/
https://codeshoppy.com/shop/product/student-attendance/
https://codeshoppy.com/shop/product/college-management-system-2/
https://codeshoppy.com/shop/product/ebanking-app-to-manage-account-and-transfer/
https://codeshoppy.com/shop/product/ecom-mobile-app 

Android Application Implementation Using Formal Method

Android Application Implementation Using Formal Method

Information security is becoming more and more importantnowadays. Companies, governments and militaries are con-necting themselves to the internet for various reasons suchas to provide certain services to public, to cooperate withpartners and to allow their staffs to work remotely and soon. However, when they connect to internet, they are alsoexposing a possible entrance for the adversaries to break intotheir internal networks and to access to their private data ifthere are vulnerabilities. It is also the same case when it comesto the individual person who connects oneself to the internetwith mobile devices. Personal data leak may cause troubles oreven financial lost [3], [4].As mobile devices are replacing traditional desktop as amain portal to internet, people rely on their mobile devicesto handle all sorts of daily activities such as online shopping,internet banking and subscribing to premium services, whichare almost impossible in the past on mobile devices. Onemight not even realize that its mobile device stores so much ofits personal information that the security of such informationon these mobile devices has become a critical and seriousproblem.Android operating system has become the most popularmobile operating system [5] , however, Android apps are notas secure as one might think it should be. The vulnerabilitiesmight come from flaws of protocol an Android applicationadopted [6], the misunderstandings when implementing proto-cols in the apps [7], not aware of the assumptions when usingcertain SDKs [8] and even from Android operating systemitself [9], [10].Many of the vulnerabilities are actually implementation spe-cific. Therefore, it’s imperative to study the security propertyof concrete implementation of Android apps to improve thesecurity level of them.In this dissertation, the author presents the preliminaryresults of his ongoing research project mainly in two scenarios:A formal analysis of Android apps that provide Single Sign-on (SSO) service and the initial analysis of information flowleak in Android appsThis section is about the formal analysis of SSO implemen-tation on Android. It first introduces background of SingleSign-on (SSO) protocol; then a typical SSO process; afterthat is the method used in analyzing SSO implementation onAndroid and finally the outcome of the analysis.A. SSO BackgroundWith the development of information technology, more andmore websites emerge and they have demands to record users’data. User needs to register at these websites before they canuse the services from them. However, the more accounts auser has, the more reluctant the user becomes to register newaccounts as this will increase the cost of managing differentaccounts across different websites. Therefore, the user maytend to use a same password for its different accounts. Never-theless, it will inevitably increase the risk that one passwordbeing compromised endangers its identities on other websites[11], [12]. The attacker can try to break user’s other accountswith brute-force attack. It even exacerbates this situation whenuser uses simple password.Single Sign-on is an authentication scheme which allowsa user to login to a third party application (service provider,SP) with the identity it registers in an identity provider (IdP).This protocol mainly involves three parties, namely, the user,the SP and the IdP. Although SSO protocol does not solve theproblem of using a same password across different websites,but it simplifies the account creation process or even skips ittotally, which eases the burden when a user uses a new website.It will also ease the cost of managing different accounts froma use’s perspective.As SSO becomes more and more popular, the securityof SSO is one of the concerns that recent researches focuson [6], [8], [13]. However, most prior studies only focuson SSO on desktop or web-based browser environment andfew of them have inspected the security of the concrete SSOimplementation in mobile platforms.Being a different platform other than the desktop or webbrowser, Android OS has its own attack surfaces and as-sumptions. Due to mobile device’s product orientation andthe physical limitation of a hand-held device, it is infeasibleor even impossible to deploy a real-time malware detectionsystem to protect Android from the attacks of virus or trojans[14]. Moreover, unlike the desktop browser, Android doesnot have important security mechanisms like the Same OriginPolicy (SOP) [1], [2] which is a standard on almost all modernbrowsers. This would let Android suffer from the vulnerabilitythat is not easy to exit in browser environment. Moreover, asmentioned above, there might be misunderstandings or hiddenassumptions regarding to the developer documentation of aprotocol which introduces more vulnerabilities to the concreteimplementation in Android apps. Therefore, it is important totake these factors into consideration and to inspect the concreteimplementation of SSO on Android OS in a systematic andrigorous manner.Formal analysis has been proved to be such an powerfulapproach which is systematic and partially automatic approachto analyze the design of a protocol or a system. Recentresearches adopting formal analysis have confirm its ability[9], [13], [15]. It can verify property CodeShoppy

One of the current state-of-the-art research on this problemis Droidsafe [22]. It claims to have developed a most full-fledged Android model so far to facilitate the information flowanalysis. Thus, it achieves the most precise and accurate resultcomparing to the former state-of-the-art framework FlowDroidon three sorts of benchmark: DroidBench and the other twosorts of benchmark developed by the same team of Droidsafe.However, one of the major drawbacks in this work isthat the information flow analysis is carried out in a flow-insensitive way. This, although covers all the possible eventorders and flows, decreases the precision of the analysis asnot all of the event orders are possible in Android operatingsystem. Therefore, one possible improvement to this work isto consider the possible event orders and to eliminate thoseflows that are impossible to occur. This contains two steps;first step is still using Droidsafe to detect all the informationflows between sources and sinks; then the second step is touse the possible event orders to eliminate the impossible flowsso that only the valid flows remain.Another drawback is Droidsafe still can not handle theimplicit flow.

https://codeshoppy.com/php-projects-titles-topics.html

 

 

Analyzing Security Property of Android Application

Analyzing Security Property of Android Application

 As mobile phones are becoming a main approachfor people to use to access internet, security is a major concernwhen people are using their mobile phones. Different from theweb browser which has mature isolation mechanisms to protectusers’ information such as cookies and credentials, Androidapp developers have to implement the isolation mechanism suchas the Single Origin Policy (SOP) [1], [2] themselves. Duringthe implementation process, it is highly likely that there isvulnerability in the implementation. Therefore, it is necessaryto perform analysis to the implementation before it is releasedto market. As part of an ongoing Ph.D. research project, thisdissertation inspects two scenarios. The first scenario is an appwhich provides Single Sign-on (SSO) service using FacebookSDK. The author builds formal models from the capturednetwork traffic of the app and uses a verifier Proverif to checkagainst the defined properties of the formal models. After theanalysis, one vulnerability is discovered which violates SOP. Asfor the second scenario, it is an initial analysis of informationflow leak in Android apps.CodeShoppy

Information security is becoming more and more importantnowadays. Companies, governments and militaries are con-necting themselves to the internet for various reasons suchas to provide certain services to public, to cooperate withpartners and to allow their staffs to work remotely and soon. However, when they connect to internet, they are alsoexposing a possible entrance for the adversaries to break intotheir internal networks and to access to their private data ifthere are vulnerabilities. It is also the same case when it comesto the individual person who connects oneself to the internetwith mobile devices. Personal data leak may cause troubles oreven financial lost [3], [4].As mobile devices are replacing traditional desktop as amain portal to internet, people rely on their mobile devicesto handle all sorts of daily activities such as online shopping,internet banking and subscribing to premium services, whichare almost impossible in the past on mobile devices. Onemight not even realize that its mobile device stores so much ofits personal information that the security of such informationon these mobile devices has become a critical and seriousproblem.Android operating system has become the most popularmobile operating system [5] , however, Android apps are notas secure as one might think it should be. The vulnerabilitiesmight come from flaws of protocol an Android applicationadopted [6], the misunderstandings when implementing proto-cols in the apps [7], not aware of the assumptions when usingcertain SDKs [8] and even from Android operating systemitself [9], [10].Many of the vulnerabilities are actually implementation spe-cific. Therefore, it’s imperative to study the security propertyof concrete implementation of Android apps to improve thesecurity level of them.In this dissertation, the author presents the preliminaryresults of his ongoing research project mainly in two scenarios:A formal analysis of Android apps that provide Single Sign-on (SSO) service and the initial analysis of information flowleak in Android apps

SSO Background With the development of information technology, more andmore websites emerge and they have demands to record users’data. User needs to register at these websites before they canuse the services from them. However, the more accounts auser has, the more reluctant the user becomes to register newaccounts as this will increase the cost of managing differentaccounts across different websites. Therefore, the user maytend to use a same password for its different accounts. Never-theless, it will inevitably increase the risk that one passwordbeing compromised endangers its identities on other websites[11], [12]. The attacker can try to break user’s other accountswith brute-force attack. It even exacerbates this situation whenuser uses simple password.Single Sign-on is an authentication scheme which allowsa user to login to a third party application (service provider,SP) with the identity it registers in an identity provider (IdP).This protocol mainly involves three parties, namely, the user,the SP and the IdP. Although SSO protocol does not solve theproblem of using a same password across different websites,but it simplifies the account creation process or even skips ittotally, which eases the burden when a user uses a new website.It will also ease the cost of managing different accounts froma use’s perspective.As SSO becomes more and more popular, the securityof SSO is one of the concerns that recent researches focuson [6], [8], [13]. However, most prior studies only focuson SSO on desktop or web-based browser environment andfew of them have inspected the security of the concrete SSOimplementation in mobile platforms.Being a different platform other than the desktop or webbrowser, Android OS has its own attack surfaces and as-sumptions. Due to mobile device’s product orientation andthe physical limitation of a hand-held device, it is infeasibleor even impossible to deploy a real-time malware detectionsystem to protect Android from the attacks of virus or trojans[14]. Moreover, unlike the desktop browser, Android doesnot have important security mechanisms like the Same OriginPolicy (SOP) [1], [2] which is a standard on almost all modernbrowsers. This would let Android suffer from the vulnerabilitythat is not easy to exit in browser environment. Moreover, asmentioned above, there might be misunderstandings or hiddenassumptions regarding to the developer documentation of aprotocol which introduces more vulnerabilities to the concreteimplementation in Android apps. Therefore, it is important totake these factors into consideration and to inspect the concreteimplementation of SSO on Android OS in a systematic andrigorous manner.Formal analysis has been proved to be such an powerfulapproach which is systematic and partially automatic approachto analyze the design of a protocol or a system. Recentresearches adopting formal analysis have confirm its ability[9], [13], [15]. It can verify properties of protocol design in amathematical and rigorous manner 

https://codeshoppy.com/android-app-ideas-for-students-college-project.html