yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mastarifla:
As long as you are listening to my concerns about bugs I'm happy, I just want this to be the best damn rom yet! :)

Any idea what is causing the mobile data issue? because there is still the checkbox that works under, "settings > mobile networks > data enabled" its just the widget seems to be making the UI crash.

I can also confirm this, it sees to be linking to gallery and crashing. How does one take a log and upload it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xhead:
I mean the actual Icon to even run tthe Camera App isnt even there ? I
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nate_benji:
Try making a phone call, for some odd reason it worked for me before.. But i Had the proper apns, strange that it wont let you add the apns..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ih8mydroid:
Just gives me the proverbial finger. All of the normal tricks to get data to kick in are not working for me. Hopefully somebody may also get a download going and see if they have better luck. Still unable to manually add an APN and none show up from install.

2nd Install is the exact same issue. No data, no APNS and am still unable to get an APN created and saved. I am getting no FC or errors of any sort. Oh well, maybe tomorrow, back to my nandroid.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] energyracing:
Same here, 1228 is broken. Do not flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nate_benji:
Yeah, seems to be. I get no service at all.

Im gonna mess around with it for a bit, see if i can get it going.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Agreed. It's borked. No APNs!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Yep. 12/28 is a nogo for me. Not even a single bar of service.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 02busa:
Same here.... Glad I've got a back up phone... :D

Sent from my Atrix HD Maxx...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nate_benji:
Same here, Had to reflash 12/27.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevey500:
Yes 12/28 is dead radio. No service. *#*#info#*#* says IMEI:unknown

Blank phone number.

Going to try to flash 12/27 zip. Didn't backup my data. *facepalm

Update:

Flashed 12/27 over 12/28, radio is alive. All went well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adammur:
Confirmed, no signal for me whatsoever.

Sent from the future in a tie-fighter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RCizzle65:
Like others have stated, no signal at all, avoid 12/28
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
I don't think they'll ever fix the data issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nklenchik:
It's been less than a week since we started getting 10.1 nightlies :P Rome wasn't built in a day
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
and the popular call echo issue

---------- Post added at 11:59 AM ---------- Previous post was at 11:57 AM ----------

What about the call echo? Is this fixed in the 1227 build?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Agreed. I think people are not doing full wipes which includes formatting system.

---------- Post added at 07:09 AM ---------- Previous post was at 07:06 AM ----------

Have you changed your min or max? Sounds like you might have your screen off setting too low. Try using 384 or 486.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
I think we have already been through this. Data is DEFINITELY NOT FIXED! If its working FULLY for you then consider yourself a lucky person. Go buy a lottery ticket tonight or something but the data issue is FOR SURE, WITHOUT A DOUBT, DEFINITELY STILL THERE!!! And if your data is working seamlessly on the 12/28 build then it's AMAZING seeing as how there aren't any APNs showing up! On another note, is anybody on here having a harder time getting data on the 12/27 build than the 12/26? I can't for the life of me get ANY data on the 12/27 build. I'm also using KT's 12/21 test kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adammur:
Well... Its the test kernel that's the problem. It's mentioned in his thread, I was also running it and it broke data for me every time.

Once I started using cm kernel, no data problems since 12/23, save for a slow switching to different connections. Data on 12/27 is normal.

Sent from the future in a tie-fighter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
I can't get data on anything BUT the test kernel on the 12/27 build. I tried using the stock CM kernel & doing the toggle data & airplane mode method & I couldn't get any kinda data. How are you managing to get data?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xaznxplaya:
I didn't try trebuchet in 10.1 but from the previous version, Nova Prime is way faster, has way more features Trebuchet doesn't have. Not sure if I can do this In Trebuchet

PoWeReD By that SeXy s3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adammur:
I did a factory reset and restored only from nandroid data backup before flashing, other than that, if I don't get data right away, I turn data on and off a few time and reboot. Last resort I just place a call to myself and connection will appear.

That was on the older builds though. On 12/27 I haven't had to do that, quite reliable.

Sent from the future in a tie-fighter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
When you're rebooting, do you leave data enabled or do you turn data off & toggle it to on after your phone boots up? Sorry for all the questions...I'm just trying to get the specifics. I'm gonna try to do some testing. I just wanna know EXACTLY your method for getting data upon boot. Maybe it will save me some time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adammur:
Disable reboot, wait a minute or so, turn data on, maybe toggle a few times too.

