yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Div033:
Thanks for the in depth follow up. I was pretty frustrated as I'm usually not the odd one out with issues, so my apologies.

It sounds like in call volume works perfectly for you. I have an idea for what's going on but I can't confirm it unless someone else comes along describing the same bug as I.

Samsung uses all sorts of different parts from several different companies to create the GS3. This means that they could make some phones with one type of ear-piece speaker and several others with one completely different. This could lead to the variances we see in people's experience; maybe the CM10 fix works well with your ear piece hardware (I actually don't know if the earpiece hardware would cause this, I'm more or less using it as an example) but still has some kinks on my differently branded earpiece speaker.

I guess for now I can live with the call volume at 3.

For those wondering, my in call volume does not stick when I choose one of the first 2 settings; the following call is max volume again. Curiously though, the volume setting does work when I leave it at 3 or higher. Super odd.
[Verizon Samsung Galaxy S III] wctaylor79:
So been looking through the pages and been searching XDA and other sites. It is a known issue with MMS picture quality when sending out, but seems no one has ever addressed this issue. Does anyone know a good fix? I know that there was a stand alone AOSP app made that had the fix. The issue is in the XML files of the MMS app, but seems that no one has addressed it for the official nightlies. Unfortunately I will admit I am dumb when it comes to editing XML files and can never seem to get it right. Any advice?
[Verizon Samsung Galaxy S III] Brian Gove:
Something is wrong with battery life lately on CM10. I used multiple nightlies and the m2 and I was consistently losing 12-17% overnight in good service area and I switched to AOKP yesterday with the same kernel I used on CM10 and same app setup and I lost 6% and had the same wakelocks even.
[Verizon Samsung Galaxy S III] alee:
It's not like they're sitting on their hands. I think people underestimate what is required to do a project like CM10. Let's remember d2vzw isn't the only release platform.
[Verizon Samsung Galaxy S III] glensta:
Good point

