yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chasesavestheday:
If I take a backup via ROM Manager and then install the new updated bootloader, rom, and kernel. Can I still restore back to that previous backup before all of that? Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
To be honest I would stop using Rom manager. And if you do restore it will not restore the bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] F1reEng1neRed:
Duplicate
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chasesavestheday:
What would be the reason to quit using Rom Manager? What would you suggest using? Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
Use the Recovery. Rom Manager has always done nothing but cause issues on most devices. Use the recovery options.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrben522:
I had this for about the first day after I updated to the latest build, it seems to have gone away for me though. If it's persistent on your device I would suggest you wipe and reflash, if that doesn't do it just revert back to your nand and wait a free updates and it will be automagically be fixed

Edit: this is in response to the people with signal dropping issues
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chasesavestheday:
Are the options to customize the SMS thread gone? (Ex. changing the background / bubble color of messages sent vs. those received)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] juni0rz:
Wow really dude do you read the change logs
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chasesavestheday:
I apologize if I missed something, but I wasnt aware that the changes would remove features. Sorry?

- Switched Mms app (This one will be easier for me to work with and now works with Dark UI.)

- Increased mms size, height and width
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Search would also have helped. Options to theme have been removed from MMS.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niksha:
U mean update to the 5-21 rom right?? To answer your question-becuase it has been a good rom for me without any issues except this!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
If you don't want the updated ROM with fixes (including audio fixes listed in the change log) then that's fine, but then you also can't ask for help. If you won't wear the new underwear, you can't complain because there are holes in the old underwear no matter how comfortable :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EK2:
here's the answer
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arfarf2:
It's call blacklisting in the latest? If so, can someone tip me where it is?

Thnks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Phone settings
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godfirst:
I can assure you as of right now netflix doesnt work, I can get Netflix to load pick what to watch but video doesn't actually play. And that's been done with a full wipe etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godfirst:
I don't have the notification issue, it works properly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stoicism:
As per your linked post. Of course you should make a nandroid, that way you can just give it a try and go back to your old build if you need to. i use Titanium for apps, but never use it for data as the settings might not play nice with the ROM.

Just try it, that's half the fun. If you've got a backup its easy to just restore it if you're unhappy
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hightechlive:
Mine keeps blinking with no notifications
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godfirst:
Mine blinks like a bright white if I'm not mistaken during notifications and once I clear it, it goes a way. I've only been on the 7/28 and now 8/1 builds, previously coming from kyanrom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stoicism:
Ya, mine too. It just comes on randomly, sometimes just goes on solid, other times it blinks rapidly. I have the LED notification turned off.

I've tried restarting, wiping and reflashing, nothing works. Kinda driving me nuts, so I'll have to restore to a previous version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godfirst:
Maybe its hit and miss with some people,but I'm not and have not experienced it like that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Mine was goofy till I went in to the LED settings, changed the color (I picked blue :)), and rebooted. Working fine now (so far). But the change log makes it clear that it's not done, so YMMV (and mine :D)

One other thought - in "Display" did you uncheck "pulse notification light"? could make a difference...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
little behind?

Just think of it as going from WinVista to Win7 by doing clean install... So you decide to image your harddrive, copy some files over to your external, then you have to format, take a little bit of time restoring a few things, and you've got your image in case for some crazy reason you liked vista better, or the 7 install wasn't so perfect... Experience has always been the best teacher, by doing it multiple times... before you know it you'll be downloading over mobile data, flashing without computers around... keep at least one nandroid on the phone, use titianium backup for only recommended things, and follow the OP instructions in recovery... Even if you do have some data loss, whats the worst that could happen? Google keeps all the important stuff...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pdubcramp:
My LED notifications don't go away either. But I'm thinking it's only the case for non-system apps (in my case it's WhatsApp and Go SMS). I can't figure out any other reason why it would work fine for some people and not for others.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] godfirst:
Yeah I don't use those apps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
If you turn off notifications in the apps, and in LED Notifications, and uncheck pulse notifications, do they go away? If we could get one answer on how to turn them off, then we could work on how to selectively turn them on and add it to the FAQ.

FYI Gmail was what started mine blinking, after I changed color and rebooted (and turned off Gmail notifications) I now get correct flashing from Touchdown and it stops fine. So it's not just a third-party thing.

