yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Hellven:
I have used MyFitnessPal with CM11 and I am thinking it is the app. Other barcode scanning apps work with the nightly (01-01) I am on (shopsavy, amazon).

I also, just checked it on my wife's Samsung running stock 4.3 and it works as it should.
[Verizon Samsung Galaxy S III] merdely:
Yeah. I figure it's a combination of updates to CM11 and updates to MyFitnessPal that don't jive.

Yep. That kind of (but not totally) agrees with what I said above.

---------- Post added at 06:25 PM ---------- Previous post was at 06:24 PM ----------

Not only that, but Google Search is chewing up my battery like mad. I'm going back to 01/01.

Edit: adjust date to match what I restored to.
[Verizon Samsung Galaxy S III] dvaderx:
My wife uses that with cm11 and said the bc scanner works fine for her
[Verizon Samsung Galaxy S III] merdely:
Is she using the latest and greatest MFP?
[Verizon Samsung Galaxy S III] dvaderx:
Yes but I'll verify with her phone when she gets home. But i txt and asked about the bcs. She said it works fine
[Verizon Samsung Galaxy S III] bdr9:
Does Skype work for anyone? When I enter a call, the app crashes for me on the 1/3 nightly.
[Verizon Samsung Galaxy S III] ecooce:
Anyone know when long pressing the Home button on lockscreen to turn on torch will be built back into CM11 for the SGS3? Really miss that ease of use...
[Verizon Samsung Galaxy S III] annoyingduck:
I know, it's killing me! Gravity box has a mod that works well, but the vibration does not work when enabling. You also can't use art with it...
[Verizon Samsung Galaxy S III] ecooce:
Well the last time I tried ART everything crashed so I wont be testing that again anytime soon. I have been doing dirty flashes, well 2 update zips, one for just the newest files - all my modded files (build.prop for NAV buttons, Sprint SGS3 lines for Wallet, and keylayouts, plus sounds, and some others), then one update.zip for the newest kernel. I used to be good at writing update scripts, but 2 zips work fine for me. So thats how I have been updating for a month now ;)
[Verizon Samsung Galaxy S III] npro1464:
Im running the stable CM 10.2, and am experiencing random reboots. Anyone else experience this? Is there a kernel I can flash to make it better? Is the Snapshot CM 11 any better? Thanks.
[Verizon Samsung Galaxy S III] ecooce:
Random reboots can be caused by many many things, and happens to everyone at random, I even got them on stock (every device Ive owned), so I would say, I dont know what to say :)
[Verizon Samsung Galaxy S III] lou1210:
I have some questions please.

First, I had my phone replaced under warranty. I updated to 4.3 and would like to root my phone. I have been reading quite a bit about the warranty flag and the safe root file but some questions remain. But no search keywords have shown me answers to these questions.

1. Do you still need to install ez unlock to unlock the bootloader?

2. Will triangle away work like it did before in case I need to send this phone back under warranty?

3. Is installing cwm recovery the same - using ez recovery so I can flash an old ROM?

I think once I can get these questions answered I can get going on rooting my replacement phone. Thank you all in advance. Sorry again to get off topic.
[Verizon Samsung Galaxy S III] abtxpress:
Anyone try the m2 snapshot yet? I'm downloading now.

---------- Post added at 12:21 AM ---------- Previous post was at 12:17 AM ----------

As far as I know if your device has the 4.3 firmware you'll never have root because insecure bootloader will brick your device because Samsung and Verizon put some kind of software checker in the new firmware.
[Verizon Samsung Galaxy S III] lou1210:
Here is a link that says it can be done: http://honai-android.blogspot.com/2013/12/how-to-root-galaxy-s3-verizon-sch-i535.html?m=1
[Verizon Samsung Galaxy S III] titanshadow:
You can root via saferoot, I'm running it right now. You cannot load CM because you cannot unlock the bootloader. With the bootloader locked you can flash a custom recovery but you cannot use it, booting into it is impossible. The new bootloader does not allow you to downgrade or alter the bootloader at all.

In short, you can root, but you cannot downgrade to an unlocked bootloader so you can't load a custom firmware or custom recovery. I haven't tried triangle away yet myself but I would be concerned about messing with it as there are sites that say doing the wrong thing hard bricks your phone.

