yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] dvaderx:
I also spent a while bulk swapping out libs and other audio related files.

but that got me boot loops or after the cache would build i'd get "starting apps" and it would sit forever.

I also tried swapping older kernels, didn't seem to help.

but at some point, you have to say, if i'm swapping out all these old files, i might as well run the older release.

i also dug through lots of the of the commits and i noticed several audio changes after the 18th, one of them being "swapped out the audio system for open source"

I also did recall seeing one commit that the comments said, don't upload breaks the mic. and then was approved the next day.

i have to question their approval process. i looked at many of those commits and saw lots of

"don't merge/upload - breaks xyz"

only to later that day or the next day see "looks good to me" and then "approved"

I ran a diff on the 18th files and then the ones after and found plenty of differences, but as i said, simply swapping them out didn't seem to help.

I think this could be a kernel + rom files type of situation.

I guess the greater question is why hasn't this been fixed in over a month? It still is a phone after all and having multiple MIC related issues seems to me something that should be a priority..

I wonder if CVPCS would be receptive to working on the issue, i think he has an s3?

---------- Post added at 12:58 PM ---------- Previous post was at 12:55 PM ----------

That was me who made that post.. I dug through all the old commit/gerrit logs I was just updating a bug report incase any devs from CM read that bug report, they would know when it broke (after 8/18 - ish)
[Verizon Samsung Galaxy S III] grin0048:
Yeah, definitely before the fix was merged. I can't seem to find when the bad translation was merged--this is going to bother me all day until I can get home and look at the actual file in question :eek:
[Verizon Samsung Galaxy S III] Dcox28:
I think part of it has to do with the right people (devs) having the issue. Most say they don't experience the echo or other mic issues. Hopefully from people speaking out today and yesterday about this will get some awareness and get this issue resolved. Just not sure if this thread will raise that awareness to the correct people!!
[Verizon Samsung Galaxy S III] alee:
Sorry... the build broke last night because a quotation mark in the Dutch translation wasn't properly escaped so it created a mismatch (open quote without end quote).

All the builds last night that had the Dutch translation merged were broken as a result.

This was fixed last night, so barring any other issues, it should build and generate a nightly tonight.
[Verizon Samsung Galaxy S III] dvaderx:
looks like a commit went in at 6:04 am to enable low power audio.. probably wont fix our problem

but you never know
[Verizon Samsung Galaxy S III] lchupacabras:
Not sure if this has been previously discussed or not but my GPS isn't working at all :/ Anyone else experiencing similar issues or have a fix?
[Verizon Samsung Galaxy S III] cgulliver:
There is a difference between a nightly merge approval and stable. CM has very high standards for release. A lot of roms have no approval process.
[Verizon Samsung Galaxy S III] d1ez3:
http://cm10log.appspot.com/?device=d2vzw

wow next nightly looks like it incorporates a huge amount of changes
[Verizon Samsung Galaxy S III] elreydenj:
Have you checked the selection that says gps source? You have to choose the internal gps before it will work.
[Verizon Samsung Galaxy S III] grin0048:
Alright, mystery solved, the broken Finnish translation was merged shortly after I pulled. Now I can get back to work. :p
[Verizon Samsung Galaxy S III] lchupacabras:
Yep, it's selected.
[Verizon Samsung Galaxy S III] TechSavvy2:
Don't know how much is necessary but it definately works - try going to apps - all - and click on google services framework and clear data, then reboot, then turn off all GPS services and then turn all back on and select internal GPS.

If that doesn't work, reload a nandroid you have of stock tw, turn on and get GPS lock, then flash back to cm10 backup and follow above method again.
[Verizon Samsung Galaxy S III] NegativeOne:
Yeah, but if you merge bad changes into your trunk, you have to fix them separately. IT would have been better that crap like that didn't make it in.

Where did you find changes from the 18th? I'd like to have a look please.
[Verizon Samsung Galaxy S III] lchupacabras:
Tried the first part, still no go. I should probably make it clear that only Navigation has problems. I can get my location in maps, etc just fine (no wifi)...
[Verizon Samsung Galaxy S III] dvaderx:
review.cyanogenmod.com

just follow the dates and keep clicking previous until you get back to around 8/18

like i said b4, it looks like they changed the entire audio system around 8/23-ish to an open source model (if i understand the commit comment correctly)

i also saw a commit note that said "still needs allot of work" after an audio related change around 8/24

---------- Post added at 02:18 PM ---------- Previous post was at 02:07 PM ----------

I wasn't trying to imply that CM had low standards, but from the comments (and i could just be misinterpreting what they mean) it seems as several of the commits had the following process