But in haven't had to do that in a while so I'd suggest trying the other things I mentioned first.

Sent from the future in a tie-fighter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Ok. I ended up just leaving data on & rebooting the phone. It didn't grab data on the first time so I just left data on & toggled airplane mode on then back off & when I turned airplane mode back off, it grabbed a data connection the first time. I'm getting what looks to be so far like horrible battery life & the phone runs really hot. I'll give it a while to settle.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpstiehl:
APNs are MIA

Flashed 12/28 and did the customary reboot with data unchecked only to find out that I am missing all the APNs I had prior to flashing last night's nightly. Anyone else?

In addition, I tried to enter in an APN manually but it won't save. It just disappears. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevemiana:
how do u get that theme, that is awesome
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Yeah. Its happened to pretty much everyone so far I think. It definitely happened to me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] philalford:
If you use the OTA CM updater it's a good idea hold on to your last "good" download while you test the latest build. I had the same missing APN issue as everyone else with 12/28, so I went back in and OTA flashed 12/27 again... quicker and easier than having to backup/restore... Which I don't do after EVERY nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rjyanj:
Just to confirm, I also experienced the same issue w/ 12/28. I freaked out and thought I completely lost IMEI. Flashed back to 12/26 (last build that kicked ass for me) and data was fully restored.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MoeisHere:
anyone know where we can contact the cm team to notify them about 12/28?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] timbit123:
For the build of 28, baseband is not detected, in about phone the version is mark as Unknown.

Don't flash this build today or you will not have any call or data.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Lol. I did the same exact thing! I thought I was absolutely screwed for a second. Wasn't it a good feeling when you flashed back to 12/27 & everything came up working!?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] philalford:
It definitely was, especially since I had just started my work day and knew it would be at least 10 hours before I could get it working again! :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Twitter?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Same issue here with 12/28. There was some fix in the change log regarding APN's too if I recall correctly.

---------- Post added at 11:50 AM ---------- Previous post was at 11:48 AM ----------

Until 12/28, I was getting data just fine running stock 10/1. I didn't flash other kernels.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HaruSoul:
I think they will see the last 2 pages in here about people freaking out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Wow, that was scary! I also thought my IMEI was GONE!

Flashed back to 12/26. 12/27 has a nasty bluetooth audio problem -static/pitch problems/stuttering - for pandora.

I had to toggle several times to get data this time, which I don't normally have to do. Just circumstance I guess.

Now I have several APNs I don't think I need.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
Do you think they even look at these threads?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xetrev:
12/27 has bluetooth issues all over the place..

Outgoing calls via my car worked fine, incoming calls on bluetooth had major issues.

I would click accept call in the car but the phone would not accept, phone then rebooted on its own. It did that 3-4 times when calls came in while bluetooth paired to my car.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Nope.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] uplift777:
No data for me either ...reflashed 12/27
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dschamis:
Same alien sound on BT audio - doesn't happen always but often - calls work fine and I've used it quite a bit. Glad I'm not the only one.

Skipped 12/28 - hopefully 12/29 will address some of these.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
I tried to get in contact with them on Google+ through the Cyanogenmod page and community and never received any responses from anyone on the CM team, just a bunch of dudes +1ing the post and commenting they had the same issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bentonhall:
Did anyone that flashed 12/28 try flashing a modem to see if it would help?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] muqali:
I've flashed a modem and will be putting 12/28 on there in just a minute. Let you know how it goes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gmac1990:
Idk about all the data issues but my status says I'm at 2147483647dbm. Lol. And my actual steedtest speeds are under 1mb down but I do have connectivity. Also the phone reflects I'm on 4g with full bars. So idk lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zerojay:
I think a lot of people here have no idea what "nightlies" mean and shouldn't be using them. Of course they aren't going to be watching this thread, they are far more concerned about long-term development over you losing data for a day so bothering them about it isn't going to help anything. If you want to help, just stop using nightlies unless you are a developer or you understand what using a nightly build entails.

Sometimes things are going to be broken and if you can't deal with that constructively, you're going to have a bad time. If you are using nightlies because you want the absolute latest version of Android, you're going to have a bad time.

