yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
After you get 10.1 installed fresh, then yes, I guess flashing nightlies on top of it will fly. But any issues that crop up after a dirty flash must be assumed to be caused by dirty flashing. Most Devs agree that it is best to clean flash but some only do it when there are framework changes..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ak789:
How about camera and photosphere?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dLo GSR:
yup, works great!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Why report it if it's because of a dirty flash.

No, the move from 4.1.to 4.2 is not nearly as drastic as from 2.3 to 4... but why do you think there are so many things that are not present any more in 4.2? Like the Bluetooth bass problem, home/power button non-wake ups, SODs and random reboots... gone. This is a different OS, These things were not fixed in 4.2, they NEVER existed in 4.2! That's why they were never fixed in 4.1... why bother fixing an old (at this point) operating system.

The thing is that is you didn't clean install 4.2, some of the problem from 4.1 are still there... you had any RRs or n SOD yet? How about your Bluetooth bass?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
I had the same issue with euroskank nightly..I pulled gallery2.apk from the unofficial cm10.1 build and pushed it to system/app, deleted the existing gallery.apk fixed perms to match all other system apps and camera was fully functional after that..except the photo-sphere deal thingy

AT&T SGS3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] knarfl1:
Phone quality and data (hspa, hspa+ and LTE) are fine on my s3.

It's pretty simple: Dirtier your s3, buggy-er your phone will be.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thresherhorn:
So I tried moving back to 10.0 to attempt to see if I could stabilize my problems and in turn created more problems. So I've aquired a boot loop, will now be Odinning back to stock and attempting to redo everything.... Can't blame everything on CM10.1 though, it was an inadvertent dirty flash. Just wish the CM updater made it more prominent that it was 10.1 ... blargh
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
really... that was a tough break...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackroseMD1:
Running smooth so far aside from SU force closing all over the place. Guess I'll just wait and see what the next nightly has in store.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
your one of the lucky one then..a dirty flash doesn't have anything to do with the bug that's screwing with data connectivity .. I always fresh/clean flash any ROM I use but the last two 10.1 nightlys have been the same as far as data go..Im pretty sure the ppl without workable data far out weigh the ppl with working data..but I'm sure cm knows about it..task already knows about it..

AT&T SGS3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mtl171:
Flash the SU from this thread: http://xdaforums.com/showthread.php?t=1538053 and update in playstore. Should fix your problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] funkdoobi:
Odin'd back to 3.07 rooted Rogers stock rom and now I'm stuck on Samsung logo on the boot up. Any suggestion to if I missed something?

Odin passed just fine as well.. Not sure what else to do?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arcticrobot:


Boot into recovery and do factory reset/wipe cache
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackroseMD1:
Awesome. Thanks man. Worked perfectly.

Sent while hanging with that really hoopy frood Ford Prefect.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] knarfl1:
I'm not talking just about dirty install. Even if you do a clean install, your device can still be dirty.

I should have said "More virgin, less the germs on your s3." :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Go into recovery and factory reset
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dubmusic:
SIM card with active PIN failing on CM10.1

Interesting issue. When upgrading to CM10.1, after setting the mobile networks to the appropriate setting (LTE/GSM/WCDMA), the phone refuses to switch data on. This seems similar to the issues encountered by many here, so I attempted a reboot to investigate. When the phone booted back up, it asked me for the PIN (as usual), prior to logging into the phone. After entering the PIN, I was presented with the notification that the SIM card has been added and that the phone would be restarted. Again, the phone rebooted and the as mentioned, notification repeated with reboots and, unfortunately no sign of functioning data.

It seems that there is a process registering the SIM that is either not correctly recording it, or simply not checking for it's status upon reboot. I reverted back to CM10 for now. Other than that issue, most of the functionality I rely on worked and besides that, it looked great and ran smoothly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] calvin35:
If your data won't work after flashing 10.1 you should try simply calling someone to see if that will get data working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dubmusic:
That would be nice to try once I get out of the SIM card registration loop. It seems to be a different issues, possibly only affecting situations where the user has a SIM PIN that is required after a reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thresherhorn:
So finally back up and running after my boot loop fiasco. And some good news all around. Just to document my experience on what has and has not worked.....

1. Should have re-read 1st post fully (overwriting gallery/camera with ANY VERSION gapps will break the camera -- still broken for me with 12/12/12 and the 11/26 "fixed" version) -- the standard camera/gallery that come with cm10.1 do work

