yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] The Archangel:
That's how much tmobile wants from me to get the gs3. My sig shows what I have.
[T-Mobile, Samsung Galaxy SIII] 4Orr:
The price will drop after Christmas. If you have a Costco, they have a good deal right now.
[T-Mobile, Samsung Galaxy SIII] The Archangel:
I'm up to 138.44 :D:D:D
[T-Mobile, Samsung Galaxy SIII] 4Orr:
Good going!

Btw, I have some news that you may not want to hear. Starting in 2013, T-Mobile won't be subsidizing phones any longer. Phones will be sold at full price.
[T-Mobile, Samsung Galaxy SIII] The Archangel:
This might be my last upgrade an contact with tmobile then.
[T-Mobile, Samsung Galaxy SIII] The_F_Word:
I got my phone for 97cents it was a special for pre black friday at sams club :)
[T-Mobile, Samsung Galaxy SIII] The Archangel:
:eek::eek::eek::eek::eek:
[T-Mobile, Samsung Galaxy SIII] mt3g:
Where is this coming from!?!?! I'm buying nexus line if that's the case.
[T-Mobile, Samsung Galaxy SIII] saranhai:
Why the heck would they do that?? You gotta source?

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] Woody:
I read it today too.

http://www.engadget.com/2012/12/06/t-mobile-value-plans/
[T-Mobile, Samsung Galaxy SIII] mt3g:
In a way it kinda makes sense. But I still prefer 2 year and 200$... interesting tactics.
[T-Mobile, Samsung Galaxy SIII] 4Orr:
I read it here.

http://www.androidcentral.com/t-mobile-stop-subsidizing-handsets-2013
[T-Mobile, Samsung Galaxy SIII] The Archangel:
well this really sucks for me...im just a user here now.....
[T-Mobile, Samsung Galaxy SIII] jjlean:
That stinks they are doing that. So... 600 for a phone. F that
[T-Mobile, Samsung Galaxy SIII] flipq88:
Well it says it will still have the value plans, which is what I prefer. Even though you end up paying full price (phone payments for 20 months) the monthly bill is still around the same. Plus when you finish paying the phone your bill will be a lot cheaper. Or like me, I still had $100 left to pay off my s2 after a 10months of having it, so I paid it off and started a new value plan and got the s3. Really better than waiting 2years for an upgrade. Hoping to do the same when the S4 drops

Sent from Flip's S3
[T-Mobile, Samsung Galaxy SIII] 4Orr:
Definitely a savings there, but you will have to pay upfront. It's amazing how we have become so dependent on phones with instant internet access. It is definitely a luxury for most that we pay handsomely for. It was the iPhone people that made this mainstream in my workplace. What do you people think?
[T-Mobile, Samsung Galaxy SIII] imilleson:
That's how much tmobile wanted to charge me with full upgrade so I talked to cancelations and said I am going sprint for the cheaper gsIII and they gave it to me for 150 to retain me
[T-Mobile, Samsung Galaxy SIII] The Archangel:
Might have to have another conversation with them.
[T-Mobile, Samsung Galaxy SIII] imilleson:
Looks like your current balance is 150$, maybe today T-Mobile will make you a very happy android user :)
[T-Mobile, Samsung Galaxy SIII] marseillesw:
Hey Saranhai, u think u and the team can port this? Test your might!!! Lol

http://xdaforums.com/showthread.php?p=35161290

sent from GS3 disguised as a GNote2
[T-Mobile, Samsung Galaxy SIII] ruvelojr:
Think its the retention Dept for T-Mobile.I was on the line with them for 2 hours on n off hold this n that but I. The end got my s3for 150 in 50 mail in
[T-Mobile, Samsung Galaxy SIII] pnut22r:
Saranhai and marsielles

I was with both of you on the mytouch 4g many moons ago. I see you both with the galaxy s3. You like the device? I have a Nexus 4 on its way, but after using my wife's for a few days, I'm not so sure about it. Instead I might pick up a s3. Seem like a good idea? Haven't spent much time on the s3, you guys like it? Why? Would you rather have an n4, or you like what you got?
[T-Mobile, Samsung Galaxy SIII] mattedwards2686:
I didnt like my N4. I had the infamous buzzing problem from the speaker, terrible battery life, and the build quality received terrible reviews( link attached at bottom). Also, the lack of expandable storage...It lasted 3 days before I called up t-mobile and demanded another phone.

