yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] srnoth:
Anyone else find the USB OTG & HDMI are not working with current nightly? They both worked last time I check about 2 months ago.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jason_Nguyen:
Is it the real deal?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Check my original post. I've got a screen capture of the text I received from Rogers (my carrier). I'm not on stock right now and don't have the time to fully revert back to check it out but I'm going to say this is real deal. 4.2.1 or 4.2.2 is another question however.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VashTS:
yes sir it is not working, im on latest nightly. tested out last night. mic works with everything else, except google hangouts. i think its the app, because prior to the update it was working great. i use it to chat with my son while at work

oh and my wife is on stock 4.1 and she can transmit audio to me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] luncht1me:
For us on ROGERS in Canada, we've (at least, I have) always used AT&T forks. Are you sure we're supposed to use the Canadian LK4 one instead this time around??

I just don't feel like having to bust out the Riffbox for the first time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yes, for the bootloader use the canadian one.

I, like you, use AT&T roms, recovery and everything else though. =)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevey500:
Anyone unable to flash the latest CM10.1 nightlies using TWRP 2.5.0.0 ? I am getting "assert.failed: ro.bootloader ..**modelnumber something and halts.

It does this right at the beginning of flashing. I have tried wiping cache, dalvik, and system before flashing. Fails with build.prop errors, restored system&boot and rebooted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yes, read the multitude of posts before yours regarding the necessary bootloader upgrade.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
It just never fails to amaze how little searching is done before people post...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevey500:
Just here to be one of "those guys," you're welcome.

I was clicking pages back, reading through but apparently didn't go far enough.

Thanks anyhow. Odin flashing imminent.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tylerlaczko:
Flashing with Odin

To be fair this thread is 1300+ pages... maybe nicer to link it multiple times. Took a long time for me to find. so here it is

"

I made some ODIN-flashable files that contain the bootloader, RPM, TZ, and baseband of the stated versions, so that people won't have to go completely back to stock TW. It's intended for those not on the necessary bootloaders yet so that they can flash future CM builds. Put them into the PDA section in Odin and flash away.

I747UCDLK3 (AT&T): http://d-h.st/L64

http://www.mediafire.com/?pu279m19ob7ufru

I747MVLDLK4 (Canadian): http://d-h.st/yqV

http://www.mediafire.com/?74b1e321p537f5d

Note: They're untested, but should work as intended. Tested by fellow users, works fine. Please flash at your own risk!

EDIT: Threw up Mediafire mirrors, since d-h.st seems to be down randomly.

"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gab1to:
Can someone provide a Heimdall version of this bootloader? This one is not compatible with heimdall and it throws an error: The file selected was not a valid PIT file.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Thanks for taking the time. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Thr33Seed:
Planning on probably going back to CM10.1, did they fix the MMS issue yet?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I send and receive MMS weekly without any issue since March, so I'm not sure what you are referring to.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tony_YYZ:
I got this today as well. Pretty sure it's a hoax.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
So does anyone have any input in regards to my postings? For being a development thread with a big push of staying on topic and posting logcats, screen captures and useful information to backup your question, bug etc there doesn't seem to be a lot of interest in helping others out. We seem to be more interested in whether or not the MMS issue from months ago has been fixed and if RC2 or the latest nightly is better.

So aside from a few thanks and a couple people saying I should report it on JIRA, no one else has any comment? Does anyone else see the same issue? Am I wasting my time? Is it just my phone?

So much for try to post something that ACTUALLY belongs here looking for guidance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Can't say I've ever had/noticed this issue myself otherwise I would have helped you, and yeah you should probably submit to JIRA. At home I get full strength signal, at work I barely get any 3G signal because this place is a huge concrete slab.

Dev thread is probably too big of a title for this place though. I would take it as "help other noobs as good as you can". I don't think it's anywhere close to being monitored by knowledgeable people. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sage2050:
I searched w/ google about this very thoroughly and only found the answer when I came here and asked about it. searching for "assert failed getprop ( " ro.bootloader " ) gets you absolutely nowhere.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mscott998:
I'm having MMS issues also on 2.3 going to upgrade to 2.4 and see what happens
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
2.3 & 2.4? What are you referring to?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I've reported it on JIRA.

https://jira.cyanogenmod.org/browse/CYAN-1209
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bxsteve31:
Status 7