2. Data is working as best it can (data cycling fixes the issue until reboot) - also I did mention earlier in this thread I was having terrible 4G speeds, however I kinda forgot I traveled halfway across the state yesterday... new network towers probly have more to do with this problem I'm currently experiencing than 10.1 does

3. Superuser is broken (fixable by flashing SU a few posts back)

4. With clean flash my graphically odd google search bar is back to normal

Those are really the only 4 major flaws I've come across that are either fixable / have workaround / curable with clean flash

Pros vs cm10

1. I Honestly feel it's smoother than latest cm10 nightlies (might be placebo, might be the fact I clean flashed)

2. No more wakelock problems - you click that power button/home button and she's coming on!

3. New goodies to play with (notification bar, lockscreens,

4. Bluetooth with BASS!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] primod808:
developer options in setting option

was developer options not in the 12/17 build?

thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GilaMonster1:
I know this is kind off topic of most people talking about 10.1

But a few questions.....

1. Are the camera options just poor or what compared to Touchwiz's quality?. I Download FV-5 which is a more professional app with a lot of options, but even when I take a decent picture in it, it is still worse than the Touchwiz camera. There is a lot more noise, it isn't as focused, the colours aren't as crisp. I mean the are still good pictures, but if Touchwiz is a 9 for camera, this is like a 6. I've tried a few camera apps and none of them are as good.

2. Same thing phone call quality. It is just isn't as good as it was. It was almost like using a landline on Touchwiz and the noise filter was excellent. CM10 makes it sound like my old iPhone 3GS
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
My data is super sporadic as of now. Yesterday it worked fine through 2 reboots then today after an abnormal one it stopped, and I can't get it working again. Fixing permissions and wiping cache and dalvik don't work either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sublimejosh2000:
USB Dock Audio Routing is Borked... Just FYI.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
So I'm assuming there won't be anymore cm10 nightlies released by the cm team? It will just be cm10.1 from now on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] robg2008:
I see a lot of people complaining about not seeing developed options.

Go to settings>about phone and scroll to the bottom of that page

Then repeatedly press the last option I think its build version or something like that. Keep selecting it rapidly around 7-10 times and it will tell you that you are now a developer and you can go back and see dev options.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
I can't get Portable Wi-Fi hotspot to work?

It worked on the first boot but now it looks like i can toggle it on and off but the icon never comes up in the notification area showing it's on and it doesn't show up when i scan for wi-fi.

I've tried rebooting several times to no avail.

any ideas, has anyone else tried it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lothos:
The last nightly probably has all the changes to the cm10 branch that have been made. If not, you can always build it yourself. It isn't hard and only takes a couple hours of build time to make one target.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Latest build no data or signal connection
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vitalious:
battery icon

Anyone else notice that the option to change the battery icon is now gone?

Also, my profile override settings keep nulling out with every phone reset.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djjuice:
for those with having data problems. This worked for me. I went into the Mobile network settings and deselected data enabled/re-enabled it. Now i had it do it twice, as the first time just sorta reset it, but the 2nd time it was solid. Hopefully this works for you till a fix is in place
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
Do this

Until the 12/18 build, I only had to cycle mobile data between reboots. Hopefully this is a more permanent solution, but I need data at the moment so I'm not going to reboot yet to find out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ARchamps:
Stupid question incoming. Where is the 12/18 build you speak of? Not in the nightly link in OP
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gordietm:
http://jenkinsmanifest.clockworkmod.com/device/d2att/all

Sent from my Samsung SGH-I747M
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BlackDino:
This doesnt really help because ADB seems to not be working in the latest builds
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
Just noticed it's not on get.cm. It did show up on CyanDelta for me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smelenchuk:
Eh? It's working fine for me (so long as you remember to go and (re-)activate USB debugging in the developer menu).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BlackDino:
maybe its a mac incompatibility, any time i plug my phone in it doesn't even recognize a device is connected
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] argus1185:
Anybody having issues with "0" folders being created in the main sd card directory. how do you get rid of these, or rather how do u install a clean flash of CM10.1? w/o the left overs from 10.0...stupid questions but im curious. Thanks =)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smelenchuk:
The initial /0 folder is created by any 4.2 build as part of its multiuser support - you get a /0 to hold data from the first user, a /1 for the second user, a /2 for the third user, etc.

If you're getting recursive /0/0/0 folders, it's due to an issue with recoveries wiping the /data/.layout_version file which indicates that the /0 move has already been done. TWRP 2.3.2.0 and above have this issue addressed; I do not know if CWM has addressed this yet or not.