http://www.xda-developers.com/android/nexus-4-battery-shot-reveals-potential-quality-issues/
[T-Mobile, Samsung Galaxy SIII] marseillesw:
What up pnut, yeah the mt4g community was like home away from home bro..small and tight knit, good times...but about the s3 itself, it's a beast of a phone and although I miss sense like my momma biscuits, I don't regret getting this phone not one bit. The only device I would consider trading for right now is the note 2, but I'd probably loose the pen so screw it lol, plus I'm running the note 2rom anyway. The nexus four to me isn't an upgrade, its more like a lateral step. No removable battery or expandable memory, and made by LG..PASS!!! Development on the S3 is growing fast with more and more devs picking up this phone..shout out Saranhai!! (Still asking about that sense port bro! Lol) Anyway, u won't be disappointed with this piece of machinery, just be prepared for the jump from htc to sammy..whole new tool set bro...not to mention, one of my favorite kernel chefs just got this device and is already making magic..I'm here to stay...till the s4 that is

sent from GS3 disguised as a GNote2
[Verizon Samsung Galaxy S III] jl93sundance:
Hi, I'm going to be rooting my buddy's vzw gsIII, i'm wondering which are some of everyone's favorite roms? Looking for a themed, and stable rom. Also any red themed roms? I'm on a sprint gs3 running jellybomb domination, just not sure what are some good roms for verizon. Thanks:good:.
[Verizon Samsung Galaxy S III] jonnyboiii:
I'm on bean's build 2 (latest is B3) and I love it. It's very stable, themed to be AOSP-esque with some cyan blue, themeable clock size/position, battery look, nice notification shade with customizable toggles and aroma installer which is incredibly handy.
[Verizon Samsung Galaxy S III] JustSomeDude:
For stable/worry-free, go with scrosler's CleanRom 4.5, then choose one of the red themes from WasabiWa83's Ultimate OMG Theme .
[Verizon Samsung Galaxy S III] jonnyboiii:
There isn't a lot of themeing going on in that rom it's just a cleaner faster version of stock.
[Verizon Samsung Galaxy S III] ddurandSGS3:
which is where wasabis themes come in!

jonny can you add a wallapper to that notification pull down you just posted in beanss?
[Verizon Samsung Galaxy S III] jonnyboiii:
Not that I'm aware of, but I like the transparent themeing it has :)
[Captivate Q&A, Help & Troubleshooting] johnnyrichter:
There seems to be plenty of us still suffering sleep deaths on our cappies and I figured an up-to-date list of possible remedies would be nice, just in case there's been any progress in figuring out what causes the problem and how one could go about fixing it.

So far the solutions I've tried that did not work for me...

-Increased minimum clock speed

-Increased voltage of minimum clock speed

-Removed Titanium Backup

-Removed all third party apps

-Disabled deep idle

-Removed/didn't use task killers

-Tried various ICS & JB ROMs

-Tried various ICS and JB kernels, including baked-in versions

-Tried i9000 bootloaders

These are pretty much all the details I have so far on these SoDs, hopefully they add up to a possible cause or explanation...

-SoDs happen anywhere from 1-2 times an hour to 1-2 times a day and only when screen is locked/phone is idle

-Having GrooveIP or Skype running doesn't prevent SoDs, but Pandora Radio running seems to prevent it

-Sometimes on a fresh ROM install I can go about 24-36 hours before the first sleep death, but after that they occur normally

-If I unlock the screen every few minutes it seems to stay on. If I let it sit anywhere from 15-30 minutes or longer then it will usually shut off.

-The only time I can get this phone to not suffer an SoD is on stock software(GB KK4). Not sure what this means, but it is aggravating because I would like to have better software.

What remedies have you tried, and what worked/didn't work for you?
[Captivate Q&A, Help & Troubleshooting] BWolf56:
The first thing I'd try after disabling deep idle is to change kernel. Also, usually sleep deaths happen even when plugged so yours is kinda special lol.
[Captivate Q&A, Help & Troubleshooting] johnnyrichter:
I've used all sorts of different kernels and ROMs, get SoDs with everything. Some might result in a day or maybe three days of no sleep deaths, but they eventually start right back up without any sort of a "trigger" to cause it...like changing a certain setting or installing a certain app.

I was hoping someone would have determined the actual cause by now but it seems it's still an unknown factor causing it.
[Captivate Q&A, Help & Troubleshooting] BWolf56:
SoD doesn't happen much with JB, it's usually due to deep idle or bad kernel

user

config (not saying this is the case here).

Have you tried flashing back to stock KK4 and do a clean flash of whichever ROM you want to use?

If you could narrow down what causes it or get some sort of logcat of when it happens, that would probably help. Although, flashing back to stock still seems like the best bet.

