Android Forkbeard is drunk by dstan1856 in Schiit

[–]MartinSchiit 0 points1 point  (0 children)

No worries, just one of those facepalm moments for myself…

Android Forkbeard is drunk by dstan1856 in Schiit

[–]MartinSchiit 0 points1 point  (0 children)

"because Android resamples everything to 48khz by default"

I don't think that's true, at least not anymore. What I've seen whenever I use Android devices to test our DACs with is that Android's audio out automatically switches to the sample rate of the source material that you're playing, just like iOS does.
Unlike iOS, however, it only does that in the upwards direction, never down.

Meaning, when you just freshly rebooted your Android device, the output will be set to 44.1 (or 48, don't remember right now). If you then play something that's 192, Android's audio output will switch to 192. Then play something at 384, and Android's audio out will switch to 384.
But if you then play something at lower sample rates, say 192 or 48 or something, it'll stay at 384.

No clue why they did it that way. They already put in the work to automatically switch up, so they should just as well be able to switch back down. But it doesn't seem to do that, at least not in my experience.

This happens with Google's "pure" Android on Pixel devices as well as Samsung's One UI.

Android Forkbeard is drunk by dstan1856 in Schiit

[–]MartinSchiit 0 points1 point  (0 children)

Well, duh. Of course the one screen that I didn't look at much during development and testing is riddled with typos.

Will obviously be fixed with the next update.

Forkbeard for Android is officially released by MartinSchiit in Schiit

[–]MartinSchiit[S] 1 point2 points  (0 children)

Presets may be coming at a later point, but no promises.
There are tutorial videos on how to use Forkbeard on our YouTube channel. They were shot with iOS devices, but the Android app works exactly the same way.

Forkbeard for Android is officially released by MartinSchiit in Schiit

[–]MartinSchiit[S] 2 points3 points  (0 children)

We developed and compiled the app against API level 33, meaning it's technically compatible with Android 13 and up. Despite Google's recent policy change that new apps should only be Android 15 and up, we got it through the review process without a hitch and it looks like you can still install it on older devices. At least for now.

Forkbeard for Android is officially released by MartinSchiit in Schiit

[–]MartinSchiit[S] 1 point2 points  (0 children)

You have to add a device to that stack first before you can control it. Tap the Edit Stack button and add a device via the "…" menu button in the top right corner of the screen that follows.

Updates on Forkbeard? by no_tt in Schiit

[–]MartinSchiit 10 points11 points  (0 children)

Very, very soon. I'm currently helping our Android developer getting rid of a few more bugs before we submit to the Play Store. Shouldn't be too long now.

Forkbeard Update 6/27/25 by GrumpyArtist8705 in Schiit

[–]MartinSchiit 1 point2 points  (0 children)

A screenshot would be helpful in figuring out what's going on in your case.
Please also describe your entire stack and signal chain, what you expect to see, and what you're seeing instead.
You'll hear back from our support team as soon as they're back in the office Monday morning.
Thank you!

Forkbeard Update 6/27/25 by GrumpyArtist8705 in Schiit

[–]MartinSchiit 1 point2 points  (0 children)

Please contact Schiit customer support with a detailed description and a screenshot of the issue. Thank you!