yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] legendrocker:
Yes, I guess it's not only from CM roms then. I guess I should say anything other than TW rom?

I tried pure CM too but same thing... any variation of CM rom does this. I tried Paranoid, AOKP, Liquid Smooth, Bean Stalk, Slim, and they all give me this weird sound when unlocking. Driving me nuts!

I always do internal sdcard format when I install new roms to avoid potential problems (I'm a fan of super clean installs).

I haven't tried reverting back to stock but I know I went through step by step process of rooting and all was done correctly...

It seems like only my phone does this, and I think I've seen a couple of other people raising similar issues but noone was able to provide any solutions. I can't even find this particular sound in my phone, so it's gotta be some sort of a random bug??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
You definitely have a weird issue. I believe you when you say that you followed instructions and did it right. Only because you say you have not tried it, it may be worth trying going back to stock. Grasping yes, but I don't know what else to suggest.

Good luck!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Doomstick:
Back when I was on rc1 there was an issue with the phone trying to play all sounds through the ear speaker after plugging in headphones and then unplugging them, or going completely mute. Checking to see if that's sorted out yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Try to clean your USB port with isopropyl alcohol and a toothpick. Get all the grime out of there and make sure the contacts are perfectly clear.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jblparisi:
CM 10.2 Stable is out for those that care.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Agreed. That's nuts.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Anyone has i747 at&t and rom flash Ok with on fail in twrp

---------- Post added at 02:25 AM ---------- Previous post was at 02:23 AM ----------

I have 4.3 ota and I just rooted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jblparisi:
Working fine here. Make sure you are running the latest twrp.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
What bootloader do you have.I have i747UCUEMJB.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jblparisi:
Yup, same one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
flashed the stable last night right before bed and got the best battery life overnight that i've gotten in a looooooong time. .6%/hr drain with wifi on all night. now i hope it lasts.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Not sure how CM defines stable and decides that its time to release a stable build but there are still a number or major outstanding issues on both d2att and cross platform.

They really should just call it and end point of production cause that's all it is. The 2013 models are no long being made but the 2014 models are available on the lots. Doesn't mean the 2013 are suddenly perfect.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Well got this rom set seems to be the only rom I can flash because of the bootloader I have.

Now I was wondering about kernels. Way back when when I did use cm builds never had to do to much with flashing of the kernel but I like the options.

Also mods to flash with this rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhomiec:
this might be a stupid question, i couldn't find anything mentioned in this thread.

is updating the bootloader required for CM10.2.0?

i'm still on UCDLK3. and running CM10.1.3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
I would be careful about updating the bootloader. Because I did some messing around and I hard brick my phone and it took awhile to get it back. But I'm on i747UCUEMJB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I've had good luck with the recent nightlies, for that matters. 1120 to 1202 seems to be faring well, so not super surprised about the stable being a continuation of those.

You can flash other roms with a simple updater-script edit. Add your bootloader in there and done.

No.

Supported bootloaders by the stable

assert(getprop("ro.bootloader") == "I747UCDLK3" ||
getprop("ro.bootloader") == "I747UCDMG2" ||
getprop("ro.bootloader") == "I747UCUEMJ2" ||
getprop("ro.bootloader") == "I747UCUEMJB" ||
getprop("ro.bootloader") == "I747MVLDLK4" ||
getprop("ro.bootloader") == "I747MVLDMF1" ||
getprop("ro.bootloader") == "I747MUMBLK3" ||
getprop("ro.bootloader") == "I747MUMBLL1");
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
You bricked it because you tried to roll back from the latest. There is a "feature" that Samsung has implemented that bricks your phone if you try to roll back to an earlier bootloader once you are on the one released with the 4.3 official update. You will hear to it referred to as efuses.

There should never be any reason to downgrade once you do upgrade so there should never be an issue. Some guys though are getting confused with the asserts and the missing new bootloaders from them. They are then being told to update their bootloader to LK3 which in some cases is a downgrade and will brick your phone.

The misinformation and the assert not containing all the eligible bootloaders for some ROMs is causing a few guys like yourself some major headaches.

You can easily find a list of all bootloaders for our phones. Check to see if you are running LK3 (for AT&T users) or newer which you are and if you still can't flash you need to contact the ROM dev to get it added in or edit the script yourself which is a pain.

As it stands all the new AT&T bootloaders have been added as of the other night in CM. We are just waiting on the M variant to be added and I have already contacts the guy about it. I just need to run some tests to make sure it works probably and is safe to add.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Ha I just contacted Jiangyi about it, hope we're not both messaging him haha >_>
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I messaged him the other night about it but he wants me to make sure its stable and safe to add. I'm just waiting for dstruck2k to repost the zip flashable bootloaders so I can try it out for a day or two. I'm too lazy to go back to stock to get it.

The bootloaders were removed because too many people we borking their phones with them he wanted to make them a little more fool proof before he released them to the masses again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Ah alright, guess I'll crawl back under my figurative rock. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Thanks flex. And I'm not editing any props to the bootloader I'm happy with cm 10. Do far so good. And Yea that's what happened to me because I remember Lk3 was older and I have the mjb Idk why I did it lol. But I'm glad it's all going good now and able to flash at CM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
You know these asserts are really coming back to make a mess of things. I remember I posted on here a while back when they were implementing them and I asked why not make it a list that makes sure you DON'T have a certain bootloader installed instead of making sure you have one installed off a predetermined list. We knew which ones didnt work and were almost 100% sure all new ones going forward were going to be okay. My way you wouldn't have to add any new bootloaders as the come out. That idea was shot down at the time for reasons I don't really agree with. Either way, my idea is sounding a whole lot better now and is a lot less hassle.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yep, excluding older bootloaders would seem like a better idea rather than including new ones every damn time. Because let's face it, in the terrible event one new bootloader doesn't act nicely (not likely to happen), you can just add this one to the blacklist. This makes sure anyone installing the NIGHTLIES doesn't have to edit the updater-script for a few weeks before changes get merged...

As for the stable and RCs, couldn't really care less.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
http://xdaforums.com/showpost.php?p=43126339&postcount=14461

In case anyone is interested in reading my original post about the assert being a blacklist instead of an ever changing white list and the reason why they didn't want to do it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
Flex,

Where did you find a file to flash the latest bootloader? I've been unable to locate it.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
http://xdaforums.com/showthread.php?t=2321310

They have been removed temporarily but should be back up sometime today.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
.. Wasn't there a goodies page for CM10 like kernels, mods, hacks etc. I've been looking and I've seen some stuff but date for 2012.

---------- Post added at 10:43 AM ---------- Previous post was at 10:40 AM ----------

Also was there a post/thread already for the cm11 I think it was the unofficial version of it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Most mods and hacks are a bit deprecated I believe, considering the advancement in most custom roms (including CM)

As for kernels, all the popular ones are available in the subforum(s).

Off the top of my head, the ones that are maintained:

BMS

LeanKernel

KT747

QuantumKernel

dkp
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
Gotcha. That's where I had been looking but never saw the latest BL. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
http://review.cyanogenmod.org/#/c/55061/

MK5 is being added to the assert in the next nightly for us Canadian users looking to update our bootloaders.

Once again remember that this only makes it a valid bootloader for CM based ROMs build after tonight. It will not magically make any builds prior to tonight work, like RC1 for example.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
Is it worth flashing the latest bootloader now? Or should I wait until CM11 nightlies (which I probably won't jump on right away)? I'm on UCDLK3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
No it's not really worth flashing the bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I'm under the impression that newer is better and that there will be some under the hood improvements.

There really is no need to update though. As always you run the risk of something going wrong. If it ain't broken don't fix it is the safest bet. Plus it will become a royal pain to flash any older ROMs if you see something else that you like. Its not guaranteed to have the new one added in the assert.

I on the other hand will be flashing the new bootloader out of curiosity more than anything. I understand the risks and that I am forever handcuffed to the new one as you can't downgrade. If you dont understand then dont flash it. There is no harm in staying on the older ones that are in the assert.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
Thanks for the quick responses, Team Canada! :) Appreciate having knowledgeable people who don't mind giving advice to the rest of us in the thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cryceratops:
What exactly does it mean if you flash a new bootloader? Can you not go back to certain ROMs after that, or is it for TouchWiz/CM only... sorry for the noob question, but I've had a lot of confusion about this whole new bootloader thing. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
No question too stupid regarding bootloaders, it's somewhat complicated, and it's like multiple questions in one.

In a few (many?) custom roms based off CM mostly there's a check that verify which version bootloader you have. If your bootloader isn't in the list, it won't install. This is because some bootloaders in the past have proved to be unreliable and to cause problems so they have been blocked.

The issue is that if your bootloader is "too new" then CM won't have added it to the list of accepted bootloaders yet. Galaxy S3 US variants bootloaders all have been added, so no issue there. Canadians haven't been this lucky, but starting tomorrow the new bootloader will be added.

As for not being able to go back, if you go to the newest US bootloader, you cannot use ODIN to go back to a stock 4.1.1 TW or you will brick your phone. Although I have not tested myself, I imagine this to be similar for the Canadian variant.

This can be somewhat problematic if you want to roll back for whichever reason obviously.

Also, custom roms that didn't add the new bootloader because they were created prior to the new bootloader appearance won't install if they have a check for the bootloader, such as older CM builds and others.

Overall, it's a complicated fiasco. The bootloader check in CM update-script becomes a nightmare for less informed people, some go as far as rolling back to previous TouchWiz builds thinking that might fix the install, and then brick their phones.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
The problem if you want to call it that way is that you can't downgrade the bootloaders. If you try you will gain a new paper weight or jtag.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cryceratops:
Very informative, thanks. If the new Canadian bootloaders are being added tomorrow, does that mean for the newly released stable version of CM 10.2 for the S3, it does not include the new bootloaders? So attempting to flash that from a 10.1 install would fail? Also, you cannot Odin back to 4.1.1, but I assume you're safe to do so for 4.1.2+?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
assert(getprop("ro.bootloader") == "I747UCDLK3" ||
getprop("ro.bootloader") == "I747UCDMG2" ||
getprop("ro.bootloader") == "I747UCUEMJ2" ||
getprop("ro.bootloader") == "I747UCUEMJB" ||
getprop("ro.bootloader") == "I747MVLDLK4" ||
getprop("ro.bootloader") == "I747MVLDMF1" ||
getprop("ro.bootloader") == "I747MUMBLK3" ||
getprop("ro.bootloader") == "I747MUMBLL1");

Those are the bootloaders supported by the stable build. Any other bootloader, including the latest available I747MVLUEMK5 for Canadian users are not in there, thus will throw an error when installing from CWM or TWRP. You can circumvent this pretty easily though by manually editing update-script in the archive.

Attempting to flash from 10.1 to 10.2.0 stable is not an issue if your bootloader is in that list. Common flashing procedure is to follow (wipe stuff, make sure to install latest gapps)

Downgrading:

No you are not safe. Downgrading from 4.3 to 4.1.2 via ODIN to return to stock will brick your device. I keep writing 4.1.1 for some reason, but I mean 4.1.2. Simple typo.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cryceratops:
I see, so I suppose the only safe way to Odin to stock is through a stock 4.3 image then.. which I don't believe is available (at least for Canada). I guess I understand now why so many people favour Nexus devices, this is all quite confusing :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I don't think it's available for US either. Correct me if I'm wrong.

As for Nexus devices, owned a Nexus S in the past, thing was easy to work with. The S3 isn't that terrible either though, I've seen more difficult.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cryceratops:
Hm. I'm not sure if this is the same as what I'm looking for.. but isn't this a 4.3 image for Canadians?

http://i.imgur.com/ueYQdlX.jpg
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Where can I find the change logs for the nightlies and do you have to flash Gapps everytime you flash CM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
http://10.2.cmxlog.com/?device=d2att

And no, only during changes to a different version of Android.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skim7x:
I'm currently on CM 10.1.3-RC2 and I go to the built-in CM updater under "About Phone"/"CyanogenMod updates," but when I try to download "cm-10.2.0-RC1", the phone just goes straight back to "About Phone" menu. If I click on a different update, such as "cm-10.2.0", it starts to download the ROM normally. Anyone have any idea what is wrong here? Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Corrupt download probably. Erase the file from the directory (not sure but I think the file is located under /sdcard/CMupdater, it's been a while I've used it).

Either way, probably a good idea to use the stable instead of the RC1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Also anyone know of any battery flashable zips for battery mods.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Xposed module + flashable packs

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

UOT Kitchen

http://uot.dakra.lt/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skim7x:
The problem is that it doesn't even download... it just goes straight back to the "About Phone" menu. If I go to the CMUpdater folder, it only has the associated changelog file, but no actual file for the ROM. Any other ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
There's no other file in there?

Otherwise, not really. I don't use CM Updater myself, I prefer CyanDelta. I don't usually touch the RCs and stables and CyanDelta downloads a small delta file, a file containing the changes between nightlies, instead of the whole rom for quicker and more efficient updating.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Anyone having Blue tooth connection issues. I just flash the 12.4.13. I tried to pair my phone to my BT speaker and it'd no pairing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I'm on 10.2. Working really well. Prior to 10.2rc I got horrible battery life and terrible Bluetooth stuttering.

Since then, all is fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Also this thread by the same guy, which is updated more I believe

http://xdaforums.com/showthread.php?t=2516074
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Where's that link and I'm on i747UCUEMJB att. And I tried to pair to another blue tooth device and I can't.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
Exactly!!! Weird one too... when mine did that, it just happened to be in one particular Panera Bread which I could reproduce the problem during another visit but ever since then, I did not go back there so that did not prove if the problem still existed.

It was just a single-fast notification tone which I did not have app using it. I did not have WiFi on at the time and always on data (LTE).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
It's just the 10.2 build in the settings, about, updates.

Would send you a link here but their dumb site points to installer only.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
http://download.cyanogenmod.com instead of get.cm
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
I clicked the link and is it for the at&t i747UCUEMJB? it shows nexus 7..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tokuzumi:
Make sure to click the d2att on the left hand side, so you only see ROMs for the at&t gs3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Ha, ok duh well Im on that build and the only thing im having issues with right is B/T not connecting to bluetooth speaker.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] texuntaz:
lock screen not staying locked