Also, you're running on a nightly build (as per your signature). Ever concidered using a daily (stable) ROM?
[Captivate Q&A, Help & Troubleshooting] johnnyrichter:
I've wiped back to stock numerous times and have used many different stable ICS/JB kernels and ROMs. I've tweaked almost every kernel setting possible, tried all sorts of different overclocks, tried deep idle on and off, etc.

The only time I never had SoDs is when the phone was originally stock. Ever since the first time I rooted and ROM'd it I've been getting sleep deaths. I have not tried actually using stock software again to see if the SoDs go away mainly because I don't want stock software.
[Captivate Q&A, Help & Troubleshooting] BWolf56:
That's very unusual. If I were you I'd still try to use stock for testing purpose. Oh and I'm sure you already tried this but don't OC/UV.

If you don't get SoD on stock, try flashing something else that people haven't reported SoD on (like AoCP on stock kernel). Which makes me wonder, have you used a JB rom with it's stock kernel (CM10/AoKP)?
[Captivate Q&A, Help & Troubleshooting] johnnyrichter:
Most ROMs I've tried I kept the stock kernel. I'm also on the stock kernel for CM10 at the moment.

I have tried two different AOSP ROMs with their stock kernels and had SoDs on those as well.

I have also tried no OC with at least three different kernels/ROMs.
[Captivate Q&A, Help & Troubleshooting] BWolf56:
I'm really running outta ideas here.. This doesn't seem normal. Only other thing I can really think of is either that it's coming from a app or it's a hardware problem (maybe battery but somehow doubt it).

So yeah, only thing I could suggest other than stock KK4 and AoCP is to clean flash without restoring your apps (Gapps are fine of course) and use stock kernel.. After that, I'm all outta ideas.

You got some testing to do, I'll be looking forward to the results.
[Captivate Q&A, Help & Troubleshooting] johnnyrichter:
The only apps that have been consecutive across all my different software installations have been...

-Gapps

-Gmail

-Facebook

-Pandora

-GrooveIP

-Heywire

-Skype(Only been using this for a couple of weeks so I can probably rule it out)

I could try a fresh CM10 nightly and only run gapps. Maybe wait a few days and then install GrooveIP, wait a few days and then install Skype, etc until I can maybe get an app install to trigger the SoDs.

You mentioned logcats...what are those? Is this some sort of debug log? If so, do you think it could actually pick up any events leading up to an SoD or even log the SoD itself? I'd imagine if that was possible someone would have posted the results by now.
[Captivate Q&A, Help & Troubleshooting] BWolf56:
A Logcat is simply a log of everything your phone does (Logcat Extreme is a good app for it). You'd have to set it to run in background until a SoD happen and then you'd see w/e your phone did before the SoD happened. Could help narrow down the problem. The only thing I'm not sure is if it will save the log before your phone shuts down but that could be something to look into. If not, then it won't be any help eh.
[Captivate Q&A, Help & Troubleshooting] johnnyrichter:
I'll check out that app right now and report back with any findings.
[Captivate Q&A, Help & Troubleshooting] johnnyrichter:
Booted phone up just now after an SoD and the only log available is the one it just started. So if it logged anything before it looks like it didn't save it. Crap.
[Captivate Q&A, Help & Troubleshooting] johnnyrichter:
One-clicked back to stock GB KK4 and after a few hours I have yet to get a sleep death so far, but overnight idling will be the final test for that. That's with the following installed...

-GoLauncherEX

-Skype

-Gmail

-Facebook

-Opera

-GrooveIP

-Heywire

While installing all my apps I realized that the GrooveIP installation I was using was an apk I got ages ago, one that I don't think has been automatically updating. I thought maybe that could be the issue so I went with a fresh install from the market.

If it turns out that SoDs only appear when rooted/ROM'd then I'll probably toss this phone once I find a replacement because I can't be without my CM10 and devil kernel. I really wish someone could figure out the cause and a possible solution for this. :(
[Captivate Q&A, Help & Troubleshooting] BWolf56:
CM10 features can be found in other ROMs. As for Devil, it could be the problem. Hopefully KK4 will be fine, at least we'll have a start point to work from. If you get SoD on it, get rid of GrooveIP and heywire. We'll then know if it's app related.
[Captivate Q&A, Help & Troubleshooting] johnnyrichter:
Still no SoD and that's with/without Skype running. GrooveIP boots with phone.

If it won't SoD on stock software then I wonder what the problem could be? It's SoD'd with every kernel and ROM I've ever tried.
[Captivate Q&A, Help & Troubleshooting] JoeCastellon:
Sorry for the extreme noob moment here, how do I tell if my device went into SoD? Is it when it gets so extremely slow that even the power button seems to have no effect?

