I have hope that Acer would release a working kernel configuration, but until then lets play for safe and try to do something ourselves..
This is what I checked that works:
Make/receive calls sms/mms Touchscreen Cpu Scalling Bluetooth turns on (think it works, didn't test) USB storage/debug Battery (temporary fix, not safe) reboot, via some program (because the same fix of battery) Modem 1GHz cpu can be done but it makes the phone be less smoother (strange, hun..!?) the buttons below the screen system sound (didn't test music, but supose it will work too) acceleromter digital compass sd card light/proximity sensor Hardware buttons camera vibrator 3d accel GPS (couldn't test properly because I was inside home, but works)
now the bad part, what don't works
Wifi Multitouch think could be achieved (everything else not in working list)
There is lots of work to be done, mostly because some things work for now because of temporary fixes, witch means, highly unstable!
Some results from neocore test:
1Ghz 34.7FPS (in parts of the test the cpu don't even goes to full load [1Ghz], really nice snapdragon )
Kernel repo added and kernel being uploaded
Now we can all share our work..
create an account and send it to me so you can upload your changes
Before start building do:
make mrproper cp acerconfig .config
and you are ready to build
Ok, so I flashed my liquid with the new 2.000.16 EMA that behnaam posted and found that acer have modified the bootloader.
The result is that in some cases liquidmkbootimg don't creates compatible boot images.
I don't yet fully understand how new liquid bootloader works, so I compilled a new liquidmkbootimg that can deploy the ramdisk in 3 different modes, see "liquidmkbootimg --help".
I'll explain how it works:
--deploy 0 -> Deploys the ramdisk inside the boot.img normally.
--deploy 1 -> Adds an extra pagesize before ramdisk.
--deploy 2 -> This is only in last resource. The ramdisk in boot.img of 2.000.16 starts at adress 0x219000, and this could be a predefined adress where liquid's bootloader searches for ramdisk.
--deploy 0 can be omitted, as is the default way. And --deploy 1 worked for me sometimes, so if your self compiled kernel don't works in default creation mode, test at least with mode 1.
Search for the new linux binary here.
Bootloader and recovery:
In case you flashed a bad boot.img with 2.000.16 ROM you will get yourself in a situation where you will think you f**ked up once and for all your phone because you can't get into bootloader with camera + power anymore. So, relax, its time to do some magic and make the bootloader appear on your screen..
1. turn off your phone (and unplug usb if plugged)
2. press camera + volume up and then without releasing this two buttons hit power and the phone will vibrate two times. Release all buttons.
3. take the battery out and put it back (don't touch any button on the phone)
4. connect the usb to your computer and you will the acer logo and then bootloader will pop up.
5. Say thanks to acer for making it so complicated (:
or just do "Camera + Back + Power". Thanks CedricGatay (;
Recovery is a bit more easy: (only usefull for who flashed Lickons recovery)
1. turn off your phone
2. hit camera + volume down and without releasing them hit power button and the phone will vibrate two times. Release.
3. Just hit the power button and wait for it to boot into recovery.
Does someone want busybox and dropbear?? I ask this because I had my owns working in the last 1.008 and now I need to reinstall everything in new ROM and remembered to ask others..
Edited by disc0, 08 February 2010 - 05:23 AM.