yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] gregurbo:
If your speakers are tiny, get some new ones!

Sent from my SCH-I535 running CM10 :)
[Verizon Samsung Galaxy S III] aeroevan:
Did you Odin back to an ICS ROM? There seems to be issues coming from JB leaks to cm10 for NFC.

My linaro build has some new msm_fb kernel code and updates to the display Hal that seem to have fixed the display being off but keys lit for me, but I've only been testing for a day.
[Verizon Samsung Galaxy S III] sivarticus85:
Does the cam still have low recording volume?
[Verizon Samsung Galaxy S III] EGill42:
The ROM I used Odin to back to was indeed an ICS ROM. It should have been the ROM the phone shipped with. Perhaps I will try this again when I get a chance. Just curious, what does it mean to say linaro build? I have seen that term pop up before.
[Verizon Samsung Galaxy S III] antiseen:
Bluetooth still has no bass until you make a call then hangup. Confirmed.
[Verizon Samsung Galaxy S III] ddggttff3:
Anyone else with NFC not turning on in the latest nightlies? I might just need a full data wipe as its been a week of constant nightly updates.
[Verizon Samsung Galaxy S III] vincatzero:
I don't get dock audio o out of the Samsung Infuse car dock. I have the setting turned on. Is therea compatibility issue with this dock?
[Verizon Samsung Galaxy S III] Argent36:
I'm pretty sure USB audio hasn't ever worked on CM10 yet - but I could be wrong - I haven't tried using it recently since it didn't work before...
[Verizon Samsung Galaxy S III] NegativeOne:
I'm starting to agree with a previous poster - this ROM is getting worse and worse. Nov has been a terrible month. I think the problem is, nobody is working on the d2 branches, so when the trunk gets updates, they break stuff in our branch and nobody ever fixes them.

If you look at the checkins, they are mostly on recovery, and like.. infuze?
[Verizon Samsung Galaxy S III] mastamoon:
I have audio out using the Infuse 4G desktop dock working right now on a 11/23 build. To get it to work, I had to go into Advanced -> Sound and check Use Dock USB Audio.
[Verizon Samsung Galaxy S III] Argent36:
yup - this worked as well for the desktop dock I have
[Verizon Samsung Galaxy S III] M Diddy:
This. You don't see any fixes being put in place for the d2vzw. The majority of fixes going into the nightlies are CM related things. Recovery, File Manager, etc.

I'm hoping once the JB kernel source gets released (come on VZW! :mad:) we'll start to see some fixes to our branch.
[Verizon Samsung Galaxy S III] littleneutrino:
Ever since a week or so ago when they re-added the option USB Audio has worked without issue on the Official Samsung Desk Dock however, there is a comparability issue with the car dock (as it has some functionality built in that requests the phone perform some action when connected) due to that it is broken currently. I do not know the details as to why it does not work I just know that it has been a known issue for a long time.
[Verizon Samsung Galaxy S III] julesism:
Yea, I'm still on a nightly build from 10/29. I try other ROMs but always come back to CM. Hopefully December will be a better month for us :)
[Verizon Samsung Galaxy S III] TechSavvy2:
My guesstimate......they're not working on fixes to cm10 for d2 devices, nor will they. But I have a sneaking suspicion its because of cm 10.1 (4.2 merge). Why fix stuff that's just gonna get re-broke with 4.2? I kinda wonder if that's why they had the big "stable" release the day before 4.2 dropped. I will admit, that build was a winner.
[Verizon Samsung Galaxy S III] cordell12:
You won't see many changes to the device tree. Fixes for our device are under d2-common, qcom-common, qcom-display/audio, and msm8960-common.

These repos effect all US GS3, the project is headed mainly by Steven, aka Cyanogen himself.

Forgot kernel, kernel-samsung-d2.
[Verizon Samsung Galaxy S III] Breezer23:
Not sure what you all are complaining about, seems pretty functional to me on the 11.24 release
[Verizon Samsung Galaxy S III] peaceofpi:
Search NFC flash fix on this thread. It's a simple zip you flash and all is gummy bears and rainbows.
[Verizon Samsung Galaxy S III] StrumerJohn:
NFC not working, Blue tooth Media sound borked, Force Closes, Lag, Random Reboots, Horrid battery life - - That kind of stuff. On 11/24 as well.
[Verizon Samsung Galaxy S III] Breezer23:
I spoke too soon anyway lol.
[Verizon Samsung Galaxy S III] gts24:
bout ready to tap out for awhile and go to something else for a bit... same thing
[Verizon Samsung Galaxy S III] Trumps:
Well, he should grow some thicker skin and not take it personally, because people post about what's not working so others can decide whether or not they can live with the latest set of bugs and caveats.

