yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S II SGH-T989] Calz-:
It's a common bug in cm, aokp both ics and jellybean roms. You have to go to your apps settings, and find media storage and clear data. Reboot your phone and let it reload for a couple minutes.

Sent from my SGH-T989
[T-Mobile Samsung Galaxy S II SGH-T989] TheLastSidekick:
Yep. Had it too. Don't know how to rid of it. I hence stopped using JB. No problem now. Then again I'm on CM 9.1 4.0.4 and not using Apollo.

Edit : Its a normal bug to get sound notifications in all music players after using CM and AOKP. Try the other posters fix. Looks legit, lol. When I go back to JB I'll try it myself.
[Kindle Fire Q&A, Help & Troubleshooting] shnish:
Today I tried loading 4.1 Jellybean on my fire, but it wasn't opening applications properly and being annoying so I unloaded it. I used KFU to root it, and had TWRP recovery on it. I then figured I'd revert it back to the default OS, so I grabbed a copy of the kindle fire 6.2.1 software from Amazon's page and renamed it to update.zip (it converted to a .zip with identical contents to the one directly from KFU).When I had TWRP, KFU recognized my device as online, but didn't have a version, so there was no help there. I wiped the entire thing using the recovery tool and then I hit "Install --> Update.zip". Everything seemed fine after this worked, so I rebooted the device. I thought it worked, but now it's stuck at the Kindle Fire default splash screen. When I plug iit into my computer, Windows doesn't recognize it, nor does KFU. I haven't tried letting the battery drain (since that would take awhile), but it seems like it's bricked. Please help!

EDIT: My main problem right now is that it can't even be recognized at windows. I feel like it's stuck in the wrong fastboot mode right now, but I can't even get windows to recognize it. Also, it's not running Fire fire fire, the splash screen shows the basic unanimated Kindle Fire logo. It's likely stuck on fastboot 4002 instead of 4000. I'm currently letting the battery drain so I can plug it in and see if windows will recognize it. My guess is that I can get it to work as long as windows will recognize it.
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
I don't have time right now to get into very much with you, so I'll have to edit my post when I can (unless someone beats me to it). For now, though...

DON'T LET YOUR BATTERY DIE!
[Kindle Fire Q&A, Help & Troubleshooting] shnish:
Are you sure about that? I was just reading about how it's just stuck in the fastbooter and I have to let the battery drain, plug it into my computer to get my computer to recognize it, and then it should work. Then I just have to change the fastbooter from 4002 to 4000 and it should work. Is this wrong?
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
You're right, I'm lying to you. I have nothing better to do than to feed you misinformation in the hopes that it will prolong your suffering.
[Kindle Fire Q&A, Help & Troubleshooting] shnish:
I know that you know more about this than me, but I feel like if it's stuck on the wrong fastboot type, preventing the battery from draining would be a bad idea (or at least slow down the "fixing" processor). Sorry, but why does that seem so wrong?
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Since you are having trouble spotting the STICKY at the top of this forum, I'll help you out a bit.

http://xdaforums.com/showthread.php?p=25400963
[Kindle Fire Q&A, Help & Troubleshooting] shnish:
http://xdaforums.com/showpost.php?p=20619033&postcount=11

This is what I read that might solve my problem. Does it seem incorrect? I feel like the only way to get it to recognize the kindle fire in windows is to either manually put it in USB mode by prying off the back cover, or to let the battery drain.
[Kindle Fire Q&A, Help & Troubleshooting] shnish:
But my Fire won't even work when plugged into my computer. Can you really quickly explain any steps I should take to at least get windows to recognize it? Thanks!
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
umm...
[Kindle Fire Q&A, Help & Troubleshooting] shnish:
Alright. Looks like I might need a factory cable?
[Kindle Fire Q&A, Help & Troubleshooting] kinfauns:
Some of the ideas in the post are going in the right direction, but draining your battery is not one of them. That would only complicate matters.

