Analysis Of The Most Recent Trojans On The Android Operating System

The current increase in smartphone users has caused various mobile device operating system companies to compete with each other to create a mobile device operating system that is suitable and acceptable to the public. Competition among mobile operating system market shares can be analyzed using the Lotka-Volterra model. This study aims to reconstruct the Lotka-Volterra model for the cellular operating system market share in Indonesia. In addition, a stability analysis was carried out, which aims to determine the stability of the competitive model for the market share of the operating system in Indonesia. The results of the study show that a competitive Lotka-Volterra model can be built on the Android and iOS operating system market share in Indonesia. In this model, there are four equilibrium points, one of which is unstable, and the other three equilibrium points are conditionally stable.

Help Without Borders: How the Google Android Case Threatens to Derail the Limited Scope of the Obligation to Assist Competitors

Instant messenger, often shortened to IM is one type of communication service that allows person to have a conversation (chat) privately with others via the internet. Within the calls & messaging on Android and iOS operating systems, they both have an equal value in the terms of innovation and performance. In this work, we focus on evaluate the performance of the IM application on Android and iOS operating systems used several criteria; delay, packet size, and throughput. We use two methods of data collection; primary and secondary data, and compare the IM application using simulation methods. Input parameters for this simulation is in the stanza form of a text message, and the output consists of delay, packet size, and throughput. The results of this work indicate that the IM on iOS operating system with criteria of delay, packet size and throughput can send and receive messages faster than IM on android operating system.

The purpose of the work is to analyze, evaluate, and identify the advantages and disadvantages of mobile operating systems. The methodology used in the work, consists in determining the requirements for modern technologies for using mobile operating systems, which includes studying their advantages and disadvantages, investigated through the prism of updated technical and technological requirements for highly effective innovative information technologies, mediated by the development and improvement of technical means of functioning in the most used industries. The scientific novelty of the work lies in the study, analysis, comparison and identification of positive and negative criteria for the design, development and implementation of mobile operating systems as significant levers for ensuring efficiency and optimizing functioning in all industries that require mobility of decision-making in modern conditions. Conclusions. The factors influencing the development trends of mobile operating systems are identified, using the example of the introduction and implementation of iOS 26. The criteria are analyzed and the methods of updating the system in recent years are characterized. The main features of iOS 26 are studied: design, security, and the Apple ecosystem. The features of the updated design were tested and the main characteristics of the updated design were studied, and the quality of the implemented built-in artificial intelligence in the presented updated version was analyzed and assessed. The indisputability of the proposed updated flexible personalization and other elements that deserve analysis are established, and aspects that require further study, expansion, and improvement are identified. Research was conducted on the revolutionary design change of Liquid Glass and the updated operating system version numbering system was studied, and modern accessory security policies were evaluated, namely the control of connected devices in a locked state. Platform unification is being developed: synchronization of the design system between all Apple devices. Based on the criteria-based and phased analysis of the features of IOS26, Based on key security, design, and ecosystem characteristics, key factors have been updated to ensure the development of a methodology for further improving such mobile operating systems. Considered revolutionary design changes: Liquid Glass as the next stage of interface evolution, where it is determined that iOS 26 represents the first radical redesign of the system since iOS 7, based on a single design language of Liquid Glass. The proposed concept fundamentally changes Apple's approach to visual design, combining elements of glass morphism with dynamic effects. It has been found that unifying visual elements across all applications and system components creates a seamless experience across the entire Apple ecosystem, given the fact that the system also automatically adapts the intensity of effects depending on device performance and accessibility settings. The new operating system version numbering system was investigated and fundamental changes in the operating system branding strategy were identified, reflecting a long-term planning strategy for improving the mobile operating system and a focus on the future.

