yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] brossovitch:
No need for apologies, you're doing a fantasic job! This device is amazing on CM12.1, so 13 should be even better! Regardless, keeping a 4yr old phone up to date is incredible in itself.

Thank you for your effort and contribution to the Android Community.
[T-Mobile, Samsung Galaxy SIII] StealthBravo:
Got it! This should work. https://www.androidfilehost.com/?fid=24411628330026190

Happy flashing.
[T-Mobile, Samsung Galaxy SIII] cLogic:
installer script still has only d2tmo and d2lte .. no d2can
[T-Mobile, Samsung Galaxy SIII] pcaseiro:
Installed it last night and had a random reboot during the night which made the alarm clock not to go off.

However since then up until now it's been running great.

Thanks Stealth Bravo
[T-Mobile, Samsung Galaxy SIII] FantasmicalMan:
Snapchat still laging and not sure if taking a front facing photo will restart the phone again, but so far so good, thank you for caring about an older phone such as the SIII and doing what carriers won't even day a year and a half after release of some phones but the S3 was announced 5/3/2012 and still supported. love the rom, love your work (especially after trying a few others that were all jellybean with slight tweaks). Thank you, Thank you :D :svetius:

Update: No, Snapchat front facing camera is still laging and freezes and stops responding or restarts phone, not sure if isolated problem but for me front facing camera is shotty at best but most other things fine.
[T-Mobile, Samsung Galaxy SIII] qasar30:
Clear cache again after

After dirty flash with TWRP (wipe davlik, wipe cache checked) I noticed abnormal jumps in my battery meter. I thought it was improved life, then meter jumped from 66 to 40 after some mindless short (few minutes) video, for example. I first tried calibration but the jumps stayed. So I went back and cleared davlik and cache again using recovery. Works great again.

Again, great work! So quick to switch between apps. Videos start faster for me than last one, too. More use and report coming, but so far SO GOOD!

Q
[T-Mobile, Samsung Galaxy SIII] pcaseiro:
Does anybody have issues with lack of sound coming out of the phone's speaker? No sound at all...
[T-Mobile, Samsung Galaxy SIII] pcaseiro:
Downloaded this ROM again, wiped cache and Dalvik and flashes this ROM again. All working well.

Odd that i got no sound previously...
[T-Mobile, Samsung Galaxy SIII] Macgyver984:
Looks great! Thanks for the hard work! I checked the front facing camera and run into the same issue of it freezing up. I also notice issues with BT that I hadn't seen posted on this thread. On the Dec 15 build, my BT phone worked fine in my truck but the media stream did not, it would lock up forcing a reboot. The Jan 24 build fixed the BT media stream, but now the phone locks up forcing a reboot. I just confirmed this is the same in the Feb 11 build. Anyone else having these issues? Thanks!
[T-Mobile, Samsung Galaxy SIII] CarlosBattousai:
It's been a long while since I've flashed anything on my S3 if I'm dirty flashing do I need to flash the newest gapps or not?
[T-Mobile, Samsung Galaxy SIII] wulfie66:
afaik, no, you don't need to flash gapps again if you're dirty flashing
[T-Mobile, Samsung Galaxy SIII] cLogic:
depends on what "a long while" means

if you are flashing a different version of android, I highly recommend a clean flash

since a clean flash includes wiping the system partition first, there would be No gapps for the rom zip to backup/restore .. so yes, you would have to flash the proper gapps for the new rom version

different versions have different framework structures .. a dirty flash would almost always result in many problems
[T-Mobile, Samsung Galaxy SIII] marcuspr:
my unit is sgh t999l version 4.3.0 to install this rom 6.0.1 a boot loader and kernel?
[T-Mobile, Samsung Galaxy SIII] DJAlik:
Is anyone else experiencing weird permission problems with this ROM? I did a full wipe prior to installing it, except the SD card. Here are the issues I have:

- I can't take screenshots, keep getting the "Can't take the screenshot due to limited storage space, or isn't allowed by the app or your organization".

