Fixed
Status Update
No update yet.
Comments
gr...@google.com
I get this too. HTC Desire + FroYo
[Deleted User] <[Deleted User]>
Verified - not reading Artist info in WMA ID3 tags. Research indicates issue exists across Froyo implementation, not specific to any model phone.
[Deleted User] <[Deleted User]>
Also appears to affect AAC files.
gr...@google.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.
[Deleted User] <[Deleted User]>
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..
gr...@google.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
el...@greensql.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.
[Deleted User] <[Deleted User]>
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.
ya...@google.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!
[Deleted User] <[Deleted User]>
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.
is...@google.com
ya...@google.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.
[Deleted User] <[Deleted User]>
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.
ra...@covermore.com.au
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.
ry...@google.com
Android 2.2 won't recognize tags in WMA files. please fix!!
ya...@google.com
Same problem with unrecognised tags in WMA files: 'Unknown Artist' appears in music player after Froyo update on HTC Desire. Works fine otherwise.
pr...@gmail.com
I have the same problem with unrecogised wma tags. I received an Android system patch a couple of days ago but it hasn't fixed it
ma...@craig-mitchell.com
For those of us with HTC phones, please submit a ticket to HTC as well. I called their support and they acted like they had no idea of this issue.
ya...@google.com
Phoned HTC and they said send my phone back and they will reinstall all the software. I am doubtful it will fix it. But they said it might just be due to the download having a hiccup mid process.
Is this common to all HTCs on Android 2.2? If so I definately dont think it will work (plus it seems to be on other phones too)
Is this common to all HTCs on Android 2.2? If so I definately dont think it will work (plus it seems to be on other phones too)
dp...@gmail.com
That's interesting. When I submitted a ticket to HTC online their second level response told me to convert all my music to mp3. Worthless
jo...@gmail.com
I have also got this problem since upgrading to 2.2 on my HTC desire. None of my wma files display artist information despite having been fine before the update. The files are not corrupt as loading them back onto my PC shows them to be fine. I had no problems during my update process and would be very surprised if this could be caused by such a thing anyway.
an...@gmail.com
Same issue here. All WMA files are listed as "unknown artist". When can we expect a fix for this as surely Google/HTC or whatever manufacturer don't think it's acceptable for this not to work properly.
jo...@gmail.com
This is not an HTC issue, though reporting it to them may help encourage Google to patch this. It is strictly an issue with Froyo and any music player that depends on how Froyo reads the file tags. Other players that read the file tags independently are fine.
an...@gmail.com
[Comment deleted]
jo...@gmail.com
I'd be willing to bet when Google finally fixes this my phone will be so obsolete I won't even get an update
jo...@gmail.com
Same issue here with an HTC Incredible running 2.2. I had issues before in 2.1, but mp3tag helped me fix those. Now, however, it has no affect as the ID3 tags are properly saved.
av...@travelers.com
Same issue here. The file in question DOES have the artist name listed under properties.
ca...@gmail.com
Same issue on desire with froyo
an...@gmail.com
This is a big problem for users of our MixZing Media Player app, anyone with WMA files on 2.2 is now telling us they get unknown artist on all their songs.
And why do you use the parent directory name as the album name? I know that will work sometimes, but it gives totally random and confusing results. Better to have "<unknown>", which is the truth.
And why do you use the parent directory name as the album name? I know that will work sometimes, but it gives totally random and confusing results. Better to have "<unknown>", which is the truth.
te...@gmail.com
As a user of MixZing (and very nice it is too) can I just add my name to the gripe list that .wma are no longer properly listed since updating to 2.2. A fix would be really appreciated.
pr...@gmail.com
Same here... HTC Desire on Orange running 2.2.
This was working fine before the 2.2 update.
This bug makes the media player "almost" useless, trying to find anything is now very difficult.
This was working fine before the 2.2 update.
This bug makes the media player "almost" useless, trying to find anything is now very difficult.
br...@gmail.com
[Comment deleted]
[Deleted User] <[Deleted User]>
Why is it that Google never ever comment on any of these bugs? It's like talking to a brick wall. Are we getting a fix for this, it's a really annoying problem and makes Android's ability to play WMA file utterly useless. It also means that all WMA files are scrobbled to last.fm with "unknown artist". Come on Google!!!!! Can you imagine is iOS suddenly stopped reading the artist tag of AAC files? At least there would be some sort of acknowledgment from Apple and probably a fix within days. It's unacceptable to have this issue unfixed and not even acknowledged for such a long time.
cl...@gmail.com
Verizon's vmm app fixeds everything by morphing files to ogg. This is Verizon with with the big dick.... fucking us all..
ol...@mailchimp.intuit.com
Verizon's vmm app fixeds everything by morphing files to ogg. This is Verizon with with the big dick.... fucking us all..
ad...@afrl.af.mil
Verizon's vmm app fixeds everything by morphing files to ogg. This is Verizon with with the big dick.... fucking us all..
Description
What steps will reproduce the problem?
gcloud init
What is the expected output? What do you see instead?
expected: connection to gcloud.
Instead :
Checking network connection...done.
ERROR: Reachability Check failed.
Cannot reach
Cannot reach
Cannot reach
son (SSLHandshakeError)
Network connection problems may be due to proxy or firewall settings.
Current effective Cloud SDK network proxy settings:
type = http
host =
port = 80
username = None
password = None
What would you like to do?
[1] Change Cloud SDK network proxy properties
[2] Clear all gcloud proxy properties
[3] Exit
Please enter your numeric choice: 3
ERROR: Network diagnostic (0/1 checks) failed.
Please provide any additional information below.
1) environment variables "http_proxy" and "https_proxy" are set.
2) This error is most likely because this is behind a corporate proxy, which does packet inspection. In order to do this, it injects its own certificates into the SSL certificate "chain of trust". These additional certificates are in the Java and Windows certificate stores.
3) I believe that Python27 (used by the Gcloud SDK) uses OpenSSL for the SSL work. Locally this is at version 1.0.2h, and I have set env variables SSL_CERT_FILE and SSL_CERT_DIR to point to a certificate store containing the corporate proxy certificates, with no success.
4) Likewise, hard to obtain any further information about the nature of the failure. It could be down to mismatch of encryption algorithms, but less likely since recent OpenSSL in use. Or it could be related to the certificates.
Installation information:
Google Cloud SDK [137.0.1]
Platform: [Windows, x86_64]
Python Version: [2.7.12 (v2.7.12:d33e0cf91556, Jun 27 2016, 15:24:40) [MSC v.1500 64 bit (AMD64)]]
Python Location: [C:\opt\Python27\python.exe]
Site Packages: [Disabled]
Installation Root: [c:\opt\google-cloud-sdk]
Installed Components:
bundled-python: [2.7.10]
bq-win: [2.0.24]
core: [2016.12.08]
core-win: [2016.12.08]
gcloud: []
windows-ssh-tools: [2016.12.08]
gsutil: [4.22]
bq: [2.0.24]
gsutil-win: [4.22]
System PATH: [c:\opt\google-cloud-sdk\bin\..\bin\sdk;c:\opt\Python27;D:\IBM\WebSphere MQ\java\lib;D:\IBM\WebSphere MQ\java\lib64;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Sennheiser\SoftphoneSDK\;C:\Program Files (x86)\GNU\GnuPG\pub;C:\Program Files\nodejs\;C:\Program Files\Cloud Foundry;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\ProgramData\chocolatey\bin;D:\IBM\WebSphere MQ\bin64;D:\IBM\WebSphere MQ\bin;D:\IBM\WebSphere MQ\tools\c\samples\bin;C:\apps\FME\;C:\apps\FME2015\;C:\Users\angus\AppData\Roaming\npm;C:\Program Files (x86)\Microsoft VS Code\bin]
Cloud SDK on PATH: [False]
Kubectl on PATH: [False]
[output truncated]