yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] Philosobyte:
[MENTION=6287517]brossovitch[/MENTION] if you're still on one of these problematic ROMs, could you do me a favor and go to APN settings, delete the T-Mobile MMS or TMUS APN at the very bottom of the list, and then go to T-Mobile US LTE and add http://mms.msg.eng.t-mobile.com/mms/wapenc to the MMSC setting? Tell me what happens.

I'm on the April 13th official currently, by the way.
[T-Mobile, Samsung Galaxy SIII] brossovitch:
I updated to the newest a few hours ago. It seems fine. I'm going to test it when going to work. It seems to only have the issue with leaving my home Wi-Fi.

I actually selected the reset option in the APN section then wiped cache & dalvik in TWRP.

Seemed to help. We'll see..

My next test was to toggle the, "Mobile Data Always Active," option in developer options.

Perhaps even the aggressive handover, still haven't tried that one..

Upon comparison to my other T-Mobile devices, the APN is definitely not the same.

Notice the differences? This is a device with zero issues, compare to the D2..

I've been aware of this, just figured it was a new setup or something. There's some good options in Developer Options BTW..

I do find it quite odd that the MMS part of the APN now has it's own, wonder why?

Okay, I'll try your theory out. I am currently trying to fall asleep so give me a while and I'll report back.

Thank you!

Additionally: the working devices also ha e the extra APN at the bottom of the list..

