yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
When I was running 10.2.1 i would have an issue where if i used headphone to listen to pocket cast (possibly any app) and when i quit using headphones the audio would not work over the speaker anymore (notifications, phone calls, and such) unless i reboot or sometime using headphones later would fix it.

I was hoping a clean install of 11.0 M3 would resolve the issue so i installed it over the weekend but today i'm back to having audio stop after using headphones. it's like it's stuck in vibrate mode or something?

Has anyone else had this problem or know what the deal is?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Somehow, the broken ART issue also caused me to not be able to get into twrp. I'd see the initial logo for twrp then boot loop. Somehow, pulling the battery,I was finally able to get into twrp and restore. I only posted this in case someone else sees similar.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phaze13:
Not ROM related at all. 90% sure the headphone/speaker issue is related to the jack on your headphones. This happens to me as well with the aux input in the car. A quick plug in/out with the stock headphones fixes the issue.

I'm assuming the jack in my car must have ****ty tolerances and the phone believes the headphones are still plugged in after unplugging, hence why there us no sound from the speaker.

Could also be that after 18 months the headphone port in the phone is wearing, anyway pretty sure it's hardware related.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
Thanks, this makes sense and acts just like you are describing. Happens all the time from car connection but not often with headphones.

Stinks it crapped out barely 2 years old.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Try using SuperSU if you're not already. I think I had this big when I was using the default superuser.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Good news(unconfirmed)

We can hope for the CM12 in near future for our device. CM has started work on CM12 for our device. I was going through the github and noticed the CM12 tree for our device

https://github.com/CyanogenMod/android_kernel_samsung_d2/tree/cm-12.0

https://github.com/CyanogenMod/android_device_samsung_d2-common/tree/cm-12.0

Reports are hinting for the CM nightlies to be available by end of November or early December. Fingers crossed

I think invisiblek is the man behind this development

I was planning to purchase new device, but if CM continues the development I will stay.

Enjoy!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CFoote:
Maybe we should start a donation pool for invisiblek? Even a few bucks per person would go a long way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] korrectmethod:
Well his PayPal donation is dan.pasanen@gmail.com

I'll probably donate a few dollars.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tomerFire:
My camera on CM11 is not working.

Please help me in this issue:

http://xdaforums.com/galaxy-s3-att/help/camera-stock-rom-t2943803
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
this has been an issue for a while.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
My camera works just fine. In the nightlies.

*thumbs down M releases incessantly*
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tomerFire:
What is your modem version?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Absolutely unrelated, but I747MVLUFNH2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tomerFire:
Do you have any guess what can cause my problem?

Fireware? kernel? recovery? ROM?

Im trying to fix this issue for 3 days with no luck.

BTW:

Here is my phone full info

http://xdaforums.com/galaxy-s3-att/help/camera-stock-rom-t2943803/post56830391#post56830391
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yes, you're running the M12 releases. Not a nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tomerFire:
Is this the last nightly?

cm-11-20140217-NIGHTLY-d2att
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yes.

Here's a picture taken 1 second ago with the camera.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] korrectmethod:
M12 camera working fine here. Dirty flashed over m11.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tomerFire:
I cant install CM11 because I updated my firmware to NE4.

But I have installed cm-10.2.1-d2att_for_NE4 and the camera still no working...

Only on stock ROM after disabling KNOX my camera works.

Maybe it kernel issue? root?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ominousnimbus:
A clean install of M12 is finally bug-free for me (insofar as I can tell), after so many issues with both nightlies and Ms the past 1-2 months.

However, dirty flashing M12 (or any recent nightlies) over old nightlies from September resulted in broken wifi hotspot, for some reason. Just in case anyone out there happens to run into that, clean install fixed it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisn812:
tomerFire, are you saying I can't install Cm11 if I'm on NE4? I've been running SR3x but wanted to go back to CM11.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tomerFire:
You cant.

You can install cm-10.2.1-d2att_for_NE4 and then upgrade from the phone to CM11 but I dont think its nightly version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
That's misinformation. Plenty of people are running NE4 and cm11 nightlies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tomerFire:
When I tried to flash CM11 on NE4 I got wrong asset error.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
What was the full error? An assert fail means CM11 didn't flash, usually to protect you from something wrong you're about to do.

If you look inside the zip file of the cm-11-20141120-NIGHTLY-d2lte nightly for update-binary you'll see this assert:

assert(getprop("ro.product.device") == "d2att" ||
getprop("ro.build.product") == "d2att" ||
getprop("ro.product.device") == "d2spr" ||
getprop("ro.build.product") == "d2spr" ||
getprop("ro.product.device") == "d2spi" ||
getprop("ro.build.product") == "d2spi" ||
getprop("ro.product.device") == "d2tfnspr" ||
getprop("ro.build.product") == "d2tfnspr" ||
getprop("ro.product.device") == "d2tmo" ||
getprop("ro.build.product") == "d2tmo" ||
getprop("ro.product.device") == "d2cri" ||
getprop("ro.build.product") == "d2cri" ||
getprop("ro.product.device") == "d2mtr" ||
getprop("ro.build.product") == "d2mtr" ||
getprop("ro.product.device") == "d2usc" ||
getprop("ro.build.product") == "d2usc" ||
getprop("ro.product.device") == "d2vmu" ||
getprop("ro.build.product") == "d2vmu" ||
getprop("ro.product.device") == "d2vzw" ||
getprop("ro.build.product") == "d2vzw" ||
getprop("ro.product.device") == "d2lte" ||
getprop("ro.build.product") == "d2lte" ||
getprop("ro.product.device") == "d2can" ||
getprop("ro.build.product") == "d2can" ||
abort("This package is for device: d2att,d2spr,d2spi,d2tfnspr,d2tmo,d2cri,d2mtr,d2usc,d2vmu,d2vzw,d2lte,d2can; this device is " + getprop("ro.product.device") + "."););

If your device isn't in the list, it won't flash.

Second, you'll see otasigcheck.sh is also extracted and ran to verify once again the compatibility of the installation:

#!/sbin/sh

# Validate that the incoming OTA is compatible with an already-installed
# system

grep -q "Command:.*\"--wipe\_data\"" /tmp/recovery.log
if [ $? -eq 0 ]; then
echo "Data will be wiped after install; skipping signature check..."
exit 0
fi

if [ -f /data/system/packages.xml -a -f /tmp/releasekey ]; then
relCert=$(grep -A3 'package name="com.android.htmlviewer"' /data/system/packages.xml | grep "cert index" | head -n 1 | sed -e 's|.*"\([[:digit:]][[:digit:]]*\)".*|\1|g')

grep "cert index=\"$relCert\"" /data/system/packages.xml | grep -q `cat /tmp/releasekey`
if [ $? -ne 0 ]; then
echo "You have an installed system that isn't signed with this build's key, aborting..."
# Edify doesn't abort on non-zero executions, so let's trash the key and use sha1sum instead
echo "INVALID" > /tmp/releasekey
exit 1
fi
fi

exit 0

This part pretty much verifies if you have wiped properly. If you haven't, it won't install.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tomerFire:
In the update-script file you will find this:

As you can NE4 is not in the allowed bootloaders.

You may have CM11 with NE4 if you flash CM11 before you had NE4 bootloader and after this you updated your bootloader to NE4.

**Checked on cm-11-20140217-NIGHTLY-d2att**
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You're checking a 10 months old nightly, obviously it doesn't have a bootloader that got out AFTER this date.

d2 devices got merged in February of this year and are now all under d2lte.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tomerFire:
Ok, I see it, thanks!

---------- Post added at 09:38 PM ---------- Previous post was at 09:29 PM ----------

I flashed cm-11-20141120-NIGHTLY-d2lte.zip camera crashes...

After 5 reboots it working!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tomerFire:
I have flashed the new nightly and its working ok.

The first time I flashed it the camera didnt work. I made a few reboots and the camera worked. After one more reboot it didnt worked again and I couldnt make it work again.

I tried to reflash the ROM and the camera still does not work.

Here is a vide of the crashing camera:

https://www.youtube.com/watch?v=Zh7vkEcmqrk&feature=youtu.be

In the video its a fresh new ROM after full wipe + advanced wipe using openrecovery-twrp-2.8.1.0-d2att

gapps is minimal and containing only google services (I also tried without google apps it makes no change)

I also tried to set "fixed" camera from here:

http://xdaforums.com/galaxy-s3/themes-apps/17-fixed-camera-app-lib-cm-aosp-roms-t2505973

The camera crashes, same issue.

In the attachment you can see my phone details.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
When you say full wipe, what do you mean exactly? Did you wipe system, data, cache and dalvik?

Try clearing the data for Gallery2/Camera in the app details, rebooting, then trying it.

Also, where are you getting your gapps?

I can't vouch for the 20th nightly, I'm currently on the 16th as I've had no time for myself (or the phone) so it's entirely possible it's bogus on it, but the fact you're having so many camera issues with any CM version so far seems really strange.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tomerFire:
Yes I wiped system, data, cache and dalvik (even root).

I deleted Gallery2 and Camera2.

I installed the Gallery2 app from this thread that someome said that it can fix my issue but its does not work.

http://xdaforums.com/showthread.php?t=2542700

Third party camera apps also does not work.

My gapps is from here: http://xdaforums.com/showthread.php?t=2397942

I installed this version: pa_gapps-modular-pico-4.4.4-20141110-signed

