[OFFICIAL]CM10.1.3 Release for D2VZW GSIII (OP updated 9/24/13)

Search This thread

JohnnyTToxic

Senior Member
Apr 9, 2010
93
29
Chicago

Attachments

  • Screenshot_2013-06-27-15-39-50.jpg
    Screenshot_2013-06-27-15-39-50.jpg
    29.3 KB · Views: 576

apacseven

Senior Member
Aug 10, 2011
499
163
Yes of course, I always do.

I've had this problem before too. It has nothing to do with "clean install". My situation ended up being related to a widget, can't remember if it was beautiful widgets or HD widgets. So if you have widgets on your homescreen, that could be where its coming from. Fire up BetterBatteryStats (theres a free copy here on the forums) and see whats causing the wakelock.
 

tehloxely

Senior Member
Nov 9, 2010
380
40
I would like to flash another kernel, but if I don't like the one I flash, how would it be possible to flash the stable release one?
 

SomeGuyDude

Senior Member
Jun 7, 2010
1,250
218
For the S3? MROM without a doubt. I'm running it now and frankly won't do any more flashing elsewhere. I'm keeping an eye here though because I like CM and am curious how the full stable release is once invisiblek gets the issues ironed out.
 

JPD19

Senior Member
Jul 16, 2008
58
1
Hey, the latest "stable" Rom 10.1.0.1 is not so stable. One of the key apps, the dialer, does not work. Once a call is placed, the keypad is non-functional. You can't even hang up the phone unless you reboot. The notification bar always says "unknown" as the caller ID, and the hang up function from notification bar also does not work.

This is not an issue with KT747 kernal compatibility with the new stable CM ROM. I reinstalled 10.1.0.1 without custom kernal, and the same issue can be recreated. I'm on MB1.
 
Last edited:

brockkk

Senior Member
Aug 29, 2010
403
87
Hey, the latest "stable" Rom 10.1.0.1 is not so stable. One of the key apps, the dialer, does not work. Once a call is placed, the keypad is non-functional. You can't even hang up the phone unless you reboot. The notification bar always says "unknown" as the caller ID, and the hang up function from notification bar also does not work.

This is not an issue with KT747 kernal compatibility with the new stable CM ROM. I reinstalled 10.1.0.1 without custom kernal, and the same issue can be recreated. I'm on MB1.

Works perfectly fine for me. Sounds like user error.
 

JPD19

Senior Member
Jul 16, 2008
58
1
Works perfectly fine for me. Sounds like user error.

Really? hmmm...I flashed back CM 10.1.0 and the issue resolved. I'll try reflashing 10.1.0.1 and see if I can recreate the issue. If so, it's got to be the new ROM.


ADDENDUM:
CM 10.1.0.1 for sure does not have a working dialer. I reflashed 10.1.0.1, and the same issue occurred. Back to 10.1.0!
 
Last edited:

AudiTuner

Member
Aug 4, 2010
34
2
Hey, the latest "stable" Rom 10.1.0.1 is not so stable. One of the key apps, the dialer, does not work. Once a call is placed, the keypad is non-functional. You can't even hang up the phone unless you reboot. The notification bar always says "unknown" as the caller ID, and the hang up function from notification bar also does not work.

This is not an issue with KT747 kernal compatibility with the new stable CM ROM. I reinstalled 10.1.0.1 without custom kernal, and the same issue can be recreated. I'm on MB1.