I'll still try.
[T-Mobile, Samsung Galaxy SIII] Philosobyte:
Thanks for looking into it. I don't want to get anyone's hopes up prematurely like I did previously, but after doing the modifications I suggested above (getting rid of the standalone MMS APN, putting its MMSC URL into the main APN, and changing the main APN's APN type from "default,supl" to "default,mms,supl"), I'm not encountering any issues whatsoever. Mobile hotspot, group and picture MMS messages, YouTube, Chrome, everything works without data issues. I guess this is when we see if our data issue is the same issue, or if your problem is different.

My D2's original, default settings match your screenshot. I'm really kicking myself for not thinking of this APN modification earlier. I'd experimented with it weeks before the issue started and I never recalled it.
[T-Mobile, Samsung Galaxy SIII] brossovitch:
I'm going to Odin flash the latest firmware tonight and then re-root with TWRP.

Hopefully Odin flashing TWRP 3.0.2-0 will work also.

Rather than bricking the device again! LOL

Then I'll flash CM13 afterwards. It's a bit of extra hoops to jump through but my D2 is only on its first update firmware from TMO. So I'll be flashing the latest update completely.

After this download is complete I'll upload it to my MEGA drive and share it if anyone is interested.

The D2 full firmware download is about a 967mb download.

EDIT: For anyone interested in reflashing stock updated firmware for their d2tmo, here is the latest firmware, yes it has Kies too, it is for US T-Mobile model SGH-T999L (the one I have):

https://mega.nz/#!45tnWDjT!VgG2naumKirEKqmT5mlJODpsBofzxG-lSIhNVLQr8HA

Must extract & use Odin to flash. It's very easy. (Google or YouTube for more help)

This came from Sammobile, I uploaded it to mega to make downloading easier/faster for others without a sammobile account.

Goodnight.
[T-Mobile, Samsung Galaxy SIII] brossovitch:
Okay, quick update..

I flashed stock via Odin. Then flashed TWRP 3.0.2-0 via Odin. Restored my internal storage and data.

All seems great! No brick from TWRP so now I'm updated and got the latest baseband too!

Quite exciting.

[MENTION=7233319]Philosobyte[/MENTION] I haven't tried your theory as of yet, still want to see if all this flashing & restoration has been worth the trouble. Thank you.
[T-Mobile, Samsung Galaxy SIII] Philosobyte:
You don't need to try my theory if you're not having problems. I just wanted to see if I could conclusively post on other forums that my theory was a solution and not an isolated case. My firmware was already up to date, so I had no problems there. I will link to this thread on other forums such as the Cyanogenmod forums so they can try your solution if they're having problems.
[T-Mobile, Samsung Galaxy SIII] QuanNguyen1302:
Does this ROM work with Snapchat???
[T-Mobile, Samsung Galaxy SIII] brossovitch:
With root disabled and no xposed.
[T-Mobile, Samsung Galaxy SIII] QuanNguyen1302:
I mean does camera work well? And does it lag or force close???
[T-Mobile, Samsung Galaxy SIII] brossovitch:
I never tried the unofficial ROM but the camera works fine on the official CM13 nightly.

I don't use malicious virus-like battery killers like snapchat, so I can't honestly say for sure if there's any issue with it. Best way is to try.

I personally haven't installed/used snapchat for at least 3yrs.
[T-Mobile, Samsung Galaxy SIII] brossovitch:
Okay, after all the flashing I did, the issue is still present.

Tried your theory...

Seems to work actually. I am not definitive on this yet, still have to test while going to work.

My issue has been with leaving Wi-Fi. If I leave wifi data kinda just stops working until I toggle it off & on. Kind of a hassle for an average user, so I'm scared to update any of my friends' S3 beyond the CM12.1 Snapshot.
[T-Mobile, Samsung Galaxy SIII] bkwas:
No quick settings menu

Thought I would try cm 13 again. Coming from cm 12.1 with a clean install. Used the auto download zip.

Got no quick pull down notifications or settings menu.

Any thoughts or help please?
[T-Mobile, Samsung Galaxy SIII] Rasgola:
hi, i dirty flashed "cm-13.0-20160502-NIGHTLY-d2tmo" on S3 T999 (T-Mobile) on top of 12.1 with GAPPS micro. everything seems working but notification bar is not working. If i pull notification bar nothing coming up just "No notification" message. am i missing something ? does anybody see this issue? have not found any answer in this tread though.

---------- Post added at 09:01 PM ---------- Previous post was at 08:34 PM ----------

i am using 3.x in my S3, you can install directly from Google store. TWRP

---------- Post added at 09:04 PM ---------- Previous post was at 09:01 PM ----------

I have same issue, i did dirty flash from CM 12.1.
[T-Mobile, Samsung Galaxy SIII] bkwas:
Even if this issue were fixed the rom is not working properly.

Big conflict between dialer and bluethooth.
[T-Mobile, Samsung Galaxy SIII] brossovitch:
For 20160430-nightly Receiving calls makes tons of errors and freezes device. Need to reboot after every call. Trying to update to latest version if issues persist falling back to CM12.1 snapshot.
[T-Mobile, Samsung Galaxy SIII] freeridindirtbiker:
Let us know your results!
[T-Mobile, Samsung Galaxy SIII] brossovitch:
I updated to 20160502-nightly. Works much better. I also cannot find any issues with bluetooth.

As for the data issues I have been having, I tried selecting the Mobile Data always active option in developer options. Didn't actually help. This time I'm trying the Use Legacy DHCP also in developer options.

However, the fix to merge the APN that we were discussing earlier in this thread did seem to help.

Upon further studies, it seems many Samsung devices and even Nexus devices are having this same issue..
[T-Mobile, Samsung Galaxy SIII] Eternall Love:
Couple of issues with the 5/3/16 build

I had just gotten done switching mobos for this gs3 from another (killed it with a bad kernel image) and since I couldn't fix it via odin nor the sd trick. I had the brilliant idea "why not switch mobos, they're both T-mobile gs3s". Keep in mind I am a newb when messing with the actual hardware. I did use Ifixits guide but barely. Nonetheless it helped me out a bit. And I managed to get it working.

Anyways short story aside, I'm having issues with themes crashing when opened (white screen then message saying it stopped responding). And another would be when I try to change photos for the user, it says "documents crashed". Nonetheless it's not putting me off, this is a test phone (already have two other s4s, one on stock and another on cm 13 'stable'). But I'd love the rom already. Also camera seems to be broken still (had read the others replies from the beginning).

Hoping to see newer builds fix that. Gonna try it out more and see what else is broken.

Also battery life is amazing, stayed at 74% and lasted through xposed installs, couple reboots for the modules, moving a gigs of files and general use. Went down to 65 after an hour. Also charges quicker than it used to. Systems fluid and smooth, no lag anywhere. Everythings stable.
[T-Mobile, Samsung Galaxy SIII] Rasgola:
Which nightly build is a good for s3?
[T-Mobile, Samsung Galaxy SIII] brossovitch:
No you don't. There's no stable CM13 for S4, only nightly builds. The S4 has only had CM13 available for less than 2 months. LOL I know this because I rooted and installed CM12.1 on 3 less than two months ago and then CM13 nighties rolled out a week later..

?

Mostly, they're all fine. For a more stable experience you may want to just keep to the cm12.1 snapshot (stable) build. But all in all there's not many issues with cm13 nighties if you can troubleshoot simple problems like apps crashing. Because thing's like documents or bluetooth crashing is easily fixable in a few moments. But I have been tinkering since Android 1.5 Cupcake and have grown accustomed to how Android operates.

The latest nightly is likely the best bet for least bugs. 20160502-nightly is good, i haven't tried the next one personally.
[T-Mobile, Samsung Galaxy SIII] Rasgola:
I have notification issue with 20160502 build. Pull down nitrification is not working trying to figure it out what is the issue? Do you guys see this issue?. I will flash today's nightly let's see if any better.
[T-Mobile, Samsung Galaxy SIII] brossovitch:
Okay, so 20160502-nightly seems very good. With legacy DHCP option active I haven't seen much data loss issue. Seems to be working just fine.
[T-Mobile, Samsung Galaxy SIII] anil2653:
I too have this issue from last few days and I checked even 20160503 build also have notification issues.

Any settings to enable pull down notification as I checked but couldn't find.
[T-Mobile, Samsung Galaxy SIII] s_karani:
I had the same problem with pull down notifications not working. Dirty flashing 20160504 build did not solve the problem. Did a complete wipe (system, data, cache) and reinstalled 20160504 build. Problem solved. Pull down notifications are working now.
[T-Mobile, Samsung Galaxy SIII] Rasgola:
Yes, same with 5/3 build, could not found any option to enable it. Else CM13 is great. I don't mind as this is not my primary phone but experimenting all possible ways.
[T-Mobile, Samsung Galaxy SIII] anil2653:
Clean installed 05/05 build but same issue with pull down notifications

Any thing I am missing?

Working correctly with Octo M builds
[T-Mobile, Samsung Galaxy SIII] Rasgola:
Clean install (factory reset) solved the issue. Try couple time. For my case 3rd time it fixed magically
[T-Mobile, Samsung Galaxy SIII] s_karani:
I use CWM recovery. Factory reset does not format system in CWM not sure about other recoveries. Factory reset in CWM and reinstall did not solve my issue. I had to explicitly format system along with factory reset in CWM and reinstall which solved my issue.
[T-Mobile, Samsung Galaxy SIII] brossovitch:
Okay guys, just an update.. I've been having issues with data whenever I leave my home Wi-Fi. Upon leaving the Wi-Fi network mobile data would fail and never work without toggling it off and back on.

I've found a fully working fix!

In Settings>Developer Options, toggling, "Use Legacy DHCP Client," under the heading, "Networking." This makes everything function correctly just as it did in CM12.1!

I'm quite ecstatic about this.

If you have issues with data upon leaving Wi-Fi, definitely give this a try.

Make sure to reboot after toggling the option.?

Note: Screenshot is from one of my other CM13 devices.
[T-Mobile, Samsung Galaxy SIII] anil2653:
Unable to get Status bar notification when using twrp recovery so switched to cwm recovery and clean flashed and now everything is fine

So I feel something messed up with twrp recovery updates?
[T-Mobile, Samsung Galaxy SIII] sylikc:
I have a quick question, regarding bluetooth audio again. I haven't actually played audio, but I've found something funky with Bluetooth.

1) Turn BT on.

