DeX

AppWizard
October 1, 2026
Android manufacturers curate devices, often leading to frustration for users who struggle to find specific settings due to the absence of desired features. The open-source community offers tools to enhance device functionality. MT Manager allows deep app modification directly on devices, providing access to app decompiling and editing without needing a desktop. It requires root permissions for its most powerful features and is not available on Google Play. Install with Options enables users to bypass installation restrictions on Android 7.0 and later, allowing the installation of apps outside the Google Play Store by using shell-level privileges or root access. Canta Debloater helps users safely remove carrier bloatware without root access on devices running Android 9.0 and above, using color-coded safety guidance to assist in the uninstallation process. ColorBlendr offers precise control over Material You color palettes on Android 12 and newer, allowing users to customize colors and themes with a live preview function. It requires elevated access via Root, Shizuku, or Wireless ADB. Kvaesitso Launcher replaces the default home screen with a search-centric interface, streamlining app navigation through a unified search bar that handles queries for apps, contacts, files, and calendar events. It is available on GitHub, F-Droid, and IzzyOnDroid.
BetaBeacon
September 28, 2026
Main features of version 3.0 include managing Pokémon by editing various aspects, legalizing Pokémon offline, moving Pokémon between games, storing collections in a Bank, tracking the Pokédex, browsing and injecting events, editing the bag and trainer, using RNG tools, batch editing, breeding and hatching Pokémon, completing the Pokédex, playing with Pokémon in the Poképark, sharing teams, using game-specific editors, keeping saves safe, and supporting dual-screen devices. The software supports various generations of Pokémon games and emulators.
AppWizard
September 23, 2026
The Android development community has historically addressed memory optimization reactively, but new performance requirements from Google Play, effective February 2027, emphasize proactive memory management. These requirements include metrics for dynamic memory usage, bitmap memory, and DEX code optimization, with apps needing at least 25% optimization coverage. Memory usage can now hinder releases even without local crash replication, necessitating its integration into the pre-production process alongside other performance metrics. Dynamic memory usage is defined as anonymous RSS plus swap, excluding file-backed data. Google Play will evaluate this across different application states and device performance categories. Bitmap memory is scrutinized for the retention of invisible bitmaps, and DEX optimization aims to reduce memory footprint and improve performance. Investigating memory growth involves using Android Studio’s Memory Profiler to monitor memory changes during specific user flows and conducting heap dumps to identify retained objects. Issues often arise from retained state, where components hold onto callbacks that reference image data, necessitating a focus on lifecycle management rather than merely cache size. Bitmap memory should be carefully managed, as the decoded size can significantly exceed the compressed file size. Downsampling images to match UI dimensions is crucial. Memory checks should occur before production, with a focus on establishing a memory budget based on actual measurements and defining representative memory scenarios for testing. A pre-release memory checklist includes running user flows repeatedly, testing on various devices, inspecting heap dumps, examining image configurations, and reviewing optimization metrics. Monitoring Android vitals and Play Console warnings is essential to detect potential issues before they lead to user-reported crashes.
AppWizard
September 21, 2026
In August 2026, Google Play announced new performance requirements for memory management that will be enforced starting February 2027. These requirements include metrics for dynamic memory usage, bitmap memory, and DEX code optimization. Applications that exceed these thresholds may face reduced visibility and publishing capabilities on the platform. Dynamic memory usage is defined as the sum of anonymous RSS and swap, excluding file-backed data. Google is focused on whether applications retain non-visible bitmaps and requires at least 25% coverage in DEX optimization. Memory issues can be difficult to reproduce, and developers are encouraged to use Android Studio’s Memory Profiler to investigate memory growth. A thorough investigation involves monitoring memory changes, taking heap dumps, and understanding reference paths. Bitmap memory should be carefully managed, as the runtime cost of images can exceed their file size. Google will provide real-world memory metrics through the Play Console, and teams are advised to establish memory budgets and perform pre-release checks to identify potential issues before they lead to out-of-memory (OOM) crashes.
AppWizard
September 18, 2026
Cybersecurity experts have identified a new Android malware named RatHat, believed to be operated by Chinese threat actors. RatHat is distributed primarily through smishing and malvertising campaigns, leading users to deceptive download portals. It employs an automated multi-stage infection process and exploits Accessibility features along with a local ADB self-pairing mechanism to escape the Android application sandbox. The malware uses various anti-analysis techniques, including container tampering, manifest bombs, DEX bytecode poisoning, and dual string-encryption. RatHat's architecture consists of a malicious Android application, a Go agent, and an FRP reverse-proxy client, which together enable it to gain critical system permissions and perform various malicious activities such as credential capturing, screen recording, and SMS interception. Even if uninstalled, the malware retains shell access to the device, allowing attackers to reinstall it. RatHat can serialize the device's Accessibility tree to XML and communicate with a Generative AI assistant for tasks like screen coordinate determination and text extraction. The Go Agent, masquerading as a native library, exploits shell access to execute commands and establish a persistent connection to a command-and-control server via the FRP client. The C2 server can issue extensive commands to collect sensitive information, including SMS messages, credentials, files, and keystrokes, and RatHat also features a hardware-level keylogger.
AppWizard
August 31, 2026
Google will implement new memory usage regulations for Android applications starting in February 2027, due to a global RAM shortage. Apps exceeding the set memory limits may be throttled, terminated, or face reduced visibility on the Play Store. The memory thresholds vary based on device specifications, with specific limits for foreground, background, and bitmap memory usage. Non-compliance will result in penalties affecting app distribution and visibility. The memory crisis is attributed to increased demand from the AI data center industry, leading to rising RAM costs. The new limits will first apply to Pixel devices with Android 17, and other manufacturers are expected to follow. Additionally, by April 2027, all apps on the Play Store must support zero-tap credential restoration for users transitioning to new devices.
AppWizard
August 27, 2026
Starting in early 2027, Android apps on Google Play must meet new memory performance standards due to rising RAM prices and consumer demand for streamlined smartphones. Google is concerned about a potential "ecosystem-wide memory crisis" and aims to improve memory efficiency in app development. The new standards will be implemented in two phases: the first phase in February 2027 will set thresholds for undesirable behavior and code optimization, while the second phase in April 2027 will enhance device migration with a zero-tap credential restoration feature. Specific memory limits include: - For devices with 8 GB of RAM: foreground app usage capped at 2.25 GB, 1.5 GB for user-perceived services, and 1.5 GB for background processes. - Devices with more than 16 GB of RAM will be largely exempt from these restrictions. - Bitmap memory usage limited to 200 MB for user-perceived and background services, with a cached limit of 400 MB across all devices. - Gaming applications will have different memory requirements. The DEX code optimization mandate aims to improve memory utilization, app launch speed, and runtime performance. The zero-tap sign-in requirement in the second phase seeks to streamline device migration and enhance security, addressing risks associated with manual sign-ins.
Search