yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] the_gonz79:
My battery also got sucked up pretty badly today. I was looking at what was running and Google+ seemed to be running quite a bit even though I didn't check it all day. My guess that it may have been downloading my photo library (fresh install) and since I was in a building that had horrible signal, it may have been eating up the battery. Maybe something similar may have been happening in your case? Ill see how it behaves tomorrow.
[Verizon Samsung Galaxy S III] alee:
Jenkins for NFC 9/1 build (got built early so it's still showing 8/31) link: http://jenkins.cyanogenmod.com/view/All/job/android/7252/
[Verizon Samsung Galaxy S III] dlsolo:
Had similar situations. I think I narrowed it down to ktoonsez kernel. Either I didn't setup my settings correctly or it, somehow, makes certain apps high priority. I'm not sure, but the stock kernel on AOKP and CM10 seem to fix that issue.
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
Does this one fix the incoming call delay?
[Verizon Samsung Galaxy S III] dlsolo:
Under the phone, settings, you should have an option for Ring Delay. The option to turn Off is available.

What that what you were referencing?
[Verizon Samsung Galaxy S III] eMpTy43:
Just wanted to throw this out there... I rebooted into recovery and flashed the "9/1" nightly, booted up to a 6% battery drop, rebooted once more and was down another 4%. This is all with a stock kernel and no real use.

I would like to note that going from 8-27 to 8-31 I did see a small decrease in battery life... I did leave my mobile data on for a few hours at work though and I have a horrid signal there (about -118dBm) which makes the phone work really hard.
[Verizon Samsung Galaxy S III] djeddieone:
I see NFC is finally working that's major what about the Verizon apps like NFL and My Verizon are those working?
[Verizon Samsung Galaxy S III] imablackhat:
I'm on 831 and my Verizon works just have to login every time you open it. Haven't updated yet because people are crying about battery life for NFC to work.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
No

On 8/30 with incoming calls there is a few seconds of silence when you first answer the phone
[Verizon Samsung Galaxy S III] imablackhat:
Anyway to get messaging not to split messages and send them as two like older style phones?... kinda silly

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] Brian Gove:
It should be noted that CWM Touch will NOT work to flash this... unless I'm just the unlucky bastard....

I used CWM Touch 5.8.4.9 from EZ Recovery and got errors installing...

Now I thought maybe with all the screwing around I've done maybe something was out of whack... I used Odin to go back to stock and start all over again... still the same error.... so I used my little friend Google(which I should have done in the first place) and found that a Status 7 error is due to a recovery that will not work....

So I flashed the latest regular CWM and it all worked fine....
[Verizon Samsung Galaxy S III] wera750:
The newest cwm touch(6.0.2.1 I think) recovery works perfect. I used it up until two days ago when twrp got updated and fully functioning.
[Verizon Samsung Galaxy S III] revolt1:
I had that problem a while ago touch sucks on cwr so I use the normal one on my gnex I use touch
[Verizon Samsung Galaxy S III] wera750:
http://db.tt/RFOxoy76

Bet this one works fine...(credit Koush)
[Verizon Samsung Galaxy S III] drbveb88:
Been using the newest Twrp 2.2 and it is working great for me. And I usually flash something everyday.:)

Shhh.. my Galaxy is a little Paranoid
[Verizon Samsung Galaxy S III] eMpTy43:
Can't say where I was reading it, could be early on in this thread or in one of the CWM threads but CWM Touch has had issues flashing things previously. IMHO a recovery app to me is something I want to work regardless of a touch screen so I won't use CWM Touch, prefer the hardware keys. Meh, call me old-skool :highfive:
[Verizon Samsung Galaxy S III] walcs:
Awesome that the NFC is working now! Now the camera needs to go higher than 3MP :P
[Verizon Samsung Galaxy S III] Brian Gove:
Never ran into a problem until now... granted I've only flashed stock TW ROMs until now too...

