yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
Running the latest nightlies, my usage chart has flattened out to reflect what my actual usage is, starting somewhere between 0602 and 0603. My chart does still show the inflated values prior to installing one of those builds, so your calculation may include data it thought you used before it was fixed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djjuice:
I get the data drops, but usually turning on/off airplane mode will bring it back. Thats my simple workaround till a better fix.

the only other issue i get is when if I turn off Bluetooth, it won't turn back on/off correctly it gets stuck on "turning off" and sometimes it shows that it's still connected when it isn't.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It's a hassle, but in the bluetooth settings disconnect from the device before turning bluetooth off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
i updated from 5/29 nightly where my data was being reported properly, so this is something with RC4 i think. plus, my phone is set to turn over on the 4th, so it's saying that since yesterday, i used 2gb on rc4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
I have been noticing the Bluetooth staying connected when it isn't as well. As soon as I notice it, it switches back to disconnected though (usually pulling it out of my pocket after leaving the car) making me think it's a laggy icon update. I haven't looked into it further though.

For the stuck turning off, killing Bluetooth share is normally the quickest way to stop that. I use a tasker profile to do that automatically every time I turn off Bluetooth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ryanallan:
I had this problem as well (nested /0 folders). My work around for file transfers was dropbox which was really slow.

During the whole bootloader freak out phase a couple weeks back, I used Odin to flash the stock ROM on my phone. This fixed the nested /0 problem. It wipes the memory clean though, so make sure everything is backed up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kwang0429:
I realized Bluetooth started to fail since last week's ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] marinierb:
I'm still on RC2 because BT stopped working with my car a while back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SomethingAwesome:
I haven't tested all situations, but when trying to connect to my laptop with a Bluetooth barcode scanner app I have to re-pair the devices every time to get the connection to initialize correctly.

My MW600 headset didn't connect automatically, I had to go into the phone Bluetooth menu and click on the device (initiating the connection) to get it working.

Definitely still working, but not exactly bug free.

This is on the 06/06/2013 nightly.

Sent from my magical SGS3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikalCarbine:
I'm having this same issue. Can anyone post the modem.bin from a 4.1 build? Could this fix this issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
I think what we'll need is a 4.2.2 modem - I'm using 4.1 modem now and I believe so is flexfulton
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
For me the best nightly is still 2013-03-17, still using 3.0 kernel, just before 3.4 kernel was introduced. I tried RC2 which drained my battery, and just tried 2013-06-05 nightly and had huge battery drains due to heavy CPU usage of process 'sec-ril'.

I'm going to stick with 2013-03-17 until battery drain & bluetooth issues are resolved, because to me they're show stoppers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Monkeymannnn:
That's your choice, but the 3.4 kernel is glorious. I'm very impressed with the 6/4 nightly. I don't use bluetooth, but battery life is pretty on par with the March nightlies. Definitely not better, but still not bad. Flashed only clearing cache and dalvik. 30 hours up time, not a single reboot, stutter, hiccup or anything. As buttery smooth as you could ask for at that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
Thanks for the feedback, but 6/4 was 2 days ago, and that isn't enough anecdotal evidence to support the stability or battery life claims you're making about 3.4 kernel. I was on RC2 for weeks and my battery would never last more than 20-22 hours maximum. On the other hand, the 3.0 kernel allows me to go for nearly 30 hours without a charge with the same amount of usage. And then 6/5 nightly was a disaster: sec-ril had the CPU pegged for hours and my battery was drained in less than 6 hours.

On top of that, the Bluetooth issues. You don't notice it because you don't use Bluetooth, but if you need Bluetooth then it's best to stick with an older nightly or 2013-03-17.

Btw, I always only do a system wipe, cache wipe, and dalvik-cache wipe before I flash nightly and gapps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Monkeymannnn:
I do need to get through a few more cycles before I can really judge battery life, but it's been holding up under heavy use so far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikalCarbine:
I can't find the 3-17 version under the CM downloads page, anyone know where this can be found?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
http://xdaforums.com/showthread.php?p=39511571#post39511571

Don't forget to thank him.

For what it's worth, 3/17 also has bluetooth issues, for those unaware.

Example: http://xdaforums.com/showthread.php?p=39979052#post39979052
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Me too. The Bluetooth is not an issue if you disconnect your device before turning off the phone... how hard is that... I mean you have to turn the headset off anyway... just do it first. And the guy must have had a bad flash because I got 3 hours screen time with 1 day and 20 hours up time. THAT, is better than I ever got on a 3.0 kernel. 3/17 is choppy in comparison too. It's nice, but It's an antique.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
For the past week, a few apps when accessing the front camera causes the whole device to crash and reboot. These apps are Cerberus and Photochron.

