yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] monkeysez:
Any way to get dialer codes working on CM11?

Or at least a list of working ones.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fr3d0x:
I found a bug,i dont know why this always happend, when i enable and disable wifi 4 times my cell always reboot at the 4 time,is wierd...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
1. Why?

2. Tried to reproduce bug. Didn't reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Agreed. Can't reproduce.

You also really didn't give enough info to make your post useful enough for anyone to help you. What ROM are your running? Date or release and 10.2 or 11? Also do you let it fully connect before toggling again or just hammer on the button 4 times? Where are you toggling it? Via settings menu or quick panel actions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fr3d0x:
im on the latest nightly and this happens during the day, if I turn off more than 5 times phone restarts,i toggle it in settings,quick panel and drawer and is the same always reboots,im have the i747M with the new modem of 4.3 rom, i dont hvae this problem on CM 10.2 only in CM 11
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Also on latest CM11 nightly. Modem isn't going to affect what the WiFi toggle does. I tried it in the quick panel and nothing happened. Try a clean flash. Thank you for clarifying, by the way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fr3d0x:
i did a clean flash and same problem, have to go back to cm 10.2..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
Why do you need to turn WiFi on and off so often?

Tried to reproduce and nothing happened.

Is WiFi working for you when its on.. And do you have cell data when its off?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] The Jack of Clubs:
how do you make the phone speaker ring when you have a bluetooth audio device paired and connected? or is that a bug that cant be fixed? on cm11. my brother keeps asking about this. he has a bluetooth headset, bluetooth headphones, and bluetooth on his car stereo, so something is always connected and now his phone never rings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
Weird issue on 20140102.

When i dial a number and push the call button, my signals goes from full 4 bars to empty and the call doesnt go thru. I've tried many calls SOME will go thru but most dont. I can receive calls perfectly fine tho.

I've done a full wipe and re installed 20140102, same issue.

I've installed an older CM11 (20131211) to test out and im not having this issue with this older one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
I had this issue too, I flash backed to 12/31 and its okay now. Im Rogers. Seems like most issues I have are specific to the I747M model.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
I am on Rogers with 747M too.

Just tried 20140103 and the issue is still present. I'm going back to 1231 for now. I don't mind nightlies that break some stuff but not being able to make calls is a bit much hehe :)

Hopefully it gets fixed quickly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I'm on the 01/03 nightly on an M variant phone and I don't have any problems. Just made a series of 5 calls and I did not experience what your are mentioning.

Just in case you didn't know and this may help you debug your system but our phones don't make calls over the LTE network. So if your phone is connected to LTE and you place a call, your phone will automatically switch to 3g to place it. Perhaps there are some funky settings with your APN or preferred network modes that aren't switching the phone to the right state to place the call.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jooced:
Does anyone else get extremely inaccurate GPS location with the latest few builds? Is there anything I can do to improve that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] monkeysez:
I have the exact same issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
I'm on the MK5 bootloader and baseband. Perhaps this is the issue? What baseband are you on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Same.

I don't make a lot of calls on any given day but to try and see if I have the same problem as you guys I have made about 20 calls this morning to a couple numbers and all of them went through no problems.

I also tried making calls while connected to LTE and 3G to start as well as making calls from my contacts list, by typing in the number in the dialpad directly and from the call log and none of them acted up for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
clean install removes this issue, but restoring data makes the issue come back... UGH.. have to reinstall everything sad face.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
When I first came to CM11 from 10.2 my phone would boot loop as soon as the lock screen came up. No matter what I did it would not boot. In the end I had to do a clean install even though others were able to dirty flash from 10.2 no problem. I was unable to restore any system data either as that would cause fits again. So there was something my phone was set up for that obviously wasn't playing nicely with CM11. I think half the problem may be that not everything had(s) been forward ported yet so its possible my settings were trying to do something that CM11 didn't know how to handle. In the end I did a clean install and only restored my market apps and data. Nothing system related and it was fine.

Guess there is something similar in your case. Some setting somewhere isn't right. Maybe fiddle around a bit with some of the settings and see if you can get it to work.

I have uploaded my mobile network settings. Try comparing to see if anything is different.

