Help Message dated Jun-1 1970. Help.

[specificocean]

Going through my message list on my Lava A72, I found this really odd message, which shows that I sent the word "test" to a number, back in June 1, 1970. Why on earth.

I suspect it's a virus. Please help. Thanks.

 

[Mikestony]

Hello!
Nah, I don't believe it's a "virus"
It has to do with Android's Epoch time and it could just be a glitch

Edit: I don't even know what link to provide to explain it in layman's terms, sorry.
Perhaps someone else can elaborate on that.

 

[specificocean]

Hello!
Nah, I don't believe it's a "virus"
It has to do with Android's Epoch time and it could just be a glitch

Edit: I don't even know what link to provide to explain it in layman's terms, sorry.
Perhaps someone else can elaborate on that.

Hello!
Nah, I don't believe it's a "virus"
It has to do with Android's Epoch time and it could just be a glitch

Edit: I don't even know what link to provide to explain it in layman's terms, sorry.
Perhaps someone else can elaborate on that.

Thanks, but still think there's another reason...

 

[Mikestony]

Thanks, but still think there's another reason...

Indeed that is odd!
Do you use the stock messaging app? Based on the messages sent before and after that one, when do you think that message was sent?

 

[svim]

... back in June 1, 1970. Why on earth.
I suspect it's a virus. Please help. Thanks.

(Note that your initial query states 'June' but your screenshot shows January)

I doubt a message dated 'Jan 1, 1970' is a virus issue, that specific date is just too notable from fundamental programming sense. It would be just too coincidental. That date is tied to Unix Epoch time, the date that's been not-s0-arbitraritly set as 'zero'.
http://www.williammalone.com/articles/epoch_time/
https://en.wikipedia.org/wiki/Unix_time
In a loose correlation, with older PCs, when the CMOS battery would die that would often return the BIOS back to its firmware default settings, including the hardware clock chip being reset to January 1, 1970. At startup the operating system would show that incorrect date as current, at least until it updated itself to an online time server. Until the OS corrected itself, if you created a document and saved it, its creation date would reflect what would be the current date on that PC, Jan. 1, 1970.
So getting back to your allegedly four decade+ old message, I'm going with @Mikestony on this. Sounds like a glitch where the time stamp just didn't get applied correctly. Don't forget that Android does have tenuous link to Unix, it runs a Linux kernel. If you start seeing a number of other messages and documents with that epoch date, then that should be something to worry about. Again not necessarily a 'virus' issue but probably a hardware/Android matter.

 

[specificocean]

(Note that your initial query states 'June' but your screenshot shows January)

I doubt a message dated 'Jan 1, 1970' is a virus issue, that specific date is just too notable from fundamental programming sense. It would be just too coincidental. That date is tied to Unix Epoch time, the date that's been not-s0-arbitraritly set as 'zero'.
http://www.williammalone.com/articles/epoch_time/
https://en.wikipedia.org/wiki/Unix_time
In a loose correlation, with older PCs, when the CMOS battery would die that would often return the BIOS back to its firmware default settings, including the hardware clock chip being reset to January 1, 1970. At startup the operating system would show that incorrect date as current, at least until it updated itself to an online time server. Until the OS corrected itself, if you created a document and saved it, its creation date would reflect what would be the current date on that PC, Jan. 1, 1970.
So getting back to your allegedly four decade+ old message, I'm going with @Mikestony on this. Sounds like a glitch where the time stamp just didn't get applied correctly. Don't forget that Android does have tenuous link to Unix, it runs a Linux kernel. If you start seeing a number of other messages and documents with that epoch date, then that should be something to worry about. Again not necessarily a 'virus' issue but probably a hardware/Android matter.

Thanks.