yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Defragger51:
Am I the only one having GPS lock issues. It usually take me between 5 and 10 minutes to get a gps lock and sometimes it takes longer, happens even after a reboot, to try and fix the problem . If I get a gps lock it is off by like 100 ft or more and usually goes up in distance not down. I have been having this problem ever since the 9/12 build and I have done clean installs and full wipe installs and continue to have the same issue . I am currently running 9/23 since 10am and still have the same problem. Today I had 24 satellites in view and 16 satellites in use, with GPS test and still have No gps lock. Is there any kind of GPS fix available
[Verizon Samsung Galaxy S III] manywelps:
Try a custom gps.conf.
[Verizon Samsung Galaxy S III] rgrossie:
Try FasterGPS from play. You can choose your location and it builds the gps.conf file for you. It fixed mine, now my lock is almost instant, although not as exact as I'd like it to be. It's good if I'm moving (in the car for example), but indoors it's just so-so. The stock Touchwiz GPS was amazingly fast and accurate, even indoors. I'm guessing this will get there but not yet.
[Verizon Samsung Galaxy S III] vdefender:
I know its been mentioned before, but maybe you missed it, or you are doing this and its still too loud? But when you're in a call have you pulled the phone away from your ear so the screen turns on, then click the volume up bottom until its full volume, then click volume down until its all the way down? When I do that it gets really low and works fine for me. Sometimes I have to actually turn it back up because it gets too quiet. I only have to do that the first time I get or make a call on a fresh reboot.
[Verizon Samsung Galaxy S III] TechSavvy2:
This is what I usually do but absolutely can't stand having to do it on every single phone call every day.
[Verizon Samsung Galaxy S III] jmill75:
Being that the phone is for work, i receive way to many calls throughout the day to mess with this. Ive tried believe me. I just cant believe this bug has been around this long.
[Verizon Samsung Galaxy S III] AlexDeGruven:
If you NEED your phone or a specific function, don't run pre-release and alpha software on your phone. It will only cause you heartache.

---------- Post added at 06:40 AM ---------- Previous post was at 06:39 AM ----------

it's been 2 months, and it's being worked on by volunteers.
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Could you use a bluetooth? I use a BT on my phone for 95% of the calling an never have a problem with the volume. I understand if work don't want you using a bluetooth, just a thought.
[Verizon Samsung Galaxy S III] elreydenj:
Could you share your kernel/radio and any other tweaks that may affect things? I am plagued by this issue of the echo while on speakerphone. Rom is very solid other than this. I am desperately looking for a way to change the mic gain or speaker volume. Thank you.
[Verizon Samsung Galaxy S III] mybook4:
Running about a day on the 9/23 nightly. Excellent so far.

