Shuttle
Shuttle copied to clipboard
Track order for albums with multiple discs gets mixed together
Shuttle version:
v2.0.2
Device, OS:
OnePlus 3, Android 8.0.0
Description of bug:
Albums discs gets mixed together if the track numbers start at 1 for each disc.
Steps to reproduce:
- In album view, select an album with multiple discs where each disc starts the track number at 1
- Make sure you are using the default sorting
Expected outcome:
Have the tracks listed as: disc 1 track 1, disc 1 track 2, ... disc 2 track 1, etc
Observations/Actual Result:
The tracks are listed as: disc 1 track 1, disc 2 track 1, disc 1 track 2, disc 2 track 2, etc
Only some albums are affected, they show the correct disc number in "Edit tags" but shows them as disc 0 in "Song Info"
Quick question @tollyx , what file format are you files in? I have one album which seems to not be affected by this bug and the only thing that is different with it vs my other albums is that it's in mp3 rather than ogg.
Also interestingly this seems to only affect Android 8. A friends android 7 devices is unaffected. I would be interested to see if it's still broken on Android 9 betas if anyone could try (which I can't otherwise I would)
It's all mp3, and now that you mention it, I also got one album where it works properly, mp3 as well.
One interesting tidbit I noticed now about the discs that gets mixed up: it reports as disc 0 in "Song Info", while it displays the proper disc in "Edit tags"
Slight bit of progress on my end. LineageOS 15.1, android 8.1, became available for my phone so i installed and had a look at this bug. Albums are now correctly seperated by disks. If @tollyx can confirm this still affects them then we can assume that is a bug dependant on Android 8.0, thus fixed in higher versions, or ROM dependent, thus the root cause isnt really fixable
Yeah, this still affects me on Android 8.0 (OxygenOS 5.0.3)
I've been thinking of trying out LineageOS myself, so if I do I'll check if that solves the issue for me as well.
Bump for this as it's still occurring and quite annoying. Hoping someone has some fresh ideas. I don't think it's Shuttle specific, rather how Android's MediaScanner and MediaStore work.
Based on this reddit thread I've tried padding the disc number using Mp3Tag as nn and nn/nn. After re-running the MediaScanner it made no difference.
The Android MediaStore documentation has no disc number property and implies TRACK should start with the disc number. Question is does the media scanner read the disc tag and append it to the track field? Somehow I don't think so otherwise we wouldn't have this problem.
Running Shuttle2.0.12b5 on Android 10

While this issue reproduces on my phone in certain albums, I'm not able to reproduce it on an emulator (with the same mp3 files). I tried with both 2.0.15 and the latest dev branch version.
Update:
I saw the same issue happening in the Google Play Music app on my phone. Don't think it's specific to Shuttle.
Also, see this thread: https://www.reddit.com/r/googleplaymusic/comments/7rz1aq/songs_out_of_order_despite_having_proper_tags/
I know Shuttle+ isn't being developed anymore, but FYI it appears Google have fixed this issue in a recent update. On a new Pixel 4a and old 3a the Mediastore now correctly orders the tracks.
I know Shuttle+ isn't being developed anymore, but FYI it appears Google have fixed this issue in a recent update. On a new Pixel 4a and old 3a the Mediastore now correctly orders the tracks.
@daedos Could you post your Android version? Also, was the update a system update, or one delivered through the Play Store?
I
I know Shuttle+ isn't being developed anymore, but FYI it appears Google have fixed this issue in a recent update. On a new Pixel 4a and old 3a the Mediastore now correctly orders the tracks.
@daedos Could you post your Android version? Also, was the update a system update, or one delivered through the Play Store?
I don't know when or how it was fixed, just happened to notice this weekend. Since both phones are Pixels they are as up to date as can be. Android version = 11 Android security update = 5 March 2021 Google Play system update = 1 February 2021 Build number = RQ2A.210305.006