yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] Kalm_Traveler:
I noticed some slight screen lag at first but after a few days of use it seems smoother than my stock ROM. No lag since that first few hours and I haven't had any freezes or locking up at all.
[T-Mobile, Samsung Galaxy SIII] futuremonkey:
I'm always astonished at people who somehow manage to get such crazy battery performance. Maybe I'm just unlucky or doing something wrong, but I can never come anywhere close to most of these claims. For example, I have to leave my phone locked in a locker most of the day while I'm at work. So during the 4 hours between the time I get to work and the time I go to lunch, my phone has usually dropped from 100% to about 80%, sitting idle, doing nothing at all. I use Falcon Pro and G+ for maybe 30 minutes at lunch, then back in the locker it goes for another 4 hours. I'm lucky to have 50% juice left when I pick up the phone again. It was only slightly better on the stock TouchWiz ROM.
[T-Mobile, Samsung Galaxy SIII] Kalm_Traveler:
I have noticed that a huge difference had to do with being on Wi-Fi or strong cell signal. If I'm not on Wi-Fi or am somewhere with poor signal from cell towers the drain is much much faster
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
With the phone in your locker, and you don't have access to it:

1) Turn it off.

2) Put it in airplane mode.
[T-Mobile, Samsung Galaxy SIII] imilleson:
So the flicker and reboots has been keeping me away from flashing this ( I tried it in January and it flickered with hw overlays and rebooted every so often) . if this has been resolved which it looks like it has in the latest nightly according to the last few pages, I might flash. I love cyanogenmod (used to use it on the vibe). How quick is GPS lock ?
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Wait until tomorrrow's build, at least. See if they address the phantom battery drain issues people are reporting.
[T-Mobile, Samsung Galaxy SIII] klin1344:
http://changelog.bbqdroid.org/#/d2tmo/next

From the changelog for the next nightly, it doesn't look like there is anything related directly to fixing the battery life on d2... Is there a specific commit you are eyeing?
[T-Mobile, Samsung Galaxy SIII] Bray90820:
My logcat is attached and I should state that I am using the T999L which is the LTE version of the T999
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
http://10.1.cmxlog.com/?device=d2tmo#

I really wish these were synced. Particularly looking at the memory leak commits. Also curious about the wifi one.
[T-Mobile, Samsung Galaxy SIII] imilleson:
I saw someone a couple pages back saying nightly 6-10 had amazing battery life?
[T-Mobile, Samsung Galaxy SIII] rage913:
My bad kind sir. Thought that I had posted them! Lol :o well at least the right ones. I did reboot my phone when you told me to and I did turn off location settings aswell and battery got way better. It's just frustrating to not be able to use Google now.... But here are my stats for now at least. Haven't really used my phone as hard... But still decent.

Alright, I believe I've posted kernel, partial, and other from bbs. No WLD! :cool:;)
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
It's terrible right now. There's some kind of memory leak or something. Which means its fine for a while, and slowly gets terrible. BBS is unable to detect the cause. It's not wakelocking.

You can have GPS location enabled, just disable the wifi & mobile network location. That stops the NLP wakelocks. Greenifying Maps should stop those other Maps wakelocks, unless Google Now is starting it. I don't use Now, so I can't comment. The idea is cool, but it has no practical application for me. In what way are you using Now?

In your case, PowerManager wakelocks look all music related. Can't avoid those if you want your music! I work outside, and alone, so I always have music going. On top of normal drain, Poweramp uses ~1.5% per hour. So 2.5-3% an hour drainage with music going (and nothing else). I like Play Music ok, but all my mp3s there are 320kbps. I chewed throught half a gig of data in an hour. Oh well, I'll just copy the music I want to my SD card. That's kind of why I have it.

