yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
Guys I would like to restate that XDA is not a Rom site, A support site, or anything other then a developers site. Here you are expected to put in your own research and leg work. If you have an issue spend a few hours or maybe a day to get all the info you need and trying to track down and fix the issue. I see far to many people coming here and flashing roms and then thinking that is all they have to do. No one is gonna fix your issues except you. Take some time to learn. That is what XDA is all about. Teaching you how to do this yourself. And before I hear the whole "I dont have time for all that" if you dont have time to learn what you are doing and how to fix it maybe your should rethink flashing a custom OS that only has one support tech. You
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ballgum:
Sorry, I'll see what I can tweak... I thought it probably was a bug guess I was wrong...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
New release available in the OP for download or just check your OTA Updaters.

AOKP 4.2.2 Jellybean 5.17.2013

Updated Kernel

Reworked Dark UI (Dark AOKP now, and a lot of other changes.)

Updated cLock

Added Custom Density Settings (ROM Control/General UI)

Update mGerrit

Torch Updates

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

Fixed some Memory Leaks

Dynamic glowScale adjustment and spacing of NavBar

Updated Permissions Manager

Ect...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evodon84:
Task,

I downloaded the file with the OTA updater and then through my computer and transfered it over and when I attempt to flash either, I get the following error.

assert failed: getprop("ro.bootloader") == "i747 getprop("ro.bootloader") == "i747MVLDLK4"

I am currently running your 5.14.2013 version using TWRP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Update to the latest bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evodon84:
ok, my bad. will do.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xLordNitro:
Perhaps I'm incorrect but all I see on the root threads for AT&T is DLK3? The other providers have DLK4...should I flash one of those even if my phone is AT&T? If there's a different way let me know?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
This is an ATT thread with and ATT ROM. Other threads, carriers, ect.. dont apply here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xLordNitro:
I understand that. I have the AT&T variant. And the latest version that they have listed in the Root threads is DLK3, which I already have..that don't list DLK4, so how would I update to that bootloader then?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xLordNitro:
I don't mean to come off the wrong way..But..I'm downloading the file and its labeled DLK3, whereas your check before the install seems to be looking for DLK4? In which case flashing this wouldn't help? Perhaps I'm wrong
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You're wrong though. My assert checks for both. You are more than welcome to take a look if you need. AT&T doesn't have a LK4 release. Thats a Canadian device.

assert(getprop("ro.bootloader") == "I747UCDLK3" ||

getprop("ro.bootloader") == "I747MVLDLK4");
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xLordNitro:
Ah. My bad sir. I will flash that file and let the magic commence! Thank you again :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
After saying you wont have much time for this anymore, you push an update the next day. 5.17 works awesome. Great work && thanks again! Im going to donate finally once i get settled into my new house
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dalewest:
I've downloaded the file you linked to three times, but Odin keeps failing the MD5 check. Am I the only one?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Who knows....

There's a thread for that dude http://xdaforums.com/showthread.php?t=1781242

You could also just go flash a stock LK3 ROM if you're having issues. I flashed this just fine. Make sure you're using the PDA slot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bleedingthru:
I actually do practice this that's why if I have a random reboot or ect I don't come running here with a log and such I try everything first my self reflashing no apps ect cuz I do find it a little easier and I know the dev can help but why complain I'd rather have fun and enjoy my phone and the free service that task and others provide that I know that in a cold day in hell I couldn't do my self
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
@everyone

Try the new link in this post. Old one might have gotten corrupted in the upload.

@ Everyone

I've added the bootloader check that CM has added recently. You need to be on the latest JB bootloaders in order to flash this release. It has come to light that being on anything else could be what is causing all the issues that some may be having.

Directions:

1.) Make a nandroid backup

2.) Get Odin

3.) Flash this package with Odin

4.) Flash the latest ROM.

If you don't know how to do any of these things then you need to search for how to do so.

DOWNLOAD HERE
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Taken care of. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gtluke:
Still no good task.

Is your ftp in ASCII or Binary? j/k, what year is this? :P

<OSM> Firmware-Update_UCDLK3.tar (1).md5 is invalid.