If you do have nested /0/0/0 folders, people have generally just been able to move the files from /0/0/0 to just /0 (if staying on 4.2) or to the top sdcard level (if going back to something 4.1-based or earlier).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thresherhorn:
Awesome! I thought they just didn't add it in this build. Sneaky sneaky. BTW, overnight battery test looking great so far with 12/17.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bradhoschar:
Great ROM!

This is very stable for me!

My OcD always makes me wipe everything 3 times just to be safe!!!

After the wipes, installed 10.1, flashed the latest 4.2 GAPPS, and BAM!

Im showing 4G, but im getting LTE speeds....

No issues as of yet!

Keep it up dev's!!:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] argus1185:
would it be ok to deleted the 0 folders, if you are running cm10.1?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shaker2k:
Is the 12/18 solid? Are there still data issues?

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevemiana:
Im getting camera issues, it stopped working and then it says cant access gallery, any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
LTE = 4G
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Maroon Mushroom:
Updated to 12/18 and my data connectivity died.

Tried flashing a new modem but the installation keeps failing... I'll have to find a new way to flash it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tony_YYZ:
make sure you're flashing the correct GAPPS version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevemiana:
I flashed the fixed on, do u know which one i should have for the 18/12 build?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tony_YYZ:
Try the 12/12/12 version from Mike Ramsay: http://goo.im/devs/itsmikeramsay/gapps-jb-20121212-signed.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
No matter what I do (and I followed your instructions religiously), I cannot get any data on my new SGS3. Mind you, we don't have LTE in town; nevertheless, I guess it should work fine on HSDPA, right? (Running the 20121218 CM build, on i747UCDLK3 modem.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Maroon Mushroom:
Same issue here. If you disable mobile data and reboot you'll at least get a signal. But no data.

Try flashing an older modem? I'm at work so I can't test this
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenji117:
Did you try the following steps?

1) Turn off Data

2) Reboot phone

3) Wait 30 seconds

4) Turn on Data

That seems to work for me also try flashing the justunbean gapps. I wasn't getting signal with the 12/12/12 gapps from Goo.im but everything has been working great with the justunbean gapps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smelenchuk:
If you want your data back, do that first, then change your APN to something else and change it back; you should then be able to enable mobile data and have it work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevemiana:
Still same problem
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevey500:
Running 12/18 right now, no data.

Flashed a modem, wiped cache/dalvic cache and data is still dead. I totally forgot to disable data before flashing anything though. 3G popped up for a split moment before it went to no signal, came back full signal with no data.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smelenchuk:
By "folders", do you mean you're seeing a /0/0/0 tree like I described?

If you are running CM10.1 (which is 4.2-based), you probably want to retain /0, but anything nested more deeply than that can be handled in the manner I described.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
When that happened to me I toggled airplane mode for 10 seconds and then back off and it came to.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kennyaa:
Wifi Hotspot doesn't seem to be working for me. Anyone else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Cyanogen himself said a wipe is not needed to go to 4.2.1, only to install it manually instead of the Updater https://plus.google.com/+CyanogenMod/posts/9X561GFMxL5 I think I will wait a week or so and give it a try again, hopefully the bugs will be worked out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Is anyone running Ktoonsez's 4.2.1 kernel with CM10.1? If you are, how's it working? Are you getting data if you follow the workarounds?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevemiana:
Anybody to help with camera problems, doesnt work for me even after installed latest gapps
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Ktoonsez's kernel will have no effect on data. Data works the same with cm kernel or ktoonsez kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mtl171:
Ktoons works like a charm. As for data, disabling, rebooting, then renabling after reboot seems to work most of the time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bostonirishguy13:
Not working for me. Just stays at "Turning hotspot on..."
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
Thanks, no workie, no matter what I'd do. Haven't tried the justunbean gapps, though at this point i'd rather stick w/the regular gapps. I think it's pretty clear that there's an issue with the 10.1 releases (or at least w/the latest one).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tony_YYZ:
did you wipe cache/dalvik and fix permissions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bostonirishguy13:
Weird LTE Speeds

I'm on 10.1 (12/18 nightly) after clean installing 12/17 yesterday. Data is working, but the LTE speeds on speedtest.net are weird:

2-9 Mbps down and 65-177 Mbps up. On 10, I'd average about 30 down and 12-15 up.

I'm in a solid coverage area in downtown Boston.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Why is the 12/18 build on other sites like cwm but not get.cm?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevey500:
Same here.

