Will The G1 Continue To Get One?
One of the significant disadvantages of being an early adopter of any new technology is what comes after it, specifically, the improvements that every technology experiences over time. Such appears to be the case for those who rushed to pick up the G1 — the first Android phone on the market — as questions have begun to pop up over whether the device is in line to see its last update.
Like any device, the G1 has certain physical limitations — only so much stuff can fit in the case, and among the stuff being stuffed in is its memory. Apparently, according to one of Google's developers, not enough memory was stuffed when the stuffing was good, and now G1 owners may find themselves short on updates.
Posting via Twitter — the mass-communication tool of choice these days, it would seem — Google's Jean-Baptiste Queru announced on Friday that the G1 is running out of space. "As much as I'm hoping that it'll be possible to somehow continue updating the G1, I can't promise anything." Queru ought to know, considering that he's one of the guys working on it, and apparently the team knew going in that space would be shrinking. "We knew that internal flash space was going to be very tight on the G1 and we kept the system partition tight on purpose," he wrote later, in response to ideas from fellow Twitterites on how to proceed.
Google, for its part, apparently isn't commenting, but T-Mobile apparently was. A statement from the company reportedly proclaimed: "We plan to continue working with Google to introduce future software updates to the T-Mobile G1. Reports to the contrary are inaccurate." That raises the question — and users are most certainly already raising it — of whether the company is denying outright that a problem exists, if there is a solution in the works that nobody is willing to talk about, or if a bit of corporate doublespeak is underway. The suggestion has already been made that "future software updates" may refer to security and bugfix updates, but not feature upgrades.
Those interested in Queru's comments might wish to have a look through his Twitter stream, though his most recent tweet, as of this writing, suggests that he's said his piece. "At this point I can't comment any further on this issue, sorry."
Justin Ryan is News Editor for LinuxJournal.com.
Submit a tip: Email IRC
Justin Ryan is a Contributing Editor for Linux Journal.
Getting Started with DevOps - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report
August 27, 2015
12:00 PM CDT
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code. It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
Free to Linux Journal readers.Register Now!
- Django Models and Migrations
- Hacking a Safe with Bash
- Secure Server Deployments in Hostile Territory, Part II
- Home Automation with Raspberry Pi
- The Controversy Behind Canonical's Intellectual Property Policy
- Huge Package Overhaul for Debian and Ubuntu
- Shashlik - a Tasty New Android Simulator
- Embed Linux in Monitoring and Control Systems
- KDE Reveals Plasma Mobile
- diff -u: What's New in Kernel Development