yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acloaf:
I stand by what I said. If you aren't happy, flash again and see what you get. 0921 nightly went from 100% to 0 in three hours for me. Not typical in any way but I ran it for 3 days and was getting between 10 to 12 hours. On a couple occasions I had a similar experience running the early 10.1 nightlies.

Seems every now and then flashing a nightly kills battery life. In my experience rarely does it not clean up after a couple charge cycles. If it doesn't improve try a new nightly. If you been 3 years on nightlies then you know it's a risk you run by running them. Battery life complaints are the one thing that don't help anybody because there's so many other factors that contribute.

Sent from my SAMSUNG-SGH-I747M running CM10.2 nightlies
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spotdog14:
Is everyone complaining about battery life have the option turned off in Location Access for "WiFi & Mobile Network Location"? I find that if I turn that off I get a great improvement in battery life.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
Guys, I just noticed that my wife's i747 doesn't ring anymore. The phone is on one of the latest CM nightlies, though not the latest. Is that a known issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Check that your ringtones are still set. Happens sometimes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
I had that happen myself. Check ringtones first, but then do a reflash. I reflashed and mine came back, not sure why they disappeared.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
They're set, alright. Don't know what's happening.

Yeah, I'll flash the latest nightly, see what happens. Will report back. Thanks for the replies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Check to make sure that you don't have a profile or quiet hours turned on by accident.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
I'm officially on the latest nightly. Flashed twice. Nothing. Checked everything, nothing looks funny. I do have silent hours enabled, though that won't come into effect for at least one hour from now. I'm desperate.

Edit: I think I know what's happening: the ringtone is routed to the front speaker instead of the back one. How do I fix that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joemommasfat:
I've noticed that cm won't allow you use any ringtones that aren't media indexed.

I put a .nomedia file in my download folder to prevent Apollo and gallery from using stuff in there. When I did that, it disabled all ringtones in there as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I know you think you have fixed it but another idea for others is that ring tones don't loop so if you have a short ring tone and asending ring tones set up and starting really quiet, you just might not hear it ring because it's not long enough to be still going when a audible volume is reached.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
Updated to latest and long press menu button to open Google search broke. Voice search works, but setting to just open Google Now is broken.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
Works fine for me on latest nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
Your next best bet is do a nandroid backup, wipe data, reinstall the ROM, then restore your data.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lessaj:
Works for me too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
Alright, mystery solved: it turns out that "Ascending ringtone/On each ring" was enabled, and that particular option ("On each ring") is broken. Anybody cares to submit a bug report, as I don't know how to do it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thecapitalr:
I'm currently running the 8/13 cm 10.1 nightly (I believe the last 10.1 that came out?). The thing is rock stable and has been since it's release. It looks like from reading the last few pages of this thread that I shouldn't upgrade yet? The nightlies are still unstable for 10.2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Well, unstable might be a harsh word for it, but they definitely aren't as rock-solid and smooth as the later builds of 10.1 just yet. Still a little ways to go in that regard.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cristianpark:
I found the nightlies not so unstable, I'm running 9/12 without a problem although I don't use LTE network, just 3G. You should give it a chance and see if its stable for your needs or if you have to stay at cm 10.1 by now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
I have never used OFFICIAL CM 10.2 on any device I've owned. Closest to it is Quantum by PwnCakes.