I get that a lot when I've been browsing for a few minutes (even on stock browser) or when playing some games.
[Captivate Q&A, Help & Troubleshooting] johnnyrichter:
SoD means, while idle, that it randomly turns itself off. It was a defect in X amount of phones produced up to a certain IMEI number, and ATT/Samsung at one point offered an exchange program so people can turn theirs in for a model that didn't have the issue.

What you're suffering from is low memory. You probably have apps running in the background that are utilizing X amount of RAM, and your browsing/gaming is eating up the rest which slows down the phone. Some ways to fix this...

-Use a kernel that allows you to increase maximum memory. I think Devil kernel allows up to 396mb with no downsides, and 413mb at the cost of something that has to do with playing a certain video resolution IIRC.

-Use a task killer. This lets you kill running tasks except for those you choose to "lock." Some advise against using a task killer, but honestly I've yet to have a problem with any of them. My favorite is the one you can get for GOLauncherEX.

-Use Titanium Backup to delete(or freeze if you buy the pro version) apps that you don't use that you can safely remove, specifically items that constantly run in the background eating up your RAM.

-Use a different ROM. There's plenty of ROMs out there including slim/aosp/etc releases that are faster and arguably better-performing.
[Captivate Q&A, Help & Troubleshooting] BWolf56:
I believe you tried this already but using the I9000 bootloaders seems to have fixed the SoD issue for many people on JB.

I'm not sure if that would change anything, but try flashing Mosaic.
[Captivate Q&A, Help & Troubleshooting] johnnyrichter:
I don't think I've tried the i9000 bootloaders. Any time I flash back to stock I use the link in my sig(one-click w/ bootloaders) and those are the GB version. My phone still hasn't SoD'd on stock software/GB bootloaders so I wouldn't think those bootloaders are the problem, but on the other hand I suppose it's possible that a third party kernel/rom clash with them on my phone.

Are there any downsides to using the i9000 bootloaders? Would you happen to have a link to this mosaic thing you mentioned?

ETA: If it matters any, when I got the phone I believe it was on GB KK4 and was never modded before. When I got it I used the easy-root to corn 7.0a method and first ran Legend5 ICS ROM. That was the first time I started suffering sleep deaths. Ever since then I have used the one-click back to stock w/ GB bootloaders before using any other kernel or rom.

I've used several different kernels/cwm versions to obtain root, at least 6 different ROMs, several different versions of gapps, and numerous other kernels after ROM installation. I've also used the baked-in kernel of each ROM for at least several days before upgrading to something like Devil or Sema. SoDs on everything, both ICS and JB.

I have also tried one-clicking back to stock with what I believe were "up-to-date" GB bootloaders. This was posted by another member that did it and fixed his SoD problem. It didn't produce any sort of a change for me.

I have not tried checking for SoDs on just a root(without ROM). I suppose if I did this I could figure out if it's the root or the ROM that is triggering the sleep deaths, but even if I did get any results from that I'm still not sure how to figure out exactly what's causing the problem since this event apparently can't be logged.
[Captivate Q&A, Help & Troubleshooting] BWolf56:
Mosaic is a ROM that was made by The Family; http://xdaforums.com/showthread.php?t=1061203

It is I9000 based so I'm thinking you won't get any SoD on it. Thing is that it's not JB based. Devs aren't porting from I9000 anymore so you won't find a I9000 ported JB ROM. (Hoping I'm not wrong on this lol)

And yeah, many users reported that flashing the I9000 bootloaders with a JB ROM fixed their SoD problem. Back in GB, it wasn't suggested to have I9000 bootloaders and run a I897 ROM (music player wouldn't work and some other little things) but it seems fine now.

EDIT: I highly doubt root is the problem.
[Captivate Q&A, Help & Troubleshooting] johnnyrichter:
So to run that ROM I need to Odin the i9000 bootloaders, root, then install that?

I wonder how much different this will be compared to Legend5, iirc the same guys made it and I really liked that ROM.
[Captivate Q&A, Help & Troubleshooting] BWolf56:
Same team, different Devs (Now back to 2 different teams: Collective and The Family) :P And yes, Mosaic runs on I9000 bootloaders but could be fine on I897.
[Captivate Q&A, Help & Troubleshooting] johnnyrichter:
Can't seem to find any info along the lines of using Odin to install i9000 bootloaders on my phone. All I'm finding is how to get the GB bootloaders which I already have.

Are they included in the Odin Mosaic flash? If so, since I'm on stock GB KK4, I should be able to just follow the mosaic install instructions and I'll be gtg?
[Captivate Q&A, Help & Troubleshooting] BWolf56:
Umm I don't think they are (unless it says so). The I9000 bootloaders are indeed GB bootloaders, you can probably get them in the I9000 thread.

