Developer Builds Battery-Efficient Android Geofencing Engine to Auto-Manage Phone Profiles

·1 views

A developer has detailed the architecture of a low-power geofencing system for Android that automatically switches phone sound profiles based on physical location. The project was motivated by the common problem of forgetting to silence a phone in places like mosques, offices, or medical clinics. Instead of battery-draining GPS polling, the solution uses Google Play Services' GeofencingClient, which relies on a combination of Wi-Fi, cell tower, and GPS data managed at the OS level. A PendingIntent tied to a BroadcastReceiver ensures the geofence triggers remain active even if the app process is killed by the system. The developer also flagged unexpected complications with Android's Doze mode affecting GPS precision during background operation.

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)

AI Agents Need Action Receipts, Not Just Memory, to Prevent Duplicate Actions

AI agents can retain extensive conversation history and still repeat actions like sending duplicate emails or publications due to ambiguous network failures. The core issue is not a memory problem but an 'action-receipt' problem, where agents cannot distinguish between a request that was never received and one that succeeded without a response. A proposed solution involves writing a durable receipt before any external request is submitted, tracking operation states such as 'submitted', 'succeeded', 'rejected', and 'outcome_unknown'. When a transport failure occurs, the state is marked 'outcome_unknown' rather than defaulting to a retry, preventing duplicate actions. Reconciliation is then handled by querying the external system to verify whether the intended effect occurred before any further action is taken.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Qdrant's Async Indexing Causes Silent Recall Failures in AI Agent Memory

A developer investigating an AI agent memory failure discovered that Qdrant's vector database does not wait for index refresh after an upsert by default, causing queries immediately following writes to return empty or partial results. The recall rate had dropped from 98% to 60% in production, with the inconsistency being difficult to reproduce since local tests often passed while CI builds intermittently failed. After 300 automated test runs using pytest with Qdrant's in-memory mode, the asynchronous gap between write operations and index availability was confirmed as the root cause. A common workaround of inserting a time.sleep() delay was dismissed as unreliable engineering practice, since the required wait time is unpredictable. The developer built an isolated pytest-based test suite covering single-point recall, batch writes, and payload-filtered queries to reliably expose and address the underlying indexing behavior.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why a Boring Three-Part Payment System Outperformed Everything on Black Friday

A payment service built with just one queue, one database, and one service ran unchanged for four years while engineers repeatedly questioned its simplicity. When Black Friday traffic overwhelmed the recommendation engine, search, and mobile app, the payment service processed every order without a single duplicate charge. The system's reliability stemmed from deliberate restraint — each component had a clear, singular role and no unnecessary layers were added. Stripe's idempotency key follows the same philosophy, using one authoritative record to prevent duplicate billing instead of introducing extra services. The article argues that in system design, knowing when three components are enough is a harder and more valuable skill than stacking more parts together.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

7 Local LLMs Benchmarked on NVIDIA DGX Spark: Bigger Models Don't Always Win

A Microsoft MVP based in Japan tested seven major local large language models by running the exact same Japanese business question through each one on a single NVIDIA DGX Spark machine. The benchmark evaluated not just generation speed in tokens per second, but also format compliance, factual reliability, and appropriate caveats for real business use. Results showed no clear correlation between model size and output quality — one fast model produced answers too risky for customer-facing use, while a 120B-parameter model returned a completely empty response field. NVIDIA's Nemotron 3 Super 120B-A12B, requiring 87GB of weights, was directly compared against smaller models in the 23GB class to assess whether its size justified its resource cost. All tests were conducted under identical fixed conditions — temperature zero, the same seed, and a capped generation budget — to isolate model differences from configuration variables.

0 comments Read more at DEV Community