2) connect to an audio device.

3) turn BT off (without disconnecting)

4) wait... and BT will automatically turn on and reconnect to your audio device.

That didn't happen in the past, and I don't think that should be the expected behavior... BT should stay off, period. If you disconnect from the device THEN turn BT off, then BT stays off.

Can anyone else validate this is happening? And I guess a fix for those who might know how to code or report it elsewhere? Thanks
[T-Mobile, Samsung Galaxy SIII] taqulic:
Same here.. My Bluetooth works fine (audio and calls)..But turns itself back on.. After shutting it off.
[T-Mobile, Samsung Galaxy SIII] brossovitch:
Have you tried updating to the latest Nightly? There were a lot of fixes for this device this week.

Also, have you tried clearing data for all things pertaining to Bluetooth and rebooting? Of course you'll lose any pairings you may have saved, but it may help.

Since Lollipop, however, I've had mine automatically connect to the last device synced such as a bluetooth speaker. At least for my other devices.

I haven't ever used bluetooth on the D2 except for tethering which works pretty well.

But I've not had issues with bluetooth turning itself on randomly..

You can also try reporting issues on the Cyanogenmod Forums on their site. Which I've been meaning to do myself, just haven't gotten around to it with all the devices I work with. The D2tmo is more of a side project at this point.
[T-Mobile, Samsung Galaxy SIII] sylikc:
Yeah, I guess I should really report onto the Cyanogenmod forums, since this thread doesn't quite get the volume.

