2.0 on G1 why not the pulse?

[Guest GB-UK]

Just found this

which has android 2.0 on a G1. If they can get it running on a G1 then surely this will be no problem for the pulse.

[Guest jonathonf]

It's no problem at all. After all, Google partnered with HTC for Android phones so all the tools are geared towards HTC phones. HTC devices also have hardware drivers that work with kernel version 2.6.29 which is needed for Android 2.0. Oh, that and the G1 is the *Google Dev Phone* and is what people working at Google *actually use* (well, up when to the Nexus One was released).

After all, the HTC Dream/G1 is exactly the same hardware as the Huawei U8220. It's got to just work, hasn't it?

/sarcasm overload.

Seriously, though, have you tried to get it working?I've spent a good few hours just trying to get a build environment that works - this s*** is non-trivial and I'm nowhere near a novice.

[Guest Bakes]

Just found this

which has android 2.0 on a G1. If they can get it running on a G1 then surely this will be no problem for the pulse.

Most HTC phones share a large amount of their hardware for simplicity. This means that with work, Hero roms can run on the G1, G1 roms on the Hero, etc.

That's why it won't work.

Real-world comparison:

Golf - G1

Golf GTI - Hero

various other golfs - G2, etc

Skoda Fabia - Pulse

Whilst the majority of components might be similar, you wouldn't be able to just swap them between them.

[Guest xangma]

I have however, had a 1.6 ROM from the G1 working on the pulse. It did require a lot of work, but unfortunately hope was lost as was the work. I am currently working on a 2.6.29 kernel for the pulse and to say the least, it isn't working well. BUT, if you would like to help out (starting with) focusing your attention on what we can do instead of what we cannot, we may get a lot further.

[Guest Jan M]

Most HTC phones share a large amount of their hardware for simplicity. This means that with work, Hero roms can run on the G1, G1 roms on the Hero, etc.

That's why it won't work.

Real-world comparison:

Golf - G1

Golf GTI - Hero

various other golfs - G2, etc

Skoda Fabia - Pulse

Whilst the majority of components might be similar, you wouldn't be able to just swap them between them.

Actually you would be able to swap a lot of the components (ex. same engines) between VW/Skoda/Audi/Seat because they're one company =]

[Guest Bakes]

Actually you would be able to swap a lot of the components (ex. same engines) between VW/Skoda/Audi/Seat because they're one company =]

Well yes, a lot of the components are interchangeable that was my point, but even though they share an engine, and only have slightly modified suspension, you probably wouldn't be able to use the same onboard computer software because it would be written quite differently, and you wouldn't be able to just plug in the gear stick or the steering wheel from a golf into a skoda fabia.

[Guest de_shepherd]

Well yes, a lot of the components are interchangeable that was my point, but even though they share an engine, and only have slightly modified suspension, you probably wouldn't be able to use the same onboard computer software because it would be written quite differently, and you wouldn't be able to just plug in the gear stick or the steering wheel from a golf into a skoda fabia.

... maybe if you tried a Fabia and a Polo you'd have more luck!

[Guest Bakes]

... maybe if you tried a Fabia and a Polo you'd have more luck!

Maybe, but now we're just getting off topic :D

To answer the OP, it's because it's tricky to do in the first place, and the G1 is the android phone that has the most devs working on it (it's the Android Developer Phone after all) so has more people working on getting different roms working.