yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Man dude, you have a serious attitude problem. And you are just plain wrong. It is stable, and they are working on a single point now... it's called the future. Did you notice that the new stuff is 10.1? Working on an old build just makes no sense... even if you think it does. And bluetooth works in 10.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Moh_Jay:
Go back to touchwiz if it isnt stable for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LoneFlac:
I don't have a attitude problem you guys are being Co plateau unfair. I said one thing. I love this rom and it's stable to an extent but the little things don't work or some anyways and it gets annoying sometimes that's all. Sorry to come off as a duck. I very much appreciate all work going into all roms.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackangel104:
Dang it son! ... I'll be sure not to voice my opinions anymore
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
It's all right. Stay humble :)

Also ...quack quack? lol

Sent from my Galaxy S3 [AT&T][CM10]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LoneFlac:
Thanks and lol sorry, I just started using Swype.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
I've been using CM10 since mid-November and it is hands down one of the 3 most stable ROMs available for this phone. Being anything TW-based (because Samsung licensed career programmers made it), Tasks AOKP, and CM10.

Bugs are ALWAYS going to be present. Its only been on the nightly distribution for a about 2 months with daily updates. These things take time.

Also its important to remember, CM10 is not designed to be for one specific device. Its meant to be able to be used on any device, therefore, the developers won't always have a specific device on-hand to use for testing. And another point, not every specific device of one model (say, 2 d2att's) are the same. So yes there will be different experiences and varying success rates for every individual person.

I'd say after everything is said and done, what these developers have achieved for our phone is quite amazing and I for one am certainly GRATEFUL for their countless hours of time put into this project. As much as I would love to learn, I simply don't have the time being in the military and getting ready to start my transition to college for biological sciences to learn how to PROPERLY develop ROMs and such, but I have picked up some tricks in the past few years.

Most of the issues in CM are from Google anyway that the developers fix on their own :thumbup:

Absolutely not trying to bash anyone in any way whatsoever, just wanted to put this into a different perspective for some people. Regardless, I for one respect everyones opinion regardless what it is :o
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
Please stop the bickering.

Please remember this is a development thread. That is all, nothing more. P;ease stick to development and bring anything else to a chat forum or PM.

Thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Really? That's tough to do when the opinion is contrary to one's own, don't you think. I am not talking about the thread per say, but like for instance, when those opinions get in your face and want to destroy life itself (like some fundamentally religious types), Why should one respect the Taliban's opinions for instance? I'm just sayin', sometimes it is best to draw a line.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Absolutely, and I drew the line at this forum, strictly this subject. As far as the Taliban is concerned.. I've deployed as an infantry marine to Afghanistan multiple times, so my opinions should be pretty blatantly obvious on those subjects.... I am now dropping this subject as we are SO off-topic haha :banghead:

Onto development, anyone know how to get Kies working on this? I know its for TW but Im pretty freakin sure i had it on CM10 previously, but now I get the your device in incompatible crap
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t3chn0s1s:
You all need to remind yourselves this is NOT a chat room. This is a development thread. Please respect your fellow XDA users and follow the rules. Your personal opinions have no place here.

sent from my AOKP powered Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
Is this rom compatible with TWRP?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trecko1234:
All roms are, it flashes the same way as CWM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chris_barsoum:
Does anyone know how to capacitive buttons stay on until the screen turns off?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackangel104:
How is the latest nightly?? I'm currently on the serenity rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t3chn0s1s:
Take 5 minutes to make a Nandroid and try it yourself.

