yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
1.) There's no need to post other ROMs with a line of code removed (if that's what you're saying.

2.) All it takes is removing the line....

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

getprop("ro.bootloader") == "I747MVLDLK4");
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x0ne215:
I was referring to posting:

So other people who have the same question can just get the answer right there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MallCop:
Task,

You do excellent work here, thank you for putting up with the knuckleheads so that the rest of us can use your ROM. Your 'don't take sh*t' attitude has kept me from asking questions that I eventually found the answer to on my own by searching for a few minutes.

I don't understand the mentality of people who demand answers from you...I've never had a problem that couldn't be fixed with a wipe/reflash or a search of the Q&A thread. I do have an occasional random reboot, but since I've started tweaking the kernel settings it's gotten much better-from several times a day to once every few days (it's a work in progress).

Keep up the good work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jazenf:
Loving this ROM first off. Is there a file that I can flash that will allow me to boost the volume higher?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
1.) Please read the OP before posting in this thread.

2.) After reading the OP will you post this in the appropriate thread. This is a development thread. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rwbarnes67:
There's this thing called the Play Store.....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] A.VOID:
Seeing reboots coming out of sleep. I'm trying to raise voltage +25 on 378 setting.

When is the 189mhz setting used? Stats not showing any time in 189.

Everything else very responsive for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
That sounds pretty awesome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] A.VOID:
True, but about that 189 setting?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Works great.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
If your min frequency is set to 378 then anything under that will be unused.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rattles:
i will keep it short and sweet since it is a bit OT. for the past 2 months i was forced to use the iPhone due to work and yesterday i went back to my S3. i did a full wipe, installed the latest version of this ROM and i all i can say is that all is good in the world again. i can't even tell you how much i missed this rom and this latest version is incredible.

awesome work as always Task!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsterrette:
Random Reboot

On 5.21
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bleedingthru:
one reboot dont mean its broke have you tried fixing this your self ( and its not hard to diagnose)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] F1reEng1neRed:
Not what I would call a great first post. Are we playing a guessing game? You provided absolutely no background or context. What exactly were you doing when this happened? Can you reproduce it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Subject is random reboot and last_kmsg was attached. But nice snap judgment from your phone. Better first post than most people manage, so don't discourage - maybe be helpful? ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] F1reEng1neRed:
Snap judgement? Not sure what that's all about considering I read the last_kmsg and without background or context it's not a lot of help. But nice snap judgment from your pc. :D

But you're right... It is more than what we usually get.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsterrette:
Never said it was broke and wasn't complaining. Far from it actually. Looked over and noticed it had restarted - wasn't doing anything.

Simply wanted to provide the information that I did have - last kernel msg and version I was running. The once in a blue moon restart is so worth everything else that's in the rom, but I figure it might be something task would like to see..

I thought that was the protocol on a random reboot... please let me know what would make the post better so that my next post is more helpful.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Try upping your voltage 25mv across the board. If you get another reboot try another scheduler/governor.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] F1reEng1neRed:
No problem. Are you undervolted or overclocked? What gov/sched are you using? On tasks kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsterrette:
Out of the box 5.21 release. Yes on task's kernel. No undervolting or overclocking. Governor never been adjusted (interactive), neither has scheduler (deadline)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] F1reEng1neRed:
And you weren't doing anything at the time? As the poster a couple posts up suggested, bring up your voltages. I know that has proven helpful to others.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsterrette:
Nope, it was just sitting there... like I said.. not a big deal at all. Just thought the info might be useful.. I'll see of it happens again and if so will play with the voltages and report back.

Appreciate it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gyasih:
delete
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Franky_V:
I bumped all mine up 50mV ,as per tasks suggestion, and I have not had a single reboot since.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bleedingthru:
sorry for being to brash but ya i would try what these others have suggested but also try the q and a forums for this rom as well and maybe an app on your phone casued the reboot there are so many variables thats why alot of users get annoyed lol but i will help too as much as possible without straying OT
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niksha:
thread closed every sunday??))