Sent from my Obsession
[Verizon Samsung Galaxy S III] nivanov:
Is MHL working OK on M2? I got the 11pin to 5pin adapter from Monoprice (product ID: 9716, sorry, can't post links yet) and the MHL adapter (product id: 8675) and I can't get any signal on my tv. MHL should just activate automatically when I plug in the phone, correct? No need to fiddle with settings?
[Verizon Samsung Galaxy S III] aatrek:
Is there a way to disable the CRT screen-off animation? It's really, really laggy on my GS3, even with animation timings turned down to 0.5.
[Verizon Samsung Galaxy S III] FryDay444:
Anyone else having Lightflow issues with the latest nightly? Does't work anymore for me.

Correction. It apparently doesn't work with the first boot. Reboot fixed it. My bad :-/
[Verizon Samsung Galaxy S III] aatrek:
Yup, it's giving me problems too.
[Verizon Samsung Galaxy S III] rfmodeler:
I use this feature every day and have only had to reboot a couple of times. I always get the metadata on my stock Toyota head unit. I'm on the m2 build still.
[Verizon Samsung Galaxy S III] FryDay444:
Try rebooting. It ended up fixing it for me.
[Verizon Samsung Galaxy S III] aatrek:
That only solves it temporarily - after about 10 minutes, LF just seems to... stop.
[Verizon Samsung Galaxy S III] FryDay444:
So far mine is holding strong. We'll see how long it lasts though.
[Verizon Samsung Galaxy S III] neyenlives:
i think i saw a thread here where others said the monoprice adapter doesn't work
[Verizon Samsung Galaxy S III] Imatoasta:
Yes I know that it takes a lot of work but I hold the CM team to a higher standard than all other ROM makers. I feel that they are so good at what they do that making the memory manager in cm10 scale to any amount of memory would be an under the hood feature first and foremost since they are dealing with so many different phones. We have this super bad ass phone with tons of RAM but it barely uses a 1/3 of it. I just want to know: why? Its super frustrating.
[Verizon Samsung Galaxy S III] SymbioticGenius:
To my knowledge this is the first phone with 2GB of ram to have cm. That might have something to do with it.
[Verizon Samsung Galaxy S III] khaoskosmos:
Would like to know also.
[Verizon Samsung Galaxy S III] cgulliver:
Same here but it's always been flaky for me on this rom.
[Verizon Samsung Galaxy S III] fix-this!:
Agreed 100%.
[Verizon Samsung Galaxy S III] alee:
Seriously? Again, d2vzw isn't the only build out there. d2vzw will be fully supported, but we aren't even in beta stage yet. You're asking for a new feature for the only 2GB phone available today.

Patience. I certainly home they're not wasting their time right now figuring that out when there's all sorts of loose ends to be fixed that affect things like battery life and stability.
[Verizon Samsung Galaxy S III] Imatoasta:
I KNOW they work on a million devices like I said. I'm just curious as to WHY a certain amount of RAM can't be used. They're using the Linux kernel and on a linux desktop the memory scales to however much you have but for some reason it won't go under 1 GB of free memory. It seems like its arbitrarily set you know?
[Verizon Samsung Galaxy S III] NegativeOne:
I feel like different kernels may handle this better.
[Verizon Samsung Galaxy S III] imp3r10:
The 10/24 version I was getting lots of GPS drops and probably an increase of data drops from previous versions.
[Verizon Samsung Galaxy S III] Jaegermeiste:
I don't know the answer, and since there don't seem to be any actual CM10 devs monitoring this forum, the only way to find out is probably to browse the source code.
[Verizon Samsung Galaxy S III] WhammyDroid:
Here's an idea: Become a developer, search through the CM repository, find the issue, and offer a better solution/fix it.
[Verizon Samsung Galaxy S III] mybook4:
Your point is valid and correct and frustration can be understood, however, let's be a little nicer to each other.

I am also interested in tweaking the memory manager to utilize more RAM on the GS3. Please open a thread in the general section that is more focused on this research. I'd love to contribute as I have an interest in the issue.
[Verizon Samsung Galaxy S III] ssmaster:
Does the new Sprint JB kernel release help at all for AOSP roms?
[Verizon Samsung Galaxy S III] Imatoasta:
Is this the generic XDA response for when somebody questions anything ROM related? Its seriously annoying when asking a legit question.
[Verizon Samsung Galaxy S III] fix-this!:
Im getting tired of these type of comments.
[Verizon Samsung Galaxy S III] TechSavvy2:
No, the xda responses were the first three answers offered that were actually valid. That particular response you quoted is what's offered when you yourself rejected all others before it.

Android does not manage memory like a desktop does. Cm builds for like 80 devices, of which 4 have 2 GB memory. Safe to say its on the back burner until more than 5% of devices utilize it.
[Verizon Samsung Galaxy S III] tv31284:
In terms of the memory manager, wouldn't this

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

help things? I used it on my old droid and thunderbolt and it seemed to run well. I haven't tried it on the s3 since we do have so much memory.
[Verizon Samsung Galaxy S III] fix-this!:
I dont think supercharger is needed on the sg3.
[Verizon Samsung Galaxy S III] mkasick:
What's the exact problem you're having? Do you have a means to reproduce it?

I don't see evidence of a limit on memory usage on d2spr. If I open enough programs, it uses additional memory accordingly.
[Verizon Samsung Galaxy S III] Div033:
Does anyone still have the speaker phone echo bug? That is, when using speaker phone the person on the other end can hear an echo of him/herself when speaking.

I still have it on a clean flash, but I also still have the in call volume issue.
[Verizon Samsung Galaxy S III] tv31284:
Well, like I said, I don't use it, but for those who are concerned about CM closing things too aggressively, wouldn't this be a temporary solution?
[Verizon Samsung Galaxy S III] Imatoasta:
I digress but whatever; I'm over it.

I noticed that even having 6 apps cached would lead to older ones being killed off so I tested it by opening every app I have and it never went under 1 GB of free memory. Im running LK, too. Have you seen under 1 GB free?
[Verizon Samsung Galaxy S III] mkasick:
I just tested running ten apps. None of their processes were killed. Using 1146 of 1630 MB, 485 MB free.

Do keep in mind that Jellybean runs on "512 MB" devices that actually only have ~360 MB memory available to the OS. Thus, most apps are written to be sufficiently memory efficient as to not blow their heap budget. In contrast, the d2 devices have nearly 5x as much memory available. Between that, and our heapgrowthlimit of 64 MB, you can have quite a number of apps open and still see lots of free memory.

If you really want to execise RAM utilization, you'll have to open multiple "largeHeap" apps. Good candidates are web browsers (e.g., Chrome, Firefox, Opera, etc.) with a few tabs open to different websites on each.

In terms of "making use" of the full 2 GB available to us, we do use the default xhdpi heap sizes, which are "tailored" for phones with 1 GB of RAM. That doesn't preclude the use of the full 2 GB (really, 1.6 GB) of RAM, but using larger heap sizes would allow apps to avoid garbage collection as often.

In any event I don't think that's something we're going to monkey with right now. We're a few days away from the announcement of the rumored Nexus 4, which if it matches the Optimus G specs will also be xhdpi and ship with 2 GB RAM. If so, we might see a new heap size profile in Android 4.2 and we can switch to that at that time.
[Verizon Samsung Galaxy S III] Imatoasta:
Thanks for the technical insight. This clears thing up a lot.

Another example: while typing this I have 4 apps cached in the recents menu (the apps menu says 11 though). I went back into dolphin and it had to refresh because it was killed. I don't remember stock being like that?
[Verizon Samsung Galaxy S III] fix-this!:
well this is the second time in a week my phone died overnight after a full charge. seems the cause is high cell standby. looks like im back to beans ics for now.
[Verizon Samsung Galaxy S III] jackpot08:
My Google music always does this anyone else?
[Verizon Samsung Galaxy S III] NegativeOne:
Yeah, mine does it too - only noticed it in landscape mode
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Keep getting gapps an Apollo music has stopped errors, any idea what causes that? I'm on cm10 build 25, stock cm kernel. Fresh wipe on m2 build an this is the first nonwipe install after m2

Sent from my rOot3d Samsung Galaxy S3
[Verizon Samsung Galaxy S III] d1ez3:
I'm getting tons of partial wake locks on latest nightly from media scanner and alarm. Media is taking up 49%of my battery. anyone else?
[Verizon Samsung Galaxy S III] NeWCuLTKiNG:
Disable media media storage in app manager fully charge reboot then enable again
[Verizon Samsung Galaxy S III] PerCompLLC:
Give it about an hour. As soon as the media scanning service finished scanning your partitions it will stop and all will be good.
[Verizon Samsung Galaxy S III] jmsdvs:
Has anyone had the problem of the sound going extremely low on the external speaker. Only way I can hear sound is if I put my ear up to it. This happened 2 weeks ago, then the sound came back for no reason for a day then went back to messing up. Thanks for any help.
[Verizon Samsung Galaxy S III] neyenlives:
As long as they didn't dumb it down to include memory gimped devices that are still considered high end with an S4 platform but only 1GB of RAM such as the HOX and International SGSIII.
[Verizon Samsung Galaxy S III] beaups:
1GB ram is hardly "gimped".
[Verizon Samsung Galaxy S III] jackpot08:
Is there any fix for the Google music hang up?
[Verizon Samsung Galaxy S III] d1ez3:
These are the partial wakelocks I'm getting with my screen off idle

EDIT: looks like it's doing much better after flashing lean kernel 1.6
[Verizon Samsung Galaxy S III] lchupacabras:
So the current nightly is unusable right? Is there one worth flashing or no?
[Verizon Samsung Galaxy S III] alee:
Been running it all day w/o issue... seems pretty usable to me.
[Verizon Samsung Galaxy S III] lchupacabras:
B b b but everyone before you said its nothing but trouble :(
[Verizon Samsung Galaxy S III] toddley:
Latest is working fine for me as well but a new build should be up shortly
[Verizon Samsung Galaxy S III] mike216:
I hope so I'm going to run CM for the first time on my new D2vzw
[Verizon Samsung Galaxy S III] littleneutrino:
I ran the 10/29 update via the updater and It got stuck at the boot animation, did a battery pull same thing. I ended up just flashing the zip file manually and everything came up. It was just strange. Thought I would post in case anyone else experiences this.
[Verizon Samsung Galaxy S III] goldsmitht:
Seems that everyone who has been having problems, have had it using the updater. I've been using TWRP, and dirty flashing, and never had a problem. I like bit, Cuz I can set my backup name so bit makes sense, and don't have to do the brain search trying to remember what day I backed up what
[Verizon Samsung Galaxy S III] JohnnyTToxic:
I'm pretty happy to note that the commits on 10-28:

frameworks/base: Fix for headset switch detect

frameworks/base: Add support for wired headset detection

frameworks/base: Fix for headset switch detect

Made all of my headsets work properly (Klipsch SIIA, Promedia gaming, Beats cable, knockoff chinese multibutton headsets), making it so that I don't have to use an app like Jay's Headset or Klipsch's headset app in order to get my mic and headset buttons to work as designed.

Previously there was an issue with the impedance values of certain headset buttons and the polarity of the microphone causing the galaxy s3 (and other phones) to not recognize the headset as having a mic (in the case of mic polarity in reverse of what samsung touchwiz expected) or not recognizing button presses (in the case of non-standard resistor values inline of the switch)

Big thanks to the CM team for fixing this issue as it bugged the hell out of me. Chuffed to bits.
[Verizon Samsung Galaxy S III] Restola:
My little recap of where we are the with latest nightlies.

-So it looks like some time recently the low-recording volume was fixed for videos, that's awesome.

-No call echo on normal calls.

-Skype is essentially unusable due to 100% echo back to who is calling.

-Youtube is watchable, but there are artifacts that flash when changing the volume.

-Battery is fine for me, no complaints compared to TW cleanrom.
[Verizon Samsung Galaxy S III] alee:
Try this... fixes the issue for me:

http://xdaforums.com/showpost.php?p=33177317&postcount=4989
[Verizon Samsung Galaxy S III] Restola:
That fixes the issue for me too, hoping a fix gets added soon to the nightlies so we dont have to edit files each flahs.
[Verizon Samsung Galaxy S III] mike216:
Awesome find! I'm just happy it works perfect!

Loving some CM! I tried AOKP and it was great but I prefer the options CM has opposed to AOKP
[Verizon Samsung Galaxy S III] fix-this!:
back on cm10, there's no way i can go back to ics after jellybean love. verizon is sending me a new battery so hopefully that may solve my issues. also trying the leankernel.

bah... the high battery drain is back after a phone call. i better use better battery stats to see what the deal is. i hope it's just a faulty battery.
[Verizon Samsung Galaxy S III] Zacharybinx34:
Skype and YouTube need fixed.
[Verizon Samsung Galaxy S III] Imatoasta:
Performance wise is it best to check or uncheck "disable hardware overlays" and "force GPU rendering"? I've always checked them both but don't know if that's best.
[Verizon Samsung Galaxy S III] pclever1:
Android 4.2 (Key Lime Pie)

I am running this rom right now but just a question:

Will this rom and updates (cm 10) cover 4.2 Key Lime Pie (if not is there a different bate place to go)?

Thanks
[Verizon Samsung Galaxy S III] jdhas:
Well, that didn't take long....
[Verizon Samsung Galaxy S III] bL33d:
How did they get video recording low fixed... I'm running latest aokp and everything is perfect but the low video recording.
[Verizon Samsung Galaxy S III] Restola:
No idea, I just noticed it worked for me on the last two nightlies. I looked back at some changelogs but couldn't figure out why.

VZW Galaxy S3 via Tapatalk
[Verizon Samsung Galaxy S III] Jay Evans:
Yes and no. 4.2 is still Jelly Bean.
[Verizon Samsung Galaxy S III] lchupacabras:
Seeing as 4.2 will be an incremental update (still JB) we should see it merged into CM10 shortly after its release.

In other news, I'm happy to report that this newest nightly is fantastic... not so happy to report, however, that the phone app is glitcby as all hell; especially switching from speaker and then back to headset. :/ It's nice to see them getting the bugs worked out but kind of disappointing that the main function of the device is lacking.
[Verizon Samsung Galaxy S III] jackpot08:
Same exact feeling.love it but everyone forgets it's a phone.speaker and switching to regular is a little wonk but otherwise great
[Verizon Samsung Galaxy S III] bL33d:
My phone was doing that on lk 1.6 but using kernel that comes with aokp the phone app works fine.
[Verizon Samsung Galaxy S III] lchupacabras:
This isn't AOKP...
[Verizon Samsung Galaxy S III] bL33d:
I'm aware just stating the kernel packaged with aokp works fine and that its the lean kernel causing the issue as it happened on aokp also when using lk 1.6
[Verizon Samsung Galaxy S III] kls629:
I havent updated my nightly over a month, curious if sound on video recorder was fixed?
[Verizon Samsung Galaxy S III] mybook4:
It would be much easier to buy a wireless router for less than $30 that will act as a repeater. Dedicated Router hardware is better at keeping a connection than phones (higher powered transceivers). If the signal is still too weak, ask a neighbor in the dorm that is closer to the access point to keep the extender in their room. Worst case scenario you lose a $30 router. Best case scenario you'll get to reuse the router for the next 5 years.
[Verizon Samsung Galaxy S III] trbman:
my college won't let you re-broadcast their signal. even if its encrypted. and even with a hidden SSID. I tried and they caught me.

Sent from my Galaxy S3 using the XDA App
[Verizon Samsung Galaxy S III] AtLemacks:
For those who have been asking about the video recording volume. I have been on 10/24 and had a big party this weekend, took a video walking through my house before it got really crowded and the volume was fine.

Not sure if anyone on here will be able to view the video, but here's the link. http://www.facebook.com/photo.php?v=10151323170861289
[Verizon Samsung Galaxy S III] fix-this!:
well i guess im stuck on m2. i tired all other newer versions of cm10 and aokp and i cannot get wifi to work after a reboot. really mind blowing for me. :(

i really hope this gets addressed, i reported this weeks ago on the bug tracker.
[Verizon Samsung Galaxy S III] rampantandroid:
Heh, people in one of the AOKP threads (not on XDA) just got done telling me this was an issue only

I

had. Try the KT747 kernel, fixed the issue for me.
[Verizon Samsung Galaxy S III] fix-this!:
already tried, doesn't fix it.
[Verizon Samsung Galaxy S III] mybook4:
That sucks. I downloaded the driver and read the readme file. Seems like a really simple, standard kernel module. It's super straightforward if you have a development environment set up (i.e. you can compile CM10).

I don't have one set up right now and am pretty busy. These instructions will help to get a development environment set up. I highly recommend doing this because it's a great learning experience. You could also ask a kernel dev to help as they pretty much always have a development environment ready (although you don't want to bug them, they're pretty busy).

You really only need the kernel sources so you can compile the drivers. Once you compile the drivers and have the asix.ko, you can just transfer the .ko and install the kernel mod (see readme file for details) on your existing ROM in terminal as root (I don't believe you don't need to flash anything new to your phone or build CM10 entirely from source, just the kernel module).
[Verizon Samsung Galaxy S III] drdagreenphd:
I know this won't sound too appealing, but try flashing a stock(rooted) touchwiz rom. Allow it to settle for about an hour or two, then (clean) flash back to CMX or AOKP. This may resolve your issue.
[Verizon Samsung Galaxy S III] fix-this!:
trust me man ive spent 3hrs on this with no resolution, i even odin back to stock and started over. as ive said numerous times alot of people are having this if you search the net, not just on the gs3, multi-device with jellybean/aosp.

i dunno what i did to get wifi to work on m2 but i cannot duplicate my positive results an any of the other aosp roms. aokp, cm10, slimbean and even eclipse.

it's even being talked about here on the google bug tracker: http://code.google.com/p/android/issues/detail?id=34212
[Verizon Samsung Galaxy S III] beaups:
WiFi is a mess on many custom ROMs and kernels. If you can't deal with it just go back to stock.
[Verizon Samsung Galaxy S III] trbman:
i'll try this weekend. Thanks!

Sent from my Galaxy S3 using the XDA App
[Verizon Samsung Galaxy S III] fix-this!:
who was complaining? im looking for resolution. stop taking bug reports soo literally.
[Verizon Samsung Galaxy S III] beaups:
I didn't state you were complaining. Not being negative either. I've flashed umpteen ROMs and they all have issues. Big one being borked WiFi. For me, stock it is (sadly).
[Verizon Samsung Galaxy S III] fix-this!:
sorry just frustrated. soo weird only certain people are having this and not everyone.
[Verizon Samsung Galaxy S III] TechSavvy2:
Have you gone elsewhere and tried other WiFi networks? Every time you bring this up it sounds like router/security issues or incompatibility. WiFi network security settings do change as builds go on....
[Verizon Samsung Galaxy S III] mike216:
New lean kernel out you might wanna try before the nightlies and it's a monster!
[Verizon Samsung Galaxy S III] Nnyan:
I had some time so i dirty flashed the first 4 JB roms i found and wifi worked fine connecting to 4 routers and 2 phones as APs. Was hoping it would fail so i could document what worked.

Now i have had wifi issues in the past here are some things i recalled.

I assumed you disabled all security and such? Tried it with phone close to router? Change your SSID to something completey different? Tried various channels? Tried flashing diff firmware?
[Verizon Samsung Galaxy S III] danstar:
Something I noticed with my phone and wifi. Back before I rooted and unlocked the bootloader, I could connect to routers that were wireless G with no problems. As soon as I tried to connect with a router that was wireless N, it was a no go, or an unstable connection. I still don't know w hy this was the case when the specs say it is compatible with wireless G and N. Just a suggestion for all the people reporting wifi connection problems, they may want to check what version of router they are trying to connect to.
[Verizon Samsung Galaxy S III] dreDrennon1:
I love this Rom
[Verizon Samsung Galaxy S III] bluezr1:
Is there a way to bring up the close "all" recent apps after holding down the home button, instead of closing each one out individually?

I was on liquid's rom where I was able to set it up this way, although I'm not sure if I just can't find it or that it doesn't exist on this rom.
[Verizon Samsung Galaxy S III] fix-this!:
cant be router related as the people i have spoken too have different routers with the same issues. IF it is my netgear i guess they can send me a new one lol. seriously my wife's razr running ics works fine. beans rom works fine, jellywiz works fine. see my point. i guess since this only effects a few dozen people "from my search" it will never be rectified.