yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pseudoware:
I have this problem w/contacts where their phone number has been stored with a "1" before the area code. I think the "1" was preprended when I just "save to contacts" from the call log, and just save as is, w/o modifying the number. I believe such contacts were not saved with CM10, but were saved to the cloud with a prior ROM or device altogether. If there is no "1", the above steps do not re-produce this problem. But yeah, the ROM s/b smart enough to handle the "1" properly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adamt19:
Agree the OS should handle it.. I wish I tested this on stock ICS. My screwy contacts list is due to 5 years of owning iPhones, which, as you might guess, "just worked" with whatever number format I used ;)

I installed this app to clean up all 1700 of my contacts within 30 seconds..

https://play.google.com/store/apps/details?id=org.peterbaldwin.client.android.cleanup

All my contacts had area codes, but the app still requires you to set a 'fall back' area code for numbers where one isn't defined.

I knew that the only numbers in my list without area codes would be from where I grew up, Maine (207), so I used that, and obv. 1 for the country code.

The app gives you a chance to scroll through all of your affected numbers and perform some QA on what it is about to do, before it does it.

Now all my numbers are formatted: +1-123-456-7890, and they all work with the messages app :)

I just took a spin through my contacts in the Gmail desktop web-app, and they had already been synced back to the 'cloud'. The whole process was really quick. I DID make a backup (CSV) of my original contacts before doing all of this.. (in the desktop web app: select all contacts, more -> export -> csv..)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenji117:
I followed Bnaughty's super clean install method and now I am having an issue with restoring apps via TiBu. Titanium backup won't restore Apps, just Data. Anybody know how to fix this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adamt19:
are you setting the backup location (presumably, on external SD, where you hopefully backed your apps up) before running the restore?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenji117:
I backed up to the internal but, it knows where the folder is located as its able to restore data for the previously installed apps. I.E. if I install the apps from market place it restores the settings and such but they seem to be glitchy as I did it earlier and my Apex Launcher was resizing and moving widgets on its own.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
I didn't have access to a desktop... and using tapatalk is a pain to edit posts... list is now updated... thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] msgnyc:
I had the contacts issue when sending texts on my X10 2-3 devices ago. Its something to do with the formatting of the number. I just removed the 1 before the area code of all my contacts and hadn't had an issue since. Its not the area code that is getting cut off, it is actually the last # getting cut off that's not allowing texts to be sent.

so rather then 1 (123) 456-7890 all my numbers are stored as (123) 456-7890 now.

The OS seams to handle dialing 1 first just fine on its own for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kschumake83:
And you have to turn volume all the way off then back on. I played with the volume before I posted, but it now works after I toggled it completely off then on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dx9:
A new Nightly 0827 just finished compiling on Jenkins.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naturefreak85:
Mass Storage won't work with the ext3/4 based file system. It has been this way for any device that offers the full internal storage for ANY media. No workarounds for it AFAIK. Just use either Air droid or MTP

---------- Post added at 07:23 AM ---------- Previous post was at 07:20 AM ----------

It is a bug...and a big one for some of us, but not for everyone. Texting works even if it is broken but it still works. Nightlies will first focus on show stopping bugs, then cleaning up code. If Volume doesn't work then that's a show stopper....same thing with Netflix/LEDs. May not be a show stopper for you, but the basic functionality is missing.

Keep in mind SMS is Short Messaging Service. Never designed for long texts. Yes I want it since that's how most of my friends communicate, even though longer messages are better suited for email but that's life.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peaster3:
There is a free app on the market called Root Checker. It will confirm whether you're rooted or not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doctorspeed1:
Anyone having problems echo with the 827 build ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naturefreak85:
Considering I don't see anything in the changelog that I can think would apply to the Echo? The issue is still likely there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EvilOmniscience:
Latest build may have a bug with auto brightness not working.

I'd look into it more, but I'm not in a position to do any real testing right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BklynB3ast70:
any way to fix the low recording volume.. everything is low and i cant find a fix.. any help would be appreciated..:)-
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] d2k12:
Found an issue in the 8/26 build. Sound still comes out of the speaker when headphones are plugged in and no sound on headphones.

Edit: A reboot fixed it. Not sure what triggered the headphones not to work when plugged in.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] atlaswingpasaway:
Mine leaks ringtones out the speakers even if the call audio and music are still in the headphones.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sultanqasim:
It seems as if the low recording level issue is still present, and I prematurely thought it was fixed, however cyanogen has a fix for it in the pipeline.

