Linux Format forums

[AndyBaxman]

Android is at a rather crucial point in its life. One that could make or break it.

Currently there are a number of devices out there, all running different versions of Android (1.5, 1.6, 2.0, 2.1 and 2.2 (aka froyo)).

A number of earlier devices either won't be (officially) updated to the newest version, or the manufacturer and/or service provider won't commit themselves one way or the other (e.g Vodafone's stance on the HTC Magic).

Being locked into a 2 year contract with a service provider who won't ensure your phone is able to run the latest apps is intensely irritating, particularly compared with the iPhone where all except owners of the original 2G iPhone know they will get iOS 4 when it is released.

It should be noted that this isn't because the phones won't support the update. There are a number of unofficial (e.g Cyanogen) 2.x ROMS for the early G1s and Magics which are reported to work very well.

It appears to be more a case of a "We've got your money, so f*** off" attitude from the likes of Vodafone.

This isn't a problem with the OS itself. Its a problem with the attitude of the manufacturers and service providers who are more interested in selling new phones than supporting old ones.

The trouble is, if you piss your customer off halfway through a 24 month contract by refusing to keep his device up to date, then he is going to think very carefully about buying another Android device (or staying with the same service provider / manufacturer) when his contract expires.
_________________
Bomb #20: "Let there be light"

[Rhakios]

I don't know that this problem is unique to Android, when I had a Symbian phone, T-mobile's updates did not include all the features of the original versions.

Of course, in the case of the iPhone, Apple are keeping complete control of the firmware, while in the case of Android, Google are not. That's the inevitable result of it being Open Source, I suppose.
I suppose it's also an advantage of the iPhone that updating the OS is a user-controlled process through iTunes, which encompasses the important functions of back up and restore. Installing an unofficial image on an Android phone (I've had a look at the idea of rooting mine) looks like somewhat of a dark art, and you don't want to brick several hundred quids worth of phone with one mistake.

Edit: I've split this topic as it has got rather far from the original "oh look here's some Android hardware" subject in one short leap.
_________________
Bye, Rhakios

[AndyBaxman]

Rooted my Magic with CyanogenMod (4.2.15). Worked a treat and breathed new life into the thing.

Quite straightforward to do. I found this guide useful.

It all went exactly as described in the guide, apart from having to do an adb push of the recovery image (as described in the comments).

The bottom line with rooting is that its no different to installing an OS on any other computer. If you can install Linux (or dual boot) then you can root your Android.

This is a 1.6 build. Probably go with the 5.0.8 build next, which is Android 2.1 (Eclair).
_________________
Bomb #20: "Let there be light"

[Rhakios]

[AndyBaxman]

[Rhakios]

Phones are very much devices intended for the common user, so seein the process of upgrading as an admin's task isn't going to help Android in the world at large.
Really, we're back where we started, that the support given by vendors and phone companies is inadequate.
_________________
Bye, Rhakios

[M0PHP]

It's the desire of the phone networks to keep control which seems to be the major factor here - and I don't see why this should be the case (from a consumer point of view).

Non-smartphones don't have this issue, do they? For example, Nokia release firmware for their phones themselves and users can upgrade when they want or need to. Why is the process different for Android?

Perhaps some of the blame lies at Google's doorstep here. The main difference is that Google just produce the operating system - they can't control it once it's out of their hands - and why should they care? It is then down to the hardware manufacturers to integrate this and ship it. So who's responsibility is it now to keep customers up to date?

Then there are the motives of the network provider. Android 2.2 has a native tethering and portable wifi hotspot feature, which works great. I can imagine that this feature is something which networks will want to disable if they are responsible for pushing out updates.

I consider myself lucky in that I bought the Google Nexus One outright, and managed to get a cheap contract on a short term. I'd much rather have this situation than be locked down tight with an iPhone.
_________________

[nelz]

[AndyBaxman]

Well, Having rooted my Magic earlier in the week, I have just updated to Android 2.1 (Cyanogen 5.0.. It took about 10 minutes and consisted of copying the new image to the SD card, booting into "Recovery" (installed during the rooting process) and accessed by holding "Home" while powering up), and choosing to install a new image.

Actually much simpler than installing a PC OS.
_________________
Bomb #20: "Let there be light"

[Rhakios]

How about restoring all your settings?
_________________
Bye, Rhakios

[AndyBaxman]

[guy]

I guess part of the issue is simple support logistics.

If say ten models and various OS upgrades have been released over time, that'd probably build up to something like 40 or 50 combinations in circulation. Then there will be the rooted ones with non-standard OS, either by the user or by malware of which the user is oblivious.

For any kind of support contract, it's all a nightmare. Far easier to say that model X comes with OS version Y and lock it down to reduce the risk of rooting.
_________________
Cheers,
Guy
The eternal noob

[LeeNukes]

Sounds like you're running a 1.6 Android phone Andy and you're bitter you won't be getting the 2.2 update.
_________________
Join GiffGaff and get £5 free credit

[AndyBaxman]

[towy71]