anyone else getting a status 7 error with the new nightly? i have been flashing CM since october and never received this before. my current rom is from March so its been over 2 months. i hope i didnt miss any steps that had to be taken.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Check the few last pages regarding the bootloader upgrade necessary. It's the most talked subject in this thread as of late.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bxsteve31:
thanks man. i havent been on here in a long time. ill search bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Good luck!

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

No problem. I'd link you to the necessary files for ODIN flashable bootloader, but I don't have them on hand. You can find them by going backwards I'm sure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bxsteve31:
thanks. i think i found the page. would you happen to know off hand what is the last CM version that is usable with the old bootloader?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I sense some sarcastic undertones here. I don't have a chance in hell with them do I? haha.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yes, 5/13 is the latest version without any bootloader check.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bxsteve31:
much appreciated. Thank you again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I think your issue is as well documented as a normal user could document it, but dealing with CM JIRA is a PITA... Just the fact you need a logcat for every submission, even those that cannot be diagnosed with one, kinda makes it... biased.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bxsteve31:
crap so im at http://www.get.cm/?device=d2att and it jumps from 5/11 RC to 5/17 nightly. is 5/13 no longer available. if so ill just go with the 5/11RC
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I don't imagine there were any substantial changes in these 2 days, someone correct me if I'm wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bxsteve31:
you're probably right. plus im 2 months behind as it is so 5/11 will be good enough for now. I should have PM'd you instead of posting these questions in here. sorry peeps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
The information could be relevant to someone's else interest though, so it's all good. Plus I usually ask people to post in the respective threads instead of PM'ing me. That way if I don't have the answer or no time to help, someone else can chime in. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
I installed via command line heimdall. Just extract the files, run a print-pit, and match up the files. A quick search here to help with the commands: http://xdaforums.com/showthread.php?t=1508703
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
See my earlier post with the link to my Dropbox archive of d2att nightlies. 5/13 is in there for sure. However, see my other post for updating the bootloader if you want. It really isn't that big of a process. Took me 20 minutes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Landmine:
After flashing RC2 from RC1 I no longer have service, I do have WiFi, and all of my APNs are hidden/gone and I cannot add new ones.

Any ideas on how to resolve this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Settings->Wireless & Networks->Mobile Networks->Access Point Names is totally empty?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Landmine:
Yes, but it turns out my SIM card died on me going from my LG OGP to my GS3. Replzed the SIM and its back online.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
That'll do it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ryanallan:
I haven't seen the camera talked about in a while.

On RC2, the exposure still doesn't work.

I.e. changing from +2 to -2 doesn't do anything.

Is this still expected behavior?

Also missing photosphere, but that's another story.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
Yes, the exposure doesn't work. I'm waiting on that to be fixed as well.

Photosphere is proprietary to Google and will only work on nexus devices. However, there's a zip somewhere in the forum you can flash via cwm.

Edit: zip can be found here:

http://xdaforums.com/showthread.php?t=1966426
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Getting random reboots when watching YouTube videos. It only happens once a day or so. Try watching a video that's 10+ mins and see if you guys get the reboots.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Where is your logcat? Information on what CM release you are running...Now a days we have people sticking on M2 for bluetooth stability, RC2 for bug reporting and stability, 3/17 cause they are scared of Linux 3.4, 5/13 cause they don't want to update the bootloader and some running the latest nightly. What kernel you are running? Are you overclocked, undervolted? Was this a one time occurance for you or does it happen every time? Are you keeping an eye on the phone temperature sensors while watching?

Come on. How do you think anyone is going to help you if you put up uninformative posts such as that one. Be proactive and try to figure out for yourself what is going on. I'm sure as heck not going to watch a 10 minute video to see if my phone reboots. You didn't put any effort into it, why should I? Sorry for sounding like a prick but you've been around long enough. You should know that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Truth bomb!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gab1to:
Thanks dude.

For those wondering how to do this on Linux or Mac you have to do the following:

Put the phone in download mode

In a terminal copy this: sudo heimdall print-pit --no-reboot and match each partition identifier with every file that you will flash

It will look something like this: sudo heimdall flash --3 sbl2.mbn --4 sbl3.mbn --5 aboot.mbn --6 rpm.mbn --8 tz.mbn --1 NON-HLOS.bin --no-reboot

Those numbers are the Identifier of each partition that you need to replace with your own.