I suggest you slow down and do some reading...

http://xdaforums.com/showthread.php?t=1668159

You must first determine what state your device is in based on what happens when the device powers up. The only way you'll be able to fix this problem quickly is if you are truly in fastboot mode, but I have some doubts about that. If you do not understand the terminology used in the post above, you must read this...

http://xdaforums.com/showthread.php?t=1552547

If you are going to rely on the help of others here, you are going to have to learn the jargon and understand how these parts fit together. I suggest you do that before proceeding.

The second post in that guide will help you to fix your device drivers and have the computer recognize the device.

Personally, if I were in your shoes, I'd find a way back to fastboot mode and reflash TWRP and then FFF from TWRP before trying to boot it normally. If your system partition happens to be broken and you reboot it into it, you'll be going backwards and then you'll need a factory cable or have to open up the case.
[Kindle Fire Q&A, Help & Troubleshooting] shnish:
The device ended up losing power, but it still powers on properly when I plug it in (stuck on the kindle fire logo, of course).

I suppose it's not in fastboot mode, it's just stuck on the stock loader. I'm not quite positive, but it seems like I'll need a factory cable to get this thing working again. I really don't want to have to blow any money on this, if I can revert it back to stock settings easily, I'll never mess with it again. Is there any additional help that can be given if it's stuck on an unanimated stock screen and won't be recognized by windows?
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
http://xdaforums.com/showpost.php?p=30629067

[Edit:] This might be helpful as well...

http://xdaforums.com/showpost.php?p=31117605
[Kindle Fire Q&A, Help & Troubleshooting] shnish:
So if I install Ubuntu, I should be good to go? Ubuntu will recognize the kindle fire?
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
Read the post I gave you.
[Kindle Fire Q&A, Help & Troubleshooting] shnish:
Yes. He has the exact same problem as me! I did the same thing as him, and I'm really hoping I'll be able to solve this issue. All I want is the stock kindle back so I can stop worrying. I've read through tons of these posts (I have 13 xda posts open in my browser), but none of them seem too helpful as to how I can get my computer to recognize the Kindle. My guess is that Ubuntu won't recognize the Kindle either, though. In that case, would a factory cable solve all my problems? I stupidly removed root access by simply updating my kindle fire without thinking of the problems that could have come with that. I figured it would just remove root access and start booting up normally. I was very wrong.
[Kindle Fire Q&A, Help & Troubleshooting] shnish:
I'm going to try it in Ubuntu, but assuming that doesn't work, I'll need to get a factory cable. What do I do to revert to stock settings once I have a factory cable?
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
I'm really trying to be patient with you, but you're making it extremely difficult for me.

Your lack of attention is troubling. If you would take some time to actually read and process the information given to you, you would see that everything you need to know to fix your problem is there. Be a little less argumentative and follow direction, and you'll see that, not only are people more willing to help but you'll have your problem solved a lot easier and faster than you are now.

That being said, this will be the last bit of help you'll recieve from me...

The first link I gave you, sends you to my SoupKit thread. Read it. Ubuntu(Linux) does not detect the Kindle Fire (or any Android device) by default; it must be configured, which is why I sent you to the "Idiot-proof way to configure Linux for adb and fastboot".

While booted into Linux, run the script and reboot; that's it. You can figure out how to fix your Kindle on your own from there.
[Kindle Fire Q&A, Help & Troubleshooting] shnish:
Thanks. I normally wouldn't act this way, but I'm having trouble calming down about this (I usually get this way when technology breaks). I know that in the end everything should be fine, but for some reason I can't get myself to actually stop worrying about the damn thing. I really do appreciate all your help, and I swear I have been reading all the links that have been sent. It's just that even with what I've read, I don't 100% understand everything. I know the general problem with it, but I'm a complete noob with shell commands. Fixing it once I can actually connect should be easier, just have to put the recovery back onto it and properly set it back to stock settings, right?
[Kindle Fire Q&A, Help & Troubleshooting] soupmagnet:
:good:
[General Questions and Answers] stagmo:
I've been through four roms and managed to try each one out successfully. I've had issues, but none too difficult to figure out. I tried this one:

http://xdaforums.com/showthread.php?t=1867484

And am having the WiFi problem some of the other posters outlined. I can't post on the forum because I don't have enough posts. I'm coming from the lastest Helly Bean build (http://xdaforums.com/showthread.php?t=1783064). I followed the instructions (as much as possible from my version of recovery). I wiped data 3 times, wiped cache, wiped dalvik cache, then installed it. Wifi gets stuck on "turning on wifi" and remains there after restarting and attempting to reinstall the rom 3 times. Finally gave up and went back to Helly Bean.

Gonna check out a couple other JB roms in the meantime, but I was hoping that one would work since people attest to the speed!
[General Questions and Answers] roofrider:
Asking in the device specific (captivate in your case) General and Q/A forums will be of more use to u.
[General Questions and Answers] stagmo:
Thanks, will do.
[Galaxy S III Q&A, Help & Troubleshooting] JitinDhillon:
I recently flashed CWM onto my uncles GS3 and rooted his current rom. I made a backup and then tried out a new AOSP rom, which we decided not to keep because my uncle did not like it. But now, returning to the old rooted stock rom, every time the phone disconnects from wifi, it completely freezes up on the lock screen. Pressing the lock button does not shut off the screen and instead just locks it. You are unable to unlock it as the phone completely freezes up. The only way to get into the phone is to double tap home to get into the voice commands, and then go to home from there.

But even after that the phone continues to freeze. I tried another ROM on his phone today, but the problem still persisted a while later. It all happens when the phone is connected to wifi, and you walk out of range. After which the phone starts to freeze up.

I'm totally unsure whats going on. I just flashed the rom again, and we are trying a clean slate with no restoring of any data. It may have started to happen after we installed root browser (just as a guess), but we could be completely wrong.

If this continues again on this rom as well (which is Revolution HD) Im going to go back to completely stock (rom & recovery), and hope it still doesn't persist there. If not then I am out of options, and I have no clue what to do.

Any help would be GREATLY appreciated. We spent so many hours today trying to resolve this.

Thanks!
[Galaxy S III Q&A, Help & Troubleshooting] SirKunon:
Usualy WiFi problems are kernel related. Have you tried Siyah or another custom kernel?

If this will not help than returning to stock with all wipes is the best idea, this should resolve your problem. If not, than you can try to reset router or set static IP for s3. Also try to remove WiFi setting for your home network in the phone and set it again manualy or via WPS mode.

i9.0.1.3k galaxy imperator
[Galaxy S III Q&A, Help & Troubleshooting] JitinDhillon:
Thanks for the reply. This issue has been occurring between two different roms, so can the kernal still be an issue? Its happened with the absolute stock rom (w/ root) and Android HD Revolution.

My uncle said he would play around with the phone and let me know if it freezes again by tomorrow. If it does im going to wipe and stock.
[Galaxy S III Q&A, Help & Troubleshooting] JitinDhillon:
Can anyone show me where to get the stock roms for the i9300?

I've downloaded and tried 3 different ones, but the phone never manages to boot up!
[Galaxy S III Q&A, Help & Troubleshooting] Arsaw:
http://xdaforums.com/showthread.php?t=1671969
[Galaxy S III Q&A, Help & Troubleshooting] juliobahar:
Same problem on Galaxy Note N7000, did your problem resolve by reverting back to stock because I've tried every possible option, to no avail?
[Galaxy S III Q&A, Help & Troubleshooting] JitinDhillon:
Go into recovery and wipe the cache, I believe that was my problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tejh:
Very nice! Thanks for porting this over. Mind if I pm you about some questions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] d0cx:
Great. I might be testing this tomorrow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gharris040604:
thank you! Im downloading now (such a flash addict)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drewgaren:
let me know if you run into any issues flashing, make sure to follow the directions. if you are upgrading you should not have an issue. if you are doing a new install make sure you follow the instructions.