Cheers and good luck.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Give it the Titanium Backup treatment. Best money ever spent. Backup all your apps + data, wipe everything, restore your apps and data. Still a bit of a pain to make your settings but at least you won't lose your apps data. Did that not long ago and re-installed my CM10.2 and I feel great. haha!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
Anybody having problems with Bluetooth on recent nightlies? Was working on 12/26 nightly, but I'm trying 1/02 Vanir and it's not recognizing my BT headset. I know this isn't a Vanir thread but Vanir team claims not to have changed anything related to Bluetooth from CM base.

EDIT: Since I'm new to BT headsets, I didn't realize I had to re-pair the headset with my phone after flashing a new ROM. So BT is working just fine for me now. Back on CM 10.2 I had no problem connecting to BT car audio, but haven't tried with a Kitkat ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liebowa:
Microphone issues w/nightly 20140103

Having the following issues w/lastnight's nightly (20140103). All testing was done on a cleanly wiped device, including cache/data, system and dalvik. Also, I did two fresh wipe/installs to verify it wasn't a fluke.

1.) Google voice typing does not work. Sometimes I get unable to contact Google at moment, but 90% of time it does not look like it's hearing any sounds.

2.) Sound records does not work at all.

So, seems like there are microphone/sound driver issues. even though voice calls work fine.

Anyone else NOT having these issues?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
I'ts not working for me at all. After like 10 fresh installs I cant get it to work. After a fresh install, without installing any other apps, calls dont work. I think this change http://review.cyanogenmod.org/#/c/56626/ is causing the problem for me and some other people.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Yes, mine is that I can't reconnect to car system, get out, back in car, etc. Also, giving me trouble on initial connect, saying no media, until I toggle it.

10.2 latest nightlies, were working the best since 10.0 November 2012.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Scratchy roboto voice is back on voice calls.

---------- Post added at 01:35 AM ---------- Previous post was at 01:34 AM ----------

Cm11 that is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I placed a call this afternoon whilst running the 01/03 nightly and it sounded fine to me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
On 0103 NIGHTLY and realized that it's now version 4.4.2... didn't have chance to test much but at least WiFi speed still sucked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Yeah, that's what I'm running.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bleedingthru:
M snap shot out guys im dl right now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Its been at version 4.4.2 for at least a couple weeks now if not more.

---------- Post added at 10:09 PM ---------- Previous post was at 10:08 PM ----------

Just remember that nothing magically works now just because it is called an M release. It will be the same as the nightlies we are running.

What it will however do is allow us to create JIRA tickets against it.

Open up the flood gates.....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bleedingthru:
Ya I know thay just being a dork over here lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
I had upgraded to CM11 but downgraded back to CM10.2 'cause I didn't like it that much...

Have they updated the intents menu in the latest nightlies, or is it the same ugly vertical list like a few weeks ago? I'm really surprised that Google would make it uglier than 4.2.2. I thought they were suppose to be going to something like this in KitKat?

Also, on GEL, can you modify # of rows, columns on the home screen?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adrock74:
My chromecast doesn't work on any app with this. Don't ask me why.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
Found out 0104 still has this issue and I'm on Rogers Wireless. I didn't notice this is previous NIGHTLY as I didn't make any call until today... and obviously there was no issue when answering incoming call.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
There is potentially a change coming in the next nightly that might fix the problem some of you are seeing. We don't know exactly what happened but there was speculation over a commit merged into the 01/01 nightly that messed things up and the commit that I'm referring too for the next nightly is a fix of that.

So be on the lookout for your call issues being fixed soon hopefully.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lessaj:
I haven't updated in a few days, anyone on Bell having any issues, or just Rogers?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
I forgot to come here and let everyone know that after flashing the M2 my phone calls work again. I dunno what fixed it but I'm just glad its working
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skim7x:
Running 10.2 and have noticed a consistent problem. While texting from the stock texting app, I go to the menu and select "insert contact information" to send a buddy another friend's phone number. The phone takes me to the contact list without issue. However, when I start typing in a name into the search box, Contacts always force closes. Anyone else have this problem? If I just scroll through contacts and select the contact, there are no problems, only when I search. If I search from the phone app (as opposed to while texting) there is no problem either. I did a clean install of 10.2 but still have the issue. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
Go to CM11, 10.2 isn't supported anymore.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
It wasn't fixed in M2. M2 is just a snapshot of the ROM at a particular point in time. Obviously the commit wasn't included in the snapshot perhaps because the line was drawn in the sand at Dec 31st and the commit that broke it didn't occur until Jan 1st. So it more like running an old nightly.

