yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
are you guys doing clean installs of the latest build or dirty flash
[Verizon Samsung Galaxy S III] tmar23:
I did a dirty flash from previous night's flash. I try to limit full wipes to weekly, or as needed if I have issues.
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
i did a full wipe and i just called my wife and she is the echo was still there..:(
[Verizon Samsung Galaxy S III] crazytalk151:
Has anyone got Wifi tether or music to play from the doc?
[Verizon Samsung Galaxy S III] dlsolo:
I posted this over in the unofficial CM10 thread, but wanted to share this here as well:

For all who are having issues, fix permissions will probably fix most of your issues.

I'm currently running the latest nightly with Imo's .7 kernel and have no random reboots or force closings. Not had one issues with my camera force closing from the app drawer or from the lock screen selection.

My suggestion -

After a full-wipe install or a dirty install, run "fix permissions" from your recovery. Heck, run "fix permissions" reboot back into CM10, let it sit for a couple of minutes, then reboot back into recovery and run "fix permissions" again.

Hope this helps.
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
for dirty flash are you supposed to reflash the gapps?
[Verizon Samsung Galaxy S III] dlsolo:
Not necessary
[Verizon Samsung Galaxy S III] strung:
Just tried that however it didn't seem to affect the compass. Thanks for the suggestion though!
[Verizon Samsung Galaxy S III] Durthquake:
Tomorrow? I want it yesterday! :cyclops:
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
To those saying the echo bug is fixed.. What did you do different because I just did a dirty flash and a clean flash and both of them still have the echo
[Verizon Samsung Galaxy S III] JCSIII:
How do you get light flow to work on this ROM?
[Verizon Samsung Galaxy S III] Mercuie:
System Settings, Display, Notification light, Notification light checkbox. Then you can use light flow normally. No need to use the S3 root mode in light flow either, so your lights will actually flash instead of stay on. (if you so choose)
[Verizon Samsung Galaxy S III] Srambo217:
It's probably been addressed, but would I have to reformat my memory card to FAT32? I read somewhere CM10 will not play nice with an extSD formatted card.
[Verizon Samsung Galaxy S III] jdhas:
Yes, you need to format your SD Card to FAT32. This is the best resource I've found: http://www.epiccm.org/2012/06/why-not-exfat.html
[Verizon Samsung Galaxy S III] JCSIII:
Thanks Merc :)

---------- Post added at 04:36 PM ---------- Previous post was at 04:35 PM ----------

This ROM runs perfect with Apex Launcher...Nova was a mess
[Verizon Samsung Galaxy S III] tomyboombotz:
I didn't have to format mine I just did a search on both external and internal for. .Nomedia

File and delete everyone that comes up. Reboot and download scan media from play and everything should come up
[Verizon Samsung Galaxy S III] jprovan1:
So.... Just so I'm correct. If I have cm10 8/19 and I go to the 8/21 build. Can I just flash over what I have currently or is it a full wipe
[Verizon Samsung Galaxy S III] tomyboombotz:
I didn't wipe anything just flashed and flashed gapps and good to go
[Verizon Samsung Galaxy S III] fix-this!:
switched from twrp to cwm touch and m2 flashed with no wifi errors this time, weird. anyways it's running good except i have troubles waking the phone with the home button at times. also i have to enable gpu rendering or i get lag scrolling through menus.
[Verizon Samsung Galaxy S III] bluezr1:
+1 whenever I know that I'm getting a new phone I'll order batteries before I even get the phone.

One thing that I found out with this phone is, if I get anywhere from 4-5 hrs. of onscreen time I'm doing good.
[Verizon Samsung Galaxy S III] grin0048:
Just going to throw it out there for anyone who may want to give it a try--the file that is modified by the call volume fix is snd_soc_msm_2x, that file is simply copied by the build to /system/etc/snd_soc_msm/snd_soc_msm_2x. The fix is just changing line 2320 from "ACDBID 71:1" to "ACDBID 7:1". I'm guessing that the fix can be applied by modifying the file and rebooting. I messed around with it for a few minutes, but JOTA wouldn't save the file for me--I gave up after the angel on my shoulder told me to get back to work :p

Obviously, standard disclaimers about screwing with your device like this apply--should go without saying. And, of course, it's entirely possible I'm wrong about whether this would work or not. ;)

edit: or I could just upload the unofficial I built last night with the fix cherry-picked, if anyone is interested.
[Verizon Samsung Galaxy S III] NegativeOne:
I'll try it
[Verizon Samsung Galaxy S III] glensta:
Hi All,