Just figured it should be mentioned in the OP so people don't run into the same BS I did... I was able to fix it and am loving CM so far on my SIII seems like a lot more things work than when they were trying to get it to work on the DX..

EDIT: Has anyone had troubles with TiBu seeing their external SD card on this ROM??? Formatted to fat32.
[Verizon Samsung Galaxy S III] revolt1:
There for sure a 3sec delay in answering the phone wonder what that is
[Verizon Samsung Galaxy S III] CKyl22:
So is NFC confirmed to work now? :D

If only the call delay wasn't there.

Ahh I'm so excited! :D
[Verizon Samsung Galaxy S III] Brian Gove:
NFC does not work... but the call delay has been fixed....

jk
[Verizon Samsung Galaxy S III] eMpTy43:
^^^ LOL

NFC will definitely turn on and Google Wallet recognizes it being on. I was able to set everything up successfully. Apparently my local after hours retailers and fast food joints are cheap and don't have PayPass/NFC payment options so I couldn't test a transaction.

CALL DELAY: Yes, it's still ~3 seconds on the 9-1 build

SCREEN PERMA-SLEEP FLUKE (One time):

I performed a test call (outgoing to a VZW Droid 4). I ended the call on the Droid 4 while the S3 was up to my head (sensor had screen off). I did not hear my call ended noise and once I tried to wake up my screen it stayed dark/off. The soft keys lit up but no screen. I set it down for about 1-2 minutes and picked it back up, could not wake screen, no soft key lights. The phone had powered itself off, turned it on and all is well... I could not duplicate the issue.
[Verizon Samsung Galaxy S III] flameinthefire:
where can i get google wallet from that works on cm10
[Verizon Samsung Galaxy S III] Kirkenjerk:
Getting a lot of force closes with this version. Almost every app I open force closes once or twice.

8-31-2012 version that is.
[Verizon Samsung Galaxy S III] jonathanphx1:
there's a new update dated for today 9/1 check the change log it is different than the 2 prior ones dated 8/31download it through rom manager
[Verizon Samsung Galaxy S III] Aali1011:
LTE Toggle in the Notification Drawer does anybody have it working? Searched through the thread and haven't seen anything so wondering if isolated issue or something else. I haven't had it work since maybe the 8/16 build.
[Verizon Samsung Galaxy S III] TechSavvy2:
Op is not maintained anymore. He left.

Newest clockwork works 100% functional. 6.0.1.2 I've been using it since that specific version dropped on ROM manager and havent had a single glitch yet. And that includes touch version. And I flash about 5 times a day :)

I just hate seeing people knock cwm touch, there's not a single issue with it. Solution - don't use ez-recovery, its outdated with old version.
[Verizon Samsung Galaxy S III] droidxuser123:
sounds like a S.O.D.
[Verizon Samsung Galaxy S III] eMpTy43:
http://xdaforums.com/showthread.php?t=1769083 has links to the different wallet files. I'm using modaco r75
[Verizon Samsung Galaxy S III] cgulliver:
Ok so still a little nervous about Google Wallet. Is there still a risk of permanently borking NFC?
[Verizon Samsung Galaxy S III] eMpTy43:
These moded Wallet apps just get rid of device and location checks on startup and then the pesky error message for "unsupported version". My NFC can turn on and off just fine. Google wallet is just an app APK so it doesn't have any control over the NFC radio.

For example, if I turn my NFC off via settings and start up Wallet it prompts me to turn it back on via settings (same way maps jumps you to location settings).
[Verizon Samsung Galaxy S III] codyvance:
Yes! You MUST reset Google Wallet anytime you do a full wipe or you will permanently break NFC for wallet use
[Verizon Samsung Galaxy S III] imablackhat:
On 831, noticed issues. In call volume up down etc doesn't change a thing. No echo though. Never experienced the echo because I wasn't on the builds till now.

