I'm building an app using Supabase Auth, and my email verification emails are landing in users' spam folders.

For those who've dealt with this, what worked for you? Would only configuring SPF, DKIM, and DMARC solve the issue?

Any practical advice from developers who've fixed this would be greatly appreciated!

I'm looking to modernize my Android CI/CD setup to make it as AI-friendly and low-maintenance as possible for our company's daily workflow with coding agents.

I’m considering Dagger.io, do any guys has actually run Android builds through Dagger and how does it feel, or is there a better tool I should look into instead?

I'm an Android dev (Kotlin + React Native) trying to get models genuinely running on the Hexagon NPU of my iQOO Neo 10R (Snapdragon 8s Gen 3, SM8635, HTP V73, 4 MB VTCM), not on the CPU or GPU fallback.

What I've learned so far: - Qualcomm's ladder is FP16 → W16A16 → W8A16, with AIMET (AdaRound, SeqMSE, QAT) for accuracy recovery - The ORT QNN EP rejects dynamic shapes and Loop/If, and disable_cpu_ep_fallback=1 is a cheap check that everything stayed on the NPU - Most tutorials target V75 (8 Gen 3), and those binaries won't run on V73 - Apps need <uses-native-library android:name="libcdsprpc.so"> and extracted native libs (useLegacyPackaging) for the skel to load

Questions for anyone who has shipped this: 1. If you fine-tuned (LoRA or full) a small LLM or vision model, did you do QAT, or PTQ after fine-tuning? How much accuracy did W8A16 or W4A16 cost you? 2. What changes to the architecture did you have to make to stay fully on HTP (op swaps, static KV-cache layout, splitting the model into parts)? 3. Has anyone got a QNN context binary running from a normal third-party app on vivo/iQOO or Xiaomi firmware? Same-chip Poco F6 logs show llama.cpp's Hexagon backend failing with 0x80000406.

Happy to share my notes and code back. Thanks!

There is now a new way to run a Linux distribution on Android using UMLinux. UML is a program that executes an independent Linux kernel as if it were a standard user-space process within a Linux system. This allows for running a distribution that supports system init, Docker, and various other features that do not function in proot-distro. Notably, it operates without requiring root access or AVF, is faster than QEMU in TCG mode, and utilizes ptrace or seccomp. To provide internet connectivity within the distribution, additional programs such as slirp4netns, passt, or gvproxy

Hello, I’d like to introduce Acephale a simple, straightforward, old-school PDF viewer. It’s quite lightweight, built in Kotlin, and is open-source under the GPLv3 license.

I hope it works for you.

I'm guessing it's not the 20 days it takes our apps to get approved.

I'm sure there are laws against this sort of stuff, using your industry position to your own advantage...

I've about 2+ years of experience in Android dev and been doing DSA in c++ in college(current organization did not have any DSA rounds). I'm planning to switch in the coming months. So should I do relearn DSA in Kotlin or C++ would be fine?

Thanks.

Hi

I'm building an Android app and trying to implement an overlay that stays attached to a specific product page, but I'm struggling to get the behaviour right.

For example, imagine browsing a product on Amazon. I want the overlay to behave like this:

• On the product page: The overlay should appear and stay associated with that specific product page.
• When scrolling away: The overlay should disappear immediately when I leave the product page, rather than remaining fixed on the screen.
• When scrolling back: If I return to the product page, the overlay should appear again.
• Smooth transitions: There shouldn't be any delay or flickering when the overlay appears or disappears.
• i need help with flutter tvh

Currently, the overlay either stays fixed on the screen while I scroll through other pages or takes too long to disappear. do i need to learn about flutter ?

I'm looking for a solution that makes the overlay behave as if it's attached to the product page itself, rather than floating independently over the entire app.

Has anyone implemented something similar on Android using an accessibility service, a floating window, or another approach? I'd really appreciate any suggestions, technical guidance, or examples!

Thanks in advance!

My Vestel TV has 900 MB of RAM and the stock launcher was slow and full of ads, so I built OMNI: a launcher in plain Java (0.7 MB), a Control Center on INFO, a typed/voice assistant, device notices, and Kotlin apps (Cinema, Weather…). There's also a small Python server that turns a folder of films into a library with posters and resume. Free, Apache-2.0, no ads or tracking (the README lists every outside host). Tested on three TVs , so more reports from other TVs are very welcome. I verified it on real hardware. [RELEASE ON V.1 IS YET TO COME IN THE FOLLOWING HOURS]

