Urgent.News

What's breaking now, across thousands of outlets.

AI

I Tried to Build a Bengali Voice Dialer for Android. Here Is What Actually Happened and How I Finally got it right.

A personal project to make phone calls easier for an elderly, non English-speaking parent that works entirely offline, and the long road through Whisper models, sherpa-onnx, frame-size crashes, and Android's scoped storage pitfalls before it finally worked with zipformer. 12 min read · Android · AI models · Bengali · ASR · On-device AI I wanted to build a simple tool for my elderly,…

A personal project aimed at creating a voice dialer app for an elderly, non-English-speaking mother led to a long and challenging journey through various Whisper models, Android's scoped storage limitations, and the quest for on-device AI solutions. After testing different Whisper models on a MacBook, the turbo variant of the large-v3 model proved to be the most successful on Mac, producing clean output in either Bengali script or Devanagari.

However, porting the model to Android presented significant challenges due to the latency introduced by the encoder pass, which took 60-80 seconds for a three-second voice clip. Attempts to optimize the encoder by reducing the window size and using the OpenCL GPU backend were unsuccessful. The author then switched to using sherpa-onnx, a production ASR framework, which provided a significant speedup, reducing the transcription time to about 2 seconds.

Despite this improvement, the app still faced issues with language detection, as Whisper's internal language classifier randomly misidentified Bengali utterances as Hindi, English, or Spanish. By writing a custom mapper to normalize the output and extending the intent parser, the app was eventually able to transcribe Bengali speech accurately.

The final breakthrough came when the author discovered a Bengali-specific model published in the sherpa-onnx release assets, which drastically improved the accuracy and performance of the voice dialer app.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in AI

Building an evidence-first multi-agent system: 720 paired missions, rollback, and strict claim boundaries

I am an independent R&D developer building SSI V5 , an experimental multi-agent architecture focused on evidence, provenance, consolidation, and rollback. The implementation itself is proprietary.

  • SSI V5 multi-agent system focuses on evidence, provenance, consolidation, and rollback capabilities
  • Six agents (ISKRA1-ISKRA6) used in experiments with 720 paired missions
  • System passes training sequence (S1-S10) and completes drone, humanoid tasks with 100% success

Your Agent's Memory Is an Attack Surface

In Post 3, the behavioral difference tracked the memory graph, not the substrate. When I swapped one individual's learned associations into an identical brain, the subject did not just get confused.

  • Agent's memory can be compromised, turning it into an attack surface.
  • Memory graph, not substrate, shapes agent's behavior based on bias current.
  • Proposed solution: provenance of experience to differentiate earned from authored memory.

More from Sunday 20 September →