Gerrit link: http://review.cyanogenmod.com/#/c/22237/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Deputy13:
I haven't had a single one
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pellel2:
Faux kernel was working fine on 25.8 but on the new build it is very choppy and sound problems. I reverted back to cyanogen stock kernel and no problems
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Deputy13:
Nope
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Artimus009:
When I first flashed this nightly, it worked fine but then had to re-flash gapps and now its low...can wait for the fix....:(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Deputy13:
I can't reproduce this either
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pellel2:
Any feedback on 27.8? So far so good over here

---------- Post added at 02:42 PM ---------- Previous post was at 02:40 PM ----------

That method is the best I haven't had any reboots either and I flash a lot of crap in this phone lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EvilOmniscience:
I've noticed that the auto brightness does not seem to work however otherwise so far so good
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sultanqasim:
Does anyone else find scrolling through a longish list of browser bookmarks in the stock web browser to be slow, choppy, laggy, at a very low not all all buttery framerate (I.e. around 7-10 fps)? Its a minor issue, I'm just wondering if others have it too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] patmann03:
I have this issue as well. If you choose the user from the phone book and choose to create a message it works, but if you choose the user from the messaging app the formatting will get messed up. Annoying but there is a work around.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sublimejosh2000:
Yea, I am having issues with a LWP. When I unlock the phone, it is very choppy and slow, the whole phone gets into a funk... the LWP is choppy in the back ground as well. I have to remove the LWP, I was using the New ocean HD. I have never had issues with LWP before the 8/27 nightly.

Looks like this revert may fix it in the new nightly..

http://review.cyanogenmod.com/#/c/22235/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] patmann03:
Thanks for this! Made all of my phone numbers formatted the same and the messaging issue is fixed as well. I had a work around for the messaging but it was annoying.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pseudoware:
Auto-brightness works for me on 8/27. FWIW, I did a full wipe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sublimejosh2000:
Logcat for the Choppy LWP...

https://docs.google.com/open?id=0BxsDZT2VS-_2cXdHbmllS041dWs
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LanceM:
Still having to sometimes hit the speaker phone button and then back to normal to hear phone calls. Kind of use to it now, but wanted to report it. This is with the 8-24 build. Upgrading to 8-27 in just a sec.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheFiveDots:
Not sure if it's working or not, but they did definitely merge in some changes to the backlight code:

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

However, it doesn't look like the front-end settings options for the new code has been merged yet:

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

Could be causing some issues.

Not much value on reporting a bug from 4 builds ago.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vashht:
My APN's disappeared when doing a dirty flash on 8/27, can someone post a screenshot of their ATT LTE APN settings for me?

Edit: NVM did a reboot and they came back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EvilOmniscience:
I normally don't. So far until now it hasn't been that big of an issue and hasn't caused any problems. But I suppose I was due for at least 1 eventually.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
Anyone else's music hiccups for a split second randomly? Logcat doesn't seem to oshow anything.

Wiped and flashed 8/24, then today dirty flashed 8/27, no change in this behavior.

No such problem on stock, so it's not my sd card crapping out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] captiv123:
Hi

Sorry if this has been asked before;

I just loaded up 08/27 and all seems fine except when I load power amp for music, it says there are no files. And I have to re scan my system every time for it to recognize them. I did not have to on 08/26. Any idea why?

My music is on the internal SD card.

Could it be related to ROM manager?

Any help would be much appreciated

Thanks :)

Loving the ROM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JediSooner:
I searched this thread for "camera external sd" and didn't find anything. Is the option to save photos to external SD not there because of the duplicates for some of the options that are in the camera settings? Or am I looking in the wrong place? I'm on the 8/26 nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hartford:
Just wiped all / reset all and installed 8/27 build. The only problem I am having as of this moment is that the in-call volume, both ear piece and speakerphone, is almost non-existent. May have to go back to an earlier build if this isn't addressed immediately as it's really vital.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bostonirishguy13:
Ran into an issue following the instructions.

Wipe Data \ Factory Reset

Wipe Cache

Advanced => Wipe Dalvik Cache

Mounts and Storage => format /system

Mounts and Storage => format /data

Mounts and Storage => format /cache

Advanced => Reboot Recovery

Got this far and hit reboot by mistake. Now the phone is stuck on the "Samung Galaxy SIII" screen. Tried to manually reboot into recovery by trying both volume up/home/power and volume down/home/power, with no luck. I tried to connect via the Samsung GS3 QCom toolkit. No dice

What's the best course of action?

Wipe Data \ Factory Reset

Wipe Cache

Advanced => Wipe Dalvik Cache

Mounts and Storage => format /system

Mounts and Storage => format /data

Mounts and Storage => format /cache

Advanced => Reboot Recovery