I'm getting a "Failed" error message since trying install the 10/22 or 10/23 nightlies. I'm using twrp recovery and wiping cache, dalvik cache, factory reset - the usual flash method I've used hundreds of times. Anybody getting the same? Solution?

Thank you.

Glen

*Edit: I'm a knucklehead, I was d/l'ing the tmo cm10 nightlies instead of vzn. Airheads anonymous....Lol...
[Verizon Samsung Galaxy S III] dougmod:
I am on M2 with a clean install. I have had it for about a week now and notice bluetooth issues. I notice it does not always connect to my devices. I have to turn bluetooth on and off a few times to get it to work. anyone else have this going on? i have been following the thread but have not see this
[Verizon Samsung Galaxy S III] nohbdyshero:
I had issues with earlier builds. I am back on TW stock rom and this is 1 of the reasons.
[Verizon Samsung Galaxy S III] TechSavvy2:
Lol, I did that once. Took me half hour to figure out why it wouldn't take, haha.
[Verizon Samsung Galaxy S III] kejar31:
how to fix the the artifacts that got included starting in 10/17 with transitions and

how to fix the the artifacts that got included starting in 10/17 with transitions and and youtube....

open Root explorer or Solid explorer (any filemanager with root access will do)

edit /system/build.prop

change this line from

debug.composition.type=dyn

to

debug.composition.type=gpu

reboot
[Verizon Samsung Galaxy S III] Jaegermeiste:
Absolutely glorious. No more artifacts.
[Verizon Samsung Galaxy S III] vmbgap:
I searched the thread and didn't see an answer.

Anyone else able to receive txt but people are getting your sent txt? CM10 was working for about a day and then all of the sudden my sent text weren't getting to people.
[Verizon Samsung Galaxy S III] mastamoon:
here is my unoffical build o'theday.. https://dl.dropbox.com/u/13144052/CM10/cm-10-20121023-UNOFFICIAL-d2vzw.zip current as of now 4:15PM EST compared to http://cm10log.appspot.com/?device=d2vzw plus a few other cherry picks.. avoid copybit, tcp tweaks, volume fix... and some gps tweaks.
[Verizon Samsung Galaxy S III] grin0048:
And just so people know, avoid copybit is the same modification that kejar31 posted a bit ago.
[Verizon Samsung Galaxy S III] cbunting:
I edited the file in JOTA, saved into a different location, then went into root explore and pasted it over the file under r/w mode, and it worked.

Anyone know why the hardware buttons don't allow you to change the volume when the screen is off (resting on your ear)

and also why the slider doesn't go past the second to lowest setting with the hardware buttons?
[Verizon Samsung Galaxy S III] kejar31:
Easy Volume fix until CM commits it

Here is flashable zip file with the in-call volume fix to help out until it gets committed.. should be able to flash it over any CM10 build...

Here is a link to the original Garrett Review change http://review.cyanogenmod.com/#/c/25249/
[Verizon Samsung Galaxy S III] Charm8er:
This does work! Thanks that was really starting to get annoying.
[Verizon Samsung Galaxy S III] fix-this!:
i just applied this on m2 but i noticed no difference? also probably a stupid question but is there any other fixes that can be flashed for people that want to stay on the snapshot builds?
[Verizon Samsung Galaxy S III] alee:
At that point you're not on an M build anymore though. The M releases are nice, but they don't hold any sort of special properties compared to other releases.
[Verizon Samsung Galaxy S III] Imatoasta:
I wonder if the new kernel commits will help the battery life on the new builds.
[Verizon Samsung Galaxy S III] ssmaster:
I just flashed the zip for the call fix and it works great!!!
[Verizon Samsung Galaxy S III] Zacharybinx34:
Just run the newest nightly starting tomorrow.
[Verizon Samsung Galaxy S III] Byonik:
+1 for me. Finally! Now just need the video recording volume fixed, and this is a true DD.

For me, battery life is equal or better on CM10-based ROMs. Go figure. As they say, YMMV.

Anyone truly troubled by poor battery life, do yourself a favor and go pick up two more batteries and an external charger. I always have at least two fresh batteries ready to go, and I haven't had to tether my phone to a charger for months. Best $20 I've spent.
[Verizon Samsung Galaxy S III] tv31284:
My connection has been really unstable lately, especially in areas with weak, but not terrible 4g reception. I think it started around the M2 release. I've tried numerous radios but nothing has helped aside from installing an older build. I wonder if this commit will help.