Now I can continue flashing new roms.:cyclops:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] minnick:
If I knew how to help you I would sir. All I can do is thank you for reporting the issue correctly/extensively and hope the issue is resolved by the dedicated coders.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spotdog14:
First, please let me give my thanks to the maintainers of this ROM, I love it! I am new to the GS3 after breaking my HTC One X+ I am using by bosses old GS3 with a cracked screen. Anyway after rooting, unlocking and flashing I really like this phone.

Two quick questions that I am sure have been covered in the 1,500+ pages but I'm sorry I don't have the time to go through page by page so I apologize.

First, is there an LTE icon when connected to LTE?

Second, I get worse reception at my house compared to my HTC One X+, are there any other radios I can try for AT&T?

Again, thank you and I'm sorry for asking questions that have been asked before.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
1st: It will show 4G

2nd: http://xdaforums.com/showthread.php?t=1831898

You could have found the second easily perusing in the AT&T Galaxy S III Android Dev section.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spotdog14:
Thank you!

Now a side question, is the radio CM10 using listed in that thread? I am thinking about going back to the stock radio, has anyone else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
CM10.1 has no radio included, like most (if not all) custom roms.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
In other words, CM 10.1 does not replace the existing radio firmware on your phone. You can flash any radio firmware on your phone and CM 10.1 will not touch it when you flash CM 10.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spotdog14:
Look at that, I learn something new every day.

So what you are saying is that I still have the stock radio installed because I have not flashed a custom radio.

I wonder why I get such poor reception then. I shall have to investigate.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yes.

Modems/radios barely affect the strength quality though on S3, unlike certain other phones where there was a lot of change going from one to another.

I guess if the screen is cracked, the phone might have been dropped, thus it's not unlikely it would be a hardware issue. My 2 cents.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
All released radios are stock. There is no such thing as a "custom" radio released by any devs here. Whatever one you may pick from the thread linked above is "stock".

The radio you should have on it now will coincide with whatever the last stock firmware was that you installed on it. You can flash any of the radios (also referred to as baseband or modems) onto your phone without any problems. Some modems MIGHT work better than others but I've never had much of a change in signal strength or anything by switching from one to another. Radios also can affect wifi strength. Some people claim better battery life with one modem over another and if on Rogers in Canada, some modems can negatively affect the Call Display (CNAP) name feature we have but other than that, flash away and see what works best for you.

Just make sure you flash the right modem for your phone. There are AT&T modems and "Canadian" modems that are used on the "M" variants of the I747.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
Something to keep in mind, the radios are not custom (that I know of). I believe they are pulled from official updates and packaged here for convenience. I would seek out the list of radios for your phone and flash until you find the one that works best for you. [Settings > About Phone > Baseband] will tell you what your current radio version is.

Disclaimer: you've come this far, so I expect you are aware of the potential bricking flashing radios can do.

... I see flex beat me to it. :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Call Display Name on Rogers/Fido

Okay for those of us Canadian users who are on Rogers and Fido and get the great feature of Name Call Display (CNAP) but have found that there are some basebands that work and others that show garbled names there has been a Bug Report opened on JIRA and I'm trying to help the guys figure it out. https://jira.cyanogenmod.org/browse/CYAN-1202

It looks like back in the CM9.1 days there was a commit made to get this work. Ever since JB came out though, none of the new JB based modems work to show the name (LK3, LK4 and LL1). Hopefully this matter gets resolved. I know it's been talked about in various places across various devices with the usual response on a fix being flash a different modem. Hopefully in the future we will be able to use the latest JB basebands without crippling the CNAP feature. I'm hoping the fix from CM9.1 just needs to be merged into CM10.1 but it's likely not that easy as the ICS modems work fine with CM10.1.

We will see.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spotdog14:
I found this very useful in the FAQ section:

4G LTE/Wireless Data

-Make sure you are aware of the difference between the service providers' terminology and the "real"/CM terminology (AT&T 4G is actually HSPA+, AT&T 4G LTE is actually 4G).

I can't tell you how much happier I am with CM10 then Sense on my HOX+
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Yes CM10.1 doesn't use the term LTE. They report 4G for an LTE connection and H+ for HSPA and 3G for 3G. This is a more accurate representation of connection types as HSPA+ is basically 3.5G even though AT&T calls it 4G. Which is why all the major carriers had to use the term 4G LTE when true full 4G came out to distinguish between the two.

Anyway, I don't want to confuse you. Sounds like you are getting it all figured out today.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Did anyone still think carriers were honest businesses? :silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Hell no.

