yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] wctaylor79:
I am using the stock kernel so not sure, but worth a shot to go back and wipe again and see what happens.. :) Thank you for the advice. I agree doesn't seem to be a big issue all around.
[Verizon Samsung Galaxy S III] ExodusC:
It can't be that, as it's on the default setting, which doesn't kill background tasks unless memory is needed- which is why this must be a bug, since Android normally doesn't kill active background processes, it kills the least-used and idle processes.
[Verizon Samsung Galaxy S III] strung:
8/30 call volume way too loud and can't change it
[Verizon Samsung Galaxy S III] yznhmr:
+1 im on 30, but agree with what was stated above.. about echo, and BT

stock kernel, gogin to flash 747..

I wonder if Google restoring the apps and settings is breaking the ECHO fix.. any thoughts?
[Verizon Samsung Galaxy S III] Coderedpl:
Godamn it i want to jump on this but these echos and stuff are really bothering me =(
[Verizon Samsung Galaxy S III] vdefender:
Just thought I'd finally chime in here. I'm still running g 8/28. No echo here. Sound is all working. Alarms are good. Only issue I have is sometimes I get the screen flicker which isn't that bad. My other issue is that when I connect to my car stereo Bluetooth to stream music, I have to click once down on the Bluetooth volume and then back up on the volume to get the max volume. Otherwise its quiet. Anyone else have that issue?
[Verizon Samsung Galaxy S III] awmobjects:
I wiped cache/dalvik and factory reset with 8/29 with np at all so far...using ROM kernel.
[Verizon Samsung Galaxy S III] toddley:
8/28 here. Definitely have the echo and occasional screen flicker but those are the only issues. Haven't done much with Bluetooth but I may test it some later. With the 3 experimental builds yesterday it's obvious they are working hard on the echo so I'd say that won't be an issue in a couple of days
[Verizon Samsung Galaxy S III] lxetuo:
If you go to 'Settings' -> 'About phone' and tap quickly on 'Android version' or 'CyanogenMod version', you'll get a graphic (different one depending on which one you tap). Then if you long press on the graphic, it'll take you to an animation you can play around with. It's like hidden easter eggs! :)
[Verizon Samsung Galaxy S III] ssmaster:
I have abyssplug governor with vr I/O scheduler. Whats a good way to keep the lightflow app in memory? I think it is being killed automatically because sometimes my lights don't work until I re-open the lightflow app.
[Verizon Samsung Galaxy S III] alee:
Noticed this as well. Don't think it's being killed though -- I think the accessibility services aren't being consistently called upon each new notification.
[Verizon Samsung Galaxy S III] AlexDeGruven:
Then don't do it yet. It's not a big deal, and stuff is changing daily. Don't be frustrated that your particular dealbreaker hasn't been addressed yet, because it very likely will in the near future. Code is changing constantly, and new updates are literally daily at this stage.
[Verizon Samsung Galaxy S III] tekhna:
Does anyone else get sleeps of death? Occasionally I'll turn the screen on but it'll stay black, however the button lights come up. Takes a battery pull to get out of it.
[Verizon Samsung Galaxy S III] strung:
Yes, on every nightly.
[Verizon Samsung Galaxy S III] Nnyan:
On the 8.30 and so far (about a dozen calls or so) no echo's! All I did was wipe cache/dalvik and installed right ontop of 8.29 which was having echo that could get really bad. Haven't had a chance to do much testing but here is initial findings:

Data/wifi sensitivity: is still less then stellar

BT Auto Connections: short term BT disconnects don't phase it (will leave my BT device off for a few hours to see how it handles that).

GPS: Very fast lock (even to or better then stock) in Waze and Google Maps. GPS test in view/in use is 18/10 with more yellows then I've ever had on an AOSP ROM. Accuracy down to 13' which I had never been able to get to before. Very nice but not quite up to stock where I could get 10' and some green.

I have not seen a SOD in a while.

Can't get it no matter how quickly i tap it.
[Verizon Samsung Galaxy S III] henrys01:
Which 8/30? The official 8/30 built isn't available on the server

http://download.cyanogenmod.com/get/jenkins/7171/cm-10-20120830-NIGHTLY-d2vzw.zip << fails
[Verizon Samsung Galaxy S III] juancaperez2000:
try from here http://jenkins.cyanogenmod.com/job/android/7171/
[Verizon Samsung Galaxy S III] imablackhat:
Does 830 fix all echo and no sound or too loud sound in calls issues? I want to try this rom now as my dd if this is the case.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] Travisimo:
I have never gotten a sleep of death on any of the cm10 builds I've installed (currently on 8/29). There has to be a certain variable that causes it that isn't present on my phone, I guess.