Android is the most popular mobile platform today, and it is also the mobile operating system that is most heavily targeted by malware. Existing static analyses are effective in detecting the presence of most malicious code and unwanted information flows. However, certain types of malice are very difficult to capture explicitly by modeling permission sets, suspicious API calls, or unwanted information flows. One important type of such malice is malicious application logic, where a program (often subtly) modifies its outputs or performs actions that violate the expectations of the user. Malicious application logic is very hard to identify without a specification of the normal, expected functionality of the application. We refer to malicious application logic that is executed, or triggered, only under certain (often narrow) circumstances as a logic bomb. This is a powerful mechanism that is commonly employed by targeted malware, often used as part of APTs and state-sponsored attacks: in fact, in this scenario, the malware is designed to target specific victims and to only activate under certain circumstances. In this paper, we make a first step towards detecting logic bombs. In particular, we propose trigger analysis, a new static analysis technique that seeks to automatically identify triggers in Android applications. Our analysis combines symbolic execution, path predicate reconstruction and minimization, and inter-procedural control-dependency analysis to enable the precise detection and characterization of triggers, and it overcomes several limitations of existing approaches. We implemented a prototype of our analysis, called TriggerScope, and we evaluated it over a large corpus of 9,582 benign apps from the Google Play Store and a set of trigger-based malware, including the recently-discovered HackingTeam's RCSAndroid advanced malware. Our system is capable of automatically identify several interesting time-, location-, and SMS-related triggers, is affected by a low false positive rate (0.38%), and it achieves 100% detection rate on the malware set. We also show how existing approaches, specifically when tasked to detect logic bombs, are affected by either a very high false positive rate or false negative rate. Finally, we discuss the logic bombs identified by our analysis, including two previously-unknown backdoors in benign apps.

Ever since its initial release in 2008, the Android operating system has rapidly grown to become the world’s most widely used mobile operating system. Mobile vendors extend the Android Open Source Project (AOSP) led by Google to customize their own Android variants. With the AOSP releasing new versions frequently, vendors need to periodically carry out Android upgrades that integrate the latest code changes from AOSP into their Android variants. Both the AOSP and Android variants independently undergo complex modifications. Consequently, Android upgrades often lead to merge conflicts caused by competing changes to the same code line. Vendors have devoted significant effort to understanding and resolving these problems. Despite extensive research on Android upgrades and merge conflicts, there is little understanding of the conflict-related activities performed in Android upgrade practice, and the corresponding challenges faced by practitioners . In this study, we employed a qualitative research methodology involving questionnaires with 120 practitioners and interviews with a leading Android vendor to explore the challenges and improvement opportunities. Our investigation demonstrates that Android upgrade process is fundamentally an exercise in architectural evolution, necessitating the adoption of architectural thinking rather than relying on mere code-level patches to systematically address upgrade-induced challenges. We have identified challenges at different stages of Android upgrade implementation, including baseline analysis, conflict reason analysis, conflict resolution, and conflict impact analysis. Our findings indicate opportunities for enhancing the Android upgrade practice, particularly in documentation, management, refactoring activities, and team collaboration. Additionally, we outline future research directions from an architectural perspective. We envision that our study can benefit software ecosystems where customized downstream derivatives need to maintain co-evolution with their upstream core.

One of the main directions of information systems development is to increase the efficiency of collecting, processing and exchanging information through the introduction of modern data transfer technologies, automated remote monitoring and control. The cornerstone of this concept is mobile devices that solve the issue of operational data exchange and processing. Modern mobile services used including the exchange and processing of personalized, banking and critical data are the result of the steady increase in the number of crimes in the field of information security in relation to and using mobile devices. The widespread use of these devices for access to protected information contained in information systems has given special importance to the issue of information security.The subject of this research is to assess the current state of information security mechanisms for mobile operating systems that form the basis of the structure of episodic distributed mobile networks. The Android OS (operating system) was used as an example. The article discusses the problems of the development of a mobile ecosystem and methods aimed at solving them, the main vectors of malicious impact, ways of countering the means of static and dynamic analysis and modern protection mechanisms.