<OSM> End...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I'm throwing up a mirror in case you guys are having problems with the server.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Remove the .md5 extension from the end.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Hmmm... Now my phone is being f$cked and wont let me log in. I'll be at a windows computer in a minute or so. I want to test that link that was posted earlier to make sure its alright. I would rather brick my device rather than you guys. Bootloaders arent really something to mess around with. This might be the easier way for me right now. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Link is borked anyway, so you've got time :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
@ Everyone

I don't have time to screw around. I just tested this and it works fine. I just would've rather bricked my device rather than yours. That's why I like to test all links for these types of things before I promote them off to you guys.. ;)

1.) Go here http://xdaforums.com/showpost.php?p=41503727&postcount=13716

2.) Put phone into download mode and then open Odin.

3.) Choose the PDA slot and then select the correct file for your device (AT&T is LK3)

4.) Hit start and wait until its finished.

5.) Done

5.) Remind me that I shouldn't be trying to do this from my phone. All it does it piss me off. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Blaze03:
Thanks task file from other thread you posted worked.. Running 5-17 now :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] martinomac:
Can confirm that the I747MVLDLK4 (Canadian): http://d-h.st/yqV version worked just fine for my i747M. Thanks for the link and new release!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
Good Again!

Thanks again Task. Now my MMS looks great. Thanks for all your work.

Smoooth!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
No need for confirmation here. This thread is clearly titled "[ROM] AOKP(Jellybean 4.2.2 )Task650 (5.17.2013) (AT&T)"

AT&T being the most important part. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] martinomac:
deleted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I push those commits. I know what they are. There's no need to post them here. Please stay on topic and stick to development in this thread. I really don't want things getting sidetracked on a Friday. Things can go pretty f$cked over the weekends. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rickriego:
im thinking bootloaders should be be flashed via desktop odin and not mobile..?

533d.oF.eLiTe.bR33d5
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MWilkenson:
http://xdaforums.com/showthread.php?t=1781242
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mumbo jumbo:
Yes desktop only. I asked this in Q&A thread and task advised
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] selw0nk:
I remember when I asked you about the dark mms app ever coming in future releases, and now you have it in your rom. Thanks dude!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] microcell:
If the Baseband version of the phone already shows I747UCDLK3 does it still need the bootloader updated before flashing new version of rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reluttr:
I take it that you do not need to do this if you have flashed the latest JB touchwiz at one point?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Please search on what baseband is. That's not boot loader related. That's the modem you're using dude. I've already advised users in this thread, the Q & A thread, in the change log, and at the download links to update their boot loaders. Please just follow the instructions in order to flash this ROM correctly. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
So I should be institutionalized? You're not the first to say that :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
f$ck autocorrect today. it's been killing me! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] microcell:
Thanks for clarifying it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NorskHelgen:
Anyone else having audio issue with notifications? After I wipe cache and dalvik the notification sounds stop working about an hour into using the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Follow the rules and read the OP before posting. This isn't a Q & A thread. This is a development thread. Thanks.

http://xdaforums.com/showthread.php?p=38843439&highlight=+everyone#post38843439
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Sean I did just this.^ It went through correctly but when I went to flash your latest it still wouldn't let me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I would just keep trying until it works. There's really nothing more that can be done. The reason for the boot loader update before flashing is beneficial to knock out a lot of the issues that some users have been having.

You could just flash back to the full stock ROM (LK3) and then start the process.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Today's release is running great. Thanks for the heads up on the bootloader! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NorskHelgen:
Between how disorganized and bunched your question and answer section is to the lack of clarification, it really does not answer my question anyway. Doesn't matter, this ROM isn't worth the bugs it contains.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
I am sorry you must have mistaken this for a rom site. :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] e2tango:
Just a heads up. I'm on Telus S3. I flashed the stock TW rom and did a complete system wipe. I then flashed TWRP and tried to use the new 5.17 rom. It still failed to update everything I tried (tried 5 or 6 times). Am I doing something wrong?

As a follow up< I was able to install liquid smooth 2.4 which also says the new bootloader must be installed? Any ideas why this rom won't let me flash yet the other rom will? Again, sorry to push this in here but just hoping this might help others who are having trouble flashing the new version of this rom.