https://play.google.com/store/apps/details?id=com.lsdroid.cerberus

https://play.google.com/store/apps/details?id=com.photochron

I think it happens for apps that try to access the front camera directly. Other apps that access the front camera through the gallery app, like Whatsapp or Google+, don't have any issues. I think this began happening after 5/29, when there were a large number of camera related commits. Anyone else seeing this too?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 9umis:
In my humble opinion it is an issue. Many times u don't have time or even think of disconnecting device then phone. I use it a lot especially driving. And its pain in a .... But it's possible to live with it.

I have been using many ROMs: cm, smooth liquid, task650, root box, and deviant xoned. All of the them have this or similar issue with BT. It is Bluetooth driver problem for 4.2, because on stock jb 4.1 it's working well.

Hope one day can be fix.

Cheers! :beer:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] froggymike911:
failing

Hopefully i dont get blasted for this, i've searched A LOT. most recent bootloader (I747UCDLK3) most recent twrp (2.5) and i'm still failing. Even tried wiping the internal entirely and re-odin the stock with injected root and then installed twrp. Still failling.

ANYONE, please help! RC2 flashes fine. losing my mind here.

edit: nevermind. finally got it working somehow. no idea what was going on. MD5 was checking out fine the whole time. Frustrating.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
What is the exact error message?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
For those of you with Bluetooth issues, a commit has been pushed to git, which will fix the Bluetooth connection problems.

Look here: http://review.cyanogenmod.org/#/c/43830/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
on the latest build 6/7 there is an issue with custom lockscreen background

I can't get it to work (currently using buzz launcher)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
I can't believe how much got merged last night; thank you devs!

BTW, if you haven't yet, open a JIRA account and vote for flexfulton's submission. I was able to find it by searching "flexfulton"; took me less than a minute.

---------- Post added at 05:53 AM ---------- Previous post was at 05:37 AM ----------

I can confirm the same. It is darker, but selecting a custom image for the lock screen does nothing; the image stays the same as your regular background.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
There was a commit last night that borked it. I've already commented on the JIRA report about the new problem it caused.

JIRA reporting the original bug of not adding a shadow to custom lockscreen wallpapers can be found here. https://jira.cyanogenmod.org/browse/CYAN-1280

Commit information can be found here. http://review.cyanogenmod.org/#/c/43630/

So whatever they did to try to add the shadow to a custom lock screen image now prevents the custom lock screen option from working.

Hopefully it gets reverted or corrected soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
I can confirm this not only corrects the issue with Bluetooth not correcting properly, it also fixes Bluetooth hanging when you turn it off using toggles AND it doesn't do that weird thing where it sounds like a Transformer for a second if you've put a song on hold for awhile!

Once again, great job CM devs!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
looks like RC5 is out: http://get.cm/?device=d2att
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Wow, hope this should be the last rc before the final release
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
anyone know what changed in RC5? beside the bug on lockscreen lol

i can't find the changelog
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
http://changelog.bbqdroid.org/#/d2att/next perhaps?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] marinierb:
Yes! BT is fixed! I can go back to crack-flashing...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Nope, this only lists the last nightly aka 6/7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
My Issue Fixed?

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

This looks very promising. Can't wait until the next nightly!

---------- Post added at 08:23 PM ---------- Previous post was at 07:51 PM ----------

I'm not convinced the lockscreen wallpaper bug introduced in last night's nightly was fixed in RC5 but rather didn't have the original commit that borked it. Tonight's nightly should restore the custom wallpaper feature and include the darker overlay. RC5 shows the correct custom wallpaper but doesn't include the overlay which is what they were trying to fix all along which is why I believe RC5 just didn't have that code.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
Afaik, rc's are only getting bug fixes, not new features nor enhancements

Sent from my Nexus 7 [CM10.1]

Samsung Galaxy S3 [AT&T] [CM10.1]

Galaxy S Captivate [CM10.1]

OUYA
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I'm currently compiling a build with the latest fixes including the RIL one posted above. I'll edit this post with a link once I get it uploaded.

EDIT:

Here's the build. Only use on d2att please. It has all changes up to 8:30 PM EST. cm10.1-unofficial201301608
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I know that and none of what I mentioned was a feature addition. It was all bug fixes and fixes for new bugs that first fixes introduced.