This study focuses on the state of application development in developing countries. The first objective is to estimate the existence of application vendors locating in developing countries. The second objective is to identify some reasons for developing country software vendors to enter mobile application markets rather than more traditional software markets. We argue that app stores offer a possibility for developing countries to pass some of the problems that come with industrialisation by partly post-industrialising directly. This study is divided to two phases which study the existence of application vendors in developing countries and their characteristics from different viewpoints. The first phase focuses on the analysis of the most popular applications in Google Play, Apple Store and Windows Phone Store. The second phase starts by analysing the email addresses of application vendors who sell their products in Google Play marketplace for devices using Android operating system and continues by sending questionnaire to those application vendors whose email addresses has country domain belonging to developing country. Our study shows that mobile applications are developed in developing countries, although, the biggest part of application vendors is located in developed countries. Among developing countries, most important mobile application producers belong to upper-middle income economies, such as China or Russia, or to lower-middle income economies, such as India. However, there appears to be few application vendors who operate from low income economies, such as Bangladesh or Kenya. According to our results, application vendors located in developing countries choose to develop mobile applications largely due to same reasons than application vendors located in developed countries. They prefer mobile application marketplaces, because they offer easy access to large amount of potential customers. Android platform is appreciated for its low development and access cost, however, it is criticized for the wide range of customer interfaces.

The global sales market is currently led by devices with the Android operating system. In 2015, more than 1 billion smartphones were sold, of which 81.5% were operated by the Android platform. In 2017, it is estimated that 267.78 billion applications will be downloaded from Google Play. According to Qian, 90% of applications are vulnerable, despite the recommendations of rules and standards for the safe software development. This study presents a classification of vulnerabilities, indicating the vulnerability, the safety aspect defined by the Brazilian Association of Technical Standards (Associacao Brasileira de Normas Tecnicas - ABNT) norm NBR ISO/IEC 27002 which will be violated, which lines of code generate the vulnerability and what should be done to avoid it, and the threat agent used by each of them. This classification allows the identification of possible points of vulnerability, allowing the developer to correct the identified gaps

The Balinese language which is used in daily life on the island of Bali has experienced a shift in usage so it needs to be preserved. In an effort to preserve the Balinese language and script, the Provincial Government issued Bali Governor Regulation Number 20 of 2013 and Regulation number 1 of 2018. I Made Suatjana submitted a proposal that the Balinese script be included in Unicode to make it easier to display Balinese script on digital media. Cokorda Rai Adi Pramartha developed keyboards or keyboards and an application called T@miang to facilitate typing Balinese characters on computer devices. Computer equipment is slowly becoming obsolete, replaced by mobile devices used by 53.03% of users in Indonesia, so it is necessary to build a Balinese script keyboard that can be used on mobile devices. PaTik Bali is built for mobile devices with Android operating system. PaTik Bali layout is adapted to T@miang keyboard layout. PaTik Bali version 1.0 only uses the Balinese script on each keyboard key. In version 2.0 each button on PaTik Bali has been added Latin letters because of the large number of entries on the Google Play page. Based on data recorded on the Google Play Console, there are 41,820 devices that have installed the Balinese Keyboard (PaTik Bali) application, 99.19% are from Indonesia. In general, the PaTik Bali application can be accepted in the community, this can be seen from the average rating given by users on Google Play which is 4.27 on a scale of 5. However, some users complain about the incorrect form of letters. The PaTik Bali application uses fonts that have been embedded in the Android operating system so that it can be used as a keyboard in other applications. This font still has enough problems. To fix this problem, it is necessary to develop the Balinese font then ask Google as an Android developer to enter the new font into the Android operating system.

—The rapid advancement of mobile technologies has led to increasingly powerful and feature-rich devices, yet this progress has also intensified the challenge of managing energy consumption effectively. Power optimization has therefore become a critical focus in mobile operating systems (OS), aiming to balance performance, functionality, and energy efficiency. As mobile devices integrate more complex hardware components and resource-intensive applications, ensuring sustainable power usage has become essential for improving battery life, user experience, and environmental sustainability. This research explores the fundamental question: How can mobile operating systems intelligently manage hardware and software resources to minimize power consumption without compromising performance or usability? To address this, the study examines key power optimization strategies and mechanisms integrated within modern mobile OS architectures, including Dynamic Voltage and Frequency Scaling (DVFS), power-aware CPU scheduling, Doze and App Standby modes, adaptive display and sensor management, and network optimization. The research also investigates the role of advanced techniques such as context-aware power management and machine learning-based predictive models in achieving dynamic, intelligent energy control. Using tools like Trepn Profiler, PowerTutor, and Android Battery Historian, the study evaluates how power consumption patterns can be analyzed and optimized in real time. The findings reveal that combining hardware-level techniques (like voltage scaling and clock gating) with software-level optimizations (such as adaptive scheduling and contextual awareness) results in significant energy savings while maintaining user satisfaction. Furthermore, the study highlights emerging challenges, including the trade-offs between performance and energy efficiency, the integration of AI for predictive optimization, and the need for sustainability across the device lifecycle. Ultimately, this research demonstrates that power optimization in mobile operating systems is not merely a technical requirement but a cornerstone of sustainable computing. Through intelligent power management, future mobile OSs can achieve greater efficiency, extended device longevity, and reduced environmental impact aligning technological innovation with eco-efficiency and user-centric design.

