yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trh1341:
Oh good god! I literally get an average of about 700 kbps!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
Dosen't boot for me. Gets past the CM kernel splash and then black screen. I looked away for a second and looked back and saw black. Thought I bricked lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
dirty or clean flash? I'm waiting on the next build to compile before I install it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
Clean from Carbon 1.8. I knew it may be a bit risky, but I flashed the new bootloader this morning and removed the build stuff from the updater script so I can flash. It may or may not be the issue. I am able to get into recovery though so no harm done.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Yeah watch out for the bootloader, they updated the fingerprint for our devices the other day but they haven't added the new AT&T bootloader or modem into check. Do you have a link for the bootloader?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
Wouldnt boot for me either, got the same thing. Splash and then black screen
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
Should be in this update.zip.

http://xdaforums.com/showthread.php?t=2387423
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Modem doesn't matter, but there's a new bootloader for AT&T? Jiangyi has been adding commits for them so far. Just need to bring his attention here. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Well the second build with the cherry picks I made still doesn't boot past the kernel splash. I'm going to try out 1 more build and I'll see how far I can get from there, maybe I messed up at one point.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
Correct. I posted the link above your post ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
What's the new bootloader version? Can't say I want to wait for a painfully slow download just to see a version haha. That's all Jiangyi will need to add the commit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
I747UCDMG2.

It was OTA released i guess a day ago.

This link http://xdaforums.com/showthread.php?t=2387423 is pretty straight forward. Odin back to UCKD3, flash update ZIP and good to go.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Don't need it myself though, but people who update will not be able to update their CM rom until someone adds the new bootloader to the update-script.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
True. I just remove it from the updater script ;):highfive:

Also, cmxlog is quiet. No new commits today. I smell something big coming for the weekend.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
That would be sweet, but there was no commits on 07/29 either, and that brought nothing. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chasesavestheday:
Also having the same issue. I noticed when installing the MMS fix it does in fact fix my issue. Although it seems that SMS.apk does not have the emoji quick button, or am i missing it somewhere?

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Very possible the emoji quick button was added after the release of the milestone and since it's just the mms.apk without any sort of mod or recompile there's not much I can do.

I could always go further and edit mms.apk from the latest nightly instead but I'll need some time and someone to test.

Maybe tonight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trh1341:
Whenever I try to remove it, I get status 6:(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jiangyi:
I'll need you guys to make sure that everything actually runs fine on the new bootloader before I submit a commit to add it. Better safe than sorry.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Thanks for keeping an eye. Appreciated by many I'm sure, even if most don't realize you're involved. The dark knight etc etc :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Hey guys

After trying to update my phone yesterday and getting the "Installation aborted" message, all my pictures from my DCIM folder on my external SD card seem to have been deleted...what gives?!

Thanks,

Elliott
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
I updated it manually using Heimdall. I got one random reboot while updating some apps but that happens to me once in a while.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trh1341:
Happened to me and my friend too. Dont worry, however I'm using the T-Mobile build
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krapt0:
What is the best kernel? I have not used anything other then stock kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
Comes down to user preference and how your device reacts to certain settings. Also this question should be in Q&A forum (or search as this has been asked a lot)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheSchatz:
How would one go about doing this? I assume this would avoid going back to stock?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krapt0:
Sorry, Thought I could ask here since I am on cm nightly.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
I found a copy of the update and extracted the files inside that ended in .mbn(NON-HLOS, sbl2, sbl3, aboot, tz, rpm). I installed them all at once using the Heimdall GUI frontend.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
It's Alive!!!!!

Hey guys! I've been working on this for the last few hours, and I finally got it working with the help of some friends. Here we go, CM 10.2! https://docs.google.com/file/d/0B2aPnkdBCg08ZVk1OWhZYnd4b00/edit?usp=sharing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trh1341:
What's different from the first one you posted?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Well for starters it actually boots! Camera works as well! I'm running it as we speak, no issues at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trh1341:
Oh good! Glad someone got it working! (Wish I could have better internet! :P) I've been using the T-Mobile 10.2 ROM! Seems to be great! I will flash yours in the morning after I get my new kitten:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
I know I shouldn't so this... But do you think a dirty flash over the latest nightly will work?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Does anyone have a change log for the nightly last night? A build was run but I can seem to figure out why.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgarrand:
4.3 over 4.2.2 Nightly

It worked for me. I also flashed a 4.3 version of gapps just in case but it's all working wonderfully.

Scott
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alkiter:
Nice ! Dirty flashed over 10.1 and works! Had to reinstall Gmail, Google Play Music, Chrome and clear browser cache.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgarrand:
I flashed a 4.3 version of gapps from http://xdaforums.com/showthread.php?p=43972031 and all of the Google apps just worked.

Scott

---------- Post added at 08:03 AM ---------- Previous post was at 07:29 AM ----------

Thanks for the build! Love it. Only one little issue. The Focal app is screwy. It freezes the phone and causes a reboot. If you try to launch the stock camera app it will say "Cannot connect to camera". I'll just stay away from Focal for now. :)

Spoke too soon, took a picture with the stock app and it displayed artifacts on the bottom and rebooted the phone. This may be due to my "dirty flashing" so I'll make that known.

Scott
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
http://changelog.bbqdroid.org/#/d2att/1375421381
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeathKoil:
Full wipe, clean flash, and I have issues to report.

The camera app will work once, then if you try to open it again the system will hang and reboot. This happens in Focal and in the stock app.

Attempting to make a phone call will either make the screen go black when you hit the call button, or the phone will hang while you dial in the number. In both cases, the phone will reboot. Mobile data does work though.

Receiving a phone call causes the phone to hang when you pick up, then reboot.

This is a very good start for an unofficial build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] marinierb:
Is this the unofficial 10.2 thread now?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Changelog somehow didn't follow through haha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgarrand:
I guess it should be branched off into its' own thread. I am excited to have a 4.3 unofficial but it is kind of hidden here.