CM is in lockdown though from new features being added. You are right.

---------- Post added at 08:47 PM ---------- Previous post was at 08:36 PM ----------

The corrupted garbled name call display seems to be fixed in RC5 for us Canadians who have that feature provided by our carriers (Rogers, Fido etc.) Looks like we are good to go with all modems now instead of having to use the ICS based ones.

---------- Post added at 09:11 PM ---------- Previous post was at 08:47 PM ----------

Downloaded and installed but the issue is still present. Reporting 0dBm and lingering on that instead of handing off to 3G. It looked promising and even made mention of a few things LTE and incorrectly reporting related but it's not what I was hoping for.

Thanks for compiling that. It is much appreciated! Have a great weekend.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] humblehyper:
Have they ever fixed the low volume while recording video? And when creating mms and attaching a capture video is too short, i think 5 secs only?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
The so called rc5 has battery draining problem. The phone.apk sucks the battery like a vampire. Clearing cache, permission didn't solved the problem
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
So far, so good on 6/8.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Have you tried a data wipe? Seems abnormal for an rc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
Any news on 8th bluetooth?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
It's been working well for me for the past few days. Solid connections, solid reconnecting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Clean install
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corno1979:
No unusual usage by phone.apk on RC5 here. It's using about 2% for me, but I have made few calls. Are you referring to unusual drain when making calls, or is your phone.apk draining even when idle?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pudgieluv:
Data Disconnecting Permenatly

Anyone having issues with data on RC4 or 5 - I did 3 clean installs, my data will work for a day then it won't connect.. Really weird issue... Wireless works fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Even when idle, tons of wake locks. Reverting to aokp
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corno1979:
Anyone who uses a USB car dock should be a pal and vote for this bug:

CYAN-1080
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
For those with bluetooth issues, it seems that the new Ktoonsez kernel updated to fix bluetooth issues.

http://xdaforums.com/showthread.php?t=1756776
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
It was updated with CM code that fixed it. So it should be noted that whatever KT has in his kernel is present in the stock CM kernel too. His isn't the only one with fixes and he didn't come up with the fix on his own for his kernel only.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lessaj:
Had that happen once or twice. All I did was reboot and it was fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
KT states in his change log that the fix was from CM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I am aware. I'm not saying KT claimed it as his own fix. The guy who I replied to was almost implying that KT had the bluetooth issues fixed in his kernel but that it wasn't fixed in CM.

I was simply saying KT merged the code from CM which yes is stated in his changelog.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
Came from RC4 to nightly, and battery is terrible. How is RC5?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sNoxious:
Which Nightly are you on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
Today's...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Updated to latest nightly, came back to 5/20.

Tired of this crap, still graphical freezing when playing games after some time. d2can with d2att TWRP & CM10.1 d2att nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] plonka2000:
MHL fixed?

Hi guys, any news on MHL support in the latest build?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tarphoun:
RC5 is amazing for me. Looks like the idle battery life issues are fix. Phone been unplug for 21 hours now. Down to 67% battery. used less then 10% during the night.

I could not be happier right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gtridr:
No idea, but i have an adapter. I'll test tonight if i have time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
so far RC5 is pretty good for me

~30% battery a day with minimal usage
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
my battery on the last few nightlies up to and through RC5 hasn't been great, but I haven't done a clean flash yet. I'm just waiting until the stable release to go through the BS of a clean install.

Besides that, everything has been gravy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
I just dirty flashed back to RC5, much better.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikalCarbine:
I've experienced this twice now, at first I thought it was just an AT&T call anomoly but it's happened twice in two different locations and hasn't happened to me before.

When placing a call the audio is all garbled up, the ring and the voice during the call. The person on the other side can hear me fine. Multiple calls after this would have the same effect, a reboot was the only way to fix it. Currently running RC5 with UCLI5 modem and CM10.1 kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tiffany84:
I went ahead and updated the mod again based on the 7/27 build. Follow the same instructions to flash.

Circle Battery Mod for 7/27 Build:

http://d-h.st/cnE
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I've noticed that the latest AOKP build was faster than the 7/25 of CM10. install Kt557 kernel and you'll be golden. My battery life is running at about 24 hours of on time with heavy usage.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kurant1:
Nope, I've had this problem since the original build. I've since gone back to ICS. This build was no different.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phoneguy589:
Thanks for this.

