Continuing on from gh123man's Open ICS thread, we extended the scope of the project to cover the A100 & A200 devices too.
For the last month we've been quietly working on this & the wheels are now in motion to get the devices merged into CyanogenMods source.
It should only be a matter of time till the nightlies start rolling.
Merge status: Done
If you wanted to compile for yourself, follow one of the many guides on xda to get your machine set up & the CyanogenMod source downloaded.
Following instructions are for the a500, substitute a100 or a200 as needed
Code:
. build/envsetup.sh
lunch cm_a500-userdebug
Wait for the device folders to be downloaded.
Connect your device via adb.
Run extract-files.sh in the device/acer/a500 folder
Code:
brunch cm_a500-userdebug
wait for the compile to finish (can take a while), flash new rom...
Please hit the thanks button on some of their posts too, this has been a team effort.
Once we're official, threads will be started for each of the devices in their respective forums, in the meantime it'd be good to keep discussion here so it's a little easier for us to track.
Not working:
Known bugs:
Wifi? haven't had a report of trouble in a long time... tentatively saying this is no longer an issue
Reporting bugs
Please please please read the following:
If you have a bug, we need a bit more info than "such & such isn't working"
Things to check before reporting a bug
Did you wipe before flashing the build?
If no, nandroid, wipe & re-flash...
Check to see if the bug still exists.
Did you restore settings/data using Ti backup or similar?
If yes, nandroid, wipe, re-flash & don't restore your data...
Check to see if the bug still exists.
If you've done the above, & the bug is still there, we need some debugging info!
logcat output is usually a pretty good start (post it to pastebin or similar), we will let you know if we need more.
Credits & thanks:
vache - all the leaked ROM's
drellisdee - patched A500 kernel
CyanogenMod - source
Google - source
More to come.
Q: assert.failed:getprop("ro.product.device")=="Picas so" || getprop("ro.build.product")=="picasso" E:Error in /sdcard/Download/update-cm-9.0.0-RC0-picasso-UNOFFICIAL-signed.zip Status 7
A: Open the zip. Go to META-INF/com/google/android/update-sctipt. Remove the top line with the assert then repackage and flash has to do with your recovery. some recovery's name the device differently (thors for example does this, just as an example). our tree uses the device name picasso, if the recovery does not use picasso it will fail, the only fix for this is a unified recovery or to remove the line from the update-script, hope this more detailed answer helps more...
Thought it's about time to let the cat out of the bag.
Continuing on from gh123man's Open ICS thread, we extended the scope of the project to cover the A100 & A200 devices too.
For the last month we've been quietly working on this & the wheels are now in motion to get the devices merged into CyanogenMods source.
It should only be a matter of time till the nightlies start rolling.
You, sir, are a massive tease!
Current Devices: Samsung Galaxy Note II (N7100), Acer Iconia Tab A511
Past Devices (too many to list, mostly Acers!)
Users with the Honeycomb bootloader can use the following boot.img (flash after the rom) picasso_cm9_hc_bl_bootimg-signed.zip
md5 4dd954cf0f60deca02c6c93880fd1fcb
Standard CYA clause applies, flash at your own risk.
Thanks..id like to try but the hc boot.img link is the same as the rom.
Acer ICONIA TAB A500 16Gb
[randomblame JB 4.2 AOSP] “Let the future tell the truth, and evaluate each one according to his work and accomplishments. The present is theirs; the future, for which I have really worked, is mine.” -Nikola Tesla
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?