MMS.apk app splitsmessages over 160char like a old school phone and no way to combine ?. Maybe go SMS would fix this...

NFC doesn't work (but that's an obvious). Doesn't make it or break it for me.

I want to clearly dirty to the latest but people are crying about battery life on 91?

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] eMpTy43:
I left my phone off the charger last night with 9-1... only a 10-15% drop over 10 hours (2 hours heavy use and 8 in standby). I'm definitely not complaining! I'll post tonight after a day off with moderate use and I usually get a sub par signal of 1-2 bars of 4G at my house.

Sent from my R00T3D/UNL0CK3D SGS3 running CM10 nightlies ;)
[Verizon Samsung Galaxy S III] wera750:
The new sms pop up looks sweet, hope it gets merged tonight
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
Where can I see this pop up that you speak of
[Verizon Samsung Galaxy S III] imablackhat:
Auto brightness doesn't work. Only when you first turn on the screen for me.

Example. Turn on screen on dark room it'll be dark. Turn on screen in bright lit room it'll be bright. It doesn't change while on..unlike stock Roms

Sent from my SCH-I535

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

SMS over 160 char sends as two messages. Installing other messaging apps doesn't work. It will fail to send the message... the hell.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] wera750:
mhttps://dl.dropbox.com/u/50993944/Screenshot_2012-08-26-13-45-10.pngHere is a picture

http://review.cyanogenmod.com/#/c/22188/ here is gerrit
[Verizon Samsung Galaxy S III] eMpTy43:
If you accidentally flash a ROM or Wipe without resetting can't you just restore a Nandroid, reset Wallet, and then flash another ROM or Wipe?

Sent from my R00T3D/UNL0CK3D SGS3 running CM10 nightlies ;)
[Verizon Samsung Galaxy S III] codyvance:
Yes
[Verizon Samsung Galaxy S III] Trumps:
Anybody else kind of disappointed with lack of progress in CM10 so far? I've been a die hard CM guy ever since my OG droid.

Now, every morning I wake up and look at the changelog and I'm like, "Woo, more Danish translations, awesome!".

Meanwhile, I look like an idiot answering my phone in public. "Hello? Hello!? Hello...... Hello?"
[Verizon Samsung Galaxy S III] eMpTy43:
Jelly Bean is brand new and the boot loader has only been unlocked for 2-3 weeks. The CM guys are making sure everything is going to be perfect once we get to an RC and finally a Stable release...

I really don't think it takes a rocket scientist to click Answer/Accept, count to 3, and then say Hi... just my 2 cents. If counting to 3 is too much of a deal breaker rock another ROM until the incoming delay is fixed.

Development is going to come with its quirks... there was a lot of chatter about NFC yesterday, most likely why NFC was addressed over the call delay. @CM devs: Could we possibly get some work in on that today?

Sent from my R00T3D/UNL0CK3D SGS3 running CM10 nightlies ;)
[Verizon Samsung Galaxy S III] awmobjects:
I'm very pleased with the efforts and progress...NO COMPLAINTS!
[Verizon Samsung Galaxy S III] jgrimberg1979:
You don't need to reset the secure setting ever at least I never have. I Google wallet app and data via titanium backup. Works every time.
[Verizon Samsung Galaxy S III] Raegx:
You are using a build meant for QA and test purposes. Every build is going to be both steps forward and steps back since they are doing new development. New development never goes perfectly.

I think the progress you are looking for is what we see during the RC cycle where they are just polishing the ROM.

tl:dr wait for the RC releases
[Verizon Samsung Galaxy S III] jmill75:
Im by no means complaining like the guy above...I love the development process. I do wish the simple features like calling and answering were worked on first so we could be able to run this daily and help find the harder to fix bugs and send feedback.

