yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] muaddib519:
I had a similar issue. Wifi wasn't working well and when I tried to load the settings for wifi, the settings app would crash. A temporary solution was to turn wifi on and off and then it would work.

I found out how to fix this problem. Go into settings -> themes -> theme packs, click the default theme then apply/update it.

You'll want to change your settings back to to way they were, backgrounds, ringtone, notification sound, etc, but, for me, wifi now works without issue.
[T-Mobile, Samsung Galaxy SIII] Kalm_Traveler:
I have only used leankernel and WiFi always works.
[T-Mobile, Samsung Galaxy SIII] scott7175:
The WiFi only breaks on older kernels that were made before the 28. Anything after that should work
[T-Mobile, Samsung Galaxy SIII] Sixonefour:
M9 is live!
[T-Mobile, Samsung Galaxy SIII] dzasta:
Just posting this as a useful tip for others that might have experienced the same issue as me.

i like my custom ringtones/notifications. i have a custom ringtone/notification for everything. then i suddenly started noticing that my ringtones kept reverting back to "default ringtone sound" and not my custom ringtone. and then it would switch back to my custom ringtone. this would happen seemingly at random which drove me nuts. about 3 factory clean wipes later with a format internal SD card sprinkled in, i realized that the source of this odd behavior was due to the new-to-me CM profiles!

I have 3 profiles that i setup mainly to conserve my battery life. one for work, one for home and then a default. everytime i was NOT in my default profile, the profile would override my custom ringtone!!! which was why it seemed random. i literally wasted almost 3 days of my life trying to figure out if this was a new nightly bug or something i did.

so to fix this, you have to go into system settings > profiles > click on menu icon for desired profile > app groups > phone > then set the 'notification mode' and 'ring mode' to no override. then repeat the same for the SMS app group.

hopefully this will save some of you some of the grief i had to deal with... :good:
[T-Mobile, Samsung Galaxy SIII] zolo185:
Doesn't matter cuz didnt they stop for d2tmo 2-17-14? atleast thats what i assume because on the cm download page that's as recent as it is.

Just rooted sgs3 for my friend and im not familiar with this thread.
[T-Mobile, Samsung Galaxy SIII] serio22:
No, all d2 devices have been merged to d2lte
[T-Mobile, Samsung Galaxy SIII] zolo185:
Ahh thanks. Just found a link to it.
[T-Mobile, Samsung Galaxy SIII] crazexr7:
First time on kitkat and M9 is very nice!
[T-Mobile, Samsung Galaxy SIII] z4ckm0rris:
Anyone having issues with CM11 and apps like Whatsapp? Specifically the Microphone. As my girlfriend puts it.. I sound like a robot. And listening to it myself, it sounds like my microphone is boosting or doing something strange. Phone/Mic sounds normal on regular phone calls though. On the 8-11-2014 Nightly.

Edit: Just installed the 8-13-2014 Nightly. Appears to have made it worse.. as strange as that seems.
[T-Mobile, Samsung Galaxy SIII] dzasta:
Did you try a factory reset/clean wipe?
[T-Mobile, Samsung Galaxy SIII] z4ckm0rris:
[/COLOR]

Ran it clean. Funny enough it only occurs when using the onboard mic. As in, if I put in a headset and speak it's crystal clear. If I pull the headset out, it remains crystal clear for awhile and then later on seems to go back to me having a robot voice.
[T-Mobile, Samsung Galaxy SIII] CarlosBattousai:
Does Google wallet work for anyone? Nfc works fine,but not when I try to use Wallet.

Wifi tether down too on Cm11 M9 for me.

any idea guys?
[T-Mobile, Samsung Galaxy SIII] moraha1287:
I hope someone can help me out. I haven't touched any ROMs or updates on my phone for over a year now and I completely forgot some of the basics. I'm looking through this thread and keep seeing these "M" releases so I'm way behind. I'm still running 10.2.0 on my phone and just want to try something new. Are there any stable releases passed that version that I can easily just flash into my phone? With all of the other releases, I always did a dirty flash and never had problems from what I remember but I'm not sure what happens when trying to go to completely newer versions.

