NVIDIA Recalls Shield Tablets Over Heat Risk 27
An anonymous reader writes: NVIDIA has issued a recall for 88,000 units of its 8-inch Shield tablet sold in the past year. Predictably, it's because of the battery. There have been reports of overheating, including two reports that the tablet got so hot it damaged the floor it was resting on. Oddly, the company is requiring anyone returning the tablet to update its OS to the latest release.
Nothing "odd" about the required update (Score:5, Informative)
The required update isn't "odd" because it facilitates two things:
First, it checks whether you're a owner of a affected device or not.
Second, if this is indeed the case it then facilitates getting the RMA number in conjunction with the website.
Basically, you go into "System" on your device, check the battery, it tells you that you're affected. You then open the website, enter the serial number of the device. You get an RMA number, and enter that into the device. You then get another number (some kind of receipt, probably) and enter that into the website, along with your contact information.
Sounds more complicated than it is and you're done in about 4 minutes, depending on how fast you type.
Re: (Score:3)
If you have the old firmware you will not see the battery type you have. It is not until you update your firmware that you will see that on the about screen.
Re: (Score:2)
But you can also use the serial number and that one is stenciled on the case.
Re: (Score:2)
That's pretty poor. Why doesn't the device read it's own serial#?
Probably a liability thing in case someone is now afraid to use their device fearing it will burn their house down if they even turn it on.
Nice garden path sentence (Score:2)
From the title, I was wondering how NVIDIA recalls were shielding tablets over a heat risk. You would expect the opposite - a recall should, well, recall tablets, not shield them.
Re: (Score:3)
From the title, I was wondering how NVIDIA recalls were shielding tablets over a heat risk. You would expect the opposite - a recall should, well, recall tablets, not shield them.
Never heard of heat shields? ;-)
Re: (Score:2)
I was expecting some sort of Marvel tie-in myself.
Hey, we have the ASUS Transformer devices.
Re: (Score:2)
Have seen this popping in everywhere, still don't get it.
Re: (Score:2)
/. administrators! Can't you block this crap from spewing across almost every article? Whoever is posting this stuff is a douche nozzle.
Re: (Score:3)
MOOOOOO! Is the sound of the universe telling you to stop browsing comments at -1.
Modders Go MOOOOOO! (Score:2)
MOOOOOO! Is the sound of the universe telling you to stop browsing comments at -1.
You need to browsing at +3 or higher to escape this nonsense. The sound your hear may be Slashdot circling around the drain.
Re: (Score:1)
Slashdot has only ever removed one post and that was on order of the Scientologists. Are you a Scientologist? MOOOOOOOOO say the Scientologists! YOU SCIENTOLOGIST!
Update required (Score:2, Informative)
The update is actually required so that you can get your battery model number. Without the update, the "Battery" field that they tell you to check isn't present.
NVIDIA Support (Score:1)
Re: (Score:2)
Yeah they're great with support. Unless you happen to have a bump gated 6000 series gpu in a laptop and they decide not to provide your OEM with the resources to fix it.
8800 desktop series cards as well (Score:2)
Too late for me (Score:3)
I just sent it back to the vendor (under warranty) because the latest OS update caused the speakers to melt.
While browsing the net I noticed the smell of burnt plastic, and quickly noticed the edges (where the speakers are) was too hot to touch. Turned the thing off but they were cooked.
Then I found I wasn't alone... https://forums.geforce.com/default/topic/834884/shield-tablet/speakers-damaged-after-3-0-update/ [geforce.com]
Apparently somehow the speakers got fed DC current while doing nothing in particular. Impressive if you ask me.
Re: (Score:2)
Apparently somehow the speakers got fed DC current while doing nothing in particular. Impressive if you ask me.
I would guess a software bug that wrote inappropriate values to the DAC (possiblly straight binary vs 2's complement confusion) combined with an idiot hardware designer DC coupling the audio path.
When do we get the discounted returns? (Score:1)