Wipe Data \ Factory Reset

Wipe Cache

Advanced => Wipe Dalvik Cache

Mounts and Storage => Mount /system

Mounts and Storage => Mount /data

Flash ROM

Flash Gapps

Advanced => Fix Permissions

Reboot system now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
Do a battery pull. Hold down home, volume +, and power. When the screen first flickers, let go of power. When the samsung screen comes up with the tiny blue text and the top, let go of home and volume.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bostonirishguy13:
Thank you. I'm back up and running!

I had originally dirty flashed 8/27 over 8/24, and appeared to lose LTE connectivity. Went back to wipe everything and reinstall, and my big fingers did me in.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doctorspeed1:
Same problem on Google music and Apollo for me. Never could pin it down. And it doesn't always happen either. My music is on extsdcard all well so i wonder if it would still happen if i moved out to the internal sdcard
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] patmann03:
Hmm, I'm still having issues with Google Voice playing voice mails over the speaker (works fine if held to head). I don't recall if this used to work on an earlier CM or not as I got CM on the 8/18 build. Not sure if this is an issue with Google Voice and JB or with the mod itself.

Anyone else having this issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheFiveDots:
The feature has yet to be added to CM10.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] d2k12:
Can somebody please confirm if NFC works on the 8/26 or 8/27 builds? I still cannot get NFC to work. Thanks.

It remains like this when I enable it:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gabik123:
Hey guys, I still can't get my phone to dirty update a nightly without an error message. I updated to cmw 6.0.1.2 but no difference. If I want to do a clean setup and then restore my apps and text messages, is that just titanium backup and restore? I'm still learning android... Ios convert
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
download sms backup & restore from market to backup your text messages, backup everything else (launcher settings, dictionarys, ect), then backup all apps with titanium backup. also i like to make a checklist of cm settings to easily restore everything after a full wipe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Electroz:
Works fine for me. You don't happen to be using a cheap 3rd party battery do you? The NFC antenna is built into the battery.....

That, or if you were using google wallet previously, I hope you disabled it prior to flashing a new rom....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] d2k12:
I tried my buddies battery and had the same result. His works but he is still on the preview build. I never used google wallet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thracky:
No issues enabling/disabling NFC here on any builds from the last week including 08/27
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
I'm on the latest 8/27 nightly and for some reason media is pulling the most battery. I'm looking under battery in settings and it's the highest one. I don't have any music apps to sync. Anyone else getting this?

Transmitted from my GALAXYSIII running Jelly Bean. XDA premium
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] madkapitolist:
THANK YOU

Thank you so much for getting netflix to work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adamt19:
or someone can just look for superuser? or, perhaps it's not installed with all rooting methods?

Make sure you test with a number formatted as described: 1 (***) ***-****. Try sending a NEW SMS to someone with a number like that. Thats where the bug lies..

youuuuure welcome ;D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naturefreak85:
Stick with Backdrop root https://play.google.com/store/apps/details?id=com.handyandy.backdrop&hl=en it will back up your MMS as well as SMS
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thracky:
Am I going crazy here, or has the 4G indicator been replaced with the HSPA+ "H+" indicator?

It's possible my 4G signal just sucks here in my office but I've never seen the H+ until now, and I did have 4G/LTE before I flashed 08/27.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheFiveDots:
I feel like something here has changed as well. However, I'm in a non-LTE area. Previously only saw 3G and H, today I'm seeing 3G and H+ after flashing 08/27.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aznkenshin:
Mine isn't at the top. Did you do plenty of downloading though?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheFiveDots:
Confirmed, formatted like that there is a bug.

1 555-555-5555 works, 1 (555) 555-5555 does not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ainen:
It now accurately shows what you are connected to. "H" was for H and H+, now they are separated. If you have LTE it should just say "4G"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thracky:
Ahh thanks for the clarification. I know my 4G can be a bit spotty in here so I just wanted to be sure.

Had I not been lazy and checked the changelog, I would have found this. http://review.cyanogenmod.com/#/c/21869/

:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ainen:
No problem! There are currently people installing the LTE transmitters on my tower so I am very much looking forward to using LTE again! I got to use it for a day and have missed it ever since.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeathKoil:
Call audio bug is present in 8/27. I just got a phone call and had no sound at all until I turned on Speaker then turned it back off again. This of course results in the Echo bug, but at least I could hear.

Can someone tell me when the call audio being silent until you toggled speaker back and forth showed up? Is there a build without it? IIRC 7/29 didn't have it, but I could be mistaken.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thracky:
I had a call come in earlier today when I was still on 8/26 and had no issue. Haven't tried calls on 8/27 yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeathKoil:
It doesn't happen on all calls. For example, I just now got a call and audio worked fine without having to toggle the speaker, but the call I got before that was silent until I toggle the speakerphone on and off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adamt19:
Thanks!