http://review.cyanogenmod.com/#/c/25130/
[Verizon Samsung Galaxy S III] NeoMagus:
downloading 10-24 now, its up
[Verizon Samsung Galaxy S III] NegativeOne:
Sounds like it's for Sprint LTE
[Verizon Samsung Galaxy S III] WhammyDroid:
The fix works (as it is not blaringly loud), but I cannot adjust the volume on the handset during a call.

Is anyone else experiencing this?
[Verizon Samsung Galaxy S III] abreeden:
I second this
[Verizon Samsung Galaxy S III] kejar31:
yea its pretty obvious that fix only adjusts the pre-set in-call volume, if you take a look at whats done in the change...
[Verizon Samsung Galaxy S III] cgulliver:
Agreed. Gain can already be adjusted in the DSP Manger. This may be more of a bandaid.
[Verizon Samsung Galaxy S III] xsteven77x:
There hasn't been any real changes or improvements since m2.

I don't know if it's the rom or Swype, but half the time I click on a text field and it takes thirty seconds for the keyboard to show up.

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

Mile stone releases are just the nightly from whatever day it was made with the "m" label on it.
[Verizon Samsung Galaxy S III] kejar31:
Never Mind
[Verizon Samsung Galaxy S III] JohnnyTToxic:
FWIW, I'm not seeing that issue at all, using current release of swype beta and haven't seen the issue you described on any nightlies (jumped in sometime just before M1 and have flashed every nightly)

This isn't meant to be some sort of "nyah nyah mine works must be user error" sort of post, but rather a post of encouragement/ light at the end of the tunnel sort of deal.

Maybe try to uninstall swype, reboot, reinstall swype using the official swype beta installer (not from TIbackup) and hopefully you'll be alright. I had some issue using TIbackup restoring older versions of Swype in the past.

Slightly unrelated: I just dled keymonk this morning and it's pretty slick.

TLDR: Mine works; hope yours can too.
[Verizon Samsung Galaxy S III] TechSavvy2:
Sorry I completely disagree. To me there is night and day difference between m2 and today's builds. M-snapshots will be better down the road, but its too early in development with too many major fixes being implemented all the time.

In-call volume, case and point.

---------- Post added at 11:31 AM ---------- Previous post was at 11:24 AM ----------

So is cm10 your dd these days? If so, GLAD to have you aboard!!!
[Verizon Samsung Galaxy S III] Zacharybinx34:
When is the YouTube graphics going to be fixed?
[Verizon Samsung Galaxy S III] That Baker Guy:
Im getting a glitch when i turn up or down the volume while watching a video. when the volume slider pops up on the screen it glitches and makes everything wack for a bout half a second. Sorry if this has been reported before.
[Verizon Samsung Galaxy S III] fix-this!:
I just wish cm10 wasnt such a battery hog for me.
[Verizon Samsung Galaxy S III] grin0048:
You can fix it now if you want to:

http://xdaforums.com/showpost.php?p=33177317&postcount=4989
[Verizon Samsung Galaxy S III] B_rock:
Go to settings then check "Disable HW Overlays".
[Verizon Samsung Galaxy S III] Zacharybinx34:
Why isn't it in already?
[Verizon Samsung Galaxy S III] alee:
It's in tonight's build.
[Verizon Samsung Galaxy S III] TechSavvy2:
Or run invisiblek, its all already fixed
[Verizon Samsung Galaxy S III] cordell12:
nevermind
[Verizon Samsung Galaxy S III] abissel22:
Anyone know where all this invisiblek stuff is? Sorry I'm a noob for some stuff. And anyone know how to get mono audio on cm10? It came with toutchwhiz and was pretty helpful. Also anyone know how to make the clock in center of screen? I'm on the M2 build.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] ef-civic:
http://goo.im/devs/invisiblek/i535/roms/cm10.unofficial.nightlies
[Verizon Samsung Galaxy S III] imp3r10:
Anyone else lose ability to unlock phone with home screen. When switching to 10/23 and if 10/24 fixed it?
[Verizon Samsung Galaxy S III] Raegx:
I have read almost all of this thread for references to Google Wallet and I am just looking for someone to confirm what I have read. If I install Google Wallet by following this thread I can still use the built-in CM Updater without first clearing Google Wallet's settings (in order to avoid breaking the 'secure element'). Correct?
[Verizon Samsung Galaxy S III] Jaegermeiste:
This
[Verizon Samsung Galaxy S III] mikejr83:
I think the OP of that thread may have replied to a recent post about this question. However since I'm the type that is overly paranoid about things when flashing the anything on my phone I'll clue you in to how I do it.