I will try loading the latest nightly tonight. This one is on my test phone... I own 2 d2tmo's and I wipe this one clean every time when testing. I want to move to MM as soon as possible, but sort of don't want to mess with a semi-stable LP build as my dd on my main phone until I've tested all the Xposed stuff I'm running and making sure it's stable (as stable as alpha software can be).

It's not so much that BT is turning itself on randomly, but that it turns on after I turn it off when it was connected to an audio device. So the expected behavior is, if I turn it off, BT stays off. If I turn it on, it will reconnect with the last device..... What's currently happening is, I turn it off (when it was connected to a device). Some time later (less than a minute or so), BT automatically turns itself on, and then reconnects to the last device.
[T-Mobile, Samsung Galaxy SIII] mehul kushki:
no sim card issue

i installed this rom working fine camera and all other apps, just facing the issue of no sim card found.

can u help me with it.

thanks in advance.
[T-Mobile, Samsung Galaxy SIII] brossovitch:
Have you made sure you disabled bluetooth scanning in location settings?

Any way you can check what apps are running in your background?

Have you tried checking your wakelocks? There's a few ways, like wakelock detector from the Play Store, or A really good option is BetterBatteryStats it's available in PS and XDA and quite good. Especially when using the dump report, it will show you all wake locks and all.

Maybe alternatively, take a minute and skim through Privacy Guard as well.

Maybe you have something utilizing a Keep Awake or Toggle Bluetooth permission? Since you have a test device beside your DD you can try stuff like that right?

No harm no foul, I do the same with my DD LG phone which helps a lot..

Please give a try and see if you can make this issue go away.

Even though you're not the dev, but finding a fix for it by simply toggling something or changing a preference may actually help identify the cause of the issue.

What if you swiped the app you were using with bluetooth away in recent apps? I assume you've done that though..
[T-Mobile, Samsung Galaxy SIII] ahmedzetm:
any fix to snapchat is crash and tell camera disable forn camera lag and freeze
[T-Mobile, Samsung Galaxy SIII] brossovitch:
Okay so, the data issues have been worked out in the latest nightly builds. But no matter, buying some LG G4s soon.. Thanks to everyone here and the dev for this great ROM!
[T-Mobile, Samsung Galaxy SIII] madanneo:
I am facing two problems with SGH T999 on CM13 and gapps.

1. I cannot install supersu ( I tried but hanged, then I had to reflash CM 13 and gapps again)

2. Every time i flash, in the recovery ( CWM 6) it is asking whether to fix the root. That means already some root is there?

Some body help me.
[T-Mobile, Samsung Galaxy SIII] brossovitch:
First off , CM13 has root built in you enable it in developer options.

Secondly, SuperSU v2.65 in system mode works perfectly. I don't recommend any of the systemless or beta versions on the D2.

Also, CWM recovery may be at fault. Have you tried TWRP?
[T-Mobile, Samsung Galaxy SIII] madanneo:
i tried TWRP but file system changed, it seems CWM more compatible. Any way thanks bro.
[T-Mobile, Samsung Galaxy SIII] Feredion:
I heard snapchat force closes now because of being rooted but not to sure don't quote me on this.
[T-Mobile, Samsung Galaxy SIII] Smoothzz:
Just flashed 0602 build. Im having issues with quick settings pulldown as well. Not working. Did you resolve it?
[T-Mobile, Samsung Galaxy SIII] Smoothzz:
Reflashed again wiped cache, system and data. It works now
[T-Mobile, Samsung Galaxy SIII] ahmedzetm:
no i used A CM 12.1 Snapshot and work prefect with same supersu 2.65 :confused:
[T-Mobile, Samsung Galaxy SIII] hezmekiah:
Brightness Bug

The brightness slider does not continue to lower brightness past 45% and there is a clear jump in brightness when crossing that section. Is this fixable by factory reset? Thank you
[T-Mobile, Samsung Galaxy SIII] hasan.sy:
The front camera doesn't work ..it says setparameter crash i am running cm13 20160605_nightly.is there any fix
[T-Mobile, Samsung Galaxy SIII] mitboss:
cm-13.0-20160622-NIGHTLY-d2tmo.zip - installed pretty solid so far -
[T-Mobile, Samsung Galaxy SIII] StealthBravo:
Just in case anyone was curious, I will be doing CM 14 nightlies once they become available, though this is no longer my primary device.
[T-Mobile, Samsung Galaxy SIII] brossovitch:
Yes, just.installed 0623 build on the D2tmo. Seems all the issues have been worked out finally!