"change xyz uploaded/added"

"don't merge breaks 1234"

"looks good to me"

"approved"

I know from the past and looking at other commits that there is often a back and forth where they fix something a re-submit.

but i was looking at audio related changes for the s3 around the end of august and it *seemed* as a few of those they were getting approved regardless. their very well could have been more to the individual change process that wasn't logged, but that's just how it appeared to me.
[Verizon Samsung Galaxy S III] d1ez3:
Would the implementation of low power audio help the battery drain listening to mp3's and podcasts?
[Verizon Samsung Galaxy S III] dvaderx:
yes I think so.
[Verizon Samsung Galaxy S III] alee:
http://review.cyanogenmod.com/#/c/23895/

RIL change from last night reverted for breaking Toro builds.
[Verizon Samsung Galaxy S III] Srambo217:
Are those of you in 3G only areas still experiencing data drops?
[Verizon Samsung Galaxy S III] shinjielric:
I haven't had any data drops. Tho I have no sound unless I have headphones plunged in.
[Verizon Samsung Galaxy S III] miguel11691:
How is this Rom for apps on the micro sd card.. I play games like shadowgun and others from gameloft .. will they run smooth as well
[Verizon Samsung Galaxy S III] sidn3y:
Experiencing a few screen flickers now and then plus a few System UI crashes as well. Other than that everything seems to be running great.

Also, forgive me if this isnt the right thread but how would I go about changing the signal meter icon(s) to the stock TW ones? Is there a centralized place where people discuss modding (theme wise) CM10?

Thanks :)
[Verizon Samsung Galaxy S III] mybook4:
There is a Themes and Apps section of the verizon galaxy s iii forums, but for asking questions you'd probably want to post in the Q&A section.

I can help you out with that. Post a thread in the Q&A area and I'll reply with details. I would respond here or PM you, but it's lengthy, outside the scope of this thread, and others may benefit from a public post.
[Verizon Samsung Galaxy S III] s197:
Anyone try this and see if it fixes the low volume recording issue?

http://rootzwiki.com/topic/33633-mod-aosp-camera-mod-for-jb/

Changlog says audio fixes for the latest version.
[Verizon Samsung Galaxy S III] zxsix:
Listening to music via the Apollo player through Bluetooth a2dp to a stereo Bluetooth headset.

In dsp manager, the Bluetooth tab eq doesn't have any effect. The eq under the speaker tab is what is being used. Is that expected behavior or a bug?
[Verizon Samsung Galaxy S III] Droosh:
I posted that link a while back. I've been running since then. The audio issue carries over from CM and isn't fixed by the mod. The mod does allow 16:9 images, photos while shooting video, and directly saving to the external SD card among other changes.
[Verizon Samsung Galaxy S III] zxsix:
Another bug, but I am unsure as to where to report it.

Originally I thought it was a bug in the Apollo player, but the same issue also appears in Player Pro.

I have a .pls file that has the new Green Day album in it.

One of the songs is Carpe Diem.

The structure of the playlist file is:

./punk rock/green day/uno/carpe diem.mp3

In both music players, the song that appears in the playlist and ends up playing is not Green Day at all.

It's a song of the same title, but different band.

It is stored on the sd card at ./death metal/August Burns Red/Carpe Diem.mp3

"August Burns Red" absolutely does not appear in the playlist file at all! Not sure why the players are even looking at that song at all.

Since it's affecting the included music app and a 3rd party app, I suspect it's the fault of the media scanning service, which is part of the rom.
[Verizon Samsung Galaxy S III] Imatoasta:
I'm on the latest paranoid and I'm still getting them. Its cherry picked so idk what changes it has merged. I'm curious if these new RIL commits are going to help us.
[Verizon Samsung Galaxy S III] beaups:
Have you looked at the tag? That's where the info comes from, not the folder.
[Verizon Samsung Galaxy S III] imveryemo:
for anyone who's NFC just greys out when you click to turn it on, flash a TW 4.0.4 ROM, turn it on, then nandroid back to CM10 and it'll be back on. happy to be setting up my GWallet on CM10 :D
[Verizon Samsung Galaxy S III] zxsix:
Yes I have. The Green Day version of Carpe Diem is tagged as Green Day and correct album name.

When it shows up in the playlist, it ends up showing August Burns red as artist and album, and the audio that plays is not Green Day.

It's playing the August Burns Red file instead of Green Day.

I connect phone to pc via usb cable.

Using windows explorer I navigated to the /music/punk rock/green day/ folder and clicked on the Carpe Diem.mp3 file. It's playing Green Day correctly and shows Green Day tags as expected.