Every few flashes I make a backup. I flash updates to cm10 from the updater so there is not an option as far as I'm aware to backup then flash. Regardless I backup with a working wallet app. Before I update I just reset the wallet app and then perform the update. After the update is finished I just run the scripts I am the thread, flash the wallet app, and add my cards.

However, I have had the case where I forgot to reset secure element and I was able to go back to the working backup and reset it there.

It may be overkill but I still have a working wallet install.
[Verizon Samsung Galaxy S III] PerCompLLC:
All you have to do is modify your build.prop after updating (note: I use the Galaxy Nexus device changes). You will need to do this

every time

though as CM overwrites the build.prop file during install. Google Wallet settings will stay intact between flashes. There is no need to reset Google Wallet using this method (at least I haven't had to).
[Verizon Samsung Galaxy S III] NegativeOne:
Anyone else notice the following problem?

I set my lock screen to use a PIN. And I set a profile for home use that says "use insecure lockscreen", but it seems to have no effect on the PIN, which is still requested.
[Verizon Samsung Galaxy S III] qqhorus:
I'm getting 19 hours of use with my phone looking for service in my office and a lot of texting throughout the day while this is happenin, along with the a little web browsing.

I think that's pretty damn good.
[Verizon Samsung Galaxy S III] DriveEuro:
Would help if you would give an idea of how much screen on time. Without giving screen on time, its hard to say whether what you got is good or not.
[Verizon Samsung Galaxy S III] goldsmitht:
what kernnel are you using? I'm on KT747, and am getting fairly good battery use. Also, if you are having problems with your phone constantly looking for service, try uploading a different radio. HE works the best for me, and gives me the best service

:cyclops:
[Verizon Samsung Galaxy S III] Brian Gove:
For those of you that use better battery stats, what kind of percentage per hour are you losing overnight? In eight hours of non use, just sitting on my nightstand, I lost 1.9% per hour. I could have sworn on earlier versions I lost significantly less overnight. That I was getting closer to 1%.

My wake locks aren't that bad either, I don't think.
[Verizon Samsung Galaxy S III] d1ez3:
It depends for me, sometimes it takes a really long time to get into deep idle, I use battery monitor widget which shows me the %/hr I am using (after inputting the battery size). I can usually get around 0.7%/hr when idle on wifi. On TW ICS Roms sometimes I could get as low as 0.4-.5%/hr when idle, but those are rare occasions. I'm not sure what the parameters need to be in order to get such good idle because there are definitely times where it does not go as low.
[Verizon Samsung Galaxy S III] Flowah:
Has anyone here running CM10 used an MHL cable with success?
[Verizon Samsung Galaxy S III] NedDasty:
For Google Wallet I've used this thread (http://xdaforums.com/showthread.php?t=1810040) without ever having to clear out my GWallet settings, and haven't run into any problems. Sticks around after fresh CM10 nightlies installs as well.
[Verizon Samsung Galaxy S III] qqhorus:
Around 2-2.5hrs on screen time.
[Verizon Samsung Galaxy S III] Defragger51:
NFC Tapping app missing

I installed cm 10 10/23 on a friends SGS3, I have the same phone and the same rom. after wards I tried to NFC beam him a picture to no avail. I checked his phone to make sure NFC was on and Bluetooth was on , when I notice he does not have NFC Tapping as an option when trying to iniciate a share from his phone. I have NFC Tapping on my phone under the share options. have searched for 2 days and can not find a NFC Tapping app or apk . Anyone have an Idea why its missing and or how to get it installed on his phone. I tried to copy the files off my phone to put on his that was a no go also.
[Verizon Samsung Galaxy S III] Jay Evans:
Will the now released source code of the Sprint JB TW ROM help with the hardware bugs?
[Verizon Samsung Galaxy S III] Div033:
Is there any way to stop any AOSP ROM from killing off my backgrounded processes so aggressively? This is one of my biggest qualms with AOSP right now, it makes 2GB of ram redundant.
[Verizon Samsung Galaxy S III] Imatoasta:
I've been looking for a solution for awhile and haven't found anything. It makes 2gb pointless.
[Verizon Samsung Galaxy S III] landale:
I just wonder if it's because there hasn't been a real AOSP device with 2GB of RAM before. Perhaps with the release of the Nexus 4 next week we will finally see something that can address this.
[Verizon Samsung Galaxy S III] Div033:
Also call volume still isn't fixed, just quieter which is a nice band-aid in the meantime making it more usable. The call volume will still max out on a new call regardless of the current setting. Difference is max volume won't hurt your ear!

Edit:

Nevermind, its still loud for me. I did a full wipe (data/cache, formatted system too) so its a clean flash...

Edit 2:

Okay so the bug only seems to occur when I have the lowest or second to lowest call volume set. If I leave it on 3 or higher it remembers where it should be and doesn't automatically go up to maximum. Very odd, I wonder if its always been like this?
[Verizon Samsung Galaxy S III] Ty07allstar:
Yes. I was using the stock kernel.
[Verizon Samsung Galaxy S III] TechSavvy2:
Works fine for me.
[Verizon Samsung Galaxy S III] Div033:
Can you confirm that in-call volume, the sounds that come out of the earpiece when someone is talking to you, does NOT default to max volume (even though the slider says differently) when your in-call volume is set to the lowest or second lowest setting from the call previous?

Because it "Works fine for me" too when I have it set to the third or higher setting. I don't mind leaving it at volume level 3 if it means it won't be max on my next call, but I'm confused as to why it only occurs on volume levels 1 and 2.

Also, how did you flash the ROM? I use CWM 6.0.1.2 and I wipe data/cache and system, then flash the ROM, gapps, reboot. Is there something I should be doing differently to achieve proper in-call volume?

Or maybe my phone is a lemon and the new nexus can't come soon enough.
[Verizon Samsung Galaxy S III] fix-this!:
Flash another kernel. Im not having that issue. Battery life is whats bugging me.

---------- Post added at 06:19 PM ---------- Previous post was at 06:17 PM ----------

I must of had a wake lock. I lost 90% last night. Did a wipe and its better. Happens again ill go back to beans.
[Verizon Samsung Galaxy S III] Brian Gove:
The sprint leak has been out for a relatively long time. Granted I'm sure devs are still picking the bones but the meat of it has already been applied.
[Verizon Samsung Galaxy S III] mybook4:
I use system panel lite to see available memory. On TW based roms, I'd have around 300MB available (after opening many apps). On AOSP, I always have at least 700MB available. To me this means the memory manager is killing background apps more aggressively than the TW one. How much available memory are you seeing?
[Verizon Samsung Galaxy S III] neyenlives:
by now i was really expecting to see some devs doing some things never done before with all the extra ram....i mean, you should be able to leave everything always running in ram and create a much faster user experience than on a device with 1GB of ram right?
[Verizon Samsung Galaxy S III] BungeBash:
I'm having the worst time with Bluetooth audio syncing on my car. Playerpro keeps locking up pretty hard and won't play. My dash says the audio is playing but its not. The only thing that fixes it is a phone reboot. Once the phone disconnects if I step out of hte car I have to reboot to fix again. Also, still pretty disappointed I get no meta data sent to my head unit.
[Verizon Samsung Galaxy S III] Jay Evans:
No I'm talking Source Code on the Samsung Open source site. LJ7
[Verizon Samsung Galaxy S III] rgrossie:
I've never had NFC problems, so I don't know the precise details, but it's something like this: Flash a TW ROM, turn on NFC. Then flash the latest nightly of this. NFC should work. There is no NFC APK, it's built into the rom. Please do the search before listening to my advice though, I don't know the details. The answer is in this thread, probably about 100 pages ago!
[Verizon Samsung Galaxy S III] nohbdyshero:
this ROM is pretty close to a Daily driver at this point. Only big issue I am having is on bluetooth I can't use DTMF (like to call an automated system) and the phone app sometimes crashes. W/O bluetooth everything is fine. Been this way forever
[Verizon Samsung Galaxy S III] Imatoasta:
I love what the devs do but this just seems like a HUGE oversight.
[Verizon Samsung Galaxy S III] d1ez3:
http://review.cyanogenmod.com/#/q/status:open,n,z

good new for those who play a lot of audio, looks like LPA will be working again soon
[Verizon Samsung Galaxy S III] TechSavvy2:
I apologize for my vagueness and your frustrations both :)

To answer your question, yes, all volume levels work while in calls now. If I minimize it, I can barely hear it. Hang up and recall, I can still barely hear it. Turn it all the way up, its much louder (granted the incall volume bug kinda gave the term "loud" a new meaning recently, lol). If I hang up and recall at same volume, its still louder. Point being, it always stays where I most recently left it at. Seems to work exactly how it should for me :)

I can tell you that I had dirty flashed this over older builds. That's honestly all I did, although I know a couple people said they had troubles with it also until they did a clean install of it. And by clean install, I only mean wipe data, wipe cache, wipe dalvik, install, install, reboot.

Hope that helps :)

EDIT: And for your last comment, we ALL want Nexus devices.....ALWAYS.....;)