1. Download the #1 Android News App:   EarlyBird - News for Android
    Dismiss Notice

[Verizon] Running CM10

Last Updated:

  1. rehpyc

    rehpyc Well-Known Member

    CM10 is simply amazing. No negative things found as of yet. Should definitely check it out!

  2. Metfanant

    Metfanant Well-Known Member

    camera/camcorder is FULLY functioning?
  3. Travisimo

    Travisimo Well-Known Member

    I am holding off until they get the IMEI bugs worked out. Some people are losing their IMEI even after restoring back to stock. And it's happening on all of the carrier variants. I'm sure it'll be worked out soon, so I'm trying to be patient... If I get the urge, I'll just use my GNex for a while. lol
  4. Metfanant

    Metfanant Well-Known Member

    yeah was reading about that lol...im going to TRY and patiently wait a few days and see if they smooth out the little quirks, but it seems pretty damn stable as of right now...

    only thing i WISH was possible was to able to install the TouchWiz camera
  5. rehpyc

    rehpyc Well-Known Member

    Have both taken pictures and recorded things just fine. Everything is super smooth and opens without delay. Battery life seems equally as good as stock.
  6. nateap87

    nateap87 Well-Known Member

    We have it on our Verizon s3?
  7. Metfanant

    Metfanant Well-Known Member

  8. nateap87

    nateap87 Well-Known Member

    So does this basically render the dev edition pointless?
  9. jkc120

    jkc120 Well-Known Member

    Pretty much. If it ever releases...it's starting to smell like vaporware or Verizon pushing back on Samsung not to release it. :confused:
  10. rehpyc

    rehpyc Well-Known Member

    Devs finding ways around the boot loader has nothing to do with Verizon..
  11. jkc120

    jkc120 Well-Known Member

    What kind of statement is that? Of course it does. If Verizon hadn't locked it, we wouldn't need devs to work around it.

    Anyway, my point was they announced this dev edition and it still hasn't released. The most likely reason I can think of is Verizon is pissed they are offering it and they are trying to get them not to sell them.
    MistaWolfe likes this.
  12. WhoDoo Voodoo

    WhoDoo Voodoo Well-Known Member

    Chrome is so laggy it's annoying as hell. Netflix doesn't work. The phone is getting a bit warm. There are several apps that are not compatible.

    The keyboard is boss. Youtube is running fine on 07-23. Make sure you get the full Gapps. The response time is nice. Only 1 FC so far.

    To me when they get chrome straight it is daily driver worthy.
  13. rehpyc

    rehpyc Well-Known Member

    Where does Chrome lag for you? I use it as my browser and haven't had a single issue.

    Hopefully all developers update their apps to be fully compatible with JB.
  14. rehpyc

    rehpyc Well-Known Member

    BTW, to any worried about losing their IMEI, on xda there's a way to back it up.
  15. Travisimo

    Travisimo Well-Known Member

    Where are the latest gapps found? I see the cm10 updates at droidhive, but I don't see where to get the correct gapps. Do we have to make sure to use a certain version of gapps with a certain version of the cm10 rom?

    Link please?
  16. rehpyc

    rehpyc Well-Known Member

    http://forum.xda-developers.com/showthread.php?t=1791291 to back up your IMEI

    Head over to XDA Original Development for proper means of flashing CM10, which will include the proper CWM and JB gapps
  17. WhoDoo Voodoo

    WhoDoo Voodoo Well-Known Member

    I have the latest 7-23 and chrome is laggy and YouTube is a mess. The radio does seem to work better. Don't know why but signal is better. The way the icons move around is cool. If you want the latest version you have to go to droidhive. He seems to be releasing it there. A couple of annoying tweaks but it is really close.

  18. rehpyc

    rehpyc Well-Known Member

    That must be it.. I'm running an older version, 7/21 I believe. Chrome and YouTube work fine.
  19. Travisimo

    Travisimo Well-Known Member

    I've been on build 7/23 of the cm10 rom for close to 24 hours now. I've used the phone quite a bit during that time, and will continue to add to my observations regarding performance and bugs. Just for reference, here are the specifics of what I'm running and what steps I took up to this point:

    - Rooted my phone (stock rooted)
    - Installed the K-Exec CWM recovery via the EZ-Recovery app (downloaded from DroidHive), but I rebooted to recovery by using terminal
    - Wiped data, cache, dalvik, formatted system
    - Installed cm10 7/23 build
    - Installed gapps 7/15 (DroidHive)
    - Successfully rebooted to OS
    - Installed Titanium and individually restored missing apps (NOT system data)
    - Installed Nova Launcher and my backup of it's settings and home screen

    Here are my current observations after running cm10 for 24 hours:

    1) DATA. 4G LTE is working fantastic! When I'm in a 4G area, it is working at least as good as on stock. However, when I move to a marginal area or an area with only 3G, I am getting erratic behavior. The bars will go gray with no 3G/4G symbol and I will lost data connection for a few seconds. Then 3G will show up but my signal strength will fluctuate between half-way decent (-90 to -100) to horribly incorrect (-200 to -250). The bars while on 3G will go from zero to 5 and then back to zero again erratically. Sometimes it'll stay the same for a while, but it is obviously either having trouble staying connected or something. I can normally still use data, but it's slow and sometimes cuts out. When I return back to a 4G area, all is well again. I still have IMEI, but I have no phone number (unknown) . I thought I read a fix for that - is there???

    2) Bluetooth. I use BT headphones all the time, so this was important to me. Unlike some other reports, BT seems to be working fine. I use Doggcatcher for podcasts and they play fine through my headphones. Pandora also works fine. And Google Music works fine. Ford Sync also works fine for A2DP (not sure about phone because I don't use that profile). Bluetooth DUN for tethering does not seem to work at all.

    3) GPS. All aspects of GPS seem to be working great. Location locks on right away. Maps & Navigation work great.

    4) Google Now & Voice Search. I had previously used both on my Galaxy Nexus running Jelly Belly, so I knew what to expect here. Upon first bootup, the Voice Search would not work (just said Initializing). It started working after I made a phone call. I have not rebooted since then, but I read you have to make a phone call after each reboot to get it to work. I am able to launch Google Now by clicking the Google Search bar or by holding the Menu button down. However, both of those methods open the keyboard or mic when launching Google Now. I'm not sure how to open Google Now to the main screen without starting a search right away. On the GNex, you just swipe up from the Home button, but that obviously doesn't work on the GS3. The only way I can do it without opening the keyboard or mic is to click on a notification in the notification bar (which is not always there for Google Now). Anyone know how to open Google Now without performing a text or voice search (when you just want to see your cards, for example)???

    5) Camera. At first boot, the camera locked up after the first photo and would not work again. I extracted the Gallery2.apk from the T-Mo preview version of cm10 and installed that and now the camera works (somewhat). I can take photos, no video like the other reports. It's a messy fix, but it makes the camera somewhat usable for now. I can still take photos for my Foursquare checkins or FB, so I'm ok for now.

    6) Battery Life. Seems to be about the same as when I was on stock TW, with the exception of some increased usage when I am on 3G and experience the erratic behavior I described. The phone will also get warm, presumably because it is searching hard for signal. On stock Touchwiz, this rarely happened. So once they (hopefully) get the data issues worked out, this will be running at least as long as stock.

    7) JellyBean. JB is great and a definite improvement over ICS or TW. No, we don't have any of those Samsung customizations but I don't miss any of them. In fact, I am greatly relieved NOT to have those stupid status bar icons for GPS, etc. The status bar is nice and clean now, as is the notification bar. No more WIFI nag notification or popup (yay)! No more having to disable bloatware.

    IS THIS A DAILY DRIVER? That depends on YOU. I'm going to stick with it now, as I figure it can only get better with each update (unless it introduces new bugs, lol). The erratic 3G data thing is probably my biggest issue right now, but luckily I'm on 4G most of the time in my area. I can live with the camera. If Bluetooth wasn't working, I'd probably go back because I listen to podcasts at work almost every night. I use GPS a lot too, so glad that's working. IN SUMMARY, it just depends on what your daily needs are for the phone. I'd also be concerned if this was my only phone because of the IMEI risk, but I have the GNex as a backup.

    Hope this helps anyone who is watching and waiting, or those who like to compare notes! :D
    _Aardvark, jbdan, YankeeDudeL and 2 others like this.
  20. durarian

    durarian Well-Known Member

    Seems the CM10 post was taken down, guess that puts off my interest in flashing to it and potentially saves my phone! lol
  21. UNDERT0W

    UNDERT0W Well-Known Member

    You can back up your IMEI with a adb command promp.
    "You need to do this on a rooted phone, it's been tested only with root66. You need USB debugging on and adb on your computer.

    adb shell
    dd if=/dev/block/mmcblk0p11 of=/sdcard/efs.sbn
    (exit adb)
    adb pull /sdcard/efs.sbn

    DD is a linux utility that can be used to copy data from point a to point b and many, many ways. What we did here is copied the EFS partition to a single file (and then copied it to your PC). The efs.sbn file was about 13.6mb, but I've heard reports as low as 10mb. We can reverse this process to restore as well:

    adb push efs.sbn /sdcard/efs.sbn
    adb shell
    dd if=/sdcard/efs.sbn of=/dev/block/mmcblk0p11

    I keep a backup on my external sdcard and on my computer. cm10 works fine but make sure you go into "development" and clock your cpu back down because when you first flash it its set to like 1800 which can cause force closes. I put my back down to 1512 when running this rom. I like the unofficial cm10 but it just doesn't have all the features that I like in stock, but it does allow you to customize more like the notification icons.
  22. cp1

    cp1 Well-Known Member

    I'm not sure where the post went, but the latest file is here:
    Directory index
  23. nateap87

    nateap87 Well-Known Member

    So I just rooted my phone. Is getting cm10 as simple as flashing cwm through ROM manager then just flashing the ROM?
  24. Rolo42

    Rolo42 Well-Known Member

    If ROM manager supports kexec/dual-booting, yes. If not, no.

    The reason is that CM10 uses a custom kernel and that cannot be flashed to the boot.img (on VZW phones) where its supposed to be; instead it must be flashed to recovery.img.

    People are filing complaints with the FCC over this.
  25. nateap87

    nateap87 Well-Known Member

    Well it gives me the option to flash cwm. Should I not do it?

Share This Page