What I *am* getting on this build is a Home button problem: sometimes a home button press does not turn on the phone, but if I press it a couple of times in succession, it will come on. I thought perhaps the home button was going back, but I'm not having any problems with the home button once the phone is unlocked. It's not the screen of death issue because the phone just doesn't unlock or come on (no lights or anything).
[Verizon Samsung Galaxy S III] psycho_asylum:
I noticed that there is no echo in this experimental build but I cannot change the call volume AT ALL. Up and down volume button shows the display for the sound and it moves up and down but the volume does not change.

Same here.
[Verizon Samsung Galaxy S III] jmill75:
Yeah home button is inconsistent.
[Verizon Samsung Galaxy S III] psufan5:
any of you try Volume+ to adjust the sound?
[Verizon Samsung Galaxy S III] betam4x:
Has there been a build better than 8/16 yet? I know netflix apparently works on newer builds, but from what i hear everything else broke.
[Verizon Samsung Galaxy S III] psufan5:
Everything else??? Think that might be a little... off.
[Verizon Samsung Galaxy S III] strung:
In-call sound volume can't be changed, vibration for notifications don't happen, in-call echo still occur ... still some graphics flicker but better... NFC can't be enabled ... not sure what else. Netflix works though. HTH
[Verizon Samsung Galaxy S III] betam4x:
Okay, maybe i should clarify? Data, Bluetooth, Call audio, etc...that's what i'm getting from reading recent posts at least. However the signal to noise ratio is rather flat as of late. It's hard to tell what is an actual issue people are experiencing, and what only one person is experience (due to improper flash, overclocking, custom kernels, etc).
[Verizon Samsung Galaxy S III] psufan5:
I just used bluetooth in my car. Im going to try volume+ to see if it fixes the headset volume in a few minutes.
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Volume+ isn't compatible with jelly been yet. Unless it's been improved in the last few days

Sent from my rOot3d Samsung Galaxy S3 now with the uNL0ck3d bootloader
[Verizon Samsung Galaxy S III] PerCompLLC:
Volume works perfectly for me (in call volume as well). 8/30 experimental
[Verizon Samsung Galaxy S III] patt2k:
I am on the 8/30 Build there is only one issue when someone calls me , I cant hear him/her I have to call back in order for it to work, any fix for that?

I cleared dalvik and cache partition
[Verizon Samsung Galaxy S III] Ratzinc:
Tried out the 830 exp, got complaints about the echoing, camera res options are missing, no sound at boot (played with the sliders and it kicked in.) And the data isn't stable yet. MMS worked and network speed were excellent, down clocked to 1.2 and just as snappier than full speed stock if not more so. Will try it out once camera options/ quality and data stability are refined...can't wait!
[Verizon Samsung Galaxy S III] PerCompLLC:
I don't have that problem, but there was a fix posted a page or two back...
[Verizon Samsung Galaxy S III] manywelps:
I was running 8-20 up until yesterday and never got an SOD either. I went to leankernel after a few days too for 1900MHz goodness and fastcharge.
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
What's the verdict? Which nightly has the echo fix? I'm still on 8/23
[Verizon Samsung Galaxy S III] alee:
Why don't you tell us?