is this forum closed every sunday cuz there are too many nutters around or is it my imagination?!!seems like the mods close it down or everyone chills and noone posts??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Huh? I have no clue what you are talking about. I only close this thread when the trolls and whiners show up here and act out like children. Otherwise its always open. So no. It's not closed every Sunday. Let's stay on topic here. No need to stir the pot. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] selw0nk:
Because they will get flamed and being asked to go to the Q&A and this is a development thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Ahhh... That's cute. I notice you are one of the guys that comes in here and only thanks the users that come in and cause problems. Gold star for you on that one.

Also. Please get your facts straight. Yes. This is a development thread. And no. Just because users are directed to a more appropriate place for there non-development related posts doesn't make it flaming. There is a very simple thing that those users can do to avoid being redirected. Just simply read what we've taken a lot of time to provide and make it easy on everyone. It's called the Q & A that is conveniently located in BIG BOLD LETTERING in the OP. Most will just skip the OP and start posting here when their answer is already taken care of in that very detailed Q & A/FAQ. ;)

Please stay on topic or stop posting here. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I haven't forgotten about this device or anything guys. Just been really busy with work. You'll probably see an update tonight or tomorrow sometime. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rbedell:
Take your time man. No issues here. :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ac3theone:
Loving this roms stability so far, nice work tasks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsr84:
I'm going through flash withdrawal. lol!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
You mean there's something else for you to do on this rom?

**** man, I thought it was done!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] derberts:
Google should just throw in the towel and use your code.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reaganSMASH:
Samsung, not Google.. but I couldn't agree more. As always, thanks for your hard work and awesome rom Task!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EPC7:
Let's see if I can log this issue right :)

Just moved from a Galaxy Nexus to SGS III, and this issue did not occur on the GNex or stock ROM, so I figure it's something to possibly report. And to preface: I've done a full format/reinstall of the ROM in troubleshooting, and I'm trying another one right now for S&G.

Symptom:

Device loses Bluetooth functionality. Bluetooth cannot be toggle off (Clicking Off results in a "Turning Bluetooth off..." text that does not resolve). Bluetooth devices do not receive proper signal from the phone. Attempting to remove devices and re-pair them results in similar oddness. New devices cannot be added. Resolves with phone reboot. Problem occurs about 8-12 hours after boot or so.

Conditions:

SGS III running Task650's AOKP 5.21.2013 (happened in earlier builds too)

Following Bluetooth devices paired: Pebble watch and UE9000 headset

Bluetooth device usually connected: Pebble watch and running associated app

After 8-12 hours, Pebble watch stops receiving notifications. Attempts to disconnect/reconnect the device or turn Bluetooth off and on fail.

Resolves with reboot (Also have to un-pair/re-pair the the Pebble and UE9000 to get them to work again)

It might be something with the Pebble app, but this didn't occur on my GNex or while this phone was running stock. Attached is logcat file I ran that had the issue occur while that log was recording. I have earlier logs that started near boot if that would help, but the watch was receiving signal from the phone no problem during those.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
No logs needed for this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Cool story, but you didn't do the first thing first. Read the OP, the FAQ, and check the Q&A thread, and then search the thread (and other threads). Bluetooth issues are well known and reported over and over and over. Also, some reading would have shown you that comparisons to other software (or hardware, which is really extreme) have no value.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Yea I vote we don't discourage informative well articulated issue reports like EPC7's (FWIW). Other BT reports were subpar.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
That's cool. But when an issue has already been reported more times than I can count, we really don't want to encourage that either. It's just annoying getting the same report over and over and over and over and over and over and over and over and over again. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
https://www.youtube.com/watch?v=hOXqIQKJakQ&feature=youtube_gdata_player
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You're more than welcome to fix anything you like dude. Contributions are always welcome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] EPC7:
Well, unfortunately, some of the typical QA repositories are not being updated all too well, like the first post here: http://xdaforums.com/showthread.php?p=29198513 I also don't want to say "OMG but searching is haaard", but there's a ton of noise when it comes to feedback, and sometimes it helps to rely on a feedback aggregator.