Disabled data, rebooted to recover, flashed modem, wipe cache, dalvik, fix permission, reboot,... optimizing......

booted, waited a few minutes, enabled, data... service indicator dropped, waited a few moment, service bars came back, no data. I'm in a 3g/H+ strong signal area.

Deleting the data folder for the Phone/telephony app, will that maybe work? Hmm. I haven't dealt with telephony in android since editing CDMA radios of HTC's and motorolas before the simcard days.

Edit:

In *#*#INFO#*#* I see that it defaults to LTE/GSM Auto (PRL)

Where in all roms before and stock rom I swear it used to be LTE/GSM/CDMA auto (PRL)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
It seems that you are going to have to do a full wipe to resolve your problems if a reflash doesn't get it....

Maybe clear data for camera?

---------- Post added at 01:19 PM ---------- Previous post was at 01:18 PM ----------

Nope, no hotspot for me. It appears to be turning on but my laptop doesn't see it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
GPS

Seems 12/17 GPS was able to find location with 12/18, it's not able to even find location -

Does anyone see this? Does anyone know if it's been added to the 'fix' list?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
I've never had an issue with zero signal. I've always had a signal, just no data connection. I do notice though at times before I apply some sort of fix I get a data icon briefly (<.5 seconds) then I lose signal for about 5 seconds. It comes back to signal, but no data. Almost seems as though something is crashing the instant it gets a data connection.

Yesterday, I tried a number of different things (reflash modem, toggle data, APN changes, and APN shuffling) but what finally worked was toggling to a different APN, back-buttoning all the way to the home screen, changing back to original stock ATT LTE APN, backing to home, then toggling data off/on. I don't know if or how what I had done earlier in the day impacted my success.

This morning after I flashed 12/18, I had to disable data, reflash modem (using LH1, but I don't believe that matters), then reenable data.

All I can say is that as long as you have an intact IMEI, some combination of the actions above should get you working. I do believe that time is a factor and that performing those sequences of events in rapid order can have a different (ineffective) outcome, so take your time. Wait ~30 seconds between each step. Once you do get it working, it seems that all you need to do is toggle data off/on after reboots.

Also, I'm in an LTE area but all I have to do is walk into my office at Faraday Inc to get nothing but mediocre 3G. It works, but I never get H or H+. I'm not sure if those icons were deprecated in 4.2 or if there's still underlying issues with the data connection.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lothos:
Same here. I built from the latest source this morning and no go. I get data instantly after restoring backup. Sucks...!

People that get your data working, can you report if you are in a 4G/LTE area or only an HSPA area?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kswa1987:
I'm guessing its been independently compiled... 12/17 has some issues but I'll most likely wait until the next official nightly as I have been able to fix the no data problem using the methods discussed in this thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
True on the combination of various toggles and wipes/permission fixes it gets data working eventually, but for me i found even if i do turn off data before reboot, it will not come back up after unless i go through again all the various toggles / wipes / fixes... and even those various toggles / wipes / fixes are not consistent, same combination that worked first time, does not work second time :) so it's just a matter of being patient and keep hammering at it, until data is back. Then don't reboot :D:D:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] marinierb:
I fixed my data problem by putting a proxy ip and port in the APN settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
How are the wakelocks in 10.1?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Interesting, are you on ATT? what was your proxy IP? i just pinged proxy.mobile.att.net (ATT proxy) and got 67.215.65.131
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevemiana:
this 18\12 build is the worse ive flashed to my phone, battery life very bad, camera not working properly, data problem, phone heats up like crazy

I was wondering if I can just flash back to an unofficial build without wiping data?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
I'm in San Diego (east county right now) with excellent 4g. I'm on 12/18, flashed via cyandelta with 121212 gapps and navbar mod, on ucdlk3 modem. I lose data on reboot, disable data for about 30 seconds, flip it on and it's stable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] assaf.bm:
I couldn't use cyandelta as it gave me an error in recovery:

"SD Card marker not found"

Any idea?

Also it seems as the superuser keeps force close when i use cyandelta.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t3chn0s1s:
You can do anything you want.

sent from my Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ARchamps:
Did you make a nandroid backup? You could just revert to that. I flashed it last night too and no data. I didnt want to rely on workarounds so I flashed my backup I made right before.

I would wipe because some issues may linger if you dirty flash. Just my opinion.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
No, I can't get it to work :( confirmed with at least one other, now you.