Droid Basement

-cleaned up local source once more, and rebased/remerged
-remove patched vold from update.zip
-merged (from Cyanogen’s cm-kernel github):
d68f1d1e796aa60f430fbcc8bc000a0d8100c03a (arm: msm: smd: use either package v3 or v4 not both)

Note:
Known Issues (this only effects non-froyo users):
-vold will throw a SIGSEV upon kernel boot. You can download a patched vold below, which will return 0 for SDIO during UEVENT, in attempts for some speed up during this process. vold’s structure has changed for Froyo, and as such, no patched vold is needed (it terminates once it connects) for that platform.
-when unplugging and then plugging back in (USB), then hitting USB mount, vold will throw a SIGSEV. Wait until you hear the USB notification on the phone (after hitting mount the first time), prior to hitting mount again. Then you will see the popup on your computer.
-Slight delay in showing USB pulldown, when unplugging and then plugging back in.
-if you repeatedly receive a USB notification while plugged in (and vold is SIGSEV’ing), try rebooting the phone with the cable plugged in, or unplug, wait a few seconds and replugging back in.

Patched VOLD (for Eclair only):
vold-patched-eclair-n1.zip
Download: vold-patched-eclair-n1.zip

Push .zip/bin/vold to /system/bin/vold and set 755 on it, via recovery.

——–

-Do not use this kernel set if you are on CM5.0.6

——–

-XTRA contains:
*some more cgroup options
*namespaces support (excluding network)
*deadline i/o scheduler
*v4 block device and data integrity support
*3d register driver
*erratas 430973, 458693 and 460075 applied

CM5.0.5.x, CM5.0.7.x and CM5.0.8:
boot-cm_2635_rc3-oc-uv-btn-aud-ram-neon_fp-070110.zip
Download: boot-cm_2635_rc3-oc-uv-btn-aud-ram-neon_fp-070110.zip

boot-cm_2635_rc3-oc-uv-xtra-btn-aud-ram-neon_fp-070110.zip
Download: boot-cm_2635_rc3-oc-uv-xtra-btn-aud-ram-neon_fp-070110.zip

<><><>

Android 2.2 (Froyo):
boot-cm_2635_rc3_froyo-oc-uv-btn-aud-ram-neon_fp-070110.zip
Download: boot-cm_2635_rc3_froyo-oc-uv-btn-aud-ram-neon_fp-070110.zip

boot-cm_2635_rc3_froyo-oc-uv-xtra-btn-aud-ram-neon_fp-070110.zip
Download: boot-cm_2635_rc3_froyo-oc-uv-xtra-btn-aud-ram-neon_fp-070110.zip

——–

Source:
http://github.com/cyanogen/cm-kernel
http://github.com/pershoot/nexus-kernel-2635
http://android.git.kernel.org/?p=kernel/experimental.git;a=shortlog;h=refs/heads/android-msm-2.6.34-test2
http://android.git.kernel.org/?p=kernel/experimental.git;a=shortlog;h=refs/heads/android-2.6.34-test2
http://android.git.kernel.org/?p=kernel/experimental.git;a=shortlog;h=refs/heads/android-msm-2.6.35-rc3-wip
http://osdir.com/ml/android-porting/2009-07/msg00386.html
——–

Instructions:
Flash the .zip through recovery
or

fastboot flash zimage zImage (zImage can be found in update.zip kernel folder)
then

take the bcm4329.ko file from the update.zip lib/modules folder (use winrar for windows or unzip for linux) and

adb remount
adb push bcm4329.ko /system/lib/modules
or
copy the bcm4329.ko to /sdcard, bounce in to recovery, mount /sdcard and /system, and copy the .ko module from /sdcard to /system/lib/modules; set chmod 644 on it.

Note:
If you use SetCPU, please do not set any Advanced settings, and you should use ondemand CPU governor

-cleaned up local source, and rebased/remerged
-set RWSEM_GENERIC_SPINLOCK, REMOTE_SPINLOCK_LDREX and REMOTE_SPINLOCK
-set _BLK_CGROUP and CFQ_GROUP_IOSCHED for non -xtra