Might give it a try. (; Should I? :o
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Cm10.1.3 stable is decent enough believe me. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thecapitalr:
Funny I tried using 10.1.3 and got tons of wake locks and battery drains. None of it on the 8/13 nightly. This is by far the longest I have been on a random nightly ha but it works for me!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Wakelocks from?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phaze13:
No sound from phone speaker after unplugging headphones.

Looks like I may be the only one with this problem (have not seen anybody post about it). Started happening after flashing an update and persisted through a few more flash updates, currently on 09/28.

Phone speaker works until I plug in headphones. When I unplug them the phone speaker stops working.

A reboot will get the speaker working again.

Any ideas beside a full wipe flash?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I'm no help for that, but you can update your signature and write CM10.2 for your S3 now. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
So every build of 10.1.3 that I've tried has the same strange problem. Whenever I share something from one app to another, the second app will take place of the first whenever I try to launch it from Recents.

For example, if I share a link from Browser to Hangouts, opening up Recents and tapping on Browser will open up Hangouts instead. This will happen until I remove browser from Recents completely and launch it from scratch again.

Anybody else experiencing this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Works just like that until you back out of said app.

Example: Open browser, find a link to a video clip you can stream and it opens in your favorite video player. Press home button, then if you check recent you'll see your browser but when you select it, it's actually your video player.

I don't know if it's a problem or a feature.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
It's definitely a problem. That's not how it's supposed to work at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Doesn't really cause me grief though, and it seems to make sense to me, since I was technically using the video player spawned by that browser rather than the browser itself. Can't say I've paid attention to this on cm10.2 though, does it still happen?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
http://review.cyanogenmod.org/#/c/50197/

;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
You might not like it, but that's definitely how it's supposed to work and how Android has always worked from day 1 :), depending on how the app was written wrt to intent flags for each activity started in the back stack. source: Tasks and Back Stack
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ormandj:
I have the same issue, except occurring after using BT streaming in my Jeep. I have to reboot the phone to fix it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Hi guys. Ive noticed that all my APNs are missing from the list. Although they are not there my phone works properly. Is anyone else missing there APNs? I'm on a Canadian phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Running the latest nightly on the Rogers network and I have all mine intact.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DamnCampers:
Interesting issue I ran into recently. I dirty flashed the 20130927 nightly over an older nightly, old nightly prior to the MMS resizing working correctly, and noticed that I was able to send MMS messages without any problems. They would resize and send without any problems. I was experiancing a lot of force closes as I did not intinally update gapps. After installing the lastest Gapps for CM I am now noticing that I can no longer send or receive MMS messages. Is this an issue with doing a dirty flash, or is this just random?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Random and carrier related I would guess. Are you one of those that used my old mms fix?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DamnCampers:
Yes I did try the old MMS replacement patch, but it didn't work for me even then.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Have you checked if your APNs are set properly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DamnCampers:
Yes I've checked them several times. Still no luck. I've even gone as far as to replace all of APNs to see if that would work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
For the sake of it, can you take a screenshot of your APN settings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Bye

Just wanted to say BYE all.

This CM XDA thread has been my fav subscription for the past year+ with a mostly-great set of users helping each other out without big egos getting in the way (unlike certain other ROM threads I could mention :)), but, I'm moving on to a Galaxy Note 3 (64GB T-Mobile version) and selling my SGS3, so this is my last post here. *sniff*

Hope to see some of you again in the Note3 CM forums when it's available :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DamnCampers:
Picture 1 and 2 are the 3g settings. Picture 3 and 4 is for the lte settings I'm using.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Man, all seems good. You can receive but not send, right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DamnCampers:
I could receive on the old nightly, but since I installed 2013927 and Gapps I can't send or receive.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Ok so definitely not a resizing issue. Which gapps did you get? Not that's supposed to matter.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DamnCampers:
20130813 from the cyanogen wiki as I didn't grab it when I pulled the update from the settings menu.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Google released 4.3.1 yesterday, hope CM catches up soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
It was released yesterday... So just sit tight lol. Also the update weighed about 10mb so I doubt its anything groundbreaking. Kitkat is coming out soon anyways so I wouldn't mind if they just waited for 4.4.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
If you hang around long enough you'll notice matrixzone is hyped about every commit. Agree with you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
lol. agreed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I just LOL'd.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Being vocal is not bad but getting personnel is, which what you have done. The reason users are using CM or even XDA is the latest technology, if you like the older stick with the stock ROM and then you don't have to read my post anymore. CM/XDA is all about cutting edge technology with latest commits which change the games on some occasion.

---------- Post added at 11:40 AM ---------- Previous post was at 11:37 AM ----------

10MB can contain lots of updates, the size is not what matters dude. 10MB can contain the updated kernel, features and other stuff. Don't know if you have ever being into development. In that case, for you 4.2 and 4.3 will also be not major update, but Google has actually improved the stability, and framework in 4.3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
I'm sure if there was something worth noting in the 4.3.1 update Google would have announced something before release. Also it only hit one device, so most likely a bug fix or something.

