Last call time displayed as last HS restart time

[S-F]

If HS3 restarts after the last call the time listed for the last call on the devices on the home screen is the time of the restart, not the actual time of the call. The call log remains correct. Otherwise the other information is correct. Is this a bug? Is this planned? Is there a way around this?

[Ultrajones]

The routine that rebuilds the devices on startup was setting the last change time. I posted UltraCID3 HSPI version 3.0.5341.13686 that only updates the last change when the device is created.

Regards,
Ultrajones

[S-F]

Thanks! I'll let you know how it all goes once I get a new call and restart HS3.

[S-F]

The new plugin isn't registering any new calls for me. I've gotten a few and they don't show up. Should I give you a debug log or something like that?

[Ultrajones]

What type of troubleshooting have you done so far? Have you tried to restarting your computer?

Regards,
Ultrajones

[S-F]

Yeah, I have restarted it a bunch of times because I was having all kinds of crazy inexplicable database issues yesterday. Not sure what happened but at least that all seems to have gotten better. Still no CID though.

[Ultrajones]

Okay, next step is to make sure your modem is still on the com port you selected and that it is outputting caller Id data. Please see the "Initial Setup Checklist" section of the UltraCID3 HSPI User's Guide on how to confirm CID is working outside of the plug-in.

Regards,
Ultrajones

[S-F]

Gotcha. Will do. I forget what all is involved in the setup but I did verify that the COM port is correct.

[S-F]

So it passed step #2 but 3 and 5 failed to show anything in the window. I didn't quite follow #4 but gather that it may not be relevant to me any way. Next I will try to connect a phone physically to the cable going to the modem, but things don't look good for some weird reason.

If the modem died that would mean that while I was away last week:

HS3 went crazy with a corrupted database somewhere,
My router died,
The batteries on my keyboard died. Had no extras
Batteries on the lock went from 67% to 13% so presumable almost died. Uses the same batteries as the keyboard. :/
No it's looking like my CID modem went ta ta's up.

Is there any other possibility aside from the cable being bad or some other simple physical issue like that?

[S-F]

I dunno.

I unplugged the modem and plugged it back in. Then I uninstalled the driver and restarted the PC. Now everything works.

I've had a confusing few days with my high tech world here at home.

Thanks for the help. I'm back up and running.

Now to deal with the UltraLog errors I've been getting this week.