Do the same thing with /music/death metal/august burns red/ and click on the Carpe Diem.mp3 file there, it plays the ABR song and shows ABR tags as expected.

It's the music players on the phone that are mixing up the 2 songs and the only similarity in the tags is the song title.

Another test.

Forget playlists... go to the SONGS tab in Apollo. I see both Carpe Diem tracks listed. One shows Green Day, one shows August Burns Red. Play the one that says Green Day, and I get Green Day. Play the one that says ABR, and I get ABR. Works perfectly.

Problem is with the playlist feature.
[Verizon Samsung Galaxy S III] imveryemo:
don't know if it's been posted, but for anyone who's NFC just greys out when you click to turn it on, flash a TW 4.0.4 ROM, turn it on, then nandroid back to CM10 and it'll be back on. happy to be setting up my GWallet on CM10 :D
[Verizon Samsung Galaxy S III] alee:
There is no RIL commit... it was reverted earlier today.
[Verizon Samsung Galaxy S III] s197:
Sorry I know this was posted a while back but if you look at the latest versions changelog it says "fixed audio issue" so I was hopeful maybe that would help us but it appears it doesn't.
[Verizon Samsung Galaxy S III] scriz:
I gave this a shot but was unable to get NFC to enable.
[Verizon Samsung Galaxy S III] imveryemo:
really? i spent the better part of last week trying to figure out how to get NFC to work again, and found someone suggested that on rootzwiki, tried it with the ultra lite cleanROM and it was on as soon as i nandroid back to CM10. sorry it didn't work for you
[Verizon Samsung Galaxy S III] goatman101:
I can vouch for this, it worked for me!
[Verizon Samsung Galaxy S III] jmill75:
Where can i find builds from Aug?...Aug 19th i think is what i need
[Verizon Samsung Galaxy S III] goldsmitht:
i use power amp, and eq works great!

---------- Post added at 10:25 PM ---------- Previous post was at 10:20 PM ----------

power amp allows your to go in and adjust what files are played, and would probably fix that
[Verizon Samsung Galaxy S III] dvaderx:
patch just submitted @ 11:02

I hope it makes it into tonight's nightly as that seems like something we may need :)
[Verizon Samsung Galaxy S III] masri1987:
you think there will be a nightly tonight? it's already 9 42 pm
[Verizon Samsung Galaxy S III] codyvance:
Looks like all the builds on Jenkins are failing...
[Verizon Samsung Galaxy S III] TechSavvy2:
Seems our device doesn't build/post till around 1am usually, I'd say it was good to go time wise....however see the following.......
[Verizon Samsung Galaxy S III] zipkicker:
Make sure you're flashing an ICS rom
[Verizon Samsung Galaxy S III] TechSavvy2:
Well on the plus side, this is probably the most commits that have gone into a "single" nightly thus far......
[Verizon Samsung Galaxy S III] abreeden:
9-26 is up
[Verizon Samsung Galaxy S III] PerCompLLC:
And working WELL! :)
[Verizon Samsung Galaxy S III] abreeden:
Agreed. First flash since 9-18 for me, and things seem snappier. No echo and screen flicker for me.

Video audio doesn't seem low to me. Just tested it, and seemed ok. i am alone in my office and its quiet in here. may not be a good indicator.

CM10 is getting so good :)

Edit: Video recording still low.
[Verizon Samsung Galaxy S III] Droosh:
The commit to keep capacitive buttons off after reboot works. :cool:
[Verizon Samsung Galaxy S III] alee:
9/26 looking good so far as well. NFC working. Seems pretty zippy at first blush.
[Verizon Samsung Galaxy S III] droidxuser123:
9/26 good so far

Widgetlocker doesn't work just FC's all the time. Not a deal breaker but really wish it worked :p
[Verizon Samsung Galaxy S III] NegativeOne:
How are the microphone/audio issues?
[Verizon Samsung Galaxy S III] dmbfan13:
When I was using TouchWiz based roms, I had something I could flash that would give me the stock messenger. It had emoji with it. Wondering if I can just flash that using CM10.
[Verizon Samsung Galaxy S III] schnyd:
Thanks. I thought that may be it . The version I have is touch that's why I was still on it.
[Verizon Samsung Galaxy S III] cordell12:
Are everyone's calls getting disconnected when receiving a text message? Happened to me twice today, phone vibrates twice then reboots itself :(
[Verizon Samsung Galaxy S III] td1320:
I use Car Dock Home from the App store. Lets you do a whole lot more then just USB audio. I have that same Car Dock as well.