- I can't move files to SD card or delete files from SD card using the CM File Manager or others (i.e, Root Browser)
[T-Mobile, Samsung Galaxy SIII] mouseclone:
Installed yesterday. Everything worked great. Decided to do the encryption, and no sim card. I'm still looking for a solution, but really seams that the solution is to start over from recovery.
[T-Mobile, Samsung Galaxy SIII] qasar30:
Idk for screenshots. I don't try them. But each app asks you to select the root of the SD card the first time you try to move to/from or delete or save to the SD card since 6.0. This is for the Removable storage option. My card is not fast enough to be used like internal storage. I use ES File Manager to manipulate files. The other day I reinstalled MX Player Pro and after watching went to delete video. Was prompted again to select root of SD card to allow actions on it. After that, works like 5.1.
[T-Mobile, Samsung Galaxy SIII] DJAlik:
What's preventing this from becoming Official? I see the following commit that has been under review for a week that could make it official

http://review.cyanogenmod.org/#/c/124028/
[T-Mobile, Samsung Galaxy SIII] pcaseiro:
That would be great! Developers here have been doing a fantastic work but I would like to see this going official.
[T-Mobile, Samsung Galaxy SIII] StealthBravo:
New build: https://www.androidfilehost.com/?fid=24421527759888206

I'd assume this is pretty close to the final initial release for d2.
[T-Mobile, Samsung Galaxy SIII] pcaseiro:
You and matrixzone are awesome. Great developers.

Thanks for the update
[T-Mobile, Samsung Galaxy SIII] ahmedzetm:
are you test this rom

the front facing camera into the same issue of it freezing up

or fixing
[T-Mobile, Samsung Galaxy SIII] pcaseiro:
I use CameraMx and I have no such issue.
[T-Mobile, Samsung Galaxy SIII] StealthBravo:
CM Camera still has some issues. I don't know exactly when they'll be ironed out, but until then, I'd recommend using OpenCamera or another third-party camera app.
[T-Mobile, Samsung Galaxy SIII] guest_2011:
installed cm13 first time, looks ok. Is it me or GPS seems faster now?
[T-Mobile, Samsung Galaxy SIII] ahmedzetm:
camera not big probelm but i test on snapchat freezing and show me camera not conceted