I went to the download link in the first post and the last nightly that I see was back in February. Is there a new page to download the releases?
[T-Mobile, Samsung Galaxy SIII] aaronkt:
http://get.cm/?device=d2tmo&type=

so these would be safe to use correct?
[T-Mobile, Samsung Galaxy SIII] brfield:
I really love this build, but the camera might be what sends me back to a TW variant. I don't want to go as I love CM and JB. I'm torn between the two. If I went back I'd theme it all the way into oblivion to get rid of TW.
[T-Mobile, Samsung Galaxy SIII] durhamite:
Yeah. But these are cm 9 builds
[T-Mobile, Samsung Galaxy SIII] mustk1ll20:
Try camera fv-5 from the market. I liked it so much I got the full version.
[T-Mobile, Samsung Galaxy SIII] aaronkt:
thank god your reading skills are better than mine.
[T-Mobile, Samsung Galaxy SIII] arathur:
I also started using Camera FV-5 as suggested by another xda user. However, yesterday I flashed the 8/2 euroskank build and since then the camera seems to be malfunctioning. When I press the picture-taking button, if I'm taking a close-up shot of something, nothing happens. However, if I'm taking a non-close-up picture, then the app will produce a picture. But still, it's a great app and does a wonderful job in making up for the lack of touch-to-focus on cm10.
[T-Mobile, Samsung Galaxy SIII] cyanogendroid:
IM GOIN CRAZY! checked this thread probably 50 times today. Thanks for the amazing work Steve, wish I could donate but I'm 15 and ain't got no credit card.

Sent from my Santa Cruz Blur LT
[T-Mobile, Samsung Galaxy SIII] sleevasteve:
Steve, feel free to post this Q&A thread in the OP: http://xdaforums.com/showthread.php?p=29746565

Thanks mt3g

Sent from my Wicked Blue ICS SIII
[T-Mobile, Samsung Galaxy SIII] mustk1ll20:
I noticed that it doesn't take closeups a little bit ago. I'm messing with the settings, but haven't found anything.
[T-Mobile, Samsung Galaxy SIII] arathur:
It should take them just fine in "macro" mode (the setting is designated by a picture of a flower). However, when I press the picture taking button, no image is recorded into the gallery. It's like the app isn't responding to the command. However, if I take a more far away picture, it gets saved just fine.
[T-Mobile, Samsung Galaxy SIII] Lakeshow423:
Use the 720P mode in settings! It takes full pics and come out sharp. Without this setting enabled I would definitely be back on a TW ROM! JB is just too sweet and with Google now working, hawt damn!
[T-Mobile, Samsung Galaxy SIII] mustk1ll20:
Fixed mine by creating data, force closing and rebooting. Takes closeups now.

Chip bag lol

That's what mine has been set at before I even took the first picture.
[T-Mobile, Samsung Galaxy SIII] shawn157:
Does anyone know what tree they use to make the kernel?

Edit: Looks like it's using the d2 one but I'm not sure if that's compatible with tmo version.

I basically just want to know if the d2 kernel tree will work on the tmo so I don't flash and end up screwed lol.
[T-Mobile, Samsung Galaxy SIII] Spider_Pig27:
I'm wondering what does "Preview ROM" stand for because to be honest this ROM is f***** awesome and there isn't much wrong with it.. just the mute calls while in a phone call and not being able to lower volume while in calls aside from that I love this ROM as my dd
[T-Mobile, Samsung Galaxy SIII] brfield:
When I was building the device tree was "d2tmo" but it has dome shared with d2 iirc.
[T-Mobile, Samsung Galaxy SIII] shawn157:
I am using that tree but there isn't a kernel tree for it, just a common d2 tree so idk.
[T-Mobile, Samsung Galaxy SIII] brfield:
Cynogenmod integrates the kernel building, so when the git repo is cloned, make sure you have /device/samsumg/d2tmo, device/samsung/d2-common, and /kernel/samsung/d2