I am unsure why you have Apollo, 8tracks, and Play Music running at the same time :) Streaming services eat a fair bit more battery. 2-3% extra per hour on top of the other stuff. And stay away from TuneIn Radio. That app eats 15% an hour. Not nearly enough people complaining about that bull****. Totally unacceptable. How is this ok to anybody?
[T-Mobile, Samsung Galaxy SIII] itzsmokey:
Doesn't that mean they'll be included in the next nightly?
[T-Mobile, Samsung Galaxy SIII] frappe33:
Had this issue - issue was corrected by removing gallery and manually installing the version extracted from the RC5 zip.

---------- Post added at 12:51 PM ---------- Previous post was at 12:39 PM ----------

Did you disable hardware overlays in developer options? This corrects the animation lags in most cases.
[T-Mobile, Samsung Galaxy SIII] titan703:
So I was running RC5 and the 6/10 nightly just fine, but when I flashed (through cmupdater) the 6/12 build, I lost the ability to send MMS. I get "Service not activated on network." Now, I know it could be a T-Mobile problem, but I have seen nothing about it anywhere today, and was hesitant to call them since their trouble shooting steps always involve things not compatible with AOSP. I reverted to a Backup from yesterday, four days ago, and even older, and the issue persists. I have done everything short of a wipe and clean install, but I don't see how that is going to help.

Anything?
[T-Mobile, Samsung Galaxy SIII] mt3g:
It's a CM issue I think if the image is too large it is not resizing it for some reason. Try to send an image of something small like an icon I can send 10/10 but a picture I just capture it will give me the same error as yours above.
[T-Mobile, Samsung Galaxy SIII] ami2510:
I got the same issue, any ideas?
[T-Mobile, Samsung Galaxy SIII] mdfritz:
6/12 seems better today. No reboots, no freezes, no blue tooth hang (used all day and switched bt devices multiple times with calls). No mystery drain yet (at 35 percent now with 5.1 percent/hour drain.
[T-Mobile, Samsung Galaxy SIII] klin1344:
However, if you disable hardware overlays you are basically disabling project butter. You will notice that in scrolling with hw overlays disabled, there will be stutters if you scroll fast.

This post talks about it: http://xdaforums.com/showpost.php?p=40095456&postcount=2
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
The msm_otg wakelock seems to have reared it's ugly head again with the newest nightly.

And 3 outgoing calls in a row failed to dial. Had to reboot.
[T-Mobile, Samsung Galaxy SIII] mondokat:
quiet

either the latest nightly has so little wrong with it there's nothing to say, or there's so much wrong with it, no one's phones work well enough to post...

which is it?
[T-Mobile, Samsung Galaxy SIII] klin1344:
The first one ;)
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
I detailed some pretty serious issues in my last post. Not being able to make outgoing calls without rebooting is a very serious problem - one that I haven't seen since 10.1 was brand new.
[T-Mobile, Samsung Galaxy SIII] corkythetard:
Same here :cool:
[T-Mobile, Samsung Galaxy SIII] ajm786:
I don't have any of these issues at all. What happens when you revert to a previous nightly?
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Revert? There is no backwards, only forwards!

I can't reproduce any of these issues. But they most definitely were there.
[T-Mobile, Samsung Galaxy SIII] mdfritz:
On 6/13 I had a freeze up during a call. It's not as frequent as it was about a month or two ago when it was an epidemic, but the last 2 or 3 nightlies have been freezing sporadically. We'll see how 6/14 does.
[T-Mobile, Samsung Galaxy SIII] falcons2:
I can't send MMS on rc5. Is their a fix for this? It tells me service is not activated on network.
[T-Mobile, Samsung Galaxy SIII] milenko11:
I have this problem on CM9 as well.
[T-Mobile, Samsung Galaxy SIII] es7241:
Have you tried formatting the card through windows
[T-Mobile, Samsung Galaxy SIII] doubled227:
You know... never thought of that. Can I do that with windows cuz I know next to nothing about Linux
[T-Mobile, Samsung Galaxy SIII] doubled227:
You know... before reading that, I searched for a windows option and found a program. Now the only thing that confused me is that I used aokp on ice with my galaxy s2 and I never needed to reformat. I was under the impression that aokp was based on cm so I should have had these issues but I didn't. But I am having it also with the jb aokp on this phone
[T-Mobile, Samsung Galaxy SIII] es7241:
Did you format the SD card on the Galaxy s3 before flashing CM , that may be why.
[T-Mobile, Samsung Galaxy SIII] doubled227:
Nah... I never needed to format at all. From when I had it from my galaxy s2 (while using touchwiz and aokp) and until now, I never needed to format. I only needed to worry about formatting until I got to cm10 and jb aokp. I was only confused that ics aokp was based on cm9 so I should have ran into the issue earlier but I didn't
[T-Mobile, Samsung Galaxy SIII] SlakWReX:
You CAN format to fat32 on a windows. No programs needed.