In their defense though marketing a network called 3.5G isn't as sexy as bumping it up one whole number to 4G. Except they were screwed once a full 4G network came along.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] huladaddy:
For the last couple of nightlies, I've had some strange things going on. SMS messages take a very long time (10-60 mins) to send and receive. Downloading apps from the Play Store takes a lot longer than before. Anyone else experiencing this? Could something else be going on?

Edit: Oh, and there is a very long pause between tapping the torch button and it actually turning on or off!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
I can't speak to SMS - I use Google voice or instant messaging exclusively - but downloads only seem to slow for me when I near that throttling threshold AT&T implements, and testing torch is instant for me. It used to have a lot of lag, but I did a full wipe when I updated my bootloader. I didn't try to track down the torch issue that had cropped up, so I can only advise a full wipe and see if the same issues persist. Or track down and clear app data/ cache.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ormandj:
Anybody else getting multicolored static when at the lock screen? Also, BT has been really slow to reconnect, if ever, sometimes. Have to turn it off then on and it works right away. Already stopped BT sharing and cleared data and cache. I am on the latest nightly, has been happening ever since I flashed the stock firmware then flashed cm back on. Did full wipe when I did that. Otherwise things seem OK.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bcos:
Yep, same here.

FWIW, I'm on 5/21.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Not sure what they did but opening up settings in camera now doesn't trigger a force close! Nice work devs!!! :thumbup::thumbup::thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Radio Logcat Request

Can anyone run a quick radio logcat and see if you are seeing anything like this? It's a reoccuring set of errors. I see it every 20 or so lines popping up. Just interested in seeing if it's just me or if it's possibly wide spread.

05-21 12:46:11.983 E/RIL-RAWDATA( 371): service_ID = 3, message_ID = 4f

05-21 12:46:11.983 E/RIL-RAWDATA( 371): 01 0C 00 00 03 01 00 B1 03 4F 00 ..

05-21 12:46:11.983 E/RIL-QMI ( 371): [SMDPORT] >> BEFORE, Write SMD Port [fd = 10] [msg_len = 13]

05-21 12:46:11.983 E/RIL-QMI ( 371): [SMDPORT] << AFTER, Write SMD Port [rc = 0]

05-21 12:46:11.983 E/RIL-RAWDATA( 371): service_ID = 3, message_ID = 4f

05-21 12:46:11.983 E/RIL-RAWDATA( 371): 01 21 00 80 03 01 02 B1 03 4F 00 ..

Any help in understanding this error would also be greatly appreciated.

Thanks in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
I don't suppose this is the fix for the loss of BT streaming playback volume I reported a while back, is it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheToiletSpaula:
Quick Question.

How does one go about flashing a .img recovery? The easiest method?

I am used to just flashing things as a zip or using odin.

Any help would be Greatly appreciated!

Thanks,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Sounds like a great question for the Q&A thread!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
What's the difference between a "radio logcat" and a regular logcat? How do I "run a quick radio logcat"?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
http://www.teamw.in/project/twrp2/104
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I use CatLog which can be found in the market for free. Go into settings and change the buffer to Radio.

This will report anything network related call related etc that is going on behind the scenes on your phone instead of a main logcat that will report on other areas such as dalvik, sensors etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
I am seeing the same 6, and another two.

05-24 12:22:40.910 E/RIL-RAWDATA(366): service_ID = 3, message_ID = 51
05-24 12:22:40.910 E/RIL-RAWDATA(366): 01 15 00 80 03 01 04 00 00 51 00 ..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
Hey guys, as of 2 days ago I cannot send MMS. Everything else works fine. Using stock messaging app. Reset APNs and all of that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] poetikal:
I decided to send myself an MMS, and it came through with no problems. Your best bet is to flash back to stock (with the most recent bootloader, of course) and reflash whatever version of CM you are on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] marinierb:
I keep having to go back to RC2 because of Bluetooth. RC2 connects to my car consistently. The later nightlies don't. I tried the trick where you turn BT off then force stop it and clear data, reboot and turn BT back on, all to no avail.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
I'm running 5/13 and I'm not having any issues but I've had them before for a long time. I'm wondering what bootloader you have? I updated mine to work with the new kernel and I'm wondering if that was causing the bluetooth issues as well.

Sent from my Galaxy S3 [AT&T][CM10.1]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Anyone using car dock with nightlied? Is there a trick to get sound out not through phone speakers but through dock?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheSchatz:
Settings>Advanced>Sound>usb audio out

Should fix you up