Cheers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
I did that this morning still won't let me flash your latest Rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
I have root checker also and my screen shot looks just like yours, I followed Task instructions and I updated no problem and installed the 5/17. Every device reacts differently just keep trying bud.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
This ROM only contains as many bugs as the user can cause sometimes. Whether its disorganized (it isn't) or not, it seems as though you didn't comprehend what I was telling you. I'll break it down a little for you. This is a development thread. Google search if you don't know what one is. Questions belong in the Q & A thread. You can also Google search that also if you don't know what one is. In your original post you provided absolutely nothing for the troubleshooting process to even begin. This isn't a "Guess my problems" thread. It's a development thread. You need to provide the proper information.

Also. This isn't your personal help desk or a "my feelings are hurt and now I will act out" thread either. Take this elsewhere. Your opinion doesn't matter here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iTchill:
Ok..soo.. I get the status 7 error when i flash the latest ..lolololol

Just kidding everything went great !! Nice work :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wutbdat:
Kernels

In previous comments task suggests trying out different kernels to see which ones work best for certain phones. Can somebody recommend some kernels that they have have success with? You can just PM me the response to not clutter up the forum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
This is a development thread for this ROM and kernel dude. Please treat it as one. None of this post has anything to do with development. Read the OP before posting here. There is a link conveniently placed in the OP for these types of things.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justflorin:
What I did to get this bad boy working...downloaded the newest Odin and placed the tar file task provided in the PDA section, not boot loader. Afterward I rebooted and then went back into recovery (cwm BTW) and cleared dalvik cache and regular cache. I then flashed the 5/17 with no issues...I even did the gapps again for good measure.

With my extended battery, I got about 36hrs of off charger use with just over 7hrs of screen time.

Thanks for what you do task and like we used to say it the old axura days of sgs, haters be hating :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vapuri:
Google Hangouts - microphone not recording

Task, thanks for sharing a wonderful ROM. I saw some people reported this on the Q&A thread but without the proper info, so I thought I'll provide the log with some details if it helps.

ROM/Kernel version: AOKP 4.2.2 Jellybean Build 5.17.2013, Underwear Kernel 5.17.2013

Application: Google Hangout - latest version from the play store released May 17th - 1.0.1.678536

Issue: In a Google Hangouts video call, the microphone isn't recording which results in a one-way audio

Here are the relevant log messages (the full logcat is also attached):

05-18 09:28:31.692 E/AudioRecord(12520): Could not get audio input for record source 7

05-18 09:28:31.692 E/AudioRecord-JNI(12520): Error creating AudioRecord instance: initialization check failed.

05-18 09:28:31.692 E/AudioRecord-Java(12520): [ android.media.AudioRecord ] Error code -20 when initializing native AudioRecord object.

05-18 09:28:31.692 E/WebRTC AD java(12520): InitRecording: Failed

05-18 09:28:31.692 E/libjingle(12520): Error(webrtcvoiceengine.cc:1121): WebRtc:InitRecording failed (-1)

05-18 09:28:31.692 E/libjingle(12520): Error(webrtcvoiceengine.cc:1121): WebRtc:StartSend() failed to initialize recording

05-18 09:28:31.692 E/libjingle(12520): Error(webrtcvoiceengine.cc:1121): WebRtc:StartSend() failed to start recording (error=10028)

05-18 09:28:31.692 W/libjingle(12520): Warning(webrtcvoiceengine.cc:1855): StartSend(0) failed, err=10028
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] minieli:
I've tried to watch videos on reddit sync lately and keep getting these errors:

Here's my logcat:

(Running 5.17.2013 build, underwear kernel)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] f_E_a_R_e_D:
Can I flash the bootloader with Mobile Odin, I have searched and that is why I am posting here.

EDIT:

No need it worked and I am ready to flash 5/17 release
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Search again. This has been answered here and in the Q & A thread. You might just wanna read my instructions that are posted in two different places in the OP. Also. This post doesn't belong here. There is a Q & A thread for these types of posts as this has nothing to do with development. Use Odin dude.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] i5lee8bit:
Tried to post this seconds after the short thread lock...

Wow, all the kernel commits from today put a party in my pants. Won't even have a chance to install the rom til after the weekend, maybe that's a good thing.

3HH37326A39035604

Gave u and KT equal amounts... You both kick arse. Hope u get that s4 covered soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Thanks man. I appreciate it. :highfive:

P.S- I didn't mean to lock thread. XDA was screwing with me on my phone and kept activating the lock. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KiiKeEp:
Tried to flash on TWRP 2.5.0.0, CWM 6.0.3.1 and both gave me "status 7" error, downloaded the ROM file 3 times too, and the same..