I tried to flash everything I could find but all I could do on mine was to brick it and ended up having to just flash stock as it came from Verizon.
[Verizon Samsung Galaxy S III] lou1210:
Well, it has been great chatting with everyone and trying new Roms while I could. Unfortunately I got the 4.3 upgrade and can no longer root. I wanted to make sure to thank everyone for the great and constant support. And to the CM developers, of course, for creating the great ROM they did. I liked the ability to have the control I previously had and the great variety. I will hope I can root my next phone, whatever it will be, but it certainly won't be another Samsung phone. Best wishes to everyone and happy rooting and ROM flashing.
[Verizon Samsung Galaxy S III] Bamdroid:
This M2 is rather snappy. Haven't tested everything but there's definitely a noticeable difference IMO.
[Verizon Samsung Galaxy S III] cheekoo:
whats M2?
[Verizon Samsung Galaxy S III] Gibscreen:
Can't get usb otg to work. Is there a trick?
[Verizon Samsung Galaxy S III] Bamdroid:
I'm assuming a semi stable version but it says SNAPSHOT on the build. It's running pretty smooth so far.

http://www.cyanogenmod.org/blog/cyanogenmod-11-0-m2-release

You won't find it in the CM updater but they have it for d2vzw from the downloads link on their site. I dirty flashed on top of 1/1 nightly and I haven't bumped into any issues.

(Not sure if this helps, but I also updated CWM through ROM Manager yesterday).
[Verizon Samsung Galaxy S III] Bamdroid:
Yeah, it's more stable than a nightly but not as stable as an RC. (Milestone).
[Verizon Samsung Galaxy S III] abtxpress:
I dirty flashed the m2. I had problems with Google apps not connecting and fc'ing.

Fixed by flashing kk gapps... And then had to delete almost all gapps and reinstall any that fc'ed.
[Verizon Samsung Galaxy S III] dvaderx:
Hangouts camera is upside down again with M2
[Verizon Samsung Galaxy S III] Defragger51:
Does Bluetooth work Correctly Yet, I keep reading everyday one thing or another is now broken or broken again but no mention if Bluetooth is working correctly again yet. I went back to 4.3 because working Bluetooth is more important to me than a working camera. I need an ear piece while driving ,don't need a camera while driving.
[Verizon Samsung Galaxy S III] dvaderx:
No but I'm sure someone will post when it does
[Verizon Samsung Galaxy S III] Div033:
Unfortunately the 10.2 "stable" version isn't exactly stable. I too experienced frequent random reboots on it with the stock kernel.

My suggestion is to roll back to 10.1. That's the most stable version of CM we have to date and might end up being the most stable we'll ever get on this phone. CM11 isn't any better in my experience and still has a long way to go to reach the level of 10.1's stability.

It's important to note that I still experienced random reboots on 10.1, but only after 200-300 hours of uptime vs. the 10-20 hours on 10.2 and 11.
[Verizon Samsung Galaxy S III] cheekoo:
Thanks!
[Verizon Samsung Galaxy S III] ecooce:
I know this isnt the place to ask, but anyone know how to enable call forwarding, Ive never done this on an android (or any phone) before?
[Verizon Samsung Galaxy S III] dpeeps74:
Tried this? http://m-support.verizonwireless.com/mobl/features.kb_17268.tp_2.html
[Verizon Samsung Galaxy S III] ecooce:
THANKS!!!

---------- Post added at 05:04 PM ---------- Previous post was at 04:28 PM ----------

Ok, now I have GrooveIP on my OG Epic4g getting calls from my Verizon S3 #, is there a way to get sms forwarded?
[Verizon Samsung Galaxy S III] merdely:
Seems like the problem with Voice Search and battery drain that I saw in 20140103 is gone with M2.
[Verizon Samsung Galaxy S III] metalcated:
Since I started flashing this ROM, MMS.apk keeps not being the default SMS app and isn't even being installed when I flash nightlies. It doesn't even exist in priv-app. Any idea why this happens flash after flash? I have to manually copy MMS.apk to priv-app every time. And if I forget... I go the whole time with SMS messages getting lost.

