yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] primer70:
Thanks for the info update. And yes people are still reading old threads. My experiences are the same with this rom as yours has been, and so far so good! (2nd March 2016). Mostly it's been very stable for about two months now. One thing I do notice though is my screen can get hot when watching videos with MX pro. (after about 10 minutes or so). No reboots, no other issues.... it just gets hot and more than the usual amount. I say that because I have another phone ( i747) and its running a different CM 12.1 rom (unofficial Matrix from July 2015) and it doesn't get as hot, but it has other glitches. (Dialer app sometimes fails to open and headphones don't disconnect sound from speakers). So maybe with this Rom (2nd March) it's a hardware issue with my phone (or maybe it's the Rom itself?) also just to note, I'm running SuperUser 2.78, Opengapps Full + Flux Themes with Greenify. This Rom is very good though, and it's the best one I've tried so far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] witchcraftz:
I'm on a different bootloader from Fido network: I747MVLUEMK5

I'm hesitant to modify it to the AT&T network version: NJ1. Will downloading and installing the Rom work without updating the bootloader?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
I do not recommend flashing AT&T bootloaders to a Fido s3 as certain modem/bootloader combinations could hard-brick the phone.

I recommend flashing the latest stock Fido/Rogers/Bell/Telus ROM to the Fido s3, install TWRP, create a nandroid back, and then flash any d2att ROM you want. If you get an updater script error, you can just edit the updater script.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] martiroskg:
SO where is link to DOWNLOAD?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nehc_rm:
Not sure if you read this post but I was wondering if you still have the rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bugly Astard:
What are you needing? I have the march 2nd copy saved. https://drive.google.com/file/d/16kc0QCBOY6RFKEW3bWMEQf5rYj4d60zK/view?usp=drivesdk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nehc_rm:
Thank you very much for sharing. I've saved a copy offline. It's pretty hard find old CM rom for d2att. I am skeptical to install Android 7.xx. People seems to have problem with how much the device drains the battery.

I would like to know your impression with this rom? How's the battery life, is it stable, what doesn't works. I am sorry to ask all those questions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bugly Astard:
I only archive roms that I've tested and are reliable, it's real good, except no lockscreen torch (could use xposed?). My daily rom of choice is an old jellybean miui rom with bionic sheep kernel. I have a kitkat cm11 rom archived that is really good, but kitkat carbon rom is WAY better. Cyanogenmod based roms are sweet, but miui has features I can't ditch.

As for 7.x roms, the carbon rom works nicely but it did drain battery, and titanium backup only sees internal memory.. I just don't need the latest Android version. I'm using a jellybean rom that works great for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nehc_rm:
After weeks with no problem, my phone went into bootloop mode after installing some apps. Wiping the cache and dalvik cache didn't help to fix the problem. So apparently I am not alone and it's an issue with old CM build, pre CM 13: https://xdaforums.com/general/help/bootloop-updating-apps-telegram-t3700773

The solution is to install a patch. I have flashed on my phone and it did fix the bootloop. The patch is for a different phone than Samsung Galaxy S3 but it does work. I think will work for other CM 12.1 phone. It just modify a system file in CM. https://xdaforums.com/showpost.php?p=74842530&postcount=464

If you are using KitKat, you might find this more useful, https://xdaforums.com/showpost.php?p=75958727&postcount=184

It might come handy to you. It's just something I would like to share with you since you were kind to share the ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bugly Astard:
Thank you. I actually did have problems with cm12, and carbon kitkat bootlooping when installing or restoring certain apps, so I just avoided those apps. Both are sweet roms, and I've tested the files you shared, work perfectly. I'm running carbon kitkat right now. I'll add the file and a few other fixes, to both roms and make them available on the appropriate threads. Thanks again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mstrswrd06:
I'll add myself to the Bluetooth issues here. Eventually would connect fine, but I honestly have more trouble with it automatically disconnecting when it's supposed to.

Mostly when I shut my car off, which the phone is linked to as a headset, but then I'll notice later that the phone still thinks it's connected to the car. Mostly noticing because Smart Lock is bypassing the pattern lock on the lock screen because my car is added as an exception in Smart Lock.

Experienced this with 5/12, 5/13, and 5/14. Installing 5/15 now to see what happens on my way home from work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Well, installing SuperSU will give you that ability and removing the #.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doomrt:
I tried builds up to 05/13, and the auto connect problem is still there. On the other hand, I didn't have any problem with pickup up, hanging up or sound quality since I switched to official nightlies...only auto connect, and sometimes disconnect. For now i'm on CM11, but i'm looking forward to try the next build with BT changes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
I agree. The Bluetooth issues keep me on 4.4.4 for now...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
AT&T i747 NJ1 modem/bootloader. CM12.1 05/14 Nightly with CM Kernel