I have an issue where I setup the security to enforce a lock screen (I've tried pin and pattern.) This works for some time, but eventually it will stop locking altogether until I reboot the phone.

I saw one reference to this issue several months back, but have not seen any resolution.

Anyone have any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You have not disabled it in a CM profile, have you? :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] texuntaz:
Nope. Under system settings, I have profiles disabled.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
And you're not able to replicate the thing 100%? It just happens randomly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] texuntaz:
That's correct. I thought it might be the pop-up settings in handcent. Went several hours with no messages, still stopped locking. Changed to gosms as well, just to check. No love. Went about 2 hours before it started; rebooted; went about 5 hours. I cannot make it happen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I'm pretty sure it's Handcent. I recall using it and when I got a popup and replied it would disable the lockscreen. This can also with Whatsapp and Viber if I'm not mistaken.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] texuntaz:
I'll see if I can force it to happen, or maybe just kill handcent processes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
And although not a solution to your problem, maybe try an alternative SMS app (stock?).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
I se go smd, and work perfect.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
10.2.0 is looking good. First obvious things coming from 10.1.3:

new boot screen animation I really like it.

Network now says LTE vs 4G yes the same and a silly thing but I like it better.

Battery life seems about the same (great for the S3)

Had to reset my phone dialer icon. Meh no biggie