You know what's really annoying? People being disingenuous and posting about how awesome a buggy rom is. That's ultimately what the problem is here, folks. People clamor over how amazing CM10 is and throw five golden stars and rave reviews everywhere, others read this, take the time to blow their phone up with a set of great expectations, and then immediately find several very annoying deal-breaking issues. I personally carry a stock and reliable second phone (iphone 5!) so a bad nightly doesn't ruin my day, but I can see how incredibly frustrating the regressions are for others when they rely on false input from people who flat out lie about how great the rom is.

The fact is, you have two groups of people here: Light users and power users. Light users should not be commenting on how amazing everything is. Users who live in notoriously reliable signal-rich areas (like me) should not be commenting on how stable the radio or data connections are. I traveled with my phone last week to a different part of the country and was mortified by how poor the data connectivity was in a spotty area.

Let's face it: The d2vzw CM10 has been consistently and extremely broken since the first nightly. There were a few good builds and it really showed promise, but I feel that if I hang on any longer I will become that battered wife who hopes my abusive husband will change.
[Verizon Samsung Galaxy S III] PVLMTREE:
I got a quick question, is there any way to set Network Mode to "global" perhaps? I don't think CM10 nor AOKP has this function.
[Verizon Samsung Galaxy S III] Div033:
For me, CM10 is more stable than touchwiz! I keep this note on my phone and am constantly editing it, but let me paste it for you all:

Touchwiz VS. AOSP

Touchwiz:

- No Bluetooth and Aux input simultaneously

- No way to disable auto volume reduction upon headset plug-in

- Google Music will randomly stop working, requires screen to be turned on for it to start playing the next track (If on JB leak, music sometimes switches to external speaker from aux when changing track)

AOSP:

- Low recording volume

- Acts as if it only has 1GB of RAM

- Hot reboots every once in a while

I use this list to help me decide if I should run TW or AOSP. Currently the touchwiz bugs affect me more negatively than the AOSP bugs, so I'm on CM10. I don't use Bluetooth for music though, just for phone calls. I suppose things might be different if my car supported it!

As far as performance and battery life goes, its about the same as what I got on stock.
[Verizon Samsung Galaxy S III] seang:
agreed.

personally i get tired of people using a "nightly" build and expecting it to be 100% functional. posting bugs is one thing, but, full on complaining about the bugs not being fixed fast enough is just ridiculous.

please, go jump on a TW rom.
[Verizon Samsung Galaxy S III] Trumps:
Nobody expects nightlies to be even remotely perfect. A lot of things are broken in the 10.0.0 stable build. A LOT.

Frankly I'm just tired of people talking about how awesome CM10 runs on the S3, thereby raising everybody's expectations. They use a whopping 3 features in the phone for 5 minutes and suddenly they're ready to personally certify it as stable. People read their comments and then install CM10 and are disappointed. Then they install every nightly with the hope nagging issue X is fixed, and then 5 more issues appear, meanwhile issue X is still not fixed months later. At that point they become dependent on CM10 for additional features that DO work, so switching back to TW seems like a step backward, even though it's a step forward from a reliability standpoint.
[Verizon Samsung Galaxy S III] softwarestealer0:
From the cyano g+..... Looks like 10.1 is booted on the gs3...Apparently it's not really usable yet... Soon soon
[Verizon Samsung Galaxy S III] MrBrady:
Curious, can you expound on this? AOSP doesn't take full advantage of our RAM?

Been running CM10 stable for about two weeks now. Pretty rock solid except for when I screw things up by trying to tweak it a little too much with kernel tweaks or V6 supercharger changes.
[Verizon Samsung Galaxy S III] tcsac:
This is literally my exact experience. I'm kicking myself for not just going with a galaxy nexus at this point and instead listening to the people in these threads painting such a rosy picture of how great CM10 was/is on the S3.
[Verizon Samsung Galaxy S III] Slacker101:
Eh I have both and honestly ignoring that the nexus has 4.2 now, most things work on the s3 pretty damn well. Well enough that I use it as my normal phone with CM10 since the battery life is so much better. Basically comes down to battery life > 100% stable to me.
[Verizon Samsung Galaxy S III] bluezr1:
I don't understand why anyone is complaining. If you want a phone where everything works, then buy a phone and keep it stock - problem solved.