-merged (from android.git.kernel.org’s github):
8ea0ee0293eabe108b7aa54ab4ca7d74bbb6537c (network: wireless: bcm4329: Set special OUI: 02:1A:11:FH:HH:HH for SoftAP)
0069a321978ecd9927fb1ecaecc7808d1a5af8ee ([ARM] msm: mahimahi: Set built-in flag for wlan device)
5324897646395a4f3011a96e38f3e62991933fc3 ([ARM] msm: mmc: Fix built-in device detect delay)
41cde44e12dd30043199c198b60ae091e5235bf5 ([ARM] msm: only build the legacy rpc servers for msm7x01a devices)
8602dc175b533f0555370d5c50884695bd88bb76 (msm72k_udc: disable excessive debug chatter)
5e97d05f96e32f0aab6b96b718163dac6531df80 (drivers: mmc: msm: Change max frequency to 49152000)
59c99cb3b7d9f1562758b8b41baffcc8cda4fe24 ([ARM] video: msm: drop mddi clock request and power down pad drivers on suspend)
4063529580910da1b3c47e98a2318d4aebc0fd9a ([ARM] video: msm: mddi: enable clocks before touching registers on resume)
97d4a7830bf782d089179a78e175cc3299968cce ([ARM] video: msm: kgsl: manage the grp pclk, if present)
8dd4f61373f68bd9981e0a22bb629ce7eebff31d ([ARM] msm: Do not assume reset vector is at 0x0)
78bbafb65cb92ab5405445230583dc387fc20be4 ([ARM] video: msm: Manage mdp/mddi pclk clocks, if present)
fa979a0dd43009738642123b191a738f9b56a175 ([ARM] video: msm: small cleanup of setting dma fb format)
d0c6863677483394784aa4d7988fa41287fe7081 ([ARM] msm: remove unneeded cfg_dma func ptr in mdp_device)
6d6bf92590adb32c68aa3b32f397cbf03e9b6739 ([ARM] video: msm: use the configured pack pattern for mddi)
e6f5c55b07f32839abd06eeb1ecd206334048b66 (input: gpio_event: make driver be more robust against incorrectly configured lvl trigger irqs)
fe2aaf502653dcdbbc24d7ee96890c989a0efb10 (Input: gpio_event: Don’t call gpio_cansleep before gpio_request.)
e678928136195cf18e549bef4282190f938b30ff ([ARM] msm: add a define for first board gpio)
46813573c89ee21717b2fef4df6f01ddb7cc2c50 ([ARM] msm: add a remote spinlock implementation for sync with modem processor)
cabe1296bd49edf4352ef20a6618bbb349c93e5e ([ARM] msm: add remote spinlcok config options and build rule)
9e62104f8fa9d27b413c10a5496299542f5e4c12 (ARM] msm: smd_debug: parse the hw version/id info from smem build id)
6ce09dafaed8ee93d395c26f7dc96f53e3478dfe ([ARM] usb: msm72k_udc: Force the phy to non-driving mode after reset)
7517250f169af83a00f632342272b05f5a15efe6 (arm: msm: usb: add usb core clk management, as found on 7×30)
286f27352874b76067f5c6f255be4460c7bbd5ac ([ARM] boot: fix typo with #ifdef defined() when debug is enabled)
31b9c2d76fdd2b670a61445cbcfb9fc91914561c (arm: msm: use correct regs for scorpion powerup/powerdown for pm)
5b5e52acdd171d3e915b975637eabc1aaef212e8 (arm: msm: correctly signal the apps-to-modem irq in smd/proc_comm)
e454e231a4a3fb68d5067e9e3abaced2beef1464 ([ARM] mtd: msm_nand: platform partition data is now in units of blocks, not bytes)
d1e51c3275abd94dfbed2c4681abdce70032ed37 ([ARM] msm: nand_part: Pass partition size/offset in blocks instead of bytes)
fe008c4b87356a51b2396e50b4a7fb23ef78eaa3 (yaffs: Use init_timer_on_stack for timer on stack)

Note:
Known Issues:
-Video camcorder will not work unless you are using Android 2.2 (Froyo) and its associated radio, or CM5.0.8 and Froyo’s radio.

Note:
The wifi module in the update.zip format files is the new one (Version: 4.218.239)
If you would like to try the older version wifi module (more details: ?p=410), push the bcm4329.ko module contained within this .zip to /system/lib/modules:

wifi-OLD.zip
Download: wifi-OLD.zip

-Do not use this kernel set if you are on CM5.0.6

——–

-XTRA contains:
*some more cgroup options
*namespaces support (excluding network)
*deadline i/o scheduler
*v4 block device and data integrity support
*3d register driver
*erratas 430972, 458693 and 460075 applied

CM5.0.5.x, CM5.0.7.x and CM5.0.8:
boot-cm_2634-oc-uv-btn-aud-ram-neon_fp-070110.zip
Download: boot-cm_2634-oc-uv-btn-aud-ram-neon_fp-070110.zip

boot-cm_2634-oc-uv-xtra-btn-aud-ram-neon_fp-070110.zip
Download: boot-cm_2634-oc-uv-xtra-btn-aud-ram-neon_fp-070110.zip

<><><>

Android 2.2 (Froyo):
boot-cm_2634_froyo-oc-uv-btn-aud-ram-neon_fp-070110.zip
Download: boot-cm_2634_froyo-oc-uv-btn-aud-ram-neon_fp-070110.zip

boot-cm_2634_froyo-oc-uv-xtra-btn-aud-ram-neon_fp-070110.zip
Download: boot-cm_2634_froyo-oc-uv-xtra-btn-aud-ram-neon_fp-070110.zip

——–

Source:
http://github.com/cyanogen/cm-kernel
http://github.com/pershoot/nexus-kernel
http://android.git.kernel.org/?p=kernel/experimental.git;a=shortlog;h=refs/heads/android-msm-2.6.34-test2
http://android.git.kernel.org/?p=kernel/experimental.git;a=shortlog;h=refs/heads/android-2.6.34-test2
http://android.git.kernel.org/?p=kernel/experimental.git;a=shortlog;h=refs/heads/android-mem-2.6.35-rc3-wip

——–

Instructions:
Flash the .zip through recovery
or

fastboot flash zimage zImage (zImage can be found in update.zip kernel folder)
then

take the bcm4329.ko file from the update.zip lib/modules folder (use winrar for windows or unzip for linux) and

adb remount
adb push bcm4329.ko /system/lib/modules
or
copy the bcm4329.ko to /sdcard, bounce in to recovery, mount /sdcard and /system, and copy the .ko module from /sdcard to /system/lib/modules; set chmod 644 on it.

Note:
If you use SetCPU, please do not set any Advanced settings, and you should use ondemand CPU governor

Update (-063010):
-cleaned up local source, rebased/remerged
-merged (from Cyanogen’s cm-kernel github):
b924424a708d0e2d93bf5197e96ae31886df30ea (msm: serial: Fix wakeup handling)

(-062910)
-merged (from android.git.kernel.org’s github):
8ea0ee0293eabe108b7aa54ab4ca7d74bbb6537c (network: wireless: bcm4329: Set special OUI: 02:1A:11:FH:HH:HH for SoftAP)
5d25bc1867239c11b9a472e2656c503c22dddc47 (USB: gadget: android: Remove unused function android_usb_set_connected())
6146b9ff697dea64bd8b01220fc802c85b1af3c1 (nohz: Fix nohz ratelimit)
60880c5315f54919ec161932cf7c3e2197bd1024 (USB: composite: Add support for functions overriding USB_DT_STRING descriptors)
0069a321978ecd9927fb1ecaecc7808d1a5af8ee ([ARM] msm: mahimahi: Set built-in flag for wlan device)
5324897646395a4f3011a96e38f3e62991933fc3 ([ARM] msm: mmc: Fix built-in device detect delay)
29ee630714b23d7e554aad746d7f613889e55cc5 ([ARM] i2c: qup (msm): Do not take pclk name from pdata, request it normally)
797a7f487ebde54bd10363d44496748f6d4501a9 ([ARM] msm: rename camif_pad_pclk to its actual function, qup_pclk)
a1439d90ca87a54f7db70d5781f3d632af9139e8 (msm_iomap-8×50.h: Rename MSM_SMI_BASE to avoid conflict)
d5c429210c20834733198a4a6ecb2183132bf04b ([ARM] msm: smd/clock: use config var to decide rpc versioning scheme)
d0c6863677483394784aa4d7988fa41287fe7081 ([ARM] msm: remove unneeded cfg_dma func ptr in mdp_device)
e6f5c55b07f32839abd06eeb1ecd206334048b66 (input: gpio_event: make driver be more robust against incorrectly configured lvl trigger irqs)
fe2aaf502653dcdbbc24d7ee96890c989a0efb10 (Input: gpio_event: Don’t call gpio_cansleep before gpio_request.)
e678928136195cf18e549bef4282190f938b30ff ([ARM] msm: add a define for first board gpio)
6376a8c7f9918f2480cdd6d93707091dfc7952a2 ([ARM] msm: devices: add the pmic ssbi device and resources)
222674d8f2f4e9d8b34961c85479d9ad740ce369 ([ARM] msm: add single-wire serial bus interface (SSBI) driver)
46813573c89ee21717b2fef4df6f01ddb7cc2c50 ([ARM] msm: add a remote spinlock implementation for sync with modem processor)
9e62104f8fa9d27b413c10a5496299542f5e4c12 ([ARM] msm: smd_debug: parse the hw version/id info from smem build id)
6ce09dafaed8ee93d395c26f7dc96f53e3478dfe ([ARM] usb: msm72k_udc: Force the phy to non-driving mode after reset)
b4194b94c6534f432783282b0510151280a7503c ([ARM] mtd: msm_nand: Use the correct base address from the iomap)
7517250f169af83a00f632342272b05f5a15efe6 (arm: msm: usb: add usb core clk management, as found on 7×30)
286f27352874b76067f5c6f255be4460c7bbd5ac ([ARM] boot: fix typo with #ifdef defined() when debug is enabled)
31b9c2d76fdd2b670a61445cbcfb9fc91914561c (arm: msm: use correct regs for scorpion powerup/powerdown for pm)
5b5e52acdd171d3e915b975637eabc1aaef212e8 (arm: msm: correctly signal the apps-to-modem irq in smd/proc_comm)
e454e231a4a3fb68d5067e9e3abaced2beef1464 ([ARM] mtd: msm_nand: platform partition data is now in units of blocks, not bytes)
d1e51c3275abd94dfbed2c4681abdce70032ed37 ([ARM] msm: nand_part: Pass partition size/offset in blocks instead of bytes)
a2464412d135e7e6c3ed29b2554c7014beac9bfd (Revert “drivers: misc: pass miscdevice pointer via file private data”)
fe008c4b87356a51b2396e50b4a7fb23ef78eaa3 (yaffs: Use init_timer_on_stack for timer on stack)
85275491ccd783bc266a6d43517465c151748557 ([ARM] msm: clock: Don’t get unused ebi1 clock in msm_clock_init)
b979bc54db405573abe3398204f32ba245cc4165 (sirc: fix build)

Note:
Known Issues (this only effects non-froyo users):
-vold will throw a SIGSEV upon kernel boot. Both non -froyo files contain a patched vold which will return 0 for SDIO during UEVENT, in attempts for some speed up during this process. vold’s structure has changed for Froyo, and as such, no patched vold is provided nor may be needed (it terminates once it connects) for that platform.
-when unplugging and then plugging back in (USB), then hitting USB mount, vold will throw a SIGSEV. Wait until you hear the USB notification on the phone (after hitting mount the first time), prior to hitting mount again. Then you will see the popup on your computer.
-Slight delay in showing USB pulldown, when unplugging and then plugging back in.
-if you repeatedly receive a USB notification while plugged in (and vold is SIGSEV’ing), try unplugging, waiting a few seconds, and then plugging back in.

-Do not use this kernel set if you are on CM5.0.6

——–

-XTRA contains:
*some more cgroup options
*namespaces support (excluding network)
*deadline i/o scheduler
*v4 block device and data integrity support
*3d register driver
*erratas 430973, 458693 and 460075 applied

CM5.0.5.x, CM5.0.7.x and CM5.0.8:
boot-cm_2635_rc3-oc-uv-btn-aud-ram-neon_fp-063010.zip
Download: boot-cm_2635_rc3-oc-uv-btn-aud-ram-neon_fp-063010.zip

boot-cm_2635_rc3-oc-uv-xtra-btn-aud-ram-neon_fp-063010.zip
Download: boot-cm_2635_rc3-oc-uv-xtra-btn-aud-ram-neon_fp-063010.zip

<><><>

Android 2.2 (Froyo):
boot-cm_2635_rc3_froyo-oc-uv-btn-aud-ram-neon_fp-063010.zip
Download: boot-cm_2635_rc3_froyo-oc-uv-btn-aud-ram-neon_fp-063010.zip

boot-cm_2635_rc3_froyo-oc-uv-xtra-btn-aud-ram-neon_fp-063010.zip
Download: boot-cm_2635_rc3_froyo-oc-uv-xtra-btn-aud-ram-neon_fp-063010.zip

——–

Source:
http://github.com/cyanogen/cm-kernel
http://github.com/pershoot/nexus-kernel-2635
http://android.git.kernel.org/?p=kernel/experimental.git;a=shortlog;h=refs/heads/android-msm-2.6.34-test2
http://android.git.kernel.org/?p=kernel/experimental.git;a=shortlog;h=refs/heads/android-2.6.34-test2
http://android.git.kernel.org/?p=kernel/experimental.git;a=shortlog;h=refs/heads/android-msm-2.6.35-rc3-wip
http://osdir.com/ml/android-porting/2009-07/msg00386.html

——–

Instructions:
Flash the .zip through recovery
or

fastboot flash zimage zImage (zImage can be found in update.zip kernel folder)
then

take the bcm4329.ko file from the update.zip lib/modules folder (use winrar for windows or unzip for linux) and

adb remount
adb push bcm4329.ko /system/lib/modules
or
copy the bcm4329.ko to /sdcard, bounce in to recovery, mount /sdcard and /system, and copy the .ko module from /sdcard to /system/lib/modules; set chmod 644 on it.

Note:
If you use SetCPU, please do not set any Advanced settings, and you should use ondemand CPU governor

-rebase to android.git.kernel.org’s 2.6.35-rc3
-set: cgroup: Block IO controller and CONFIG_CFQ_GROUP_IOSCHED for non -xtra
-set RWSEM_GENERIC_SPINLOCK, REMOTE_SPINLOCK_LDREX and REMOTE_SPINLOCK

-revert:
847306ecc8e7d8b7cebdc592e23896bccea35395 (USB: gadget: f_mass_storage: Integrate android customizations)

Note:
Known Issues (this only effects non-froyo users):
-vold will throw a SIGSEV upon kernel boot. Both non -froyo files contain a patched vold which will return 0 for SDIO during UEVENT, in attempts for some speed up during this process. vold’s structure has changed for Froyo, and as such, no patched vold is provided nor may be needed (it terminates once it connects) for that platform.
-when unplugging and then plugging back in (USB), then hitting USB mount, vold will throw a SIGSEV. Wait until you hear the USB notification on the phone (after hitting mount the first time), prior to hitting mount again. Then you will see the popup on your computer.
-Slight delay in showing USB pulldown, when unplugging and then plugging back in.
-if you repeatedly receive a USB notification while plugged in (and vold is SIGSEV’ing), try unplugging, waiting a few seconds, and then plugging back in.

-Do not use this kernel set if you are on CM5.0.6

——–

-XTRA contains:
*some more cgroup options
*namespaces support (excluding network)
*deadline i/o scheduler
*v4 block device and data integrity support
*3d register driver
*erratas 430973, 458693 and 460075 applied

CM5.0.5.x, CM5.0.7.x and CM5.0.8:
boot-cm_2635_rc3-oc-uv-btn-aud-ram-neon_fp-062810.zip
Download: boot-cm_2635_rc3-oc-uv-btn-aud-ram-neon_fp-062810.zip

boot-cm_2635_rc3-oc-uv-xtra-btn-aud-ram-neon_fp-062810.zip
Download: boot-cm_2635_rc3-oc-uv-xtra-btn-aud-ram-neon_fp-062810.zip

<><><>

Android 2.2 (Froyo):
boot-cm_2635_rc3_froyo-oc-uv-btn-aud-ram-neon_fp-062810.zip
Download: boot-cm_2635_rc3_froyo-oc-uv-btn-aud-ram-neon_fp-062810.zip

boot-cm_2635_rc3_froyo-oc-uv-xtra-btn-aud-ram-neon_fp-062810.zip
Download: boot-cm_2635_rc3_froyo-oc-uv-xtra-btn-aud-ram-neon_fp-062810.zip

——–

Source:
http://github.com/cyanogen/cm-kernel
http://github.com/pershoot/nexus-kernel-2635
http://android.git.kernel.org/?p=kernel/experimental.git;a=shortlog;h=refs/heads/android-msm-2.6.34-test2
http://android.git.kernel.org/?p=kernel/experimental.git;a=shortlog;h=refs/heads/android-2.6.34-test2
http://android.git.kernel.org/?p=kernel/experimental.git;a=shortlog;h=refs/heads/android-msm-2.6.35-rc3-wip
http://osdir.com/ml/android-porting/2009-07/msg00386.html

——–

Instructions:
Flash the .zip through recovery
or

fastboot flash zimage zImage (zImage can be found in update.zip kernel folder)
then

take the bcm4329.ko file from the update.zip lib/modules folder (use winrar for windows or unzip for linux) and

adb remount
adb push bcm4329.ko /system/lib/modules
or
copy the bcm4329.ko to /sdcard, bounce in to recovery, mount /sdcard and /system, and copy the .ko module from /sdcard to /system/lib/modules; set chmod 644 on it.

Note:
If you use SetCPU, please do not set any Advanced settings, and you should use ondemand CPU governor

ADW Launcher (almostNexus mod) 0.9, by Anderwebs

-modified to use /data/data/com.android.launcher2 (pershoot)
-last github source commit: about 1 hour ago

adwlauncher_0.9-n1-062810.zip
Download: adwlauncher_0.9-n1-062810

——

Source:
http://github.com/AnderWeb/android_packages_apps_Launcher

——

Instructions:
Flash the .zip through recovery

Note:
CM5.0.8 contains /system/app/ADWLauncher.apk. If you have already selected ADW to be your default, you can alternatively push (and not flash the update.zip) Launcher2.apk from update.zip/app to /system/app/ADWLauncher.apk. You will have to re-setup your homescreens.

ADW Launcher (almostNexus mod) 0.9, by Anderwebs

-last github source commit: about 1 hour ago

adwlauncher_0.9-ds-062810.zip
Download: adwlauncher_0.9-ds-062810

——

Source:
http://github.com/AnderWeb/android_packages_apps_Launcher

——

Instructions:
Flash the .zip through recovery

Note:
If you are running the latest CM5.0.8 final or the latest CM5.0.8-T Series, then:

Option A:
After flashing go to console and:
rm /system/app/ADWLauncher.apk

or

Option B:
Do not flash through recovery and pull the Launcher.apk from update.zip/app folder and in recovery:
adb shell mount /system
adb push Launcher.apk /system/app/ADWLauncher.apk
adb shell umount /system

ADW Launcher (almostNexus mod) 0.8 (.8), by Anderwebs

-modified to use /data/data/com.android.launcher2 (pershoot)
-last github source commit: about 13 hours ago

adwlauncher_0.8-n1-062610.zip
Download: adwlauncher_0.8-n1-062610

——

Source:
http://github.com/AnderWeb/android_packages_apps_Launcher

——

Instructions:
Flash the .zip through recovery

Note:
CM5.0.8 contains /system/app/ADWLauncher.apk. If you have already selected ADW to be your default, you can alternatively push (and not flash the update.zip) Launcher2.apk from update.zip/app to /system/app/ADWLauncher.apk. You will have to re-setup your homescreens.

ADW Launcher (almostNexus mod) 0.8 (.8), by Anderwebs

-last github source commit: about 13 hours ago

adwlauncher_0.8-ds-062610.zip
Download: adwlauncher_0.8-ds-062610

——

Source:
http://github.com/AnderWeb/android_packages_apps_Launcher

——

Instructions:
Flash the .zip through recovery

Note:
If you are running the latest CM5.0.8 final or the latest CM5.0.8-T Series, then:

Option A:
After flashing go to console and:
rm /system/app/ADWLauncher.apk

or

Option B:
Do not flash through recovery and pull the Launcher.apk from update.zip/app folder and in recovery:
adb shell mount /system
adb push Launcher.apk /system/app/ADWLauncher.apk
adb shell umount /system

ADW Launcher (almostNexus mod) 0.8 (.8), by Anderwebs

-modified to use /data/data/com.android.launcher2 (pershoot)
-last github source commit: about 4 hours ago

Note: Will show 0.8.7.

adwlauncher_0.8-n1-062410.zip
Download: adwlauncher_0.8-n1-062410

——

Source:
http://github.com/AnderWeb/android_packages_apps_Launcher

——

Instructions:
Flash the .zip through recovery

Note:
CM5.0.8 contains /system/app/ADWLauncher.apk. If you have already selected ADW to be your default, you can alternatively push (and not flash the update.zip) Launcher2.apk from update.zip/app to /system/app/ADWLauncher.apk. You will have to re-setup your homescreens.

ADW Launcher (almostNexus mod) 0.8 (.8), by Anderwebs

-last github source commit: about 4 hours ago

Note: Will show 0.8.7.

adwlauncher_0.8-ds-062410.zip
Download: adwlauncher_0.8-ds-062410

——

Source:
http://github.com/AnderWeb/android_packages_apps_Launcher

——

Instructions:
Flash the .zip through recovery

Note:
If you are running the latest CM5.0.8 final or the latest CM5.0.8-T Series, then:

Option A:
After flashing go to console and:
rm /system/app/ADWLauncher.apk

or

Option B:
Do not flash through recovery and pull the Launcher.apk from update.zip/app folder and in recovery:
adb shell mount /system
adb push Launcher.apk /system/app/ADWLauncher.apk
adb shell umount /system