Courtesy Source

What are the implications? Well, I don’t think we’ll hear Google complaining. The Android OS is the company’s attempt to make its mobile presence more significant, and Google is traditionally about letting people do what they want with what they have (Google Voice vs. Apple, anyone?).

We will hear complaints from T-Mobile, as this hack potentially gives them less control over its subscribers, if any will remain at all. This will probably lead to other operators to rethink any plans to subsidize Android OS devices, as US operators love dictating what their customers can and can’t do.

In any case, click on the source for full instructions on rooting your Android device—and what precautions to take. A video summarizing that is below:

Source

Post from: The Gadget Blog

At the same time however, Ed’s discussion of the issue also shows the advantages of open source, and why being able to share info quickly over the internet is a great thing:

Because Android is open source, the problem was quickly tracked down by users to a couple lines in the system file init.rc. My guess is that this was accidentally left in during device debugging. Thankfully the fix is trivial; you can probably even make it yourself if you’re so inclined (just comment out the offending lines described in the reports above and reboot).

Here’s a workaround I just discovered: Open the keyboard and type these 5 keystrokes: -c-a-t-. That will cause the phantom shell to not listen to commands any more, at least until the next reboot. [italics mine]

Let’s go over that again, shall we? First, Ed highlights the open-source nature of Google’s Android OS, facilitating the discovery of the problem’s source by users. At the same time, through his own blog, Ed quickly shares his own solution to the problem. Now, what more could you ask for?

By the way, a fix for this is part of RC30. So any (legit) G1 users out there, feel free to update as soon as possible.

Post from: The Gadget Blog