[Official] CM 10.1 Q&A Thread - RC2 (OP updated 5/24/13)
Post development questions/logcats etc in the development thread. Post "my data doesn't work" here (after reading the OP). The mods don't like the developers thread being filled with these questions, and it's contrary to the goal of that board. I'll keep both OPs updated.
RC2 is out. The camera and 1-channel audio issue should be resolved. Download via cmupdater, get.cm or my google drive mirror
Huge thanks to the CM devs! Pop on over to http://www.cyanogenmod.org/ and make a donation (scroll to bottom of the page) if you'd like to help support the CM project!
I am not a developer, I'm just a community member maintaining this post.
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!
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 CM10 and CM10.1 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.
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.
As you may have noticed, we started updating some devices from cm10 (Android 4.1) to 10.1 (Android 4.2) during the weekend. The upgrade process has been tested extensively for the older devices (manta and mako didn't have that problem since they started out with 10.1), so you should be able to update directly without losing any data.
The single application known not to work is the Clock: Our changes to 4.1's clock to add the Stopwatch and Timer in CM10 aren't compatible with Google's own implementation of those features in 4.2 (which we're using in cm10.1); If your clock starts crashing after upgrading to 10.1, simply go into the Settings -> Apps menu, choose Clock from the All tab, and hit "Clear data".
Over the weekend we extended the release of nightlies for CM 10.1 to additional devices. These include:
# All Galaxy Nexus Variants
# All Nexus 7 Variants (including the GSM enabled 'tilapia')
# Transformer Infinity (tf700)
# Galaxy Tab 2 7.0
# Galaxy Tab 2 10.1
# Galaxy S (select models)
# Galaxy S II (select models)
# Galaxy S III (select models)
Now this means a lot of you will be upgrading from CM 10.0 and are likely to run into some common items when upgrading. Here are some of the major considerations:
# CM 10.1 is based on Android 4.2.1. Any and all proprietary applications that you have installed outside of CM should be updated to their 4.2.1 counterparts. Do not use the 4.1 versions of proprietary applications, else you will experience difficulties.
# Do not use the CyanogenMod Updater to go from 10.0 to 10.1. While you will have a functional rom, due to the 1st bullet point, you will be left without your proprietary applications and their data. We highly suggest performing the initial install manually via recovery (flashing CM and your addons). Once you are on 10.1, you can use the CM Updater as per normal.
# You do not need to wipe when updating to 10.1 if coming from and earlier CM version. However, as we mentioned in the weekend's PSA, users updating (instead of wiping) will experience a conflict in the application data for the Clock app. You are advised to clear this apps data on first boot of 10.1.
# Another item to note is that the support for the 10.0 feature that allowed for an expanded number of targets on the pattern lockscreen is not in 10.1. If you use this lockscreen, disable it before updating to 10.0.
# Finally, we always advise that you create a backup before any update. Do note, however, that due to Android 4.2 changes to support multi-user mode, your backups will automatically be transferred to /sdcard/0/[backup folder]. Remember this when attempting to restore 10.0.
Make sure you select your device using the wrench in the upper right, it'll probably error right away because I haven't fixed it up all the way yet and it's looking for a device that doesn't have 10.1 yet to begin with.
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.
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)
If at the end of this process you boot up and are stuck at activating or are roaming, see post #2.
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.
I'll try to post logcats later but seems like I'm having gps issues. Tried what invisiblek suggested as well as the agps flash test going around. Nothing seems to work. It just won't get a lock.
I'm currently on 12/28/12 build, and my Google Music player seems unresponsive. I get no errors, just when I try to play a song, it doesn't play, and if I try to increase/decrease phone's volume via side buttons, my S3 freezes completely. Does any else encountered this?
PARAVEX Project strives to accomplish a better Android experience.
I'm currently on 12/28/12 build, and my Google Music player seems unresponsive. I get no errors, just when I try to play a song, it doesn't play, and if I try to increase/decrease phone's volume via side buttons, my S3 freezes completely. Does any else encountered this?
Known issue with the 12/28 build. I dirty flashed the 12/27 build over the top of 12/28 and Google Music, Apollo, and Pandora are working again. Just a suggestion although I'm sure that the CM team will figure it out within a couple of days.
Sent from my SGS3 using Tapatalk 2.
Retired: OG Droid, DX, Thunderbolt, Bionic, GNexus (donated to wife)
Current Device: VZW Samsung Galaxy S3 / CM10.1
Twitter - @PerCompLLC
Thanks for the new spot!
Just an idea..... wouldn't it be nice if, when people posted questions, that they also supplied basic configs as well. I see so many wasted posts chasing down info just to try to be able to help. If you did a clean install, state it. If you did dirty, state what you came from. If you are custom radio,rpm,kernel,recovery version, or anything else, put info with your question. For example, the YouTube issue... I did a wipe with clean install of todays CM 10.1 12/28 nightly, NO gapps at all, YouTube version 4.2.16, and I don't have any issue. My install/config will not match yours, but in the other thread we would have a dozen people going on about the issue, when noone has any info to base an answer off of... Posting my config info also answers other questions right off the bat, like "why didn't I get stuck in the activation process like many others"? SIMPLE, I don't ever use gapps.
It will make it way easier to get better and faster results if we follow the recommendations above.
Just my 2¢…
I just did a dirty flash via latest CWM recovery of CM10.1 12/28 over CM10 official stable and none of my data was moved from sdcard0 to "\0". All my files that were on my internal storage are gone... Anyone else have this issue? I didn't have this problem when I flashed unofficial nightlies before, but flashed back to CM10 stable for more stability. Now this...
APDroid's Tablet Talk - Text message on your tablet using Bluetooth or WiFi https://play.google.com/store/apps/d...pdroid.tabtalk
-------------------------------------------------Samsung Galaxy SIII - CM10.1 nightlies
Samsung Google Nexus 10 - CM10.1 nightlies
Asus Google Nexus 7 (Thanks APDroid)- CM10.1 nightlies
I'm on 10.0 still, wanting to switch to 10.1 but I use wireless tethering for my commute daily (supplying data for my Samsung Galaxy Tab installed in my dashboard). Can anyone confirm it works.? I read the op and saw what it says about it.
Anyone tried the old flash fix from 10.0 to get it to work secure?
After reading about Dan Rosenberg’s bootloader exploit for the Samsung Galaxy S 4,I … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?
Introducing XDA:DevCon – A Conference For Developers By Developers
>
[Official] CM 10.1 Q&A Thread - RC2 (OP updated 5/24/13)
Print
Email
[Official] CM 10.1 Q&A Thread - RC2 (OP updated 5/24/13)
View Profile
View Forum Posts
Follow on Twitter
View Facebook page
Anyone else have this issue? I didn't have this problem when I flashed unofficial nightlies before, but flashed back to CM10 stable for more stability. Now this...
Visit Homepage
Linear Mode
