yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] KeithLM:
I might in a few weeks, I don't want to spend that much time setting up my phone again for every nightly. I'm just trying to find out if other people are seeing this. It's something where it degrades over time.

And I can't really trust Titanium Backup in this case, can I? After all it might restore whatever is causing the problem.
[T-Mobile, Samsung Galaxy SIII] AviatorJud:
Why are the nightlies constantly disappearing from ROM manager?
[T-Mobile, Samsung Galaxy SIII] djxspike:
I've noticed that as well... You could try GooManager Beta: https://play.google.com/store/apps/details?id=com.s0up.goomanager

Update:

Interesting... I just force stopped the app, reopened ROM Manager and it's now showing them just fine!
[T-Mobile, Samsung Galaxy SIII] tmobilewinguser:
Sorry if this has been asked already but has there been any word on when PTP might be fixed

Thanks in advance. :cowboy:
[T-Mobile, Samsung Galaxy SIII] franknozly:
So I was wondering if anyone has tried to flash this on their SGH-T999V, for Mobilicity?

The device code is d2can, product.name is d2vw.

The hardware should be the same, but wasn't sure if something catastrophically bad might happen.

--

EDIT:

Well I gave it a try anyways, removed the assert line in the updater script and flashed it on a multiboot setup...

Not surprisingly, The Model number changed to SGH-T999 and ro.build.product, ro.product.device, and ro.product.name changed to d2tmo.

Other than that, it took about 3 minutes for the system to find a signal, then everything was golden. I could make calls, my IMEI didn't disappear or anything, wifi works.
[T-Mobile, Samsung Galaxy SIII] AviatorJud:
Haptic is janky on this last one (8/3) Prob gonna turn it off til it gets fixed. Really annoying when typing.

However it does appear so far that the notification light is working much better. Strange cuz I didn't see anything in the changelog about it.
[T-Mobile, Samsung Galaxy SIII] AviatorJud:
Camera still crashes all the time. Mostly when trying to focus on certain areas of the screen.
[T-Mobile, Samsung Galaxy SIII] AviatorJud:
For the first time ever the phone inexplicably turned itself off in the middle of the night last night. It didn't restart, just turned off. It was plugged in like always but it appears that once it turned off it did not charge anymore, as it was only at 46% when I turned it back on. Very strange.
[T-Mobile, Samsung Galaxy SIII] AviatorJud:
Figured out why. As you can see, even as the phone was charging last night it discharged all the way til the phone turned off. I had left the clock in night mode with the screen dim which I do every night. For some reason on this current nightly, this happened. Will try again tonight and see.
[T-Mobile, Samsung Galaxy SIII] InversedTech:
Does anyone know what formats CM as far as microSD cards go? I just ordered mine online and I was curious because, if I remember correctly, Fat32 isn't supported.
[T-Mobile, Samsung Galaxy SIII] george241312:
Latest nightly on me is freezing but its only like the gpu is freezing I'm in a call and it freezes I touch speaker it does nothing until I turn the screen off and on it shows that I did press speaker but it froze again. while browsing the web it would freeze and I would swipe down it didn't do anything I close browser and open it again and then its wipes down by itself but freezes again... it's like the gpu is freezing
[T-Mobile, Samsung Galaxy SIII] AviatorJud:
Yeah something in the past few days has made it worse overall. Haptic feedback is totally messed up. I've also noticed a delay when turning the screen on from standby with either button.

I'd anyone from the CM team even reading this????? I feel like I'm giving all this feedback to no one.
[T-Mobile, Samsung Galaxy SIII] InversedTech:
A few pages back I said that I had lost screen lock sounds, and keyboard sounds too, and I thought it was because I had flashed a kernel.

I flashed the 8-1 nightly (day of release) , wiped cache, and data, and I got those sounds back, but I didn't flash a kernel.

Yesterday when I was on my way to work, I plugged in my headphones, and put my phone on vibrate. I think this is when I lost those sounds again, because when I got home later that night, I put my phone back on loud(?) and when I locked it, it didn't make a sound. I typed something, and no sound.

