Sorry if this has posted before, but I was out for two weeks and there are just too many messages to try to catch up on :)

I'm using 2.0b3. Up until this morning the clock was working fine. The last time I looked at it was 17:45 last night when I got home from work. This morning, it looked like it might've been a little fast (like 20 mins or so - it read 07:00 instead of ~06:40 which I was expecting). As I made my way to work (about a 25 minute commute), the clock just went wacko. I glanced at it again, and it said it was 00:15. I thought that it might've been on the wrong time mode, so I cycled the time display until I found the clock again. This time it was reading 01:38. I verified the time display was set to clock again, and it was 01:59 or something. The elapsed and remaining times look correct.

I'm kinda excited to get back to my car and find out what time it is when I leave ;)

It IS a Mk2, right?

Yup. MK2a. Like I said, it worked perfectly up until this morning, and that includes a two-three week period where it wasn't plugged in at all.

I just realized last night that if you hit pause while in player mode, with the clock displayed, the clock pauses too.

that if you hit pause while in player mode, with the clock displayed, the clock pauses too.

Known bug FITNR.

Was that the only problem?

No, but I haven't been able to reproduce the wonkiness that the clock exhibited last week. It was out of whack for about 24 hours, then back to normal. I swear I'm not crazy ;)

... known bug before B3, SHBFITR!

Wheeeee. Another update. It has happened two more times this weekend. What it ends up doing is keeping an elapsed time of how long the car has been running, not the track or playlist or anything else. When I start the car, it will sometimes set the clock to 0:00:00, and it progresses normally. It has only happened three times (that I've noticed).

Sure you're not just accidentally pressing the "1" key on the remote and setting it to elapsed time, and then being on the Aux or Radio inputs? Or are you on a Mk1 that doesn't have a clock at all? (EDIT: I read back on the thread and see you are on a 2a.)

Nope, most of the time I don't even touch the remote, it just sits on the passenger seat. Really weird. It's now doing it about 1/10 car starts (I almost said car reboots, but stopped myself - I still haven't lived down referring to a convertable as an 'open cockpit'). I wonder if the electrical system in my car is on its way out or something.

I'd guess it was your supercap, not your car. If the time setting is lost when you pull the unit from the sled, the RTC is probably not getting juice from the cap. If you want, you can put a voltmeter across the capacitor's leads. If you get ~3V, it's good. Much less, and you should have the cap replaced

That might be it, except I don't usually remove the empeg from the sled . The time isn't really 'lost', it just doesn't get displayed. It goes back to normal without removing the empeg from the sled, or resetting the clock, or touching the remote, just restart the car (and hence, reboot the empeg - its shutdown timer is set to like 5 or 10 secs). Sometimes it works, other times it just doesn't. *shrug*

Since it doesn't seem that anybody else is experiencing this, now I'm really really really confused

I am having a similar problem.

This morning my display clock stopped for approximately 20 minutes. Then it resumed where it left off, effectively making it 20 minutes late. The actions that led up to this behavior:

1. Start car. Previous playlist resumes playing.
2. Switch to another playlist after 5 minutes.
3. Look down a few minutes later and notice that the clock has stopped on the Info screen.
4. Continue drive. Clock resumes operation after ~25 minutes.