sent from my AOKP powered Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
Its been very stable for me actually...gr8 battery life too (I'm on stock cm10..nothing changed..also in an LTE region)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RoachForLife:
Apologize if I missed this somewhere in this thread but I dont see an option to turn off camera sounds anywhere. Is this is a menu or do I need to modify a system file to get this to work? Guess same for video cam and anytime there is focusing

On a relating note, if I recall when I had TW I could hold the shutter button down and it would keep taking photos forever. I dont see this either. Thanks guys
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
I just long-press the powerbutton to temporarily mute the phone when I want to take quiet upskirt pics. j/k

Have to switch to burst mode if you want that, which was added only about 2 months ago.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
I'm on the 12/15 nightly and I can't connect my bluetooth headset, I'm coming off of a full wipe. I do a search it find my bluetooth, it finds it the when I go to pair it says " Couldn't pair with Bose BT2 01.50.00 because of an incorrect pin or passkey" It never gave me an option for a passkey. Any suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
I Got it to finally work, I had to reset the bluetooth by pressing power and volume for 5 seconds. Then my phone paired.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nccu_eagles:
did you quote yourself? LOL why not just edit your previous post :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Does anyone know why they are still using an old kernel, (.48)?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trecko1234:
Haven't bothered to update it is my guess. You shouldn't be using the stock kernel anyway, custom kernels are faster and provide more features.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
What custom kernel are you using? can you give me a link please. I'm on stock and would like to try custom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
I know they are faster and better but it would make more sense if cm10 came with an updated kernel. My phone randomly reboots itself with custom kernels and I'm forced to use the stock kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SielickiN:
removed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Yeah, that's what I think too. They should update the stock kernel of cm10 to .56 like the rest of developers have.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LoneFlac:
When did somebody say that disable HW overlays thing was going to be fixed? It's been three build since and I forgot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SielickiN:
Where can I download that kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
What kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
the importance of quoting....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Most of the custom kernels have been updated to .56, except for CM10 which is still on .48. Ktoonsez has updated his to .56 and it's super smooth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trecko1234:
http://xdaforums.com/showthread.php?t=1756776

I use ktoonz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Does anyone know how hard it would be for them to update the stock kernel to .56? I'm guessing it wouldn't be hard since Samsung released the source files? I'm not a dev so I have no idea.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GilaMonster1:
I upgraded my nightly and Google Wallet disappeared. Why is this? I didn't clear the cache or anything either
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
It probably overwrote a key file for the GoogleWallet fix.. I haven't looked into the GoogleWallet fix personally but that is the only reason it would disappear after an update. Just re-do the GoogleWallet fix and you will be good to go :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Before you update nightlies, you are supposed to reset Google Wallet. After you update nightlies, you have to re flash Google Wallet & set it up again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
It's not hard
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vcharette:
You don't want to have your thread polluted yet you come here trolling/bragging without contributing in any constructive way. Logic fail.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GilaMonster1:
I knew if needed to be reset before flashing a new ROM, bug not upgrading a nightlh
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Is 10.1 available for download yet?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gunz.jones:
He answered the question to the point and showed proof of the update he has on his own kernel. Capt stated he is not a dev and asked about difficulty, not process.

@Capt : Ktoonz also has his kernel running .56 on AOSP. I'm sure the devs will update if they find something valuable in cm once they have 10.1 built to work better on s3.

Sent from my horny pink pony
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
I believe only euroskank and unofficial are available right now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Thanks man, I went on the get.cm and it does not say what's what. I wanted to give cm10.1 a shot I'm on AOKP 4.2 and my battery life cut in half from 4.1.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
no problem..I would hold off on flashing though..data is acting like a biaatch..kinda hit or miss for some ppl..I using euroskanks build and managed to get data working for now..camera not to lucky yet:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Anybody else getting "Can't connect to camera" errors? It usually happens after using Google Goggles. I don't think it makes much of a difference for the camera but I am using Ktoonsez's latest kernel on the latest nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mynameisnoah:
get.cm is showing 10.1 for the latest nightly http://get.cm/?device=d2att&type=

Haven't tried it yet, but will later today. Unofficial 10.1 is running pretty great for me, with the exception of a few easily overcome data hiccups.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] astralmind:
Yup I can confirm that the update brings in 10.1 for last night's. I didn't even notice until I realised my gapps were gone and there were some odd menu changes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benjihana:
The 12/17 10.1 build is completely wankered for me. No Google accounts available. It's showing Verizon. No data, everything is crashing, even on clean install with a full wipe. Wrong build/premature? I know it's a nightly, but it's unusable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] astralmind:
As expected it is indeed bugged. I'd recommend not to update to it.

Camera works but has focus issues

No development menu?!

Issues with gdrive sync

Cell data randomly drops

A few fc on basic apps

GPS not working. I get fast and numerous locks but no location is maps and any other app.

That's what I've experienced in the past 20 minutes. ;)

Hopefully things will get better fast
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] araemo:
It was hidden in 4.2: Tap 'build number' in the about screen ~10 times to be taken to the developer options.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LanceM:
You have to get into "about phone" and click some like the build date or something numerous times to get it to show.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lothos:
That actually is not necessary if you ensure that Google wallet is reinstalled BEFORE you reboot after installing a new nightly. Or you can use a script similar to the one included with gapps that will automatically preserve your wallet apk. This is what I use, but it has to be updated for every version of Google wallet. It could probably be modified to use a regex or glob to match any future versions of the apk, or you could just install the apk as wallet.apk every time.