CM10's progress depends on everyone testing the software and reporting back. The best part is going back in time to a build that worked for you is always an option.
[Verizon Samsung Galaxy S III] manny108:
Is anyone having problems sending pics via SMS? I'm on 8/30 expiermental.
[Verizon Samsung Galaxy S III] PerCompLLC:
Sent a pic this morning with no issues.. 8/30 experimental
[Verizon Samsung Galaxy S III] manny108:
Thanks. I have tried WiFi 3g and 4g. Can't send pics via text. Vial email its fine.
[Verizon Samsung Galaxy S III] alee:
8/31 build looks to be pretty substantial so far.

Looking like a kernel update to 3.0.42, some code related to enabling the noise cancellation chip (perhaps echo related?), and some interesting stuff going on with how CM10 manages memory.

That last one is related to other apps getting killed unnecessarily when the system tries to kill apps to preserve memory. Those of us that are LightFlow users might see more reliable LightFlow behavior after this.

Could be a really great build, or could be the worst one yet... ;)
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Double post, please delete

Sent from my rOot3d Samsung Galaxy S3 now with the uNL0ck3d bootloader
[Verizon Samsung Galaxy S III] TheBiles:
Looking forward to the next nightly. I'm tired of my girlfriend complaining about the echo.

Sent from my Nexus 7
[Verizon Samsung Galaxy S III] yznhmr:
Im tired of hearing her complain also...:D
[Verizon Samsung Galaxy S III] ExodusC:
I assume you mean this commit?

Oh thank goodness. The whole system killing off active background apps was honestly starting to frustrate me, because that's in a sense quite a crippling bug.

I also experienced the other person not being able to hear when they called me- I rarely receive calls to this cell, so it's not a big deal.
[Verizon Samsung Galaxy S III] Karl:
anyone else getting 404 on 2012-08-30 06:30:08 release
[Verizon Samsung Galaxy S III] WhammyDroid:
Is anyone able to access the log files via logcat (ex. alogcat)? I've been told with JB that access to the log files has been removed. Can anyone else verify this? If this has been done, is there any way to get around it?

Thanks!
[Verizon Samsung Galaxy S III] alee:
Yep, that's the one. It's a huge win if it's fixed.
[Verizon Samsung Galaxy S III] codyvance:
I'm really excited for the 8-31 build.. Looks very promising with kernel upgrade and other fixes
[Verizon Samsung Galaxy S III] patt2k:
I really hope the 8-31 build is fixed.. :)
[Verizon Samsung Galaxy S III] Mystikalrush:
Will 31 be released tonight?
[Verizon Samsung Galaxy S III] BlueCross:
Is there a way to get the tablet theme on cm10 similar to what paranoid jellybean is running?
[Verizon Samsung Galaxy S III] Recon0212:
What's going to change in the next update?
[Verizon Samsung Galaxy S III] hopesrequiem:
Look one page back...
[Verizon Samsung Galaxy S III] Kirkenjerk:
More than likely.
[Verizon Samsung Galaxy S III] codyvance:
Build bot just started so we will know soon enough :)
[Verizon Samsung Galaxy S III] renzo.olivares:
8-31 is up only short link is working for me anyways about to flash...linux kernel is update to 3.0.42 weee
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Looking at what we have now as far as setting that can be changed in cm10, what percentage are we at when compared to the full version of cm10? I had cm7.1 on my old Tbolt, and i seemed that it had setting for setting. Are all the different variables already implemented into cm10, or is there alot more that will be added as we move forward on each nightly?
[Verizon Samsung Galaxy S III] cgulliver:
8/31 linky.... http://jenkins.cyanogenmod.com/view/All/job/android/7218/

+ kt747 8/30 update.....

http://www.mediafire.com/?yjj3g7ga1veedj0
[Verizon Samsung Galaxy S III] psufan5:
Did a test call, sound works on 3/31. Also seems silky smooth. :)
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
No echo?
[Verizon Samsung Galaxy S III] lxetuo:
Been running 8/31 unofficial (built it from source) since last night with no issues. Battery life seems to have improved. After some browsing/podcasting, still at 97%. Usually I'm at about 92-94% at this point.
[Verizon Samsung Galaxy S III] TheBiles:
I have zero echo on 8/31. However, I was lagging like crazy with KT747, so I reverted to stock kernel.

