Difficult to bring custom Froyo/Gingerbread on Liquid? Lets know why

[Guest mmick]

I opened this topic because I don´t know why Gingerbread/Froyo drivers on Liquid are so difficult to build, therefor the question for our experts. A friend of mine bought an Orange Boston (in this case "Optimus Boston", the portuguese version) and despite the original Android was 1.6 (like Liquid A1) it grew *very* fast to Android 2.1, 2.2 and now it also sports Gingerbread!!!

More info (about Optimus Boston Gingerbread) here: Optimus Boston Gingerbread

What are my questions? As of now a much inferior device with a hardware much different from Nexus S has unofficially Gingerbread 2.3.1 + OC up to 1.2Ghz (original speed 600Mhz)...

1) Why a so much different device from Nexus S already advanced so quickly?

2) Can they have access to code that Liquid ROM coders don´t?

3) Can we use that kind of code to make the port for Liquid faster?

4) AFAIK someone tweaked the Orange Boston´s SoC voltage to achieve a cool 1.2/1.3Ghz

5) AFAIK they brought the SoC speed down to 22Mhz on idle conditions to improve battery

6) AFAIK they decreased the SoC´s voltage and increase SoC speed on intensive tasks (Wifi, 3D, 3G internet)

7) Can this be done on Liquid´s Snapdragon? Can this be done on a Liquid ROM?

Cheers and kudos for all ROM coders!

Edited January 5, 2011 by mmick

[Guest koudelka]

I opened this topic because I don´t know why Gingerbread/Froyo drivers on Liquid are so difficult to build, therefor the question for our experts. A friend of mine bought an Orange Boston (in this case "Optimus Boston", the portuguese version) and despite the original Android was 1.6 (like Liquid A1) it grew *very* fast to Android 2.1, 2.2 and now it also sports Gingerbread!!!

More info (about Optimus Boston Gingerbread) here: Optimus Boston Gingerbread

What are my questions? As of now a much inferior device with a hardware much different from Nexus S has unofficially Gingerbread 2.3.1 + OC up to 1.2Ghz (original speed 600Mhz)...

1) Why a so much different device from Nexus S already advanced so quickly?

2) Can they have access to code that Liquid ROM coders don´t?

3) Can we use that kind of code to make the port for Liquid faster?

4) AFAIK someone tweaked the Orange Boston´s SoC voltage to achieve a cool 1.2/1.3Ghz

5) AFAIK they brought the SoC speed down to 22Mhz on idle conditions to improve battery

6) AFAIK they decreased the SoC´s voltage and increase SoC speed on intensive tasks (Wifi, 3D, 3G internet)

7) Can this be done on Liquid´s Snapdragon? Can this be done on a Liquid ROM?

Cheers and kudos for all ROM coders!

optimus boston is a device called z71 and there are actually many phones with the same hardware. I belive they have better kernel sources than we have and also they might have more developers. Their device tree is well worked out and they can build alot of their binaries from source. https://github.com/CyanogenMod/android_devi...d/device_z71.mk

we use same libcamera as the z71 for our liquid. Also acer use different prelinking that can make things a bit more complicated.

Mostly I think we just dont have enough developers.

[Guest fear_factory84]

I think that mmick is too negative..

Acer liquid community is great, the number of custom roms is high, and also the quality.

Gingerbread is being ported, but it's alpha quality, but it's still immature also on nexus one!

The only thing that we can complain are acer kernel source releases, that are not in sync with binary releases, and (probably) have something missing.

But, thanks to the efforts of our devs (I don't write names because I want to mean all..), we have a custom kernel with full hw support working on froyo (see this great post by koudelka http://android.modaco.com/content/acer-liq...or-teacher/#)...

Regards