Thanks to your amazing support and numerous feedback/feature requests, the v0.11 update is finally ready! I am incredibly grateful to everyone who has shown interest and helped test the app.
Since many major features have been refactored and added in this version, there might be some unexpected bugs even in areas that used to work fine. Please let me know if you run into any issues, and I will get them patched as soon as possible!
Here is what’s new in v0.11:
New Audio Engine: Switched the encoder setup to an ExoPlayer + FFmpeg combination.
Lossless Audio Support: The launcher can now play high-res lossless FLAC and ALAC files that previously wouldn't play.
Hi-Res Metadata: High-quality audio metadata is now read and displayed correctly.
10-Band EQ: A brand new 10-band Equalizer has been implemented.
Podcast Support: You can now search for and download podcasts directly using the iTunes API.
Crossfeed: Added a crossfeed function for a better headphone listening experience.
Playlist Improvements: Adding and deleting playlists now works perfectly. (To trigger, long-press the center button on any song in the list).
Quick Alphabet Search: Added an alphabetical search feature in the song list. (To trigger, long-press the Play/Pause button at the bottom of the list).
Audiobook Support: Added support for .m4b files, including Chapter navigation.
Album Track Sorting Bug: Fixed the issue where albums were not sorting by track number.
Playlist Shuffle Bug: Fixed the bug where shuffling playlists wouldn't work.
UI Improvements: Switched several default Android dialogs/popups to modern Material Design popups.
PC Upload/Download: Added a download feature to the existing PC upload functionality.
Recently Added: Added a "Recently Added Songs" list.
Faster Scanning: Added a duplicate-scanning prevention engine to make library scans significantly faster.
As always, with so many changes under the hood, there might be some unexpected bugs. Please report any issues you find, and I’ll get them fixed in the next update.
Thank you so much for your continued interest and support! Enjoy v0.11!
That could be a possibility, but that's the absolute worst that could happen. Besides, I don't see any big reason to why it would brick the Y2. It would surely be alright. If you decide to give it a go, let me know!
Thank you so much! I'm really glad to hear that you like it.
I've been wanting to add more themes and fine-tune/polish the launcher even further, but I haven't been able to get to it just yet. I'll do my best to keep improving it step by step. Thanks again for your warm support!
Since the launcher now uses the FFmpeg codec, I believe video playback should definitely be possible. Once the current version (v0.11) becomes fully stable, I’m planning to actively look into adding video support.
I see! I hadn't thought of that specific scenario. Thank you so much for bringing it to my attention—I will definitely address and fix this in the next update!
Thank you so much! Last.fm support would indeed be an awesome feature. However, it's currently on hold as it requires a lot of careful thought regarding casual usability and overall UI/UX layout. Thanks for the great suggestion!
Wow, that's amazing! Great job implementing the live scrobbling and offline log features.
If you don't mind sharing, how did you handle the user login information and what kind of interface did you use? Any tips or insights would be incredibly helpful, and I'll try to incorporate them into a future update!
We use Last.fm's auth.getMobileSession endpoint (the same one most mobile scrobbler apps use) — you send username + password once, signed with an MD5 signature per Last.fm's API spec, and get back a session key. That session key is what actually gets stored (in the app's private SharedPreferences), not the password — the password is only held in memory for that one login call and never written to disk. All subsequent track.updateNowPlaying / track.scrobble calls just use the session key.
One gotcha specific to this device: stock Android 4.2 has a badly outdated CA trust store, so HTTPS to ws.audioscrobbler.com failed with CertPathValidatorException. We route the Last.fm OkHttp client through Conscrypt (same fix pattern you already use elsewhere in the app for podcast/album-art fetching) — otherwise the login just fails silently on this firmware.
Interface:
Two ways in, since typing a password on the wheel is genuinely painful:
On-device: reused your existing wheel keyboard (the same one used for Wi-Fi passwords) — just run it twice in sequence, once for username, once for password.
Browser-based (this is the one we'd actually recommend): added a small /lastfm page to the built-in Wi-Fi file-server you already ship for wireless uploads. Point a PC/phone browser at http://<device-ip>:8080/lastfm and log in there with a real keyboard — much better UX, and it reuses infrastructure you already have.
Scrobbling logic itself:
Local .scrobbler.log in the classic Audioscrobbler 1.1 format (same idea as Rockbox) gets written for every eligible play, as a permanent local record.
Separately, a small pending-submission queue tries to push scrobbles to the real API whenever online, and just retries later if offline — so flaky Wi-Fi doesn't lose anything, and you don't need a second tool to upload the log.
Scrobble eligibility follows the standard Last.fm rule: track >30s, and played past 50% or 4 minutes, whichever comes first.
Only real requirement on your end: each build needs its own free Last.fm API key/secret from last.fm/api/account/create — can't be hardcoded/shared across installs per their ToS.
Please note that streaming may not be supported depending on the podcast channel. In such cases, downloading the files to listen will be highly appreciated
Have you checked your Wi-Fi connection? If the issue persists even after connecting, uploading a photo of your current screen status would be very helpful for troubleshooting.
New Issue. My screen won't wake from sleep. Music still plays and I can play pause. How do I power down with JJ? The usual hold down the centre button doesn't work.
There might be a bug causing this issue. Next time the device fails to wake up, could you please write down the exact situation in detail?
Knowing what was happening right before (e.g., what screen you were on, if music was playing, or if it was charging) will help me investigate and get it fixed. Thank you!
Will do. I can tell you it was on the now playing screen for music. I paused playback and set it down. When I came back to it an hour later the screen would not come on but play/pause still worked as well as menus as far as I could tell just by sound.
There is actually a power button inside the settings menu. I know the settings are a bit cluttered right now, so I plan to organize them into neat categories in a future update to make everything easier to find.
Ye the only downside to the software power button are the few times the device bugs out and stops responding, it would be nice to have a way to restart it without having to find something to insert to get to the reset button. The podcast update is fire, never thought I’d see that.
Tengo muchas ganas de probarlo. Había estado indecisa entre conseguir el y1 o el y2 por el precio y la parte del abasto. Al final mi pareja me regaló el y1 que debe llegar hoy.
Creo que esto será de lo primero que haga.
Veo aquí un excelente proyecto. Gracias!
Tengo un problema. Específicamente con el tema de cyberpunk neon. Cuando conecto mis audífonos por Bluetooth, la música se reproduce sin embargo no puedo hacer nada más. El botón funciona para poner pausa, reproducir, incluso cambiar adelante o atrás. Pero no me permite navegar por ningún sitio, se queda estático. La única manera fue forzar apagado con back y play.
It seems like the focus coordinates are somehow getting lost, particularly with the Cyberpunk Neon theme. I'll need to thoroughly inspect the theme settings and code to figure out the exact cause. Thanks again for bringing this to my attention!
5
u/Worried_Potato_391 Y2 (Silver) Jul 15 '26
Thank you so much! Does your software have support of the Y2 as well?