Now stop whining and stop harassing the developers and let them do their work and in the meantime, go back to using the last stable build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
I tweeted @CyanogenMod. Whoever has that account seems to answer the other tweets that they get. If he replies to me I'll let y'all know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
Didn't work for me. No APNs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Elaldeano:
Same problem as everyone in terms of data. My gps seemed not to work but then I Downloaded gps status and back to normal. I hope the devs solve this issue by tonight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
false. Did a nandroid, full wipe /system, /sdcard ... i mean... FULL wipe, even went as far as doing a full wipe in cwm then flashed twrp and did one there, phone is as wiped as wiped can be. Flashed 12/28 clean, flashed latest gapps that I KNOW works without issue and got data on first boot, lost it through reboots. If nothing else, this is a consistent issue through all of the official nightlies. This is not to say that I don't enjoy the development and am not thrilled to have CM10.1 on this device, it's just simply not working for everyone consistently. I have since reflashed my aokp setup and have solid data.... kthxbye
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] philalford:
If you actually got data at all on 12/28, you're the first to report it in this thread...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Drybones5:
Yes, this is a Nightly, but everyone here is reporting and confirming an issue. The developers should monitor the forums for feedback and issues with each build or else how will they know about wide spread major bugs and issues?

What's the point of doing nightlies if you're not gonna monitor the feedback?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
i had to setup on wifi but was pretty sure it popped up for a second and then I immediately rebooted, i didn't even give it a chance to fully initiate in anticipation that the reboot would kill it.... i'll try again in a bit and see though

There's a way to submit feedback properly to the CM team and twitter, google + and the like are not it... neither is this thread.

http://code.google.com/p/cyanogenmod/issues/list
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
Back on 12/26 now. No bluetooth issues and can get data functioning.

Bluetooth borked in 27th.

Couldn't fix data on 28th most likely missing APN's.

Had reliable data on 24th - 27th but after flashing 28th going back data became flaky again but at least fixable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
There is no official channel to report issues with alpha releases of CM. This includes the 10.1 nightlies, obviously.

Until a 10.1 beta is released for d2att, this thread is as legitimate a place to discuss and confirm issues as any.

The issue tracker you linked does not accommodate 10.1 yet, making it actually the one definitive incorrect place to report issues with the 10.1 nightlies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acloaf:
1227 was unreliable data for me. Restored 1226 and couldn't get data back till I flashed KT 1220 kernel and then rebooted. 1228 was a no go like everyone else reported. I'm doing (and have been doing) a full wipe on every update until 10.1 gets a little stability built into it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tylerlaczko:
No Data

Data not working 2012-12-28
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iriestx:
There's no APNs in the 12/28. They don't magically appear when you wipe CWM in addition to a full wipe. You are mistaken.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ih8mydroid:
This is true. The changes to the framework res apk seems to be causing some issues on 12/28. Are we able to flash the tmo cm10.1?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] noobnl:
I am aware of the ril issues, we recently consolidated blobs, I am making a new build that possibly fix it http://jenkins.cyanogenmod.com/job/android/16415/

edit: build failure, new build
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zerojay:
Clearly you are missing the entire point of the nightlies. They aren't about collecting feedback, they aren't even meant to really be USED, they are just made to make sure that nothing build-wise has broken. Does the code compile and come out the other end? If not, you already know something's wrong. It's a simple smoke test. When they decide to put out release candidates, THAT is when they'll ask for and closely monitor feedback. At this point, you should assume that they already are quite aware of what issues are there in the nightlies and they are already working on it. They may half finish something and commit it and then finish it off the next day. That's how development works... but instead of that, you get people pissing about it here because they have zero understanding of how any of it works.

So yeah, reporting issues here and comparing with other nightly users is fine but clearly we're seeing other people who are stomping mad about there being no data in the last build like as if they expect a fully perfect ROM on a nightly basis with zero problems.

Let them at least get to beta, geez.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
I downloading and flashing this now, how's it running for anyone else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MethodX:
No dice. No signal still. Did a full wipe including system
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] noobnl:
PM me your skype name
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
I'm down to help you with this if you need it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MethodX:
Thanks buddy. I don't have Skype
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] noobnl:
okay
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Talk?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] noobnl:
k pm me it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klef25:
No telephony, usb audio

I just wanted to clarify with everyone about 12/28. I got perfect data through WiFi, but no telephony functions. I flashed back to 12/27 and things were good.