I checked my system settings to see if I had sounds enabled (which I did) and made sure that the system volume was up all the way (which it was) and even after a reboot, I couldn't get those sounds to come back.

My phone still rings when I get a call, however,and notifications are also heard. I Can also still hear game sounds and even play music through the speakers, but no screen lock or keyboard sounds. I'm not sure if anyone has experienced this random little bug as well, but it was something that happened to me, and I felt it was important to share.
[T-Mobile, Samsung Galaxy SIII] Zephyron:
I think it was exfat that isn't supported if I remember correctly

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] volcomguyaz:
Sorry to hear about all these issues...sounds like we''re ready for an update?
[T-Mobile, Samsung Galaxy SIII] cwalker29:
Reading all of these problems I'm sticking with cm10 :)

Sent from T mobile galaxy s3 (24mbs down) 4g network
[T-Mobile, Samsung Galaxy SIII] AviatorJud:
How could cm 10 have less issues?
[T-Mobile, Samsung Galaxy SIII] jgalan14:
Maybe cause cyanogen himself is really into it ,he ain't touching cm9 at the moment ,he also promise project butter next update and I'm waiting for that , BTW using cm10 as my DD right now
[T-Mobile, Samsung Galaxy SIII] stonew5082:
It doesn't have less it has more. The ui overlay hasn't been finished so it's choppy. The next build will be cause to switch though, and is coming soon
[T-Mobile, Samsung Galaxy SIII] G1_enthusiast:
I disagree I was using it last night on my friend phone and it's very quick, only problem is no a2dp which I need
[T-Mobile, Samsung Galaxy SIII] rayman2k1:
I did a search but couldn't find a report of this issue: (gmail) emails are not marked as read when being read on the phone. So, let's say I get two new emails and I read them on the phone. They appear as read on the phone, but when logging in with a browser, they are still unread. The strange thing is that the new message counter on the gmail app is still showing that they're unread, but they're not longer highlighted. Has anyone seen this? Is this a bug or a setting that I'm missing? I've looked around settings and can't see any setting that would fix this.
[T-Mobile, Samsung Galaxy SIII] Zephyron:
Yeah this happens from time to time, Im not quite sure what causes it but it eventually fixes it self. Time may vary though.
[T-Mobile, Samsung Galaxy SIII] JZ832:
Anyway to turn on battery percentage?
[T-Mobile, Samsung Galaxy SIII] KeithLM:
Yes.

Settings -> System -> Status bar -> Battery status style
[T-Mobile, Samsung Galaxy SIII] JZ832:
Thanks a lot!

---------- Post added at 12:23 AM ---------- Previous post was at 12:15 AM ----------

One more thing what about the vibrate haptic feedback can I change that?
[T-Mobile, Samsung Galaxy SIII] twosixths:
Did you try clearing your app data? Go to Settings -> Application Manager -> All. Find the Gmail app and hit "Clear Data". You'll have to re-open the app afterwards and it'll take a moment to refresh. But that usually fixes that issue for me. Usually only happens when I've flashed and restored apps several times. Hope that helps.
[T-Mobile, Samsung Galaxy SIII] Lw00d:
could some one post the link to the change log?
[T-Mobile, Samsung Galaxy SIII] stonew5082:
http://changelog.bbqdroid.org/#d2tmo/cm9/1342176990
[T-Mobile, Samsung Galaxy SIII] djxspike:
I prefer this one: http://cm9log.appspot.com/?device=d2tmo
[T-Mobile, Samsung Galaxy SIII] lemon seltzer:
CM9 thread's been like a ghost town lately...am I the only one that's still hoping we make it into the stable release tonight?
[T-Mobile, Samsung Galaxy SIII] PennStater:
I am! Also, I have a question. While on a call with the phone to my ear, the volume buttons do not seem to adjust the call volume. I have to take the phone away from my ear and then sometimes the volume buttons work. Or, once I hit the volume button it will bring up the on-screen volume slider and I'm forced to use that to make the actual adjustment rather than the buttons. Has anyone else noticed this, or is it possibly a known issue?

Thanks!
[T-Mobile, Samsung Galaxy SIII] Monk4Life:
Known issue.
[T-Mobile, Samsung Galaxy SIII] PennStater:
Okay, thanks.
[T-Mobile, Samsung Galaxy SIII] InversedTech:
The stable release of CM is coming out tonight?