I recently came from the Evo 4g where half of the time there wasn't even a working camera. And forget about the front facing camera or 4g, neither one of them has worked for about a year now, that is unless you wanted to go back to a GB rom.

For what I use my phone for this rom has been pretty solid. I don't use Bluetooth or record videos, which seems from what others are saying, are causing some problems. Although even a completely stock phone will have problems from time to time.
[Verizon Samsung Galaxy S III] Ryphez:
Hey guys,

I have been trying to debug why my System UI keeps crashing and I have a logcat which is located http://pastebin.com/UpV679vM. I think the crash occurs around "Process com.android.systemui". Anyone have any tips or ideas? I just did a clean flash of the 11/25 nightly. Thanks in advance

Edit: I haven't applied any themes or anything also
[Verizon Samsung Galaxy S III] Div033:
I'm not sure on the technical side behind it but basically on AOSP, the system is much more aggressive with closing apps running in the background. This isn't a huge deal but is just slightly annoying to have to reload apps during multitasking when you know full well that your phone has enough RAM to have kept them running.
[Verizon Samsung Galaxy S III] PVLMTREE:
CM10 compatible with other carriers?

I'm currently on CleanROM 5.0 using T-Mobile and every function works.

Will there be any compatibility with CM10? Because I had no luck at all. I hope for a quick fix soon!
[Verizon Samsung Galaxy S III] iofthestorm:
That's the i9300 which is completely different. But I don't expect the US versions to take much longer as up till now the US versions have had better support in CM10 than the Exynos packing international version.
[Verizon Samsung Galaxy S III] neyenlives:
this...contrary to what the International guys will try to tell you.....the Qualcomm based US version is actually better supported. I have been reading an increasingly large number of devs upset with Samsung over their proprietary BS. Not that Qualcomm is entirely open, they aren't, but they are widely adopted compared to Exynos.
[Verizon Samsung Galaxy S III] neyenlives:
This +1. There's actually an app that you can use, System Tuner, along with a custom kernel, to adjust those kernel level memory settings yourself. The "out of the box" CM kernel probably won't ever be tuned to run optimally on a 2Gb ram device because it has to be able to run on devices with as little as 512Mb of ram also. It's one of the drawbacks to having a "one rom for all" solution.
[Verizon Samsung Galaxy S III] tcsac:
My wife has a nexus. battery life is the same and she doesn't have all the weird broken ****. I listen to audio in my car daily, having to turn off bluetooth and turn it back on to get it to connect combined with the ****ty sounding music until I make a call is EXTREMELY annoying. And her battery lasts an entire day of use, not sure what more you're looking for. Either way, it's pretty easy to buy a higher capacity battery for the Nexus. I can't just order non-buggy firmware off Amazon.
[Verizon Samsung Galaxy S III] NegativeOne:
So which kernel are you using?
[Verizon Samsung Galaxy S III] funkdoctor:
Glad someone finally said something. People are a lot more forthcoming about the issues with AOSP and the S3 over on Reddit, so I hope the Cyanogenmod people at least read over there. There is a lot less of the "Well I don't have that problem, it must not exist!" over there. I'm thankful for all of the work that Cyanogenmod put into their ROM, I just don't think it helps when people pretend problems dont exist especially when you can jump onto any of the Android forums (XDA, Rootzwiki, etc.) and see people complaining about the same ****. The stable build wasn't that stable. The nightlies are worse - hopefully they get better over time.
[Verizon Samsung Galaxy S III] seang:
reliability or bleeding edge, pick one. you don't get both. ever.
[Verizon Samsung Galaxy S III] NegativeOne:
Your post is useless, counterproductive and misses the point. I don't know a nice way to put it.

Once more, for the cheap seats: The issue is that new bugs are being added by trunk checkins that break stuff in d2, but there are no commits to the d2 branch that seek to address any of them. We haven't had a "stable" build of CM10 for d2 yet. And arguments like "well go use something else" have NO place in this thread. We are here to discuss issues with the nightlies. If you don't like it, don't read the thread. If you're perfectly happy and everything works for you, then I honestly have no idea what you're doing reading this.
[Verizon Samsung Galaxy S III] ddgarcia05:
I tried the stable roms and the only bug I found was when I was listening to a podcast via dog cather on the speaker and received a call it would route all sound to the ear piece even after the call. Other than that I didn't play around with the build to much. Since then I have gone back to the shipped ICS rom and re locked my phone. I do believe it's very hard to have a truly bug free rom even when built on stock and I felt the stock (touchwiz) experience was more reliable for my everyday use of the S3. I appreciate the work that the CM team have done and have donated to them and other rom makers in the past. I know a time will come when I re root my phone to play with the latest and greatest roms. I like what the other member stated above about posting small bugs that are found on the rom because many people do read the forums and decide based on what we post if they should root their phone.
[Verizon Samsung Galaxy S III] neyenlives:
At the time I saw the options available I believe I was on the KT747 kernel. Don't hold me to that, I've tried them all.
[Verizon Samsung Galaxy S III] Trumps:
Thank you!

