e-t-l

Ok, so it is a bug then.

Yes. To clarify, when I say, "If I tap it, it does X," the implied corollary is that—as with any other UI element—if I _don't_ tap it, then X does...

Some resources that might be a good starting place for this... Quick replies from smartwatches appear to involve `NotificationCompat.WearableExtender` API: https://developer.android.com/training/wearables/notifications An example of the API implemented in the AOSP...

Also, if the Google app (or Assistant, or Google Calendar, or if you're on GrapheneOS the Google Play/Services/Framework app, etc...) have been granted the Read/Write SMS permission (or even Notifications...

> I tried to build the /e/ fork, and I was eventually able to get it to build, but it didn't run Do we even know that the /e/ fork...

If you're still referring to the /e/ fork, they're a reputable group and I would trust them. But it don't think they're making active improvements to qksms, is what I'm...

Yeah that's the one. It was already linked in https://github.com/moezbhatti/qksms/issues/1885#issuecomment-1278097179 above so I didn't think to relink it

Yeah, you're free to read through the source code. There's nothing there that could possibly record your phone number and send it to any server. Lot sof apps can read...

According to #224 this should have been fixed in QKSMS v3.0, but it definitely occurs as of v3.9.4, so it might be a regression. @moezbhatti can we take a look...

> I could use it by editing dnscrypt-proxy.toml manually @awebeer256 Did you end up doing this? If so, what edits were required to get ODOH working?