I can now consistently hang up calls using bluetooth earpiece and voicedialing still works. I do still have the connect/reconnect issues with my Jawbone. I have not had any other freezes or random crashes or reboots even. Everything else with the phone appears to work except bluetooth. GPS, Compass, volume controls so far have all been great.

Back to bluetooth though. Here is where I do have a weird issue. I have an IOGear solar powered Handsfree. It worked when I was running stock (I think I tested when I still had Kitkat stock). It's been a long time sitting unused. I recently decided to try running it again and now have an issue with it. I will post pics below but here is the basic issue: I pair the device, it works. I turn off the device. It still shows as a paired device in Bluetooth settings. I turn on device, it doesn't connect, it then shows under available devices and trying to pair it again gets the error "Couldn't pair with .... because of an incorrect PIN or passkey." and then I have to clear bluetooth share to get it to pair again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
a few posts above yours. Several of us having this issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HamZusGh:
i have same problem in any bluild please help as we need a solution

We need help anyone can help ???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Post a log. otherwise wait for new nightly, or go back to one that works
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HamZusGh:
thanks man i am back to CM11

In kitkat it's cool i am waiting for the best buikd to install it please tell me if it work my phone is Sgh-i747m
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
The 5/16 nightly proved disastrous. After updating from the 5/15 nightly, it would boot into a black screen that only had the status bar. I could pull down the notification and quick start screens, but tapping on anything went back to the black screen with just the status bar. I couldn't do a log because I could not execute anything. I tried to go back to the 5/15 nightly, but it runs an infinite Optimizing app routine. When app 171 (the last) app is optimized, the phone reboots and goes back to beginning of optimizing. It's in one last round now, and then I'm going to restore my 4.4.4 nandroid backup. I don't see another way out at the moment except a factory wipe, and I don't have time for that at the moment.

The CM 12.1 nightlies have been so stable, this caught me completely by surprise, but I fully understand the natures of nightlies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
So, sounds like a problem using this AT&T build on the i747m phones??? Could the other people with reboot issues post their phone and basebands?

---------- Post added at 08:13 AM ---------- Previous post was at 08:12 AM ----------

Are you on an i747 AT&T phone or an i747m and what baseband?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HamZusGh:
i am an i747m

Baseband I747MVLUEMK5 Please help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kirkgbr:
[MENTION=6264827]HamZusGh[/MENTION] - Help with what? You've already been given guidance by gvsuikids.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Until now, I have never had a sim card go bad on me.

Text works fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rdoac:
Just upgraded from unofficial 4/26 which is the last one with reliable Bluetooth, however upon finishing the apps optimize I got Missing Sim Card. Going back to nandroid backup. This is dirty flashing 5/16.

Reporting it here in case anyone else has it. Using latest baseband/modem on at&t.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
It says "no sim card" after boot. Give it about 5 min. Also, you may want to get a new sim card. Mine used to take a while to connect. I just put a new one in and it connected almost instantly after boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
First post updated with status of known bugs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
i747 AT&T, NJ1 baseband. I restored my CM 11 nandroid and I'm up and running again on CM 11.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HamZusGh:
a solution

For the front camera in candycamera and retrica if a takr a pic the phone reboot automatically

I need just a solution for that
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
"Front camera reboots on certain apps is also a known issue and is intentional. Yes you read that right. This is a design choice."

That's very intriguing. Would you mind explaining the benefits of this design choice?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
There is a problem with apps that use video recording without properly setting that mode. This includes Snapchat, Skype, Hangouts video chat. I got tired of working around such apps and changed it to be compatible with them by default. You can take regular snapshots with any app but you can not really replace the functionality of the video chatting apps so I have chosen to ensure they work properly. This affects all cm based Roms.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Omarkoopa:
here is it on the sgh-747m

working fine yup ... just i wonder why when i flashed the 05/16 first boot sayed no sim card i waited about 3m then it reconized my sim card .. while i didn't face any random reboots but i don't know still waiting :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
"Bluetooth issues should be fixed in 5/17 build."

This certainly puts a smile on my face! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ngotan9:
headphone not working in 16/05 buid. help me! how to my fix?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
On the coming nightly change log next it would be some fixes for Bluetooth. Just wait tomorrow nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HamZusGh:
thank's

