ATLASX NET

✅💡 ATLASX Apps This folder contains all the applications from the ATLASX project, each developed with a specific purpose to provide different forms of Android optimization. Instead of an all-in-one application, each project is designed to address a distinct need, allowing users to choose the most suitable solution for their specific use case. Inside this folder, you will find detailed descriptions of each app, including its function, core features, how it interacts with the system, and the story behind its development. Some projects were built from scratch, while others were born from old, abandoned APKs that have been rebuilt, fixed, and enhanced to offer a more modern, efficient, and stable experience. The goal of the ATLASX project is to provide tools that bring genuine improvements to Android performance, stability, and efficiency. We are committed to transparency regarding how each app works, strictly avoiding unfounded or empty promises. This folder will be continuously updated as new applications are launched or when existing projects receive new features, bug fixes, and overall improvements.

⚠️💡 UPDATE — ATLASX AETHER v8.1 Legacy ADB ATLASX AETHER has been completely rebuilt on a unified ADB architecture, following the same standard as the ATLASX ARC, ATLASX TOUCH, and ATLASX GOOGLE modules. This version is focused on older devices, low RAM capacity, and real-world daily use prioritizing stability, fluidity, and reducing system load. 🛠️ What has been fixed The older AETHER had a more fragmented and heavy logic, which affected performance on weaker devices. In this version, the system has been simplified and reorganized: • Reduced load on heavy apps and services. • Improved overall fluidity on older hardware. • More efficient control of RAM, cache, sync, and network scans. • Optimization of the Play Store, WebView, network, and system startup. • Fully reversible system via the restore command. • Centralized and lighter structure. 🏗️ New Structure • The module now operates on a unified architecture: • Single execution via aether.sh. • Central core located in lib/common.sh. • Saves state only for what is strictly necessary for restoration. • Automatic profiles based on RAM capacity and Android version. • Smart compile system with caching per package version. • Division by real memory tiers. 📥 Installation Extract the package. Copy the ScriptAETHER folder to your internal storage. Confirm the path: /sdcard/ScriptAETHER Mandatory structure: /sdcard/ScriptAETHER/aether.sh /sdcard/ScriptAETHER/functions/ /sdcard/ScriptAETHER/lib/ /sdcard/ScriptAETHER/config/ 💻 Main Command sh /sdcard/ScriptAETHER/aether.sh ⚙️ Core Commands sh /sdcard/ScriptAETHER/aether.sh status sh /sdcard/ScriptAETHER/aether.sh doctor sh /sdcard/ScriptAETHER/aether.sh restore 🤖 Automatic Profiles AETHER automatically selects the most appropriate profile according to your device: • ultra: For very old or extremely limited devices. • battery: Focuses on power saving and reducing system load. • balanced: A balance between performance and daily usage. 📝 Important Note Without root access, Android limits deep adjustments to the kernel, scheduler, and drivers. Because of this, AETHER operates solely via ADB shell, settings, appops, standby buckets, cache management, and smart compiling. This maintains full compatibility with older devices without compromising system stability.

ATLASX TOUCH has been completely rebuilt to operate in the style of ARC, featuring a cleaner structure, centralized execution, and a direct focus on touch response and fluidity. This version reduces dependencies on scattered scripts and concentrates all logic into a single command, with automatic profiles tailored to the device's hardware. 🛠️ What has been improved This version has been tweaked to make ATLASX TOUCH lighter, more direct, and more consistent: • Automatic detection of the device's maximum refresh rate. • Target set to 120Hz or 90Hz when supported. • Avoids unnecessary settings (like 144Hz) when they are not part of the profile. • Reduction of rewrites in settings to decrease overhead. • Backups only what genuinely needs to be restored. • Clears local state after execution and restoration. • Complete centralization of the flow within atlasx.sh. ⚙️ How TOUCH works now • Single execution via atlasx.sh. • Automatic device analysis before applying tweaks. • Automatic selection of the most compatible profile. • Real-time application of touch response optimizations. • Automatic target refresh rate definition (120Hz or 90Hz). • Final display of the detected profile and applied state. • Fully compatible restoration without script fragmentation. 🚀 Integrated Touch Boost When running atlasx.sh, the system automatically: • Detects the ROM, manufacturer, and system behavior. • Chooses the most suitable touch profile. • Adjusts the target refresh rate to 120Hz or 90Hz when available. • Improves input parameters such as: • pointer_speed • Touch response (tap latency) • Gesture precision • Multi-touch handling • Reduces perceived visual latency. • Applies safe fluidity tweaks. • Removes minor interferences that affect input (overlays and inconsistent states).

✅🔗 UPDATE — ATLASX GOOGLE v7.1 Stateless ATLASX GOOGLE has been completely rebuilt to offer a simpler, smarter, and more efficient experience when managing Google services. Following the new architecture of the ATLASX ARC, ATLASX TOUCH, and ATLASX AETHER modules, this version centralizes all functions into a single command and applies optimizations that automatically adapt to each device's hardware. 🛠️ What has changed • New Stateless mode architecture, reducing local writes and eliminating the dependency on fragmented scripts. • Reorganized structure to a central core via google.sh, making the module lighter, cleaner, and more compatible. • Automatic profiles based on RAM capacity, Android version, and device manufacturer. • Smart backup and restore system, saving only essential data for rollbacks. • Optimized compile pass system, recompiling only the Google packages that have actually been modified. • Greater compatibility with entry-level and mid-range devices, as well as older Android versions. • Direct optimization of the Google ecosystem (GMS, GSF, Play Store, Sync, FCM, and location services). ⚙️ Functional Improvements Now, the entire module runs through google.sh, allowing the system itself to analyze the device before applying any optimizations. During execution, ATLASX GOOGLE automatically identifies the amount of RAM, Android version, manufacturer, and system behavior to select the most appropriate profile. Additionally, it performs deep optimizations within the Google ecosystem, including: • Google Play Services memory management • Account synchronization control • Play Store and update services optimization • Reduction of telemetry and background activities • Location and network scanning adjustments • Cache and standby bucket optimization • FCM notification stabilization • Maintenance of essential Google services without breaking functionality At the end of the execution, a summary is displayed showing the detected profile and all applied optimizations. 🚀 How to use Inside ATLASX GOOGLE, there is a README.md file containing all the installation and usage instructions for the module. After reading the README, copy the command below and run it in the AXManager terminal: sh /sdcard/ScriptGOOGLE/google.sh It is also possible to use additional commands directly through google.sh, such as: • System status • Complete diagnostics • Service restoration • Manual profile application • Advanced control for sync, location, RAM, and Play Store Furthermore, the module's 25 commands can be used directly in the AXManager terminal for fine-grained control of the Google ecosystem, allowing for manual adjustments or specific performance tests. 🎯 The Result ATLASX GOOGLE v7.1 Stateless offers a more organized, lightweight, and automated structure, allowing the module itself to identify the device, choose the most suitable profile, and apply optimizations intelligently. The focus of this version is to provide greater efficiency in the use of Google services, reducing battery consumption, RAM usage, and unnecessary background activities, always within the limitations of ADB mode and maintaining compatibility across different manufacturers and Android versions.