Maybe not for our phone but I mean CM in general.
[T-Mobile, Samsung Galaxy SIII] dave2metz:
No, you're not alone. I am hoping it goes stable as well. I just dl CM10 last night and it sucks!
[T-Mobile, Samsung Galaxy SIII] Trevnerdio:
Oh wise Cyanogen, sir, how did you and your team work around the tethering issue? On CM I could just go into my wireless settings and turn it on no problem. On a stock, rooted ROM however, it checks for a subscription and blocks my connection. Is there something easy that I can remove with Titanium Backup like I did with my S II?
[T-Mobile, Samsung Galaxy SIII] lemon seltzer:
yes

http://www.cyanogenmod.com/blog/cyanogenmod-9-stable
[T-Mobile, Samsung Galaxy SIII] lferrin:
I think cm9 is the perfect from. With the Google now hack. Fast and great battery
[T-Mobile, Samsung Galaxy SIII] Zephyron:
Holy jumping jalepenos just exactly what I've wanted to hear :D

Lets hope our s3 is on that list to make the stable release!
[T-Mobile, Samsung Galaxy SIII] KeithLM:
They can call it stable if they want, but we haven't seen any commits recently addressing known issues, so it's likely not going to be a real stable release for the S3.

Frankly it looks like the only changes recently have been things that probably affect a number of phones and are not S3 specific. I wonder if anyone is really working on CM9 for S3s from any US vendors.
[T-Mobile, Samsung Galaxy SIII] anesthetic:
cm9 for tmo s3 is far away from stable, camera needs to be fixed first...and lots of fc...

don't need to mention cm10...

but good thing is clean stock is dam good, what is cm :p
[T-Mobile, Samsung Galaxy SIII] Monk4Life:
You shut your whore mouth! ...................JK :)
[T-Mobile, Samsung Galaxy SIII] Zephyron:
Havent gotten a FC aside from changing camera quality
[T-Mobile, Samsung Galaxy SIII] InversedTech:
Does this mean we're getting the official update?

https://github.com/CyanogenMod/android_vendor_cm/commit/65a97fe9d1c09cb184f16c5eeaf40896c70cd21c
[T-Mobile, Samsung Galaxy SIII] dave2metz:
Me either.. In fact, I really haven't found any reason to not use this as a daily driver.
[T-Mobile, Samsung Galaxy SIII] Lawful123:
List of changes

Dont see our camera fix so far :crying:

http://changelog.bbqdroid.org/#d2tmo/cm9/next
[T-Mobile, Samsung Galaxy SIII] anesthetic:
SI GAY:laugh:
[T-Mobile, Samsung Galaxy SIII] bhaismachine:
Can anyone please point me to the right google apps link ? I am unable to find it.
[T-Mobile, Samsung Galaxy SIII] Lawful123:
New nightly is out.
[T-Mobile, Samsung Galaxy SIII] InversedTech:
Here you go!

http://goo.im/gapps/gapps-ics-20120429-signed.zip

I was up late last night waiting for it, ha ha.

May not be a stable release, but it's something nonetheless!
[T-Mobile, Samsung Galaxy SIII] dave2metz:
Where is the best place to find nightly change logs? For 8/10?
[T-Mobile, Samsung Galaxy SIII] InversedTech:
I use this site:http://changelog.bbqdroid.org/#d2tmo/cm9/1342090149
[T-Mobile, Samsung Galaxy SIII] dave2metz:
Do we know for sure that the T- Mobile Galaxy S3 is getting a stable CM9 tonight?
[T-Mobile, Samsung Galaxy SIII] AviatorJud:
So there's a major issue with tonight's "stable" release. In the last few hours since it has been installed my battery has taken a dive. When I checked out CPU Spy I learned why. It's never going into the deep sleep CPU state as it should when the screen is off. It just stays on 384Mhz. Clearly there is something keeping it awake and I'm gonna have to go back to the previous build. The battery would die in a matter of hours if left like this.
[T-Mobile, Samsung Galaxy SIII] Lawful123:
Well, it is not a "stable" release yet. Hopefully they are not rushing it. I have noiced a drop in battery life (not as drastic as yours). I'm sure they will fix the bugs and make it better before moving on to CM10.
[T-Mobile, Samsung Galaxy SIII] AviatorJud:
Went back to 8/8 nightly and the issue went away.
[T-Mobile, Samsung Galaxy SIII] cyanogen:
edit!