https://play.google.com/store/apps/details?id=net.cwfk.ig88.carhome3&feature=search_result#?t=W10.
[Verizon Samsung Galaxy S III] strung:
I can confirm this. It took about 10 messages but eventually it rebooted. I noticed it wouldn't vibrate either even though Messages app is set to vibrate even on a call.
[Verizon Samsung Galaxy S III] majmuni:
+1
[Verizon Samsung Galaxy S III] irtehun:
Same here.
[Verizon Samsung Galaxy S III] minmongoblin:
Thanks, I'll give it a shot. I assume it stays on indefinitely when plugged in? That's how I like it =)
[Verizon Samsung Galaxy S III] Mystikalrush:
Is this the touchwiz jb version? Touchwiz is really growing in me and I'd prefer it over stock jb.
[Verizon Samsung Galaxy S III] bakaz:
This setting is a global setting (not specific to your dock software). It's in Options > Developer Options > Stay Awake.
[Verizon Samsung Galaxy S III] WildZontar:
Is the MEID displayed differently on AOSP roms than it is on TouchWiz?

I compared my MEID to the TW screenshot I took before flashing, and noticed that the one that CM10 reported was nothing near what TW reported (mine started with A1000...). After restoring my nandroid backup (back to TW), the MEID display was the same as the screenshot again.

No calling or data problems on either ROM, just wondering why my AOSP MEID didn't match my TW MEID.
[Verizon Samsung Galaxy S III] Mean Sixteen:
Nope.
[Verizon Samsung Galaxy S III] DROID3R:
Going to beansstock rom for now cant deal with these random reboots. Ill keep an eye on this thread though

VERIZON GALAXY S 3
[Verizon Samsung Galaxy S III] TechSavvy2:
It did that to me too but I finally figured it out. Like others said, you're on a "broken" version on cwm. Download ROM manager and install the touch version from the bottom of it. Works fine after that.

I've fully wiped and installed all three builds and haven't had a single reboot fwiw. Been going three days good and steady. No phone echo that others speak of either.

Full wipe AND format system every time is how I achieved these results.

---------- Post added at 02:07 PM ---------- Previous post was at 02:05 PM ----------

In reference to my previous post....
[Verizon Samsung Galaxy S III] himom:
Upgrade your recovery. Search the shop for EZ Recovery and flash 6.0 (NOT TOUCH) or look in this forum for the Odin Recovery guide and flash that (you can flash touch). 5.x recovery doesn't work on this version of CM.
[Verizon Samsung Galaxy S III] drbveb88:
What's wrong with the touch version, should we be using the 6.0.12 not touch version?

---------- Post added at 05:26 PM ---------- Previous post was at 05:24 PM ----------

Going "three days"??? Your not running the 0820 nightly are you?
[Verizon Samsung Galaxy S III] TechSavvy2:
Those both have too many tricks to them, and nobody wants non touch, lol. Use ROM manager, they both work now.

Yes ez recovery was great but we don't need it anymore. :sad face:

---------- Post added at 02:30 PM ---------- Previous post was at 02:27 PM ----------

I don't know who follows status elsewhere, but apparently Mr Cyanogen himself found the video streaming issue and is supposed to be submitted yesterday or today. Who knows when it'll be merged.

So happy for this....!!!!:):):)
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
To all those people having issues with the latest build just stick to 8/18 honestly that build is very very solid.. For sure a daily driver.. I have had zero issues with it..

I'd recommend sticking to that until something stable comes along

Idk maybe it's just me but I don't wanna lose my imei so I try and keep from flashing all these nightlies unless I come in here and see everyone saying it's stable
[Verizon Samsung Galaxy S III] minmongoblin:
For what it's worth I can also confirm the echo when I talk to someone. They said I "sound like [I'm] in a barrel" and that they can hear themselves talking on a one-second delay.

EDIT: I'm on the 2012-08-20 02:14:49 build
[Verizon Samsung Galaxy S III] W4LLY:
Is there a list of what is/isn't working in this ROM?

Just curious If i missed where it was posted.