Part of the reason people "notice" that you are itchy for the latest updates/commits is because you almost always post that you are eager for an update/anticipating the next release, which is understandable. It's not necessary to post it though. Everyone is eager, because like you said we use CM/XDA for the latest and greatest. I don't mean to start anything and this is already off topic as is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You've asked for an update in nearly all threads of custom kernels available every time there is a vaguely interesting commit that you've somehow stumbled upon.

You're free to show your interest, whether or not you fully understand how it all works, but I can't help but chuckle a bit whenever I see one of your posts. I'm pretty sure that's not considered as "bashing".

And without intention of making this a popularity contest, apparently at least 5 other people agree with me that you have a very peculiar way of expressing yourself.

Now be a champ and take this as it was meant to be, just a simple joke. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thecapitalr:
Just wanted to say that I finally upgraded from the 8/13 cm 10.1 nightly to the 10/6 cm10.2 nightly..

Very impressed. Thus far have had zero issues to speak of! Did a dirty flash too. Good stuff! Seems a bit smoother than 10.1 did.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I did the same. I've been testing on and off cm10.2 nightlies while always keeping my cm10.1.3 stable (and my nightly prior) and 10/6 has been my choice now. Strange coincidence, or great minds think alike? :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
CWM ADB Installation

After copying recovery.img to the Sdcard the following command path was working for installing CWMs on Cyanogen 10.1 and earlier.

dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 <<<

This no longer works since 4.3 has emulated file structure.

New Path for installation is:

dd if=/storage/emulated/0/recovery.img of=/dev/block/mmcblk0p18
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
You are right I am excited with every commit which maybe the latest 4.3.1 update which for some users could be 10MB update, but for me any incremental update is important. So if that is going to hurt someone, then those people have to live with this. If 5 have thanked your post, someone thanked my post which is irrelevant in XDA. If people don't like update, stick 4.0 and leave XDA
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Just updated to my first 10.2 nightly after reading some of these positive reports about stability and speed, and I was wondering one thing about these 4.3 ROMs for the S3.

Do they add TRIM support like they do on Nexus devices? Or was some sort of TRIM functionality already baked into CM in earlier versions as well?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
If your rom mounts /data with the discard option it's mitigated. Not the "right way" to do it, but effective enough. Plus without proper TRIM, performance degrades as memory gets full. This doesn't happen if mounted with discard.

If you have a fstrim init.d script or similar, whenever you reboot it's gonna get TRIM'ed and you'll never really face the issue unless you go extended length with lots of writes without rebooting. And once again, if your /data isn't mounted with the discard option.

I do not know how the volumes are mounted under "stock" CM10.2, but you can check yourself if you feel like it. You can also mitigate this bug no matter what if you have a lot of free space. Say half your memory is empty, then you'd be lucky to run into degrading performance because of this.

You can also check yourself by using a few commands:

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

Adapt them for the S3 blocks though, this is for One X.

(I know it's like the third time you've asked this and I never took the time to answer you, but I honestly didn't do any research to bring facts to you about how CM handles the issue with the S3, so I know my post isn't as informative as it could/should be. But hey, at least you have a little something)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Ah, okay. So even though TRIM support was added officially to AOSP 4.3, there's no guarantee that 4.3 custom ROMs feature it in the same way?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I don't know, haven't researched it. I would think it would be since it's AOSP, but even on 4.2 and prior CM might have used a workaround to mitigate the issue. Or not. Hence my not so clear post.

Somebody with the time/knowledge might be able to answer you in a more certain way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Okay, gotcha. Sounds like it wouldn't make much of a difference for me either way since I always have plenty of free space of my devices.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] araemo:
Wrong. The SE drivers are in CM10.2, (and were in 10.1). But google wallet has a whitelist of devices/carriers it's allowed to enable Tap & Pay on. I use this XPosed module to bypass the device checks. Combine that with build.prop edits during initial wallet setup, and tap&pay gets enabled. You can revert the build.prop edits after tap&pay is initially enabled, but you have to keep XPosed and that module installed and active (Re-install xposed framework after every time you flash a new nightly/rom). Edit: I did notice that a lot of 'build.prop' editor apps fail in 4.3, so I just did it directly with adb pull/push.

---------- Post added at 10:29 AM ---------- Previous post was at 10:27 AM ----------