Also, normally "duh" on the hw/sw comparisons, but if you saw the first couple iterations of the Pebble sw or fw, proving that it's functioning normally on other systems is actually a valid step to take ;)

Anyways, enough self defense. For the record, I've been using Task650's work since the first say of owning a sgh-i777, though I've only really posted on here to help with my g/f's nightmarish Atrix. And this is now enough noise in a dev thread: I only shared cause this is the first time I've seen an issue that: A) annoyed me and B) lingered more than a couple releases in this ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
1.) This is a development thread. Please treat it as one. Not sure what this has to do with anything here.

2.) Your report has been reported a ton of times. There's no need to beat a dead horse here. It doesn't get anyone closer to the goal.

3.) If you feel as though you need to defend yourself, do it elsewhere. XDA has a nice pm system for these types of things. If you have an issue with something that someone says , either leave it alone or pm them about it. There's no need to bring it into a thread that I maintain.

4.) Please stay on topic here. Thanks.
[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.27.2013

Updated Kernel (Linux 3.4.47)

Fixed the No Sound in Google Hangouts

Phone apk updates

mGerrit updates

Ribbons Overhaul

Added Transparency Setting for Lockscreen

Updated Dark UI (Moar things, moar dark)

Update some proprietaries

More... busy...sleep now... ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nappent:
The op link is downloading an April 27 version. Just a heads up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Try again...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
Looking through the changelog, I don't see an April 27th release, so its probably just a typo...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
All is good :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pilothaz:
Pumped for the hangouts fix. Cheers.!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Running great, underwear and all!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maDIEmG:
Besides the bluetooth issue of not syncing everything else so far on 5/27 is working flawlessly for me, still the best rom eva! =D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jonnyredcorn:
Bluetooth works fine for me, I did a dirty flash via ota updater.

Loving the new dark ui keyboard.

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neumanntm:
Hey guys, I read through everything and I installed everything but I seem to be caught in a boot loop? It's stuck at the SWAGGER ACTIVATED and it won't progress from there. Any ideas? Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mcnutty:
First, probably best to use the Q&A thread. This one is development only. Second, follow the directions in the first post. If at first you don't succeed, try them again until you do.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vastelectron:
Anyone noticed when using the flashlight phone gets really slow, freezing up or unresponsive? Is it just a CM10 problem?

Another strange random issue I noticed strange screen artifacts kinda like over clocked/heated graphics you'd see on computer but phone still works fine.

Thank you for this beautiful ROM (5/21 ed)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpasilliumNexus:
You've been here since 2007 to know that you should always read first, and by reading first you'd know that questions like these don't belong here, right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vastelectron:
I don't see how your post is useful. I'm only asking others if they experienced the same.

Most posts here are mostly comments and non ROM related anyways. So shouldn't waste time posting a none helpful post & Thanks for the tips. Seen it before
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
Task only wants development related posts here. Just because you've seen it doesn't mean its permitted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibilln:
Yikes! Battery!

The battery seems vastly better in the 5.27 version. Wondering if any obvious change for this? This -includes- the download, nandroid, and new flash. Then w/wifi/gps off, a bit of calling, twitter, etc, (Dirty flash from prev.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Check tasks source..... you can easily see what he merges/cherry picks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
1.) This is a development thread.

2.) Please use the Q & A.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slam666:
Since the last 2-3 rom my Bluetooth is not working correctly in my car. Right now I can use my phone and place a call and it is working perfectly thru Bluetooth. If my phone ring and I want to use my car to answer it does not work, also if I want to use my car to make a call it does not work either. My phone connect with no problem to my car. Seem to be a problem with the car talking to the phone but the phone can talk to the car perfectly, weird.