And please, everybody - we know they're busted - we don't need 5 more pages of "LED keeps blinking" posts - it makes for dull reading :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smeatr0n:
Yeah a bit, I hated it when it was on TV, but when I heard Netflix was bringing it back for another season I started watching it. I'm loving it now so I'll have to wait for Netflix to work before I can use this rom.

/end of off topic post, please don't yell at me I'm very sensitive. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
I'm the same way about Breaking Bad...just got into it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pdubcramp:
Unfortunately, I haven't come across any way to to stop the LED after it has started aside from a reboot. In Go SMS specifically, you can test the notification. I can't even get that test to stop blinking.

However I'm not a good test subject because my Gmail notifications aren't working normally either.

EDIT: LED light stops when the phone is in deep sleep and there is no notification. Comes right back on when I wake it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bitter Moose:
Anyone else getting horrible battery life with this? I'm getting like 3-4 hours with 20 minutes of screen time. I had to go back to ICS for now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eatonjb:
yea, I even tried changing the /storage/sdcard1 to rwxrwxt-x, but then I would remount the External SD and the perms would go back to --rwxr-x

I tried everything.. no go.. and I don't know how to manuely mount the SD card to a folder on the internal SD..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Intercrew:
Alright :) I got the stuff down now. Just one last, very last concern. The nandroid that I backup before flashing AOKP or any original android ROM's, it shouldn't be used in CWM for advance restore data, restore data once I'm done flashing AOKP? For example I backed up my nandroid from my stock before flashing Kryan ROM, but once I flashed that ROM, I went into the advance restore data option in CWM and restored my previous nandroid so everything I had before the ROM was "re-uploaded" while being on the new Kran ROM.

Thats basically what I just wanted to know out of all this hectic confusion :S

EDIT: NVM, so your not supposed to restore your nandroid for the original android development ROM's
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] camoto:
that's weird. ok thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
i would expect that to dump a bunch of crap into your data partitions, its still having data from touchwiz specific apps, that aren't in aosp... same rom to updated version of same rom, I don't see any issues with that, other people do that too, but if you see crazy issues from trying to restore user data like that from a touchwiz rom to an aosp rom, that's going to be the first thing people point out at... you have your nandroid in case...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Does the front facing camera image look elongated? The pictures are fine just the direct output looks stretched out with both orientations.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] captican:
re:modems

Would the change in bootloaders, as of the 5-17 build, change the modem? I noticed that the data connection speeds seemed to be lower today. If the answer is yes, then is there anyway to recover the version number for the older modem? I did not write down that information before switching to the 5/21 build from the 5/14 (or so).

Thanks in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Nope - no change - you're welcome to try other modems, but I'd blame the carrier or solar flares first (and I'm not kidding on the flares).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] F1reEng1neRed:
I'm not even sure what you're asking. The wallpaper can easily be changed under settings >display.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
S4 BOOTLOADER was just cracked and Cyanogen mod is running. Do you still have the S4 and will you be gracing us with your version of Aokp?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
1.) This is an s3 thread. The s4 can suck it in this thread. Please stay on topic.

2.) You don't read the internet much obviously.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Lol no soup for me. Gotcha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Actually, the Canadian version has the old modem (LK4) instead of LL1, which is the last one that came out.

Now I know this doesn't affect AT&T but figured I'd point it out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cirusnb:
Hi, I had the same issue, when i first flashed the boot loader, per the exact instructions. It was also killing my battery, i'm talking about 7% cell idle usage per hour, it was nuts. I'm on bell, and was running the I747MUMLL1 modem b4, and had no issues with battery or signal, speed on 3g or LTE

I reflashed the old the updated modem from here again. http://xdaforums.com/showthread.php?t=1831898 and its running great now.

it worked for me, please note this was from a fresh install, bootloader, full wipe.

regards,

---------- Post added at 09:57 AM ---------- Previous post was at 09:10 AM ----------

Yup, same for me, I posted right below you, you beat me to it LOL.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ParishM:
is there any way to block SMS / MMS messages in blacklist ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geokilla:
It's not the wallpaper. Take a look at the notification bar. See how it's light there? While the picture of the cat is dark near the top?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
I don't know what you're talking about but I would bet a hefty chunk of my net worth you didn't try redownloading and doing a full wipe after getting this issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
That's not the problem. You just lost a hefty chunk of your net worth ;)

