yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] skytbest:
Well I have hello set to my default SMS appication, and SMS isn't turned on in hangouts. Now that I look at it more this notification looks more like it is coming from the system rather than any specific app, when I clicked on it is asked me what app I wanted to open with, I selected to always do HelloSMS but it still didn't go away!
[Verizon Samsung Galaxy S III] Hybridnoob:
Try disabling the stock messaging app. That's what I did and it worked.
[Verizon Samsung Galaxy S III] Leraeniesh:
Thinking about switching from 10.1 to 11 on my sister's S3.

Any issues with current builds? M3?
[Verizon Samsung Galaxy S III] chowner:
Was shaky for a bit, but M3 forward seem solid so far.
[Verizon Samsung Galaxy S III] skytbest:
Worked. Thank you!
[Verizon Samsung Galaxy S III] Defragger51:
Best Battery life ever on 2/11 build. After installing 2/11 and fully charging I have been running with bluetooth on and not connected since about 1:30 noon yesterday. Its 9:55 am and I still have 62% battery left. I see something in the change log for tomorrows nightly that sounds like there going to change or take away a wake lock ,So does this mean the excellent battery life is going away. About to try today's 02/12 build.will be putting the 02/11 build in the To Keep Folder...... I ask again anyone with an idea how to get google wallet fully working on cm11 ? I can do everything but actually pay with it.
[Verizon Samsung Galaxy S III] skytbest:
Notifications that are expandable are not displaying correctly in their 'compressed' form. For instance, if I have an email the Gmail notification can display a small preview of that email in a larger sized notification if it is the only notification in the drawer (or if you pull it down), but will show the normal smaller notification if there are many others. Right now it is not showing that smaller version correctly, it is just a scrunched up version of the larger one, which shouldn't be the case.

Does anyone know what I'm talking about?
[Verizon Samsung Galaxy S III] Zacharybinx34:
Any idea when Trebuchet will let us change the grid size?
[Verizon Samsung Galaxy S III] skytbest:
Can you undervolt on the stock kernel? And also lower the minimum clock speed?

Also, I just flashed KToonz but I think I might want to go back to stock, I've heard there are some changes that make it the preferred kernel (is this true?). How do I got back to the stock kernel? Just dirty flash a nightly (even if its the same version I'm currently on)?
[Verizon Samsung Galaxy S III] dmginc:
Why not just use Nova?
[Verizon Samsung Galaxy S III] bmeek:
are CM development plans secret, or just vague?

Due to the nature of CM development (mostly volunteer devs, etc.), your question is hard to answer (iow, I wish I knew).

The answer is "probably someday". The most I've seen from the CM folks on the return of Trebuchet in CM11 is in ciwrl's latest blog post.

---------- Post added at 11:26 AM ---------- Previous post was at 11:20 AM ----------

Yes - it seems that GPS / Location services must be toggled off & back on prior to reliable operation. Makes it tedious to get directions quickly...
[Verizon Samsung Galaxy S III] Omega Ra:
Not sure if it is the nightly's fault. But all of a sudden today my Battery TANKED real fast. I updated to the 2/12 this morning and everything seemed ok, then I just looked at my phone and the battery plummeted.

edit: I just looked at the battery history and it looks like it may have been the update. it started dropping fast right after, so far as I Can tell. 2/12 may not be good.
[Verizon Samsung Galaxy S III] merdely:
After 6 hours, I'm at 85%. That's good for me, I think. I haven't made any phone calls, though I was connected to Bluetooth for my 25 minute commute and then another 15 minutes of driving later.