Any solutions? :S
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Use the Q & A if you want suggestions. Otherwise just follow the instructions in the OP and you should have no issues. Make sure to flash the correct recovery for ATT devices (d2att).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
task how can I know if I have latest bootloader? Instead of go flashing bootloader right away :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
There's a Q & A thread for things like this. Please use it.

You would think just trying to flash the ROM would help you figure this out pretty easily. If it doesn't flash, then there would be one logical answer for it. You would need to update the boot loader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tamkhanh:
There are apps for that. Read back couple of pages and you should see a screenshot of the app. And q&a thread should have more info as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SophisticatedRetard:
Awesome release as usual task :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rickriego:
it won't work mobile. I tried.

533d.oF.eLiTe.bR33d5
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlbjmb35:
Follow the opp guys, it's simple and works!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Yes. I've already stated that here and in the Q & A thread. Its has been established that mobile Odin is not to be used. No need to beat a dead horse here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pilothaz:
Funny mobile worked for me. Again thanks for the slick rom task!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reup247:
No it didn't. It does not touch the bootloader. You probably had already used the stock JB ROM..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arfarf2:
Free android tools root checker is the thing to get to see the real story.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Nope. It didn't work. You were already on the latest bootloader. Mobile odin won't touch bootloaders as stated below.

Yep. ;) :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dillis:
love the new dark ui,amazing idea,great for battery life,keep up the good work! my favorite rom for sure:good::D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jazenf:
I'm trying to flash the new update but it keeps crashing in cwm recovery. Is or did anyone else have that same problem and how did you fix it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mcnutty:
Read the directions...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] F1reEng1neRed:
Yes, others have reported this problem. Had you searched, you would already have your answer and you wouldn't have found the need to post in the wrong thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayRokk:
I got you bro!!

Use this!

It fixed my problem right away!

http://xdaforums.com/showthread.php?p=38843439
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jazenf:
Thanks everyone for your quick reply, I got flashed and I'm loving:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nopnopnop:
Some people say "Semper Fi" is the US Marine Corps motto. The real motto seems to be "I don't have time to screw around." ;)

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rickriego:
they say that cuz it actually is our motto.

533d.oF.eLiTe.bR33d5
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Really? No way?!? *tons of sarcasm* ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bballer182:
Isn't "Semper Fidelis" the ACTUAL motto??? :):):):):p:p:p:p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Well, the "official" motto. But in my experience, generally it's either "what the f*** are we waiting around for" or "why the f*** are we doing this" :good::highfive::highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grubby0:
Just because. Confirmation number: 2VX369671D8592406
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] martinomac:
Thanks dude!

6E780771YF472523M
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Thank you dude. :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
Task, just wanted to say thanks for adding the cell broadcasting a few releases ago. I'm about 2 miles northeast of Moore, OK and for a while there we were in that tornados crosshairs. Those cell broadcasts are what alerted me to the fact that sh!t was getting very real.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mart3n1uk:
I just purchased my i747m and flashed Task650 5.17.2013 with stock kernel. I love how smooth, fast and stable everything is on this ROM. I was getting questionable battery life so I tried flashing Ktoonsez newest kernel to compare stats and got stuck at boot loop. Anyone else experience this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
That would be a question better suited for KT's kernel.

Either way, sounds like you flashed the wrong version. Make sure you grab the 4.2.2 version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
1.) This is a development thread. Please treat is as one.

2.) Please read the OP before posting here. There is a Q & A link conveniently located in the OP.

3.)This thread is only to support this ROM and Kernel provided in the OP. Go to ktoonsez's kernel thread if you need support for that kernel.

4.) http://xdaforums.com/showpost.php?p=38843439&postcount=24316
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mart3n1uk:
I'll check and make sure I flashed the correct version. Thanks!

Edit: Sorry Task, I'll make sure I direct my questions to Q & A. Thanks for the Fantastic ROM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Followed OP instructions and it's been working perfectly for me along with the underwear kernel. Whenever I try a different kernel (BMS or ktoons) I get constant reboots, but I know that isn't supported here since it's not the kernel included. Thanks for your hard work, man.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
That's a really cool story and all, but why are you posting this here? You even say yourself that it's not supported in this thread? Weird. Please stay on topic. Thanks.

You're welcome.