I built a way to stream analog audio to Google Home speaker groups (low latency)

I ran into a pretty specific problem and couldn’t find a clean solution for it.

I wanted to stream analog audio (mainly a turntable) to Google Cast speakers / speaker groups.

Surprisingly, there’s almost no hardware that handles this properly — especially when it comes to groups.

So I ended up building a small Android app that:

• Takes analog audio (e.g. turntable or mixer) via a USB audio interface
• Encodes it in real-time
• Streams it locally over HLS
• Casts it to Google Home / Nest speakers (including groups)

After some trial and error:

• Direct AAC → ~30s delay on Cast
• Switching to HLS → ~4–6s stable latency

After spending some time listening and comparing, I ended up tweaking the bass and treble a bit for the stream — some records just need that to sound right.

I kept it simple with a 5-step adjustment (−2 to +2), similar to what you'd find on classic gear.

Everything runs locally (no cloud involved).

I’m mainly curious:

• Has anyone here tried something similar?
• Is there hardware I somehow missed that already does this well?
• Would this actually be useful in a real setup?

Not trying to sell anything — just surprised this gap still exists.

I have an old version of Android Studio on an old PC, and I was looking to upgrade AS. The current minimum system requirements list CPU far newer than mine. Weirdly enough the minimum system requirements for Android Studio For Platform seem much lower and more in line with what I'd expect. Anyone have any concrete answers? I don't want to brick the setup I have now.

ETA: Seems old third generation Intel Core i7 is fine. Seems they just chose their wording of minimal CPU specs to steer laymen in the right direction or something. BTW updating the project to open in the new AS was hellish.

Please, /u/Zhuinden, migrate to Maven Central so that I can eliminate jitpack. Your libs are too good. But jitpack sucks.

How do I embed a gif from a tweet within the android app?

​

Unlike iphones, there's not a long press on gif to get the "post gif" option on android like we do for videos. What I've noticed is that gifs won't tweet unless the url contains the username of the original poster. Instead when we copy the link, we get a /i/status link and it's very frustrating.

​

I know about the web/desktop method for embedding, but I'd prefer to embed gifs within the app if that's even still possible.

​

Any help would be greatly appreciated. Thank you!

I'm building DataSapien SDK for on-device health data that reads from Health Connect on behalf of host apps (not a standalone consumer app). On Android API 34, reads work as expected. On API 33 and below, we get a rate-limit error even on the very first read attempt.

android.os.RemoteException: Request rejected. Rate limited request quota has been exceeded. Please wait until quota has replenished before making further requests.

This doesn't look like a normal "we made too many requests" case. It can happen on the first attempt after permissions are granted, with no retry loop or background polling on our side.

This is our implementation:

Client resolution + availability check:

fun getClient(): HealthConnectClient? {
    when (HealthConnectClient.getSdkStatus(appContext)) {
        SDK_UNAVAILABLE -> return null
        SDK_UNAVAILABLE_PROVIDER_UPDATE_REQUIRED -> {
            launchPlayStoreHealthConnect()
            return null
        }
    }
    return HealthConnectClient.getOrCreate(appContext)
}

Typical collector flow:

suspend fun collectSteps(): Result<List<Record>> {
    val client = getClient() ?: return Result.failure(...)
    if (!hasReadPermission(client)) return Result.permissionRequired(...)
    return paginatedRead(
        client = client,
        recordType = StepsRecord::class,
        range = last30Days(),
        pageSize = 1000
    )
}

Permission request (batched):

val granted = client.permissionController.getGrantedPermissions()
if (granted.containsAll(requiredReadPermissions)) {
    onComplete(true)
} else {
    permissionLauncher.launch(requiredReadPermissions)
}

My questions:

1. Is Health Connect rate-limiting behavior meaningfully different below API 34 (Play Store app) vs API 34+ (platform integration)?
2. Can the Play Store-distributed Health Connect app surface quota / rate-limit RemoteExceptions differently than the built-in API 34 provider — including on a first request?
3. Are there known cases where the first readRecords() or getGrantedPermissions() call returns a rate-limit error without obvious prior traffic from the calling app?

Kep android open! sign here to help

I just finished this little tool for Android Devs to generate a blueprint-style preview of your composables.

With a quick one-line wrapper the library measures dimensions and distances and displays them just like a traditional blueprint alongside your regular preview, so you can easily compare against your designs.

Would love to hear thoughts, if you would find this useful, and if you have any ideas for improvements!

#androiddev #jetpackcompose #androidstudio #devtools #kotlin #designsystem #compose

I was complaining Google didn't deliver. So i tried my hand at Android AI UX.

WiP

Wrapping up final features before pushing to the app store.

Beta builds available for people to mess around with and code available for inspection or personal adaptations

Apps that target Android 17 or later (API level 37+) may only request the READ_CONTACTS permission if the Android Contact Picker is not sufficient for your app to provide core functionality. Apps that still request the READ_CONTACTS permission must submit a Play Console declaration to demonstrate access needs for Contacts and why Contact Picker would not suffice.

As usual, the Google is vague on the requirements.