A good test would be to see if the expanded volume control panel option is available in M2 or not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Confirmed as happening even on the latest CM10.2 nightly. Scroll the list instead haha.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skim7x:
Haha yeah, scrolling isn't terrible with the index scroll bar... thanks for the reply!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
I'm on CM10.2-2013.12.06 and don't have that issue. I don't really have any bugs with this so never updated...or maybe it's the last CM10.2...not sure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
No it's definitely there. I thought mine didn't do it, but go in sms conversation with someone, press the menu button then insert contact details. Now it's really important that you type the name at the top, not scroll through the list. It will crash after a second. Not that big of a deal though haha.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
I did...no bug trust me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
That's strange. Maybe something in one or many of our contacts that's breaking the parsing. Can't be arsed to debug though haha.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Are you on 12-06?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I was on 1206 just before switching to quantum. Maybe it's quantum ha, forgot I switched.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skim7x:
I'm on the STABLE release: cm-10.2.0-d2att.zip from 12/02/13. Clean install. Using the included CM Kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Well if you really want it to work I suggest 12-06 hehe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] indymx:
On the latest nightly of CM11 all sound is routed thru the ear speaker?

Notification sounds aren't loud enough to hear.. Anyone else seeing this?

**** a reboot seems to have fixed it. Still odd.. ****
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adrock74:
Anyone ever had this happen: I downloaded latest nightly thru cm updater and when I hit update it opens cwm and there are errors upon opening. It asks to install untrusted zip. Whether I hit yes or no it reboots phone. I basically can't use recovery. I even deleted the nightly and it still does it. I'm on philz latest cwm
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
I can confirm, I'm on 0106 and the call issue i had is gone.

Envoyé de mon SAMSUNG-SGH-I747 en utilisant Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
On 0106, this issue has been taken care!

Thx CM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
I'm on the 2014-01-07 nightly and the LTE tile doesn't work for me either. Looking at logcat while pressing it I see no activity. Interestingly the location tile was also not working for me until I went in to location settings and now it strangely works. Maybe there's something that needs to be triggered in the configuration in order for the LTE tile to work. I even tried to delete the tile and add it back but to no avail.

---------- Post added at 10:29 PM ---------- Previous post was at 10:25 PM ----------

Also wanted to add the USB tethering is not working for me. It just shows "USB tethering error". Does it work for anyone else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
I am experiencing high battery drainage on the latest cm nightlies because of proximity sensor wake lock. The wake lock gets activated on any call and continues to drain the battery until the call is over..

I have not seen this wakelock on Cm 10 nightlies. Any help will be highly appreciated..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] |-Goku-|:
Anyone else having issues with random reboots? Listening to music, phone will reboot. Was on the phone. Phone rebooted. Phone was charging, phone rebooted.

These releases don't seem stable to me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It's like they're... Nightlies! :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
I don't have any issues with crashing. Are you using cyandelta? Cause I think cyandelta is not working 100% for cm11. I was using it before but I noticed that it wasn't adding all the changes from CM and so after a while I got a really unstable build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I've been using Cyandelta for a very very long time both with CM10 and CM11 and I've never had any problems.

Also your statement is nothing but a huge assumption and to bash a great app like Cyandelta without any hard proof is wrong. Have you tried contacting the app dev with your issues or concerns first before publicly saying it doesn't work?

Also how did you notice it wasn't adding all the changes? Based on the changelog? Cause the changelog isn't accurate and even on CMs own sites you can get varying reports. I can assure you Cyandelta is applying all the changes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
+1. The way the deltas are generated and applied doesn't leave much room for error. Actually, it leaves none. You can even compare hashes between all the files in the CyanDelta zip and all the files in the official CM nightly zip for that day. They'll be 100% identical.

http://www.cyandelta.com/index2213.html?q=FAQ
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
My wife has 10.2 installed on her phone, but wants to go back to stock. I've been searching around for a bit trying to find a way to go back to stock, but I can't find something that makes total sense given the updates to the phone with 4.3. I have to make sure I don't screw it up or she'll kill me, and you do NOT want to face her wrath. haha.

We didn't update the bootloader when we installed it, so I don't think it should be an issue. It just seems that all of the rollback instructions I see are for going back to 4.1.2. Is that the only way to get back to stock touchwiz?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Why are you asking here? This is a development thread?

