Ahhh! The stars? Umm, I'll check this morning. I usually just stay in the FAV list so I wouldn't see the icons. Is this something that would have been fixed at 1205? I know they're not there at 1204.

Actually they are not stars, David sent me a sideways triangle or something. But yeah, they should be working now, and showing in the Favorites section too, I will remove them though when viewing "Favorites" that seems to make sense...
Note too that we are on 1.206 now, I made a significant fix last night, but I don't think you had that problem of garbled station and song info...

Actually they are not stars, David sent me a sideways triangle or something. But yeah, they should be working now...

And they are!

Ya' know.. the arrows are a bit weird though since everywhere else they're used to show that there's more information "to the right". Plus, from a UI continuity perspective, you'd want to no change the star on the favorites toggle to an arrow, and that will really be confusing.

I thought the stars were fine, though a bit big.

...and showing in the Favorites section too, I will remove them though when viewing "Favorites" that seems to make sense...

Good idea, and you thinking about it saves me suggesting that you do it.

Note too that we are on 1.206 now, I made a significant fix last night, but I don't think you had that problem of garbled station and song info...

I never saw the garbled stuff, but I did see issues with stations having the wrong name, so "Bone Yard" is shown as the name for 82 (which is The System).

I'll pull 1.206 now and install it over lunch... and of course check first to see if you've dropped in 1.207.

Scott; I think I have a clue on the "XM doesn't resume from hibernate" issue.

This is happening to me about 1 out of 5 times, and it happened yesterday after work. The simple symptom is that XM comes up, but there's no track info and no audio. Restarting CF _does_ bring it back.

What I found yesterday is that when the symptom was happening, looking at the XM settings showed... (wait for it, it's a good one!) ...Device = XMPCR. Very weird.

I have the log but um... What're you doing in here Scott? I have timestamps like "49:09:36", and the file is full of control characters...

is that when the symptom was happening, looking at the XM settings showed... (wait for it, it's a good one!) ...Device = XMPCR. Very weird.

"The settings" - as you went into Settings when CF running, and it was listed in Settings as XMPCR? Or you looked at the config.xml file right after it happened? Can you give me all the info you can on that?

"The settings" - as you went into Settings when CF running, and it was listed in Settings as XMPCR? Or you looked at the config.xml file right after it happened? Can you give me all the info you can on that?

Randomly selected stations, bounced in and out of XM, started playback from Media, happened to look at NAV. Everything else seemed fine.

Looked at Settings from within CF, noted that Device = XMPCR

Exited CF, reloaded CF, XM came up. CF showed Device = XMDirect

I didn't explicitly look at the XML, but given that a restart of CF brought it back and showed valid info, I'd bet that the XML was "correct" in that it was still showing "XMDirect".

I'll check for sure the next time it happens.

When you come out of hibernation and it's still working, in Settings does it show XMDirect as it should? Put another way, it shows XMPCR only in the case where it does not work coming out of hibernation?

When you come out of hibernation and it's still working, in Settings does it show XMDirect as it should? Put another way, it shows XMPCR only in the case where it does not work coming out of hibernation?

A far as I've seen, yes, this is true. But honestly, I've fallen into the trap of only looking for the source of trouble when there there _is_ trouble.

I'll keep a closer eye.

Any hints on working with the log file so that I can get you pieces from there when this happens? Though, it looks more like the logging is just focused on commands and responses to the receiver.

A far as I've seen, yes, this is true. But honestly, I've fallen into the trap of only looking for the source of trouble when there there _is_ trouble.

I'll keep a closer eye.

Any hints on working with the log file so that I can get you pieces from there when this happens? Though, it looks more like the logging is just focused on commands and responses to the receiver.

If you can send it all that would be great ([email protected]). If too big look for the text "PowerMode Change:" and we can look around/after that area, which would indicate the system coming out of hibernation... The commands will tell me if it is trying to do the XMPCR way, or the XMDirect way, it won't say explicitly...