On another note. I cannot get audio out through usb. I use a car dock and the audio out through it with the Samsung stock worked fine, but Cyanogenmod doesn't. 12/22 was the first build that I tried on the GS III. I was previously using a Captivate with Cyanogenmod and it worked fine in it's dock, but I think I was running Cyanogenmod 9 at that time. Can anyone tell me if they have seen audio out through usb work in any 10 or 10.1 builds?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GADGTGUY:
Same here...

I updated, no radio, went back to last nightly, works fine.

D.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] uplift777:
There's a new 28 nightly experimental out ...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MethodX:
Maybe you should read the previous page.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
If you need some help with signal testing let me know..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
So I guess we should wait for the next nightly and hope they fix data/signal.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
You definitely could have connected through Wifi, I did that, but without APNs, and there are NONE in the 12/28 build, you did NOT connect to data. Nobody did, and nobody will untill the APNs are added back in by the CM team.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
People I have another bug on 1228 No Audio? even on Speaker or Headset no audio at all and of course signal and data dead :( no baseband or IMEI Shown on settings.. and it's a fail :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shamidude:
No signal with 12/28 nightly

I am also seeing no signal with 12/28 nightly, so I had to restore an earlier backup...

I have to say that the nightly builds have been surprisingly reliable, and because of that we tend to forget that they are just nightlies used to demonstrate that the code base can be compiled (without any additional promises of quality assurances that usually come with release candidates).

The cyanogen update process is so smooth, and if anything goes wrong, we can easily rollback to earlier backups. Nothing really to lose, except the short time it takes to click the update/backup buttons.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] noobnl:
http://jenkins.cyanogenmod.com/job/android/16416/

new build that fixes mms on my d2spr but it could possibly fix the problem you are having
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] noobnl:
forgot to commit the unconsolidation patch http://jenkins.cyanogenmod.com/job/android/16417/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GADGTGUY:
+1

They are what they are..... till they are "stable builds" you have to take it like it is.

I am just happy that the CM crew are awesome and roll-backs are easy.

I am using CM on my Galaxy Nexus and SIII

Best ROM ever!

D.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xaznxplaya:
Nova prime, minimilistic or whatever its called , zooper , simple calender and widget and use your imagination

PoWeReD By that SeXy s3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Maroon Mushroom:
lol people are going to wonder why the build bot is doing it's 4th AT&T build in a row.

Which I had a server like that at my disposal.

Thanks for helping us out noobnl
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
+1 on the thanks noobnl! Really do appreciate it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] noobnl:
I need somebody with experience with adb on gtalk or skype, if this doesn't work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bengali548:
im on jellybam 3.1 right now

everytime i try to update to cm10.1 both nightly and experimental it says "unknown baseband" and wont connect to my carrier? whats the deal
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MethodX:
No go buddy. No experience with adb much. Also not skype etc. Hope someone can help out here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
Alright folks, I see three experimental fixes. Should I assume that the latest one is the best?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jeremysv:
I'm fairly experienced with android dev. PM me if you want stuff pulled from adb.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MethodX:
Did you read the post above you?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
Sorry, i don't have any experience with adb.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shamidude:
I noticed this issue recently: pressing menu, home and back button would result in "long press" events. This doesn't happen all the time, but once it happens, the only way for me to fix it was to reboot the phone.

The issue with the "home" button is particularly annoying, because I can't use it to go back to the home screen (it always opens the "recent tasks" view).

I am not complaining, because I know nightlies are experimental. I am just wondering if I am alone, and if others have found workarounds for the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Drybones5:
No, you're not alone in this issue. I think I fixed it by rebooting, but it hasn't happened since and I re-enabled the long press shortcuts.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Turns out that there are multiple 12/28 builds and now a 12/29 build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Turns out the chicken crossed the road to post before reading...

---------- Post added at 09:43 PM ---------- Previous post was at 09:38 PM ----------

noobnl,

Just flashed your rilfixtest3 build, and... nogo wrt to data (no APNs listed). Every nightly before 12/28 data has worked for ME, though (but not many others). If you need another competent adb monkey, ping me for gtalk (I'll be flashing my working 12/27 nandroid back in an hour or so). Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nklenchik:
Come on guys we got this! Appreciate all the hard work put into this phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] noobnl:
http://jenkins.cyanogenmod.com/job/android/16418/