1.24.13 nightly has a working Global/GSM. Any newer than that, CM has a broken Global/GSM compatibility.
1.24.13 nightly has a working Global/GSM. Any newer than that, CM has a broken Global/GSM compatibility.
Loud beeping while ending call
Anyone know if there's a fix for the loud beep that comes from the speakerphone when ending a call? It's the only thing stopping me from using this as my daily driver. Thanks:fingers-crossed:
Anyone know if there's a fix for the loud beep that comes from the speakerphone when ending a call? It's the only thing stopping me from using this as my daily driver. Thanks:fingers-crossed:
Not sure if this thread is being monitored or not anymore. Can't blame the CM people if not, there's a lot of drift here!
I've been getting a lot of Sleep of Death recently. It happens specifically when I boot the phone from scratch. The phone will go through the spinning CM logo, then go into the lockscreen, then if I let it go to sleep it doesn't wake up. It's pretty frustrating. I'm currently on the latest nightly, stock kernel. It happened to me on 2/17 too (I skipped the ones between because I was travelling). If I unlock the phone immediately then this doesn't happen.
I used to get SOD, but it would respond after I hit the power key, this doesn't respond and needs another battery pull.
I clean wiped about 3 weeks ago- I mean completely clean, flashed a stock image, wiped internal memory completely.
I've been getting a lot of Sleep of Death recently. It happens specifically when I boot the phone from scratch. The phone will go through the spinning CM logo, then go into the lockscreen, then if I let it go to sleep it doesn't wake up. It's pretty frustrating. I'm currently on the latest nightly, stock kernel. It happened to me on 2/17 too (I skipped the ones between because I was travelling). If I unlock the phone immediately then this doesn't happen.
I used to get SOD, but it would respond after I hit the power key, this doesn't respond and needs another battery pull.
I clean wiped about 3 weeks ago- I mean completely clean, flashed a stock image, wiped internal memory completely.
If you stay with the CM kernal the minimum cpu freq should be set at 384 MHz and I honestly don't know the voltages used. When I flash a kernal I always set the minimum cpu frequency at 384 MHz as well as keep voltages above 1000 MHz. Maybe try setting the minimum cpu frequency at 486 MHz...just a thought...eat the meat & throw out the bones.
Re: [Official] CM 10.1 Q&A Thread - OP updated 2/17
Anyone know why once in a while when quick pressing the home button it behaves as if you long pressed it and brings up recent apps screen? Reboot fixes it for a bit.
Sent from my SCH-I535 using xda premium
Anyone know why once in a while when quick pressing the home button it behaves as if you long pressed it and brings up recent apps screen? Reboot fixes it for a bit.
Sent from my SCH-I535 using xda premium
Re: [Official] CM 10.1 Q&A Thread - OP updated 2/17
I have the same thing going on as well. I've set my minimum clock to what the post below yours stated. I hope this is resolved soon. It is obviously related to the kernel commit in one of the latest nightlies.
Sent from my SCH-I535 using Tapatalk 2
I have the same thing going on as well. I've set my minimum clock to what the post below yours stated. I hope this is resolved soon. It is obviously related to the kernel commit in one of the latest nightlies.
Sent from my SCH-I535 using Tapatalk 2
This has been around for a while. Doesn't quite seem to be on anyone's radar yet.
I'm sure that it is important to the CM team... Just not as high a priority as other bugs. It will get fixed eventually.
According to Cyanogen on Google+, there is an official procedure for reporting problems but it is outside my technical expertise. Hopefully someone will report it using their system. I know they are very busy so they probably don't respond to reports here. I assume this is more for user-to-user assistance.
So I hope someone can get it on the radar.
Re: [Official] CM 10.1 Q&A Thread - OP updated 2/17
The devs are very aware of this. IIRC correctly invisiblek said it's a kernel issue and is fixed in an updated kernel that is still a work in progress.
I've had the sleep of deaths with the most recent nightlies as well so if anyone is thinking of flashing I'd give it a few more days. 2/21 seems pretty stable though so I've been sticking with it
Sent from my SCH-I535 using xda app-developers app
The devs are very aware of this. IIRC correctly invisiblek said it's a kernel issue and is fixed in an updated kernel that is still a work in progress.
I've had the sleep of deaths with the most recent nightlies as well so if anyone is thinking of flashing I'd give it a few more days. 2/21 seems pretty stable though so I've been sticking with it
Sent from my SCH-I535 using xda app-developers app
Good to see. It's one of those things that's minor enough to get put behind, but just annoying enough to get people to talk about it.
I'm running 2/22 and haven't had any SOD's since moving to 10.1 on 1/5.
Another bug that I've noticed is that on Tesla Unread PlugIn, the email unread notification for the stock email app will stop working - meaning that the notification bar will indicate that I have a new email, but the email icon itself will not indicate that there is an unread new email.
I found that rebooting the phone appears to correct this issue.
I found that rebooting the phone appears to correct this issue.
Re: [Official] CM 10.1 Q&A Thread - OP updated 2/17
Whatever happened my phone died from 33% battery. Insta-drained Idk what happened. I think this might be related with the kernel.
Sent from my SCH-I535 using Tapatalk 2
Whatever happened my phone died from 33% battery. Insta-drained Idk what happened. I think this might be related with the kernel.
Sent from my SCH-I535 using Tapatalk 2
Re: [Official] CM 10.1 Q&A Thread - OP updated 2/17
Any help on this? It's making the ROM pretty much useless for me...
Any help on this? It's making the ROM pretty much useless for me...
Re: [Official] CM 10.1 Q&A Thread - OP updated 2/17
+1 here on the wifi issue. I've found when I get the "failed to connect" message, simply turning the screen off and back on fixes the problem temporarily.
Sent from my SCH-I535 using xda premium
+1 here on the wifi issue. I've found when I get the "failed to connect" message, simply turning the screen off and back on fixes the problem temporarily.
Sent from my SCH-I535 using xda premium
Re: [Official] CM 10.1 Q&A Thread - OP updated 2/17
The standard answer when you have a problem most people don't: Wipe everything, clean install, don't restore apps or settings. See if that fixes it.
I personally haven't had that problem and don't remember anyone but these last two posts mentioning it.
Tapatalk via CM10.1 Galaxy S3
The standard answer when you have a problem most people don't: Wipe everything, clean install, don't restore apps or settings. See if that fixes it.
I personally haven't had that problem and don't remember anyone but these last two posts mentioning it.
Tapatalk via CM10.1 Galaxy S3
Re: [Official] CM 10.1 Q&A Thread - OP updated 2/17
I have been using Juice Defender Ultimate for a while now (since my Dinc). Turns out disabling it squashed my wifi problem. Strange that it didn't cause an issue on CM10. But looks like that's it for my problem.
Sent from my SCH-I535 using xda premium
I have been using Juice Defender Ultimate for a while now (since my Dinc). Turns out disabling it squashed my wifi problem. Strange that it didn't cause an issue on CM10. But looks like that's it for my problem.
Sent from my SCH-I535 using xda premium
Re: [Official] CM 10.1 Q&A Thread - OP updated 2/17
I tried disabling JD for a whole day to see if that made a difference. No change...
I did change one of the settings within Wifi to not try to use as little battery when wifi is on and that seems to help keep wifi on a bit longer, but then it all goes to hell when it disconnects.
Sent from my SCH-I535 using xda app-developers app
I tried disabling JD for a whole day to see if that made a difference. No change...
I did change one of the settings within Wifi to not try to use as little battery when wifi is on and that seems to help keep wifi on a bit longer, but then it all goes to hell when it disconnects.
Sent from my SCH-I535 using xda app-developers app
Re: [Official] CM 10.1 Q&A Thread - OP updated 2/17
You may want to mess with the wifi region or something like that in the network settings on your phone? Or maybe channels on your router. Also I have heard on other devices that sometimes 5GHz networks have issues.
You may want to mess with the wifi region or something like that in the network settings on your phone? Or maybe channels on your router. Also I have heard on other devices that sometimes 5GHz networks have issues.
This was actually an issue with Tesla Unread and 4.2.2. The plugin updated today and fixed the problem for me.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
13Post 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.
Development thread: http://xdaforums.com/showthread.php?t=2053799
10.1.3 has been released.
As for all recent releases, please make sure you are on the MF1 modem
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!
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!
-+-+-+-+-+-+-+-+ 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: One channel audio on headphones.
6: Low recording volume using the camcorder.
7: If you set up a phone number to include pauses (like your voicemail PIN) the keypad wont register any other touches during that call.
On the latest nightlies: (updated 7/18)
1: If you cycle bluetooth off and on it may get stuck. You need to reboot to resolve the issue.
2: Verizon FIOS app crashes
3: BT headsets don't work with the Skype app
4: Low recording volume using the camcorder.
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!10
I'm starting a petition for you to write your own animation. If I get 2 more signatures, you have to do it. +1's and Thanks to this post count as signatures. Contract is binding and non-negotiable. You are as obligated to perform your end as the CM10.1 devs are to listen to your petition. Petition open.5
Actually, I'm not sure if this is fixed in 3.4 or not. I usually reboot too often to see this (for me it would take like a day for the problem to surface)
It's most definitely on the radar, just not high priority. I'll try to keep it running for an extended period of time and see if this problem comes up. (But the weekend might be a bad time to make a promise like this =P)
The problem with 90% of these "one-off" issues that people have is that there are too many variables. My suggestion, if you are running into an unreported or obscure problem, is to wipe data/factory reset, reflash your rom and official gapps only. No custom stuff (inverted gapps, custom kernels, etc) and boot up, don't install any apps, and see if the problem is still there. When you start replacing system files with "unofficial" ones (gapps, kernel/modules) many different things can happen that are tough to account for. This goes for installing root apps too, or apps designed to "monitor" your device for certain things. Who knows WTF a root app is doing mucking around on your device, and these battery monitor, tasker, etc apps can cause wakelocks and other unintentional problems. Especially since you don't know how an app for say, ICS, would play with JB 4.2.2, and who knows if the app dev has updated to account for any changes to JB. I don't mean to bash anyone's app or kernel, I'm sure most of them run perfectly fine, but getting to the root cause of a problem has to start with eliminating all external variables.
Ok, enough of my long-winded rants.
Regardless of what you have running/flashed/etc, make sure you are posting relevant logcats and dmesgs, especially on these odd problems that nobody else seems to have. If you don't, your post isn't much help to anyone. (Hint: use pastebin!)5http://invisiblek.org/sch-i535/roms/cm10.1/cm-10.1-20121229-UNOFFICIAL-d2vzw.zip
Has LockClock included:
https://plus.google.com/105849811393167071979/posts/KBHPeMRXpGo
Also the gps squash from caf:
http://review.cyanogenmod.org/#/c/29349/
Sync'd about 15-20 minutes ago4For those of you having trouble with the Lock Screen Clock, here is what works to get it up and running. First you go into system settings (settings), then under the "interface" section you will hit "system". There you will find the settings for "Lock clock widget". After you have set up all the preferences, get your phone back to the lock screen (I found that going to your home screen and then hitting the power button is the easiest way). Now that you are sitting at a black screen, hit the power button, or home button, to wake the screen. Immediately upon doing that, you will see the two big gridlines appear on each side of the screen, the subtle prompt to show you there are screens to each side you can swipe. Swipe the screen from left to right. You will see a big "+" in the middle of the screen. Now, while at that screen with the "+", swipe back from right to left and it will take you back to the main lock screen. As soon as you hit the main lock screen, long press the screen and drag it up into the garbage can. If you correctly deleted the home lock screen, it will now automatically advance you back to the big "+" screen. Hit the big "+". You will now see you have a few options. The third one down will be "Lock Clock". Hit that and you will now have it as your lock screen. I will however say that it is a little bit buggy right now, especially if you are trying to get appointments to show, but it does work!
I am on the latest OFFICIAL 10.1-20121231-NIGHTLY, flashed dirty from yesterdays nightly. I will be doing a full wipe and clean install later today to see if the anomalies with the new lock screen widget persist or go away. What I am seeing is that when you add the lock screen widget, it will show your calendar event, but after the screen goes to sleep, the appointments are no longer on the widget when you wake the screen back up. The weather is there, and the battery state is there right below the weather, but no appointments. If I swipe that screen showing weather and battery state back and forth from the "+" screen, the appointments show back up, but the battery state is missing. Also, turning the battery status off on the lock screen doesn't change it from not showing the appointments. I think that should be enough info to point someone to a fix.
I hope that helps!
Scott