Since I'm already using space to reply, I might as well tell you. The most surefire way to get back to stock would be to Odin back to 4.1.1. Make sure you didn't update your bootloader to 4.3, though. If you can't figure out how to do that, you might want to go to the questions portion of the i747 forum.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
I asked here because everyone here seems to know what they're talking about, and people are usually pretty nice and understanding (mainly Polo and Flex). Plus, it has to do with CM10, which this thread is for.

I figured I could do what you said as long as the bootloader wasn't updated, but if it is, I think I'm basically stuck on CM, right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
No, you could always flash a 4.3 rom if you have 4.3 bootloaders, we just don't have an Odin package for that, yet. As long as you don't flash anything before 4.3 you'll be fine, in that case.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
That's what I figured. Thanks for the info. I don't recall flashing the bootloader specifically for 4.3, so I think we're ok.

Another question, actually. For some reason, her 2012 Nissan Sentra isn't downloading her contacts via BT, which it did successfully on TW. Is this a known bug, or are things just being funky on her end? Again, this is running 10.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Bluetooth is all sorts of screwed up on CM. Should work fine w/ TW.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
Yeah. That's what I thought, too. Guess I'll try the TW option tonight for her and hope I don't brick her phone. She'll kill me. Haha.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
I'm not bashing cyandelta I love it but about two weeks ago when I flashed the update I couldn't wake my phone up from sleep. I wiped and flashed the cyandelta zip and I was getting the same problem but when I downloaded from get.cm my phone was fine. I could only assume that the problem was with cyandelta since they haven't updated their app since cm11 started and cause the zips that caused the problems were the cyandelta zips. I've used cyan delta for a long time and I recommend it to anyone I can. I was sad when I stopped using it cause it makes flashing so much easier. I shall try again now but it doesn't change the fact that I experienced this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Use Root Checker a free app from the market by Free Android Tools. Under the build info see what it says for Bootloader.

If you are on LK3 you can use the images here to get back to stock with root injected. http://xdaforums.com/showthread.php?t=1739426

Or here for straight out of the box stock. http://xdaforums.com/showthread.php?t=1968625

As long as you aren't on bootloader MJB and flash the AT&T image you wont brick your phone. Provided you don't unplug during update or anything like that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
Groovy. Will I be able to use that voodoo root keeper to upgrade to JB OTA while keeping root, or will that knox thing knock it out and just go straight stock on update?

I knew you'd come through!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
Yes I had them on 10.1 stables and currently have them on 10.2. Search my post in this thread. I had a JIRA open. Haven't had time to get another for 10.2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
The only random reboots I've had were cause by HW overlay and Dynamic FSYNC (although I don't believe this is included in stock CM kernel). Disabled those and I'm smooth sailing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
Here's something interesting I've noticed. Both my wife and I have 10.2 on our phones with Voice+ disabled. However, on her phone, it's still running in the running apps section, whereas in mine, it is not running. The only difference in the way our phones are set up is that she has her regular google voice syncing notifications for voicemails, while my phone does not.

Any ideas how to totally turn it off on her phone? I tried to force stop it and it didn't work, and there's no way to disable it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Freeze it with Titanium Backup or delete it from /system/app.

Also I thought you were gonna put her back on stock? :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
I was, and I may still. But the more I grill her about the "issues" with the phone, the more I realize it's mostly user error. We got the BT phone book synched with her car. Her complaint that the touch screen doesn't always respond was met with me never seeing the issue and being convinced that her longer nails are the cause, and her lack of occasional internet is probably because of her work's ****ty internet.

We'll see if she keeps complaining. Haha.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Oi, I hate when that happens, you'll always be the culprit. It doesn't work well "since you touched it". Doesn't matter what you did, doesn't matter if you bring her back to stock, it's still your fault for every problem for the life of the device. :p

Edit: For christmas, I bought my GF a SSD drive for her laptop among other things. 2 weeks passed and it actually died out of nowhere. Now she's pretty sure this computer is doomed forever even though I fixed it already haha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
Hahhaha. That's great. For some reason, after about a year, her phone (on stock) started to act mad funky. I put CM on it and it was a bit better. I'm wondering if her hardware is just whack. We both have GS3 (hers is white, mine is blue) and they act totally differently. It's so weird.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Could be. It's not like these things are made of stone.