Thanks for the best rom around.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Sounds pretty awesome. Let me know when you fix it. You've given no information for me to look into anything so it's on you to do what you can. Also. Bluetooth has been a known issue for the last few builds. Please search the thread before posting here as this has already been reported multiple times already. Patience.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tunasty:
Just wanna say that this rom is running smooth as a baby's butt lol. Great job Task!

Current setup: Task's AOKP + BMS
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shadowronemus:
This ROM just keeps getting better, I've never had an issue other than ones that you've let us know about and I flash nearly every update. I use my S3 more than my S4 because this ROM is just that damn good. Thanks as always.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joeyl:
Thank you for the hard work :good:

Next pint is on me:

9U515246NU020364T
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] noobchef:
Thanks for the awesome ROM. This thing is crazy quick and smooth. I have enough options to keep me busy till I get flash-happy again:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lNOFXl:
I don't post lots, I usually don't have the time but im taking the time tonight. I have to say that I f*ç&î;- love your rom. I mean I do get the odd (while fairly rare) force closes but its definitely not going to sway me from loving it so much. So thanks for the awesome work and don't quit... For the love of God! :D :rolleyes:

Sent from AOKP Task650 :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheemer:
This rom runs awesome now on my phone... No f/cs
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rbedell:
Force closes are a thing of the ancient past lol. Task squashed that back when we first got the 3.4 kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KeeperOfThePizza:
Running good here. No issues so far.. Battery seems to be draining quick but I'll give it time first. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mag-netic:
***Since the last 2-3 rom my Bluetooth is not working correctly in my car. Right now I can use my phone and place a call and it is working perfectly thru Bluetooth. If my phone ring and I want to use my car to answer it does not work, also if I want to use my car to make a call it does not work either. My phone connect with no problem to my car. Seem to be a problem with the car talking to the phone but the phone can talk to the car perfectly, weird.***I have the same problem!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Huh? What are you talking about? Please use the quote but when responding in this thread!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Battery life is subjective to the user, not the ROM. You will need to find out what is draining your battery and squash it. We don't own your phone, use the same apps, use the same settings, live in the same area, ect...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KeeperOfThePizza:
Yeah of course it is. I'm not using much. Other than Apollo Music, Instagram for Apps and GPS, Sync, NFC, Bluetooth, always off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justflorin:
Try doing a fix permission within recovery or ensuring you get a full charge or even rebooting once in a while.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lukkaz:
Just wanted to stop by and say thanks task, best rom I ever flashed keep up the great work!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fvargasfrank:
Yes I notice this to, its then only issue I found with the new rom other than this is running good
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andy_d0:
Hi. I'm not exactly sure how troubleshoot this but the attached shows what is happening. For some reason, I keep getting a grainy background that disappears / reappears. I have not been able to replicate it. It just happens randomly. If I click on the power button, it'll go away. Moments later it'll come back

Has anyone else experience this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Increase your voltage - that usually does it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikewestlake:
I would move this to the qa thread listed in the op as it's particular to your phone and an older issue.

typically, you need to wipe and try again to make sure of a good install and test without installing backups of apps (via titanium) to isolate what may be causing it.

searching will provide answers to try like disabling hw overlays which should make it go away. this is not a fix as the base rom does not do this for most people. I say most when it may mean almost everyone. mine certainly shows no problems like this.

it's also helpful to specify what versions you are running.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Should I be concerned?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Well, you should be in the Q&A thread at least - and probably in the Q&A forum posting your own thread, since I don't see what this has to do with Task's ROM...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Not in this thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Draiter:
Getting the same thing...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andy_d0:
I ended up switching to ktoonz kernel and it seems to be ok for now. I wasn't sure what to do with the voltages so figured if just try a different kernel for now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Deleted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Clipse79:
OK I came here for the exact issue. Can someone direct me to kernals, as that is something I have yet to dive into..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Psssst.... hey task...

HAPPY WEEKEND!!!

;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
They r in the same sub forum as this thread
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Those things that are plainly labeled in the appropriate forums? Hint: Development and Original Development.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Clipse79:
Think I got it. Sorry I am still learning some of this stuff but I appreciate the direction.