leak

AppWizard
September 25, 2026
Google is rolling out Android 17 QPR2 Beta 6 to Pixel testers to fix various issues, including crashes and unexpected reboots. The update addresses a reboot issue with the Pixel 9 Pro Fold related to third-party apps when opening the camera viewfinder. It follows the release of QPR2 Beta 5 and achieves Platform Stability, with all devices aligned on build numbers. Notable fixes include resolving a system kernel crash during simultaneous access to the camera and microphone, a visual regression affecting content display, a blank screensaver issue while charging, problems with dismissing locked applications, and device crashes during scrolling. Google has also temporarily removed blurred notifications on the lock screen to address certain bugs.
Winsage
September 24, 2026
Security researchers from Graz University of Technology in Austria have discovered significant vulnerabilities in the file notification systems of major operating systems: Android, Linux, macOS, and Windows. These flaws have existed for decades and can lead to the leakage of sensitive system information. The affected systems include inotify on Linux (since 2005), FileObserver on Android (since 2008), ReadDirectoryChangesW on Windows (since 2000), and FSEvents on macOS (since 2007). The vulnerabilities allow unprivileged users to monitor file events without explicit read permissions, enabling potential attacks such as inter-keystroke timing attacks and website fingerprinting. For example, on Linux, monitoring a readable directory can leak events on files that cannot be read, allowing attackers to achieve a 93.1% to 100% accuracy rate in monitoring keystrokes. Specific vulnerabilities include CVE-2025-68788 on Linux, which received a partial fix in December 2025, and issues on Android where FileObserver can bypass app storage isolation. On macOS, limited information is available due to a lack of bypasses for private directories, while on Windows, monitoring the root directory can reveal the full path of every accessed file, allowing real-time tracking of web activity with a 97.8% accuracy rate. Microsoft has described the issue as "by-design," which has faced criticism. The researchers propose stronger mitigations, such as disallowing monitoring of entire drives on Windows and introducing a permission system for file monitoring on Windows and macOS. Their findings will be presented at the ACM CCS 2026 conference in November in The Hague, Netherlands.
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 23, 2026
Images of Tesla's next-generation Optimus robot, Gen 3, were leaked from the Tesla Android app APK by researcher @wholemars, showcasing design assets of both Gen 2.5 and Gen 3. The leak reveals significant design evolution, suggesting enhancements in aesthetics and functionality. Preliminary observations indicate that Gen 3 may feature advanced sensors and improved mobility, along with a more intuitive user interface. This model could position Tesla as a leader in the humanoid robot market and enable diverse applications, from personal assistance to industrial automation.
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.
Winsage
September 19, 2026
Windows XP was released in two versions: Retail for individual consumers and Volume for Microsoft's partners and OEMs. The product key FCKGW-RHQQ2-YXRKT-8TG6W-2B7Q8 became widely recognized due to a potential leak by an insider at a major OEM, which was then spread by the pirate group Devils0wn. The Volume version's activation system required a unique key, but the FCKGW key was incompatible with the standard installation CD. To verify the legitimacy of Volume discs, the activation system searched for a secret 10MB binary blob exclusive to the Volume media. Microsoft blacklisted the FCKGW key with Service Pack 1 and implemented further security measures with Service Pack 2, restricting access to certain updates. Contrary to prior beliefs, the key's functionality was not due to a simple key generation algorithm but was designed by skilled engineers.
Winsage
September 17, 2026
The most recognized Windows XP product key is FCKGW-RHQQ2-YXRKT-8TG6W-2B7Q8. Windows XP was released in two formats: Retail for consumers and Volume for Microsoft partners and OEMs. The Volume discs were not intended for the general public and were designed for mass installations without individual activation. The final CD version, Release to Manufacturing (RTM), was completed on August 24, 2001, two months before the official launch on October 25. A leak of the Volume image and its Volume License Key (VLK) is believed to have originated from a major OEM, possibly Dell or Intel, which was exploited by the pirate group Devils0wn, allowing broader access to Windows XP.
Search