EasyTether USB tethering working fine. (would have been a deal breaker)

I have not tested wifi hotspot or bluetooth audio but will report back if no one says anything first.

Well done CyanogenMod team looks like another high quality product.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
This is misinformation as well. There is zero evidence an eFuse is involved. I agree with the rest of your post, but aside from the information that is going around, even from some very respected developers, the eFuse is only a rumor. And personally, if one was involved on the S3, it most likely would have shipped with it active and ready to brick your device at its release. Simply, don't flash aftermarket unless you know what you're doing. Don't change asserts unless you REALLY know what you're doing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cryceratops:
Is anyone experiencing a very low microphone on the latest nightlies? When I talk to people through Skype or using the sound recorder my voice comes out very low, I was using a TW based ROM before this and the sound was very high. Is there any way to fix this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
Just flashed the new CM11 nightly and the kk gapps, and am getting boot loops... Anyone else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jblparisi:
1 reboot on first boot which might have been normal then it booted fine since.

If it matters I did the first boot without gapps installed just to verify it would boot then I went ahead and flashed gapps.

Btw, KITKAT is running great on the Galaxy S3, I am very impressed even the camera is working as it should.

Hope that helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
What kind of kernel your using. I'm not on that build but usually when that happens to me it could the kernel. Maybe flash a different one