Very nice!
[T-Mobile, Samsung Galaxy SIII] wulfie66:
which version of gapps is recommended when doing a clean install of 0623+ builds? And is it still a wipe of data, cache, and dalvik?
[T-Mobile, Samsung Galaxy SIII] bkwas:
Still has issues 0625 build on the D2tmo. Calls on car Bluetooth cancel then phone hangs and reboots. Poor battery life.

Going back to cm12. Maybe some day this build will work.
[T-Mobile, Samsung Galaxy SIII] RussellAlan:
Let me know if there is anything I can do to help this build.
[T-Mobile, Samsung Galaxy SIII] sikkustar:
how to get root access in these rom
[T-Mobile, Samsung Galaxy SIII] apanihi:
Really good advice here. CWM was flashing CM13 and Gapps all screwed up and it would go into an optimization loop. Once I used TWRP to flash, it worked perfectly the first try.

I also found out about the tapping the CM13 build version in the About menu 7 times to unlock Dev mode and enable root. This is something a lot of people don't know can be done in CM13 unless you somehow randomly run into the information like I did.

Having a separate issue here with the 6-23 nightly. After a full wipe and fresh install of CM13 and Gapps it gets stuck on the first initial setup menu where you choose your country. Every time I tap Next it flashes a little lock in the middle of the screen at the bottom and the top pull down menu attempts to come down every time. It's really strange went back to 6-17 that one works well.
[T-Mobile, Samsung Galaxy SIII] anil2653:
7-23 has this issue I checked on my d2tmo and moto g 2nd gen with same issue and stucking to first screen

Flashed 7-24 and it is working now
[T-Mobile, Samsung Galaxy SIII] mehul kushki:
please help

hello Sir,

when i flashed the cm13 into my SGH-T999, rom works fine there is only one issue i m facing is, it says no sim card detected.

please sir help with it.

thanks in advance sirji.
[T-Mobile, Samsung Galaxy SIII] Shack70:
Delete this, accidentally hit enter while reading in tapatalk. Sorry
[T-Mobile, Samsung Galaxy SIII] apanihi:
Hey when you upgrade do you do a complete wipe? Or do you flash the latest nightly and gapps and wipe cache and reboot? Just curious since I don't want to wipe, but I do want to upgrade.
[T-Mobile, Samsung Galaxy SIII] anil2653:
Which baseband and modem you are running

I am on NC2

if you are on older baseband then you have to update to Oh1 or nc2

---------- Post added at 11:50 AM ---------- Previous post was at 11:48 AM ----------

I only flash new build over the previous and wipes catches

I don't flash gapps every time
[T-Mobile, Samsung Galaxy SIII] mehul kushki:
currently my baseband is t999uvdljc and using cm11.

how do i update my baseband to nc2.

can u please provide the steps for the same.
[T-Mobile, Samsung Galaxy SIII] zamorph:
I am running 13.0 with all the updates installed. I cannot get snapchat to work. I tried installing an older apk and updating.
[T-Mobile, Samsung Galaxy SIII] anil2653:
You download these modem zip files from Docholiday's thread and flash in recovery as usual but mind that once you come to newer baseband then don't try to flash older firmware then 4.3

Read thread carefully before flashing
[T-Mobile, Samsung Galaxy SIII] mehul kushki:
Thank you sir, phone is working fine on cm13.
[T-Mobile, Samsung Galaxy SIII] Shack70:
Installed the 7/28 nightly and everything is working perfectly. Did a full wipe before install.
[T-Mobile, Samsung Galaxy SIII] radar9:
I factory reset and installed this today too. Running good so far but I lost root. hmmm
[T-Mobile, Samsung Galaxy SIII] wulfie66:
afaik, root is built in, under system settings
[T-Mobile, Samsung Galaxy SIII] Shack70:
You have to enable it. In the settings at the bottom open "About Phone". Tap "Cyanogen Version" 7 times to enable developer options. In "Developer Options" scroll down to "Root Access" and enable root.
[T-Mobile, Samsung Galaxy SIII] radar9:
I saw that. But even after I enabled it, it still showed phone as not rooted. I ended up Odin flashing SU 2.76. After that, root was restored.
[T-Mobile, Samsung Galaxy SIII] wulfie66:
did you reboot your phone after enabling root in admin settings?
[T-Mobile, Samsung Galaxy SIII] radar9:
Yes, several times. Regular reboot and battery pull.