#!/sbin/sh
#
# /system/addon.d/70-wallet.sh
#
. /tmp/backuptool.functions

list_files() {
cat <<EOF
app/com.google.android.apps.walletnfcrel.modaco.1.5-r75-v6.apk
app/com.google.android.apps.walletnfcrel.modaco.1.5-R79-v5.apk
app/com.google.android.apps.walletnfcrel.modaco.1.5-R81-v4.apk
EOF
}

case "$1" in
backup)
list_files | while read FILE DUMMY; do
backup_file $S/$FILE
done
;;
restore)
list_files | while read FILE REPLACEMENT; do
R=""
[ -n "$REPLACEMENT" ] && R="$S/$REPLACEMENT"
[ -f "$C/$S/$FILE" ] && restore_file $S/$FILE $R
done
;;
pre-backup)
# Stub
;;
post-backup)
# Stub
;;
pre-restore)
# Stub
;;
post-restore)
# Stub
;;
esac
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
Group SMS is busted for me. It worked about half a day, then my buddy got a Group message that I was attached on and I never saw it. They went back and forth a while and I never got a single message from it. He then sent me one from just his phone and it worked fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Maroon Mushroom:
Official CM 10.1!!!

Pissing myself with excitement.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] likonvampire:
Reporting post 121722012 CM 10.1 nightly , camera works , data works , GPS works etc....

All is good .. ( not tested photosphere as yet )
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Did you guys do a full wipe? A lot of that stuff sounds like you didn't fully wipe /system, /data, /cache, and /dalvik-cache prior to updating. Most of these issues sound like they are being caused by having 4.1.2 gapps on a 4.2.1 ROM :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HaruSoul:
Updated to 10.1 by accident, can't even login to my phone. Lockscreen got changed from 4x4 to 3x3 :crying:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sublimejosh2000:
So you are the first to report working Camera and no other issues. Is this true?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
yea man try flashing back to 10.0 without wiping data, but you might be SOL and have to wipe data to clear the lockscreen stuff
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] IUH1991:
Which recovery are you guys using to flash the latest nightly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gordietm:
Use TWRP 2.3.2.3

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mkatforum:
So you wiped/installed ROM and installed 4.2 Gapps?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benjihana:
My gapps (for 4.2.x) install failed first time around. I clean installed (full clear as above) and it booted fine.

Camera seems to be working. MMS is failing to send (per my first test). Most other things seem to be working. Haven't tested fully.

Since I realized that the gapps issue caused my first issue go around, I went back to my 4.1.2 nandroid, then cleared cache and dalvik-cache, and flashed over that with gapps. 10.1 worked about the same, and I was able to retain my custom bootani, settings, etc, without the hassle of a reboot.

As always, YMMV.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] likonvampire:
Correct I wiped cache , system , internal sdcard ( just to be safe ) ,flashed the latest nightly and gapps .

All went smooth , booted up , selected the correct APN and all is up and running .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] astralmind:
The camera does work but the focus is slower than usual ie, no "continuous shooting" at least on mine.

Data does work but coming in and out of wifi or dead zones, it doesn't always switch back on on its own

GPS locks extremely fast but somehow I cannot get an actual locked position (ie doesn't report any level of precision in meters)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benjihana:
Is your group MMS function working? Regular MMS with pics, etc?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Maroon Mushroom:
Everything seems to work on mine. MMS works, camera works, LTE works, custom kernel flashed just fine.

Very very happy. Daily driver so far
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] likonvampire:
How are you testing the GPS lock ?

I opened Maps application and it locked on fine on my current location and even GPS works good while getting weather updates.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Did anybody else have their internal SD contents moved around to a folder '0'? I can't even restore with CWM because the paths changed. So now I'm copying the entire clockworkmod directory to the external SD where I can get to it from CWM so I can restore. There goes the day.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lothos:
That is normal, from what I understand. Probably has something to do with support for multiple users on tablets.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sublimejosh2000:
Titanuim Preferences --> Backup Location --> Search Whole Device
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cypho:
The move to 0 folder is an expected change for 4.2.