I did notice the call volume being high but I actually love that (don't have to press the phone firmly against my head just to hear someone).

Usb analog audio / dock mode didn't work, but that's a known and documented bug.

Battery life seems comparable to TW ICS roms (I've ran Bean's and Synergy previously).

Custom notification LED options seem to work well (and are a great feature).

Haven't tested 3g dropping that much as I'm in a strong 4g area (thankfully).

Speakerphone worked well, but I noticed that the microphone on the top of the phone (near the headphone jack) was being used rather than the correct one on the bottom (near the usb port). Although I didn't experience echo, this may be contributing to the echo others have experienced (the top microphone is much closer to the speaker than the bottom microphone.

I did notice that the free memory never drops below 700MB (seems like the kernel could utilize more to be efficient). I have run a nightly since 9/4, so I could not be up to speed on this (or how to adjust it). Does anyone have any info on this?
[Verizon Samsung Galaxy S III] chetqwerty:
There is a new-ish setting under location settings gps source you must check internal.
[Verizon Samsung Galaxy S III] Droosh:
My GPS gets a fix in 2 seconds indoors. Connected to 16/21 satellites as well. Only tweak I've done is use the GPS Status app. In it you can reset and upload new A-GPS XTRA data. This might help you.
[Verizon Samsung Galaxy S III] cgulliver:
Built with zcache this morning and also has SIO scheduler now. Both great additions.

btw - has anyone attempted to use the DSP Manager to band aid the call volume issue until its fixed?
[Verizon Samsung Galaxy S III] sanjsrik:
To be MUCH more specific:

Go to WiFi > Advanced WiFI > Wi-Fi region code, make sure you select the country where you live.
[Verizon Samsung Galaxy S III] seang:
you are using the wrong ROM.

this is in the "Original Development" section.

you want a 100% stable build, go back to stock, or find a TW rom.
[Verizon Samsung Galaxy S III] Defragger51:
Thanks I could not find FasterGPS but I did find FastFix for gps and my lock is a lot faster now but no more accurate, I also check every time to make sure internal gps is checked and I have used GPS Status. with faster lock but accuracy still over 100 most of the time. the lowest it has gone is 52, I use to get 9 and 13 ft all the time until after the 9/12 build
[Verizon Samsung Galaxy S III] MG386:
Make sure you clear cache and data from maps if your location is not accurate..
[Verizon Samsung Galaxy S III] Jedis:
Is there anyway to enable the charging LED? Mine doesn't work ever since flashing any of the CM10 nightlies. Is it broken? Other notification LEDs function.
[Verizon Samsung Galaxy S III] rfmodeler:
That's a different setting than what the other poster was talking about.
[Verizon Samsung Galaxy S III] nfamouswun:
im on cm10 9-20 with google wallet working. everything is working fine for the most part. NFC stopped working one day. rebooted the phone and it was back.

how should i go about flashing newest and future nightlies?

do i just dirty flash the newest nightly? do i have to flash the nightlies i missed in order until i reach newest? (im a little new to the nightly builds of cm. i usually stick on one build or hop to another rom then restart and go back to another nightly months later, this was during my dx days.)

do i wipe data/cache/davlik when flashing nightly?

do i re-flash gapps?

will i have to disable g-wallet and set it up again?

sorry for the questions. im just paranoid about messing everything up when im so close to having it perfect the way i want it. (just looking to flash newest nightlies for more stability)
[Verizon Samsung Galaxy S III] SeanFloyd:
GPS not currently locking. And keyboard "swype beta" cannot keep up with text... any known fixes? Also probably a stupid question but is data wiping supposed to be done before or after installing new Rom?
[Verizon Samsung Galaxy S III] rgrossie:
See above in Red for specific answers to the best of my knowledge.
[Verizon Samsung Galaxy S III] scriz:
9/24 is up.
[Verizon Samsung Galaxy S III] Marcismo55:
After you reboot to recovery to make your backup prior to flashing the newest nightly, reset wallet and then boot back to recovery to do your necessary wipes and flash your latest nightly. n You will need to start from scratch because the build.prop edit you made will be overwritten by flashing the new rom.

This is the safest way to do it to avoid having any issues with Wallet.
[Verizon Samsung Galaxy S III] kls629:
i heard jelly bean is being released in europe already, anyway we can snatch something from them?
[Verizon Samsung Galaxy S III] TechSavvy2:
Potentially some driver cleanup. But RIL won't be fixed until vzw jb drops (or they figure out how to fix it independently)
[Verizon Samsung Galaxy S III] pchoi94:
Does that include the sound volume levels for video recording? Last I tried this ROM it was very low compared to stock, which was the deal breaker for me... thanks!
[Verizon Samsung Galaxy S III] elreydenj:
Is there any way around this microphone/speakerphone issue. This makes perfect sense that it would cause an echo as the voice of the person you are talking to would come right out of the top mic and go right into the top speaker. The echo problem is very bad.
[Verizon Samsung Galaxy S III] mybook4:
I'm not the most knowledgeable person on the subject, but I believe it would be a kernel related issue. If I'm mistaken someone please correct me. One of our local kernel devs may know for sure.
[Verizon Samsung Galaxy S III] elreydenj:
Can someone suggest an aosp kernel that may fix this issue?

---------- Post added at 04:57 PM ---------- Previous post was at 04:56 PM ----------

What kernel is everyone using that does not have the other person experience an echo when you put them on speakerphone? Please provide some suggestions. Thank you.
[Verizon Samsung Galaxy S III] AlexDeGruven:
If there was one that fixed it, everyone would be recommending it. As of now, there isn't a fix.
[Verizon Samsung Galaxy S III] Ryphez:
Hey guys,

I just installed the "M" series because I had been experiencing issues with the echo and according to some it had been fixed or was better with it. Well I clean flashed it and I am still getting people saying it's poor. Is there a solution to this besides basically going back to a TouchWiz based rom?

Thanks
[Verizon Samsung Galaxy S III] MG386:
I'm on 9/23 official no call echo on either end on earpiece or speakerphone

CM10 9/23 official w/official cm kernel

Clean installed format system, data, cache, and dalvik.

G7 radio

Not sure why many people still have echo.
[Verizon Samsung Galaxy S III] elreydenj:
What do you mean by format system? i wipe data, cache and dalvik. How do you format the system?
[Verizon Samsung Galaxy S III] kls629:
mounts and storage > mount/system and format/system
[Verizon Samsung Galaxy S III] imveryemo:
seconded
[Verizon Samsung Galaxy S III] Ryphez:
Maybe it's the radio. I am still running the first stock 1 that came out. I will give that a shot and report back
[Verizon Samsung Galaxy S III] sd_N:
Thirded
[Verizon Samsung Galaxy S III] elreydenj:
If i mount system and format system will this affect my recovery or the unlocked status of my bootloader? Ez unlock and cwm both have file folders on the internal storage.
[Verizon Samsung Galaxy S III] kennyho35:
U should never store files of that importance on your internal move them to ext sd also it's recommended to format the internal sd as well!
[Verizon Samsung Galaxy S III] elreydenj:
When you download the app ez unlock and do the unlocking, it automatically puts a file folder on your internal.
[Verizon Samsung Galaxy S III] MG386:
Theres nothing wrong with storing files on internal SD. A format system, data, cache, dalvik will not harm, change, or touch your internal SD, bootloader, cwm files.
[Verizon Samsung Galaxy S III] elreydenj:
However they are recommending to format the internal sd as well. What do you think?
[Verizon Samsung Galaxy S III] MG386:
Not sure about "they" but I recommend format system, data, cache, and dalvik.

This will NOT touch your internal SD.

There is NO reason to format internal or external SD.
[Verizon Samsung Galaxy S III] Marcismo55:
Negative. Format of the internal storage is completely uneccesary unless you are have seen SERIOUS issues.

Just as another user said...always factory reset, format system, and wipe dalvik prior to flashing another ROM.
[Verizon Samsung Galaxy S III] mybook4:
For those wondering how battery life is...

Just over 4 hours of screen time on 9/23. Not too shabby.
[Verizon Samsung Galaxy S III] apacseven:
If you are formatting system and data, its redundant to also do cache and dalvik as they will already be gone.
[Verizon Samsung Galaxy S III] Recon0212:
Am I the only one getting much better battery life on 9/24?
[Verizon Samsung Galaxy S III] beaups:
I'm sure not. Are you guys on stock kernel?
[Verizon Samsung Galaxy S III] Recon0212:
Yeah, I flashed from 9/20. But I'm at 9 hours on battery with minimal use at 49% remaining.
[Verizon Samsung Galaxy S III] beaups:
Oh I've had that kind of battery life. I miss the nearly 2 days on my one x :(
[Verizon Samsung Galaxy S III] alee:
RIL commit for tonight's build...

http://review.cyanogenmod.com/#/c/23846/

Could carry over to better 3G/4G stability on D2VZW? We'll know in 4 hours or so.
[Verizon Samsung Galaxy S III] jdubau55:
Lots of merges going in to tomorrows build. Might just have to flash it.
[Verizon Samsung Galaxy S III] kls629:
No it will not format your phone like a computer. It will help erase any trace of previous rom. It is actually recommended to do

Also i am on 9-24 and my fiance told me she still hears a slight echo on speakerphone
[Verizon Samsung Galaxy S III] jackpot08:
maybe im stupid but i can't find it. can i change it to vertical scrolling for the app drawer not horizontal. i hate horizontal
[Verizon Samsung Galaxy S III] dvaderx:
I went back and loaded a bunch of nightlies to try and find where audio broke

when recording video the audio is perfect on 8/18

it does still seem to work on 8/22 (but feels a *little* lower)

8/24 video recording doesn't work at all (force closes)

8/28 - 9/24 audio is extremely low when recording video.

hope someone can use that info
[Verizon Samsung Galaxy S III] Brian Gove:
Its very unlikely that its a kernel issue with all the different kernels having the same problem.
[Verizon Samsung Galaxy S III] alxdgr8:
Mine sure isn't anywhere close to that. 9/23 build (clean flash) has given me HORRIBLE radio coverage and GSam is estimating my battery life at just over 8 hours. Jelly Bean is awesome, but I'm probably going to go back to Synergy ICS unless my battery life gets better.
[Verizon Samsung Galaxy S III] chetqwerty:
Honestly, i hate it when people post for no reason saying how great everything is running for them but..... here goes.... lol seriously i have never had echo since coming from Synergy for nightly 17, i have never once clean flashed since installing 17, my gps locks instantly on every build except for the little curveball thrown with having to check internal gps, screen flickers ONLY when swiping an icon from GOLauncher off the screen, call volume is not too loud and easily adjusts in a call without having to pull away from my ear, right now i'm at 14 hours on battery and still have 74% left, never dropped a data connection. Odd how we all have the same phone yet some of the above really seams to haunt some. I would never flash another nightly if the blasted dialtone pause issue was solved! I dont use NFC of Google Wallet so no comments there. So maybe if this is going to be a helpful post to anyone try using GOLauncher. It may fix some of your issues who knows....
[Verizon Samsung Galaxy S III] guthrien:
This was super impressive of you, whether it leads to anything or not I'm appreciative. It exists on all the cm10 based roms too. The call volume issue isn't there on codefireX for instance, but I still can't record with any volume. It's a really annoying bug.
[Verizon Samsung Galaxy S III] shinjielric:
I just installed the latest nightley (23/9) and I only have sound when I have headphones plunged in. Ringtones and notifications play fine but if I play a game or turn a song on; nothing.
[Verizon Samsung Galaxy S III] neyenlives:
Looks like build didn't make.
[Verizon Samsung Galaxy S III] ssmaster:
Has anyone been able to successfully use myverizon.apk and the sso.apk from a Verizon galaxy nexus 4.1.1 system dump? I tried installing then converting to a system app, but all I get is an error, "Cannot process your request at this moment..."

Could this help lead to a more stable working NFL mobile?
[Verizon Samsung Galaxy S III] elreydenj:
What kernel are you using? I clean flashed like described above once more and still have the echo.
[Verizon Samsung Galaxy S III] cgulliver:
It was killed due to being broken.
[Verizon Samsung Galaxy S III] NegativeOne:
Radio does not affect things like microphone. So no.

How about the microphone issue? Does your phone do voice recognition okay if you're not speaking into the top microphone directly (from within a few inches?) Please try speaking softly into the bottom one and report back.

Says it fixes MOTOROLA devices...
[Verizon Samsung Galaxy S III] alee:
That just suggests it has been tested and fixed on Motorola devices, but does not exclude it from being fixed on Samsung devices as well.

There is no Samsung specific code in the 2 RIL commits.

If Samsung uses an RIL less than v7, this is very likely to carry over as a benefit for D2VZW.
[Verizon Samsung Galaxy S III] kimsj756:
I hope this nightly will fix low volume on recording which is my biggest wish!
[Verizon Samsung Galaxy S III] minmongoblin:
So no 9/25 nightly, gotta wait until 9/26?
[Verizon Samsung Galaxy S III] NegativeOne:
Does anyone know of a way to get old nightlies / changelogs? There is an interesting comment on the bugtracker about when some of these items started popping up (late August - so not showing up on the normal view of the bbqlog). I wanted to see if I could track down the changes.
[Verizon Samsung Galaxy S III] alee:
Yep. Unless someone builds an unofficial.

This was committed to address the build error:

http://review.cyanogenmod.com/#/c/23876/
[Verizon Samsung Galaxy S III] Droosh:
I've too am solid. I noticed that you didn't say that you have TW sound levels on recorded video. Assuming you don't?
[Verizon Samsung Galaxy S III] elreydenj:
My top microphone only works when using voice recognition. The bottom one does not recognize what I am saying. This is a big issue and is part of the reason for the echo when on speakerphone as the wrong mic is being used and mic gain is wrong IMO. I really wish that someone could get this straight. On both cm10 nightlies and Paranoid Android this is the only problem that I experience and it is a big one for me.
[Verizon Samsung Galaxy S III] grin0048:
Here's an unofficial I built last night if anyone is interested.

Not sure why mine wasn't broken by whatever stopped the official build. :confused:
[Verizon Samsung Galaxy S III] NegativeOne:
I was directing the question specifically to MG386 because he said that a lot of his issues regarding the mic were cleared up.
[Verizon Samsung Galaxy S III] elreydenj:
I understand. They are not cleared up for everyone and it is very frustrating. Low recording volume on video. Also, horrible echo for the person you are talking to of their own voice when on speakerphone, and finally the bottom mic not recognizing what you are saying while the top mic does. I am not telling anyone anything new. The frustrating part is that the fixes can be implemented into a kernel but it is yet to be done.
[Verizon Samsung Galaxy S III] ugachris:
This is a community project. If you know how to fix this, why not drop a kernel we can test?
[Verizon Samsung Galaxy S III] ynotbike:
http://changelog.bbqdroid.org/#d2vzw/cm10/next
[Verizon Samsung Galaxy S III] MG386:
I said i was using stock CM kernel

I've tried voice recognition in top and bottom mic, and both seem to work well. I've tried speaker phone calls speaking into top and bottom mics and both seem to work well.

Again, besides a very clean install, and stock kernel, I'm not sure why mine is good and others aren't. I have noise canceling turned on as well.
[Verizon Samsung Galaxy S III] elreydenj:
I do not know how. I do not have the experience. I have been told, for what its worth, by other very experienced members that controls for the microphones, mic volumes, and mic gains and such can be incorporated into a kernel or obviously directly into a rom. There are enough people experiencing mic issues related to volume, echo and just quality in general and i don't understand why a fix has not been found yet. I would gladly donate if it rid me and others of the horrible problem related to an echo while on speakerphone.
[Verizon Samsung Galaxy S III] Dcox28:
I'm not sure that people still understand what the problem is on the echo issue. Just to be clear, you will never hear the echo yourself. It happens when you call someone and put them on speaker phone, then ask them to talk. They will hear there own voice echo over and over.
[Verizon Samsung Galaxy S III] elreydenj:
I agree, not everyone understands exactly what it is. Granted, not everyone is experiencing it, but more there are more that just have not been alerted to this issue as of yet. Unfortunately it appears that the people who could do something about testing and searching for the proper fix are not having any issue.
[Verizon Samsung Galaxy S III] zxsix:
It's not only on speakerphone. Callers hear echo when I have the phone to my ear using it like a normal phone handset. Most likely caused by the volume being so loud even with the volume slider all the way to the left and then it probably gets picked up by the upper microphone and reheard again by the caller.
[Verizon Samsung Galaxy S III] NegativeOne:
I do not think they are kernel fixes. MG386 - what is the first build you know that the problems are fixed on for you ?

I'm on a clean build too, but an older one.

That doesn't show OLD builds... I mean like OLDER than that page... like Middle of august. Here's a quote from the bug tracker:

I wanna find those.
[Verizon Samsung Galaxy S III] rfmodeler:
I'm not very good at programming and I don't have the time, but there is a lot of info on the topic. It seems like there are a few simple algorithms that might work. I think the key is knowing how the mics are connected so the algorithm can be properly implemented in code.

http://en.wikipedia.org/wiki/Noise-canceling_microphone

http://www.andreaelectronics.com/pdf_files/ancwhitepaper.pdf

http://mobiledevdesign.com/tutorials/cancel-noise-mobile-phones-headphones-0611/

http://www.onsemi.com/PowerSolutions/product.do?id=BELASIGNA R261

http://www.utdallas.edu/~loizou/cimplants/pubs/dual_mic_coherence.pdf

I didn't read all these links, but it might be as simple as coherently subtracting(dividing if you are dealing with voltages not power) the secondary mic input from the primary mic input. I only know how to do that in very high level languages like MATLAB, but I'm sure it's a common programming practice for all you software guys.
[Verizon Samsung Galaxy S III] NegativeOne:
I don't know what you mean by "mic control", but noice canceling is IN the rom... click phone > settings...

Just... the mic config is f'd up right now.
[Verizon Samsung Galaxy S III] alee:
Depends on what time you pulled the codebase. The fix was merged at 2:48am. Or if you pulled right before the bad Dutch translation went in.
[Verizon Samsung Galaxy S III] MG386:
I understand the issue. I had call echo weeks ago on earlier builds. (On other end of call) Every time I load a new nightly I test phone calls with and without speaker phone using 2 other phones I have. I go outside and talk to my wife inside the house, and then trade phones to see if either of us hears any echo. Last several builds have been good for me.
[Verizon Samsung Galaxy S III] rfmodeler:
The noise cancelling code might be in the ROM, but it's probably not implemented properly for this setup, or there are other mic changes that need to be made before it can work (mic levels, phase correction, etc). The other audio problems probably have something to do with it.
[Verizon Samsung Galaxy S III] NegativeOne:
What is "the" fix?