Totally posting in the wrong thread
[T-Mobile, Samsung Galaxy SIII] Monk4Life:
Darn! I was hoping for something epic in the CM9 thread. You got my hopes up Mr. Kondik.
[T-Mobile, Samsung Galaxy SIII] Gvaz:
Does this work on SCH-R530U?
[T-Mobile, Samsung Galaxy SIII] Spider_Pig27:
Nope! This forum is only for the T-Mobile US Variant Model SGH-T999 don't even attempt to flash it you'll brick your device

Go here

http://xdaforums.com/forumdisplay.php?f=1563
[T-Mobile, Samsung Galaxy SIII] dave2metz:
What happened to getting a stable CM9 release?
[T-Mobile, Samsung Galaxy SIII] KeithLM:
I don't think anyone ever officially said we were. All the posts were about the Galaxy Nexus and then several other devices getting stable releases. Keep an eye on the change logs. Not until something significant for this device shows up there can we count on a stable CM9 for the SGH-T999. Probably we'll get a stable CM10 at some point and CM9 for this phone will be abandoned. But that's just speculation on my part.
[T-Mobile, Samsung Galaxy SIII] dave2metz:
Actually, I just read that we will be getting a Release Candidate (RC) at some point. That's all I know...
[T-Mobile, Samsung Galaxy SIII] InversedTech:
Well we will get one eventually, but there are still quote a few bugs that need fixing. The two big ones that I can think of are the LED notifications, and the camera focusing. For me, my keyboard and screen lock sounds are derpy when I plug in my headphones, I don't know about anyone else.

Speaking of LED notifications, Google Voice used to blink red, but after the 8-10 release, my LED now blinks green.
[T-Mobile, Samsung Galaxy SIII] evan742:
This might be a dumb question, but how do I activate wifi calling? I don't see an option for it anywhere in the settings menu like there is on the stock rom. Is there no option for it because it's just always turned on?
[T-Mobile, Samsung Galaxy SIII] Lawful123:
No option because it does not include it.
[T-Mobile, Samsung Galaxy SIII] PennStater:
Is that because it can't be done, or is it on the to-do list somewhere? Just curious.
[T-Mobile, Samsung Galaxy SIII] mt3g:
never been stated anywhere... in CM7 it was included on a few phones. I'm sure once cm9/10 hits stable point a lot of our cooks that are building off stock ICS firmware (TouchWiz) they will move over to CM9/10 and start cooking things in, might be one of them to hope for.
[T-Mobile, Samsung Galaxy SIII] alias503:
@ mt3g ... nice to see a familiar face from g2x. :).

Not sure how much of this is true, but spoke with a tmo rep a week back and was mentioned that the hole wifi calling app is a little more complex than before. He said there was a bit of an issue with complaints of it cutting out from the router. (Disconnects random and periodicly) . I guess I could gather from this is that it may be a bit more that what we had on the g2x.

I guess it is waiting time. This device is still young. Wifi calling works on Stock....it could come to CM9... I hope
[T-Mobile, Samsung Galaxy SIII] mt3g:
Definitely a lot more complex, it has libs in a lot of places that it needs to work I've read. I'm sure someone will get on it at some point.
[T-Mobile, Samsung Galaxy SIII] darknessxyz:
Need quick help please. After I use the Qcom toolkit root my S3 and try to flash the latest CM9. I get error message when installing update