Biggest concern is having Tethering available as well as email, and MMS
[Verizon Samsung Galaxy S III] Dcox28:
Has anyone that had the speaker phone echo problem downloaded last nights build and tested? If not I guess I will have to give it a try
[Verizon Samsung Galaxy S III] dvaderx:
Same
[Verizon Samsung Galaxy S III] Dcox28:
For those with the speaker phone echo problem I can confirm that last nights build does NOT fix it. I just flashed and tested and echo is still as bad as ever.
[Verizon Samsung Galaxy S III] NegativeOne:
That's disappointing. I don't anticipate a fix any time soon though. Too bad - I'm totally crazy about cm10, but I need my speakerphone and voice recognition (which does work, if I hold the top of the phone to my mouth, but that's kind of useless for me).
[Verizon Samsung Galaxy S III] Dcox28:
Same here. I love CM10, my personal preference is Paranoid Android but I have to use speaker phone on a daily basis with work. What is really frustrating is that most users say they don't have the echo problem. Not sure what is different for us and why we do have it.
[Verizon Samsung Galaxy S III] d1ez3:
I don't understand why I don't have the speakerphone echo problem while so many others do, is there a difference in hardware that causes this?
[Verizon Samsung Galaxy S III] NegativeOne:
A) Dcox28 - do you have the noise cancelation option selected

B) d1ez3 - do you ? Have you asked people you're talking to if they hear echo?
[Verizon Samsung Galaxy S III] elreydenj:
Very disappointing. I need the speakerphone functionality as well. How can we create more awareness of the issue so that someone can continually work on it until there is a fix? There are enough people experiencing this that they could get a nice little donation if everyone was willing.
[Verizon Samsung Galaxy S III] NeoMagus:
In case nobody noticed 9-26 build is now based from JRO03R. ..no issues here except the low audio recording video.
[Verizon Samsung Galaxy S III] beaups:
Can you elaborate on what you mean?
[Verizon Samsung Galaxy S III] NeoMagus:
Was on 9-23 it was based on JRO03L , 9-26 it is the recent version from AOSP.. the build number of Android version. You've been here longer than me surely you knew that , unless you meant the low audio recording thing just take a video and the sound on it is really low
[Verizon Samsung Galaxy S III] jmill75:
It doesn't help when we get posts like this that says everything is fine except 1 issue. There are many more issues, why even test the builds if your going to say everything is great. If I was to read your post I would flash this in a heartbeat, better than stock??? But its not, there are issues. Heck the call volume is a huge issue that effects the use of the phone, not even getting into the other features of the phone.
[Verizon Samsung Galaxy S III] NeoMagus:
Are you serious dude? I posted the only issue I have. I dont have the echo everyone talks about (I test between my S3 and Galaxy Nexus). My NFC, GPS all that stuff works fine which I posted LAST time I posted. What else do you want to know? That I've dirty flashed since 8-26 and seem to have less issues than the people that swear over CLEAN FLASH EVERY TIME? Haven't had an issue DD'ing this since initial echo with 8-26 which cleared up on 9-5 for me.. Get off your high horse

And as for your call volume issue my earpiece is always at maximum anyway had I not read about it on here I wouldn't have even noticed. Sorry its a superhuge deal for you.
[Verizon Samsung Galaxy S III] jmill75:
This is the response I figured I would get....

So your in call volume is great? No speakerphone echo? Both of your mics work for what they are suppose to?

Just saying these are KNOWN issues
[Verizon Samsung Galaxy S III] NegativeOne:
It' a new JB build from google. Basically an OTA for Galaxy Nexus (Since GN gets its stuff straight from Google)

Not sure how you've come to the conclusion that 9/26 is based on this. I see nothing about JRO03R in the changelog though. Unfortunately, the low recording volume has been widely attributed to the "reversed" microphones issue, so that implies that the voice recognition and echo problem still exists.
[Verizon Samsung Galaxy S III] Argent36:
One thing I've just noticed today after dirty flashing the latest was that my headphone jack doesn't seem to be working - not sure if it's just me or what....figured I'd put that out there....I can plug headphones in but I don't get the icon in the notification and audio still plays out the phone speaker.

EDIT wiped and clean flashed 9-26 and still no headphone audio from the jack - anyone else have this problem?
[Verizon Samsung Galaxy S III] abreeden:
I'm with Neo. The ONLY issue i have is low video recording. That is it. i too am a dirty flasher. everything works for me. i also agree, that some of you take this forum way too seriously. feedback is feedback. relax.
[Verizon Samsung Galaxy S III] NeoMagus:
It's in the build.prop, open with a text editor its under the string ro.build.id

I guess you should go back read my response again. I detailed all three of your questions, you apparently didn't read them. :highfive:

Watch out man I didn't want to have to even say that but next some other know-it-all will start harping on that again lol
[Verizon Samsung Galaxy S III] Dcox28:
I've tested both with and without Noise Suppression checked as well as Call Privacy and neither make a difference.
[Verizon Samsung Galaxy S III] Version_3:
Here's where you can easily find that info. Settings > About phone, scroll to the bottom for info on the version. I don't know, however, if the GNex will see this version, GSM or otherwise.