That's cause the notification bar' alpha is set to 0% (fully transparent) and the lockscreen doesn't cover it.

I think if you set them separately, you should be fine. I believe they're checked to have their alpha set together by default.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Full wipe would restore his settings to default... Seems like there's some funkiness going on with that flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Settings -> Rom Control -> General UI -> Transparency settings

You can match lockscreen's alpha. I believe it's at 44% (112). If you have a theme installed, it might mess up with it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] noamaniac:
Is everyone running stock kernel settings out of the box or swapping governers and settings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
It doesn't really matter considering no one here has your specific device. You need to find the kernel settings that work best for your device. Also. If you would've followed XDA Rules and searched first you would have seen the hundreds of posts about this very topic. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibilln:
Can't turn off notification LED

Hi

Have tried varios combos of Rom_Control/LED settings but can't turn off the notification LED.

Get an email - get a flashing LED.

I must be missing something: Am seeking assistance from the worthies of the Q&A thread. --Thnx
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] F1reEng1neRed:
It's not in led settings. It's under settings >display.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] noamaniac:
Sorry task normally I run kt or lean but everyone has said for now I should stick with yours. this is my first time using underwear and I know a lot of commits were applied to it so I was just looking for a general consensus.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crewxp:
Has anyone had an issue with bluetooth on the recent build? I had this issue last year but haven't had it since today. I always do full wipes when I flash.

My phone doesn't auto connect to my car anymore via bluetooth. If I try to manually connect, it also doesn't work. I have to restart my phone to get it to work. Then to use bluetooth every time after that, I have to keep restarting my phone. Also, turning bluetooth off in options just freezes the bluetooth service. It says "Turning bluetooth off" for forever until I restart.

I'm sure someone else has run into this before. Any workaround/fix? ...or maybe something stupid I'm doing? :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] juni0rz:
Running the newest build and only problem I am having is during incoming & outgoing calls people can't hear me unless I talk with the headset on or speaker phone... Go back a build and its fine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] natefish:
I'm currently having this same issue. On the past few builds, notification, sms alerts, etc. work fine after my clean, fresh flash and restore, but then after a few days (this time just one day), I lose all sounds for anything incoming, including calls. Currently on latest build

Do I need to reset some permission or something? I haven't installed anything sounds related that I had on older builds. I'll try anything at this point to keep using this amazing rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bradld:
I resolved my issue by moving all sounds to the external card, moving them back, resetting permissions + rebooting. After that I verified in each app that the sounds were working. Not sure why that worked but hasn't been a problem for me on any subsequent builds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
Same here. Still trying stuff...........reload,reflash, full wipe, didn't help???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] natefish:
Thanks! Can you tell me how you reset permissions? Also, did you reset the permissions while the sound were still on the SD card? Thanks again.

---------- Post added at 09:27 AM ---------- Previous post was at 09:24 AM ----------

As I said, everything works fine after a full wipe and flash, but then something happens to cancel the sounds. Today, all sounds are working, so it seems something is intermittently causing the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bradld:
Use your favorite file manager program and note the permissions of the sound files before you try and move the files over. When you move them back they may end up with different permissions so use that same file manager to set them back to the same values. That's all I did and it worked for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] natefish:
Thanks. That gives me a direction to try and makes me think of something else: I'll note the permissions of the sound files now while they're working and then compare if they go silent again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] carpboy:
I flashed the bootloader and Task 5.21.2013, I find my IMEI is gone. Phone works, has data (stuck on G).

Any thoughts as to what happened? Trying to find a recovery, going to try something like http://xdaforums.com/showthread.php?t=1801997

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ParishM:
will flashing this bootloader cause issues with other ROMS should i decide to try something else ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
no it won't.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gtluke:
Yup new too, came in here to see if it's been reported. Let me know if you find a fix.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jointedman:
What happened to the 5/25/13 release?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
...? There's none AFAIK. Unless you think task sticks to a schedule.... which you're poorly mistaken.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Huh? I have no clue what you are talking about.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JamFan05:
OH NO! Task has started releases for the s4. I hope he doesn't forget about us lowly s3 users. Just messing around, I'm sure he won't. This is the best rom I've ever used. Thanks task for all you do for us.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InfiniteImp:
Not likely. See the P.S. in Task's post below.

