Releasing a 2.x rom

[Guest chunga]

Just want to know how the things are going.

So what's keeping you to release a 2.x rom now that you have kernel?

Community showed respect to you and give you phones as gift for you to work on a 2.x ROM.

It's ok the themes and thank you for all your contribution. But I think the major interest it's a 2.x ROM.

Are you waiting for acer release the 2.x rom?

[Guest Angio]

Just want to know how the things are going.

So what's keeping you to release a 2.x rom now that you have kernel?

Community showed respect to you and give you phones as gift for you to work on a 2.x ROM.

It's ok the themes and thank you for all your contribution. But I think the major interest it's a 2.x ROM.

Are you waiting for acer release the 2.x rom?

????? Me.... or are you talking about the other devs ?????

Edited February 13, 2010 by Angio

[Guest bais]

I don't know why are people asking for the 2.X rom.

We'll have an official update , and if it tends to have lots of bugs then Acer will have to release the 2.X kernel source anyway.

It will probably take more time for the devs to release a fully working 2.1 release than for Acer to release an official one.

[Guest fantong]

????? Me.... or are you talking about the other devs ?????

I think it's to difficult to one developer to do all work as Acer should do.

3rd party devs only can hack , cut or add or modify limited things to make end user feel better.

[Guest behnaam]

I stated what the issues are with building AOSP for Liquid in a thread. So since some seems to have missed it here are the issues in simple language:

- Acer built their android built using prelinked libs, which means that the libs are located in specified places. AOSP disables this as default, and even if u enable it, u have to find where acer located different libs and how these are linked. Which requires deep reverse engineering of the already built code, so count it as a huge task that needs alot of knowledge in reverse engineering C code.

- So AOSP version 1.6, 2.0, 2.0.1, 2.1 wouldnt even boot even if we set up an correct vendor for it, due to that acer seems to load build in a different way onto the phone.

- Looking at acers kernel config showed that nexus has almost identical hardware platform and this mean that in theory it should load onto the liquid without issues, but as stated above this failed.

So what we devs can to for now (at least what im doing) is to wait for a eclair dump from Acer to work with.

To get rid of this confusion we have on this board, kernel source has nothing to do with the ability to build a correctly working AOSP 2.x build for Liquid or even porting one.

Hope this answers your questions Chunga, and believe me I know how some people might feel when not much progress is done on Liquid scene and only modified stock roms are released. But there isnt much u can do with what acer did with this device.

Edited February 13, 2010 by behnaam

[Guest maxisma]

I stated what the issues are with building AOSP for Liquid in a thread. So since some seems to have missed it here are the issues in simple language:

- Acer built their android built using prelinked libs, which means that the libs are located in specified places. AOSP disables this as default, and even if u enable it, u have to find where acer located different libs and how these are linked. Which requires deep reverse engineering of the already built code, so count it as a huge task that needs alot of knowledge in reverse engineering C code.

- So AOSP version 1.6, 2.0, 2.0.1, 2.1 wouldnt even boot even if we set up an correct vendor for it, due to that acer seems to load build in a different way onto the phone.

- Looking at acers kernel config showed that nexus has almost identical hardware platform and this mean that in theory it should load onto the liquid without issues, but as stated above this failed.

So what we devs can to for now (at least what im doing) is to wait for a eclair dump from Acer to work with.

To get rid of this confusion we have on this board, kernel source has nothing to do with the ability to build a correctly working AOSP 2.x build for Liquid or even porting one.

Hope this answers your questions Chunga, and believe me I know how some people might feel when not much progress is done on Liquid scene and only modified stock roms are released. But there isnt much u can do with what acer did with this device.

Exactly. Very well explained. This should be a sticky.

[Guest behnaam]

Exactly. Very well explained. This should be a sticky.

maxisma log in to gtalk, I have an theory to discuss :D

[Guest Scsiborg]

I don't know why are people asking for the 2.X rom.

We'll have an official update , and if it tends to have lots of bugs then Acer will have to release the 2.X kernel source anyway.

It will probably take more time for the devs to release a fully working 2.1 release than for Acer to release an official one.

What a load of of rubbish - look at the htc hero, thats still officially only supports 1.5! i know people who are running 2.1 - did they wait around for htc? no.

The only thing stopping us now is drivers - fact is the Acer donut device drivers dont work on eclair.

[Guest maxisma]

What a load of of rubbish - look at the htc hero, thats still officially only supports 1.5! i know people who are running 2.1 - did they wait around for htc? no.

The only thing stopping us now is drivers - fact is the Acer donut device drivers dont work on eclair.

1) They got drivers etc from leaked images

2) The Android source is designed for HTC & Motorola devices

[Guest Scsiborg]

1) They got drivers etc from leaked images

2) The Android source is designed for HTC & Motorola devices

So just what is stopping us then - we have people claiming to have 2.0 running with no drivers, no wifi etc. Your saying we have the drivers from leaked roms - so just what goes wrong when you put the two together?

[Guest Scsiborg]

Sorry i messread your reply - you make my point quite well - we dont have 2.x acer drivers