As mobile devices and applications continue to grow in popularity worldwide, so do the rise of cybersecurity attacks and threats to daily users of both Android and iOS devices on a widespread basis. These attacks not only target mobile devices at the application level but also at the Operating System (OS) device level and Application Programming Interface (API) level extending the Internet of Things (IoT). This paper will address the security vulnerabilities in Android Operating System at the intersection of APIs, device OS, and application-level vulnerabilities by identifying an intersection of commonalities to create mitigation strategies and best practices for securing mobile devices for organizations. The study recommends the adoption of processes of authentication on mobile devices and web-based log-ins as well as access control mechanisms that can mitigate the overlapping security challenges of APIs, mobile devices OS and applications using optimal resources to enhance security. This was achieved by analyzing the threats and vulnerabilities of API.KeywordsAPIsSecurity vulnerabilitiesMobile OSAndroidiOS

While media buzz regularly circulates around iPhone and Android, Nokia still leads the pack in terms of world market share. Symbian, for instance, remains the most widely used mobile operating system. With Nokia's open development platform, the opportunities available for mobile developers to target this vastly popular operating system are abundant and clear. Use Qt to target both platforms: Symbian, the most widely used mobile operating system in the world, as well as MeeGo, the Intel/Nokia platform for mobile devices. Develop HTML5 applications for both Symbian and MeeGo platforms that will run with little modification on other mobile platforms. Novice developers learn the basics of Qt with a mobile slant, giving them the ability to target both desktop and mobile platforms. What youll learn How to do Qt basics What is QML or the Qt Markup Language What is Qt for Meego and how to use it and how to use it How to work with the Web Runtime Why mobile development is different How to port/support MeeGo and Symbian platforms Who this book is for This must have book is for mobile developers wanting to target the Meego and Symbian platforms (either as the sole platform or in cross-platform development), and existing mobile developers wanting to start using Qt. Table of Contents Introducing Nokias Software Platform Designing Your Application Working with the Nokia Qt SDK Beginning Qt Development Doing More with Qt Introducing Qt Quick Developing with HTML5 Testing Your Application Deploying Your Application

Mobile devices implementing Android operating systems inherently encourage opportunities to create and implement malicious software. This opportunity increases as dissemination of the Android OS to standalone devices, such as cameras, increases. The problem intensifies when these devices utilize cloud storage service capabilities. Previous security and forensics research is focused on Android malware detection, data leakage and operating system modifications. In this research, malware was developed and implemented on a camera running an Android Operating System. The execution of this malware successfully transferred images to a secondary cloud location without notifying the user about the data transfer or raising noticeable indicators with an industry accepted mobile device analysis toolkit. The research contribution is an initial empirical analysis of the viability of software to divert an image and store it in a secondary cloud storage environment without alerting digital forensics software about the malicious nature of the malware.

Mobile operating systems have expanded from running exclusively on smartphones to include tablets and music players as well, making them available to a larger audience. These operating systems are responsible for maintaining a multitude of schedules, messages, calls, music, documents, applications, photos, videos, and other personal data with the goal of increasing efficiency. Because of this, developers of mobile operating systems have built in configuration options to these operating systems to better protect the device from security vulnerabilities. However, not all of these operating systems have such settings turned on when the device is pulled out of the box. Furthermore, not all users are aware of how to best protect their information, nor the kind of issues that should be considered when owning and using these devices. This paper suggests best practices for the three major mobile platforms - Android, BlackBerry, and iOS - to mitigate and/or prevent unauthorized access, loss of information, and loss of confidentiality.