Overall, I'm really happy with 2/12.
[Verizon Samsung Galaxy S III] Omega Ra:
Could it possibly be because I just did the update through the settings instead of doing a clean install? I did a clean install of 2/11 yesterday, and I have a nandroid of that, but today I just ran the update and wiped the dalvik and cache.
[Verizon Samsung Galaxy S III] merdely:
I haven't done a clean install since I first installed CM11. Whenever I update, I boot to recovery, back up, clear cache, clear dalvik, install new CM, boot, wait for it to finish booting, power down, and then power up.
[Verizon Samsung Galaxy S III] Omega Ra:
Hmm. I don't download it separately. I just download it through the about phone>cyanogenmod updates menu, and it automatically reboots me to recovery
[Verizon Samsung Galaxy S III] merdely:
I download through CM Updates under About, but I reboot manually into recovery to back up and clear caches.
[Verizon Samsung Galaxy S III] Omega Ra:
Ah, gotcha. Not sure what is happening then...
[Verizon Samsung Galaxy S III] ned4spd8874:
Can someone please enlighten me on how the Privacy Guard is supposed to stop programs for auto starting? I just found out about this feature today, but can't seem to get it working. For example, Pandora starts, but I don't want it to. I enabled privacy guard for it and set the switch to off for auto start; but when I reboot, it's running right away again!
[Verizon Samsung Galaxy S III] chowner:
When flashing through the updater are caches cleared?
[Verizon Samsung Galaxy S III] bmeek:
The 2/12 build seems fine to me (it's holding a charge reasonably well and there are no persistent wake-locks or anything).

Was the phone unusually warm when you noticed your battery had "TANKED"?

FWIW, I also update using CMUpdater and don't generally see any issues (the script used does wipe cache, etc.). Perhaps it's superstition on my part, but I like to power down and do a battery-pull when I see something like you've described. I would then let the battery drain down and recharge it...

BTW, I've occasionally seen my phone report a relatively-full charge one moment and a much lower percentage a moment later. I'm not sure what causes this, but I tend to suspect a faulty reading over an actual rapid discharge. Take a look at BetterBatteryStats from the Play Store to see what the culprit is (if there actually is a culprit).
[Verizon Samsung Galaxy S III] merdely:
I don't know. That's why I do the manual part.
[Verizon Samsung Galaxy S III] cheekoo:
yes, thats how I have been going back to stock ROM, if needed
[Verizon Samsung Galaxy S III] ChiefIlliniwek5:
If I understand that feature correctly, it keeps apps from accessing your personal info on your phone. I don't think it has anything to do with preventing apps from running.
[Verizon Samsung Galaxy S III] ned4spd8874:
But there is a switch to toggle "Auto start".
[Verizon Samsung Galaxy S III] npro1464:
How is the M/Snapshot build? I was considering flashing to it. I typically only to stable builds, but I'm itching for some Kitkat!
[Verizon Samsung Galaxy S III] lakingslayer:
I clean flashed the 2/11 build and the battery lifewasn't very good. Worse than usual from a clean flash. I used cm updater to update to 2/12 and the battery life is pretty good now.
[Verizon Samsung Galaxy S III] ecooce:
Just wanted to say thank you to all the devs working on CM11 for the S3!

Follow me on...

Youtube http://bit.ly/To93d6

Google+ http://bit.ly/RqyYPa

Facebook http://on.fb.me/RFIADb

Twitter [MENTION=2601927]jason_[/MENTION]Feriani http://bit.ly/Qa3Yyu
[Verizon Samsung Galaxy S III] brockkk:
2/13 build has the best battery life I have ever had. Wow. And the pulse led is soooo much better. The stock flicker would piss me off. Lol
[Verizon Samsung Galaxy S III] im_on_fire:
2/11 has terrible battery life for me too. Lost 50% battery overnight (phone died) and that's a 7000mah zero lemon battery
[Verizon Samsung Galaxy S III] RedRumy3:
Camera issue fix with latest nightly, I can switch to video and back to camera and it doesn't crash.
[Verizon Samsung Galaxy S III] lakingslayer:
On the 2/12 build my camera froze when I tried to change the image size from 8MP to 3MP. I rebooted and then had no freezing issues even switching between camera->video->panoramic->camera. 2/13 is working fine too. Very little hesitation when going from portrait mode to landscape and back.

I noticed a weird thing this morning that I've not noticed before. I saw some BT additions to the 2/13 build so I thought I'd try my Sirius XM in my car again. I have not been able to get audio to come out in the car. I had the phone still in vibe mode and all other volumes shut down from when I went to bed last night. When I tuned on the Sirius to play in the car I turned the volume up which showed the BT volume going up. Normal correct? Well when got in to work I noticed I was still in vibe mode so I turned up the volume and also touched the settings to the right of the volume level display to turn up my alarm and other volumes. I noticed the BT volume was still turned all the way down. Weird. Anyone else see this?

All-in-all this rom is 99% complete as far as I can see for what I use it for. Extremely nice! Thanks for the hard work CM developers.:good:
[Verizon Samsung Galaxy S III] jabhall:
I have been using the M3 snapshot for a couple days now and it has been solid for me. BT works, battery is fine, no reboots. Although I haven't tried crashing the camera by switching to video and back (not really an issue for me), this appears to be my new DD.
[Verizon Samsung Galaxy S III] 250 or Point 65:
What camera version do all of you guys have? I think this may be the issue.

I still can't fine "continuous focus" as an option in mine.
[Verizon Samsung Galaxy S III] Hybridnoob:
They work fine here.
[Verizon Samsung Galaxy S III] merdely:
With 02/13, Bluetooth did not autoconnect. I'll try again later. Other than that, it seems fine. Battery seems good.

---------- Post added at 12:34 PM ---------- Previous post was at 12:14 PM ----------

For what it's worth, I just flashed this baseband update to I535VRUCML1 and I already see better signal. I had been a little weary of doing this until now, but I got sick of bad signal in the lower level of my house.

I just flashed it as I would a ROM using recovery.
[Verizon Samsung Galaxy S III] Hellven:
I was sort of getting the same thing on 2/13. They say that they are sending, but nothing happens for like a minuet, then they send in spurts. A reboot and everything is looking good.
[Verizon Samsung Galaxy S III] Casper34:
Can anyone else confirm this? Right now this is the only stopper from me installing 2/13. I do everything by text.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] merdely:
I haven't had any text problems with 02/13. Or any other nightly, for that matter.
[Verizon Samsung Galaxy S III] Casper34:
I haven't either, but this is the first people have posted about texting problems. So, before I flash, I just want to make sure its just a random issue.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] bmeek:
No problem here - texts are working fine on the 2/13 build as always.

