One thing massive simply occurred. Because the Open Dwelling Basis’s Android developer for Dwelling Assistant, I used to be invited by the European Fee (EC) to seek the advice of on Android interoperability. The decision for suggestions was a part of the Fee’s work underneath the Digital Markets Act (DMA). For anybody unfamiliar, the DMA is an EU regulation that defines and regulates “gatekeeper platforms” – people who supply “core” companies like search engines like google and yahoo, app shops, and messaging platforms – to make digital markets fairer and extra open to competitors. As you may think, I had a lot to say about Google’s restrictions on Android, particularly the tech large limiting wake phrase detection to its personal Gemini assistant, a priority I surfaced in our Dwelling Assistant 2026.3 Launch Get together. To place it plainly, Google had no grounds for limiting Android interoperability within the first place, aside from to present itself the higher hand. We knew our neighborhood deserved higher, and that’s what we instructed the Fee.
The consequence? The EC listened to us and all the opposite organizations that contributed. On July 16, 2026, the European Fee adopted a choice underneath the DMA that requires Alphabet (Google’s mum or dad firm) to open up eleven Android options, together with always-on wake phrase detection, ambient sensor entry, and display screen automation – to all assistants, on equal phrases.
As an EU citizen, I’m genuinely happy to see this sort of regulation of Massive Tech leveling the digital market enjoying discipline and representing actual progress for customers. Not solely that, nevertheless it’s an actual win for the Open Dwelling Basis: we exist to combat for privateness, alternative, and sustainability in sensible properties, and this final result reveals what’s doable once we advocate for our neighborhood. We already briefly coated this information in our July e-newsletter, however I need to take a while now to interrupt down how we obtained right here, what this resolution says, why it issues for our neighborhood, and what it might unlock for Dwelling Assistant and the remainder of the trade.
A little bit of background
For 3 years, our neighborhood had tried to ship an always-on wake phrase detection within the Android Dwelling Assistant Companion app. We needed customers to have the ability to say “Okay Nabu,” and have their self-hosted Help voice assistant reply. But our early makes an attempt stored breaking. Most notably, after every reboot the system’s microphone not picked up the wake phrase. So we dug into the Android supply code, and lo and behold, there was an answer: however Google wasn’t letting us use it.
Android has a well-designed mechanism that lets your system pay attention for “Hey Google” all day, with out draining your battery. Their wake phrase detection runs in two levels. A small mannequin does the primary detection on a DSP (digital sign processor), which is a devoted chip that processes audio utilizing a fraction of the facility your system’s essential processor (CPU) would want. This primary stage runs in an remoted course of blocked from the community, and may’t extract audio till a possible wake phrase is detected. Then the second stage makes use of a stronger mannequin through the CPU to substantiate the detection.
Most modern gadgets have DSPs. However Android-based gadgets block entry to it for anybody aside from Google and the producer of the system. For the reason that wake phrase mechanism utilizing the DSP merely wasn’t out there to third-party apps, and developer documentation didn’t exist publicly, we used what we might to construct a workaround.
From microWakeWord to macro outcomes
Our answer was operating a small microWakeWord mannequin on the system’s CPU inside our app. This labored, however got here with some massive downsides:
- Battery utilization would bounce from roughly 1% to fifteen% with wake phrase detection enabled, for the reason that CPU is much much less environment friendly for this activity.
- The microphone privateness indicator (the inexperienced dot) would keep on completely, as a result of we wanted full microphone entry to run detection ourselves. We really suppose the indicator is the proper design – the issue is that we had no technique to supply the stronger assure Google offers itself: an remoted course of that may’t ship audio anyplace. As an alternative, you needed to belief that we had been dealing with that entry responsibly. And never as a result of a safer model isn’t technically out there. However as a result of the DSP path is arbitrarily blocked by Google for anticompetitive causes, forcing a much less safe method that introduces privateness dangers for the consumer.
- You would need to set Dwelling Assistant as your default assistant, as a result of that was the one manner Android would preserve our service alive throughout reboots. That will lock you out of Gemini and every little thing tied to it (and also you shouldn’t have to decide on).
Once I was invited to share these limitations (and others) with the Fee, I didn’t maintain again. Which is why we had been thrilled to find an impressively exact and technically correct resolution from the EU: it accurately describes the two-stage wake phrase structure, the DSP, the remoted course of, and the function coupling. The report went right down to particulars we solely discovered by studying Android’s supply code ourselves. Which brings us to what the ruling really says…
A wake-up name for Google
The choice requires Google to present third events interoperability that’s “equally efficient” as what Google’s personal assistant will get throughout eleven Android options, freed from cost. For wake phrase detection particularly, Google should present:
- The power to create a customized wake phrase mannequin in Android, with first-stage detection run by the DSP (when out there) as an alternative of the app
- The power to run a second-stage validation after the DSP has doubtlessly recognized the wake phrase in first-stage detection
- Testing instruments and full documentation, with out requiring a industrial settlement with Google
Two traces deserve a particular point out. First: Google “shall not topic entry to options to the app holding a default function, together with the default assistant function.” That’s the decoupling we mentioned with the Fee. Second: wake phrase detection “from a number of companies, together with companies belonging to 3rd events and Alphabet, are in a position to run concurrently.” This may allow you to say “Okay Nabu” to regulate your private home with out altering any defaults or having to surrender utilizing Gemini for different functions.
Past wake phrases, the choice covers invoking assistants from the long-press house gesture, entry to ambient knowledge just like the microphone and digital camera underneath the identical circumstances as Google, structured integration with apps (together with Gmail, Calendar, and Maps), system-level controls, entry to on-device AI fashions, and honest background execution guidelines. Opening up these options hasn’t been with out pushback – Google itself has raised safety considerations, which we’ll get into beneath. However with all issues thought-about, we consider the advantages to customers and the trade far outweigh the dangers.
Time’s ticking
Google should ship these adjustments in Android 18 (the following main launch), by August 1, 2027. Concurrent hotword detection – letting a number of companies be triggered by voice – should be in place by Android 19, no later than August 1, 2028.
It’s price noting the choice nonetheless depends on Google to design and implement the adjustments, and with that comes a threat of malicious compliance: a technically sound answer that’s unusable in actuality (it wouldn’t be the primary time a gatekeeper wrangled its manner out of a regulation). However the effective print offers grounds for hope: Google should ship options which can be “equally efficient” on ease of use, velocity, and vitality consumption, publish full documentation and testing instruments, and report progress to the Fee month-to-month. An actual win for builders, and one which makes transport the naked minimal a lot tougher to get away with. With that in thoughts, right here’s what it might seem like for Dwelling Assistant.
Assist us make this alteration stick
We’re at all times working arduous to create the very best expertise for our Android Dwelling Assistant customers, although we’re a small workforce – which is why neighborhood contributions to the Android app matter a lot. Should you’d like to assist (in keeping with our not too long ago launched AI coverage), we’d love to listen to from you. Whereas the concepts beneath are simply that, and don’t kind a part of our roadmap, your enter might assist unlock them sooner or later:
Battery-efficient wake phrase detection
Like we talked about earlier, transferring first-stage detection from the CPU to the DSP ought to enhance battery effectivity considerably. Our plan is to assist two strategies: on newer telephones with Android 18, we’ll use the cellphone’s low-power chip to pay attention for the wake phrase. On older telephones, or these with out that chip, detection will preserve operating because it does right now. Both manner, we’ll present you which ones technique your cellphone is utilizing from throughout the Companion app.
One cellphone, two assistants
Immediately, selecting a third-party wake phrase means giving up Gemini, together with calls and messages via your default assistant. Default-role decoupling and concurrent wake phrase entry would finish that: You possibly can speak to Gemini like aways, but in addition say “Okay Nabu” whenever you need to work together with your private home through Dwelling Assistant.
Think about in the event you might set totally different wake phrases for various assistants contained in the app itself, like “Hey Jarvis” in your admin dashboard and “Okay Nabu” for the household. This received’t even be technically doable till 2028 when Android 19 is launched (and it’ll take a whole lot of work), nevertheless it’s a pleasant objective to have trying forward.
Higher built-in privateness
That is the half I discover most enjoyable. The ruling requires wake phrase affirmation to run in a safe, remoted course of (often known as sandboxing) through the DSP. This implies the a part of the system that controls this function is walled off, with no technique to ship audio anyplace till the wake phrase is confirmed. I don’t need to depend on belief with regards to one thing as delicate as interactions with my voice assistant. I need to be in management, with a transparent rationalization of what the issues I allow really suggest. Sandboxing offers us that by design: privateness enforced by the OS itself, the identical secure-by-default safety Google has at all times had, now lastly out there to all.
A extra succesful assistant, for everybody
Sensor entry isn’t the one place this equal remedy applies. The choice additionally requires Google to open structured integrations with its personal apps – Gmail, Calendar, Maps, and so on – to certified assistants, not simply Gemini. In idea, meaning your assistant might draft an electronic mail, handle a calendar occasion, or ship a textual content and begin a name in your behalf: precisely the capabilities our customers inform us they miss once they go away Gemini, and ones that might genuinely increase usability, particularly for customers with accessibility wants.
That very same entry might broaden the vary of sensors and controls the app already studies to Dwelling Assistant: sound detection (smoke alarm, breaking glass, doorbell) as automation triggers, and controls like do-not-disturb or Bluetooth your assistant can really act on, not simply observe.
On the safety argument
Google has pushed again on the ruling, citing safety dangers. It warns the choice grants third events “delicate and highly effective system permissions,” exposing consumer knowledge “with out consumer information or consent.” This framing overstates the dangers in a well-recognized tactic: sounding the alarm on safety considerations to curtail makes an attempt for interoperability. We’d level out, as a type of third events, that the choice already builds within the safeguards that concern requires: Google can nonetheless require consumer consent, present privateness indicators, and let customers revoke entry per service. For probably the most delicate options like well being knowledge entry, it additionally has a coverage in place through the Play Retailer to verify safety, privateness, and knowledge minimization earlier than any app will get entry.
And to be clear, these capabilities exist already in your cellphone, and Google’s personal companies already use them, with out ever asking your approval. The danger didn’t seem when the EU requested for that entry to be shared extra broadly – what modified is who will get to resolve who has it. No matter dangers stay, like these launched by utilizing any sensible system, ought to be taken severely – simply not as a veil for Google’s double-dealing.
Our view is that belief with out verification isn’t a safety mannequin, and limiting these safeguards to Google alone isn’t safety. Even main AI distributors have had safety incidents, Hugging Face/OpenAI amongst them. What does supply safety is giving customers alternative and transparency into safety processes, together with a safe technical structure: sandboxing, isolation, revocable permissions – enforced equally, which is what this resolution requires.
It’s price watching the place Google goes subsequent: from 2027, its developer verification program would require each Android developer to be centrally verified earlier than their apps may even be put in – a transfer contested by the Maintain Android Open marketing campaign, and one we’re additionally skeptical about. It’s a reminder that this combat isn’t over, and neither is our work.
There each step of the best way
Google should report its implementation plans to the Fee inside two months, and eligibility program phrases are due for public session by February 2027. We’ll be there for all of it: to check the betas, report on whether or not implementation lives as much as the promise, and preserve you knowledgeable. Within the meantime, we’ll proceed doing all we will to champion sensible house tech that’s personal, native, and managed by you, on your phrases.
