Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is a preview build of Android JellyBean 4.2 from AOSP source code based on the CyaogenMod device tree for Acer A700. I have made this build to gauge how difficult it would be to port JellyBean 4.2 to current devices.
Kernel Source Code: https://github.com/pawitp/android_kernel_acer_t30/tree/jellybean-next
Device Tree: None yet available (Only notable part: patch for TinyHAL: https://gist.github.com/4104332)
Downloads
ROM: http://goo.im/devs/pawitp/a700/a700_aosp_jb42_20121116.zip
Google Apps: Currently integrated due to lack of gapps package for 4.2
SuperSU: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip (Currently, only SuperSU is compatible with 4.2)
Installation
Note: due to new /data/media layout in 4.2 for multiple user support, your data in /data/media (/sdcard) will be moved to /data/media/0. This may cause problems in restoring backups in recovery, you may fix it by moving data /data/media/0 back to /data/media via adb in recover prior to restoring data.
- Install CWM recovery from http://xdaforums.com/showthread.php?t=1791165
- Do a Nandroid Backup!
- Install the ROM using ClockworkMod Recovery
- Optionally install the Google Addon
- Wipe data if coming from stock
Known Issues
- Camera does not work
- Bluetooth sometimes freezes bringing down Wi-Fi with it
Reporting Bugs
You are allowed to report bugs only in this thread. Note that this is a preview release and non-device specific bugs will not be accepted. The development of this preview will also cease once enough progress has been made in CyanogenMod.
- Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
- If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Last edited: