Toshiba Thrive

The Toshiba Thrive Android tablet went on sale just over a week ago, but early customers are already starting to notice a major with the company’s first tablet to run Google Android 3.1 Honeycomb. According to a thread at the Toshiba forums, a number of users are having trouble getting the tablet to resume from sleep.

In other words, if you let the tablet display turn off and then press the power button to turn the screen back on… nothing happens. In this situation the only fix appears to be holding down the power button until the device turns all the way so you can reboot. That process can take a couple of minutes. Part of the appeal of Android tablets is supposed to be their “always on” capabilities which allow you to start using the device within a second of tapping the power button.

Honestly, I haven’t really noticed this issue on the demo unit Toshiba sent me to review, but I haven’t had a chance to test the tablet extensively yet.

But the folks at PC World reached out to Toshiba and received a note acknowledging the issue and promising that a solution is in the works. Toshiba will push out a software update using the Toshiba Service Station app that comes preloaded on the tablet. There’s no word on when we can expect to see that update though.

Support Liliputing

Liliputing's primary sources of revenue are advertising and affiliate links (if you click the "Shop" button at the top of the page and buy something on Amazon, for example, we'll get a small commission).

But there are several ways you can support the site directly even if you're using an ad blocker* and hate online shopping.

Contribute to our Patreon campaign

or...

Contribute via PayPal

* If you are using an ad blocker like uBlock Origin and seeing a pop-up message at the bottom of the screen, we have a guide that may help you disable it.

3 replies on “Toshiba working on sleep/resume bug affecting the Thrive tablet”

  1. Had this problem after a long sleep.  Ended up having to take the battery out to do a hard reset, but I have since left it on longer sleep cycles without problems.  .  .  (The latest OS fix from last weekend was installed, so it does not appear to correct this problem.)

  2. Well OS’s are big complex beasties, and tiny incompatibilities can be introduced by even the smallest changes in components (sourcing something as simple as a screen from different vendors can sometimes introduce bugs that require driver updates), so this is…  hardly surprising?  Glad they got a fix for it already.  Bet there’s an Engineer slapping their forehead going ‘how did we miss this’.

    So been there recently.

Comments are closed.