Scott
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Thanks. My usual source at cmxlog didn't show anything for last night.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Because it's an unofficial CM10.2 build by a member, I imagine. PwnCakes should probably make a topic as you guys noted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
No problem; I normally check CMXlog too, but happened to check the BBQLog app this morning right before you posted this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pkimkpop:
bug report

Just flashed 10.2 and so far so good! 2 bugs to note

1) in phone dialing shortcuts for contacts does not work

2) in settings 'about phone' android 4.3 attempting to play with little jelly beans causes hard reboot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brolybrah:
For those that updated to 4.1.2 OTA AT&T, I went ahead and edited the update script in PwnCakes193 10.2 package. This should let you bypass the error 7 you might get when flashing his rom.

Enjoy!

https://docs.google.com/file/d/0B3ud7L79aPOLcmgxRTNWWXpRSHM/edit?usp=sharing

as usual, im not responsible for anything that happens to your phone. I personally find the camera app(s) to be too buggy for my liking so I'll probably be going back to the official nightlies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] roemicha:
Wanted to report the following bugs with the Unofficial CM 10.2 build:

1. FC of gapps using initial posted 7.26.2013 gapps - (fixed with http://xdaforums.com/show...php?p=43972031)

2. Lost root when flashing from Jellybam 9.2 to Unofficial CM 10.2 - (use Chainfire's CF-Auto-Root: easy fix)

3. Both cameras (Stock 4.3 and Focal) are buggy - (downloaded latest CM 10.1 nightly and pulled Galery2.apk and inserted to system/app)

Will update with other bugs as found. Will also copy over to new thread once made.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jiangyi:
I747UCDMG2 is now merged and ready to go: http://review.cyanogenmod.org/#/c/46841

http://review.cyanogenmod.org/#/c/46842

Recovery-flashable firmware package, courtesy of invisiblek: http://invisiblek.org/sgh-i747/d2att_UCDMG2_firmware.zip

Everyone is encouraged to update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mhdsanto85:
im sorry for the noob question, but what is this firmware for??

thanks in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Keep in mind if you flash this you won't be able to go back and flash any of the stables or any nightly released today or before unless you edit the script or revert your bootloader back to last official one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
So you can update your bootloader through recovery? No ODIN no Stock needed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] poetikal:
I know the talk is about CM 10.2 and the new 4.1.2. update, but I'm wondering if the awesome people of CM managed to fix the the front-facing camera rebooting issue when using a third party app? I'm currently running Dandroid 3.8 and loving it, but I really want to go back to CyanogenMod badly; it's the camera issue that's holding me back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trh1341:
Just saying guys.. People keep saying they lost root. But I said earlier, to enable root, you must tap the build number a lot to enable developer options, then enable root access from developer options
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enzyne:
Having some call audio issues all of a sudden with the 7/29 build. Reboot seems to have fixed the problem but wait it came back 8U.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ava0425:
This is the fastest and smoothest phone I have ever used since flashing cm10 tonight. Amazing. Love you cyanogen!

Sent from my CM10 SGS3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] perigee:
I had some strange battery performance yesterday. it only lasted about 6 hours with about an hour of screen time. the phone itself kept feeling pretty warm too. I tried turning down the CPU governor to power save and also reduced the max CPU speed. unfortunately the phone died well before I cold get to a charger because I was out all day.