TRIM support needs to be enabled in the OS (Android), the kernel, and the device hardware.. Whether or not the d2's flash controllers support TRIM is an open question to me (I haven't bothered to research it), and then that would have to be filtered up to userspace through the kernel so that the android framework would know to run the trim passes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yes I'm aware of the SE drivers being present (SIM being the SE IIRC), although my post didn't make this clear (and even made it sounds like it wasn't available at all, my apologies). I should have explained further. Sometimes I'm a bit too in my own thoughts. :p

Long: I believe modifying the build.prop or any other methods to make Google Mobile Wallet run on anything other than an eligible mobile phone equipped with NFC or outside of the 50 states and the district of columbia or to deal with anything other than US dollar to be a breach of the terms and might end up with your account being terminated without notice. That's scary enough considering it deals with your money, so I'd rather keep away from such. You can confirm this by reading the terms & conditions.

In other words, it might be a matter of time before Google takes more active initiatives to close these "holes" down. Bringing build.prop modding and such to a more popular state and displaying it all over the net might just get them to do it faster. Thread with caution. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Go to the terminal and switch to root ("su"). Then do "fstrim -v /system", "fstrim -v /cache", and "fstrim -v /data".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Or run LagFix from Play Store if you're lazy. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Yeah, it does the exact same thing. LagFix(the paid version) can be set to run at start-up(or on a schedule IIRC). You could always do an init.d script for free.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joemommasfat:
As far as google wallet goes, I have been flashing this with the nightlies for a few weeks, and it works. I just add it to my cyandelta post-install zips.

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

No build.prop modifications are necessary, just flash the zip and go.

I've had issues initializing the tap-and-pay on occasion. I got error 11 and error 13 a couple times. When this happened I would clear the app data, delvik cache, re-flash the rom and re-flash the wallet zip. One of those (or a combination of those) things would always fix it for me.

Some people will say you should reset wallet before flashing a new rom. Go to change account, and it will clear everything out. Cancel before setting a new account. When I have done this before updating nightlies, I never had any errors.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yes, free is good. =)

I'm sure some people will find this information useful.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
I've been out of the loop for a bit. Are there any glaring issues with the 4.3 nightlies that would prevent someone on stable 10.1.3 from wanting to upgrade?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Not that I have found. Reached a pretty solid state, enough to warrant me to upgrade. I feel like it's a bit smoother in some places yet a bit hiccup-y when pulling the drawer. Definitely nothing too terrible though, since I got used to it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
I just recently switched from 10.1.3. to the 10/06 nightly, and it's been pretty smooth sailing for me so far. I say you take the leap of faith. :angel:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
Groovy. You seem to know your ****, so I'm apt to give it a go. With, of course, a nandroid backup.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I know some. But I used to flash nightly after nightly until I got tired of one nightly being stable and the next one being pure broken crap, so now I thread carefully and usually nandroid and test slowly until CM gets to a point that I consider usable.

Some people will accept broken functions (even very primary stuff in my opinion) but I usually don't. Still a bit "meh" about front facing cam being broken in third party apps though.

I despise how big CM has got and how it's managed sometimes, can't do **** about that though. It used to be good, now it's all blown out of proportion and there's always small things not working on every dang phone with a CM build available. Still love the rom and the outstanding community that uses it. :S
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Has the 10.1 camera regained all the features of the 10.2 camera such as burst, saving to the SD card, etc.?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I imagine you mean the contrary? No, no burst or save to SD available in the 10.2 camera. Both are functions I don't use though, so I won't personally miss them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jblparisi:
Working fine for me here, unless I'm missing something.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You have burst and save to SD on cm 10.2 camera? I'm on October 6th nightly and it's not there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jblparisi:
Yup, checked SD card and multiple shots are in there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
yeah. i feel that. i've actually been debating going back to touchwiz once they drop 4.3, just because we know everything works solid. yeah, it's hideous, but stability and functionality is more important in the end. i don't use the front facing camera really, so that's not a big deal. my battery, however, is always so random. some days it's great, some days it sucks. it doesn't make any sense as i use it pretty much exactly the same every single day. we'll see how the 10.2 stable is once it's released before i make a decision though.