also do a backup first.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wali01x:
reserved for later =)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gharris040604:
awh darn yea that was the reason you guys took yours down, I've already ran that one :crying:

I will still load it up and give it a try, hell I got all night to test it out
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Alucardis666:
Thanks for sharing this :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wali01x:
yeah even we're trying to dig in but it seems its internal issue. but lets hope for another leak and we are all rolling.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drewgaren:
Sorry to burst your bubble, but root has always for my permissions on my phone. Superuser seems to work fine and I am able to adb fine as well. I have not had any force closes in Browser yet, maybe because I tend to use Chrome more then Browser. However I still have not once force close on the rom. I have yet to run Facebook longer then 5 minutes but it did not force close on me and has sync'd fine. There is some issue with other things syncing however such as calendar. I had to turn that on and off before it re-synced.

If you have a issue, simply don't run the rom. For me and many others it seems to work fine. When we have an official build we will use that but with this and future improvements it's something to start. I offered something for people to enjoy not to bash. Don't use it if you don't like it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] T3hBraveBoss:
Would that apn work for bell (I would persume not) if not what is the apn for it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] expertzero1:
The international got another leak today so we should get one soo.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unleashed12:
Wow thanks so much for this! been waiting forever since the tmo firmware first leaked, always figured someone would do a port since the phones are so similar.

:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Crimson Ghoul:
Would you mind posting screenshot pretty please :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drewgaren:
I'm not sure if bell will work but I believe it may
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drewgaren:
It looks like the stock galaxy s iii
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] T3hBraveBoss:
I found my apn setting,... I just went into my settings and copied everything down. Installing the rom right now I'll install it tmr; if it works out thank you very much

And just to clarify its fine to install this rom over stock rooted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wali01x:
wow you went hostile on me like im against your contribution or time. i respect it and not against your work. i was just stating when i tried stock browser its always vibrating twice & closing down which leads to a problem in webcore.so and as far as facebook if you click someone's link its then it'd cause problems. i never mentioned anything about sync because it works well. and running the rom? i am running it right now too, and yeah remove browser for chrome and so forth even im aware of that before anything. and lets say for a noobie they're gonna question you 1,000 times as to why they're getting shell issues so you might as well be prepared to let them know what needs to be done rather then turning hostile like you did just now. and did u ever have skyrocket i727 ? cause i remember seeing you there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gharris040604:
alright here is my breakdown, I wiped everything than installed, smooth rom browser is still an issue phone vibrates then closes tried clearing cache etc still a no go ( I use chrome for the most part) havent tried the facebook app but here is a tip use fb from the chrome browser looks exactly like the app plus loads a hell of alot faster imo. any questions feel free to ask
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trinikartel:
Flashed this last night. So far it's been a bit rocky with the force closes (nothing too drastic) but overall I'm liking it. Great job drew!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ryandelman:
Not to derail things, but people need to let devs handle their own sh*t, in my humble opinion.

Anyone has the right to ask for ETA, and if the dev wishes to take exception to that request, the dev can do so him or herself. No need for one of us Joe Schmos to chime in on the devs behalf like some little yappy Chihuahua with a Napoleon complex.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mocsab:
Kernel ???

I have been using this ROM since it's release and other than the issues mentioned in OP I have had no problems at all - my only wish is that there was a kernel avaiallble that I could use to adjust voltages and OC - I don't beleive the current kernel supports that - and I don't beleive that Kootz's touchwiz kernel will work either - any chance there might be a kernel soon?