Again, not complaining could i could flash TW back in seconds, but that would just be boring now wouldn't it!!! :)
[Verizon Samsung Galaxy S III] cgulliver:
I have actually noticed an increase in the commits recently. The velocity is picking up.
[Verizon Samsung Galaxy S III] theraptscallion:
Nope, I'm completely satisfied with development on the s3 so far. It's light years ahead of my experiencewith tthe razr and fascinate.

That said, since flashing 8/31, my battery won't charge above 60% despite hours on the charger. Tried resetting battery stats but no change. Ideas?
[Verizon Samsung Galaxy S III] Mayze23:
Anybody else kind of disappointed with the lack of contribution of people who complain about free labor? Android is open source. If you don't like it fix it.
[Verizon Samsung Galaxy S III] neyenlives:
Ok, I started this thread so I will try to keep the OP updated periodically. If you know of a specific issue or change to the ROM that isn't properly reflected in the OP, please PM me. I don't read every post in the thread.

Thanks
[Verizon Samsung Galaxy S III] codyvance:
Flip flopper! Lol thanks for updating
[Verizon Samsung Galaxy S III] Flip35:
Remember the reason why cm has gotten this far is because they do things right, they don't try to rush it to please us, they make sure those builds are stable, sh!t even their alpha builds are pretty solid, I remember alpha v3 on my evo3d was so solid, be patient man these guys don't have to do this for us, yet they take their time to

Sent from my SCH-I535 using 2
[Verizon Samsung Galaxy S III] alee:
Big set of updates coming in 9/2:

http://cm10log.appspot.com/?device=d2vzw

Seems focused on SMS/MMS improvements, including the quick reply pop-up mentioned in earlier posts. Lot of internationalization bits.

Bunch of bug fixes, and possibly some performance improvements.
[Verizon Samsung Galaxy S III] wera750:
Can anyone confirm no mhl connectivity? I can't get anything, even tried multiple hdmi cables.
[Verizon Samsung Galaxy S III] alee:
Are you using the SGS3 version of the MHL cable?

I was able to use MHL a few days ago on an earlier build without a problem.
[Verizon Samsung Galaxy S III] seang:
really?

they are called nightlies for a reason. this isnt even an alpha, beta, or a RC yet.

once theres a RC, and your phone doesnt answer correctly, then we may have an issue. hell, samsung hasnt even released 4.1 for verizon yet.
[Verizon Samsung Galaxy S III] wera750:
Yes. I've used it in the past as well with cm10. But I got nothing on the 9/1 build.
[Verizon Samsung Galaxy S III] alee:
Just tested... confirmed NOT working on 9/1.
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
Is anyone running the latest nightly with lean kernel? If so how's it running?

I tried latest build with k747 and I had that lag issue n it looks like a lot of people are
[Verizon Samsung Galaxy S III] Trumps:
I just find it ironic that the phone portion of the the phone is constantly broken right now. After 3 weeks I somewhat expect the ability to make and receive calls without audio cutouts, delays, or echoes. I absolutely understand that unintentional breaks are unavoidable at times, but it's been one thing after another with the actual "phone" portion.

Does the rest of the build work great? Yep, you bet!

I have no complaints other than the phone functionality being constantly broken and no way to disable the intrusive nature of notifications pausing music. I'm starting to think making phone calls and listening to music are two things people don't do anymore.
[Verizon Samsung Galaxy S III] the_gonz79:
I don't know if anyone else can replicate this, but when checking messages from the lock screen, the drop-down menu has some graphical issues. (Im on 8/31 build, stock kernel). Everything else seems to be working. Battery is much better today so I will chalk it up to long-term data pulling by Google+.
[Verizon Samsung Galaxy S III] XDAholic:
You might want to try the 8/16/12 alpha build. Surprisingly the only broken feature I could find was NFC.

The call quality, data and battery are on par with stock TW roms. I have only used CM kernel tho.....
[Verizon Samsung Galaxy S III] eMpTy43:
Personally... I might make a phone call 3-4 times a week and never listen to music from my phone. LOL @ me, guess that's why IDC about those 2 issues :p