my only thoughts are that I had used the camera and also some GPS apps. maybe they stayed running or something in the background? the battery stats didn't offer any clues. nothing stood out as a battery hog besides the screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] answer1o1:
That's exactly what I do. I'll try to record it later today and post it up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Travisimo:
My apologies for jumping in this thread as a VZW customer, but I just have a few quick questions to more appropriately understand how development of cm10 is commencing on the various GS3 devices:

1) Which model of the GS3 is cm10 being built on? International/AT&T/T-Mo?

2) Is it just @dhacker29 that is developing the VZW version by taking the cyanogen releases and tweaking them for VZW?

3) Is the Cyanogen team directly developing for the VZW version at all?

I know we VZW users are fortunately to even have cm10 available to us with the locked bootloader (thanks to all the hard work on getting kexec to work seemlessly). I just happened to see the news about a 7/29 update and started wondering how the overall development process is commencing on the various devices, and which developer(s) are working on the various builds.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hightechlive:
question 1,can i install this rom with TWRP?

question 2,do i ahve to have a sd card to install?

questions 3,will i lose my imei number and if i do what happens?

thanks off to work did a quick search but did not fine my answers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enzyne:
1.Yes

2.External, no, you have 16GB of internal storage.

3.It didnt happen to me, i believe that is with certain roms. And apparently is fixable now??

---------- Post added at 10:22 AM ---------- Previous post was at 09:30 AM ----------

Is there anyway to remove that popup that says your sending sms to fast from the stock messaging app?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Igotsanevo4g:
You may get crucified around here by not posting in your devices thread or asking questions, watch out. Some people get their jollys that way *shrug*

Of course you know d2vzw is almost identical as all the other variants are to each other so all devices usually benefit from most patches pushed to gerrit. But bottom line is your boot loader is locked, sucks to suck bro. Cyanogen has a tmo gs3, that's what he's using personally.

Really though people will probably know more in your devices thread.

Awesome, its purely placebo but it never seems quite as slick without that CRT ani :silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PuffinNugz:
No you didn't. If you searched, you'd know not to post this in this thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
LOL this is the same question u asked on Aokp thread
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RampageRR:
Lmao I was just getting ready to post this. You win.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iskuruts:
is hotspot working on open security only still? no wpa/wpa2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scott8281:
First let me say thanks so much Cyanogen, Great build, smooth as hell....

I posted early on reporting that MTP was not working with android file transfer on OSX Lion or Mountain Lion it is however working on Snow Leopard. Up to this build 7/29 PTP was working on Lion & Mountain Lion and even opening up iPhoto as if it was connecting to a Camera but its no longer working in PTP now.

In an attempt to help narrow it down i tested it with my Galaxy Nexus on stock/cm9/cm10 & MTP works fine. My S3 running TW 4.0.4 will mount the internal SD but only when selecting PTP (Selecting MTP does nothing & oddly, selecting PTP opens android file transfer)

It seems to be an S3 issue as MTP doesnt work on Stock 4.0.4/ CM9 or CM10. Where as PTP opens Android File Transfer on Stock TW 4.0.4 & opens iPhoto in CM9 and Does nothing in CM10.