I flashed the newest build of CM10 over AOKP and ask is working good but is there an option to move the clock to the center of the status bar? Might have to wipe then reflash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DynamiteRave:
The s3 uses a specific type of mhl adapter. Go to Amazon and search EPL-3FHUBEGSTD.

Bath salts made me eat my nexus
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tophaholic:
That has been my observation as well. Cm10 seems to be much smoother than aokp as of now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mentalmuso:
I am using camera ICS+ as a workaround. Focuses great.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rosalesj:
Awesome thanks !
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] answer1o1:
Works great! Although it crashed after I tried auto focusing like 30 times haha simple reboot fixed it though.

Edit; Camera ICS+ keeps crashing after each pic I take. I'll just wait for the fix no biggie.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nismax:
Nice work my friend. Its so nice to have such a polite dev. Thanks again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cyanogen:
If you change the kernel, please don't even consider posting bugs here :)

The kernel in this build is very bleeding edge and has a huge number of changes in the graphics/video subsystem- it's the jb-test branch.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] los0325:
Delete
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snotyak:
You shouldn't be posting QUESTIONS here, but a quick google search will get you this - https://play.google.com/store/apps/details?id=com.klncity1.emojikeyboard
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] los0325:
Thanks tho i already tried that app it was garbage
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enzyne:
Retracted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
The main draw of the kernel was the UC to 192 and the inclusion of the smartass v2 governor. Right now I'm using noop/ondemand on your 7/27 CM10. What governor do you suggest I use?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dmize:
I figured out why jb SMS wasn't working. If the number you add from the contact list has parenthesis around any part like the area code, it gives a number like 1 742 7636. Instead of what might be in the address book like 1 (655)742 7636. Take out those ( ) and it works. Hope this helps!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Uss_Defiant:
I'm curious about this too. Also, anyone know the good / bad about the msm-dcvs governor on this Rom? I tried searching but couldn't find much about it, especially from a reputable source.

It seems to be working quite well for me but cannot comment on battery life just yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AmazingSpanoMan:
I second this. Taking the ( ) does work also if you don't want to go through your contacts and remove them on each one, I found that if you go into the contacts app and select someone and use the send message icon from there the number comes up correctly.

Next, I wanted to report that most apps that have small popup ads for some reason FC when an ad pops up. Specifically, the engadget app does this every time. This is not new for this build just wanted to point it out. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] QuarkGluonSoup:
When I install this and CM9 gapps, there is no native camera app. Is his normal? I can download one but I thought one was suppose to come with the ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Maybe try a newer modem? I think the latest official is CDLK3 for AT&T
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] minnick:
I dirty flashed from 5/1 to 6/9 and feel the battery life has gotten better. Just an opinion of course.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikalCarbine:
I'll revert back, I flashed the older modem hoping it'd help these weird signal issues but I think its because we done have a 4.2.2 modem yet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] radeon_x:
Low volume in recorded videos is still an issue, unfortunately.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unit_vector:
Game/Graphics Freezing

I see a few other people have the same problem when playing a game (even one as simple as a crossword puzzle) eventually the game will "freeze" (really just run really slowly, it will actually respond to taps if you wait long enough and you can get back to your launcher). I've found a workaround is to disable hardware overlays in developer options. Unfortunately this isn't a "fix" since it disables a useful (though broken) feature, and the setting does not save across reboots, but it does allow me to play games on my phone without the freezes. If you can manage to get back to your launcher and into settings you can even disable it on the fly and get back into your game running in the background.

Does everyone else have this problem? Can anyone confirm that they do NOT have any problem playing games for an extended period of time?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Darren Moffatt:
No problems playing games for extended periods of time here.

In setting up RC5 I wiped EVERYTHING from /data, /system and even /sdcard just for good measure. Once the phone was completely cleaned out I flashed RC5 and GApps only. Let the phone reboot, ran initial setup and then left it to settle before I started going install happy.

Phone is running flawlessly so far!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Thanks. Do you have a d2att or d2can? What games have you tried? I've had issues with Real Racing 3 and Snuggle Truck (I believe) so far.

https://play.google.com/store/apps/details?id=com.ea.games.r3_na

https://play.google.com/store/apps/details?id=com.OwlchemyLabs.SnuggleTruckAndroid

I'm aware the first game is quite big so I understand you might not want to take so much time to download it (unless you like this type of game). The second is smaller however. If you can, try to play for at least 15 minutes. Thanks again