I'll remember to check for this each time I get messages/notifications and report back.

Battery on the 9/1 build is freaking awesome... just over 4 hours with light use and I'm only down to 84%. At this rate I'll be leaving it off the charger tonight to see just how far it'll go. These results are with WiFi, mobile data, auto brightness, and NFC turned on. I have 1-2 4G bars but most of the time I'll sit at 1.
[Verizon Samsung Galaxy S III] revolt1:
runninggood smooth
[Verizon Samsung Galaxy S III] eMpTy43:
Can anyone that was experiencing issues with multiple notification/ringtone entries try 9/1 to see if it's resolved?

There was one person that couldn't view pictures on an external SD card via the Gallery app... any luck with 9/1?
[Verizon Samsung Galaxy S III] Nnyan:
I guess we have different experience, yes there are issues but this is the ROM I spend most if my time on and I find it very functional
[Verizon Samsung Galaxy S III] neyenlives:
i'll be honest, my wife and I have 700 minutes to share between us and it looks like we might use 200-300 minutes a month combined....there's not too many situations that dictate a phone call for me. Texts are faster and more convenient for both parties. If the message is larger than a text, email works if you have lots of detail to share. Voice calls are only for very lengthy conversations that cannot be properly expressed in a text or email.

Haven't had any issues listening to the 30 or so Gigabytes of music on my sdcard using Poweramp. Streaming music is something I can do but haven't in a long time. I have both Google Music (their cloud) and Audiogalaxy(my cloud) set up but rarely use them. They are more of a redundancy.

So what's the verdict on the 9-1 Official build in terms of call volume/quality? I am still on the 8-23 build because I never had any issues with calls and would rather not upgrade if all I get is reduced functionality.
[Verizon Samsung Galaxy S III] ssmaster:
My new game granny smith is not working on 9/1 with the kt7441 whatever kernel. It worked fine on the 8/30 version. I tried reinstalling the game and it still won't work.

Edit: turns out it was my auto rotate app. For some reason it turned on auto forced which kept my screen on portrait mode and the game wouldn't load because of that.
[Verizon Samsung Galaxy S III] alee:
How about with the 9/1 kernel? 3rd party kernels really just add to the noise here. CM10 is developed, tested and distributed with its own kernel.

If it works with the bundled CM10 kernel, CM10 is working fine. If it doesn't, then it's a bug.

If it doesn't work with a 3rd party kernel, the discussion really belongs in a kernel thread, not a CM10 thread in my opinion.
[Verizon Samsung Galaxy S III] iofthestorm:
Haha, you must be new to this kind of thing. The Samsung fascinate and Epic, the first major Samsung CDMA devices, took months before the RIL was figured out for AOSP ROMs. I think it was at least 6 months before the first AOSP ROM that you could even make phone calls from was out. Three weeks is really nothing. These guys are doing this in their spare time and many developers support multiple phones. We're just lucky that Samsung has gotten a lot better over the years with their support of open source and providing good source dumps.

Incidentally, bugs don't get fixed without hard data, so if you're having problems make sure to attach the relevant logs. If you don't know how to do that, you honestly should not be running custom ROMs, especially not nightlies. The whole point of nightlies is so that people can help find bugs, not complain about them constantly, which is all I see in this thread. I mean, it's useful to point out that a bug exists in a certain build, but repeatedly complaining about how something doesn't work really helps no one.

Incidentally, I'm still on 8/31 so I'll check out my MHL adapter and see if it still works and report back.
[Verizon Samsung Galaxy S III] aznguyen316:
Heh I'm pretty much in this boat. GF and I are on a 700 minute plan with unlimited data.. I have 1/2 of my library synced to my SDcard and entire lib on google music. I mostly listen to music via sdcard but occasionally will pull up a song or two via Google Music to listen to.