d2tmo getprop (ro.product.device")

E: error in /sdcard/cm-9-20120813-nightly-d2tmo.zip

(Status 7)

What did I do wrong?

---------- Post added at 01:41 AM ---------- Previous post was at 01:40 AM ----------

Need quick help please. After I use the Qcom toolkit root my S3 and try to flash the latest CM9. I get error message when installing update

d2tmo getprop (ro.product.device")

E: error in /sdcard/cm-9-20120813-nightly-d2tmo.zip

(Status 7)

What did I do wrong?
[T-Mobile, Samsung Galaxy SIII] Lawful123:
What version of CWM are you using?
[T-Mobile, Samsung Galaxy SIII] InversedTech:
Download ROM Manager from the Market (if you haven't already) and flash the latest recovery.
[T-Mobile, Samsung Galaxy SIII] darknessxyz:
Finally get it running. However, it's seems like kinda hot when I'm using it. Also it takes very long to charge up. I wipe all the cache and battery stat already.
[T-Mobile, Samsung Galaxy SIII] djxspike:
Open the dialer, dial *#*#4636#*#*, go to Phone Info, scroll down to "Set Preferred network type" and make sure it's set to "GSM Auto (PRL)" and see if that doesn't help...
[T-Mobile, Samsung Galaxy SIII] AviatorJud:
Anybody's ringtones get messed up on this last build?
[T-Mobile, Samsung Galaxy SIII] mt3g:
On CM10 it seems latest build does something to internal so if any of your ringtones were on the internal they cannot be used without you moving them manually.

I know some of the repos they use are for both...
[T-Mobile, Samsung Galaxy SIII] evan742:
When I flash back to earlier builds, I still can't use the ringtones/notifications on the internal SD. tried restoring backups, and still couldn't.

Moving the notifications and ringtones manually into root\system\media\audio\notifications or root\system\media\audio\ringtones isn't working for me either. How can I get my ringtones back?

EDIT:

Got ringtones and notifications working by moving them manually to system\media\audio\[notification or ringtone] Had to move them and then reboot the phone. Still, it's weird that after installing the 8/15 update it's broken my phone's ability to read ringtones from the internal SD even when flashing earlier builds and backups
[T-Mobile, Samsung Galaxy SIII] mt3g:
Did you reboot after moving files? Other then that, I honestly have no clue... there might be a corrupt file with in there or something.
[T-Mobile, Samsung Galaxy SIII] AviatorJud:
You know I hate to sound ungrateful but it's very confusing to me how as these nightlies keep progressing, more issues seem to continue to pop up and none of the issues that have existed from the beginning are being addressed. If you look at the changelog, its a bunch of random language additions and things that don't make any real difference in the daily performance of the phone. Cyanogen started this thread and then hasn't seemed to pay any attention to it since. I understand that this work is done free for all of us, and the team seems very organized and motivated but I think if you're gonna put a lot of time into something then you should do it right.
[T-Mobile, Samsung Galaxy SIII] Zephyron:
Seeing the changelog does seem a bit depressing.
[T-Mobile, Samsung Galaxy SIII] Lawful123:
There by the grace of the CyanogenMod team do I flash my phone.

Lets face it eventualy CM10 is what we want on our phones and it looks like CM10 is the teams main focus. Since they do it for free i am not complaining too much however it would be nice to have a stable CM9.
[T-Mobile, Samsung Galaxy SIII] sn0warmy:
While I do agree that it would be great to have a stable CM9 build, I think majority of us can agree that we'd rather have the CM team working diligently (as they are) on a CM10 build instead. Otherwise it will just prolong the release of a stable CM10 RC in the long run.

I don't know why you guys are still concerned about having CM9 anyway when the latest 8/14 CM10 build has very few bugs as is and is more than capable of being a daily driver.
[T-Mobile, Samsung Galaxy SIII] osho741:
Otherwise if your not happy with cm10. You can always hold out for cm-eleventeen!

On a more serious note a new kernel was pushed a few hours ago

Linux 3.0.41

Conflicts:

drivers/homelife/girlfriend.left.you/youpaynoattn2me.c

arch/arm/mm/tlb-v7.S

drivers/net/tun.c

drivers/usb/core/hub.c

kernel/irq/manage.c

mm/memory-failure.c

mm/page_alloc.c

Flux Capacitor (Fixed enable time travel at speeds greater than 88 MPH)

OK so I made a few mods to the kernel. And no I won't upload or share it! :p
[T-Mobile, Samsung Galaxy SIII] Monk4Life:
I think you meant flux capacitor. But still funny.
[T-Mobile, Samsung Galaxy SIII] osho741:
Indeed correction noted!
[T-Mobile, Samsung Galaxy SIII] AviatorJud:
Well you convinced me to jump ship to 10. And so far so good. Better than the current version of 9 so far.
[T-Mobile, Samsung Galaxy SIII] george241312:
This is now a cm10 thread ......
[T-Mobile, Samsung Galaxy SIII] dave2metz:
No its not! CM9 4 LIFE!
[T-Mobile, Samsung Galaxy SIII] KennyG123:
How would you both like to share an infraction?

Sick of this childish crap!

Zero tolerance for flaming and trolls will be added to this S3 forum as well!

RESPECT IS A FORUM RULE

Thanks

Thead cleaned

NFNM
[T-Mobile, Samsung Galaxy SIII] darknessxyz:
Just flashed the latest rom. The camera can't change to SD card
[T-Mobile, Samsung Galaxy SIII] KeithLM:
Is there some other place to get nightlies other than get.cm? This mixing of nightlies for CM9 and CM10 is going to cause nothing but trouble.
[T-Mobile, Samsung Galaxy SIII] sn0warmy:
CM9:

http://cm9log.appspot.com/?device=d2tmo

CM10:

http://cm10log.appspot.com/?device=d2tmo
[T-Mobile, Samsung Galaxy SIII] micahman:
CM9 is running great with the latest faux kernel. My DD fo sho until CM10 call echo and random reboots are fixed.
[T-Mobile, Samsung Galaxy SIII] sn0warmy:
I've decided to switch from CM10 back to the latest CM9 nightly. The screen glitches and the call audio issues on CM10 really made my life difficult today. I'll be curious to see what the current CM9 bugs are. If it's still just the camera bug then I will be just fine with this as a DD.
[T-Mobile, Samsung Galaxy SIII] aNYthing24:
I'm tempted to go back to CM9 (for working Netflix mainly) but a couple of things (revamped notifications, Google Now, speed improvements) keep me on CM10 for now.
[T-Mobile, Samsung Galaxy SIII] sn0warmy:
Yeah, I just flashed CM9 and went through the setup process (after letting it sit for 10 minutes) and compared to CM10 it's crawling...

I'm going to wait until the morning when the latest CM10 nightly is available and flash that. I'm hoping that between tonight's build and last night's build they've fixed some more big bugs. The changelogs are looking REAL long so I'm optimistic.
[T-Mobile, Samsung Galaxy SIII] Slicktune:
I Couldnt Find The Latest Faux Kernel You Were Talkin About

:(

Would You Be So Kind To Provide The Link...:highfive:
[T-Mobile, Samsung Galaxy SIII] micahman:
No problem, http://faux.androidro.ms/SGS3-ATT-TMO-kernel-cm-013m.zip
[T-Mobile, Samsung Galaxy SIII] lferrin:
Wow. Latest CM9 nightly with faux 13m. Already at over 2 hours screen time on and still at 60%
[T-Mobile, Samsung Galaxy SIII] PennStater:
Is there a way to have the built-in SMS app merge long texts into a single message (or at least what appears to be a single message... I know in the background it's still more than one)? This is the way it used to work when I was running CM7 on my G2, and it is what I would prefer if possible.

Thanks.
[T-Mobile, Samsung Galaxy SIII] danieljordanmaddux:
Just copied all of my pictures and videos to my computer and all of my videos taken in 1080p won't play right on the computer. Its like the videos were taken at too high fps. With windows media player videos play at about half speed and the audio gets way ahead and with QuickTime it just skips forward every second or so to catch up with the audio. /:
[T-Mobile, Samsung Galaxy SIII] digitalfiend:
8/26/2012 Nightly Build - so far so good

I've found the 8/26/2012 CM9 nightly build to be pretty solid. Great job developers! I've had a two small issues that I'd like to report if they're not already known. Where can I find a list of known issues with these nightly builds and provide feedback in the event my two issues are new?
[T-Mobile, Samsung Galaxy SIII] aNYthing24:
Check the OP. You can report your issues here.