Sent from my Nexus 7
[Verizon Samsung Galaxy S III] dvigue:
What UNOFFICIAL build are you talking about? link? Thank you
[Verizon Samsung Galaxy S III] lxetuo:
By unofficial I mean I built it myself from the cm10 repository. I'm assuming all the changes in my unofficial build are in the 8/31 nightly built by the bot. Just like to build my own flashable zip from time to time :)
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
You mind sharing :)

I wanna see how this official goes if I have a bad experience mind sharing your unofficial?
[Verizon Samsung Galaxy S III] JuniorBevins:
It's anyone else having issues with downloading from Rom Manager I can't seem to get to any of the new one?
[Verizon Samsung Galaxy S III] manny108:
CM10 Nightly 8/31

The 8/31 has been running great so far. Thanks. :good: Still only having issue sending and receiving pictures via MMS.

Verizon Samsung Galaxy SIII - Rooted - UNLOCKED

Rom CM10 8/31 Nightly Kernel KT747 8/30
[Verizon Samsung Galaxy S III] huwarrior:
Can someone compare the experience of running cm10 vs Beans Custom Rom or even Synergy? I am debating switching over but given how great Beans Rom runs (and that it has Google Now baked in) I don't know if its worth changing.

Looking for comparisons in overall speed, battery life, etc...
[Verizon Samsung Galaxy S III] manny108:
I came from Synergy and Beans.. I was hesitant at first but, not ever going back. I love CM10. The quadrant scores are better on Synergy but, I'm not a fan of touchwiz themes at all. Plus CM10 has project butter baked in and it is very smooth. Love the vanilla android and how easy I can customize my themes by going to market and downloading CM10 themes.. With heavy use I get about 11 hours on battery.
[Verizon Samsung Galaxy S III] huwarrior:
Thanks Manny -

What was your battery life on Synergy or Beans with that same heavy use? Is Cm10 at a place where it is a dependable daily driver to rely on work email and stuff?
[Verizon Samsung Galaxy S III] WhammyDroid:
I was on Synergy, but completely hate TouchWiz. Moving to a pure CM wasn't even a question.
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
Did a few test calls and no echo!

Nightly 8/31 stock kernel
[Verizon Samsung Galaxy S III] manny108:
I got about 12 hours with heavy use on Synergy.. CM10 is my daily driver.. It is very stable.. I had an issue sending and receiving pics via MMS but, I had that with Synergy and Beans also.

Samsung Galaxy SIII - Rooted - UNLOCKED

Rom CM10 8/31 Nightly Kernel KT747 8/30
[Verizon Samsung Galaxy S III] schmaltzy:
I had this problem yesterday. I basically just booted into recovery, wiped cache and dalvik, reflashed the build I was on and it seemed to cure the problem.
[Verizon Samsung Galaxy S III] yukonhijack:
I am going to ask, because I just cant help myself {cringes}. Does NFC work in this build? I saw that in previous builds some folks said it worked, but I could not get it to stick after ticking off the check box.
[Verizon Samsung Galaxy S III] PerCompLLC:
No issues sending/receiving MMS for me on the 8/31 nightly... Sent two pics this morning to my wife and she received them without issue.

---------- Post added at 09:38 AM ---------- Previous post was at 09:34 AM ----------

Doesn't turn on for me on the 8/31 nightly... Earlier this morning I saw that some NFC stuff was going to be included in the next nightly, but it is no longer in the list. This indicates (to me at least) that the issue is being actively worked.

Changelog that I'm referencing: http://cm10log.appspot.com/?device=d2vzw
[Verizon Samsung Galaxy S III] Hilbe:
xoomdev fixed NFC on d2vzw for AOKP in upcoming builds:

http://gerrit.sudoservers.com/#/c/3059/

https://twitter.com/xoomdev/status/241526038209916929
[Verizon Samsung Galaxy S III] theraptscallion:
Flashed 8/31 this morning, no echo after several tests, bluetooth worked fine on the daily commute, and screen flicker seems lessened. Data remains slightly unstable (less bars in fewer places) but wifi holds steady for extended periods. No issue with incoming calls, as I can hear them and they can hear me, of course, I've only received three calls and made four, so take that with a grain of salt.

After three hours of light use, battery is at 87%, though I've noticed slight lag (could be me just getting used to ondemand instead of smartassv2 or it could be an Apex Launcher issue, since it's only present on homescreens).

EDIT: Notification vibration working for me as well.
[Verizon Samsung Galaxy S III] huwarrior:
So I took the plunge. Everything seems to work but I am not getting any 4G signal sitting at my desk where I routinely got full bars of 4G coverage on stock and Beans rom. It is just stuck on 3G. I already checked to be sure LTE was turned on.

Any deas?
[Verizon Samsung Galaxy S III] TheBiles:
I found that switching to the stock kernel got rid of the lag. I had horrible lag with KT747 and smartass2.

Sent from my Nexus 7
[Verizon Samsung Galaxy S III] WhammyDroid:
Is anyone seeing multiple sounds files listed when trying to pick a ringtone or notification? This would be for any sound sitting on the internal SDCard.

Edit: I am also seeing this with Apollo and Winamp. Mp3s are being listed more than once.

Edit 2: Reported to bug tracker: http://code.google.com/p/d2vzw-cm10-bugs/issues/detail?id=34&thanks=34&ts=1346424839
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
Not a deal breaker but I noticed a bit of noise when I'm on the call.. The noise that my wife used to hear I hear it now on my end.. Also when I answer a call like for a few seconds the caller can't hear me.. Echo seems fixed and the build is solid
[Verizon Samsung Galaxy S III] boynamedstacy:
Have you tried toggling airplane mode on and off ?

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] henrys01:
Same result here. I've called land line, ATT and VZ phones. No echo!
[Verizon Samsung Galaxy S III] ddurandSGS3:
new to CM10/other versions, but am i correct in assuming the motion controls from touch wiz will not work with this rom? (particularly smart alert)

also, what makes this official now? wasnt it unofficial before?
[Verizon Samsung Galaxy S III] eMpTy43:
Dirty flashed 8-31 this morning and after ticking NFC it greys out still and doesn't activate. Maybe tomorrow, wake me up when September comes... :silly:

Same here, sent 2 pics to the wife and she got them.

Same as someone already said, toggle airplane mode or toggle mobile data to restart your radios. Maybe a reboot/battery pull would help too.