[MENTION=4803536]rockbottom8[/MENTION] - what is your default messaging app?

[MENTION=2182697]merdely[/MENTION] - Bluetooth is auto-connecting fine for me... an immediate connection when I turn my Plantronics M155.
[Verizon Samsung Galaxy S III] blueblur:
I'm noticing if my phone is paired to my Bluetooth headset and someone tries to call me, the phone does not have an audible ring.

In the past, the phone would ring as well as in the earpiece.

Am I missing a setting or did anyone else notice this when paired with a Bluetooth headset?
[Verizon Samsung Galaxy S III] merdely:
Went back out to my car and BT is working great! And batter seems exceptional.
[Verizon Samsung Galaxy S III] Defragger51:
Been running 2/13 build of a full charge since 10 am with Bluetooth and WiFi on and getting excellent battery life 86% battery left as of 4:30 pm . Bluetooth connects every time I turn my headset on, Txt messages send right away . have not received a call with headset on so can not speak on the ring issue .
[Verizon Samsung Galaxy S III] Defragger51:
Add On.Received a call with Bluetooth headset connected and both the phone and the headset rang . Again Awesome battery life after a 55 min phone call I am left with 74% battery
[Verizon Samsung Galaxy S III] bmeek:
Yes. If your phone is connected to your Bluetooth headset with the device option for "Media audio" selected, you won't hear the phone ringtone (or notification ringtone) unless the headset is in your ear or is turned off.

When you say "In the past, the phone would ring as well as in the earpiece", I suspect you're remembering the behavior of a TouchWiz ROM.

This has been the behavior of CM10 and CM11 for as long as I can remember. I post about it from time to time but no one seems to care... It would be great if there were an option to ring-out-loud on the handset when a Bluetooth device is connected for media playback.

---------- Post added at 03:07 PM ---------- Previous post was at 03:00 PM ----------

Unless you're saying you found an Add-on to enable this (and I've never heard of such an add-on), I suspect your headset doesn't support A2DP.

If you navigate to Settings --> Bluetooth --> Device --> Settings, do you see an option for "Media audio"? If so, do you have it checked/selected?
[Verizon Samsung Galaxy S III] Defragger51:
Sorry for the misunderstanding, No idea how I confused you on that one . What I was trying to do was add it on to my last comment . My Bluetooth is working perfectly.
[Verizon Samsung Galaxy S III] bmeek:
No worries and glad to hear it's working perfectly for you, but please answer the question about whether or not your headset is paired to use "Media audio" (in addition to "Phone audio").
[Verizon Samsung Galaxy S III] Defragger51:
My headset/ear piece connects as phone only. My nexus 7 and my Bluetooth speaker connect as a media device. hope that helps
[Verizon Samsung Galaxy S III] bmeek:
Yeah. Thanks for the confirmation. You'll find that when your phone is connected to a Bluetooth device with media audio enabled, your handset speaker won't sound a ringtone on incoming calls.

I can understand when this may be desirable, but for most circumstances I consider this a bug or a design flaw.
[Verizon Samsung Galaxy S III] Shakes The AssClown:
Clean flashed 2/13...working great...a few things I noticed. Lock screen shows roaming indicator off instead of Verizon Wireless. Calendar widget doesn't show anything. Location in quick panel doesn't toggle..can't tell if it's on or off.

All have cleared after a reboot.
[Verizon Samsung Galaxy S III] blueblur:
You nailed it. Interestingly enough, I was using cm 11 but it was a build from November 25 and it was also a kang. I can't recall which one now but I do know that I was using it as a daily driver for the longest until I got tired of camera reboots.

