Yes.vlc-android (being a libvlc-based player) supports ".opus" files now. You have to grab APKs from here until they release a new version.

A lot of cycles are used on my relatively low-end ARMv6-based phone (around 22-24% mono, 39% stereo). This could be caused by using the floating-point decoder implementation. Anything ARMv7-based should work better.

Rockbox should have it fairly soon, and the decoder implementation is integer and reasonably efficient (much optimization is still needed however).

Any info on how well it performs? From what I heard about the Opus decoder for Windows (or generally x86/x64), it is much slower than decoders for other lossy formats. On a portable device battery usage is a really important issue for an audio format.

Rockbox should have it fairly soon, and the decoder implementation is integer and reasonably efficient (much optimization is still needed however).

Any info on how well it performs? From what I heard about the Opus decoder for Windows (or generally x86/x64), it is much slower than decoders for other lossy formats. On a portable device battery usage is a really important issue for an audio format.

Its pretty well optimized now for ARM. The main thing remaining is to go through an write the FFT in assembly. Unfortunately, Opus does not use the same FFT lengths as other lossy formats, so it will need to be done from scratch. Once thats done it should be comparable to any other lossy format.

Rockbox should have it fairly soon, and the decoder implementation is integer and reasonably efficient (much optimization is still needed however).

Any info on how well it performs? From what I heard about the Opus decoder for Windows (or generally x86/x64), it is much slower than decoders for other lossy formats. On a portable device battery usage is a really important issue for an audio format.

This is a bit of a repeat of what I posted in a thread about audiobooks, but more on topic here. At this point (still not considered a stable release) Opus decodes fine on my E200 sansa at 12 kb/s (speech). It's about at the edge but works at 64 kb/s, and hangs up the controls at 128 kb/s. I'm told there is still a lot of improvement possible. At this point I will switch to Opus for speech but for music I'll wait.

Haven't tried it on my android tablet, but the power usage analysis shows the vast majority of power going to the display pretty much whatever I run even with wifi and GPS running, and the display goes to sleep after a few minutes if I'm just playing audio. On that device I've been sticking with Google music as I can have everything on the cloud and specify albums to be cached locally (for when I'm out of wifi range) and all works well... except that program is basically centered around MP3. I may get another app that handles Opus just to try it, but I'm limited to 16 GB total local storage so I really like the cloud aspect of google music.

From what I heard about the Opus decoder for Windows (or generally x86/x64), it is much slower than decoders for other lossy formats.

I ran some tests with latest foobar2000 1.2 beta 1, which now uses ffmpeg decoders for some popular lossy formats. I used presets for both lossy and lossless formats which yielded comparable bitrates (~62kbps/~700kbps). LAME didn't quite reach the desired bitrate even with V9. Here's the result:

So, Opus is not even faster than Speex, with which it also competes, and at least on x86 it is considerably slower than other common lossy formats. You can also see that the new ffmpeg decoders are really blazing fast, Musepack is now third to last in lossy codecs (if you include Speex), too. Let's hope Opus decoders will see some development in the future, but seeing how Xiph steadily improved all their other formats (Vorbis,Theora), I am quite optimistic.

The math doesn't work by itself. You need to analyze a whole system.The math can't explain this!

For a modern mobile devices (smartphones etc.) there won't be a gain in battery life in practice if You choose codec A that requires 6-7 MHz for realtime playback comparing to codec B (60-70 MHz) because the lowest frequency of today smartphone's proccessors is 200 MHz (Cortex A series). Something that your math can't see.On top of that, CPU consumes only a fraction of power because other parts like display consume comparable amount (if not more).

From what I heard about the Opus decoder for Windows (or generally x86/x64), it is much slower than decoders for other lossy formats.

I ran some tests with latest foobar2000 1.2 beta 1, which now uses ffmpeg decoders for some popular lossy formats. I used presets for both lossy and lossless formats which yielded comparable bitrates (~62kbps/~700kbps). LAME didn't quite reach the desired bitrate even with V9. Here's the result:

So, Opus is not even faster than Speex, with which it also competes, and at least on x86 it is considerably slower than other common lossy formats. You can also see that the new ffmpeg decoders are really blazing fast, Musepack is now third to last in lossy codecs (if you include Speex), too. Let's hope Opus decoders will see some development in the future, but seeing how Xiph steadily improved all their other formats (Vorbis,Theora), I am quite optimistic.

Opus might not be faster, but this is not what it's competing against with Speex. It is encoding latency where opus is winning clearly, making it the perfect candidate for voip.

There's FreeMP which support Opus as well by using the BASS audio library from Un4Seen. It has very few functions compared to other players like PowerAmp. However thanks to the BASS library which has ARM optimised decoders on Android, the resource usage is much lower than with VLC for example.

GoneMAD was lagging with Opus on my Nexus 5, at least while i was on the move and listening to music on my Bluetooth headunit in my car.Also it made my JVC headunit's calling ability crazy. Sometimes it made redial the last number when i finished the calling and was sure it was GoneMad because i could reproduce the problem more than once if GoneMad is running. I haven't tried it though lately.

Thanks for mentioning AIMP, i didn't know they are working on an Android version. My biggest issue with FreeMP is that it doesn't allow controlling the player from the headunit but looks like AIMP already supports that. Also i'm missing Replaygain. Don't know if AIMP is supporting it already.

- I have an old GT-I9100 which I use exclusively as a media player, so I can not reproduce the same problem occurred with you. Did you try increasing the audio buffer and enabe high priority receiver in settings?

You can run DeaDBeeF on Android. It is a Linux player along the same lines as Foobar, but less features.

Ah, yes! DeaDBeeF is an excellent audio player, undoubtedly.But the Android version does not support Opus format. Not long ago I made a request to the DeadBeef's developer, Alexey Yakovenko, according to their response support for Opus is not in his plans at the moment.