:(:(:(:confused: can any one fix this or what and wifi drop when open snapchat or any camera app

i test snapshot cm12.1 work perfectly
[T-Mobile, Samsung Galaxy SIII] soberarmy:
Wiped and flashed new build. But still show 2016/2/12 why
[T-Mobile, Samsung Galaxy SIII] hasan.sy:
Oh..there ars some bugs in camera ex:front camera doesn't work ,and both camera doesn't detect face..another bug is some apps are closed directly when i open them...thanks
[T-Mobile, Samsung Galaxy SIII] guest_2011:
It's happened before with older CM's, can't remember 11 or 12, but i lost some brightness after flashing CM13. In the past i had to completely wipe everything and reflash, which i did anyway before flashing CM13. Pain in the ass to reinstall and configure apps again and no guarantee reflashing the same build will fix anything. Is there a fix? Anyone else has dim screen?
[T-Mobile, Samsung Galaxy SIII] roadtripguy:
Just wanted to report what I think is a bug with the cm-13.0-2016-0225-UNOFFICIAL-d2tmo build. When receiving a call, I've noticed that the volume of the speaker is extraordinarily loud even on the lowest volume setting. However, if I turn the speaker phone on and back off, the volume returns to normal on the regular speaker. Weird, but that's a temp fix I guess til' a later version. Just wanted to report that and see if anyone else is having the same issue. Thanks.
[T-Mobile, Samsung Galaxy SIII] aBeautifulStory:
I'm trying to flash from Cyanide L on my S3 T999, and I keep getting an error that I am coming from d2att and therefore cannot flash. The previous ROM I was using (I've already wiped the device) (Cyanide L) is "d2att" but fully compatible with d2tmo. Can anyone help? Would love to try out Marshmallow for my S3!

Thanks in advance.

:)
[T-Mobile, Samsung Galaxy SIII] chris-l-a:
I have this ROM installed on my T999V.

I think the secret was to use TWRP for the T999V. I'm currently using the latest (3.0.0). If you have not already, give that a try.
[T-Mobile, Samsung Galaxy SIII] aBeautifulStory:
Oh this was it! Thank you so much!
[T-Mobile, Samsung Galaxy SIII] FantasmicalMan:
I think I found some of my problems out!

I think I found out some of the issues with the ROM that for me at least has persisted since I first installed it:

#1 the "Snapdragon S4" is using around 80%-99% on idle after an app crashes or just sometimes randomly. This in turn causes a lot of issues with other apps and generally very slow, chews through battery life (obviously), and gets HOT like an Snapdragon 810!

#2

Cell Signal (3G, 4G, everything) cuts out and doesn't work until you restart the phone when sent any text messages with an image (MMS message) and if you did not decide to delete the image from being downloaded it will continually try to re-download it on restart until it stops trying after a few minutes thus making no internet access without WI-FI for several minutes.

#3 (an old one I already went over) Front facing camera works around 35% of the time for me, Snapchat crashes most of the time when trying to use the front facing camera or using the filters or face altering filter which the crash leads to the phone either restarting or the 99% usage.

Now time to stop being a whining little boy;

This ROM while having problems, they are easy to get around and at least there is someone willing to put in the effort for us, due to otherwise being left to what Android Ice Cream Sandwich and yes while stable, what fun is that!! I also like to have marshmallow so you can use all the new apps that work perfectly fine on an older phone just not the right software or OS. So Thank you for doing the lords work StealthBravo! :angel: :good:

Edit: I did see the "(CM 12.1 only) IMPORTANT: If you are losing mobile data, or your APNs are not working, please flash this baseband" but I don't believe that applies to me since were running 13.0 and I don't know if that's only if your upgrading from 12.1 or if your on it currently.
[T-Mobile, Samsung Galaxy SIII] wulfie66:
I ran an earlier build of this and had nothing but problems with cellular data so went back to 12.1 release and haven't had a problem yet, knock on wood ;) really hoping that the cellular data issues get fixed with this rom, really want to get to marshmallow since that's what I have on my moto 360 smart watch :D
[T-Mobile, Samsung Galaxy SIII] hasan.sy:
is there any new realise in the next few days?
[T-Mobile, Samsung Galaxy SIII] Gus Ghanem:
CM 13.0 for D2TMO has gone official (first nightly):

http://download.cyanogenmod.org/?device=d2tmo

Getting error from Google App/Search, otherwise CM 13.0 seems to be working great.
[T-Mobile, Samsung Galaxy SIII] ed116:
hey guys is there anyway to gain root on this rom?
[T-Mobile, Samsung Galaxy SIII] Gus Ghanem:
Settings, About Phone, tap "Build Number" 7 times, go back one screen to "Developer Options", tap "Root Access".
[T-Mobile, Samsung Galaxy SIII] cLogic:
is there any difference between the official cm 13 for d2att and the official cm 13 for d2tmo ?
[T-Mobile, Samsung Galaxy SIII] StealthBravo:
Besides carrier crap, no.

As other have mentioned, official nightlies started last night/today. Further development is officially discontinued unless the nightlies stop. Builds will be pushed out for Android N/CM 14, whenever that launches.

Like before, do feel free to use this as a support thread for d2tmo.
[T-Mobile, Samsung Galaxy SIII] pcaseiro:
It's so great that we still might see this phone getting android N in the future.

Love this phone and I'm surely going to keep it for a long time.

Thank you very much SteathBravo
[T-Mobile, Samsung Galaxy SIII] soberarmy:
Google play store error after installing nightly. Can't download anything from play store.

Error retrieving information from server.

RPC:S-7:AEC-70576-IPFQ-PHLQS.
[T-Mobile, Samsung Galaxy SIII] Gus Ghanem:
Updating from CM 12.1 to CM 13.0 is bound to cause some issues. It is best to clean flash CM 13.0 and MM Gapps, or you could try clearing the non-system partitions in TWRP, then flashing the 6.0 version of the Gapps you flashed on CM 12.1.

(OK never mind, this is not a 12.1 thread, I have an old S3 that I never use, so I wasn't following this thread, but the above still applies)

---------- Post added at 07:41 PM ---------- Previous post was at 07:17 PM ----------

Anyway, I clean flashed the official CM 13.0 Nightly, and Delta Gapps, everything works fine, including the Play Store (except for some errors from Google App/Search). Previousely updating from CM 12.1 Nightly to official 13.0 Nightly was a mess.
[T-Mobile, Samsung Galaxy SIII] soberarmy:
I was on the unofficial CM13. Everything worked fine. I did a full wipe and installed ROM and open Gapps.
[T-Mobile, Samsung Galaxy SIII] brossovitch:
Just installed the official CM13 build for D2TMO this morning, coming from CM12.1 I had to factory reset but it was worth it.

I'd like to say, thank you for your hard work! ?
[T-Mobile, Samsung Galaxy SIII] soberarmy:
all is good now. I factory reset and reinstalled Rom and Open Gapps again. It fix my issue. Thanks to all who would of helped me. Awesome community
[T-Mobile, Samsung Galaxy SIII] sameer99#:
alarm error

while alarm is trigredd .. clock app throws an error .. so guys take a look ..this is seen in latest nightly... if any one found a fix tell me guyss...
[T-Mobile, Samsung Galaxy SIII] brossovitch:
Have you tried clearing the data/cache of the app and also have you allowed it permission to storage?

---------- Post added at 02:14 ---------- Previous post was at 01:15 ----------

Has anyone had any issues with data connection on the official nightly cm13?

When I leave Wi-Fi mobile cannot find a connection anywhere?

This may not be the place to ask, but I'll look elsewhere too.

Thank you.

Edit: I just installed the 3/17 build and it seems fine. Clock app has zero issue also. Thanks again!
[T-Mobile, Samsung Galaxy SIII] hasan.sy:
The front camera still buggy ..no video recording ...face detection feature has removed .......problems with reboot...that's i saw
[T-Mobile, Samsung Galaxy SIII] wulfie66:
so are there any builds of that that you'd use as a daily driver? really want marshmallow on this s3, but it's my only phone
[T-Mobile, Samsung Galaxy SIII] sameer99#:
Yes I had tried that also. As I m saying problem is on running alarm not the clock app.. Thanks

---------- Post added at 04:44 AM ---------- Previous post was at 04:35 AM ----------

No not problem with clock app..bproblem arises while running alarm.. And also network is working well , means mobile network but cannot see network activity aroows .. Thanks
[T-Mobile, Samsung Galaxy SIII] brossovitch:
The official CM13 nightlies are fine.

The latest build of CM13 official nighty is fine on my d2tmo. Tested it after I read your comment. Try updating to the 3/17/2016 build.

I had an issue with mobile data not connecting when I left WiFi on the 3/15/2016 build, but when I updated to the 3/17/2016 build it was fine.

Clock app also has no issues.

And alarms work just fine.
[T-Mobile, Samsung Galaxy SIII] sameer99#:
ok then.. i will try latest nightly after few dayss... hope it will be fine... also there is no network activity arrows(uplink & downlink) .. is that problem of cm or just marshmallow?? if we find any new bugs we should sayy ook... to make d2tmo betterr .. :o :o :o :o :o ... cheers
[T-Mobile, Samsung Galaxy SIII] ahmedzetm:
can use f2fs
[T-Mobile, Samsung Galaxy SIII] hasan.sy:
bluetooth had some problems when i turn it from status bar <so ishoud go to setting to enable it....wifi data download and upload signal doesn't appear on status bar,magnetic field has some issues,,,
[T-Mobile, Samsung Galaxy SIII] sameer99#:
so ... thats the issue i was sayinggg... maybe steathbravo should see this... and gps is working on you guys???
[T-Mobile, Samsung Galaxy SIII] StealthBravo:
As far as I'm concerned, upload/download indicators haven't made it to CM 13.

GPS has always been buggy on CM, but it has worked for me recently.
[T-Mobile, Samsung Galaxy SIII] pcaseiro:
GPS is working just fine. If your having problems with GPS locking your position than go on YouTube and there a really nice video that shows how to fix it. You need to take the back cover and apply dialectic grease in some screws. The problem is poor ground connection.

I've had problems with that too where I had to wait a couple minutes before it locked but after this fix it's dead on
[T-Mobile, Samsung Galaxy SIII] hasan.sy:
gps works perfectly
[T-Mobile, Samsung Galaxy SIII] DJAlik:
When I switched to CM13, first unofficial build posted here and even now in the official nightlies, my permissions got all jacked:

- I can't take a screenshot with the built in Power Button + Volume Down . I get an error: "Couldn't capture screenshot. Can't take screenshot due to limited storage space or it isn't allowed by the app or your organization". Screenshots were fine in CM12.

- I can't move files to or delete files on an SD from the phone itself. Only if I connect the phone to a computer then I can move and delete files on SD.

Any suggestions?
[T-Mobile, Samsung Galaxy SIII] Gus Ghanem:
Screen capture works fine for me, on latest nightly. I did not modify any permissions, everything is at default. I wiped all 5 partitions before clean flashing the March 17 Nightly, then updated to 18.
[T-Mobile, Samsung Galaxy SIII] hasan.sy:
is there any fix for 1080p recording...the s3 t999 lost this feature in cyanogenmod roms but s3 i9300 still record 1080p video ...i wish it could be return to this device if there is no problem
[T-Mobile, Samsung Galaxy SIII] gramesy:
This might be a n00b question but I need help. Flashed CM13 nightly last night (now I'm on the 3-18 nightly), coming from stock 4.3, and the only showstopper I'm experiencing is unusable call audio. I can place and receive calls, but the audio is totally garbled. I'm not sure how to fix it. Thanks for pointing me in the right direction. I'd hate to have to flash back to stock at this point.
[T-Mobile, Samsung Galaxy SIII] brossovitch:
Did you do a full wipe before flashing?
[T-Mobile, Samsung Galaxy SIII] gramesy:
I did a factory reset wipe from TWRP before flashing.
[T-Mobile, Samsung Galaxy SIII] anil2653:
I too have same issue of disturbed audio on all calls on 3-18 build now back to 3-17 and no issues
[T-Mobile, Samsung Galaxy SIII] brossovitch:
Okay, so I downloaded the 3/19 build and everything seems fixed. (d2tmo)

Calling and alarms.
[T-Mobile, Samsung Galaxy SIII] gramesy:
I updated to 3/19 this morning and calls work fine now.
[T-Mobile, Samsung Galaxy SIII] sameer99#:
#brossovitch,, is alarm fixed?? If yes then I will update my nightly .. Cheers...

---------- Post added at 03:46 AM ---------- Previous post was at 03:19 AM ----------

Also I found a bug on early nightly.. Latest nightly I don't know.. While going on call statistics there is error.. I haven't flashed latest nightly so I font know either it is fixed or not. But take a look..thanks
[T-Mobile, Samsung Galaxy SIII] brossovitch:
Yep, it works for me. I've never had issues setting alarms or having them go off. Same with video recording, never had any issues. But 3/18 build calls were messed up and garbled.

I actually came here to ask if anyone had updated to the 3/20/2016 build because there's no changlog for it.

The next build changelog seems to have some nice fixes as well.

I have the 3/19 build currently with no issues that I can find. I don't use many apps on this device but it seems to run perfectly. Hopefully the d2 gets the next CM13 snapshot build...
[T-Mobile, Samsung Galaxy SIII] wulfie66:
serious cellular data issues here ,went back to 12.1
[T-Mobile, Samsung Galaxy SIII] sameer99#:
No problem with cellular data.. May be problem with access point settings.. Thanks
[T-Mobile, Samsung Galaxy SIII] Fry-kun:
T999L, trying to install in multiboot, getting a "system partition has unexpected contents after OTA update"

I tried flashed my model's latest modem from baseband page, UVUBOH1 -- didn't help

Is this related to the multiboot?

I found the check/warning in META-INF/com/google/android/updater-script but didn't figure out what the sha1 check is looking for, exactly...

ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
ui_print("Verifying the updated system image...");
if range_sha1("/dev/block/platform/msm_sdcc.1/by-name/system", "42,0,32770,32865,32867,33367,65535,65536,65538,98304,98306,98401,98403,98903,131071,131072,131074,163840,163842,163937,163939,164439,196607,196608,196610,229376,229378,229473,229475,229975,252903,262144,262146,294912,294914,295009,295011,327680,327682,360448,360450,360950,383999") == "2490140199ac43e2ab1ae360b81cfcf4d1a6bf27" then
if range_sha1("/dev/block/platform/msm_sdcc.1/by-name/system", "56,32770,32865,32867,33367,65535,65536,65538,66050,97792,98304,98306,98401,98403,98903,131071,131072,131074,131586,163328,163840,163842,163937,163939,164439,196607,196608,196610,197122,228864,229376,229378,229473,229475,229975,252903,253415,261632,262144,262146,262658,294400,294912,294914,295009,295011,295523,327168,327680,327682,328194,359936,360448,360450,360950,383999,384000") == "fd104ca087a4e3ad7114741142fcd97f2815e4e7" then
ui_print("Verified the updated system image.");
else
abort("system partition has unexpected non-zero contents after OTA update");
endif;
else
abort("system partition has unexpected contents after OTA update");
endif;

P.S. wary of flashing UVUENC2 from 1st post, since it's for T999, not T999L

Edit: wait.. looks like it's trying to validate something it had just written. And failing? o_O

Edit: almost certainly caused by multiboot, don't mess with it!
[T-Mobile, Samsung Galaxy SIII] ahmedzetm:
Front camera has minor issues how can fix it
[T-Mobile, Samsung Galaxy SIII] sylikc:
Hi, I've actually wiped down the phone clean (aside from like cleaning internal memory. What's the fix in terms of data wipe. I have a test S3 where I'm clearing everything but internal memory, using the TWRP wipe feature for everything, and this bug still manifests itself
[T-Mobile, Samsung Galaxy SIII] bkwas:
unofficial or nightly

I am relatively new at this. Can somebody tell me the difference between the two?
[T-Mobile, Samsung Galaxy SIII] brossovitch:
Between the 2 what?

D2lte and others?

d2lte was a unified build, everyone should've been off of that build over a year ago and onto their variant specific build.

d2tmo is T-Mobile

d2att is AT&T

d2vzn is Verizon

And so on.

CM team made multiple variants unified but then seen the error of doing so, so they went back to separate builds for each variant.
[T-Mobile, Samsung Galaxy SIII] brossovitch:
One is unofficial and the other is official from CyanogenMod.
[T-Mobile, Samsung Galaxy SIII] bkwas:
Thanks, Can I dirty flash the nightly over [ROM] [6.0.1] [2-24-16] CyanogenMod
[T-Mobile, Samsung Galaxy SIII] brossovitch:
I wouldn't recommend that. Even CyanogenMod teams Blog specifically says not to do that.

I'd make a nandroid, wipe Cache, Dalvik, & System. Then flash the ROM, GApps, & any other add-ons you use.
[T-Mobile, Samsung Galaxy SIII] bkwas:
Yes I did that cm 13 over 12.1 and it did not work. I was confused with the cm 13 updates showing up in notifications.
[T-Mobile, Samsung Galaxy SIII] brossovitch:
Yea, when I updated from CM12.1 to CM13 I had to wipe everything and start fresh.
[T-Mobile, Samsung Galaxy SIII] bkwas:
I clean flashed cm 13 nightly and could not get bluetooth to work.

Just finished flashing the unofficial and all is well so far.
[T-Mobile, Samsung Galaxy SIII] brossovitch:
Same here. Had to physically open the Bluetooth and Bluetooth sahring info and force stop them and wipe their data then reboot. Works fine now. Most things work that way for me. Especially on CM13.