Sent from a Galaxy 3759295 light years away.

Thank me if I helped :D
[T-Mobile, Samsung Galaxy SIII] krazygreen:
Posted an in depth video showcasing this rom (with Jelly Bean Gapps flashed and included), for anyone interested in watching -

http://www.youtube.com/watch?v=UNGQSWWIozs"]http://www.youtube.com/watch?v=UNGQSWWIozs

Thanks.

---------- Post added at 06:13 PM ---------- Previous post was at 06:12 PM ----------

Bret doesn't mind =)

He sells phones for a living, that's his shops number - no biggie, he actually likes shootin' the **** with random Android heads so give him a call! ;)
[T-Mobile, Samsung Galaxy SIII] jwalters1123:
Oh OK cool, I was just giving you a heads up in case he didn't want his number everywhere and you didn't realize it was clearly recognizable. Anywho, maybe I'll drunk dial him if I ever brick this thing ;)
[T-Mobile, Samsung Galaxy SIII] krazygreen:
Haha

"Heeeyy Bret! Long time no talk! So Jelly Bean huh?! Yeaaa boy smokin' iOS one update at a time! BRB Bret ol' buddy ol' pal, gotta take another shot!"
[T-Mobile, Samsung Galaxy SIII] sn0warmy:
While the 7/20 build had too many bugs and wasn't stable enough for a daily driver, I've got to say that this is not the case with the 7/29 build.

The only bug I've run into over the past 2.5 days on this build is the inability to increase/decrease in call volume while on a call. However, the simple solution to this is just to pull the phone away from your ear and let the screen turn on before adjusting the volume with the volume rocker. Aside from that I've found no glitches in my daily use. My data speeds seem just fine as well.

