I found an introduced (2.0b3 and higher) bug in the player software that causes the player to crash if the shutdown delay timer is set too hi.

I need to keep it fairly high, so I can do remote sync's via wireless lan. If anyone else is doing this, what shutdown values are you using.

I was using 20,000 seconds
Cheers
Peterk

Are you talking about the 'stock' in-car shutdown timer or the hijack shutdown timer?

He's talking about the standby time set in Emplode. The one that gets invoked when you shut off the ignition.

Since there's a bug in the software, though, I'll bet whatever number it ends up being gets changed when the bug gets fixed.

In reply to:

---

Turns out that it was the shutdown delay. I had mine set at 20,000 so I could synchronize, via wireless lan, with the unit still in the car. 2.0b3 and higher writes that as 20,000,000 (milliseconds) to the player .ini file. Whats the bet that when the ignition is switched off, the player reads the value from the file, does an atol on it and ....shits itself.

---

You can test that theory by installing a Hijack kernel (totally unrelated to your problem), and using the "Force DC/Car Mode" option to test it in the house with a serial cable connected. If something is puking, there may be messages spat out the serial link.

You'll also need to edit config.ini to get the serial port back to the right speed (115200) first, since car mode switches it to 4800..

-ml

since car mode switches it to 4800..

Or you set car_rate in config.ini

....Since there's a bug in the software, though, I'll bet whatever number it ends up being gets changed when the bug gets fixed.....

My guess too. I'm just wondering what value people are currently using. Assuming that people are still doing this, there were a lot of posts about it ......

Of course I could just test it through trial and error.

PK

Of course I could just test it through trial and error.

Yeah... start out at, say, 1,000 milliseconds. See if it works. Then try 1,001 milliseconds. Then 1,002 milliseconds.

Let us know what you find out.

tanstaafl.

Of course I could just test it through trial and error.

Yeah... start out at, say, 1,000 milliseconds. See if it works. Then try 1,001 milliseconds. Then 1,002 milliseconds.

Let us know what you find out.

I did, only I lost my place somwhere around 1,000,436 and couldn't bring myself to do it again.

Seriously though, what happened to all the people who were doing this?

PK