Obsolete
Status Update
No update yet.
Comments
rc...@gmail.com
I get this too. HTC Desire + FroYo
rc...@gmail.com
Verified - not reading Artist info in WMA ID3 tags. Research indicates issue exists across Froyo implementation, not specific to any model phone.
0x...@jeffbryner.com
Also appears to affect AAC files.
jo...@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.
0x...@jeffbryner.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..
jo...@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
de...@champds.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.
is...@google.com
jp...@google.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.
Description
Include in the Users.history:list response the timestamp of when the event occurred.
What is the purpose of this new feature?
To better understand when the activity actually happens (labels added/removed, messages deleted). For new emails, this information can be taken from the internalDate in the get message response although for consistency would be best to have it also included in the history list response together with the other events.
What existing APIs would this affect?
Users.history:list
What existing data does this use?
Unaware if this data is not already recorded internally. If it is, it just needs to be exposed in the API response.
Notes:
The alternative to this, is to setup push notifications and record the timestamp of when the message was sent to the app server. This feels like an unnecessary overhead and not accurate in the event of delays getting the notifications due to network unavailability.
To subsequent readers: If you are also interested in this requested
feature, please
click the star next to the issue number.