That is the multiple-users functionality. User#0 is in folder 0, user#1 in folder 1....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Makes sense. I suppose having the backup and restore software support that might also make sense. This is a mess. But moving on, I can recover from this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] astralmind:
tried with maps on its own and then opened up GPS status where I saw it locked on 15 sats really quickly but did not report a "precision" ie, not the usual 3m or similar, just blank, no other location data. very weird. It was working ok prior to 10.1 flash but could be unrelated I guess.

Data seems to behave ok now could have been bad luck at first.

Camera is working ok too after reboot.

However, gdrive sync fails, google music FC and so does SU

If I could get passed the GPS glitch I'd say it's pretty good in the end :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kennyaa:
After flashing the new 10.1 with the latest gapps 4.2, I'm always getting "Runtime Exception" error. It says: "Google Drive sync error occured. Not all data may have sync'd successfully."

Anyone else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tony_YYZ:
Maybe try to Fix Permissions for your FC issues?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tj_ona:
Just installed after full wipe, coming from a TW rom. Everything seems to be working. GPS locked in less and 5 seconds, headphone jack working, camera working, and everything else ive tested. Loving the 4.2 goodness. Flashed Gapps from 12/12 and they seem the be working. Maps didnt install right away, but i just installed from playstore.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Maroon Mushroom:
Hmm... I'm not seeing any issues with the google services, although I did have some troubles with SU a bit ago.

GPS locks and data seem fine on mine so far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tj_ona:
One thing i did notice, and i've never seen this before, when i try to Fix Permissions on TWRP it just reboots. I'm running the newest version.

---------- Post added at 11:00 AM ---------- Previous post was at 10:50 AM ----------

I lost all my stystem data and cannot reboot. No roms on my phone nothing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gordietm:
Now that CM has 10.1, I wonder if we keep using this thread or they will start a new 10.1 thread.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spthomas:
Flashed 10.1 and it changed to my unlock pattern. D'Oh!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tony_YYZ:
They'll probably start up a new thread eventually.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ormandj:
They all work for me, as well. Haven't tried GPS/BT yet, though. I did a full wipe, installed, installed gapps, perm fix, etc etc process.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BourqueJ:
Superuser not working after clean install of CM10.1

Hi,

I just clean installed CM10.1 with the appropriate gapps but now, my superuser app keeps crashing every time it needs to grant access. Anyone have a suggestion on how to fix this?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gordietm:
Same thing happened to me. Go take a look at the unofficial 10.1 thread. I posted the link for supersu to flash.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
I flashed this version of Super User & it fixed my force close issues.

http://db.tt/I5MfLfrv
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] energyracing:
Don't know if this will be of any help, but concerning the data drop,

I flashed 10.1 Official this morning in the same method I would flash a new nightly (Wipe Cache, Dalvik, and Format system, install 10.1 and gapps, reboot) and 10.1 came up and running with no data issues, but superuser kept FCing. So I decided to do a full out wipe (Factory reset and Format Data) and reinstall 10.1 and Gapps. No data.

I'm going to try going back to 10.0, update to 10.1 as before, and try to work out whatever is going on with Superuser. Or just disable it and install SuperSU.

EDIT: While typing this, Data decided to randomly come on while my phone was just sitting idly next to me. Rebooted, said "Restriced access changed' on the notification bar, then H+ showed up and data is still good. So I'm not going to fix what's not broken right now. If it drops out again, I will do the rollback to 10.0 as I mentioned above.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trecko1234:
Have you tried reflashing your modem? That has worked for some people, mess around with different modem versions, one time it worked for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
So did the nightlies officially kick over to 4.2?

Which nightly was the first on the new version?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nelsocracy:
My data always comes back after I go into settings -> data usage, then toggle mobile data off then on again. Every once in a while it turns off again but starts working as soon as I do this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tj_ona:
Sorry, my last post was out of fear. I'm good. Everything moved over to the 0 folder. Not sure why, but i need to mover everything back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cypho:
Today's(12/17) nightly is the first 10.1 nightly.

http://get.cm/?device=d2att

You can see yesterday was still 10
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drewdatrip:
It has to do with the users functionality of 4.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
4.2 Bluetooth ALMOST THERE!

I was so happy to find that with 4.2, my phone audio quickly connected, all the volume was there, no need to do the vol-up/down trick, and no stuttering.

I was belting out tunes for all of 30 seconds when a notification popped up and the audio level dropped to half. After that, I can't raise the volume back up. It's like it's permanently attenuated after the notification sound.

Should we report stuff like this here, or log it somewhere?

Also, is this going to be our best place to talk about 4.2 ongoing, or will there be a new thread?