hope this helps & Thanks Again Man!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
You should pull logcats after every test, posting about it with logcats gives a chance of possible fixes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nate_sheedy:
I noticed that my USB pid and vid changed from using TW and CM. And in recovery the USB pid is the same as a galaxy nexus pid. And works with nexus adb drivers. Full commandline operation. But no mtp or ptp with CM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nate_sheedy:
I'm wondering if the adb drivers work, why not just add a few lines of code to include the nexus usb pid into the i747 mtp driver inf file. Would file transfer be plausible in recovery at that point?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scott8281:
I'll pull one now, thanks for the heads up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] answer1o1:
Finally got my stock camera to focus! Long story short you need to take 1 picture with flash on. It always readjusts itself when flash is on, once you get that out of the way you can turn the flash of (if needed off) and it'll focus as much as you want as long as you don't close the app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scott8281:
I can confirm that ADB works in Build 7/29 CM10, I just pulled a Log Cat and posted it above hoping to help with the MTP issue on OSX Lion/Mountain Lion
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] americasteam:
Great find. Thanks!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jiangyi:
For this one, yes. Just be careful that you're flashing this on an I747 and not the Canadian/Mexican/Puerto Rican I747M.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
I guess this wont work for me then. Since I have a 747M.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skim7x:
n00b question... so I have no problems with flashing the firmware package via CWMR... what are the first two links for? Is there supposed to be a downloadable link in either of those links? And I'm assuming we have to update to the latest nightly immediately after updating the firmware? Or will my current nightly from 3/17/13 still work with the new firmware?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Hey guys I moved everything over to here

The latest build has working front camera!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
The first two links were showing the commits being made to add the new bootloader to the CM code. Nothing more and nothing to download from them. As for what you can and can't use. You can use your current nightly if that's what you are on but you cannot flash any nightly again that is older than last nights release. This also includes all stable builds. Reason is those were compiled and released before this bootloader version was added to the assert and those previous builds will fail to install because this version isn't built into the previous code.

Going forward you can flash all future nightlys but that will be it unless you revert back to LK3 or edit the script to remove the assert or add your latest bootloader to it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skim7x:
OK that's awesome. So I can actually load the new firmware and stay on 3/17/13 if I so choose... but when I update, I can only update to those builds more recent than last night's build. And I won't be able to go back to the 3/17/13 build. Got it, thanks!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Yes it won't affect the build you are currently on. Just what you try to flash in the future. There are ways to circumvent this but it is a little bit of work.

There are absolutely nothing wrong with the latest nightlys however so I highly recommend updating to the latest nightly anyway.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skim7x:
Hmm... so I flashed the firmware update via CWMR and it installed successfully... but then I went to "System Settings/About Phone/CyanogenMod Updates" and downloaded the 20130802 nightly, but had the same error I had before firmware update. Any idea why it didn't work?

Under "About Phone" it does say that my Baseband version is "I747UCDMG2" which, I believe, confirms that the firmware was installed...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Because the commit won't be added until the next nightly. That should be ttonight's build. The build from last night didn't have the commit yet. Try installing the build from over night tonight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skim7x:
I see... so I'll flash the 08/02/13 nightly tomorrow after the commit is added... I'm assuming all future nightlies will have the commit added as well?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pseudoware:
It will actually be the 8/3 nightly. s/b available in about 3 hours.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
new nightly up. (:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Krad:
I hear everyone saying the nightlys are perfect. Is the 5ghz channel bug fixed over channel 46?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skim7x:
Installed the firmware last night and then the 08.03 nightly just now. Worked perfectly and loving the new nightly! Thanks for everyone's help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dalephill2:
nightlies, whats been added

Hi fellows, I am liking the cyanogen alot, so quick.. i have a question for those that can answer, when a new nightly has been posted how does one go about finding out what was added or fixed etc... thanks...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mhdsanto85:
http://10.1.cmxlog.com/?device=d2att
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
Also, if you use cyandelta from the play store to update (look it up), the change log is there before you download the update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 2new2care:
Anyone remember on 10.1 how long it was after the international version was built that we got ours? Post 15k BTW....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hormosapiens:
Im on nightly 8/3 but my baseband is still DLK3. is that normal?

I came from TW rom, clean install, wiped everything except external sd.

any idea?

thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
CyanogenMod doesn't change your modem/baseband. The modem is proprietary(and signed) so they only come from Qualcomm/Samsung. You can install a new one through recovery just like a ROM. MG2 is the latest for d2att.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mhdsanto85:
But mg2 is better than dlk3 ?? Is it recommended to update? Thanks in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
I've personally noticed an improvement but there are some people who go between modems and swear some older ones are better. Newer has always been better for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
Flashed that, now my phone wont boot at all! Screen stays black, phone doesnt vibrate or anything.

Any ideas ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Its only for the 747 not for 747M

lalala boom