U can fix the problem of the front camera too ? And thank's for that i have i747m
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
I am running into an trouble officially registering an issue with CM12.1. Since it has not has a milestone release, the official bug tracker cannot be used. And since it is something that has never worked in CM12.1, it cannot be registered in the regression testing tracker either.

This issue is lack of support for dock audio. When you dock the phone, audio continue to be routed through the phone speaker or 3.5mm jack, rather than through the dock. I'm not sure if support ever made it into CM11, but I do know that it made it into CM10. The good news is the work was done in CM10, and probably just needs to be ported to CM12.1.

In CM10 there were 3 issues which together addressed the problem - 25274, 25279, and 25281. One of those changes actually added settings to control whether or not sound would be directed through the dock when docked. I think that was later removed in favour of always directing audio though the dock if present.

Is there a way to get this information to the right people sometime before a milestone release?

Or are the right folks watching this board? I don't think so, but that would be great!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
[MENTION=2044079]Nardholio[/MENTION] is the maintainer of this thread. He would probably know who to talk to.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AsureDawn:
Hmm? That's weird, I've been on MJB since forever--CM12.1 works fine for me. Maybe I was stealth-upgraded? Baseband is still MJB in About Phone, but ro.build.description is "d2uc-user 4.4.2 KOT49H I747UCUFNJ1...". Oh well, it's working for me, so that's all I care about. :D

Anyone on the latest nightly? I'm on 05/10 and it's working fine, don't want to upgrade if there are regressions. Don't use bluetooth much, so can't really comment on that. I do know that I've had issues staying connected to my router with WPS, whereas using a passphrase works fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InsaneDDay69:
I'm on the 5/17 and it seems to be working just fine. Not sure if Bluetooth is fixed as I don't use it very often and I haven't tried it yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rdoac:
Bluetooth seems better, but not fixed. I have a pebble and it disconnects every few hours. Sometimes turning BT off and on is enough, other times BT won't turn back on and I have to reboot. I don't always notice, but it's dangerous if I'm driving and the phone rings and BT is not working as I can't pick up the call on the radio thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zeezerzots:
Yep, same here on 5/17. I have a Moto 360 and it will disconnect from bluetooth in about 5-10 mins. If I try to do something on the watch, it will reconnect in ~10 seconds. Then disconnect after 5-10 mins again. But it's better than it was before.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
I have a different Bluetooth issue. It connects to anything I hook it to rock solid. But sounds are slightly crackly and a bit slow. Files transfer easily and it always turns on and off only when I toggle it. I'm not a big Bluetooth user tho.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Instead of rebooting when Bluetooth dies, force close the Bluetooth Share app via Menu > Settings > Apps > Bluetooth Share.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doomrt:
Are you sure awesome player isn't still on? Its exactly the issue it causes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Reboot phone then hit switch
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
After testing that way, I toggled it this way and rebooted and checked again. No real difference at all. Crackly and slow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
I'm on this:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Oops
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InsaneDDay69:
The only issue I seem to have with Bluetooth is my Google music app plays slowly through my headset. App works fine on my phone speaker. There's a little bit of crackling, but I could handle that.

Sent from my Lollipopped Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I've had crackling in my Bluetooth since cm10. No one would ever agree that they were having the same issue.

I'm still on 05/14 right now. And I've noticed a weird issue. I have notification volume separate from ringtone volume. But I was just unable to adjust the notification volume at all from the expanded on screen display as shown below:(it's the third one shown with the bell on the left. It won't move at all)

But I could still adjust it here:

All other volumes adjust in the drop down just fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
Yes, after the 5/16 gave me an unrecoverable black screen, I restored my 4.4.4 backup. Everything works perfectly on CM 11 4/26 nightly. I've since loaded LiquidSmooth 4.1 (Android 5.1.1) and LTE works fine on it w/o deleting any APNs. BT also works well on LS 4.1. It appears that the CM team has made kernel or driver changes that adversely affect both data connections and BT operation.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Maybe [MENTION=2044079]Nardholio[/MENTION] can get with amf66 and matrix and they can pick through the LS 4.1 code to see what the differences are? I think it's more like CM has a generic codebase and nard is having to tweak it for the s3 and LS has a codebase that's more unique to each device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Liquid is playing conservative. Liquid code base is old and does not have the latest commits. They do not have the latest commits from CM. And it seems one of the latest commits could be the reason of the reported issue. I am sure nard is working on fixing the reported issue
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Ok. If he knows how old their base is, then maybe he or someone else can trace the commits to find the Bluetooth related ones only...

