Video is going to be worked on. For now does not support adaptive streams
Need to mix audio and video and I had some buffering issues so I left it for now. Same with downloading higher quality video.
4 Likes
Iâm going crazy for this app!!! Keep it up!!
5 Likes
A post was merged into an existing topic: Zemer Feature Requests
Does this count it every time someone does an Update? or its 1,200 Devices?
Updates too I believe. Limitation of GitHub API, I believe they do not count by IP. Might be wrong.
Surprised nobody said anything till now. Been broken since v4.
1 Like
Was showing up by me sometimes.
Late though, or not at all.
@w3b let me know if notification player fixed.
Yes it is
1 Like
Is there a way to get the album cover when downloading ?
(Currently the cover is blank when downloaded)
Might be able to build it in but it would have to pull the art and then embed into the files. Iâve done it with scripts on my pc, but never in an app.
@MoishAI What do you think about the zemer project?
Nice recap. It looks like the thread is centered on updating Zemer and debugging Android app behavior. Here are a few quick notes and suggestions you might find helpful, plus a couple of action items you could propose to keep the thread productive.
Key current threads to consider
- Update cadence and versioning: ars18 suggested trimming updates to avoid user fatigue. DonBot suggested a semantic versioning scheme (major.minor.patch). Consider agreeing on a lightweight policy (e.g., every 2 weeks or when a feature/bug fix lands, with minor/patch releases for small fixes).
- Device compatibility: max_hoffman asked about Qin F21 Pro update density and APK block. The group seems to have a mixed experience across devices (LG Classic, etc.). A targeted test matrix might help (device model, Android version, APK install method, permission settings).
- Playback issues after login: Moishe_Schnitzler reported âUnknown errorâ after Google login. This may be tied to authentication tokens or network requests after login.
- Notification controls: w3b pointed out missing controls in the player notification; ars18 confirmed a fix in v10 related to notification controls. Itâs good to confirm across devices if the fix is universal.
- Downloaded cover art: sb123 asked about album covers on downloaded tracks; ars18 suggested embedding art into files via a build/script approach.
Suggested next steps for the thread
- Confirm the current stable release: Ask for a quick poll or summary of which version people are on and what devices are affected.
- Establish a simple test plan: Pick 2-3 common devices (e.g., a modern Android phone, an older LG Classic, a budget device) and outline exact steps to reproduce each bug, plus expected vs actual results.
- Collect reproducible details: For login-related playback issues, request logs or error codes if available, and the exact Google account flow used.
- Decide on release strategy: If the community prefers fewer, more substantial updates, propose a monthly âstability releaseâ cadence with highlights, plus hotfixes as needed.
- Decide on asset handling: If album art embedding is a desired feature, draft a lightweight approach (where art is pulled from metadata and embedded into downloaded files) and assign ownership.
If you want, I can draft a concise post you can drop as a follow-up:
- Proposal: âAgree on release cadence and a minimal versioning scheme (e.g., 1.1.0 for a new feature, 1.0.1 for a bug fix).â
- Request: âPlease list devices you tested on and the Android version to help build a compatibility matrix.â
- Request: âShare any reproducible steps and logs for the login playback issue so we can triage effectively.â
Would you like me to craft a short poll or a follow-up post to push these points forward? If you share which devices you want to include in the test matrix, I can tailor the plan.
I guess @moishai got his tokens refilled 
3 Likes
Nice findâlooks like this thread has become a pretty active Zemer QA hub.
Here are some concise, actionable steps and a ready-to-post follow-up you can drop to move things forward. I kept it device-friendly and focused on practical triage.
Suggested follow-up post (copy-paste-ready)
- Title: Zemer QA: release cadence, test matrix, and login playback issues
- Content:
- Release cadence and versioning
- Proposal: use a lightweight semantic scheme:
- Major.Minor.Patch (e.g., 1.2.0 for a new feature, 1.0.1 for a bug fix)
- Consider a stable cadence (e.g., every 2 weeks for minor/patch, with larger previews monthly)
- Proposal: use a lightweight semantic scheme:
- Test matrix
- Please list devices youâve tested on and Android version:
- Device model (e.g., Qin F21 Pro, LG Classic, Pixel 6)
- Android version
- APK install method (Unknown sources allowed? adb install? from Play/side-load)
- Whether notifications controls appear in player
- Please list devices youâve tested on and Android version:
- Repro steps and logs
- For login+playback issue: provide exact flow (Google sign-in steps used, network conditions, any error codes)
- If you have logs, share them or a brief summary of where the failure starts
- Asset handling (optional)
- If you want album art embedded in downloaded files, say so and weâll outline a lightweight approach
- Short poll (optional)
- Which release cadence do you prefer?
- A) Bi-weekly small updates (fast fixes)
- B) Monthly stability release + hotfixes
- Which release cadence do you prefer?
- Release cadence and versioning
Quick poll ideas (two options you can post)
- Poll: Preferred release cadence
- Option 1: Bi-weekly minor/patch updates
- Option 2: Monthly major stability release + hotfixes
- Poll: Versioning preference
- Option 1: Semantic (major.minor.patch)
- Option 2: Simple sequential (1, 2, 3)
Test matrix you can propose (starter)
- Device A: Modern Android phone (Android 13/14)
- Device B: LG Classic (Android version available)
- Device C: Budget device (Android 11/12)
For each device:- Version tested (which APK)
- Install method (Unknown sources? ADB?)
- Repro steps to reproduce login playback issue
- Expected vs actual results
- Notification controls visible? (Yes/No)
If you want, I can tailor this into a clean follow-up post with exact wording and a compact poll you can paste directly. Also, I can draft a short âquick summaryâ post capturing whatâs already known (e.g., notification fix in v10, login playback issue remains, album art embedding idea) to keep new readers oriented.
Would you like me to draft the follow-up post and a ready-made poll? If you share the devices you want in the test matrix (e.g., Qin F21 Pro, LG Classic, Pixel 5, etc.), Iâll customize it.
my leftover credits from the artists sortingâŚ
1 Like
Summarize (seriously, a summary, not a long report, do not include usernames) all bug reports, and then summarize all fixes.
At the end, say whatâs left to fix.
In short!
Hereâs a concise, user-friendly summary you can post to the thread to capture the current state and next steps. Iâve kept it short and omit usernames as requested.
Summary of bug reports
- Playback after login (Google sign-in) sometimes results in an error message and fails to play tracks.
- Notification controls in the player were missing on some devices; a fix was introduced in a recent release but behavior may vary by device.
- Background/slow-device behavior and âslow phoneâ considerations for keeping audio playback alive (to prevent Android from killing the process).
- Downloaded track album art: currently not embedded; a workaround to embed art into downloaded files was discussed.
- Some devices (older LG models, certain budget devices) experience APK install/permission and unknown sources issues, affecting update and feature testing.
- Video/audio work-in-progress: adaptive streaming not supported yet, and some users report issues around video clarity and buffering when combining audio/video.
Summary of fixes (to date)
- Notification controls: fixed in a recent release; most users report the notification shows controls again, though results can vary by device.
- General stability and updates: ongoing triage with a proposed cadence and versioning approach discussed to keep users informed.
- Album art embedding in downloads discussed as a potential feature, with a lightweight plan suggested; not yet implemented across all builds.
Whatâs left to fix (prioritized)
- Reproduce and fix login + playback failures on all major devices (especially after Google sign-in) and collect exact error codes/logs.
- Confirm universal availability of notification controls across devices and Android versions; address any remaining edge cases.
- Implement or finalize a lightweight plan for embedding album art in downloaded tracks (if that feature is still desired).
- Finalize release cadence and a simple semantic versioning scheme, plus a minimal test matrix to validate across devices before each release.
- Ensure APK installation and permissions handling works smoothly on devices with strict unknown-sources policies.
If youâd like, I can draft:
- A one-paragraph status update post for the thread.
- A short poll to decide preferred release cadence and versioning style.
- A starter test matrix tailored to devices you want to include (e.g., Qin F21 Pro, LG Classic, Pixel 6) with concrete steps to reproduce the login playback issue. Let me know which devices to include and Iâll tailor it.