Jul 25, 2011

[Rom 2.3.4] Cyanogen MOD 7 build 144 + battery & memory fix

CyanogenMOD 7 for Commtiva Z71, Apanda A60, Chinavision  Excalibur, Cincinnati Bell Blaze, Gigabyte Gsmart G1305, Motorola XT502, Muchtel A1, Optimus Boston, Orange Boston, Spice Mi-300, Vibo A688 and Wellcom A88 - official nightly version

Visit the CHANGELOG for a full list of changes and features!"

Nightly version after Stable:
Download: cm_z71_full-144.zip

Google Apps: gapps-gb-20110613-signed.zip

Battery and memory fix (Now with SuperAOSP 8 Kernel AW): SuperAOSP_8.6_.2.6.32.9-AW
Apply this after update the rom, lasts more than 2 days (Thanks to CML)

How to -> For who still have the old 2.1 or 2.2 rom and want to put this amazing rom, need to do this steps:

1- download 2.3 nb0 rom cm7.0.2_z71_battery_memory_fix.nb0

2- update your phone to 2.3 rom using SUT SUTLR_v1.7.0

3- download cm_z71_full-144.zip and SuperAOSP 8.6 2.6.32.9-AW to your memory card

4- on the recovery menu apply the new rom build update and after that apply the battery and memory fix

5- reboot your phone and that's all :D You have the 2.3.4 rom !!!

Thank you to EVERYONE involved in Cyanogen! Enjoy!

24 comments:

  1. Is this usable? For me the SuperAOSP 8.6 2.6.32.9-AW kept rebooting every few hours if not minutes with #127.

    Have been using #127 with standard CM7 kernel.

    ReplyDelete
  2. Why this kernel(SuperAOSP_8.6_.2.6.32.9-AW) flash in my phone , if screen off the wifi will disconnecte??

    I already check option from:
    internet setting>advanced>wifi always connecte

    ReplyDelete
  3. http://www.thephonedatabase.com/Motorola_Quench_XT5_XT502_221_vs_HTC_Salsa_411_Compare_Phones

    Does this spec sheet indicate that the ROMs of these two phones will be compatible with each other?

    ReplyDelete
  4. i flashed this rom with the SuperAOSP 8.6 2.6.32.9 Kernel and it runs really smooth, best rom i ever had, quadrant about 1050, no reboots or other bad things... i let you know how the battery live is after a few days...

    ReplyDelete
  5. Most stable for me with ok battery is build 127 with SuperAOSP 8.6 2.6.32.9-AW. Does build 144 still have the upside down screen issue? 128 onwards had this issue.

    ReplyDelete
  6. Does anyone knows if the touchscreen problem remains at this nightlie?
    Any report on major issue with this nightlie?

    Thanks

    ReplyDelete
  7. 144 has the screen rotation problem resolved. However 147 doesn't! I installed 144 then booted, it was ok, then rebooted and installed the SuperAOSP kernel. So all looks good.

    ReplyDelete
  8. Rui, I would backup your current stable and then try it. If its no good you can then just restore?

    ReplyDelete
  9. 1 Day 6h20... 64% of battery NICE XD

    ReplyDelete
  10. Enable the USB debug, USB device can't mount it...

    ReplyDelete
  11. After update, SUTLR doesn't see my phone..any ideas ? :(

    ReplyDelete
  12. Same issue as reported by Lawliet

    ReplyDelete
  13. Installed the 147 and applied the kernel patch. I just notice the little lag, but probably that's to save battery life. I specifically noticed that i have to press the trackball for a longer time (few milliseconds) than usual to wake up the phone. This has been consistent always when applying a kernel patch. No reboots as of now. I had faced severe reboots earlier when I had patched the kernel on 127.

    ReplyDelete
  14. I'm stuck with this version, cuz SUTLR can't see my phone..any ideas ? please..

    ReplyDelete
  15. I too am facing the problem the SUTLR can't see my phone

    ReplyDelete
  16. u must get into the "Fastboot" mode!! those who cant connect SUTLR to phone

    ReplyDelete
  17. Hi lunenknight
    how to go into the "fastboot" kindly guide me

    ReplyDelete
  18. Have you tried Google? Sigh: fastboot mode is Volume down+End Call+Power (from Google).

    ReplyDelete
  19. After installing kernel, the accelerometer sensor is not working correctly. is there any solutions?

    ReplyDelete
  20. This comment has been removed by the author.

    ReplyDelete
  21. he phone is working fine still a couple of problems are there
    1. The SUTLR would not recognize the phone.

    2. The browser would show the last opened website even after killing with task manager

    3. The pre installed DSP manager does not get killed.

    4. The battery is about 34 hrs with moderate usage. ( the battery was better with the 137 build)

    Overall I feel its better as the phone used to reboot very frequently with the 137 build but with this no such problem has been faced yet. Lets see in coming days.

    ReplyDelete
  22. How come everybody faces different issues even if the build is same and the phone is same?

    ReplyDelete
  23. I agree with Askganesha... i got no prob using this build and somehow wondering why is it so many problem faced by others but no me...

    ReplyDelete