Thanks for the hard work!
[T-Mobile, Samsung Galaxy SIII] Monk4Life:
That's good to know. This same bug is present on CM9. If that's the only thing you noticed then I am switching to cm10.
[T-Mobile, Samsung Galaxy SIII] ikhtiaralam:
I see that A2DP is completely broken. What does that mean? Can I not connect my phone to my car's Bluetooth?
[T-Mobile, Samsung Galaxy SIII] G1_enthusiast:
yep, i'm waiting on this to get fix this is the only thing stoppping me
[T-Mobile, Samsung Galaxy SIII] cashyftw:
exactly
[T-Mobile, Samsung Galaxy SIII] ikhtiaralam:
Okay, thanks. But in CM9 it's fully functional. Correct?
[T-Mobile, Samsung Galaxy SIII] TheSeanTeam:
Check here yet?
[T-Mobile, Samsung Galaxy SIII] OGWisdom:
You are correct bro! cm9 is the base of aokp, cm10 is the base of aokp jb. Without cm, aokp wouldnt exist! Now, When I got my 64gb, I thought it would be a snap to just install it and go. This was not the case! Everytime I tried to format using windows, I got no dice! I even downloaded and installed a program just for formatting sd cards, that didnt work! What I finally had to do, I flashed my gs2 all the way back to stock, no root, no nothing! Went to setting->storage->format sd. It finally formatted and has took ever since! It can now be read when plugged into the computer, although not every way works. I ordered a nano card reader, seemed to be the only way windows would recognize the card. But the card went from my gs2 to my gs3 with no issues! Hope this helps and good luck bro! O, two more things, one you should NEVER have to keep re-formatting your card like that! And two, yes the card needs to be formatted using FAT32. I guess the gs2 stock did all that!
[T-Mobile, Samsung Galaxy SIII] arathur:
I love this ROM. I just hope one day the camera works as well as the stock TW one. That one used to auto focus on everything in an instant. With the cm10 one, I can't seem to focus on objects very close to the camera, not even in macro mode.
[T-Mobile, Samsung Galaxy SIII] krazygreen:
Try downloading Camera FV-5. It's a great replacement and somewhat makes up for not having the stock TW camera. It's got great features and a good auto focus, which functions well with this rom.
[T-Mobile, Samsung Galaxy SIII] Vodkanakas:
So is this only cm10 4.1.2 or does this apply to cm10.1 4.2.2? Cause I've tried cm10.1 with 12/03/01 gapps and the phone freezes reboots randomly and some apps don't work period.:( loved cm10.1 on my s2 but it's just not working on my s3.

Edit: Sorry about the date lol but its gapps-jb-20130301
[T-Mobile, Samsung Galaxy SIII] Sixonefour:
This thread is CM10.1 (4.2.2) and have you tried a clean install? RC5 is working pretty nice for me.

You have may to update your bootloader.

Edit: http://xdaforums.com/showthread.php?t=2282603.

That link should work for you if your bootloader needs updated. You may also want to consider updating your gapps to 20130301 or any variation you can find around here.
[T-Mobile, Samsung Galaxy SIII] mondokat:
you convinced me, upgraded from rc2 to latest nightly, everything is good. better in fact. what a difference a month's worth of commits makes. :P
[T-Mobile, Samsung Galaxy SIII] mdfritz:
This seems to be a general AOSP/AOKP issue, but I can't seem to get any answers when searching: Has anybody else noticed that photos aren't automatically uploaded to Google + auto backup since about May 31st or prior. When you select auto backup in G+ settings, it says to enable auto backup in android Google Account settings, but there is no checkbox for that in settings. Seems like Google updated their sync setting checkbox, but the ROM settings haven't caught up.
[T-Mobile, Samsung Galaxy SIII] rage913:
Looks like 6-15 has some new commits to mms :D. Let's see if this helps out people with networking errors. Downloading as we speak and ill report back in a few!

Edit: well that blows. I wasn't getting the error message before but I don't think my pictures were sending. Now I'm getting the full blown "not connecting to network"
[T-Mobile, Samsung Galaxy SIII] ami2510:
I've been getting that message since I've been in the 6 12 build. Doors anyone know how to remedy it?
[T-Mobile, Samsung Galaxy SIII] ajm786:
I'm on the 6-14 nightly, and I'm not having any of these issues you speak of. I just sent myself some pictures, and they all came through just fine.

I suggest you try resetting your APNs (literally, there's an option for it in the APN settings), and then try choosing a different one to see if it makes any difference.
[T-Mobile, Samsung Galaxy SIII] ziggy46:
Ive been on 6-15 since there buildbot spit it out. No problems here
[T-Mobile, Samsung Galaxy SIII] rage913:
[\QUOTE]I'm on the 6-14 nightly, and I'm not having any of these issues you speak of. I just sent myself some pictures, and they all came through just fine.

I suggest you try resetting your APNs (literally, there's an option for it in the APN settings), and then try choosing a different one to see if it makes any difference.[/QUOTE]

This is what I've got. Sad face. It's bothering me wanting to send a pic and I can't. I've refreshed the messenger app and I've switched to all three different T mobile and I still get no dice. And I've changed fro gsm/wdcma and all other three. Grr :banghead:
[T-Mobile, Samsung Galaxy SIII] rage913:
Are you on a custom kernel. I went backwards to rc5 just dirty flashing without kt747 and I can send messages now. Going to go forward to 6-15 and see if i can still send messages then flash kt747 and see what happens.

Edit: apparently 6-15 doesn't like my phone. Rc5 is cool with my phone but not 6-15. Going to try wiry a custom kernel.
[T-Mobile, Samsung Galaxy SIII] Derzicom:
Still having problems sending pics in my messages (MMS) For you that are not experiencing any problems is you camera set to take 1Mb photos? From my testing it all comes down to my photos not being reduced in size automatically if I crop them to something less than 1Mb it will go though. Please work on this
[T-Mobile, Samsung Galaxy SIII] ajm786:
I just sent myself a picture of a photo that I took that is 8MP (1.77MB) in size. It downsampled it to 215kb, sent, and I received it just fine.
[T-Mobile, Samsung Galaxy SIII] corkythetard:
No MMS issues here. Just flashed 6/14 a few hours ago and sending/receiving via GoSMS like nothing's changed.
[T-Mobile, Samsung Galaxy SIII] rage913:
It seems like I'm able to send messages now but here's my question. Are you guys on stock kernel or custom. As soon as I flashed back and kept the cm kernel I was able to send mms. I'm hesitant to re flash kt747 lol... Just curious.
[T-Mobile, Samsung Galaxy SIII] Derzicom:
I'm stock.. I try not to muck things too much. Sometimes the pics will send and then when I really want/need it to it wont!:confused:
[T-Mobile, Samsung Galaxy SIII] ajm786:
Stock. Custom kernels have always given me problems, except when I've used a franco kernel (obviously, none for our phones, so stock it is).
[T-Mobile, Samsung Galaxy SIII] stonew5082:
I can confirm mms works using ktoonsez on the latest nightly fyi
[T-Mobile, Samsung Galaxy SIII] corkythetard:
Stock kernel here. I wanted to see how it compared to me running ktoonsez for the last few weeks. So far, MONEY! I have no need for a custom kernel unless I want the fast charge and other tweaks that come with the ktweaker app. All flickering that ktoonsez's kernel fixed is gone for me, so I'm back to stock. Set cpu @ 1350Mhz and i/o to ROW.

BUTTAH!!! :good::good::good:
[T-Mobile, Samsung Galaxy SIII] stonew5082:
Why do people put colons after good I don't get it
[T-Mobile, Samsung Galaxy SIII] rage913:
Hmm I may try stock. I just flashed kt747 and im able to send pic messages again. Let's see how it fairs tomorrow. Was driving me damn nuts.

I think it's the smiley face on mobile not being spaced out. :eek::eek: :eek:
[T-Mobile, Samsung Galaxy SIII] corkythetard:
For some reason DSP is still not working for me on Pandora! *ducks and covers* Ya man, stock set to ondemand is good for me so far. Definitely worth checking out. :good:
[T-Mobile, Samsung Galaxy SIII] mdfritz:
Yeah , dsp on streaming apps never got fixed. How do you tweak governor and I/o settings on stock kernel? Is there an app that you use?

Edit: Nevermind :o just looked at performance settings and paid attention for the first time ever.
[T-Mobile, Samsung Galaxy SIII] labrea:
After a year + over 12k messages and still nightly builds, wow I never seen a rom takes that long to get released, good luck guys for everyone who puts effort on it
[T-Mobile, Samsung Galaxy SIII] rage913:
Gee that escalated quickly... On another note mms seems like they have called down and I now have pie working flawless!!! And I still have long press on my physical buttons :D:p;)
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Eager to learn your idle battery drain with stock and kt747.
[T-Mobile, Samsung Galaxy SIII] corkythetard:
Will let you know. Not sure how relevant it will be once I gather the data since the next nightly appears to be going back to the 3.0 kernel.
[T-Mobile, Samsung Galaxy SIII] matrixzone:
Why are they doing this? Crazy
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
I suspect that "msm8960: allow 3.0 kernel" <> reverting to 3.0 kernel.
[T-Mobile, Samsung Galaxy SIII] ajm786:
Something changed in the last month, where the MDP bandwidth fix that fixed all the flickering either got reverted, or something else messed up, because the flickering has been back ever since. I even opened up a JIRA report on it and it's assigned to Steve Kondik now. Annoying, because everything else seems to be working great.

https://jira.cyanogenmod.org/browse/CYAN-1405
[T-Mobile, Samsung Galaxy SIII] corkythetard:
I see what you're talking about, but I'm the bug anomaly around here and have no flickering, even the app specific flickering prior to flashing ktoonsez's kernel, on 6/14. I used to have to disable hw overlays even with ktoons kernel. Not with this build.

Thank you for opening the JIRA report for everyone else! Glad it got assigned to Steve!! :good::good:

---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------

That's what I read and why I didn't know if my bbs stats would be relevant once the 3.0 kernel revert is implemented.

---------- Post added at 03:33 PM ---------- Previous post was at 03:31 PM ----------

When they switched to the 3.4 kernel from 3.0 things went wonky for just about everyone. From flickering to random reboots mid phone call to hot boots, etc.
[T-Mobile, Samsung Galaxy SIII] klin1344:
Lol guys I don't think that the CM devs want to revert to back to the 3.0 kernel again...we'll be on the 3.4 until Qualcomm decides to stop updating it for newer Android versions.

I think that the commit "allow 3.0 kernel" was because the apexq, Galaxy S Relay 4G, will be being merged into the source trees and getting official CM support. Because the Samsung msm8960's (d2, jf) are both on the 3.4 kernel, they needed to ifdef the flags for the Relay 4G because it is still using a 3.0 kernel.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
<> = does not equal.
[T-Mobile, Samsung Galaxy SIII] klin1344:
You mean != ? :p
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Ha! Depends on the language :)
[T-Mobile, Samsung Galaxy SIII] corkythetard:
Thank you for the clarification. I'm heading off for the night and wanted to share the 5+ hour drain of little to no real use. 1 phone call. FB a few times and a few e-mails. What confused me was the amount of time cLock is draining. Any suggestions? The overall drain isn't too bad, imo. Better than what I was getting with ktoosez's last build. :confused:
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Weird. That's some hardcore wakelocking. I've never seen it do that before. Does it still do that after a reboot?
[T-Mobile, Samsung Galaxy SIII] Six6Sicks:
Well you know nothing then because he no longer works at Samsung.

Also, this ROM has never been 100% stable, ever. While yes, the CM team does do a lot for the community...blah, blah, blah, it still baffles me, as well as many others as to why problems a, b, and c might get fixed, x, y, and z problems pop up.....then they get fixed, then here come problems a, b, and c all jacked up again. I've been on stock for over 2 months now due to the roller coaster of issues.

So stop with your almighty CM rant cause the fact is this ROM still has issues and has, since day 1.
[T-Mobile, Samsung Galaxy SIII] ckisgen:
everyone's experience (device, setup, etc) is different.

this ROM has been totally stable overall for me for MONTHS.

noticeably more stable than stock.

soo, just my $0.02 - but your post sounds a lot like an almighty CM rant too. just from the other side of the table.

(my point is, your 'facts' are relative. to you. which is fine and all. just keep other people's experience and opinions in mind too)

... ps, to everyone else - I'd feel even the SLIGHTEST bit bad making a totally useless off topic post like this if this thread wasn't 92% a joke anyway. (HEY, WHY CAN'T I FLASH CM. I GET AN ERROR IN RECOVERY. or HEY, HERE'S THE SAME THING 74 OTHER PEOPLE JUST SAID IN THE LAST 5 PAGES BUT I NEVER BOTHERED TO LOOK, etc)

peace.
[T-Mobile, Samsung Galaxy SIII] Halotron:
Bleh. Tapatalk not uploading screenshots properly. 50+ hours of battery life images later if I remember.