Same issue here. :(
 

Top Liked Posts

  • There are no posts matching your filters.
  • 51
    Post development questions/logcats etc here. Post "my data doesn't work" (after reading the OP) in the Q&A thread. The mods don't like the developers thread being filled with these user questions, and it's contrary to the goal of this board.

    Read this post from our very helpful moderator if you still have any questions. I'll keep both OPs updated. I try to install every nightly and read all of the 10.1 threads. If anything is missing please PM me.

    Q&A thread: http://xdaforums.com/showthread.php?t=2071252

    10.1.3 has been released.

    As for all recent releases, please make sure you are on the MF1 modem


    cmlogo.png

    Cyanogen Mod 10.1.0 Release is now available:
    http://get.cm/?device=d2vzw

    Huge thanks to the CM devs! Pop on over to http://www.cyanogenmod.org/ and make a donation (mouse over "Community" at the top right then select "Donate to us") if you'd like to help support the CM project!

    cm101.png



    Anyone looking for mastamoon's build with his tweaks, reverts, and cherrypicks - it was moved to Android Development. Here is the link! http://xdaforums.com/showthread.php?t=2094251


    Rooting, flashing, installing roms, following any instructions below, will void your phone's warranty and there is a chance (however small) that you'll screw up and permanently break your phone. Anything you do to your phone in violation of the warranty, insurance, or anything else is at your own risk!



    CyanogenMod June 24th, 2013

    http://www.cyanogenmod.org/blog/cyanogenmod-10-1-0-release

    CyanogenMod 10.1.0 Release

    Tonight we are ending the Release Candidate phase and pushing CM 10.1.0 to general release.

    The files will be landing on our servers as they complete the build process. The list of devices will be in line with the devices that have received release candidates to-date. At this time, we do not plan on incorporating devices that did not receive a RC into this release. Also absent from this release are Tegra 2 powered devices and many of the Exynos based Samsung devices. We will provide a status report for these devices later this week.

    Next on deck

    With the 10.1.0 code finalized, we will return to our M-release cycle and work towards adding additional functionality and features; including the new Privacy Guard feature, which was merged into the nightlies today.

    There are many new and exciting things planned for the remainder of the year, just wait and see what we will do next!

    -The CyanogenMod Team

    -+-+-+-+-+-+-+-+ OFFICIAL DOWNLOAD LINK -+-+-+-+-+-+-+-+

    http://get.cm/?device=d2vzw


    -+-+-+-+-+-+-+-+ NIGHTLY CHANGE LOG -+-+-+-+-+-+-+-+

    App from invisiblek: https://play.google.com/store/apps/details?id=com.invisiblek.cm.nightlies

    Or: http://10.1.cmxlog.com/?device=d2vzw


    -+-+-+-+-+-+-+-+ GUIDE ON HOW TO ROOT AND FLASH -+-+-+-+-+-+-+-+

    http://xdaforums.com/showthread.php?t=2046439


    -+-+-+-+-+-+-+-+ HOW TO BACKUP AND RESTORE YOUR IMEI -+-+-+-+-+-+-+-+

    http://xdaforums.com/showthread.php?t=1852255&highlight=nvbackup


    -+-+-+-+-+-+-+-+ OFFICIAL GOOGLE+ -+-+-+-+-+-+-+-+

    https://plus.google.com/+CyanogenMod/posts


    -+-+-+-+-+-+-+-+ OFFICIAL GOOGLE+ COMMUNITY -+-+-+-+-+-+-+-+

    https://plus.google.com/communities/107373456059326217974


    -+-+-+-+-+-+-+-+ KNOWN / REPORTED ISSUES -+-+-+-+-+-+-+-+

    On the 10.1.3 RC: (updated 7/18)
    1: Only use the MF1 AIO file available here.

    2: If you cycle bluetooth off and on it may get stuck. You need to reboot to resolve the issue.

    3: Verizon FIOS app crashes

    4: BT headsets don't work with the Skype app

    5: If you set up a phone number to include pauses (like your voicemail PIN) the keypad wont register any other touches during that call.


    Many other problems are fixed by simply re-flashing the same rom file over itself.

    Please PM repeatable issues from the release to me. Post a logcat in the developer thread or a JIRA ticket if you expect it to get fixed.


    -+-+-+-+-+-+-+-+ SPECIAL NOTES -+-+-+-+-+-+-+-+

    1. To enable Developer Options: Menu > Settings > About Phone. Tap build number 7 times to unlock Developer Options

    2. Photosphere: This feature is not offered on non-nexus devices

    3. There are a lot of questions about how CM10.1 moves your files to sdcard/0/ folder. This is to support multi-users. If you flash back and forth between a non-4.2 ROM and CM10.1 (which is 4.2) you'll end up with sdcard/0/0/..etc since the upgrade to 10.1 moves your folders into a new /0/. You can safely move your files out of /0/ back to your sdcard if you're on CM10, or back to the first /0 folder if you're on CM10.1.

    4. Don't update from CM10 to CM10.1 using the built-in cmupdater. Update in recovery for the first flash from CM10 to 10.1. Once on 10.1 you can use cmupdater.


    -+-+-+-+-+-+-+-+ INSTALLATION NOTES -+-+-+-+-+-+-+-+

    • CM can be flashed using CWM or TWRP. Only use the latest TWRP or CWM!
    • When you install CM10.1 your data will be moved to a new folder /0/ (this is to support multi-users).
    • Make sure you have the latest CWM or TWRP installed so that your recovery isn't confused by the new location of your backups. Official TWRP d2vzw or Latest CWM (scroll down to Samsung Galaxy S3 (Verizon))
    • GAPPS is not included in any CM download. You must flash a gapps zip if coming from another rom or when starting with a clean install. You do not need to flash gapps when 'dirty flashing' over a previous CM install. Download gapps here.
    • According to Cyanogen it is possible to flash CM10.1 over top of an existing CM10 installation. It is generally recommended to do a clean install if you run into any issues.
    • Always make a backup before you try a dirty flash or upgrade to CM10.1.


    -+-+-+-+-+-+-+-+ HOW TO INSTALL OVER CM10 -+-+-+-+-+-+-+-+

    • Consider backing up your IMEI if you haven't already (link)
    • If you use a lockscreen pattern disable it
    • Flash the latest CWM or Official TWRP d2vzw
    • Download a CM10.1 rom (nightly or unofficial) to your sd card
    • Download the latest gapps from goo to your sd card
    • Reboot into recovery
    • Make a backup
    • Wipe cache and dalvik (if you want)
    • Install CM10.1 zip
    • Install gapps
    • Reboot
    • After your phone boots go into Menu > Settings > Apps. Under "All" find "Clock", open it, and click "Clear Data"


    -+-+-+-+-+-+-+-+ HOW TO INSTALL FROM ANY ROM OTHER THAN CM -+-+-+-+-+-+-+-+

    • Consider backing up your IMEI if you haven't already (link)
    • Flash the latest CWM or Official TWRP d2vzw
    • Download a CM10.1 rom (nightly or unofficial) to your sd card
    • Download the latest gapps from goo to your sd card
    • Use an app like Titanium Backup or Mybackup Pro to backup your apps (if you want)
    • Use an app like SMS Backup+ to backup your text messages and call log (if you want)
    • Reboot into recovery
    • Make a backup
    • Wipe cache and dalvik (if you want)
    • Wipe Data/Factory Reset/System
    • Install CM10.1 zip
    • Install gapps
    • Reboot
    • Reinstall Titanium Backup/Mybackup Pro/SMS Backup+ and restore the stuff you have to have, but its better to reinstall things from the market if possible (keep in mind your backups will be located in sdcard/0/) (if you want)


    -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    I am not a developer, I have no direct association with the CM project, I am just a community member. I will do my best to maintain this thread. Please PM me with any OP suggestions!
    29
    Thread cleaned!
    I will tolerate no trash talking of any developer
    If you want to confront Mr. Goodman do it on Anthrax where he can defend himself
    DO NOT Bring this crap on XDA
    Please report posts and do not engage members
    I promise my intentions are only for mutual respect of both sites and will deal with instigators severely!
    Thank you for your cooperation
    Friendly Neighborhood Moderator
    26
    I Fixing Data

    If you flashed a CM10.1 nightly and are stuck at roaming/activating or don't have data, try any of the following (in order of simplicity):

    (1) Go into Mobile Settings - Mobile Networks. Change CDMA mode to RUIM, go into airplane mode, come out, it should login to 4g in a minute. You can wait for activating to time out then skip or not install gapps until after setting the correct mobile network setting.
    (2) Power down. Take out the sim card and reboot. In mobile network settings set roaming to auto and the subscription to RUIM/SIM, turn off the phone, pop the sim card back in, boot up.

    If none of those work this will work for sure:

    Hallelujah! My phone has voice AND data back! (thanks to the posters above)

    How to get voice AND data back:
    1.) Odin the root66.tar file from http://xdaforums.com/showthread.php?t=1762204 (the torrent version downloads MUCH faster)
    2.) Open the dialer and enter *2767*3855#
    3.) DONE! Voice and data should be fixed (it fixed it for me at least, and I had tried EVERYTHING else)

    From there just Odin back to Jellybean following http://xdaforums.com/showthread.php?t=1974114 and you're golden...

    That's how to get back to working condition without fail... Might want to post similar instructions in the OP as dirty flashing did nothing for quite a few of us.

    -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    Fixing GPS
    GPS - it HAS been working for 98% of builds, however if you cannot get GPS to connect, possibly due to dirty flashing, the following has worked every build for me: Settings - Apps - downloaded - GPS Status - clear cache, clear data, force stop. Then open gps status back up, let it sit with gps on for a moment and see if it starts searching for signal again....if this still doesn't work (sometimes) - settings - apps - all - google services framework - clear data. This has worked 100% of the time but I try to avoid it because if you do this, you need to go open back up the play store and see if it still connects. If not, recovery - clear cache, clear dalvik usually takes care of that.
    Clean install of builds has given me 100% functional gps every time.

    -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    Unofficial CM10.1
    (I know several people have posted these, I looked quickly and only found mastamoon's which is also what I am running, I'll happily post more here if I find them).



    25
    CLOSED FOR CLEANING

    BTW, Those of you who report these kind of threads you should heed the rules too...

    This thread has been repeatdly reported... Therefore I will continually monitor it and infract and delete ALL posts non-development related... I already warned everyone here: http://xdaforums.com/showpost.php?p=35887882&postcount=680 and I asked NICELY.

    If you DO NOT know what the fifference between a development question and non-development question is you probably shouldn't post in this thread.... LAST WARNING...

    VeNuM

    Update, I cleaned a couple of pages, but theres just to much to purge... If your post was deleted this is YOUR CLUE that it is NON-Development related.

    1. Stop asking questions here (its not the place. Go to Q and A)

    2. Stop posting what works and doesn't work here (General is for this and point 3 below)

    3. If you have issues stop posting here without a logcat (its useless and doesnt help the developer fix ANYTHING)

    4. The op has all your answers in the first to posts. Go there to find them. If you can't find it go somewhere else.

    5. Please read this: http://xdaforums.com/showpost.php?p=9227274&postcount=1 it will help you understand how to give CONSTRUCTIVE feedback. Its also in my signature.

    6. Another good thread to read: http://xdaforums.com/announcement.php?a=81 please pay particular attention to number 1, 2.5, 2.6 and 15...

    This will remain closed for a short time to let what I've written SINK in...
    24
    This ROM is the farthest thing from stable, but that's the case with all AOSP Roms for the GS3.

    Sent from my SCH-I535 using Tapatalk 4 Beta

    ROFL
    "The farthest thing from stable" (sorry just had to requote that)
    ROFL (sorry just had to reiterate that)

    Let's hear what's not so stable about it. Let's also see some logs of errors. If you don't provide either, you don't belong in this thread.

    AOKP isn't bad.. It's the only aosp tree based ROM I will use

    Sent from my SCH-I535 using Tapatalk 4 Beta

    Please go to the aokp thread and let them know how much you love their rom. Posts like these have no business in this or any development thread.