Quoting in hopes people will read it if they missed it the first time.
[Verizon Samsung Galaxy S III] seang:
as i stated earlier, bug reports are fine. lets do that. please. lets NOT complain about the rate at which they get fixed.

complaints about free software are what are counter productive, and have no place here.
[Verizon Samsung Galaxy S III] AtLemacks:
What Nexus does she have because my GNex sure as hell doesn't last anywhere near as long as my GS3.
[Verizon Samsung Galaxy S III] MrBrady:
I believe the latest Multitasking Mod from V6 Supercharger / Zeppelinrox tries to correct this behavior:

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

From the post:

Mod 1. Jelly ISCream for ICS and Jelly Bean. This will SuperCharge Your Home Launcher and ADJ/OOM Priorities! Bonus: You pick launcher strength! There's some info on that here.

Mod 2. Maximum MultiTasking Mods for Froyo and above has 2 parts.

a. -=Maximum Overdrive=- This lets you run up to 70 hidden apps instead of the default 15 (RAM permitting) without breaking the lowmemorykiller!

Why only 15 by default? See the google groups link in Post 2

b. Time Killer Killer. This tries to bypass the 30 minute service inactivity limit by increasing it to 24 hours ;^]

Huge thanks to dorimanx from XDA Forums for ideas and the initial mod to bypass the lowmemorykiller for greater multitasking

Mod 3. Non-Sense App Limit for Sense 4 and above (Not needed for Sense 3.6 and below).

This eliminates additional restrictions introduced with Sense 4.

a. Visible tasks increased from 8 apps to 50 (RAM permitting)

b. Something called "HTC Recent App Fusion" is rendered a non-factor.
[Verizon Samsung Galaxy S III] Div033:
Y'know, I tried system tuner way earlier and it didn't do squat. I probably didn't have a custom kernel installed.

However, now that I do (lean kernel) its working wonderfully. Just one more issue to erase from my AOSP-TW issue comparison! For my uses, AOSP now has less issues than TW. Looks like I'm here to stay.
[Verizon Samsung Galaxy S III] coldhardtruth:
Has 4.2 been implemented into cm10 or on any ROM yet?
[Verizon Samsung Galaxy S III] AtLemacks:
Yes, but not for our device. But it is moot because 4.2.1 was released today and CM is merging it in the builds. Last I had seen on G+ booting 4.2 (CM10.1) on D2VZW was absolutely unstable.
[Verizon Samsung Galaxy S III] Ryphez:
I posted earlier about System UI crashing and have found what seems to be the main error I it.

" E/overlay (283): Failed to call ioctl MSMFB_OVERLAY_SET err=Operation not permitted"

Any ideas?
[Verizon Samsung Galaxy S III] cvo515:
Who are you following there?
[Verizon Samsung Galaxy S III] PerCompLLC:
Follow +CyanogenMod
[Verizon Samsung Galaxy S III] sweeds:
Is there any HWA with this ROM, is it possible to achieve on our phones? From what I know, this is affected by the kernel, correct?
[Verizon Samsung Galaxy S III] cvo515:
I do. But didn't see anything with d2vzw. Maybe I missed it.
[Verizon Samsung Galaxy S III] PerCompLLC:
Go to CyanogenMod on G+ and scroll down. It's about the 5th or 8th post down (more depending on when you check).
[Verizon Samsung Galaxy S III] ned4spd8874:
Are there any plans to add a tethering (usb or wifi) toggle to the notification area along with the others that are available now?
[Verizon Samsung Galaxy S III] Imatoasta:
You can already do it.
[Verizon Samsung Galaxy S III] ned4spd8874:
Where? I've looked at the available toggles and don't see it.
[Verizon Samsung Galaxy S III] Deevious88:
Settings -> System -> Notification Drawer -> Widget Buttons