I have always used a Motorola S11 flex-hd which handles media audio and it used to ring. Glad to know I'm not missing a setting and apparently this is per design.
[Verizon Samsung Galaxy S III] Casper34:
I'm not getting hangout notifications unless I am in hangouts. Running the 2/13 build. Anyone else having this happen??

Default SMS app is hangouts

Volumes are up

No icon unless not in the same conversation

No tone unless in hangouts

No clue.... frustrating....

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] merdely:
I got an SMS earlier and got both sound and visual notification. I use Hangouts for SMS.

Sent from my Verizon GS3 running CM11
[Verizon Samsung Galaxy S III] Casper34:
Ya me too, I have used it since switching to CM11, but I never had this. Its weird. It started after I updated from 8 to 13. I have rebooted, cleared the cache, not the data.... that's next.

I have had no issues since switching to cm11, this is the first. :confused:

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] Omega Ra:
Since recharging it and taking the screen off AUTO brightness, I haven't had any more issues.

---------- Post added at 09:00 AM ---------- Previous post was at 08:56 AM ----------

Still having some off BT issues. Not sure if it is the ROM or the app for my watch. It seems like the background task for the app isn't running. In the app I have it set to sync every hour, but it doesn't seem to do it. If the app isn't running and I try to manually sync from the watch it can't connect, but if I open the app and hit sync from the watch it can. Seems like the background task...
[Verizon Samsung Galaxy S III] bmeek:
Wow. A *long* list of changes to the d2 kernel in today's nightly (2/14).

I've been running it for a while now without any issues, although I see that Wi-Fi has been on 100% even though I have it set to never remain on during sleep. I'll toggle Wi-Fi and do a battery pull and see if that behavior persists...
[Verizon Samsung Galaxy S III] PerCompLLC:
Not seeing this long list of d2 kernel changes... I see a grand total of one. http://review.cyanogenmod.org/#/c/59507/ I do see a bunch of samsung_jf kernel changes though.

Am I missing something?
[Verizon Samsung Galaxy S III] Kaaru:
I just got an update from cyanogen mod with something like screen shot mod something

.what is that update???
[Verizon Samsung Galaxy S III] bmeek:
I just look at the nightly change logs via cmupdater (tap the description/filename).

I confirm that I'm now seeing WiFi-related wake locks and WiFi remaining on 100% of the time, even when WiFi is turned off, if I leave the advanced WiFi option to have "Scanning always available"checked.

Edit: I'm retracting my WiFi gripe... WiFi does seem to settle down to sleep on the 2/14 build. BetterBatteryStats shows WiFi to be "running" 100% of the time, but only "on" while the phone is awake (at least when I have the "Keep WiFi on during sleep" option set to "Never").

IOW, WiFi seems to be working well enough. Sorry for what appears to have been a false alarm...
[Verizon Samsung Galaxy S III] PerCompLLC:
Interesting how that the change log doesn't seem to correlate with the mergelog at http://review.cyanogenmod.org/. Hmmmm....
[Verizon Samsung Galaxy S III] Defragger51:
I am on 02/13 and am not having any wake lock problems and excelent battery life. I had my Bluetooth and Wifi on all day yesterday and last night. had 60% battery at 12:30 am and when I woke up at 7:45 am with Bluetooth and Wifi still on I had 45% battery left
[Verizon Samsung Galaxy S III] bmeek:
I wasn't referring to the 2/13 build. Just the 2/14 build.
[Verizon Samsung Galaxy S III] rhcreed:
Are we in dd range yet? On the last 10.2, runs perfect but would love to get up to 4.4.2... Have the Bluetooth/WiFi/camera/battery/reboots issues been resolved (seems like not everyone was having problems).

Hoping to not loose stability for the new version... Thanks!
[Verizon Samsung Galaxy S III] Hybridnoob:
You can always flash it and keep a nandroid to revert back to if you're unhappy. I have no issues and have been using this as a DD since December (even through the rough patches). I'm running 2/13 and am very happy with it. You can try M3 if you want to stick with an M build.
[Verizon Samsung Galaxy S III] Prack:
2/13 is the best build, runs better than any of the 10.2 ROM's did IMO. I can't find anything wrong with it either.
[Verizon Samsung Galaxy S III] xneuromancer:
Build: 20140214-Nightly

anybody having gps lock issues? i can get satellites in "view", but I never get a lock and have 0 accuracy according to gps test.