Here for the BLs:
[Captivate Q&A, Help & Troubleshooting] johnnyrichter:
Sweet, I'll get on that.

There's a problem with Mosaic, though. They only have one mirror and it stops at or before 25%. No one has responded to me in that thread, assuming it's abandonware now that they appear to be working on the SIII port.
[Captivate Q&A, Help & Troubleshooting] BWolf56:
Actually I posted a link in Mosaic's thread lol
[Captivate Q&A, Help & Troubleshooting] johnnyrichter:
Awesome, downloading now.

I didn't realize it until now, but that post you quoted from user fohdeesha was the last thing I tried and it still resulted in SoDs. Those are the latest GB bootloaders.

In that post he was replying to this person..

Apparently they went the i9000 route and it got rid of their SoD problem. His/her experience and instructions are here...

http://xdaforums.com/showpost.php?p=25722784&postcount=1153

They have yet to report the SoD problem again so I went ahead and did this. I didn't notice any difference afterwards, and nothing looked different in my about/status info so I'm not sure if it worked or not. I suppose I can go ahead and flash Mosaic now.
[Captivate Q&A, Help & Troubleshooting] johnnyrichter:
Looks like the file you re-hosted is a .zip rather than the tar.gz, so I can't flash via odin. I'm going to use the easy-root method in my sig and then flash Mosaic. Will report back with results.

Also, download mode is now VolumeDown + USB so it looks like the i9000 bootloaders are installed. I also noticed the i900 bootup screen which is only up for a second.
[Captivate Q&A, Help & Troubleshooting] johnnyrichter:
Crap. It now boots up to the i9000 boot screen, switches to the SGH-I897 bootscreen, then reboots. Here's what I did...

Flashed i9000 bootloaders via Odin. Confirmed by button-combos for download/recovery and i9000 bootup screen. Phone booted up fine.

Easy-rooted corn 7.0a to obtain root/cwm. Phone rebooted in to recovery.

Wiped/reset, wipe cache, wipe dalvik.

Flashed mosaic.zip in CWM. Rebooted.

I'm guessing I did something wrong with the Mosaic install. The instructions are for tar.gz/odin installation and I have a .zip which is for CWM flashing, so I did what I normally do for normal ROM flashes. I was able to button-combo in to recovery and re-flash Mosaic to see if that helps, but upon reboot it just got stuck in the bootloop again.

I am now one-clicking back to stock GB KK4 w/ GB bootloaders until I can figure out what I did wrong and how to go about this the correct way.
[Captivate Q&A, Help & Troubleshooting] BWolf56:
Well there are 2 things you can do:

1. Flash Mosaic on the I897 bootloaders.

2. Flash a (stable) JB ROM on I9000 bootloaders.

As for M9, it is meant to be a flashable zip. I don't have the Odin version myself.
[Captivate Q&A, Help & Troubleshooting] johnnyrichter:
Ah ok. I thought I was supposed to flash mosaic on the i9000 bootloaders. That's probably where the double-boot-screen boot loop issue came from.

I one-clicked back to stock GB KK4 w/ bootloaders. I'll try my sig easy-root once more and flash mosaic again.

If that produces SoDs then the next step would be to one-click back to stock again, odin the i9000 bootloaders...then what? Should I use the easy-root method in my sig to get cwm or is there another way I should do that before trying to flash a stable JB rom? Is there a short-list of good JB roms that are known to work with i9000 BLs?
[Captivate Q&A, Help & Troubleshooting] johnnyrichter:
1. Results in boot loop.

2. Haven't tried yet since I don't know if there's something I'm doing wrong, i.e. using the easy-root in my sig instead of a more proper way to obtain root/cwm.
[Captivate Q&A, Help & Troubleshooting] BWolf56:
I kinda expected boot loop for the first option but figured it would be worth trying.

As for your root, it should be fine. Any JB ROM should do the job (a few people have been reporting reboots/SoD on LANIGHT tho). Just make sure you grab something stable. You said you liked Legend, AoCP is made by the same devs so you might like it.
[Captivate Q&A, Help & Troubleshooting] johnnyrichter:
I'll check out some of the other popular JB roms in the dev section and pick one to try out. CM10 and LANIGHT definitely SoD'd on me but that was with the stock GB bootloaders. This is my first attempt on i9000 bootloaders.

Just so I'm sure I'm not doing anything wrong...

One click back to stock GB KK4 w/ bootloaders, odin flash i9000 bootloaders, easy-root corn 7.0 kernel, flash rom via cwm?
[Captivate Q&A, Help & Troubleshooting] BWolf56:
Sounds right.