Infeasible
Status Update
No update yet.
Comments
lb...@gmail.com
I get this too. HTC Desire + FroYo
am...@google.com
am...@google.com
Verified - not reading Artist info in WMA ID3 tags. Research indicates issue exists across Froyo implementation, not specific to any model phone.
am...@google.com
Also appears to affect AAC files.
zh...@gmail.com
It is also affecting most, but not all, of my MP3 files. I'm getting "unknown artist," "unknown year," "unknown disc number" and "unknown track number" on the files affected. It appears to be affecting files in odd random ways, ie., I have the tag info for the first track of one album, but not the rest and the first 2 of another. There is also an issue with track duration reporting. Tracks are being reported with lengths of 20~30+ minutes.
zh...@gmail.com
Same here unfortunately with unbranded HTC Desire and Android 2.2. Not sure whether to wait for a fix from Google or to convert my WMA into MP3..
pe...@gmail.com
Ok, whats up with this case. Sorry, but this servich is much worster then the HTC support. Now i have an unbranded desire and have to convert 7 GB wma files to mp3? So please, give us a fix for that or a reaction. Then we kow that you trying to fix this problem
lb...@gmail.com
Same problem on HTC Evo 4G 2.2 both stock and FreshMod. WMA files with ID3 tags don't show up correctly in either HTC music (stock) or DoubleTwist. WMA9 files don't play at all (though they never did). Ogg and MP3 seem fine, ogg tags show up correctly.
Guess I'll transcode all to ogg until a fix is available.
Guess I'll transcode all to ogg until a fix is available.
pa...@gmail.com
How could this have happened? No one thought to check if there would be issues with any of the major music file types? Those working on the Android OS have done great things, but this is a real bummer.
lb...@gmail.com
Same problem on my Droid Incredible with 2.2--happens with the HTC music player as well as Mixzing, a 3rd party player. However, Mortplayer does include the correct ID3 information, so I would suggest that program for accurate track reporting.
If the big brains at Google can correct this problem, can you also make it so that the tracks are listed in track order, not alphabetical order? I'd say 99.999% of the population prefer to listen to their albums in the order that the artist intended!
If the big brains at Google can correct this problem, can you also make it so that the tracks are listed in track order, not alphabetical order? I'd say 99.999% of the population prefer to listen to their albums in the order that the artist intended!
na...@google.com
Come in guys, without htis feature, the player is for me nearly useless. I buy my music in wma and dont wont to have a double workload while converting the files into mp3.
lb...@gmail.com
I have the same issue - however i had the problem previously (2.1) too. I have checked and triple checked - all the tags are present and correct. All my music is WMA. Synced from WMP12 - or copied directly to SD - makes no difference... HTC Desire.
se...@gmail.com
I am also experiencing this on htc droid incredible with froyo. Everything works fine for mp3 files. But with wma files, the songs always get placed in the "Unknown artist" section. I also verified that the wma files (on the phone memory) have the artist metadata correct.
lb...@gmail.com
I can't imagine this would be terribly difficult to fix. The HTC Music player has lost the ability to play .wav files from our Cisco phone system and does not recognize tags correctly.
Description
"MASTER" Android 8.0.
* What device are you using? (for example, Nexus 6P)
Android emulator.
* What are the steps to reproduce the problem? (Please provide the minimal reproducible test case.)
Run the attached sample code to show information about each of the availbale storage volumes.
This is the part of the code that causes the issue:
@SuppressLint("WrongConstant") final StorageStatsManager storageStatsManager = (StorageStatsManager) getSystemService(Context.STORAGE_STATS_SERVICE);
final StorageManager storageManager = (StorageManager) getSystemService(Context.STORAGE_SERVICE);
final List<StorageVolume> storageVolumes = storageManager.getStorageVolumes();
for (StorageVolume storageVolume : storageVolumes) {
final String uuidStr = storageVolume.getUuid();
final UUID uuid = uuidStr == null ? StorageManager.UUID_DEFAULT : UUID.fromString(uuidStr); //crash here
...
}
* Issue Category e.g. Framework (platform), NDK (platform), Hardware (CPU, GPU, Sensor, Camera), ART (platform), Runtime Permissions etc
Framework? Emulator?
* What was the expected result?
To run the code just fine.
* What was the actual result?
It crashed, even though the input value there was legit. Not sure though why I see 2 storage volumes on the emulator, but still...
The crash can occur even if you grant the app storage permission, though it's not required at all.
Here's the crash log:
java.lang.IllegalArgumentException: Invalid UUID string: 1AFD-3711
at java.util.UUID.fromString(UUID.java:194)
at com.example.user.appsizetest.MainActivity$1.run(MainActivity.java:51)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:243)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at java.lang.Thread.run(Thread.java:764)
The crash occurs for a UUID that's not null. It was : "1AFD-3711" . Something the framework should be able to handle...
On Nexus 5x with OPP3 this didn't occur, BTW.