I'm only seeing the usual 1 entry per file on both internal and external sounds. Try clearing your cache/dalvik and rebooting.
[Verizon Samsung Galaxy S III] thejron:
No NFC. sad day :(
[Verizon Samsung Galaxy S III] lxetuo:
That is correct, no touchwiz motions.

It's official in that there are actually nightlies now that are supported by CyanogenMod team. Unofficial ones are created by users outside of Cyanogenmod I believe.
[Verizon Samsung Galaxy S III] Hilbe:
Look 1 page back. AOKP's build for today *will* have it. Someone will most likely submit it to CM10 gerrit soon as well.
[Verizon Samsung Galaxy S III] alee:
There's got to be more to it than that.

All he's changing here is the location of the library. I made a copy of libpn544_fw.so and put it in the new location and NFC is still not enabled.

I/NfcService( 1062): Enabling NFC
D/NFCJNI ( 1062): Start Initialization
D/NFCJNI ( 1062): NFC capabilities: HAL = 8150100, FW = b1010f, HW = 620003, Model = 12, HCI = 1, Full_FW = 1, Rev = 15, FW Update Info = 254
D/NFCJNI ( 1062): Download new Firmware
W/NFCJNI ( 1062): Firmware update FAILED
D/NFCJNI ( 1062): Download new Firmware
W/NFCJNI ( 1062): Firmware update FAILED
D/NFCJNI ( 1062): Download new Firmware
W/NFCJNI ( 1062): Firmware update FAILED
E/NFCJNI ( 1062): Unable to update firmware, giving up
D/NFCJNI ( 1062): Terminating client thread...
W/NfcService( 1062): Error enabling NFC
[Verizon Samsung Galaxy S III] imablackhat:
I'm on 830 and so far so good. When you guys dirty do you just wipe cache and dalvik?

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] eMpTy43:
Yes, dirty is just the cache wipes and flashing the next nightly through recovery. A clean flash would be doing a factory data reset as well (which just leaves the OS on the phone, you have to re-install all your apps and configure your home screens/settings again.
[Verizon Samsung Galaxy S III] WhammyDroid:
Nope. Still does not work.
[Verizon Samsung Galaxy S III] lxetuo:
I sometimes format /system as well, not sure if it helps with minimizing issues or not. But if you do that, you'll need to re-install Gapps.
[Verizon Samsung Galaxy S III] ddurandSGS3:
damn. i really like smart alert.

still might give this a shot down the road though.
[Verizon Samsung Galaxy S III] WhammyDroid:
Also discovered I am unable to view pictures on the SDCard via Gallery.
[Verizon Samsung Galaxy S III] imablackhat:
Why are benchmark so much lower with this rom vs a stock rom. I'm scoring so low. What kernel do you guys use. The built in one?

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] codyvance:
KT747, allows OC, UV, 15 or so governors, and many more feature
[Verizon Samsung Galaxy S III] imablackhat:
Is there an app to control that kernel

Also do I have wipe anything to install it or can I just flash over?

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] codyvance:
It installs KTweaker automatically to control...

After you flash it, wipe cache/dalvik, fix permissions
[Verizon Samsung Galaxy S III] imablackhat:
Benchmark is just as bad went back to stock cm kernel. Reflashed cm10. I'm still like over a thousand below what it should be. On stock ics I was. Like 4400

Sent from my SCH-I535

---------- Post added at 04:33 PM ---------- Previous post was at 04:14 PM ----------

Also can't get Google wallet? Un compatible with device.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] niv3d:
Delete
[Verizon Samsung Galaxy S III] henrys01:
Antutu on CM10 usually delivers 8xxx score while stock rom 6xxx. I just tested mine and got 8005 with an untweaked CM kernel.
[Verizon Samsung Galaxy S III] eMpTy43:
What exactly are you benchmarking? With a ROM in development if your benchmark includes any features that are still in development will score extremely low, another possibility could be app functionality within a different ROM, certain apps I use hang a bit more on CM10 but still "work". Could be a possibility to your low scores, I'm not into benchmarking much though so take this with a grain of salt ;)

This issue is very strange... Anyone else on 8-31 experiencing issues with files on your internal/external SD???
[Verizon Samsung Galaxy S III] Version_3:
My 3G data drops every 2 minutes (timed multiple times with a stopwatch and measured drop to drop). Logcat attached with the drops happening (zipped due to it exceeding forum limits). This has happened for many nightlies now.

I have done a full wipe, a complete flash back to stock and then back to the latest nightly, tried both modems and tried to reseat the sim card. I do not get any drops on the stock I535VZWALF2 ROM.
[Verizon Samsung Galaxy S III] imablackhat:
I'm scoring please 2800-3000 vs stock 4400-4800

Sent from my SCH-I535

---------- Post added at 04:42 PM ---------- Previous post was at 04:41 PM ----------

I'm having no issues accessing things from my internal or external sd card. Thru gallery etc

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] awmobjects:
I'm around 7XXX using cm kernel.
[Verizon Samsung Galaxy S III] imablackhat:
I just scored 6043 stock cm kernel no tweaks. Umm with that app. I usually use a the other one.. So I guess I'm not alone.

Sent from my SCH-I535