Then when you build it targeting d2tmo, it will build the kernel while building the rom due to the instruction in the d2tmo blobs. You may need proprietary files though.
[T-Mobile, Samsung Galaxy SIII] atlprettygirl2145:
It would be nice to have the motions available and the led for when the phone is charging and fully charged
[T-Mobile, Samsung Galaxy SIII] Evo4eva:
So set the LED to come on when you're charging it then.
[T-Mobile, Samsung Galaxy SIII] Lieu10ant:
so this rom hasn't been updated, and the latest version is from the 29th, right?
[T-Mobile, Samsung Galaxy SIII] RickG13:
The newer releases should be under "d2lte". I believe M9 snapshot was released recently.
[T-Mobile, Samsung Galaxy SIII] :
Odd behavior on either the 9/2 or 9/3 nightly: whenever somebody calls me, if I answer with my BT headset, I can't hear the caller. If I answer with the phone, no problems.

Just wondering if anybody is experiencing the same thing? Thanks.
[T-Mobile, Samsung Galaxy SIII] WhoWhere:
I ran into the same problem on 7.8 SlimKat.
[T-Mobile, Samsung Galaxy SIII] :
I wonder, then, if CM has messed up Bluetooth again? I'm going to be sticking with the 9/1 nightly for the time being.
[T-Mobile, Samsung Galaxy SIII] matrixzone:
There has been some major telephone commits in the last two nightlies which could be the reason for this... Report this in the next monthly build on cm bug tracker and that should be fixed in no time
[T-Mobile, Samsung Galaxy SIII] Jay Rock:
I rarely make phone calls but when I do, the speaker is way too loud at lowest volume. Kind of sucks when your mother starts nearly screaming through the phone.
[T-Mobile, Samsung Galaxy SIII] :
There's an entry in the changelog for 09/06 that reduces the speaker volume. Perhaps that will help. :)

