Android Developer Builds Doze-Resistant Sound Manager Using AlarmManager and BroadcastReceiver

·4 views

A developer on DEV Community has detailed how they built an automated Android sound manager after a disruptive ringtone interrupted a client presentation. The system is designed to toggle ringer modes based on scheduled rules, such as prayer times or calendar meetings, without requiring manual input. The core architecture pairs AlarmManager's setExactAndAllowWhileIdle method to wake the device from Doze mode with a BroadcastReceiver that executes the actual AudioManager state changes. Decoupling scheduling from execution ensures the system remains stable across different Android manufacturers and their aggressive power-management implementations. A key challenge encountered was the volatility of Do Not Disturb API permissions, which some manufacturers reset after major system updates.

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)

Xiaomi Enters NAS Market with 4-Bay Smart Storage Device Priced at 2,699 RMB

Xiaomi launched its first network-attached storage device, the Xiaomi Smart Storage, listing it for reservation on August 21 at a starting price of 2,699 RMB. The 4-bay desktop NAS features an Intel N100 processor, 6GB RAM, dual 2.5G Ethernet ports, and supports up to 24TB per bay, along with Docker and phone photo backup functionality. Its specs place it in direct competition with established NAS makers like Synology and QNAP at a similar price point. The device features a matte white enclosure with an angled top grille for dust resistance and a magnetic snap-on front panel for tool-free drive access. Xiaomi's entry into the category is seen as a signal that NAS devices are shifting from niche geek hardware toward mainstream consumer electronics.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Context Packets: A Smarter Way to Feed Architecture to AI Coding Agents

Giving an AI coding agent access to an entire repository does not guarantee better understanding, as large codebases contain outdated code and undocumented decisions that dilute useful signals. A proposed solution called a 'context packet' is a small, versioned, machine-readable description of a system that captures contracts and architectural decisions source code alone does not reveal. Rather than relying on folder structure or full-repo access, a context packet is assembled from a dependency graph and scoped specifically to the change at hand. It covers key technical layers including intent, boundaries, contracts, constraints, and execution policies. Like source code, context packets should be versioned and reviewed, making context selection an auditable, improvable policy rather than an ad-hoc prompt.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why a Flawless Test Score Is Not Enough to Ship an AI Model

A developer building an LLM-powered order-reading system chose not to ship the model despite it achieving zero fatal errors on a 29-question evaluation. The core concern was that every test question was self-authored, meaning the exam only covered scenarios the developer could personally imagine, not the unpredictable inputs real customers produce. To make the system safely shippable, a human-handoff guard was built in so that unrecognized inputs are flagged rather than processed automatically. Post-launch, humans reviewed all outputs during an initial period, with real-world misses converted into new test cases to expand the exam beyond imagination. Notably, the evaluation caught five errors made by the developer himself — in the answer key and grader — versus just one model mistake, underscoring the exam's value as a tool for the builder, not just the AI.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How a 0.2% AI Hallucination Rate Caused 245 Retries in a 5-Day Loop

A team running around 100 unattended LLM agents discovered that one pipeline task had retried 245 times over five days before they caught it. The root cause was a conflict between two automated agents: a reviewer hallucinated formatting requirements that did not exist in the original document, and its fix instructions were mathematically incompatible with the producer's minimum output contract. Because no single response could satisfy both constraints simultaneously, the producer kept failing and retrying indefinitely. An audit of 2,038 stored reviews found a 0.2% hallucination rate, which was enough to trigger nearly 500 wasted processing cycles. The team has since patched the pipeline by passing the original request into review prompts, flagging impossible instructions before they enter the queue, and capping consecutive failures at five before routing the task to a human reviewer.

0 comments Read more at DEV Community