Even without that - this ROM is pretty cool and nice to have JB in Touchwiz - thanks for your efforts!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gharris040604:
Not until source is released
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alias3800:
For the people not really having any issues (i.e. forces closes), did you do anything in specific? Like signing in to apps only using the enter key as someone suggested earlier, or something to that effect?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] biggggant:
I did a wipe of data, cache etc fixed permissions a few times and I still had a few problems. I did do an app only TiBU restore. The only issue that bothers is me is the nfl.com fantasy football app crashing. I can't wait to try the next release and see if things have improved.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alias3800:
Yeah same here, because this rom, early as it is being released, is really the best of both worlds. I'm too used to Google now and the smoother multi-tasking menu
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RiPpeR_dUdE:
I wiped data, caches, etc... installed then restored all apps/data from TiBu... no issue's other than the signature problem I posted in an earlier post.... I did remove some of the TMobile crap and did have to manually create the pta APN, but other than that, working fine.

Although the signature issue is minor, I did restore back to ICS until the next release... it just bugs me, so we'll see if its resolved with the update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FrankJL_:
Anxiously waiting for the next reelease.

I thought I owuld never ay this. But I enjoy everything touchwiz offers. I think i finally found the one rom i can stick with
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] meleii:
Now that bell got a least will you use that as base?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chiensibut:
hey could i flash this rom on my t-mobile s3 seem it is tmobile based, the original leak had a gallery pick wallpaper bug, was it been fix on this one?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andrewjrr:
good for the most part.. anyone else having issue of screen staying on when a text comes in? stays on until i either hit the power button or clear the notification

edit: fixed on a reboot, not sure what the cause of the problem was though
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enzyne:
Refer to the tmobile galaxy s3 section.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drewgaren:
New leak update

I am currently working on the new leak there is no eta, originally I had planned for today but I'm going to try do some additional things in the kernel and the rom itself. I will get it out as soon as can.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cundiffr:
Anyone experiance this with this rom? Gallery has used almost 600mbs.

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drewgaren:
Turn off Google Photos and Picassa sync in your Google account.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drewgaren:
You can't flash this on T-Mobile as some files including the kernel have been updated for SGH-I747 device. T-Mobile has there build that this is ported from.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jhoopes517:
SMS not working? I added the APN...

NVM: Just needed a power cycle.

Thanks for the good work! Like the rom so far!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drewgaren:
Update: We now have a leak!

UPDATE

WE NOW HAVE LEAK!

http://www.sammobile.com/2012/09/06/first-jelly-bean-ota-leak-for-samsung-sgh-i747m-galaxy-s-iii/

I will have this for SGH-I747 also should work both ways.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jawonder:
Everyone's getting leaks hey Sammy what about att ? . Can't wait for you to fix this up for us , nice ! .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erwinyap69@gmail.com:
Anyone with Rogers up yet? ?

SGS3, GNote, LG Optimist HD, EVO 3D, gotta Stop swapping every 4mths...... lol....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1stHTCphone:
I am using Fido with a Roger phone... It's working Good!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] g0d4lm1ty:
Slowest download speed ever.. Should use lte instead of Wi-Fi.. too late.. half way through.

Sent from my... oh wait.. he didn't.. oh yes he did. ... Sizzent from my Samsizung Gizalaxy S Thrizzle...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rambo8987:
Any themes for this Rom? Is there a way to use blackjellybean theme?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drewgaren:
I don't have themes for this but Milestone 5 has themes when it's out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rambo8987:
What's the di difference between this and 4.5
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bronos:
Is there anyway to update without having to setup my widgets and settings? Titanium backup pro doesn't seem to do it or I'm not backing up properly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rambo8987:
How are you backing up? Mines retains my set up
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] g0d4lm1ty:
Flashing ms4.5 now. See you in a few...

Sent from my... oh wait.. he didn't.. oh yes he did. ... Sizzent from my Samsizung Gizalaxy S Thrizzle...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
As far as the widgets go it depends on the launcher. If you use something like Nova Prime and do a backup with Nova it will be much easier to set up your widgets after flashing a new ROM.