Please suggest a fix minus a clean flash which I'll do but I'd prefer to fix it.
[Verizon Samsung Galaxy S III] annoyingduck:
Some gapps packages remove the AOSP MMS and replace it with hangouts. The full PA gapps are one of these packages (I recommend the minimal PA gapps, it doesn't remove it).

Just use a root file manager and extract the messaging apk from system/app in the cm zip file you flashed and paste it in system/app (not private/app), change permissions to rw/r/r, and reboot. Then change the default messaging in more under settings.
[Verizon Samsung Galaxy S III] droiddudex2:
Anyone have problems flashing the newest snapshot? I tried re-installing it and it still fails mid flash... I was clean flashing from the CM10.2 stable if that helps anyone
[Verizon Samsung Galaxy S III] Hybridnoob:
What process are you doing? What recovery (including version) are you using?
[Verizon Samsung Galaxy S III] eppo12-:
Every once in a while I have been having issues with the camera, thought it was random until recently.

sometimes when taking pictures the screen would go black and phone will be unresponsive. I have to pull the battery to get it working again.

I noticed that when I was taking pics a this one family members house, it would happen. I thought it might have been data connection related( I get crap signal while i'm there).

So today, while at a friends house, I'm having the same issue... once again, crap signal.

So this time I put it into airplane mode, and I'm able to take pictures again.

I also had tried with focal, and had no issues with it, regardless of airplane mode on/off.

Has anyone else noticed this?

I'm pretty sure this has been an issue from CM10-CM11.
[Verizon Samsung Galaxy S III] dmginc:
In the future, just boot into recovery then wipe system and cache. Then just reflash the ROM and gapps and you'll be good to go.
[Verizon Samsung Galaxy S III] prafullsabat:
Hey Guys.. I am using this ROM for Reliance CDMA(India) but i am not able to get DATA enabled with This ROM. Any suggestion on how to enable data for alt carriers ? will like to thanks in advance
[Verizon Samsung Galaxy S III] Lorenzo VonMatterhorn:
I am getting Netflix phone reboots on M2 . ... won't play at all .

Edit: seems to only be upon first use ? Works great now.
[Verizon Samsung Galaxy S III] dvaderx:
hangouts camera fixed (again) on 1/5 :)
[Verizon Samsung Galaxy S III] abtxpress:
I always wipe cache and delvak. I dirty flashed from 10.2. I've never had this happen.
[Verizon Samsung Galaxy S III] metalcated:
I've tried that before and I did try it again. As soon as you flash an update its goes poof with the script that cleans up /system. Short of installing the apk as a User APP, I am not too sure what to do. I suppose I could try another gapps package where MMS.apk is the default SMS package. I will post results if it comes to that otherwise I leave the question out to you folks. ;)

Thanks
[Verizon Samsung Galaxy S III] GPS3:
Is there a way to get the Emoji support back into the Messaging app?

I am using cm-11-20140104-SNAPSHOT-M2-d2vzw.zip and 20131208 gapps.

CM 10.2 Stable had stock Emoji support.

Thanks.
[Verizon Samsung Galaxy S III] metalcated:
Also as I am checking for updated GAPPS packages. I see the 1208 and 1119 both listed on invisiblek's sites and cyanogenmod's site the same. However on CM's site the 1208 package is showing not to use with ART. Last I knew I enabled ART but now when I go looking under Developer Options, I don't see the toggle for ART/Dalvik anymore?? Did that get removed?

Which version of GAPPS is everyone using?
[Verizon Samsung Galaxy S III] WarER4X:
I was running 12/28 with ART runtime enabled (and PA ART-compatible gapps, of course) with not problems. Then, I jumped to the 1/03 build and everything worked except Google Now Voice Search kept intermittently losing the ability to connect to Google. I went back to 12/28 and everything all is working properly again. Did anyone else see that issue? Also, is anyone seeing it on the latest builds, including M2?
[Verizon Samsung Galaxy S III] GPS3:
I am running CM11 M2 and 20131119 gapps with ART enabled. Both the ROM and gapps were pulled from CM's website.
[Verizon Samsung Galaxy S III] WarER4X:
IIRC, I am using the 12/08 pa gapps. I may try out the CM11 M2, but it is hard to leave the 12/28 nightly because everything has been working so well and my battery life has been terrific on that build. I'm a bit spooked to switch at the moment because, when I went to go back from the 1/03 build to the 12/28, I simply tried to restore the system backup that I had created just prior to installing 1/03 and the restore failed (I use TWRP). I'm not sure why, except that the backup was created with TWRP's "Active Backup" (that runs without restarting to Recovery) and tried to restore it from TWRP in Recovery mode. I don't know if that matters, but I won't be trying that again. From now on, all of my backups will be run from Recovery, I think.

-SR-
[Verizon Samsung Galaxy S III] NedDasty:
Any idea where going on here? haven't even opened the phone app today.
[Verizon Samsung Galaxy S III] xgujuplaya:
any idea when the front facing camera issue for apps like snapchat will be fixed?
[Verizon Samsung Galaxy S III] AndyMan386:
seems like they dont really care about this one, no matter how often people post about it
[Verizon Samsung Galaxy S III] podspi:
I don't think it is a matter of not caring, I think there is a lot to do to get CM11 up and running smoothly, and the camera's are low on the list compared to other things that have to get done.
[Verizon Samsung Galaxy S III] titanshadow:
Don't assume that the developers don't care because the feature you want isn't up and running in your time table. Debugging hardware drivers and such is hard, especially since most don't have professional debugging tools like a JTAG or other system to do break points and instruction step through. That makes knowing what is really going on inside a device with the code, it's variables, etc.. Very difficult and a matter of educated guess, trial, and error.
[Verizon Samsung Galaxy S III] lakingslayer:
With that said I think these developers do an incredible job with the tools at their disposal. Most are not full time Android developers and do this as a hobby for free. If they spend all their time answering everyone's posts on these threads (there are many forums covering the same stuff) then they'd never get anything worthwhile done. Nobody seems to have patience anymore.
[Verizon Samsung Galaxy S III] Div033:
It also has to do with what they have to work with... Our current camera blobs are highly incompatible with 4.4 so in order to get things functioning properly it takes a lot of work and hackery. I'd wager the 'camera issue' is regarded as a big issue on their list... Big not because of popularity, but because of how difficult it is to tackle.
[Verizon Samsung Galaxy S III] Skyrocketing:
I've been experiencing issues with using a bad code scanner, I'm assuming that's bundled with the other camera issues?
[Verizon Samsung Galaxy S III] AlphaXray:
Does anyone else experience an issue where the alarms they have set will not ring after updating their device. I update using CM updater. Sometimes this is an issue and sometimes it's not, but i've been becoming paranoid that I won't be able to wake up for work so I set a test alarm to see. The phone still vibrates but the ringer does not work until after I restart the device.
[Verizon Samsung Galaxy S III] invisiblek:
This works fine for me other than it being a bit janky. It keeps freezing for a second every couple seconds, but never crashes or anything. Always seems to take a picture too.

Considering this isn't happening on other camera apps (stock, focal, camera mx) I'm inclined to blame snapchat's app for the jank.

On another note, good news in the future for those of you bluetooth users out there. Bluetooth has long been a royal PITA on d2 and I think we've got it nailed down. Code is on gerrit, so you should hopefully see it trickle into the nightlies pretty soon.
[Verizon Samsung Galaxy S III] hoodieNation:
I don't even use Bluetooth but I still like to see that. Lol.
[Verizon Samsung Galaxy S III] AlphaXray:
Making me happy. I never used to use bluetooth but now I have 3 different bluetooth speakers. So this is awesome.
[Verizon Samsung Galaxy S III] cheekoo:
i was seeing the same thing. I wiped the phone, installed everything from backup n it's good now.
[Verizon Samsung Galaxy S III] StormFreak:
Great to hear about Bluetooth! Keep up the awesome work!

Regarding the camera 'issues', the only things I notice are in Vine, when trying to take a video an error occurs stating that the feature isn't supported on this device and on Instagram, taking a video works, but crashes when you try to post it. Also last night, I noticed the barcode scanner in MyFitnessPal was not working. All of these work fine with TW, but I love this ROM too much to leave it. I know these are minor, but I figured I'd just mention them. Thanks again for all the hard work!
[Verizon Samsung Galaxy S III] bmeek:
Thanks very much for the hard work and the great news! Now, while y'all are in there working on Bluetooth, is there any chance we can get cm11 to produce an audible ringtone when an A2DP Bluetooth device is connected for media output?

Is this silent-ringtone-with-Bluetooth behavior common to all CM devices? All AOSP ROMs? It was also an issue (or a design-flaw) with cm10.2 on our phones.

I do know that TouchWiz ROMs behave the way I think they should - your ringtone sounds out loud, through the phone's speakers, even when your Bluetooth headset is connected...

I'm not sure if I'm talking about proper behavior, a design-flaw or a bug. Thus it should probably be an option :).
[Verizon Samsung Galaxy S III] annoyingduck:
Are we going to see lockscreen button controls (so I can long press home for torch) again, or are they not going to be merged into CM11?
[Verizon Samsung Galaxy S III] SDQB17:
I just dl'd the 07 nightly, I had read there was an update to the cLock app. They must have decided not to because nothing on it has changed, there are no different options and it still shows weird looking lines over the sun instead of clouds...just thought I would mention it. Perhaps I just read the post from CM on G+ wrong. Everything else seems to be working as it did on the snapshot.
[Verizon Samsung Galaxy S III] annoyingduck:
Flash the 8th build and then tap the weather on cLock...
[Verizon Samsung Galaxy S III] SDQB17:
Ahh...ok my cm updater must be a day behind :) I will once it downloads...thx