Github(https://github.com/Rashica07/omni-tv)

Hi all,

As a hobby I'm building a personal voice assistant for my phone (Kotlin / Jetpack Compose), powered by the Claude API: calls, SMS, Gmail, calendar, Spotify & Sonos, Home Assistant (lights, alarm, TVs, energy usage…).

Code is public: github.com/NicoPi-dev/Assistant

Everything works well except the wake word, which bothers me.

**Current setup**

- A foreground service (microphone type) listening continuously with **Vosk**, offline, using a restricted grammar ("hey claude" + [unk]) and a confidence threshold.

- It works, but the mic is open 24/7: Android's green privacy dot stays on, it drains battery, and I'm not thrilled about it privacy-wise, even though everything stays local.

**What I'm after**

Something closer to "Hey Google" / Gemini: very low-power listening, ideally hardware (DSP) based, that only wakes the app on the hotword.

**Constraints**

- Free, no subscription or time-limited key

- Offline if possible

- No root (OnePlus 10T, OxygenOS 15 / Android 15, locked bootloader)

- Reliable: few false triggers (TV, conversations)

**Already looked at**

- **Picovoice Porcupine**: excellent, but the free tier is limited and needs an account key.

- **openWakeWord / microWakeWord**: promising, but unsure about battery impact running continuously on Android.

- **VoiceInteractionService / HotwordDetectionService**: the official DSP route, but it seems restricted to system/privileged apps (CAPTURE_AUDIO_HOTWORD).

- Setting my app as the **default assistant**: works for long-pressing the button, not for voice.

**Questions**

1. Can a third-party app set as default assistant access the hardware hotword on a non-rooted device? Has anyone pulled it off?

2. Otherwise, what's the most battery-friendly software approach you know: a tflite model like microWakeWord, VAD gating before Vosk, listening only when the screen is on or in the car…?

3. Tricks to limit listening automatically: while charging, when connected to Android Auto, at home on Wi-Fi…?

Any pointers or experience welcome. Thanks! 🙏

Hey Android devs,

Over the past few weeks, I’ve been working on an open-source framework and native runtime (Kotlin + C++17 NDK) designed to detect on-device hardware acceleration (Snapdragon NPU, Adreno GPU, Hexagon DSP, and ARM Cortex CPU) and route models to their optimal backend.

It features an embedded llama.cpp runtime for GGUF reasoning models alongside TensorFlow Lite (NNAPI/GPU delegates) and ONNX Runtime.

I wanted to share the benchmarks, lessons learned debugging the NDK/JNI bridge on real silicon, and how we solved common Android OS memory and storage constraints.

Real Silicon Benchmarks (Samsung Galaxy S22 - Snapdragon 8 Gen 1, Android 14)

Tested with Qwen3.5-2B Reasoning (Q4_K_M, ~1.2 GB):

Key Architectural Decisions & Android Gotchas

1. Zero JVM Heap Overhead (Preventing LMK Kills)

One of the biggest risks running LLMs on Android is the Low Memory Killer (LMK). We bypass the JVM heap entirely: models are memory-mapped via native mmap() syscalls directly from context.filesDir into C++ space. The JVM heap stays below 60 MB even during heavy generation loops.

2. ARMv8.4-a / ARMv9 Vector Flags in CMake

In CMakeLists.txt, passing -march=armv8.4-a+dotprod+i8mm -O3 enables Clang to generate vector instructions (SDOT/UDOT and SMMLA INT8 matrix multiply). This sustains 7.70 tokens/sec on 4 threads, handling 300+ token <think> reasoning chains smoothly.

3. Thread Affinity & Thermal Throttling

Octa-core Snapdragon SoCs typically feature a 1+3+4 topology (1 Prime Cortex-X2 + 3 Gold Cortex-A710 + 4 Silver Cortex-A510). Setting nThreads = 4 saturates the performance cores without starving Android's Main/UI thread or dumping heat into low-efficiency Silver cores. Generation stays thermally stable for 10+ continuous minutes.

4. Bypassing Android 11+ Scoped Storage via Embedded REST Server

Pushing 1GB+ GGUF files via adb push frequently hits permission or Knox SELinux issues. The app embeds a lightweight NanoHTTPD server on port 8080, enabling model uploads and inference directly over local Wi-Fi:

# Upload model directly into the app sandbox
curl -X POST http://<PHONE_IP>:8080/api/v1/models/upload \
  -F "file=@./models/Qwen3.5-2B.Q4_K_M.gguf" \
  -F "name=Qwen3.5-2B.Q4_K_M.gguf"

# Query the phone from any machine on LAN
curl -X POST http://<PHONE_IP>:8080/api/v1/llm/generate \
  -H "Content-Type: application/json" \
  -d '{
    "model": "Qwen3.5-2B.Q4_K_M.gguf",
    "prompt": "<|im_start|>user\nExplain Android memory management in 30 words.<|im_end|>\n<|im_start|>assistant\n",
    "max_tokens": 100
  }'

Source Code & GitHub

