My Google Pixel C tablet is nearing the end of its life.

One of the facts which I did blog about was that, around April of 2017, I had purchased a Google Pixel C Tablet, which, in the meantime, had an O/S Upgrade to Android 8.1.0. That tablet is nearing the end of its life, and it’s barely 3 years old.

Firstly, it has not been receiving any system upgrades since 2019.

Secondly, as of a few months ago, it has started the behaviour of ‘spontaneously rebooting’ every few weeks, even though all I’ve been doing with it was, to keep it idling.

Some people tend to dismiss this behaviour of certain Android devices, just spontaneously to reboot, as if it was insignificant. But to the contrary, I tend to look at this as a crash each time, just as if a PC running Windows had suddenly received a Blue Screen. It can be caused by several things, but in this case I’m afraid, it might be a hardware problem, especially, since I have not been installing much software on it, nor receiving System Upgrades, at least, in the recent months.

Therefore, I am looking for a replacement, Android, Tablet.

BTW, The dedicated keyboard that came with this tablet has continued to work, to this day. I guess that I was lucky, not to receive a keyboard with a degraded built-in battery.

Dirk

 

Pixel C Crash Yesterday Night

Yesterday evening, my new Pixel C Tablet did something for the first time, which was ominous. Its screen just went dark, and then started to display the logo, which it displays during a restart. It followed through with a successful restart.

Some people mistakenly think that this behavior is a reboot. If we were to call it that, then this behavior would need to be called a Hard Boot – as opposed to a Soft Boot, which happens when the user shuts the tablet down from the software-side, in telling it to reboot. In fact, a Hard Boot would be happening when the user uses the power-button to force a Hard Boot, and would have an explanation in that.

In reality, what the tablet did was a spontaneous reset. This type of event is also a File System Event, as the File System was never unmounted. Hence, the tablet also needed to repair its file system when it booted anew.

But, there are certain safety-factors built into how any serious O/S works, and built into how any file system works. So in most cases, the repair to the file system succeeds.

The fact that this has happened to a brand-new tablet, causes me to question how (un)stable it might really be. I’ve only had this tablet for a few short months now.

One of the features of how this happens, which is even less reassuring, is that after the reset, there is nothing displayed in the user interface, which betrays the fact that the reset happened. What this means is that in theory, this could be happening every night as I sleep, even while the tablet is charging, because by the next morning, there would be nothing displayed, to betray the fact that it has happened.

It just happens to have taken place once now, while I was sitting in front of it.

Dirk

(Edit : )

I should add, that this tablet is running the May 5 patch of Android 7.1.2 .