Thread: XM hanging occassionally

Played with the new test version and I had a hangup not even 2 minutes into using ME. Here are my steps:

1- Load ME
2- Go into Settings menu
3- Click Done, go back to ME
4- Go to FM/XM Screen
5- Go back to Home
6- Repeat steps 2 through 4. It then hangs on Loading screen

Also, trying out hibernation:
1- Play XM channel
2- Hibernated and come back
3- Loads right back to XM screen, no sound. Able to switch stations but no sound. Able to successfully exit ME without hanging.

Have you experienced any of the older issues where you were unable to change channels, or spontaneously exited out of the player while listening to XM?

I'll work on the hibernate / standby issues sometime next week, and I'll try to reproduce and solve your first problem then as well. I think they're actually related.

I have not had any of the older issues since the patch.

I've been pulling my hair out trying to reproduce these issues, and it's just not happening, at least not with me sitting in front of my laptop.

The only way I can reproduce these issues is if I pull the power plug on the XM receiver before the system is done suspending / hibernating. If you have your XM receiver wired to get power from your ACC line and not the atx power supply, that might be one of the issues here.

The other factor that might come into play here is that I cannot test this with a fully-functional setup. There's no way I can get XM signal where I work, so all I can tell is that I'm either talking to the receiver via the serial protocol, or not.

Originally Posted by tmar89

Played with the new test version and I had a hangup not even 2 minutes into using ME.

I cannot reproduce your problem at all - though if you do what you're saying fast enough, it will hang it up. I'm not sure if that's what's happening to you, but under normal use if yours hangs there every time, please turn on XM data logging and send me your debug.log based on this latest build.

Thanks for the update. Maybe not having any issues is a good thing and I'm just messing things up by being too hard on the software. I will turn on debugging and try to catch anything happening. One question. My Car PC uses an M2-ATX power supply thats connected directly to the battery. I don't have a keyboard connected to my PC so when I get stuck on the Loading screen I'm kinda stuck when I'm driving. And I don't have any guarantee that it will continue at any moment. So it makes it inconvenient to test. If I connect a keyboard to the PC and if I get stuck on the Loading screen, will I be able to just ALT-TAB or CTRL-ALT-DELETE to get out of the program?

As for the power, my XM is connected to my ATX power supply. But when I come back from hibernate, I dont get any XM audio like I do with FrodoSat. It's almost as if the XM software in FrodoSat is reinitialized when it senses a start from hibernate.

Thanks for the update. I will re-check everything in my set up and try to be a little more patient and see if I am the potential cause.

My XM is also connected to the power computer power supply.

The fact you don't get an XM signal when testing will make it pretty difficult to identify. After coming out of hibernation, and going into the XM Radio settings, It "looks" as if I am getting no signal (i.e. it shows that I have XM enabled and the receiver ID is there, but the signal bar shows nothing even know I am in clear range of an XM signal.)

Since you are trying this w/out a signal, after returning from Hibernation, try clicking the "Enabled" check box in the Radio Settings. Mine it won't allow me to uncheck/recheck it... After clicking a few times it will kick me out of the program.

Ok, I have a disturbing problem. I'm running ME 2.3.5 where I just copied the mediaengine.exe file into the 2.3.4 installation. When I open ME and go into the setup and click on the Debug Log tab, ME completely shuts down (crashes). I tried going into it 4 times today, even after a reboot. I finally just gave up the debug option and went into ME, clicked the XM button, it took a few seconds then kicked me right back to the main screen. I clicked the XM button again and it froze on the Loading screen. I wasn't able to ALT-TAB or CTRL-ALT-DEL out of the program. I had to pull the XM serial cable from my computer to get it to reboot physically. Maybe I have an installation problem with 2.3.5? Can I get a fresh 2.3.5 install to try?

Originally Posted by tmar89

Can I get a fresh 2.3.5 install to try?

There's nothing that an installer will do that copying the latest binary over won't.

There is an issue with using the debug tab inside the app when you have a large logfile, I've been meaning to fix that. Best thing to do is just copy the file onto a flash drive though - you'll need to be able to send it to me if you can find something useful.

Originally Posted by CTGTi337

The fact you don't get an XM signal when testing will make it pretty difficult to identify. After coming out of hibernation, and going into the XM Radio settings, It "looks" as if I am getting no signal (i.e. it shows that I have XM enabled and the receiver ID is there, but the signal bar shows nothing even know I am in clear range of an XM signal.)

Since you are trying this w/out a signal, after returning from Hibernation, try clicking the "Enabled" check box in the Radio Settings. Mine it won't allow me to uncheck/recheck it... After clicking a few times it will kick me out of the program.

The dead signal strength indicator you're observing is just an indication that communications with the receiver have died. Look in your debug.log file (not using the debug tab) and you will probably see a timeout message. As I mentioned, the only time I can reproduce this behavior is if I pull the power plug on the XMD1000 before hibernating. If returning from hibernation is the only issue you're having I'd strongly suggest shutting down / rebooting. You're probably not saving an awful lot of time anyway. My laptop actually restarts windows as fast as (possibly faster than) it hibernates / resumes.

Not sure what else to do with this to be honest. With or without signal it's hard to reproduce these issues, especially on my development machine.

Here's my debug log. Maybe this will help.