http://xdaforums.com/showthread.php?p=41040896
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grubby0:
Oh but Task has a schedule. But it is his schedule and if anyone doesn't like it then GTFO. :D.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InfiniteImp:
That makes 3 of us with the Bluetooth issue in the 5/21 build. I haven't posted about it in the dev thread as it seemed to make sense to come here first and see if it's come up. Plus I haven't done enough on my own yet to try and resolve it. So far I've tried the following:

1. Installed 5/21 over the 5/17 build (dirty flash) and tested BT. Failed.

2. Factory reset and installed 5/21. Tested BT, Failed. Did this twice.

3. Unpaired and re-paired devices. Tested BT, Failed.

5. Re-installed 5/17 and re-paired. It appears to be fine again but I only tried once. I'll test more tomorrow.

In all cases, same Bluetooth issue (phone will not auto-connect when I get in the car. If I manually connect it, Bluetooth will work but when I get out and turn off the car, BT still shows as connected (blue icon as opposed to the grey icon). Interestingly enough, my BT headset connects and disconnects fine but only after a long delay. With the previous build it would connect almost immediately. With the new one there's about a 5 second delay. My guess is that while the BT headset waits that long, the car's BT doesn't which is why it doesn't link up. Trying to turn BT off at that point fails (just says at 'turning off bluetooth')

Rebooting the phone typically resolves it.

As far as I know that issue wasn't there in 5/17 but since I flashed 5/17 and 5/21 pretty close together, the issue may actually have existed previous to the 5/21 build. I'm back on the 5/17 build now so I'll do more testing tomorrow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jointedman:
i was looking at the S4 thread thinking it was the S3, i went back and looked at my history and i guess i must have been high to notice.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] F1reEng1neRed:
There is an entire thread on IMEI recovery in the regular development thread. Just wondering... Have you rebooted once or twice since you lost it? Sometimes that's all it takes to get it back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] carpboy:
Oh God yes, rebooted many times. The thread I referenced has suddenly disappeared as did a similar thread.

I have managed to get my IMEI injected back into nvm, that appears to be correct now, but I am stuck on minimal data, if anything at all, and voice usage is virtually impossible, just barely works and then for only a little bit.

The thread that is now gone had something in it about restoring data functionality after an IMEI injection.

But I've tried everything: ODIN'ed, all kinds of nandroids, etc., I can't get data and reliable voice. This was just out of the blue, very disturbing.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
This is due to the tool and the tut on ways to change the IMEI which is against XDA rules as doing so is against the law in many countries. So the tool is being removed from XDA. I will see if I can find the info for you. I would suggest if you get it back to working to make a backup of your EFS as restoring that will be the only way to fix this from here on out. Still not sure why they are putting this info in a place that could be over erased so easy.

Edit. Ok here is The contents of that threads 3rd post.

Create a QCN backup of your phone using QPST (see OP for instructions).

On a Windows Vista or higher computer download the app and install it.

Once installed,

close the app

.

Go to start menu, you will find app under DanX and run it.

(If there are any new updates the app will find it.)

Select your Carrier

If you need your IMEI injected then click the checkbox next to "Inject IMEI"

Upload your QCN backup into the app.

If you clicked the checkbox a window will pop up at this time asking for your IMEI.

**Enter it exactly how you see it on the back of your phone.

Select a save location and create a save name.

Verify that your IMEI is correct.

Click "IMEI Verified" button.

Wait and the QCN should be generated.

Go to the location where you saved the QCN.

Go to QPST and restore file into your phone (see OP for instructions).

Manually reboot your phone.

If you have a slow connection still but you're no longer on 2g reboot again.

If you still a have slow connection after that consider flashing stock again through Odin and then generate another backup using this app.

You can also try flashing a different modem and then generate another backup using this app.

If it still is not working respond to this thread.

Wayne Tech Nexus
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] carpboy:
Ahh, ok that explains it. Funny, even the cached Google pages disappeared.

Thanks for taking the time of finding and pasting that.

Oh and yes the nvm will be archived. I wasn't aware that there was a section of phone memory not grabbed in the nandroids. Sigh.

Update: The QCN creation tool fails, generic output file error message. Oh well...