The project is 100% open-source under the MIT license:
GitHub: https://github.com/rafael-b-souza/ai-hardware-detector

Would love to hear thoughts, feedback, or PRs from other Android engineers working on NDK, on-device ML, and edge inference!

There is not a guarantee that a given USB-C-to-C cable supports PD, see the article USB-C was a missed opportunity and it’s too late to fix the mess.

Does Android have any API that lets an application check whether USB PD is currently active?

Posting this because I lost a stupid amount of time on it and I doubt I'm the only one.

App just closes on Android. No red screen, nothing in Metro, DevTools disconnects. I did what everyone does: rerun, clear cache, paste the code into AI a few times.

The reason was in logcat the whole time. Native code threw, the app died before JS could say anything, and the Android log had the exact line.

What worked for me:

- open the android folder in Android Studio and open Logcat (it picks up the app even if you started it with yarn run android)

- clear it, then reproduce the crash

- set the level to Error and search FATAL EXCEPTION

- read the exception message first, then the first line in the stack trace that isn't Handler / Looper / ActivityThread. Click it and it jumps to the code

One thing that got me: in the terminal, filtering by pid after a crash gives you nothing because the process is gone. adb logcat -d -s AndroidRuntime worked better.

Also the stack trace only told me where it died, not who passed the bad value. I needed a breakpoint for that part.

I made a small demo crash and recorded the whole thing for anyone who'd rather watch than read: https://youtu.be/oVYBmnOVaI8

What do you check first when Metro says nothing?

https://github.com/M5Devs/VPortable

For infos

Hi,

Our organization developer account (TosiMarketplace) was terminated under the Play Console Requirements and Developer Distribution Agreement Section 11.4. Our appeal was rejected, and support forms now redirect to ticket 6-7479000041612.

During registration we made two mistakes:

1. The organization name entered in Play Console did not exactly match the legal company name on our D-U-N-S profile.
2. The $25 registration fee was paid with the founder's personal credit card, because the company card had not yet been issued.

We suspect these mismatches caused the account information to be treated as inaccurate under Section 11.4, but we are not certain.

We have our corporate registration documents, matching government-issued IDs, and our D-U-N-S profile available.

Our questions:

1. Do these mismatches explain the termination, or should we look at something else?
2. Is there any way to request a human review to correct these details after an appeal has been rejected?

Thank you.

Couple of days ago I made a fresh Google account using Firefox developers browser and my phone number (which has another 2 associated Google accounts), after making the account I signed out, next day I signed in again went to developer section, meanwhile I was informed that I have to make a website that will describe the developer and provide the text of privacy policy and terms of service.

So I went directly to github and tried many times to sign up using Google and each time the OAuth took me again to the sign in page in github, so I decided to try from another device (same wifi) and another browser, this time everything went smooth and I opened my session on github and started my website, meanwhile google started the "verify it is you" scenario and started the robot tests and stuff, finally the send sms gave error of too many attempts try again after several hours!

I leaved it for 2 days to cool down, today when i tried and after making me send sms 2 times it showed a messages that the account was looking like it was created or used with multiple other accounts...etc and it will be considered for deletion after 1 year with an option to submit appeal!

Where did I go wrong and what should I do to avoid such a problem in the future? Need someone with developer background to help me.

I've been building NetPulse, a lightweight Android app for checking your network quality. It has a Material 3 interface with light and dark themes.

What works in v0.1.0-beta:

- Live ICMP ping monitor with Start / Stop

- Latency, min / average / max, jitter and packet loss over the last 300 samples

- Only two permissions (INTERNET and ACCESS_NETWORK_STATE), no ads, no analytics, nothing uploaded

What's coming next: a DNS benchmark (Cloudflare, Google, Quad9, Control D) measured separately from ping, latency charts, test history and CSV export.

The app uses the system ping tool, so some phones may block it. That's the main thing I want to find out: does it work on your device? Please tell me your phone brand and Android version, and any bugs or features you'd like to see.

Beta APK: https://github.com/Mireli5656/NetPulse/releases/tag/v0.1.0-beta

Source code: https://github.com/Mireli5656/NetPulse

The beta is signed with a debug key, so uninstall any earlier NetPulse build before installing it.

Thanks for trying it!

Wanted the iOS 26 liquid glass look in a Compose app, so I made a version and tuned the shaders side by side with a real iPhone. Putting it on GitHub in case anyone else needs it.

It works, but it’s an early version. If anyone wants to contribute to bringing liquid glass over fully, I’d be happy to have you. Issues and PRs welcome.

1988R@

Hi everyone,

I'm planning to transfer my app from one Google Play Console developer account to another.

For those who have already completed an app transfer, how long did it take for Google to approve and complete the transfer?

Did it take a few days, a week, or longer?

I'd appreciate it if you could share your experience. Thanks!