Edit: updated to 08, it has changed, however now I get no weather icon at all. I get all the other info...but the icon space is just empty, I have tried all the 3 icons also to choose from, they just wont show up on screen. Several reboots seemed to have fixed the weather icon issue...good for now.
[Verizon Samsung Galaxy S III] thefuzz4:
Going to give this a whirl here in a few mins once the latest nightly completes its d/l.
[Verizon Samsung Galaxy S III] merdely:
Glad I'm not the only one.
[Verizon Samsung Galaxy S III] Prack:
Did you guys even read the thread? Look at the last line:

Q: Do I need this patch?

A: It depends on what ROM you are using:

if you're on stock ROM, you'll benefit from flashing both bionic and dalvik patches,

if you're using a custom ROM, you most probably don't need bionic patch, as these are already included in most custom ROMs. You'd benefit only from flashing dalvik patch (if it's not already included by your ROM maintainer, of course),

don't use the bionic patch on CyanogenMod, PSX and probably others, because they already have more optimized versions!
[Verizon Samsung Galaxy S III] xs11e:
Thanks, BT is all that's keeping me from using CyanogenMod as a daily driver.
[Verizon Samsung Galaxy S III] Zacharybinx34:
My netflix/video playback sometimes causes hard reboots. Anyone else experiencing this?
[Verizon Samsung Galaxy S III] Travisholt92:
Anybody still having issues with poweramp freezing on song change and sometimes playing very quickly on song change? Thats the only issue preventing me from using 4.4.2 as a daily driver. :/ gotta have my music man.
[Verizon Samsung Galaxy S III] Casper34:
I miss this, please add this in the near future.

