Android 2.2 - check this out .....

[Guest mkrogh]

http://www.androidpolice.com/2010/05/11/ex...out-450-faster/

BR.

MKrogh

[Guest Roton]

http://www.androidpolice.com/2010/05/11/ex...out-450-faster/

BR.

MKrogh

I really hope this is leaked. We might be having a 2.2 custom rom on our hero's before htc even release the official 2.1 lol.

[Guest]

I really hope my Hero turns into a Nexus One in the night.

[Guest Roton]

I really hope my Hero turns into a Nexus One in the night.

Yeah because android 2.2 will only be for the nexus one.

[Guest raf2k]

Yeah because android 2.2 will only be for the nexus one.

Google will first realese it for N1, then for Desire and maybe for other phones to.

[Guest]

Yeah because android 2.2 will only be for the nexus one.

Well, HTC won't make it for the phone I have and I expect any version that does appear won't run as well on my phone as it does on Nexus One.

For that reason, again, I'll be hoping that my phone turns into a Nexus One tonight.

[Guest prupert]

Actually, Google has stated they want to combat the current Android OS fragmentation, as it is impeding the growth of Android. The improvements you see speedwise in 2.2 over 2.1 are mostly down to the new JIT java virtual machine and not so much to do with the power of the Nexus One (which, based on the fact that the Evo 4G will now be offered instead of the Nexus One by some US carriers, is not the fastest Android phone any more). I thus wouldn't be surprised if Google push to see 2.2 on many phones (it has been shown on the G1, so thus there is no reason for it not to be on the Hero).

However, HTC will sell less phones if their older models can be updated to 2.2. Thus, it will be HTC putting the block on. So it will be up to the modders to give us 2.2 if HTC get their way.

[Guest pulser]

Actually, Google has stated they want to combat the current Android OS fragmentation, as it is impeding the growth of Android. The improvements you see speedwise in 2.2 over 2.1 are mostly down to the new JIT java virtual machine and not so much to do with the power of the Nexus One (which, based on the fact that the Evo 4G will now be offered instead of the Nexus One by some US carriers, is not the fastest Android phone any more). I thus wouldn't be surprised if Google push to see 2.2 on many phones (it has been shown on the G1, so thus there is no reason for it not to be on the Hero).

However, HTC will sell less phones if their older models can be updated to 2.2. Thus, it will be HTC putting the block on. So it will be up to the modders to give us 2.2 if HTC get their way.

Nathan from VillainROM is actively seeking out a 2.2 leak, and he'll release one if he can get his hands on one.

[Guest]

it has been shown on the G1, so thus there is no reason for it not to be on the Hero

There is a reason. HTC is too lazy. Yet there's a small chance they cancel the 2.1 update and say "hey folks, we're sorry to disappoint you, but to deliver the best experience for your hero, we decided to skip 2.1 and make a 2.2 update instead."

I see this scheme going on like forever.

[Guest Roton]

There is a reason. HTC is too lazy. Yet there's a small chance they cancel the 2.1 update and say "hey folks, we're sorry to disappoint you, but to deliver the best experience for your hero, we decided to skip 2.1 and make a 2.2 update instead."

I see this scheme going on like forever.

I couldn't care less about HTC tbh. The only HTC firmware I used was the one which came with my Hero; it was slow and buggy. I've moved through various versions of Modaco's custom rom and now to some 2.1 leaks. They all performed near perfectly. I would even be happy to run a vanilla 2.2 rom, HTC can just stick to making phones... leave the firmware to people who understand how to meet deadlines and exceed expectation.

Edited May 14, 2010 by Roton

[Guest]

I couldn't care less about HTC tbh. The only HTC firmware I used was the one which came with my Hero; it was slow and buggy. I've moved through various versions of Modaco's custom rom and now to some 2.1 leaks. They all performed near perfectly. I would even be happy to run a vanilla 2.2 rom, HTC can just stick to making phones... leave the firmware to people who understand how to meet deadlines and exceed expectation.

All the MCR's are built from HTC releases though, aren't they?

[Guest venturerider]

Funny, isn't it. People complain that HTC can't do anything right, yet the cooks are all waiting for HTC to release their stuff.

[Guest Roton]

All the MCR's are built from HTC releases though, aren't they?

I don't know, I thought the source was universal? apart from the senseui, even if they are, the 2.1's aren't and I also like the vanilla releases (which again are nothing to do with htc).

[Guest zorm]

I don't know, I thought the source was universal? apart from the senseui, even if they are, the 2.1's aren't and I also like the vanilla releases (which again are nothing to do with htc).

Wrong. Each device requires drivers which are hardware specific & act as a kernel interface between the hardware & Android. These are either produced by the handset manufacturer or, aiui, sometimes by the relevant chipset manufacturer. When Android changes version, Google often also update the Linux kernel. This mandates driver updates. The source code to the drivers is invariably closed, so updates to Android rely on the handset manufacturers updating drivers themselves. Virtually all the bugs in recent cooked 2.1 ROMs are down to a lack of fully functioning drivers.

When there is no offical upgrade, the only alternative is for creative devs to either patch drivers for similar hardware & the new kernel to work with their target hardware, or to patch drivers for the old kernel to work with the new kernel. However talented the dev, without source code or chipset manufacturer docs, this involves a lot of work & much experimentation/guesswork. It is a slow process with unreliable results.

[Guest mkrogh]

Wrong. Each device requires drivers which are hardware specific & act as a kernel interface between the hardware & Android. These are either produced by the handset manufacturer or, aiui, sometimes by the relevant chipset manufacturer. When Android changes version, Google often also update the Linux kernel. This mandates driver updates. The source code to the drivers is invariably closed, so updates to Android rely on the handset manufacturers updating drivers themselves. Virtually all the bugs in recent cooked 2.1 ROMs are down to a lack of fully functioning drivers.

When there is no offical upgrade, the only alternative is for creative devs to either patch drivers for similar hardware & the new kernel to work with their target hardware, or to patch drivers for the old kernel to work with the new kernel. However talented the dev, without source code or chipset manufacturer docs, this involves a lot of work & much experimentation/guesswork. It is a slow process with unreliable results.

Haleluja brother :)

BR.

MKrogh

[Guest shokka9]

Funny, isn't it. People complain that HTC can't do anything right, yet the cooks are all waiting for HTC to release their stuff.

Some cooks wait for authentic ingredients before adding theirs flavours, to make the perfect blend of meal.

Unfortunately many of them are not farmers and dont own big fields to grow all the crops and yield the resources.

:)

[Guest Roton]

*coughs*