Quick question: has anybody tried the newest nightlies? If so, do you know if the BT issue (where we can't hear the caller on BT headset but OK on phone) is fixed? Thanks.
[T-Mobile, Samsung Galaxy SIII] shane1diamond:
Is HDMI out working on builds after 8/20? I just flashed an experimental build via ROM installer on my daughters S3, to my amazement the HDMI/mhl out and USB otg works great. Is this old news? And does it work on these newer builds? Thanks all.
[T-Mobile, Samsung Galaxy SIII] WhoWhere:
I'm going to be updating my version of SlimKat this evening. If it's fixed there, I would assume it is on CM. I'll let you know.
[T-Mobile, Samsung Galaxy SIII] :
Just tried the 9/9 nightly...still not working. :(
[T-Mobile, Samsung Galaxy SIII] Jay Rock:
Yeah I noticed sound was lower and so better than before, but in every nightly right after the speakerphone volume has sky rocketed again. Learned the hard way by answering a phone call in the quiet library surrounded by a bunch of people. Possibly the main reason I have to switch back to a stock ROM besides the camera.
[T-Mobile, Samsung Galaxy SIII] jhenson496:
Hey everyone, sorry is this question is out of line for this thread. I've checked the last couple pages and did not see anything. Long story short, my G2 is out of actions so I had to switch to my wifes old SIII for the time being. When I look on the CM download page the last CM nightly I see is for 2/17/2014. I'm looking under d2tmo. Is this correct?
[T-Mobile, Samsung Galaxy SIII] :
Look for d2lte.
[T-Mobile, Samsung Galaxy SIII] jhenson496:
Thanks. will the d2lte work even though I don't have the lte model?

Nevermind, looks like it's for all US versions.
[T-Mobile, Samsung Galaxy SIII] :
It looks like there are some BlueTooth fixes listed in the change log for the next build. Will try it out once the nightly drops.

--EDIT-- Nope ... still broke. :(
[T-Mobile, Samsung Galaxy SIII] MrFunEGUY:
On every nightly after 8/20, I cannot use Mobile Data. Also, is there a way to change the location of the kill all button in the recent apps switcher? The top right is ridiculously inconvenient for me after using it on the bottom left in Liquid Smooth.
[T-Mobile, Samsung Galaxy SIII] :
Strange - I've had no problem with mobile data and I'm on the 09/01 nightly.
[T-Mobile, Samsung Galaxy SIII] CarlosBattousai:
Is anyone able to use Google wallet? If so which version are you on?
[T-Mobile, Samsung Galaxy SIII] MrFunEGUY:
I'm gonna be honest, that was an assumption after trying three after 8/20. I didn't try that one specifically. Also, on LiquidSmooth, which is where I came from, my Mobile Data was broken after 8/24 as well, so I assume it was something about versions after that.

But really guys, app killer button, how do I change that.
[T-Mobile, Samsung Galaxy SIII] dzasta:
any luck on bluetooth working on the newer nightlies? I'm on 9/8 and its super frustrating to not have bluetooth while driving..
[T-Mobile, Samsung Galaxy SIII] :
Unfortunately not, it's still borked. However, in their bug reporting tool, the issue got assigned to a developer so I'm hoping for a fix soon.
[T-Mobile, Samsung Galaxy SIII] mondokat:
I'm running a stock CM11-M10 and bluetooth works fine.
[T-Mobile, Samsung Galaxy SIII] :
Perhaps M10 doesn't have the same problems that have affected the latest nightlies, then.
[T-Mobile, Samsung Galaxy SIII] JustZaphod:
Looks like anything with Cyanogen code is affected.. I'm running Carbon and the lastest Nightly has no Data or cell signal...

reverting back to a previous Nightly brought it back..
[T-Mobile, Samsung Galaxy SIII] ergibson83:
Same for me. I updated to M10 yesterday and I had to go back because I was getting cell and data app crashes. I just reverted back to 9/15 nightly and that fixed my issue.
[T-Mobile, Samsung Galaxy SIII] mondokat:
Makes sense. The snapshots are supposed to be more stable. Seems like they made the M10 snap then added a bunch of unstable code that broke everything. That's what happens sometimes on the nightlies.
[T-Mobile, Samsung Galaxy SIII] Sixonefour:
I'm not having any issues with M10 at all with data or crashes of any kind. Its pretty smooth in my perspective.
[T-Mobile, Samsung Galaxy SIII] JustZaphod:
What ROM are you using? You may have a ROM that is unaffected by the Radio glitch..

I've tested the latest CM and got the same problem..
[T-Mobile, Samsung Galaxy SIII] freeridindirtbiker:
I'm in the same boat. The M10 SNAPSHOT has not given me any issues what-so-ever. Everyone who is having issues, be sure that you are clean flashing to M10 and not dirty flashing from a nightly. Problems WILL occur if you are dirty flashing.
[T-Mobile, Samsung Galaxy SIII] Sixonefour:
M10 snapshot
[T-Mobile, Samsung Galaxy SIII] JustZaphod:
Well Snapshots are far more stable, Nightlies are Alpha, where Snapshots are Beta... ETC..

I would expect a Snapshot to work.. just about flawlessly..
[T-Mobile, Samsung Galaxy SIII] Sixonefour:
I was referring to [MENTION=2632009]ergibson83[/MENTION]. See the first quote here. We aren't talking about the same thing. I probably should have quoted him in my original response to avoid this confusion.
[T-Mobile, Samsung Galaxy SIII] mondokat:
Spoke too soon?

So, I reverted to M9. I was having troubles in M10 with bluetooth. I could make calls fine, but receiving calls there was no audio. Phone answered like it was supposed to, but neither of us could hear anything. If I dialed out though it worked fine. Also, the phone's volume is WAAAAAAAY louder than it was. Speaker for notifications was like twice as loud and the in call volume on the handset was extremely loud, so loud the speaker would crackle with the gain. This was not adjustable.

So I'm back on M9. Hopefully M11 will be better.
[T-Mobile, Samsung Galaxy SIII] Mervingio:
Try M11

---------- Post added at 02:55 PM ---------- Previous post was at 02:54 PM ----------
[T-Mobile, Samsung Galaxy SIII] soundman1024:
Heh. I've been "dirty" flashing my S3 since before monthly snapshots were a thing. I've had to nandroid restore two or three times along the way. Phone seems to work fine.
[T-Mobile, Samsung Galaxy SIII] CarlosBattousai:
Can anyone use Google Wallet? Nfc works fine,but for some unknown reason ( To me) I can't pay with Wallet anymore.

Anyone have any luck?
[T-Mobile, Samsung Galaxy SIII] skyxliner:
Does anyone have an issue with the dialer while in call? I can press back and then dialer again and it works.
[T-Mobile, Samsung Galaxy SIII] nirogu325:
That dialer pad issue only happened to me a month or so ago when I had animations completely turned off. If it is now another thing, then I dunno. Just an idea.
[T-Mobile, Samsung Galaxy SIII] skyxliner:
I was hoping you were right, turned it back to 1x and it didn't fix it... i'll try restarting it to see if it makes a difference.

What setting animation do you have now so that the dialr doesn't break?

EDIT: OMG THAT WAS IT! that dialer was bugging me for months!

You do need a soft reboot to fix the dilar again.

now i'm testing to see which animation setting is really the culprit cause i want to change back to 0 for whatever i can get away with.

---------- Post added at 12:55 PM ---------- Previous post was at 12:23 PM ----------

If anyone was curious about the dialer bug.

You can set window animation scale 0

transition animation scale 0

animator duration scale 0.1 (this is the problematic setting)
[T-Mobile, Samsung Galaxy SIII] AtomicPC:
What about APN? My APN is gone and I can't connect to data. Calls come in. I can't add the info, it doesn't stick.
[T-Mobile, Samsung Galaxy SIII] DutchDogg54:
Just did some light cleaning - let's keep this on-topic everyone.

Thank you.
[T-Mobile, Samsung Galaxy SIII] anderson79:
Works in t999l?

Enviado desde mi SM-G900F mediante Tapatalk
[T-Mobile, Samsung Galaxy SIII] serio22:
Yes. d2lte supports all d2 devices
[T-Mobile, Samsung Galaxy SIII] Sixonefour:
Thanks for this. This has been an issue for a long time if I remember correctly and highly annoying.
[T-Mobile, Samsung Galaxy SIII] Bray90820:
Is it just me or is the Radio bug still present in M11
[T-Mobile, Samsung Galaxy SIII] mondokat:
No problems for me. I use stock cm kernel and everything. I had a very stable m9, m10 had volume problems in calls, and m11 seems stable again so far.
[T-Mobile, Samsung Galaxy SIII] nirogu325:
Same here except for YouTube playback. Sometimes videos would load distorted without color. I just quit and reload the video. That's the only issue I've discovered so far.
[T-Mobile, Samsung Galaxy SIII] nighthawkca:
APN Problem

I have an SGH-T999 that was running snapshot M6. It was running fine until a couple of days ago it had an encryption problem and said it needed a factory reset. I did a factory reset and used the opportunity to install M11. The phone boots up and runs great on wireless, but it will not connect to the mobile network (I use T-Mobile). There is a good signal quality, but no connection to the network. I checked and the IMEI is not 0. I checked the APN and the list is blank. So I tried to add a T-Mobile APN and when I press menu->save, the APN is NOT saved. The APN list remains blank. I've rebooted a few times and I simply cannot save an APN. I searched the thread and could not find a solution. Any ideas what might be wrong? Thanks!

I also tried the "Reset to default" from the APN menu and the list remains blank.

I've tried two sims, both work perfectly in other devices but have the same problem in this device: no connection to the mobile network and no entries in the APN list.
[T-Mobile, Samsung Galaxy SIII] s1dest3pnate:
Sounds like you just need to do a wipe. You could try first to just wipe system/cache/dalvik (don't wipe data), install CM11, and then check. If the issue remains, wipe again and include data this time.
[T-Mobile, Samsung Galaxy SIII] nighthawkca:
I already did a factory reset before I installed milestone 11. Doesn't that already wipe data?

BTW - I also had wiped system along with cache and dalvik. I think that's a clean install of CM11 m11. The only thing that didn't get wiped was internal storage.

EDIT: Ok, I did a super clean install of CM11 m11. I wiped everything. system, data, cache, dalvik, internal storage. But still the same problem: no connection to the mobile network, no entries in the APN list, and I can't add an APN. The sim works fine in another device.

I'm really stuck. Any other thoughts? Thanks.
[T-Mobile, Samsung Galaxy SIII] nirogu325:
Just giving ideas. Check if you have the latest bootloader and modem (NC2). Reinstall modem if needed. I got those and have no issues with M11. If that doesn't solve it, I've no ideas left for now.
[T-Mobile, Samsung Galaxy SIII] mondokat:
Hm, imei problem? Haven't heard of people having problems with that in years, but it sounds like it can't figure out your imei. I forget the details, but there's ways to backup/restore your imei and if you have no backup (which sounds likely) ways to determine and restore without it. You'll have to search the forums, but at least you have a search term now. Good luck.

Edit: almost forgot, about page on your phone should list the imei. If it's missing, bingo.
[T-Mobile, Samsung Galaxy SIII] anil2653:
It happened few times with me too after flashing some Roms and also kernel but once I flashed other ROMs or restore earlier backup and got everything back

You too try to flash some of your working rom or restore backup if you have

All the best ?
[T-Mobile, Samsung Galaxy SIII] nighthawkca:
Yeah, I checked my imei right away. It's still there. That's when I started down the APN path, and found no APN's and not able to save an APN. This phone has been running CM11 from the early nightlies with no problems (besides the CM bugs of course!). It's been running well until this current issue.
[T-Mobile, Samsung Galaxy SIII] nirogu325:
Here's another thing you can try. Download any recent SlimKat buildings and extract the apns-conf.xml file from /system/etc. Transfer that file to your ROM's same folder (/system/etc) with file permissions set to rw-r--r--. Reboot and test. Could be a corrupt apns-conf.xml file.
[T-Mobile, Samsung Galaxy SIII] nighthawkca:
I restored a m6 backup and the phone goes on the t-mo network just fine! So something really went wonky with my m11 clean install. Maybe I'll just try to flash the latest nightly over the top of this restored rom and see what happens. Is there anything I should specifically save from this running state before I flash it again?

EDIT: Wow, this is very strange. I restored my m6 backup and the phone goes onto the mobile network just fine. I then booted into recovery (TWRP) and dirty flashed the latest nightly (and wiped cache/dalvik) and then the phone no longer goes on the mobile network and the APN list is blank. Could the apns xml file be broken on the builds since m11 for me?

EDIT2: I restored the m6 backup, copied the apns-conf.xml file from /system/etc, dirty flashed the latest nightly, copied back the m6 apns-conf.xml file to /system/etc, set permissions set to rw-r--r--, and rebooted. Still no service on the mobile network. Stranger and stranger....

EDIT3: As a test, I clean flashed the latest LiquidSmooth rom. No luck, I still cannot connect to the mobile network. The only think that seems to work is restoring my old CM11 M6 backup. I don't know what's going on... :(
[T-Mobile, Samsung Galaxy SIII] nirogu325:
Hmm...only thing I can suggest now is to format /system along with the factory reset, now do ODIN back to NC2, then flash TWRP via ODIN, redownload M11 and try again. Yes, sometimes our phones can get cranky if they experience too many flashes, particularly on the AOSP side of the pond, so that's why I suggest ODIN'ing back to NC2 for a clean slate. It has helped solve weird issues before.
[T-Mobile, Samsung Galaxy SIII] nighthawkca:
I'm willing to try since my phone is now pretty useless. I don't really know how to ODIN back to NC2, I've only used ODIN to flash TWRP. I did some searching and it's not clear what I need to download and how to then use NC2. Do you happen to have a link to a clear guide on how to do the steps to ODIN back to NC2? Thanks!
[T-Mobile, Samsung Galaxy SIII] nirogu325:
Here is the thread with the root66 version of NC2 ODIN firmware to download. Once you download NC2 for your T999, in post 2 please look for "How to Flash the Stock Firmware" where right below in pink you will see "USING ODIN".