Developer builds Android sound manager that works through Doze mode and geofencing

·7 views

A developer created an Android app called Muffle to automatically manage phone sound profiles based on location and time, after a personally embarrassing moment during a college lecture. Standard background services proved unreliable due to Android's Doze mode and App Standby battery optimizations, which kill background processes when the screen is off. The solution required combining a Foreground Service with AlarmManager's setExactAndAllowWhileIdle to force the OS to wake the app at precise trigger moments. Additional hurdles included handling Do Not Disturb permissions, which fail silently without explicit user authorization, and replacing battery-draining GPS polling with the GeofencingClient API. The project highlights how building reliable background services on Android demands working around aggressive OS-level power management rather than relying on standard execution methods.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Developer builds open-source widget to show how much heat a PC pumps into a room

A developer created HeatLens, a free desktop widget, after finding no existing tool that translated PC power draw into room heat metrics. The app converts live wattage readings into BTU per hour, session heat totals, and rough exhaust airflow estimates, using the simple formula BTU/hr ≈ watts × 3.412. It pulls sensor data from LibreHardwareMonitor, nvidia-smi, and Linux RAPL, with labeled fallbacks when direct power sensors are unavailable. Built with Python and Tkinter, HeatLens is available as a portable executable for Windows and Linux under an MIT license on GitHub. The developer notes it is not a substitute for a plug-in wall meter and advises treating its readings as contextual estimates rather than precise measurements.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Builds Retro-Style Personal Website as Tribute to Cat Juma

A developer created a personal tribute website dedicated to their cat, Juma, as part of DEV Community's Weekend Challenge: Passion Edition. The project aimed to recreate the nostalgic aesthetic of the early internet era. It was built using foundational web technologies — HTML, CSS, and JavaScript — to achieve its retro look and feel. CSS was used for animations, gradients, and responsive design, while JavaScript powered interactive effects like falling stars. The developer shared the source code publicly on GitHub but opted out of prize category submissions.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How React List Virtualization Kept a Live Chat Feed Stable at 3,700+ Messages

A frontend developer built LiveShop, a simulated live-shopping stream UI, to study how chat feeds behave under high message volume — a scenario rarely covered in tutorials. Testing revealed that a standard React list render accumulated over 3,300 DOM nodes at 3,700 messages, causing frame rates to drop to 25fps with visible stutter during simulated spikes. Switching to react-window, a list virtualization library, reduced the active DOM node count to just 14 at any time by rendering only the rows visible in the scroll viewport. After the change, the same stress test maintained a steady 60fps regardless of total message count. Additional optimizations, such as capping concurrent reaction animations at eight, further stabilized performance under rapid, unpredictable input bursts.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Kubernetes ingress-nginx retired: what teams must do before the next CVE hits

The Kubernetes SIG Network officially stopped maintaining ingress-nginx as of March 2026, leaving clusters that still run it exposed to unpatched security vulnerabilities and without future feature updates. A CNCF blog post published on July 9 outlines two migration paths: a lateral swap to another Ingress-compatible controller such as Contour, or a fuller move to the Gateway API, the upstream-designated successor to the Ingress spec. The post recommends using the ingress2gateway tool to automate translation and suggests running the new controller in parallel before gradually shifting non-critical workloads. Engineers are cautioned that ingress annotations — covering timeouts, rewrites, TLS settings, and affinity rules — do not translate cleanly between controllers, and mismatches can cause silent traffic regressions on the most critical paths. The risk is not immediate but is tied to the calendar, as the threat grows each time a new CVE emerges against a controller that will no longer receive upstream fixes.

0 comments Read more at DEV Community