Edited February 13, 2010 by Scsiborg

[Guest g4rb4g3]

We don't have drivers, maxisma said they (htc hero guys!!!) got their drivers from a leak.

[Guest behnaam]

So just what is stopping us then - we have people claiming to have 2.0 running with no drivers, no wifi etc. Your saying we have the drivers from leaked roms - so just what goes wrong when you put the two together?

Put the word claiming in bold, cuz we dont have actual proof that 2.0 ran on the device, the screenshots might aswell come from a android emulator on th sdk with changed build prop running WVGA mode right?

And the second thing, if lets say somebody actually booted 2.0 onto the liquid, who would ever run a rom not including vital stuff as WiFi, radio, camera, 3d acceleration, accelerometer, bluetooth etc... would be pretty useless right?

[Guest chunga]

I got the point.

You said that you can't compile kernel and Disc0 put efforts on that and in a week did it.

If you don't have enough skills just don't promise things you can't achieve.

Maybe someone can RE drivers now and fix the linker, can't you sniff inside the code and symlink the libs?

[Guest todbld]

WOW this has to be the rudest thread ever, i find it funny that you guys are attacking the people that are putting in time and work on these devices to try and help all of us, they do not work for you, they are not employed by you, they owe you nothing, they simply have the same phone as you and are smarter than you and have know how in development so are lending there time and services. As far as the CLAIMS laid early in this forum i Believe maxima asked for donation for a device so he could develop for it his claim was that he developed for phones in the past and wanted to do it for this phone and made obscure quotes like lets get 2.x working like as a goal, not if you donate a few $$ to me i will get you 2.x you are so selfish and ignorant these guys have spent alot of time and effort trying to better this entire communities devices so i guess if you think you were owed something or were slighted than why are you here.

I for one appreciate the work done here as i do not have the hours upon hours of my life to go through code at the moment and appreciate that they offer to share there work and findins because they do have the time. Personally i think what ever donation was made was paid for alone in the rom leaks that we may not of had access to otherwise. Considering what was released by acer and what i saw in the kernel in my very limited time i had to look at it i think they have done great work, these men do not work for acer and do not have a "team of developers" that work on this for a living they have lives school jobs and much else so lets support there efforts rather than complain!!!

[Guest maxisma]

I got the point.

You said that you can't compile kernel and Disc0 put efforts on that and in a week did it.

If you don't have enough skills just don't promise things you can't achieve.

Maybe someone can RE drivers now and fix the linker, can't you sniff inside the code and symlink the libs?

First: I don't want to attack you, just want to clear some things.

I am able to compile a Kernel. But I wasn't able to fix the bugs Acer left in the source.

Disc0 did a great job.

I didn't promise everything. I said I will try to make 2.x for the Liquid. I asked for donations and didn't tell people to purchase something.

I already disassembled the binaries, but it was still a really low-leveled computerlanguage and I would need to see at least some sort of code so I could see the adresses for the libs and binaries in the Liquid's RAM.

Then I could compile the Android source with those adresses (prelinked).

It has nothing to do with symlinking libs.

Oh and I just returned from a class tour and I'm ill, though I'm already installing Ubuntu on my freshly formatted computer again.

Edited February 13, 2010 by maxisma

[Guest bais]

todbld: + OVER 9000 (obscure reference inside :D )

[Guest maxisma]

todbld: + OVER 9000 (obscure reference inside :D )

hm?

[Guest todbld]

hm?

i am confused as well did he mean in the kernel ?

[Guest Scsiborg]

WOW this has to be the rudest thread ever

Just to make something clear - im not being rude. The question was asked "why dont we have a working 2.0 rom yet?" - the answer is (in the main) that we dont have suitible drivers.

im not concerning myself with other peoples woes about none fruitful donations - these things take time, you arent buying a product. You need to cut them some slack.

[Guest chunga]

I don't care about the money spent in donations, but at least share the points you are limited. Expose in threads like disc0 did, he get tips from other devs and got progress. Don't limit it to a git, xmpp's please share

[Guest maxisma]

I don't care about the money spent in donations, but at least share the points you are limited. Expose in threads like disc0 did, he get tips from other devs and got progress. Don't limit it to a git, xmpp's please share

Well, I'm doing that. At least behnam and me are in constant contact. But at the moment we don't make a real progress.

Behnam just had a good idea and we are working on trying it out.

[Guest Piter1225]

Sorry i messread your reply - you make my point quite well - we dont have 2.x acer drivers

Well, if we go this way, we can say, that we - in theory - are able to build 1.6 AOSP.

But we can't (according to maxisma's posts from the past)

[Guest kylenk]

@scsiborg: you did come across pretty rude regardless of whether that was your intention.

[Guest three_pineapples]

this thread is a perfect example of why i can't be bothered reading this forum anymore. We have devs and non-devs (normal users) all being childish (not saying all devs or users are...just some).

It's just not worth my time reading. Goodbye modaco! maybe i'll revisit when i get a nexus one.

P.S.: My only gift to the community is here: http://wiki.xda-developers.com/index.php?p...AcerLiquidGuide