I may ask on CM forums....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Gapps is fine. Don't delete camera and gallery, just clear the data and cache for both. Both work mighty fine for me under the 16th nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] monkeysez:
Good bye cm11 thread. Time to unsubscribe. Hello Cm12 thread. How you doing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Wow, already?

Link please...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
Here's the discussion. It's still a very early alpha.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CFoote:
So I have to say, I was a bit skeptical to try the CM11 builds on my GS3, but so far I'm pleasantly surprised.

It's not as 'snappy' as CM10, but still quite reasonable. No reboots so far (2 days in), we will see how it works out.

No GPS issues for me either, but I was on MJ2 (same as NE4 but without KNOX/e-fuse) before I upgraded. GPS locks quick - within seconds.

So far so good, I'm thrilled they will develop CM12 for this phone.

Chris
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] realist123:
So looks like the CM12 thread is closed and the OP's account is disabled, which is too bad because I really appreciated his work.

Will anyone be able to pick up working on CM12 builds?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BottleB:
Account disabled also? Damn.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tony_YYZ:
Just refreshed the thread and saw the Mod lock msg. It states that the thread was closed per OP's request. I wonder what happened.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] korrectmethod:
A member pointed the OP to camera fix for cm12, OP insulted person (not sure why), member reported post and shortly after that the thread was closed. Back on topic.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cfili:
Cricket Wireless

Hey guys thinking about flashing this on my AT&T S3. However, I am on Cricket wireless will I have any problems?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
U should be able to use any ROMs found here just BACKUP and flash away!! always make a nandroid first so u can restore if something goes wrong!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Can anyone access http://stats.cyanogenmod.org/? It's been down for a while for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pandasa123:
CM

Hey guys, I just finished uploading to the build server I use. Let's see how this server fares before deciding to switch to AFH (consistency issues). If it turns out that a lot of you guys really want another hosting site, I will gladly set it up (except Dropbox, Google Drive, or MEGA because of download hits / annoying compliance issues)

But without further ado, http://downloads.codefi.re/pandasa123/CM12/Samsung/d2att

Have fun flashing and give me some time to set a thread up. Thanks :)

---------- Post added at 11:13 PM ---------- Previous post was at 10:45 PM ----------

Also, here is the thread link. Banter / off-topic is allowed, but keep it respectful. I'll let you guys use it as a Q/A too as long as you guys search before posting

http://xdaforums.com/galaxy-s3-att/orig-development/rom-cm12-d2att-alpha-builds-t2959561
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ButtonBoy:
Latest Play Store?

I've been updating my i747 to the latest build of CM11 about once a week. My latest was from mid last week. I saw my phone reboot itself today right after it downloaded the new version of the PlayStore app. It has rebooted every time I launch that app since then, and has other anti-social behavior as well. Anyone else seen this? I will try to get more information about the precise version of CM11, and my radio stuff.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Click play store clear data, remove your Google account from the phone, reboot and add your account again see if that helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ButtonBoy:
I figured it out. It turns out there is a problem with Clueful Privacy Advisor, which was actually doing the bad stuff. As soon as I removed that, all my troubles went away. Never needed to clean/reinstall the Play Store.

That said, a bad app should never cause the underlying O/S to go down.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
Hi guys, may i just ask, is it worth it to flash nightly builds than milestones? Thanks and what custom kernel would you recommend with cm11?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] korrectmethod:
For max stability, flash the latest m release. Usually the nightlies are fine but occasionally things like GPS are broken. Cm11 comes with it's own kernel when you flash the ROM, I'd recommend sticking to that.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sketch2k278:
All I saw were nightly builds no milestone releases
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ThreeofNine:
The last stable rom was the cm-11-20141112-SNAPSHOT-M12-d2lte.zip of Nov 12th. I wonder if there will be a M13 snapshot? :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
I think we should have M13 which could be the last M release on CM11. Expect this in the next couple of days!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
I have build unofficial cm12 build and have posted the link on the at&t help section.

Link

http://xdaforums.com/showthread.php?p=57390988

This build has the home button fix, camera is still broken.

Thread Link:

http://xdaforums.com/galaxy-s3-att/development/unofficial-cyanogenmod-12-t2968854
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Guys if you want to fix the camera on CM11 and upcoming CM12, please vote and post the logcat in the following CM Bug tracker:

https://jira.cyanogenmod.org/browse/NIGHTLIES-402

This has been assigned to the best developer in CM - Dan Pasanen

This will help to increase the importance of this bug and provide more data points to the CM developer to fix the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
After having trouble recording Videos on the latest Google camera app I ended up uninstalling the latest update and deleting the DCIM folder. It's been working since then.

