Monday, August 20, 2012

CM9 Stable for Epic 4G

CM9 stable for Epic 4G was released a while ago at Cyanogenmod.  Get the latest stable build from get.cm.  The install instructions in our CM9 Install Guide still apply.

Update 12/21/2012: CM10.1 Preview for Epic 4G.

Update 9/29/2012: If you are running CM10, you will need the temporary FC09 utility v4 in order to update Profile and PRL.  Thanks to mkasick and bbelos for fixing it!

The same team works on CM10, news is posted elsewhere on the Google+ page.

34 comments:

  1. Thank you very much. I look forward to updating to the Stable version. I really looking forward to the CM10 release.

    ReplyDelete
  2. Nice work guys. Loving every bit of it!

    ReplyDelete
  3. With all due respect, I do not find this release very stable. I am experiencing the same problems, including awful call connectivity and reliability, daily lock ups, battery issues, overall sluggishness, continued MMS problems, and much more.

    I realize this is volunteer stuff and you don't pull in enough money to buy a decent dinner, but this is just not a stable release. I do thank you for the work though.

    ReplyDelete
    Replies
    1. Try a different phone, or Odin to Stock and Go stable direct. and a new SD card. somethings wrong.

      Delete
    2. I also have none of the problems you have. The bad connectivity and reliability could be your area. My kids both have the same phone (both stock) and they don't get the same service standing right next to each other. One makes calls fine in the house, while the other complains that they never have signal.

      The lock ups, battery drain and sluggishness are probably all the same issue. An app that is using a lot of your processor will slow the phone down and kill the battery, as well as cause lock ups if all the system's resources are tied up. Check your battery usage stats and try installing spare parts plus to see what is using your processor or other radios. It may just be a poorly written app causing your problems.

      Delete
  4. noticed that previous nightlies, this, and current nightlies all have broken Pandora over 3g, tried updating profile and PRL and Pandora still fails... will buffer 2% and then switch to the next song. Also data seems slow and long response times in general. Hopefully a fix to make this work with the Nexus S modem will come out soon.

    ReplyDelete
    Replies
    1. I booted the FC09 liveboot, installed and ran pandora, PRL updated and data, then booted back to CM9 stable, uninstalled and reisntalled Pandora, and it works. Also contacted Pandora while doing that, may have been something on their end, per an account basis.

      Delete
    2. Its the pandora version drop back to an earlier apk worked for me

      Delete
  5. i would have to agree with Michael on this not being a REAL stable release....daily lock ups, battery issues, overall sluggishness, continued MMS problems

    The " including awful call connectivity and reliability" i am not having an issue with myself

    Seems that some of the beta releases were more stable then the RC and the stable release

    ReplyDelete
  6. Now that the developers are working on CM10 they are probably not going to fix the issues in CM9. Funny, because I'm sure that when the next version of Android is released we will be almost stable with CM10, and they will drop that to begin work on CM11.

    ReplyDelete
  7. I haven't had any issues on this release so far. My only complaint (and this has been the case with all CM9 builds I've tried) is that an input method never appears in the Chrome Beta app. When I tap on a text field, the typing cursor appears, but the keyboard never comes up. Just curious if anyone else has this issue. I've searched all over the place and can't find anything about it.

    ReplyDelete
    Replies
    1. I experience the same issue. I finally just installed the GO Keyboard and it works fine.

      Delete
    2. Not to diminish your issue, but chrome is in beta which means it may very well be causing the conflict. Using a different browser might be better anyway, since chrome uses a ton of battery compared to alternatives

      Delete
    3. Sure, I use the Dolphin browser and TouchPal keyboard primarily, but I do like some of Chrome's features, hence the question. I wasn't really concerned so much with why it was happening, I just didn't know if I was the only person experiencing the problem.

      Delete
  8. I have the same problem that has Jacob Byrd on chrome install a rom JB 4.1 that was found and fixed but I never served CM9
      'm Dominican excuse my English :)

    ReplyDelete
  9. The Chrome thing i remember them acknowledging that they knew about it but i guess it didn't get fixed.....

    ReplyDelete
  10. CM9 works great on my Epic 4G. The stock GB locked up several times a week and would get slow every day. I broke a case because I had to take out the battery so many times with Samsung GB. Since the release of stable CM9, I have no crashes or lockups and everything is working great and fast. Voice/data/SMS/WiFi/VPN all working well. I can now use ICS apps on a Sprint phone with a keyboard! The only issue I have so far is the early timeout on the keyboard backlight. I hope CM9 gets a few more updates and bug fixes for Sprint PRL and other little things, but I'm happy with CM9. Great job team!

    ReplyDelete
  11. the mms is still not working - can anyone figure out a fix? (sprint). Sometimes I found deleteing the telephony.db in /data/data/com.android.providers.telephony/databases will work temporarily after a reboot. but very cumbersome to do this each time it gets stuck

    ReplyDelete
  12. Try this - http://forum.xda-developers.com/showthread.php?t=1756464 - worked like a charm for me

    ReplyDelete
  13. I've been using this for a while, and did note a number of issues initially, but I think I've discovered the way around them. Each time, I followed the update instructions exactly. Tossing those out and following a modified fresh install method (remove external SD card, factory reset, boot into CWM, format every partition, wipe cache, wipe Dalvik, fix permissions, installed CM, installed gapps, reboot, install freshly formatted SD card) seems to have worked most/all the kinks out. It still get a little sluggish here and there, but I'm not getting the multiple app crashes per hour (I use my phone *a lot*).

    ReplyDelete
  14. I got my Samsung Epic 4G used and it was stock GB. It froze once or twice a day, causing me to take the case off and the back and force restart. Installed CM9 RC1 as first ROM and it never froze or nothing. Had no problems with RC1. Now I installed CM9.1, the latest stable ROM. So hopefully this will be better :D

    ReplyDelete
  15. I jumped from CM9 RC2 to CM9.1, skipping 9.0. RC2 was perfectly stable for me, despite the claims that there were issues with it holding the zip installations of things like gapps. Since installation of 9.1 ~36 hours ago, I've gotten about a half dozen resets of my phone. It's probably something to do with some programs on my phone, but just an FYI.

    Otherwise, I can't thank you guys enough for extending the life of my Epic and keeping it up to date.

    ReplyDelete
  16. @unknown
    The main reason to reinstall gapps and everything is to make it a "fresh" install to prevent the random lockups/reboots. There are still issues with this either way.
    Could do as @Cobey said and do a fresh micro sd card and then wipe cache and dalvik and permissions. I have not had the time or the will to actually do this yet* I am still on 9.0.0 and seems to be working fine for me with a lock up every other day or so. Still WAY better then RC2 but not as great as the betas

    ReplyDelete
    Replies
    1. I don't know why it's showing me up as Unknown when I'm signed in using Google... Whatever. I'll just tag myself at the end. But yea, I'm Unknown from above. I always reinstall gapps when updating CM, it's just force of habit, which may have been why I never had any issues with RC2. I did go through and fix permissions though (I already wiped cache/dalvik on update to 9.1, again, habit), which appears (so far) to have possibly fixed my issues. I've now gone 24 hours without any lockups or force closes. Anyway, thanks. I'll let you guys know if I run into anything else. :)

      -kfduncanjr

      Delete
  17. Love this ROM. Using it as my daily driver and having NO lockups / random reboots, whatsoever. Now I wait for CyanogenMod Team to make JB for Epic :D. But I can gladly wait, since I got CM9.1 :D

    ReplyDelete
  18. there is 20120904 build http://get.cm/get/jenkins/7484/cm-10-20120904-NIGHTLY-epicmtd.zip

    ReplyDelete
  19. PROBLEM WITH CHROME FIXED IN SOME CM10 IF NOT COME INTO WORK SETTINGS disable keyboard and input method Put the physical keyboard and not everything will be fine

    excuse my English :)

    ReplyDelete
  20. Wow, CM10 (Jelly Bean) is MUCH improved from CM9. All apps are much faster, smoother, bluetooth is fully functional, A+++!

    Thanks! Won't be buying a new phone anytime soon thanks to this new ROM.

    ReplyDelete
  21. hmm i shall try this now, right now lolz

    ReplyDelete
  22. Can anyone comment on the stability of the cm10 nightly builds? Are there any major issues that we should be aware of?

    Cheers!

    ReplyDelete
    Replies
    1. Only major issue is the temporary FC09 fails to boot. We aren't sure why. It is a tool that every CM user should occasionally use in order to update Profile and PRL. The team will eventually come up with a solution.

      Delete
  23. I require my phone for work, and stability is key with respect to phone calls, SMS, and e-mail. I love the slide-out keyboard, but want to remove the default apps (nascar, etc), and install CM to make my phone 'leaner'. Stability is key.

    Which version do you recommend installing from a stock build, with stability in mind?

    ReplyDelete
  24. Hi, I am running 9.1. I get lockups/restarts here and there, but I think that is because the epic 4g hardware was never meant for ics (low ram and cpu etc.). Anyway, I have trouble streaming amazon instant video (using adobe flash player 11) which worked fine before (on stock FC09).

    ReplyDelete