RIP, Nextbit Robin: latest software update destroys our unit
UPDATE: Nextbit has gotten back to us, ensuring us that the issue should be isolated to our unit only. Apparently, being a media review unit, it's been running a version of the software that's different from the one on retail units.
Funny how fate likes to play its sinister little tricks on us. One minute your phone receives a software update meant to improve power management — always a cause for celebration — the other it overheats and leaves this world for good. Officially joining the clouds today is the so-called cloud phone, the Nextbit Robin. In what has been a most unfortunate closure to our otherwise happy coexistence, our Robin unit here at the PhoneArena offices suffered a critical overheat issue today after receiving the latest software update from Nextbit.
The update, which Nextbit promised last month and succeeded in delivering on time (admittedly not in the best way possible), is supposed to improve the camera, speakers, and overall power management, leading to better battery life and performance. It's a big, 450 MB piece of software which many early adopters of the Robin have been looking forward to. In our review, I noted that the phone tends to heat up quite a bit during even some mundane tasks like web browsing, so obviously there was a problem with how it handled load, which Nextbit was willing to address. Unfortunately, soon after downloading the update, the Robin restarted and never booted up again. After an unsuccessful attempt at powering it up, a faint smell of burning electronics appeared, followed by a burning sensation on my fingers, which were holding the phone.
For a moment there, I thought the Robin may combust into flames, but the plastic shell — which I do find inspiringly pretty — managed to withstand the heat and retain its entirety. Only a slight portion of the bottom bezel was later found out to have warped just a bit from the heat. Nevertheless, we had our fire-extinguisher at the ready throughout the day.
I hope this is just an isolated issue with our unit, but just in case, you might want to hold off running the update procedure on your Robins for the time being.