I wonder if there are other devices having the same issues. Maybe the stack is broken in some way for most devices.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rnagam1:
I am running 5/17 nightly on att s3. I noticed the following issues:

1. When the bluetooth is on and then I turn on my car, the phone does not auto connect to the car. I have to manually go into settings on the phone and connect to the car..

2. When I switch music bluetooth streaming in my car, the music player on my phone does not start automatically. I have to open the music player manually on my phone.

3. When in Battery saver mode, the app icons within a folder don't show. When I tap on a folder, an empty screen comes up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpiderNhan:
Anyone else notice that the UI(swiping between home screens and app drawer, scrolling within menus and apps) is a bit laggy on the 5/17 and 5/18 builds? I flashed back to 5/16 and earlier builds to confirm and those builds all perform smoother.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Laggy scrolling menu in app drawer is caused (on my phone anyway) by Google launcher.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I'm about to go from 05/14 to latest 05/18. I use nova launcher so I'll report what happens.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Look like the earliest commit to be included in the next nightly might address dock audio! It at least adds the analog dock as an output device in the audio policy file. Looking forward to trying it tomorrow.

FWIW, I'm on the 5/12 build. Spent a couple hours on a call today using a bluetooth headset. Never an issue. From what I've been reading here, it seems like the bluetooth issues may be dependant on the particular bluetooth device being used. Even ended the call using the headset. Hopefully I don't lose all that goodness when I update tomorrow morning.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Reboot while charging

https://docs.google.com/file/d/0B7u_Do3wdBUTdWsxeDAzMjUxVmM/edit?usp=docslist_api
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
Not sure what's going on, but when I use kernel aduitor, MPDecision is turned off and I have to manually turn this back on. I'm not sure if this is the app itself misbehaving or what. I think this happened with TW 4.4.2 too. Can anybody else install this app and double check for me?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
Mine is turned off by default in the app as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
Oh good, it's not just me. Why is that happening? Is it the app? 2nd core never goes off if that's turned off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] franko2100:
Wifi Direct not working !!!!

What about WiFi Direct at this Rom i canot use it i can do connect to it but cannot use

cannot send or reseved any thing with WiFi Direct

No icon to wifi direct at CM12.1 !!

plz help me

i have last update but no new plz need answers

:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mringer:
Android Wear issues....

First of all, thanks to all the contributors....much appreciated. I wanted to mention an issue I have with my Moto 360 watch. I am having constant disconnects and intermittent sync issues. If needed, I can post a syscat log. I know one way to induce the problem, is to wear my watch out of range of the phone and then it will not be able to reconnect. A reboot will fix the issue...and even toggling bluetooth on/off will sometimes fix it. I've seen some other mention of bluetooth issues but nothing related to android wear...so wanted to throw this in also.

Thanks,

-Mat R
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Which nightly are you on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mringer:
Currently on the 5/17 release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
On 05/18 and scrolling on nova launcher is smooth. Other ui animations seen smooth as well. This was even a dirty flash from 05/14.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Matt_the_Geek:
Still on the 5/13 build, and it's been working well for me. I don't really use bluetooth, so that's not been an issue for me. And flashing to this ROM brought my GPS back to life, it had died when on the LS 4.4.4 ROM.

Anyway

On that ROM you could turn on the Network Speed Monitor kind of thing that showed your Network in/out speeds on the Notification bar, any chance something like that can be implemented?

keep up the great work!
[8125, K-JAM, P4300, MDA Vario ROM Development] ANTC:
Well I saw a thread in the hermes section and thought It would be nice to have it here..

so whos the best chef for our wizard?

ANTC

faria

mfrazzz

mattk_r

anichillus

Nottoosmart

MuN

funman

jwzg

Sorry if I forgot anyone I tried too look though all the Wm6 threads..I wish there was a subsection in the WM6 section for ROm releases..

But here take your pick
[8125, K-JAM, P4300, MDA Vario ROM Development] bowlopho:
i pick mfrazzz

I would pick faria, but im using mfrazz suped up version of faria's

and cause i see mfrazzz all over the forums giving pointers all over the place. that or because his icon just pops out at me so i look at his name. it's one of those reasons i swear
[8125, K-JAM, P4300, MDA Vario ROM Development] Vilem:
ANTC, it's bad enough that you think you are a chef, but putting yourself in a list with mUn and Faria is too much.

I hope your parents know your trying to ruin their expensive device.