I think I want to try this official version of CM10 out.. gonna flash 9/1 and see how it goes.. Been on CleanRom 2.0
[Verizon Samsung Galaxy S III] eMpTy43:
Agreed. This thread is about the official CM10 nightlies, not moded ones. Cyanogen creates their own entire package, if you want to add 3rd party kernels tell them their kernel dropped into CM10 doesn't work.

Sent from my R00T3D/UNL0CK3D SGS3 running CM10 nightlies ;)
[Verizon Samsung Galaxy S III] neyenlives:
you'll like it....at least I can speak for the 8-23 build
[Verizon Samsung Galaxy S III] tv31284:
I just took a call and didn't notice the 3 second delay. I wonder if there's some setting that's causing the bug. I'm on the 8/31 build btw.
[Verizon Samsung Galaxy S III] imablackhat:
I'm on 9/1 now dirtied from 831. Notice I can enable NFC. Can't test it though Haha. Don't notice anything else really. Still can't adjust in call volume. All up and down don't make a difference?

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] eMpTy43:
Just bought some irrigation parts from home depot... NFC kicks ass!

Sent from my R00T3D/UNL0CK3D SGS3 running CM10 nightlies ;)
[Verizon Samsung Galaxy S III] digitalsynner85:
I think unless something breaks somehow while running 9/1 with the Google wallet hack, I'll be using it as my DD, haven't experienced the 3 sec bug, no audio echo in calls, no Wi-Fi or data issues, or any graphical hiccups. This is a great Rom and love the work the mods put into it.

PS bought a meal from McDonald's to try out nfc and it works like a charm
[Verizon Samsung Galaxy S III] NeoMagus:
I have been using this as well , only problems I've had on the alpha is no NFC/ no Netflix, now that they seem fixed on nightlies just waiting til the echo/delay issue is solved before I jump onboard.
[Verizon Samsung Galaxy S III] theebrownieee:
Anyone else not able to get a GPS lock?
[Verizon Samsung Galaxy S III] dividebyzero:
Are you using the usual hack where you change the build prop to htc_jewel or nexus then flashing wallet fix in recovery or is there a better hack out there yet?
[Verizon Samsung Galaxy S III] apacseven:
No problem getting GPS lock here, 9-1 official stock, formatted system/data/cache and wiped dalvik.
[Verizon Samsung Galaxy S III] theraptscallion:
I can get a lock almost instantly with third party apps, but Google Maps seems to be unable to maintain the lock and has a difficult time getting it in navigation at all.
[Verizon Samsung Galaxy S III] Brian Gove:
I just tried with Maps and The Weather Channel and neither could get a lock. I'm on 8/31 build and came from a complete wipe etc...
[Verizon Samsung Galaxy S III] codyvance:
New build just finished.. I'm going to flash it now..
[Verizon Samsung Galaxy S III] eMpTy43:
Same ole' way :good:

Maps and Nav don't lock for me. It'll get really close then jump around.

Sent from my R00T3D/UNL0CK3D SGS3 running CM10 nightlies ;)
[Verizon Samsung Galaxy S III] wera750:
I see two 9/1 builds. I'm assuming your flashing the second one. Can you report back if it has the pop up sms?
[Verizon Samsung Galaxy S III] codyvance:
Correct, second one... Doesn't seem like there is pop up sms yet, unless there is a setting to be enabled i do not see
[Verizon Samsung Galaxy S III] wera750:
have you got a text yet?
[Verizon Samsung Galaxy S III] codyvance:
lol yes, I sent myself one..
[Verizon Samsung Galaxy S III] renzo.olivares:
heres build i compiled like 30 minutes ago if anyone wants it

http://beta.androidfilehost.com/?fid=9390077933525139467

sms pop up is in [enable in sms app>settings>quickmessage]

also ive changed the build fingerprint to reflect the newest version of jellybean instead of ICS

NFC enables and disables but i cant test