Now I just need to figure out how to submit this bug to the actual CM10 team. Pretty sure they're not combing all of our Q&A threads for leads..

if anyone knows what/where the mechanism is for submitting real bugs, please advise!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drwx:
as far as i know, that has always been a problem. When I got my first android phone, I had to run through my contacts and reformat them to all use dashes and no parentheses.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gleonard3:
I don't think they actually officially accept bugs on Nightlys. Only on RC's. So we get what we get.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Deputy13:
What's wrong with nfc if you didn't doable Google wallet before flashing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] d2k12:
Would somebody please post the nfc.apk. Thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheFiveDots:
I'm guessing that for security reasons it ties your wallet account to the ID of your NFC unit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naturefreak85:
I don't use Google Wallet, but I would suspect as long as you don't wipe your phone during the flashing process you won't brick your NFC. The bricking happens when the Secure Element is wiped. Thus, not wiping should retain the NFC work with Google Wallet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
As far as I understand it, even if you broke your secure element, NFC would still work...just not for secure payment systems such as Google Wallet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stickem601:
I'm having the same issue with the Sgs3 going in a reboot loop once the MHL to HDMI cable "11 pin" is plugged into the phone. And now with all the other roms using sources from cm10 its happening with those roms as well. I've also tried the 5 pin mhl to see if it would work, but it's not responding , as it should not. So there is something in cm10 that's effecting video/audio out cables "MHL".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dschamis:
I have dirty flashed over Google Wallet many times - what happens to me is that it obviously doesn't cause any issues with the NFC, and but the install removes Google Wallet so I have to reinstall it (with changing get the build.prop, etc.). This seems to happen whether or not I also flash GApps when I flash the nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
I've done it many times too without a problem. However something (not sure what the scenario would be to cause it) can go wrong that breaks the secure element forever ruining your ability to use Google Wallet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dschamis:
Agreed - that's why my process for a new ROM flash is:

Google Wallet => Settings => Remove Account

Titanium Backup = > Uninstall Google Wallet

Wipe Cache / Wipe Dalvik / Flash ROM

Make sure things are generally working

Change build.prop file

Reboot - reinstall Googlw Wallet from ZIP

Setup account (always get that welcome to Google Wallet email)

Change build.prop back to original

Reboot and wait 24 hours
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] patmann03:
I had a battery drain today. Lost about 20% of the battery for no reason, no apps were running, phone wasn't active much and didn't have the screen on. I use tasker to turn on and off the data connection since exchange and the other email polling kills the battery if data is left on. I had this issue on stock, but hadn't had it until today on any CM build (could have been lucky). Not sure if anyone else experiences this as well or has experienced it in the past.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
Okay, wait wait.

So if I had Google Wallet installed on the stock firmware, and then did nothing to it, went into recovery, wiped everything and installed CM, I'm completely ****ed with regards to Google Wallet working?

EDIT:

According to this website, I can restore my backup and **** will work. I will get back to you guys if this succeeds (probably tomorrow).

QUESTION:

Does google wallet immediately say "can't communicate with secure element" if it's fried or not?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] keeper22:
I am also not able to play audio out of the dock when connected.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dschamis:
Which nightly are you running?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheFiveDots:
Frequently flashing ROMs will mess with your battery reporting, so I'd take it all with a grain of salt until you've run through at least a few more cycles.

That, and the 08/26 build adjusted the battery capacity to the correct 2100mAh instead of 1800mAh.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] privatedoodle:
The changelog for 8/27 says that a UMS option is enabled. Anybody figure out how to turn on UMS?

I manage my music on a Mac and I'd love to be able to connect the phone via USB.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] colin.hristow:
I noticed the same thing with this build. Im on Rogers and have access to the LTE network. Because its an ATT build, 4G symbol represents LTE. If you are in an LTE area you should get really high speeds of sometimes 50mbps which is not 4G.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
STOCK

GPRS = GPRS

EDGE = E

3G = 3G

HSPA = 3G

HSPA+ (aka 3.5G) = 4G

LTE (aka 4G) = 4G LTE

REAL (CM version)

GPRS = GPRS

EDGE = E

3G = 3G

HSPA = H

HSPA+ (aka 3.5G) = H+

LTE (aka 4G) = 4G

Don't fall for AT&T marketing traps. What they tell you is "4G" is actually 3.5G, while what they tell you is "4G LTE" is actually 4G.