I have not had any issues with poweramp. I have been running the 1/2 nightly since its release. :thumbup:

Sent from my Ktoonzified PACmaned SGS3!
[Verizon Samsung Galaxy S III] duarian:
Turn off crossfade in the audio settings. That should clear it up.

I wrote a guide somewhere on the general forum section. Probably buried by now but my poweramp works great except the lock screen fails to update sometimes.
[Verizon Samsung Galaxy S III] headcheese:
Add Xposed and gravity box the option is in there.
[Verizon Samsung Galaxy S III] annoyingduck:
Yes it is, but haptic doesn't work when enabling, and I use art run time - so no xposed for me...
[Verizon Samsung Galaxy S III] Casper34:
I have not had this issue since I removed a hacked version of an app.....

My issue, I can't seem to go below 20% battery. By 5 I should be around 40% or so, since I installed this rom, I have been around 60-70%. I have been constantly on my phone e for the last hour with the screen on and its only gone from 23 to 21%.

My question is, has anyone else had this issue? If so, what fixed it?

Or

You think a fresh install will work? (Factory reset)

You can see that for the last hour its leveled off with the screen on.

Sent from my Ktoonzified PACmaned SGS3!
[Verizon Samsung Galaxy S III] joedajoester:
I decided to completely drain my battery once and it stayed around 20 percent for a while and then my phone just shut off. When I plugged it in, it was around 1%. This was on sspencer's KitKat build. I even thought my battery was going bad. I hope this isn't a new problem in cm :/
[Verizon Samsung Galaxy S III] duarian:
A question about the cm updater, I haven't used it in quite some time. Does it not install the ROM for you anymore? I just want to make sure I'm not doing something stupid .
[Verizon Samsung Galaxy S III] Casper34:
I hope so also. Maybe someone else can confirm this bug?

Also, I had philz recovery installed before and love it, but had to remove to update pacman, does anyone know if philz will install this rom?

Sent from my Ktoonzified PACmaned SGS3!
[Verizon Samsung Galaxy S III] BadUsername:
It will, it's based from this roms source, it's made to work with the update-binary from this rom.
[Verizon Samsung Galaxy S III] Casper34:
Sweet! Thanks! Now if someoneelse can confirm the battery issue.... :rolleyes:

Sent from my Ktoonzified PACmaned SGS3!
[Verizon Samsung Galaxy S III] PSUFINN:
It does update the rom for you
[Verizon Samsung Galaxy S III] duarian:
Hmm...my recovery must be messed up then. It doesn't update it when I have it reboot. Just says csnr read recovery.log or something (this happens every time I boot into recovery).

I'll download and try again. Thanks!
[Verizon Samsung Galaxy S III] PSUFINN:
Try updating to the newest recovery of you are not already on the latest
[Verizon Samsung Galaxy S III] k.electron:
alarm volume issue.

This has been a recurring theme for past few CM versions including the CM10.2 final. The alarm will go off making the phone vibrate but tone is not played. If I go into the clock and modify the alarm tone, none of the examples play either, going into ringtone and notification, none of those examples play either. its almost like the phone has lost its loudspeaker, but if i go play youtube or something, it plays fine.

Fyi: i dont use a dock, or bluetooth at all. i just charge at night with regular ac <-> microusb charger and bluetooth is permanently turned off.