Thanks for the bug tracker info. This definitely needs fixing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Stock camera app is working for you?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mervingio:
I use the Verizon S3 CM 12 version and install Camera FX and works instantly [emoji15]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Third party Camera apps are working on all builds of CM. CM accepts the bug reports only for the stock CM apps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
I am talking about the official Google camera app from play store. That has given me lot of trouble.

Last version was giving me lot of troubles with videos. Force closures and can't connect to camera errors. I used this thread to install the fix.... Its been fine since then.

http://xdaforums.com/galaxy-s3/themes-apps/17-fixed-camera-app-lib-cm-aosp-roms-t2505973

This is the file I am using : "Fixed Cam for CM 10.2_CM11 V2.3.zip"

Also delete your DCIM folder after backing up. It will get recreated automatically.

Without using the above fix even third party apps such as camera zoom fx was crashing with same errors as original Google camera app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mervingio:
Sorry man but I tried a lot of camera apps on your latest and only got black screen and reboot damn

---------- Post added at 09:06 PM ---------- Previous post was at 09:03 PM ----------

I will try it later
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
The mobile in on which bootloader version? Clean install?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mervingio:
No but in others cm 12 Roms Camera works yes clean install T999L
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikeRWK:
I came here because my camera stopped working but didnt expect to see its a common problem.Mine was great until I tried to switch from 1080p to 480p to make a youtube video.I'm going to try and edit the setting back to 1080 manually I just forget where the camera settings are stored, a search will turn that up quick.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikeRWK:
Tried the 2.3 and 5.0 fixes, camera works for about 3 seconds jesus ****ing christ this is pissing me off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kenetix:
A few issues

On the 1/03 build, my camera wouldn't work. And then my phone started to heat up in my pocket and within an hour, it completely discharged the battery. I hadn't had that happen since i owned my infuse. Is this rom overclocked ? Anyway, it has always been a solid rom, and this is just a hiccup. Thought i would let you know. Thanks for the hard work everyday.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
It's been mighty quiet here lately.

So what is going on with the nightlies? Commits have been bare minimum? Anyone wana update us?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nirogu325:
Information here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
Sadly, I don't see d2lte on the L list, which is surprisingly short. Perhaps the maintainer has not gotten around to putting an initial build together.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
d2lte is no more! It's deunified again. Going forward, its back to individual builds d2att, d2tmo, d2vzw, d2spr, etc...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
Thank you for the update!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bilal132:
camera Bug

stock cm11 camera again not working on latest nightly (2015-1-11). :( is there anyway to solve this problem???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Wait for next M release..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bilal132:
[MENTION=4551784]matrixzone[/MENTION]. i am experiencing heavy battery drain on CM11 roms. but on stock kitkat rom i have a little better battery backup.

when i Flash CM official rom and connect to charger it does not charge my cell phone. it stuck several hours at same percentage and also charging timing is worse than stock rom. I just wana know that is it normal when someone flash a new CM11 base rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
None of what you mentioned is any kind of normal, for any Official ROM, however nightlies often have a lot of bugs & problems stick to the M builds & always clean flash to avoid issues, I recommend flashing in recovery over, the cm updater, or installer, but that's just my opinion!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
I was having high battery drain issue as well. Now i have greenified everything that was bothering me. Plus I am using an app called disable service, and disabled quiet a few Google Play services. My battery life now is amazing :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Disabled services...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] korrectmethod:
As always with this ROM, I'm getting complete wakelock. Out of 15 hours, it didn't deep sleep once. Will this EVER be addressed? This is a continuous issue with this ROM. I'm done with CM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] canodroid15:
Probably not, as the focus is shifting towards CM12, it is odd tho! I've experienced this 2 as well as my phone temp getting so hot I had to take it out of my pocket. This happened on almost a bone stock run, almost no apps at all. Even changing the kernel didn't help. Its been awhile now tho I've been on lollipop since the first builds started floating, anyway? Sorry for the RANT! I know how ya feel bro!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] korrectmethod:
That's pretty much what I've been getting. I'm going to try the latest nano modular gapps and hope that fixes it. There are still quite a few bugs that make LP not an option for me yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
I had these issues in the past both on the stock ROM and CM. On CM, I was able to isolate the issue to Google apps resetting push capabilities on after updates as well as some Google APIs for the health system calls. If you search the Net, you will find information on disabling the appropriate APIs using the Disable Services app. You also have to diligently root out the Gooble push apps - email, Google+, etc. Once I handled all that, my battery life became excellent and the overheating mostly disappeared. On rare occasions when my phone heats up for no apparent reason, simply restarting it fixes the issue. I suspect that a bad app is not closing a system call, but haven't been able to nail it down. After taking the previously-mentioned measures, the overheats occur very rarely. On the stock ROM, the overheats were a regular occurrence and I could never nail down the cause.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] korrectmethod:
Clean flashed, installed nano modular PA gapps, and installed deep sleep battery saver. It's working for now but we will see.