Our system comprises two key components: a custom power-intensive application named "SERVIVERSE”, and a battery optimizer connected to Firebase for data storage.
Custom Power-Intensive Application:
ServiVerse, designed to drain the phone's battery efficiently, utilizes built-in Android services such as Bluetooth, Wi-Fi, location services, sensors, and timers. Essential components of the application interface include a splash screen that displays a graphical representation when it launches, a home screen with a user-friendly dashboard made with grid layout and card views, and specialized functionality for Bluetooth, Wi-Fi, location, sensors, and timers depicted in Figure 2.
Figure 2: ServiVerseFeatures
Users may communicate with associated devices, control Wi-Fi connections, obtain textual map data with satellite views, retrieve different sensor readings, and use stopwatches and alarms by using these functions. Our unique, resource-intensive program "ServiVerse" has fundamental functions to provide users with a full user experience. To accurately achieve battery depletion, it periodically modifies its power consumption patterns to simulate practical situations when various processes run simultaneously in a mobile phone.
Use of Bluetooth feature to link devices for file transfer, the Wi-Fi module to mimic data-intensive actions like downloading huge files or streaming high-definition media. Furthermore, the app simulates ongoing GPS monitoring, giving important details about location-based power usage. The sensors show the impacts of sensor-intensive applications on battery life in addition to reading proximity, acceleration, temperature, humidity, brightness, pressure, magnetic effects, and RGB data. Additionally, the timer function not only includes a stopwatch but also integrates various alarms with diverse pre-installed ringtones, showcasing the power usage implications of timer-based applications.
Battery Optimizer:
Although there are already mobile phone battery optimizers available that improve performance by clearing cache, none of them include a built-in feature associated with the cloud. Our optimizer has an integrated function linked to the cloud (Firebase), where all the cached data is securely stored in encrypted format once it is offloaded. Figure 3 illustrates the phases involved in the battery optimizer development process using Android Studio.
Figure 3: Battery OptimizerDevelopment Procedure
In contrast, the battery optimizer, which is integrated with Firebase, comprises numerous interactive screens. The splash screen serves as an introductory interface during application loading, followed by a signup screen where users can register their personal information, enabling seamless integration with the system. With the use of a username and password, the login page guarantees safe user authentication. The optimizer offers comprehensive information on the phone's charging state, including battery level, temperature, voltage, health, and technology. Additionally, it also provides a list of internal and external programs, giving users the option to authorize access or change settings for each one individually as shown in Figure 4.
Figure 4: Battery Optimizer-Fetching
The program data is saved chronologically, displaying the history of cleaning, together with cache and RAM details. Although it was initially intended to transfer program components to the cloud, Android constraints have limited what can be saved there to just useful information. This includes information like the status of Bluetooth and torches, as well as wiping history, clearing space, and background applications that have been stopped.
Moreover, to help users keep track of their device's performance, the optimizer also provides graphical representations of battery status and temperature over the last 24 hours, 3 days, or 5 days. All of these details, such as cleaning history, cache removal, space freed up, and the status of background programs, are meticulously logged and connected to specific user accounts on Firebase as depicted in Figure 5.
Figure 5: Battery Optimizer-History and Graphical Representation
When employing a battery optimizer to enhance mobile performance, various key pieces of information are extracted. Firstly, the cleanup timestamps are logged to record the optimization process. Additionally, the battery level after each cleanup is depicted, presenting insights into the device's power status during this operation. The optimizer also reveals the amount of memory that has been liberated, indicating the efficiency of the cleanup in optimizing storage. It identifies background applications that were consuming battery resources, specifying the total number of terminated apps that impact on overall battery. Notably, features like Bluetooth or the torch are automatically turned off, contributing to a more comprehensive and effective optimization approach. This makes certain efficient battery management and provides users with valuable insights into their device's power consumption patterns.
Overall, our research implementation not only focuses on draining the battery for analysis but also delves deeper into real-world usage scenarios. Through interactive notifications and detailed graphical representations, our system ensures active user participation, ultimately leading to more effective battery optimization strategies tailored to individual user's needs and habits.
Illustrated in Figure 6 is a thorough overview of the hierarchical organization within the Battery Optimizer Backend, delineating the interconnections and structure among its various components. Throughout the development process in Android Studio, the Main Activity class of the battery optimizer assumes a pivotal role, with the ‘DataEstimator’ class estimating device and battery-related data through the mApp object. The ‘NetworkWatcher’ class manages server status, device registration, and data transmission to the Firebase server via the ‘CommunicationManager’ class. The ‘OnRefreshComplete’ method updates the UI after completing a task list refresh, and ‘loadComponents’ initialize necessary components and data for the activity, such as setting up the database, services, permissions, and event listeners.
Figure 6: Battery Optimizer-Backend Hierarchy
The ‘AppsFragment’ handles the power-intensive app "ServiVerse" along with managing tasks related to phone internal and external information, such as running processes, killing apps, and handling permissions for device resources using the ‘getMemory’ method. It includes a cleanup process triggered by a clean button click, which disables Wi-Fi and Bluetooth, kills apps, logs device information, and performs other operations like turning off the camera torch and refreshing app data. The ‘DeleteSessionsTask’ class executes the deletion of outdated battery sessions in the background, and the ‘HistoryFragment’ displays historical app data, allowing users to view additional information by clicking on items.
The ‘CommunicationManager’ class orchestrates the uploading of data samples to the firebase, managing communication flow and providing status updates to the UI. The ‘RegisterDeviceHandler’ class is responsible for device registration, making API calls using Retrofit, and gathering device-specific information for the registration payload, including model, manufacturer, OS version, and root status. Overall, these classes work together to ensure effective communication with Firebase, data estimation, and management of app-related tasks on the Android device.
Discussion:
This system's standout feature is its ability to offload power-intensive mobile tasks to Firebase, a cloud server. Firebase meticulously records and organizes information, tracking each user's phone cleaning activities. Figure 7 and Figure 8 visually represent the frequency of cleaning sessions, the amount of cache and RAM eliminated, and the storage space freed up. The process of storing the cache cleaning session in Firebase is executed in an encrypted format, ensuring heightened user security when data is stored in the cloud. This not only enhances energy efficiency but also extends battery life. The approach is sustainable, as it reduces user’s device strain, ensures secure data storage, and maintains user privacy. The cloud infrastructure incorporates a default safety mechanism to enhance security for its users. This implies that our optimizer, seamlessly integrated with the cloud, ensures security for users. Each user undergoes a distinct registration process within the optimizer, ensuring personalized and separate user profiles. Once each user has performed their respective cleansing operations, the data is safely offloaded to the cloud in an encrypted format, with each user's information stored separately.
The tracked user activity provides valuable insights for continuous optimization and the visual feedback fosters transparency. The integration with Firebase streamlines data management, ensuring immediate updates and accessibility. As the system promotes responsible and efficient resource utilization, it contributes to better performance. The steady monitoring of cleaning activities establishes a robust feedback loop for further developments. The system also includes a feature that automatically turns off the Torch and Bluetooth connections within the device, enhancing both security and energy efficiency. This comprehensive approach not only ensures user's devices are optimized for performance but also showcases valuable insights into user behavior and preferences, aiding in continuous improvement and customization of the optimization process.
This study holds significant implications across various domains. Firstly, it focuses on mobile device optimization, which aims to improve mobile device performance and battery life. The influence extends to user experience improvement, where graphical representations and insights into energy utilization allow users to make educated decisions regarding their device's performance. Furthermore, the study promotes energy efficiency by integrating cloud computing for power-intensive tasks. The usage of Firebase demonstrates a priority on data security and privacy, with default safety measures and individualized user profiles offering comprehensive data protection for users. Overall, this study proposes a comprehensive approach that seamlessly integrates cloud computing, data analytics, and user-friendly applications to overcome the limits of mobile devices while improving overall performance and battery life.
Figure 7: Firebase-Individual User Details
Figure 8: Firebase-Individual User Cleanup
Conclusion
This research has effectively applied an approach to increase battery power in mobile devices, which delivers a solution to continuous battery depletion amid improvements in mobile technology. Our innovation is intelligently spotting power-consuming components in a mobile phone and applying the code-offloading method to run the computation process on a cloud server. This approach is achieved by the convergence of mobile computing with cloud computing to ease the battery usage of the mobile itself. The proposed optimizer for mobile phone applications leads to considerable power savings, extending battery life, and improving processing capability. This tactic has proven crucial in solving the urgent problem of background processing and power depletion on mobile devices, giving consumers a battery performance that is more effective and lasts longer.
We reported on manual, small-scale feasibility research and highlighted several potential barriers to validate the implication of bandwidth and power consumption optimization in MC hybrid systems. Firebase operates in an event-driven manner, calling the thread that started its on-event handler whenever an event occurs. From the perspective of scalability, using Firebase or other similar systems as middleware might not be the best option. The callback from the Firebase handler will be stopped owing to an intrinsic feature of Android systems if the waiting thread is the main thread to retrieve the results from the cloud. The alternative is to utilize socket-based middleware, which operates in a suspend-migrate-receive-resume manner and generates appropriate responses based on the sent request attributes within a timeframe. It is essential to note that since the study is centered on Mobile Cloud Computing (MCC), the availability and reliability of network connections may have an impact on its efficacy. Users in places with inadequate network coverage may experience limitations in user experience and face challenges in accessing cloud resources. In upcoming phases, when implementing the suggested application, we might conduct a survey to gather feedback. This survey will be useful in incorporating recommendations for data format, storage, and maintenance from various users. Additional enhancements can be made by incorporating extra features like personalized power-saving configurations or widgets for real-time monitoring. In forthcoming research endeavors, Exploring and evaluating different optimization algorithms, including the integration of machine learning, can enhance the system's adaptability to user behavior. Additionally, analysis of energy consumption patterns, and evaluating the environmental impact in terms of green computing contribute to the broader applicability and sustainability of the proposed solution.
Author’s Contribution:
Dua Agha: Writing – original
draft, methodology,
experimentation,
visualization, literature
review, result reporting.
Veena Kumari: Writing
original draft, methodology, experimentation,
visualization, literature
review, and result reporting.
Areej Fatemah Meghji:
Methodology, writing –
editing and review,
validation, result reporting.
Acknowledgement: Nil
Conflict of Interest:The authors declare they
have no conflict of interest in
publishing this manuscript in
IJIST.
Project Details: This
research was not part of any
project.
Reference
[1] H. K. Shaikha and A. B. Sallow, “Mobile Cloud Computing: A Review,” Acad. J. Nawroz Univ., vol. 6, no. 3, pp. 129–134, Aug. 2017, doi: 10.25007/AJNU.V6N3A96.
[2] S. C. Toader, R. I. Ciobanu, and C. Dobre, “Smart Computation Offloading for Mobile Clouds,” 2023 IEEE Int. Conf. Pervasive Comput. Commun. Work. other Affil. Events, PerCom Work. 2023, pp. 62–67, 2023, doi: 10.1109/PERCOMWORKSHOPS56833.2023.10150282.
[3] C. Nigam, G. Sharma, and E. Menghani, “Comprehensive Review and Analysis on Mobile Cloud Computing and Users Offloading using Improved Optimization Approach for Edge Computing,” Int. J. Intell. Syst. Appl. Eng., vol. 10, no. 1s, pp. 234–242, Oct. 2022, Accessed: Feb. 06, 2024. [Online]. Available: https://ijisae.org/index.php/IJISAE/article/view/2286
[4] P. Eastham, A. Sharma, U. Syed, S. Vassilvitskii, and F. Yu, “Learning Battery Consumption of Mobile Devices,” 2016.
[5] M. Ali, J. M. Zain, M. F. Zolkipli, and G. Badshah, “Mobile cloud computing & mobile battery augmentation techniques: A survey,” 2014 IEEE Student Conf. Res. Dev. SCOReD 2014, Mar. 2014, doi: 10.1109/SCORED.2014.7072944.
[6] M. R. Nakhkash, T. N. Gia, I. Azimi, A. Anzanpour, A. M. Rahmani, and P. Liljeberg, “Analysis of performance and energy consumption of wearable devices and mobile gateways in IoT applications,” ACM Int. Conf. Proceeding Ser., vol. Part F148162, pp. 68–73, 2019, doi: 10.1145/3312614.3312632.
[7] “View of A Systematic Survey of Simulation Tools for Cloud and Mobile Cloud Computing Paradigm.” Accessed: Feb. 06, 2024. [Online]. Available: https://jisrc.szabist.edu.pk/ojs/index.php/jisrc/article/view/40/30
[8] V. P. Estamsetty, “Cloud Computing , Mobile Cloud Computing and its Comparative Study,” no. January, 2021, doi: 10.13140/RG.2.2.30812.41601.
[9] B. G. Chun, S. Ihm, P. Maniatis, M. Naik, and A. Patti, “CloneCloud: Elastic execution between mobile device and cloud,” EuroSys’11 - Proc. EuroSys 2011 Conf., pp. 301–314, 2011, doi: 10.1145/1966445.1966473.
[10] Y. Hmimz, M. El Ghmary, T. Chanyour, and M. O. Cherkaoui Malki, “Computation offloading to a mobile edge computing server with delay and energy constraints,” 2019 Int. Conf. Wirel. Technol. Embed. Intell. Syst. WITS 2019, Apr. 2019, doi: 10.1109/WITS.2019.8723733.
[11] S. Cao, X. Tao, Y. Hou, and Q. Cui, “An energy-optimal offloading algorithm of mobile computing based on HetNets,” 2015 Int. Conf. Connect. Veh. Expo, ICCVE 2015 - Proc., pp. 254–258, Apr. 2016, doi: 10.1109/ICCVE.2015.68.
[12] D. J. S. Raj, “Improved Response Time and Energy Management for Mobile Cloud Computing Using Computational Offloading,” J. ISMAC, vol. 2, no. 1, pp. 38–49, Mar. 2020, doi: 10.36548/JISMAC.2020.1.004.
[13] M. A. Elgendy, A. Shawish, and M. I. Moussa, “MCACC: New approach for augmenting the computing capabilities of mobile devices with Cloud Computing,” Proc. 2014 Sci. Inf. Conf. SAI 2014, pp. 79–86, Oct. 2014, doi: 10.1109/SAI.2014.6918175.
[14] Y. Sun, J. Wu, L. Chen, T. Liu, M. Yao, and W. Sun, “Latency optimization for mobile edge computing with dynamic energy harvesting,” Proc. - 2019 IEEE Intl Conf Parallel Distrib. Process. with Appl. Big Data Cloud Comput. Sustain. Comput. Commun. Soc. Comput. Networking, ISPA/BDCloud/SustainCom/SocialCom 2019, pp. 79–83, Dec. 2019, doi: 10.1109/ISPA-BDCLOUD-SUSTAINCOM-SOCIALCOM48970.2019.00022.
[15] Y. Miao, G. Wu, M. Li, A. Ghoneim, M. Al-Rakhami, and M. S. Hossain, “Intelligent task prediction and computation offloading based on mobile-edge cloud computing,” Futur. Gener. Comput. Syst., vol. 102, pp. 925–931, Jan. 2020, doi: 10.1016/J.FUTURE.2019.09.035.
[16] A. Ali et al., “An Efficient Dynamic-Decision Based Task Scheduler for Task Offloading Optimization and Energy Management in Mobile Cloud Computing,” Sensors 2021, Vol. 21, Page 4527, vol. 21, no. 13, p. 4527, Jul. 2021, doi: 10.3390/S21134527.
[17] A. Akbar and P. R. Lewis, “Towards the optimization of power and bandwidth consumption in mobile-cloud hybrid applications,” 2017 2nd Int. Conf. Fog Mob. Edge Comput. FMEC 2017, pp. 213–218, Jun. 2017, doi: 10.1109/FMEC.2017.7946433.
[18] N. Dange, K. Devadkar, and D. Kalbande, “Scheduling of task in collaborative environment using mobile cloud,” Proc. - Int. Conf. Glob. Trends Signal Process. Inf. Comput. Commun. ICGTSPICC 2016, pp. 579–583, Jun. 2017, doi: 10.1109/ICGTSPICC.2016.7955367.
[19] I. Kaur, S. Sharma, and M. Arora, “Research Paper on Enhanced Battery for Android Phones using the Power of Cloud through Data Synchronization,” 2014.
[20] A. Wajid, N. Nigar, S. Islam, and M. K. Shahzad, “A SURVEY ON MOBILE CLOUD COMPUTING PROBLEMS AND SOLUTIONS,” Pak. J. Sci., vol. 75, no. 1, pp. 71–77, Mar. 2023, doi: 10.57041/PJS.V75I1.824.
[21] B. Assistant Professor, “Mobile Cloud Computing: Implementation using Android and Firebase API,” Int. J. Creat. Res. Thoughts, vol. 6, no. 2, pp. 2320–2882, 2018, Accessed: Feb. 06, 2024. [Online]. Available: www.ijcrt.orgwww.ijcrt.org
[22] A. B. Semma, M. Ali, M. Saerozi, Mansur, and Kusrini, “Cloud computing: google firebase firestore optimization analysis,” Indones. J. Electr. Eng. Comput. Sci., vol. 29, no. 3, pp. 1719–1728, Mar. 2023, doi: 10.11591/IJEECS.V29.I3.PP1719-1728.