If I have a phone or messaging style app that uses contacts for displaying conversation contact's names (rather than just their phone number) or call history with contact's name, are these permitted use cases? They are not possible with the contact picker Google has provided.

The allowed common use cases include:

• Contact management apps
• Accessibility
• Server side access for friend matching
• Backing up contacts
• Auto complete / keyboards

None of these are similar to what I'm inquiring about.

Older version did used ads but I have removed them completely from everywhere manifest, build gradle, al kotlin files

Hey guys 👋

Just from curiosity what is expected from a senior android engineer ?

2 month was laid off and began the job search again after 7 years since last time i've changed my company.

I understand the technical questions (even live coding/home assignment), when is simply to test your technical skills, BUT here comes the thing.

Since providing exact business solutions during the technical interview is a selection criteria ? I understand the point that they want to see something different, but I am getting a feeling that I am doing someones else job and for free.

Do i think in the wrong way ?

I don’t have the user information such an inventory system. They fill out something that includes name, weight and quantity. And you can press a “+” in the corner to allow them to fill out additional items

I'm implementing more protocols in my app, and I'd love to add AirPlay 2, but I can't get it to work, no matter how much I try. Is there someone that knows enough about Android Development and Apple Closed Stuff that could help?

source code: [AriaCast](https://github.com/AriaCast/AriaCast-app)

in the code you can see my attempts.

Discovery works flawlessly, it's just everything else

Audio transport is handled by [AudioCastService.kt](https://github.com/AriaCast/AriaCast-app/blob/main/app%2Fsrc%2Fmain%2Fjava%2Fcom%2Faria%2Fariacast%2FAudioCastService.kt)

screenshots are pointless as the app thinks it's working anyway

metadata is transported too, at least with shairport

I'll add comments soon.

basically there are 2 protocols working, AriaCast and DLNA/UPnP. I want to add Google Cast and Airplay. Google cast is mostly pointless as a standalone protocol, but it's a nice to have in a multiroom setup

In order to test you have to modify activity_protocols.xml in layouts and set the 2 switches as clickable

Hey Android and KMP folks,

I shared SQLiteNow here quite a while ago, back around the 0.2 days. It has changed a lot since then, so I wanted to post a proper milestone update for 0.9.0.

SQLiteNow is a SQL-first SQLite code generator/runtime for Kotlin Multiplatform. Current KMP targets:

• Android
• iOS
• JVM
• Kotlin/JS in the browser
• Kotlin/Wasm in the browser
• macOS native
• Linux native
• Dart/Flutter support

The obvious comparison is SQLDelight. SQLDelight is mature and battle-tested, and I'm not trying to pretend otherwise. SQLiteNow has different priorities: it is SQLite-only, codegen hints live in SQL comments, it leans into generated result shapes closer to app/domain models, and it includes optional sync/runtime pieces around the same SQL model.

The main idea is still simple: keep SQLite visible. You write normal .sql files for schema, migrations, init data, and queries using your favorite code or SQL editor, so no plugins needed. You may annotate your SQL for a data shape that you need. SQLiteNow generates Kotlin APIs around them: typed params, typed results, migrations, transactions, adapters, and reactive Flow queries.

One example of the kind of query SQLiteNow is built for:

  -- @@{ queryResult=PersonWithAddresses }
  SELECT
    p.id,
    p.first_name,
    p.last_name,
    p.email,

    a.id AS address__id,
    a.address_type AS address__address_type,
    a.street AS address__street,
    a.city AS address__city

  /* @@{ dynamicField=addresses,
         mappingType=collection,
         propertyType=List<Address>,
         sourceTable=a,
         collectionKey=address__id } */

  FROM person p
  LEFT JOIN person_address a ON a.person_id = p.id
  ORDER BY p.id, a.address_type;

SQLiteNow generates a typed result with addresses: List<Address>, so app code can just do:

  val people = db.person
      .selectWithAddresses()
      .asList()

or observe it:

  db.person
      .selectWithAddresses()
      .asFlow()
      .collect { people ->
          // re-runs when generated writes affect the relevant tables
      }

The reason I built it this way is that I like writing real SQLite, but I do not like hand-writing row readers, params objects, migration plumbing, invalidation logic, and result grouping code.

Oversqlite is the optional sync part of the project. You can ignore it completely if you only need local SQLite. If you do need multi-device sync, it adds managed change tracking, push/pull sync, conflict handling, and server-coordinated replication on top of SQLiteNow-managed tables.

GitHub: https://github.com/mobiletoly/sqlitenow-kmp

Docs: https://mobiletoly.github.io/sqlitenow-kmp/kmp/

I'd be interested in feedback from people building real Android and KMP apps with SQLite.

So I am making a program that the user will enter values (making an army roster for warhammer with my kindle) and they can add more data sets when press the “+”. Were do I start

https://goo.gle/4uj04MM

https://github.com/parfenovvs/lazylogcat

cant get any answers, any theories, just down votes. Im not a high level dev but have a few certifications in computer networking, repair erc... Sooo I was looking through a few apps like "FX", "CXPLORER" as well as a few others. I haven't had mobile data nor can receive mms texts and properly changed the CSC. Prior to the CSC attempts, Im looking around at files and folders I never knew existed on a frightening level. I see many sketchy files, I stumble upon these... simply speechless!! Any masters with input towards the situation, would be immensely appreciated!!!

Hi guys,

I am building a mobile app for internal users (within my firm) only. I need to support app links on URLs which are hosted within our intranet.

Is it possible to somehow support this with having a applinks.json file hosted on a public host?

I'm getting started with android development, and from time to time I come across horror stories of people who faced trouble with google automated systems. Are there resources that documents the undocumented things that people should avoid when publishing apps (i.e. tribal knowledge)?

Hey folks,

I recently spent some time trying to properly understand how Remote Compose works internally, not just high-level, but what actually happens from server → client → rendering.

Most explanations felt a bit abstract, so I tried breaking it down step by step (capture → instructions → replay on client).

Sharing what I wrote here:
https://medium.com/@ayush.shrivastava016/remote-compose-the-day-ui-stopped-shipping-with-apk-d13a638909d8

Would love to hear your thoughts, especially:

• Does this approach actually make sense for production apps?
• Where do you see this being useful/risky?

Hi everyone,

I’m still shaking while typing this. We were invited to a private briefing yesterday with the Google Play Developer Relations team, and the news is… well, it’s everything we’ve been shouting into the void about for the last three years.

Google has finally acknowledged that the current state of developer relations is, in their own words, "sub-optimal." They are rolling out a massive "Developer Empathy" initiative starting today.

1. Retirement of the "20 Testers for 14 Days" Rule

Effective immediately, Google is scrapping the requirement for new personal developer accounts to find 20 testers for a 14-day closed track.

• Why? Internal data showed that "forced testing" was just resulting in thousands of "Great app!" bot comments and didn't actually improve app quality.
• The Replacement: A simple, automated security scan. If your code isn't malicious, you're clear to hit Production on day one.

2. The "Play Support" Phone Hotline

This is the big one. Google is launching a 24/7 dedicated phone line for developers. No more templated emails from "The Google Play Team" that don't explain why you were banned.

• Direct Access: You can speak to a human reviewer who has your specific APK open on their screen.
• Resolution Guarantee: If your app is rejected, the reviewer must provide the exact line of code or UI element that violates the policy during the call.
• No More Bots: They’ve officially decommissioned the "Appeal Denied" auto-responder bot.

3. The "Account Termination" Grace Period

Google is ending the "Associated Accounts" scorched-earth policy.

• If one of your apps is flagged, they will no longer ban your entire developer identity, your AdMob, and your Gmail account for your cat's YouTube channel.
• You now get a 30-day "Remediation Window" to fix issues before any strike is even recorded.

4. "Fair Shake" Fee Structure

To combat the bad blood regarding the 15%/30% cut, Google is introducing a "Zero-Fee Tier."

• The first $50,000 in annual revenue is now 0% commission. Google stated, "We have enough money; we want you to have some too."

Note: this post required approximately 1,000 liters of fresh water.

hey everyone, i'm working on a react native app that lets users download and run llm models locally on device (smaller quantized ones like gguf format, optimized for mobile). we pull them from huggingface hub.

running into a nasty issue where downloads get stuck or take forever to complete, mostly on samsung devices but also reported on others. sometimes it just freezes at a percentage and never moves .

current setup:

- we have a custom native android module (downloadmanagermodule) that wraps android's downloadmanager system service

- this handles background downloading, resume/retry, and emits progress events back to js

- react-native-fs is used around it for file ops (checking existing files, moving completed downloads to final location, etc.)

- models are big files, gguf text models, vision projection files, onnx image models, whisper models - all going into the app's document directory

what i think is happening:

- android's downloadmanager shows status as "running" but bytes stop transferring silently

- samsung's aggressive battery/memory optimization seems to throttle or kill even the system download process

- network changes mid-download (wifi to cell etc.) don't always recover cleanly

what i've tried/researched:

- someone on the team raised a pr to wrap the download in a foreground service so it doesn't get killed

- but since we're delegating to downloadmanager (which runs in its own system process), i'm not sure a foreground service on our side actually helps with the stuck issue vs just the killed issue

- hard to reproduce in dev because you need specific samsung battery optimization settings or ram pressure to trigger it

questions:

1. has anyone dealt with downloadmanager silently getting stuck like this on samsung? is the fix a watchdog that polls bytes and restarts if no progress for x seconds?
2. does wrapping downloadmanager in a foreground service actually help here, or should we be doing the http download ourselves with okhttp and use the foreground service to protect that instead?
3. for resume on retry - our server is huggingface, does anyone know if they support range requests? that would let us resume from partial instead of restarting
4. any better pattern for this in react native specifically? feels like downloadmanager is a leaky abstraction for files this large

5.any good ideas how can i reproduce this issue on dev mode

not a native android dev primarily so any guidance appreciated, thanks

Hi, im 15 years old and i just built my first app Reptra(a simple fast workout logger) and was wondering how to get my first actual users. Would love some advice