i've tried multiple gps.conf's, no luck.
[Verizon Samsung Galaxy S III] rhcreed:
Not getting WiFi, any trick? Also, what firmware do you recommend, flashed the one from the op..

It's shutting off after a few minutes and won't reconnect. Cycle it on/off and it won't come back.

Any suggestions? Read back a few pages and nothing...
[Verizon Samsung Galaxy S III] ChuckFarley:
I'm back to cyanogen after a long tw hiatus, and goddamn is it good! Smooth and better looking than ever! You're doing the Lord's work, Invisiblek.
[Verizon Samsung Galaxy S III] skrusrnmz:
The camera problems seem to be fixed. They were a deal-breaker for me before which kept me on 10.2.1 (in my opinion still the most stable CM build I've used).

Don't know how long you've been away but you can now natively save to external SD. I could deal with the SD thing before, my biggest problem was the crashing. I have too many kids running around to not have a good camera immediately available. The camera no longer crashes when you switch back and forth between video and camera.

M3 had the camera crash so don't use it.

Cant speak to the other issues yet but it seems really smooth so far.
[Verizon Samsung Galaxy S III] ctheory83:
Having loads of issues, and i'm not sure why. Well, I have an idea, honestly.

When half asleep this morning, I tried flashing 4.4 over my old nightly (whoops) without formatting or doing anything. Tried then to format everything, download a nightly, grabbed both KK gapps, and tried to flash again - this time I get Status 7. Wiped, tried a different 4.4 nightly, got past the Status 7, then gapps wouldn't install. Started all over, same sequence, Status 7 again.

Can someone confirm which gapps I install with this build, and has anyone run into this?
[Verizon Samsung Galaxy S III] briaking:
Update CWM to flash CM 11

Make sure you are on the newest CWM. I had the same issue. Reflash CM 10.2.0 stable and download the clockworkmod app to flash the newest CWM or find the zip file and flash that manually.

I had the same issue because I was on an older CWM.
[Verizon Samsung Galaxy S III] ctheory83:
Good call, going to try this now. Thanks brother.
[Verizon Samsung Galaxy S III] Hybridnoob:
In times past, I have been able to dirty flash between different versions of CM (e.g 10.1 -> 10.2) as described here (http://forum.cyanogenmod.com/topic/74526-how-do-i-update-cyanogenmod/). I'm currently on 10.2 stable (latest radios and CWM recovery), but would like to test CM11. I attempted to manually dirty flash 12/7 and 12/8 (with 11/19 4.4 gapps) by only wiping cache and dalvik, but both builds bootlooped after going through the Android is upgrading screen.

I'll likely eventually clean flash CM11 M1 (once released), but would like to know why I'm unable to dirty flash CM11 and if anyone has successfully done it. Thanks!
[Verizon Samsung Galaxy S III] RedRumy3:
So only way I can get builds to boot is to do a fresh install of them, basically I installed 12/7 build on fresh install and tried to update to 12/8 or 12/9 it wont boot, my phone gets stuck on boot screen until I pull battery but if I do a fresh install it will work. I am just going to keep 12/7 build for now since I don't have any problems. Will probably wait until end of month to flash another build with fresh install.
[Verizon Samsung Galaxy S III] Shakes The AssClown:
I have location services on but I notice on the weather apps that my location is totally off while in Google Map it seems pretty accurate. Not sure why that would be.
[Verizon Samsung Galaxy S III] jehelmer:
I tried the toggle in the notification drawer as well as in settings.

I have since reverted to a backup of 12/8. I will probably try again tonight with 12/9
[Verizon Samsung Galaxy S III] jlokos:
lean kernel. What nightly are you on? It was working on the 12/8 build.
[Verizon Samsung Galaxy S III] caifan:
My WiFi has been kinda wonky also. I'm on 12/9 and this is the first time (have been on mastamoons and then official) that I've had any kind of WiFi-LTE handoff issue. When I got to work, my home WiFi was still "connected" and the LTE handoff did not occur until I toggled WiFi.
[Verizon Samsung Galaxy S III] sanjsrik:
holy crap, that was the most convoluted thing I've done on Android.

thanks for the instructions. I would NEVER have found this on my own.
[Verizon Samsung Galaxy S III] BlaJod:
Anybody having success with Google Wallet and Tap and Pay? Wallet shows up in Tap and Pay like it's supposed to and card is showing in wallet app, but at terminal both times I've tried, the phone and terminal doesn't make any type of confirmation, it doesnt beep or make any sound when I get close to pay. Turned NFC on and off just to be sure and still no go, I've made sure NFC isn't broke by beaming stuff to a Note 3 so its not NFC I wouldn't think. Anybody have any input.