"Toggle Wi-Fi AP"
[Verizon Samsung Galaxy S III] ned4spd8874:
Ah, yes, sorry about that, thanks!. How about the USB tether though?
[Verizon Samsung Galaxy S III] revolt1:
I've been looking for a solution on why I get screen flicker while in navigation and how to correct this
[Verizon Samsung Galaxy S III] jakereeves31:
Do you have the flicker on Liquidsmooth or here? Cause you posted about it in both threads
[Verizon Samsung Galaxy S III] revolt1:
there in both tried them both
[Verizon Samsung Galaxy S III] MrBrady:
Running CM10 stable w/ the latest V6 supercharger and Lean Kernel 1.10.

Anyone else have issues with the dialer?

Earlier today I received severe lag when using the dial pad during a call. Only remedy was to reboot the phone. I think it turned out to be an issue with the theme because after revering to the stock theme, the problem seemed to go away.

Also, I was on a two hour call (I rarely use my phone for an actual phone) and after pulling the phone away from my face to hang up, it was unresponsive. Screen didn't turn on and buttons didn't do anything. Had to hold down the power key for a period of time until the phone rebooted.
[Verizon Samsung Galaxy S III] TechSavvy2:
Sorry dude, but this is probably one of the larger loads of sh*t I've read on here. The problem isn't people reporting feature x or y doesn't work. That's productive and what the thread is all about. The comments you're defending of "this ROM sucks ass and I'm leaving!" do absolutely nothing. You really want to get into power user status? Read the damn thread and you wouldn't even have brought it up. I utilize every feature my phone has to offer on every build. Updated nightly, from a fully clean install. 16 hrs of use, BT streaming while on 3 hrs of GPS guidance in and out of service constantly. Need I go on and on here? The ROM works for me. I'll post an effin video of it running fine if it shuts you up about it. I'm posting that it works for me because guess what? It DOES work for me.

What I don't understand is that reading the hate mail in here, a lot of people seem to be getting the " this ROM sucks ass, doesn't work, is getting worse, nothing is being done about it, I'm effin angry and not putting up with it anymore!" type of attitude. What I don't understand is why you're still here?!?! I don't go filling up another thread about all the bugs it has and demand that I deserve better or that people shouldnt defend the ROM features that work for them and show support for the ROM. That's why I just leave and go back to what works. You have a problem with it, ask for help. What's up with the "we shall rise up against cm because they owe us" mentality?

If a feature does work for one person, and not for another person, do we say it works or that it doesn't? Should we say that it just doesn't work, and it is a magical miracle that made it work for some people? Or is it likely that something went wrong somewhere along the lines? Maybe bad install. Maybe someone needs a clean install. Or system formatted. Or multi-wipe performed?

I feel the last few pages tell new users that they basically should 100% walk away from this ROM. There seems to be problems with people getting false hopes? Because things work for me? In your point, you seemed to be doing exactly exactly what you preach against.

You have that big of a problem with cm10? Walk away, its not worth the trouble.
[Verizon Samsung Galaxy S III] PerCompLLC:
^^ This^^

Quoted because it bears repeating.

(Please note that I have yet to do a clean install since the earliest days of CM10 - problems have been minimal for me - luck/magic has nothing to do with it)
[Verizon Samsung Galaxy S III] RED ZMAN:
Okay ladies, you're all beautiful. Can we get back to the task at hand?

Namely, is anyone having a problem with video in full screen not having any control anymore?

LOL

Blasted from my Samsung Galaxy SIII (CM10).
[Verizon Samsung Galaxy S III] iofthestorm:
Same here. Also NFC works perfectly for me on the latest nightly just so that it's clear (I think it was broken somewhat recently and after it was fixed some people mentioned still having problems).
[Verizon Samsung Galaxy S III] ddggttff3:
im having the strangest issues with NFC. its currently NOT working on my GS3 with the latest nightly, yet my friends black GS3 has no issues with it. I even flashed back to stock, turned NFC on, and went back to CM10. Still no NFC. Any ideas?
[Verizon Samsung Galaxy S III] abreeden:
I had no problems EVER with anything dirty flashing since August until that one day NFC just tanked.... it took me 2 tries to get it back. going back to stock TW then CM10 (failed) and then again a second time (worked!)

Then it was immediately gone again when i flashed my next nightly. i dont feel like dealing with it daily, so i think i will just get it going again and stand pat on nighlies until the 10.1 release and then just wait for major updates. these nightlies are so hit or miss lately. i do however have some VERY good battery life (for me at least / 17hrs w 3.5hrs screen on time)
[Verizon Samsung Galaxy S III] landale:
So I have system tuner installed but can't figure out what I am supposed to change. Any suggestions on what to do to improve RAM use?